Clearing And Acknowledging Alarms; Clearing Alarms - Siemens RUGGEDCOM ROX II User Manual

RUGGEDCOM ROX II
CLI User Guide
show admin alarms
A table or list similar to the following example appears:
ruggedcom# show admin alarms | tab
ALARM
SUBSYSTEM ID
ACTUATORS
---------------------------------------------------------------------------------------------
switch 1
For information on how to clear or acknowledge an active alarm, refer to
Acknowledging Alarms".
Section 4.6.3

Clearing and Acknowledging Alarms

There are two types of alarms: conditional and non-conditional. Conditional alarms are generated when the
condition is true and cleared when the condition is resolved and the incident is acknowledged by the user.
Non-conditional alarms, however, are simply generated when the event occurs (a notification) and it is the
responsibility of the user to clear the alarm.
An example of a conditional alarm is a link down alarm. When the condition is resolved (i.e. the link comes up),
the LED and alarm relay are both disabled, if the auto-clear option is enabled.
Examples of non-conditional alarms are link up and internal configuration errors.
The following sections describe how to acknowledge and clear alarms:
• Section 4.6.3.1, "Clearing Alarms"
• Section 4.6.3.2, "Acknowledging Alarms"
Section 4.6.3.1

Clearing Alarms

Non-conditional alarms must be cleared by the user. Conditional alarms, when configured, are cleared
automatically.
To clear all clear-able, non-conditional alarms, type:
admin clear-all-alarms
Alternatively, to clear an individual non-conditional alarm, type:
admin alarms active-alarms type id event clear
Where:
• type is the type of alarm. Options include admincellmodemchassisethsecurityswitchwan.
• id is the ID for the chosen alarm
• event is the ID for the chosen event
Clearing and Acknowledging Alarms
EVENT
ID SEVERITY DESCRIPTION
1 notice Link-up on port lm1/8
DATE TIME
Wed Feb 6 16:08:44 2013
Section 4.6.3, "Clearing and
Chapter 4
System Administration
USER ACTIONS
clear-or-ack none
163