proactive notification for STP loops

[axfalk]

We're in a switched environment, with a couple of Cat-6506's in the core and Cat-2980's on the access layer. We're also running CW2K for monitoring and proactive notification. So far, it has worked OK, except yesterday, we had an STP loop and did not find out about it until it was too late. Does anybody happen to know if there's any way to configure the CW2K for proactively notifying about the STP loops?

Thanks

[rickellis]

I'd be interested in a reply to this as well.

On occasion we get killed by bridge loops and are now in the process of implementing storm control. I'm curious as to what type of notifications you are currently receving via Ciscoworks (DFM traps? or syslog?). Also are you using storm control?

cheers,

Rick

[steve.busby]

This sounds like a perfect place to use the RME Syslog automated actions. It will take a bit of tweaking on your part, but if you follow the instructions included in the link below, I believe it'll work for you.

http://cisco.com/en/US/partner/products/sw/cscowork/ps2073/products_tech_note09186a00800a7275.shtml

HTH

Steve

[hgru]

Couple of remarks

- I think that if a loop occurs that within miliseconds you have a broadcast storm. Any message will come too late I guess. By the time you will recieve it you already have a servere problem.

- STP should prevent a loop if it doesn't it is because it is not aware of a loop problem so it cannot warn you bout it either.

- Maybe a external probe or sniffer can detect al loop by seeing the same packet passing by multiple times in a short time frame. Maybe it can send you snmp trap via a seprate interface on a different network.

- Is it maybe an idea to assume a loop if the utilisation of a processor of a switch is very high and or if the forwarding rate is very high.

- Anyway if it is possibile to detect a loop make a defautl action to shut down an interface.

Kind regards,

Hans