i finally followed this document's recommendation and configured 'similar' timeouts for both arp and the macaddress table. things have settled down now, but i was wondering if anybody out there has seen this problem and if you would recommend actually giving the mac-aging-time more time (say 5 hours) so that arp works its magic first and unicast flooding is mitigated.
Re: [unicast flooding] arp-timeout vs. mac-aging-time
I feel having a larger value for mac aging time is fine to resolve this problem, and don't see any major issues. But, you may have to think of any negative effects that might occur like using more memory to retain the MAC addresses and packets being forwarded to a machine even if it is not available etc. Ofcourse, you might be able to mitigate certain problems by increasing the aging time only for certain vlans. I am also wondering if VTP pruning will also help in anyway if a machine is no more available on the network. But, the solution suggested in the document gives best of both in my opinion, unless you are concerned about flooding frequent ARP broadcasts.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.