01-12-2004 03:52 PM - edited 03-02-2019 12:50 PM
After using 'sh looktable' to identify the MAC address which causes this error, what do we do? This host is downstream from our 5500 across an ATM link. It keeps coming up in the MLS Notification and eventually we get this error: %MLS-4-MOVEOVERFLOW:Too many moves, stop MLS for 5 sec.
Now that we have the host identified, what next?
Thanks.
01-13-2004 05:30 AM
dear sir,
the key is to identify why the host's mac is been reported on 2 different links on the same LAN.
so focus on the "show mls notification" output that shows all the ports that mac was reported on.
Identify the only port the traffic should be coming in on, and figure out why the other ports are recording that mac address.
if you don't have the cisco doc that talks about how to troubleshoot mls too many moves, go to URL: http://www.cisco.com/warp/customer/473/62.shtml#t5
05-18-2004 01:36 AM
Hello,
we are also troubleshooting such a problem.
Do you know if I can clear the output of:
"show mls notification".
Or is it possible to get a timestamp with this show command?
With kind regards, Peter Muilman
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide