Spectrum Alarm with Global Alarm IDs in the message may seem cryptic.

Products

• CA Spectrum

Issue/Introduction

 

Introduction: 

Alarms with Global Alarm IDs may seem cryptic.

Question: 

I have received an alarm that has a lot of HEX in the message. What does this mean?

Example: Alarm 56f7d7d4-f37d-1040-0348-b82a72de479c is no longer being caused by alarm 56f7d7d4-f36b-1040-0348-b82a72de479c. Alarm 56f7d7d4-f37d-1040-0348-b82a72de479c (major, probable cause id 0x56e1000) is now being hidden because it is caused by alarm 56f7d7d4-f36b-1040-0348-b82a72de479c (major, probable cause id 0x56e10ba on model 0x7040cf).

Environment:  

Platform Independent

Answer: 

The HEX that is displayed in the alarm are the Global Alarm IDs for those alarms mentioned. This HEX is normal, as the Global Alarm ID contains HEX for the Landscape handle of the Landscape, and other details in HEX.

When these alarms are viewed, it can help to pick out key information that can be used to search for more information on the event that occurred.

For instance, in the example above, the message contains handles for both Probable Cause IDs for the event and a model handle of the device affected:

Alarm 56f7d7d4-f37d-1040-0348-b82a72de479c (major, probable cause id 0x56e1000) is now being hidden because it is caused by alarm 56f7d7d4-f36b-1040-0348-b82a72de479c (major, probable cause id 0x56e10ba on model 0x7040cf).

The model handle (0x7040cf ) can be searched in the Locator tab of OneClick for more details on alarms on that model.

In this case, the example is a Condition Correlation alarm. So for this alarm, the Probable Cause ID can be searched in Condition Correlation Editor for more specific details on this event. Be sure to remove the “0x” prefix first before performing the search (i.e. 56e1000)

Additional Information:

N/A

 

 

Environment

Release: SPDBIP99000-9.4-Spectrum-Device Based Suite-IP Services Manager
Component: