Packet flooding : MAC address table forgets entries

Unanswered Question
Aug 9th, 2007

Greetings all,

I am working on a strange problem here : there is a switch (Catalyst 2950-24, IOS 12.1(9)EA1) that "forgets" the MAC address table entry of another switch (same type and IOS), despite the direct connection between the two (EtherChannel including Fe0/23 and Fe0/24).

The effects are quite nasty : any IP interaction (a ping, for example) with the VLAN1 produces a flooding of packets, which are eventually destructed due to TTL expired. By so, many packets which should be switched get discarded.

The problem has appeared on 2 of my LANs recently, without any structural change or upgrade. After boot or a direct ping between the 2 switches, the situation is OK as long as the MAC address table keeps the entry. The problem appears after a moment, which seems to equal the MAC address table aging time.

A quick fix that works is to set a static Mac Address Table entry ("mac-address-table static" command), but it remains quick & dirty.

Besides, I would really like to understand what can make Mac Address auto-learning fail like this. Any idea ?

(other technologies involved at LAN level are STP and HSRP)

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Richard Burts Thu, 08/09/2007 - 03:26


There are several things that can cause the unicast flooding that you describe. Probably the most common is the difference between the timeout of the ARP cache and the aging time of the MAC forwarding table (much shorter by default). Basically the issue is that the ARP table has the MAC which it learned and if an IP packet is to be sent to the other switch, it puts the destination MAC into the frame since the ARP table has the MAC. But the MAC forwarding table has aged out the MAC (and since packets from the IP of the other switch have not been received for a while it has not relearned the MAC). So the frame is flooded to all ports in that VLAN. The solution for this is usually to change the ARP timeout so that it matches the MAC aging timer.

I am surprised that this appeared recently, since this behavior should have been present all along.

Change the ARP timer and let us know if it fixes the problem.



eric.ternant Thu, 08/09/2007 - 04:25

I have made the change (value 300) on the VLAN1 for both switches, the problem is still there, unfortunately.

Anyway, is it a setting you would advise me to set on all my LANs ? If so, one could ask why those 2 timers have different default values...

What strikes me most in this case is that once the entry is deleted from the table, it is never learnt again automatically. I have to set it manually or launch a ping from the other switch or from a nearby router to make it enter the MAC Address Table again.

glen.grant Fri, 08/10/2007 - 16:57

you might want to try upgrading the code too 12.1.9 that is ancient and could have bugs in it .


This Discussion