How To Implement Logging Services; Setting Up Destinations For System Logging Messages - Cisco ASR 9000 Serie Configuration Manuals

Implementing Logging Services
Command
logging trap

How to Implement Logging Services

Setting Up Destinations for System Logging Messages

This task explains how to configure logging to destinations other than the console terminal.
For conceptual information, see the
SUMMARY STEPS
1. configure
2. logging buffered [size | severity]
3. logging monitor [ severity]
4. commit
5. terminal monitor
DETAILED STEPS
Command or Action
Step 1 configure
Step 2 logging buffered [size | severity]
Example:
RP/0/RSP0/CPU0:router(config)#
logging buffered severity
warnings
Step 3 logging monitor [ severity]
Example:
RP/0/RSP0/CPU0:router(config)#
logging monitor critical
Syslog Message Destinations, on page 288
Purpose
Specifies the logging buffer as a destination for syslog messages, sets the size of the
logging buffer, and limits syslog messages sent to the logging buffer based on
severity.
• The default value for the size argument is 4096 bytes.
• The default value for the severity argument is debugging.
• Keyword options for the severity argument are emergencies, alerts, critical,
errors, warnings, notifications, informational, and debugging.
• By default, entering this command without specifying a severity level for the
severity argument or specifying the size of the buffer for the size argument
sets the severity level to debugging and the buffer size to 4096 bytes.
Specifies terminal lines other than console terminal as destinations for syslog
messages and limits the number of messages sent to terminal lines based on severity.
• Keyword options for the severity argument are emergencies, alerts, critical,
errors, warnings, notifications, informational, and debugging.
Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide, Release 4.2.x
Default Severity Keyword
informational
How to Implement Logging Services
Level
6
section.
295