Broadcast limiting vs an unmanaged switch with a loop

Question

I'm working with a 7150-24 port switch in a test environment.

I'm looking at how to address potential loops for connected un-managed switches - good or bad, I have to deal with this ugly reality.  While loop-detection DOES work, the affected port doesn't automatically reset once the loop is removed.  The port remains in a err-disable/shutdown state until the loop-detection is cleared on the switch.

From what I see, a loop on the un-managed switch creates a broadcast storm.  Setting a broadcast limit doesn't seem to have any effect on limiting traffic on a given port.

Or does Broadcast limits not apply to broadcast storms?

scott_farrand_f · Answer

Thank you!

I'll give that a test as that would solve the issue I had with using loop-detection.

I am confused about why broadcast limits didn't appear to be working the way I'd expected them to work.

BenBeck · Answer

Hey Scott,

There is an auto recovery mechanism you can enable. Please check the L2 guide. The general config would be something like this:

ICX(config)# errdisable recovery cause loop-detection

There is also a configurable timer for the feature:

ICX(config)# errdisable recovery interval