Foundry NetIron M2404C and M2404F Metro Access Switches
Configuring System Message Logging (Rev. 03)
System Message Logging
© 2008 Foundry Networks, Inc.
Page 3 of 22
The first two fields in
Table 1
are always included in the system message. The
PRIORITY
field, the
sequence number and date and time are optional. By default these fields are not included in any
message. To force inclusion of the
PRIORITY
field and sequence number in trap-messages, use the
log include priority
command and
log include sequence-number
in Global Configuration mode.
The
log timestamp datetime localtime timezone msecs
command displays the date and time.
Understanding How System Message Logging Works
The system message logging software can save messages in a log file or direct those messages to
other devices. The system message logging facility has the following features:
•
It provides the user with logging information for monitoring and troubleshooting.
•
It allows the user to select the types of logging information to be captured.
•
It allows the user to select the destination of captured logging information.
The minimum severity level is used to specify which system messages should be saved (see
Table
2
). the user can configure the system to store messages according to the Error level (severity level
3) up. By default, only Emergency-level messages are stored in the NVRAM. Log messages with
severity levels between 4 (warning) and 7 (debugging) are filtered out and are not stored in the
NVRAM. Messages are time-stamped to enhance real-time debugging and management.
Trap level for logging should be configured per device - NVRAM history, buffer, CLI console,
VTY terminal, Telnet console and per facility.
Table 2: Log Message Severity Levels
Severity Level Keyword
Description
0
emergency
Internal error occurred. The device reached a crash state and
cannot continue to operate.
1
alert
Internal error occurred. The device might operate incorrectly.
2
critical
Internal error or non-supported event occurred.
3
error
Error on a setting done by user.
4
warning
Warning on a setting done by user.
5
notification
Notify on configuration setting.
6
information
Inform on state changes.
7
debugging
Debug message to be used by Technical Support.
The user can monitor system messages remotely by accessing the device through Telnet or the
console port, or by viewing the logs on a Syslog server.
Memory buffer logging is an alternative to console logging. However, both are not mutually
exclusive and can be configured independently. Memory buffer logging can be enabled or disabled.
The user can resize the buffer size, which is measured in number of messages. The buffer is
circular – when full, the newest message displaces the oldest one. Logging to an internal buffer is
the method with the least overhead. The buffer can be uploaded to an FTP server with a desired file
name.
Privilege-limited logging can be used to allow only the administrator group to view messages with
priorities numerically higher than the configured trap levels.
The user can set the type of debug messages the user wants to display by using one of the debug
commands in Privileged (Enable) mode.