Installation Guide

History
Release version Command history
R05.7.00b This command was introduced.
Using alarms to collect and monitor device status
Beginning in the Extreme NetIron software R05.3.00, the software keeps two logs; one of hardware status currently available to the
system, and another of hardware status history. The current alarm log keeps only entries for current information; when a hardware status
is no longer valid, the entry is cleared. The alarm history log keeps a record of hardware statuses even after the status has changed. The
alarm history log enables you to quickly determine trouble areas in a system. For example, by accessing the history, you can quickly
determine if a problem is occurring too frequently and might require action.
Each hardware status entry is called an alarm and is classied by severity assigned by the software. The software categorizes alarms in
the following levels:
• Critical - A condition that will cause damage to the system. A condition that causes a trac outage on multiple ports.
• Major - A condition that causes trac outage on single ports or might cause damage to the system.
• Minor - A condition that should be investigated but will not damage the system.
By default, all hardware status alarm levels of major severity and higher are logged, though you can
congure the status alarm levels sent
to both alarm logs (current and history). You can use the show alarm command to view the current status on a device, or a logged history
of hardware alarms. To change the levels of alarms sent to the alarm logs, refer to Conguring Alarm History Buer Size on page 228.
The alarms are specic to hardware status, whereas the syslog records information for software events. Alarms can also be congured on
very specic terms such as a failed temperature sensor on a single interface module.
To take advantage of this feature, you should rst set the alarm history buer size. This is optional, but you have the option to limit how
many entries are stored in the alarm history so you can free up space for other resources. Refer to Conguring Alarm History Buer Size
on page 228 for more information.
Next, you should congure the severity of alarms for each device you want logged. For detailed information, refer to Conguring alarm
logging on page 229. Once you have congured your alarm logging, you can display alarms in the current alarm log and alarm history
log using the show alarm command, as described in Displaying alarms on page 229.
Conguring Alarm History Buer Size
The history buer size is congurable. The default buer size is 400 entries, but it can be congured to list between 100 and 3000
entries using the alarm history command.
For example, to congure the alarm history log size to 100 entries, enter the following command:
device# alarm history 100
Syntax: [no] alarm history n
where n is the number of log entries you want to store in the alarm history log, between 100 and 3000.
To reset the alarm history back to the default buer size, use the alarm history command with the no operand. For example, to set the
buer size back to the default entry size from 100, enter the following command:
device# no alarm history 100
Using alarms to collect and monitor device status
Extreme Routing MLX Series Hardware Installation Guide
228 53-1004203-04