Link down traps for Cisco models not asserting proper event in Spectrum

Document ID : KB000046625
Last Modified Date : 05/12/2018
Show Technical Document Details
Issue:

We have modified the standard link down trap configuration to assert a custom event and alarm. This works except for the Cisco models. The Cisco models still assert the default out of the box events and alarms.

Out of the box, the standard mib-2 link down trap is defined in the $SPECROOT/SS/CsVendor/IETF/AlertMap as follows:

2.0                   0x00220001        1.3.6.1.2.1.2.2.1.1(1,2)\

As you can see above, the out of the box event is 0x00220001.

We have modified the AlertMap file to assert a custom event like the following example::

2.0                   0xfff00001            1.3.6.1.2.1.2.2.1.1(1,2)\

When the link down trap is received for a non-Cisco model, the 0xfff00001 event is asserted. However, when the link down trap is received for a Cisco model, the 0x00220001 event is still asserted.

Cause:

This was done by design. The link down trap for Cisco devices is intercepted by internal code and still asserts the default 0x00220001 event no matter the configuration of the link down trap in the AlertMap file.

Resolution:

None as this was done by design.

Additional Information:

If there is additional processing the user wishes to perform when a link down trap is received, like an event rule of some kind, configure the rule on the default 0x00220001 event.