starlingx/docs
Code Issues Proposed changes
docs/doc/source/fault-mgmt/deleting-an-alarm-using-the-cli.rst
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

989 B
Raw Blame History

Delete an Alarm Using the CLI

You can manually delete an alarm that is not automatically cleared by the system.

Warning

Manually deleting an alarm should not be done unless it is absolutely clear that there is no reason for the alarm to be active.

You can use the command fm alarm-delete to manually delete an alarm that remains active/set for no apparent reason, which may happen in rare conditions. Alarms usually clear automatically when the related trigger or fault condition is corrected.

  • To delete an alarm, use the fm alarm-delete command.

    For example:

    ~(keystone_admin)$ fm alarm-delete 4ab5698a-19cb-4c17-bd63-302173fef62c

    Substitute the UUID of the alarm you wish to delete.