Disabling Global Custom alarms for services

You cannot disable a global alarm for a service unless you create another enabled global alarm for the attribute. This is because if all alarms within a class for an attribute are disabled, the NMS service interprets the class as having no alarms configured for the attribute and evaluates the next lower class for the enabled alarm.

Before you begin

About this task

Instead of creating a Global Custom alarm and disabling it for selected services, reconfigure the alarms such that you create individual local Custom alarms for the services that require the alarm. If you want to ensure that all these Custom alarms have the same configuration, you can create a Global Custom alarm, disable it, and then enable it for selected services as a Custom alarm.
If you want to create a Global Custom alarm and disable it for selected services, you must create a local Custom alarm for that service that will never be triggered. Doing this overrides all Global Custom alarms for that service.
Note: Alarms cannot be disabled for individual rows in a table.

Steps

  1. Create a local Custom alarm for a service that will never be triggered.
  2. Select Grid.
  3. Select the service or component in the Grid Topology tree.
  4. Click Configuration > Alarms .
  5. In the Global Custom alarm table, click Copy Copy icon next to the alarm you want to disable.
    The alarm is copied to the Custom Alarms table.
  6. Clear Enabled for the alarm.
  7. Click Apply Changes.