Alarm Logging Correlation; Configuring Basic Message Logging - Cisco CRS-1 - Carrier Routing System Router Getting Started Manual

Configuring Logging and Logging Correlation
You can log messages based on the severity level of the messages, as shown in
Table 5-4
Level
Level 0—Emergencies
Level 1—Alerts
Level 2—Critical
Level 3—Errors
Level 4—Warnings
Level 5—Notifications
Level 6—Informational
Level 7—Debugging

Alarm Logging Correlation

Alarm logging correlation is used to group and filter similar messages to reduce the amount of redundant
logs and isolate the root causes of the messages.
For example, the original message describing a card online insertion and removal (OIR) and system state
being up or down can be reported, and all subsequent messages reiterating the same event can be
correlated. When you create correlation rules, a common root event that is generating larger volumes of
follow-on error messages can be isolated and sent to the correlation buffer. An operator can pull up all
correlated messages for display later, should the need arise. Refer to "Implementing and Monitoring Alarms
and Alarm Log Correlation on Cisco IOS XR Software" in the Cisco IOS XR System Management
Configuration Guide for more information.

Configuring Basic Message Logging

Numerous options for logging system messages in Cisco IOS XR software are available. This section
provides a basic example.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
Cisco CRS-1 Series Carrier Routing System Getting Started Guide
5-12
Logging Severity Levels for System Error Messages
configure
logging {ip-address | hostname}
logging trap severity
logging console [severity]
logging buffered [severity | buffer-size]
commit
end
show logging
Chapter 5 Initial Configuration of the Cisco IOS XR Software
Description
System has become unusable.
Immediate action needed to restore system stability.
Critical conditions that may require attention.
Error conditions that may help track problems.
Warning conditions that are not severe.
Normal but significant conditions that bear notification.
Informational messages that do not require action.
Debugging messages for system troubleshooting only.
Table 5-4.