#Juniper srx show mac address on interface series#
Show ethernet-switching mac-learning-log (QFX Series Switches, QFabric, NFX Series Devices and EX4600) show ethernet-switching mac-learning-log Show ethernet-switching mac-learning-log (EX Series switch) show ethernet-switching mac-learning-log Output fields are listed in the approximate order in which The show ethernet-switching mac-learning-log command on SRX Seriesĭevices. The log displays the name of the interfaceįrom where the MAC address moved, and the name of the interface toĭisplays the MAC address flags in which the MAC event
When a MAC address is moved, there is another field with The name of the interface on which the MAC address is Or moved from one interface to another interface. MAC address that are added, learned, deleted, changed The name of the VLAN on which the MAC is learned. A value defined by the user for all user-configured You probably want to be a bit careful creeping much past this if you want to push bits for a long amount of time as this traffic is generated from the internal em0.Ethernet-switching mac-learning-log Output Fields Now, if you execute the above command 25 times, I found this generates about 850Mbps of traffic. I thought it was a great idea – and now I’m sharing it with start shell Since this wasn’t quite enough traffic – a suggestion (not mine) was to drop into the shell and queue up a bunch of jobs to do the same thing. Increasing your ping size, obviously results in a larger amount of data being dropped on the link per ping. By using rapid – you’re forcing the ping to continuously send traffic before the previous request has expired, effectively doubling the amount of data on the link. In practice – this command netted about 67Mbps of traffic dropped onto the link, looping about until the TTL expired. * this must be the MAC address of your local interface so you’ll accept the traffic */Īrp 1.1.1.2 mac ping 1.1.1.2 source 1.1.1.1 routing-instance LINKTEST size 65000 count 200 rapid Interface show configuration interfaces xe-2/1/3 I modified this somewhat in that I created a routing-instance type virtual router, placed my interface in that routing-instance and performed the tests noted above so that you’re not mucking about in the default routing-table should you mess something up with your IP allocation, show configuration routing-instances LINKTEST You can follow the steps outlined here to generate some traffic. We probably want to generate some traffic to determine if any of the equipment involved in the loop is responsible for that pesky CRC you’re trying to find. So you’ve been receiving errors on your Juniper router, and asked your local provider to drop a loop on the cable facing your box at some point in the cable run in order to divide and conquer.
0 kommentar(er)
