Removing unwanted alarms from CA Spectrum OneClick

Products

• Spectrum
• Network Observability

Issue/Introduction

In a scenario, for example, where you have created a custom event code and set in the events alarm options "Generate a Unique Alarm for Each Event " you may see over time a number of alarms being generated that are not required if there is no clear event created to also remove these alarms.

When setting the "Generate a Unique Alarm for Each Event" option instead of just seeing the occurrence count increase on the first alarm raised you will have a new separate alarm raised in OneClick every time the event that generates this alarm is created.

Environment

Spectrum: All Spectrum Releases

Resolution

To remove the unwanted, accumulated alarms you can add a temporary clear event via Event Configuration to clear the alarms.

Note: you can also do this if you already have one defined but want to mark this as special clearing, using a temporary event code to do it.

The following expands upon the steps given in Broadcom TechDocs : CA Spectrum - About Configuring Events

1. Select the event in the Navigation panel, and then click the Alarms tab in the Details panel.
   
   
2. Under Cleared Alarm(s), click (Adds an alarm to the list).
   
   The Add Cleared Alarm dialog opens displaying the alarm cause codes for all alarms currently loaded into Event Configuration.
   
   
3. Click Browse, and in the Select Alarm Cause Code dialog, select the alarm cause code of the alarm to clear.
   
   To help you identify the desired alarm, you can enter a text string in the Filter text box to filter the list to include only the alarms with displayedproperties that contain the text string.
   
   
4. Click OK.
   
   
5. If the alarm you want to clear was generated based on event variable discriminators, select Clear Options, and then specify how the alarm should be cleared. You can select one of the following options:
   
   All Alarms
   Select this option if the event should clear all existing instances of the alarm regardless of whether the values in the alarm-clearing event match the values stored in the alarm instances.
   
   Event Variable Discriminators
   Select this option if the event should clear existing instances of the alarm based on the values of the alarm's variables (which are copied from the alarm-generating event to the alarm when the alarm is generated). Then enter a comma-separated list of event variable IDs (for example: 1,3,5). You must enter each ID; ranges of IDs are not supported.
   
   The alarm is cleared by the alarm-clearing event if the values in event match the values stored in the alarm.
   For examples of using event discriminators to clear alarms, see Clearing Alarms.
   
   
6. Click OK.
   
   
7. (Optional) Repeat the preceding steps to add additional alarms to be cleared.
   
   
8. Once you have created the clear event next you just need to send that clearing event to every model which has had this alarm generated on it via CLI (you need to have the model handle):
   
   cd $SPECROOT/vnmsh
   
   ./connect.exe
   
   ./create event type=< clearing event code > text= mh=< model handle of alarmed device/model >
   
   
9. This will then clear every instance of that alarm on the model. Of course they will start fresh but ongoing it should not be getting new alarms generated anyway.
   
   
10. Ongoing the original event generating the event can be modified to uncheck "Generate a Unique Alarm for Each Event" so that unwanted alarms are not created.