Spectrum "BAD LINK DETECTED" alarm clearing and reasserting even though the associated interface was down between asserted alarms.
search cancel

Spectrum "BAD LINK DETECTED" alarm clearing and reasserting even though the associated interface was down between asserted alarms.

book

Article ID: 45624

calendar_today

Updated On:

Products

CA Spectrum DX NetOps

Issue/Introduction

For interface models that have alarming enabled, the Spectrum "BAD LINK DETECTED" alarm is clearing and reasserting even though the associated interface was down between asserted alarms. 

Environment

Release: Any
Component: Spectrum Events and Alarms

Cause

While the "BAD LINK DETECTED" alarm with Probable Cause id 0x1040a exists, Spectrum lost snmp contact with the device. Then when Spectrum regained snmp contact with the device, Spectrum asserted the 0x10d2a event on the interface model. The 0x10d2a event is configured to clear the "BAD LINK DETECTED ALARM". The 0x10d2a event is NOT configured to be logged so it is not seen historically in the Events tab of the interface model.  The next time Spectrum polls the status of the interface, if it is still down, Spectrum asserts a new "BAD LINK DETECTED" alarm.

Resolution

This is functioning as designed.