This problem happened few hours ago in my network.
%SYS-4-P2_WARN: 1/Host 00:05:31:df:b8:09 is flapping between port 3/46 and port 2/1
I discovered a loop in a switch layer 2 connected in my port 3/46. The port 2/1 is a trunk port, I have a Catalyst 4006 with a module RSM, I have about 25 vlans. There is another trunk port 2/2, both are connected in GigabitEthernet's RSM 3 and 4.
In this moment everything ok, but I wish to know why this happen?
By its very nature, a "loop" means packets keep circulating the network endlessly. When that happens, suppose there is a host with a MAC address 'M' that is actually 'seen' on gig 2/1. So the switch would add the mac M in its cam table and associate it with port 2/1. Things are normal so far...
now when a loop occurs, the packet sourced by that host are also circulating your network through the 'looped' port 3/46. This makes the switch 'see' the (looped) packet coming from 3/46 and it 'relearns' the MAC M on port 3/46.
So when there are a lot of cam table changed like this i.e. first learn from 2/1 then 3/46 etc...you get a syslog printed as what you got.
But, what I can't understand is the mac address in conflict is the mac address for internal Catalyst's trunk port 2/1. All my vlan's default gateways are configured in my router switch module, and if I look arp's table in RSM, all have the same mac address. Ok it's correct, but why port 3/46 connected with a switch in other floor, Catalyst "seen" the same mac?
The reasoning still remains the same. The syslog that you see is generated only when the switch see's a particular mac address onetime on port x and another time on port y changing rapidly.
This L2 ethernet frame could be user packet or a system generated frame. As long as there is some looping mechanism in your L2 network, the switch would 'see' the same packet once on the original port and another time on the looping port.
Do you happen to have Dell desktops in your environment?
Why I'm asking? Well, we are running into a similar problem where multiple Dell desktops seem to boot up after a power failure, all using the same particular MAC address. Since we are running DHCP all desktops get the same reservation, e.g the same IP address. The OS (Winblows) never detects an IP address conflict since the MAC address is the same. The MAC address seen is typically not the MAC address of the Ethernet Adapter. So far we narrowed it down to a BIOS related issue and will escalate to Dell to have them investigate.
Don't know if this helps you, but if it does, please post reply and let us all know, as this might be more generic in this case.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...