How to clear mistakenly raised suppressed alarms

Document ID : KB000048310
Last Modified Date : 14/02/2018
Show Technical Document Details


In a scenario that you have customized event configuration that resulted in unexpected suppressed alarms on models, you want to clear the suppressed alarms. By default suppressed alarms are not shown nor accessible from the OneClick Console, neither you can use CLI to destroy the alarms. Just setting the Condition attribute (attribute id 0x1000a) value from Suppressed (5) to Normal (0) is not a solution because it is not clearing the internal suppressed alarm. This KB article shows how you can clear the suppressed alarms.


There are 2 options you can do to clear the unexpected suppressed alarms.

  1. Create a dummy event via Event Configuration tool to clear the suppressed alarms. And then use the following CLI command to raise the event against the affected models.

    ./create event type=<event type> text=dummy mh=<model handle>

    Note: <event type> is the event type of the created new event. <model handle> is the model handle of affected model.
    Please see below figure.
    You have to run the CLI command against all of the affected models.

  2. Restart SpectroSERVER.
    By default restarting SpectroSERVER will clear the unexpected user-created suppressed alarms.

If you know the alarm Cause Code and all the affected models you should choose option 1, otherwise option 2.

Figure 1