Stone 037c99f0b7 Fault Management doc

Added Data Networks toctree

Changed case on doc title in top level index - changed doc directory to
fault-mgmt.

Added Distributed Cloud section.

Broke out "OpenStack Fault Management Overview" statement about remote log
collection to conditionally included file.

Incorporated patch 6 review comments. Also implemented rST :abbr:
for first instance of SNMP in each file.

Changed port number and community string in two SNMP walk examples.

Change-Id: I1afd71265e752c4c9a54bf2dc9a173b3e17332a7
Signed-off-by: Stone <ronald.stone@windriver.com>

2020-11-27 14:13:00 -05:00

1.0 KiB

Raw Blame History

Unsuppressing 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]
```

1.0 KiB Raw Blame History

Unsuppressing an Alarm Using the CLI

1.0 KiB

Raw Blame History