e60b972a04
This update brings FM in line with directory and index structure of other content. Signed-off-by: Stone <ronald.stone@windriver.com> Change-Id: If730098dc3eb119defa89647b04ac9f7c8717992
36 lines
989 B
ReStructuredText
36 lines
989 B
ReStructuredText
|
|
.. cpy1552680695138
|
|
.. _deleting-an-alarm-using-the-cli:
|
|
|
|
=============================
|
|
Delete an Alarm Using the CLI
|
|
=============================
|
|
|
|
You can manually delete an alarm that is not automatically cleared by the
|
|
system.
|
|
|
|
.. rubric:: |context|
|
|
|
|
.. 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 :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.
|
|
|
|
.. rubric:: |proc|
|
|
|
|
.. _deleting-an-alarm-using-the-cli-steps-clp-fzw-nkb:
|
|
|
|
- To delete an alarm, use the :command:`fm alarm-delete` command.
|
|
|
|
For example:
|
|
|
|
.. code-block:: none
|
|
|
|
~(keystone_admin)$ fm alarm-delete 4ab5698a-19cb-4c17-bd63-302173fef62c
|
|
|
|
Substitute the UUID of the alarm you wish to delete. |