Syslog message -

[getwithrob]

On Catalyst 6000-6500s running CatOS, when a port goes to an error disabled state, this message is logged –

************************************************************************

Error Message %MGMT-5-PORT_ERRDISABLE: Port [dec]/[dec] is errdisabled because of Broadcast Suppression

Explanation This message indicates that a port is errdisabled because of broadcast suppression. [dec]/[dec] is the module number/port number.

Recommended Action No action is necessary. This message is provided for information only.

************************************************************************

On Catalyst 4000/4500s or 5000/5500s devices running CatOS, I don’t see this as a valid message and can’t seem to find a message that would indicate a port has gone to the errdisabled state. The funny thing is the 4000/4500s and 5000/5500s do have a message that the error disabled port is being re-enabled. I don’t get it….

************************************************************************

MGMT-5-ERRDISPORTENABLED: Port [dec]/[dec] err-disabled by

[chars] enabled by errdisable timeout

Explanation This message indicates that an error disabled port is being reenabled. [dec]/[dec] is the module number and port number and [chars] is the error message. Action No action is necessary. This message is provided for information only.

************************************************************************

What I’m trying to do is setup an automated action to email when a port goes to this state. Before I can set it up, I need to know the message.

Any ideas???

[spremkumar]

Hi

AFAIK you can generate a SNMP trap from your cisco box which can be sent to your NMS which in turn can send u an email stating the status of the port..

regds

[getwithrob]

Would this fall under snmp module traps? I see there are also snmp chassis traps....

I will need to ensure this is enabled on all set based Catalyst. I haven't even looked into the Cats running IOS but imagine it's very similar.

I will also need to ensure NerveCenter can interpret this trap before it is forwarded up to Netcool.

[getwithrob]

Another question ?

NerveCenter is the SNMP management platform used here. How can I get a list of what traps can be interpreted by NerveCenter? For example, what module and chassis snmp traps can be sent from the Catalyst switches and can NerveCenter interpret them? IE. Astro Errors on a module, module CRC errors and many more?

[getwithrob]

Is this maybe how it works? All syslog messages sent via snmp are sent on or with a specific OID. Somewhere in the trap is the text of the message?

Am I even close?

Here's an Astro error message from a device that is configured with 'set snmp trap enable syslog'

This message was received on the mgmt station but not processed because it's probably not configured correctly.

Time=11/17/2005 03:54:57 Thu; LogId=292046158; NodeName=kp_scie_lcarvsc131.rvsd.ca.kp.org; NodePropertyGroup=KP-CSCO-CSW-SET; NodeAddressList=10.200.62.131; ReadCommunity=VER143r; WriteCommunity=none; TrapPduAgentAddress=10.200.62.131; TrapPduCommunity=VER143r; TrapPduTime=-1900061712; TrapPduEnterprise=1.3.6.1.4.1.9.9.41.2; TrapOid=; TrapPduGenericNumber=6; TrapPduSpecificNumber=1; TriggerInstance=; TriggerBaseObject=; 1.3.6.1.4.1.9.9.41.1.2.3.1.2.0=SYS; 1.3.6.1.4.1.9.9.41.1.2.3.1.3.0=5; 1.3.6.1.4.1.9.9.41.1.2.3.1.4.0=SYS; 1.3.6.1.4.1.9.9.41.1.2.3.1.5.0=2005 Nov 17 00:52:32 PST -08:00 %SYS-4-P2_WARN: 1/Astro(2/5) - timeout occurred; 1.3.6.1.4.1.9.9.41.1.2.3.1.6.0=-1900061712

[getwithrob]

I left off the part that this is the CISCO-SYSLOG-MIB........

[yjdabear]

Yes, IIRC, all the syslogs sent as SNMP traps have the same OID. Most NNM products by default pre-process SNMP traps based on the unique OIDs . With the syslogs masqueraded as traps, now you gotta configure pre-process by message string, if the NNM product lets you. Why bother then, unless one can't run a syslog server and have something sift through the original syslogs?