ASR 9000 Series_Command Reference

Cisco ASR 9000 Series Aggregation Services Router SystemManagement Command Reference, Release 4.0

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000 800 553-NETS (6387)Fax: 408 527-0883

Text Part Number: OL-23255-05

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITEDWARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITHTHE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain versionof the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.

NOTWITHSTANDINGANYOTHERWARRANTYHEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS"WITH ALL FAULTS.CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shownfor illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnershiprelationship between Cisco and any other company. (1110R)

2013 Cisco Systems, Inc. All rights reserved.

Preface

This reference describes the Cisco IOSXR SystemManagement commands. The preface for Cisco ASR 9000Series Aggregation Services Router SystemManagement Command Reference contains the following sections:

Changes to This Document, page iii

Obtaining Documentation and Submitting a Service Request, page iv

Changes to This DocumentThis table lists the technical changes made to this document since it was first printed.

Table 1: Changes to This Document

Change SummaryDateRevision

Modified an example in the clock timezonecommand.

Added a note to the exception sparse commandregarding core dumps on the RP.

Removed the system backup and show systembackup commands.

December 2011OL-23255-05

Modified the description of the showenvironment command last keyword.

Fixed the range for the snmp-serverqueue-length command.

July 2011OL-23255-04

Added a note to qualify when the rollbackconfiguration command might not work.

March 2011OL-23255-03

Cisco ASR 9000 Series Aggregation Services Router System Management Command Reference, Release 4.0 OL-23255-05 iii

Change SummaryDateRevision

The fpd auto-upgrade command was added.

Profile commands were added to the HardwareRedundancy and Node Administration module.

December 2010OL-23255-02

Initial release of this document.September 2010OL-23255-01

Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, submitting a service request, and gathering additional information,see the monthlyWhat's New in Cisco Product Documentation, which also lists all new and revised Ciscotechnical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to theWhat's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feedand set content to be delivered directly to your desktop using a reader application. The RSS feeds are a freeservice and Cisco currently supports RSS version 2.0.

Cisco ASR 9000 Series Aggregation Services Router System Management Command Reference, Release 4.0iv OL-23255-05

PrefaceObtaining Documentation and Submitting a Service Request

Boot Commands on the Cisco ASR 9000 SeriesRouter

This module describes the commands used to boot or reset Cisco IOS XR software.

For more information about ROM Monitor (ROMMON) and boot tasks, see Cisco ASR 9000 SeriesAggregation Services Router ROM Monitor Guide or Cisco ASR 9000 Series Aggregation Services RouterGetting Started Guide.

config-register, page 2

mirror, page 5

mirror pause, page 7

mirror resume, page 9

mirror verify, page 11

reload, page 13

reload (administration EXEC), page 15

show epm trace boot, page 17

show mirror, page 19

show reboot, page 23

show variables boot, page 27

show variables system, page 29

system boot-sequence, page 31

Cisco ASR 9000 Series Aggregation Services Router System Management Command Reference, Release 4.0 OL-23255-05 1

config-registerTo define the configuration register boot value, use the config-register command in administration EXECmode.

config-register {value| boot-mode {exec-mode| rom-monitor}| console-baud baud-rate| console-break-key{disable| enable}| password-recovery {disable| enable}} [location {node-id| all}]

Syntax Description Hexadecimal or decimal value that represents the 16-bitconfiguration register value to be used the next time therouter is reloaded. Range is from 0x0 to 0xFFFF (0 to 65535in decimal).

For information about common configuration registersettings, see Table 2: Common Configuration RegisterSettings, on page 3.

value

Specifies what to do when the system is rebooted.boot-mode

Specifies to load the Cisco IOSXR software and enter EXECmode on next system reboot.

exec-mode

Specifies to enter ROM Monitor mode on next systemreboot.

rom-monitor

Specifies the console baud rate.console-baud baud-rate

Specifies to disable or enable the console break key on thenext system reboot.

console-break-key {disable | enable}

Specifies to enable or disable the password recovery modeon the next reboot.

password-recovery {disable | enable}

(Optional) Specifies the RSP node for which to define theconfiguration register boot value. The all keyword specifiesall RSP nodes.

location {node-id | all}

Command Default By default, the configuration register value is 0x102 after a Turboboot.

Command Modes Administration EXEC

Command History ModificationRelease

This command was introduced.Release 3.7.2

Cisco ASR 9000 Series Aggregation Services Router System Management Command Reference, Release 4.02 OL-23255-05

Boot Commands on the Cisco ASR 9000 Series Routerconfig-register

Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate taskIDs. If the user group assignment is preventing you from using a command, contact your AAA administratorfor assistance.

The configuration register setting is a 16-bit, user-configurable value that determines how the router switchprocessor (RSP) functions during initialization. The configuration register can cause the RSP to boot normallyfrom the default configuration, or to enter ROMMON mode during a reload. Configuration register settingscan also be used to perform tasks such as password recovery.

The config-register command is entered in administration EXEC mode, on the designated shelf controller(DSC) of the system. The DSC is the primary RSP of the owner secure domain router (owner SDR). Whensetting the configuration register value for the config-register command, note the following conditions:

If both the primary and standby DSC are up and running when the configuration register value is set,the configuration register value applies to both the primary and standby DSC.

By contrast, if only the primary DSC is up and running when the configuration register value is set andthe standby DSC is introduced into the router at a later time, the router does not attempt to synchronizethe configuration register value for the standby RSP to that of the active RSP; in this situation, theconfiguration register setting applied to the standby DSC is determined by the configuration registervalue set in ROMMON mode.

To display the current configuration settings, use the show variables boot command .Note

This table describes the most commonly used configuration register settings.

Table 2: Common Configuration Register Settings

DescriptionValue

RSP enters ROMMON mode (rommon B1>) on thenext system boot.

0x0

RSP loads the Cisco IOS XR software and defaultconfiguration on the next system boot. After loggingin, the user can access EXEC mode.

0x2

Router loads the Cisco IOS XR software with theconsole Break key disabled on the next system boot.

0x102

Router enters the password recovery mode on thenext system boot.

0x40

If you use the various keywords to set the configuration settings, note that the hexadecimal value is updatedin an additive or subtractive manner to represent the keyword used. For example, if the current configurationsetting is 0x102 and you use the config-register command with the password-recovery enable keywords,the value is updated to 0x142.



Task ID OperationsTask ID

read, writeroot-lr

Examples The following example shows how to set the configuration register on the DSC to 0x2. Setting the configurationregistration to 0x2 causes the router to boot the Cisco IOS XR software and enter EXECmode during a routerreload.

RP/0/RSP0/CPU0:router(admin)# config-register boot-mode exec-mode

Sun May 31 12:10:36.037 PST Successfully set config-register to0x2 on node 0/RSP0/CPU0

Related Commands DescriptionCommand

Reloads the route switch processor (RSP).reload

Displays the configuration register setting and boot file setting for the RSPsin the system.

show variables boot

Displays the configuration of the system hardware, the software version, thenames and sources of configuration files, and the boot images.

show version



mirrorTo configure disk mirroring on a node, use themirror command in global configuration mode. To disabledisk mirroring, use the no form of this command.

mirror location [preconfigure] node-id primary-device:secondary-device:

no mirror location

Syntax Description Specifies the node of the RP. It can be a node that is not yetinstalled if the preconfigure keyword is used. The node-idargument is entered in the rack/slot/module notation.

location node-id

(Optional) Enables you to specify a node that is not yetinstalled.

preconfigure

Specifies the primary boot device used to store installationpackages and configuration files. Supported devices are:

disk0:

disk1: (if installed)

compactflash: (if installed)

primary-device :

Storage device on the same RP as the primary-device, towhere critical data is replicated. Supported devices are thesame as for primary-device :, but secondary-device : mustbe different than the primary-device :.

secondary-device :

Command Default None

Command Modes Global configuration





Boot Commands on the Cisco ASR 9000 Series Routermirror

Themirror command replicates all critical data contained in the primary partition of the primary boot device,onto a second storage device on the same RSP. Therefore, if the primary boot device fails, applications continueto be serviced transparently by the secondary device, without having to switch control to a standby RSP.

Before themirror command can be used, the secondary storage device must be partitioned using the format,on page 255 command. If the primary boot device is not partitioned, once mirroring is enabled and all data onthe primary boot device is replicated to the secondary device, the primary boot device is partitionedautomatically. This guarantees that only critical data on the primary boot device is mirrored to the secondarydevice. Noncritical data, such as logging data, should not be mirrored and should, therefore, be saved to thesecondary partition on the storage device.

To temporarily suspend disk mirroring without changing the configuration, use themirror pause commandin EXEC mode.


read, writeroot-lr

Examples The following example shows how to configure disk mirroring from the primary boot device (disk0:) to thesecondary storage device (disk1:):

RP/0/RSP0/CPU0:router(config)# mirror location 0/rp0/cpu0 disk0: disk1:


Formats a file system.format

Temporarily pauses disk mirroring on a node.mirror pause

Resumes disk mirroring on a node after it has been temporarily stopped.mirror resume


Boot Commands on the Cisco ASR 9000 Series Routermirror

mirror pauseTo temporarily pause disk mirroring on a node, use themirror pause command in EXEC or administrationEXEC mode.

mirror pause [location {node-id| all}]

Syntax Description (Optional) Specifies the node of the RSP. The node-id argument is enteredin the rack/slot/module notation. The all keyword specifies all RSP nodes.


Command Default If no node is specified, disk mirroring is paused on the active RSP.

Command Modes EXEC

Administration EXEC




Themirror pause command temporarily pauses the mirroring of the primary boot device. This command isprimarily useful during an installation operation to prevent significant performance degradation on singleCPU boards. Themirror pause command does not change the configured state of mirroring, but rather causesthe mirroring to be suspended until themirror resume command is used.

Themirror pause command has no affect if themirror configuration command is not enabled.


read, writeroot-lr


Boot Commands on the Cisco ASR 9000 Series Routermirror pause

Examples The following example shows how to pause disk mirroring on the active RSP:

RP/0/RSP0/CPU0:router# mirror pause


Configures disk mirroring on a node.mirror

Resumes disk mirroring on a node after it has been temporarily stopped.mirror resume


Boot Commands on the Cisco ASR 9000 Series Routermirror pause

mirror resumeTo resume disk mirroring on a node after it has been temporarily stopped, use themirror resume commandin EXEC or administration EXEC mode.

mirror resume [location {node-id| all}]

Syntax Description (Optional) Specifies the node of the RSP. The node-id argument is enteredin the rack/slot/module notation. The all keyword specifies all RSP nodes.


Command Modes EXEC

Administration EXEC




Themirror resume command resumes the mirroring of the primary boot device after it has been temporarilypaused with themirror pause command.

Themirror resume command has no affect if the mirror configuration command is not enabled and themirror pause command has not been used.


read, writeroot-lr

Examples The following example shows how to resume disk mirroring on the active RSP:

RP/0/RSP0/CPU0:router# mirror resume




Boot Commands on the Cisco ASR 9000 Series Routermirror resume

DescriptionCommand

Temporarily pauses disk mirroring on a node.mirror pause


Boot Commands on the Cisco ASR 9000 Series Routermirror resume

mirror verifyTo verify disk synchronization for disk mirroring on a node, use the mirror verify command in EXEC oradministration EXEC mode.

mirror verify [location node-id]

Syntax Description (Optional) Specifies the node of the RSP. The node-id argument is enteredin the rack/slot/module notation.

location node-id

Command Default If no node is specified, the verification is done on the active RSP.

Command Modes EXEC

Administration EXEC




The mirror verify command verifies the synchronization consistency between the primary and secondarymedia devices being used in mirroring. The command verifies that the full contents are identical between themirrored devices and reports any inconsistencies found.


read, writeroot-lr

Examples The following example shows how to verify the disk mirroring on the active RSP:

RP/0/RSP0/CPU0:router# mirror verify

Mirror Verify Information for 0/RSP0/CPU0.


Boot Commands on the Cisco ASR 9000 Series Routermirror verify

========================================================Primary device and secondary device are fully synchronized.




Boot Commands on the Cisco ASR 9000 Series Routermirror verify

reloadTo reload the route switch processor (RSP), use the reload command in EXEC mode.

reload

Syntax Description This command has no keywords or arguments.

Command Default No default behavior or values

Command Modes EXEC

Command History ModificationsReleases



Use the reload command to cause the RSP to reload the Cisco IOSXR software according to the configurationregister setting (for example, 0x0 to enter ROMMON mode and 0x2 to reload the RSP to EXEC mode). If astandby RSP is in the ready redundancy state, the reload command also causes the router to fail over to thestandby RSP. Use the show redundancy command in EXEC mode to display the status of the standby RSP.

When the reload command is used and a switchover occurs, the running (active) software configuration isautomatically maintained during switchover.

If a standby RSP is not installed or is not in the ready state, then the router experiences a loss of servicewhile the active RSP is reloading Cisco IOS XR software. To view the status of the standby RSP, issuethe show redundancy command in EXEC mode.

Caution

If you use the reload command and there is no available standby node, you are prompted to continue withthe reload:

RP/0/RSP0/CPU0:router# reload

Standby card not present or not Ready for failover. Proceed?[confirm]y


executeroot-lr


Boot Commands on the Cisco ASR 9000 Series Routerreload

Examples The following example shows how to reload the active RSP. If a standby RSP is in the ready state, then therouter fails over to the standby RSP. If the standby RSP is not installed or is not in the ready state, then therouter enters ROMMON mode and routing operations stop.

RP/0/RSP0/CPU0:router# reload

Updating Commit Database. Please wait...[OK]Proceed with reload? [confirm] y

PCI0 device[7]: Vendor ID 0x10eePCI0 device[7]: Device ID 0x300ePCI1 device[7]: Device ID 0x1100PCI1 device[7]: Vendor ID 0x1013PCI1 device[8]: Device ID 0x649PCI1 device[8]: Vendor ID 0x1095PCI1 device[9]: Device ID 0x5618PCI1 device[9]: Vendor ID 0x14e4PCI1 device[10]: Device ID 0x5618PCI1 device[10]: Vendor ID 0x14e4System Bootstrap, Version 1.15(20040120:002852) ,Copyright (c) 1994-2004 by cisco Systems, Inc.Board type is 0x100000 (1048576)Enabling watchdogBroadcom 5618 #0 Found on PCIBroadcom 5618 #1 Found on PCINo. of BCM 56xx switches found 2 .BCM Switch #0 initialisation complete.BCM Switch #1 initialisation completeG4(7450-SMP-GT64260_A) platform with 2048 Mb of main memory

rommon B1 >


Defines the configuration register boot values.config-register

Reloads a node or all nodes on a single chassis or multishelf system.reload (administration EXEC)

Displays the status of route processor redundancy.show redundancy


Boot Commands on the Cisco ASR 9000 Series Routerreload

reload (administration EXEC)To reload a node or all nodes on a single chassis or multishelf system, use the reload command in administrationEXEC mode.

reload [location {node-id| all}| rack rack-number]

Syntax Description (Optional) Specifies the node to reload. The node-id argument is enteredin the rack/slot/module notation. The all keyword specifies all RP nodes.


Reloads all the nodes on a specified chassis.rack

Rack number of the line card chassis or fabric chassis.rack-number






Before reloading nodes on the router, we recommend using the cfs check command to check the sanityof the configuration file system and attempt to recover from internal inconsistencies.

Note

To reload a specific node on the router, specify the reload command with the location node-id keyword andargument. The node-id is expressed in the rack/slot/module notation.


executeroot-system


Boot Commands on the Cisco ASR 9000 Series Routerreload (administration EXEC)

Examples The following example shows how to reload all nodes on the router:

RP/0/RSP0/CPU0:router(admin)# reload location all

Graceful reload of all nodes not supportedAssuming 'force'Operation may result in file corruptions or loss of config. Proceed [Y/N]? y

To ensure the sanity of the configuration file system, enter the cfs check command on the router.Note


Performs a check of the Configuration File System (CFS).cfs check



Displays the status of route processor redundancy.show redundancy


Boot Commands on the Cisco ASR 9000 Series Routerreload (administration EXEC)

show epm trace bootTo display execution path monitoring traces, use the show epm trace boot command in administrationEXEC mode.

show epm trace boot [hexdump] [last n] [reverse] [stats] [tailf] [unique][verbose] [wrapping][file filenameoriginal] [location {node-id| all}]

Syntax Description (Optional) Displays traces in hexadecimal format.hexdump

(Optional) Displays the last n number of traces only.last n

(Optional) Displays the most recent traces first.reverse

(Optional) Displays execution path statistics.stats

(Optional) Displays new traces as they are added.tailf

(Optional) Displays unique entries only, along with the countof the number of times this entry appears.

unique

(Optional) Displays additional internal debugging information.verbose

(Optional) Displays wrapping entries.wrapping

(Optional) Specifies the filename of the file to display. Youcan specify up to four trace files.

file filename original

(Optional) Specifies the node of the RSP. The node-idargument is entered in the rack/slot/module notation. You canspecify up to four nodes. The all keyword specifies all RSPnodes.







Boot Commands on the Cisco ASR 9000 Series Routershow epm trace boot


The show epm trace boot command provides a simple way of tracking and time-stamping critical eventsto clearly understand their temporal relationship to one another and the amount of time spent performingcritical operations.


readbasic services

Examples The following example shows sample output from the show epm trace boot command:

RP/0/RSP0/CPU0:router(admin)# show epm trace boot

Mon Jun 1 03:16:36.946 PST22 wrapping entries (1024 possible, 0 filtered, 22 total)Oct 8 07:54:49.610 epm/boot 0/RSP0/CPU0 t1 @ 00:00:06 - [init] process-startOct 8 07:55:25.710 epm/boot 0/RSP0/CPU0 t1 @ 00:00:42 - [insthelper] process-startOct 8 07:57:08.992 epm/boot 0/RSP0/CPU0 t1 @ 00:02:25 - [sysmgr] process-startOct 8 07:57:09.785 epm/boot 0/RSP0/CPU0 t7 @ 00:02:26 - [sysmgr] start-level: startOct 8 07:57:10.722 epm/boot 0/RSP0/CPU0 t1 @ 00:02:27 - [sw_dwnld_svr] process-startOct 8 07:57:12.482 epm/boot 0/RSP0/CPU0 t11 @ 00:02:29 - [sysmgr] start-level: adminOct 8 07:57:13.385 epm/boot 0/RSP0/CPU0 t1 @ 00:02:30 - [instdir] process-startOct 8 07:57:19.638 epm/boot 0/RSP0/CPU0 t1 @ 00:02:36 - [instdir_lr] process-startOct 8 07:58:07.045 epm/boot 0/RSP0/CPU0 t9 @ 00:03:23 - [sysmgr] admin-plane-upOct 8 07:58:52.057 epm/boot 0/RSP0/CPU0 t4 @ 00:04:08 - [cfgmgr-rp] admin-config-startOct 8 07:58:59.973 epm/boot 0/RSP0/CPU0 t4 @ 00:04:16 - [cfgmgr-rp] admin-config-doneOct 8 07:59:00.079 epm/boot 0/RSP0/CPU0 t9 @ 00:04:16 - [sysmgr] start-level: infraOct 8 07:59:00.615 epm/boot 0/RSP0/CPU0 t1 @ 00:04:17 - [devc-conaux] exec-availableOct 8 07:59:02.288 epm/boot 0/RSP0/CPU0 t4 @ 00:04:18 - [cfgmgr-rp] admin-plane-mount-doneOct 8 07:59:08.157 epm/boot 0/RSP0/CPU0 t6 @ 00:04:24 - [instdir] ready-for-requestsOct 8 07:59:15.999 epm/boot 0/RSP0/CPU0 t6 @ 00:04:32 - [sysmgr] start-level: activeOct 8 07:59:32.300 epm/boot 0/RSP0/CPU0 t13 @ 00:04:48 - [sysmgr] start-level: finalOct 8 07:59:38.143 epm/boot 0/RSP0/CPU0 t9 @ 00:04:54 - [sysmgr] lr-plane-upOct 8 07:59:38.189 epm/boot 0/RSP0/CPU0 t4 @ 00:04:54 - [cfgmgr-rp] lr-config-startOct 8 07:59:49.898 epm/boot 0/RSP0/CPU0 t4 @ 00:05:06 - [cfgmgr-rp] lr-config-doneOct 8 07:59:50.259 epm/boot 0/RSP0/CPU0 t4 @ 00:05:06 - [cfgmgr-rp]bulk-interface-config-startOct 8 07:59:50.351 epm/boot 0/RSP0/CPU0 t7 @ 00:05:06 - [cfgmgr-rp] node-config-done

In this sample output, the time stamp following the @ sign is the elapsed time in the format hh:mm:ss sincethe execution phase started (for example, since node start, in the case of a boot).


Boot Commands on the Cisco ASR 9000 Series Routershow epm trace boot

show mirrorTo display disk mirroring information, use the show mirror command in EXEC or administration EXECmode.

show mirror [location {node-id| all}]

Syntax Description (Optional) Specifies the node of the RSP for which to display the mirroringinformation. The node-id argument is entered in the rack/slot/module notation.The all keyword specifies all RSP nodes.



Command Modes EXEC

Administration EXEC





readfilesystem

Examples The following is sample output from the show mirror command:

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

Mirror Information for 0/RSP0/CPU0.========================================================Mirroring EnabledConfigured Primary: disk0:Configured Secondary: disk1:


Boot Commands on the Cisco ASR 9000 Series Routershow mirror

Current Mirroring State: Syncing FilesCurrent Physical Primary: disk1:Current Physical Secondary: disk0:

Mirroring Logical Device: disk0:

Physical Device State Flags--------------------------------------------------------disk0: Available Enabled Formatteddisk1: Available Enabled Formattedcompactflash: Not Presentdisk0a: Available Formatteddisk1a: Available Formattedcompactflasha: Not Present

Mirroring Rommon VariableBOOT_DEV_SEQ_CONF = disk0:;disk1:BOOT_DEV_SEQ_OPER = disk1:MIRROR_ENABLE = Y

Table 3: show mirror Field Descriptions

DescriptionField

Indicates whether mirroring is enabled or disabled.Mirroring Enabled

If mirroring is enabled, the configured primary diskfor mirroring.

Configured Primary

If mirroring is enabled, the configured secondary diskfor mirroring.

Configured Secondary

Current status of mirroring. Possible values are asfollows:

Syncing filesFiles are being synchronized betweenthe primary and secondary disks.

Not ConfiguredMirroring is not configured.

Mirroring PausedIn this state, no mirroring is beingdone to the secondary device and the disk redundancyhas been removed. The values of theBOOT_DEV_SEQ_OPERandMIRROR_ENABLEvariables reflect this.

RedundantThe primary and secondary disks aretotally in synchronization. Any read or write failureon the primary device results in disk redundancyswitchover such that all operations are performed onthe secondary device.

Current Mirroring State

Current primary disk.Current Physical Primary

Current secondary disk.Current Physical Secondary



DescriptionField

Device name used by the mirroring process tointercept all application requests to that named devicebefore passing them through to one of the mirroredphysical devices.

Mirroring Logical Device

Physical disk in router.Physical Device

Status of the disk. Possible values are as follows:

AvailableDisk exists in router and is available.

Not presentDisk does not exist in router.Partitioning of disks is available only after the diskhas been formatted with the partition keyword.

State

EnabledDisk mirroring has been enabled on thisdevice and the device is part of the mirroring process.

RepairedDuring the boot, some minorinconsistencies were discovered on the disk and wererepaired to make the file system consistent.

FormattedDiskwas formatted beforemirroringwasenabled.

Flags

ROM Monitor environmental variable for the bootdisk sequence. This variable is is set when mirroringis enabled through the mirror configurationcommand. The devices in this ROMMON variabledeclare the primary and the secondary devices of themirroring process. The first device is the primarydevice and the second device is the secondary devicein the mirroring process.

This variable is also shared by the diskbackup feature. This variable can also be setor unset using the system boot-sequencecommand of the disk backup feature. Butthe use of system boot-sequence and systembackup commands is blocked, if mirroringis enabled.

Note

BOOT_DEV_SEQ_CONF=

ROMMonitor environmental variable that reflectsthe state of the disk redundancy status. Whenmirroring is enabled and the state is redundant, thisvariable is set to the primary device followed by thesecondary device. When mirroring is not in theredundancy state, then this variable is updated tocontain only the primary device.

BOOT_DEV_SEQ_OPER=



DescriptionField

ROMMonitor environmental variable whose valuereflects the mirroring status. If it is set to Y, thenmirroring is enabled. If it is set to P, then mirroringis paused. If empty, mirroring is not enabled.

MIRROR_ENABLE



Verifies disk synchronization for disk mirroring on a node.mirror verify



show rebootTo display reboot information for a node, use the show reboot command in EXEC or administration EXECmode.

show reboot {{first| last} {crashinfo| syslog| trace}| graceful| history [reverse]| pcds} location node-id

Syntax Description (Optional) Displays information about the first ungraceful reboot.first

(Optional) Displays information about the last ungraceful reboot.last

Displays crash information for an ungraceful reboot.crashinfo

Displays the syslogs related to an ungraceful reboot.syslog

Displays trace information for an ungraceful reboot.trace

Displays information about the last graceful reboot.graceful

Displays the reboot history of a specific node.history

(Optional) Displays the reboot history information in reverse chronologicalorder.

reverse

Displays PCDS critical information about the last ungraceful reboot.pcds

Specifies which node to reload. The node-id argument is expressed in therack/slot/module notation.

location node-id


Command Modes EXEC

Administration EXEC





Boot Commands on the Cisco ASR 9000 Series Routershow reboot

The history keyword for the show reboot command displays all reboot causes stored for previous noderesets.

Crash information ( crashinfo ), syslog, and kernel dumper ltrace ( trace ) can be displayed for the first orlast reboot if it is an ungraceful reboot.


readsystem

Examples This example shows sample output from the show reboot command with the history keyword:

RP/0/RSP0/CPU0:router# show reboot history location 0/rp0/cpu0

No Time Cause Code Reason--------------------------------------------------------------------------------01 Thu Jul 19 00:25:03 2007 0x00000001 Cause: User Initiated reload

Process: reloadTraceback: fc1941a0 fc194290 fc042d90 48200624 48202120 0

02 Thu Jul 19 20:32:57 2007 0x21000010 Cause: Missed deadline, client: sc-reddrv-main,timeout: 5Process: wd-critical-monTraceback: fc1941a0 fc194290 48200738 482013cc 48201c04 fc1d4fb0

03 Thu Jul 19 22:21:05 2007 0x0000000004 Thu Jul 19 22:44:37 2007 0x00000045 Cause: Non-dSC node booted with composite image

Process: insthelperTraceback: fc1941a0 fc194290 fc61e4a0 4820f928 48210654 48201cc0

05 Thu Jul 19 22:52:19 2007 0x00000045 Cause: Non-dSC node booted with composite image

Process: insthelperTraceback: fc1941a0 fc194290 fc6204a0 4820f928 48210654 48201cc0

06 Fri Jul 20 02:10:51 2007 0x00000001 Cause: User Initiated reloadProcess: reloadTraceback: fc15a1a0 fc15a290 fc045d90 48200624 48202120 0

07 Mon Jul 23 19:39:49 2007 0x00000045 Cause: RP cold booted with incorrect software

Process: insthelperTraceback: fc1941a0 fc194290 fc61a4a0 4820f8b0 48210fc8 48201cc0

08 Mon Jul 23 19:54:45 2007 0x00000002 Cause: User Initiated RebootProcess: rebootTraceback: fc1941a0 fc194290 48200154 48201468 0 0

The following example shows sample output from the show reboot command with the first crashinfokeywords:

RP/0/RSP0/CPU0:router# show reboot first crashinfo location 0/rp0/cpu0

Crashinfo Timestamp: Thu Jul 19 20:32:57 2007

20070719 20:32:57

Crash Reason: Cause code 0x21000010 Cause: Missed deadline,client: sc-reddrv-main, timeout: 5 Process: wd-critical-mon

Traceback: fc1941a0 fc194290 48200738 482013cc 48201c04 fc1d4fb0 Timezone UTC0



Exception at 0xfc1944c8 signal 5 c=1 f=3

Active process(s):pkg/bin/wd-critical-mon Thread ID 1 on cpu 0pkg/bin/l3test Thread ID 0 on cpu 1

REGISTER INFOr0 r1 r2 r3

R0 01000000 4817e8c0 4820e208 000000der4 r5 r6 r7

R4 fc1b4856 7fffffff 4817e738 fc1b4856r8 r9 r10 r11

R8 00000000 602cf522 00000000 00000000r12 r13 r14 r15

R12 602cf51c 4820e1a0 00000000 00000000r16 r17 r18 r19

R16 00000000 00000000 00000000 00000000r20 r21 r22 r23

R20 00000000 00000000 48200000 48200000r24 r25 r26 r27

R24 48200000 48200000 48200000 48200000r28 r29 r30 r31

R28 00000028 00000001 21000010 6029b000cnt lr msr pc

R32 00000000 fc194290 0002d932 fc1944c8cnd xer

R36 44000094 20000006

SUPERVISOR REGISTERS

Memory Management Registers

Instruction BAT RegistersIndex # ValueIBAT0U # 0x1ffeIBAT0L # 0x12IBAT1U # 0IBAT1L # 0IBAT2U # 0x30000ffeIBAT2L # 0xf0000032IBAT3U # 0xfffc0003IBAT3L # 0x40011

Data BAT RegistersIndex # ValueDBAT0U # 0x1ffeDBAT0L # 0x12DBAT1U # 0DBAT1L # 0x10000012DBAT2U # 0x30000ffeDBAT2L # 0xf000006aDBAT3U # 0xfffc0003DBAT3L # 0x40011

Segment RegistersIndex # SR-Value

0 # 01 # 02 # 03 # 04 # 05 # 06 # 07 # 08 # 09 # 010 # 011 # 012 # 013 # 014 # 015 # 0



Exception Handling RegistersData Addr Reg # DSISR0x602cf440 # 0x42000000

SPRG0 # SPRG1 # SPRG2 # SPRG30x1 # 0x21000010 # 0x6029b000 # 0

SaveNRestore SRR0 # SaveNRestore SRR10xfc1944c4 # 0x2d932

Miscellaneous RegistersProcessor Id Reg # 0

HID0 # 0x8410c0bcHID1 # 0x9001ac80

MSSCR0 # 0x88000MSSSR0 # 0

STACK TRACE#0 0xfc194290#1 0x48200738#2 0x482013cc#3 0x48201c04#4 0xfc1d4fb0





show variables bootTo display the configuration register setting and boot file setting for the route switch processors (RSPs) inthe system, use the show variables boot command in administration EXEC mode.

show variables boot [location {all| node-id}]

Syntax Description (Optional) Specifies the node to reload. The node-id argument isexpressed in the rack/slot/module notation. Use the all keyword toindicate all nodes.

location{node-id | all}






Use the show variables boot command to display system boot variables for the router. This command displaysthe configuration register setting and boot file setting for the RSPs in the system. Use the location node-idkeyword and argument to display the configuration register setting for a specific card.

The configuration register setting is set with the config-register command. The boot variable is set in ROMMonitor mode. For more information about ROM Monitor mode, see Cisco ASR 9000 Series AggregationServices Router ROM Monitor Guide.


readroot-lr

Examples This example shows sample output from the show variables boot command:

RP/0/RSP0/CPU0:router# show variables boot

Mon Jun 1 05:21:56.791 PST


Boot Commands on the Cisco ASR 9000 Series Routershow variables boot

BOOT variable = disk0:asr9k-os-mbi-3.9.0.11I/mbiasr9k-rp.vm,1;CONFREG variable = 0x102



Displays internal system environmental variables.show variables system

Displays the configuration of the system hardware, the software version,the names and sources of configuration files, and the boot images.

show version


Boot Commands on the Cisco ASR 9000 Series Routershow variables boot

show variables systemTo display internal system environmental variables set on the router, use the show variables system commandin EXEC mode.

show variables system



Command Modes EXEC




Use the show variables system command to display system environmental variables for the router.

To display the configuration register setting, use the show variables boot command in administration EXECmode.


readbasic-services

Examples This example illustrates sample output from the show variables system command. The output is meant to beinterpreted by Cisco personnel.

RP/0/RSP0/CPU0:router# show variables system

TERM=vt220GDB_PDEBUG=-P1TERM=vt100DIR_PREFIX=.LOADPATH=/pkgLD_LIBRARY_PATH=/pkg/libPATH=/pkg/binBFM_CONFIG_PATH=/pkg/bfm/configBGP_PATH=/pkg/bgp


Boot Commands on the Cisco ASR 9000 Series Routershow variables system

CONFIGS_PATH=/pkg/configsCRAFT_PATH=/pkg/cwiCTF_PATH=/pkg/ctfDM_RULES_PATH=/pkg/dm/rulesETC_PATH=/pkg/etcFPD_PATH=/pkg/fpdIM_RULES_PATH=/pkg/rulesINIT_STARTUP_PATH=/pkg/init.dINSTHELPER_PATH=/pkg/otherMAN_PATH=/pkg/manMIB_LIBRARY_PATH=/pkg/lib/mibMIB_PATH=/pkg/mibNETIO_SCRIPT_PATH=/pkg/scriptPARSER_PATH=/pkg/parserPARTITIONS_PATH=/pkg/partitionsQOS_PATH=/pkg/qosSCHEMA_PATH=/pkg/schemaSTARTUP_PATH=/pkg/startupTCL_LIBRARY=/pkg/lib/tclUCODE_PATH=/pkg/gsr/ucodeUCODE_ROOT_PATH=/pkg/ucodeVCM_RULES_PATH=/pkg/vcmrulesJOB_ID=0INSTANCE_ID=1SYSMGR_TUPLE=SYSMGR_NODE=node0_RSP0_CPU0EXIT_STATUS=0SYSMGR_RESTART_REASON=0AAA_USER=labuserEXEC_PID=18280619TASKID_MAP_SIZE=72HOME=/disk0:/usrTMPDIR=/disk0:/var/tmpPWD=/disk0:/usr



Displays the configuration register setting and boot file setting for the RSPsin the system.

show variables boot

Displays the configuration of the system hardware, the software version,the names and sources of configuration files, and the boot images.

show version


Boot Commands on the Cisco ASR 9000 Series Routershow variables system

system boot-sequenceTo define the order of local storage devices used to boot a router, use the system boot-sequence commandin EXEC or administration EXEC mode.

system boot-sequence {primary-device [ secondary-device ]| disable} [location {node-id| all}]

Syntax Description Default device where software packages are installed and run. This device is alsothe default location for router configurations. The value of the primary-deviceargument is normally disk0:.

primary-device

(Optional) Secondary (backup) boot device, used by the system backup commandto back up system software and configurations. Supported storage devices are:

disk0:

disk1: (if installed)

compactflash: (if installed)

The value of the secondary-device argument must be different from thevalue of the primary-device argument.

Note

secondary-device

Temporarily disables the automatic recovery mechanism.disable

(Optional) Specifies the node of the RSP for which to define the boot sequence.The node-id argument is expressed in the rack/slot/module notation. The all keywordspecifies all RSP nodes.


Command Default The primary device is disk0:. The (optional) secondary boot device is not defined.

Command Modes EXEC

Administration EXEC





Boot Commands on the Cisco ASR 9000 Series Routersystem boot-sequence

Use the system boot-sequence command to define the local storage devices used to boot a router. You candefine two devices with this command.

The value of the primary-device argument defines the default device where software packages areinstalled and run. This device is also the default location for router configurations.

The value of the secondary-device argument defines the device used by the system backup commandto back up system software and configurations. This field is optional.

The secondary device can also be temporarily defined when the system backup command is executedwith the target-device argument. Use the system boot-sequence command with the secondary-deviceargument to permanently define the secondary (backup) device.

The system backup command is not supported on all platforms.Note

The primary and secondary device definitions remain in effect until the system boot-sequence commandis entered again.

Note

General Guidelines

The value of the secondary-device argument must be different from the value of the primary-deviceargument.

We recommend disk0: as the primary boot device in the boot sequence, and disk1: as the secondary bootdevice.

The boot device specified with the system boot-sequence command must be installed in the card or thecommand is rejected.

Command Mode Options

Use the system boot-sequence command in administration EXEC mode to define the boot sequencefor the system.

Use the system boot-sequence command in EXEC mode to define the boot sequence for a specificSDR.

Location Node

Use the location node-id keyword and argument to define the boot sequence for a specific route switchprocessor (RSP).

Use the location all keywords to define the boot sequence for all RSPs in the router.

Disabling Automatic Recovery

Use the system boot-sequence command with the disable keyword to disable the automatic recovery.

Displaying the Current Boot Sequence Settings

Enter the show system backup command to display the currently configured boot sequence devices.




read, writeroot-lr

Examples The following example shows how to define the primary and secondary boot device for the active RSP (DSC).In this example, the default location for software and configurations is disk0:. The location for backups ofsoftware and configurations is disk1:.

RP/0/RSP0/CPU0:router# adminRP/0/RSP0/CPU0:router(admin)# system boot-sequence disk0: disk1:

Info: node0_0_CPU0: command succeeded.



Bulk Content Downloader (BCDL) Commands onthe Cisco ASR 9000 Series Router

This module describes the show commands that you can use to see the status of the Bulk Content Downloader(BCDL) process. The BCDL provides the Cisco IOS XR software with high-performance downloadingcapabilities. This capability is used by the following internal applications:

IPv4 and IPv6 unicast routing protocolsTo provide the ability to download forwarding informationfrom the router Global Routing Information Base (GRIB) to the line cards.

IPv4 and IPv6 multicast routing protocolsTo download the Multicast Routing Information Base(MRIB) entries to consumers managing the Multicast Forwarding Information Base (MFIB) on thevarious line cards.

MPLSTo download the Label Forwarding Information Base (LFIB) entries to the line card.

Fabric ManagementTo update memberships for individual fabric group IDs (FGIDs) to selectedportions of the fabric hardware.

CDSContext Distribution Service.

There is no configuration necessary for the BCDL.

show bcdl, page 36

show bcdl consumers, page 39

show bcdl queues, page 41

show bcdl tables, page 43

show bcdl trace, page 45


show bcdlTo display Bulk Content Downloader (BCDL) information, use the show bcdl command in EXEC mode.

show bcdl [ group_name ]

Syntax Description (Optional) Displays information for a specific BCDL group.group_name


Command Modes EXEC





readsysmgr

Examples The following example shows sample output from the show bcdl command:

RP/0/RSP0/CPU0:router# show bcdl ipv4_rib

Sun May 31 06:56:12.093 PSTgrp ipv4_rib, gid 2040, sg cnt 1, agent jid 124, node 0/RSP0/CPU0, pulse 105,new mbr 0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2043 11 4 no no no 0 113 103 0


Bulk Content Downloader (BCDL) Commands on the Cisco ASR 9000 Series Routershow bcdl

Table 4: show bcdl Field Descriptions

DescriptionField

Type of download and the Group Services Protocol(GSP) group name.

group

Heavyweight group (HWG) in the GSP. This is thegroup that a consumer initially joins. It is used by theBCDL agent to send control updates.

gid

Number of subgroups for this particular downloadtype.

sg count

Job identifier of the BCDL agent. The JID isnumerical identifier for a particular process andremains the same across process restarts.

agent jid

Node, expressed in the rack/slot/module notation, inwhich the agent is running.

node

Pulse code used by the producer to pulse the BCDLagent.

pulse

Number of new consumers that have not yet beenassigned a subgroup.

new mbr

Subgroups number.sg

Lightweight group in GSP. This is a type of childgroup of the HWG. The BCDL agent tells theconsumers to join this group to receive data.

lwg

The connection handle between the producer and theBCDL agent.

fd

Number of consumers.csmr

Specifies if there is a download in progress.hdlr-act

Indicates whether the convergence flag has been sentor not.

dnld-act

Indicates whether the download is suspended due tothe queue filling up.

susp

If nonzero, some thread is waiting for other thread totake control of this subgroup.

wait-lck

Sequence number of the last message sent on thissubgroup.

seq



DescriptionField

Total number of pulses sent by the producer to theBCDL agent.

pulse-tot

Total number of outstanding pulses that have not yetbeen processed by the BCDL agent.

pulse-out



show bcdl consumersTo display Bulk Content Downloader (BCDL) consumer information, use the show bcdl consumers commandin EXEC mode.

show bcdl consumers [ group_name ]



Command Modes EXEC





readsysmgr

Examples The following example shows sample output using the show bcdl consumers command:

RP/0/RSP0/CPU0:router# show bcdl consumers ipv4_rib

Sun May 31 06:17:38.209 PSTgroup ipv4_rib, gsp gid 2040, 4 consumers, agent jid 124, node 0/RSP0/CPU0(expected 4 consumers to reply, received 4 replies)

pid node asg csg lwg sus messages bytes errs name323727 0/RSP0/CPU0 0 0 2043 N 113 54196 0 fib_mgr110686 0/6/CPU0 0 0 2043 N 111 54140 0 fib_mgr110686 0/4/CPU0 0 0 2043 N 112 54168 0 fib_mgr110686 0/1/CPU0 0 0 2043 N 111 54140 0 fib_mgr

This table describes the significant fields shown in the display that are not described in Table 4: show bcdlField Descriptions, on page 37.


Bulk Content Downloader (BCDL) Commands on the Cisco ASR 9000 Series Routershow bcdl consumers

Table 5: show bcdl consumers Field Descriptions

DescriptionField

Process identifier.PID

Consumer node, expressed in the rack/slot/modulenotation.

node

Subgroup to which the BCDL agent thinks thisconsumer belongs.

asg

Subgroup to which the consumer thinks it belongs.csg

Number of messages processed by this particularconsumer.

messages

Bytes processed by this particular consumer.bytes

Errors encountered by the consumer. This fieldindicates the number of times the connection wasreset.

errors

Name of the consumer process.name


Bulk Content Downloader (BCDL) Commands on the Cisco ASR 9000 Series Routershow bcdl consumers

show bcdl queuesTo display the Bulk Content Downloader (BCDL) queue information, use the show bcdl queues commandin EXEC mode.

show bcdl queues [ group_name ]



Command Modes EXEC





readsysmgr

Examples The following example shows sample output from the show bcdl queues command:

RP/0/RSP0/CPU0:router# show bcdl queues ipv4_rib

Sun May 31 07:13:28.665 PSTgroup ipv4_rib, gsp gid 2040, 4 consumers, agent jid 124, node 0/RSP0/CPU0(expected 4 consumers to reply, received 4 replies)

pid node asg csg lwg sus msgs_in_q bytes_in_q errs name323727 0/RSP0/CPU0 0 0 2043 N 0 0 0 fib_mgr110686 0/6/CPU0 0 0 2043 N 0 0 0 fib_mgr110686 0/1/CPU0 0 0 2043 N 0 0 0 fib_mgr110686 0/4/CPU0 0 0 2043 N 0 0 0 fib_mgr


Bulk Content Downloader (BCDL) Commands on the Cisco ASR 9000 Series Routershow bcdl queues

Table 4: show bcdl Field Descriptions, on page 37 and Table 5: show bcdl consumers Field Descriptions,on page 39 describe the significant fields shown in the display.


Bulk Content Downloader (BCDL) Commands on the Cisco ASR 9000 Series Routershow bcdl queues

show bcdl tablesTo display Bulk Content Downloader (BCDL) table information, use the show bcdl tables command in EXECmode.

show bcdl tables [ group_name ]

Syntax Description Displays information for a specific BCDL group.group_name


Command Modes EXEC





readsysmgr

Examples The following example shows sample output using the show bcdl tables command:

RP/0/RSP0/CPU0:router# show bcdl tables ipv4_rib

Sun May 31 07:19:29.878 PSTgrp ipv4_rib, gid 2040, sg cnt 1, agent jid 124, node 0/RSP0/CPU0, pulse 105, new mbr 0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2043 11 4 no no no 0 113 103 0

sgs: 1, table_cnt: 1, table_mid_cnt: 4, buf size: 100Showing table info for 1 subgroupssg 0: has 1 tables (messages: 0, bytes: 0)table 0xe0000000: 4 members, dnld act: 0, messages: 113, bytes: 54196cnsmr 0: pid 323727 on node 0/RSP0/CPU0cnsmr 1: pid 110686 on node 0/6/CPU0cnsmr 2: pid 110686 on node 0/1/CPU0


Bulk Content Downloader (BCDL) Commands on the Cisco ASR 9000 Series Routershow bcdl tables

cnsmr 3: pid 110686 on node 0/4/CPU0

The significant fields shown in the display that are not described in Table 4: show bcdl Field Descriptions,on page 37 or Table 5: show bcdl consumers Field Descriptions, on page 39 are described in this table.

Table 6: show bcdl tables Field Descriptions

DescriptionField

Number of subgroups.sgs

Number of tables in this subgroup.table_cnt

Specific subgroup for which information is provided.sg

Number of tables in this subgroup.has 1 tables

Messages sent that are not associated with a particulartable ID.

messages

Bytes sent that are not associated with a particulartable ID.

bytes

Specific table ID for which information is provided.table

Number of consumers associated with this table.members

Indicates whether or not the convergence flag hasbeen sent.

dnld act

Number of messages sent for a particular table.messages

Number of bytes sent for a particular table.bytes

Process ID and node information for each consumerin the specified table.

cnsmr 0: pid 419725 on node 0/RP0/CPU0


Bulk Content Downloader (BCDL) Commands on the Cisco ASR 9000 Series Routershow bcdl tables

show bcdl traceTo display Bulk Content Downloader (BCDL) trace information, use the show bcdl trace command in EXECmode.

show bcdl trace [ group_name ] [event] [timing] [grpsnd] [wrapping| unique] [hexdump] [last n] [reverse][stats] [tailf] [verbose] [file filename original location node-id| location {node-id| all}]


(Optional) Displays event trace entries.event

(Optional) Displays timing trace entries.timing

(Optional) Displays group send trace entries.grpsnd

(Optional) Displays wrapping entries.wrapping

(Optional) Displays unique entries only, along with the count of the numberof times this entry appears.

unique

(Optional) Displays traces in hexadecimal format.hexdump

(Optional) Displays the last n number of traces only.last n

(Optional) Displays the most recent traces first.reverse

(Optional) Displays execution path statistics.stats

(Optional) Displays new traces as they are added.tailf

(Optional) Displays additional internal debugging information.verbose

(Optional) Specifies a filename and original location of the file to display.file filename original locationnode-id

Specifies the RP node for which to display the execution path monitoringinformation. The node-id argument is expressed in the rack/slot/modulenotation. The all keyword specifies all RP nodes.



Command Modes EXEC


Bulk Content Downloader (BCDL) Commands on the Cisco ASR 9000 Series Routershow bcdl trace





readsysmgr

Examples The following example shows sample output using the show bcdl trace command:

RP/0/RSP0/CPU0:router# show bcdl trace ipv4_rib location 0/1/cpu0

Sun May 31 08:21:07.933 PST143 wrapping entries (4096 possible, 0 filtered, 143 total)May 21 15:14:55.790 bcdl/c/ipv4_rib 0/1/CPU0 t4 LEbcdl_join_internal: timer_create ret 0, id is 9

May 21 15:14:56.890 bcdl/c/ipv4_rib 0/1/CPU0 t7 LEbcdl_join_internal: group_lookup bcdl_ipv4_ribreturned gid 2040

May 21 15:14:56.966 bcdl/c/ipv4_rib 0/1/CPU0 t7 LEjoin hwg 2040 returns 0

May 21 15:14:56.978 bcdl/c/ipv4_rib 0/1/CPU0 t7 LEbcdl_join_internal: joined group bcdl_ipv4_rib,member count 5

May 21 15:14:58.969 bcdl/c/ipv4_rib 0/1/CPU0 t7 LErcv gsp mtype 3: connection init sg 1 cur_seq 0lwg_gid 2056 table tag 0x00000000 resend state yes

May 21 15:14:58.969 bcdl/c/ipv4_rib 0/1/CPU0 t7 LEpc ring high water 0 -> 1, 0 bytes

May 21 15:14:58.969 bcdl/c/ipv4_rib 0/1/CPU0 t4 LEc_h deliver msg_id 7 connection init, table event0 table tag 0x00000000

May 21 15:14:58.969 bcdl/c/ipv4_rib 0/1/CPU0 t4 LEconn init, seq 64206 -> 0, sg 65534 -> 1, gid 2040,lwg gid -1 -> 2056...


Bulk Content Downloader (BCDL) Commands on the Cisco ASR 9000 Series Routershow bcdl trace

CDP Commands on the Cisco ASR 9000 SeriesRouter

This module describes the Cisco IOS XR software commands for monitoring the networking device andnetwork using Cisco Discovery Protocol (CDP).

For detailed information about CDP concepts, configuration tasks, and examples, see the Implementing CDPon Cisco IOS XR Software module in Cisco ASR 9000 Series Aggregation Services Router SystemManagement Configuration Guide.

cdp, page 48

cdp advertise v1, page 50

cdp holdtime, page 52

cdp log adjacency changes, page 54

cdp timer, page 56

clear cdp counters, page 58

clear cdp table, page 60

show cdp, page 62

show cdp entry, page 64

show cdp interface, page 67

show cdp neighbors, page 70

show cdp traffic, page 74


cdpTo enable the Cisco Discovery Protocol (CDP) globally or on an interface, use the cdp command in theappropriate configuration mode. To disable CDP globally or on an interface, use the no form of this command.

cdp

no cdp


Command Default CDP is disabled.


Interface configuration




By default, CDP is disabled globally. To enable CDP, CDP must be enabled globally and then enabled foreach interface.

To enable CDP globally, use the cdp command in global configuration mode. To disable CDP globally, usethe no form of this command in global configuration mode.

To enable CDP on a specific interface, use the cdp command in interface configuration mode. To disableCDP on a specific interface, use the no form of this command in interface configuration mode.


read, writecdp

Examples The following example shows how to globally enable CDP:

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


CDP Commands on the Cisco ASR 9000 Series Routercdp

The following example shows how to enable CDP on an interface:

RP/0/RSP0/CPU0:router(config)# interface gigabitethernet 0/0/0/1RP/0/RSP0/CPU0:router(config-if)# cdp

The following example shows how to disable CDP on an interface:

RP/0/RSP0/CPU0:router(config)# interface gigabitethernet 0/0/0/1RP/0/RSP0/CPU0:router(config-if)# no cdp


Displays global Cisco Discovery Protocol information, including CDP version,timer, and holdtime information.

show cdp


CDP Commands on the Cisco ASR 9000 Series Routercdp

cdp advertise v1To change the version of Cisco Discovery Protocol (CDP) that is used to communicate with neighboringdevices to version 1 (CDPv1), use the cdp advertise v1 command in global configuration mode. To removethe cdp advertise v1 command from the configuration file and restore the system to its default conditionwith respect to this command, use the no form of this command.

cdp advertise v1

no cdp advertise [v1]


Command Default Version 2 is enabled.





CDPv2 packets are sent by default. CDP also sends and receives CDPv1 packets if the device with whichCDP is interacting does not process CDPv2 packets.

CDPv2 adds device information over CDPv1. The additional information that is contained in the CDPv2messages relates to Native VLAN, VLAN Trunking Protocol (VTP) Management Domain, Ethernet Duplex,and other features.


read, writecdp

Examples The following example shows how to set a networking device to send and receive only CDPv1 advertisements:

RP/0/RSP0/CPU0:router(config)# cdp advertise v1


CDP Commands on the Cisco ASR 9000 Series Routercdp advertise v1

The following example shows how to restore the default condition (sending and receiving CDPv2advertisements):

RP/0/RSP0/CPU0:router(config)# no cdp advertise


Enables the Cisco Discovery Protocol globally or on an interface.cdp


show cdp


CDP Commands on the Cisco ASR 9000 Series Routercdp advertise v1

cdp holdtimeTo specify the time for which the receiving device should hold a Cisco Discovery Protocol (CDP) packetfrom your networking device before discarding it, use the cdp holdtime command in global configurationmode. To remove the cdp holdtime command from the configuration file and restore the system to its defaultcondition with respect to this command, use the no form of this command.

cdp holdtime seconds

no cdp holdtime

Syntax Description Holdtime to be sent in the CDP update packets, in seconds. Range is 10 to255.

seconds

Command Default seconds : 180





CDP packets are sent with a time-to-live value or holdtime, that is nonzero after an interface is enabled.

The CDP holdtime must be set to a higher number of seconds than the time between CDP transmissions,which is set using the cdp time command.


read, writecdp

Examples The following example shows how to specify that the CDP packets sent from the networking device are heldby the receiving device for 60 seconds before being discarded. You might want to set the holdtime lower than


CDP Commands on the Cisco ASR 9000 Series Routercdp holdtime

the default setting of 180 seconds if information about your networking device changes often and you wantthe receiving devices to purge this information more quickly.

RP/0/RSP0/CPU0:router(config)# cdp holdtime 60


Specifies how often the software sends Cisco Discovery Protocol updates.cdp timer


show cdp


CDP Commands on the Cisco ASR 9000 Series Routercdp holdtime

cdp log adjacency changesTo log changes to the Cisco Discovery Protocol (CDP) adjacency table, use the cdp log adjacency changescommand in global configuration mode. To disable the logging, use the no form of this command.

cdp log adjacency changes

no cdp log adjacency changes


Command Default CDP adjacency table logging is disabled.





When CDP adjacency table logging is enabled, a syslog is generated each time a CDP neighbor is added orremoved.


read, writecdp

Examples The following example shows how to enable CDP adjacency table logging:

RP/0/RSP0/CPU0:router# configureRP/0/RSP0/CPU0:router(config)# cdp log adjacency changes

When CDP adjacency table logging is enabled, a syslog is generated each time a CDP neighbor is added orremoved. The following is an example of the log entry:

LC/0/5/CPU0:Jun 5 10:51:18.081 : cdp[109]: %L2-CDP-6-DELETED_NEIGHBOR :CDP Neighbour TBA04110127 on interface GigabitEthernet0/5/0/0has been deleted, remote interface 3/2

LC/0/5/CPU0:Jun 5 10:51:33.120 : cdp[109]: %L2-CDP-6-NEW_NEIGHBOR :


CDP Commands on the Cisco ASR 9000 Series Routercdp log adjacency changes

New CDP neighbor TBA04110127 detected on interface GigabitEthernet0/5/0/0,remote interface 3/2



show cdp


CDP Commands on the Cisco ASR 9000 Series Routercdp log adjacency changes

cdp timerTo specify how often the software sends Cisco Discovery Protocol (CDP) updates, use the cdp timercommand in global configuration mode. To remove the cdp timer global configuration command from theconfiguration file and restore the system to its default condition with respect to this command, use the noform of this command.

cdp timer seconds

no cdp timer

Syntax Description Frequency with which the Cisco IOS XR software sends CDP updates, in seconds.Range is 5 to 254. The default is 60.

seconds

Command Default seconds : 60





A lower timer setting causes CDP updates to be sent more frequently.


read, writecdp

Examples The following example shows how to set the CDP timer to 80 seconds, which is less frequent than the defaultsetting of 60 seconds:

RP/0/RSP0/CPU0:router(config)# cdp timer 80


CDP Commands on the Cisco ASR 9000 Series Routercdp timer


Specifies the time for which the receiving device should hold a Cisco DiscoveryProtocol.

cdp holdtime


show cdp


CDP Commands on the Cisco ASR 9000 Series Routercdp timer

clear cdp countersTo reset Cisco Discovery Protocol (CDP) traffic counters to zero (0), use the clear cdp counters commandin EXEC mode.

clear cdp counters location node-id

Syntax Description Clears CDP traffic counters for the designated node. The node-id argumentis entered in the rack/slot/module notation.

location node-id

Command Default The counters are set to zero.

Command Modes EXEC





read, writecdp

Examples The following example shows how to clear CDP counters. The show cdp traffic output shows that all trafficcounters have been reset to zero (0).

RP/0/RSP0/CPU0:router# clear cdp countersRP/0/RSP0/CPU0:router# show cdp traffic

CDP counters:Packets output: 0, Input: 0Hdr syntax: 0, Chksum error: 0, Encaps failed: 0No memory: 0, Invalid packet: 0, Truncated: 0CDP version 1 advertisements output: 0, Input: 0CDP version 2 advertisements output: 0, Input: 0Unrecognize Hdr version: 0, File open failed: 0


CDP Commands on the Cisco ASR 9000 Series Routerclear cdp counters


Clears and automatically resizes the table that contains Cisco DiscoveryProtocol information about neighbors.

clear cdp table

Displays information about the traffic gathered between devices using CiscoDiscovery Protocol.

show cdp traffic


CDP Commands on the Cisco ASR 9000 Series Routerclear cdp counters

clear cdp tableTo clear and automatically resize the table that contains Cisco Discovery Protocol (CDP) information aboutneighbors, use the clear cdp table command in EXEC mode.

clear cdp table location node-id

Syntax Description Clears and resizes the CDP table for the designated node. The node-id argumentis entered in the rack/slot/module notation.

location node-id


Command Modes EXEC




Use the clear cdp table command to clear and resize the CDP table that contains the neighbor entries. Thenew table size is calculated according to the recommended hash table size, as seen in the show cdp commandoutput.


read, writecdp

Examples The following example shows how to clear and resize the CDP table. The output of the show cdp neighborscommand before and after use of the clear cdp table command shows that all information has been deletedfrom the table:

RP/0/RSP0/CPU0:router# show cdp neighbors

Capability Codes: R - Router, T - Trans Bridge, B - Source Route BridgeS - Switch, H - Host, I - IGMP, r - Repeater

Device ID Local Intrfce Holdtme Capability Platform Port ID


CDP Commands on the Cisco ASR 9000 Series Routerclear cdp table

TBA04341195(15la Mg0/RP1/CPU0/0 171 T S WS-C2924 0/1

RP/0/RSP0/CPU0:router# clear cdp tableRP/0/RSP0/CPU0:router# show cdp neighbors

Capability Codes: R - Router, T - Trans Bridge, B - Source Route BridgeS - Switch, H - Host, I - IGMP, r - Repeater

Device ID Local Intrfce Holdtme Capability Platform Port ID

The show cdp command shows that the table has been resized:

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

Global CDP information:Sending CDP packets every 60 secondsSending a holdtime value of 180 secondsSending CDPv2 advertisements is enabled


Displays global CiscoDiscovery Protocol information, including CDP version,timer, and holdtime information.

show cdp

Displays detailed information about neighboring devices discovered usingCisco Discovery Protocol.

show cdp neighbors


CDP Commands on the Cisco ASR 9000 Series Routerclear cdp table

show cdpTo display global Cisco Discovery Protocol (CDP) information, including CDP version, timer, and holdtimeinformation, use the show cdp command in EXEC mode.

show cdp



Command Modes EXEC

ModificationRelease


No modification.Release 3.9.0


Use the show cdp command to display CDP version, timer, and holdtime information relative to CDPoperations.


readcdp

Examples The following example shows how to use the show cdp command to verify the CDP global settings:

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

Global CDP information:Sending CDP packets every 20 secondsSending a holdtime value of 30 secondsSending CDPv2 advertisements is not enabled


CDP Commands on the Cisco ASR 9000 Series Routershow cdp

Table 7: show cdp Field Descriptions

DefinitionField

Interval between transmissions of CDPadvertisements. This field is controlled by the cdptimer command.

Sending CDP packets every 20 seconds

Time for which the device directs the neighbor tohold a CDP advertisement before discarding it. Thisfield is controlled by the cdp holdtime command.

Sending a holdtime value of 30 seconds

State of being enabled or disabled for the transmissionof CDP version 2-type advertisements. This field iscontrolled by the cdp advertise v1 command.

Sending CDPv2 advertisements is not enabled


Changes the version of Cisco Discovery Protocol that is used to communicatewith neighboring devices to version 1.

cdp advertise v1

Specifies the time for which the receiving device should hold a CiscoDiscoveryProtocol.

cdp holdtime

Specifies how often the software sends Cisco Discovery Protocol updates.cdp timer

Clears and automatically resizes the table that contains Cisco DiscoveryProtocol information about neighbors.

clear cdp table

Displays information about a specific neighboring dev

Documents

ASR 9000 Series_Command Reference