Installation Guide

history of hardware alarms. To change the levels of alarms sent to the alarm logs, refer to Configuring Alarm History Buffer Size on page
224.
The alarms are specific to hardware status, whereas the syslog records information for software events. Alarms can also be configured
on very specific terms such as a failed temperature sensor on a single interface module.
To take advantage of this feature, you should first set the alarm history buffer 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 Configuring Alarm History Buffer Size
on page 224 for more information.
Next, you should configure the severity of alarms for each device you want logged. For detailed information, refer to Configuring alarm
logging on page 224. Once you have configured 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 225.
Configuring Alarm History Buffer Size
The history buffer size is configurable. The default buffer size is 400 entries, but it can be configured to list between 100 and 3000
entries using the alarm history command.
For example, to configure 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 buffer size, use the alarm history command with the no operand. For example, to set the
buffer size back to the default entry size from 100, enter the following command:
device# no alarm history 100
Configuring alarm logging
You can configure the system to log only specific level alarms for specific devices using the alarm command. The configuration setting
applies to both logs, the current and history alarm logs. The level you set is the minimum level of alarms that will be logged. For example,
if you set the configuration to log a minimum of minor level events, all minor, major and critical events will be logged. If you set the
configuration to log a minimum of major level events, all major and critical events will be logged. If you set the configuration to log a
minimum of critical level events, only critical level events will be logged.
For example, to configure the system to log a minimum of major level alarms on an interface module in slot 1, optic in slot 9, enter the
following command:
device# alarm lp 1 optic 9 major
Alarms of major and critical severity will be logged for the optic in slot 9 on interface module in slot 1.
To reset the alarm history severity logging back to the default severity level, use the alarm command with the no operand. For example,
to reset the alarms for the example above back to default, enter the following command:
device# no alarm lp 1 optic 9 major
NOTE
You cannot configure alarm severity on a system wide basis; you must specify a specific device, such as a fan, power supply or
optic device. Once an alarm is set to log a minimum alarm level, the show commands cannot display alarm levels of lower
severity levels as the information is not logged.
Managing Routers and Modules
Brocade NetIron MLXe Series Hardware Installation Guide
224 53-1004203-03