Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide
Implementing Logging Services on the Cisco ASR 9000 Series Router
Downloads: This chapterpdf (PDF - 614.0KB) The complete bookPDF (PDF - 5.36MB) | Feedback

Implementing Logging Services on Cisco ASR 9000 Series Router

Table Of Contents

Implementing Logging Services on Cisco ASR 9000 Series Router

Contents

Prerequisites for Implementing Logging Servicese

Information About Implementing Logging Services

System Logging Process

Format of System Logging Messages

Syslog Message Destinations

Guidelines for Sending Syslog Messages to Destinations Other Than the Console

Logging for the Current Terminal Session

Syslog Messages Sent to Syslog Servers

UNIX System Logging Facilities

Hostname Prefix Logging

Syslog Source Address Logging

UNIX Syslog Daemon Configuration

Archiving Logging Messages on a Local Storage Device

Setting Archive Attributes

Archive Storage Directories

Severity Levels

Logging History Table

Syslog Message Severity Level Definitions

Syslog Severity Level Command Defaults

How to Implement Logging Services

Setting Up Destinations for SystemLogging Messages

Configuring Logging to a Remote Server

Prerequisites

Configuring the Settings for the Logging History Table

Prerequisites

Modifying Logging to the Console Terminal and the Logging Buffer

Modifying the Format of Time Stamps

Disabling Time Stamps

Suppressing Duplicate Syslog Messages

Disabling the Logging of Link-Status Syslog Messages

Displaying System Logging Messages

Examples

Archiving System Logging Messages to a Local Storage Device

Restrictions

Examples

Configuration Examples for Implementing Logging Services

Configuring Logging to the Console Terminal and the Logging Buffer: Example

Setting Up Destinations for Syslog Messages: Example

Configuring the Settings for the Logging History Table: Example

Modifying Time Stamps: Example

Configuring a Logging Archive: Example

Where to Go Next

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance


Implementing Logging Services on Cisco ASR 9000 Series Router


This module describes the new and revised tasks you need to implement logging services on the Cisco ASR 9000 Series Aggregation Services Routers.

The Cisco IOS XR software provides basic logging services. Logging services provide a means to gather logging information for monitoring and troubleshooting, to select the type of logging information captured, and to specify the destinations of captured system logging (syslog) messages.


Note For more information about logging services on the Cisco IOS XR software and complete descriptions of the logging commands listed in this module, see the "Related Documents" section of this module.


Feature History for Implementing Logging Services on Cisco ASR 9000 Series Router

Release
Modification

Release 3.7.2

This feature was introduced on the Cisco ASR 9000 Series Router.

Release 3.9.0

No modification.


Contents

Prerequisites for Implementing Logging Servicese

How to Implement Logging Services

Configuration Examples for Implementing Logging Services

Where to Go Next

Additional References

Prerequisites for Implementing Logging Servicese

The following prerequisites are required to implement logging services in your network operating center (NOC):

You must be in a user group associated with a task group that includes the proper task IDs. The command reference guides include the task IDs required for each command. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

You must have connectivity with syslog servers to configure syslog server hosts as the recipients for syslog messages.

Information About Implementing Logging Services

To implement logging services, you need to understand the following concepts:

System Logging Process

Format of System Logging Messages

Syslog Message Destinations

Syslog Messages Sent to Syslog Servers

UNIX Syslog Daemon Configuration

Archiving Logging Messages on a Local Storage Device

Severity Levels

System Logging Process

By default, routers are configured to send syslog messages to a syslog process. The syslog process controls the distribution of messages to the destination of syslog messages such as the logging buffer, terminal lines, or a syslog server. The syslog process also sends messages to the console terminal by default.

Format of System Logging Messages

By default, the general format of syslog messages generated by the syslog process on the Cisco IOS XR software is as follows:

node-id:timestamp : process-name [pid] : %message-group-severity-message-code : message-text

The following is a sample syslog message:

RP/0/RSP0/CPU0:Nov 28 23:56:53.826 : config[65710]: %SYS-5-CONFIG_I : Configured from 
console by console
 
   

Table 1 describes the general format of syslog messages on Cisco IOS XR software.

Table 1 General Syslog Message Format 

Field
Description

node-id

Node from which the syslog message originated.

timestamp

Time stamp in the form month day HH:MM:SS, indicating when the message was generated.

Note The time-stamp format can be modified using the service timestamps command. See the "Modifying the Format of Time Stamps" section.

process-name

Process that generated the syslog message.

[pid]

Process ID (pid) of the process that generated the syslog message.

%message-group-severity-message-code

Message group name, severity, and message code associated with the syslog message.

message-text

Text string describing the syslog message.


Syslog Message Destinations

Syslog message logging to the console terminal is enabled by default. To disable logging to the console terminal, use the no logging console command in global configuration mode. To reenable logging to the console terminal, use the logging console command in global configuration mode.

Syslog messages can be sent to destinations other than the console, such as the logging buffer, syslog servers, and terminal lines other than the console (such as vtys). Table 2 lists the commands used to specify syslog destinations.

Table 2 Commands Used to Set Syslog Destinations

Command
Description

logging buffered

Specifies the logging buffer as a destination for syslog messages.

logging {hostname | ip-address}

Specifies a syslog server host as a destination for syslog messages.

logging monitor

Specifies terminal lines other than the console as destinations for syslog messages.


The logging buffered command copies logging messages to the logging buffer. The buffer is circular, so newer messages overwrite older messages after the buffer is full. To display the syslog messages that are logged in the logging buffer, use the show logging command. The first message displayed is the oldest message in the buffer. To clear the current contents of the logging buffer, use the clear logging command. To disable logging to the logging buffer, use the no logging buffered command in global configuration mode.

The logging command identifies a syslog server host to receive logging messages. By issuing this command more than once, you build a list of syslog servers that receive logging messages. To delete the syslog server with the specified IP address or hostname from the list of available syslog servers, use the no logging command in global configuration mode.

The logging monitor command globally enables the logging of syslog messages to terminal lines other than the console, such as vtys. To disable logging to terminal lines other than the console, use the no logging monitor command in global configuration mode.

Guidelines for Sending Syslog Messages to Destinations Other Than the Console

The logging process sends syslog messages to destinations other than the console terminal and the process is enabled by default. Logging is enabled to the logging buffer, terminal lines and syslog servers.

Logging for the Current Terminal Session

The logging monitor command globally enable the logging of syslog messages to terminal lines other than console terminal. Once the logging monitor command is enabled, use the terminal monitor command to display syslog messages during a terminal session.

To disable the logging of syslog messages to a terminal during a terminal session, use the terminal monitor disable command in EXEC mode.The terminal monitor disable command disables logging for only the current terminal session.

To reenable the logging of syslog messages for the current terminal session, use the terminal monitor command in EXEC mode.


Note The terminal monitor and terminal monitor disable commands are set locally and will not remain in effect after the terminal session is ended.


Syslog Messages Sent to Syslog Servers

The Cisco IOS XR software provides the following features to help manage syslog messages sent to syslog servers:

UNIX system facilities

Hostname prefix logging

Source interface logging

UNIX System Logging Facilities

You can configure the syslog facility in which syslog messages are sent by using the logging facility command. Consult the operator manual for your UNIX operating system for more information about these UNIX system facilities. The syslog format is compatible with Berkeley Standard Distribution (BSD) UNIX version 4.3.

Table 3 describes the facility type keywords that can be supplied for the type argument.

Table 3 Logging Facility Type Keywords 

Facility Type Keyword
Description

auth

Indicates the authorization system.

cron

Indicates the cron facility.

daemon

Indicates the system daemon.

kern

Indicates the Kernel.

local0-7

Reserved for locally defined messages.

lpr

Indicates line printer system.

mail

Indicates mail system.

news

Indicates USENET news.

sys9

Indicates system use.

sys10

Indicates system use.

sys11

Indicates system use.

sys12

Indicates system use.

sys13

Indicates system use.

sys14

Indicates system use.

syslog

Indicates the system log.

user

Indicates user process.

uucp

Indicates UNIX-to-UNIX copy system.


Hostname Prefix Logging

To help manage system logging messages sent to syslog servers, Cisco IOS XR software supports hostname prefix logging. When enabled, hostname prefix logging appends a hostname prefix to syslog messages being sent from the router to syslog servers. You can use hostname prefixes to sort the messages being sent to a given syslog server from different networking devices.

To append a hostname prefix to syslog messages sent to syslog servers, use the logging hostname command in global configuration mode.

Syslog Source Address Logging

By default, a syslog message contains the IP address of the interface it uses to leave the router when sent to syslog servers. To set all syslog messages to contain the same IP address, regardless of which interface the syslog message uses to exit the router, use the logging source-interface command in global configuration mode.

UNIX Syslog Daemon Configuration

To configure the syslog daemon on a 4.3 BSD UNIX system, include a line such as the following in the /etc/syslog.conf file:

local7.debug /usr/adm/logs/cisco.log
 
   

The debugging keyword specifies the syslog level; see Table 7 for a general description of other keywords. The local7 keyword specifies the logging facility to be used; see Table 3 for a general description of other keywords.

The syslog daemon sends messages at this level or at a more severe level to the file specified in the next field. The file must already exist, and the syslog daemon must have permission to write to it.

Archiving Logging Messages on a Local Storage Device

Syslog messages can also be saved to an archive on a local storage device, such as the hard disk or a flash disk. Messages can be saved based on severity level, and you can specify attributes such as the size of the archive, how often messages are added (daily or weekly), and how many total weeks of messages the archive will hold.

Setting Archive Attributes

To create a logging archive and specify how the logging messages will be collected and stored, use the logging archive command in global configuration mode. The logging archive command enters the logging archive submode where you can configure the attributes for archiving syslogs. Table 4 lists the commands used to specify the archive attributes once you are in the logging archive submode.

Table 4 Commands Used to Set Syslog Archive Attributes 

Command
Description

archive-length weeks

Specifies the maximum number of weeks that the archive logs are maintained in the archive. Any logs older than this number are automatically removed from the archive.

archive-size size

Specifies the maximum total size of the syslog archives on a storage device. If the size is exceeded then the oldest file in the archive is deleted to make space for new logs.

device {disk0 | disk1 | harddisk}

Specifies the local storage device where syslogs are archived. By default, the logs are created under the directory <device>/var/log. If the device is not configured, then all other logging archive configurations are rejected. We recommend that syslogs be archived to the harddisk because it has more capacity than flash disks.

file-size size

Specifies the maximum file size (in megabytes) that a single log file in the archive can grow to. Once this limit is reached, a new file is automatically created with an increasing serial number.

frequency {daily | weekly}

Specifies if logs are collected on a daily or weekly basis.

severity severity

Specifies the minimum severity of log messages to archive. All syslog messages greater than or equal to this configured level are archived while those lesser than this are filtered out. See the "Severity Levels" section for more information.


Archive Storage Directories

By default, syslog archives are stored in the directory <device>/var/log. Individual archive files are saved to sub directories based on the year, month, and day the archive was created. For example, archive files created on February 26, 2006 are stored in the following directory:

harddisk:/var/log/2006/02/26
 
   

Severity Levels

You can limit the number of messages sent to a logging destination by specifying the severity level of syslog messages sent to a destination (see Table 7 for severity level definitions). Table 5 lists the commands used to control the severity level of syslog messages.

Table 5 Commands Used to Control the Severity Level of Syslog Messages

Command
Description

logging buffered [severity]

Limits the syslog messages sent to the logging buffer based on severity.

logging console [severity]

Limits the syslog messages sent to the console terminal based on severity.

logging monitor [severity]

Limits the syslog messages sent to terminal lines based on severity.

logging trap [severity]

Limits the syslog messages sent to syslog servers based on severity.

severity severity

Limits the syslog messages sent to a syslog archive based on severity.


The logging buffered, logging console, logging monitor, and logging traps commands limit syslog messages sent to their respective destinations to messages with a level number at or below the specified severity level, which is specified with the severity argument.


Note Syslog messages of lower severity level indicate events of higher importance. See Table 7 for severity level definitions.


Logging History Table

If you have enabled syslog messages traps to be sent to a Simple Network Management Protocol (SNMP) network management station (NMS) with the snmp-server enable traps syslog command, you can change the level of messages sent and stored in a history table on the router. You can also change the number of messages that get stored in the history table.

Messages are stored in the history table, because SNMP traps are not guaranteed to reach their destination. By default, one message of the level warning and above (see Table 7) is stored in the history table even if syslog traps are not enabled.

Table 6 lists the commands used to change the severity level and table size defaults of the logging history table.

Table 6 Logging History Table Commands

Command
Description

logging history severity

Changes the default severity level of syslog messages stored in the history file and sent to the SNMP server.

logging history size number

Changes the number of syslog messages that can be stored in the history table.



Note Table 7 lists the level keywords and severity level. For SNMP usage, the severity level values use +1. For example, emergency equals 1 not 0 and critical equals 3 not 2.


Syslog Message Severity Level Definitions

Table 7 lists the severity level keywords that can be supplied for the severity argument and corresponding UNIX syslog definitions in order from the most severe level to the least severe level.

Table 7 Syslog Message Severity Levels 

Severity Keyword
Level
Description
Syslog Definition

emergencies

0

System unusable

LOG_EMERG

alerts

1

Immediate action needed

LOG_ALERT

critical

2

Critical conditions

LOG_CRIT

errors

3

Error conditions

LOG_ERR

warnings

4

Warning conditions

LOG_WARNING

notifications

5

Normal but significant condition

LOG_NOTICE

informational

6

Informational messages only

LOG_INFO

debugging

7

Debugging messages

LOG_DEBUG


Syslog Severity Level Command Defaults

Table 8 lists the default severity level settings for the commands that support the severity argument.

Table 8 Severity Level Command Defaults

Command
Default Severity Keyword
Level

logging buffered

debugging

7

logging console

informational

6

logging history

warnings

4

logging monitor

debugging

7

logging trap

informational

6


How to Implement Logging Services

This section contains the following procedures:

Setting Up Destinations for SystemLogging Messages (required)

Configuring Logging to a Remote Server (required)

Configuring the Settings for the Logging History Table (required)

Modifying Logging to the Console Terminal and the Logging Buffer (optional)

Modifying the Format of Time Stamps (optional)

Disabling Time Stamps (optional)

Suppressing Duplicate Syslog Messages (optional)

Disabling the Logging of Link-Status Syslog Messages (optional)

Displaying System Logging Messages (optional)

Setting Up Destinations for SystemLogging Messages

This task explains how to configure logging to destinations other than the console terminal.

For conceptual information, see the Syslog Message Destinations section.

SUMMARY STEPS

1. configure

2. logging buffered [size | severity]

3. logging monitor [severity]

4. end
or
commit

5. terminal monitor

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

logging buffered [size | severity]

Example:

RP/0/RSP0/CPU0:router(config)# logging buffered severity warnings

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 valuefor 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.

Step 3 

logging monitor [severity]

Example:

RP/0/RSP0/CPU0:router(config)# logging monitor critical

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.

By default, entering this command without specifying a severity level for the severity argument sets the severity level to debugging.

Step 4 

end

or

commit

Example:

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 5 

terminal monitor

Example:

RP/0/RSP0/CPU0:router# terminal monitor

Enables the display of syslog messages for the current terminal session.

Note The logging of syslog message for the current terminal can be disabled with the terminal monitor disable command.

Use this command to reenable the display of syslog messages for the current session if the logging of messages for the current session was disabled with terminal monitor disable command.

Note Because this command is an EXEC mode command, it is set locally and will not remain in effect after the current session is ended.

Configuring Logging to a Remote Server

This task explains how to configure logging to remote syslog servers.

Prerequisites

You must have connectivity with syslog servers to configure syslog server hosts as the recipients for syslog messages.

SUMMARY STEPS

1. configure

2. logging [ip-address | hostname}

3. logging trap [severity]

4. logging facility [type]

5. logging hostnameprefix hostname

6. logging source-interface type interface-path-id

7. end
or
commit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router#

Enters global configuration mode.

Step 2 

logging {ip-address | hostname}

Example:

RP/0/RSP0/CPU0:router(config)# logging 10.3.32.154

Specifies a syslog server host as a destination for syslog messages.

By issuing this command more than once, you build a list of syslog servers that receive logging messages.

Step 3 

logging trap [severity]

Example:

RP/0/RSP0/CPU0:router(config)#

Limits the syslog messages sent to syslog servers based on severity.

By default, entering this command without specifying a severity level for the severity argument sets the severity level to informational.

Step 4 

logging facility [type]

Example:

RP/0/RSP0/CPU0:router(config)# logging facility kern

(Optional) Configures syslog facilities.

By default, entering this command without specifying a facility type for the type argument sets the facility to local-7.

Step 5 

logging hostnameprefix hostname

Example:

RP/0/RSP0/CPU0:router(config)#

(Optional) Appends a hostname prefix to syslog messages being sent from the router to syslog servers.

Tip Hostname prefix logging can be useful for sorting syslog messages received by syslog servers.

Step 6 

logging source-interface type interface-path-id

Example:

RP/0/RSP0/CPU0:router(config)#

(Optional) Sets the syslog source address.

By default, a syslog message sent to a syslog server contains the IP address of the interface it uses to leave the router.

Use this command to set all syslog messages being sent from the router to contain the same IP address, regardless of which interface the syslog message uses to exit the router.

Step 7 

end

or

commit

Example:

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Settings for the Logging History Table

This task explains how to configure the settings for the logging history table.

For conceptual information, see the Severity Levels section.

Prerequisites

Logging of messages to an SNMP NMS is enabled by the snmp-server enable traps syslog command. For more information about SNMP, see the Related Documents section.

SUMMARY STEPS

1. configure

2. logging history severity

3. logging history size number

4. end
or
commit

5. show logging history

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

logging history severity

Example:

RP/0/RSP0/CPU0:router(config)# logging history errors

Changes the default severity level of syslog messages stored in the history file and sent to the SNMP server.

By default, syslog messages at or below the warnings severity level are stored in the history file and sent to the SNMP server.

Step 3 

logging history size number

Example:

RP/0/RSP0/CPU0:router(config)# logging history size 200

Changes the number of syslog messages that can be stored in the history table.

By default, one syslog message is stored in the history table.

Note When the history table is full (that is, when it contains the maximum number of messages specified with this command), the oldest message is deleted from the table to allow the new message to be stored.

Step 4 

end

or

commit

Example:

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 5 

show logging history

Example:

RP/0/RSP0/CPU0:router# show logging history

(Optional) Displays information about the state of the syslog history table.

Modifying Logging to the Console Terminal and the Logging Buffer

This task explains how to modify logging configuration for the console terminal and the logging buffer.


Note Logging is enabled by default.


SUMMARY STEPS

1. configure

2. logging buffered [size | severity]

3. logging console [severity]

4. end
or
commit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

logging buffered [size | severity]

Example:

RP/0/RSP0/CPU0:router(config)# logging buffered size 60000

Specifies the logging buffer as a destination for syslog messages, sets the size of the logging buffer, and limits the the syslog messages sent to the logging buffer based on severity.

The default for the size argument is 4096 bytes.

The default 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.

Step 3 

logging console [severity]

Example:

RP/0/RSP0/CPU0:router(config)# logging console alerts

Limits messages sent to the console terminal based on severity.

Syslog messages are logged to the console terminal at the informational severity level by default.

Keyword options for the severity argument are emergencies, alerts, critical, errors, warnings, notifications, informational, and debugging.

Entering this command without specifying a severity level for the severity argument sets the severity level to informational.

Note Use this command to reenable logging to the console terminal if it was disabled with the no logging console command.

Step 4 

end

or

commit

Example:

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Modifying the Format of Time Stamps

This task explains how to modify the time-stamp format for syslog and debugging messages.

SUMMARY STEPS

1. configure

2. service timestamps log datetime [localtime] [msec] [show-timezone]
or
service timestamps log uptime

3. service timestamps debug datetime [localtime] [msec] [show-timezone]
or
service timestamps debug uptime

4. end
or
commit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

service timestamps log datetime [localtime] [msec] [show-timezone]

or

service timestamps log uptime

Example:

RP/0/RSP0/CPU0:router(config)# service timestamps log datetime localtime msec

or

RP/0/RSP0/CPU0:router(config)# service timestamps log uptime

Modifies the time-stamp format for syslog messages.

By default, time stamps are enabled. The default time-stamp format is month day HH:MM:SS.

Issuing the service timestamps log datetime command configures syslog messages to be time-stamped with the date and time.

The optional localtime keyword includes the local time zone in time stamps.

The optional msec keyword includes milliseconds in time stamps.

The optional show-timezone keyword includes time zone information in time stamps.

Issuing the service timestamps log uptime command configures syslog messages to be time-stamped with the time that has elapsed since the router last rebooted.

The service timestamps log uptime command configures time-stamps to be configured in HHHH:MM:SS, indicating the time since the router last rebooted.

Step 3 

service timestamps debug datetime [localtime] [msec] [show-timezone]

or

service timestamps debug uptime

Example:

RP/0/RSP0/CPU0:router(config)# service timestamps debug datetime msec show-timezone

or

RP/0/RSP0/CPU0:router(config)# service timestamps debug uptime

Modifies the time-stamp format for debugging messages.

By default, time-stamps are enabled. The default time stamp format is month day HH:MM:SS.

Issuing the service timestamps log datetime command configures debugging messages to be time-stamped with the date and time.

The optional localtime keyword includes the local time zone in time stamps.

The optional msec keyword includes milliseconds in time stamps.

The optional show-timezone keyword includes time zone information in time stamps.

Issuing the service timestamps log uptime command configures debugging messages to be time-stamped with the time that has elapsed since the networking device last rebooted.

Tip Entering the service timestamps command without any keywords or arguments is equivalent to entering the service timestamps debug uptime command.

Step 4 

end

or

commit

Example:

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Disabling Time Stamps

This tasks explains how to disable the inclusion of time stamps in syslog messages.

SUMMARY STEPS

1. configure

2. service timestamps disable
or
no service timestamps [debug | log] [datetime [localtime] [msec] [show-timezone]] | uptime]

3. end
or
commit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

service timestamps disable

or

no service timestamps [debug | log] [datetime [localtime] [msec] [show-timezone]] | uptime]

Disables the inclusion of time stamps in syslog messages.

Note Both commands disable the inclusion of time stamps in syslog messages; however, specifying the service timestamps disable command saves the command to the configuration, whereas specifying the no form of the service timestamps command removes the command from the configuration.

Step 3 

end

or

commit

Example:

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Suppressing Duplicate Syslog Messages

This task explains how to suppress the consecutive logging of duplicate syslog messages.

SUMMARY STEPS

1. configure

2. logging suppress duplicates

3. end
or
commit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

logging suppress duplicates

Example:

RP/0/RSP0/CPU0:router(config)# logging suppress duplicates

Prevents the consecutive logging of duplicate syslog messages.


Caution If this command is enabled during debugging sessions, you could miss important information related to problems that you are attempting to isolate and resolve. In such a case, you might consider disabling this command.

Step 3 

end

or

commit

Example:

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Disabling the Logging of Link-Status Syslog Messages

This task explains how to disable the logging of link-status syslog messages for logical and physical links.

When the logging of link-status messages is enabled, the router can generate a high volume of link-status updown syslog messages. Disabling the logging of link-status syslog messages reduces the number of messages logged.

SUMMARY STEPS

1. configure

2. logging events link-status disable

3. end
or
commit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

logging events link-status disable

Example:

RP/0/RSP0/CPU0:router(config)# logging events link-status disable

Disables the logging of link-status syslog messages for software (logical) and physical links.

The logging of link-status syslog messages is enabled by default for physical links.

To enable link-status syslog messages for both physical and logical links, use the logging events link-status software-interfaces command.

Use the no logging events link-status command to enable link-status syslog messages on physical links only.

Step 3 

end

or

commit

Example:

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Displaying System Logging Messages

This task explains how to display the syslog messages stored in the logging buffer.


Note The commands can be entered in any order.


SUMMARY STEPS

1. show logging

2. show logging location node-id

3. show logging process name

4. show logging string string

5. show logging start month day hh:mm:ss

6. show logging end month day hh:mm:ss

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show logging

Example:

RP/0/RSP0/CPU0:router# show logging

Displays all syslog messages stored in the buffer.

Step 2 

show logging location node-id

Example:

RP/0/RSP0/CPU0:router# show logging location 0/1/CPU0

Displays syslog messages that have originated from the designated node.

Step 3 

show logging process name

Example:

RP/0/RSP0/CPU0:router# show logging process init

Displays syslog messages that are related to the specified process.

Step 4 

show logging string string

Example:

RP/0/RSP0/CPU0:router# show logging string install

Displays syslog messages that contain the specified string.

Step 5 

show logging start month day hh:mm:ss

Example:

RP/0/RSP0/CPU0:router# show logging start december 1 10:30:00

Displays syslog messages in the logging buffer that were generated on or after the specified date and time.

Step 6 

show logging end month day hh:mm:ss

Example:

RP/0/RSP0/CPU0:router# show logging end december 2 22:16:00

Displays syslog messages in the logging buffer that were generated on or before the specified date and time.

Examples

In this example, the output displays all syslog messages stored in the logging buffer:

RP/0/0/CPU0:router# show logging
 
   
Syslog logging: enabled (20 messages dropped, 0 flushes, 0 overruns)
    Console logging: level debugging, 45 messages logged
    Monitor logging: level debugging, 0 messages logged
    Trap logging: level informational, 10 messages logged
    Logging to 172.19.72.224, 10 message lines logged
    Buffer logging: level debugging, 30 messages logged
 
   
Log Buffer (16384 bytes):
 
   
RP/0/0/CPU0:Dec  3 10:28:24.245 : wdsysmon[296]: %HA_WD-4-DISK_ALARM : A monitored disk is 
above 80% utilization. Please remove unwanted user files and configuration rollback 
points. 
RP/0/0/CPU0:Dec  3 10:28:24.247 : wdsysmon[296]: %HA_WD-6-DISK_USAGE : /disk0: usage 88%  
RP/0/0/CPU0:Dec  3 10:28:31.247 : lrd[215]: LRd waited 40 seconds for inventory... rc = 
1082230272 nCount = -1
.
.
.
 
   

In this example, the output displays s syslog messages stored in the logging buffer that originated from node 0/0/CPU0:

RP/0/0/CPU0:router# show logging location 0/0/CPU0
 
   
Syslog logging: enabled (20 messages dropped, 0 flushes, 0 overruns)
    Console logging: level debugging, 45 messages logged
    Monitor logging: level debugging, 0 messages logged
    Trap logging: level informational, 10 messages logged
    Logging to 172.19.72.224, 10 message lines logged
    Buffer logging: level debugging, 30 messages logged
 
   
Log Buffer (16384 bytes):
 
   
RP/0/0/CPU0:Dec  3 10:28:24.245 : wdsysmon[296]: %HA_WD-4-DISK_ALARM : A monitored disk is 
above 80% utilization. Please remove unwanted user files and configuration rollback 
points. 
RP/0/0/CPU0:Dec  3 10:28:24.247 : wdsysmon[296]: %HA_WD-6-DISK_USAGE : /disk0: usage 88%  
RP/0/0/CPU0:Dec  3 10:28:31.247 : lrd[215]: LRd waited 40 seconds for inventory... rc = 
1082230272 nCount = -1
RP/0/0/CPU0:Dec  3 10:30:35.068 : locald[210]: %LOCALD-3-ROOT_USERDB_INIT_FAIL : Failed to 
create aaa directory: File exists 
RP/0/0/CPU0:Dec  3 10:30:41.023 : config[129]: %CONFIGCLI-7-INFRA_READY : Infrastructure 
not ready to consume configuration. 
RP/0/0/CPU0:Dec  3 10:31:10.504 : sip[252]: sxa_iox_chkpt_init 154 SIP-LOG: SIP started - 
performing a cold start.
.
.
.
 
   

In this example, the output displays syslog messages stored in the logging buffer that were related to the wdsysmon process:

RP/0/0/CPU0:router# show logging process wdsysmon
 
   
Syslog logging: enabled (20 messages dropped, 0 flushes, 0 overruns)
    Console logging: level debugging, 45 messages logged
    Monitor logging: level debugging, 0 messages logged
    Trap logging: level informational, 10 messages logged
    Logging to 172.19.72.224, 10 message lines logged
    Buffer logging: level debugging, 30 messages logged
 
   
Log Buffer (16384 bytes):
 
   
RP/0/0/CPU0:Dec  3 10:28:24.245 : wdsysmon[296]: %HA_WD-4-DISK_ALARM : A monitored disk is 
above 80% utilization. Please remove unwanted user files and configuration rollback 
points. 
RP/0/0/CPU0:Dec  3 10:28:24.247 : wdsysmon[296]: %HA_WD-6-DISK_USAGE : /disk0: usage 88%  
LC/0/2/CPU0:wdsysmon[186]: %HA_WD-6-MEMORY_RECOVERY_DISABLED : Node physical memory 256MB 
LC/0/7/CPU0:wdsysmon[186]: %HA_WD-6-MEMORY_RECOVERY_DISABLED : Node physical memory 256MB 
LC/0/6/CPU0:wdsysmon[186]: %HA_WD-6-MEMORY_RECOVERY_DISABLED : Node physical memory 256MB 
.
.
.
 
   

In this example, the output displays syslog messages stored in the logging buffer that contained the string MgmtEth:

RP/0/0/CPU0:router# show logging string MgmtEth
 
   
Syslog logging: enabled (20 messages dropped, 0 flushes, 0 overruns)
    Console logging: level debugging, 45 messages logged
    Monitor logging: level debugging, 0 messages logged
    Trap logging: level informational, 10 messages logged
    Logging to 172.19.72.224, 10 message lines logged
    Buffer logging: level debugging, 30 messages logged
 
   
Log Buffer (16384 bytes):
 
   
RP/0/0/CPU0:Dec  3 10:32:15.608 : ifmgr[171]: %LINK-3-UPDOWN : Interface 
MgmtEth0/0/CPU0/0, changed state to Down 
RP/0/0/CPU0:Dec  3 10:32:15.642 : ifmgr[171]: %LINK-3-UPDOWN : Interface 
MgmtEth0/0/CPU0/0, changed state to Up 
.
.
.

In this example, the output displays syslog messages stored in the logging buffer that were logged on or after 11:00 on December 3:

RP/0/0/CPU0:router# show logging start december 3 11:00:00
 
   
Syslog logging: enabled (20 messages dropped, 0 flushes, 0 overruns)
    Console logging: level debugging, 45 messages logged
    Monitor logging: level debugging, 0 messages logged
    Trap logging: level informational, 10 messages logged
    Logging to 172.19.72.224, 10 message lines logged
    Buffer logging: level debugging, 30 messages logged
 
   
Log Buffer (16384 bytes):
 
   
RP/0/0/CPU0:Dec  3 11:48:44.513 : sysmgr[76]: sip(1) (jid 252) abnormally terminated, 
restart scheduled 
RP/0/0/CPU0:Dec  3 11:48:48.431 : sip[252]: sxa_iox_chkpt_init 130 SIP-LOG: SIP restart - 
warm start - 2 sessions so far.
LC/0/5/CPU0:Dec  3 13:28:19.070 : DI_Partner[50]: %SONET-4-ALARM : SONET0_5_0_0: SLOS  
LC/0/5/CPU0:Dec  3 13:34:12.281 : DI_Partner[50]: %SONET-4-ALARM : SONET0_5_0_0: SLOS 
cleared 
.
.
.
 
   

In this example, the output displays syslog messages stored in the logging buffer that were logged on or before 10:29:00 on December 3:

RP/0/0/CPU0:router# show logging end december 3 10:29:00
 
   
Syslog logging: enabled (20 messages dropped, 0 flushes, 0 overruns)
    Console logging: level debugging, 45 messages logged
    Monitor logging: level debugging, 0 messages logged
    Trap logging: level informational, 10 messages logged
    Logging to 172.19.72.224, 10 message lines logged
    Buffer logging: level debugging, 30 messages logged
 
   
Log Buffer (16384 bytes):
 
   
RP/0/0/CPU0:Dec  3 10:28:24.245 : wdsysmon[296]: %HA_WD-4-DISK_ALARM : A monitored disk is 
above 80% utilization. Please remove unwanted user files and configuration rollback 
points. 
RP/0/0/CPU0:Dec  3 10:28:24.247 : wdsysmon[296]: %HA_WD-6-DISK_USAGE : /disk0: usage 88%  
RP/0/0/CPU0:Dec  3 10:28:31.247 : lrd[215]: LRd waited 40 seconds for inventory... rc = 
1082230272 nCount = -1
.
.
.
 
   

In this example, the output displays syslog messages stored in the logging buffer that were logged on or between 10:30 and 11:00 on December 3:

RP/0/0/CPU0:router# show logging start december 3 10:30:00 end december 3 11:00:00
 
   
Syslog logging: enabled (20 messages dropped, 0 flushes, 0 overruns)
    Console logging: level debugging, 45 messages logged
    Monitor logging: level debugging, 0 messages logged
    Trap logging: level informational, 10 messages logged
    Logging to 172.19.72.224, 10 message lines logged
    Buffer logging: level debugging, 30 messages logged
 
   
Log Buffer (16384 bytes):
 
   
RP/0/0/CPU0:Dec  3 10:30:35.068 : locald[210]: %LOCALD-3-ROOT_USERDB_INIT_FAIL : Failed to 
create aaa directory: File exists 
RP/0/0/CPU0:Dec  3 10:30:41.023 : config[129]: %CONFIGCLI-7-INFRA_READY : Infrastructure 
not ready to consume configuration. 
RP/0/0/CPU0:Dec  3 10:31:10.504 : sip[252]: sxa_iox_chkpt_init 154 SIP-LOG: SIP started - 
performing a cold start.
RP/0/0/CPU0:Dec  3 10:31:33.782 : config[129]: %CONFIGCLI-7-INFRA_READY : Infrastructure 
ready to consume configuration. 
.
.

Archiving System Logging Messages to a Local Storage Device

This task explains how to display save syslog messages to an archive on a local storage device.

Restrictions

The local storage device must have enough space available to store the archive files. We recommend that syslogs be archived to the harddisk because it has more capacity than flash disks.

SUMMARY STEPS

1. configure

2. logging archive

3. device {disk0 | disk1 | harddisk}

4. frequency {daily | weekly}

5. severity severity

6. archive-length weeks

7. archive-size size

8. file-size size

9. end
or
commit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RSP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

logging archive

Example:

RP/0/RSP0/CPU0:router(config)# logging archive

Enters logging archive configuration mode.

Step 3 

device {disk0 | disk1 | harddisk}

Example:

RP/0/RSP0/CPU0:router(config-logging-arch)# device disk1

Specify the device to be used for logging syslogs.

This step is required. If the device is not configured, then all other logging archive configurations are rejected.

We recommend that syslogs be archived to the harddisk because it has more capacity than flash disks.

By default, the logs are created under the directory <device>/var/log

Step 4 

frequency {daily | weekly}

Example:

RP/0/RSP0/CPU0:router(config-logging-arch)# frequency weekly

(Optional) Specifies if logs are collected on a daily or weekly basis.Logs are collected daily by default.

Step 5 

severity severity

Example:

RP/0/RSP0/CPU0:router(config-logging-arch)# severity warnings

(Optional) Specifies the minimum severity of log messages to archive. All syslog messages greater than or equal to this configured level are archived while those lesser than this are filtered out. The severity levels are:

emergencies

alerts

critical

errors

warnings

notifications

informational

debugging

See the Syslog Message Severity Level Definitions section for information.

Step 6 

archive-length weeks

Example:

RP/0/RSP0/CPU0:router(config-logging-arch)# archive-length 6

(Optional) Specifies the maximum number of weeks that the archive logs are maintained in the archive. Any logs older than this number are automatically removed from the archive.

By default, archive logs are stored for 4 weeks.

Step 7 

archive-size size

Example:

RP/0/RSP0/CPU0:router(config-logging-arch)# archive-size 50

(Optional) Specifies the maximum total size of the syslog archives on a storage device. If the size is exceeded then the oldest file in the archive is deleted to make space for new logs.

The default archive size is 20 MB.

Step 8 

file-size size

Example:

RP/0/RSP0/CPU0:router(config-logging-arch)# file-size 10

(Optional) Specifies the maximum file size (in megabytes) that a single log file in the archive can grow to. Once this limit is reached, a new file is automatically created with an increasing serial number.

By default, the maximum file size is 1 megabyte.

Step 9 

end

or

commit

Example:

RP/0/RSP0/CPU0:router(config)# end

or

RP/0/RSP0/CPU0:router(config)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Examples

The following example shows how to configure a logging archive, and define the archive attributes:

RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# logging archive
RP/0/RSP0/CPU0:router(config-logging-arch)# device disk1
RP/0/RSP0/CPU0:router(config-logging-arch)# frequency weekly
RP/0/RSP0/CPU0:router(config-logging-arch)# severity warnings
RP/0/RSP0/CPU0:router(config-logging-arch)# archive-length 6
RP/0/RSP0/CPU0:router(config-logging-arch)# archive-size 50
RP/0/RSP0/CPU0:router(config-logging-arch)# file-size 10

Configuration Examples for Implementing Logging Services

This section provides the following configuration examples:

Configuring Logging to the Console Terminal and the Logging Buffer: Example

Setting Up Destinations for Syslog Messages: Example

Configuring the Settings for the Logging History Table: Example

Modifying Time Stamps: Example

Configuring a Logging Archive: Example

Configuring Logging to the Console Terminal and the Logging Buffer: Example

The following example shows a logging configuration where logging to the logging buffer is enabled, the severity level of syslog messages sent to the console terminal is limited to syslog messages at or below the critical severity level, and the size of the logging buffer is set to 60,000 bytes.

!
logging console critical
logging buffered 60000
!

Setting Up Destinations for Syslog Messages: Example

The following example shows a logging configuration where logging is configured to destinations other than the console terminal. In this configuration, the following is configured:

Logging is enabled to destinations other than the console terminal.

Syslog messages at or below the warnings severity level are sent to syslog server hosts.

Syslog messages at or below the critical severity level are sent to terminal lines.

The size of the logging buffer is set to 60,000 bytes.

The syslog server host at IP address 172.19.72.224 is configured as a recipient for syslog messages.

!
logging trap warnings
logging monitor critical
logging buffered 60000
logging 172.19.72.224
!

Configuring the Settings for the Logging History Table: Example

The following example shows a logging configuration in which the size of the logging history table is to 200 entries and the severity of level of syslog messages sent to the logging history table is limited to messages at or below the errors severity level:

logging history size 200
logging history errors

Modifying Time Stamps: Example

The following example shows a time-stamp configuration in which time stamps are configured to follow the format month date HH:MM:SS time zone:

service timestamps log datetime show-timezone
 
   

The following example shows a time-stamp configuration in which time stamps are configured to follow the format month date HH:MM:SS.milliseconds time zone:

service timestamps log datetime msec show-timezone

Configuring a Logging Archive: Example

The following example shows how to configure a logging archive, and define the archive attributes:

RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# logging archive
RP/0/RSP0/CPU0:router(config-logging-arch)# device disk1
RP/0/RSP0/CPU0:router(config-logging-arch)# frequency weekly
RP/0/RSP0/CPU0:router(config-logging-arch)# severity warnings
RP/0/RSP0/CPU0:router(config-logging-arch)# archive-length 6
RP/0/RSP0/CPU0:router(config-logging-arch)# archive-size 50
RP/0/RSP0/CPU0:router(config-logging-arch)# file-size 10

Where to Go Next

To configure alarm log correlation, see the Implementing and Monitoring Alarms and Logging Correlation on Cisco ASR 9000 Series Router module in the Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide.

Additional References

The following sections provide references related to implementing logging services on Cisco IOS XR software.

Related Documents

Related Topic
Document Title

Logging services command reference

Logging Services Commands on Cisco ASR 9000 Series Router module in the Cisco ASR 9000 Series Aggregation Services Router System Monitoring Command Reference

Onboard Failure Logging (OBFL) configuration

Onboard Failure Logging on Cisco ASR 9000 Series Router module in the Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide

Onboard Failure Logging (OBFL) commands

Onboard Failure Logging Commands on Cisco ASR 9000 Series Router module in the Cisco ASR 9000 Series Aggregation Services Router System Monitoring Command Reference

Alarm and logging correlation commands

Alarm Management and Logging Correlation Commands on Cisco ASR 9000 Series Router module in the Cisco ASR 9000 Series Aggregation Services Router System Monitoring Command Reference

Alarm and logging correlation configuration and monitoring tasks

Implementing and Monitoring Alarms and Alarm Log Correlation on Cisco ASR 9000 Series Router module in the Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide

SNMP commands

SNMP Commands on Cisco ASR 9000 Series Router module in the Cisco ASR 9000 Series Aggregation Services Router System Monitoring Command Reference

SNMP configuration tasks

Implementing SNMP on Cisco ASR 9000 Series Router module in the Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide

Cisco IOS XR getting started material

Cisco ASR 9000 Series Aggregation Services Router Getting Started Guide

Information about user groups and task IDs

Configuring AAA Services on Cisco ASR 9000 Series Aggregation Services Router module in the Cisco ASR 9000 Series Aggregation Services Router System Security Command Reference


Standards

Standards
Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.


MIBs

MIBs
MIBs Link

To locate and download MIBs using Cisco IOS XR software, use the Cisco MIB Locator found at the following URL and choose a platform under the Cisco Access Products menu: http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml


RFCs

RFCs
Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.


Technical Assistance

Description
Link

The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/techsupport