Alarm suppression in Spectrum - All Devices in a Location are Down and are Suppressed Without Having An Alarm Created

book

Article ID: 185984

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction


When Spectrum loses connectivity to a group of connected devices it is unable to determine the root cause
   of the network outage. In this case, the status of all devices affected by the outage is set to gray, and a red
   Unresolved Fault alarm is generated. (Typically the inability to determine the cause is due to network devices
   between the SpectroSERVER and target group of devices not existing in the landscape. This is usually due to
   the traffic passes through an ISP, a Client's network for which access is not available).

 


In cases like this, an Unresolved Fault alarm is either generated on the 'Fault Isolation' application model
  or on a device within the fault domain (A fault domain is a group of connected devices). In this specific case
  the Unresolved Fault event was generated but an alarm was not produced.






   

Cause


The 0x10d05 event responsible for generating the Critical Unresolved Fault alarm had been customized to not
  alarm. This resulted in the group of devices all being suppressed without an alarm to signify the outage.

From the $SPECROOT/custom/Events/EventDisp file

Environment

Release : 10.x

Component : 

Resolution


Restore the Unresolved Fault event to again alarm by removing the entry from the $SPECROOT/custom/Events/EventDisp file.

The default out of the box definition is located in
  $SPECROOT/SS/CsVendor/Cabletron/EventDisp
 


Additional Information


The following document page lists the events that should not be modified due to fault isolation

Event and Alarm Customization
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/spectrum/10-4/managing-network/event-configuration/event-and-alarm-customization.html


Attachments