But, in the case being described, these one-way conversations will far out weight the normal two-way conversations. I hate perl, so i leave the perl solution to smeone else. Under normal conditions, such conversations would be rare and only a few packets. Here is 'tolower' used to convert uppercase hex-digits to lowercase hexdigits, then the MAC address is split in the 6 blocks divided by ':' by the function 'split' and with the 'printf' thoses blocks are recombined to the MAC address in 'cisco format'. With two Cisco ME3600 (or similar MPLS & VPLS capable devices) running recent code 15. from netaddr import fh open('mac.txt', 'r') for line in fh: mac EUI(line) mac.dialect maccisco print mac fh.close Put all the MACs in a text file and then it will print out the MACs. There will be packets in the capture going from MAC address A to MAC address B but zero packets going from MAC address B to MAC address A. I was able to put together the following Python script which uses netaddr to convert the MACs. The solution is to set up each point to generate MAC Notification traps when a MAC address is added or removed from the network. iptrace or tcpdump) on the SEA show a large number of conversations at the ethernet level to be one direction. (2) netstat/entstat shows very large numbers of "Hypervisor Send Failures" on the Virtual Ethernet Adapters (VEAs) under a Shared Ethernet Adapter (SEA). The send failures normally would be roughly equal to the sum of the "Hypervisor Receive Failures" on all of the virtual clients but in this case, they will not be. we have mac address and our port is sticky as shown in figure below. For this, remove the interface from PC3 attach it to another PC as shown in the figure below. Now, we do not have MAC address of PC here. The etherchannel may or may not be part of a SEA. The following commands will apply this concept. (1) When an etherchannel in 802.3ad mode is set up, netstat/entstat shows the LACP Partner "Synchronization: OUT_OF_SYNC", errpt shows ECH_PORT_OUT_OF_SYNC and the "Received LACPDUs" not incrementing. The switch detects this as a loop.įor more information about this message, refer to following link.įollowing symptoms may be observed on AIX/VIOS lpars when "FWM-2-STM_LOOP_DETECT" message is logged in the switch log. This message indicates that the switch receives frames with the same source MAC address on these two ports and that the swtich learns the same MAC address on these ports at a very high speed.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |