starlingx/docs
Code Issues Proposed changes
Files
b60579b00161ce06b6615e6d31ac347cf859d4e1
docs/doc/source/fault-mgmt/unsuppressing-an-alarm-using-the-cli.rst
MCamp859 ebdf63ec68 Fix clerical errors in 2 guides 
Node Management index: change BCM to BMC
Fault Management guide: remove “ing” from title of 2 topics

Change-Id: I33b4c29e2ca92e842f585f4bb641780b52769206
Signed-off-by: MCamp859 <maryx.camp@intel.com>
2021-01-14 15:25:03 -05:00

1.0 KiB
Raw Blame History

Unsuppress an Alarm Using the CLI

If you need to reactivate a suppressed alarm, you can do so using the CLI.

  • Use the fm event-unsuppress CLI command to unsuppress a currently suppressed alarm.

    ~(keystone_admin)$ fm event-unsuppress [--nowrap] --alarm_id <alarm-id>[,<alarm-id>] \
[--nopaging] [--uuid]

    where

    <alarm-id>

    is a comma separated Alarm ID list of alarms to unsuppress.

    --nowrap

    disables output wrapping.

    --nopaging

    disables paged output

    --uuid

    includes the alarm type UUIDs in the output.

    Alarm type(s) with the specified <alarm-id(s)> will be unsuppressed.

    You can unsuppress all currently suppressed alarms using the following command:

    ~(keystone_admin)$ fm event-unsuppress -all [--nopaging] [--uuid]