08-14-2007 10:37 PM - edited 03-05-2019 05:54 PM
Hi,
I have a really strange loopback problem..
Sometimes, when my network topology change (like a link goes down), about half of my 802.1q trunks over the network goes err-disabled because of a loopback detection.
I've triple-checked... There's absolutly no loopback not managed by STP on my network.
I really don't understand why only half of my switches are detecting the problems and others don't...
I have about 120 switches on the network (80X2950 (12.1(20)), 30X2960 (12.2(25)), 10X3750 (12.2(20)))
To patch the problem, I was considering stopping the errdisable for the loopback cause or at least, making a low recovery interval for this cause...
Someone have any advices to give me??
Thanks,
Emmanuel Bouchard
Solved! Go to Solution.
08-15-2007 12:12 AM
Have a look at this link
Narayan
08-15-2007 12:03 AM
May require more info to identify what is the problem but for a start -
Hope you have not enabled spanning-tree portfast on any port where you are connecting another switch.
Which link going down is affecting the network? Is it the same link which goes down always which creates this situation?
From the logs can you find out which ports go down first?
any difference in the trunk configs of switch which goes down and and the switch which does not go down.
08-15-2007 12:12 AM
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