Agreed, your mileage may vary on the exact timers to use (I ended up at 900 seconds), but synchronizing MAC and ARP aging timers should solve your unicast flooding issues, assuming the traffic is to legitimate destinations.
Have you captured any traffic to identify the destination of flooded traffic? -- Eric Cables On Thu, Aug 6, 2009 at 9:35 PM, Kevin Loch <kl...@kl.net> wrote: > C and C Dominte wrote: > > Thank you for your advice, however, increasing the timers >> did not work. >> >> >> I powered down the active linecards from switch 2 >> yesterday to see if it stopped the unicast flood, which it did. >> >> Today I increased the mac address syncronisation activity >> time to 640 and the mac address aging time to 1920 (3x640) as below: >> > > While I have not run 6500's in VSS mode I have run into similar unicast > flooding with certain non-VSS configurations of 6500's. The most > reliable fix I have found is "arp timeout 120" in the affected vlan > interfaces. > > - Kevin > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
