DFM/LMS email notifications for Err-disable port events

Unanswered Question
Jun 19th, 2008

I'd like alerts if/when any port goes err-disabled, has anyone done this before? Would this be a custom set up?

thanks!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Thu, 06/19/2008 - 11:12

I believe I looked into this for something else, and it cannot be done with DFM. DFM isn't looking at the necessary objects to determine if a port is err-disable.

However, if there is a syslog messages relating to a port going err-disable (and I believe there is one), then RME's Syslog Analyzer can trigger an email if you define an Automated Action to do so. The Automated Actions can be setup under RME > Tools > Syslog > Automated Actions.

yjdabear Thu, 06/19/2008 - 11:17

DFM is more of an SNMP trap receiver, whereas RME is more apt at dealing with syslogs, which is the protocol Cisco OSes usually use to send err-disabled notifications.

To begin with, you need to compile a list of causes interfaces/ports can be err-disabled for. Assuming your routers/switches are adequately configured to spit out the relevant syslogs, RME's Syslog Automated Actions can be set up to email notifications upon reception of such syslogs. Here're some commonly seen err-disabled syslogs to key on:

UDLD-SP-4-UDLD_PORT_DISABLED

PM-SP-4-ERR_DISABLE

SPANTREE-2-RX_PORTFAST:Received BPDU on PortFast enable port. Disabling [mod/port].

SPANTREE-2-RX_BPDUGUARD: Received BPDU on bpdu guard enabled port. Disabling [mod/port].

js88888888 Fri, 06/20/2008 - 07:43

Thank you very much for both replies. Is there a generic "this port is err-disabled for any reason" syslog msg I can use?

Joe Clarke Fri, 06/20/2008 - 08:11

The PM-4-ERR_DISABLE message seems to be a good one for a wide variety of switches. Of course, AA doesn't require you just pick one message. You can lump a whole bunch into the same Automated Action.

yjdabear Fri, 06/20/2008 - 09:52

One'd hope so, but unfortunately given the multitude of possible triggers and how each OS is coded to phrase the syslog differently, it almost always takes getting "bitten" at least once first, before learning there's another reason ports get err-disabled. This translates into perpetually updating the Automated Actions to catch up.

Actions

This Discussion