logging history
To change the severity level of system logging (syslog) messages sent to the history table on the router and
a Simple Network Management Protocol (SNMP) network management station (NMS), use the
logging
history
command in global configuration mode. To remove the
logging history
command from the
configuration and return the logging of messages to the default level, use the
no
form of this command.
logging history severity
no logging history
Syntax Description
Severity level of messages sent to the history table on the router and an SNMP NMS, including
events of a higher severity level (numerically lower). Settings for the severity levels and their
respective system conditions are listed in
Table 29: Severity Levels for Messages, on page
312
under the
“
Usage Guidelines
”
section for the
logging buffered
command.
severity
Command Default
severity
:
warnings
Command Modes
Global configuration
Command History
Modification
Release
This command was introduced.
Release 3.2
Usage Guidelines
Logging of messages to an SNMP NMS is enabled by the
snmp-server enable traps
command. Because
SNMP traps are inherently unreliable and much too important to lose, at least one syslog message, the most
recent message, is stored in a history table on the router.
Use the
logging history
command to reflect the history of last 500 syslog messages. For example, when this
command is issued, the last 500 syslog messages with severity less than warning message are displayed in
the output of
show logging history
command.
Use the
show logging history, on page 348
command to display the history table, which contains table size,
message status, and message text data.
Use the
logging history size, on page 327
command to change the number of messages stored in the history
table.
The value specified for the
severity
argument causes messages at that severity level and at numerically lower
levels to be stored in the history table of the router and sent to the SNMP NMS. Severity levels are
numbered 0 to 7, with 1 being the most important message and 7 being the least important message (that is,
the lower the number, the more critical the message). For example, specifying the level critical with the
critical
keyword causes messages at the severity level of
critical
(2),
alerts
(1), and
emergencies
(0) to be stored in
the history table and sent to the SNMP NMS.
Cisco IOS XR System Monitoring Command Reference for the Cisco XR 12000 Series Router, Release 4.1
OL-24735-01
325
Logging Services Commands
logging history
