ar38book

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Cisco IOS XR Advanced System Command Reference Cisco IOS XR Software Release 3.8

Text Part Number: OL-17332-01

http://www.cisco.com

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 LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE 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 version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, 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 OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

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

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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 partnership relationship between Cisco and any other company. (1005R)

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 shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Cisco IOS XR Advanced System Command Reference © 2009 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

AR-iiiCisco IOS XR Advanced System Command Reference

OL-17332-01

Preface

This chapter describes the commands used to troubleshoot a router using Cisco IOS XR software.

This chapter contains the following sections:

• Changes to This Document, page iii

• Obtaining Documentation and Submitting a Service Request, page iii

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

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

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

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

Table 1 Changes to This Document

Revision Date Change Summary

OL-17332-01 March 2009 Initial release of this document.

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

Preface

AR-ivCisco IOS XR Advanced System Command Reference

OL-17332-01

AR-1Cisco IOS XR Advanced System Command Reference

OL-17332-01

ASIC Driver Commands on Cisco IOS XR Software

This module describes the commands used to configure and monitor the application-specific integrated circuit (ASIC) driver on a router running Cisco IOS XR software.

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan egressq (block number)


OL-17332-01

asic-scan egressq (block number)To run, enable, or disable a generic ASIC scan on a specific egress queue ASIC block ID or error cause, use the asic-scan egressq command in EXEC mode.

asic-scan egressq block_number [[error_cause] [disable | enable] | help-cause] location node-id

Syntax Description

Defaults No default behavior or values

Command Modes EXEC

Command History

Usage Guidelines To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.

block_number Identifies the block on which to enable or disable the ASIC scan.

error_cause (Optional) Identifies an error cause in the specified block. When you include the error_cause argument in the asic-scan egressq command syntax, the command takes place on the specified error cause.

disable (Optional) Disables the ASIC scan on the specified block or error cause.

enable (Optional) Enables the ASIC scan on the specified block or error cause.

help_cause (Optional) Displays a list of all error causes in the specified block.

location node-id Identifies the location of the node hosting the egress queue on which to run, enable, or disable an ASIC scan. The node-id argument is expressed in the rack/slot/module notation.

Note Use the show platform command to see the location of all nodes installed in the router.

Release Modification

Release 3.5.0 This command was introduced on the Cisco CRS-1.

Release 3.6.0 Note was added in the Usage Guidelines section that this command can adversely affect the router operation.

Release 3.7.0 No modification.


ASIC Driver Commands on Cisco IOS XR Softwareasic-scan egressq (block number)


OL-17332-01

Note This command should be used only with Cisco support supervision. Incorrect usage of this command can accidentally remove the relevant card from service.

Task ID

Examples The following example shows how to display a list of all error causes in the specified block:

RP/0/RP0/CPU0:router# asic-scan egressq 10 help-cause location 0/6/CPU0

Total 6 cause(s)

Cause Number Cause Name 0 lbm_owl_ovl 1 scr_m4_ovl 2 scr_m3_ovl 3 scr_m2_ovl 4 scr_m1_ovl 5 scr_m0_ovl

The following example shows how to run a scan on the egress queue ASIC block ID 30 located on the CPU node in slot 1:

RP/0/RP0/CPU0:router# asic-scan egressq 30 location 0/6/CPU0

Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan egressq disable


OL-17332-01

asic-scan egressq disableTo disable an ASIC scan on all causes in all blocks on the specified node, use the asic-scan egressq disable command in EXEC mode.

asic-scan egressq disable location node-id

Syntax Description


Command Modes EXEC

Command History



Task ID

location node-id Identifies the location of the node on which to disable the ASIC scan. The node-id argument is expressed in the rack/slot/module notation.







Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan egressq disable


OL-17332-01

Examples The following example shows how to disable an ASIC scan on all causes in all blocks on the egress queue that is located on the CPU node in slot 6:

RP/0/RP0/CPU0:router# asic-scan egressq disable location 0/6/CPU0

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan egressq enable


OL-17332-01

asic-scan egressq enableTo enable an ASIC scan on all causes in all blocks on the specified node, use the asic-scan egressq enable command in EXEC mode.

asic-scan egressq enable location node-id

Syntax Description


Command Modes EXEC

Command History



location node-id Identifies the location of the node on which to enable the ASIC scan. The node-id argument is expressed in the rack/slot/module notation.







ASIC Driver Commands on Cisco IOS XR Softwareasic-scan egressq enable


OL-17332-01

Task ID

Examples The following example shows how to enable an ASIC scan on all causes in all blocks on the egress queue that is located on the CPU node in slot 6:

RP/0/RP0/CPU0:router# asic-scan egressq enable location 0/6/CPU0

Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan egressq help-block


OL-17332-01

asic-scan egressq help-blockTo enable an ASIC scan that lists all the blocks on the specified node, use the asic-scan egressq help-block command in EXEC mode.

asic-scan egressq help-block location node-id

Syntax Description


Command Modes EXEC

Command History



Task ID

location node-id Identifies the location of the node on which to enable the ASIC scan. The node-id argument is expressed in the rack/slot/module notation.






Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan egressq help-block


OL-17332-01

Examples The following example shows how to enable an ASIC scan that lists all block numbers on the egress queue that is located on the CPU node in slot 6:

RP/0/RP0/CPU0:router# asic-scan egressq help-block location 0/6/CPU0

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan egressq location


OL-17332-01

asic-scan egressq locationTo run an ASIC scan on all the egress queues on a specific node, use the asic-scan egressq location command in EXEC mode.

asic-scan egressq location node-id

Syntax Description


Command Modes EXEC

Command History



Task ID

location node-id Identifies the location of the node hosting the egress queues on which to run the ASIC scan. The node-id argument is expressed in the rack/slot/module notation.







Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan egressq location


OL-17332-01

Examples The following example shows how to run an ASIC scan on all egress queues located on the CPU node in slot 1:

RP/0/RP0/CPU0:router# asic-scan egressq location 0/1/CPU0

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan egressq quick-scan


OL-17332-01

asic-scan egressq quick-scanTo run a quick ASIC scan on a specific file or on all bits of the chip, use the asic-scan egressq quick-scan command in EXEC mode.

asic-scan egressq quick-scan {filename | allscan} location node-id

Syntax Description


Command Modes EXEC

Command History



Task ID

filename Name of the .xsvf file on which to run the quick ASIC scan

allscan Performs a quick ASIC scan on all bits of the chip, including the preread for Metro.

location node-id Identifies the location of the node hosting the egress queue on which to run the ASIC scan. The node-id argument is expressed in the rack/slot/module notation.







Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan egressq quick-scan


OL-17332-01

Examples The following example shows how to run a quick ASIC scan on all bits of the chip on the egress queue that is located on the CPU node in slot 1:

RP/0/RP0/CPU0:router# asic-scan egressq quick-scan allscan location 0/1/CPU0

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse egress (block number)


OL-17332-01

asic-scan pse egress (block number)To run, enable, or disable a generic ASIC scan on a specific egress packet switching engine (PSE) device block or error cause, use the asic-scan pse egress command in EXEC mode.

asic-scan pse egress block_number [[error_cause] [disable | enable] | help-cause] location node-id

Syntax Description


Command Modes EXEC

Command History


error_cause (Optional) Identifies an error cause in the specified block. When you include the error_cause argument in the asic-scan pse egress command syntax, the command takes place on the specified error cause.



help_cause (Optional) Displays a list of all error causes in the specified block.

location node-id Identifies the location of the node hosting the egress PSE device on which to run, enable, or disable an ASIC scan. The node-id argument is expressed in the rack/slot/module notation.



Release 2.0 This command was introduced on the Cisco CRS-1.

Release 3.0 No modification.








ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse egress (block number)


OL-17332-01



Task ID

Examples The following example shows how to display a list of all error causes in the specified block of a PSE device:

RP/0/RP0/CPU0:router# asic-scan pse egress 10 help-cause location 0/6/CPU0

Total 6 cause(s)


The following example shows how to run a scan on the PSE ASIC block ID 30 located on the CPU node in slot 1:

RP/0/RP0/CPU0:router# asic-scan pse egress 30 location 0/6/CPU0

Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse egress disable


OL-17332-01

asic-scan pse egress disableTo disable an ASIC scan on all causes in all blocks of a specific packet switching engine (PSE) device, use the asic-scan pse egress disable command in EXEC mode.

asic-scan pse egress disable location node-id

Syntax Description


Command Modes EXEC

Command History















ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse egress disable


OL-17332-01

Task ID

Examples The following example shows how to disable an ASIC scan on all causes in all blocks of the egress PSE device that is located on the CPU node in slot 6:

RP/0/RP0/CPU0:router# asic-scan pse egress disable location 0/6/CPU0

Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse egress enable


OL-17332-01

asic-scan pse egress enableTo enable an ASIC scan on all causes in all blocks of a specific egress packet switching engine (PSE) device, use the asic-scan pse egress enable command in EXEC mode.

asic-scan pse egress enable location node-id

Syntax Description


Command Modes EXEC

Command History



location node-id Identifies the location of the node that hosts the egress PSE on which to enable the ASIC scan. The node-id argument is expressed in the rack/slot/module notation.












ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse egress enable


OL-17332-01

Task ID

Examples The following example shows how to enable an ASIC scan on all causes in all blocks on the egress PSE that is located on the CPU node in slot 6:

RP/0/RP0/CPU0:router# asic-scan pse egress enable location 0/6/CPU0

Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse egress help-block


OL-17332-01

asic-scan pse egress help-blockTo enable an ASIC scan that lists all block numbers of a specific egress packet switching engine (PSE) device, use the asic-scan pse egress help-block command in EXEC mode.

asic-scan pse egress help-block location node-id

Syntax Description


Command Modes EXEC

Command History



Task ID

Examples The following example shows how to enable an ASIC scan that lists all block numbers on the egress PSE that is located on the CPU node in slot 6:

RP/0/RP0/CPU0:router# asic-scan pse egress help-block location 0/6/CPU0

location node-id Identifies the location of the node that hosts the egress PSE on which to enable the ASIC scan. The node-id argument is expressed in the rack/slot/module notation.






Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse egress location


OL-17332-01

asic-scan pse egress locationTo run an ASIC scan on a specific packet switching engine (PSE) device, use the asic-scan pse egress location command in EXEC mode.

asic-scan pse egress location node-id

Syntax Description


Command Modes EXEC

Command History



location node-id Identifies the location of the node hosting the PSE on which to run the ASIC scan. The node-id argument is expressed in the rack/slot/module notation.












ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse egress location


OL-17332-01

Task ID

Examples The following example shows how to run an ASIC scan on all egress PSE located on the CPU node in slot 1:

RP/0/RP0/CPU0:router# asic-scan pse egress location 0/1/CPU0

Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse egress quick-scan


OL-17332-01

asic-scan pse egress quick-scanTo run a quick ASIC scan on a specific file or on all bits of the chip located on a specific packet switching engine (PSE) device, use the asic-scan pse egress quick-scan command in EXEC mode.

asic-scan pse egress quick-scan {filename | allscan} location node-id

Syntax Description


Command Modes EXEC

Command History





location node-id Identifies the location of the node hosting the egress PSE on which to run the ASIC scan. The node-id argument is expressed in the rack/slot/module notation.












ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse egress quick-scan


OL-17332-01

Task ID

Examples The following example shows how to run a quick ASIC scan on all bits of the chip on the egress PSE device that is located on the CPU node in slot 1:

RP/0/RP0/CPU0:router# asic-scan pse egress quick-scan allscan location 0/1/CPU0

Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse ingress (block number)


OL-17332-01

asic-scan pse ingress (block number)To run, enable, or disable a generic ASIC scan on a specific ingress packet switching engine (PSE) device block or error cause, use the asic-scan pse ingress command in EXEC mode.

asic-scan pse ingress block_number [[error_cause] [disable | enable] | help-cause] location node-id

Syntax Description


Command Modes EXEC

Command History


error_cause (Optional) Identifies an error cause in the specified block. When you include the error_cause argument in the asic-scan pse ingress command syntax, the command takes place on the specified error cause.



help-cause (Optional) Displays a list of all error causes in the specified block.

location node-id Identifies the location of the node hosting the ingress PSE device on which to run, enable, or disable an ASIC scan. The node-id argument is expressed in the rack/slot/module notation.












ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse ingress (block number)


OL-17332-01



Task ID

Examples The following example shows how to display a list of all error causes in the specified block of a PSE device:

RP/0/RP0/CPU0:router# asic-scan pse ingress 10 help-cause location 0/6/CPU0

Total 6 cause(s)


The following example shows how to run a scan on the PSE ASIC block ID 30 located on the CPU node in slot 1:

RP/0/RP0/CPU0:router# asic-scan pse ingress 30 location 0/6/CPU0

Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse ingress disable


OL-17332-01

asic-scan pse ingress disableTo disable an ASIC scan on all causes in all blocks of a specific packet switching engine (PSE) device, use the asic-scan pse ingress disable command in EXEC mode.

asic-scan pse ingress disable location node-id

Syntax Description


Command Modes EXEC

Command History















ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse ingress disable


OL-17332-01

Task ID

Examples The following example shows how to disable an ASIC scan on all causes in all blocks of the ingress PSE device that is located on the CPU node in slot 6:

RP/0/RP0/CPU0:router# asic-scan pse ingress disable location 0/6/CPU0

Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse ingress enable


OL-17332-01

asic-scan pse ingress enableTo enable an ASIC scan on all causes in all blocks of a specific ingress packet switching engine (PSE) device, use the asic-scan pse ingress enable command in EXEC mode.

asic-scan pse ingress enable location node-id

Syntax Description


Command Modes EXEC

Command History



location node-id Identifies the location of the node that hosts the ingress PSE on which to enable the ASIC scan. The node-id argument is expressed in the rack/slot/module notation.












ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse ingress enable


OL-17332-01

Task ID

Examples The following example shows how to enable an ASIC scan on all causes in all blocks on the ingress PSE that is located on the CPU node in slot 6:

RP/0/RP0/CPU0:router# asic-scan pse ingress enable location 0/6/CPU0

Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse ingress help-block


OL-17332-01

asic-scan pse ingress help-block To enable an ASIC scan that lists all block numbers of a specific ingress packet switching engine (PSE) device, use the asic-scan pse ingress help-block command in EXEC mode.

asic-scan pse ingress help-block location node-id

Syntax Description


Command Modes EXEC

Command History



Task ID

Examples The following example shows how to enable an ASIC scan that lists all block numbers on the ingress PSE that is located on the CPU node in slot 6:

RP/0/RP0/CPU0:router# asic-scan pse ingress help-block location 0/6/CPU0

location node-id Identifies the location of the node that hosts the ingress PSE on which to enable the ASIC scan. The node-id argument is expressed in the rack/slot/module notation.






Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse ingress location


OL-17332-01

asic-scan pse ingress locationTo run an ASIC scan on a specific packet switching engine (PSE) device, use the asic-scan pse ingress location command in EXEC mode.

asic-scan pse ingress location node-id

Syntax Description


Command Modes EXEC

Command History

Usage Guidelines To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.


Task ID

location node-id Identifies the location of the node hosting the PSE on which to run the ASIC scan. The node-id argument is expressed in the rack/slot/module notation.












Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse ingress location


OL-17332-01

Examples The following example shows how to run an ASIC scan on all ingress PSE located on the CPU node in slot 1:

RP/0/RP0/CPU0:router# asic-scan pse ingress location 0/1/CPU0

ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse ingress quick-scan


OL-17332-01

asic-scan pse ingress quick-scanTo run a quick ASIC scan on a specific file or on all bits of the chip located on a specific packet switching engine (PSE) device, use the asic-scan pse ingress quick-scan command in EXEC mode.

asic-scan pse ingress quick-scan {filename | allscan} location node-id

Syntax Description


Command Modes EXEC

Command History





location node-id Identifies the location of the node hosting the ingress PSE on which to run the ASIC scan. The node-id argument is expressed in the rack/slot/module notation.












ASIC Driver Commands on Cisco IOS XR Softwareasic-scan pse ingress quick-scan


OL-17332-01

Task ID

Examples The following example shows how to run a quick ASIC scan on all bits of the chip on the ingress PSE device that is located on the CPU node in slot 1:

RP/0/RP0/CPU0:router# asic-scan pse ingress quick-scan allscan location 0/1/CPU0

Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareclear controller egressq queue


OL-17332-01

clear controller egressq queueTo clear a specific controller egress queue, use the clear controller egressq queue command in EXEC mode.

clear controller egressq queue queue-id1 [queue-id2] location node-id

Syntax Description


Command Modes EXEC

Command History


queue-id1 Queue you want to clear. Replace the queue-id1 argument with a queue number. Range is from 1 through 8191.

queue-id2 (Optional) Last queue in a range of queues to clear. Replace the queue-id2 argument with a queue number. Range is from 1 through 8191.

location node-id Identifies the location of the node whose egress queue you want to clear. The node-id argument is expressed in the rack/slot/module notation.












ASIC Driver Commands on Cisco IOS XR Softwareclear controller egressq queue


OL-17332-01

Note If you enter the optional [queue-id2] argument after you enter the queue-id1 argument, then the queue-id1 argument specifies the first queue in a range of queues to be cleared. If you enter the queue-id1 argument without specifying the queue-id2 argument, then only the queue specified for queue-id1 is cleared.

Task ID

Examples The following example shows how to clear a specific controller egress queue:

RP/0/RP0/CPU0:router# clear controller egress queue 1 location 0/1/CPU0

Related Commands

Task ID Operations

root-system read

basic-services read, write

drivers read, write

Command Description

clear controller egressq queue all Clears all controller egress queues in the specified location.

ASIC Driver Commands on Cisco IOS XR Softwareclear controller egressq queue all


OL-17332-01

clear controller egressq queue allTo clear all controller egress queues on a specific node, use the clear controller egressq queue all command in EXEC mode.

clear controller egressq queue all location node-id

Syntax Description


Command Modes EXEC

Command History


Task ID

all Clears all egress queues in the specified location.

location node-id Identifies the location of the egressq queue you want to clear. The node-id argument is expressed in the rack/slot/module notation.








Release 3.5.0 The basic-services and root-system s were removed from this command.




Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareclear controller egressq queue all


OL-17332-01

Examples The following example shows how to clear all controller egress queues on a specific node:

RP/0/RP0/CPU0:router# clear controller egress queue all location 0/1/CPU0

Related Commands Command Description

show asic errors Clears a specific controller egress queue.

ASIC Driver Commands on Cisco IOS XR Softwareclear controller egressq statistics


OL-17332-01

clear controller egressq statisticsTo clear the egress queue statistics in a specific location, use the clear controller egressq statistics command in EXEC mode.

clear controller egressq statistics location node-id

Syntax Description


Command Modes EXEC

Command History


Task ID

location node-id Identifies the location of the egressq queue whose statistics you want to clear. The node-id argument is expressed in the rack/slot/module notation.












Task ID Operations

drivers read, write

ASIC Driver Commands on Cisco IOS XR Softwareclear controller egressq statistics


OL-17332-01

Examples The following example shows how to clear all controller egress queue statistics on a specific node:

RP/0/RP0/CPU0:router# clear controller egressq statistics location 0/1/CPU0


show controllers egressq statistics Displays egress queue manager statistics.

ASIC Driver Commands on Cisco IOS XR Softwareclear controller pse statistics


OL-17332-01

clear controller pse statisticsTo clear statistics maintained by the packet switching engine (PSE) on a specific node, use the clear controller pse statistics command in EXEC mode.

clear controller pse statistics [egress | ingress] location node-id

Syntax Description

Defaults If the egress or ingress keywords are not specified, the clear controller pse statistics command takes effect on both device instances.

Command Modes EXEC

Command History

egress (Optional) Clears statistics on the egress PSE device only.

ingress (Optional) Clears statistics on the ingress PSE device only.

location node-id Identifies the location of the node whose PSE device statistics you want to clear. The node-id argument is expressed in the rack/slot/module notation.








Release 3.5.0 • The instance 0 and instance 1 keywords were replaced by the ingress and egress keywords.

• The clear controller pse statistics command was removed from the root-system task-ID.

• The clear controller pse statistics command was first supported under the interface task-ID.




ASIC Driver Commands on Cisco IOS XR Softwareclear controller pse statistics


OL-17332-01


Task ID

Examples The following example shows how to clear all PSE statistics on a specific node (0/1/CPU0):

RP/0/RP0/CPU0:router# clear controller pse statistics location 0/1/CPU0

The following example shows how to clear all egress PSE statistics on a specific node (0/6/CPU0):

RP/0/RP0/CPU0:router# clear controller pse statistics egress location 0/6/CPU0

Related Commands

Task ID Operations

interface read, write

drivers read, write

Command Description

show controllers pse eio links

Displays PSE information for EIO (Elastic I/O) links or for a specific controller.

show controllers pse ipc

Displays PSE information for IPC connections or for a specific IPC controller.

show controllers pse mp

Displays PSE information for the maintenance processor on a specific controller or node.

show controllers pse statistics

Displays PSE statistics for a specific controller instance or for a specific node.

show controllers pse summary

Displays a summary of PSE information for a specific controller or node.

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers cpuctrl cdma channel


OL-17332-01

show controllers cpuctrl cdma channelTo display information about the CPU controller Control Direct-Memory-Access (CDMA) engine, use the show controllers cpuctrl cdma channel command in EXEC mode.

show controllers cpuctrl cdma channel {0 | 1} queue {queue-id | all} {active | detail} [location node-id]

Syntax Description


Command Modes EXEC

Command History

{0 | 1} Displays CPU controller CDMA engine information for the specified channel. Enter 0 to display CDMA engine information for channel 0, or enter 1 to display CDMA engine information for channel 1.

queue {queue-id | all} Displays CDMA information for a specific Direct-Memory-Access (DMA) queue, or for all DMA queues on the specified channel.

• Enter the queue all keywords to display CDMA information for all DMA queues on the specified channel.

• Enter the queue keyword and queue-id argument to display CDMA information for a specific queue. Replace the queue-id argument with a queue number. Range is from 1 through 7.

active Displays descriptions for active DMA queues only.

detail Displays descriptions for any DMA queues, regardless of whether they are active.

location node-id (Optional) Identifies the location of the node whose CPU controller CDMA information you want to display. The node-id argument is expressed in the rack/slot/module notation.







Release 3.5.0 • The show controllers cpuctrl cdma command was replaced by the show controllers cpuctrl cdma channel command.

• The show controllers cpuctrl cdma channel command was first supported under the interface task-ID.




OL-17332-01


Task ID

Examples The following example shows partial output from the show controllers cpuctrl cdma channel command with the detail keyword.

RP/0/RP0/CPU0:router# show controllers cpuctrl cdma channel 1 queue 1 detail location 0/6/CPU0

-------------------------------------------------------DMA queue:Channel: 1 queue: 1 state: Active

OS Interrupt Level = 108 Cpuctrl Int Level = 12 OS Run Priority = 45 client handle = 1 ISR context = 0x780cff84 Pakman/Bufman Inst = bufman/misc client callback function = 0x482038e4 cleanup function = 0x48203a90 Pakmode = 0x00000002 Pollflags = 0x00000000 Total DMA transactions = 3 Queue create count = 1 DMA transactions = 3 Bytes transferred = 67584 DMA Out of Desc errs = 0 DMA IWA = 0 DMA transaction errs = 0

Descriptor list base addr = 0xec0370f0 Physical address = 0x0510f0f0 list_size = 32 Active descriptors = 0 current_index = 3 tx_enqueue_index = 3

Index 0, Shadow: Hdr 0x00000000 Flags 0x00000000 Descriptor: 0x40200060 |...|DIR|...|...| Width 0x0020 0x0000fff8 Bufsize 0x0000 | Xfersize 0xfff8 0x00120000 Memaddr 0x000120000 0x6fb4d000 Squidaddr 0x606fb4d000

Index 1, Shadow: Hdr 0x00000000 Flags 0x00000000 Descriptor: 0x40200060 |...|DIR|...|...| Width 0x0020 0x00000008 Bufsize 0x0000 | Xfersize 0x0008 0x0012fff8 Memaddr 0x00012fff8 0x6fb4d000 Squidaddr 0x606fb4d000

Index 2, Shadow: Hdr 0x00000000 Flags 0x00000000 Descriptor: 0x40100060 |...|DIR|...|...| Width 0x0010 0x00000800 Bufsize 0x0000 | Xfersize 0x0800




Task ID Operations

drivers read

interface read



OL-17332-01

0x00041000 Memaddr 0x000041000 0x6fb42000 Squidaddr 0x606fb42000

Index 3, Shadow: Hdr 0x00000000 Flags 0x00000000 Descriptor: 0x00000000 |...|...|...|...| Width 0x0000 0x00000000 Bufsize 0x0000 | Xfersize 0x0000 0x00000000 Memaddr 0x000000000 0x00000000 Squidaddr 0x0000000000 Index 4, Shadow: Hdr 0x00000000 Flags 0x00000000 --More--

Table 1 describes the significant fields shown in the display.

Table 1 show controllers cpuctrl cdma channel Field Descriptions

Field Description

DMA queue Identifies the DMA1 queue.

Channel Identifies the channel whose DMA queue is displayed. 0 is the ingress channel, and 1 is the egress channel

queue Identifies the queue.

state Current state of the queue.

OS Interrupt Level Current interrupt level for the queue.

Cpuctrl Interrupt Level Current interrupt level for the CPU controller.

OS Run Priority Run priority level for this queue.

client handle Internal identifier for the Cisco client.

ISR context Internal information about the location of the ISR2 pointer.

Pakman/Bufman Instance Internal information about the location of the Pakman and Bufman Instance.

client callback function pointer Internal information about the client callback function pointer.

cleanup function Internal information about the client cleanup function pointer.

Queue Created 1 times Number of times this queue was regenerated.

Pakmode Information about internal data structures and parameters.

Pollflags Specifies whether the CDMA queue uses a polling or interrupt-driven approach for detecting CDMA operation completion notification.

Note Currently, CDMA queues use interrupt driven completion only. PDMA queues use interrupt-driven and polling completion.

Total DMA transactions Number of DMA transactions in the queue.

Queue create count Number of times this queue was regenerated.

DMA transactions Number of DMA transactions in the queue.

Bytes transferred Number of bytes that have been transferred by the Direct-Memory-Access engine.

DMA Out of Desc errs Number of DMA errors in the queue.

CDMA transactions Number of CDMA transactions in the queue.

DMA IWA Number of IWA bytes that have been processed by the Direct-Memory-Access engine.



OL-17332-01

1. Direct Memory Access

Related Commands

DMA transaction errs Number of DMA transactions that had errors.

Descriptor list base addr Internal information about the location of the descriptor list.

Physical address Physical address of the CPU memory that holds the descriptors in the ring used by the CDMA queue hardware.

list_size Total number of descriptors in the ring used by the CDMA queue hardware.

Active descriptors Number of descriptors that have transactions that are not cleaned after being notified of their completion. Note that the hardware may not yet have completed these transactions.

current_index Points to the next descriptor that the hardware is expected to complete.

tx_enqueue_index Points to the descriptor that will be added to the next operation request.

Index Location of the descriptor in the ring.

Shadow Internal field that manages requests that have been split into multiple descriptors.

Hdr Internal field that manages requests that have been split into multiple descriptors.

Flags Internal field that manages requests that have been split into multiple descriptors.

Descriptor Descriptor heading.

Width Width of the data on the ASIC side in bits. The DMA stride is rounded up to the next power of two bytes that contains this number of bits.

Bufsize Size of the buffer used for the transfer.

Xfersize Number of bytes on the CPU memory that are occupied by the transfer.

Memaddr 36 bit physical address of the CPU memory in the transfer.

Squidaddr 40 bit address of the ASIC register or memory in the transfer.

Table 1 show controllers cpuctrl cdma channel Field Descriptions (continued)

Field Description

Command Description

show controllers cpuctrl clients

Displays information about all CPU controller clients on the router, or for specific CPU controller clients.

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers cpuctrl clients


OL-17332-01

show controllers cpuctrl clientsTo display information about all CPU controller clients on the router, or for specific CPU controller clients, use the show controllers cpuctrl clients command in EXEC mode.

show controllers cpuctrl clients {all | cdma clients | pdma clients} {active | detail} [location node-id]

Syntax Description all Displays a summary information for all clients on the router.

cdma clients Displays information about Control Direct-Memory-Access (CDMA) clients only. Replace the clients argument with one of the following keywords:

• dcc—Displays information for the DCC client.

• egressq—Displays information for the egressq client.

• fabricq—Displays information for the Fabricq ASIC client.

• fia—Displays information for the Fabric Interface ASIC (FIA) client.

• ingressq—Displays information for the ingressq ASIC client.

• jacketcard—Displays information for the jacketcard client.

• mipc—Displays information for the Metro Inter-Process-Communication (MIPC) client.

• pla768—Displays information for the ASIC client for OC-768.

• plaspa—Displays information for the ASIC client for the SPA.

• plim—Displays information for the PLIM client.

• plimasic—Displays information for the PLIM ASIC client.

• pse—Displays information for the PSE client.

pdma clients Displays information for Packet Direct-Memory-Access (PDMA) clients only. Replace clients with one of the following keywords:

• bfd—Displays information for the client bidirectional forwarding detection (BFD) PDMA packet.

• diag—Displays information for the PDMA client called DIAG packet.

• fabio—Displays information for the FABIO PDMA packet client.

• fia—Displays information for the fabric interface ASIC packet PDMA client.

• frr—Displays information for the fast reroute (FRR) packet PDMA client.

• gsp—Displays information for the Group Services Packet (GSP) PDMA client.

• mipc—Displays information for the MIPC packet PDMA client.

• mstats—Displays information for the MSTATS packet PDMA client.

• netflow—Displays information for the NetFlow packet PDMA client.

active Displays descriptions for active queues only.



OL-17332-01


Command Modes EXEC

Command History


Task ID

detail Displays descriptions for any queues, regardless of whether or not they are active.

location node-id (Optional) Identifies the location of the node whose CPU controller information you want to display. The node-id argument is expressed in the rack/slot/module notation.







Release 3.5.0 The show controllers cpuctrl clients command was first supported under the interface task-ID.

Release 3.6.0 The following keywords were added:

• bfd

• fabio

• pla768

• plaspa

The netio keyword was removed.



Task ID Operations

drivers read

interface read



OL-17332-01

Examples The following example shows how to display information about the active queues on the CPU controller client called “plimasic”:

RP/0/RP0/CPU0:router# show controllers cpuctrl clients cdma plimasic active location 0/6/CPU0

------------------------------------------------------------client_name: Plimasic client_handle: 3isr_count: 1 queue_count: 1client_pid: 6150

ISR function pointer: 0xfc6f5b8c ISR name: Squid DMA Event ISR

OS interrupt level:111 cpuctrl interrupt level:15 OS run priority: 45 queues chain for above ISR: -------------------------------------------------------- DMA queue: Channel: 0 queue: 5 state: Active

ISR context = 0x7810c558 Pakman/Bufman Inst = bufman/misc client callback function = 0xfc71b430 cleanup function = 0xfc71b5a4 Pakmode = 0x00000002 Pollflags = 0x00000000 Total DMA transactions = 353 Queue create count = 1 DMA transactions = 353 Bytes transferred = 6600 DMA Out of Desc errs = 0 DMA IWA = 0 DMA transaction errs = 0 Descriptor list base addr = 0xec05b110 Physical address = 0x3005b110 list_size = 128 Active descriptors = 0 current_index = 97 tx_enqueue_index = 97


1. Direct Memory Access

2. Interrupt Service Routine

3. Process Identifier

Table 2 show controllers cpuctrl clients Field Descriptions

Field Description

client Client type. Value is DMA1 or PKT.

client_name Name of the client.

client_handle Internal client identifier.

isr_count ISR2 counters.

queue_count Queue counters.

client_pid Client PID3.



OL-17332-01


show controllers cpuctrl cdma channel

Displays information about the CPU controller CDMA engine.

show controllers cpuctrl summary

Displays summarized information about all the ASICs accessed through the CPU controller ASICs on the router or on a specific node.

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers cpuctrl devices


OL-17332-01

show controllers cpuctrl devicesTo display information about the CPU controller devices on the router, use the show controllers cpuctrl devices command in EXEC mode.

show controllers cpuctrl devices device-name {pdma queue {all | tx | rx} {active | detail} | pio} [location node-id]

Syntax Description device-name Displays information about a specific CPU controller device. Replace the device-name argument with one of the following device names:

• egressq—Displays information about the egressq ASIC instance 0.

• epse—Displays information about the egress packet switching engine (PSE) ASIC.

• fabricq instance 0—Displays information about the fabricq ASIC instance 0.




• fia instance 0—Displays information about the Fabric Interface ASIC (FIA) instance 0.

• fia instance 1—Displays information about the FIA instance 1.

• ingressq—Displays information about the ingressq ASIC.

• ipse—Displays information about the ingress packet switching engine (PSE) ASIC.

• jacketcard instance 0—Displays information about the jacketcard instance 0 ASIC.



• plim asic instance 0—Displays information about the PLIM ASIC instance 0.


• plim asic instance 2 —Displays information about the PLIM ASIC instance 2.


• plim fpga—Displays information about the field-programmable gate array (FPGA) PLIM.



OL-17332-01


Command Modes EXEC

Command History

pdma queue all Displays transmit and receive Packet Direct-Memory-Access (PDMA) information for the specified queue. Replace the queue argument with a queue number. The range is from 0 to 7.

pdma queue tx Displays transmit PDMA information only for the specified queue. Replace the queue argument with a queue number. The range is from 0 to7.

pdma queue rx Displays receive PDMA information only for the specified queue. Replace the queue argument with a queue number. The range is from 0 to 7.

pdma all Displays transmit and receive PDMA information for all queues.


detail Displays detailed descriptions for any queues, regardless of whether they are active.

pio Displays transmit and receive Polled I/O (PIO) information for the specified queue.

location node-id (Optional) Identifies the location of the node whose CPU controller information you want to display. The node-id argument is expressed in the rack/slot/module notation.







Release 3.5.0 The show controllers cpuctrl devices command was first supported under the interface task-ID.



OL-17332-01


Task ID

Examples The following example shows how to display transmit and receive PDMA information for all active queues on the egressq ASIC instance 0:

RP/0/RP0/CPU0:router# show controllers cpuctrl devices egressq pdma queue all active location 0/6/CPU0

--------------------------------------------------------TX PKT queue: cpuctrl net Port: 7 (Egressq ) queue: 0 state: Active

OS Interrupt Level = 127 Cpuctrl Int Level = 31 OS Run Priority = 10 client handle = 6 ISR context = 0x7810c1c8 Pakman/Bufman Inst = pakman/server client callback function = 0x48200298 cleanup function = 0x482002bc

Release 3.6.0 The following keywords were changed:

• fabricq0 changed to fabric instance 0




• fia0 changed to fia instance 0

• fia1 changed to fia instance 1

• jacketcard0 changed to jacketcard instance 0



• plimasic0 changed to plim asic instance 0




• plimfpga changed to plim fpga




Task ID Operations

drivers read

interface read



OL-17332-01

Pakmode = 0x00000001 Pollflags = 0x00000000Total Packets transmitted = 660089 Queue create count = 1 Packets transmitted = 660089 Bytes transmitted = 17166002

Tx Out of Descriptor errs = 0 Tx IWA = 0 Tx oversize errs = 0 Tx EgressQ q0 errs = 0

Descriptor list base addr = 0xec348068 Physical address = 0x30348068 list_size = 1024 Active descriptors = 0 current_index = 633 tx_enqueue_index = 633

-------------------------------------------------------TX PKT queue:cpuctrl net Port: 0 (Egressq ) queue: 1 state: Inactive -------------------------------------------------------TX PKT queue:cpuctrl net Port: 0 (Egressq ) queue: 2 state: Inactive

-------------------------------------------------------TX PKT queue:cpuctrl net Port: 0 (Egressq ) queue: 3 state: Inactive



-------------------------------------------------------TX PKT queue:cpuctrl net Port: 7 (Egressq ) queue: 6 state: Active

OS Interrupt Level = 118 Cpuctrl Int Level = 22 OS Run Priority = 10 client handle = 2 ISR context = 0x7810cf24 Pakman/Bufman Inst = bufman/ipc client callback function = 0xfc71d604 cleanup function = 0xfc71d6b8 Pakmode = 0x00000005 Pollflags = 0x00000000Total Packets transmitted = 0 Queue create count = 1 Packets transmitted = 0 Bytes transmitted = 0


Descriptor list base addr = 0xec07a110 Physical address = 0x3007a110 list_size = 256 Active descriptors = 0 current_index = 0 tx_enqueue_index = 0

-------------------------------------------------------TX PKT queue:cpuctrl net Port: 7 (Egressq ) queue: 7 state: Active

OS Interrupt Level = 119 Cpuctrl Int Level = 23 OS Run Priority = 40 client handle = 9 ISR context = 0x7810d008 Pakman/Bufman Inst = pakman/sever client callback function = 0xfc71d604 cleanup function = 0xfc71d6b8 Pakmode = 0x00000001 Pollflags = 0x00000000Total Packets transmitted = 0 Queue create count = 1 Packets transmitted = 0 Bytes transmitted = 0




OL-17332-01

Descriptor list base addr = 0xed63a068 Physical address = 0x3163a068 list_size = 1024 Active descriptors = 0 current_index = 0 tx_enqueue_index = 0

-------------------------------------------------------RX PKT queue:cpuctrl net Port: 7 (Egressq ) queue: 0 state: Active

OS Interrupt Level = 121 Cpuctrl Int Level = 25 OS Run Priority = 10 client handle = 8 ISR context = 0x7810d0ec Pakman/Bufman Inst = bufman/misc client callback function = 0xfc71d550 cleanup function = 0xfc71d6b8 Pakmode = 0x00000001 Pollflags = 0x00000000 Requested Rx Buffer Size = 1024 Packet switchcount = 20 Actual Rx Buffer Size = 1648 Pool = 4 MTU = 12188 MTU Descriptors = 8 Total Packets received = 71080 Queue create count = 1 Packets received = 71080 Bytes received = 858219920 Rx No Buffer errs = 0 NoBufferLimit errs = 0 Rx No Packet Header errs = 0 Packet Form errs = 0 Rx Packet errs = 0 Rx Intr Stall errs = 0 Rx Intr Drop errs = 0

Descriptor list base addr = 0xec05c940 Physical address = 0x3005c940 list_size = 128 Active descriptors = 0 current_index = 64 tx_enqueue_index = 64

--More--


1. transmit

2. receive

Related Commands

Table 3 show controllers cpuctrl devices Field Descriptions

Field Description

PKT queue: Displays whether the packet queue is TX1 or RX2.

cpuctrl net Port Identifies the CPU controller port.

queue Identifies the queue whose CPU controller device information is displayed.

client handle Internal Cisco client identifier.

queue state Current state of the queue. The queue can be Active or Inactive.

Command Description



ASIC Driver Commands on Cisco IOS XR Softwareshow controllers cpuctrl internal


OL-17332-01

show controllers cpuctrl internalTo display internal information about the CPU controller, use the show controllers cpuctrl internal command in EXEC mode.

show controllers cpuctrl internal [location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID

location node-id (Optional) Identifies the location of the node whose internal CPU controller information you want to display. The node-id argument is expressed in the rack/slot/module notation.







Release 3.5.0 The show controllers cpuctrl internal command was first supported under the interface task-ID.

Release 3.6.0 The location node-id keyword and argument were changed from required to optional.



Task ID Operations

drivers read

interface read



OL-17332-01

Examples The following example shows how to display internal information about the CPU controller:

RP/0/RP0/CPU0:router# show controllers cpuctrl internal

Cpuctrl Internal Info for node 0/0/CPU0: Error Interrupts = 0 Spurious Error Interrupts = 0 PCI Error Overflows = 0 PCI PM Error Overflows = 0 PCIX Error Overflows = 0 Internal Access PCI Overflows = 0 Port Error Overflows = 0 Error Log Overflows = 0 cpuctrl Config Reg = 0x8357ffff cpuctrl Physical Offset = 0x80000000 cpuctrl Window Size = 0x40000000 cpuctrl Port Window Size = 0x04000000 cpuctrl SHMem Size = 0x00800000 cpuctrl SHMem Used = 0x00223ee8 cpuctrl version info: Squid FPGA v2.07 Fri Jan 23 16:21:01 2004 ykoren

Cpuctrl Internal Info for node 0/3/CPU0: Error Interrupts = 0 Spurious Error Interrupts = 0 PCI Error Overflows = 0 PCI PM Error Overflows = 0 PCIX Error Overflows = 0 Internal Access PCI Overflows = 0 Port Error Overflows = 0 Error Log Overflows = 0 cpuctrl Config Reg = 0x8357ffff cpuctrl Physical Offset = 0x80000000 cpuctrl Window Size = 0x40000000 cpuctrl Port Window Size = 0x04000000 cpuctrl SHMem Size = 0x00800000 cpuctrl SHMem Used = 0x00223ee8 cpuctrl version info: Squid FPGA v2.07 Fri Jan 23 16:21:01 2004 ykoren

Cpuctrl Internal Info for node 0/RP0/CPU0: Error Interrupts = 0 Spurious Error Interrupts = 0 PCI Error Overflows = 0 PCI PM Error Overflows = 0 PCIX Error Overflows = 0 Internal Access PCI Overflows = 0 Port Error Overflows = 0 Error Log Overflows = 0 cpuctrl Config Reg = 0x803f007f cpuctrl Physical Offset = 0x80000000 cpuctrl Window Size = 0x40000000 cpuctrl Port Window Size = 0x04000000 cpuctrl SHMem Size = 0x00800000 cpuctrl SHMem Used = 0x00223ee8 cpuctrl version info: Squid FPGA v2.07 Fri Feb 6 17:49:22 2004 ykoren

Cpuctrl Internal Info for node 0/RP1/CPU0: Error Interrupts = 0 Spurious Error Interrupts = 0 PCI Error Overflows = 0 PCI PM Error Overflows = 0 PCIX Error Overflows = 0 Internal Access PCI Overflows = 0 Port Error Overflows = 0 Error Log Overflows = 0 cpuctrl Config Reg = 0x003f007f cpuctrl Physical Offset = 0x80000000 cpuctrl Window Size = 0x40000000 cpuctrl Port Window Size = 0x04000000 cpuctrl SHMem Size = 0x00800000 cpuctrl SHMem Used = 0x00223ee8 cpuctrl version info: Squid FPGA v2.05 Wed Sep 3 17:37:47 2003 ykoren



OL-17332-01


1. Peripheral Component Interconnect

2. port manager

Related Commands

Table 4 show controllers cpuctrl internal Field Descriptions

Field Description

Error Interrupts Total of error interrupts that have occurred on this node.

Spurious Error Interrupts Current number interrupts that have occurred on this node due to spurious errors.

PCI Error Overflows Number of times the PCI1 error buffer overflowed on the node.

PCI PM Error Overflows Number of times PCI PM2 error buffer overflowed on this node.

PCIX Error Overflows Number of times the PCI-X error buffer overflowed on this node.

Internal Access PCI Overflows Number of times the Internal Access PCI buffer overflowed on this node.

Port Error Overflows Number of times the port error buffer overflowed on this node.

Error Log Overflows Number of times the error log buffer overflowed on this node.

cpuctrl Config Reg CPU controller configuration register, expressed in hexadecimal format.

cpuctrl Physical Offset CPU controller physical offset, expressed in hexadecimal format.

cpuctrl Window Size CPU controller window size, expressed in hexadecimal format.

cpuctrl Port Window Size CPU controller port window size, expressed in hexadecimal format.

cpuctrl SHMem Size CPU controller shared memory size, expressed in hexadecimal format.

cpuctrl SHMem Used CPU controller shared memory that has been used already, expressed in hexadecimal format.

cpuctrl version info Provides version information for the CPU controller. The information displayed is:

• Squid version

• Date of the last version installation or upgrade

Command Description



ASIC Driver Commands on Cisco IOS XR Softwareshow controllers cpuctrl ports


OL-17332-01

show controllers cpuctrl portsTo display port information for the specified CPU controller ASIC, use the show controllers cpuctrl ports command in EXEC mode.

show controllers cpuctrl ports {asic_id} {pdma queue {queue-id | all} direction {all | rx | tx} {active | detail} | pio} [location node-id]

Syntax Description asic_id Identifies the CPU controller ASIC whose port information you want to display. Replace the asic_id argument with one of the following keywords:

• cpuctrl—Displays port information for the CPU controller ASIC instance 0.

• egressq—Displays port information for instance 0 of the egressq ASIC.

• epse—Displays port information for the egress packet switching engine (EPSE) ASIC.

• fabricq instance 0—Displays port information for instance 0 of the fabricq ASIC.




• fia instance 0—Displays port information for instance 0 of the fabric Interface ASIC (FIA).

• fia instance 1—Displays port information for instance 1 of the FIA.

• ingressq—Displays port information for the ingressq ASIC.

• ipse—Displays port information for the ingress packet switching engine (PSE) ASIC.

• jacketcard instance 0—Displays port information for instance 0 of the jacketcard ASIC.



• pla768—Displays port information for the OC768 plim ASIC.

• plaspa instance 0—Displays port information for instance 0 of the SPA plim ASIC.


• plim asic instance 0—Displays port information for instance 0 of the plim ASIC.




pdma queue queue-id

Displays transmit and receive Packet Direct-Memory-Access (PDMA) information for the specified queue.



OL-17332-01


Command Modes EXEC

Command History


pdma queue all

Displays transmit and receive PDMA information for all queues. The information displayed pertains to the ASIC indicated in the show controllers cpuctrl ports command.

direction all Displays transmit and receive Packet Direct-Memory-Access (PDMA) information for the specified queue. The information displayed pertains to the ASIC you specified for the asic_id argument.

direction rx Displays receive PDMA information only for the specified queue. The information displayed pertains to the ASIC you specified for the asic_id argument.

direction tx Displays transmit PDMA information only for the specified queue. The information displayed pertains to the ASIC you specified for the asic_id argument.


detail Displays descriptions for any queues, regardless of whether they are active.


location node-id

(Optional) Identifies the location of the node whose CPU controller port information you want to display. The node-id argument is expressed in the rack/slot/module notation.







Release 3.5.0 The show controllers cpuctrl ports command was first supported under the interface task-ID.

The queue and direction keywords were added to the show controllers cpuctrl ports command.






OL-17332-01

Task ID

Examples The following example shows how to display port information for the transmit and receive PIO queues on the EPSE ASIC:

RP/0/RP0/CPU0:router# show controllers cpuctrl ports epse pio

client name: PSE device instance: 1cpuctrl net port: 6 pci base: 0x98000000map reg: 0x6076a12c OS interrupt level: 102Cpuctrl interrupt level: 6 OS Run priority: 6config reg: 0x00000000 channels reg: 0x00000000int_cause_asic_mask: 0x00000010 int_cause_error_mask: 0x00000020int_cause_link_error_mask: 0x00000040crc_errors: 0 sync_errors: 0 reframe_events: 0

client name: PSE device instance: 1cpuctrl net port: 6 pci base: 0x98000000map reg: 0x6076a12c OS interrupt level: 102Cpuctrl interrupt level: 6 OS Run prority: 6config reg: 0x00000000 channels reg: 0x00000000int_cause_asic_mask: 0x00000010 int_cause_error_mask: 0x00000020int_cause_link_error_mask: 0x00000040crc_errors: 0 sync_errors: 0 reframe_events: 0

device PSE instance 1 is not detected on node 201/


Task ID Operations

drivers read

interface read

Table 5 show controllers cpuctrl ports Field Descriptions

Field Description

client name Identifies the client whose port CPU controller information is displayed.

device instance The client device instance for which the port CPU controller information is displayed.

cpuctrl net port Identifies the CPU controller net port.

pci base PCI1 base.

map reg Client map register.

OS interrupt level Level of Cisco IOS XR interrupt configured for the port. Interrupts are triggered by arrival of a packet that causes the CPU to postpone other tasks and handle the packet.

Cpuctrl interrupt level Level of CPU controller interrupt configured for the port.

OS Run priority Cisco IOS XR priority.

config reg Configuration register, expressed in hexadecimal format.

channels reg Channel register, expressed in hexadecimal format.

int_cause_asic_mask Internal ASIC masking information.



OL-17332-01


2. cyclic redundancy check

Related Commands

int_cause_error_mask Internal error masking information.

int_cause_link_error_mask Internal link error masking information.

crc_errors Number of CRC2 errors that have occurred on this port.

sync_errors Number of synchronization errors that have occurred on this port.

reframe_events Number of reframe events that have occurred on this port.

Table 5 show controllers cpuctrl ports Field Descriptions (continued)

Field Description

Command Description



ASIC Driver Commands on Cisco IOS XR Softwareshow controllers cpuctrl ports cpuctrl pio


OL-17332-01

show controllers cpuctrl ports cpuctrl pioTo display polled I/O (PIO) information for the specified CPU controller ASIC, use the show controllers cpuctrl ports cpuctrl pio command in EXEC mode.

show controllers cpuctrl ports {asic_id} cpuctrl pio [location node-id]

Syntax Description asic_id Identifies the CPU controller ASIC whose port information you want to display. Replace the asic_id argument with one of the following keywords:

• cpuctrl—Displays port information for the CPU controller ASIC instance 0.

• egressq—Displays port information for instance 0 of the egressq ASIC.

• epse—Displays port information for the egress packet switching engine (EPSE) ASIC.





• fia instance 0—Displays port information for instance 0 of the fabric Interface ASIC (FIA).

• fia instance 1—Displays port information for instance 1 of the FIA.

• ingressq—Displays port information for the ingressq ASIC.

• ipse—Displays port information for the ingress packet switching engine (PSE) ASIC.




• pla768—Displays port information for the OC768 plim ASIC.

• pdma—Displays port PDMA information.

• pio—Displays port Polled I/O (PIO) information.









OL-17332-01


Command Modes EXEC

Command History


Task ID

Examples The following example shows how to display port information for the transmit and receive PIO queues on the EPSE ASIC:

RP/0/RP0/CPU0:router# show controllers cpuctrl ports cpuctrl pio location 0/1/CPU0

client name: Cpuctrl device instance: 0 cpuctrl net port: 0 pci base: 0x80000000map reg: 0x00000000 OS interrupt level: 96


location node-id

(Optional) Identifies the location of the node whose CPU controller port information you want to display. The node-id argument is expressed in the rack/slot/module notation.







Release 3.5.0 The show controllers cpuctrl ports command was first supported under the interface task-ID.

The queue and direction keywords were added to the show controllers cpuctrl ports command.




Task ID Operations

drivers read

interface read



OL-17332-01

Cpuctrl interrupt level: 0 OS Run prority: 0 config reg: 0x00000000 channels reg: 0x00000000int_cause_asic_mask: 0x00000000 int_cause_error_mask: 0x00000000

int_cause_link_error_mask: 0x00000000crc_errors: 0 sync_errors: 0 reframe_events: 0


show controllers cpuctrl ports

Displays port information for the specified CPU controller ASIC.



ASIC Driver Commands on Cisco IOS XR Softwareshow controllers cpuctrl summary


OL-17332-01

show controllers cpuctrl summaryTo display summarized information about all the ASICs accessed through the CPU controller ASICs on the router or on a specific node, use the show controllers cpuctrl summary command in EXEC mode.

show controllers cpuctrl summary [location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID

location node-id (Optional) Identifies the location of the node whose CPU controller ASIC information you want to display. The node-id argument is expressed in the rack/slot/module notation.







Release 3.5.0 The show controllers cpuctrl summary command was first supported under the interface task-ID.




Task ID Operations

drivers read

interface read



OL-17332-01

Examples The following example shows how to display summarized information about all the ASICs accessed through the CPU controller ASICs on a specific node:

RP/0/RP0/CPU0:router# show controllers cpuctrl summary location 0/0/CPU0

Cpuctrl discovered 11 device on node 0/0/CPU0:Cpuctrl HW version string for this node is:Squid FPGA v2.07 Fri Jan 23 16:21:01 2004 ykoren

-----------------------------------------------------------device_name: Fabricq device instance: 0Cpuctrl net port: 3 pci_base: 0x8c000000

-----------------------------------------------------------device_name: Fabricq device instance: 1Cpuctrl net port: 4 pci_base: 0x90000000

-----------------------------------------------------------device_name: Ingressq device instance: 0Cpuctrl net port: 8 pci_base: 0xa0000000

-----------------------------------------------------------device_name: Egressq device instance: 0Cpuctrl net port: 7 pci_base: 0x9c000000

-----------------------------------------------------------device_name: FIA device instance: 0Cpuctrl net port: 1 pci_base: 0x84000000

-----------------------------------------------------------device_name: FIA device instance: 1Cpuctrl net port: 2 pci_base: 0x88000000

-----------------------------------------------------------device_name: Cpuctrl device instance: 0Cpuctrl net port: 0 pci_base: 0x80000000

-----------------------------------------------------------device_name: PSE device instance: 1Cpuctrl net port: 6 pci_base: 0x98000000

--More--



Table 6 show controllers cpuctrl summary Field Descriptions

Field Description

device_name Identifies the device whose CPU controller information is displayed.

device instance Identifies the CPU device whose information is displayed.

Cpuctrl net port Identifies the CPU controller network port.

pci_base PCI1 base, in hexadecimal format.



OL-17332-01


show controllers cpuctrl cdma channel

Displays information about the CPU controller CDMA engine.

show controllers cpuctrl clients

Displays information about all CPU controller clients on the router, or for specific CPU controller clients.

show controllers cpuctrl devices

Displays information about the CPU controller devices on the router.

show controllers cpuctrl internal

Displays information about the internal CPU controller.

show controllers cpuctrl ports

Displays port information for the specified CPU controller ASIC.

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers egressq eio links


OL-17332-01

show controllers egressq eio linksTo display Elastic I/O (EIO) information for the egress queueing ASIC, use the show controllers egressq eio links command in EXEC mode.

show controllers egressq eio links {link-id | all} location node-id

Syntax Description


Command Modes EXEC

Command History


Task ID

link-id Identifies the EIO link whose egress queueing ASIC information you want to display. Replace the link-id argument with a link identifier. Range is from 0 to 4294967295.

all Displays egress queueing ASIC information for all links on the specified node.

location node-id Identifies the location of the egress queue manager whose EIO link information you want to display. The node-id argument is expressed in the rack/slot/module notation.









Task ID Operations

drivers read

interface read

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers egressq eio links


OL-17332-01

Examples The following example shows how to display information for all EIO links on a node’s egress queueing ASIC:

RP/0/RP0/CPU0:router# show controllers egressq eio links all location 0/2/CPU0

Node: 0/2/CPU0:----------------------------------------

EIO links:-------------------------------------------------------------------ASIC Id Peer Id Type Link-Id Attempts Accept Failed State-------------------------------------------------------------------EGRESSQ_0 PSE_1 RX 11 1 1 0 EIO_LINK_TRAINEDEGRESSQ_0 PSE_1 TX 64 0 0 0 EIO_LINK_TRAINEDEGRESSQ_0 PLIM-ASIC_0 TX 60 0 0 0 EIO_LINK_TRAINEDEGRESSQ_0 PLIM-ASIC_1 TX 61 0 0 0 EIO_ADD_LINKEGRESSQ_0 PLIM-ASIC_2 TX 62 0 0 0 EIO_ADD_LINKEGRESSQ_0 PLIM-ASIC_3 TX 63 0 0 0 EIO_ADD_LINK


Related Commands

Table 7 show controllers egressq eio links Field Descriptions

Field Description

ASIC Id Identifies the ASIC that is associated with the link whose information is displayed.

Peer Id Identifies the ASIC peer.

Type Indicates whether the AISC is receiving (RX) or transmitting (TX).

Link-Id Link identifier.

Attempts Number of attempts made to send or receive information on the specified link.

Accept Number of consecutive EIO requests for the link made by the PSE driver to the peer that were accepted.

Failed Number of consecutive EIO requests for the link that failed.

State Current link state.

Command Description

show controllers egressq group

Displays information for about egress queue groups.

show controllers egressq interface

Displays information about interfaces associated with an egress queue.

show controllers egressq port

Displays egress queue information for a port, or for several ports.

show controllers egressq queue

Displays information about a specific egress queue, or a range of egress queues.

show controllers egressq statistics

Displays egress queue manager statistics.

show controllers plim asic egress-channel bay

Displays ingress queue manager statistics.

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers egressq group


OL-17332-01

show controllers egressq groupTo display information about egress queue groups, use the show controllers egressq group command in EXEC mode.

show controllers egressq group {group1 [group2] | all | limits {max | min}} location node-id

Syntax Description


Command Modes EXEC

Command History


group1 First group whose information you want to display. Range is from 1 to 2047.

group2 (Optional) Last group whose information you want to display. Range is from 1 to 2047.

all Indicates that you want to display information about all egress queue groups on a specific node.

limits Indicates that you want to display the limits table. Follow the keyword with max to display the maximum limits table, or min to display the minimum limits table.

max Display the maximum limits table.

min Display the minimum limits table.

location node-id Identifies the location of the egress queue whose group information you want to display. The node-id argument is expressed in the rack/slot/module notation.











OL-17332-01

If you do not specify a group number for the group2 argument, information is displayed only for the egress queue you specified for the group1 argument. If you specify group1 and group2, information is displayed for all groups within the range from group1 through group2.

Task ID

Examples The following example shows how to display information for a specific range of egress queue groups on the CPU node in slot 2:

RP/0/RP0/CPU0:router# show controllers egressq group 1 3 location 0/2/CPU0

---------------------------------- Group 1---------------------------------- Port : 0 Priority : Low Max LB Tokens : 7812 Max LB Limit Index : 38 Min LB Tokens : 0 Min LB Limit Index : 0 Quantum : 27 Default Queue : 1 High Priority Queue : N/A Low Priority Queue : 1-------------------------------------------------------------------- Group 2---------------------------------- Port : 1 Priority : Low Max LB Tokens : 7812 Max LB Limit Index : 38 Min LB Tokens : 0 Min LB Limit Index : 0 Quantum : 27 Default Queue : 2 High Priority Queue : N/A Low Priority Queue : 2-------------------------------------------------------------------- Group 3---------------------------------- Port : 256 Priority : Low Max LB Tokens : 7812 Max LB Limit Index : 38 Min LB Tokens : 0 Min LB Limit Index : 0 Quantum : 27 Default Queue : 3 High Priority Queue : N/A Low Priority Queue : 3----------------------------------

Task ID Operations

drivers read

interface read



OL-17332-01


Related Commands

Table 8 show controllers egressq group Field Descriptions

Field Description

Port Port identifier.

Priority Group priority.

Max LB Tokens Maximum number of port LB tokens.

Max LB Limit Index Maximum LB limit.

Min LB Tokens Minimum number of port LB tokens.

Min LB Limit Index Minimum LB limit.

Quantum Quantum value for this group.

Default Queue Default queue for this group.

High Priority Queue High priority queue identifier.

Low Priority Queue Low priority queue identifier.

Command Description

show controllers egressq eio links

Displays EIO information for the egress queueing ASIC.











ASIC Driver Commands on Cisco IOS XR Softwareshow controllers egressq interface


OL-17332-01

show controllers egressq interfaceTo display information about interfaces associated with an egress queue, use the show controllers egressq interface command in EXEC mode.

show controllers egressq interface [type instance | all] location node-id

Syntax Description


Command Modes EXEC

Command History


Task ID

type instance Identifies a physical interface or a virtual interface.

Note Use the show interfaces command to see a list of all possible interfaces currently configured on the router.

all Indicates that you want to display egress queue information for all interfaces in the specified location.

location node-id Identifies the location of the interface whose egress queue information you want to display. The node-id argument is expressed in the rack/slot/module notation.









Task ID Operations

interface read

drivers read



OL-17332-01

Examples The following example shows how to display egress queue information for all configured interfaces on the router:

RP/0/RP0/CPU0:router# show controllers egressq interface all

/CPU0---------------------------------- Interface POS0/0/0/15---------------------------------- Port 776---------------------------------- Max LB Tokens : 18720 Max LB Limit Index : 41 Quantum : 27 Default Group : 24 High Priority Group : N/A Low Priority Group : 24-------------------------------------------------------------------- Interface POS0/0/0/14---------------------------------- Port 780---------------------------------- Max LB Tokens : 18720 Max LB Limit Index : 41 Quantum : 27 Default Group : 23 High Priority Group : N/A Low Priority Group : 23-------------------------------------------------------------------- Interface POS0/0/0/13---------------------------------- Port 778---------------------------------- Max LB Tokens : 18720 Max LB Limit Index : 41 Quantum : 27 Default Group : 22 High Priority Group : N/A Low Priority Group : 22-------------------------------------------------------------------- Interface POS0/0/0/12---------------------------------- Port 782---------------------------------- Max LB Tokens : 18720 Max LB Limit Index : 41 Quantum : 27 Default Group : 21 High Priority Group : N/A Low Priority Group : 21-------------------------------------------------------------------- Interface POS0/0/0/11---------------------------------- Port 520---------------------------------- Max LB Tokens : 18720 Max LB Limit Index : 41 Quantum : 27 Default Group : 20



OL-17332-01

High Priority Group : N/A Low Priority Group : 20-------------------------------------------------------------------- Interface POS0/0/0/10---------------------------------- Port 524---------------------------------- Max LB Tokens : 18720 Max LB Limit Index : 41 Quantum : 27 Default Group : 19 High Priority Group : N/A Low Priority Group : 19-------------------------------------------------------------------- Interface POS0/0/0/9---------------------------------- Port 522---------------------------------- Max LB Tokens : 18720 Max LB Limit Index : 41 Quantum : 27 Default Group : 18 High Priority Group : N/A Low Priority Group : 18-------------------------------------------------------------------- Interface POS0/0/0/8---------------------------------- Port 526---------------------------------- Max LB Tokens : 18720 Max LB Limit Index : 41 Quantum : 27 Default Group : 17 High Priority Group : N/A Low Priority Group : 17--------------------------------------------------------------------


Table 9 show controllers egressq interface Field Descriptions

Field Description

Interface Interface identifier, in the <type>rack/slot/module/port format.

Port Port to which the specified interface belongs.



Quantum Average number of bytes in the interface egress queue.

Default Group Default group for this interface.

High Priority Group High priority group identifier.

Low Priority Group Low priority group identifier.



OL-17332-01














ASIC Driver Commands on Cisco IOS XR Softwareshow controllers egressq port


OL-17332-01

show controllers egressq portTo display egress queue information for a port, or for several ports, use the show controllers egressq port command in EXEC mode.

show controllers egressq port {port1 [port2] | all | limits max] location node-id

Syntax Description


Command Modes EXEC

Command History


port1 Identifies the port whose egress queue information you want to display. Replace the port1 argument with a port identifier. Range is from 0 to 1023.

port2 Identifies the last port whose egress queue information you want to display. Replace the port2 argument with a port identifier. Range is from 0 to 1023.

all Indicates that you want to display egress queue information for all ports on the node in the specified location.

limits max Indicates that you want to display the maximum limits table.

location node-id Identifies the location of the egress queue whose group information you want to display. The node-id argument is expressed in the rack/slot/module notation.



Release 3.3.0 This command was first supported on the Cisco XR 12000 Series Router.








OL-17332-01

Task ID

Examples The following example shows how to display egress queue information for ports 1, 2, and 3 on the CPU node in slot 2:

RP/0/RP0/CPU0:router# show controllers egressq port 1 3 location 0/2/CPU0

---------------------------------- Port 1---------------------------------- Max LB Tokens : 7812 Max LB Limit Index : 38 Quantum : 27 Default Group : 2 High Priority Group : N/A Low Priority Group : 2----------------------------------

---------------------------------- Port 2----------------------------------Port is not allocated---------------------------------- Port 3----------------------------------Port is not allocated


Task ID Operations

interface read

drivers read

Table 10 show controllers egressq port Field Descriptions

Field Description

Port Port identifier.



Quantum Quantum value for this interface.

Default Group Default group.

High Priority Group High priority group identifier.

Low Priority Group Low priority group identifier.



OL-17332-01














ASIC Driver Commands on Cisco IOS XR Softwareshow controllers egressq queue


OL-17332-01

show controllers egressq queueTo display information about a specific egress queue, or a range of egress queues, use the show controllers egressq queue command in EXEC mode.

show controllers egressq queue {queue1 [queue2 | from-group {group-id | all} | from-interface {type instance | all} | from-port {port-id | all} | limits {max | min} | all] location node-id

Syntax Description


Command Modes EXEC

queue1 Identifies the first port whose egress queue information you want to display. Replace the queue1 argument with a queue identifier. Range is from 1 through 8191.

queue2 (Optional) Identifies the last port whose egress queue information you want to display. Replace the queue2 argument with a queue identifier. Range is from 1 through 8191.

from-group group-id Displays egress queue information for a specific port group. Replace the group-id argument with the number that identifies the port group whose information is to be displayed. Range is from 1 through 2047.

from-group all Displays egress queue information for all port groups on the specified location.

from-interface type instance

Displays egress queue information for a specific interface. Replace the type instance argument with a physical interface ID or a virtual interface ID.


from-interface all Displays egress queue information for all interfaces on the specified location.

from-port port-id Displays egress queue information for a specific port. Replace the port-id argument with a port ID. Range is from 0 to 1023.

from-port all Displays egress queue information for all ports on the specified location.

limits max Displays the maximum limits table.

limits min Displays the minimum limits table.

all Displays detailed information about all egress queues on the specified location.

location node-id Identifies the location of the node whose egress queue information you want to display. The node-id argument is expressed in the rack/slot/module notation.



OL-17332-01

Command History


Task ID

Examples The following example shows how to display information about egress queues 1 and 2 on the CPU node in slot 2:

RP/0/RP0/CPU0:router# show controllers egressq queue 1 2 location 0/2/CPU0---------------------------------- Queue 1---------------------------------- Group : 1 Priority : Low Max LB Tokens : 7812 Max LB Limit Index : 38 Min LB Tokens : 0 Min LB Limit Index : 0 Quantum : 27 Instantaneous length : 0 Length high watermark : 0-------------------------------------------------------------------- Queue 2---------------------------------- Group : 2 Priority : Low Max LB Tokens : 7812



Release 3.3.0 This command was first supported on the Cisco XR 12000 Series Router.


Release 3.5.0 The context keyword and max_elements argument were removed from the show controllers egressq queue command.

The following keywords and arguments were added to the show controllers egressq queue command:

• from-group {group-id | all}

• from-interface {type instance | all}

• from-port {port-id | all}




Task ID Operations

drivers read

interface read



OL-17332-01

Max LB Limit Index : 38 Min LB Tokens : 0 Min LB Limit Index : 0 Quantum : 27 Instantaneous length : 0 Length high watermark : 0


Related Commands

Table 11 show controllers egressq queue Field Descriptions

Field Description

Group Group identifier.

Priority Group priority.



Min LB Tokens Minimum number of port LB tokens.

Min LB Limit Index Minimum LB limit.

Quantum Quantum value for this queue.

Instantaneous length Egress queue instantaneous length.

Length high watermark Length high watermark register.

Command Description













ASIC Driver Commands on Cisco IOS XR Softwareshow controllers egressq statistics


OL-17332-01

show controllers egressq statisticsTo display egress queue manager statistics, use the show controllers egressq statistics command in EXEC mode.

show controllers egressq statistics location node-id

Syntax Description


Command Modes EXEC

Command History


Task ID

Examples The following example shows how to display egress queue manager statistics:

RP/0/RP0/CPU0:router# show controllers egressq statistics location 0/2/CPU0

-------------------------------------------------- Egressq Statistics--------------------------------------------------egressq ASIC version: 1

location node-id Identifies the location of the egress queue whose statistics you want to display. The node-id argument is expressed in the rack/slot/module notation.









Task ID Operations

drivers read

interface read



OL-17332-01

egressq ASIC state: Normalplimasic link0 output packets: 0plimasic link0 output bytes: 0plimasic link1 output packets: 0plimasic link1 output bytes: 0plimasic link2 output packets: 0plimasic link2 output bytes: 0plimasic link3 output packets: 0plimasic link3 output bytes: 0cpuctrl input packets: 0cpuctrl output bytes: 1433250pse input packets: 29250pse dropped packets: 0cpuctrl dropped packets: 0--------------------------------------------------


Related Commands

Table 12 show controllers egressq statistics Field Descriptions

Field Description

egressq ASIC version Version identifier for the egress queue ASIC.

egressq ASIC state Current state of the egress queue ASIC.

plimasic link0 output packets Number of output packets on link 0 of the ASIC.

plimasic link0 output bytes Output bytes on link 0 of the ASIC.


plimasic link1 output bytes Number of output packets on link 1 of the ASIC.

plimasic link2 output packets Number of output packets on link 2 of the ASIC




cpuctrl input packets Number of CPU controller input packets received on this ASIC.

cpuctrl output bytes CPU controller output bytes transmitted on this ASIC.

pse input packets Number of PSE input packets received on this ASIC.

pse dropped packets Number of PSE packets that were dropped by this ASIC due to errors.

cpuctrl dropped packets Number of CPU controller packets that were dropped by this ASIC due to errors.

Command Description











OL-17332-01





Command Description

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers plim asic egress-channel bay


OL-17332-01

show controllers plim asic egress-channel bayTo display statistical information for the SPI4.2 transmit channel on a physical layer interface module (PLIM) ASIC, use the show controllers plim asic egress-channel bay command in EXEC mode.

show controllers plim asic egress-channel bay {0 | 1} channel channel_number [location node-id]

Syntax Description


Command Modes EXEC

Command History


0 Displays statistical information for the SPI4.2 transmit channel that is located in the bottom bay.

1 Displays statistical information for the SPI4.2 transmit channel that is located in the top bay.

channel channel_number Identifies the transmit channel whose statistics you want to display. Replace the channel_number argument with the number of the channel whose statistics you want to display. Range is from 1 through 255.

location node-id Identifies the location of the PLIM whose ASIC information you want to display. The node-id argument is expressed in the rack/slot/module notation.



Release 3.2 This command was first supported on the Cisco XR 12000 Series Router.



Release 3.5.0 The show controllers plim asic tx-channel bay command was replaced by the show controllers plim asic egress-channel bay command.




ASIC Driver Commands on Cisco IOS XR Softwareshow controllers plim asic egress-channel bay


OL-17332-01

Task ID

Examples The following example shows sample output from the show controllers plim asic egress-channel bay command:

RP/0/0/CPU0:router# show controllers plim asic egress-channel bay 0 channel 0 location 0/4/CPU0

Host bay 0 Tx SPI4.2 channel 0 :=============================================Ifname : DATA_PORT_0SPI4.2 Channel state : provisionedBay number : 0Tx SPI4.2 channel number : 0Internal Buffer number : 0SPI4.2 calendar entries : 1Buffer Almost Full Threshold : 0x2c00Tx Queuing ASIC port number : 0


1. System Packet Level Interface 4.2

Task ID Operations

interface read

root-system read

Table 13 show controllers plim asic egress-channel bay Field Descriptions

Field Description

Ifname Identifies the primary transmit interface.

SPI4.2 Channel state Indicates if the SPI4.21 channel is provisioned.

Bay number Identifies the bay that hosts the specified SPI4.2 transmit channel. Can be 0 or 1.

Tx SPI4.2 channel number Identifies the SPI4.2 channel whose information is displayed.

Internal Buffer number Identifies the internal buffer associated with the SPI4.2 transmit channel.

SPI4.2 calendar entries Number of entries in the SPI4.2 calendar.

Buffer Almost Full Threshold An increment counter which indicates that the transmit buffer is almost full. The “Buffer Almost Full Threshold” is expressed in hexadecimal format.

Tx Queuing ASIC port number Identifies the SPI4.2 transmit port.

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers plim asic ingress-channel bay


OL-17332-01

show controllers plim asic ingress-channel bayTo display statistical information for the SPI4.2 receive channel on a physical layer interface module (PLIM) ASIC, use the show controllers plim asic ingress-channel bay command in EXEC mode.

show controllers plim asic ingress-channel bay {0 | 1} channel channel_number [location node-id]

Syntax Description


Command Modes EXEC

Command History


0 Displays statistical information for the SPI4.2 receive channel that is located in the bottom bay.

1 Displays statistical information for the SPI4.2 receive channel that is located in the top bay.

channel channel_number Identifies the receive channel whose statistics you want to display. Replace the channel_number argument with the number of the channel whose statistics you want to display. Range is from 1 through 255.

location node-id Identifies the location of the PLIM whose ASIC information you want to display. The node-id argument is expressed in the rack/slot/module notation.






Release 3.5.0 The show controllers plim asic rx-channel bay command was replaced by the show controllers plim asic ingress-channel bay command.






OL-17332-01

Task ID

Examples The following example shows sample output from the show controllers plim asic ingress-channel bay command:

RP/0/0/CPU0:router# show controllers plim asic ingress-channel bay 0 channel 0 location 0/4/CPU0

Host bay 0 Rx SPI4.2 channel 0 :============================================Ifname : DATA_PORT_0SPI4.2 Channel state : provisionedBay number : 0Rx SPI4.2 channel number : 0Internal Buffer number : 0Rx edram buffer start address : 0x0Rx edram buffer end address : 0x31fffRx edram buffer size : 0x32000Rx length buffer start address : 0x0Rx length buffer end address : 0x63ffRx length buffer size : 0x6400Number of calendar entries : 1Quantum : 209714

RxEDRAM buffer threshold settings:==================================

------------------ <-- Buffer Start (0x0) | | |------------------|<-- SPI4 AEmpty0 (0x6400) | | | | |------------------|<-- SPI4 AEmpty1 (0xc800) | | | | | | | | | | | | |------------------|<-- SPI4 AFull 0 (0x1f400) | | | | |------------------|<-- SPI4 AFull 1 (0x25800) | | | | |------------------|<-- Buffer Full (0x2bc00) | | ------------------ <-- Buffer End (0x31fff)

RxLen EDRAM buffer threshold settings:======================================

------------------ <-- Buffer Start (0x0) | | |------------------|<-- SPI4 AEmpty0 (0xc80) | | | |

Task ID Operations

interface read

root-system read



OL-17332-01

|------------------|<-- SPI4 AEmpty1 (0x1900) | | | | | | | | | | | | |------------------|<-- SPI4 AFull 0 (0x3e80) | | | | |------------------|<-- SPI4 AFull 1 (0x4b00) | | | | |------------------|<-- Buffer Full (0x5780) | | ------------------ <-- Buffer End (0x63ff)


1. System Packet Level Interface 4.2

Table 14 show controllers plim asic ingress-channel bay Field Descriptions

Field Description

Ifname Identifies the primary transmit interface.

SPI4.2 Channel state Indicates if the SPI4.21 channel is provisioned.

Bay number Identifies the bay that hosts the specified SPI4.2 receive channel. Can be 0 or 1.

Rx SPI4.2 channel number Identifies the SPI4.2 receive channel whose information is displayed.

Internal Buffer number Identifies the internal buffer associated with the SPI4.2 receive channel.

Rx edram buffer start address Embedded DRAM buffer start address in hexadecimal format.

Rx edram buffer end address Embedded DRAM buffer end address in hexadecimal format.

Rx edram buffer size Embedded DRAM buffer size in hexadecimal format.

Rx length buffer start address Receive length buffer start address in hexadecimal format.

Rx length buffer end address Receive length DRAM buffer end address in hexadecimal format.

Rx length buffer size Receive length DRAM buffer size in hexadecimal format.

Number of calendar entries Number of entries in the SPI4.2 calendar.

Quantum Average number of bytes in the interface queue.

Buffer Almost Full Threshold An increment counter which indicates that the transmit buffer is almost full. The “Buffer Almost Full Threshold” is expressed in hexadecimal format.

Tx Queuing ASIC port number Identifies the SPI4.2 transmit port.

RxEDRAM buffer threshold settings

Displays embedded DRAM receive buffer threshold counter settings in hexadecimal format.

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers plim asic pla


OL-17332-01

show controllers plim asic plaTo display physical layer interface module (PLIM) ASIC line-card information for the plane card, use the show controllers plim asic pla command in EXEC mode.

show controllers plim asic pla {clients | eio {link number | all} error | packet {mbp | instance number} pointers | sbp} [location node-id]

Syntax Description


Command Modes EXEC

Command History


clients Displays information for PLA clients.

eio Displays information about EIO commands for PLA.

eio link id Displays PLA information for a specific link ID. Range is from 0 to 4294967295.

all Displays PLA information for all links.

error Displays PLA error information.

packet Displays information for the dump packet.

mbp Displays MBP buffer information.

PLA instance number Displays the PLA instance number for a specific instance. Range is from 0 to 3.

pointers Displays information for PLA pointers.

sbp Displays sharp back-pressure (SBP) table.

location node-id Identifies the location of the node whose PLIM ASIC information you want to display. The node-id argument is expressed in the rack/slot/module notation.




ASIC Driver Commands on Cisco IOS XR Softwareshow controllers plim asic pla


OL-17332-01

Task ID

Examples The following example shows how to display PLIM ASIC PLA information for an interface on a Cisco CRS-1 router:

RP/0/RP0/CPU0:router# show controllers plim asic pla eio links?

<0-4294967295> link idall show all links

Task ID Operations

interface read

drivers read

cisco-support read

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers plim asic pla768


OL-17332-01

show controllers plim asic pla768To display physical layer interface module (PLIM) ASIC line-card information for the OC-768 card, use the show controllers plim asic pla768 command in EXEC mode.

show controllers plim asic pla768 {ports | eio {link id | all}} [location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID

Examples The following example shows how to display PLIM ASIC PLA768 information for an interface on a Cisco CRS-1:

ports Displays port mapping information.

eio Displays information about Elastic I/O (EIO) commands for the Reindeer ASIC.

eio link id Displays OC-768 information for a specific link ID. Range is from 0 to 4294967295.






Task ID Operations

interface read

drivers read

cisco-support read

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers plim asic pla768


OL-17332-01

RP/0/RP0/CPU0:router# show controllers plim asic pla768 ?

eio Show eio commands for the Reindeer ASICports Port mapping information

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers plim asic plaspa


OL-17332-01

show controllers plim asic plaspaTo display physical layer interface module (PLIM) ASIC line-card information for the shared port adapters (SPA), use the show controllers plim asic plaspa command in EXEC mode.

show controllers plim asic plaspa {eio {link id | all} | error | ifhandle | instance | num-list | queues | sbp | txport | uidb {entry instance | map instance | table instance}} [location node-id]

Syntax Description


Command Modes EXEC

Command History


eio link id Displays EIO commands for PLASPA information for a specific link ID. Range is from 0 to 4294967295.


error Displays PLASPA error information.

ifhandle Displays the name associated with the interface.

instance Displays instance information of the PLASPA ASIC. Range is from 0 to1.

num-inst Displays number of instances of the PLASPA ASIC.

queues Displays PLASPA queue information.

sbp Displays egress queue back-pressure table information.

txport Displays egressq port information. Range of shared port adapters (SPA) instance is from 0 to 5.

uidb Displays PLASPA uidb hash table information.





ASIC Driver Commands on Cisco IOS XR Softwareshow controllers plim asic plaspa


OL-17332-01

Task ID

Examples The following example shows how to display PLIM ASIC PLASPA information for an interface on a Cisco CRS-1 router:

RP/0/RP0/CPU0:router# show controllers plim asic plaspa eio links all location 0/3/CPU0

Wed Sep 10 04:52:27.452 UTC

Node: 0/3/CPU0:

----------------------------------------

EIO links:

-------------------------------------------------------------------

ASIC Id Peer Id Type Link-Id Attempts Accept Failed State

-------------------------------------------------------------------

PLASPA_1 PSE_0 TX 2 0 0 0 EIO_LINK_TRAINED

PLASPA_1 EGRESSQ_0 RX 61 1 1 0 EIO_LINK_TRAINED

Task ID Operations

interface read

drivers read

cisco-support read

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers plim asic spa bay


OL-17332-01

show controllers plim asic spa bay To display statistical information for the SPA ASIC, use the show controllers plim asic spa command in EXEC mode.

show controllers plim asic spa bay {bay-number} [location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID

bay-number Displays information about the SPA in the specified bay. Range is from 1 through 3.

location node-id Identifies the location of the SPA whose ASIC information you want to display. The node-id argument is expressed in the rack/slot/module notation.






Release 3.5.0 The {0 | 1} keywords were replaced with the bay-number argument.




Task ID Operations

interface read

root-system read



OL-17332-01

Examples The following sample output is from the show controllers plim asic spa bay command:

RP/0/0/CPU0:router# show controllers plim asic spa bay 0 location 0/4/CPU0

SPA 0 table:=======================================SPA OIR state : presentSPA state : enabledSPA allocated Rx buffer size : 4MBSPA available Rx buffer size : 0x20c000RxSPI PLL reset : inactiveHeader Format type : Format APad bytes : 0L2LA : 0Strict priority mode : activeEFC Manager : disabledSPA dual wide mode : inactiveMax SPA channels : 10PLIM loopback : inactiveSPI loopback : inactiveDatamaxT : 4096Training M : 16DIP2 Match : 3DIP2 Error : 3Tx SClk edge : fallingDIP4 Match : 15DIP4 Error : 2Rx SClk edge : risingSPI bus speed : 350MHzTx Burst size : 64 BytesRx Burst size sysdb : 80 BytesRx SPI state : enabledRx SPI sync state : inframeRx calendar mode : singleMaximun RxSPI channels : 10Tx SPI state : enabledTx SPI sync state : inframeTx calendar mode : singleMaximun Tx SPI4.2 channels : 5


Table 15 show controllers plim asic spa bay Field Descriptions

Field Description

SPA OIR state Current OIR1 status for this SPA.

SPA state Current state of the specified SPA. Can be enabled or disabled.

SPA allocated Rx buffer size Number of bytes allocated for the receive buffer.

SPA available Rx buffer size Number of bytes available in the receive buffer.

RxSPI PLL reset SPI PLL receive timer reset value.

Header Format type Header format used by this ASIC.

Pad bytes Number of pad bytes allowed to fill out the packets sent on this ASIC.

L2LA Layer 2 Length Adjust. When a length entry has been read or is being written, this bit contains the value of the L2LA field.



OL-17332-01

Strict priority mode Indicates whether strict priority mode is active or inactive on this SPA.

Strict priority mode ensures that the Priority Queue is serviced only when it is not empty. This provides the lowest possible delay for matching traffic.

EFC Manager Indicates whether the EFC2 manager is enabled or disabled on this SPA.

SPA dual wide mode Indicates whether dual wide mode is active or inactive on this SPA.

Max SPA channels Maximum channels supported on this SPA.

PLIM loopback Indicates whether loopback is active or inactive on this SPA.

SPI loopback Indicates whether SPI loopback is active or inactive on this SPA.

DatamaxT Maximum data training interval. This is the maximum interval between scheduling of training sequences on the SPI4 data path. If the DatamaxT field shows 0, then the core never sends periodic training.

Training M Number of consecutive DIP-2 errors detected on the Tstat bus before the TxSPI module enters the out-of-frame state. This signal can be safely set at any time.

DIP2 Match Total number of 2-bit DIP23 packets that met specific match clauses.

Note DIP2 is a parity algorithm where a 2-bit odd parity is computed diagonally over status words.

DIP2 Error Total number of 2-bit DIP2 errors


Tx SClk edge Indicates which edge of the transmit SClk to use to sample the Tstat bus. Selects rising or falling edge as the active transmit SClk edge.

DIP4 Match Total number of 2-bit DIP4 packets that met specific match clauses.

Rx SClk edge Indicates which edge of the receive SClk to use to sample the Tstat bus. Selects rising or falling edge as the active transmit SClk edge.

DIP4 Error Total number of DIP4 errors.


SPI bus speed SPI4 bus speed in MHz5.

Tx Burst size Committed burst size in bits for traffic transmitted on this SPA.

Rx Burst size sysdb Committed burst size in bits for traffic received on this SPA.

Rx SPI state Indicates whether receive SPI is enabled or disabled.

Rx SPI sync state Indicates which parameter controls the synchronization behavior of the RXSPI module.

Rx calendar mode Indicates which RXSPI status protocol will be used to transmit status.

Table 15 show controllers plim asic spa bay Field Descriptions (continued)

Field Description



OL-17332-01

1. online insertion and removal

2. Extended Flow Control

3. 2-bit Diagonal Interleaved Parity

4. security policy index

5. megahertz

Maximum RxSPI channels Maximum number of SPI receive channels supported on this SPA.

Tx SPI state Indicates whether transmit SPI is enabled or disabled.

Tx SPI sync state Indicates which parameter controls the synchronization behavior of the TXSPI module.

Tx calendar mode Indicates which TXSPI status protocol will be used to transmit status.

Maximum Tx SPI4.2 channels Maximum number of SPI4.2 transmit channels supported on this SPA.

Table 15 show controllers plim asic spa bay Field Descriptions (continued)

Field Description

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers plim asic statistics


OL-17332-01

show controllers plim asic statisticsTo display physical layer interface module (PLIM) ASIC statistics for a specific node or interface, use the show controllers plim asic statistics command in EXEC mode.

show controllers plim asic statistics {interface type interface-path-id | summary} [location node-id]

Syntax Description


Command Modes EXEC

Command History

type Interface type. For more information, use the question mark (?) online help function.

interface-path-id Physical interface or virtual interface.

Note Use the show interfaces command to see a list of all interfaces currently configured on the router.

For more information about the syntax for the router, use the question mark (?) online help function.

summary Displays a summarized information for PLIM ASICs on a specified node, or for all interfaces on the router.















OL-17332-01


Task ID

Examples The following example shows how to display PLIM ASIC statistics information for a POS interface on a Cisco CRS-1:

RP/0/RP0/CPU0router# show controllers plim asic statistics interface POS 0/2/0/0

Node: 0/2/CPU0-------------------------------------------------------------------------------POS0/2/0/0 Tx Statistics-------------------------------------------------------------------------------TotalOctets : 78904040 TotalPkts : 1622308Unicastpkts : 1622308 MulticastPkts : 0BroadcastPkts : 0 <64Octets : 161043364Octets : 0 65to127Octets : 11875128to255Octets : 0 256to511Octets : 0512to1023Octets : 0 1024to1518Octets : 01519to1548Octets : 0 1549to9216Octets : 0>9216Octet : 0 BadCRCPkts : 0802.1QPkts : 0 Underrun : 0Runt : 0 Giant : 0PausePkts : 0 Jabbers : 0DeferralAbort : 0 LateCollision : 0CollisionAbort : 0 OneCollision : 0MultiCollision : 0 TotalCollisions : 0TotalDefer : 0 LateCollisionAbort: 0LengthAbort : 0 TxBP count : 0

POS0/2/0/0 Rx Statistics------------------------------------------------------------------------------- --More-- failed to get statsTotalOctets : 91010808TotalPkts : 1815571 UnicastPkts : 1815571MulticastPkts : 0 BroadcastPkts : 064Octets : 63846 65to127Octets : 11844128to255Octets : 7 256to511Octets : 0512to1023Octets : 0 1024to1518Octets : 01519to1548Octets : 0 1549to9216Octets : 0>9216Octets : 0 BadCRCPkts : 0BadCodedPkts : 0 Runt : 0ShortPkts : 1739874 802.1QPkts : 0Drop : 0 PausePkts : 0ControlPkts : 0 Jabbers : 0BadPreamble : 0

POS0/2/0/0 Drop-------------------------------------------------------------------------------RxFiFO Drop : 0 PAR Tail Drop : 0TxFIFO Drop : 0

Task ID Operations

interface read

root-system read



OL-17332-01


Table 16 show controllers plim asic statistics Field Descriptions

Field Description

TotalOctets Number of octets received or transmitted on the interface.

TotalPkts Number of total packets received or transmitted on the interface.

UnicastPkts Number of unicast packets received or transmitted on the interface.

MulticastPkts Number of multicast packets received or transmitted on the interface. Received packets were directed to the multicast address.

BroadcastPkts Number of good broadcast packets received or transmitted. Received packets were directed to the broadcast address.

64Octets Number of packets (including bad packets) received or transmitted that were less than 64 octets in length (excluding framing bits but including FCS octets).

64Octets Number of packets (including bad packets) received or transmitted that were 64 octets in length (excluding framing bits but including FCS octets).

65to127Octets Number of packets (including bad packets) received or transmitted that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets).







>9216Octet Number of packets (including bad packets) received or transmitted that were greater than 9216 octets in length (excluding framing bits but including FCS octets).



OL-17332-01

BadCRCPkts Number of packets received or transmitted that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS error) or a bad FCS with a non integral number of octets (alignment error).

802.1QPkts Number of 802.1QPkts received or transmitted on the interface.

Underrun Number of packets that were not retrieved quickly enough from shared memory to be transmitted or received.

Runt Number of packets received or transmitted that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed.

Giant Number of packets received or transmitted that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.

PausePkts Number of pause packets transmitted/received on the interface. Pause packets that tell remote devices to delay sending more packets for a specified period of time.

Jabbers Number of packets received or transmitted that were longer than 1518 octets (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS error) or a bad FCS with a non-integral number of octets (assigned error).

DeferralAbort Number of deferral aborts that occurred on this segment.

LateCollision Number of late collisions on this segment

CollisionAbort Number of collisions that were aborted.

OneCollision Number of single collisions that occurred on this segment.

MultiCollision Number multiple collisions that occurred on this segment.

TotalCollisions Number of collisions on this segment.

TotalDefer Number of deferrals on this segment.

LateCollisionAbort Number of late collision aborts that occurred on this segment.

LengthAbort Number of length aborts that occurred on this segment.

TxBP count Number of transmit BP on this segment.

Rx Statistics Indicates the statistics that follow were received by the interface.

TX statistics Indicates the statistics that follow were transmitted by the interface.

RxFiFO Drop Displays the receive FIFO drop information.

PAR Tail Drop Displays PAR tail drop information.

TxFIFO Drop Displays transmitted FIFO drop information.

Table 16 show controllers plim asic statistics Field Descriptions (continued)

Field Description

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers plim asic summary


OL-17332-01

show controllers plim asic summaryTo display summarized physical layer interface module (PLIM) ASIC information for a specific node or interface, use the show controllers plim asic command in EXEC mode.

show controllers plim asic summary [location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID













Task ID Operations

interface read

root-system read



OL-17332-01

Examples The following example shows how to display summarized PLIM ASIC information for all locations:

RP/0/RP0/CPU0router# show controllers plim asic summary

Node: 0/1/CPU0--------------------------------------Instance# 0 Summary info:--------------------------------------Name : PLASPA Version : 2

Port 0Jacket slot: 1 SPA type : SPA_NAME_UNKNOWNPort 1Jacket slot: 3 SPA type : SPA_NAME_UNKNOWNPort 2Jacket slot: 0 SPA type : 4xOC3 POS SPA

Instance# 1 Summary info:--------------------------------------Name : PLASPA Version : 2

Port 0Jacket slot: 2 SPA type : SPA_NAME_UNKNOWNPort 1Jacket slot: 4 SPA type : 4xOC48 POS/RPR HHSPAPort 2Jacket slot: 5 SPA type : 8xGE SPA

IFName : POS0/1/0/0Inst# : 0 Port : 2RxLPORT : 0x80 TxLPORT : 0x48Uidb : 0x2 Key : 0x80Hkey : 209 Hkey idx : 0

IFName : POS0/1/0/1Inst# : 0 Port : 2RxLPORT : 0x81 TxLPORT : 0x49Uidb : 0x4 Key : 0x81Hkey : 28 Hkey idx : 0

IFName : POS0/1/0/2Inst# : 0 Port : 2RxLPORT : 0x82 TxLPORT : 0x4aUidb : 0x6 Key : 0x82Hkey : 183 Hkey idx : 0

--More--



OL-17332-01


1. Universal interface descriptor block

Table 17 show controllers plim asic summary Field Descriptions

Field Description

Node Node whose information is displayed. Information is displayed for each node’s SPA and its interfaces.

Instance PLIM ASIC identifier. This is the PLIM ASIC associated with the specified location.

Summary info (for SPA) Displays the following info for all SPAs installed in the router:

• Name—Identifies the SPA.whose information is displayed.

• Version—Version identifier for the PLIM ASIC.

• Jacket slot—Identifies the slot containing the jacket card for the specified SPA.

• SPA type —Describes the SPA whose information is displayed.

• Port—Port associated with the PLIM ASIC.

• Inst#—SPA ASIC instance Identifier.

Summary info (for interfaces) Displays the following info for all interfaces associated with the specified SPA:

• Intf name—Identifies the SPA.whose information is displayed.

• Inst#—ASIC associated with this interface.

• Port—Port associated with the PLIM ASIC.

• RxLPORT—Receive port, in hexadecimal format.

• TxLPORT—Transmit port, in hexadecimal format.

• Uidb—UIDB1 assigned by the software, in hexadecimal format.

• Key—AISC key, in hexadecimal format.

• Hkey—ASIC registry key.

• Hkey idx—ASIC registry key index.

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers pse eio links


OL-17332-01

show controllers pse eio linksTo display packet switching engine (PSE) information for Elastic I/O (EIO) links, use the show controllers pse eio links command in EXEC mode.

show controllers pse eio links {link-number | all} [location node-id]

Syntax Description


Command Modes EXEC

Command History


links link-number Displays PSE information for the specified link. Replace the link_number argument with a link number in the range from 0 to 4294967295.

Note Use the show controllers pse eio links all location node-id command to display all available EIO link IDs on a node.

links all Displays PSE information for all links on the specified node.

location node-id (Optional) Displays all EIO links on a specific node only. The node-id argument is expressed in the rack/slot/module notation.









Release 3.6.0 The link-number argument range of 1 through 4294967295 has changed to 0 to 4294967295.





OL-17332-01

Task ID

Examples The following is sample output from the show controllers pse eio links command for a specific EIO link:

RP/0/RP0/CPU0:router# show controllers pse eio links 50 location 0/0/CPU0

Node: 0/0/CPU0:----------------------------------------

EIO link: 50-------------------------------------------------------------------ASIC Id Peer Id Type Link-Id Attempts Accept Failed State-------------------------------------------------------------------PSE_1 FABRICQ_0 RX 50 1 1 0 EIO_LINK_TRAINED-------------------------------------------------------------------Macro-id Windage Diag status-------------------------------------------------------------------0 4 0x00001 4 0x00002 4 0x00003 4 0x0000-------------------------------------------------------------------


Task ID Operations

drivers read

interface read

Table 18 show controllers pse eio links Field Descriptions

Field Description

Node Node whose PSE information is displayed.

EIO link EIO link whose information is displayed.

ASIC Id ASIC associated with this EIO link.

Peer Id ASIC of the remote peer of this EIO link.

Type Indicates whether this link is receiving or transmitting (re)training requests.

Link-Id Unique ID assigned by the system to the EIO link.

Attempts Number of consecutive EIO training requests for the link made by the PSE driver to the peer.

Note Typically, the PSE driver at the receive end of a link initiates the training of that EIO link. Therefore, the EIO links whose PSE driver is at the transmit end show a value of 0 for the Attempts field, even though those links are in the EIO_LINK_TRAINED state.



OL-17332-01

Related Commands

Accept Number of PSE driver requests for training that were accepted by the peer. When a PSE driver request is accepted, training is started.

Note Typically, the PSE driver at the receive end of a link initiates the training of that EIO link. Therefore, the EIO links whose PSE driver is at the transmit end show a value of 0 for the Accept field, even though those links are in the EIO_LINK_TRAINED state.

Failed Number of times the training for this link failed for any reason.

State Current state of the EIO link.

Macro-id Windage Diag status Windage value used for the training, and the final status of the training for that windage.

Note The Macro-id Windage Diag status field is displayed only when you ask EIO info for specific link.

Table 18 show controllers pse eio links Field Descriptions (continued)

Field Description


Displays PSE device information for IP connections, or for a specific IPC controller.




Displays PSE statistics for a specific controller instance, or for a specific node.



ASIC Driver Commands on Cisco IOS XR Softwareshow controllers pse ipc


OL-17332-01

show controllers pse ipc To display packet switching engine (PSE) device information for interprocess communication (IPC) connections, or for a specific IPC controller, use the show controllers pse ipc command in EXEC mode.

show controllers pse ipc {client-connection {connID | all} | cpuctrlif} [egress | ingress] [location node-id]

Syntax Description


Command Modes EXEC

client-connection connID Displays IPC information about the specified client connection. Replace the connID argument with the client connection ID. Range is from 0 to 255.

client-connection all Displays IPC information about the all client connection.

cpuctrlif Displays IPC information about the specified PSE IPC CPU controller instance.

egress (Optional) Displays IPC information for the egress PSE device.

Note Follow the egress argument with the location node-id keyword and argument to restrict the command to a specific node containing the specified device instance.

ingress (Optional) Displays IPC information for the ingress PSE device.

Note Follow the ingress argument with the location node-id keyword and argument to restrict the command to a specific node containing the specified device instance.

location node-id (Optional) Identifies the location of the node whose PSE device information you want to display. The node-id argument is expressed in the rack/slot/module notation.


Note Include the egress or ingress argument before thelocation node-id keyword and argument to restrict the command to a specific device instance on the specified node.



OL-17332-01

Command History


To display client connection IPC information for a specific device instance, include the egress or ingress argument with the command, as shown in the following examples:

show controllers pse ipc client-connection connId egressshow controllers pse ipc client-connection connId ingress

To display client connection IPC information for a specific node location, include the location node-id keyword and argument with the command, as shown in the following example:

show controllers pse ipc client-connection connId location node-id

Task ID

Examples The following command shows how to display PSE information for a specific IPC client-connection:

RP/0/RP0/CPU0:router# show controllers pse ipc client-connection 13

Node: 0/0/CPU0:----------------------------------------

PSE IPC Conn Info:-------------------------------------------------ConnId: 13 (Backdoor)ConnOptions: 0Clinfos: 0x482bf9f8 (Notif) 0 (Reply)ConnStateFlags: 0ConnNotifFlags: 0SendReqs: 0 (iHP) 4 (iNP) 0 (eHP) 0 (eNP)SendFiltered: 0 (iHP) 0 (iNP) 0 (eHP) 0 (eNP)SendFailed: 0 (iHP) 0 (iNP) 0 (eHP) 0 (eNP)







Release 3.5.0 The instance {0 | 1} keywords were replaced by the egress and ingress keywords.

Release 3.6.0 The connID argument range of 1 to 255 has changed to 0 to 255.



Task ID Operations

interface read

drivers read



OL-17332-01

RecvReqs: 0RecvReqTouts: 0RecvDatTouts: 0RecvQState: 0/16

Node: 0/3/CPU0:----------------------------------------

PSE IPC Conn Info:-------------------------------------------------ConnId: 13 (Backdoor)ConnOptions: 0Clinfos: 0x482bf9f8 (Notif) 0 (Reply)ConnStateFlags: 0ConnNotifFlags: 0SendReqs: 0 (iHP) 4 (iNP) 0 (eHP) 0 (eNP)SendFiltered: 0 (iHP) 0 (iNP) 0 (eHP) 0 (eNP)SendFailed: 0 (iHP) 0 (iNP) 0 (eHP) 0 (eNP)RecvReqs: 0RecvReqTouts: 0RecvDatTouts: 0RecvQState: 0/16


Table 19 show controllers pse ipc client-connection Field Descriptions

Field Description

ConnId Connection identifier.

ConnOptions Connection bind time options requested by the client creating this connection.

Clinfos Client information (clinfo) index number. The memory database is organized as a table of clinfos, which are indexed by the region id and maintained in shared memory.

ConnStateFlags Bitmask containing the current state of the connection.

ConnNotifFlags Bitmask of the types of notifications that the client creating this connection has registered for.

SendReqs Number of PSE IPC send requests that client has made on this connection.

SendFiltered Number of send requests that were filtered out (dropped) from the PSE driver due to any internal filter policy.

SendFailed Number of send requests that could not be handled by the PSE driver due to error conditions such as hardware I/O failures, lack of buffering space, and so forth.

RecvReqs Number of data receive requests that the client has made on this connection.

RecvReqTouts Number of data receive requests from the client that timed out because no data was received from PSE device.



OL-17332-01

The following command shows how to display PSE information for a specific IPC controller connection:

RP/0/RP0/CPU0:router# show controllers pse ipc cpuctrlif

Node: 0/0/CPU0:----------------------------------------

Pse IPC cpuctrl if Information-------------------------------------------------Cpuctrl interface is upNormal Priority Tx I/F: BufBase 0x112190 BufSize 32768 PadBufp 0xec0af118 Seqnum 854 RORegNum 10 RORegVal 0x49f0 WORegNum 2 WORegVal 0x49f0 CDMACh 0 CDMAQ 3 HoldQ 0/512 CDMAPendQ 0/128 UnackQ 0/256 NumEnqs 854 NumRejs 0 NumDmaReqFails 0 NumDmaPendFails 0 NumMbxSpcFails 0 NumHldqOvflows 0Normal Priority Rx I/F: NumPDMAEntries 64 NumEnqs 15 NumRejs 0

Pse IPC cpuctrl if Information-------------------------------------------------Cpuctrl interface is upNormal Priority Tx I/F: BufBase 0x112190 BufSize 32768 PadBufp 0xec0af14c Seqnum 424 RORegNum 10 RORegVal 0x1c60 WORegNum 2 WORegVal 0x1c60 CDMACh 1 CDMAQ 3 HoldQ 0/512 CDMAPendQ 0/128 UnackQ 0/256 NumEnqs 424 NumRejs 0 NumDmaReqFails 0 NumDmaPendFails 0 NumMbxSpcFails 0 NumHldqOvflows 0Normal Priority Rx I/F: NumPDMAEntries 64 NumEnqs 2 NumRejs 0

Node: 0/3/CPU0:----------------------------------------

Pse IPC cpuctrl if Information-------------------------------------------------Cpuctrl interface is upNormal Priority Tx I/F: BufBase 0x112190 BufSize 32768 PadBufp 0xec0af118 Seqnum 833 RORegNum 10 RORegVal 0xdb8 WORegNum 2 WORegVal 0xdb8 CDMACh 0 CDMAQ 3 HoldQ 0/512 CDMAPendQ 0/128 UnackQ 0/256 NumEnqs 833 NumRejs 0 NumDmaReqFails 0 NumDmaPendFails 0 NumMbxSpcFails 0 NumHldqOvflows 0Normal Priority Rx I/F: NumPDMAEntries 64 NumEnqs 9 NumRejs 0

RecvDatTouts Number of times data was received from PSE device, but timed out because there was no receive request from client to pick up that data from the connection.

RecvQState Current state of the internal data receive FIFO queue. The internal data receive FIFO queue buffers data arriving from the PSE device for the connection, until the client sends a receive request for that data. The RecvQState is expressed in the X/Y notation, where X is current depth of the queue, and Y is the maximum depth allowed for the queue.

Table 19 show controllers pse ipc client-connection Field Descriptions (continued)

Field Description



OL-17332-01

Pse IPC cpuctrl if Information-------------------------------------------------Cpuctrl interface is upNormal Priority Tx I/F: BufBase 0x112190 BufSize 32768 PadBufp 0xec0af14c Seqnum 409 RORegNum 10 RORegVal 0x5f70 WORegNum 2 WORegVal 0x5f70 CDMACh 1 CDMAQ 3 HoldQ 0/512 CDMAPendQ 0/128 UnackQ 0/256 NumEnqs 409 NumRejs 0 NumDmaReqFails 0 NumDmaPendFails 0 NumMbxSpcFails 0 NumHldqOvflows 0Normal Priority Rx I/F: NumPDMAEntries 64 NumEnqs 2 NumRejs 0



OL-17332-01


Related Commands

Table 20 show controllers pse ipc cpuctrlif Field Descriptions

Field Description

Cpuctrl interface is up

Cpuctrl interface is down

Whether the connection is currently up or down.

Normal Priority Tx I/F Displays the following transmit buffer information for the connection:

• BufBase

• BufSize

• PadBufp

• Seqnum

• RORegNum

• RORegVal

• WORegNum

• WORegVal

• CDMACh

• CDMAQ

• HoldQ

• CDMAPendQ

• UnackQ

• NumEnqs

• NumRejs

• NumDmaReqFails

• NumDmaPendFails

• NumMbxSpcFails

• NumHldqOvflows

Normal Priority Rx I/F: Displays the following receive buffer information for the connection:

• NumPDMAEntries

• NumEnqs

• NumRejs


Displays PSE information for EIO (Elastic I/O) links or for a specific controller.




Displays PSE statistics for a specific controller instance or for a specific node.



ASIC Driver Commands on Cisco IOS XR Softwareshow controllers pse mp


OL-17332-01

show controllers pse mp To display packet switching engine (PSE) information for the maintenance processor on a specific controller or node, use the show controllers pse mp command in EXEC mode.

show controllers pse mp [egress | ingress] [location node-id]

Syntax Description


Command Modes EXEC

Command History

egress (Optional) Displays information for the egress PSE device only.

Note Follow the egress argument with the location node-id keyword and argument to restrict the command to a specific node.

ingress (Optional) Displays information for the ingress PSE device only.

Note Follow the ingress argument with the location node-id keyword and argument to restrict the command to a specific node.



Note Include the instance {0 | 1} argument before thelocation node-id keyword and argument to restrict the command to a specific device instance on the specified node.













OL-17332-01


The instance and location optional keywords are not mutually exclusive. The instance keyword directs the command to a specific PSE device, and the location keyword directs the command to that device or devices on the specified modular services card. You can specify the instance and location options together in the same command. If you do not specify the instance {0 | 1} and location node-id keywords and argument, the show controllers pse mp command takes effect on both device instances on all modular services cards.

Task ID

Examples The following command shows how to display PSE maintenance processor information for a specific controller instance:

RP/0/RP0/CPU0:router# show controllers pse mp instance 1

Node: 0/0/CPU0:----------------------------------------

PSE 1, MP Info:-------------------------------------------------MIPC Subtask Context Information High Priority MIPC Mbox Info NumProc 0 NumUnsupp 0 NxtSeqNum 0 NumOOSeq 0 Norm Priority MIPC Mbox Info NumProc 429 NumUnsupp 0 NxtSeqNum 425 NumOOSeq 0 NumMsgsGtred 93 NumDMAErrDrops 5 NumGtrDisDrops 2MSTAT Subtask Context Information NumSegs 9 CntrsPerBrst 93 MinCycleMsecs 4000 --------- Seg[0] config ----------------- SegId 0 SegBeg 0 SegEnd 3071 ExpBeg 0 ExpEnd 0 ExpRate 0 CycBefExp 0 --------- Seg[1] config ----------------- SegId 1 SegBeg 3072 SegEnd 74239 ExpBeg 3072 ExpEnd 3072 ExpRate 0 CycBefExp 0 --------- Seg[2] config ----------------- SegId 2 SegBeg 74240 SegEnd 107007 ExpBeg 74240 ExpEnd 74240 ExpRate 0 CycBefExp 0 --------- Seg[3] config ----------------- SegId 3 SegBeg 107008 SegEnd 262143 ExpBeg 107008 ExpEnd 107008 ExpRate 0 CycBefExp 0 --------- Seg[4] config ----------------- SegId 4 SegBeg 262144 SegEnd 265215 ExpBeg 262144 ExpEnd 262144 ExpRate 0 CycBefExp 0 --------- Seg[5] config ----------------- SegId 5 SegBeg 265216 SegEnd 336383 ExpBeg 265216 ExpEnd 265216 ExpRate 0 CycBefExp 0 --------- Seg[6] config -----------------

Task ID Operations

interface read

drivers read



OL-17332-01

SegId 6 SegBeg 336384 SegEnd 442367 ExpBeg 336384 ExpEnd 336385 ExpRate 1 CycBefExp 1 --------- Seg[7] config ----------------- SegId 7 SegBeg 442368 SegEnd 458751 ExpBeg 442368 ExpEnd 442368 ExpRate 0 CycBefExp 0 --------- Seg[8] config ----------------- SegId 8 SegBeg 458752 SegEnd 491519 ExpBeg 458752 ExpEnd 458752 ExpRate 0 CycBefExp 0 CurrTokens 9 MaxTokens 44 MinTokens 11 CurrSeg 5 CurrCntr 289954 CntrsExp 66532 PktsExp 33266 DMAErrDrops 0 REDDrops 0 REDDelays 0 GtrDisDelays 0 CfgUpdsApp 1 SegUpdsApp 10 UpdsRej 0

Node: 0/3/CPU0:----------------------------------------

PSE 1, MP Info:-------------------------------------------------MIPC Subtask Context Information High Priority MIPC Mbox Info NumProc 0 NumUnsupp 0 NxtSeqNum 0 NumOOSeq 0 Norm Priority MIPC Mbox Info NumProc 416 NumUnsupp 0 NxtSeqNum 412 NumOOSeq 0 NumMsgsGtred 71 NumDMAErrDrops 4 NumGtrDisDrops 3MSTAT Subtask Context Information NumSegs 9 CntrsPerBrst 93 MinCycleMsecs 4000 --------- Seg[0] config ----------------- SegId 0 SegBeg 0 SegEnd 3071 ExpBeg 0 ExpEnd 0 ExpRate 0 CycBefExp 0 --------- Seg[1] config ----------------- SegId 1 SegBeg 3072 SegEnd 74239 ExpBeg 3072 ExpEnd 3072 ExpRate 0 CycBefExp 0 --------- Seg[2] config ----------------- SegId 2 SegBeg 74240 SegEnd 107007 ExpBeg 74240 ExpEnd 74240 ExpRate 0 CycBefExp 0 --------- Seg[3] config ----------------- SegId 3 SegBeg 107008 SegEnd 262143 ExpBeg 107008 ExpEnd 107008 ExpRate 0 CycBefExp 0 --------- Seg[4] config ----------------- SegId 4 SegBeg 262144 SegEnd 265215 ExpBeg 262144 ExpEnd 262144 ExpRate 0 CycBefExp 0 --------- Seg[5] config ----------------- SegId 5 SegBeg 265216 SegEnd 336383 ExpBeg 265216 ExpEnd 265216 ExpRate 0 CycBefExp 0 --------- Seg[6] config ----------------- SegId 6 SegBeg 336384 SegEnd 442367 ExpBeg 336384 ExpEnd 336415 ExpRate 1 CycBefExp 0 --------- Seg[7] config ----------------- SegId 7 SegBeg 442368 SegEnd 458751 ExpBeg 442368 ExpEnd 442368 ExpRate 0 CycBefExp 0 --------- Seg[8] config ----------------- SegId 8 SegBeg 458752 SegEnd 491519 ExpBeg 458752 ExpEnd 458752 ExpRate 0 CycBefExp 0 CurrTokens 5 MaxTokens 44 MinTokens 11 CurrSeg 6 CurrCntr 398633 CntrsExp 1064256 PktsExp 33258 DMAErrDrops 0 REDDrops 0 REDDelays 0 GtrDisDelays 0 CfgUpdsApp 1 SegUpdsApp 10 UpdsRej 0



OL-17332-01


Table 21 show controllers pse mp Field Descriptions

Field Description

MIPC Subtask Context Information

MIPC subtask information from the following mailboxes (queues):

• High Priority MIPC Mbox

• Norm Priority MIPC Mbox

Note The MIPC MBox is a chunk of the MP DMEM that receives MIPC messages. The Norm Priority mailbox has buffer of 32 KB, while the High Priority Mbox has an 8 KB buffer.

High Priority MIPC Mbox Info Mailbox (or queue) that receives high-priority MIPC messages. The following information is displayed for the High Priority MIPC Mbox:

• NumProc—Number of MIPC messages that have been processed.

• NumUnsupp—Number of unsupported MIPC messages.

• NxtSeqNum—Sequence number of the message with respect to other messages sent on the same MIPC channel.

• NumOOSeq—Number of MIPC messages that were received out of sequence.

Norm Priority MIPC Mbox info Mailbox (or queue) that receives normal-priority MIPC messages. The following information is displayed for the High Priority MIPC Mbox:

• NumProc—Number of MIPC messages that have been processed.

• NumUnsupp—Number of unsupported MIPC messages.

• NxtSeqNum—Identifies the sequence number of the message with respect to other messages sent on the same MIPC channel.

• NumOOSeq—Number of MIPC messages that were received out of sequence.

NumMsgsGtred Number of MIPC gather messages that have been processed.

NumDMAErrDrops Number of MIPC gather messages that were dropped due to DMA errors.

NumGtrDisDrops Number of MIPC gather messages that were dropped due to distribution errors.

MSTAT Subtask Context Information

MSTAT subtask information from the following queues:

• High Priority MIPC Mbox

• Norm Priority MIPC Mbox

The MIPC MBox is a chunk of the MP DMEM that receives MIPC messages. The Norm Priority mailbox has buffer of 32 KB, while the High Priority Mbox has an 8 KB buffer.



OL-17332-01

Related Commands show controllers pse eio links

Displays PSE information for EIO links, or for a specific controller.


Displays PSE device information for IPC connections, or for a specific IPC controller.




PSE displays a summary of PSE information for a specific controller or node.

ASIC Driver Commands on Cisco IOS XR Softwareshow controllers pse statistics


OL-17332-01

show controllers pse statistics To display packet switching engine (PSE) statistics for a specific controller instance, or for a specific node, use the show controllers pse statistics command in EXEC mode.

show controllers pse statistics [all] [egress | ingress] [location node-id]

Syntax Description

Defaults If you do not specify the egress or ingress and location node-id keywords and argument, the show controllers pse statistics command displays statistical information for both device instances on all modular services cards.

Command Modes EXEC

Command History

all (Optional) Displays all counters.

egress (Optional) Displays statistics for the egress PSE device only.


ingress (Optional) Displays statistics for the ingress PSE device only.

Note Follow the ingress argument with the location node-id keyword and argument to restrict the command to a specific node.



Note Include the egress or ingress keyword before the location node-id keyword and argument to restrict the command to a specific device instance on the specified node.








Release 3.6.0 The all keyword was changed from required to optional.



OL-17332-01


The optional egress or ingress and location keywords are not mutually exclusive. The egress and ingress keywords direct the command to specific PSE device, and the location keyword directs the command to that device or devices on the specified modular services card. You can specify the egress or ingress and location options together in the same command. If you do not specify the egress or ingress and location node-id keywords and argument, the show controllers pse statistics command displays statistical information for both device instances on all modular services cards.

Task ID

Examples The following command shows how to display PSE statistics for a specific controller instance:

RP/0/RP0/CPU0:router# show controllers pse statistics instance 0

Node: 0/0/CPU0:----------------------------------------

PSE 0, Statistics Info:-------------------------------------------------NULL_STATS_PTR : 0MPLS_FWD_STATS_MEM_OOR : 0LAYER2_LOW_PRIORITY : 0CDP : 0CONTROL : 0ARP : 0RARP : 0CGMP : 0LOOP : 0IPV4_OPTIONS : 0DROP_IPV4_LENGTH_ERROR : 0DROP_IPV4_CHECKSUM_ERROR : 0IPV4_TTL_ERROR : 0DROP_TCP_FLAG : 0DROP_ACL_NO_MATCH : 0UNKNOWN_PKT_TYPE : 0DROP_ERROR_DISTR : 0DROP_UNKNOWN_DISTR : 0PLU_EXCEPTION : 0IPV4_UNKNOWN_PLU_TYPE : 0IPV4_PLU_PUNT : 0IPV4_PLU_DROP_PKT : 0UNKNOWN_LAYER2 : 0




Task ID Operations

interface read

drivers read



OL-17332-01

IPV4_DF_SET_FRAG_NEEDED_PUNT : 0IPV4_FRAG : 0INCOMPLETE_ADJ_PUNT : 0UNKNOWN_IFIB : 0IPV4_MCAST_EMPTY_OLIST_COUNTER : 0IPV4_MCAST_MAX_COPIES_EXCEEDED_COUNTER : 0IPV4_MCAST_LAST_PACKET_TIME_WASTED_COUNTER : 0BAD_SKIP_GATHER : 0RP_PUNT : 0UNKNOWN_PUNT_REASON : 0DROP_BAD_RESOURCE_ERROR : 0IPV4_LOAD_INFO_DROP : 0DROP_IPV4_LINE_STATUS : 0DROP_PUNT_EXCEED_Q_THRESH : 0DROP_IPV6_LINE_STATUS : 0PLU_LEAF_UNTERMINATED : 0PLU_LEAF_UNUSED : 0PLU_LEAF_ECC : 0PLU_LEAF_NO_MATCH : 0PLU_LEAF_BAD_CHANNEL : 0PLU_LEAF_INVALID : 0QUEUE_THRESHOLD_DROP : 0DROP_IPV6_SANITY : 0DROP_IPV6_PLU : 0DROP_IPV6_UNKNOWN_PLU_TYPE : 0DROP_IPV6_LENGTH_ERROR : 0PUNT_IPV6_MISS_SRC_COMP : 0IPV6_LINK_LOCAL : 0IPV6_HOP_BY_HOP : 0IPV6_TTL_ERROR : 0IPV6_PLU_PUNT : 0IFIB_DROP : 0IPV4_MCAST_DROP_DF_PACKET : 0IPV6_TOO_BIG : 0IPV4_MCAST_DO_ALL_BUT_FWD : 0IPV4_NO_MATCH : 0GRE_NON_IPV4 : 0GRE_BAD_FLAGS : 0IPV4_TUNNEL_NOT_CONFIGD : 0MPLS_LOADINFO_DROP : 0IPV4_DOUBLE_TUNNEL : 0GLOBAL_IFHANDLE_TCAM_MISS : 0L2TP_COOKIE_MISMATCH : 0L2TP_TUNNEL_DOWN : 0RECIRCULATE_UIDB_INDEX : 0DUMMY_COUNTER : 2622348240762MPLS_LINE_STATUS_DN_DROP : 0MPLS_TTL_ERROR : 0MPLS_PLU_DROP_PKT : 0MPLS_INVALID_EXPNULL : 0MPLS_NOT_ENABLED_DROP : 0MPLS_UNSUPP_PLU_LABEL_TYPE : 0IPV6_MED_PRI : 0IPV4_TUNNEL_UNEXP_PHYSINTF_ADJ : 0IPV4_TUNNEL_UNEXP_TUNINTF_ADJ : 0IPV4_MCAST_DO_ALL : 0DROP_IPV4_L4HDR_LENGTH_ERROR : 0UNKNOWN_OSI : 0MPLS_PLU_ERROR : 0MPLS_PLU_NO_MATCH : 0MPLS_TTL_EXP_GEN_ICMP : 0MPLS_PLU_PUNT : 0MPLS_NON_IP_PKT_GT_MTU : 0MPLS_IPV4_DF : 0



OL-17332-01

DROP_L2TP_TOO_SHORT_ERROR : 0DROP_L2TP_TOO_LONG_ERROR : 0DROP_GRE_LENGTH_ERROR : 0DROP_IPIP_LENGTH_ERROR : 0DROP_PUNT_POL_EXCEED : 0IPV4_TUNNEL_FORUS : 0IPV4_PLU_RCV : 0IPV4_FRAG_TUNNEL_PUNT : 0IPV4MC_NO_MATCH : 0MPLS_IPV4_FRAGMENTED : 0MPLS_IPV4_PKT_WITH_OPT_NEEDS_FRAG : 0IPV4_CANNOT_FRAG : 0IPV4_NULL_RTE_DROP_PKT : 0IPV6_NULL_RTE_DROP_PKT : 0IPV4_OPTIONS_RSVP : 0IPV4_IGMP : 0IPV4_OPTIONS_PIM : 0PLIM_ASIC_HDR_ERROR : 0IPV6_PLU_RCV : 0IPV4_LOAD_INFO_PUNT : 0IPV6_LOAD_INFO_PUNT : 0IPV6_LOAD_INFO_DROP : 0RP_DEST_DROP : 0DROP_IPV6_ENABLE : 0PUNT_ACL_ICMP : 0PUNT_ACL_LOG : 0SAP_PUNT : 0MPLS_INCOMPLETE_ADJ : 0PKT_LARGE_PADDING_PUNT : 0

Node: 0/3/CPU0:----------------------------------------

PSE 0, Statistics Info:-------------------------------------------------NULL_STATS_PTR : 0MPLS_FWD_STATS_MEM_OOR : 0LAYER2_LOW_PRIORITY : 0CDP : 0CONTROL : 0ARP : 0RARP : 0CGMP : 0LOOP : 0IPV4_OPTIONS : 0DROP_IPV4_LENGTH_ERROR : 0DROP_IPV4_CHECKSUM_ERROR : 0IPV4_TTL_ERROR : 0DROP_TCP_FLAG : 0DROP_ACL_NO_MATCH : 0UNKNOWN_PKT_TYPE : 0DROP_ERROR_DISTR : 0DROP_UNKNOWN_DISTR : 0PLU_EXCEPTION : 0IPV4_UNKNOWN_PLU_TYPE : 0IPV4_PLU_PUNT : 0IPV4_PLU_DROP_PKT : 0UNKNOWN_LAYER2 : 0IPV4_DF_SET_FRAG_NEEDED_PUNT : 0IPV4_FRAG : 0INCOMPLETE_ADJ_PUNT : 0UNKNOWN_IFIB : 0IPV4_MCAST_EMPTY_OLIST_COUNTER : 0IPV4_MCAST_MAX_COPIES_EXCEEDED_COUNTER : 0



OL-17332-01

IPV4_MCAST_LAST_PACKET_TIME_WASTED_COUNTER : 0BAD_SKIP_GATHER : 0RP_PUNT : 0UNKNOWN_PUNT_REASON : 0DROP_BAD_RESOURCE_ERROR : 0IPV4_LOAD_INFO_DROP : 0DROP_IPV4_LINE_STATUS : 0DROP_PUNT_EXCEED_Q_THRESH : 0DROP_IPV6_LINE_STATUS : 0PLU_LEAF_UNTERMINATED : 0PLU_LEAF_UNUSED : 0PLU_LEAF_ECC : 0PLU_LEAF_NO_MATCH : 0PLU_LEAF_BAD_CHANNEL : 0PLU_LEAF_INVALID : 0QUEUE_THRESHOLD_DROP : 0DROP_IPV6_SANITY : 0DROP_IPV6_PLU : 0DROP_IPV6_UNKNOWN_PLU_TYPE : 0DROP_IPV6_LENGTH_ERROR : 0PUNT_IPV6_MISS_SRC_COMP : 0IPV6_LINK_LOCAL : 0IPV6_HOP_BY_HOP : 0IPV6_TTL_ERROR : 0IPV6_PLU_PUNT : 0IFIB_DROP : 0IPV4_MCAST_DROP_DF_PACKET : 0IPV6_TOO_BIG : 0IPV4_MCAST_DO_ALL_BUT_FWD : 0IPV4_NO_MATCH : 0GRE_NON_IPV4 : 0GRE_BAD_FLAGS : 0IPV4_TUNNEL_NOT_CONFIGD : 0MPLS_LOADINFO_DROP : 0IPV4_DOUBLE_TUNNEL : 0GLOBAL_IFHANDLE_TCAM_MISS : 0L2TP_COOKIE_MISMATCH : 0L2TP_TUNNEL_DOWN : 0RECIRCULATE_UIDB_INDEX : 0DUMMY_COUNTER : 2668152738279MPLS_LINE_STATUS_DN_DROP : 0MPLS_TTL_ERROR : 0MPLS_PLU_DROP_PKT : 0MPLS_INVALID_EXPNULL : 0MPLS_NOT_ENABLED_DROP : 0MPLS_UNSUPP_PLU_LABEL_TYPE : 0IPV6_MED_PRI : 0IPV4_TUNNEL_UNEXP_PHYSINTF_ADJ : 0IPV4_TUNNEL_UNEXP_TUNINTF_ADJ : 0IPV4_MCAST_DO_ALL : 0DROP_IPV4_L4HDR_LENGTH_ERROR : 0UNKNOWN_OSI : 0MPLS_PLU_ERROR : 0MPLS_PLU_NO_MATCH : 0MPLS_TTL_EXP_GEN_ICMP : 0MPLS_PLU_PUNT : 0MPLS_NON_IP_PKT_GT_MTU : 0MPLS_IPV4_DF : 0DROP_L2TP_TOO_SHORT_ERROR : 0DROP_L2TP_TOO_LONG_ERROR : 0DROP_GRE_LENGTH_ERROR : 0DROP_IPIP_LENGTH_ERROR : 0DROP_PUNT_POL_EXCEED : 0IPV4_TUNNEL_FORUS : 0



OL-17332-01

IPV4_PLU_RCV : 0IPV4_FRAG_TUNNEL_PUNT : 0IPV4MC_NO_MATCH : 0MPLS_IPV4_FRAGMENTED : 0MPLS_IPV4_PKT_WITH_OPT_NEEDS_FRAG : 0IPV4_CANNOT_FRAG : 0IPV4_NULL_RTE_DROP_PKT : 0IPV6_NULL_RTE_DROP_PKT : 0IPV4_OPTIONS_RSVP : 0IPV4_IGMP : 0IPV4_OPTIONS_PIM : 0PLIM_ASIC_HDR_ERROR : 0IPV6_PLU_RCV : 0IPV4_LOAD_INFO_PUNT : 0IPV6_LOAD_INFO_PUNT : 0IPV6_LOAD_INFO_DROP : 0RP_DEST_DROP : 0DROP_IPV6_ENABLE : 0PUNT_ACL_ICMP : 0PUNT_ACL_LOG : 0SAP_PUNT : 0MPLS_INCOMPLETE_ADJ : 0PKT_LARGE_PADDING_PUNT : 0


Related Commands

Table 22 show controllers pse statistics Field Descriptions

Field Description

Node Identifies the node whose PSE statistics are displayed. The node ID is expressed in the rack/slot/module notation.

PSE 0, Statistics Info Displays all statistics maintained by the PSE.









ASIC Driver Commands on Cisco IOS XR Softwareshow controllers pse summary


OL-17332-01

show controllers pse summaryTo display a summary of packet switching engine (PSE) information for a specific controller or node, use the show controllers pse summary command in EXEC mode.

show controllers pse summary [egress | ingress] [location node-id]

Syntax Description


Command Modes EXEC

Command History

egress (Optional) Displays information for the egress PSE device only.


ingress (Optional) Displays information for the ingress PSE device only.

Note Follow the ingress keyword with the location node-id keyword and argument to restrict the command to a specific node.



Note Include the instance {0 | 1} argument before the location node-id keyword and argument to restrict the command to a specific device instance on the specified node.











OL-17332-01


The optional egress or ingress and location keywords are not mutually exclusive. The egress and ingress keywords direct the command to specific PSE device, and the location keyword directs the command to that device or devices on the specified modular services card. You can specify the egress or ingress and location options together in the same command. If you do not specify the egress or ingress and location node-id keywords and argument, the show controllers pse summary command displays information for both device instances on all modular services cards.

Task ID

Examples The following command shows how to display a summary of PSE information for a specific controller instance:

RP/0/RP0/CPU0:router# show controllers pse summary ingress

Node: 0/0/CPU0:----------------------------------------

PSE 1, Summary Info:-------------------------------------------------IBM P/N : 47P0595 LotNum : D2300123SerialNum : 0x00001c BadPPECls : 0000Version : 1 CpuctrlPort : 6DeviceState : 0 (UP)StartupOpts : 00000000 MmappedBase : 0x60669000ClsDisMask : 0000 NFusedPPEs : 0 (0 hwf, 0 swf)MPUcodeName : /pkg/ucode/egress_mp_v1.mucodePPEUcodeName: /pkg/ucode/egress_turbo_pos_v1.mucodeINTR-Status : 00000000 INTR-Enable : 0x7ffffeNColdResets : 1 NWarmResets : 0NPPEUcDlds : 1 NResetRetry : 0NIntrtps : 1 NIntrptThrot: 0

Node: 0/3/CPU0:----------------------------------------

PSE 1, Summary Info:-------------------------------------------------IBM P/N : LotNum :SerialNum : 0xffffff BadPPECls : 0000Version : 3 CpuctrlPort : 6DeviceState : 0 (UP)




Task ID Operations

interface read

drivers read



OL-17332-01

StartupOpts : 00000000 MmappedBase : 0x60669000ClsDisMask : 0000 NFusedPPEs : 4 (0 hwf, 4 swf)MPUcodeName : /pkg/gsr/ucode/egress_mp_v3.mucodePPEUcodeName: /pkg/gsr/ucode/egress_turbo_pos_v3.mucodeINTR-Status : 00000000 INTR-Enable : 0x7ffffeNColdResets : 1 NWarmResets : 0NPPEUcDlds : 1 NResetRetry : 0NIntrtps : 1 NIntrptThrot: 0


Related Commands

Table 23 show controllers pse summary Field Descriptions

Field Description

Node Node whose PSE information is displayed.

IBM P/N IBM part number.

SerialNum Serial number of the node.

BadPPECls Number of bad PPECIs on the PSE.

Version PSE version.

CpuctrlPort Cpuctrl port associated with the PSE instance.

DeviceState Whether the node is up (active) or down (inactive).

StartupOpts Internal information about the PSE startup options.

MmappedBase Internal mapping information.

ClsDisMask Internal masking information.

NFusedPPEs Internal PPE information.

MPUcodeName Information about the MPU code.

PPEUcodeName Information about the PPEU code.

INTR-Status Internal status information.

INTR-Enable Internal enable information.

NColdResets Number of cold resets experienced by the router.

NWarmResets Number of warm resets experienced by the router.

NPPEUcDlds Internal information about the PSE.

NResetRetry Number of times the router attempted to reset itself.

NIntrtps Internal information about interrupts on the PSE.

NIntrptThrot Internal throttling information for the PSE.









ASIC Driver Commands on Cisco IOS XR Softwareshow packet-memory


OL-17332-01

show packet-memoryTo display information for packet memory, use the show packet-memory command in EXEC mode.

show packet-memory [location node-id]

Syntax Description

Defaults Displays information about all packet memory.

Command Modes EXEC

Command History


The show packet-memory command can be used to display the total number of packet and particle headers, along with the packet memory that is currently allocated in the system.

Task ID

location node-id (Optional) Displays detailed packet memory information for the designated node. The node-id argument is entered in the rack/slot/module notation.











Task ID Operations

basic-services read

ASIC Driver Commands on Cisco IOS XR Softwareshow packet-memory


OL-17332-01

Examples The following example shows how to display packet memory information:

RP/0/RP0/CPU0:router# show packet-memory

Packet memory statistics : ==========================Packet headers total: 32000, free: 32000, size: 448Particle Pools(8) Pool(0):total: 8000, free: 8000, size: 256 fallback: 0, region: 0 Pool(1):total: 4000, free: 3968, size: 512 fallback: 1, region: 0 Pool(2):total: 16, free: 16, size: 512 fallback: 2, region: 0 Pool(3):total: 8000, free: 7936, size: 768 fallback: 3, region: 0 Pool(4):total: 12800, free: 9172, size: 1648 fallback: 4, region: 0 Pool(5):total: 320, free: 320, size: 2560 fallback: 5, region: 0 Pool(6):total: 1600, free: 1088, size: 4608 fallback: 6, region: 0 Pool(7):total: 640, free: 640, size: 6240 fallback: 7, region: 0Particle clone total: 8000, free: 8000, size: 256Packet Feature Specific Variable (FSV) total: 16000, free: 16000, size: 88Packet trace total: 16384, free: 16384, size: 40


Table 24 show packet memory Field Descriptions

Field Description

Packet headers Data structure that defines and controls an aggregation of data structures, collectively known as a packet. Includes information about every packet in the system.

Particle Pools Data structure that describes a particle and may be chained to other particles in a linked list. Includes information about the actual data of the packet and other particle headers in this packet if present in this packet.

Particle clone Duplicate particle header that points to a previously allocated particle. Differs from a particle header in that a particle clone shares the particle with another particle header.

Packet Feature Specific Variable (FSV)

Scratch pad shared among the features in the packet path, listing hangs of the packet header.

Packet trace Data associated with the packet header to help tracing a packet in the system.


OL-17332-01

Fabric Management Commands on Cisco IOS XR Software

This module describes the Cisco IOS XR software commands used to monitor and control application-specific integrated circuit (ASIC) fabric queues for the Cisco XR 12000 Series Router line cards or Cisco CRS-1 modular services cards running Cisco IOS XR software.

Fabric Management Commands on Cisco IOS XR Softwareclear controller fabric statistics


OL-17332-01

clear controller fabric statisticsTo clear fabric plane statistics from the counters information table, use the clear controller fabric statistics command in administration EXEC mode.

clear controller fabric statistics plane [plane-id | all]

Syntax Description

Defaults Information for all planes is cleared.

Command Modes Administration EXEC

Command History


The clear controller fabric statistics command clears the fabric statistics for the specified fabric plane or all planes.

Task ID

plane plane-id (Optional) The fabric plane and plane ID. Range is from 0 to 7.

plane all (Optional) Specifies fabric statistics for all planes.











Task ID Operations

root-system read, write, execute

fabric read, write

Fabric Management Commands on Cisco IOS XR Softwareclear controller fabric statistics


OL-17332-01

Examples The following example shows how to clear all fabric plane statistics from the router:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# clear controller fabric statistics plane all

Fabric Management Commands on Cisco IOS XR Softwareclear controller fabricq statistics


OL-17332-01

clear controller fabricq statisticsOn linecards, RPs and DRPs, the fabricq ASICs receive the cells from the fabric planes and reassembles them into packets. To clear the statistics on fabricq ASICs, use the clear controller fabricq statistics command in EXEC mode.

clear controller fabricq statistics [instance asic_instance] [location node-id]

Syntax Description

Defaults The default is to enter the clear controller fabricq statistics command without any optional keyword arguments to clear ASIC statistics for all fabric queues on the router.

Command Modes EXEC

Command History


Only locations that contain a fabric queue ASIC can be specified for the location node-id.

This command is intended for use while performing special maintenance, test, or debugging procedures. It should not be necessary to use this command when fabric connectivity is performing normally.

instance asic_instance (Optional) Identifies the fabric queue instance whose ASIC statistics you want to clear. Range is from 0 to 3.

location node-id (Optional) Identifies a node on which to clear ASIC statistics for a specific fabric queue, or for all fabric queues. The node-id argument is entered in the rack/slot/module notation.








Release 3.6.0 The asic_instance argument range of 1 to 3 was changed to 0 to 3.



Fabric Management Commands on Cisco IOS XR Softwareclear controller fabricq statistics


OL-17332-01

Task ID

Examples The following example shows how to clear ASIC statistics on all fabric queues on the node located in 0/1/CPU0:

RP/0/RP0/CPU0:router# clear controller fabricq statistics location 0/1/CPU0

The following example shows how to clear ASIC statistics for a specific fabric queue on all nodes that are installed in the router:

RP/0/RP0/CPU0:router# clear controller fabricq statistics instance 2

The following example shows how to clear ASIC statistics for a specific fabric queue on a specific node:

RP/0/RP0/CPU0:router# clear controller fabricq statistics instance 2 location 0/1/CPU0

Related Commands

Task ID Operations

root-system execute

drivers read, write

Command Description

show controllers fabricq statistics Displays statistics about packet flow through the fabric queue ASIC.

Fabric Management Commands on Cisco IOS XR Softwareclear controller ingressq statistics


OL-17332-01

clear controller ingressq statisticsTo clear application-specific integrated circuit (ASIC) statics from the ingress fabric queue on a specific node, or on all nodes installed in the router, use the clear controller ingressq statistics command in EXEC mode.

clear controller ingressq statistics location node-id

Syntax Description

Defaults Enter the clear controller ingressq statistics command without the optional location node-id keyword and argument to clear the ASIC statistics from the ingress queues on all nodes that are installed in the router.

Command Modes EXEC

Command History


Only locations that contain a fabric queue ASIC can be specified for the node-id argument.

The clear controller ingressq statistics command is intended for use while performing special maintenance, test, or debugging procedures. You do not need to use this command when fabric connectivity is performing normally.

location node-id Identifies the node whose ASIC statistics you want to clear from the ingress fabric queue. The node-id argument is entered in the rack/slot/module notation.








Release 3.6.0 The location node-id keyword and argument were changed from optional to required.



Fabric Management Commands on Cisco IOS XR Softwareclear controller ingressq statistics


OL-17332-01

Task ID

The following example shows how to use the clear controller ingressq statistics command to clear all ASIC statistics in the ingress fabric queue from the location 0/1/CPU0:

RP/0/RP0/CPU0:router# clear controller ingressq statistics location 0/1/CPU0

Related Commands

Task ID Operations

drivers read, write

Command Description


Displays statistical information for the ingress queue ASIC.

Fabric Management Commands on Cisco IOS XR Softwareclear fabricq counters all


OL-17332-01

clear fabricq counters allTo clear all counters going to fabric and coming back from fabric associated with the fabric queue driver, use the clear fabricq counters all command in administration EXEC mode.

clear fabricq counters all location node-id

Syntax Description



Command History


Task ID

location node-id Identifies the node whose fabric counters you want to clear. The node-id argument is entered in the rack/slot/module notation.


Release 3.2 This command was introduced on the Cisco XR 12000 Series Router.



Release 3.5.0 The fabric taskID was removed from this command.




Task ID Operations

root-system read

Fabric Management Commands on Cisco IOS XR Softwareclear fabricq counters all


OL-17332-01

Examples The following example shows how to clear all fabricq counters for the location 0/1/CPU0:

RP/0/0/CPU0:router # adminRP/0/0/CPU0:router(admin)# clear fabricq counters all location 0/1/CPU0


show controllers fabricq frfab Displays from fabric statistics.

show controllers fabricq tofab Displays to fabric statistics.

Fabric Management Commands on Cisco IOS XR Softwareclear fabricq counters frfab


OL-17332-01

clear fabricq counters frfabTo clear the from fabric queue counters that are associated with the fabric queue driver, use the clear fabricq counters frfab command in administration EXEC mode.

clear fabricq counters frfab [all | error | packet] location node-id

Syntax Description

Defaults All from fabric queue driver counters are cleared for the specified location


Command History


Task ID

Examples The following example shows how to clear the from fabric queue counters for the location 0/1/CPU0:

RP/0/0/CPU0:router # adminRP/0/0/CPU0:router(admin)# clear fabricq counters frfab location 0/1/CPU0

all (Optional) Clears all counters.

error (Optional) Clears error counters.

packet (Optional) Clears packet counters.










Task ID Operations

root-system read

Fabric Management Commands on Cisco IOS XR Softwareclear fabricq counters frfab


OL-17332-01



Fabric Management Commands on Cisco IOS XR Softwareclear fabricq counters tofab


OL-17332-01

clear fabricq counters tofabTo clear the to fabric counters that are associated with the fabric queue driver, use the clear fabricq counters tofab command in administration EXEC mode.

clear fabricq counters tofab [all | error | packet] location node-id

Syntax Description

Defaults All to fabric queue driver counters are cleared for the specified location


Command History


Task ID

Examples The following example shows how to clear all to fabric queue counters for the location 0/1/CPU0:

RP/0/0/CPU0:router # adminRP/0/0/CPU0:router(admin)# clear fabricq counters tofab location 0/1/CPU0

all (Optional) Clears all counters.

error (Optional) Clears error counters.

packet (Optional) Clears packet counters.










Task ID Operations

root-system read

Fabric Management Commands on Cisco IOS XR Softwareclear fabricq counters tofab


OL-17332-01



Fabric Management Commands on Cisco IOS XR Softwarecontrollers fabric bundle port


OL-17332-01

controllers fabric bundle portTo put a specific switch fabric bundle port into the shut down state, use the controllers fabric bundle command in administration configuration mode. To return the switch fabric bundle port to an up state, use the no form of this command.

controllers fabric bundle port port-id shutdown

no controllers fabric bundle port port-id shutdown

Syntax Description


Command Modes Administration configuration

Command History


Task ID

Examples The following example shows put a switch fabric bundle port into the shut down state:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(config)# configureRP/0/RP0/CPU0:router(admin-config)# controllers fabric bundle port 0/1/CPU0/10 shutdown

port-id Identifies the switch fabric bundle port you want to put into the shutdown state. The port-id argument is entered in the rack/slot/module/port notation.

shutdown Puts the specified bundle port into a shutdown state.






Task ID Operations

fabric read, write

Fabric Management Commands on Cisco IOS XR Softwarecontrollers fabric plane oim


OL-17332-01

controllers fabric plane oimTo configure optical interface module (OIM) fabric plane properties, use the controllers fabric plane command in administration configuration mode. To return the OIM fabric plane properties to the default configuration, use the no form of this command.

controllers fabric plane plane-id oim {count {1 | 3} | width {1 | 2} | instance oim-instance location node-id | all}}

no controllers fabric plane plane-id oim {count {1 | 3} | width {1 | 2} | instance oim-instance location {node-id | all}}

Syntax Description



Command History

plane-id Identifies the fabric plane. Range is from 0 to 7.

count {1 | 3} Configures the number of OIMs used in this plane. Enter 1 to configure all cables in the plane to connect to the same OIM. Enter 3 to configure the cables from each fabric card to connect to different OIMs.

width {1 | 2} Width of OIMs in the current fabric plane. Enter 1 to indicate a single-width OIM that covers one slot only. Enter 2 to indicate a dual-width OIM that covers two slots.

instance {oim-instance}

Specifies the properties of a specific OIM. Range is from 0 to 2.

location node-id

Identifies the node whose OIM fabric plane properties you want to configure. The node-id argument is entered in the rack/slot/module notation.

location all Configures the OIM fabric plane properties on all nodes installed in the router.





Release 3.3.0 • The topology keyword was removed from the controllers fabric plane command syntax.

• The oim, count, width, and instance keywords were added to the controllers fabric plane command syntax.






Fabric Management Commands on Cisco IOS XR Softwarecontrollers fabric plane oim


OL-17332-01


Task ID

Examples The following example shows how to configure all cables in the fabric plane to connect to the same OIM:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# configureRP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 3 oim count 1

Task ID Operations

fabric read, write

Fabric Management Commands on Cisco IOS XR Softwarecontrollers fabric plane shutdown


OL-17332-01

controllers fabric plane shutdownTo shut down the state of a fabric plane, use the controllers fabric plane shutdown command in administration configuration mode. To disable the state of a fabric plane, use the no form of this command.

controllers fabric plane plane-id shutdown

no controllers fabric plane plane-id shutdown

Syntax Description

Defaults The controller fabric plane is not shut down, and data continues to flow through the plane.


Command History


Use the controllers fabric plane shutdown command to perform a graceful shutdown of the fabric plane before a fabric reconfiguration or fabric plane migration. This ensures that data is not flowing through the plane.

Task ID

plane-id Fabric plane identifier. Range is from 0 to 7.











Task ID Operations

fabric read, write

Fabric Management Commands on Cisco IOS XR Softwarecontrollers fabric plane shutdown


OL-17332-01

Examples The following example shows fabric plane 3 being shut down:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# configureRP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 3 shutdown

Fabric Management Commands on Cisco IOS XR Softwarecontrollers fabric rack


OL-17332-01

controllers fabric rackTo put the rack into installation mode so that no traffic is sent over the switch fabric, use the controllers fabric rack command in administration configuration mode. To enable traffic to be sent over the switch fabric, use the no form of this command.

controllers fabric rack rack_number install-mode

no controllers fabric rack rack_number install-mode

Syntax Description



Command History


rack_number Rack number. Range is from 0 to 17.

install-mode Puts the specified rack into installation mode, so that no traffic is sent over the switch fabric.








Fabric Management Commands on Cisco IOS XR Softwarecontrollers fabric rack


OL-17332-01

Task ID

Examples The following example shows how to put the rack into installation mode so that no traffic is sent over the switch fabric:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(config)# configureRP/0/RP0/CPU0:router(admin-config)# controllers fabric rack 1 install-mode

Task ID Operations

fabric read, write

Fabric Management Commands on Cisco IOS XR Softwarecontrollers fabric statistics collection


OL-17332-01

controllers fabric statistics collectionTo enable the collection of fabric statistics data and configure the interval at which statistics are collected, use the controllers fabric statistics collection command in administration configuration mode. To return the system to the default interval setting, use the no form of this command.

controllers fabric statistics collection {control [refresh] | interval seconds}

no controllers fabric statistics collection {control [refresh] | interval seconds}

Syntax Description

Defaults Control of fabric statistics data collection = enabled Interval= 30 seconds.


Command History


Task ID

control Enables fabric statistics data collection.

refresh (Optional) Causes the system to collect data immediately.

interval seconds Specifies the interval, in seconds, between collection of data for fabric statistics. Range is from 10 to 180 seconds. Default is 30 seconds.











Task ID Operations

fabric read, write

Fabric Management Commands on Cisco IOS XR Softwarecontrollers fabric statistics collection


OL-17332-01

Examples The following example shows statistic data collection on the fabric being disabled:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# configureRP/0/RP0/CPU0:router(admin-config)# controllers fabric statistics collection control disable

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric


OL-17332-01

show controllers fabricTo display fabric card information, use the show controllers fabric command in administration EXEC mode.

show controllers fabric [clock | csc-fpga | fab-clk | fab-control | sca | xbar]

Syntax Description

Defaults All fabric card information is displayed


Command History


Use the show controllers fabric command to display various registers associated with the fabric cards and state information associated with the fabric control software.

clock (Optional) Displays which fabric clock each slot is synchronized to and whether the clock is redundant or not.

csc-fpga (Optional) Displays registers associated with the csc-fpga on each fabric card (FC).

fab-clk (Optional) Displays registers associated with the fabric clock FPGA on all route processors (RPs), line cards (LCs), and FCs.

fab-control (Optional) Displays the state of all RPs, LCs, and FCs in the chassis from a fabric control software perspective.

sca (Optional) Displays registers associated with Scheduler Control ASIC on the CSC cards.

xbar (Optional) Displays registers associated with the Cross Bar (XBAR) ASIC on the clock scheduler card (CSC) and switch fabric card (SFC).









Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric


OL-17332-01

Task ID

Examples The following is sample output from the show controllers fabric clock command:

RP/0/0/CPU0:router# adminRP/0/0/CPU0:router(admin)# show controllers fabric clock

The Primary Clock for system is CSC_0System Fabric Clock is Redundant

Slot # Primary Clock Mode

3 CSC_0 Redundant4 CSC_0 Redundant5 CSC_0 Redundant11 CSC_0 Redundant12 CSC_0 Redundant15 CSC_0 Redundant16 CSC_0 Redundant17 CSC_0 Redundant18 CSC_0 Redundant19 CSC_0 Redundant20 CSC_0 Redundant

Task ID Operations

root-system read, write

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric bundle


OL-17332-01

show controllers fabric bundleTo display fabric card bundle information, use the show controllers fabric bundle command in administration EXEC mode.

show controllers fabric bundle {node-id [brief | detail] | all [brief | detail] | port port-id [brief | detail | statistics] | summary}

Syntax Description

Defaults Information is displayed for all fabric bundle ports on the router.


node-id Identifies a node whose fabric bundle information you want to display. The node-id argument is entered in the rack/slot/module notation.

Follow the node-id argument with one of the following optional keywords to display the data a specific format:

• brief—Displays brief information about the fabric bundle.

• detail —Displays detailed information about the fabric bundle.

brief (Optional) Displays brief information about the specified fabric bundle port or ports. This is the default.

detail (Optional) Displays detailed information about the specified fabric bundle port or ports.

all Displays bundle information for all fabric bundles.

Follow the all keyword with one of the following optional keywords to display the data in a specific format:

• brief—Displays brief information about the fabric bundles.

• detail —Displays detailed information about the fabric bundles.

port port-id Identifies a port whose fabric bundle information you want to display. The port-id argument is entered in the rack/slot/module/port notation.

Follow the port-id argument with one of the following optional keywords to display the data a specific format:

• brief—Displays brief information about the fabric bundle.

• detail —Displays detailed information about the fabric bundle.

• statistics —Displays fabric bundle statistics for the specified port.

statistics Displays fabric bundle statistics.

summary Displays summarized fabric bundle information.

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric bundle


OL-17332-01

Command History


Task ID

Examples The following is sample output from the show controllers fabric bundle command:

RP/0/0/CPU0:router# adminRP/0/0/CPU0:router(admin)# show controllers fabric bundle ?

WORD Bundle location <Rack>/<Slot>/<Module>/<Port#>all Show all fabric bundle ports.port Fabric bundle port optionsummary Show summary of bundle data








Task ID Operations

fabric read

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric connectivity


OL-17332-01

show controllers fabric connectivityTo display controller fabric connectivity information, use the show controllers fabric connectivity command in administration EXEC mode.

show controllers fabric connectivity {all | node-id} [brief | detail]

Syntax Description

Defaults Brief information about controller fabric connectivity is displayed.


Command History


Use the show controllers fabric connectivity command to monitor a modular services card as it sends data to the fabric or receives data from the fabric.

all Specifies all controller fabric ports.

node id Specifies the fabric port associated with the designated node. The node-id argument is entered in the rack/slot/module notation.

brief (Optional) Specifies brief information about controller fabric connectivity. This is the default.

detail (Optional) Specifies detailed information about controller fabric connectivity.













OL-17332-01

Task ID

Examples The following is sample output from the show controllers fabric connectivity command that displays fabric connectivity information in brief form for all resources:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# show controllers fabric connectivity all brief

Card In Tx Planes Rx Planes Monitored TotalPercent R/S/M Use 01234567 01234567 For (s) Uptime (s)Uptime-------------------------------------------------------------------------------0/2/CPU0 1 .1...... .1...... 20913 20913100.00000/RP0/CPU0 1 .1...... .1...... 20913 20913

The following is sample output from the show controllers fabric connectivity command that displays detailed fabric connectivity information for all resources:

RP/0/RP0/CPU0:router(admin)# show controllers fabric connectivity all

Card In Tx Planes Rx Planes Monitored Total Percent R/S/M Use 01234567 01234567 For (s) Uptime (s) Uptime-------------------------------------------------------------------------------0/1/CPU0 1 .1...... .1...... 8561 8561 100.00000/2/CPU0 1 .1...... .1...... 8561 8561 100.00000/RP1/CPU0 1 .1...... .1...... 8561 8561 100.0000

The following is sample output from the show controllers fabric connectivity command that displays fabric connectivity information for the modular services card on node 0/0/CPU0:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# show controller fabric connectivity 0/0/CPU0

Card In Tx Planes Rx Planes Monitored Total Percent R/S/M Use 01234567 01234567 For (s) Uptime (s) Uptime-------------------------------------------------------------------------------0/0/CPU0 1 .1...... .1...... 8805 8805 100.0000


Task ID Operations

fabric read

Table 25 show controllers fabric connectivity Field Descriptions

Field Description

Card R/S/M Identifies the fabric card, in the format rack/slot/module.

In Use Indicates the number of fabric ports that are in use on the card.

Tx Planes Indicates activity on the transmit fabric plane.

Rx Planes Indicates activity on the receive fabric plane.

Monitored For (s) Elapsed time in seconds since monitoring began.



OL-17332-01

Total Uptime Total uptime expressed in seconds.

Percent Uptime Percentage of time the card has been up since monitoring began.

Table 25 show controllers fabric connectivity Field Descriptions (continued)

Field Description

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric driver instance summary


OL-17332-01

show controllers fabric driver instance summaryTo obtain information about a specific Swtich Fabric Element (SFE) ASIC on a particular board, use the show controllers fabric driver instance summary command in administration EXEC mode.

show controller fabric driver {instance asic_instance} {backpressure | block | link-info | summary}{ location node-id}

Syntax Description



Command History


instance asic_instance

Specifies ASIC instance. The range is from 0 to 4294967295.

backpressure Displays detailed information for fabric back-pressure.

block Displays detailed information for ASIC block.

link-info Displays information for the ASIC transmit (Tx) and receiver (Rx) link port.

summary Displays summarized information about all fabric queue ASICs in the system.

location node Displays information for the fabric queue ASICs on a particular node.

Note Use the show platform command to see a list of all nodes currently installed in your system.









Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric driver instance summary


OL-17332-01

Task ID

Examples The following example shows how to obtain information about an SFE ASIC on a particular board from the router:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# show controllers fabric driver instance 5 summary location 0/SM0/SP

-------------------------------------------------------------------------

s3/0/SM0/SP/1 Summary :

-------------------------------------------------------------------------

Node ID:0/SM0/SP

Chip ID : 0x2024E049 PLD Version : 0000001E

Top Interrupt Status : 0x00000000 Top Interrupt Enable : 0000003F

Oper Status : UP Enable Status : ENABLE

Related Commands

Task ID Operations

fabric read

Command Description

show controllers fabric driver backpressure

Displays fabric back-pressure configuration for a specific SFE ASIC.

show controllers fabric driver block brm

Displays barrier state information for a specific SFE ASIC.

show controllers fabric driver block css Displays control cell store state information.

show controllers fabric driver link-info rx flap

Displays receiver link state flap information for a specific SFE ASIC.

show controllers fabric driver link-info rx topo

Displays receiver link state topology information for a specific SFE ASIC.

show controllers fabric driver link-info tx

Displays transmit link state flap information for a specific SFE ASIC.

show controllers fabric driver summary

Displays ASIC summary information.

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric fgid resource


OL-17332-01

show controllers fabric fgid resourceTo display information about the fabric resources that are allocated to specific secure domain router (SDR) fabric group IDs (FGIDs), use the show controllers fabric fgid resource command in administration EXEC mode.

show controllers fabric fgid resource {all | sdr Owner {all | application {CLI | GSP | LPTS} id fabric_fgid [elements number_of_fgids]}}

Syntax Description



Command History

all Displays FGID resource information for all SDRs on the current system.

sdr Owner Specifies the owner SDR.

all Displays information for all resources allocated to the specified SDRs.

application Displays information for a specific resource allocated to the owner SDRs. Follow the sdr Owner application keywords with one of the following keywords to specify a particular resource application:

• CLI

• GSP

• LPTS

CLI Displays command-line interface (CLI) information for the owner SDR.

GSP Displays Gateway Service Protocol (GSP) information for the owner SDR.

LPTS Displays Local Packet Transport Services (LPTS) information for the owner SDR.

id fabric_fgid Fabric FGID whose SDR resource information you want to display. Replace with an FGID. Range is from 0 to 1000000

elements number_of_fgids

(Optional) Number of fabric FGIDs to display in the command output. Replace the number_of_fgids arguments with the number of FGIDs to list in the command output. Range is from 1 through 1000000.









OL-17332-01


Use the show controllers fabric fgid resource command to verify the multicast resource ID for the fabric card multicast bit set.

Task ID

Examples The following example shows sample output from the show controllers fabric fgid resource command. In this example, LPTS information is displayed for the SDR owner FGID 1000:

RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show controllers fabric fgid resource sdr Owner application lpts id 1000 elements 1

====================================================Displaying FGID Info for:SDR: Owner APPLICATION : LPTS**** No FGID's allocated ****RP/0/RP0/CPU0:P1_CRS-8(admin)#show controllers fabric fgid resource sdr Owner $

====================================================Displaying FGID Info for:SDR: Owner APPLICATION : LPTS**** No FGID's allocated ****

The following example shows sample output from the show controllers fabric fgid resource command. In this example, fabric resource information is displayed for all SDRs in the system:RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show controllers fabric fgid resource all

====================================================Displaying FGID Info for:SDR: Owner APPLICATION : CLI**** No FGID's allocated ****

====================================================Displaying FGID Info for:SDR: Owner APPLICATION : GSP1024, 1025, 1026, 1027, 1028, 1029, 1030, 1031, 1032, 10331034, 1035, 1036, 1037, 1038, 1039, 1040, 1041, 1042, 10431044, 1045, 1046, 1047, 1048, 1049, 1050, 1051, 1052, 10531054, 1055, 1056, 1057, 1058, 1059, 1060, 1061, 1062, 10631064, 1065, 1066, 1067, 1068, 1069, 1070, 1071, 1072, 10731074, 1075, 1076, 1077, 1078, 1079, 1080, 1081, 1082, 10831084, 1085, 1086, 1087, 1088, 1089, 1090, 1091, 1092, 10931094, 1095, 1096, 1097, 1098, 1099, 1100, 1101, 1102, 11031104, 1105, 1106, 1107, 1108, 1109, 1110, 1111, 1112, 11131114, 1115, 1116, 1117, 1118, 1119, 1120, 1121, 1122, 11231124, 1125, 1126, 1127, 1128, 1129, 1130, 1131, 1132, 11331134, 1135, 1136, 1137, 1138, 1139, 1140, 1141, 1142, 11431144, 1145, 1146, 1147, 1148, 1149, 1150, 1151, 1152, 1153

Task ID Operations

fabric read



OL-17332-01

1154, 1155, 1156, 1157, 1158, 1159, 1160, 1161, 1162, 11631164, 1165, 1166, 1167, 1168, 1169, 1170, 1171, 1172, 1173

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric fgid statistics


OL-17332-01

show controllers fabric fgid statisticsTo display resource statistical information for the fabric group ID (FGID), use the show controllers fabric fgid statistics command in administration EXEC mode.

show controllers fabric fgid statistics {all | pool | sdr | system} [brief | detail]

Syntax Description

Defaults Brief information is displayed.


Command History


Use the show controllers fabric fgid statistics command to monitor FGID resource usage based on a system, pool, or client view.

all Specifies all FGID resource statistical information for the logical router and FGID resource pools.

sdr Specifies FGID resource statistics about the secure domain router (SDR).

pool Specifies FGID statistical information about the resource pool.

system Specifies FGID resource statistics for the entire physical router.

brief (Optional) Specifies brief information about FGIDs. This is the default.

detail (Optional) Specifies detailed information about FGIDs.













OL-17332-01

Task ID

Examples The following is sample output from the show controllers fabric fgid statistics command that displays resource statistics for the fabric FGID in detailed form with all resources activated:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# show controllers fabric fgid statistics all detail

Fabric FGID Resource Statistics Information:

System wide Fabric multicast resource statistics:

Total number of FGIDs in the system is 1000000 Current number of InUse FGIDs in the system is 500 High Water Mark of InUse FGIDs in the system is 500

Per SDR basis Fabric multicast resource statistics:

Secure Domain Router Name is Owner InUse FGIDs is 500 High Water Mark InUse FGIDs is 500

Per client basis FGID resource utilization:

Appl Appl Pool Current HighWater Mark Name ID ID InUse FGIDs InUse FGIDs------------------------------------------------------------------------------- CLI 0 2 0 0 LPTS 1 1 0 0 GSP 2 0 500 500

Per Pool basis Fabric multicast resource statistics:

Pool Identifier is 0 Pool Name is GSP Pool type is Dedicated The starting FGID of this pool is 1024 Total FGIDs of this pool is 10240 InUse FGIDs of this pool is 500 High Water Mark InUse FGIDs of this pool is 500

Pool Identifier is 1 Pool Name is LPTS Pool type is Dedicated The starting FGID of this pool is 11264 Total FGIDs of this pool is 32768 InUse FGIDs of this pool is 0 High Water Mark InUse FGIDs of this pool is 0

Pool Identifier is 2 Pool Name is COMMON Pool type is Shared The starting FGID of this pool is 44032 Total FGIDs of this pool is 955968 InUse FGIDs of this pool is 0 High Water Mark InUse FGIDs of this pool is 0

Task ID Operations

fabric read

root-system read, execute



OL-17332-01


Table 26 show controllers fabric fgid statistics Field Descriptions

Field Description

Total number of FGIDs in the system Total number of fabric FGIDs in the system.

Current number of Inused FGIDs in the system Total number of fabric FGIDs in use in the system.

High Water Mark of Inused FGIDs in the system Number of in-use fabric FGIDs at the highest point within the system.

Secure Domain Router Name Name of the SDR.

Inused FGIDs Inused (in-use) fabric FGID.

High Water Mark inused FGIDs Number of inused (in-use) FGIDs since monitoring started.

Appl Name Application name.

Appl ID Application ID.

Pool ID Pool ID.

Current InUsed FGIDs Current number of inused (in-use) FGIDs.

Pool Identifier Group pool identifier number.

Pool Name Group pool name.

Pool type Group pool type.

Total FGIDs of this pool Number of FGIDs in the pool.

Inused FGIDs of this pool Number of FGIDs inused (in-use) in the pool.

High Water Mark inused FGIDs of this pool Number of FGIDs in the pool since the start of monitoring.

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric fsdb-pla all


OL-17332-01

show controllers fabric fsdb-pla allTo display plane availability status information for all racks in the system, use the show controllers fabric fsdb-pla all command in administration EXEC mode.

show controllers fabric fsdb-pla all

Syntax Description This command has no arguments or keywords.



Command History


Use the show controllers fabric fsdb-pla all command to verify line card connectivity to the fabric planes.

Task ID

Examples The following example shows sample output from the show controllers fabric fsdb-pla all command:

RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show controllers fabric fsdb-pla all

Rack 0:=======

SrcGrp:0








Task ID Operations

fabric read

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric fsdb-pla all


OL-17332-01

01234567Multicast Mask 11111111Unicast Mask 11111111

Destination S3-Fabricq Reachability Mask Downloaded MaskAddress Mask SrcGrp:0 SrcGrp:001234567 01234567 01234567----------------------------------------------------------------------4 11111111 11111111 111111115 11111111 11111111 1111111112 11111111 11111111 1111111113 11111111 11111111 1111111124 11111111 11111111 1111111125 11111111 11111111 1111111130 11111111 11111111 1111111131 11111111 11111111 11111111:

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric link port


OL-17332-01

show controllers fabric link portTo display link information for a specific fabric port, use the show controllers fabric link port command in administration EXEC mode.

show controllers fabric link port {fabricqrx | ingressqtx | s1ro | s1rx | s1tx | s2rx | s2tx | s3rx | s3tx} {port | all} [brief | detail | state | statistics | summary]

Syntax Description

Defaults Enter the show controllers fabric link port command without specifying any of the optional parameters to display summarized fabric link information. This is the same information that is displayed when you include the brief option in the show controllers fabric link port command string.

fabricqrx Displays information for the fabric queue receive port.

ingressqtx Displays information for the ingress queue transmit port.

s1ro Displays information for the S1 Out-of-Band receive port.

The out of band ports connect the fabric planes together so that the flow control information collected within a fabric plane is distributed across all fabric planes. This is essential in controlling fabric congestion and the congestion location within fabric.

s1rx Displays information for the Stage 1 (S1) receive port. The S1 receive port distributes incoming traffic.

s1tx Displays information for the Stage 1 (S1) transmit port. The S1 transmit port distributes outgoing traffic.

s2rx Displays information for the Stage 2 (S2) receive port. The S2 receive port forwards incoming cells to Stage 3 (S3) port.

s2tx Displays information for the Stage 2 (S2) transmit port. The S2 transmit port forwards outgoing cells to Stage 3 (S3) transmit port.

s3rx Displays information about S3 receive port. The S3 receive port performs switching for incoming traffic.

s3tx Displays information about S3 transmit port. The S3 receive port performs switching for outgoing traffic.

port Specifies the port whose fabric link information you want to display. Replace the port argument with a port identifier. The port argument naming notation is in the rack/slot/module/asic/port format.

Note A slash between values is required as part of the port naming notation.

all Displays fabric link information for all specified ports.

brief (Optional) Displays summarized fabric link information.

detail (Optional) Specifies that the command output includes detailed fabric link information.

state (Optional) Displays the state of the specific fabric link.

statistics (Optional) Displays the fabric link statistics information.

summary (Optional) Displays summarized fabric link information.



OL-17332-01


Command History


Use the show controllers fabric link port command to check the health of fabric internal connections.

Task ID

Examples The following example shows partial sample output from the show controllers fabric link port command for all S1RO ports in the system:

RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show controllers fabric link port s1ro all

Flags: P - plane admin down, p - plane oper downC - card admin down, c - card oper downL - link port admin down, l - linkport oper downA - asic admin down, a - asic oper downB - bundle port admin Down, b - bundle port oper downI - bundle admin down, i - bundle oper downN - node admin down, n - node downo - other end of link down d - data downf - failed component downstreamm - plane multicast downSfe Port Admin Oper Down Other Near-end Far-endR/S/M/A/P State State Flags End Bport Bport------------------------------------------------------------------------------0/SM0/SP/0/0 UP UP 0/SM0/SP/1/150/SM0/SP/0/1 UP UP 0/SM1/SP/0/330/SM0/SP/0/2 UP UP 0/SM1/SP/1/330/SM0/SP/0/3 UP UP 0/SM2/SP/0/330/SM0/SP/0/4 UP UP 0/SM2/SP/1/330/SM0/SP/0/5 UP UP 0/SM3/SP/0/330/SM0/SP/0/6 UP UP 0/SM3/SP/1/330/SM0/SP/1/0 UP UP 0/SM0/SP/0/15









Task ID Operations

fabric read



OL-17332-01

0/SM0/SP/1/1 UP DOWN l Unused0/SM0/SP/1/2 UP UP Unused0/SM0/SP/1/3 UP DOWN l Unused0/SM0/SP/1/4 UP DOWN l Unused0/SM0/SP/1/5 UP DOWN l Unused0/SM0/SP/1/6 UP DOWN l Unused0/SM1/SP/0/0 UP UP 0/SM1/SP/1/150/SM1/SP/0/1 UP UP 0/SM0/SP/0/330/SM1/SP/0/2 UP UP 0/SM0/SP/1/330/SM1/SP/0/3 UP UP 0/SM2/SP/0/51--More--

The following example shows partial sample output from the show controllers fabric link port command with the detail keyword included in the command string:

RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show controllers fabric link port fabricqrx all detail

Flags: P - plane admin down, p - plane oper downC - card admin down, c - card oper downL - link port admin down, l - linkport oper downA - asic admin down, a - asic oper downB - bundle port admin Down, b - bundle port oper downI - bundle admin down, i - bundle oper downN - node admin down, n - node downo - other end of link down d - data downf - failed component downstreamm - plane multicast down

Sfe Port Admin Oper Down Sfe BP Port BP OtherR/S/M/A/P State State Flags Role Role End----------------------------------------------------------------0/1/CPU0/0/0 UP UP A A 0/SM0/SP/0/15---------------------------------------------------Link Type Pin1 Name Pin2 Name---------------------------------------------------CHASSIS G5 A4

Sfe Port Admin Oper Down Sfe BP Port BP OtherR/S/M/A/P State State Flags Role Role End----------------------------------------------------------------0/1/CPU0/0/1 UP UP A B 0/SM0/SP/0/39---------------------------------------------------Link Type Pin1 Name Pin2 Name---------------------------------------------------CHASSIS G19 A34

Sfe Port Admin Oper Down Sfe BP Port BP OtherR/S/M/A/P State State Flags Role Role End----------------------------------------------------------------0/1/CPU0/0/2 UP UP A A 0/SM0/SP/0/14--More--

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric plane


OL-17332-01

show controllers fabric planeTo display system fabric plane information, use the show controllers fabric plane command in administration EXEC mode.

show controllers fabric plane {plane-id | all} [statistics] [brief | detail]

Syntax Description

Defaults Brief information is displayed


Command History


Use the show controllers fabric plane command to monitor the fabric plane status, and the cell traffic and error statistics to or from the fabric plane.

plane-id Plane number. Range is from 0 to 7.

all Specifies that all information about system fabric planes is displayed.

statistics (Optional) Specifies statistical information for cell activity within the plane.

brief (Optional) Specifies brief information about the system fabric plane. This is the default.

detail (Optional) Specifies detailed information about the system fabric plane.













OL-17332-01

Task ID

Examples The following is sample output from the show controllers fabric plane command that displays system fabric plane information from all fabric planes:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# show controllers fabric plane all

Plane Admin Oper Down Total Down Id State State Flags Bundles Bundles ------------------------------------------------------ 0 UP DOWN p 0 0 1 UP UP 0 0 2 UP DOWN p 0 0 3 UP DOWN p 0 0 4 UP DOWN p 0 0 5 UP DOWN p 0 0 6 UP DOWN p 0 0 7 UP DOWN p 0 0

The following is sample output from the show controllers fabric plane command that displays system fabric plane statistics from fabric plane 1 in brief form:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# show controllers fabric plane 1 statistics brief

In Out CE UCE PEPlane Cells Cells Cells Cells Cells-------------------------------------------------------------------------------- 1 0 0 0 0 0

The following is sample output from the show controllers fabric plane command that displays system fabric plane statistics from fabric plane 1 in detailed form:

RP/0/RP0/CPU0:router(admin)# show controllers fabric plane 1 statistics detail

The fabric plane number is 1 Total number of providers for the statistics: 0 Total received data cells: 0 Total transmitted data cells: 0 Total received correctable errored cells: 0 Total received uncorrectable errored cells: 0 Total received parity error cells: 0 Total unicast lost cells: 0 Total multicast lost cells: 0 Last clearing of "show controller fabric plane" counters never

The following is sample output from the show controllers fabric plane command that displays system fabric plane statistics from the fabric for all planes in detailed form:

RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all statistics detail

The fabric plane number is 0 Total number of providers for the statistics: 0 Total received data cells: 0 Total transmitted data cells: 0 Total received correctable errored cells: 0 Total received uncorrectable errored cells: 0 Total received parity error cells: 0 Total unicast lost cells: 0

Task ID Operations




OL-17332-01

Total multicast lost cells: 0 Last clearing of "show controller fabric plane" counters never








OL-17332-01


Related Commands

Table 27 show controllers fabric plane Field Descriptions

Field Description

The fabric plane number is 1 Fabric plane ID number.

Total number of providers for the statistics Number of providers (sources) from which statistics were extracted.

Total received data cells Total of data cells that have been received.

Total received correctable errored cells Total number of cells with errors that can be corrected.

Total received uncorrectable errored cells Total number of cells with errors that cannot be corrected.

Total received parity error cells Total number of cells that have parity errors.

Total unicast lost cells Number of lost unicast cells.

Last clearing of “show controller fabric plane” counters

Indicates when the fabric plane counters were last cleared.

Command Description

show controllers fabric connectivity Displays controller fabric connectivity information.

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric rack all


OL-17332-01

show controllers fabric rack allTo display information about the fabric racks in the current system, use the show controllers fabric rack all command in administration EXEC mode.

show controllers fabric rack all [brief | detail]

Syntax Description

Defaults Use the show controllers fabric rack all command without including any of the optional syntax to display detailed information about all fabric card racks in the current system.


Command History


Use the show controllers fabric rack all command to display fabric rack topology information.

Task ID

brief (Optional) Displays summarized fabric rack information.

detail (Optional) Specifies that the command output includes detailed fabric rack information.








Task ID Operations

fabric read

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric rack all


OL-17332-01

Examples The following example shows sample output from the show controllers fabric rack all command:

RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show controllers fabric rack all

Rack Rack ServerNum Status Status---- ------ ------

0 NORMAL PRESENTRP/0/RP0/CPU0:router(admin)#

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric sfe


OL-17332-01

show controllers fabric sfeTo display information about a specific switch fabric element, use the show controllers fabric sfe command in administration EXEC mode.

show controllers fabric sfe {fabricq | ingressq | s1 | s2 | s3} {port | all} [backpressure | brief | detail]

Syntax Description

Defaults Use the show controllers fabric sfe command without specifying any of the optional parameters to display detailed information about a specified switch fabric element.


Command History

fabricq Displays information from the fabric queue for the switching fabric element.

ingressq Displays information from the ingress queue for the switching fabric element.

s1 Displays information about Stage 1 (S1) switch fabric elements. S1 elements distribute traffic.

s2 Displays information about Stage 2 (S2) switch fabric elements. S2 elements forward cells to Stage 3 (S3) elements.

s3 Displays information about S3 switch fabric elements. S3 elements perform switching.

port Specifies the port that owns the switch fabric element you want to display. Replace the port argument with the port number, in the rack/slot/module/ASIC/port format.

Note A slash between values is required as part of the port argument notation.

all Displays information about the switch fabric elements on all ports in the system.

backpressure (Optional) Displays back-pressure information for the specified switch fabric elements.

brief (Optional) Displays summarized information for the specified switch fabric elements.

detail (Optional) Includes detailed information about the specified switch fabric elements in the command output.







Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabric sfe


OL-17332-01


Task ID

Examples The following example shows sample output from the show controllers fabric sfe command:

RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show controllers fabric sfe fabricq all

Flags: P - plane admin down, p - plane oper downC - card admin down, c - card oper downL - link port admin down, l - linkport oper downA - asic admin down, a - asic oper downB - bundle port admin Down, b - bundle port oper downI - bundle admin down, i - bundle oper downN - node admin down, n - node downo - other end of link down d - data downf - failed component downstreamm - plane multicast down

Sfe Admin OperR/S/M/A State State----------------------------0/1/CPU0/0 UP UP0/1/CPU0/1 UP UP0/3/CPU0/0 UP UP0/3/CPU0/1 UP UP0/6/CPU0/0 UP UP0/6/CPU0/1 UP UP0/RP0/CPU0/0 UP UP0/RP1/CPU0/0 UP UP




Task ID Operations

fabric read

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq barriers


OL-17332-01

show controllers fabricq barriersTo verify that barriers are flowing through the fabricq ASICs, use the show controllers fabricq barriers command in administration EXEC mode. If no optional parameter is passed, this command displays the aggregated barrier information for all ASIC instances on all locations.

show controllers fabricq barriers [aggrbarr | illegal-state | inputbarr ] [instance asic_instance] [location node-id]

Syntax Description



Command History

aggrbarr (Optional) Displays ggregated barrier information. Command reads the number of aggregated barrier transitions on this node during a 1 second window for all barrier types, that is , unicast low priority (UCL), unicast high priority (UCH), multicast low priority (MCL) and multicast high priority (MCH).

Note A count of 0x00000000 at both times for any barrier type indicates a problem with the barrier flow.

illegal-state (Optional) Displays the number of illegal barrier states seen on all the input links since the registers were cleared last.

inputbarr (Optional) D isplays the barrier state that is being received on all links at the instant the command is executed.

asic_instance (Optional) Displays barrier information for a specific fabric queue ASIC. Replace the asic_instance argument with the instance that identifies the ASIC whose barrier information you want to display.

location node-id (Optional) Displays statistical information for the designated node. The node-id argument is entered in the rack/slot/module notation.









Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq barriers


OL-17332-01


Task ID

Examples The following is detailed sample output from the show controllers fabricq barriers command for location 0/1/CPU0:

RP/0/0/CPU0:router# adminRP/0/RP0/CPU0:router (admin)# show controllers fabricq barriers aggrbarr location 0/1/CPU0

Location : 0/1/CPU0Asic Instance : 0 Fabric Destination Address : 4 -------------------------------------------------------------------------Barrier Config : 0x6Barrier Timeout Threshold : 0x4830Barrier Mask : 0Interrupt Mask : 0x1fffeError Cause : 0-------------------------------------------------------------------------Time UCH UCL MCH MCL 1210200107 0x00000000 0x00000000 0x00000000 0x00000000.1210200109 0x00007A9F 0x00007AAA 0x00007AA8 0x00007ABF.-------------------------------------------------------------------------

Location : 0/1/CPU0Asic Instance : 1 Fabric Destination Address : 5 -------------------------------------------------------------------------Barrier Config : 0x6Barrier Timeout Threshold : 0x4830Barrier Mask : 0Interrupt Mask : 0x1fffeError Cause : 0-------------------------------------------------------------------------Time UCH UCL MCH MCL 1210200109 0x00000000 0x00000000 0x00000000 0x00000000.1210200110 0x00007AA7 0x00007A8C 0x00007A8A 0x00007A85.-------------------------------------------------------------------------

Task ID Operations


Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq block


OL-17332-01

show controllers fabricq blockTo display information about the current usage of packet buffers of various sizes, use the show controllers fabricq block command in administration EXEC mode.

show controllers fabricq block {errors | registers | summary}[type instance][location node-id]

Syntax Description



Command History


Task ID

errors Displays information about block errors.

registers Displays information about block registers.

summary Displays block summary information.

type instance Physical interface or a virtual interface.




Release 3.2 This command was introduced on the Cisco CRS-1router.





Release 3.7.0 The freequeue-manager keyword was added to this command.


Task ID Operations


Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq block


OL-17332-01

Examples The following is detailed sample output from the show controllers fabricq block command:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# sh controllers fabricq block summary freequeue-manager location 0/1/CPU$

Location: 0/1/CPU0 Asic instance: 0 Vital Bump-up 'Enabled', Non-vital Bump-up 'Enabled'+------------------------------------------------------------------------------+|Buff |Enabl|Flush| Buffer References | ||Size | | | Total | Current |LowWtMrk |Corruptd |VitalThr |Occupancy |+------------------------------------------------------------------------------+ 120 Yes No 527916 527880 527874 0 5279 30e42022 240 Yes No 77136 77100 77088 0 771 40e41023 480 Yes No 77136 77100 77094 0 771 40e42022 960 Yes No 133170 133134 133128 0 1331 30e42022 1920 Yes No 107400 107364 107358 0 1073 30e42022 3840 Yes No 19374 19338 19332 0 193 30e42022 7680 Yes No 19374 19338 19332 0 193 30e40024 15360 Yes No 21516 21480 21468 0 215 40e41023

Location: 0/1/CPU0 Asic instance: 1 Vital Bump-up 'Enabled', Non-vital Bump-up 'Enabled'+------------------------------------------------------------------------------+|Buff |Enabl|Flush| Buffer References | ||Size | | | Total | Current |LowWtMrk |Corruptd |VitalThr |Occupancy |+------------------------------------------------------------------------------+ 120 Yes No 527916 527880 527874 0 5279 30e42022 240 Yes No 77136 77100 77094 0 771 30e41023 480 Yes No 77136 77100 77094 0 771 40e42022 960 Yes No 133170 133134 133128 0 1331 30e40024 1920 Yes No 107400 107364 107358 0 1073 30e42022 3840 Yes No 19374 19338 19338 0 193 00240024 7680 Yes No 19374 19338 19338 0 193 00240024 15360 Yes No 21516 21480 21474 0 215 30e40024

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq drop


OL-17332-01

show controllers fabricq dropTo display the number of packets dropped to the fabric or from the fabric on a per-slot basis in the fabric queue driver, use the show controllers fabricq drop command in administration EXEC mode.

show controllers fabricq drop [detail] [location node-id]

Syntax Description

Defaults Information about packet drops for all route processors (RPs) on the router is displayed


Command History


Use the show controllers fabricq drop command to display statistics about packet drops. Specifying a location displays information only if that location is an RP. Use the detail keyword to display detailed output.

Note The show controllers fabricq drop command is typically used for debugging purposes.

Task ID

detail (Optional) Displays detailed statistical information.










Task ID Operations




OL-17332-01

Examples The following is detailed sample output from the show controllers fabricq drop command for location 0/1/CPU0:

RP/0/0/CPU0:router# adminRP/0/0/CPU0:router(admin)# show controllers fabricq drop detail location 0/1/CPU0

Location 0/1/0:

To Fabric dropped packets:-------------------------- Slot Tx-OVS Tx-NHB Tx-NPB Tx-QF Tx-LP Tx-DS Tx-MB Tx-DIS Tx-TotalLow Priority: 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 0 9 0 0 0 0 0 0 0 0 0 10 0 0 0 0 0 0 0 0 0 11 0 0 0 0 0 0 0 0 0 12 0 0 0 0 0 0 0 0 0 13 0 0 0 0 0 0 0 0 0 14 0 0 0 0 0 0 0 0 0 15 0 0 0 0 0 0 0 0 0mcast 0 0 0 0 0 0 0 0 0High Priority: 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 0 9 0 0 0 0 0 0 0 0 0 10 0 0 0 0 0 0 0 0 0 11 0 0 0 0 0 0 0 0 0 12 0 0 0 0 0 0 0 0 0 13 0 0 0 0 0 0 0 0 0 14 0 0 0 0 0 0 0 0 0 15 0 0 0 0 0 0 0 0 0mcast 0 0 0 0 0 0 0 0 0Legend: Tx-OVS: Drops due to oversized packets Tx-NHB: Drops due to missing packet header buffer Tx-NPB: Drops due to missing packet payload buffer Tx-QF: Drops because the queue is full Tx-LP: Drops because the packet is low priority Tx-DS: Drops because the destination slot is dead Tx-MB: Drop counter for packets transmitted over MBUS (Not supported) Tx-DIS: Drops because the tofab transmission is disabled

From Fabric dropped packets:---------------------------- Slot Rx-REF Rx-PKT Rx-DEC Rx-Total 0 0 0 0 0 1 0 0 0 0 2 0 0 0 0



OL-17332-01

3 0 0 0 0 4 0 0 0 0 5 0 0 0 0 6 0 0 0 0 7 0 0 0 0 8 0 0 0 0 9 0 0 0 0 10 0 0 0 0 11 0 0 0 0 12 0 0 0 0 13 0 0 0 0 14 0 0 0 0 15 0 0 0 0Legend: Rx-REF: Drops in the FPGA reassembly Rx-PKT: Drops due to invalid packet Rx-DEC: Drops due to decoding the packet


Table 28 show controllers fabricq drop Field Descriptions

Field Description

To Fabric dropped packets Displays statistics about the transmitted packets that were dropped.

Slot Slot that contains the fabric card whose statistics are displayed.

Tx-OVS Number of transmitted packets that were dropped because they were oversized.

Tx-NHB Number of transmitted packets that were dropped because they were missing a packet header buffer.

Tx-NPB Number of transmitted packets that were dropped because they were missing a packet payload buffer.

Tx-QF Number of transmitted packets that were dropped because the queue is full.

Tx-LP Number of transmitted packets that were dropped because they were low priority.

Tx-DS Number of transmitted packets that were dropped because the destination slot is dead.

Tx-MB Number of dropped transmitted packets that were sent over the Mbus.

Tx-DIS Number of transmitted packets that were dropped because the tofab transmission is disabled.

Tx-Total Total number of packets transmitted.

From Fabric dropped packets Displays statistics about the received packets that were dropped.

Slot Slot that contains the fabric card whose statistics are displayed.

Rx-REF Number of received packets that were dropped in the FPGA reassembly.

Rx-PKT Number of received packets that were dropped because they were invalid.



OL-17332-01

1. Optimized Voice Service

Related Commands

Rx-DEC Number of received packets that were dropped due to decoding.

Rx-Total Total number of received packets that were dropped.

Table 28 show controllers fabricq drop Field Descriptions (continued)

Field Description

Command Description

show controllers fabricq errors Displays information about errors.


show controllers fabricq output Displays information about to fabric output service.

show controllers fabricq queue Displays information about packet queues.

show controllers fabricq registers Displays information about chopper and assembler registers.


Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq eio


OL-17332-01

show controllers fabricq eioTo display the current state of all the elastic I/O (EIO) information from fabric ASICs to the neighboring ASICs--PSE, Ingress, and FIA, use the show controllers fabricq eio command in administration EXEC mode.

show controllers fabricq eio links {link id | all} location node-id

Syntax Description



Command History


Task ID

link id Displays one or more EIO link states.

Note The range of the link id argument is 0 to 4294967295.










Task ID Operations


Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq eio


OL-17332-01

Examples The following is detailed sample output from the show controllers fabricq eio command for location 0/1/CPU0:

RP/0/0/CPU0:router# adminRP/0/RP0/CPU0:router (admin)# show controllers fabricq eio links all location 0/1/CPU0

Node: 0/1/CPU0:----------------------------------------

EIO links:-------------------------------------------------------------------ASIC Id Peer Id Type Link-Id Attempts Accept Failed State-------------------------------------------------------------------FABRICQ_0 FIA_0 RX 30 1 1 0 EIO_LINK_TRAINEDFABRICQ_0 FIA_0 RX 32 1 1 0 EIO_LINK_TRAINEDFABRICQ_0 FIA_0 RX 34 1 1 0 EIO_LINK_TRAINEDFABRICQ_0 FIA_0 RX 36 1 1 0 EIO_LINK_TRAINEDFABRICQ_0 FIA_1 RX 40 1 1 0 EIO_LINK_TRAINEDFABRICQ_0 FIA_1 RX 42 1 1 0 EIO_LINK_TRAINEDFABRICQ_0 FIA_1 RX 44 1 1 0 EIO_LINK_TRAINEDFABRICQ_0 FIA_1 RX 46 1 1 0 EIO_LINK_TRAINEDFABRICQ_0 PSE_1 TX 50 0 0 0 EIO_LINK_TRAINEDFABRICQ_1 FIA_0 RX 31 1 1 0 EIO_LINK_TRAINEDFABRICQ_1 FIA_0 RX 33 1 1 0 EIO_LINK_TRAINEDFABRICQ_1 FIA_0 RX 35 1 1 0 EIO_LINK_TRAINEDFABRICQ_1 FIA_0 RX 37 1 1 0 EIO_LINK_TRAINEDFABRICQ_1 FIA_1 RX 41 1 1 0 EIO_LINK_TRAINEDFABRICQ_1 FIA_1 RX 43 1 1 0 EIO_LINK_TRAINED

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq errors


OL-17332-01

show controllers fabricq errorsTo display the count of hardware errors associated with the fabric queue driver, use the show controllers fabricq errors command in administration EXEC mode.

show controllers fabricq errors [location node-id]

Syntax Description

Defaults Information about errors for all route processors (RPs) on the router is displayed


Command History


Use the show controllers fabricq errors command to display statistics about hardware errors. Specifying a location displays information only if that location is a RP.

The show controllers fabricq errors command is intended for use while performing debugging procedures.

Task ID










Task ID Operations


Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq errors


OL-17332-01

Examples The following is sample output from the show controllers fabricq errors command for location 0/1/CPU0:

RP/0/0/CPU0:router# adminRP/0/0/CPU0:router(admin)# show controllers fabricq errors location 0/1/CPU0

Location 0/1/0:

ToFab Errors: Error Type Error Count Max Rate Rate Exceeded Count-----------------------------------------------------------SRAM Parity 0 2 0DMA Address 0 100 0DMA Size 0 100 0Fusilli Parity 0 2 0PCI TRANS64 0 2 0PCI Address 0 2 0


Related Commands

Table 29 show controllers fabricq errors Field Descriptions

Field Description

Error Count Number of errors of each type.

Max Rate Maximum number of errors of that type that can be received per second.

Rate Exceeded Count Number of times that error has exceeded the Max Rate.

When the rate is exceeded, the software may try to restart the fabric queue driver and associated ASICs or FPGAs to correct the problem.

Command Description

show controllers fabricq drop Displays information about packet drops.






Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq fabric-backpressure


OL-17332-01

show controllers fabricq fabric-backpressureTo display back-pressure information for the fabric queue ASICs, use the show controllers fabricq fabric-backpressure command in EXEC and administration EXEC mode.

show controllers fabricq fabric-backpressure [summary] [instance asic_instance] [location node-id]

Syntax Description

Defaults Enter the show controllers fabricq fabric-backpressure command without including any of the optional keywords or arguments to display detailed back-pressure information about all fabric queue ASICS in the system.

Command Modes EXEC

Administration EXEC

Command History


summary (Optional) Displays summarized back-pressure information about all fabric queue ASICS in the system.

instance asic_instance (Optional) Displays back-pressure information for a specific fabric queue ASIC. Replace the asic_instance argument with the instance that identifies the ASIC whose back-pressure information you want to display.

Note Enter the show controllers fabricq fabric-backpressure command without including any of the optional keywords or arguments to display all fabric queue ASIC instances in the system.

location node Displays back-pressure information for the fabric queue ASICs on a particular node. The node-id argument is entered in the rack/slot/module notation.

Note Use the show platform command to see a list of all nodes currently installed in your system.









OL-17332-01

On the fabricq ASICs, a BP Engine configured for each non-empty fabric group present in the system is shown as enabled Yes under the Enabled column on all fabricq ASICs in the system.

Task ID

Examples The following example shows sample output from the show controllers fabricq fabric-backpressure command when it is entered with the summary keyword:

RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show controllers fabricq fabric-backpressure summary

Rack 0: All Groups Received? : Yes

The following example shows sample output from the show controllers fabricq fabric-backpressure command when it is entered without any of the optional keywords:

RP/0/RP0/CPU0:router# admin RP/0/RP0/CPU0:router(admin)# show controllers fabricq fabric-backpressure

Location: 0/1/CPU0Asic Instance: 0Fabric Destination Address: 4BP global Configuration Register: 0xff07

Cluster Number: 0Primary Link: 0Secondary Link: 9Number of Backup links: 14Backup Links: 8 1 2 10 3 11 27 16 26 17 25 18 24 19BP enable Mask: 0x4BP EC: 0BP IM: 0x1ffe+-----------------------------------------------------------+|BP Engine| Enabled |Current Link |Rx group |P Link |S Link |+-----------------------------------------------------------+| 0 | No |Secondary | 255 | 0 | 9 |+-----------------------------------------------------------+| 1 | No |Secondary | 255 | 0 | 9 |+-----------------------------------------------------------+| 2 | Yes |Primary | 0 | 0 | 9 |+-----------------------------------------------------------+


Cluster Number: 0Primary Link: 0Secondary Link: 9Number of Backup links: 14Backup Links: 8 1 2 10 3 11 27 16 26 17 25 18 24 19BP enable Mask: 0x4BP EC: 0

Task ID Operations

fabric read

interface read

drivers read



OL-17332-01

BP IM: 0x1ffe+-----------------------------------------------------------+|BP Engine| Enabled |Current Link |Rx group |P Link |S Link |+-----------------------------------------------------------+| 0 | No |Secondary | 255 | 0 | 9 |+-----------------------------------------------------------+| 1 | No |Secondary | 255 | 0 | 9 |+-----------------------------------------------------------+| 2 | Yes |Primary | 0 | 0 | 9 |+-----------------------------------------------------------+


Cluster Number: 0--More--

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq frfab


OL-17332-01

show controllers fabricq frfabTo display output from the fabric statistics associated with the fabric queue driver, use the show controllers fabricq frfab command in administration EXEC mode.

show controllers fabricq frfab [detail | trace options] [location node-id]

Syntax Description

Defaults From fabric statistics are displayed for all route processors (RPs) on the router


Command History


trace options (Optional) Displays detailed fabric queue driver trace information for a specific node. Replace the options argument with one or more of the following keywords or keyword arguments to specify the type and format of trace information displayed:

• error—Includes tofab error trace information in the command output.

• file word original—Displays trace information for a specific file.

• hexdump—Displays trace information in hexadecimal format.

• last entries—Displays trace information for a specific number of entries. Replace the entries argument with the number of entries you want to display. For example, if you enter 5, the display shows the last 5 entries in the trace data.

• packet—Includes packet trace information in the command output.

• payload—Includes payload trace information in the command output.

• reverse—Displays the latest traces first.

• stats—Includes trace statistics in the command output.

• tailf—Includes new traces as they are added in the command output.

• unique—Includes unique trace entries with counts in the command output.

• verbose—Includes internal debugging information in the command output.

• wrapping—Includes wrapping entries in the command output.








OL-17332-01


Use the show controllers fabricq frfab command to display from fabric statistics. Specifying a location displays information only if that location is an RP. Use the detail keyword to display detailed output.

Note The show controllers fabricq frfab command is typically used for debugging purposes.

Task ID

Examples The following is sample output from the show controllers fabricq frfab command for location 0/1/CPU0:

RP/0/0/CPU0:router# adminRP/0/0/CPU0:router(admin)# show controllers fabricq frfab location 0/1/CPU0

Location 0/1/0:

From Fabric Stats:-------------------Slot Rx-pkts Rx-TH-pkts Rx-dropped1 0 3928 0 2 0 37309 0 3 0 43306 0 4 0 42681 0 5 0 35063 0

From Fabric Packet per Queue Stats:-----------------------------------Packets received in queue 0 - 0Packets received in queue 1 - 3928Packets received in queue 2 - 150069Packets received in queue 3 - 8290

From Fabric Error Stats:------------------------Bigger than MTU pkts - 0Corrupted pkts - 0SPD pkt count - 0No IDB drops - 0IDB queue tail drops - 0


Release 3.6.0 The trace keyword and options argument were added.




Task ID Operations




OL-17332-01

Chan corrupted pkts - 0First/Last err pkts - 0Sequence err pkts - 0Unknown Rx type - 0Output queue 0 full drops - 0Output queue 1 full drops - 0Output queue 2 full drops - 0Output queue 3 full drops - 0Output queue unmatch drops - 0OQ 0 drops because FQ below threshold - 0OQ 1 drops because FQ below threshold - 0OQ 2 drops because FQ below threshold - 0OQ 3 drops because FQ below threshold - 0

From Fabric Error Events:-------------------------Fusilli parity errors- 0 Fusilli interface errors - 0 Free queue drop threshold events - 0Free queue empty events - 0Bad descriptors events - 0Output queue 0 almost empty events - 0Output queue 1 almost empty events - 0Output queue 2 almost empty events - 0Output queue 3 almost empty events - 0OQ 0 drops because of ptr - 0 (Not implemented)OQ 1 drops because of ptr - 0 (Not implemented)OQ 2 drops because of ptr - 0 (Not implemented)OQ 3 drops because of ptr - 0 (Not implemented)Interrupt throttle events - 0Spurious interrupt events - 0

Assembler memory statistics: ----------------------------Bufs enqueued to free queue - 163311Bufs rxed from OQ - 162287Bufs copied to public pool - 0 (Not implemented)Bufs returned to the pool - 162287Bufs returned by driver - 0 (Not implemented)Bufs from driver to OS - 0 (Not implemented)


Table 30 show controllers fabricq frfab Field Descriptions

Field Description

Rx-pkts Number of packets received from the fabric.

Rx-TH-pkts Number of “think hard” packets received from the fabric.

Rx-dropped Number of packets received from the fabric that had to be dropped.



OL-17332-01








Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq link-info


OL-17332-01

show controllers fabricq link-infoTo display the state of the links on a fabricq ASIC, use the show controllers fabricq link-info command in administration EXEC mode.

show controllers fabricq link-info {link number | all } [instance asic_instance] [location node-id]

Syntax Description



Command History


The show controllers fabricq link-info command displays the state of the links on a fabricq ASIC. Any link that is connected to a plane that is not administratively down or to an fabric board that has been removed, should show as up under the columns Driver State, FSDB State and Barrier State. If the driver state is down, the column Errors would indicate the reason behind it. The column titled Drv Bar shows the number of times the driver attempted to bring up a link's driver state and barrier state.

Task ID

link number Link number. Range is from 0 to 31.

asic_instance (Optional) Displays health information for a specific fabric queue ASIC. Replace the asic_instance argument with the instance that identifies the ASIC whose health information you want to display.










Task ID Operations


Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq link-info


OL-17332-01

Examples The following is detailed sample output from the show controllers fabricq link-info command for location 0/1/CPU0:

RP/0/0/CPU0:router# adminRP/0/RP0/CPU0:router (admin)# show controllers fabricq link-info all location 0/1/CPU0

Location: 0/1/CPU0Asic Instance: 0Fabric Destination Address: 4Retry period: 0 secLink Active bitmap (1=up,0=down): 0xffffffff+------------------------------------------------------------------------+|Link #|Driver state | FSDB state |Barrier state|Up (Drv Barr)| Errors |+------------------------------------------------------------------------+| 0 | Up | Up | Up | 1 1 | || 1 | Up | Up | Up | 1 1 | || 2 | Up | Up | Up | 1 1 | || 3 | Up | Up | Up | 1 1 | || 4 | Up | Up | Up | 1 1 | || 5 | Up | Up | Up | 1 1 | || 6 | Up | Up | Up | 1 1 | || 7 | Up | Up | Up | 1 1 | || 8 | Up | Up | Up | 1 1 | || 9 | Up | Up | Up | 1 1 | || 10 | Up | Up | Up | 1 1 | || 11 | Up | Up | Up | 1 1 | || 12 | Up | Up | Up | 1 1 | || 13 | Up | Up | Up | 1 1 | |--More--

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq output


OL-17332-01

show controllers fabricq outputTo display the fabric output service statistics associated with the fabric queue driver, use the show controllers fabricq output command in administration EXEC mode.

show controllers fabricq output [location node-id]

Syntax Description

Defaults Information is displayed for all route processors (RPs) on the router..


Command History


Use the show controllers fabricq output command to display to fabric output service statistics. Specifying a location displays information only if that location is an RP.

The service time is the time from when the RP CPU has made the packet ready to be sent to the slot to when the Field-Programmable Gate Array (FPGA) has put the packet on the queue to that particular slot.

Note The show controllers fabricq output command is typically used for debugging purposes.

Task ID










Task ID Operations




OL-17332-01

Examples The following is sample output from the show controllers fabricq output command for location 0/1/CPU0:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# show controllers fabricq output location 0/1/CPU0

Location 0/1/0:

To Fabric servicing time statistics:------------------------------------ Slot Minimum Maximum Average TimeoutsLow Priority: 0 0 0 0 0 1 0 0 0 0 2 0 10 0 0 3 0 21 0 0 4 0 0 0 0 5 0 0 0 0 6 0 0 0 0 7 0 0 0 0 8 0 0 0 0 9 0 0 0 0 10 0 0 0 0 11 0 0 0 0 12 0 0 0 0 13 0 0 0 0 14 0 0 0 0 15 0 0 0 0 mcast 0 0 0 0High Priority: 0 0 0 0 0 1 0 22 0 0 2 0 96 0 0 3 0 13 0 0 4 0 12 0 0 5 0 14 0 0 6 0 0 0 0 7 0 0 0 0 8 0 0 0 0 9 0 0 0 0 10 0 0 0 0 11 0 0 0 0 12 0 0 0 0 13 0 0 0 0 14 0 0 0 0 15 0 0 0 0 mcast 0 6 0 0


Table 31 show controllers fabricq output Field Descriptions

Field Description

Slot Slot to which the packets are sent.

Minimum Lowest service time of all the packets sent to that slot.

Maximum Highest service time of all the packets sent to that slot.

Average Average service time of all the packets sent to that slot.

Timeouts Number of times a packet’s service time has exceeded a threshold of 200 milliseconds (the packet is dropped).



OL-17332-01








Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq queue


OL-17332-01

show controllers fabricq queueTo display information about the hardware queues of the performance route processor chopper and assembler FPGAs, use the show controllers fabricq queue command in administration EXEC mode.

On the Cisco CRS-1:

show controllers fabricq queue [instance instance-id] [location node-id]

On the Cisco XR 12000 Series Router:

show controllers fabricq queue [detail] [location node-id]

Syntax Description

Defaults Information for all performance route processors on the router is displayed


Command History


instance instance-id (Optional) Displays information about a specific ASIC. Replace the instance-id argument with an ASIC instance. Range is from 1 through 4.

Note The instance instance-id keyword and argument is available on the Cisco CRS-1 only.


Note The detail keyword is available on the Cisco XR 12000 Series Router only.



Release 3.2 This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.









OL-17332-01

Use the show controllers fabricq queue command to display information about packet queues. Specifying a location displays information only if that location is an RP.

This command is intended for use while performing debugging procedures.

Task ID

Examples The following is detailed sample output from the show controllers fabricq queue command for the location 0/1/CPU0 on the Cisco XR 12000 Series Router:

RP/0/0/CPU0:router# adminRP/0/0/CPU0:router(admin)# show controllers fabricq queue detail location 0/1/CPU0

Location 0/1/0:

To Fabric Queue Stats:---------------------- Slot EnQueued DeQueued Cur-Entrys Max-Entrys Blocked BP countLow Priority: 0 0 0 0 0 No 0 1 0 0 0 0 No 0 2 300 300 0 2 No 0 3 8428 8428 0 12 No 0 4 0 0 0 0 No 0 5 0 0 0 0 No 0 6 0 0 0 0 No 0 7 0 0 0 0 No 0 8 0 0 0 0 No 0 9 0 0 0 0 No 0 10 0 0 0 0 No 0 11 0 0 0 0 No 0 12 0 0 0 0 No 0 13 0 0 0 0 No 0 14 0 0 0 0 No 0 15 0 0 0 0 No 0 mcast 0 0 0 0 No 0High Priority: 0 0 0 0 0 No 0 1 7882 7882 0 2 No 0 2 62330 62330 0 36 No 0 3 60752 60752 0 100 No 0 4 72588 72588 0 36 No 0 5 60876 60876 0 100 No 0 6 0 0 0 0 No 0 7 0 0 0 0 No 0 8 0 0 0 0 No 0 9 0 0 0 0 No 0 10 0 0 0 0 No 0 11 0 0 0 0 No 0 12 0 0 0 0 No 0 13 0 0 0 0 No 0 14 0 0 0 0 No 0 15 0 0 0 0 No 0 mcast 19562 19562 0 200 No 0Free packet header buffers 7680From Fabric Queue Stats:----------------------- Queue Allocated Free

Task ID Operations




OL-17332-01

0 0 512 1 0 512 2 0 512 3 0 512 F/Q 87 937

The following is detailed sample output from the show controllers fabricq queue command for the location 0/1/CPU0 on Cisco CRS-1:

RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# show controllers fabricq queue location 0/1/CPU0

Fabric Queue Manager Queue Information:=======================================Location: 0/1/CPU0Asic Instance: 0Fabric Destination Address: 4CpuCtrl Cast range : 0 - 7Multicast Range : 16 - 71Unicast Quanta in KBytes : 58, Multicast Quanta : 14 +------------------------------------------------------------------------------+|Type/Ifname |Port|Queue| Q |P-quanta|Q-quanta|HighW |LowW |Q Len |BW || | num| num |pri| KBytes | KBytes |KBytes|KBytes|KBytes |(kb|+------------------------------------------------------------------------------+|Cpuctrl Cast | 0|0 - 7| HI| 13| 13| 1021| 919| 0| ||Multicast | 0| 17| BE| 13| 13| 26214| 23592| 0| ||Multicast | 0| 18| AF| 13| 13| 26214| 23592| 0| ||Multicast | 0| 20| HI| 13| 1905| 26214| 23592| 0| ||POS0/1/4/0 | 1| 129| BE| 13| 450| 1755| 1578| 0|239||POS0/1/4/0 | 2| 257| AF| 13| 450| 1755| 1578| 0|239||POS0/1/4/0 | 4| 513| HI| 1905| 450| 1755| 1578| 0|239||POS0/1/0/0 | 1| 130| BE| 13| 30| 109| 98| 0| 14||POS0/1/0/0 | 2| 258| AF| 13| 30| 109| 98| 0| 14||POS0/1/0/0 | 4| 514| HI| 1905| 30| 109| 98| 0| 14||GigabitEthernet0/1/5/0| 1| 131| BE| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/0| 2| 259| AF| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/0| 4| 515| HI| 1905| 187| 732| 658| 0|||GigabitEthernet0/1/5/1| 1| 132| BE| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/1| 2| 260| AF| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/1| 4| 516| HI| 1905| 187| 732| 658| 0|||GigabitEthernet0/1/5/2| 1| 133| BE| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/2| 2| 261| AF| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/2| 4| 517| HI| 1905| 187| 732| 658| 0|||GigabitEthernet0/1/5/3| 1| 134| BE| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/3| 2| 262| AF| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/3| 4| 518| HI| 1905| 187| 732| 658| 0|||GigabitEthernet0/1/5/4| 1| 135| BE| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/4| 2| 263| AF| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/4| 4| 519| HI| 1905| 187| 732| 658| 0|||GigabitEthernet0/1/5/5| 1| 136| BE| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/5| 2| 264| AF| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/5| 4| 520| HI| 1905| 187| 732| 658| 0|||GigabitEthernet0/1/5/6| 1| 137| BE| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/6| 2| 265| AF| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/6| 4| 521| HI| 1905| 187| 732| 658| 0|||GigabitEthernet0/1/5/7| 1| 138| BE| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/7| 2| 266| AF| 13| 187| 732| 658| 0|||GigabitEthernet0/1/5/7| 4| 522| HI| 1905| 187| 732| 658| 0||--More--



OL-17332-01


Related Commands

Table 32 show controllers fabricq queue Field Descriptions

Field Description

Slot Slot or queue to which the packets are sent.

EnQueued Number of entries enqueued for that queue.

DeQueued Number of entries dequeued for that queue.

Cur-Entrys Number of entries currently for that queue.

Max-Entrys Highest number of entries for that queue.

Blocked Yes or No if that queue is blocked.

BP count Back-pressure count, which is the number of times the queue got full.

Queue Priority queues receiving packets; 0 is the highest priority. The F/Q entry is the software free packet queue.

Allocated Number of packets in that queue.

Free Number of packets available for that queue.

Command Description







Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq registers


OL-17332-01

show controllers fabricq registersTo display the hardware registers of the chopper and assembler FPGAs, use the show controllers fabricq registers command in administration EXEC mode.

show controllers fabricq registers [detail] [location node-id]

Syntax Description

Defaults Information for all route processors (RPs) on the router is displayed


Command History


Use the show controllers fabricq registers command to display the hardware registers of the chopper and assembler FPGAs. Specifying a location displays information only if that location is an RP.

This command is intended for use while performing debugging procedures.

Task ID











Task ID Operations




OL-17332-01

Examples The following is sample output from the show controllers fabricq registers command for location 0/1/CPU0:

RP/0/0/CPU0:router# adminRP/0/0/CPU0:router(admin)# show controllers fabricq registers location 0/1/CPU0

Location 0/1/0:

Chopper Registers:------------------FPGA Version 00020012HP Descriptor fetch enable 00010000Descriptor array size 000003FFInterrupt cause 00000000Interrupt mask FC01FFFFLP Descriptor fetch enable 00000008HP Interrupt desc afull 00000000LP Interrupt desc afull 00000000Discovery low control reg base address F1000840Discovery next desc reg base address F1000830Chopper PCI base address F0000000HP Descriptor queue empty status 0001FFFFHP Descriptor queue almost full 00000000Data queue empty status 0001FFFFData queue almost full 00000000LP Descriptor queue empty status 0001FFFFLP Descriptor queue almost full 00000000SRAM Descriptor threshold 000003F0SRAM Data threshold 000007F0DMA Control 000000DDBack pressure status 00000000Fusilli Tx Enable 0001FFFFCell count 0030CDA1Reset VOQ 00000000DMA Busy Status 00000000DMA Done Status 000000DDHP Descriptor start addr for queue 0 0B448000HP Descriptor start addr for queue 1 0B44A000HP Descriptor start addr for queue 2 0B44C000HP Descriptor start addr for queue 3 0B44E000HP Descriptor start addr for queue 4 0B450000HP Descriptor start addr for queue 5 0B452000HP Descriptor start addr for queue 6 0B454000HP Descriptor start addr for queue 7 0B456000HP Descriptor start addr for queue 8 0B458000HP Descriptor start addr for queue 9 0B45A000HP Descriptor start addr for queue 10 0B45C000HP Descriptor start addr for queue 11 0B45E000HP Descriptor start addr for queue 12 0B460000HP Descriptor start addr for queue 13 0B462000HP Descriptor start addr for queue 14 0B464000HP Descriptor start addr for queue 15 0B466000HP Descriptor start addr for queue 16 0B468000LP Descriptor start addr for queue 0 0B426000LP Descriptor start addr for queue 1 0B428000LP Descriptor start addr for queue 2 0B42A000LP Descriptor start addr for queue 3 0B42C000LP Descriptor start addr for queue 4 0B42E000LP Descriptor start addr for queue 5 0B430000LP Descriptor start addr for queue 6 0B432000LP Descriptor start addr for queue 7 0B434000LP Descriptor start addr for queue 8 0B436000LP Descriptor start addr for queue 9 0B438000



OL-17332-01

LP Descriptor start addr for queue 10 0B43A000LP Descriptor start addr for queue 11 0B43C000LP Descriptor start addr for queue 12 0B43E000LP Descriptor start addr for queue 13 0B440000LP Descriptor start addr for queue 14 0B442000LP Descriptor start addr for queue 15 0B444000LP Descriptor start addr for queue 16 0B446000

Assembler Registers:-------------------Version 0002000DChip Config 0000000FInt Mask 00000000Output Queue Threshold 00000033Low Pri Req level 00000030High Pri Req level 00000060Free Queue Size 00001000Free Queue Base 0B3A6000Free Queue Rd Pointer 0B3A6380Free Queue Wr Pointer 0B3A61C0Output Queue Size 00001000Output Queue 0 Base Addr 0B3A8000Output Queue 0 Write Addr 0B3A8000Output Queue 0 Read Addr 0B3A8000Output Queue 0 Match C0000200Output Queue 0 Mask 00003E00Output Queue 1 Base Addr 0B3AA000Output Queue 1 Write Addr 0B3AAB58Output Queue 1 Read Addr 0B3AAB58Output Queue 1 Match C0000C00Output Queue 1 Mask 00003E00Output Queue 2 Base Addr 0B3AC000Output Queue 2 Write Addr 0B3AC4D0Output Queue 2 Read Addr 0B3AC4D0Output Queue 2 Match C0000400Output Queue 2 Mask 00003C00Output Queue 3 Base Addr 0B3AE000Output Queue 3 Write Addr 0B3AE360Output Queue 3 Read Addr 0B3AE360Output Queue 3 Match C0000000Output Queue 3 Mask 00000000Discard Buffer Addr 0A1AC700REFIM config 00000000REFIM Max Packet Len 000000C1








Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq statistics


OL-17332-01

show controllers fabricq statisticsTo display statistics about packet flow through the fabric queue application-specific integrated circuit (ASIC), use the show controllers fabricq statistics command in EXEC mode.

show controllers fabricq statistics [instance instance] [location node-id]

Syntax Description

Defaults Information for all fabric queue ASICs for all locations is displayed

Command Modes EXEC

Command History


Use the show controllers fabricq statistics command to track the number of unicast and multicast packets that are sent from the fabric to the specified node.

Task ID

instance instance (Optional) Specifies instance and number for a single fabric queue ASIC. The instance argument is a number from 0 to 4.

location node-id (Optional) Specifies statistical packet flow information for the designated node. The node-id argument is entered in the rack/slot/module notation.





Release 3.3.0 The show controllers fabricq packet-stats command was replaced by the show controllers fabricq statistics command.






Task ID Operations

interface read

drivers read



OL-17332-01

Examples The following is sample output from the show controllers fabricq statistics command that displays statistics about fabric queue packets that have passed through ASIC 0 on node 0/1/CPU0:

RP/0/RP0/CPU0:router# show controllers fabricq statistics instance 0 location 0/1/CPU0

Fabric Queue Manager Packet Statistics ======================================

Location: 0/1/CPU0 Asic Instance: 0 Fabric Destination Address: 32

Input Cell counters: +----------------------------------------------------------+ Data cells : 42356 (+ 22 ) Control cells : 29877224 (+ 36372 ) Idle cells : 219947284936 (+ 267358842 ) BP Asserted Count : 0 (+ 0 ) MC BP Asserted Count : 0 (+ 0 )

Reassembled packet counters +----------------------------------------------------------+ Ucast pkts : 0 (+ 0 ) Mcast pkts : 0 (+ 0 ) Cpuctrlcast pkts : 21159 (+ 11 )

Dropped packets +----------------------------------------------------------+ Ucast pkts : 0 (+ 0 ) Mcast pkts : 0 (+ 0 ) Cpuctrlcast pkts : 0 (+ 0 ) Vital denied pkts : 0 (+ 0 ) NonVital denied pkts : 0 (+ 0 ) Unicast lost pkts : 0 (+ 0 ) Ucast partial pkts : 0 (+ 0 ) PSM OOR Drops : 0 (+ 0 )


Table 33 show controllers fabricq statistics Field Descriptions

Field Description

Input Cell counters Number of cells that have reached the fabric queue ASIC.

Note The numbers following the colons are the cumulative count since the last time the counts were cleared and those within parentheses are the delta since the last time the driver polled the ASIC.

Control Cells Carry discard and back-pressure information across the fabric.

Idle Cells Carry control information in the cell header and keep the links in sync.

Data Cells All other cells apart from Control cells and Idle cells are counted as data cells, regardless of whether they are CPU bound or E-metro bound.



OL-17332-01

Reassembled packet counters Number of packets the fabric queue ASIC has reassembled after transmission over the fabric.

Ucast packet Number of unicast packets.

Mcast packet Number of multicast packets.

Cpuctrlcast packet All the traffic bound for the local CPU of this linecard.

Dropped packets Number of packets the fabric queue ASIC has had to drop.

Unicast packets These packets are discarded at the Output Queue Manager block (OQM).

Multicast packets These packets are discarded at the OQM.

Cpuctrlcast packets These packets are discarded at the OQM.

Vital denied packets Represent a condition where buffer references are denied for a vital in the Packet Control Logic (PCL) block of the ASIC.

NonVital denied packets Represent a condition where buffer references are denied for a non vital in the Packet Control Logic (PCL) block of the ASIC.

Unicast lost packets Missing packets at the PCL block when packets are retired to the OQM.

Unicast partial packets Incomplete packets at the PCL block when packets are retired to the OQM.

PSM OOR Drops Number of packets that had to be dropped because Packet Status Memory (PSM) ran out of entries.

Table 33 show controllers fabricq statistics Field Descriptions (continued)

Field Description

Fabric Management Commands on Cisco IOS XR Softwareshow controllers fabricq tofab


OL-17332-01

show controllers fabricq tofabTo display to fabric statistics associated with the fabric queue driver, use the show controllers fabricq tofab command in administration EXEC mode.

show controllers fabricq tofab [detail [location node-id] | trace options {location node-id}]

Syntax Description

Defaults Statistical information is displayed for all route processors (RPs) on the router



trace options (Optional) Displays detailed fabric queue driver trace information for a specific node. Replace the options argument with one or more of the following keywords or keywords and arguments to specify the type and format of trace information displayed:

• error—Includes tofab error trace information in the command output.

• file word original—Displays trace information for a specific file.

• header—Includes tofab header trace information in the command output.

• hexdump—Display trace information in hexadecimal format.

• last entries—Display trace information for a specific number of entries. Replace the entries argument with the number of entries you want to display. For example, if you enter 5, the display will show the last 5 entries in the trace data.

• payload—Includes payload trace information in the command output.

• reverse—Displays the latest traces first.

• stats—Includes trace statistics in the command output.

• tailf—Includes new traces as they are added in the command output.

• unique—Includes unique trace entries with counts in the command output.

• verbose—Includes internal debugging information in the command output.

• wrapping—Includes wrapping entries in the command output.

location node-id (Optional) Displays statistical or trace information for the designated node. The node-id argument is entered in the rack/slot/module notation.



OL-17332-01

Command History


Use the show controllers fabricq tofab command to display to fabric statistics. Specifying a location displays information only if that location is an RP.

The show controllers fabricq tofab command is intended for use while performing debugging procedures.

Task ID

Examples The following is sample output from the show controllers fabricq tofab command for location 0/1/CPU0:

RP/0/0/CPU0:router# adminRP/0/0/CPU0:router(admin)# show controllers fabricq tofab location 0/1/CPU0

Location 0/1/0:

To Fabric Stats:---------------Slot Tx-pkts Tx-TH-pkts Tx-dropped Tx-DMA Low Priority:3 0 446 0 446 High Priority:1 0 248 0 248 2 0 13696 0 13696 3 0 14347 0 14347 4 0 15889 0 15889 5 0 14351 0 14351 mcast 0 2182 0 2182

To Fabric Errors:----------------Failed sends because of no header bufs - 0Failed sends because of no payload bufs - 0









Task ID Operations




OL-17332-01

SRAM parity errors - 0DMA errors - 0Fusilli Parity errors - 0


Related Commands

Table 34 show controllers fabricq tofab Field Descriptions

Field Description

Tx-pkts Number of packets sent to that slot.

Tx-TH-pkts Number of “think hard” packets sent to that slot.

Tx-dropped Number of dropped packets sent to that slot.

Tx-DMA Number of direct memory accesses (DMA) to send the packet to that slot.

Command Description







Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq capacity


OL-17332-01

show controllers ingressq capacityTo display ASIC capacity details for the ingress fabric queue, use the show controllers ingressq capacity command in EXEC mode.

show controllers ingressq {capacity cap table}[location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID

cap table Specific capacity table.

Note The range is from 0 to 4294967295. PMAX=0, Q-MAX=1, and QMIN=3.

location node-id Identifies the location of the ingressq queue whose statistics you want to display. The node-id argument is expressed in the rack/slot/module notation.









Task ID Operations

interface read

drivers read

Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq capacity


OL-17332-01

Examples The following example shows how to display ASIC capactiy information for the ingress fabric queue:

RP/0/RP0/CPU0:router#sh controllers ingressq capacity 0 location 0/1/CPU0 ingressq capacity table: Port Max capacityTable id: 04 8 12 16 20 24 28 32 36 40 44 48 52 56 60 64 68 72 76 88 108 136 172 216 276 348 436 552 700 884 1116 1408 1780 2248 2836 3584 4528 5724 7228 9136 11540 14580 18420 23272 29404 37152 46936 59304 74924 94664 119600 151108 190916 241212 304756 385040 486472 614628 776548 981120 1239584 1566140 1978724 2500000


show controllers ingressq clients

Displays information for all clients connected to IQM.

show controllers ingressq eio

Displays EIO information for the ingressq ASIC queue.

show controllers ingressq fabric

Displays information for all fabric interfaces.

show controllers ingressq interfaces

Displays information for interfaces associated with an ingressq queue.

show controllers ingressq queues

Displays information for all queues.

show controllers ingressq statistics

Displays information for ingressq packet statistics.

show controllers ingressq vports

Displays ingressq information for a virtual port, or for several ports.

Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq clients


OL-17332-01

show controllers ingressq clientsTo display all clients connected to the ingress queue manager (IQM), use the show controllers ingressq clients command in EXEC mode.

show controllers ingressq clients {location node-id}

Syntax Description


Command Modes EXEC

Command History


Task ID

location node-id Identifies the location of the ingress queue whose statistics you want to display. The node-id argument is expressed in the rack/slot/module notation.









Task ID Operations

interface read

drivers read

Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq clients


OL-17332-01

Examples The following example shows how to display ingressq clients connected to IQM:

RP/0/RP0/CPU0:router# show controllers ingressq clients location 0/1/CPU0-------------------------------------------------------------------------ingress queue manager clients:handle name ------------------------------------------------------------1 hfr_pm 2 QOS_EA 3 BM-EA HFR DLL


show controllers ingressq capacity

Displays capacity information for the ingressq ASIC.













Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq eio


OL-17332-01

show controllers ingressq eioTo display elastic I/O (EIO) information for the ingress queueing ASIC, use the show controllers ingressq eio command in EXEC mode.

show controllers ingressq eio links {link id | all} [location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID

link id Displays one or more EIO link states.

Note The range of the link id argument is 0 to 4294967295.

all Indicates that you want to display ingressq eio information for all interfaces in the specified location.

location node-id Identifies the location of the ingress queue manager whose EIO link information you want to display. The node-id argument is expressed in the rack/slot/module notation.









Task ID Operations

interface read

drivers read

Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq eio


OL-17332-01

Examples The following example shows how to display EIO information for the ingress fabric queue:

RP/0/RP0/CPU0:router# show controllers ingressq eio links all

Node: 0/1/CPU0:----------------------------------------

EIO links:-------------------------------------------------------------------ASIC Id Peer Id Type Link-Id Attempts Accept Failed State-------------------------------------------------------------------INGRESSQ_0 PSE_0 RX 10 1 1 0 EIO_LINK_TRAINEDINGRESSQ_0 PSE_0 TX 24 0 0 0 EIO_LINK_TRAINEDINGRESSQ_0 FIA_0 TX 20 0 0 0 EIO_LINK_TRAINEDINGRESSQ_0 FIA_0 TX 21 0 0 0 EIO_LINK_TRAINEDINGRESSQ_0 FIA_1 TX 22 0 0 0 EIO_LINK_TRAINEDINGRESSQ_0 FIA_1 TX 23 0 0 0 EIO_LINK_TRAINEDINGRESSQ_0 FABRICQ_0 RX 54 1 1 0 EIO_LINK_TRAINEDINGRESSQ_0 FABRICQ_1 RX 55 1 1 0 EIO_LINK_TRAINED

Node: 0/4/CPU0:----------------------------------------

EIO links:-------------------------------------------------------------------ASIC Id Peer Id Type Link-Id Attempts Accept Failed State-------------------------------------------------------------------INGRESSQ_0 FIA_0 TX 20 0 0 0 EIO_LINK_TRAINEDINGRESSQ_0 FABRICQ_0 RX 54 1 1 0 EIO_LINK_TRAINEDINGRESSQ_0 FABRICQ_1 RX 55 1 1 0 EIO_LINK_TRAINED-------------------------------------------------------------------------









Displays information about interfaces associated with an ingressq queue.







Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq fabric


OL-17332-01

show controllers ingressq fabricTo display various parameters of ingressq and switching fabric connectivity, use the show controllers ingressq fabric command in EXEC mode.

show controllers ingressq fabric {asic | detail | links | pla} [location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID

asic Displays ASIC states.

detail Displays fabric state information.

links Displays link states information.

pla Displays plane availability information for unicast and multicast.

location node-id Identifies the location of the ingressq queue whose statistics you want to display. The node-id argument is expressed in the rack/slot/module notation.









Task ID Operations

interface read

drivers read

Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq fabric


OL-17332-01

Examples The following example shows how to display various parameters of ingressq and switching fabric connectivity for all fabric interfaces:

RP/0/RP0/CPU0:router#sh controllers ingressq fabric links location 0/1/CPU0 Ingressq link stateplane-id link-id ADMIN-STATE OPER-STATE AVAIL-STATE UP-COUNT --------------------------------------------------------------------0 0 UP UP UP 1 0 8 UP UP UP 1 0 16 UP UP UP 1 0 24 UP UP UP 1 1 1 UP UP UP 1 1 9 UP UP UP 1 1 17 UP UP UP 1 1 25 UP UP UP 1 2 2 UP UP UP 1 2 10 UP UP UP 1 2 18 UP UP UP 1 2 26 UP UP UP 1 3 3 UP UP UP 1 3 11 UP UP UP 1 3 19 UP UP UP 1 3 27 UP UP UP 1 4 4 UP UP UP 1 4 12 UP UP UP 1 4 20 UP UP UP 1 4 28 UP UP UP 1 5 5 UP UP UP 1 5 13 UP UP UP 1 5 21 UP UP UP 1 5 29 UP UP UP 1 6 6 UP UP UP 1 6 14 UP UP UP 1 6 22 UP UP UP 1 6 30 UP UP UP 1 7 7 UP UP UP 1 7 15 UP UP UP 1 7 23 UP UP UP 1 7 31 UP UP UP 1 --------------------------------------------------------------------









Displays information about interfaces associated with an ingressq queue.







Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq interfaces


OL-17332-01

show controllers ingressq interfacesTo display the ingressq shape queue and parameters associated with the physical interfaces on the card, use the show controllers ingressq interfaces command in EXEC mode.

show controllers ingressq interfaces {type instance | all} [location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID

type instance Physical interface or a virtual interface.


all Indicates that you want to display ingressq queue information for all interfaces in the specified location.










Task ID Operations

interface read

drivers read

Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq interfaces


OL-17332-01

Examples The following example shows how to display the ingressq shape queue and parameters associated with the physical interfaces on the card:

RP/0/RP0/CPU0:router# show controllers ingressq interfaces all location 0/1/CPU0

iqm interfaces:legend:: #sub: num sub intf, rc: reference count, indx: demux num.------------------------------------------------------------------------------name intf hd parent hd #sub indx def-port ports rc Owner------------------------------------------------------------------------------Bundle-POS24 0x80050 0x0 0 0 25 1 3 hfr_pmBundle-Ether28 0x80070 0x0 3 0 26 1 6 hfr_pmBundle-Ether28.1 0x80090 0x80070 0 0 26 1 3 hfr_pmBundle-Ether28.2 0x800b0 0x80070 0 0 26 1 3 hfr_pmBundle-Ether28.3 0x800d0 0x80070 0 0 26 1 3 hfr_pmPOS0_1_0_0 0x1180060 0x0 0 0 9 1 3 hfr_pmPOS0_1_4_0 0x11800c0 0x0 0 0 8 1 3 hfr_pmTenGigE0_1_1_0 0x11800e0 0x0 0 0 18 1 3 hfr_pmGigabitEthernet0_1_5_00x1180100 0x0 0 0 10 1 3 hfr_mGigabitEthernet0_1_5_10x1180120 0x0 0 0 11 1 3 hfr_mGigabitEthernet0_1_5_20x1180140 0x0 0 0 12 1 3 hfr_mGigabitEthernet0_1_5_30x1180160 0x0 0 0 13 1 3 hfr_mGigabitEthernet0_1_5_40x1180180 0x0 0 0 14 1 3 hfr_mGigabitEthernet0_1_5_50x11801a0 0x0 0 0 15 1 3 hfr_mGigabitEthernet0_1_5_60x11801c0 0x0 0 0 16 1 3 hfr_mGigabitEthernet0_1_5_70x11801e0 0x0 0 0 17 1 3 hfr_mPOS0_1_4_1 0x1180240 0x0 0 0 19 1 3 hfr_pm--More--
















Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq queues


OL-17332-01

show controllers ingressq queuesTo display information about the ingressq shape queues and parameters that have been created for the ingress interfaces, use the show controllers ingressq queues command in EXEC mode.

show controllers ingressq queues {queue handle | all} [location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID

queue handle Specific queue marked by a unique number. Range is from 0 to 4294967295.

all Indicates that you want to display ingressq queue information for all interfaces.

location node-id Identifies the location of the ingressq queue whose statistics you want to display. The node-id is expressed in the rack/slot/module notation.








Release 3.8.0 The queue handle argument range of 0 to 4294967295 was added.

Task ID Operations

interface read

drivers read

Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq queues


OL-17332-01

Examples The following example shows how to display the ingressq shape queues and parameters that have been created for the ingress interfaces:

RP/0/RP0/CPU0:router# sh controllers ingressq queues all location 0/1/CPU0

iqm queues:legend: (*) default q, LP low priority,HP high priority, bs burst sizebw (kbps).name owner q-hd port type max_bw min_bw max_bs min_bs qut--------------------------------------------------------------------------------default_queue(*) hfr_pm 32 8 LP 2396160 0 650 0 25default_queue(*) hfr_pm 33 9 LP 149760 0 533 0 1default_queue(*) hfr_pm 34 10 LP 1000192 0 638 0 10default_queue(*) hfr_pm 35 11 LP 1000192 0 638 0 10default_queue(*) hfr_pm 36 12 LP 1000192 0 638 0 10default_queue(*) hfr_pm 37 13 LP 1000192 0 638 0 10default_queue(*) hfr_pm 38 14 LP 1000192 0 638 0 10default_queue(*) hfr_pm 39 15 LP 1000192 0 638 0 10default_queue(*) hfr_pm 40 16 LP 1000192 0 638 0 10default_queue(*) hfr_pm 41 17 LP 1000192 0 638 0 10default_queue(*) hfr_pm 42 18 LP 10000128 0 511 0 10default_queue(*) hfr_pm 43 19 LP 2396160 0 650 0 25default_queue(*) hfr_pm 44 20 LP 149760 0 533 0 1default_queue(*) hfr_pm 45 21 LP 2396160 0 650 0 25default_queue(*) hfr_pm 46 22 LP 149760 0 533 0 1default_queue(*) hfr_pm 47 23 LP 2396160 0 650 0 25default_queue(*) hfr_pm 48 24 LP 149760 0 533 0 1default_queue(*) BM-EA HFR DLL49 25 LP 4792320 0 588 0default_queue(*) BM-EA HFR DLL50 26 LP 2000000 0 578 0
















Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq statistics


OL-17332-01

show controllers ingressq statisticsTo display ingress queue manager statistics, use the in EXEC mode.

show controllers ingressq statistics [location node-id]

Syntax Description


Command Modes EXEC

Command History


Note In the show controllers ingressq statistics command display, the rx pkts counter field may wrap if it is calculating line rate traffic.

Task ID








Release 3.6.0 The location node-id keyword and argument were changed from required to optional.



Task ID Operations

interface read

drivers read



OL-17332-01

Examples The following example shows how to display ingress queue manager statistics:

RP/0/RP0/CPU0:router# show controllers ingressq statistics location 0/2/CPU0

Ingressq Rx Statistics.------------------------------------------------------------------------rx pkts : 131827 ( 33509182 bytes)rx pkts from cpu : 102509 ( 16422606 bytes)rx control pkts from cpu : 102509 ( 16422606 bytes)rx data pkts from cpu : 0 ( 0 bytes)

Ingressq Tx Statistics.------------------------------------------------------------------------tx pkts : 131826 ( 35086366 bytes)tx pkts to cpu : 29318 ( 17086576 bytes)tx control pkts to cpu : 29318 ( 17086576 bytes)tx data pkts to cpu : 0 ( 0 bytes)tx pkts shaped : 102508 ( 17999790 bytes)tx cells to fabric : 223190

Ingressq Drops.------------------------------------------------------------------------length error drops - PSE : 0length error drops - Cpuctrl : 0crc error drops - PSE : 0crc error drops - Cpuctrl : 0OOR error drops - PSE : 0OOR error drops - Cpuctrl : 0discard drops : 0tail drops : 0tail drops - no QE : 0cell drops : 0



OL-17332-01


Table 35 show controllers ingressq statistics Field Descriptions

Field Description

Ingressq Rx Statistics Displays the following receive statistics:

• rx pkts—Total number of packets received; also shown in bytes.

• rx pkts from cpu—Number of packets received from the CPU; also shown in bytes.

• rx control pkts from cpu—Number of control packets received; also shown in bytes.

• rx data pkts from cpu—Number of data packets received; also shown in bytes.

Ingressq Tx Statistics Displays the following transmit statistics:

• tx pkts—Total number of packets transmitted; also shown in bytes.

• tx pkts to cpu—Number of packets transmitted from the CPU; also shown in bytes.

• tx control pkts to cpu—Number of control packets transmitted; also shown in bytes.

• tx data pkts to cpu—Number of data packets transmitted; also shown in bytes.

• tx pkts shaped—Number of shaped data packets transmitted; also shown in bytes.

• tx cells to fabric—Number of cells that were transmitted to the switch fabric; also shown in bytes.

Ingressq Drops Displays the following ingress queue drop statistics:

• length error drops - PSE—Number of packets that were dropped by the PSE due to length errors.

• length error drops - Cpuctrl—Number of packets that were dropped by the CPU controller due to length errors.

• crc error drops - PSE—Number of packets that were dropped by the PSE due to CRC errors.

• crc error drops - Cpuctrl—Number of packets that were dropped by the CPU controller due to CRC errors

• OOR error drops - PSE—Number of packets that were dropped by the PSE due to OOR errors.

• OOR error drops - Cpuctrl—Number of packets that were dropped by the CPU controller due to OOR errors.

• discard drops—Number of packets that were discarded.

• tail drops—Number of packets discarded for this class because the queue was full.

• tail drops - no QE—Number of packets dropped due to unavailability of the ingress Queue Engine (QE).

• cell drops—Number of cells that were dropped by the ingress queue.



OL-17332-01
















Fabric Management Commands on Cisco IOS XR Softwareshow controllers ingressq vports


OL-17332-01

show controllers ingressq vports To display information about the ingressq virtual ports and its parameters that have been created for the ingressq interfaces, use the show controllers ingressq vports command in EXEC mode.

show controllers ingressq vports {port handle | all} [location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID

port handle Specific virtual port or range of ports. Range is from 0 to 4294967295.

all Indicates that you want to display ingressq virtual ports.

location node-id Identifies the location of the ingress queue whose statistics you want to display. The node-id is expressed in the rack/slot/module notation.








Release 3.8.0 The port handle argument range of 0 to 4294967295 was added.

Task ID Operations

interface read

drivers read



OL-17332-01

Examples The following example shows how to display a list of ingressq virtual ports:

RP/0/RP0/CPU0:router# show controllers ingressq vports all location 0/1/CPU0

ingressq virtual ports:bw (kbps), bs (usec), quant(10s of 2*Fab MTU).name port-# intf-hd def-q # Qs rc max-bw max-bs quant o--------------------------------------------------------------------------------default_port 8 0x11800c0 32 1 6 2396160 74924 48 hfrdefault_port 9 0x1180060 33 1 6 149760 5724 2 hfrdefault_port 10 0x1180100 34 1 6 1000192 37152 19 hfrdefault_port 11 0x1180120 35 1 6 1000192 37152 19 hfrdefault_port 12 0x1180140 36 1 6 1000192 37152 19 hfrdefault_port 13 0x1180160 37 1 6 1000192 37152 19 hfrdefault_port 14 0x1180180 38 1 6 1000192 37152 19 hfrdefault_port 15 0x11801a0 39 1 6 1000192 37152 19 hfrdefault_port 16 0x11801c0 40 1 6 1000192 37152 19 hfrdefault_port 17 0x11801e0 41 1 6 1000192 37152 19 hfrdefault_port 18 0x11800e0 42 1 6 10000128 385040 200 hfrdefault_port 19 0x1180240 43 1 6 2396160 74924 48 hfrdefault_port 20 0x11802a0 44 1 6 149760 5724 2 hfrdefault_port 21 0x1180300 45 1 6 2396160 74924 48 hfrdefault_port 22 0x1180360 46 1 6 149760 5724 2 hfrdefault_port 23 0x11803c0 47 1 6 2396160 74924 48 hfrdefault_port 24 0x1180420 48 1 6 149760 5724 2 hfrdefault_port 25 0x80050 49 1 6 4792320 151108 95 BM-Ldefault_port 26 0x80070 50 1 12 2000000 74924 40 BM-L-


















OL-17332-01


OL-17332-01

Troubleshooting Commands on Cisco IOS XR Software

This module describes commands used for troubleshooting routers running Cisco IOS XR software.

The commands in this chapter with the cisco-support task ID are used in the Cisco IOS XR Troubleshooting Guide as part of the troubleshooting process. For information about commands with the cisco-support task ID that are not documented in this chapter, please contact Cisco Technical Support. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface.

Caution These Cisco support commands are normally reserved for use by Cisco Technical Support personnel only. There is some risk that they may cause performance or other issues that impact products without proper usage, and we highly recommend that you contact Cisco Technical Support prior to using any of these commands.

Troubleshooting Commands on Cisco IOS XR Softwareshow arp trace


OL-17332-01

show arp trace To display Address Resolution Protocol (ARP) entries in the buffer, use the show arp trace command in EXEC mode.

show arp trace



Command Modes EXEC

Command History


Use the show arp trace command to display ARP entries in the buffer.

Task ID

Examples The following example shows the output of the show arp trace command:

RP/0/RP0/CPU0:router# show arp trace

Mon Nov 10 18:53:02.220 PST DST




Release 3.2 This command was supported on the Cisco XR 12000 Series Router.







Task ID Operations

cisco-support read



OL-17332-01

-------------------------------------------------------------------------------start of show tech-support routing rpl-------------------------------------------------------------------------------

-------------------------------------------------------------------------------RPL CLients Configuration-------------------------------------------------------------------------------

router ospf 100router-id 10.2.2.2nsf ciscoarea 0mpls traffic-enginterface Bundle-POS24!interface Loopback0passive enable!interface GigabitEthernet0/1/5/1!interface GigabitEthernet0/1/5/2bfd fast-detect!interface GigabitEthernet0/6/5/1!interface POS0/1/0/1!interface POS0/1/0/2!interface POS0/1/0/3!interface POS0/6/0/1!interface POS0/6/4/4!interface POS0/6/4/6!interface POS0/6/4/7!!mpls traffic-eng router-id Loopback0!

Mon Nov 10 18:53:03.313 PST DST% No such configuration item(s)

Mon Nov 10 18:53:03.975 PST DSTrouter isis labis-type level-2-onlynet 49.1122.0000.0000.0002.00interface Loopback0passiveaddress-family ipv4 unicast!!interface POS0/1/0/2address-family ipv4 unicast!!interface POS0/1/0/3address-family ipv4 unicast!!



OL-17332-01

!


Mon Nov 10 18:53:05.457 PST DSTrouter eigrp 24vrf vrf_1address-family ipv4router-id 172.20.0.0default-metric 100000 4000 200 45 4470autonomous-system 6redistribute connectedinterface POS0/1/0/0site-of-origin 201:1!!!!


Mon Nov 10 18:53:07.004 PST DST

-------------------------------------------------------------------------------show process policy_repository-------------------------------------------------------------------------------

Job Id: 312PID: 794895Executable path: /disk0/hfr-rout-3.8.0.20I/bin/policy_repositoryInstance #: 1Version ID: 00.00.0000Respawn: ONRespawn count: 2Max. spawns per minute: 12Last started: Tue Nov 4 02:56:20 2008Process state: Run (last exit status : 203)Package state: NormalStarted on config: cfg/gl/policy_lang/policies/core: MAINMEMMax. core: 0Level: 172Placement: ONstartup_path: /pkg/startup/pr.startupReady: 10.672sProcess cpu time: 0.198 user, 0.046 kernel, 0.244 totalJID TID Stack pri state TimeInState HR:MM:SS:MSEC NAME312 2 28K 10 Receive 156:58:40:0190 0:00:00:0240 policy_reposiy-------------------------------------------------------------------------------Mon Nov 10 18:53:07.633 PST DST% No such configuration item(s)

Mon Nov 10 18:53:08.002 PST DSTSysDB Verification Registrations:jid: nid: tid: handle: reg_path:00000312 0/RP0/CPU0 0002 00000606 '/cfg/gl/pim/.*/ipv4/b/rpf/topology'00000312 0/RP1/CPU0 0002 00000597 '/cfg/gl/pim/.*/ipv4/b/rpf/topology'00000312 0/RP0/CPU0 0002 00000607 '/cfg/gl/pim/.*/ipv6/b/rpf/topology'00000312 0/RP1/CPU0 0002 00000598 '/cfg/gl/pim/.*/ipv6/b/rpf/topology'00000312 0/RP0/CPU0 0002 00000595 '/cfg/gl/rip/.*/.*/ord_t/if/.*/ord_t/policy'00000312 0/RP1/CPU0 0002 00000571 '/cfg/gl/rip/.*/.*/ord_t/if/.*/ord_t/policy'00000312 0/RP0/CPU0 0002 00000596 '/cfg/gl/rip/.*/.*/ord_t/if/.*/ord_t/policy'



OL-17332-01

00000312 0/RP1/CPU0 0002 00000573 '/cfg/gl/rip/.*/.*/ord_t/if/.*/ord_t/policy'00000312 0/RP0/CPU0 0002 00000588 '/cfg/gl/rip/.*/.*/ord_t/redist/.*/.*'00000312 0/RP1/CPU0 0002 00000564 '/cfg/gl/rip/.*/.*/ord_t/redist/.*/.*'00000312 0/RP0/CPU0 0002 00000592 '/cfg/gl/rip/.*/.*/ord_t/policy-in'00000312 0/RP1/CPU0 0002 00000568 '/cfg/gl/rip/.*/.*/ord_t/policy-in'00000312 0/RP0/CPU0 0002 00000594 '/cfg/gl/rip/.*/.*/ord_t/policy-out'00000312 0/RP1/CPU0 0002 00000569 '/cfg/gl/rip/.*/.*/ord_t/policy-out'00000312 0/RP0/CPU0 0002 00000590 '/cfg/gl/rip/.*/.*/ord_t/defaultinformation'00000312 0/RP1/CPU0 0002 00000566 '/cfg/gl/rip/.*/.*/ord_t/defaultinformation'00000312 0/RP0/CPU0 0002 00000578 '/cfg/gl/rsi/vrf/.*/ord_z/afi_safi/.*/.*/de'00000312 0/RP1/CPU0 0002 00000553 '/cfg/gl/rsi/vrf/.*/ord_z/afi_safi/.*/.*/de'00000312 0/RP0/CPU0 0002 00000579 '/cfg/gl/rsi/vrf/.*/ord_z/afi_safi/.*/.*/de'00000312 0/RP1/CPU0 0002 00000555 '/cfg/gl/rsi/vrf/.*/ord_z/afi_safi/.*/.*/de'00000312 0/RP0/CPU0 0002 00000602 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000587 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000603 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000589 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000600 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000584 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000601 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000586 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000599 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000583 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000604 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000591 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000605 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000593 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000565 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000540 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000570 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000543 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000585 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000562 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000576 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000550 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000560 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000538 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000580 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000557 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000541 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000530 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000581 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000559 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000546 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP1/CPU0 0002 00000532 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP0/CPU0 0002 00000552 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP1/CPU0 0002 00000534 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP0/CPU0 0002 00000556 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP1/CPU0 0002 00000536 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP0/CPU0 0002 00000574 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP1/CPU0 0002 00000547 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP0/CPU0 0002 00000567 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000542 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000572 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000545 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000577 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000551 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000563 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000539 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000544 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000531 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000582 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000561 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000549 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/nbr/.*/edm/.'



OL-17332-01

00000312 0/RP1/CPU0 0002 00000533 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/nbr/.*/edm/.'00000312 0/RP0/CPU0 0002 00000554 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/nbr/.*/edm/.'00000312 0/RP1/CPU0 0002 00000535 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/nbr/.*/edm/.'00000312 0/RP0/CPU0 0002 00000558 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/nbr/.*/edm/.'00000312 0/RP1/CPU0 0002 00000537 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/nbr/.*/edm/.'00000312 0/RP0/CPU0 0002 00000575 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/nbr/.*/edm/.'00000312 0/RP1/CPU0 0002 00000548 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/nbr/.*/edm/.'00000312 0/RP1/CPU0 0002 00000527 '/cfg/gl/policy_lang/sets/.*/.*/bag'00000312 0/RP0/CPU0 0002 00000522 '/cfg/gl/policy_lang/sets/.*/.*/bag'00000312 0/RP1/CPU0 0002 00000529 '/cfg/gl/policy_lang/editor/.*'00000312 0/RP0/CPU0 0002 00000524 '/cfg/gl/policy_lang/editor/.*'00000312 0/RP1/CPU0 0002 00000528 '/cfg/gl/policy_lang/maximum/.*'00000312 0/RP0/CPU0 0002 00000523 '/cfg/gl/policy_lang/maximum/.*'00000312 0/RP1/CPU0 0002 00000526 '/cfg/gl/policy_lang/policies/.*/.*/bag'00000312 0/RP0/CPU0 0002 00000521 '/cfg/gl/policy_lang/policies/.*/.*/bag'

70 unique entries (3072 possible, 0 filtered)Apr 20 19:31:58.862 ipv4_arp/slow 0/RP0/CPU0 1# t1 ARP-TABLE: ip_arp_cache_tab.Apr 20 19:31:59.310 ipv4_arp/fast 0/RP0/CPU0 1# t1 Failed to bind to RSI: No syApr 20 19:31:59.310 ipv4_arp/fast 0/RP0/CPU0 1# t1 Unbind from RSIApr 20 19:31:59.310 ipv4_arp/fast 0/RP0/CPU0 1# t1 RSI connection retryApr 20 19:31:59.310 ipv4_arp/fast 0/RP0/CPU0 1# t1 Successfully initialised VRbApr 20 19:32:05.324 ipv4_arp/slow 0/RP0/CPU0 1# t1 ARP-EVENT: Repopulating AIBApr 20 19:32:05.895 ipv4_arp/slow 0/RP0/CPU0 1# t1 ARP-DEV-EVENT: Unbinding frsApr 20 19:32:05.913 ipv4_arp/slow 0/RP0/CPU0 1# t1 ARP-DEV-EVENT: successfullysApr 20 19:32:05.926 ipv4_arp/slow 0/RP0/CPU0 2# t1 ARP-EVENT-DEV: arp successf7Apr 20 19:32:05.937 ipv4_arp/slow 0/RP0/CPU0 1# t1 ARP-DEV-EVENT: successfullysApr 20 19:32:05.952 ipv4_arp/slow 0/RP0/CPU0 21# t1 ARP-DEV-EVENT: register codApr 20 19:32:06.620 ipv4_arp/fast 0/RP0/CPU0 1# t1 Successful bind to RSIApr 20 19:32:06.634 ipv4_arp/slow 0/RP0/CPU0 1# t1 ARP-EVENT: IM ORE receivedApr 20 19:32:11.166 ipv4_arp/fast 0/RP0/CPU0 1# t3 ARP-EVENT-DEV:Failed to sto)Apr 20 19:32:11.347 ipv4_arp/slow 0/RP0/CPU0 1# t3 ARP-EVENT-DEV: Init with stdApr 20 19:32:53.596 ipv4_arp/slow 0/RP0/CPU0 1# t1 ARP-EVENT-DEV: Queueing cli9Apr 20 19:32:53.597 ipv4_arp/slow 0/RP0/CPU0 1# t5 ARP-EVENT-DEV: Processing c9Apr 20 19:33:09.428 ipv4_arp/fast 0/RP0/CPU0 1# t1 Successfully looked up defa0Apr 20 19:33:09.428 ipv4_arp/fast 0/RP0/CPU0 1# t1 Added VRF, vrf_id 0x60000001Apr 20 19:33:09.428 ipv4_arp/fast 0/RP0/CPU0 1# t1 Registering VRF TBL 0xe0000SApr 20 19:33:12.377 ipv4_arp/fast 0/RP0/CPU0 10# t1 ARP-EVENT: received interf3Apr 20 19:33:12.452 ipv4_arp/slow 0/RP0/CPU0 1# t1 ARP-EVENT: Getting MAC addr]Apr 20 19:33:12.471 ipv4_arp/slow 0/RP0/CPU0 1# t1 ARP-EVENT: Getting vlan id ]Apr 20 19:33:12.487 ipv4_arp/slow 0/RP0/CPU0 3# t1 ARP-EVENT: Successfully pro]Apr 20 19:33:12.487 ipv4_arp/slow 0/RP0/CPU0 1# t1 ARP-EVENT: Get MAC callback]Apr 20 19:33:12.487 ipv4_arp/fast 0/RP0/CPU0 3# t1 ARP-EVENT: Received VLAN ID)Apr 20 19:33:12.487 ipv4_arp/fast 0/RP0/CPU0 3# t1 ARP-EVENT: Processing VLAN )Apr 20 19:33:12.487 ipv4_arp/slow 0/RP0/CPU0 8# t1 ARP-EVENT: Unable to procestApr 20 19:33:12.488 ipv4_arp/slow 0/RP0/CPU0 1# t1 ARP-EVENT: Get VLAN ID call]Apr 20 19:33:16.563 ipv4_arp/slow 0/RP0/CPU0 2# t1 ARP-BULK-EVENT: sending batrApr 20 19:33:16.563 ipv4_arp/fast 0/RP0/CPU0 5# t1 ARP-BULK-EVENT: received ip0Apr 20 19:33:16.563 ipv4_arp/fast 0/RP0/CPU0 10# t1 ARP-DEV-EVENT: IDB for ifh0Apr 20 19:33:16.567 ipv4_arp/slow 0/RP0/CPU0 5# t1 ARP-BULK-EVENT: register ipdApr 20 19:33:16.708 ipv4_arp/slow 0/RP0/CPU0 1# t3 ARP-EVENT: IMP caps add suc0Apr 20 19:33:17.097 ipv4_arp/slow 0/RP0/CPU0 1# t1 ARP-EVENT: interface_entry 0Apr 20 19:33:17.103 ipv4_arp/slow 0/RP0/CPU0 1# t1 ARP-EVENT-DEV: Queueing cli2Apr 20 19:33:17.103 ipv4_arp/slow 0/RP0/CPU0 1# t5 ARP-EVENT-DEV: Processing c2


show arp Displays the ARP.

Troubleshooting Commands on Cisco IOS XR Softwareshow captured packets


OL-17332-01

show captured packets To display information on packets that are switched and punted in the software, use the show captured packets command in EXEC mode.

show captured packets {ingress | egress} [interface type interface-path-id] [hexdump] [last number] [single-line] location node-id

Syntax Description


Command Modes EXEC

Command History

ingress Specifies ingress dropped packets.

egress Specifies egress dropped packets.

interface (Optional) Specifies an interface.

type (Optional) Interface type. For more information, use the question mark (?) online help function.

interface-path-id (Optional) Physical interface or virtual interface.



hexdump (Optional) Displays the packet contents in hex.

last number (Optional) Specifies the last number of packets in the queue to display.

single-line (Optional) Displays a one-line summary of the captured packets to facilitate the use of the include and exclude operators.

location node-id (Optional) Displays packet information for a specified node. The node-id argument is entered in the rack/slot/module notation.











Troubleshooting Commands on Cisco IOS XR Softwareshow captured packets


OL-17332-01


Use the show captured packets command to display information on packets that are switched and punted in the software.

The capture software packets command must be enabled at the interface level to use this command.

Task ID

Examples The following example shows the output of the show captured packets command:

RP/0/RP0/CPU0:router# show captured packets ingress interface tengige0/0/0/3 location 0/0/CPU0

-------------------------------------------------------packets captured on interface in ingress direction buffer overflow pkt drops:0, current: 6, non wrapping: 0 maximum: 200------------------------------------------------------- Wrapping entries-------------------------------------------------------[1] Mar 22 16:30:43.797, len: 114, hits: 1, i/p i/f: TenGigE0/0/0/3 [punt reason: IFIB] [ether dst: 0015.fa99.590b src: 0010.a4e6.22fc type/len: 0x800] [IPV4: source 172.18.2.2, dest 172.18.2.1 ihl 5, ver 4, tos 0 id 22556, len 100, prot 1, ttl 64, sum c655, offset 0] 00008612 51010000 abcdabcd abcdabcd abcdabcd abcdabcd abcdabcd abcdabcd abcdabcd abcdabcd abcdabcd abcd


Related Commands

Task ID Operations

cisco-support read

Table 36 show captured packets Field Descriptions

Field Description

punt reason: IFIB Packet was switched in the software due to the Internal Forwarding Information Base (IFIB) entry.

ether Source, destination, and type or length values in the Ethernet header.

IPV$ Depending on the type of packet, the layer 3 packet header follows.

Command Description

capture software packets Enables software packet capture.

Troubleshooting Commands on Cisco IOS XR Softwareshow cfgmgr trace


OL-17332-01

show cfgmgr trace To display trace information for the configuration manager (CFGMGR), use the show cfgmgr trace command in EXEC mode.

show cfgmgr trace



Command Modes EXEC

Command History


Use the show cfgmgr trace command to display cfgmgr trace information.

The following lines of the show cfgmgr trace command output indicate that the startup configuration has started and that it has completed on the active RP:

Feb 6 21:28:37.145 /ltrace/cfgmgr/common 0/RP0/CPU0 t5 Startup config apply requested with option '0x1'Feb 6 21:31:30.874 /ltrace/cfgmgr/common 0/RP0/CPU0 t7 Startup config done (and infra band already ready)

Note These traces are not present if the original active RP has ever reloaded (for example, if there have been any RP switchover events since the system first booted).











Troubleshooting Commands on Cisco IOS XR Softwareshow cfgmgr trace


OL-17332-01

Task ID

Examples The following example shows the output of the show cfgmgr trace command:

RP/0/RP0/CPU0:router# show cfgmgr trace

130 wrapping entries (2048 possible, 0 filtered, 130 total)Apr 23 21:15:58.587 cfgmgr/common 0/RP0/CPU0 t5 Req '4': Save interface config]Apr 23 21:15:58.707 cfgmgr/common 0/RP0/CPU0 t5 Req '4': Save node specific co]Apr 23 21:15:59.000 cfgmgr/common 0/RP0/CPU0 t5 OIR announcement made for 'nod'Apr 23 21:17:40.975 cfgmgr/common 0/RP0/CPU0 t5 The request queue IS NOT curredApr 23 21:17:40.975 cfgmgr/common 0/RP0/CPU0 t5 Process OIR save request.Apr 23 21:17:41.040 cfgmgr/common 0/RP0/CPU0 t5 Validating 'LR' configuration ]Apr 23 21:17:41.055 cfgmgr/common 0/RP0/CPU0 t5 Validating 'admin' configurati]Apr 23 21:17:41.304 cfgmgr/common 0/RP0/CPU0 t5 Req '5': Save interface config]Apr 23 21:17:41.349 cfgmgr/common 0/RP0/CPU0 t5 Req '5': Save interface config]Apr 23 21:17:41.995 cfgmgr/common 0/RP0/CPU0 t5 Req '5': Save interface config]Apr 23 21:17:42.041 cfgmgr/common 0/RP0/CPU0 t5 Req '5': Save interface config]Apr 23 21:17:42.254 cfgmgr/common 0/RP0/CPU0 t5 Req '5': Save interface config]Apr 23 21:17:42.356 cfgmgr/common 0/RP0/CPU0 t5 Req '5': Save node specific co]Apr 23 21:17:42.580 cfgmgr/common 0/RP0/CPU0 t5 OIR announcement made for 'nod'Apr 25 15:26:49.372 cfgmgr/common 0/RP0/CPU0 t1 Config media returned from dis.Apr 25 18:15:06.142 cfgmgr/common 0/RP0/CPU0 t1 Config media returned from dis.Apr 26 03:35:10.170 cfgmgr/common 0/RP0/CPU0 t1 Config media returned from dis.Apr 26 05:54:37.528 cfgmgr/common 0/RP0/CPU0 t1 Config media returned from dis.Apr 26 06:18:47.118 cfgmgr/common 0/RP0/CPU0 t1 Config media returned from dis.Apr 26 09:07:01.662 cfgmgr/common 0/RP0/CPU0 t1 Config media returned from dis.Apr 26 09:28:22.311 cfgmgr/common 0/RP0/CPU0 t1 Config media returned from dis.Apr 26 11:56:55.677 cfgmgr/common 0/RP0/CPU0 t1 Config media returned from dis.

Related Commands

Task ID Operations

cisco-support read

Command Description

show cfgmgr commitdb Displays the contents of the commit database for the configuration manager.

Troubleshooting Commands on Cisco IOS XR Softwareshow im database


OL-17332-01

show im database To display the information stored in the shared memory database of interface manager (IM), use the show im database command in EXEC mode.

show im database {[brief | detail | ifhandle | interface | summary | verbose | view] interface-type interface-instance location node-id }

Syntax Description


brief (Optional) Displays brief information about IM database.

detail (Optional) Displays detailed information about IM database.

ifhandle (Optional) Select a specific interface by handle.

interface (Optional) Select a specific interface by name.

summary (Optional) Displays IM database summary information.

verbose (Optional) Displays verbose information about IM database.

view (Optional) Specify a database view to filter the information based on the view

interface-type Interface type. For more information, use the question mark (?) online help function.

interface-instance Either a physical interface instance or a virtual interface instance as follows:

• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.

– rack: Chassis number of the rack.

– slot: Physical slot number of the modular services card or line card.

– module: Module number. A physical layer interface module (PLIM) is always 0.

– port: Physical port number of the interface.

Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.

• Virtual interface instance. Number range varies depending on interface type.


location node-id Displays IM control chain information for a specified node. The node-id argument is entered in the rack/slot/module notation.



OL-17332-01

Command Modes EXEC

Command History


Task ID

Examples The following example shows the output of the show im database command:

RP/0/RP0/CPU0:router# show im database verbose interface null 0

View: OWN - Owner, L3P - Local 3rd Party, G3P - Global 3rd Party, LDP - Local Data Plane, GDP - Global Data Plane, RED - Redundancy

Node 0/RP0/CPU0 (0x201)

Interface Null0, ifh 0x00080030 (up, 1500) Interface flags: 0x00010097 (IFINDEX|VIRTUAL|CONFIG|VIS|DATA|CONTRO Encapsulation: null Interface type: IFT_NULL Views: GDP|LDP|G3P|L3P|OWN Control location: 0/RP0/CPU0 Owner Private: 92 bytes Flags: <none> State Transitions: 1 Dampening Config: NO Shared Locks: 0 MTU default 1500 MTU ovh for bc/subif: 0/0 MTU min/max: 0/0










Release 3.8.0 This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Task ID Operations

cisco-support read

interface read



OL-17332-01

MTU avail/child: 0/1500 MTU actual/notified: 1500/1500 State (constraint): UP (UP) Callback: OWN GROUP OWNER - ID 17[-] Ctrl Flags: CFG_RDY|RDY|DNLD|INTF Instance ID: 31 Checkpoint: 48 bytes Resource in NetIO: TRUE

Protocol Caps (state, mtu) -------- ----------------- None null (up, 1500) Views: LDP|G3P|L3P|OWN Owner Private: 92 bytes Flags: <none> MTU min/max: 0/0 MTU avail/child: 1500/1500 MTU actual/notified: 1500/1500 State (constraint): UP (UP) Callback: OWN GROUP OWNER - ID 17[-] Ctrl Flags: CFG_RDY|RDY|DNLD Instance ID: 31 Checkpoint: 20 bytes Resource in NetIO: TRUE Demux limit: 0x00000000


Table 37 show im database Field Descriptions

Field Description

nodeid Identifier associated with the node.

Interface Interface name.

ifh Interface handle.

Protocol Protocol capsulations associated with the interface.

Caps (state, mtu) Capsulation names with associated state and MTU values.

Troubleshooting Commands on Cisco IOS XR Softwareshow imds interface brief


OL-17332-01

show imds interface brief To display interface information for the interface manager distribution server (IMDS), use the show imds interface brief command in EXEC mode.

show imds interface brief



Command Modes EXEC

Command History


Use the show imds interface brief command to display IMDS interface information. Use the command output to determine if the state, encapsulation being used, maximum transmission unit (MTU), and interface handle (ifhandle) for each interface are as expected.

Task ID











Task ID Operations

cisco-support read

Troubleshooting Commands on Cisco IOS XR Softwareshow imds interface brief


OL-17332-01

Examples The following example shows the output of the show imds interface brief command:

RP/0/RP0/CPU0:router# show imds interface brief

IMDS BRIEF INTERFACE DATA (Node 0x201) handle name flags state mtu encap---------- ----------------------- ------ ----------- -------- ---------------0x00080000 FINT0/RP0/CPU0 0x0007 up 8000 91 (fint_base) 0x00080010 Null0 0x100ab up 1500 17 (null) 0x00080020 MgmtEth0/RP0/CPU0/0 0x1002f up 1514 30 (ether) 0x00080030 Loopback0 0x100ab up 1514 16 (loopback) 0x00080050 Bundle-POS24 0x104ab up 4474 14 (hdlc) 0x00080070 Bundle-Ether28 0x104ab up 1514 30 (ether) 0x00080090 Bundle-Ether28.1 0x10cab up 1500 107 (dot1q) 0x000800b0 Bundle-Ether28.2 0x10cab up 1500 107 (dot1q) 0x000800d0 Bundle-Ether28.3 0x10cab up 1500 107 (dot1q) 0x01180000 FINT0/1/CPU0 0x0007 up 8000 91 (fint_base) 0x01180020 GigabitEthernet0/1/5/0 0x1002f up 1514 30 (ether) 0x01180040 GigabitEthernet0/1/5/1 0x1002f up 1514 30 (ether) 0x01180060 GigabitEthernet0/1/5/2 0x1002f up 1514 30 (ether) 0x01180080 GigabitEthernet0/1/5/3 0x1002f admin-down 1514 30 (ether) 0x011800a0 GigabitEthernet0/1/5/4 0x1002f down 1514 30 (ether) 0x011800c0 GigabitEthernet0/1/5/5 0x1002f admin-down 1514 30 (ether) ...0x01680480 SONET0/6/4/5 0x1006d up 10000 0 (Unknown) 0x016804a0 SonetPath0/6/4/5 0x10005 up 10000 0 (Unknown) 0x016804c0 POS0/6/4/5 0x1002f up 4474 14 (hdlc) 0x016804e0 SONET0/6/4/6 0x1006d up 10000 0 (Unknown) 0x01680500 SonetPath0/6/4/6 0x10005 up 10000 0 (Unknown) 0x01680520 POS0/6/4/6 0x1002f up 4474 14 (hdlc) 0x01680540 SONET0/6/4/7 0x1006d up 10000 0 (Unknown) 0x01680560 SonetPath0/6/4/7 0x10005 down 10000 0 (Unknown) 0x01680580 POS0/6/4/7 0x1002f admin-down 4474 14 (hdlc)


Related Commands

Table 38 show imds interface brief Field Descriptions

Field Description

name Interface name.

state Interface state.

mtu MTU associated with the interface.

encap Base encapsulation associated with the interface.

Command Description

show imds interface Displays interface information for the IMDS.

Troubleshooting Commands on Cisco IOS XR Softwareshow netio chains


OL-17332-01

show netio chainsTo display Network Input and Output (Netio) chains information for an interface, use the show netio chains command in EXEC mode.

show netio chains {interface-type interface-instance} [location node-id]

Syntax Description

Command Default No default behavior or values.

Command Modes EXEC

Command History











location node-id (Optional) Displays Netio chains information for a specified node. The node-id argument is entered in the rack/slot/module notation.


Release 3.8.0 This command was introduced.



OL-17332-01

Usage Guidelines To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator.

Task ID

Examples Example 1

This example shows the output of show netio chains command on a gigabitEthernet interface:

RP/0/0/CPU0:router# show netio chains gigabitEthernet 0/4/0/1

GigabitEthernet0/4/0/1 (handle: 0x05000500, nodeid 0x40) netio chains:---------------------------------Base decap chain: ether_shim <130> <0x79d99950, 0x0807bc84> < 0, 0> ether <30> <0x79d7eb14, 0x08079318> < 0, 0>

Protocol chains:---------------<Protocol number> (name) Stats Type Chain_node <caps num> <function, context> <drop pkts, drop bytes><7> (arp) Stats IN: 279 pkts, 16740 bytes; OUT: 279 pkts, 11718 bytes Encap: ether_shim <130> <0x79d99858, 0x081c649c> < 0, 0> l2_adj_rewrite <86> <0x7952437c, 0x081c5e4c> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0> Decap: arp <24> <0x79a9ba14, 0x00000000> < 0, 0> Fixup: l2_adj_rewrite <86> <0x795236c0, 0x081c5eb8> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0><12> (ipv4) Stats IN: 0 pkts, 0 bytes; OUT: 48 pkts, 9578 bytes Encap: ipv4 <26> <0x79aa2004, 0x0816c204> < 0, 0> ether <30> <0x79d7f634, 0x08079318> < 0, 0> ether_shim <130> <0x79d99858, 0x081c0ebc> < 0, 0> l2_adj_rewrite <86> <0x7952437c, 0x081c280c> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0> Decap: ipv4 <26> <0x79aa2054, 0x00000000> < 0, 0> Fixup: l2_adj_rewrite <86> <0x795236c0, 0x081c2878> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0><13> (mpls) Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes Encap: mpls <25> <0x79bd5f7c, 0x00000000> < 0, 0> ether <30> <0x79d7f634, 0x08079318> < 0, 0> ether_shim <130> <0x79d99858, 0x081cf838> < 0, 0> l2_adj_rewrite <86> <0x7952437c, 0x081cf52c> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0> Decap: mpls <25> <0x79bd3130, 0x00000000> < 0, 0> Fixup: l2_adj_rewrite <86> <0x795236c0, 0x081cf598> < 0, 0>

Task ID Operations

cisco-support read



OL-17332-01

txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0><22> (ether_sock) Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes Encap: ether_sock <98> <0x79d80aac, 0x08079318> < 0, 0> ether_shim <130> <0x79d99858, 0x0807bcfc> < 0, 0> l2_adj_rewrite <86> <0x7952437c, 0x0807b9a4> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0> Decap: ether_sock <98> <0x79d80ca8, 0x08079318> < 0, 0> Fixup: l2_adj_rewrite <86> <0x795236c0, 0x0807ba10> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0>

Protocol SAFI counts:--------------------

Protocol SAFI Pkts In Bytes In Pkts Out Bytes Out--------------- ---------- ---------- ---------- ---------- ---------- ipv4 Unicast 24330016 233944 8412 41 ipv4 Multicast 3240 60 0 0 ipv4 Broadcast 0 0 0 0 ipv6 Unicast 0 0 0 0 ipv6 Multicast 0 0 0 0

Node drop accounting:---------------------No drops

Example 2

RP/0/0/CPU0:router# show netio chains gigabitEthernet 0/4/0/1 location 0/4/CPU0

GigabitEthernet0/4/0/1 (handle: 0x05000500, nodeid 0x40) netio chains:---------------------------------Base decap chain: ether_shim <130> <0x79d99950, 0x0807bc84> < 0, 0> ether <30> <0x79d7eb14, 0x08079318> < 0, 0>

Protocol chains:---------------<Protocol number> (name) Stats Type Chain_node <caps num> <function, context> <drop pkts, drop bytes><7> (arp) Stats IN: 279 pkts, 16740 bytes; OUT: 279 pkts, 11718 bytes Encap: ether_shim <130> <0x79d99858, 0x081c649c> < 0, 0> l2_adj_rewrite <86> <0x7952437c, 0x081c5e4c> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0> Decap: arp <24> <0x79a9ba14, 0x00000000> < 0, 0> Fixup: l2_adj_rewrite <86> <0x795236c0, 0x081c5eb8> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0><12> (ipv4) Stats IN: 0 pkts, 0 bytes; OUT: 48 pkts, 9578 bytes Encap: ipv4 <26> <0x79aa2004, 0x0816c204> < 0, 0> ether <30> <0x79d7f634, 0x08079318> < 0, 0> ether_shim <130> <0x79d99858, 0x081c0ebc> < 0, 0> l2_adj_rewrite <86> <0x7952437c, 0x081c280c> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0> Decap: ipv4 <26> <0x79aa2054, 0x00000000> < 0, 0>



OL-17332-01

Fixup: l2_adj_rewrite <86> <0x795236c0, 0x081c2878> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0><13> (mpls) Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes Encap: mpls <25> <0x79bd5f7c, 0x00000000> < 0, 0> ether <30> <0x79d7f634, 0x08079318> < 0, 0> ether_shim <130> <0x79d99858, 0x081cf838> < 0, 0> l2_adj_rewrite <86> <0x7952437c, 0x081cf52c> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0> Decap: mpls <25> <0x79bd3130, 0x00000000> < 0, 0> Fixup: l2_adj_rewrite <86> <0x795236c0, 0x081cf598> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0><22> (ether_sock) Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes Encap: ether_sock <98> <0x79d80aac, 0x08079318> < 0, 0> ether_shim <130> <0x79d99858, 0x0807bcfc> < 0, 0> l2_adj_rewrite <86> <0x7952437c, 0x0807b9a4> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0> Decap: ether_sock <98> <0x79d80ca8, 0x08079318> < 0, 0> Fixup: l2_adj_rewrite <86> <0x795236c0, 0x0807ba10> < 0, 0> txm_nopull <60> <0x79516cd0, 0x0817cbd8> < 0, 0>



Node drop accounting:---------------------No drops


show netio clients Displays Netio clients information.

show netio db Displays Netio database information.

show netio idb Displays Netio IDB information.

show netio media registrations Displays protocol registrations for media changes.

show netio subblock Displays Netio subblock information.

show netio trace Displays Netio trace data.

Troubleshooting Commands on Cisco IOS XR Softwareshow netio clients


OL-17332-01

show netio clientsTo display Network Input and Output (Netio) clients information, use the show netio clients command in EXEC mode.

show netio clients [location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID

Examples Example

The following example shows the output of the show netio clients command:

RP/0/0/CPU0:router# show netio clients location 0/3/2

XIPC: OutputQ [0:0]/[6000] HighOutputQ [0:18]/[2000] PuntbackQ [0:0]/[6000]XIPC drops/total: OutputQ: 0/0 HighOutputQ: 0/15682677 PuntbackQ: 0/0Counters (error/total): Output (0/15682677) Puntback (0/0) Jump (0/0)

Input Punt XIPC InputQ XIPC PuntQClientID Drop/Total Drop/Total Cur/High/Max Cur/High/Max--------------------------------------------------------------------------------ipv6_icmp 0/0 0/0 0/0/1000 0/0/1000icmp 0/0 0/0 0/0/1000 0/0/1000clns 0/0 0/0 L 0/0/1000 0/0/0 H 0/0/1000chdlc_socket 0/802651 0/0 0/2/1000 0/0/0fr_socket 0/4454002 0/0 0/6/2000 0/0/0pre_route 0/0 0/0 0/0/1024 0/0/1024ipv6_io 0/0 0/0 0/0/1000 0/0/1000

location node-id (Optional) Displays Netio clients information for a specified node. The node-id argument is entered in the rack/slot/module notation.



Task ID Operations

cisco-support read

Troubleshooting Commands on Cisco IOS XR Softwareshow netio clients


OL-17332-01

ipv6_nd 0/0 0/0 0/0/1000 0/0/1000l2snoop 0/0 0/0 0/0/1000 0/0/0icmpv6_unreach_jump 0/0 0/0arp 0/0 0/0 0/0/1000 0/0/1000ppp 0/10432525 0/0 0/17/1000 0/0/0mpls_io 0/0 0/0 0/0/1000 0/0/1000ipv4 0/0 0/0 0/0/1000 0/0/1000ipv6 0/0 0/0 0/0/1000 0/0/1000

Key: L = queue for lower priority packets H = queue for higher priority packets


show netio chains Displays Netio chains information.






Troubleshooting Commands on Cisco IOS XR Softwareshow netio db


OL-17332-01

show netio dbTo display Network Input and Output (Netio) database information for an interface, use the show netio db command in EXEC mode.

show netio db {caps | dll | proto} [location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID

Examples Example

The following example shows the output of the show netio db command.

RP/0/5/CPU0:router# show netio db caps location 0/1/0

Capsulation (ID) Load Count DLL Name Refcountchdlc(13) 1 libchdlc_netio.dll 3hdlc(14) 2 libchdlc_netio.dll 3clns(15) 2 libclns_netio.dll 2ipv4_acl_in(22) 1 libipv4_netio_acl_filter.dll 2ipv4_acl_out(23) 1 libipv4_netio_acl_filter.dll 2arp(24) 1 libipv4_netio.dll 6mpls(25) 22 libmpls_netio.dll 3ipv4(26) 18 libipv4_netio.dll 6pim_enc(28) 2 libpim_encaps_netio.dll 1

caps Displays the capsulations in the Netio database.

dll Displays the dlls loaded in the Netio database.

proto Displays the protocol in the Netio database.

location node-id (Optional) Displays Netio database information for a specified node. The node-id argument is entered in the rack/slot/module notation.



Task ID Operations

cisco-support read

Troubleshooting Commands on Cisco IOS XR Softwareshow netio db


OL-17332-01

pim_null(29) 5 libpim_null_netio.dll 1ether(30) 2 libether_netio.dll 3mpls_te(36) 32 libmpls_netio.dll 3txm_nopull(60) 67 libsched_netio.dll 1lpts(81) 2 liblpts_netio.dll 2ipv6(82) 2 libipv6_netio.dll 5l2_adj_rewrite(86) 67 libl2_adj_netio.dll 1ipv6_preswitch(90) 1 libipv6_netio.dll 5fint_base(91) 10 libfint_netio.dll 1fint_n2n(92) 2 libfint_n2n.dll 2ether_sock(98) 2 libether_netio.dll 3ipv6_pfilter_in(102) 1 libipv6_netio_pfilter.dll 2ipv6_pfilter_out(103) 1 libipv6_netio_pfilter.dll 2netio_debug(110) 1 libnetio_debugnode.dll 1ipv4_preroute(115) 2 libipv4_netio.dll 6fint_l2transport(125) 2 libl2fib_netio.dll 2ipv6_preroute(128) 2 libipv6_netio.dll 5ether_shim(130) 4 libether_shim_netio.dll 1pos_shim(132) 3 libpos_shim_netio.dll 1fint_caps_tp(134) 2 libfint_netio_tp.dll 2








Troubleshooting Commands on Cisco IOS XR Softwareshow netio idb


OL-17332-01

show netio idb To display Network Input and Output (Netio) Interface Descriptor Block (IDB) information of an interface, use the show netio idb command in EXEC mode.

show netio idb {interface-type interface-instance}[location node-id]

Syntax Description


Command Modes EXEC

Command History











location node-id (Optional) Displays Netio IDB information for a specified node. The node-id argument is entered in the rack/slot/module notation.








OL-17332-01


Use the show netio idb command to display control plane information for the software switching path. The output provides useful statistics for determining software forwarding issues.

Task ID

Examples The following example shows the output of the show netio idb command:

RP/0/RP0/CPU0:router# show netio idb tenGigE 0/1/1/0 location 0/1/cpu0

TenGigE0/1/1/0 (handle: 0x01180020, nodeid:0x11) netio idb:---------------------------------name: TenGigE0_1_1_0interface handle: 0x01180020interface global index: 2physical media type: 30dchain ptr: <0x482ae8e0>echain ptr: <0x482d791c>fchain ptr: <0x482d79b8>driver cookie: <0x4824ad58>driver func: <0x4824ad44>number of subinterfaces: 4096subblock array size: 3DSNCNF: 0x00000000interface stats info: IN unknown proto pkts: 0 IN unknown proto bytes: 0 IN multicast pkts: 0 OUT multicast pkts: 0 IN broadcast pkts: 0 OUT broadcast pkts: 0 IN drop pkts: 0 OUT drop pkts: 0 IN errors pkts: 0 OUT errors pkts: 0

Chains--------------------Base decap chain: ether <30> <0xfd7aef88, 0x48302824> < 0, 0>





Release 3.8.0 Changed the interface-type interface-instance arguments to required ones.


Task ID Operations

cisco-support read



OL-17332-01

Protocol chains:---------------<Protocol number> (name) Stats Type Chain_node <caps num> <function, context> <drop pkts, drop bytes><7> (arp) Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes

Encap: l2_adj_rewrite <86> <0xfcec7a88, 0x4834efec> < 0, 0> queue_fifo <56> <0xfcedda68, 0x482dbee4> < 0, 0> txm_nopull <60> <0xfcea2a5c, 0x482dc11c> < 0, 0> Decap: queue_fifo <56> <0xfcedda4c, 0x482dbee4> < 0, 0> arp <24> <0xfd1082cc, 0x00000000> < 0, 0> Fixup: l2_adj_rewrite <86> <0xfcec745c, 0x00000000> < 0, 0> queue_fifo <56> <0xfcedda68, 0x482dbee4> < 0, 0> txm_nopull <60> <0xfcea2a5c, 0x482dc11c> < 0, 0><12> (ipv4) Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes Encap: ipv4 <26> <0xfd10f41c, 0x482d7724> < 0, 0> ether <30> <0xfd7aeb44, 0x48302824> < 0, 0> l2_adj_rewrite <86> <0xfcec7a88, 0x4834f104> < 0, 0> queue_fifo <56> <0xfcedda68, 0x482dbee4> < 0, 0> txm_nopull <60> <0xfcea2a5c, 0x482dc11c> < 0, 0> Decap: queue_fifo <56> <0xfcedda4c, 0x482dbee4> < 0, 0> ipv4 <26> <0xfd10f474, 0x00000000> < 0, 0> Fixup: l2_adj_rewrite <86> <0xfcec745c, 0x00000000> < 0, 0> queue_fifo <56> <0xfcedda68, 0x482dbee4> < 0, 0> txm_nopull <60> <0xfcea2a5c, 0x482dc11c> < 0, 0><22> (ether_sock) Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes Encap: ether_sock <98> <0xfd7b1630, 0x48302824> < 0, 0> l2_adj_rewrite <86> <0xfcec7a88, 0x48304c1c> < 0, 0> queue_fifo <56> <0xfcedda68, 0x482dbee4> < 0, 0> txm_nopull <60> <0xfcea2a5c, 0x482dc11c> < 0, 0> Decap: queue_fifo <56> <0xfcedda4c, 0x482dbee4> < 0, 0> ether_sock <98> <0xfd7b1874, 0x48302824> < 0, 0> Fixup: l2_adj_rewrite <86> <0xfcec745c, 0x00000000> < 0, 0> queue_fifo <56> <0xfcedda68, 0x482dbee4> < 0, 0> txm_nopull <60> <0xfcea2a5c, 0x482dc11c> < 0, 0>





OL-17332-01


Related Commands

Table 39 show netio idb Field Descriptions

Field Description

name Netio name associated with the interface.

interface handle Value assigned to the interface by the netio for identification.

IN unknown proto pkts Number of packets sent to netio that had an unknown protocol type.

IN unknown proto bytes Number of bytes sent to netio that had an unknown protocol type.

IN multicast pkts Number of ingress multicast packets for the interface.

OUT multicast pkts Number of egress multicast packets for the interface.

IN broadcast pkts Number of ingress broadcast packets for the interface.

OUT broadcast pkts Number of egress broadcast packets for the interface.

IN drop pkts Number of ingress dropped packets for the interface.

OUT drop pkts Number of egress dropped packets for the interface.

IN errors pkts Number of ingress errored packets for the interface.

OUT errors pkts Number of egress errored packets for the interface.

Base decap chain Lowest-level decap chain assigned to the interface.

Protocol chains Layer 3 protocol chains assigned to the interface.

Type Layer 3 protocol type.

drop pkts, drop bytes Dropped packet and byte counters associated with the protocol.

Endcap Processing steps in the encap chain.

Decap Processing steps in the decap chain.

Fixup Processing steps in the fixup chain.

Protocol SAFI counts Unicast or multicast counts associated with the protocol.

Protocol Protocol type.

SAFI Secondary address family identifier type.

Pkts In Number of packets in for the address family.

Bytes In Number of bytes in for the address family.

Pkts Out Number of packets out for the address family.

Bytes Out Number of bytes out for the address family.

Command Description







Troubleshooting Commands on Cisco IOS XR Softwareshow netio media-registrations


OL-17332-01

show netio media-registrationsTo display Network Input and Output (Netio) protocol registrations for media changes, use the show netio media-registrations command in EXEC mode.

show netio media-registrations [location node-id]

Syntax Description


Command Modes EXEC

Command History


Task ID

Examples Example

The following example shows the output of the show netio media-registrations command:

RP/0/5/CPU0:router# show netio media-registrations location 0/2/0

Registrations by L3 for media (change/upgrade) changesL3 Protocol Callback L2 Media--------------------------------------------clns 0x795f978c atm_mux_vc atm_nlpid_vc atm_snap_vc atm_sub dot1q ether fint_base fr_sub_base fr_vc_base hdlc srp

location node-id (Optional) Displays Netio protocol registrations for media changes for a specified node. The node-id argument is entered in the rack/slot/module notation.



Task ID Operations

cisco-support read

Troubleshooting Commands on Cisco IOS XR Softwareshow netio media-registrations


OL-17332-01

ipv4 0x79af58e8 atm_mux_vc atm_nlpid_vc atm_snap_vc atm_sub dot1q ether fint_base fr_sub_base fr_vc_base hdlc srpipv6 0x796a45e8 atm_mux_vc atm_nlpid_vc atm_snap_vc atm_sub dot1q ether fint_base fr hdlc srpmpls 0x79c66d14 atm_nlpid_vc atm_snap_vc atm_sub dot1q ether fint_base hdlc ppp srplpts 0x79563174 fint_baseipv6_preroute 0x796a456c fint_base








Troubleshooting Commands on Cisco IOS XR Softwareshow netio subblock


OL-17332-01

show netio subblockTo display Network Input and Output (Netio) subblock information, use the show netio subblock command in EXEC mode.

show netio subblock {idb{interface-type interface-instance} | registrations}[location node-id]

Syntax Description


Command Modes EXEC

Command History

idb Displays subblock information for an interface.

registrations Displays all the registered subblocks.











location node-id (Optional) Displays Netio subblock information for a specified node. The node-id argument is entered in the rack/slot/module notation.



Troubleshooting Commands on Cisco IOS XR Softwareshow netio subblock


OL-17332-01


Task ID

Examples Example

The following example shows the output of the show netio subblock command:

RP/0/5/CPU0:router# show netio subblock registrations location 0/2/2Feature Name Subblock List Destroy Func Handle <subblock addr> <intf handle> <intf name> <refcnt>---------------- ------------- --------------------- --------ipv6-switch 0x0811cbfc 0x796ae090 1 <0x0806a6b0> <0x03000100> <FINT0_2_CPU0 > < 3>ether-caps 0x08198ba0 0x79f350b4 2 <0x0807aa44> <0x03000600> <FastEthernet0_2_2_0 > < 3> <0x0807aa88> <0x03000700> <FastEthernet0_2_2_1 > < 3> <0x0807aacc> <0x03000800> <FastEthernet0_2_2_2 > < 3> <0x081c2758> <0x03000900> <FastEthernet0_2_2_3 > < 3> <0x081c279c> <0x03000a00> <FastEthernet0_2_2_4 > < 3> <0x081c27e0> <0x03000b00> <FastEthernet0_2_2_5 > < 3> <0x081c2824> <0x03000c00> <FastEthernet0_2_2_6 > < 3> <0x081c2868> <0x03000d00> <FastEthernet0_2_2_7 > < 4>fr_control_vc_base_caps 0x081bdf6c 0x7a0209c8 3 <0x081c2978> <0x03001a00> <POS0_2_0_0.0_vc_0 > < 2> <0x081c29bc> <0x03001b00> <POS0_2_0_1.0_vc_0 > < 2> <0x081c2a00> <0x03001c00> <POS0_2_0_0.0_vc_1023 > < 2> <0x081c2a44> <0x03001d00> <POS0_2_0_1.0_vc_1023 > < 2>fr_vc_base_caps 0x08206424 0x7a020890 4 <0x081c2a88> <0x03001e00> <POS0_2_0_0.1 > < 2> <0x081c2acc> <0x03001f00> <POS0_2_0_1.1 > < 2>

Related Commands

Task ID Operations

cisco-support read

Command Description







Troubleshooting Commands on Cisco IOS XR Softwareshow netio trace


OL-17332-01

show netio traceTo display Network Input and Output (Netio) trace information, use the show netio trace command in EXEC mode.

show netio trace {all | chains | control | dpc | error| interface | LC | packet} [file | hexdump | last | location | reverse | stats | tailf | unique | verbose | wrapping]

Syntax Description


Command Modes EXEC

Command History


all Displays all Netio trace data

chains Displays Netio chains trace data

control Displays Netio control trace data

dpc Displays Netio DPC trace data

error Displays Netio error trace data

interface Displays Netio interface trace data

LC Displays Netio trace information for LC processes data

packet Displays Netio packet drop error messages trace data

file (Optional) A specific file name traces in hexadecimal

hexdump (Optional) Display traces in hexadecimal

last (Optional) Displays the last n entries

location (Optional) Displays the card location

reverse (Optional) Displays the latest traces first

stats (Optional) Displays statistics

tailf (Optional) Displays new traces as added

unique (Optional) Displays unique entries with counts

verbose (Optional) Displays internal debugging information

wrapping (Optional) Displays wrapping entries





OL-17332-01

Task ID

Examples Example

The following example shows the output of the show netio trace command:

RP/0/0/CPU0:router# show netio trace chains stats location 0/0/CPU0 /net/node0_0_CPU0/dev/shmem/ltrace/netio/chains--- wrapping: inf Mbytes/sec for 1024 entries361 wrapping entries (1024 possible, 0 filtered, 361 total)Jan 11 15:04:14.695 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 0 (base), caps 91 (fint_base), op ADD, chain BD, data len 0Jan 11 15:04:15.070 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 18 (lpts), caps 81 (lpts), op ADD, chain D, data len 4Jan 11 15:04:16.265 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 18 (lpts), caps 86 (l2_adj_rewrite), op ADD, chain E, data len 0Jan 11 15:04:16.274 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 18 (lpts), caps 60 (txm_nopull), op ADD, chain E, data len 0Jan 11 15:04:16.542 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 18 (lpts), caps 86 (l2_adj_rewrite), op ADD, chain F, data len 0Jan 11 15:04:16.542 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 18 (lpts), caps 60 (txm_nopull), op ADD, chain F, data len 0Jan 11 15:04:16.542 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 18 (lpts), caps 91 (fint_base), op ADD, chain E, data len 0Jan 11 15:04:16.542 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 18 (lpts), caps 81 (lpts), op ADD, chain E, data len 4Jan 11 15:04:16.562 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 6 (fint_n2n), caps 92 (fint_n2n), op ADD, chain D, data len 0Jan 11 15:04:16.646 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 6 (fint_n2n), caps 86 (l2_adj_rewrite), op ADD, chain E, data len 0Jan 11 15:04:16.646 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 6 (fint_n2n), caps 60 (txm_nopull), op ADD, chain E, data len 0Jan 11 15:04:16.646 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 6 (fint_n2n), caps 86 (l2_adj_rewrite), op ADD, chain F, data len 0Jan 11 15:04:16.646 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 6 (fint_n2n), caps 60 (txm_nopull), op ADD, chain F, data len 0Jan 11 15:04:16.646 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, proto 6 (fint_n2n), caps 91 (fint_base), op ADD, chain E, data len 0Jan 11 15:04:16.646 netio/chains--- 0/0/CPU0 t1 Chains: update IDB chain, ifhandle 0x01000100, prot...

Task ID Operations

cisco-support read



OL-17332-01








Troubleshooting Commands on Cisco IOS XR Softwareshow sysdb trace verification location


OL-17332-01

show sysdb trace verification location To display trace verification information for the system database (SYSDB), use the show sysdb trace verification location command in EXEC mode.

show sysdb trace verification location node-id

Syntax Description


Command Modes EXEC

Command History


Use the show sysdb trace verification shared-plane location command to display details of recent verification sysDB transactions and changes on local plane configurations. The command output allows you to confirm that configuration were verified and accepted.

Task ID

node-id Specific node. The node-id argument is entered in the rack/slot/module notation.











Task ID Operations

sysmgr read

cisco-support read



OL-17332-01

Examples The following example shows the output of the show sysdb trace verification shared-plane location command. The output shows that changes to the SysDB local plane were verified and accepted.

RP/0/RP0/CPU0:router# show sysdb trace verification location 0/3/CPU0

Timestamp jid tid reg handle connid action path323 wrapping entries (4096 possible, 299 filtered, 622 total)Jul 7 20:10:36.212 260 1 90 8782 apply reply '--'Jul 7 20:10:35.476 260 1 90 4912 Apply/abort called 'cfg/if/act/GigabitEthernet0_3_4_0.1/a/sub_vlan/0x2/________/GigabitEthernet0_3_4_0/________'Jul 7 20:10:35.475 260 1 90 4912 verify reply: accept '--'Jul 7 20:10:35.471 260 1 90 4912 Verify called 'cfg/if/act/GigabitEthernet0_3_4_0.1/a/sub_vlan/0x2/________/GigabitEthernet0_3_4_0/________'Jul 7 20:10:35.471 144 1 4 8782 apply reply '--'Jul 7 20:10:35.471 144 1 4 8782 apply reply '--'Jul 7 20:10:35.471 144 1 4 8782 apply reply '--'Jul 7 20:10:35.471 144 1 4 8782 apply reply '--'Jul 7 20:10:35.471 144 1 4 8782 apply reply '--'Jul 7 20:10:35.471 144 1 4 8782 apply reply '--'Jul 7 20:10:35.471 144 1 4 8782 apply reply '--'Jul 7 20:10:35.471 144 1 4 8782 apply reply '--'Jul 7 20:10:35.470 144 1 4 474 Apply/abort batch ended ''Jul 7 20:10:35.470 144 1 4 474 Apply/abort called 'cfg/if/act/GigabitEthernet0_3_4_0/ord_x/im/shutdown'Jul 7 20:10:35.470 144 1 4 474 Apply/abort called 'cfg/if/act/GigabitEthernet0_3_4_1/ord_x/im/shutdown'Jul 7 20:10:35.470 144 1 4 474 Apply/abort called 'cfg/if/act/GigabitEthernet0_3_4_2/ord_x/im/shutdown'Jul 7 20:10:35.470 144 1 4 474 Apply/abort called 'cfg/if/act/GigabitEthernet0_3_4_3/ord_x/im/shutdown'Jul 7 20:10:35.470 144 1 4 474 Apply/abort called 'cfg/if/act/GigabitEthernet0_3_4_4/ord_x/im/shutdown'Jul 7 20:10:35.469 144 1 4 474 Apply/abort called 'cfg/if/act/GigabitEthernet0_3_4_5/ord_x/im/shutdown'Jul 7 20:10:35.469 144 1 4 474 Apply/abort called 'cfg/if/act/GigabitEthernet0_3_4_6/ord_x/im/shutdown'Jul 7 20:10:35.469 144 1 4 474 Apply/abort called 'cfg/if/act/GigabitEthernet0_3_4_7/ord_x/im/shutdown'Jul 7 20:10:35.469 144 1 4 474 Apply/abort batch started ''Jul 7 20:10:35.469 144 1 4 474 verify reply: accept '--'Jul 7 20:10:35.469 144 1 4 474 verify reply: accept '--'Jul 7 20:10:35.469 144 1 4 474 verify reply: accept '--'!!!



OL-17332-01


Related Commands

Table 40 show sysdb trace verification location Field Descriptions

Field Description

Timestamp Time of the verification.

jid Job identifier of the verification.

tid Thread identifier.

reg handle Registration handle.

connid Connection identifier.

action Action occurring between the sysDB server and client.

apply reply SysDB notification that the client that an apply action has occurred.

Apply/abort called SysDB notification for the client that an apply or abort has been called.

verify reply: accept Verifier has accepted the verification request.

Command Description

show sysdb connection path shared-plane

Displays sysDB client connection shared plane data for a specific path.

Troubleshooting Commands on Cisco IOS XR Softwareshow sysdb trace verification shared-plane


OL-17332-01

show sysdb trace verification shared-plane To display trace verification information for the system database (SYSDB), use the show sysdb trace verification shared-plane command in EXEC mode.

show sysdb trace verification shared-plane [file | hexdump | last | location | reverse | stats | tailf | unique | verbose | wrapping]

Syntax Description


Command Modes EXEC

Command History


file (Optional) Specifies the name of a file.

hexdump (Optional) Displays the packet contents in hexadecimal format.

last (Optional) Specifies the last number of packets in the queue to display.

location (Optional) Displays the card location.

reverse (Optional) Specifies the new traces as they are added.

stats (Optional) Displays trace statistics information.

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

unique (Optional) Displays a list of unique entries with counts.

verbose (Optional) Displays internal debugging information.

wrapping (Optional) Displays wrapping entries of all trace information.










Release 3.8.0 All optional arguments were added with their descriptions.

Troubleshooting Commands on Cisco IOS XR Softwareshow sysdb trace verification shared-plane


OL-17332-01

Use the show sysdb trace verification shared-plane command to display details of recent verification sysDB transactions and changes on the shared plane. The command output allows you to confirm whether the configuration was verified correctly.

Specifying a path using the | include keyword and path argument filters the data to display only the sysDB path for the router. Use the describe command to determine the path.

Task ID

Examples The following example shows the output of the show sysdb trace verification shared-plane command. The output shows that changes to the SysDB shared plane were verified and accepted.

RP/0/RP0/CPU0:router# show sysdb trace verification shared-plane | include gl/a/hostname

May 18 19:16:17.143 340 3 210 962 Apply/abort called 'cfg/gl/a/hostname'May 18 19:16:17.132 340 3 210 962 Verify called 'cfg/gl/a/hostname'May 18 19:16:17.126 340 3 210 962 Apply/abort called 'cfg/gl/a/hostname'May 18 19:16:17.109 340 3 210 962 Verify called 'cfg/gl/a/hostname'May 18 18:43:16.065 340 3 210 962 register 'cfg/gl/a/hostname'May 18 18:41:41.048 340 3 16 362 register 'cfg/gl/a/hostname'


Related Commands

Task ID Operations

sysmgr read

cisco-support read

Table 41 show sysdb trace verification shared-plane Field Descriptions

Field Description

Apply/abort called SysDB server has either applied or aborted the action requiring verification.

Verify called Client has issued a verify request to the sysDB server.

register Client has registered with sysDB server for verification.

Command Description

show sysdb connection path shared-plane

Displays sysDB client connection shared plane data for a specific path.

Troubleshooting Commands on Cisco IOS XR Softwareshow tbm hardware


OL-17332-01

show tbm hardware To displays tree bitmap hardware-related information, use the show tbm hardware command in EXEC mode.

show tbm hardware {ipv4 | ipv6 | mpls | vpnv4 | table-id | afi-all | sw-only | dual | egress | ingress} {unicast | multicast | safi-all} {dual | egress | ingress | sw-only} {brief | detail | lookup | prefix {prefix-hex-string}} location node-id

Syntax Description


Command Modes EXEC

ipv4 Specifies IP Version 4 address prefixes.

ipv6 Specifies IP Version 6 address prefixes.

mpls Specifies MPLS-related tree bitmap information.

vpnv4 Specifies VPNv4-related tree bitmap information.

table-id Specifies tree bitmap information for a specific table ID.

afi-all Specifies IPv4 and IPv6 commands.

sw-only Specifies software-only tree bitmap information.

dual Specifies tree bitmap information for dual, ingress, and egress, modes.

egress Specifies egress tree bitmap information.

ingress Specifies ingress tree bitmap information.

unicast Specifies unicast address prefixes.

multicast Specifies multicast address prefixes. This option is supported for IPv4 address families.

safi-all For subaddress family, specifies prefixes for all subaddress families. This option is supported for IPv4 address families.

dual Specifies ingress and egress tree bitmap information.

brief Displays brief information.

detail Displays detailed information.

lookup Displays key or address information to look up (longest match) in the table.

prefix Displays prefix-related information.

location node-id Displays tree bitmap hardware-related information for a specified node. The node-id argument is entered in the rack/slot/module notation.



OL-17332-01

Command History


Use the show tbm hardware command to display hardware-related ingress and egress information for the tree bitmap.

Task ID

Examples The following example shows the output of the show tbm hardware command:

RP/0/RP0/CPU0:router# show tbm hardware ipv4 unicast dual detail location 0/6/cpu0

TBM Table Type: IPv4 Unicast ------------------------------TBM: number of pulses: 71TBM: number of Err fix attempts: 0 No current failuresPast failures: leaf(0), mem(0), mipc(0), flush_mipc(0) post_compact(0), pre_compact(0)

PLU Bucket Statistics:----------------------------- Bucket 0: 44 Bucket 1: 44 Bucket 2: 327 Bucket 3: 44 Bucket 4: 44 Bucket 5: 43 Bucket 6: 43 Bucket 7: 45

Ingress PLU Info---------------- PLU: Num Writes : 3064 PLU: Num Copies : 2197











Task ID Operations

cisco-support read



OL-17332-01

PLU Memory Channel Statistics: ----------------------------- Number of compactions: 0 FCRAM0 Chan: 110 (Pages: 5, 1% used) FCRAM1 Chan: 125 (Pages: 8, 0% used) FCRAM2 Chan: 127 (Pages: 8, 0% used) FCRAM3 Chan: 148 (Pages: 8, 0% used) FCRAM4 Chan: 124 (Pages: 8, 0% used)

Egress PLU Info---------------- PLU: Num Writes : 3064 PLU: Num Copies : 2197

PLU Memory Channel Statistics: ----------------------------- Number of compactions: 0 FCRAM0 Chan: 110 (Pages: 5, 1% used) FCRAM1 Chan: 125 (Pages: 8, 0% used) FCRAM2 Chan: 127 (Pages: 8, 0% used) FCRAM3 Chan: 148 (Pages: 8, 0% used) FCRAM4 Chan: 124 (Pages: 8, 0% used)


Table 42 show tbm hardware Field Descriptions

Field Description

Past failures Number of times there was a failure in programming hardware.

PLU: Num Writes Number of writes to the PLU portion of the hardware.

PLU: Num Copies Number of copies to the PLU portion of the hardware.

PLU Memory Channel Statistics

Usage levels of each channel in the PLU memory.

Troubleshooting Commands on Cisco IOS XR Softwareshow uidb data


OL-17332-01

show uidb dataTo display index data information for the micro-interface descriptor block (uIDB), use the show uidb data command in EXEC mode.

show uidb data [shadow] [ingress | egress] [interface-type interface-instance] location node-id

Syntax Description


Command Modes EXEC

shadow (Optional) Displays uIDB data from shadow copy Route Skill Mapping (RSM) instead of Metro HW.

ingress (Optional) Displays ingress PSE-related information.

egress (Optional) Displays egress PSE-related information.











location node-id Displays micro-IDB index data information for a specified node. The node-id argument is entered in the rack/slot/module notation.



OL-17332-01

Command History


Use the show uidb index command to display micro-IDB index data information including, from a software perspective, features that are enabled on a selected interface.

Task ID

Examples The following example shows the output of the show uidb data command:

RP/0/RP1/CPU0:router# sh uidb data shadow ingress gigabitEthernet 0/2/4/4 loc 0/2/CPU0 -------------------------------------------------------------------------- Location = 0/2/CPU0 Ifname/Ifhandle = GigabitEthernet0_2_4_4 / 0x12800a0 Index = 5 Pse direction = INGRESS ============================================ * (Not programmed in hardware) * -------------------------------------------- RSM STATUS: 0x7c000000 -> used: 0x1f ->dirty: 0x00 ->badck: 0x00 -> prog: DONE ->count: 0 -------------------------------------------- BUNDLE IFHANDLE: 0 TUNNEL IFHANDLE: 0 L2 ENCAP: 3 ============================================







Release 3.5.0 Index and operation modes were not supported.


Release 3.7.0 The following keywords were added:

• shadow

• ingress

• egress


Task ID Operations

cisco-support read



OL-17332-01

General 16 bytes: ------------------------ IFHANDLE: 0x12800a STATUS: 1 ISSU State: 0 IPV4 ENABLE: 1 IPV6 ENABLE: 1 MPLS ENABLE: 0 STATS POINTER: 0x7ffd8 SPRAYER QUEUE: 36 IPV4 MULTICAST: 0 IPV6 MULTICAST: 0 USE TABLE ID IPV4: 0 USE TABLE ID IPV6: 0 USE TABLE ID MPLS: 0 TABLE ID: 0 QOS ENABLE: 0 QOS ID: 0 NETFLOW SAMPLING PERIOD: 0 L2 PKT DROP: 0 L2 QOS ENABLE: 0 SRC FWDING: 0 *[CHECKSUM]*: 0xff70f28c


Related Commands

Table 43 show uidb data Field Descriptions

Field Description

Location Node in system where the interface resides.

Ifname/Ifhandle Name associated with the interface.

Pse direction Direction flag for UIDB data.

INDEX STATUS Status of the interface.

L2 ENCAP L2 encap type.

SPRAYER QUEUE LSB Sprayer queue identifier.

ICMP PUNT FLAG Flag indicating ICMP punts are enabled for the protocol.

Command Description

show uidb trace Displays UIDB trace data debugging information that helps in troubleshooting the problem.

show uidb data-dump Displays UIDB data information in hexadecimal format.

Troubleshooting Commands on Cisco IOS XR Softwareshow uidb trace


OL-17332-01

show uidb traceTo display trace data information for the micro-interface descriptor block (IDB), use the show uidb trace command in EXEC mode.

show uidb trace {all | errors | events | init | rsm }

Syntax Description


Command Modes EXEC

Command History


Task ID

all Displays all UIDB trace information.

errors Displays information related to UIDB errors trace.

events Displays information related to UIDB events trace.

init Displays information related to UIDB init trace.

rsm Displays information related to UIDB rsm trace.







Release 3.5.0 Index and operation modes were not supported.




Task ID Operations

cisco-support read

Troubleshooting Commands on Cisco IOS XR Softwareshow uidb trace


OL-17332-01

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

RP/0/RP0/CPU0:router# sh uidb trace init loc 0/6/CPU0 --------------------------------------------------------------------------28 wrapping entries (512 possible, 0 filtered, 28 total)Mar 31 02:27:35.368 uidb_svr/initlog 0/6/CPU0 t1 Entering : Event manager initMar 31 02:27:36.641 uidb_svr/initlog 0/6/CPU0 t1 Successful : Event manager intMar 31 02:27:36.641 uidb_svr/initlog 0/6/CPU0 t1 Entering : Debug initMar 31 02:27:36.816 uidb_svr/initlog 0/6/CPU0 t1 Successful : Debug initMar 31 02:27:36.816 uidb_svr/initlog 0/6/CPU0 t1 Entering : MIPC bundMar 31 02:27:51.695 uidb_svr/initlog 0/6/CPU0 t1 Successful : MIPC bindMar 31 02:27:51.695 uidb_svr/initlog 0/6/CPU0 t1 PSE RSM : Init - main() : (50sMar 31 02:27:51.803 uidb_svr/initlog 0/6/CPU0 t1 Successful : PSE RSM Init sucdMar 31 02:27:51.803 uidb_svr/initlog 0/6/CPU0 t1 Entering : Metro bindMar 31 02:27:51.828 uidb_svr/initlog 0/6/CPU0 t1 Successful : Metro bindMar 31 02:27:51.828 uidb_svr/initlog 0/6/CPU0 t1 Entering : PLIM ASIC registerMar 31 02:27:51.922 uidb_svr/initlog 0/6/CPU0 t1 Successful : PLIM ASIC registrMar 31 02:27:51.922 uidb_svr/initlog 0/6/CPU0 t1 Entering : UIDB checkpoint intMar 31 02:27:51.944 uidb_svr/initlog 0/6/CPU0 t1 Successful : UIDB checkpoint tMar 31 02:27:51.944 uidb_svr/initlog 0/6/CPU0 t1 Entering : UIDB shadow memorytMar 31 02:27:51.944 uidb_svr/initlog 0/6/CPU0 t1 Successful : UIDB shadow memotMar 31 02:27:51.944 uidb_svr/initlog 0/6/CPU0 t1 Entering : UIDB EDM initMar 31 02:27:51.951 uidb_svr/initlog 0/6/CPU0 t1 Successful : UIDB EDM initMar 31 02:27:51.951 uidb_svr/initlog 0/6/CPU0 t1 Entering : Checkpoint ingresseMar 31 02:27:51.951 uidb_svr/initlog 0/6/CPU0 t1 Successful : Checkpoint ingreeMar 31 02:27:51.951 uidb_svr/initlog 0/6/CPU0 t1 Entering : Checkpoint egress e

Mar 31 02:27:51.951 uidb_svr/initlog 0/6/CPU0 t1 Successful : Checkpoint egrese


show uidb data Displays UIDB index data information.


Troubleshooting Commands on Cisco IOS XR Softwareshow uidb index


OL-17332-01

show uidb index To display micro-interface descriptor block (IDB) index information, use the show uidb index command in EXEC mode.

show uidb index



Command Modes EXEC

Command History


Use the show uidb index command to display the micro-IDB index assigned by the software.

Task ID

Examples The following example shows the output of the show uidb index command:

RP/0/RP0/CPU0:router# show uidb index

------------------------------------------------------------------------------ Location Interface-name Interface-Type Ingress-index Egress-index











Task ID Operations

cisco-support read



OL-17332-01

--------------------------------------------------------------------------- 0/1/CPU0 0 0 0 0/1/CPU0 GigabitEthernet0_1_5_0 Main interface 1 1 0/1/CPU0 GigabitEthernet0_1_5_1 Main interface 2 2 0/1/CPU0 GigabitEthernet0_1_5_2 Main interface 3 3 0/1/CPU0 GigabitEthernet0_1_5_3 Main interface 4 4 0/1/CPU0 GigabitEthernet0_1_5_4 Main interface 5 5 0/1/CPU0 GigabitEthernet0_1_5_5 Main interface 6 6 0/1/CPU0 GigabitEthernet0_1_5_6 Main interface 7 7 0/1/CPU0 GigabitEthernet0_1_5_7 Main interface 8 8 0/1/CPU0 POS0_1_0_0 Main interface 9 9 0/1/CPU0 POS0_1_4_0 Main interface 10 10 0/1/CPU0 POS0_1_0_1 Main interface 11 11 0/1/CPU0 POS0_1_4_1 Main interface 12 12 0/1/CPU0 POS0_1_0_2 Main interface 13 13 0/1/CPU0 POS0_1_4_2 Main interface 14 14 0/1/CPU0 POS0_1_0_3 Main interface 15 15 0/1/CPU0 POS0_1_4_3 Main interface 16 16 0/1/CPU0 Bundle-POS24 Bundle Interface 17 17 0/1/CPU0 Bundle-Ether28 Bundle Interface18 18 0/1/CPU0 Bundle-Ether28.1 Sub-interface 19 19 0/1/CPU0 Bundle-Ether28.2 Sub-interface 20 20 0/1/CPU0 Bundle-Ether28.3 Sub-interface 21 21 0/6/CPU0 0 0 0 0/6/CPU0 GigabitEthernet0_6_5_0 Main interface 1 1 0/6/CPU0 GigabitEthernet0_6_5_1 Main interface 2 2 0/6/CPU0 GigabitEthernet0_6_5_2 Main interface 3 3 0/6/CPU0 GigabitEthernet0_6_5_3 Main interface 4 4 0/6/CPU0 GigabitEthernet0_6_5_4 Main interface 5 5 0/6/CPU0 GigabitEthernet0_6_5_5 Main interface 6 6 0/6/CPU0 GigabitEthernet0_6_5_6 Main interface 7 7 0/6/CPU0 GigabitEthernet0_6_5_7 Main interface 8 8 0/6/CPU0 POS0_6_0_0 Main interface 9 9 0/6/CPU0 POS0_6_4_0 Main interface 10 10 0/6/CPU0 POS0_6_0_1 Main interface 11 11 0/6/CPU0 POS0_6_4_1 Main interface 12 12 0/6/CPU0 POS0_6_0_2 Main interface 13 13 0/6/CPU0 POS0_6_4_2 Main interface 14 14 0/6/CPU0 POS0_6_0_3 Main interface 15 15 0/6/CPU0 POS0_6_4_3 Main interface 16 16 0/6/CPU0 POS0_6_4_4 Main interface 17 17 0/6/CPU0 POS0_6_4_5 Main interface 18 18 0/6/CPU0 POS0_6_4_6 Main interface 19 19 0/6/CPU0 POS0_6_4_7 Main interface 20 20



OL-17332-01


Related Commands

Table 44 show uidb index Field Descriptions

Field Description

Location Node where index is located.

Interface-name Name of the interface.

Interface-Type Type of interface.

Ingress-index Value associated with ingress processing on the interface.

Egress-index Value associated with egress processing on the interface.

Command Description

show uidb data Displays IDB index data information.


Troubleshooting Commands on Cisco IOS XR Softwarewatchdog threshold memory


OL-17332-01

watchdog threshold memoryTo configure the value of memory available for each alarm threshold, use the watchdog threshold memory command in global configuration or interface configuration mode. To revert to the default threshold memory, use the no form of this command.

watchdog memory threshold [location node-id] minor percentage-memory-available severe percentage-memory-available critical percentage-memory-available

no watchdog memory threshold [location node-id] minor percentage-memory-available severe percentage-memory-available critical percentage-memory-available

Syntax Description

Defaults Use the show watchdog threshold memory defaults location all command to display the default memory thresholds.

Command Modes Global configuration Interface configuration

Command History


location node-id Configures the threshold memory for a specified node. The node-id argument is entered in the rack/slot/module notation.

minor Specifies the threshold for the minor state.

percentage-memory- available

Memory consumption percentage. Range is from 5 to 40.

severe Specifies the threshold for the severe state.

critical Specifies the threshold for the critical state.







Troubleshooting Commands on Cisco IOS XR Softwarewatchdog threshold memory


OL-17332-01

Use the watchdog threshold memory command to configure the memory thresholds. Threshold values can be applied to all nodes or a specific node using the location node-id keyword and argument. If the local threshold settings are removed, the local settings return to those set globally. In addition, you can view default and configured thresholds.

Table 45 lists the recommended memory threshold value calculations if the minor threshold is set to 20 percent, the severe threshold is set to 10 percent, and the critical threshold is set to 5 percent.

Task ID

Examples The following example shows how to configure the memory available for each alarm threshold:

RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# watchdog threshold memory location 0/RP0/CPU0 minor 30 severe 20 critical 10

Table 45 Recommended Memory Threshold Values

Total Available Memory (MB)

Minor Threshold (20 percent of available memory)

Severe Threshold (10 percent of available memory)

Critical Threshold (5 percent of available memory)

128 25.6 12.8 6.4

256 51.2 25.6 12.8

512 102.4 51.2 25.6

1024 204.8 102.4 51.2

2048 409.6 204.8 102.4

4096 819.2 409.6 204.8

Task ID Operations

cisco-support read, write


OL-17332-01

Tech-Support Commands on Cisco IOS XR Software

This module describes commands used for displaying the output of show commands using Cisco IOS XR software. The command output varies depending on the router platform and configuration.

The show tech-support commands all display common data from commands such as show version. Each show tech-support command also generates and gathers relevant data for a specific area. This data includes trace output to collect debugging information available in the specific area of interest.

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support


OL-17332-01

show tech-supportTo automatically run show commands that display system information, use the show tech-support command in the EXEC and administration EXEC modes.

show tech-support [password] {terminal [page] | file send-to [background] [compressed | uncompressed]} [location node-id]

Syntax Description password (Optional) Leaves passwords and other security information in the output. If not used, passwords and other security-sensitive information in the output are replaced with the label "<removed>".

terminal Displays command output on the terminal.

page (Optional) Displays the command output on a single page at a time. Use the Return key to display the next line of output or use the space bar to display the next page of information. If not used, the output scrolls (that is, it does not stop for page breaks).

Press the Ctrl-C keys to stop the command output.

file Specifies that the command output is saved to a specified file.

send-to Name of the file. The following valid options are listed:

• filename

• bootflash:filename

• compactflash:filename

• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename

• harddisk:filename

• harddiska:filename

• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename

background (Optional) Specifies that the command runs in the background.

compressed (Optional) Displays compressed command output.

uncompressed (Optional) Displays the command output with no compression.

location (Optional) Specifies a node.

node-id (Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.



OL-17332-01

Defaults The command output is not compressed. Passwords and other security information are not displayed.

Command Modes EXEC Administration EXEC

Command History


Tip This command can generate a very large amount of output. You may want to redirect the output to a file using the file send-to keyword and argument. Redirecting the output to a file also makes sending the output to your Cisco Technical Support representative easier.

Use the show tech-support command to run show commands that display system information. This command generates information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.

Note This command is not required during normal use of the router.

The following show commands run automatically when you run the show tech-support command:

• show running-config

• show version

• show interfaces

• show arm summary

• show arm conflicts

• show install













OL-17332-01

• show filesystem

• dir location all: pwd = disk0:

• dir location all: pwd = bootflash:

• run top_procs

• show processes aborts location all

• show processes blocked location all

• show placement nodes all

• show placement policy program all

• show memory summary location all

• show imds interface brief

• show lpts ifib brief

• show im chains all

• run gsp_show

• show context all location all

• show redundancy

• show dsc all

• show lr all

• show ipv4 traffic

• show ipv6 traffic

• show logging

• show inventory

• show packet-memory

• show packet-memory corrupt

• show packet-memory failures

• show platform

• show led

• show buffer reserved-memory

• show controllers fabricq eio links all

• show controllers pse eio links all

• show controllers plim asic pla eio links all

• show controllers fia eio links all

• show controllers cpuctrl summary

• admin show controllers fabric plane all

• admin show controllers fabric plane all stat

• admin show controllers fabric sfe fabricq all detail

• admin show controllers fabric sfe ingressq all detail

• admin show controllers fabric sfe s1 all detail




OL-17332-01


• show environment all

See the Cisco IOS XR command references for information about these commands and descriptions of their command output. The Cisco IOS XR command references are located at the following URL:

http://www.cisco.com/en/US/products/ps5845/prod_command_reference_list.html

Task ID

Examples The following example shows some of the show tech-support command output:

RP/0/RP0/CPU0:router# show tech-support terminal page

-------------------------------------------------------------------------------

show tech-support

-------------------------------------------------------------------------------

----------------------------- show running-config -----------------------------

Building configuration...!! Last configuration change at Tue Mar 27 15:36:13 2007 by user_A!hostname CRS-1line console exec-timeout 600 0 session-timeout 600!line default exec-timeout 600 0 session-timeout 600!clock timezone PST 8clock summer-time DST recurring 2 sunday march 02:00 first sunday november 02:00logging console informationaltelnet vrf default ipv4 server max-servers no-limitdomain ipv4 host p1 172.16.52.72domain ipv4 host p2 172.16.52.77domain ipv4 host ce6 172.16.52.73domain ipv4 host ce7 172.16.52.78domain ipv4 host pe6 172.16.52.128domain ipv4 host pe7 172.16.52.182domain ipv4 host pe11 172.16.52.83domain lookup disableusername CRS-1_2 password 7 <removed>!aps group 1 revert 1 channel 0 local SONET0/1/4/3 channel 1 local SONET0/1/4/2!vty-pool default 0 25

Task ID Operations

basic-services read




OL-17332-01

alias cr copy run disk0:/usr/base_configalias sa show aliasalias sc show config commit listalias sd show diagalias si show ip int briefalias sl show ledalias sm show mpls forwardingalias sp show platformalias sr show runalias su show usersalias sv show versionalias sir show ip routeipv4 virtual address 172.16.52.72 255.255.255.0hw-module service sbc location 0/4/CPU0hw-module service sbc location 0/4/CPU1interface Bundle-Ether28 description Connected to CRS-1_2 Bundle-Ether 28 ipv4 address 10.0.28.1 255.255.255.0 bundle minimum-active links 1 bundle minimum-active bandwidth 1000000!interface Bundle-Ether28.1 description Connected to CRS-1_2 Bundle-Ether 28.1 ipv4 address 10.0.29.1 255.255.255.0 dot1q vlan 29!interface Bundle-Ether28.2 dot1q vlan 30 description Connected to CRS-1_2 Bundle-Ether 28.2 ipv4 address 10.0.30.1 255.255.255.0!interface Bundle-Ether28.3 description Connected to CRS-1_2 Bundle-Ether 28.3 ipv4 address 10.0.31.1 255.255.255.0 dot1q vlan 31!interface Bundle-POS24 bundle minimum-active bandwidth 2488320 bundle minimum-active links 1 ipv4 address 10.10.24.1 255.255.255.0...

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support asic


OL-17332-01

show tech-support asic To save a snapshot of ASIC information specific to ASIC debugging, use the show tech-support asic command in administration EXEC mode.

show tech-support asic {name | all | cpuctrl | fabricq | ingressq | pse} {directory path | instance instance directory path} [location node-id]

Syntax Description



Command History


name ASIC name.

all Specifies all ASICs.

cpuctrl Specifies CPU controller ASICs.

fabricq Specifies fabric queue ASICs.

ingressq Specifies ingress queue ASICs.

pse Specifies power sourcing equipment ASICs.

directory Directory to save the ASIC snapshot in.

path Path of the directory.

instance Specifies an ASIC instance.

instance ASIC instance. Range is 0 to 8.











OL-17332-01

Use the show tech-support asic command to save an ASIC snapshot. This command generates ASIC information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support ASIC command:

• show hfr

• show controllers ingressq statistics location

• show controllers ingressq block fqm queues location

• show asic-errors ingressq 0 all location

• show controllers ingressq block brm location

• show controllers ingressq block brm aggrbarr location

• show controllers ingressq fabric detail location

• show controllers ingressq fabric links location

• show controllers ingressq fabric pla location

• show controllers ingressq eio links all location

• show controllers ingressq interfaces all location

• show controllers ingressq vports all location

• show controllers ingressq queues all location

• show controllers ingressq block ssm bpmem 0 location

• show controllers asic sprayer in nn location | exclude nn

• show controllers fabricq fabric-backpressure location

• show controllers fabricq link-info all location

• show controllers cpuctrl clients cdma ingressq active location

• show controllers cpuctrl clients cdma ingressq detail location

• show asic-errors pse 0 all location



Task ID Task ID Operations

admin read




OL-17332-01

Examples The following example shows some of the show tech-support asic command output:

RP/0/RP0/CPU0:router(admin)# show tech-support asic all inst 0 dir net/node0_RP0_CPU0/ harddisk:/asic_snapshots/

results in following files being created with contents..# pwd/net/node0_RP0_CPU0/harddisk:/asic_snapshots# ls -lrttotal 980...

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support bcdl


OL-17332-01

show tech-support bcdl To automatically run show commands that display information specific to Bulk Content DownLoader (BCDL) debugging, use the show tech-support bcdl command in EXEC mode.

show tech-support bcdl [bcdl-group] {terminal [page] | file send-to [background] [compressed | uncompressed]}

Syntax Description

Defaults The command output is not compressed.

Command Modes EXEC

bcdl-group (Optional) Name of the BCDL group.

terminal Displays the command output on the terminal.




sent-to Name of the file. The following valid options are listed:

• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename






OL-17332-01

Command History



Use the show tech-support bcdl command to run show commands that display information specific to BCDL debugging. The BCDL is used to pass routing information from the Routing Information Base (RIB) to the linecards for Forwarding Information Base (FIB) processing. BCDL also allows Multiprotocol Label Switching (MPLS) to send label information to the FIB and allows Local Packet Transport Services (LPTS) to send information to the linecard processes. This command generates BCDL debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support bcdl command:

• show bcdl

• show bcdl consumers

• show bcdl tables

• show process bcdl_agent

• show bcdl trace location all















OL-17332-01

Task ID

Examples The following example shows some of the show tech-support bcdl command output:

RP/0/RP0/CPU0:router# show tech-support bcdl terminal page

Mon Nov 10 18:29:05.526 PST DST

-------------------------------------------------------------------------------

show tech-support bcdl

-------------------------------------------------------------------------------

---------------------------------- show bcdl ----------------------------------grp ipv4_lmrib, gid 2104, sg cnt 1, agent jid 117, node 0/RP0/CPU0, pulse 0, ne0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2105 16 6 no yes no 0 0 0 0

grp ipv4_mrib, gid 2102, sg cnt 1, agent jid 116, node 0/RP0/CPU0, pulse 0, new0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2103 16 6 no yes no 0 0 0 0

grp ipv4_rib, gid 2049, sg cnt 1, agent jid 111, node 0/RP0/CPU0, pulse 38335, 0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2050 16 6 no no no 0 38387 38330 0

grp ipv6_mrib, gid 2100, sg cnt 1, agent jid 115, node 0/RP0/CPU0, pulse 0, new0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2101 16 6 no yes no 0 0 0 0

grp ipv6_rib, gid 2051, sg cnt 1, agent jid 112, node 0/RP0/CPU0, pulse 6, new 0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2052 16 6 no no no 0 1 1 0

grp mpls_lsd_v4, gid 2060, sg cnt 1, agent jid 113, node 0/RP0/CPU0, pulse 38430sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2061 17 6 no no no 0 38431 38432 0

grp mpls_lsd_v6, gid 2062, sg cnt 1, agent jid 114, node 0/RP0/CPU0, pulse 7, n0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2063 17 6 no no no 0 1 2 0

grp pa_ff, gid 2021, sg cnt 1, agent jid 110, node 0/RP0/CPU0, pulse 271, new m0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2022 16 6 no no no 0 260 259 0

Mon Nov 10 18:29:05.992 PST DST

----------------------------- show bcdl consumers -----------------------------group ipv4_lmrib, gsp gid 2104, 6 consumers, agent jid 117, node 0/RP0/CPU0(expected 6 consumers to reply, received 6 replies)pid node asg csg lwg sus messages bytes errs name458887 0/RP0/CPU0 0 0 2105 N 0 0 0 fib_mgr209032 0/RP1/CPU0 0 0 2105 N 0 0 0 fib_mgr

Task ID Operations

basic-services or cisco-support

read

sysmgr read



OL-17332-01

90198 0/6/CPU0 0 0 2105 N 0 0 0 fib_mgr106592 0/4/CPU0 0 0 2105 N 0 0 0 fib_mgr114782 0/4/CPU1 0 0 2105 N 0 0 0 fib_mgr90198 0/1/CPU0 0 0 2105 N 0 0 0 fib_mgr

group ipv4_mrib, gsp gid 2102, 6 consumers, agent jid 116, node 0/RP0/CPU0(expected 6 consumers to reply, received 6 replies)pid node asg csg lwg sus messages bytes errs name790787 0/RP0/CPU0 0 0 2103 N 0 0 0 ipv4_mfwd_pare262380 0/RP1/CPU0 0 0 2103 N 0 0 0 ipv4_mfwd_pare127125 0/1/CPU0 0 0 2103 N 0 0 0 ipv4_mfwd_pare139404 0/4/CPU1 0 0 2103 N 0 0 0 ipv4_mfwd_pare127114 0/6/CPU0 0 0 2103 N 0 0 0 ipv4_mfwd_pare131214 0/4/CPU0 0 0 2103 N 0 0 0 ipv4_mfwd_pare

group ipv4_rib, gsp gid 2049, 6 consumers, agent jid 111, node 0/RP0/CPU0(expected 6 consumers to reply, received 6 replies)pid node asg csg lwg sus messages bytes errs name458887 0/RP0/CPU0 0 0 2050 N 38387 4599212 0 fib_mgr209032 0/RP1/CPU0 0 0 2050 N 38385 4599156 0 fib_mgr114782 0/4/CPU1 0 0 2050 N 38330 4574016 0 fib_mgr90198 0/6/CPU0 0 0 2050 N 38363 4597820 0 fib_mgr90198 0/1/CPU0 0 0 2050 N 38385 4599156 0 fib_mgr106592 0/4/CPU0 0 0 2050 N 38333 4580188 0 fib_mgr

group ipv6_mrib, gsp gid 2100, 6 consumers, agent jid 115, node 0/RP0/CPU0(expected 6 consumers to reply, received 6 replies)pid node asg csg lwg sus messages bytes errs name790788 0/RP0/CPU0 0 0 2101 N 0 0 0 ipv6_mfwd_pare262381 0/RP1/CPU0 0 0 2101 N 0 0 0 ipv6_mfwd_pare127126 0/1/CPU0 0 0 2101 N 0 0 0 ipv6_mfwd_pare127115 0/6/CPU0 0 0 2101 N 0 0 0 ipv6_mfwd_pare139405 0/4/CPU1 0 0 2101 N 0 0 0 ipv6_mfwd_pare131215 0/4/CPU0 0 0 2101 N 0 0 0 ipv6_mfwd_pare

group ipv6_rib, gsp gid 2051, 6 consumers, agent jid 112, node 0/RP0/CPU0(expected 6 consumers to reply, received 6 replies)pid node asg csg lwg sus messages bytes errs name458887 0/RP0/CPU0 0 0 2052 N 1 28 0 fib_mgr209032 0/RP1/CPU0 0 0 2052 N 2 56 0 fib_mgr90198 0/1/CPU0 0 0 2052 N 2 56 0 fib_mgr106592 0/4/CPU0 0 0 2052 N 2 56 0 fib_mgr90198 0/6/CPU0 0 0 2052 N 2 56 0 fib_mgr114782 0/4/CPU1 0 0 2052 N 2 56 0 fib_mgr

group mpls_lsd_v4, gsp gid 2060, 6 consumers, agent jid 113, node 0/RP0/CPU0(expected 6 consumers to reply, received 6 replies)pid node asg csg lwg sus messages bytes errs name458887 0/RP0/CPU0 0 0 2061 N 38431 6895816 0 fib_mgr209032 0/RP1/CPU0 0 0 2061 N 38431 6895816 0 fib_mgr90198 0/1/CPU0 0 0 2061 N 38431 6895816 0 fib_mgr90198 0/6/CPU0 0 0 2061 N 38431 6895816 0 fib_mgr106592 0/4/CPU0 0 0 2061 N 38431 6895816 0 fib_mgr114782 0/4/CPU1 0 0 2061 N 38431 6895816 0 fib_mgr

group mpls_lsd_v6, gsp gid 2062, 6 consumers, agent jid 114, node 0/RP0/CPU0(expected 6 consumers to reply, received 6 replies)pid node asg csg lwg sus messages bytes errs name458887 0/RP0/CPU0 0 0 2063 N 1 228 0 fib_mgr209032 0/RP1/CPU0 0 0 2063 N 1 228 0 fib_mgr90198 0/1/CPU0 0 0 2063 N 1 228 0 fib_mgr90198 0/6/CPU0 0 0 2063 N 1 228 0 fib_mgr106592 0/4/CPU0 0 0 2063 N 1 228 0 fib_mgr114782 0/4/CPU1 0 0 2063 N 1 228 0 fib_mgr



OL-17332-01

group pa_ff, gsp gid 2021, 6 consumers, agent jid 110, node 0/RP0/CPU0(expected 6 consumers to reply, received 6 replies)pid node asg csg lwg sus messages bytes errs name471193 0/RP0/CPU0 0 0 2022 N 260 52876 0 pifibm_server90221 0/6/CPU0 0 0 2022 N 33 18516 0 pifibm_server90214 0/1/CPU0 0 0 2022 N 33 18516 0 pifibm_server110695 0/4/CPU0 0 0 2022 N 209 48132 0 pifibm_server118885 0/4/CPU1 0 0 2022 N 224 50052 0 pifibm_server221341 0/RP1/CPU0 0 0 2022 N 251 52796 0 pifibm_server

Mon Nov 10 18:29:06.427 PST DST

------------------------------ show bcdl tables -------------------------------grp ipv4_lmrib, gid 2104, sg cnt 1, agent jid 117, node 0/RP0/CPU0, pulse 0, ne0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2105 16 6 no yes no 0 0 0 0sgs: 1, table_cnt: 0, table_mid_cnt: 0, buf size: 20Showing table info for 1 subgroupssg 0: has 0 tables (messages: 0, bytes: 0)

grp ipv4_mrib, gid 2102, sg cnt 1, agent jid 116, node 0/RP0/CPU0, pulse 0, new0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2103 16 6 no yes no 0 0 0 0sgs: 1, table_cnt: 0, table_mid_cnt: 0, buf size: 20Showing table info for 1 subgroupssg 0: has 0 tables (messages: 0, bytes: 0)

grp ipv4_rib, gid 2049, sg cnt 1, agent jid 111, node 0/RP0/CPU0, pulse 38335, 0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2050 16 6 no no no 0 38387 38330 0sgs: 1, table_cnt: 1, table_mid_cnt: 6, buf size: 124Showing table info for 1 subgroupssg 0: has 1 tables (messages: 0, bytes: 0)table 0xe0000000: 6 members, dnld act: 0, messages: 38387, bytes: 4599212cnsmr 0: pid 458887 on node 0/RP0/CPU0cnsmr 1: pid 209032 on node 0/RP1/CPU0cnsmr 2: pid 90198 on node 0/1/CPU0cnsmr 3: pid 90198 on node 0/6/CPU0cnsmr 4: pid 106592 on node 0/4/CPU0cnsmr 5: pid 114782 on node 0/4/CPU1

grp ipv6_mrib, gid 2100, sg cnt 1, agent jid 115, node 0/RP0/CPU0, pulse 0, new0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2101 16 6 no yes no 0 0 0 0sgs: 1, table_cnt: 0, table_mid_cnt: 0, buf size: 20Showing table info for 1 subgroupssg 0: has 0 tables (messages: 0, bytes: 0)

grp ipv6_rib, gid 2051, sg cnt 1, agent jid 112, node 0/RP0/CPU0, pulse 6, new 0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2052 16 6 no no no 0 1 1 0sgs: 1, table_cnt: 1, table_mid_cnt: 6, buf size: 124Showing table info for 1 subgroupssg 0: has 1 tables (messages: 0, bytes: 0)table 0xe0800000: 6 members, dnld act: 0, messages: 1, bytes: 28cnsmr 0: pid 458887 on node 0/RP0/CPU0cnsmr 1: pid 209032 on node 0/RP1/CPU0cnsmr 2: pid 90198 on node 0/1/CPU0cnsmr 3: pid 90198 on node 0/6/CPU0cnsmr 4: pid 106592 on node 0/4/CPU0cnsmr 5: pid 114782 on node 0/4/CPU1

grp mpls_lsd_v4, gid 2060, sg cnt 1, agent jid 113, node 0/RP0/CPU0, pulse 38430



OL-17332-01

sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2061 17 6 no no no 0 38431 38432 0sgs: 1, table_cnt: 0, table_mid_cnt: 0, buf size: 20Showing table info for 1 subgroupssg 0: has 0 tables (messages: 38431, bytes: 6895816)

grp mpls_lsd_v6, gid 2062, sg cnt 1, agent jid 114, node 0/RP0/CPU0, pulse 7, n0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2063 17 6 no no no 0 1 2 0sgs: 1, table_cnt: 0, table_mid_cnt: 0, buf size: 20Showing table info for 1 subgroupssg 0: has 0 tables (messages: 1, bytes: 228)

grp pa_ff, gid 2021, sg cnt 1, agent jid 110, node 0/RP0/CPU0, pulse 271, new m0sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out0 2022 16 6 no no no 0 260 259 0sgs: 1, table_cnt: 0, table_mid_cnt: 0, buf size: 20Showing table info for 1 subgroupssg 0: has 0 tables (messages: 260, bytes: 52876)

Mon Nov 10 18:29:15.426 PST DST

--------------------------- show process bcdl_agent ---------------------------Job Id: 110PID: 462997Executable path: /disk0/hfr-base-3.8.0.20I/sbin/bcdl_agentInstance #: 1Args: -p pa_ff -m 0 -b 0 -d libbcdl_pa_ff.dllVersion ID: 00.00.0000Respawn: ONRespawn count: 1Max. spawns per minute: 12Last started: Tue Nov 4 02:01:52 2008Process state: RunPackage state: Normalcore: MAINMEMMax. core: 0startup_path: /pkg/startup/bcdl_agent.startupReady: 2.321sProcess cpu time: 3.115 user, 0.421 kernel, 3.536 totalJID TID Stack pri state TimeInState HR:MM:SS:MSEC NAME110 1 44K 10 Receive 160:27:23:0754 0:00:00:0053 bcdl_agent110 2 44K 10 Condvar 89:29:17:0305 0:00:00:0003 bcdl_agent110 3 44K 10 Receive 0:00:00:0745 0:00:01:0815 bcdl_agent110 4 44K 10 Nanosleep 0:00:06:0200 0:00:00:0025 bcdl_agent110 5 44K 10 Receive 0:00:12:0728 0:00:00:0000 bcdl_agent-------------------------------------------------------------------------------Job Id: 111PID: 479442Executable path: /disk0/hfr-base-3.8.0.20I/sbin/bcdl_agentInstance #: 2Args: -p ipv4_rib -m 0 -b 65200Version ID: 00.00.0000Respawn: ONRespawn count: 1Max. spawns per minute: 12Last started: Tue Nov 4 02:02:35 2008Process state: RunPackage state: Normalcore: MAINMEMMax. core: 0startup_path: /pkg/startup/bcdl_agent.startupReady: 3.682sProcess cpu time: 14.430 user, 1.416 kernel, 15.846 total



OL-17332-01

111 2 52K 10 Condvar 155:55:15:0696 0:00:00:0012 bcdl_agent111 3 52K 10 Receive 160:25:30:0729 0:00:00:0000 bcdl_agent111 4 52K 10 Nanosleep 0:00:01:0628 0:00:00:0026 bcdl_agent111 5 52K 10 Receive 0:00:01:0441 0:00:08:0542 bcdl_agent111 6 52K 10 Receive 0:00:13:0163 0:00:00:0000 bcdl_agent-------------------------------------------------------------------------------Job Id: 112PID: 479443Executable path: /disk0/hfr-base-3.8.0.20I/sbin/bcdl_agentInstance #: 3Args: -p ipv6_rib -m 0 -b 65200Version ID: 00.00.0000Respawn: ONRespawn count: 1Max. spawns per minute: 12Last started: Tue Nov 4 02:02:36 2008Process state: RunPackage state: Normalcore: MAINMEMMax. core: 0startup_path: /pkg/startup/bcdl_agent.startupReady: 3.545sProcess cpu time: 3.695 user, 0.428 kernel, 4.123 total112 1 48K 10 Receive 160:26:39:0019 0:00:00:0054 bcdl_agent112 2 48K 10 Condvar 155:55:17:0392 0:00:00:0002 bcdl_agent112 3 48K 10 Receive 0:00:14:0512 0:00:03:0983 bcdl_agent112 4 48K 10 Nanosleep 0:00:02:0509 0:00:00:0030 bcdl_agent112 6 48K 10 Receive 0:00:02:0001 0:00:00:0001 bcdl_agent-------------------------------------------------------------------------------Job Id: 113PID: 483569Executable path: /disk0/hfr-base-3.8.0.20I/sbin/bcdl_agentInstance #: 4Args: -p mpls_lsd_v4 -m 10 -b 32768Version ID: 00.00.0000Respawn: ONRespawn count: 1Max. spawns per minute: 12Last started: Tue Nov 4 02:03:06 2008Process state: RunPackage state: Normalcore: MAINMEMMax. core: 0startup_path: /pkg/startup/bcdl_agent.startupReady: 1.987sProcess cpu time: 18.238 user, 1.777 kernel, 20.015 total113 2 48K 10 Condvar 160:22:55:0518 0:00:00:0002 bcdl_agent113 3 48K 10 Receive 160:26:09:0157 0:00:00:0000 bcdl_agent113 4 48K 10 Nanosleep 0:00:16:0592 0:00:00:0018 bcdl_agent113 5 48K 10 Receive 0:00:00:0289 0:00:00:0002 bcdl_agent113 6 48K 10 Receive 0:00:15:0924 0:00:01:0234 bcdl_agent-------------------------------------------------------------------------------Job Id: 114PID: 487660Executable path: /disk0/hfr-base-3.8.0.20I/sbin/bcdl_agentInstance #: 5Args: -p mpls_lsd_v6 -m 10 -b 32768Version ID: 00.00.0000Respawn: ONRespawn count: 1Max. spawns per minute: 12Last started: Tue Nov 4 02:03:06 2008Process state: RunPackage state: Normal



OL-17332-01

core: MAINMEMMax. core: 0startup_path: /pkg/startup/bcdl_agent.startupReady: 2.145sProcess cpu time: 4.206 user, 0.496 kernel, 4.702 total114 1 52K 10 Receive 0:00:04:0881 0:00:04:0595 bcdl_agent114 2 52K 10 Condvar 160:22:56:0168 0:00:00:0003 bcdl_agent114 3 52K 10 Receive 160:26:09:0766 0:00:00:0000 bcdl_agent114 4 52K 10 Nanosleep 0:00:16:0666 0:00:00:0019 bcdl_agent114 5 52K 10 Receive 0:00:16:0589 0:00:00:0001 bcdl_agent

--More--...

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support bundles


OL-17332-01

show tech-support bundlesTo automatically run show commands that display information specific to bundle debugging, use the show tech-support bundles command in EXEC mode.

show tech-support bundles {terminal [page] | file send-to [background] compressed | uncompressed]} [interface type interface-path-id] [show-only] [trace-only] [vrf vrf-name] [location node-id | all]

Syntax Description file Specifies that the command output is saved to a specified file.


• filename



• compactflasha:filename

• disk0:filename

• disk0a:filename

• disk1:filename

• disk1a:filename

• ftp:filename



• harddiskb:filename

• nvram:filename

• rcp:filename

• tftp:filename




interface (Optional) Collects information about a specific interface.





show-only (Optional) Collects only show command information.


trace-only (Optional) Collects only trace information.



OL-17332-01

Command Modes EXEC

Command History



Use the show tech-support bundles command for 802.3ad link bundles. This command is used to locate any issues related to bundling. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.



vrf (Optional) Specifies a VPN routing and forwarding (VRF) instance.

vrf-name (Optional) Name of VRF.


node-id (Optional). Node ID. The node-id argument is entered in the rack/slot/module notation.

all (Optional) Specifies all locations.
















OL-17332-01

Task ID

Examples The following shows some of the show tech-support bundles command output that is displayed for the terminal:

RP/0/RP0/CPU0:router# show tech-support bundles terminal

-------------------------------------------------------------------------------

show tech-support bundles

-------------------------------------------------------------------------------

----------------------------- show running-config -----------------------------Building configuration...!! Last configuration change at Wed Oct 10 20:05:13 2007 !hostname P1_CRS-8line console exec-timeout 600 0 session-timeout 600!line default exec-timeout 600 0 session-timeout 600!clock timezone PST 8clock summer-time DST recurring 2 sunday march 02:00 first sunday november 02:00logging console informationaltelnet vrf default ipv4 server max-servers no-limitdomain ipv4 host p1 172.29.52.72domain ipv4 host p2 172.29.52.77domain ipv4 host ce6 172.29.52.73domain ipv4 host ce7 172.29.52.78domain ipv4 host p11 172.29.52.83domain ipv4 host pe6 172.29.52.128domain ipv4 host pe7 172.29.52.182domain ipv4 host ce25 172.29.52.85domain ipv4 host ce28 172.29.52.1domain ipv4 host ce29 172.29.52.178domain ipv4 host pe21 172.29.52.163domain ipv4 host pe22 172.29.52.219domain ipv4 host ce28_nme 172.29.52.177domain ipv4 host ce29_nme 172.29.52.179domain lookup disableusername P2_CRS-8 password 7 13061E010803!aps group 1 revert 1 channel 0 local SONET0/1/4/3 channel 1 local SONET0/1/4/2!vty-pool default 0 25alias cr copy run disk0:/usr/P1_base_configalias sa show aliasalias sc show config commit listalias sd show diag

Task ID Operations

cisco-support read



OL-17332-01

alias si show ip int briefalias sl show ledalias sm show mpls forwardingalias sp show platformalias sr show runalias su show usersalias sv show versionalias sir show ip routecontrol-plane management-plane inband interface all allow all ! ! !!ipv4 virtual address 172.29.52.72 255.255.255.0hw-module service sbc location 0/4/CPU0hw-module service sbc location 0/4/CPU1interface Bundle-Ether28 description Connected to P2_CRS-8 Bundle-Ether 28 ipv4 address 10.12.28.1 255.255.255.0 bundle minimum-active links 1 bundle minimum-active bandwidth 1000000!interface Bundle-Ether28.1 description Connected to P2_CRS-8 Bundle-Ether 28.1 ipv4 address 10.12.29.1 255.255.255.0 dot1q vlan 29!interface Bundle-Ether28.2 description Connected to P2_CRS-8 Bundle-Ether 28.2 ipv4 address 10.12.30.1 255.255.255.0 dot1q vlan 30!interface Bundle-Ether28.3 description Connected to P2_CRS-8 Bundle-Ether 28.3 ipv4 address 10.12.31.1 255.255.255.0 dot1q vlan 31!interface Bundle-POS24 description Connected to P2_CRS-8 Bundle-POS 24 ipv4 address 10.12.24.1 255.255.255.0 bundle minimum-active links 1 bundle minimum-active bandwidth 2488320!interface Loopback0 ipv4 address 10.1.1.1 255.255.255.255!interface MgmtEth0/4/CPU0/0 description Connected to Lab LAN ipv4 address 172.29.52.46 255.255.255.0!interface MgmtEth0/4/CPU1/0 description Connected to Lab LAN ipv4 address 172.29.52.47 255.255.255.0!interface MgmtEth0/RP0/CPU0/0 description Connected to Lab LAN ipv4 address 172.29.52.70 255.255.255.0!interface MgmtEth0/RP1/CPU0/0 description Connected to Lab LAN



OL-17332-01

ipv4 address 172.29.52.71 255.255.255.0!interface GigabitEthernet0/1/5/0 description Connected to P2_CRS-8 GE 0/1/5/0 ipv4 address 10.12.16.1 255.255.255.0!interface GigabitEthernet0/1/5/1 description Connected to P4_C12810 GE 5/2 ipv4 address 10.14.8.1 255.255.255.0!interface GigabitEthernet0/1/5/2 description Connected to PE6_C12406 GE 0/4/0/1 ipv4 address 10.16.4.1 255.255.255.0!interface GigabitEthernet0/1/5/3 shutdown!interface GigabitEthernet0/1/5/4 shutdown!interface GigabitEthernet0/1/5/5 shutdown!interface GigabitEthernet0/1/5/6 description Connected to P2_CRS-8 GE 0/1/5/6 bundle id 28 mode active!interface GigabitEthernet0/1/5/7 description Connected to P2_CRS-8 GE 0/1/5/7 bundle id 28 mode active!interface GigabitEthernet0/6/5/0 shutdown!interface GigabitEthernet0/6/5/1 description Connected to P2_CRS-8 GE 0/6/5/1 ipv4 address 10.12.20.1 255.255.255.0!interface GigabitEthernet0/6/5/2 description Connected to PE6_C12406 GE 0/4/0/2 ipv4 address 10.16.8.1 255.255.255.0!interface GigabitEthernet0/6/5/3 shutdown!interface GigabitEthernet0/6/5/4 shutdown!interface GigabitEthernet0/6/5/5 shutdown!interface GigabitEthernet0/6/5/6 shutdown!interface GigabitEthernet0/6/5/7 description Connected to P2_CRS-8 GE 0/6/5/7 ipv4 address 10.12.40.1 255.255.255.0!interface POS0/1/0/0 shutdown!interface POS0/1/0/1 description Connected to P2_CRS-8 POS 0/1/0/1 ipv4 address 10.12.8.1 255.255.255.0



OL-17332-01

!interface POS0/1/0/2 shutdown!interface POS0/1/0/3 shutdown!interface POS0/1/4/0 description Connected to P2_CRS-8 POS 0/1/4/0 bundle id 24 mode active!interface POS0/1/4/1 description Connected to P2_CRS-8 POS 0/1/4/1 bundle id 24 mode active!interface POS0/1/4/2 description Connected to P2_CRS-8 POS 0/1/4/2 ipv4 address 10.12.32.1 255.255.255.0 encapsulation ppp ppp pap sent-username P1_CRS-8 password encrypted 01100F175804 ppp authentication chap pap ppp chap password encrypted 13061E010803!interface POS0/1/4/3 description Connected to P2_CRS-8 POS 0/1/4/3 ipv4 address 10.12.32.1 255.255.255.0 encapsulation ppp ppp pap sent-username P1_CRS-8 password encrypted 070C285F4D06 ppp authentication chap pap ppp chap password encrypted 1511021F0725!interface POS0/6/0/0 description Connected to P11_CRS-4 POS 0/2/1/0 ipv4 address 10.111.4.1 255.255.255.0!interface POS0/6/0/1 description Connected to P2_CRS-8 POS 0/6/0/1 ipv4 address 10.12.12.1 255.255.255.0!interface POS0/6/0/2 shutdown!interface POS0/6/0/3 description Connected to PE21_C12406 POS 0/2/0/3 ipv4 address 10.121.4.1 255.255.255.0!interface POS0/6/4/0 shutdown!interface POS0/6/4/1 shutdown!interface POS0/6/4/2 shutdown!interface POS0/6/4/3 shutdown!interface POS0/6/4/4 description Connected to P4_C12810 POS 0/3 ipv4 address 10.14.4.1 255.255.255.0!interface POS0/6/4/5 description Connected to P2_CRS-8 POS 0/6/4/5



OL-17332-01

ipv4 address 10.12.4.1 255.255.255.0!interface POS0/6/4/6 description Connected to P3_C12008 POS 5/2 ipv4 address 10.13.4.1 255.255.255.0!interface POS0/6/4/7 description Connected to PE7_C12406 POS 0/5/0/1 ipv4 address 10.71.4.1 255.255.255.0!interface Serial0/1/1/0 shutdown!interface Serial0/1/1/1 shutdown!interface Serial0/1/1/2 shutdown!interface Serial0/1/1/3 shutdown!controller SONET0/1/0/1 clock source internal!controller SONET0/1/4/0 clock source internal!controller SONET0/1/4/1 clock source internal!controller SONET0/1/4/2 clock source internal!controller SONET0/1/4/3 clock source internal!controller SONET0/6/0/0 clock source internal!controller SONET0/6/0/1 clock source internal!controller SONET0/6/0/3 clock source internal!controller SONET0/6/4/4 clock source internal!controller SONET0/6/4/5 clock source internal!controller SONET0/6/4/6 clock source internal!controller SONET0/6/4/7 clock source internal!interface SBC1 description Connected to DRP CPU0 in slot 4 ipv4 address 10.75.75.1 255.255.255.0 service-location preferred-active 0/4/CPU0!interface SBC2



OL-17332-01

description Connected to DRP CPU1 in slot 4 ipv4 address 10.50.50.1 255.255.255.0 service-location preferred-active 0/4/CPU1!router static address-family ipv4 unicast 0.0.0.0/0 172.29.52.1 112 !!router ospf 100 router-id 10.1.1.1 nsf cisco area 0 mpls traffic-eng interface Bundle-POS24 ! interface Loopback0 passive enable ! interface GigabitEthernet0/1/5/1 ! interface GigabitEthernet0/1/5/2 ! interface GigabitEthernet0/6/5/1 ! interface GigabitEthernet0/6/5/2 ! interface POS0/1/0/1 ! interface POS0/6/0/0 ! interface POS0/6/0/1 ! interface POS0/6/0/3 ! interface POS0/6/4/4 ! interface POS0/6/4/6 ! interface POS0/6/4/7 ! interface SBC1 passive enable ! interface SBC2 passive enable ! ! mpls traffic-eng router-id Loopback0!mpls oam!rsvp interface POS0/6/0/1 bandwidth ! interface POS0/6/0/3 bandwidth ! interface POS0/6/4/7 bandwidth ! interface GigabitEthernet0/1/5/2 bandwidth



OL-17332-01

! interface GigabitEthernet0/6/5/1 bandwidth ! interface GigabitEthernet0/6/5/2 bandwidth !!mpls traffic-eng interface POS0/6/0/1 ! interface POS0/6/0/3 ! interface POS0/6/4/7 ! interface GigabitEthernet0/1/5/2 ! interface GigabitEthernet0/6/5/1 ! interface GigabitEthernet0/6/5/2 !!mpls ldp router-id 10.1.1.1 log neighbor graceful-restart ! interface Bundle-POS24 ! interface GigabitEthernet0/1/5/1 ! interface GigabitEthernet0/1/5/2 ! interface GigabitEthernet0/6/5/1 ! interface GigabitEthernet0/6/5/2 ! interface POS0/1/0/1 ! interface POS0/6/0/0 ! interface POS0/6/0/1 ! interface POS0/6/0/3 ! interface POS0/6/4/4 ! interface POS0/6/4/6 ! interface POS0/6/4/7 !!ssh serverxml agent ttyxml agent corbahttp serversbc service-1 service-location preferred-active 0/4/CPU0!sbc service-2 service-location preferred-active 0/4/CPU1!end



OL-17332-01

---------------------- show process blocked location all ----------------------

node: node0_1_CPU0------------------------------------------------------------------ Jid Pid Tid Name State TimeInState Blocked-on 55 8202 1 ksh Reply 114:09:58:0143 8199 devc-ser8250 51 20503 2 attachd Reply 114:10:03:0745 20501 eth_server 51 20503 3 attachd Reply 114:10:03:0742 8204 mqueue 72 20504 6 qnet Reply 0:00:00:0000 20501 eth_server 72 20504 7 qnet Reply 0:00:00:0001 20501 eth_server 72 20504 8 qnet Reply 0:00:00:0000 20501 eth_server 72 20504 9 qnet Reply 0:00:00:0000 20501 eth_server 52 20508 1 ksh-aux Reply 114:09:58:0360 8199 devc-ser8250 50 20509 2 attach_server Reply 114:10:03:0515 8204 mqueue 223 24613 1 reddrv_listener Reply 0:00:02:0217 20501 eth_server 250 73826 8 spa_t3e3 Reply 0:00:09:0606 8204 mqueue

node: node0_4_CPU0------------------------------------------------------------------65546 8202 1 ksh Reply 114:09:31:0294 8200 devc-conaux 51 36892 2 attachd Reply 114:09:37:0454 36890 eth_server 51 36892 3 attachd Reply 114:09:37:0453 12300 mqueue 73 36893 6 qnet Reply 0:00:00:0000 36890 eth_server 73 36893 7 qnet Reply 0:00:00:0000 36890 eth_server 73 36893 8 qnet Reply 0:00:00:0000 36890 eth_server 73 36893 9 qnet Reply 0:00:00:0000 36890 eth_server 50 36897 2 attach_server Reply 114:09:37:0414 12300 mqueue 316 41005 3 reddrv Reply 0:00:00:0188 36890 eth_server 252 102536 2 lpts_fm Reply 114:05:35:0614 381043 node 0/RP0/Ca

node: node0_4_CPU1------------------------------------------------------------------65546 8202 1 ksh Reply 114:08:40:0256 8200 devc-conaux 51 36892 2 attachd Reply 114:08:46:0362 36890 eth_server 51 36892 3 attachd Reply 114:08:46:0361 12301 mqueue 73 36893 6 qnet Reply 0:00:00:0000 36890 eth_server 73 36893 7 qnet Reply 0:00:00:0000 36890 eth_server 73 36893 8 qnet Reply 0:00:00:0000 36890 eth_server 73 36893 9 qnet Reply 0:00:00:0000 36890 eth_server 50 36897 2 attach_server Reply 114:08:46:0323 12301 mqueue 316 41005 3 reddrv Reply 0:00:00:0141 36890 eth_server 252 110726 2 lpts_fm Reply 114:05:43:0881 381043 node 0/RP0/Ca

node: node0_6_CPU0------------------------------------------------------------------ 55 8202 1 ksh Reply 114:10:03:0567 8199 devc-ser8250 51 20503 2 attachd Reply 114:10:09:0157 20501 eth_server 51 20503 3 attachd Reply 114:10:09:0154 8204 mqueue 72 20504 6 qnet Reply 0:00:00:0000 20501 eth_server 72 20504 7 qnet Reply 0:00:00:0001 20501 eth_server 72 20504 8 qnet Reply 0:00:00:0001 20501 eth_server 72 20504 9 qnet Reply 0:00:00:0001 20501 eth_server 52 20508 1 ksh-aux Reply 114:10:03:0780 8199 devc-ser8250 50 20509 2 attach_server Reply 114:10:08:0931 8204 mqueue 223 24613 1 reddrv_listener Reply 0:00:01:0285 20501 eth_server

node: node0_RP0_CPU0------------------------------------------------------------------65546 8202 1 ksh Reply 114:15:21:0545 8200 devc-conaux 52 40989 2 attachd Reply 114:15:22:0710 36891 eth_server 52 40989 3 attachd Reply 114:15:22:0708 12301 mqueue 78 40991 6 qnet Reply 0:00:00:0026 36891 eth_server



OL-17332-01

78 40991 7 qnet Reply 0:00:00:0027 36891 eth_server 78 40991 8 qnet Reply 0:00:00:0026 36891 eth_server 78 40991 9 qnet Reply 0:00:00:0027 36891 eth_server 51 40997 2 attach_server Reply 114:15:22:0461 12301 mqueue 387 155730 1 tftp_server Reply 114:14:10:0402 12301 mqueue 211 192609 3 invmgr Reply 114:08:02:0826 41005 node 0/4/CPUv 211 192609 4 invmgr Reply 114:07:59:0038 41005 node 0/4/CPUv65643 925803 1 exec Reply 0:00:06:0968 1 kernel 271 397510 2 lpts_fm Reply 2:23:10:0893 381043 lpts_pa 264 405735 5 l2vpn_mgr Reply 114:03:49:0301 426229 lspv_server 285 426236 9 te_control Reply 114:03:34:0062 426229 lspv_server 282 426237 4 mpls_ldp Reply 114:03:33:0325 426229 lspv_server65796 966916 1 showtech_helper Reply 0:00:05:0243 1 kernel65801 971017 1 show_processes Reply 0:00:00:0000 1 kernel

node: node0_RP1_CPU0------------------------------------------------------------------65546 8202 1 ksh Reply 114:15:31:0330 8200 devc-conaux 52 40989 2 attachd Reply 114:15:31:0955 36891 eth_server 52 40989 3 attachd Reply 114:15:31:0953 12301 mqueue 78 40991 6 qnet Reply 0:00:00:0000 36891 eth_server 78 40991 7 qnet Reply 0:00:00:0000 36891 eth_server 78 40991 8 qnet Reply 0:00:00:0000 36891 eth_server 78 40991 9 qnet Reply 0:00:00:0000 36891 eth_server 51 40997 2 attach_server Reply 114:15:31:0765 12301 mqueue 349 135223 1 sc_reddrv Reply 0:00:00:0025 36891 eth_server 172 159809 5 envmon Reply 0:00:00:0001 40994 i2c_server 387 168018 1 tftp_server Reply 114:07:34:0867 12301 mqueue 271 233674 2 lpts_fm Reply 114:05:45:0442 381043 node 0/RP0/Ca

-------------------------- show context location all --------------------------

node: node0_1_CPU0------------------------------------------------------------------

node: node0_4_CPU0------------------------------------------------------------------

Crashed pid = 41000 (pkg/bin/dsc)Crashed tid = 5Crash time: Mon Oct 15, 2007: 04:54:16Core for process at harddisk:/dumper/dsc.node0_4_CPU0.ppc.Z

Stack Trace#0 0xfc1e6d90#1 0xfc1e6d88#2 0xfc1e53a0#3 0xfc1e826c#4 0xfc16b0c8#5 0xfc16a7e4#6 0xfc16a324#7 0xfc16e7a8#8 0xfc16ea08#9 0x48200e20 Registers info r0 r1 r2 r3 R0 00000000 4811bc50 48215204 00000000 r4 r5 r6 r7 R4 00000000 00000002 00000000 00000000 r8 r9 r10 r11 R8 00000000 ffffffff 00000000 00000000 r12 r13 r14 r15 R12 ee6b2800 48215170 00000000 00000000 r16 r17 r18 r19



OL-17332-01

R16 00000000 00000000 00000000 00000000 r20 r21 r22 r23 R20 fc250000 fc16b0c8 4811be6c fc250000 r24 r25 r26 r27 R24 00000000 fc24a184 00000005 fc22d628 r28 r29 r30 r31 R28 fc1e826c fc24a580 0000a028 00000019 cnt lr msr pc R32 fc1e72b4 fc1e6d88 0000d932 fc1e6d90 cnd xer R36 28000024 20000001

DLL Info DLL path Text addr. Text size Data addr. Data size Version/hfr-os-3.6.0.16I/lib/libinfra.dll 0xfc15a000 0x000397b0 0xfc194000 0x000000/hfr-os-3.6.0.16I/lib/libc.dll 0xfc1ce000 0x0007b6e0 0xfc24a000 0x00002000 0

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support cef


OL-17332-01

show tech-support cefTo automatically run show commands that display information specific to Cisco Express Forwarding (CEF) debugging, use the show tech-support cef command in EXEC mode.

show tech-support cef [vrf vrf-name [ipv4 | ipv6 | mpls] [detail | brief]] [file send-to] [compress] [location node-id] {terminal [page] | file send-to [background] [compressed | uncompressed]}

Syntax Description vrf (Optional) Specifies a VPN routing and forwarding (VRF) instance.

vrf-name (Optional) Name of a VRF.

ipv4 (Optional) Specifies IPv4 CEF information.

ipv6 (Optional) Specifies IPv6 CEF information.

mpls (Optional) Specifies Multiprotocol Label Switching CEF information.

detail (Optional) Specifies detailed CEF debugging information.

brief (Optional) Specifies brief CEF debugging information.

file (Optional) Specifies that the command output is saved to a specified file.

sent-to (Optional) Name of the file. The following valid options are listed:

• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename

compress (Optional) Specifies compression for the trace file.






OL-17332-01

Defaults IPv4 is the default. The command output is not compressed.

Command Modes EXEC

Command History



Use the show tech-support cef command to run show commands that display information specific to CEF debugging. This command is used to locate any issues related to the Forwarding Information Base (FIB) which is more commonly referred to as Cisco Express Forwarding (CEF). This command generates CEF debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


















OL-17332-01


The following show commands run automatically when you run the show tech-support cef command:

• show version

• show running

• show route {ipv4 | ipv6} unicast

• show proc blocked

• show cef {ipv4 | ipv6 | mpls} exceptions

• show cef {ipv4 | ipv6 | mpls} drop

• show ipv4 interface brief

• show cef {ipv4 | ipv6} summary

• show cef {ipv4 | ipv6 | mpls} interface

• show cef ipv4 non-recursive

• show cef {ipv4 | ipv6}

• show cef {ipv4 | ipv6 | mpls} adjacency

• show mpls forwarding (if the mpls keyword is specified)



Task ID

Examples The following example shows some of the show tech-support cef command output:

RP/0/RP0/CPU0:router# show tech-support cef terminal page

-------------------------------------------------------------------------------

show tech-support cef ipv4 brief

-------------------------------------------------------------------------------

-------------------------------- show version --------------------------------

Cisco IOS XR Software, Version 3.8.0Copyright (c) 2007 by Cisco Systems, Inc.

ROM: System Bootstrap, Version 1.43(20061109:045749) [CRS-1 ROMMON],

Task ID Operations


read

cef read




OL-17332-01

CRS-1 uptime is 1 week, 2 days, 20 hours, 29 minutesSystem image file is "disk0:hfr-os-mbi-3.5/mbihfr-rp.vm"

cisco CRS-1/S (7457) processor with 4194304K bytes of memory.7457 processor at 1197Mhz, Revision 1.2 16 GigabitEthernet/IEEE 802.3 interface(s)4 Ethernet/IEEE 802.3 interface(s)20 Packet over SONET/SDH network interface(s)20 SONET/SDH Port controller(s)2043k bytes of non-volatile configuration memory.38079M bytes of hard disk.1000592k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).1000640k bytes of ATA PCMCIA card at disk 1 (Sector size 512 bytes).

Configuration register on node 0/1/CPU0 is 0x102Boot device on node 0/1/CPU0 is mem:Package active on node 0/1/CPU0:hfr-sbc, V 3.8.0, Cisco Systems, at disk0:hfr-sbc-3.8.0 Built on Thu Mar 15 01:47:29 UTC 2007 By cisco.com in /file/3.8.0

hfr-pagent, V 3.8.0, Cisco Systems, at disk0:hfr-pagent-3.8.0 Built on Thu Mar 15 02:27:23 UTC 2007By cisco.com in /file/3.8.0

hfr-fpd, V 3.8.0, Cisco Systems, at disk0:hfr-fpd-3.8.0 Built on Thu Mar 15 01:32:22 UTC 2007By cisco.com in /file/3.8.0...hfr-os-mbi, V 3.8.0, Cisco Systems, at disk0:hfr-os-mbi-3.8.0 Built on Thu Mar 15 00:18:08 UTC 2007 By cisco.com in /file/3.8.0

-------------------------------- show running --------------------------------

!! Last configuration change at Fri Mar 23 18:03:27 2007 by user_a!hostname CRS-1line console exec-timeout 600 0 session-timeout 600!line default exec-timeout 600 0 session-timeout 600!logging console informationaltelnet vrf default ipv4 server max-servers no-limitdomain ipv4 host p1 172.16.52.72domain ipv4 host p2 172.16.52.77domain ipv4 host ce6 172.16.52.73domain ipv4 host ce7 172.16.52.78domain ipv4 host pe6 172.16.52.128domain ipv4 host pe7 172.16.52.182domain ipv4 host pe11 172.16.52.83domain lookup disablevty-pool default 0 25ipv4 virtual address 172.16.52.72 255.255.255.0interface Loopback0



OL-17332-01

ipv4 address 10.1.1.1 255.255.255.255!interface MgmtEth0/RP0/CPU0/0 description Connected to aaa LAN ipv4 address 172.16.52.70 255.255.255.0!interface MgmtEth0/RP1/CPU0/0 description Connected to aaa LAN ipv4 address 172.16.52.71 255.255.255.0!router static address-family ipv4 unicast 0.0.0.0/0 172.29.52.1 200 !!mpls ldp router-id 10.1.1.1 log neighbor graceful-restart ! interface GigabitEthernet0/1/5/1 ! interface GigabitEthernet0/1/5/2 ! interface POS0/1/0/1 !!ssh serverxml agent ttyxml agent corbahttp serversbc service-1 service-location preferred-active 0/4/CPU0!sbc service-2 service-location preferred-active 0/4/CPU1!end

--------------------------- show route ipv4 unicast ---------------------------

% No matching routes found

------------------------------ show proc blocked ------------------------------

Location: 0/1/CPU0 Jid Pid Tid Name State TimeInState Blocked-on 55 8202 1 ksh Reply 236:24:17:0421 8199 devc-ser8250 51 16407 2 attachd Reply 236:24:24:0686 16405 eth_server 51 16407 3 attachd Reply 236:24:24:0684 8204 mqueue 72 16408 6 qnet Reply 0:00:00:0001 16405 eth_server 72 16408 7 qnet Reply 0:00:00:0000 16405 eth_server



OL-17332-01

72 16408 8 qnet Reply 0:00:00:0001 16405 eth_server 72 16408 9 qnet Reply 0:00:00:0000 16405 eth_server 52 16412 1 ksh-aux Reply 236:24:19:0271 8199 devc-ser8250 50 16413 2 attach_server Reply 236:24:24:0493 8204 mqueue 218 20516 1 reddrv_listener Reply 0:00:04:0086 16405 eth_server

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support control-ethernet


OL-17332-01

show tech-support control-ethernet To automatically run show commands that display information specific to control Ethernet debugging, use the show tech-support control-ethernet command in Administration EXEC mode.

show tech-support control-ethernet [location node-id] {terminal [page] | file send-to [background] [compressed | uncompressed]}

Syntax Description









• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename






OL-17332-01


Command History



Use the show tech-support control-ethernet command to run show commands that display information specific to control Ethernet debugging. This command is used to display information specific to Ethernet interface issues. This command generates control Ethernet information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support control-ethernet command:

• show version

• show hfr

• show controller fabric connectivity all

• show controller switch 0 ports node-id

• show controller switch 1 ports node-id

• show controller switch 0 statistics node-id

• show controller switch 1 statistics node-id













OL-17332-01

• show controller switch udld node-id

• show controller switch stp node-id

• show controller switch inter-rack ports all node-id

• show controller switch inter-rack statistics brief all node-id

• show controller switch inter-rack statistics detail all node-id

• show controller switch inter-rack udld all node-id

• show controller switch inter-rack stp all node-id

• show controller backplane ethernet detail node-id

• show controller backplane ethernet trace node-id



The show tech-support control-ethernet command also generates log files which are not listed. See the command output for log file information.

Task ID

Examples The following example shows some of the show tech-support control-ethernet command output:

RP/0/RP0/CPU0:router(admin)# show tech-support control-ethernet terminal page

Number of nodes 13

Gathering required commands for show tech control-ethernet

Finding available nodes in the system

Node - 0/1/CPU0

Node - 0/1/SP

Node - 0/4/CPU0

Node - 0/4/CPU1

Node - 0/4/SP

Node - 0/6/CPU0

Node - 0/6/SP

Node - 0/RP0/CPU0

Node - 0/RP1/CPU0

Node - 0/SM0/SP

Node - 0/SM1/SP

Node - 0/SM2/SP

Task ID Operations

admin read




OL-17332-01

Node - 0/SM3/SP

-------------------------------------------------------------------------------

show tech-support control-ethernet

-------------------------------------------------------------------------------

------------------- show version ---------------------------------

Cisco IOS XR Software, Version 3.8.0.20I[DT_IMAGE]Copyright (c) 2008 by Cisco Systems, Inc.


P2_CRS-8 uptime is 1 day, 18 hours, 10 minutesSystem image file is "bootflash:disk0/hfr-os-mbi-3.8.0.20I/mbihfr-rp.vm"

cisco CRS-8/S (7457) processor with 4194304K bytes of memory.7457 processor at 1197Mhz, Revision 1.2

4 Management Ethernet16 GigabitEthernet20 SONET/SDH20 Packet over SONET/SDH1019k bytes of non-volatile configuration memory.1000592k bytes of disk0: (Sector size 512 bytes).1000640k bytes of disk1: (Sector size 512 bytes).

Boot device on node 0/1/SP is bootflash:Package active on node 0/1/SP:hfr-pagent, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-pagent-3.8.0.20IBuilt on Wed Oct 29 17:24:33 DST 2008By iox13.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0

hfr-fpd, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-fpd-3.8.0.20IBuilt on Wed Oct 29 17:02:19 DST 2008By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0

hfr-diags, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-diags-3.8.0.20IBuilt on Wed Oct 29 17:02:01 DST 2008By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0

hfr-admin, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-admin-3.8.0.20IBuilt on Wed Oct 29 16:08:13 DST 2008By iox30.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0

hfr-base, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-base-3.8.0.20IBuilt on Wed Oct 29 16:07:35 DST 2008By iox30.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0

hfr-os-mbi, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-os-mbi-3.8.0.20IBuilt on Wed Oct 29 15:45:48 DST 2008By iox30.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0

Configuration register on node 0/1/CPU0 is 0x102Boot device on node 0/1/CPU0 is mem:Package active on node 0/1/CPU0:hfr-services, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-services-3.8.0IBuilt on Wed Oct 29 17:03:08 DST 2008By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0



OL-17332-01

hfr-pagent, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-pagent-3.8.0.20IBuilt on Wed Oct 29 17:24:33 DST 2008By iox13.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0



hfr-mcast, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-mcast-3.8.0.20IBuilt on Wed Oct 29 18:18:37 DST 2008By iox22.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0

hfr-mpls, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-mpls-3.8.0.20IBuilt on Wed Oct 29 18:18:25 DST 2008By iox22.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0

hfr-lc, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-lc-3.8.0.20IBuilt on Wed Oct 29 16:18:36 DST 2008By iox30.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0

hfr-fwdg, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-fwdg-3.8.0.20IBuilt on Wed Oct 29 16:13:27 DST 2008By iox30.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0

--More--

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support dsc


OL-17332-01

show tech-support dscTo automatically run show commands that display information specific to designated shelf controller (DSC) debugging, use the show tech-support dsc command in Administration EXEC mode.

show tech-support dsc [location node-id] {terminal [page] | file send-to [background] [compressed | uncompressed]}

Syntax Description








sent-to Name of the file. The following are valid options:

• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename






OL-17332-01


Command History



Use the show tech-support dsc command to run show commands that display information specific to DSC debugging. This command generates DSC information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support dsc command:

• show dsc all



Task ID

Examples The following example shows some of the show tech-support dsc command output:

RP/0/RP0/CPU0:router(admin)# show tech-support dsc terminal page

-------------------------------------------------------------------------------







Task ID Operations

admin read




OL-17332-01

show tech-support dsc for node node0_RP0_CPU0 from node node0_RP0_CPU0

-------------------------------------------------------------------------------

-------------------------------------------------------------------------------

Displaying DSC information

-------------------------------------------------------------------------------

----------------- Displaying DSC attach_process on this node ------------------

-------------------- run attach_process -p 110638 -i 1 -S ---------------------

Attaching to process pid = 110638 (pkg/bin/dsc)No tid specified, following all threads

Iteration 1 of 1------------------------------

Current process = "pkg/bin/dsc", PID = 110638 TID = 1

trace_back: #0 0xfc177518 [MsgReceivev]trace_back: #1 0xfc161354 [msg_receivev]trace_back: #2 0xfc161160 [msg_receive]trace_back: #3 0xfc16479c [event_dispatch]trace_back: #4 0xfc164958 [event_block]trace_back: #5 0x482005e8 [<N/A>]trace_back: #6 0x482012cc [<N/A>]

ENDOFSTACKTRACE


trace_back: #0 0xfc177518 [MsgReceivev]trace_back: #1 0xfc161354 [msg_receivev]trace_back: #2 0xfc161160 [msg_receive]trace_back: #3 0xfc16479c [event_dispatch]trace_back: #4 0xfc164958 [event_block]trace_back: #5 0xfc6368d4 [chk_evm_thread]

ENDOFSTACKTRACE


trace_back: #0 0xfc177518 [MsgReceivev]trace_back: #1 0xfc161354 [msg_receivev]trace_back: #2 0xfc161160 [msg_receive]trace_back: #3 0xfc16479c [event_dispatch]trace_back: #4 0xfc164958 [event_block]trace_back: #5 0x48200f34 [<N/A>]

ENDOFSTACKTRACE




OL-17332-01

trace_back: #0 0xfc177518 [MsgReceivev]trace_back: #1 0xfc161354 [msg_receivev]trace_back: #2 0xfc161160 [msg_receive]trace_back: #3 0xfc16479c [event_dispatch]trace_back: #4 0xfc164958 [event_block]trace_back: #5 0x48200ddc [<N/A>]

ENDOFSTACKTRACE


trace_back: #0 0xfc177518 [MsgReceivev]trace_back: #1 0xfc161354 [msg_receivev]trace_back: #2 0xfc161160 [msg_receive]trace_back: #3 0xfc16479c [event_dispatch]trace_back: #4 0xfc164958 [event_block]trace_back: #5 0x48200528 [<N/A>]

ENDOFSTACKTRACE

--------------------------- Displaying show dsc all ---------------------------

---------------------------- run dsc_show_table -a ----------------------------

NODE ROLE PRIORITY TBEACON PRESENT MIGRATION =====================================================================0/RP0/CPU0 DSC DEFAULT 300 YES ENABLED ---------------------------------------------------------------------0/RP1/CPU0 BACKUP DEFAULT 300 YES ENABLED ---------------------------------------------------------------------0/4/CPU0 NON-DSC 65 300 YES ENABLED ---------------------------------------------------------------------0/4/CPU1 NON-DSC 66 300 YES ENABLED ---------------------------------------------------------------------

-------------------------- Displaying Rack SerialIDs --------------------------

---------------------------- run dsc_show_table -s ----------------------------

NODE SERIAL ID ===================================0/RP0/CPU0 TBA09370035 -----------------------------------0/RP1/CPU0 TBA09370035 -----------------------------------0/4/CPU0 TBA09370035 -----------------------------------0/4/CPU1 TBA09370035 -----------------------------------

--------------------- Displaying DSC process on all nodes ---------------------

--------------------- run sysmgr_show -o -A -p dsc -n 513 --------------------- Job Id: 155 PID: 110638 Executable path: /disk0/hfr-admin-3.8.0/bin/dsc



OL-17332-01

Instance #: 1 Version ID: 00.00.0000 Respawn: ON Respawn count: 1 Max. spawns per minute: 12 Last started: Fri Mar 16 14:56:35 2007 Process state: Run Package state: Normal core: COPY Max. core: 0 Level: 40 Mandatory: ON MaintModeProc: ON startup_path: /pkg/startup/dsc.startup Ready: 4.382s Process cpu time: 891.318 user, 1328.561 kernel, 2219.879 totalJID TID Stack pri state TimeInState HR:MM:SS:MSEC NAME155 1 52K 10 Receive 0:00:52:0856 0:00:00:0176 dsc155 2 52K 10 Receive 326:49:44:0414 0:00:00:0001 dsc155 4 52K 10 Receive 0:00:00:0083 0:00:01:0127 dsc155 5 52K 10 Receive 0:00:00:0643 0:00:00:0019 dsc155 6 52K 55 Receive 0:00:00:0060 0:14:49:0966 dsc...

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support fabric


OL-17332-01

show tech-support fabric To automatically run show commands that display information specific to fabric debugging, use the show tech-support dsc command in Administration EXEC mode.

show tech-support fabric {fabric-snapshot | multicast [brief | detail] | summary | traffic [brief | detail]} [location node-id [include-fabric-cards] [include-rp]] [email | page | file send-to]

Syntax Description fabric-snapshot Runs the fabric snapshot script which generates comprehensive data on the instantaneous state of the fabric.

multicast Specifies fabric multicast information.

brief (Optional) Displays brief information.

detail (Optional) Displays detailed information.

summary Specifies fabric summary information.

traffic Specifies fabric traffic information.



include-fabric-cards (Optional) Specifies fabric card information in addition to the fabric information. This option is available when the fabric-snapshot keyword is used.

include-rp (Optional) Specifies route processor information in addition to the fabric information. This option is available when the fabric-snapshot keyword is used.

email (Optional) Specifies that the command output is sent through email. The output is copied to /disk0:/fabric_multicast.log.

Note To use the email keyword, you must have the SMTP server and domain name and the ability to connect a TCP socket to the specified SMTP server. The domain ipv4 host host-name v4address1 command must be configured to use the server lookup.





OL-17332-01



Command History




• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename










OL-17332-01


Use the show tech-support fabric command to run show commands that display information specific to fabric debugging. This command generates fabric information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support fabric multicast command:

• show controllers fabric fgid stat all detail

• show controllers fabric fgid info

• show process fgid_allocator

• show process fgid_aggregator

• show process fgid_server

• show process fgid_allocator

The following show commands run automatically when you run the show tech-support fabric traffic command:

• show controllers fabric plane all detail

• show controllers fabric plane all stat brief

• show controllers fabric plane all stat detail

• show controllers fabric link port

• show controller fabricq stat

• show controllers fabricq queues

• show controllers fabricq eio links all

• show controller ingressq stat

• show controller ingressq queue all

• show controller ingressq fabric pla

• show control ingressq block ssm bpmem 0

• show controllers ingressq block fqm queue

• show controllers ingressq vports all

• show controllers ingressq interfaces all

• show controllers ingressq eio links all

• show controller fia rxslice all uq all channel all

• show controllers cpuctrl devices ingressq pdma queue all act

• show controllers cpuctrl devices egressq pdma queue all act



OL-17332-01

• show controllers cpuctrl devices fabricq pdma queue all act



Task ID

Examples The following example shows some of the show tech-support fabric multicast command output:

RP/0/RP0/CPU0:router(admin)# show tech-support fabric multicast page

show tech-support fabric script - (/pkg/bin/fabric_showtech.tcl)Error matching ALL in node_id_mappingshow tech fabric multicastMSC: 0/1/CPU0 is runningDRP: 0/4/CPU0 is runningMSC: 0/6/CPU0 is runningRP: 0/RP0/CPU0 is runningRP: 0/RP1/CPU0 is runningSM: type: 0, 0/SM0/SP is runningSM: type: 0, 0/SM1/SP is runningSM: type: 0, 0/SM2/SP is runningSM: type: 0, 0/SM3/SP is running

This is a single chassis router.

There are 2 RPs to be checked

There are 1 DRP to be checked

There are 4 SM cards to be checked

There are 2 MSC cards to be checked

Location: all, collection option: 1

Running general FGID related commands and gathering dataPlease wait...

Nodeid 0x : hfr_fgid_show_items s all all detail Nodeid 0x : hfr_fgid_show_items i 1024 2 diag no_diag Nodeid 0x : hfr_fgid_show_items i 1524 2 diag no_diag

====================================================INFO: Show All RP/SC/DRP FGID related information====================================================

-----Show FGID information on location 0/1/CPU0-----show contr ingressq fabric pla-----Show FGID information on location 0/4/CPU0-----Nodeid 0x65 : sysmgr_show -o -A -p fgid_aggregator -n 65show contr fabric trace fgid-client loc 0/4/CPU0show contr fabric trace fgid-aggr info loc 0/4/CPU0

Task ID Operations

admin read




OL-17332-01

show contr fabric trace fgid-aggr err loc 0/4/CPU0show contr fabric trace fgid-aggr dev loc 0/4/CPU0-----Show FGID information on location 0/6/CPU0-----show contr ingressq fabric pla-----Show FGID information on location 0/RP0/CPU0-----Nodeid 0x513 : sysmgr_show -o -A -p fgid_allocator -n 513Nodeid 0x513 : sysmgr_show -o -A -p fgid_aggregator -n 513Nodeid 0x513 : sysmgr_show -o -A -p fgid_server -n 513show contr fabric trace fgid-client loc 0/RP0/CPU0show contr fabric trace fgid-alloc info loc 0/RP0/CPU0show contr fabric trace fgid-alloc err loc 0/RP0/CPU0show contr fabric trace fgid-alloc dev loc 0/RP0/CPU0show contr fabric trace fgid-svr info loc 0/RP0/CPU0show contr fabric trace fgid-svr err loc 0/RP0/CPU0show contr fabric trace fgid-svr dev loc 0/RP0/CPU0show contr fabric trace fgid-agg info loc 0/RP0/CPU0show contr fabric trace fgid-agg err loc 0/RP0/CPU0show contr fabric trace fgid-agg dev loc 0/RP0/CPU0-----Show FGID information on location 0/RP1/CPU0-----Nodeid 0x529 : sysmgr_show -o -A -p fgid_allocator -n 529Nodeid 0x529 : sysmgr_show -o -A -p fgid_aggregator -n 529Nodeid 0x529 : sysmgr_show -o -A -p fgid_server -n 529show contr fabric trace fgid-client loc 0/RP1/CPU0show contr fabric trace fgid-alloc info loc 0/RP1/CPU0show contr fabric trace fgid-alloc err loc 0/RP1/CPU0show contr fabric trace fgid-alloc dev loc 0/RP1/CPU0show contr fabric trace fgid-svr info loc 0/RP1/CPU0show contr fabric trace fgid-svr err loc 0/RP1/CPU0show contr fabric trace fgid-svr dev loc 0/RP1/CPU0show contr fabric trace fgid-agg info loc 0/RP1/CPU0show contr fabric trace fgid-agg err loc 0/RP1/CPU0show contr fabric trace fgid-agg dev loc 0/RP1/CPU0

====================================================INFO: Show All SM FGID related information====================================================

-----Show FGID information on location 0/SM0/SP-----show contr fabric trace fgid-cons dev loc 0/SM0/SPshow contr fabric trace fgid-cons err loc 0/SM0/SP-----Show FGID information on location 0/SM1/SP-----show contr fabric trace fgid-cons dev loc 0/SM1/SPshow contr fabric trace fgid-cons err loc 0/SM1/SP-----Show FGID information on location 0/SM2/SP-----show contr fabric trace fgid-cons dev loc 0/SM2/SPshow contr fabric trace fgid-cons err loc 0/SM2/SP-----Show FGID information on location 0/SM3/SP-----show contr fabric trace fgid-cons dev loc 0/SM3/SPshow contr fabric trace fgid-cons err loc 0/SM3/SP

Copying the information from /tmp/fabric_showtech.log to stdout

-----HFR Card/Module Status-----Node Type PLIM State Config State-----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/1/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON0/1/4 MSC(SPA) 4XOC48-POS OK PWR,NSHUT,MON0/1/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON0/4/SP DRP(SP) N/A IOS XR RUN PWR,NSHUT,MON0/4/CPU0 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON0/4/CPU1 DRP DRP-ACC IOS XR RUN PWR,NSHUT,MON0/6/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON



OL-17332-01

0/6/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/6/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON0/6/4 MSC(SPA) 8XOC3/OC12-POS OK PWR,NSHUT,MON0/6/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON

MSC: 0/1/CPU0 is runningDRP: 0/4/CPU0 is runningMSC: 0/6/CPU0 is runningRP: 0/RP0/CPU0 is runningRP: 0/RP1/CPU0 is runningSM: 0/SM0/SP is runningSM: 0/SM1/SP is runningSM: 0/SM2/SP is runningSM: 0/SM3/SP is running--------- SNAPSHOT show controllers fabric fgid stat all detail ----------

Fabric FGID Resource Statistics Information:

System wide Fabric multicast resource statistics:

Total number of FGIDs in the system is 1000000 Current number of InUse FGIDs in the system is 1012 High Water Mark of InUse FGIDs in the system is 1512...

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support gsp


OL-17332-01

show tech-support gsp To automatically run show commands that display information specific to Gigabit Switch Platform (GSP) debugging, use the show tech-support gsp command in EXEC mode.

show tech-support gsp [location node-id] {terminal [page] | file send-to [background] [compressed | uncompressed]}

Syntax Description









• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename






OL-17332-01

Command Modes EXEC

Command History



Use the show tech-support gsp command to run show commands that display information specific to GSP debugging. GSP is a common IPC utilized in Cisco IOS XR software to communicate between nodes. This command would be used to determine if there are any issues with GSP communication between nodes. This command generates GSP debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support gsp command:

• show gsp group addresses

• show gsp group admin addresses

• show gsp group lr-control addresses

• show gsp group gid 0



• show gsp memory













OL-17332-01

• show gsp stats client

• show gsp stats server jid 0

• show gsp trace server bootstrap location all

• show gsp trace server timeout slow location all

• show gsp trace server timeout fast location all

• show gsp trace server limp fast location all

• show gsp trace server limp slow location all

• show gsp trace server error api location all

• show gsp trace server error minor location all

• show gsp trace server ens location all



Task ID

Examples The following example shows some of the show tech-support gsp command output:

RP/0/RP0/CPU0:router# show tech-support gsp terminal page

-------------------------------------------------------------------------------

show tech-support gsp

-------------------------------------------------------------------------------

-------------------------- show gsp group addresses ---------------------------

List of groups in LR Plane Grp_ID Grp_Name Grp Address****** ******** *********** 2000 gsp 00 00. 04 00. 00 00 2001 ens_group 00 00. 04 02. 00 00 2002 _async_group 00 00. 04 04. 00 00 2003 gang_sched_group 00 00. 04 06. 00 00 2004 RDS_CGRP_NRS_CLASS_RDS_LR_1 00 00. 04 08. 00 00 2005 RDS_WTR_LWG_GRP_NRS_CLASS_RDS_L 00 00. 04 0a. 00 00...--------------------- show gsp group lr-control addresses ---------------------

List of groups in Lctrl Plane Grp_ID Grp_Name Grp Address****** ******** *********** 1000 gsp_lctrl 01 00. 00 00. 00 64

Task ID Operations


read

sysmgr read




OL-17332-01

1001 ens_lctrl_group 01 00. 00 00. 00 66 1002 _async_lctrl_group 01 00. 00 00. 00 68 1003 gang_sched_lctrl_group 01 00. 00 00. 00 6a 1004 lrd_lctrl_grp 01 00. 00 00. 00 6c 1005 sysdb_medusae 01 00. 00 00. 00 6e 1006 QSM_LR_GRP 01 00. 00 00. 00 70 1007 sysdb_medusae_s_lr_shared 01 00. 00 00. 00 72 1008 PuF group: persisted placement 01 00. 00 00. 00 74

---------------------------- show gsp group gid 0 ----------------------------- ------------ group ----------- name : gsp_admin gid : 0 parent gid : 65535 attrs :[0x9 0x4] STATIC, CLOSED, PRIVATE ADMIN PLANE

addr : 01 00. 00 00. 27 74 addr flags : 3 addr media : 4 grp_snv nodecnt : d grp_snv sns_cnt : 1 grp snv[0] : 0x1fff writer_snv nodecnt: 0 writer_snv sns_cnt: 0 writer snv is NULL grp_stub_state : 0 last-leaving client: 0 gsp_seq_state : 0 gsp_seq_retrycnt : 0

Basic Info************** gsp node id : 0 writer FALSE in service : 1 adding_to_grp : 0 node state : 0 local mbr cnt : 0 local writer cnt : 0 seq state : 0x1 seq state election: 0x0 ack_snv nodecnt : 13 ack_snv sns_cnt : 1 ack snv[0] : 0x1fff

Seqnums********* def ord next seq : 0x0 ctrl next seq : 0xac oob seq : 0xa

Def Ord Windowing Parameters ******************************** def ord win quota : 0 def ord win cnt : 0 def ord win owner : 0xffff def ord owner idx : 0xffff



OL-17332-01

def min msg id : 0x0 def ord win state : 0x0

Tx queue info ***************** blocked for win : 0 tinfo elems priv : 0 resv elems priv : 0 tinfo elems ctrl : 0 tinfo elems no resv: 0

retrans timer : 0 refcount : 1

Other info ***************** recv window size : 0x5000 downed node : 0x40 downed node : 0x42 downed node : 0x41

Gsp seq_info************** seq info flags : 0x9 seq addr : 1 0. 0 0. 27 75. 0 0 seq addr flags : 3 seq addr media : 4 seq_snv nodecnt : 4 seq_snv sns cnt : 1 seq snv[0] : 0x701

Number of sync variables: 0************************

Nodevec Entries ************** ------------- node idx 0 ------------------- node RSI id :0x201 node str :0/RP0/CPU0 node state :0 node nacked :0 node next seqnum :0 node next ctrl seq:78 node mbr cnt :0 node uc tx seqnum :0 node uc rx seqnum :0 node uc ctrl flag :0 node addr :0x0 node ucast quota :0 node ucast cnt :0 ucast min msg_id :0x0 ------------- node idx 1 ------------------- node RSI id :0x810 node str :0/SM1/SP node state :0 node nacked :0 node next seqnum :0 node next ctrl seq:f node mbr cnt :0 node uc tx seqnum :0

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support install


OL-17332-01

show tech-support installTo automatically run show commands that display information specific to installation information, use the show tech-support install command in the EXEC and administration EXEC modes.

show tech-support install [page | file send-to] [location node-id]

Syntax Description

Defaults Output is logged to the terminal screen.

Command Modes EXEC

Administration EXEC




• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename





OL-17332-01

Command History



Use the show tech-support install command to run show commands that display information specific to installation information. This command is useful for any problems encountered while executing install operations on the system during an install activate, install add, remove, or commit operation.This command generates installation information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support install command:

• show install request

• show version

• show install active summary

• show install committed summary

• show install package all detail

• show install log verbose

• show running-config sanitize

• show redundancy

• show logging

• show platform













OL-17332-01

• show install active detail

• show install committed detail

• show install inactive detail

• show pkgfs trace location all

• show install trace loadpath location node-id

• show install trace io location node-id

• show install trace instdir-lr location node-id

• show install trace insthelper location node-id

• show install trace notify location node-id

• show install trace replicator location node-id

• show install trace pkg location node-id

• show install trace inv location node-id

• show install trace platform location node-id

• show install trace ior location node-id

• show install trace state-file-replication location node-id

• show install trace sds location node-id

• show memory summary location node-id

• show context location node-id

• show processes memory location node-id

• show processes aborts location node-id

• show processes blocked location node-id

• show pkgfs trace location node-id

• show filesystem location node-id

• run diskinfo (various)



Task ID

Examples The following example shows some of the show tech-support install command output:

RP/0/RP0/CPU0:router# show tech-support install page

-------------------------------------------------------------------------------

SDR show install tech-support

Task ID Operations


read

pkg-mgmt read




OL-17332-01

-------------------------------------------------------------------------------

---------------------------- show install request -----------------------------There are no install requests in operation.

-------------------------------- show version ---------------------------------

Cisco IOS XR Software, Version 3.8.0 Copyright (c) 2007 by Cisco Systems, Inc.


CRS-1 uptime is 1 week, 3 days, 16 hours, 46 minutesSystem image file is "disk0:hfr-os-mbi-3.8.0/mbihfr-rp.vm"

cisco CRS-1 (7457) processor with 4194304K bytes of memory.7457 processor at 1197Mhz, Revision 1.2

16 GigabitEthernet/IEEE 802.3 interface(s)4 Ethernet/IEEE 802.3 interface(s)20 Packet over SONET/SDH network interface(s)20 SONET/SDH Port controller(s)2043k bytes of non-volatile configuration memory.38079M bytes of hard disk.1000592k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).1000640k bytes of ATA PCMCIA card at disk 1 (Sector size 512 bytes).

Configuration register on node 0/1/CPU0 is 0x102Boot device on node 0/1/CPU0 is mem:Package active on node 0/1/CPU0:hfr-sbc, V 3.8.0, Cisco Systems, at disk0:hfr-sbc-3.8.0 Built on Thu Mar 15 01:47:29 UTC 2007 By cisco.com in /auto/3.8.0

hfr-pagent, V 3.8.0, Cisco Systems, at disk0:hfr-pagent-3.8.0 Built on Thu Mar 15 02:27:23 UTC 2007 By cisco.com in /auto/3.8.0...hfr-os-mbi, V 3.8.0., Cisco Systems, at disk0:hfr-os-mbi-3.8.0 Built on Thu Mar 15 00:18:08 UTC 2007 By cisco.com in /auto/3.8.0

------------------------- show install active summary ------------------------- Active Packages: disk0:hfr-sbc-3.8.0 disk0:hfr-pagent-3.8.0 disk0:hfr-fpd-3.8.0 disk0:hfr-doc-3.8.0 disk0:hfr-diags-3.8.0 disk0:hfr-mgbl-3.8.0 disk0:hfr-mcast-3.8.0 disk0:hfr-mpls-3.8.0 disk0:hfr-k9sec-3.8.0 disk0:comp-hfr-mini-3.8.0

----------------------- show install committed summary ------------------------



OL-17332-01

Committed Packages: disk0:hfr-sbc-3.8.0 disk0:hfr-pagent-3.8.0 disk0:hfr-fpd-3.8.0 disk0:hfr-doc-3.8.0 disk0:hfr-diags-3.8.0 disk0:hfr-mgbl-3.8.0 disk0:hfr-mcast-3.8.0 disk0:hfr-mpls-3.8.0 disk0:hfr-k9sec-3.8.0 disk0:comp-hfr-mini-3.8.0

----------------------- show install package all detail -----------------------disk0:comp-hfr-mini-3.8.0 disk0:hfr-admin-3.8.0 hfr-admin V3.8.0 Admin Package Vendor : Cisco Systems Desc : Admin Package Build : Built on Thu Mar 15 00:40:36 UTC 2007 Source : By cisco.com in /auto/3.8.0 Card(s): RP, DRP, DRPSC, OC3-POS-4, OC12-POS, GE-3, OC12-POS-4, OC48-POS, E3-OC48-POS, E3-OC12-POS-4, E3-OC3-POS-16, E3-OC3-POS-8, E3-OC3-POS-4, E3-OC48-CH, E3-OC12-CH-4, E3-OC3-CH-16, E3-GE-4, E3-OC3-ATM-4, E3-OC12-ATM-4, E5-CEC, E5-CEC-v2, SE-SEC, LC, SP, SC Restart information: Default: parallel impacted processes restart Components in package disk0:hfr-admin-3.8.0, package hfr-admin: envmon V[ci-35/2] HFR envmon CLI eio-lib V[main/54] Elastic Input Output Link Macro ^Mtraining library. hfr-aib V[ci-35/5] AIB for HFR hfr-dsc V[ci-35/7] HFR Designated Shelf Controller hfr-pfi V[main/24] hfr PFI platform APIs gaspp-lib V[ci-35/4] Generic ASIC Peek & Poke and Memory dump for all HFR ASICS hfr-netio V[main/14] hfr NetIO platform APIs hfr-squid V[ci-35/9] Squid FPGA Driver for HFR LC and RP sc-reddrv V[ci-35/2] SC Redundancy Driver drp-reddrv V[ci-35/4] DRP redundancy driver hfr-invmgr V[ci-35/17] Inventory Manager on HFR fabric-fgid V[ci-35/17] Fabric Multicast management component fabric-fsdb V[ci-35/12] Fabric State management component hfr-fabricq V[ci-35/13] Fabric Queue Manager. Driver for the fabric queueing ASIC....

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support mpls rsvp


OL-17332-01

show tech-support mpls rsvpTo automatically run show commands that display information specific to Multiprotocol Label Switching (MPLS) Resource Reservation Protocol (RSVP) debugging, use the show tech-support mpls rsvp command in EXEC mode.

show tech-support mpls rsvp {terminal [page] | file send-to [background] [compressed | uncompressed]}

Syntax Description


Command Modes EXEC






• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename






OL-17332-01

Command History



Use the show tech-support mpls command to run show commands that display information specific to MPLS RSVP debugging. This command generates RSVP debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support mpls rsvp command:

• show rsvp interface detail

• show rsvp counters pak

• show rsvp counters handles

• show rsvp counters database private

• show rsvp counters messages private

• show rsvp counters memory

• show rsvp counters events

• show rsvp counters notifications-client

• show rsvp counters request

• show rsvp counters destroy-reasons

• show rsvp counters policy

• show rsvp graceful-restart











OL-17332-01

• show rsvp fast-reroute summary

• show rsvp graceful-restart neighbors detail

• show rsvp hello instance detail

• show rsvp sender detail

• show rsvp reservation detail

• show rsvp request detail

• show rsvp session detail

• show rsvp authentication

• show rsvp sender private

• show rsvp reservation private

• show rsvp request private

• show rsvp interface private

• show rsvp installed private

• show rsvp trace events

• show rsvp trace default

• show rsvp trace buffer

• show rsvp trace interface

• show rsvp trace errors

• show rsvp trace client

• show rsvp debug-error



Task ID

Examples The following example shows some of the show tech-support mpls rsvp command output:

RP/0/RP0/CPU0:router# show tech-support mpls rsvp terminal page

-------------------------------------------------------------------------------

show tech-support mpls rsvp (Detail with Event traces)

-------------------------------------------------------------------------------

------------------------- show rsvp interface detail --------------------------INTERFACE: POS0/1/0/0 (ifh=0x1180060). VRF ID: 0x0 (Default). BW (bits/sec): Max=1230M. MaxFlow=1230M.

Task ID Operations

cisco-support read

mpls-te or ouni read




OL-17332-01

Allocated=0 (0%). MaxSub=0. Signalling: No DSCP marking. No rate limiting. States in: 0. Max missed msgs: 4. Expiry timer: Not running. Refresh interval: 45s. Normal Refresh timer: Not running. Summary refresh timer: Not running. Refresh reduction local: Enabled. Summary Refresh: Enabled (4096 bytes max).

Reliable summary refresh: Disabled. Bundling: Enabled. (4096 bytes max). Ack hold: 400 ms, Ack max size: 4096 bytes. Retransmit: 900ms.

--------------------------- show rsvp counters pak ----------------------------Number of pak TX=0Number of pak events received from raw=1Number of spurious events received from raw=1Number of packets received from raw=0Number of errored drops=0Authentication queue: Number of enqueues=0 Number of drops due to max q size=0 High water mark=0 Current queue size=0High priority queue: Number of enqueues=0 Number of drops due to max q size=0 High water mark=0 Current queue size=0Low priority queue: Number of enqueues=0 Number of drops due to max q size=0 High water mark=0 Current queue size=0

------------------------- show rsvp counters handles --------------------------

All allocated handles: 5 Unallocated cached handles: 1019 ------- LXSB handles: 1 ISB handles: 2 KI handles: 1 ------- Total handles ever allocated: 5 Total handles ever freed: 0

--------------------- show rsvp counters database private ---------------------

Sessions: 0 Locally created and incoming Paths: 0 Outgoing Paths: 0Locally created and incoming Reservations: 0 Outgoing Reservations: 0 Interfaces: 2 Installed: 0 New LSP count: 0 Refreshed LSP count: 0 LSP count recovered from checkpoint: 0 Proxy Senders: 0 Proxy Reservations: 0 Proxy Listeners: 1 TMB allocation: 0 Local Routes: 22



OL-17332-01

--------------------- show rsvp counters messages private --------------------- Routed Recv Xmit Recv Xmit Path 0 Resv 0 PathError 0 ResvError 0 PathTear 0 ResvTear 0 ResvConfirm 0 Hello 0 Ack 0 SRefresh 0 Challenge 0 ChallengeRsp 0 Retransmit 0 Rate Limited 0 OutOfOrder Bundle 0 AckSubmsg 0 PathSubmsg 0 ResvSubmsg 0 PathTearSubmsg 0 ResvTearSubmsg 0 PathErrorSubmsg 0 ResvErrorSubmsg 0 PathQuery 0

POS0/1/0/0 Recv Xmit Recv Xmit Path 0 0 Resv 0 0 PathError 0 0 ResvError 0 0 PathTear 0 0 ResvTear 0 0 ResvConfirm 0 0 Hello 0 0 Ack 0 0 SRefresh 0 0 Challenge 0 0 ChallengeRsp 0 0 Retransmit 0 Rate Limited 0 OutOfOrder 0 Bundle 0 0 AckSubmsg 0 0 PathSubmsg 0 0 ResvSubmsg 0 0 PathTearSubmsg 0 0 ResvTearSubmsg 0 0 PathErrorSubmsg 0 0 ResvErrorSubmsg 0 0 PathQuery 0 0

All RSVP Interfaces Recv Xmit Recv Xmit Path 0 0 Resv 0 0 PathError 0 0 ResvError 0 0 PathTear 0 0 ResvTear 0 0 ResvConfirm 0 0 Hello 0 0 Ack 0 0 SRefresh 0 0 Challenge 0 0 ChallengeRsp 0 0 Retransmit 0 Rate Limited 0 OutOfOrder 0 Bundle 0 0 AckSubmsg 0 0 PathSubmsg 0 0 ResvSubmsg 0 0 PathTearSubmsg 0 0 ResvTearSubmsg 0 0 PathErrorSubmsg 0 0 ResvErrorSubmsg 0 0 PathQuery 0 0

-------------------------- show rsvp counters memory --------------------------Pool size Count ---------- ----------32 048 096 0128 0192 0256 0Dynamic 0

-------------------------- show rsvp counters events --------------------------POS0/1/0/0 All RSVP Interfaces Expired Path states 0 Expired Path states 0 Expired Resv states 0 Expired Resv states 0



OL-17332-01

NACKs received 0 NACKs received 0

------------------- show rsvp counters notifications-client -------------------Total notifications Total filtered notifications Path delete 0 Path delete 0 Path error 0 Path error 0 Path change 0 Path change 0 Matching Resv create 0 Matching Resv create 0 Matching Resv change 0 Matching Resv change 0 Matching Resv delete 0 Matching Resv delete 0 Async Path create 0 Async Path create 0 Resv delete 0 Resv delete 0 Resv error 0 Resv error 0 Resv confirm 0 Resv confirm 0 Async Resv create 0 Async Resv create 0 Listener Path create 0 Listener Path create 0 Listener Path change 0 Listener Path change 0 Listener Path delete 0 Listener Path delete 0 Listener Path FRR 0 Listener Path FRR 0 Listener Assign Backup err 0 Listener Assign Backup err 0 Listener Resv create 0 Listener Resv create 0 Listener Resv change 0 Listener Resv change 0 Listener Resv delete 0 Listener Resv delete 0 Restart Time 0 Restart Time 0 Recovery Done 0 Recovery Done 0

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support multicast


OL-17332-01

show tech-support multicast To automatically run show commands that display information specific to multicast-related information, use the show tech-support multicast command in EXEC mode.

show tech-support multicast [group group-address] {terminal [page] | file send-to} [background | compressed | uncompressed] [source source address] [location node-id] [vrf vrf-name]

Syntax Description group (Optional) Specifies the multicast group address.

group-address (Optional) Address or name of the multicast group. An address is a multicast IP address in four-part dotted-decimal notation. A name is as defined in the Domain Name System (DNS) hosts table.





• filename


• disk0:filename

• disk0a:filename

• disk1:filename

• disk1a:filename

• ftp:filename




• nvram:filename

• rcp:filename

• tftp:filename




source (Optional) Displays the multicast source address.

source address (Optional) Source address for multicast.





OL-17332-01

Defaults Output is logged to the terminal screen.

Command Modes EXEC

Command History



Use the show tech-support multicast command to run show commands that display information specific to multicast-related information for PIM, IGMP, and mcast. This command generates multicast information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support multicast command:

• show version

• show running-config

vrf (Optional) Specifies a VPN routing and forwarding (VRF) instance.

vrf-name (Optional) Name of VRF.













OL-17332-01

• show ip interface brief

• show install

• show processes aborts location all

• show processes blocked location all

• show context location all


• show ip access-lists show ip mhost default-interface

• show msdp summary

• show msdp globals

• show msdp sa-cache summary

• show msdp statistics peer

• show pim group-map

• show pim topology route-count

• show pim topology ip-address

• show pim rpf count

• show pim rpf

• show pim traffic

• show pim join-prune statistic

• show pim interface state-on

• show pim tunnel info all

• show pim neighbor

• show pim nsf

• show pim summary

• show igmp groups summary

• show igmp groups group-address

• show igmp interface

• show igmp traffic

• show igmp nsf

• show igmp summary

• show mrib client filter

• show mrib route summary

• show mrib route source-address

• show mrib nsf

• show cef ipv4 prefix location node-id

• show mfib route summary location node-id

• show mfib route source-address location node-id

• show mfib counter location node-id

• show mfib nsf location node-id



OL-17332-01

• show mfib hardware route olist detail source-address location node-id

• show mfib hardware interface detail location node-id

• show mfib hardware route statistics source-address location node-id

• show mfib hardware resource-counter location node-id

• show mfib hardware adjacency detail location node-id

• show mfib hardware route accept-bitmap detail source-address location node-id



Task ID

Examples The following example shows some of the show tech-support multicast command output:

RP/0/RP0/CPU0:router# show tech-support multicast page

-------------------------------------------------------------------------------

show tech-support multicast location all

-------------------------------------------------------------------------------

-------------------------------- show version --------------------------------

Cisco IOS XR Software, Version 3.8.0 Copyright (c) 2007 by Cisco Systems, Inc.


CRS-1 uptime is 1 week, 4 days, 19 hours, 57 minutesSystem image file is "disk0:hfr-os-mbi-3.8.0/mbihfr-rp.vm"


16 GigabitEthernet/IEEE 802.3 interface(s)4 Ethernet/IEEE 802.3 interface(s)20 Packet over SONET/SDH network interface(s)20 SONET/SDH Port controller(s)2043k bytes of non-volatile configuration memory.38079M bytes of hard disk.1000592k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).1000640k bytes of ATA PCMCIA card at disk 1 (Sector size 512 bytes).

Configuration register on node 0/1/CPU0 is 0x102Boot device on node 0/1/CPU0 is mem:Package active on node 0/1/CPU0:

Task ID Operations


read

multicast read




OL-17332-01

hfr-sbc, V 3.8.0, Cisco Systems, at disk0:hfr-sbc-3.8.0 Built on Thu Mar 15 10:47:29 DST 2007 By cisco.com in /auto/3.8.0 ...--------------------------- show ip interface brief ---------------------------

Interface IP-Address Status ProtocolLoopback0 10.1.1.1 Up Up SBC1 10.75.75.1 Up Up SBC2 10.50.50.1 Up Up Bundle-POS24 10.12.24.1 Up Up Bundle-Ether28 10.12.28.1 Up Up Bundle-Ether28.1 10.12.29.1 Up Up Bundle-Ether28.2 10.12.30.1 Up Up Bundle-Ether28.3 10.12.31.1 Up Up MgmtEth0/RP0/CPU0/0 172.29.52.70 Up Up POS0/1/0/0 unassigned Shutdown Down POS0/1/0/1 10.12.8.1 Up Up POS0/1/0/2 unassigned Shutdown Down POS0/1/0/3 unassigned Shutdown Down POS0/1/4/0 unassigned Up Up POS0/1/4/1 unassigned Up Up POS0/1/4/2 10.12.32.1 Up Up POS0/1/4/3 10.12.32.1 Down Down GigabitEthernet0/1/5/0 10.12.16.1 Up Up GigabitEthernet0/1/5/1 10.14.8.1 Up Up GigabitEthernet0/1/5/2 10.16.4.1 Up Up GigabitEthernet0/1/5/3 unassigned Shutdown Down GigabitEthernet0/1/5/4 unassigned Shutdown Down GigabitEthernet0/1/5/5 unassigned Shutdown Down GigabitEthernet0/1/5/6 unassigned Up Up GigabitEthernet0/1/5/7 unassigned Up Up MgmtEth0/4/CPU0/0 unassigned Up Up MgmtEth0/4/CPU1/0 unassigned Up Up POS0/6/0/0 unassigned Shutdown Down POS0/6/0/1 10.12.12.1 Up Up POS0/6/0/2 unassigned Shutdown Down POS0/6/0/3 unassigned Shutdown Down POS0/6/4/0 unassigned Shutdown Down POS0/6/4/1 unassigned Shutdown Down POS0/6/4/2 unassigned Shutdown Down POS0/6/4/3 unassigned Shutdown Down POS0/6/4/4 10.14.4.1 Up Up POS0/6/4/5 10.12.4.1 Up Up POS0/6/4/6 10.13.4.1 Up Up POS0/6/4/7 unassigned Shutdown Down GigabitEthernet0/6/5/0 unassigned Shutdown Down GigabitEthernet0/6/5/1 10.12.20.1 Up Up GigabitEthernet0/6/5/2 10.16.8.1 Up Up GigabitEthernet0/6/5/3 unassigned Shutdown Down GigabitEthernet0/6/5/4 unassigned Shutdown Down GigabitEthernet0/6/5/5 unassigned Shutdown Down GigabitEthernet0/6/5/6 unassigned Shutdown Down GigabitEthernet0/6/5/7 10.12.40.1 Up Up MgmtEth0/RP1/CPU0/0 172.29.52.71 Up Up

-------------------------------- show install --------------------------------

Node 0/1/CPU0 [LC] [SDR: Owner] Boot Device: mem:



OL-17332-01

Boot Image: /disk0/hfr-os-mbi-3.8.0/lc/mbihfr-lc.vm Active Packages: disk0:hfr-sbc-3.8.0 disk0:hfr-pagent-3.8.0 disk0:hfr-fpd-3.8.0 disk0:hfr-diags-3.8.0 disk0:hfr-mcast-3.8.0 disk0:hfr-mpls-3.8.0 disk0:comp-hfr-mini-3.8.0 ...--------------------- show processes aborts location all ---------------------

node: node0_1_CPU0-------------------------------------------------------------------------------No process aborts found-------------------------------------------------------------------------------node: node0_4_CPU0-------------------------------------------------------------------------------03/27/2007 08:18:35.326 chkpt_proxy(3) (jid 373) abnormally terminated, restart scheduled-------------------------------------------------------------------------------node: node0_4_CPU1-------------------------------------------------------------------------------03/27/2007 08:18:33.265 chkpt_proxy(4) (jid 374) abnormally terminated, restart scheduled-------------------------------------------------------------------------------node: node0_6_CPU0-------------------------------------------------------------------------------No process aborts found-------------------------------------------------------------------------------node: node0_RP0_CPU0-------------------------------------------------------------------------------03/27/2007 03:13:23.722 tcp(1) (jid 343) abnormally terminated, restart scheduled03/16/2007 15:00:59.658 ip_app(1) (jid 203) abnormally terminated, restart scheduled-------------------------------------------------------------------------------node: node0_RP1_CPU0-------------------------------------------------------------------------------03/27/2007 08:18:35.784 te_control(1) (jid 387) abnormally terminated, restart scheduled-------------------------------------------------------------------------------

--------------------- show processes blocked location all ---------------------

node: node0_1_CPU0------------------------------------------------------------------ Jid Pid Tid Name State TimeInState Blocked-on 55 8202 1 ksh Reply 283:52:32:0368 8199 devc-ser8250 51 16407 2 attachd Reply 283:52:39:0627 16405 eth_server 51 16407 3 attachd Reply 283:52:39:0625 8204 mqueue 72 16408 6 qnet Reply 0:00:00:0000 16405 eth_server 72 16408 7 qnet Reply 0:00:00:0000 16405 eth_server 72 16408 8 qnet Reply 0:00:00:0000 16405 eth_server 72 16408 9 qnet Reply 0:00:00:0000 16405 eth_server 52 16412 1 ksh-aux Reply 283:52:34:0211 8199 devc-ser8250 50 16413 2 attach_server Reply 283:52:39:0432 8204 mqueue 218 20516 1 reddrv_listener Reply 0:00:01:0053 16405 eth_server

node: node0_4_CPU0...

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support placement


OL-17332-01

show tech-support placementTo automatically run show commands that display information specific to process placement, use the show tech-support placement command in EXEC mode.

show tech-support placement {terminal [page] | file send-to [background | compressed | uncompressed]}

Syntax Description

Command Modes EXEC

Command History






• filename


• disk0:filename

• disk0a:filename

• disk1:filename

• disk1a:filename

• ftp:filename




• nvram:filename

• rcp:filename

• tftp:filename










OL-17332-01



This command generates process placement debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.




Task ID

Examples The following example shows some of the show tech-support placement command output that is displayed on the terminal:

RP/0/RP0/CPU0:router# show tech-support placement terminal page

-------------------------------------------------------------------------------

show tech-support placement

-------------------------------------------------------------------------------

------------------------------- run lrd_show -I -------------------------------








Task ID Operations

cisco-support read

sysmgr read




OL-17332-01

Success: node_count=6, ready=1node=0x11, type=2, memsize=256, cpus=1, speed=100, sw_state=6, red_state=0, lr_0node=0x41, type=1, memsize=256, cpus=1, speed=100, sw_state=6, red_state=1, lr_fnode=0x42, type=1, memsize=256, cpus=1, speed=100, sw_state=6, red_state=1, lr_fnode=0x61, type=2, memsize=256, cpus=1, speed=100, sw_state=6, red_state=0, lr_0node=0x201, type=0, memsize=256, cpus=1, speed=100, sw_state=6, red_state=1, lr1node=0x211, type=0, memsize=256, cpus=1, speed=100, sw_state=6, red_state=2, lr1

-------------------------- show placement trace all ---------------------------Oct 11 19:23:59.949 main bag_register_all_placed_mgmnt_defs_bags rc = No erOct 11 19:23:59.980 main bag_register_all_placed_mgmnt_bags rc = No errorOct 11 19:24:06.420 main Checkpoint initialization succeededOct 11 19:24:06.665 main Starting for the first time in this LROct 11 19:24:06.725 nodes registered nodes bags, rc = 0 (No error)Oct 11 19:24:06.728 nodes We are running on node 0/RP0/CPU0Oct 11 19:24:06.734 nodes lrd_register_card_state okOct 11 19:24:06.734 nodes Setting timer for 70 seconds, thread 1Oct 11 19:24:06.748 nodes Successfully got inventory (attempt 1 of 30)Oct 11 19:24:06.748 nodes Stopping timerOct 11 19:24:06.748 nodes LR inventory has 4 RP/DRP nodesOct 11 19:24:06.850 nodes update_node: nodeid 0/4/CPU0, pnodeid [NODEID_INV0Oct 11 19:24:06.850 nodes Creating new nodeOct 11 19:24:06.877 nodes update_node: nodeid 0/4/CPU1, pnodeid [NODEID_INV0Oct 11 19:24:06.877 nodes Creating new nodeOct 11 19:24:06.877 nodes update_node: nodeid 0/RP0/CPU0, pnodeid 0/RP1/CPU1Oct 11 19:24:06.877 nodes Creating new nodeOct 11 19:24:06.877 nodes node::_get_active_nodeid(Placed_node (482c1088) (0Oct 11 19:24:06.917 nodes update_node: nodeid 0/RP1/CPU0, pnodeid 0/RP0/CPU2Oct 11 19:24:06.917 nodes Nodeid 0/RP1/CPU0 is already in node object Place)Oct 11 19:24:06.917 nodes Information differsOct 11 19:24:06.917 nodes node 0/RP0/CPU0 is activeOct 11 19:24:06.917 nodes node::_get_active_nodeid(Placed_node (482c1088) (0Oct 11 19:24:06.917 nodes rescan_lrd_inventory rc = 0 (No error)Oct 11 19:24:06.917 nodes apply_startup_type: no action required (0)Oct 11 19:24:06.978 properties registered properties bags, rc = 0 (No error)Oct 11 19:24:06.978 properties Inserting Nodetypeaffinity (48283504) (value 100)Oct 11 19:24:06.985 edm placed_edm_init succeededOct 11 19:24:07.086 properties Inserting Classaffinity (482827b8) (value 250.00gOct 11 19:24:07.086 properties Inserting Classaffinity (48282830) (value 250.00iOct 11 19:24:07.086 properties Inserting Classaffinity (4828286c) (value 250.00gOct 11 19:24:07.086 properties Inserting Classaffinity (482828a8) (value 250.00iOct 11 19:24:07.086 properties Inserting Selfaffinity (483297ac) (value -160.00)Oct 11 19:24:07.086 properties Inserting Nodetypeaffinity (483297e0) (value -50)Oct 11 19:24:07.086 properties Inserting Nodetypeaffinity (48329814) (value 50.)Oct 11 19:24:07.086 properties Inserting Nodetypeaffinity (48329848) (value 600)Oct 11 19:24:07.131 properties Inserting Classaffinity (482828e4) (value 70.00)iOct 11 19:24:07.131 properties Inserting Classaffinity (48282920) (value 70.00)iOct 11 19:24:07.131 properties Inserting Classaffinity (4828295c) (value 70.00)iOct 11 19:24:07.132 properties Inserting Classaffinity (4832b048) (value 70.00)iOct 11 19:24:07.132 properties Inserting Nodetypeaffinity (483298b0) (value -15)Oct 11 19:24:07.132 properties Inserting Nodetypeaffinity (483298e4) (value 200)Oct 11 19:24:07.132 properties Inserting Nodetypeaffinity (48329918) (value 600)Oct 11 19:24:07.193 properties Inserting Nodetypeaffinity (4832994c) (value -20)Oct 11 19:24:07.194 properties Inserting Nodetypeaffinity (4832b818) (value 250)Oct 11 19:24:07.226 properties Inserting Nodetypeaffinity (4832b880) (value -402Oct 11 19:24:07.275 properties Inserting Nodetypeaffinity (4832b8b4) (value -20)Oct 11 19:24:07.275 properties Inserting Nodetypeaffinity (4832b8e8) (value 250)Oct 11 19:24:07.350 properties Inserting Nodetypeaffinity (4832b950) (value -402Oct 11 19:24:07.402 properties Inserting Nodetypeaffinity (4832b9b8) (value -40)Oct 11 19:24:07.562 properties Inserting Nodetypeaffinity (4832baf0) (value 100)

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support platform


OL-17332-01

show tech-support platform To automatically run show commands that display information specific to platforms, use the show tech-support platform command in EXEC mode.

show tech-support platform {terminal [page] | file send-to}

Syntax Description


Command Modes EXEC

Command History






• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename







OL-17332-01



Use the show tech-support platform command to run show commands that display information specific to platforms. This command generates platform debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support platform command:

• show controller squid summary

• show controller plim asic statistics summary location node-id

See the Cisco IOS XR command references for information about these commands and descriptions of their command output. The Cisco Cisco IOS XR command references are located at the following URL:


Task ID

Examples The following example shows some of the show tech-support platform command output:

RP/0/RP0/CPU0:router# show tech-support platform terminal page

------------------------ show controller squid summary ------------------------Cpuctrl discovered 14 device on node 0/1/CPU0:








Task ID Operations

basic-services read




OL-17332-01

Cpuctrl HW version string for this node is:Squid FPGA v2.07 Fri Jan 23 16:21:01 2004 userb

-----------------------------------------------------------device_name: Fabricq device instance: 0 Cpuctrl net port: 3 pci_base: 0x8c000000

-----------------------------------------------------------device_name: Fabricq device instance: 1 Cpuctrl net port: 4 pci_base: 0x90000000

-----------------------------------------------------------device_name: Ingressq device instance: 0 Cpuctrl net port: 8 pci_base: 0xa0000000

-----------------------------------------------------------device_name: Egressq device instance: 0 Cpuctrl net port: 7 pci_base: 0x9c000000

-----------------------------------------------------------device_name: FIA device instance: 0 Cpuctrl net port: 1 pci_base: 0x84000000

-----------------------------------------------------------device_name: FIA device instance: 1 Cpuctrl net port: 2 pci_base: 0x88000000

-----------------------------------------------------------device_name: Cpuctrl device instance: 0 Cpuctrl net port: 0 pci_base: 0x80000000

-----------------------------------------------------------device_name: PSE device instance: 1 Cpuctrl net port: 6 pci_base: 0x98000000

-----------------------------------------------------------device_name: PSE device instance: 0 Cpuctrl net port: 5 pci_base: 0x94000000

-----------------------------------------------------------device_name: PlimAsic for SPA device instance: 0 Cpuctrl net port: 9 pci_base: 0xa4000000...------- show controller plim asic statistics summary location 0/1/CPU0 -------- Node: 0/1/CPU0--------------------------------------Instance# 0 Statistics---------------------------------------------------------------------To PSE : 1034176 BP count : 2615809697RMC Runt : 0 RMC Giant : 0 RMC Tail Drop: 1 L2P Drop : 0 From Egressq : 924513 SIF Drop : 0 TLK Drop : 0

Port 0To SPA : 0 From SPA : 0 RSI FIFO Drop: 0 QPM Drop : 0 QPM OVFL : 0 RPB Drop : 0

Port 1To SPA : 0 From SPA : 0



OL-17332-01

RSI FIFO Drop: 0 QPM Drop : 0 QPM OVFL : 0 RPB Drop : 0


Instance# 1 Statistics---------------------------------------------------------------------To PSE : 9217833 BP count : 2323530765RMC Runt : 0 RMC Giant : 0 RMC Tail Drop: 2590 L2P Drop : 0 From Egressq : 9317309 SIF Drop : 0 TLK Drop : 0

Port 0To SPA : 0 From SPA : 0 RSI FIFO Drop: 0 QPM Drop : 0 QPM OVFL : 0 RPB Drop : 0 Port 1To SPA : 537745 From SPA : 546867 RSI FIFO Drop: 0 QPM Drop : 0 QPM OVFL : 0 RPB Drop : 0


Tech-Support Commands on Cisco IOS XR Softwareshow tech-support rdsfs


OL-17332-01

show tech-support rdsfsTo automatically run show commands that display information specific to Replication Data Services File System (RDSFS) debugging, use the show tech-support rdsfs command in EXEC mode.

show tech-support rdsfs {terminal [page] | file send-to [background] [compressed | uncompressed]}

Syntax Description

Command Modes EXEC

Command History






• filename


• disk0:filename

• disk0a:filename

• disk1:filename

• disk1a:filename

• ftp:filename




• nvram:filename

• rcp:filename

• tftp:filename










OL-17332-01



Use the show tech-support rdsfs command to run show commands that display information specific to RDSFS debugging and is relevant to bring to a ready state. This command generates RDSFS debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.




Task ID

Examples The following example shows some of the show tech-support rdsfs command output that is displayed on the terminal:

RP/0/RP0/CPU0:router# show tech-support rdsfs terminal page

-------------------------------------------------------------------------------

show tech-support rdsfs

-------------------------------------------------------------------------------

-------------------------------- show platform --------------------------------








Task ID Operations

cisco-support read




OL-17332-01

Node Type PLIM State Config State-----------------------------------------------------------------------------0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/1/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON0/1/1 MSC(SPA) 4T3E3 OK PWR,NSHUT,MON0/1/4 MSC(SPA) 4XOC48-POS OK PWR,NSHUT,MON0/1/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON0/4/CPU0 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON0/4/CPU1 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON0/6/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/6/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON0/6/4 MSC(SPA) 8XOC3/OC12-POS OK PWR,NSHUT,MON0/6/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON

-------------------------- follow rdsfs_svr process ---------------------------

Note that this commands will only run on the currently attached

node, regardless of location specified

These commands are run once now and once towards the end of the command. This is to avoid the delay between iterations of follow

------------------ follow process 155728 iteration 1 verbose ------------------

Attaching to process pid = 155728 (pkg/bin/rdsfs_svr)No tid specified, following all threads

DLL Loaded by this process -------------------------------

DLL path Text addr. Text size Data addr. Data size Version/pkg/lib/libsysmgr.dll 0xfc131000 0x00013748 0xfc145000 0x0000066c 0/pkg/lib/libcerrno.dll 0xfc146000 0x00002f94 0xfc088eb0 0x00000128 0/pkg/lib/libcerr_dll_tbl.dll 0xfc149000 0x00004bb0 0xfc0c5cc0 0x00000148 0/pkg/lib/libltrace.dll 0xfc14e000 0x000095d8 0xfc14566c 0x00000328 0/pkg/lib/lib_platform_infra_ltrace.dll 0xfc158000 0x00001044 0xfc0c5e08 0x000000/pkg/lib/libinfra.dll 0xfc15a000 0x000397b0 0xfc194000 0x00000cc0 0/pkg/lib/cerrno/libinfra_error.dll 0xfc1211dc 0x00000cd8 0xfc0c5e90 0x000000a8 0/pkg/lib/libios.dll 0xfc195000 0x0002d510 0xfc1c3000 0x00002000 0/pkg/lib/cerrno/libevent_manager_error.dll 0xfc159044 0x00000e88 0xfc0c5f38 0x00/pkg/lib/libc.dll 0xfc1ce000 0x0007b6e0 0xfc24a000 0x00002000 0/pkg/lib/libplatform.dll 0xfc250000 0x0000cd14 0xfc25d000 0x00002000 0/pkg/lib/lib_procfs_util.dll 0xfc261000 0x00004e8c 0xfc194cc0 0x000002a8 0/pkg/lib/libsyslog.dll 0xfc266000 0x0000564c 0xfc26c000 0x00000328 0/pkg/lib/libbackplane.dll 0xfc26d000 0x000013f0 0xfc145ea0 0x000000a8 0/pkg/lib/libnodeid.dll 0xfc279000 0x0000af28 0xfc26c8b0 0x00000260 0/pkg/lib/libdebug.dll 0xfc2d7000 0x00012764 0xfc2d61c8 0x00000630 0/pkg/lib/cerrno/libdebug_error.dll 0xfc2ea000 0x00000db0 0xfc26ce50 0x000000e8 0/pkg/lib/libsysdb.dll 0xfc629000 0x00050b00 0xfc67a000 0x00000b74 0/pkg/lib/cerrno/libsysmgr_error.dll 0xfc585058 0x00000f94 0xfc4feee4 0x000000880/pkg/lib/libsysdbutils.dll 0xfc690000 0x0000d378 0xfc5ddabc 0x0000046c 0/pkg/lib/cerrno/libsysdb_error_v1v2.dll 0xfc6a0000 0x00001e08 0xfc575e6c 0x00000/pkg/lib/cerrno/libsysdb_error_v2only.dll 0xfc6a5000 0x00002848 0xfc5c7f78 0x000

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support rib


OL-17332-01

show tech-support ribTo automatically run show commands that display information specific to Routing Information Base (RIB) debugging, use the show tech-support rib command in EXEC mode.

show tech-support rib {terminal [page] | file send-to [background] [compressed | uncompressed]} [ipv4 | ipv6]

Syntax Description

Command Modes EXEC






• filename


• disk0:filename

• disk0a:filename

• disk1:filename

• disk1a:filename

• ftp:filename




• nvram:filename

• rcp:filename

• tftp:filename




ipv4 (Optional) Displays the IPv4 command output.

ipv6 (Optional) Displays the IPv6 command output.

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support rib


OL-17332-01

Command History



The RIB data stores the best path information for the routing protocol that is sent to FIB to help build the data structures. This command generates RIB debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.




Task ID

Examples The following example shows some of the show tech-support rib command output that is displayed on the terminal:

RP/0/RP0/CPU0:router# show tech-support rib terminal page











Task ID Operations

cisco-support read


Tech-Support Commands on Cisco IOS XR Softwareshow tech-support routing bfd


OL-17332-01

show tech-support routing bfdTo automatically run show commands that display information specific to Bidirectional Forwarding Detection (BFD) debugging, use the show tech-support routing bfd command in EXEC mode.

show tech-support routing bfd {terminal [page] | file send-to [background] [compressed | uncompressed]}

Syntax Description


Command Modes EXEC






• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename






OL-17332-01

Command History



Use the show tech-support routing bfd command to run show commands that display information specific to BFD debugging. This command generates BFD debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support routing bfd command:

• show bfd session

• show bfd

• show memory heap fail all


• show process blocked location all

• show adjacency

• show bfd location

• show bfd session detail location node-id

• show cef drop location node-id

• show udp brief location node-id

• show udp statistics pcb all location node-id

• show bfd session agent detail location











OL-17332-01

• show bfd timer-groups location

• show bfd index-mgrs location

• show bfd session-array location node-id

• show bfd interfaces location node-id

• show bfd bundles detail location node-id

• show bfd counters packet invalid location node-id

• show bfd counters packet private location node-id

• show bfd client private

• show bfd trace all-cards

• show controllers cpuctrl summary

• show controllers cpuctrl client pdma bfd active location all

• show controllers cpuctrl ports ingressq pdma all active location node-id

• show controllers cpuctrl ports egressq pdma all active location node-id

• show controllers pse statistics location node-id



Task ID

Examples The following example shows some of the show tech-support routing bfd command output:

RP/0/RP0/CPU0:router# show tech-support routing bfd terminal page

-------------------------------------------------------------------------------

show tech-support bfd (Detail with Event traces)

-------------------------------------------------------------------------------

------------------------------ show bfd session -------------------------------

---------------------------------- show bfd -----------------------------------IPV4 Sessions Up: 0, Down: 0, Total: 0

-------------------------- show memory heap fail all --------------------------

---------------------- show memory summary location all -----------------------

node: node0_1_CPU0------------------------------------------------------------------Physical Memory: 2048M total Application Memory : 1905M (1401M available) Image: 14M (bootram: 14M) Reserved: 128M, IOMem: 2028M, flashfsys: 0 Total shared window: 55M

Task ID Operations

basic-services read




OL-17332-01

node: node0_4_CPU0------------------------------------------------------------------Physical Memory: 4096M total Application Memory : 3947M (3549M available) Image: 19M (bootram: 19M)

Reserved: 128M, IOMem: 2028M, flashfsys: 0 Total shared window: 21M



node: node0_RP0_CPU0------------------------------------------------------------------Physical Memory: 4096M total Application Memory : 3945M (3192M available) Image: 22M (bootram: 22M) Reserved: 128M, IOMem: 2028M, flashfsys: 0 Total shared window: 21M

node: node0_RP1_CPU0------------------------------------------------------------------Physical Memory: 4096M total Application Memory : 3945M (3372M available) Image: 22M (bootram: 22M) Reserved: 128M, IOMem: 2028M, flashfsys: 0 Total shared window: 21M

---------------------- show process blocked location all ----------------------

node: node0_1_CPU0------------------------------------------------------------------ Jid Pid Tid Name State TimeInState Blocked-on 55 8202 1 ksh Reply 304:11:57:0624 8199 devc-ser8250 51 16407 2 attachd Reply 304:12:04:0893 16405 eth_server 51 16407 3 attachd Reply 304:12:04:0891 8204 mqueue 72 16408 6 qnet Reply 0:00:00:0000 16405 eth_server 72 16408 7 qnet Reply 0:00:00:0000 16405 eth_server 72 16408 8 qnet Reply 0:00:00:0000 16405 eth_server 72 16408 9 qnet Reply 0:00:00:0000 16405 eth_server 52 16412 1 ksh-aux Reply 304:11:59:0480 8199 devc-ser8250 50 16413 2 attach_server Reply 304:12:04:0703 8204 mqueue 218 20516 1 reddrv_listener Reply 0:00:02:0206 16405 eth_server...------------------------------ show bfd location ------------------------------



OL-17332-01

Location: 0/1/CPU0IPV4 Sessions Up: 0, Down: 0, Standby: 0, Total: 0

Location: 0/1/SP...

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support routing isis


OL-17332-01

show tech-support routing isisTo automatically run show commands that display information specific to Intermediate System-to-Intermediate System (IS-IS) debugging, use the show tech-support routing isis command in EXEC mode.

show tech-support routing isis {terminal [page] | file send-to [background] [compressed | uncompressed]}

Syntax Description


Command Modes EXEC






• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename






OL-17332-01

Command History



Use the show tech-support isis command to run show commands that display information specific to IS-IS debugging. This command generates IS-IS debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support routing isis command:

• show isis instance isp trace all

• show isis all

• show clns statistics

• show imds interface all

• show ipv4 int brief

• show ipv6 int brief

• show route ipv4

• show route ipv6

• show inst which comp clns-isis














OL-17332-01

Task ID

Examples The following example shows some of the show tech-support routing isis command output:

RP/0/RP0/CPU0:router# show tech-support isis terminal page

-------------------------------------------------------------------------------

show tech-support isis

-------------------------------------------------------------------------------

---------------------- show isis instance isp trace all -----------------------184 wrapping entries (6144 possible, 0 filtered, 184 total)Mar 29 08:38:18.437 isis/isp/sev 0/RP0/CPU0 t1 STARTUP_STARTMar 29 08:38:18.437 isis/isp/sev 0/RP0/CPU0 t1 STARTUP_MODULEMar 29 08:38:18.438 isis/isp/sev 0/RP0/CPU0 t1 STARTUP_MODULEMar 29 08:38:18.438 isis/isp/sev 0/RP0/CPU0 t1 THREAD_CREATINGMar 29 08:38:18.451 isis/isp/det 0/RP0/CPU0 t1 THREAD_THREAD_IDMar 29 08:38:18.451 isis/isp/sev 0/RP0/CPU0 t1 THREAD_CREATINGMar 29 08:38:18.451 isis/isp/sev 0/RP0/CPU0 t1 THREAD_CREATINGMar 29 08:38:18.452 isis/isp/sev 0/RP0/CPU0 t1 THREAD_CREATINGMar 29 08:38:18.452 isis/isp/sev 0/RP0/CPU0 t1 THREAD_CREATINGMar 29 08:38:18.536 isis/isp/sev 0/RP0/CPU0 t1 STARTUP_MODULEMar 29 08:38:19.274 isis/isp/sev 0/RP0/CPU0 t1 STARTUP_MODULEMar 29 08:38:19.470 isis/isp/sev 0/RP0/CPU0 t1 IO_PAK_SERVER_CONNECTEDMar 29 08:38:19.551 isis/isp/det 0/RP0/CPU0 t1 IO_SOCKET_CREATE_SUCCESSMar 29 08:38:19.555 isis/isp/sev 0/RP0/CPU0 t1 IO_SOCKET_CONN_OPENMar 29 08:38:20.561 isis/isp/std 0/RP0/CPU0 t1 ROUTE_RIB_PURGE_TIME_SET...Mar 29 08:38:27.622 isis/isp/det 0/RP0/CPU0 t4 THREAD_FOP_PROCESSMar 29 08:38:27.622 isis/isp/det 0/RP0/CPU0 t4 SSM_TICK_TIMER_FIRES CR-SYNC-LSPDBMar 29 08:38:27.622 isis/isp/det 0/RP0/CPU0 t4 SSM_STATE_RESULT CR-SYNC-LSPDBMar 29 08:38:27.622 isis/isp/det 0/RP0/CPU0 t4 SSM_STATE_TIME_BUDGET CR-SYNC-LSPDBMar 29 08:38:27.622 isis/isp/sev 0/RP0/CPU0 t4 SSM_STATE_RUN CR-SYNC-LSPDB

-------------------------------- show isis all --------------------------------

No IS-IS isp levels foundNo IS-IS isp levels foundNo IS-IS isp levels foundNo IS-IS isp levels foundNo IS-IS isp levels foundNo IS-IS isp levels foundNo IS-IS isp levels foundNo IS-IS isp levels foundNo IS-IS isp levels foundNo IS-IS isp IPv4 Unicast levels foundNo IS-IS isp IPv4 Unicast levels foundNo IS-IS isp IPv4 Unicast levels foundNo IS-IS isp IPv4 Unicast levels foundNo IS-IS isp IPv4 Unicast levels foundIS-IS Router: isp System Id: 0000.0000.0000 (Not configured, protocol disabled) IS Levels: level-1-2 Manual area address(es): Routing for area address(es):

Task ID Operations

basic-services read



OL-17332-01

Non-stop forwarding: Disabled Most recent startup mode: Cold Restart Topologies supported by IS-IS: IPv4 Unicast No protocols redistributed Distance: 115 Interfaces supported by IS-IS: POS0/1/0/0 is disabled (active in configuration)

No IS-IS isp host data available

IS-IS isp InterfacesPOS0/1/0/0 Disabled (No NET configured)

IS-IS isp Interfaces Interface All Adjs Adj Topos Adv Topos CLNS MTU Prio OK L1 L2 Run/Cfg Run/Cfg L1 L2----------------- --- --------- --------- --------- ---- ---- --------PO0/1/0/0 No

No IS-IS isp mesh-groups found

IS-IS isp statistics: IS-IS statistics: Fast PSNP cache (hits/tries): 0/0 LSP checksum errors received: 0 LSP Dropped: 0 SNP Dropped: 0 UPD Max Queue size: 0

IS-IS isp neighbor summary:State L1 L2 L1L2Up 0 0 0Init 0 0 0Failed 0 0 0 IS-IS isp neighbors:System Id Interface SNPA State Holdtime Type IETF-NSF

IS-IS isp Database Summary for all LSPs Active Purged All L1 L2 Total L1 L2 Total L1 L2 Total ----- ----- ----- ----- ----- ----- ----- ----- -----Fragment 0 Counts Router LSPs: 0 0 0 0 0 0 0 0 0 Pseudo-node LSPs: 0 0 0 0 0 0 0 0 0 All LSPs: 0 0 0 0 0 0 0 0 0

All Fragment Counts Router LSPs: 0 0 0 0 0 0 0 0 0 Pseudo-node LSPs: 0 0 0 0 0 0 0 0 0 All LSPs: 0 0 0 0 0 0 0 0 0

IS-IS isp IS Topology Summary IPv4 Unicast L1 L2 Reach UnReach Total Reach UnReach Total ------- ------- ------- ------- ------- -------Router nodes: 0 0 0 0 0 0Pseudo nodes: 0 0 0 0 0 0

Total nodes: 0 0 0 0 0 0

IS-IS isp IPv4 Unicast routes



OL-17332-01

Codes: L1 - level 1, L2 - level 2, ia - interarea (leaked into level 1) df - level 1 default (closest attached router), su - summary null C - connected, S - static, R - RIP, B - BGP, O - OSPF i - IS-IS (redistributed from another instance)

Maximum parallel path count: 8

IS-IS isp checkpoint interfaceInterface Handle CircNum DIS Areas Adj Chkpt IDNo 'checkpoint interfaces' found in IS-IS isp

IS-IS isp checkpoint adjacenciesSystem ID Interface SNPA Lvl Hold Pri CID Chkpt ID NexthopsNo 'checkpoint adjacencies' found in IS-IS isp

IS-IS isp checkpoint LSPsLevel LSPID Chkpt ID No 'checkpoint LSPs' found in IS-IS isp

Total LSP count: 0 (L1: 0, L2 0, local L1: 0, local L2 0)

---------------------------- show clns statistics -----------------------------CLNS Statistics:Last counter clear: 1067929 seconds agoTotal number of packets sent: 0Total number of packets received: 0Send packets dropped, total: 0Send packets dropped, buffer overflow: 0Send packets dropped, out of memory: 0Send packets dropped, netio: 0Send packets dropped, other: 0Receive socket max queue size: 0Receive packets dropped, total: 0Receive packets dropped, other: 0Receive packets dropped per pdu class:

Class Overflow/Max Rate Limit/MaxIIH 0/0 0/0 LSP 0/0 0/0 SNP 0/0 0/0 OTHER 0/0 0/0 Total 0 0

--------------------------- show imds interface all ---------------------------IMDS INTERFACE DATA (Node 0x201)

MgmtEth0_RP0_CPU0_0 (0x00080000)-----------------------flags: 0x0001002f type: 8 (IFT_ETHERNET) encap: 30 (ether)state: 3 (up) mtu: 1514 protocol count: 4control parent: 0x00000000 data parent: 0x00000000 protocol capsulation state mtu --------------- -------------------- --------------- -------- 7 (arp) ...

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support routing ospf


OL-17332-01

show tech-support routing ospfTo automatically run show commands that display information specific to Open Shortest Path First (OSPF) debugging, use the show tech-support routing ospf command in EXEC mode.

show tech-support routing ospf [process-id] {terminal [page] | file send-to [background] [compressed | uncompressed]}

Syntax Description


Command Modes EXEC

process-id (Optional) Name of the OSPF process.






• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename






OL-17332-01

Command History



Use the show tech-support routing ospf command to run show commands that display information specific to OSPF debugging. This command generates OSPF debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support routing ospf command:

• show ospf

• show ospf vrf all

• show ospf summary

• show ospf vrf all summary

• show ospf interface

• show ospf vrf all interface

• show ospf virtual-links

• show ospf vrf all virtual-links

• show ospf neighbor detail

• show ospf vrf all neighbor detail

• show ospf database database-summary

• show ospf vrf all database database-summary











OL-17332-01

• show ospf database router self-originate

• show ospf vrf all database router self-originate

• show ospf statistics prot

• show ospf statistics raw-io

• show ospf statistics te

• show ospf statistics spf

• show ospf statistics rib-thread

• show ospf statistics rib-batch

• show ospf message-queue

• show ospf border-routers

• show ospf vrf all border-routers

• show ospf retransmission-list

• show ospf vrf all retransmission-list

• show ospf request-list

• show ospf vrf all request-list

• show ospf flood-list

• show ospf vrf all flood-list

• show ospf maxage-list

• show ospf vrf all maxage-list

• show ospf bad-checksum

• show ospf vrf all bad-checksum

• show ospf standby

• show ospf vrf all standby

• show ip interface brief

• show route ipv4 summary

• show route vrf all ipv4 summary

• show ospf trace all

• show logging process ospf



Task ID

Examples The following example shows some of the show tech-support routing ospf command output:

RP/0/RP0/CPU0:router# show tech-support routing ospf terminal page

Task ID Operations

basic-services read




OL-17332-01

-------------------------------------------------------------------------------

show tech-support ospf -------------------------------------------------------------------------------

---------------------------------- show ospf ----------------------------------

Routing Process "ospf 100" with ID 10.1.1.1 Supports only single TOS(TOS0) routes Supports opaque LSA Initial SPF schedule delay 5000 msecs Minimum hold time between two consecutive SPFs 10000 msecs Maximum wait time between two consecutive SPFs 10000 msecs Initial LSA throttle delay 500 msecs Minimum hold time for LSA throttle 5000 msecs Maximum wait time for LSA throttle 5000 msecs Minimum LSA interval 5000 msecs. Minimum LSA arrival 1 secs Flood pacing interval 33 msecs. Retransmission pacing interval 66 msecs Maximum number of configured interfaces 255 Number of external LSA 0. Checksum Sum 00000000 Number of opaque AS LSA 0. Checksum Sum 00000000 Number of DCbitless external and opaque AS LSA 0 Number of DoNotAge external and opaque AS LSA 0 Number of areas in this router is 1. 1 normal 0 stub 0 nssa External flood list length 0 Non-Stop Forwarding enabled Area BACKBONE(0) Number of interfaces in this area is 12 SPF algorithm executed 350 times Number of LSA 31. Checksum Sum 0x10c978 Number of opaque link LSA 0. Checksum Sum 00000000 Number of DCbitless LSA 0 Number of indication LSA 0 Number of DoNotAge LSA 0 Flood list length 0

------------------------------ show ospf vrf all ------------------------------

------------------------------ show ospf summary ------------------------------

Number of OSPF interfaces 12Number of OSPF interfaces up 12Number of OSPF virtual interfaces up 0Number of neighbors 9Number of neighbors adjacent 9Number of areas 1 LSA Type Count Router : 13 Network : 11 Summary Net : 7 Summary ASBR : 0 Type-7 Ext : 0 Opaque Link : 0 Opaque Area : 0 Type-5 Ext : 0 Opaque AS : 0

-------------------------- show ospf vrf all summary --------------------------

----------------------------- show ospf interface -----------------------------

POS0/1/0/1 is up, line protocol is up Internet Address 10.12.8.1/24, Area 0



OL-17332-01

Process ID 100, Router ID 10.1.1.1, Network Type POINT_TO_POINT, Cost: 1 Transmit Delay is 1 sec, State POINT_TO_POINT, Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 Non-Stop Forwarding (NSF) enabled Hello due in 00:00:08 Index 3/3, flood queue length 0 Next 0(0)/0(0) Last flood scan length is 1, maximum is 19 Last flood scan time is 0 msec, maximum is 1 msec Neighbor Count is 1, Adjacent neighbor count is 1 Adjacent with neighbor 10.2.2.2 Suppress hello for 0 neighbor(s) Multi-area interface Count is 0GigabitEthernet0/1/5/1 is up, line protocol is up Internet Address 10.14.8.1/24, Area 0 Process ID 100, Router ID 10.1.1.1, Network Type BROADCAST, Cost: 1 Transmit Delay is 1 sec, State BDR, Priority 1 Designated Router (ID) 10.4.4.4, Interface address 10.14.8.4 Backup Designated router (ID) 10.1.1.1, Interface address 10.14.8.1 Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 Non-Stop Forwarding (NSF) enabled Hello due in 00:00:05 Index 2/2, flood queue length 0 Next 0(0)/0(0) Last flood scan length is 1, maximum is 4 Last flood scan time is 0 msec, maximum is 0 msec Neighbor Count is 1, Adjacent neighbor count is 1 Adjacent with neighbor 10.4.4.4 (Designated Router) Suppress hello for 0 neighbor(s) Multi-area interface Count is 0GigabitEthernet0/1/5/2 is up, line protocol is up Internet Address 10.16.4.1/24, Area 0 Process ID 100, Router ID 10.1.1.1, Network Type BROADCAST, Cost: 1 Transmit Delay is 1 sec, State BDR, Priority 1 Designated Router (ID) 10.6.6.6, Interface address 10.16.4.6 Backup Designated router (ID) 10.1.1.1, Interface address 10.16.4.1 Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 Non-Stop Forwarding (NSF) enabled Hello due in 00:00:04 Index 4/4, flood queue length 0 Next 0(0)/0(0) Last flood scan length is 1, maximum is 4 Last flood scan time is 0 msec, maximum is 1 msec Neighbor Count is 1, Adjacent neighbor count is 1 Adjacent with neighbor 10.6.6.6 (Designated Router) Suppress hello for 0 neighbor(s) Multi-area interface Count is 0POS0/6/0/1 is up, line protocol is up Internet Address 10.12.12.1/24, Area 0 Process ID 100, Router ID 10.1.1.1, Network Type POINT_TO_POINT, Cost: 1 Transmit Delay is 1 sec, State POINT_TO_POINT, Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 Non-Stop Forwarding (NSF) enabled Hello due in 00:00:01 Index 8/8, flood queue length 0 Next 0(0)/0(0) Last flood scan length is 1, maximum is 4 Last flood scan time is 0 msec, maximum is 0 msec Neighbor Count is 1, Adjacent neighbor count is 1 Adjacent with neighbor 10.2.2.2 Suppress hello for 0 neighbor(s) Multi-area interface Count is 0..

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support routing ospfv3


OL-17332-01

show tech-support routing ospfv3To automatically run show commands that display information specific to Open Shortest Path First Version 3 (OSPFv3) debugging, use the show tech-support routing ospfv3 command in EXEC mode.

show tech-support routing ospfv3 [instance] [detail] {terminal [page] | file send-to [background] [compressed | uncompressed]}

Syntax Description


Command Modes EXEC

instance (Optional) Name of the OSPFv3 instance.

detail (Optional) Displays all available OSPFv3 information.






• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename






OL-17332-01

Command History



Use the show tech-support routing ospfv3 command to run show commands that display information specific to OSPFv3 debugging. This command generates OSPFv3 debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support routing ospfv3 command:

• show version

• show run router ospfv3

• show route ipv6 ospf

• show ospfv3

• show ospfv3 interface

• show ospfv3 virtual-links

• show ospfv3 neighbor

• show ospfv3 message-queue

• show ospfv3 request-list

• show ospfv3 retransmission-list

• show ospfv3 flood-list

• show ospfv3 border-routers

• show ospfv3 database database-summary










OL-17332-01

• show ospfv3 database

• show ospfv3 route



Task ID

Examples The following example shows some of the show tech-support routing ospfv3 command output:

RP/0/RP0/CPU0:router# show tech-support routing ospfv3 terminal page

Mon Nov 10 18:36:21.028 PST DST

-------------------------------------------------------------------------------

show tech-support ospfv3

-------------------------------------------------------------------------------

-------------------------------- show version ---------------------------------

Cisco IOS XR Software, Version 3.8.0.20I[DT_IMAGE]Copyright (c) 2008 by Cisco Systems, Inc.


P2_CRS-8 uptime is 6 days, 16 hours, 38 minutesSystem image file is "bootflash:disk0/hfr-os-mbi-3.8.0.20I/mbihfr-rp.vm"


4 Management Ethernet16 GigabitEthernet20 SONET/SDH20 Packet over SONET/SDH1019k bytes of non-volatile configuration memory.1000592k bytes of disk0: (Sector size 512 bytes).1000640k bytes of disk1: (Sector size 512 bytes).

Configuration register on node 0/1/CPU0 is 0x102Boot device on node 0/1/CPU0 is mem:Package active on node 0/1/CPU0:hfr-services, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-services-3.8.0IBuilt on Wed Oct 29 17:03:08 DST 2008By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0


hfr-fpd, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-fpd-3.8.0.20I

Task ID Operations

basic-services read




OL-17332-01

Built on Wed Oct 29 17:02:19 DST 2008By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0









Configuration register on node 0/4/CPU0 is 0x102Boot device on node 0/4/CPU0 is disk0:Package active on node 0/4/CPU0:hfr-services, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-services-3.8.0IBuilt on Wed Oct 29 17:03:08 DST 2008By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0


hfr-doc, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-doc-3.8.0.20IBuilt on Wed Oct 29 17:02:31 DST 2008By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0



hfr-k9sec, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-k9sec-3.8.0.20IBuilt on Wed Oct 29 16:59:58 DST 2008By iox26.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0

hfr-mgbl, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-mgbl-3.8.0.20IBuilt on Wed Oct 29 16:31:48 DST 2008



OL-17332-01

By sjc5-gf-021.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/h0



hfr-rout, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-rout-3.8.0.20IBuilt on Wed Oct 29 16:21:29 DST 2008By iox30.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0






Configuration register on node 0/4/CPU1 is 0x102Boot device on node 0/4/CPU1 is disk0:Package active on node 0/4/CPU1:hfr-services, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-services-3.8.0IBuilt on Wed Oct 29 17:03:08 DST 2008By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0


hfr-doc, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-doc-3.8.0.20IBuilt on Wed Oct 29 17:02:31 DST 2008By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0



hfr-k9sec, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-k9sec-3.8.0.20IBuilt on Wed Oct 29 16:59:58 DST 2008By iox26.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0

--More--

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support routing rpl


OL-17332-01

show tech-support routing rpl To automatically run show commands that display information specific to Routing Policy Language (RPL) debugging, use the show tech-support routing rpl command in EXEC mode.

show tech-support routing rpl {terminal [page] | file send-to [background] [compressed | uncompressed]}

Syntax Description


Command Modes EXEC






• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename






OL-17332-01

Command History



Use the show tech-support routing rpl command to run show commands that display information specific to RPL debugging. This command generates RPL debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.


The following show commands run automatically when you run the show tech-support routing rpl command:

• show running-config rpl

• show process policy_repository

• show rpl route-policy policy-name pxl

• show sysdb reg notif path /ipc/gl/policy_lang/policies/routing/policy-name/pxl s



Task ID






Task ID Operations

basic-services read




OL-17332-01

Examples The following example shows some of the show tech-support routing rpl command output:

RP/0/RP0/CPU0:router# show tech-support routing rpl terminal page

Mon Nov 10 18:53:02.220 PST DST

-------------------------------------------------------------------------------start of show tech-support routing rpl-------------------------------------------------------------------------------

-------------------------------------------------------------------------------RPL CLients Configuration-------------------------------------------------------------------------------

router ospf 100router-id 10.2.2.2nsf ciscoarea 0mpls traffic-enginterface Bundle-POS24!interface Loopback0passive enable!interface GigabitEthernet0/1/5/1!interface GigabitEthernet0/1/5/2bfd fast-detect!interface GigabitEthernet0/6/5/1!interface POS0/1/0/1!interface POS0/1/0/2!interface POS0/1/0/3!interface POS0/6/0/1!interface POS0/6/4/4!interface POS0/6/4/6!interface POS0/6/4/7!!mpls traffic-eng router-id Loopback0!


Mon Nov 10 18:53:03.975 PST DSTrouter isis labis-type level-2-onlynet 49.1122.0000.0000.0002.00interface Loopback0passiveaddress-family ipv4 unicast!!interface POS0/1/0/2address-family ipv4 unicast



OL-17332-01

!!interface POS0/1/0/3address-family ipv4 unicast!!!


Mon Nov 10 18:53:05.457 PST DSTrouter eigrp 24vrf vrf_1address-family ipv4router-id 172.20.0.0default-metric 100000 4000 200 45 4470autonomous-system 6redistribute connectedinterface POS0/1/0/0site-of-origin 201:1!!!!


Mon Nov 10 18:53:07.004 PST DST

-------------------------------------------------------------------------------show process policy_repository-------------------------------------------------------------------------------

Job Id: 312PID: 794895Executable path: /disk0/hfr-rout-3.8.0.20I/bin/policy_repositoryInstance #: 1Version ID: 00.00.0000Respawn: ONRespawn count: 2Max. spawns per minute: 12Last started: Tue Nov 4 02:56:20 2008Process state: Run (last exit status : 203)Package state: NormalStarted on config: cfg/gl/policy_lang/policies/core: MAINMEMMax. core: 0Level: 172Placement: ONstartup_path: /pkg/startup/pr.startupReady: 10.672sProcess cpu time: 0.198 user, 0.046 kernel, 0.244 totalJID TID Stack pri state TimeInState HR:MM:SS:MSEC NAME312 2 28K 10 Receive 156:58:40:0190 0:00:00:0240 policy_reposiy-------------------------------------------------------------------------------Mon Nov 10 18:53:07.633 PST DST% No such configuration item(s)

Mon Nov 10 18:53:08.002 PST DSTSysDB Verification Registrations:jid: nid: tid: handle: reg_path:00000312 0/RP0/CPU0 0002 00000606 '/cfg/gl/pim/.*/ipv4/b/rpf/topology'



OL-17332-01

00000312 0/RP1/CPU0 0002 00000597 '/cfg/gl/pim/.*/ipv4/b/rpf/topology'00000312 0/RP0/CPU0 0002 00000607 '/cfg/gl/pim/.*/ipv6/b/rpf/topology'00000312 0/RP1/CPU0 0002 00000598 '/cfg/gl/pim/.*/ipv6/b/rpf/topology'00000312 0/RP0/CPU0 0002 00000595 '/cfg/gl/rip/.*/.*/ord_t/if/.*/ord_t/policy'00000312 0/RP1/CPU0 0002 00000571 '/cfg/gl/rip/.*/.*/ord_t/if/.*/ord_t/policy'00000312 0/RP0/CPU0 0002 00000596 '/cfg/gl/rip/.*/.*/ord_t/if/.*/ord_t/policy'00000312 0/RP1/CPU0 0002 00000573 '/cfg/gl/rip/.*/.*/ord_t/if/.*/ord_t/policy'00000312 0/RP0/CPU0 0002 00000588 '/cfg/gl/rip/.*/.*/ord_t/redist/.*/.*'00000312 0/RP1/CPU0 0002 00000564 '/cfg/gl/rip/.*/.*/ord_t/redist/.*/.*'00000312 0/RP0/CPU0 0002 00000592 '/cfg/gl/rip/.*/.*/ord_t/policy-in'00000312 0/RP1/CPU0 0002 00000568 '/cfg/gl/rip/.*/.*/ord_t/policy-in'00000312 0/RP0/CPU0 0002 00000594 '/cfg/gl/rip/.*/.*/ord_t/policy-out'00000312 0/RP1/CPU0 0002 00000569 '/cfg/gl/rip/.*/.*/ord_t/policy-out'00000312 0/RP0/CPU0 0002 00000590 '/cfg/gl/rip/.*/.*/ord_t/defaultinformation'00000312 0/RP1/CPU0 0002 00000566 '/cfg/gl/rip/.*/.*/ord_t/defaultinformation'00000312 0/RP0/CPU0 0002 00000578 '/cfg/gl/rsi/vrf/.*/ord_z/afi_safi/.*/.*/de'00000312 0/RP1/CPU0 0002 00000553 '/cfg/gl/rsi/vrf/.*/ord_z/afi_safi/.*/.*/de'00000312 0/RP0/CPU0 0002 00000579 '/cfg/gl/rsi/vrf/.*/ord_z/afi_safi/.*/.*/de'00000312 0/RP1/CPU0 0002 00000555 '/cfg/gl/rsi/vrf/.*/ord_z/afi_safi/.*/.*/de'00000312 0/RP0/CPU0 0002 00000602 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000587 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000603 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000589 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000600 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000584 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000601 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000586 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000599 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000583 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000604 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000591 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000605 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP1/CPU0 0002 00000593 '/cfg/gl/eigrp/proc/.*/.*/.*/ord_m/af/.*/or'00000312 0/RP0/CPU0 0002 00000565 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000540 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000570 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000543 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000585 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000562 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000576 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000550 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000560 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000538 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000580 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000557 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000541 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000530 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000581 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000559 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000546 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP1/CPU0 0002 00000532 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP0/CPU0 0002 00000552 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP1/CPU0 0002 00000534 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP0/CPU0 0002 00000556 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP1/CPU0 0002 00000536 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP0/CPU0 0002 00000574 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP1/CPU0 0002 00000547 '/cfg/gl/ip-bgp/.*/.*/ord_a/.*/nbr/.*/edm/.'00000312 0/RP0/CPU0 0002 00000567 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000542 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000572 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000545 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000577 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000551 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000563 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'



OL-17332-01

00000312 0/RP1/CPU0 0002 00000539 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000544 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000531 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000582 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP1/CPU0 0002 00000561 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/gbl/edm/ord_'00000312 0/RP0/CPU0 0002 00000549 '/cfg/gl/ip-bgp/.*/.*/ord_b/.*/nbr/.*/edm/.'--More-

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support sanitized


OL-17332-01

show tech-support sanitizedTo automatically run show commands that display information specific to sanitized configuration output, use the show tech-support sanitized command in EXEC mode.

show tech-support sanitized {terminal [page] | file send-to [background] [compressed | uncompressed]} [location node-id | all]

Syntax Description

Command Modes EXEC






• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename









OL-17332-01

Command History



This command generates sanitized configuration output for debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.




Task ID

Examples The following example shows some of the show tech-support sanitized command output that is displayed on the terminal:

RP/0/RP0/CPU0:router# show tech-support sanitized terminal page

-------------------------------------------------------------------------------

show tech-support











Task ID Operations

basic-services read




OL-17332-01

-------------------------------------------------------------------------------

----------------------- show running-config (sanitized) -----------------------

Building configuration...!! Last configuration change at Wed Oct 10 20:05:13 2007 by <removed>!hostname <removed>line console exec-timeout 600 0 session-timeout 600!line default exec-timeout 600 0 session-timeout 600!clock timezone <removed> 8clock summer-time <removed> recurring 2 sunday march 02:00 first sunday novembe0logging console informationaltelnet vrf <removed> ipv4 server max-servers no-limitdomain ipv4 host <removed> 10.0.0.1domain ipv4 host <removed> 10.0.0.2domain ipv4 host <removed> 10.0.0.3domain ipv4 host <removed> 10.0.0.4domain ipv4 host <removed> 10.0.0.5domain ipv4 host <removed> 10.0.0.6domain ipv4 host <removed> 10.0.0.7domain ipv4 host <removed> 10.0.0.8domain ipv4 host <removed> 10.0.0.9domain ipv4 host <removed> 10.0.0.10domain ipv4 host <removed> 10.0.0.11domain ipv4 host <removed> 10.0.0.12domain ipv4 host <removed> 10.0.0.13domain ipv4 host <removed> 10.0.0.14domain lookup disableusername <removed> password 7 <removed>!aps group 1 revert 1 channel 0 local SONET0/1/4/3 channel 1 local SONET0/1/4/2!vty-pool default 0 25alias <removed> <removed>alias <removed> <removed>alias <removed> <removed>alias <removed> <removed>alias <removed> <removed>alias <removed> <removed>alias <removed> <removed>alias <removed> <removed>alias <removed> <removed>alias <removed> <removed>alias <removed> <removed>alias <removed> <removed>control-plane management-plane inband interface all allow all !



OL-17332-01

! !!ipv4 virtual address 10.0.0.14 255.0.0.0hw-module service sbc location 0/4/CPU0hw-module service sbc location 0/4/CPU1interface Bundle-Ether28 description <removed> ipv4 address 10.0.0.14 255.0.0.0 bundle minimum-active links 1 bundle minimum-active bandwidth 1000000!interface Bundle-Ether28.1 description <removed> ipv4 address 10.0.0.14 255.0.0.0 dot1q vlan 29!interface Bundle-Ether28.2 description <removed> ipv4 address 10.0.0.14 255.0.0.0 dot1q vlan 30!interface Bundle-Ether28.3 description <removed> ipv4 address 10.0.0.14 255.0.0.0 dot1q vlan 31!interface Bundle-POS24 description <removed> ipv4 address 10.0.0.14 255.0.0.0 bundle minimum-active links 1 bundle minimum-active bandwidth 2488320!interface Loopback0 ipv4 address 10.0.0.14 255.0.0.0!interface MgmtEth0/4/CPU0/0 description <removed> ipv4 address 10.0.0.14 255.0.0.0!interface MgmtEth0/4/CPU1/0 description <removed> ipv4 address 10.0.0.14 255.0.0.0!interface MgmtEth0/RP0/CPU0/0 description <removed> ipv4 address 10.0.0.14 255.0.0.0!interface MgmtEth0/RP1/CPU0/0 description <removed> ipv4 address 10.0.0.14 255.0.0.0!interface GigabitEthernet0/1/5/0 description <removed> ipv4 address 10.0.0.14 255.0.0.0!interface GigabitEthernet0/1/5/1 description <removed> ipv4 address 10.0.0.14 255.0.0.0!interface GigabitEthernet0/1/5/2 description <removed> ipv4 address 10.0.0.14 255.0.0.0!



OL-17332-01

interface GigabitEthernet0/1/5/3 shutdown!interface GigabitEthernet0/1/5/4 shutdown! interface GigabitEthernet0/1/5/5 shutdown!interface GigabitEthernet0/1/5/6 description <removed> bundle id 28 mode active!interface GigabitEthernet0/1/5/7 description <removed> bundle id 28 mode active!interface GigabitEthernet0/6/5/0 shutdown!interface GigabitEthernet0/6/5/1 description <removed> ipv4 address 10.0.0.14 255.0.0.0!interface GigabitEthernet0/6/5/2 description <removed> ipv4 address 10.0.0.14 255.0.0.0!interface GigabitEthernet0/6/5/3 shutdown!interface GigabitEthernet0/6/5/4 shutdown!interface GigabitEthernet0/6/5/5 shutdown!interface GigabitEthernet0/6/5/6 shutdown!interface GigabitEthernet0/6/5/7 description <removed> ipv4 address 10.0.0.14 255.0.0.0!interface POS0/1/0/0 shutdown!interface POS0/1/0/1 description <removed> ipv4 address 10.0.0.14 255.0.0.0!interface POS0/1/0/2 shutdown!interface POS0/1/0/3 shutdown!interface POS0/1/4/0 description <removed> bundle id 24 mode active!interface POS0/1/4/1 description <removed> bundle id 24 mode active



OL-17332-01

!interface POS0/1/4/2 description <removed> ipv4 address 10.0.0.14 255.0.0.0 encapsulation ppp ppp pap sent-username <removed> password encrypted <removed> ppp authentication chap pap ppp chap password encrypted <removed>!interface POS0/1/4/3 description <removed> ipv4 address 10.0.0.14 255.0.0.0 encapsulation ppp ppp pap sent-username <removed> password encrypted <removed> ppp authentication chap pap ppp chap password encrypted <removed>!interface POS0/6/0/0 description <removed> ipv4 address 10.0.0.14 255.0.0.0!interface POS0/6/0/1 description <removed> ipv4 address 10.0.0.14 255.0.0.0!interface POS0/6/0/2 shutdown!interface POS0/6/0/3 description <removed> ipv4 address 10.0.0.14 255.0.0.0!interface POS0/6/4/0

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support services


OL-17332-01

show tech-support servicesTo automatically run show commands that display information specific to tech-support information that relates to services, use the show tech-support services command in EXEC mode.

show tech-support services {diversion} {terminal [page] | file send-to [background] [compressed | uncompressed]} [location node-id | all]

Syntax Description

Command Modes EXEC

diversion Collects information about packet diversion.






• filename



• disk0:filename

• disk1:filename

• flash:filename

• ftp:filename



• nvram:filename

• rcp:filename

• slot0:filename

• slot1:filename

• tftp:filename









OL-17332-01

Command History



Use the show tech-support services command to run show commands that display information specific to the services diversion infrastructure, which is used with the service blade offerings for the Cisco IOS XR platforms. This command generates tech-support information that relates to services debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.




Task ID

Examples The following example shows some of the show tech-support services command output that is displayed on the terminal:

RP/0/RP0/CPU0:router# show tech-support services diversion terminal page

-------------------------------------------------------------------------------











Task ID Operations

cisco-support read




OL-17332-01

show tech-support service diversion

-------------------------------------------------------------------------------

-------------------------------------------------------------------------------

Global information

-------------------------------------------------------------------------------

-------------------------------- show platform --------------------------------Node Type PLIM State Config State-----------------------------------------------------------------------------0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/1/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON0/1/1 MSC(SPA) 4T3E3 OK PWR,NSHUT,MON0/1/4 MSC(SPA) 4XOC48-POS OK PWR,NSHUT,MON0/1/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON0/4/CPU0 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON0/4/CPU1 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON0/6/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/6/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON0/6/4 MSC(SPA) 8XOC3/OC12-POS OK PWR,NSHUT,MON0/6/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON

------------------------------- show redundancy -------------------------------Redundancy information for node 0/4/CPU0:==========================================Node 0/4/CPU0 is in ACTIVE roleNode 0/4/CPU0 has no valid partner

Reload and boot info----------------------DRP reloaded Thu Oct 11 19:23:45 2007: 6 days, 17 hours, 25 minutes agoActive node booted Thu Oct 11 19:23:45 2007: 6 days, 17 hours, 25 minutes ago

Redundancy information for node 0/4/CPU1:==========================================Node 0/4/CPU1 is in ACTIVE roleNode 0/4/CPU1 has no valid partner

Reload and boot info----------------------DRP reloaded Thu Oct 11 19:24:38 2007: 6 days, 17 hours, 25 minutes agoActive node booted Thu Oct 11 19:24:38 2007: 6 days, 17 hours, 25 minutes ago

Redundancy information for node 0/RP0/CPU0:==========================================Node 0/RP0/CPU0 is in ACTIVE rolePartner node (0/RP1/CPU0) is in STANDBY roleStandby node in 0/RP1/CPU0 is readyStandby node in 0/RP1/CPU0 is NSR-ready

Reload and boot info----------------------RP reloaded Thu Oct 11 19:18:01 2007: 6 days, 17 hours, 31 minutes agoActive node booted Thu Oct 11 19:18:01 2007: 6 days, 17 hours, 31 minutes agoStandby node boot Thu Oct 11 19:17:51 2007: 6 days, 17 hours, 31 minutes agoStandby node last went not ready Thu Oct 11 20:13:05 2007: 6 days, 16 hours, 36oStandby node last went ready Thu Oct 11 20:13:06 2007: 6 days, 16 hours, 36 minoStandby node last went not NSR-ready Thu Oct 11 19:29:45 2007: 6 days, 17 hourso



OL-17332-01

Standby node last went NSR-ready Thu Oct 11 19:29:45 2007: 6 days, 17 hours, 19oThere have been 0 switch-overs since reload

-------------------------- show context location all --------------------------

node: node0_1_CPU0------------------------------------------------------------------ node: node0_4_CPU0------------------------------------------------------------------

Crashed pid = 41000 (pkg/bin/dsc)Crashed tid = 5Crash time: Mon Oct 15, 2007: 04:54:16Core for process at harddisk:/dumper/dsc.node0_4_CPU0.ppc.Z

Stack Trace#0 0xfc1e6d90#1 0xfc1e6d88#2 0xfc1e53a0#3 0xfc1e826c#4 0xfc16b0c8#5 0xfc16a7e4#6 0xfc16a324#7 0xfc16e7a8#8 0xfc16ea08#9 0x48200e20 Registers info r0 r1 r2 r3 R0 00000000 4811bc50 48215204 00000000

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support spaipc


OL-17332-01

show tech-support spaipcTo automatically run show commands that display information specific to SPA Inter Process Communication (SPAIPC) debugging, use the show tech-support spaipc command in EXEC mode

show tech-support spaipc {terminal [page] | file send-to [background] [compressed | uncompressed]} [interface type interface-path-id] [show-only] [trace-only] [location node-id | all]

Syntax Description file Specifies that the command output is saved to a specified file.


• filename


• disk0:filename

• disk0a:filename

• disk1:filename

• disk1a:filename

• ftp:filename




• nvram:filename

• rcp:filename

• tftp:filename




interface (Optional) Collects information about a specific interface.





show-only (Optional) Collects only show command information.


trace-only (Optional) Collects only trace information.





OL-17332-01

Command Modes EXEC

Command History



This command generates SPAIPC debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.




















OL-17332-01

Task ID

Examples The following example shows some of the show tech-support spaipc command output that is displayed on the terminal:

RP/0/RP0/CPU0:router# show tech-support spaipc terminal page

-------------------------------------------------------------------------------

show tech-support spaipc

-------------------------------------------------------------------------------

----------------------------- show running-config -----------------------------Building configuration...!! Last configuration change at Wed Oct 10 20:05:13 2007 !hostname P1_CRS-8line console exec-timeout 600 0 session-timeout 600!line default exec-timeout 600 0 session-timeout 600!clock timezone PST 8clock summer-time DST recurring 2 sunday march 02:00 first sunday november 02:00logging console informationaltelnet vrf default ipv4 server max-servers no-limitdomain ipv4 host p1 172.29.52.72domain ipv4 host p2 172.29.52.77domain ipv4 host ce6 172.29.52.73domain ipv4 host ce7 172.29.52.78domain ipv4 host p11 172.29.52.83domain ipv4 host pe6 172.29.52.128domain ipv4 host pe7 172.29.52.182domain ipv4 host ce25 172.29.52.85domain ipv4 host ce28 172.29.52.1domain ipv4 host ce29 172.29.52.178domain ipv4 host pe21 172.29.52.163domain ipv4 host pe22 172.29.52.219domain ipv4 host ce28_nme 172.29.52.177domain ipv4 host ce29_nme 172.29.52.179domain lookup disableusername P2_CRS-8 password 7 13061E010803!aps group 1 revert 1 channel 0 local SONET0/1/4/3 channel 1 local SONET0/1/4/2!vty-pool default 0 25alias cr copy run disk0:/usr/P1_base_configalias sa show aliasalias sc show config commit listalias sd show diagalias si show ip int brief

Task ID Operations

cisco-support read



OL-17332-01

alias sl show ledalias sm show mpls forwardingalias sp show platformalias sr show runalias su show usersalias sv show versionalias sir show ip routecontrol-plane management-plane inband interface all allow all ! ! !! ipv4 virtual address 172.29.52.72 255.255.255.0hw-module service sbc location 0/4/CPU0hw-module service sbc location 0/4/CPU1interface Bundle-Ether28 description Connected to P2_CRS-8 Bundle-Ether 28 ipv4 address 10.12.28.1 255.255.255.0 bundle minimum-active links 1 bundle minimum-active bandwidth 1000000!interface Bundle-Ether28.1 description Connected to P2_CRS-8 Bundle-Ether 28.1 ipv4 address 10.12.29.1 255.255.255.0 dot1q vlan 29!interface Bundle-Ether28.2 description Connected to P2_CRS-8 Bundle-Ether 28.2 ipv4 address 10.12.30.1 255.255.255.0 dot1q vlan 30!interface Bundle-Ether28.3 description Connected to P2_CRS-8 Bundle-Ether 28.3 ipv4 address 10.12.31.1 255.255.255.0 dot1q vlan 31!interface Bundle-POS24 description Connected to P2_CRS-8 Bundle-POS 24 ipv4 address 10.12.24.1 255.255.255.0 bundle minimum-active links 1 bundle minimum-active bandwidth 2488320!interface Loopback0 ipv4 address 10.1.1.1 255.255.255.255!interface MgmtEth0/4/CPU0/0 description Connected to Lab LAN ipv4 address 172.29.52.46 255.255.255.0!interface MgmtEth0/4/CPU1/0 description Connected to Lab LAN ipv4 address 172.29.52.47 255.255.255.0!interface MgmtEth0/RP0/CPU0/0 description Connected to Lab LAN ipv4 address 172.29.52.70 255.255.255.0!interface MgmtEth0/RP1/CPU0/0 description Connected to Lab LAN ipv4 address 172.29.52.71 255.255.255.0



OL-17332-01

!interface GigabitEthernet0/1/5/0 description Connected to P2_CRS-8 GE 0/1/5/0 ipv4 address 10.12.16.1 255.255.255.0!interface GigabitEthernet0/1/5/1 description Connected to P4_C12810 GE 5/2 ipv4 address 10.14.8.1 255.255.255.0!interface GigabitEthernet0/1/5/2 description Connected to PE6_C12406 GE 0/4/0/1 ipv4 address 10.16.4.1 255.255.255.0!interface GigabitEthernet0/1/5/3 shutdown!interface GigabitEthernet0/1/5/4 shutdown!interface GigabitEthernet0/1/5/5

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support sysdb


OL-17332-01

show tech-support sysdbTo automatically run show commands that display information specific to the System Database (SysDB), use the show tech-support sysdb command in EXEC mode.

show tech-support sysdb {terminal [page] | file send-to [background] [compressed | uncompressed]} [shared-plane] [location node-id]

Syntax Description

Command Modes EXEC






• filename


• disk0:filename

• disk0a:filename

• disk1:filename

• disk1a:filename

• ftp:filename




• nvram:filename

• rcp:filename

• tftp:filename




shared-plane (Optional) Displays the data for the shared plane.





OL-17332-01

Command History



The SysDB is the memory database that is used to store configuration and statistical data with some IPC data. This command generates SysDB information that relates to debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.




Task ID

Examples The following example shows some of the show tech-support sysdb command output that is displayed on the terminal:

RP/0/RP0/CPU0:router# show tech-support sysdb terminal page

-------------------------------------------------------------------------------

show tech-support sysdb on location all

-------------------------------------------------------------------------------









Task ID Operations

cisco-support read




OL-17332-01

-------------------------------- show platform --------------------------------Node Type PLIM State Config State-----------------------------------------------------------------------------0/1/CPU0 L3 Service Eng N/A IOS XR RUN PWR,NSHUT,MON0/2/CPU0 L3LC Eng 5+ Jacket Card IOS XR RUN PWR,NSHUT,MON0/2/0 SPA SPA-4XOC3-POS-V READY PWR,NSHUT0/2/1 SPA SPA-IPSEC-2G-2 READY PWR,NSHUT0/4/CPU0 L3LC Eng 5+ Jacket Card IOS XR RUN PWR,NSHUT,MON0/4/0 SPA SPA-2X1GE-V2 READY PWR,NSHUT0/4/1 SPA SPA-8X1FE-TX-V2 READY PWR,NSHUT0/5/CPU0 PRP(Active) N/A IOS XR RUN PWR,NSHUT,MON

------------------------------- show redundancy -------------------------------Redundancy information for node 0/5/CPU0:==========================================Node 0/5/CPU0 is in ACTIVE roleNode 0/5/CPU0 has no valid partner

Reload and boot info----------------------PRP reloaded Thu Oct 11 03:17:26 2007: 1 week, 18 hours, 10 minutes agoActive node booted Thu Oct 11 03:17:26 2007: 1 week, 18 hours, 10 minutes ago

--------------------------- follow sysdb processes ----------------------------

Note that these commands will only run on the currently attached

node, regardless of location specified

These commands are run once now and once towards the end of the command. This is to avoid the delay between iterations of follow

------------------ follow process 94284 iteration 1 verbose ------------------- Attaching to process pid = 94284 (pkg/bin/sysdb_mc)No tid specified, following all threads

DLL Loaded by this process -------------------------------

DLL path Text addr. Text size Data addr. Data size Version/pkg/lib/libsysmgr.dll 0xfc133000 0x00013750 0xfc147000 0x0000066c 0/pkg/lib/libcerrno.dll 0xfc148000 0x00002f94 0xfc088eb0 0x00000128 0/pkg/lib/libcerr_dll_tbl.dll 0xfc14b000 0x00004bb0 0xfc0c5cc0 0x00000148 0/pkg/lib/libltrace.dll 0xfc150000 0x000095d8 0xfc14766c 0x00000328 0/pkg/lib/lib_platform_infra_ltrace.dll 0xfc15a000 0x00001044 0xfc0c5e08 0x000000/pkg/lib/libinfra.dll 0xfc15c000 0x000397b0 0xfc196000 0x00000cc0 0/pkg/lib/cerrno/libinfra_error.dll 0xfc1211dc 0x00000cd8 0xfc0c5e90 0x000000a8 0/pkg/lib/libios.dll 0xfc197000 0x0002d510 0xfc1c5000 0x00002000 0/pkg/lib/cerrno/libevent_manager_error.dll 0xfc130144 0x00000e88 0xfc0c5f38 0x00/pkg/lib/libss_common.dll 0xfc1c7000 0x000088f0 0xfc147994 0x00000274 0/pkg/lib/libc.dll 0xfc1d0000 0x0007b6e0 0xfc24c000 0x00002000 0/pkg/lib/lib_procfs_util.dll 0xfc252000 0x00004e8c 0xfc196cc0 0x000002a8 0/pkg/lib/libplatform.dll 0xfc25e000 0x0000e144 0xfc26d000 0x00002000 0/pkg/lib/libsyslog.dll 0xfc26f000 0x0000564c 0xfc25d258 0x00000328 0/pkg/lib/libdebug.dll 0xfc275000 0x00012764 0xfc25d580 0x00000630 0/pkg/lib/cerrno/libdebug_error.dll 0xfc26c144 0x00000db0 0xfc147e20 0x000000e8 0/pkg/lib/lib_mbus_api.dll 0xfc288000 0x00014670 0xfc29d000 0x00002000 0/pkg/lib/libc12000_device_info.dll 0xfc2be000 0x00002c40 0xfc147f70 0x00000068 0/pkg/lib/libnodeid.dll 0xfc2c2000 0x00008204 0xfc25dbb0 0x000001e0 0/pkg/lib/libshmwin.dll 0xfc474000 0x00013c1c 0xfc488000 0x00000834 0



OL-17332-01

/pkg/lib/cerrno/libshmwin_error.dll 0xfc489000 0x000013e0 0xfc3bef44 0x000000880/pkg/lib/libgroup.dll 0xfc629000 0x00018fd4 0xfc642000 0x00000508 0/pkg/lib/libsysdb.dll 0xfc643000 0x00050b00 0xfc694000 0x00000b74 0/pkg/lib/libgsputils.dll 0xfc6ba000 0x0000aaa8 0xfc6c5000 0x000007e8 0/pkg/lib/cerrno/libsysmgr_error.dll 0xfc5ca058 0x00000f94 0xfc5b3ecc 0x000000880/pkg/lib/libsysdbutils.dll 0xfc6db000 0x0000d378 0xfc694b74 0x0000046c 0/pkg/lib/cerrno/libsysdb_error_v1v2.dll 0xfc6eb000 0x00001e08 0xfc613d1c 0x00000/pkg/lib/cerrno/libsysdb_error_v2only.dll 0xfc6f5000 0x00002848 0xfc613da4 0x000/pkg/lib/cerrno/libsysdb_error_callback.dll 0xfc6fb000 0x0000168c 0xfc613f14 0x0/pkg/lib/cerrno/libsysdb_error_distrib.dll 0xfc6fd000 0x0000183c 0xfc6c5c04 0x00/pkg/lib/libltrace_shmem.dll 0xfc728000 0x00003714 0xfc6daae0 0x00000168 0/pkg/lib/libens.dll 0xfc824000 0x0000f304 0xfc834000 0x00002000 0/pkg/lib/libsysdbsvr_common.dll 0xfca28000 0x0000622c 0xfc9a95b0 0x00000288 0/pkg/lib/libnrsutils.dll 0xfca53000 0x00004254 0xfca3ed64 0x000000e8 0/pkg/lib/libnrs.dll 0xfcaf4000 0x00007fd4 0xfcaed958 0x00000628 0/pkg/lib/cerrno/libnrs_error.dll 0xfcb39000 0x000015ec 0xfca8aebc 0x00000068 0/pkg/lib/libasync.dll 0xfcb74000 0x0000cb10 0xfcb81000 0x00000b74 0/pkg/lib/cerrno/libasync_error.dll 0xfca52010 0x00000ed8 0xfcb36f50 0x00000088 0/pkg/lib/libport_un.dll 0xfd165000 0x00001678 0xfd0d0b30 0x00000068 0/pkg/lib/libatc_cache.dll 0xfd243000 0x000063b4 0xfd242108 0x00000294 0

Iteration 1 of 1------------------------------

Current process = "pkg/bin/sysdb_mc", PID = 94284 TID = 1 (main)registers_info: r0 r1 r2 r3registers_info: R0 00000020 481ffad0 4823b6c0 481ffb38 registers_info: r4 r5 r6 r7registers_info: R4 00000000 0000000c 00000000 fc24c618 registers_info: r8 r9 r10 r11registers_info: R8 fc250000 fc250000 481fffc0 00000000 registers_info: r12 r13 r14 r15registers_info: R12 48231ee8 4823b510 481ffbb0 00000002 registers_info: r16 r17 r18 r19registers_info: R16 481ffbc4 00000001 00000000 00000000 registers_info: r20 r21 r22 r23registers_info: R20 00000001 481ffb38 00000001 48230000 registers_info: r24 r25 r26 r27registers_info: R24 48220000 24000024 48238e60 00000000 registers_info: r28 r29 r30 r31registers_info: R28 00000001 481ffaf8 48230000 00000000

Tech-Support Commands on Cisco IOS XR Softwareshow tech-support terminal


OL-17332-01

show tech-support terminalTo automatically run show commands that display information specific to the terminal, use the show tech-support terminal command in EXEC mode.

show tech-support terminal [location {node-id | all} | page]

Syntax Description

Command Modes EXEC

Command History




















OL-17332-01

This command generates terminal information that relates to debugging information that can be useful for Cisco Technical Support representatives when troubleshooting a router. See “Obtaining Documentation and Submitting a Service Request” section on page iii in the Preface for Cisco Technical Support contact information.




Task ID

Examples The following example shows some of the show tech-support terminal command output:

RP/0/RP0/CPU0:router# show tech-support terminal page

-------------------------------------------------------------------------------

show tech-support

-------------------------------------------------------------------------------

---------------------- show running-config (no password) ----------------------

Building configuration...!! Last configuration change at Wed Oct 10 20:05:13 2007!hostname P1_CRS-8line console exec-timeout 600 0 session-timeout 600!line default exec-timeout 600 0 session-timeout 600!clock timezone PST 8clock summer-time DST recurring 2 sunday march 02:00 first sunday november 02:00logging console informationaltelnet vrf default ipv4 server max-servers no-limitdomain ipv4 host p1 172.29.52.72domain ipv4 host p2 172.29.52.77domain ipv4 host ce6 172.29.52.73domain ipv4 host ce7 172.29.52.78domain ipv4 host p11 172.29.52.83domain ipv4 host pe6 172.29.52.128domain ipv4 host pe7 172.29.52.182domain ipv4 host ce25 172.29.52.85domain ipv4 host ce28 172.29.52.1domain ipv4 host ce29 172.29.52.178domain ipv4 host pe21 172.29.52.163domain ipv4 host pe22 172.29.52.219

Task ID Operations

basic-services read




OL-17332-01

domain ipv4 host ce28_nme 172.29.52.177domain ipv4 host ce29_nme 172.29.52.179domain lookup disableusername P2_CRS-8 password 7 <removed>!aps group 1 revert 1 channel 0 local SONET0/1/4/3 channel 1 local SONET0/1/4/2!vty-pool default 0 25alias cr copy run disk0:/usr/P1_base_configalias sa show aliasalias sc show config commit listalias sd show diagalias si show ip int briefalias sl show ledalias sm show mpls forwardingalias sp show platformalias sr show runalias su show usersalias sv show versionalias sir show ip routecontrol-plane management-plane inband interface all allow all ! ! !!ipv4 virtual address 172.29.52.72 255.255.255.0hw-module service sbc location 0/4/CPU0hw-module service sbc location 0/4/CPU1interface Bundle-Ether28 description Connected to P2_CRS-8 Bundle-Ether 28 ipv4 address 10.12.28.1 255.255.255.0 bundle minimum-active links 1 bundle minimum-active bandwidth 1000000!interface Bundle-Ether28.1 description Connected to P2_CRS-8 Bundle-Ether 28.1 ipv4 address 10.12.29.1 255.255.255.0 dot1q vlan 29!interface Bundle-Ether28.2 description Connected to P2_CRS-8 Bundle-Ether 28.2 ipv4 address 10.12.30.1 255.255.255.0 dot1q vlan 30!interface Bundle-Ether28.3 description Connected to P2_CRS-8 Bundle-Ether 28.3 ipv4 address 10.12.31.1 255.255.255.0 dot1q vlan 31!interface Bundle-POS24 description Connected to P2_CRS-8 Bundle-POS 24 ipv4 address 10.12.24.1 255.255.255.0 bundle minimum-active links 1 bundle minimum-active bandwidth 2488320!interface Loopback0



OL-17332-01

ipv4 address 10.1.1.1 255.255.255.255!interface MgmtEth0/4/CPU0/0 description Connected to Lab LAN ipv4 address 172.29.52.46 255.255.255.0!interface MgmtEth0/4/CPU1/0 description Connected to Lab LAN ipv4 address 172.29.52.47 255.255.255.0!interface MgmtEth0/RP0/CPU0/0 description Connected to Lab LAN ipv4 address 172.29.52.70 255.255.255.0!interface MgmtEth0/RP1/CPU0/0 description Connected to Lab LAN ipv4 address 172.29.52.71 255.255.255.0!interface GigabitEthernet0/1/5/0 description Connected to P2_CRS-8 GE 0/1/5/0 ipv4 address 10.12.16.1 255.255.255.0!interface GigabitEthernet0/1/5/1 description Connected to P4_C12810 GE 5/2 ipv4 address 10.14.8.1 255.255.255.0!interface GigabitEthernet0/1/5/2 description Connected to PE6_C12406 GE 0/4/0/1 ipv4 address 10.16.4.1 255.255.255.0!interface GigabitEthernet0/1/5/3 shutdown!interface GigabitEthernet0/1/5/4 shutdown! interface GigabitEthernet0/1/5/5 shutdown!interface GigabitEthernet0/1/5/6 description Connected to P2_CRS-8 GE 0/1/5/6 bundle id 28 mode active!interface GigabitEthernet0/1/5/7 description Connected to P2_CRS-8 GE 0/1/5/7 bundle id 28 mode active!interface GigabitEthernet0/6/5/0 shutdown!interface GigabitEthernet0/6/5/1 description Connected to P2_CRS-8 GE 0/6/5/1 ipv4 address 10.12.20.1 255.255.255.0!interface GigabitEthernet0/6/5/2 description Connected to PE6_C12406 GE 0/4/0/2 ipv4 address 10.16.8.1 255.255.255.0!interface GigabitEthernet0/6/5/3 shutdown!interface GigabitEthernet0/6/5/4 shutdown!



OL-17332-01

interface GigabitEthernet0/6/5/5 shutdown!interface GigabitEthernet0/6/5/6 shutdown!interface GigabitEthernet0/6/5/7 description Connected to P2_CRS-8 GE 0/6/5/7 ipv4 address 10.12.40.1 255.255.255.0!interface POS0/1/0/0 shutdown!interface POS0/1/0/1 description Connected to P2_CRS-8 POS 0/1/0/1 ipv4 address 10.12.8.1 255.255.255.0!interface POS0/1/0/2 shutdown!interface POS0/1/0/3 shutdown!interface POS0/1/4/0 description Connected to P2_CRS-8 POS 0/1/4/0 bundle id 24 mode active!interface POS0/1/4/1 description Connected to P2_CRS-8 POS 0/1/4/1 bundle id 24 mode active!interface POS0/1/4/2 description Connected to P2_CRS-8 POS 0/1/4/2 ipv4 address 10.12.32.1 255.255.255.0 encapsulation ppp ppp pap sent-username P1_CRS-8 password encrypted <removed> ppp authentication chap pap ppp chap password encrypted <removed>!interface POS0/1/4/3



OL-17332-01


OL-17332-01

Watchdog Commands on Cisco IOS XR Software

This module describes commands used to monitor the memory states and thresholds of routers running Cisco IOS XR software.

Watchdog Commands on Cisco IOS XR Softwareshow critmon context


OL-17332-01

show critmon contextTo display information about the context for the wd-critical-mon process, use the show critmon context command in EXEC mode and in administration EXEC mode.

show critmon context {all | deadline [client client name] | ticker | watcher} {location {node-id | all}}

Syntax Description


Command Modes EXEC

Administration EXEC

Command History


Use the show critmon context command to display information about the context for the wd-critical-mon process.

all Displays all context information for the wd-critical-mon process.

deadline Displays the context information for the deadline monitoring client application.

client (Optional) Displays information only for the specified client.

client name Name of the client.

ticker Displays information for the ticker context for the wd-critical-mon process.

watcher Displays information for the watcher context for the wd-critical-mon process.

location Specifies a node to filter.

node-id Node ID. The node-id argument is entered in the rack/slot/module notation.

all Specifies all locations.







OL-17332-01

Task ID

Examples The following sample output is from the show critmon context command:

RP/0/RP0/CPU0:router# show critmon context all location all

------------------------------------------------------------------------------Ticker context info (Node: 0/5/CPU0)------------------------------------------------------------------------------ CPU# : 0 Ticker counter : 2245 Ticker last ran timestamp : 02/10/2008 01:11:10

------------------------------------------------------------------------------Watcher context info (Node: 0/5/CPU0)------------------------------------------------------------------------------ Watcher counter : 751 Watcher last ran : 02/10/2008 01:11:10

------------------------------------------------------------------------------Deadline monitoring context info (Node: 0/5/CPU0)------------------------------------------------------------------------------ Client : wdsysmon PunchTimestamp : 02/10/2008 01:11:09 PunchCounter : 226




------------------------------------------------------------------------------Ticker context info (Node: 0/2/CPU0)------------------------------------------------------------------------------ CPU# : 0

Task ID Operations

cisco-support read



OL-17332-01

Ticker counter : 61 Ticker last ran timestamp : 02/10/2008 01:11:10







Table 46 show critmon context Field Descriptions

Field Description

Ticker context info wd-critical-mon process ticker context information for the node.

CPU CPU number.

Ticker counter Current counter for the wd-critical-mon ticker thread. The ticker counter field specifies the number of times the ticker thread was run.

Ticker last ran timestamp Timestamp for the last time the wd-critical-mon ticker thread was run.



OL-17332-01

Related Commands

Watcher context info wd-critical-mon watcher thread context information that is used for the node.

Watcher counter Current counter for the wd-critical-mon watcher thread. The watcher counter field specifies the number of times the watcher thread was run

Watcher last ran Timestamp that is used for the last run of the wd-critical-mon watcher thread.

Deadline monitoring context info wd-critical-mon deadline montoring information that is used for the node.

Client Client name for deadline monitoring.

PunchTimestamp Timestamp that is used for the last run of the client application.

PunchCounter Current counter for the deadline monitoring client. This field specifies the number of times that the client application can punch the counter.

Table 46 show critmon context Field Descriptions (continued)

Field Description

Command Description

show critmon deadline Displays information about the deadline for monitoring.

show critmon statistics Displays information about critical statistics.

show critmon trace all Displays information about all traces for a critical monitor.

show critmon trace error

Displays information about error traces for a critical monitor.

show critmon trace info

Displays trace data for an information type for the critical monitor.

show critmon trace lib-error

Displays information about the trace data for the library error for the critical monitor.

show critmon trace lib-info

Displays trace data for the library information for the critical monitor.

Watchdog Commands on Cisco IOS XR Softwareshow critmon deadline


OL-17332-01

show critmon deadlineTo display information about deadline monitoring, use the show critmon deadline command in EXEC mode and in administration EXEC mode

show critmon deadline {registration} [client client name] {location {node-id | all}}

Syntax Description


Command Modes EXEC

Administration EXEC

Command History


Use the show critmon deadline command to display information about the deadline monitoring.

Task ID

Examples The following sample output is from the show critmon deadline command:

RP/0/RP0/CPU0:router# show critmon deadline registration location all

registration Displays the deadline monitoring registration information.

client (Optional) Displays information only for the specified client.









Task ID Operations

cisco-support read



OL-17332-01

------------------------------------------------------------------------------Deadline monitoring registration info (Node: 0/5/CPU0)------------------------------------------------------------------------------ ID ClientName Activated tick address timeout vale(sec) -- ------------------------ --------- ------------ ---------------- 0 wdsysmon Yes 0x6023d000 60

------------------------------------------------------------------------------Deadline monitoring registration info (Node: 0/4/CPU0)------------------------------------------------------------------------------ ID ClientName Activated tick address timeout vale(sec) -- ------------------------ --------- ------------ ---------------- 0 wdsysmon Yes 0x38146000 60




Table 47 show critmon deadline Field Descriptions

Field Description

Deadline monitoring registration info Deadline monitoring registration information that is used for the node.

ID Client ID that is internally managed by the wd-critical-mon process.

ClientName Name of the client.

Activated Field specifies that deadline monitoring is activated or not.

tick address Tick memory address for the client application.

timeout vale(sec) Deadline timeout value.



OL-17332-01


show critmon context Displays information about the context for the critical monitor.











Watchdog Commands on Cisco IOS XR Softwareshow critmon statistics


OL-17332-01

show critmon statisticsTo display information about the critical monitor statistics, use the show critmon statistics command in EXEC mode and in administration EXEC mode.

show critmon statistics {all | congestion | deadline {client client name} | ticker | watcher} {last hours} {location {node-id | all}}

Syntax Description


Command Modes EXEC

Administration EXEC

Command History


Use the show critmon statistics command to display information about the critical monitor statistics.

all Displays all the information for the critical monitor.

congestion Displays all the CPU congestion information for the critical monitor.

deadline Displays all the statistics information for the deadline monitor.

client Displays information only for the specified client.


ticker Displays the ticker statistics for the wd-critical-mon process.

watcher Displays the watcher statistics for the wd-critical-mon process.

last Displays only the last number of hours.

hours Number of last hours. The range is from 1 to 24.










OL-17332-01

Task ID

Examples The following sample output is from the show critmon statistics command:

RP/0/RP0/CPU0:router# show critmon statistics all last 5 location all

------------------------------------------------------------------------------Ticker statistics info (Node: 0/5/CPU0)------------------------------------------------------------------------------ Period SnapShotTimestamp Frequency (min) CPU# MM/DD/YYYY hh:mm:ss tick count (count/min) ------ ------ ------------------- ---------- ------------ 15 cpu:0 10/22/2007 14:33:39 4478 298 15 cpu:0 10/22/2007 14:48:39 4477 298 15 cpu:0 10/22/2007 15:03:39 4478 298 15 cpu:0 10/22/2007 15:18:39 4477 298 15 cpu:0 10/22/2007 15:33:39 4478 298 15 cpu:0 10/22/2007 15:48:39 4478 298 15 cpu:0 10/22/2007 16:03:39 4477 298 15 cpu:0 10/22/2007 16:18:39 4478 298 15 cpu:0 10/22/2007 16:33:39 4477 298 15 cpu:0 10/22/2007 16:48:39 4478 298 15 cpu:0 10/22/2007 17:03:39 4477 298 15 cpu:0 10/22/2007 17:18:39 4478 298 15 cpu:0 10/22/2007 17:33:39 4477 298 15 cpu:0 10/22/2007 17:48:39 4478 298 15 cpu:0 10/22/2007 18:03:39 4477 298 15 cpu:0 10/22/2007 18:18:39 4478 298 15 cpu:0 10/22/2007 18:33:39 4478 298 15 cpu:0 10/22/2007 18:48:39 4477 298 15 cpu:0 10/22/2007 19:03:39 4477 298 15 cpu:0 10/22/2007 19:18:39 4478 298

------------------------------------------------------------------------------Watcher statistics info (Node: 0/5/CPU0)------------------------------------------------------------------------------ Period SnapShotTimestamp Frequency (min) MM/DD/YYYY hh:mm:ss watch count (count/min) ------ ------------------- ----------- ------------ 15 10/22/2007 14:33:39 1498 99 15 10/22/2007 14:48:39 1497 99 15 10/22/2007 15:03:39 1498 99 15 10/22/2007 15:18:39 1497 99 15 10/22/2007 15:33:39 1498 99 15 10/22/2007 15:48:39 1497 99 15 10/22/2007 16:03:39 1498 99 15 10/22/2007 16:18:39 1497 99 15 10/22/2007 16:33:39 1498 99 15 10/22/2007 16:48:39 1497 99 15 10/22/2007 17:03:39 1498 99 15 10/22/2007 17:18:39 1497 99 15 10/22/2007 17:33:39 1498 99 15 10/22/2007 17:48:39 1497 99 15 10/22/2007 18:03:39 1498 99 15 10/22/2007 18:18:39 1497 99 15 10/22/2007 18:33:39 1498 99 15 10/22/2007 18:48:39 1497 99 15 10/22/2007 19:03:39 1498 99 15 10/22/2007 19:18:39 1497 99

Task ID Operations

cisco-support read



OL-17332-01

------------------------------------------------------------------------------CPU congestion history (Node: 0/5/CPU0)------------------------------------------------------------------------------

No congestion history

------------------------------------------------------------------------------Deadline monitoring statistics info (Node: 0/5/CPU0)------------------------------------------------------------------------------ client SnapShotTimestamp Frequency (name) MM/DD/YYYY hh:mm:ss tick count (count/min) ------------------------ ------------------- ---------- ------------ wdsysmon 10/22/2007 14:33:39 450 30 wdsysmon 10/22/2007 14:48:39 450 30 wdsysmon 10/22/2007 15:03:39 450 30 wdsysmon 10/22/2007 15:18:39 449 29 wdsysmon 10/22/2007 15:33:39 450 30 wdsysmon 10/22/2007 15:48:39 450 30 wdsysmon 10/22/2007 16:03:39 450 30 wdsysmon 10/22/2007 16:18:39 449 29 wdsysmon 10/22/2007 16:33:39 450 30 wdsysmon 10/22/2007 16:48:39 450 30 wdsysmon 10/22/2007 17:03:39 450 30 wdsysmon 10/22/2007 17:18:39 450 30 wdsysmon 10/22/2007 17:33:39 449 29 wdsysmon 10/22/2007 17:48:39 450 30 wdsysmon 10/22/2007 18:03:39 450 30 wdsysmon 10/22/2007 18:18:39 450 30 wdsysmon 10/22/2007 18:33:39 449 29 wdsysmon 10/22/2007 18:48:39 450 30 wdsysmon 10/22/2007 19:03:39 450 30 wdsysmon 10/22/2007 19:18:39 450 30




OL-17332-01







OL-17332-01





------------------------------------------------------------------------------



OL-17332-01

Deadline monitoring statistics info (Node: 0/2/CPU0)------------------------------------------------------------------------------ client SnapShotTimestamp Frequency (name) MM/DD/YYYY hh:mm:ss tick count (count/min) ------------------------ ------------------- ---------- ------------ wdsysmon 10/22/2007 14:25:41 449 29 wdsysmon 10/22/2007 14:40:41 450 30 wdsysmon 10/22/2007 14:55:41 449 29 wdsysmon 10/22/2007 15:10:41 450 30 wdsysmon 10/22/2007 15:25:41 449 29 wdsysmon 10/22/2007 15:40:41 450 30 wdsysmon 10/22/2007 15:55:41 449 29 wdsysmon 10/22/2007 16:10:41 450 30 wdsysmon 10/22/2007 16:25:41 449 29 wdsysmon 10/22/2007 16:40:41 450 30 wdsysmon 10/22/2007 16:55:40 449 29 wdsysmon 10/22/2007 17:10:40 450 30 wdsysmon 10/22/2007 17:25:40 449 29 wdsysmon 10/22/2007 17:40:40 450 30 wdsysmon 10/22/2007 17:55:40 449 29 wdsysmon 10/22/2007 18:10:40 450 30 wdsysmon 10/22/2007 18:25:40 449 29 wdsysmon 10/22/2007 18:40:40 450 30 wdsysmon 10/22/2007 18:55:40 449 29 wdsysmon 10/22/2007 19:10:40 450 30


------------------------------------------------------------------------------Watcher statistics info (Node: 0/1/CPU0)------------------------------------------------------------------------------ Period SnapShotTimestamp Frequency (min) MM/DD/YYYY hh:mm:ss watch count (count/min) ------ ------------------- ----------- ------------ 15 10/22/2007 14:33:53 1495 99 15 10/22/2007 14:48:53 1495 99 15 10/22/2007 15:03:53 1495 99



OL-17332-01

15 10/22/2007 15:18:53 1495 99 15 10/22/2007 15:33:53 1495 99 15 10/22/2007 15:48:53 1495 99 15 10/22/2007 16:03:53 1495 99 15 10/22/2007 16:18:52 1495 99 15 10/22/2007 16:33:52 1496 99 15 10/22/2007 16:48:52 1495 99 15 10/22/2007 17:03:52 1495 99 15 10/22/2007 17:18:52 1495 99 15 10/22/2007 17:33:52 1495 99 15 10/22/2007 17:48:52 1495 99 15 10/22/2007 18:03:52 1495 99 15 10/22/2007 18:18:52 1495 99 15 10/22/2007 18:33:52 1495 99 15 10/22/2007 18:48:52 1495 99 15 10/22/2007 19:03:52 1495 99 15 10/22/2007 19:18:52 1495 99





Table 48 show critmon statistics Field Descriptions

Field Description

Ticker statistics info Ticker thread statistics information that is used for the node.

Period Statistics sampling period.



OL-17332-01

Related Commands

CPU CPU number.

SnapShotTimestamp Timestamp that the statistics is saved.

tick count Ticker counter for the sampling period

Frequency Frequency for ticker or watcher punch count.

Watcher statistics info Watcher thread statistics information that is used for the node.

watch count Watcher count that is used for the sampling period.

CPU congestion history History of CPU congestion.

Deadline monitoring statistics info Deadline monitoring statistics information that is used for the node.

client Name of deadline monitoring client.

Table 48 show critmon statistics Field Descriptions (continued)

Field Description

Command Description












Watchdog Commands on Cisco IOS XR Softwareshow critmon trace all


OL-17332-01

show critmon trace allTo display information about all traces for a critical monitor, use the show critmon trace all command in EXEC mode and in administration EXEC mode.

show critmon trace all [file filename {original}] [hexdump] [last entries] [reverse] [stats] [tailf] [unique] [verbose] [wrapping] [location {node-id | all}]

Syntax Description


Command Modes EXEC

Administration EXEC

Command History

file (Optional) Displays a specific file.

filename Name of a specific file.

original Specifies the original location of the file.

hexdump (Optional) Displays traces in hexadecimal format.

last (Optional) Displays trace information for a specific number of entries

entries Number of entries. Replace entries with the number of entries you want to display. For example, if you enter 5, the display shows the last 5 entries in the trace data. The range is from 1 to 4294967295.

reverse (Optional) Displays the latest traces first.

stats (Optional) Displays the statistics in the command output.

tailf (Optional) Displays the new traces as they are added in the command output.

unique (Optional) Displays the unique entries with counts in the command output.

verbose (Optional) Displays the information for internal debugging in the command output.

wrapping (Optional) Displays the wrapping entries in the command output.








Watchdog Commands on Cisco IOS XR Softwareshow critmon trace all


OL-17332-01


Task ID

Examples The following sample output is from the show critmon trace all command:

RP/0/RP0/CPU0:router# show critmon trace all hexdump

1 wrapping entries (768 possible, 0 filtered, 1 total)Oct 11 03:18:11.584 wd-critical-mon/lib/info 0/5/CPU0 t10 tp0x00000302000000a0

Oct 11 03:18:11.584 wd-critical-mon/lib/info 0/5/CPU0 t10 critmon_deadline_regin

Related Commands

Task ID Operations

cisco-support read

Command Description












Watchdog Commands on Cisco IOS XR Softwareshow critmon trace error


OL-17332-01

show critmon trace errorTo display information about error traces for a critical monitor, use the show critmon trace error command in EXEC mode and in administration EXEC mode.

show critmon trace error [file filename {original}] [hexdump] [last entries] [reverse] [stats] [tailf] [unique] [verbose] [wrapping] [location {node-id | all}]

Syntax Description


Command Modes EXEC

Administration EXEC

Command History






last (Optional) Displays the last numbered entries.

entries Number of entries. The range is from 1 to 4294967295.


stats (Optional) Displays the statistics.

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

unique (Optional) Displays the unique entries with counts.

verbose (Optional) Displays the information for internal debugging.









Watchdog Commands on Cisco IOS XR Softwareshow critmon trace error


OL-17332-01

Task ID

Examples The following example shows how to use the show critmon trace error command:

RP/0/RP0/CPU0:router# show critmon trace error

Related Commands

Task ID Operations

cisco-support read

Command Description











Watchdog Commands on Cisco IOS XR Softwareshow critmon trace info


OL-17332-01

show critmon trace infoTo display trace data for an information type for the critical monitor, use the show critmon trace info command in EXEC mode and in administration EXEC mode.

show critmon trace info [file filename {original}] [hexdump] [last entries] [reverse] [stats] [tailf] [unique] [verbose] [wrapping] [location {node-id | all}]

Syntax Description


Command Modes EXEC

Administration EXEC

Command History





















Watchdog Commands on Cisco IOS XR Softwareshow critmon trace info


OL-17332-01

Task ID

Examples The following shows how to use the show critmon trace info command:

RP/0/RP0/CPU0:router# show critmon trace info

Related Commands

Task ID Operations

cisco-support read

Command Description











Watchdog Commands on Cisco IOS XR Softwareshow critmon trace lib-error


OL-17332-01

show critmon trace lib-errorTo display information about the trace data for the library error for the critical monitor, use the show critmon trace lib-error command in EXEC mode and in administration EXEC mode.

show critmon trace lib-error [file filename {original}] [hexdump] [last entries] [reverse] [stats] [tailf] [unique] [verbose] [wrapping] [location {node-id | all}]

Syntax Description


Command Modes EXEC

Administration EXEC

Command History





















Watchdog Commands on Cisco IOS XR Softwareshow critmon trace lib-error


OL-17332-01

Task ID

Examples The following shows how to use the show critmon trace lib-error command:

RP/0/RP0/CPU0:router# show critmon trace lib-error

Related Commands

Task ID Operations

cisco-support read

Command Description











Watchdog Commands on Cisco IOS XR Softwareshow critmon trace lib-info


OL-17332-01

show critmon trace lib-infoTo display trace data for the library information for the critical monitor, use the show critmon trace lib-info command in EXEC mode and in administration EXEC mode.

show critmon trace lib-info [file filename {original}] [hexdump] [last entries] [reverse] [stats] [tailf] [unique] [verbose] [wrapping] [location {node-id | all}]

Syntax Description


Command Modes EXEC

Administration EXEC

Command History





















Watchdog Commands on Cisco IOS XR Softwareshow critmon trace lib-info


OL-17332-01

Task ID

Examples The following example shows how to use the show critmon trace lib-info command:

RP/0/RP0/CPU0:router# show critmon trace lib-info

Related Commands

Task ID Operations

cisco-support read

Command Description











Watchdog Commands on Cisco IOS XR Softwareshow reboot first


OL-17332-01

show reboot firstTo display reboot information for a node first, use the show reboot first command in EXEC mode.

show reboot first {crashinfo | syslog | trace} {location node-id}

Syntax Description

Command Modes EXEC

Command History


Task ID

Examples The following sample output is from the show reboot first command:

RP/0/RP0/CPU0:router# show reboot first

crashinfo Displays crash information.

syslog Displays information for the system logs.

trace Displays the log for the reboot trace.

location Specifies a node.






Task ID Operations

system read

Watchdog Commands on Cisco IOS XR Softwareshow reboot first


OL-17332-01


show reboot graceful Displays reboot information for the last graceful reboot for a node.

show reboot history Displays reboot information for the last graceful reboot.

show reboot last Displays the latest crash information.

show reboot pcds Displays Persistent Critical Data Store (PCDS) critical information for the last ungraceful reboot.

Watchdog Commands on Cisco IOS XR Softwareshow reboot graceful


OL-17332-01

show reboot gracefulTo display reboot information for the last graceful reboot for a node, use the show reboot graceful command in EXEC mode.

show reboot graceful {location node-id}

Syntax Description

Command Modes EXEC

Command History


Task ID

Examples The following sample output is from the show reboot graceful command:

RP/0/RP0/CPU0:router# show reboot graceful location 0/1/CPU0

Reboot Time : Thu Oct 11 19:15:55 2007Reboot Cause : 0x4fReboot Reason: Cause: HBAgent reloading node on receiving reload notification 0Trace log :

[0x46ad85b7b5] Map ingressq PCI base address.ingressq_phy_base = 0xa0000000, in0[0x46ad8af9ba] Perform Node isolation from Fabric. ingressq_phy_base = 0xa000008[0x46ad8afe88] Complete Kernel dumper platform task without dumping. rc: 0







Task ID Operations

system read

Watchdog Commands on Cisco IOS XR Softwareshow reboot graceful


OL-17332-01


show reboot first Displays reboot information for a node first.




Watchdog Commands on Cisco IOS XR Softwareshow reboot history


OL-17332-01

show reboot historyTo display reboot information for the last graceful reboot, use the show reboot history command in EXEC mode.

show reboot history [reverse] {location node-id}

Syntax Description

Command Modes EXEC

Command History


The reboot history shows all reboot causes that is stored for the previous node resets.

Task ID

Examples The following sample output is from the show reboot history command:

RP/0/RP0/CPU0:router# show reboot history location 0/1/CPU0

No Time Cause Code Reason--------------------------------------------------------------------------------01 Mon Jul 30 19:27:05 2007 0x2000004f Cause: MBI-HELLO reloading node on rec eiving reload notification Process: mbi-hello Traceback: fc15b1a0 fc15b290 482 0020c fc1d5fb0 0 002 Thu Aug 16 16:32:35 2007 0x21000106 Cause: All fabric links down on Fabric q Process: fabricq_mgr

reverse (Optional) Displays the reverse in chronological order.







Task ID Operations

system read

Watchdog Commands on Cisco IOS XR Softwareshow reboot history


OL-17332-01

Traceback: fc15b1a0 fc15b290 fc9 9ded4 fc99ae00 fc99affc fc99affc03 Thu Aug 16 17:05:20 2007 0x2000004f Cause: MBI-HELLO reloading node on rec eiving reload notification Process: mbi-hello Traceback: fc15b1a0 fc15b290 482 0020c fc1d5fb0 0 004 Mon Sep 10 21:01:34 2007 0x21000106 Cause: All fabric links down on Fabric q Process: fabricq_mgr Traceback: fc15b1a0 fc15b290 fc9 a3f00 fc9a0e10 fc9a100c fc9a100c05 Mon Sep 10 21:36:10 2007 0x2000004f Cause: MBI-HELLO reloading node on rec eiving reload notification Process: mbi-hello Traceback: fc1601a0 fc160290 482 0020c fc1dcfb0 0 006 Wed Oct 10 18:28:53 2007 0x21000106 Cause: All fabric links down on Fabric q Process: fabricq_mgr Traceback: fc1601a0 fc160290 fc9 d9f48 fc9d6e58 fc9d7054 fc9d705407 Wed Oct 10 19:04:02 2007 0x2000004f Cause: MBI-HELLO reloading node on rec eiving reload notification Process: mbi-hello Traceback: fc160c38 fc160d34 482 0020c fc1ddfb0 0 008 Wed Oct 10 20:19:39 2007 0x0000004f Cause: HBAgent reloading node on recei ving reload notification Process: hbagent Traceback: fc160c38 fc160d34 482 00228 fc1ddfb0 0 009 Wed Oct 10 20:45:53 2007 0x0000004f Cause: HBAgent reloading node on recei ving reload notification Process: hbagent Traceback: fc160c38 fc160d34 482 00228 fc1ddfb0 0 010 Thu Oct 11 19:15:55 2007 0x0000004f Cause: HBAgent reloading node on recei ving reload notification Process: hbagent Traceback: fc160c38 fc160d34 482 00228 fc1ddfb0 0 0






Watchdog Commands on Cisco IOS XR Softwareshow reboot last


OL-17332-01

show reboot lastTo display the latest crash information, use the show reboot last command in EXEC mode.

show reboot last {crashinfo | syslog | trace} {location node-id}

Syntax Description

Command Modes EXEC

Command History


Task ID

Examples The following sample output is from the show reboot last command:

RP/0/RP0/CPU0:router# show reboot last crashinfo location 0/1/CPU0

Crashinfo Timestamp: Wed Oct 10 19:04:02 2007

20071010 10:04:03

Crash Reason: Cause code 0x2000004f Cause: MBI-HELLO reloading node on receivin0

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

Active process(s):

crashinfo Displays crash information.

syslog Displays information for the system logs.

trace Displays the log for the reboot trace.







Task ID Operations

system read



OL-17332-01

pkg/bin/mbi-hello Thread ID 2 on cpu 0

REGISTER INFO r0 r1 r2 r3 R0 2000004f 4815da60 4820ea44 00000138 r4 r5 r6 r7 R4 4815da38 00000002 4815da48 00000001 r8 r9 r10 r11 R8 80000000 60277440 4815da28 00000600 r12 r13 r14 r15 R12 24000094 4820ea00 00000000 00000000 r16 r17 r18 r19 R16 00000000 00000000 00000000 00000000 r20 r21 r22 r23 R20 00000000 00000000 00000000 00000000 r24 r25 r26 r27 R24 00000000 00000000 00000000 482053cc r28 r29 r30 r31 R28 4815df7c 4815db68 0000004f 00000009 cnt lr msr pc R32 fc1e800c fc160f38 0002d932 fc160f60 cnd xer R36 48000094 2000000f

SUPERVISOR REGISTERS

Memory Management Registers

Instruction BAT Registers Index # Value IBAT0U # 0x1ffe IBAT0L # 0x12 IBAT1U # 0 IBAT1L # 0 IBAT2U # 0x30000ffe IBAT2L # 0xf0000032 IBAT3U # 0 IBAT3L # 0

Data BAT Registers Index # Value DBAT0U # 0x1ffe DBAT0L # 0x12 DBAT1U # 0 DBAT1L # 0x10000012 DBAT2U # 0x30000ffe DBAT2L # 0xf000006a DBAT3U # 0 DBAT3L # 0xf0000022

Segment Registers Index # SR-Value 0 # 0 1 # 0 2 # 0 3 # 0 4 # 0 5 # 0 6 # 0 7 # 0 8 # 0 9 # 0



OL-17332-01

10 # 0 11 # 0 12 # 0 13 # 0 14 # 0 15 # 0

Exception Handling Registers Data Addr Reg # DSISR 0x60277440 # 0x42000000 SPRG0 # SPRG1 # SPRG2 # SPRG30x4815db68 # 0x4f # 0x9 # 0 SaveNRestore SRR0 # SaveNRestore SRR1 0xfc160f5c # 0x2d932

Miscellaneous Registers Processor Id Reg # 0 HID0 # 0x8410c0bc HID1 # 0x90018c80

MSSCR0 # 0x88000 MSSSR0 # 0

STACK TRACE #0 0xfc160f38 0

STACK TRACE #0 0xfc160290#1 0xfc99ded4#2 0xfc99ae00#3 0xfc99affc#4 0xfc99affc#5 0xfc99bccc#6 0xfc646548#7 0xfc63f074#8 0xfc16a404#9 0xfc1688d8#10 0xfc63f3bc#11 0xfc1d5fb0






Watchdog Commands on Cisco IOS XR Softwareshow reboot pcds


OL-17332-01

show reboot pcdsTo display Persistent Critical Data Store (PCDS) critical information for the last ungraceful reboot, use the show reboot pcds command in EXEC mode.

show reboot pcds {location node-id}

Syntax Description

Command Modes EXEC

Command History


Task ID

Examples The following example shows some sample output from the show reboot pcds command:

RP/0/RP0/CPU0:router# show reboot pcds location 0/1/CPU0

PCDS Timestamp: Wed Oct 10 19:04:02 2007PCDS size: 131072 (bytes)PCDS Data:

000000 03014352 49544d4f 4e000000 00000000 ..CRITMON.......000010 02000000 00000008 00000000 30d00000 ............0...000020 00001a90 00000000 00000000 00000000 ................000030 0b0f0b0f 13911300 b8000013 b8000017 ................000040 470ca354 11000300 00001c41 00000000 G..T.......A....000050 00000974 00000000 30464fe4 ffffff00 ...t....0FO.....000060 b8000003 b8000007 b8000003 b8000007 ................000070 0b0f0b0f 13911300 b8000013 b8000017 ................000080 470ca354 01000300 00001c44 00000000 G..T.......D....000090 00000975 00000000 30464fe4 ffffff00 ...u....0FO.....







Task ID Operations

system read



OL-17332-01

0000a0 b8000003 b8000007 b8000003 b8000007 ................0000b0 0b0f0b0f 13911300 b8000013 b8000017 ................0000c0 470ca355 11000300 00001c47 00000000 G..U.......G....0000d0 00000976 00000000 30464fe4 ffffff00 ...v....0FO.....0000e0 b8000003 b8000007 b8000003 b8000007 ................0000f0 0b0f0b0f 13911300 b8000013 b8000017 ................000100 470ca355 01000300 00001c4a 00000000 G..U.......J....000110 00000977 00000000 30464fe4 ffffff00 ...w....0FO.....000120 b8000003 b8000007 b8000003 b8000007 ................000130 0b0f0b0f 13911300 b8000013 b8000017 ................000140 470ca356 11000300 00001c4d 00000000 G..V.......M....000150 00000978 00000000 30464fe4 ffffff00 ...x....0FO.....000160 b8000003 b8000007 b8000003 b80000ff ................000170 0bff0bff 13911300 b8000013 b8000017 ................000180 470ca357 01000300 00001c50 00000000 G..W.......P....000190 00000979 00000000 30464fe4 ffffff00 ...y....0FO.....0001a0 b8000003 b8000007 b80000ff b8000007 ................0001b0 ff0fff0f ff911300 b8000013 b8000017 ................0001c0 470ca357 11000300 00001c53 00000000 G..W.......S....0001d0 0000097a 00000000 30464fe4 ffffff00 ...z....0FO.....0001e0 b8000003 b8000007 b80000ff b8000007 ................0001f0 ff0fff0f ff911300 b8000013 b80000ff ................000200 470ca358 01000300 00001c56 00000000 G..X.......V....000210 0000097b 00000000 30464fe4 ffffff00 ...{....0FO.....000220 b8000003 b8000007 b80000ff b8000007 ................000230 ff0fff0f ff911300 b8000013 b80000ff ................000240 470ca358 11000300 00001c59 00000000 G..X.......Y....000250 0000097c 00000000 30464fe4 ffffff00 ...|....0FO.....000260 b8000003 b8000007 b80000ff b8000007 ................000270 ff0fff0f ff911300 b8000013 b80000ff ................000280 470ca359 01000300 00001c5c 00000000 G..Y.......\....000290 0000097d 00000000 30464fe4 ffffff00 ...}....0FO.....0002a0 b8000003 b8000007 b8000003 b8000007 ................0002b0 0b0f0b0f 13911300 b8000013 b8000017 ................0002c0 470ca35a 11000300 00001c5f 00000000 G..Z......._....0002d0 0000097e 00000000 30464fe4 ffffff00 ...~....0FO.....0002e0 b8000003 b8000007 b8000003 b8000007 ................0002f0 0b0f0b0f 13911300 b8000013 b8000017 ................000300 470ca35a 01000300 00001c62 00000000 G..Z.......b....000310 0000097f 00000000 30464fe4 ffffff00 ........0FO.....000320 b8000003 b8000007 b8000003 b8000007 ................000330 0b0f0b0f 13911300 b8000013 b8000017 ................000340 470ca35b 11000300 00001c65 00000000 G..[.......e....000350 00000980 00000000 30464fe4 ffffff00 ........0FO.....000360 b8000003 b8000007 b8000003 b8000007 ................000370 0b0fff0f 13911300 b8000013 b8000017 ................000380 470ca35b 01000300 00001c68 00000000 G..[.......h....000390 00000981 00000000 30464fe4 ffffff00 ........0FO.....0003a0 b80000ff b80000ff b8000003 b80000ff ................0003b0 0bff0bff 13911300 b80000ff b8000017 ................0003c0 470ca35c 11000300 00001c6b 00000000 G..\.......k....0003d0 00000982 00000000 30464fe4 ffffff00 ........0FO.....0003e0 b8000003 b8000007 b8000003 b8000007 ................0003f0 0b0f0b0f 13911300 b8000013 b8000017 ................000400 470ca35d 01000300 00001c6e 00000000 G..].......n....000410 00000983 00000000 30464fe4 ffffff00 ........0FO.....000420 b8000003 b8000007 b8000003 b8000007 ................000430 0b0f0b0f 13911300 b8000013 b8000017 ................000440 470ca35d 11000300 00001c71 00000000 G..].......q....000450 00000984 00000000 30464fe4 ffffff00 ........0FO.....000460 b8000003 b8000007 b8000003 b8000007 ................000470 0b0f0b0f 13911300 b8000013 b8000017 ................000480 470ca35e 01000300 00001c74 00000000 G..^.......t....000490 00000985 00000000 30464fe4 ffffff00 ........0FO.....



OL-17332-01

0004a0 b8000003 b8000007 b8000003 b8000007 ................0004b0 0b0f0b0f 13911300 b8000013 b8000017 ................0004c0 470ca35e 11000300 00001c77 00000000 G..^.......w....0004d0 00000986 00000000 30464fe4 ffffff00 ........0FO.....0004e0 b8000003 b8000007 b8000003 b8000007 ................0004f0 0b0f0b0f 13911300 b8000013 b8000017 ................000500 470ca35f 01000300 00001c7a 00000000 G.._.......z....000510 00000987 00000000 30464fe4 ffffff00 ........0FO.....000520 b8000003 b8000007 b8000003 b8000007 ................000530 0b0f0b0f 13911300 b8000013 b8000017 ................000540 470ca360 11000300 00001c7d 00000000 G..`.......}....000550 00000988 00000000 30464fe4 ffffff00 ........0FO.....000560 b8000003 b8000007 b8000003 b8000007 ................000570 0b0f0b0f 13911300 b8000013 b8000017 ................000580 470ca360 01000300 00001c80 00000000 G..`............000590 00000989 00000000 30464fe4 ffffff00 ........0FO.....0005a0 b8000003 b8000007 b8000003 b8000007 ................0005b0 0b0f0b0f 13911300 b8000013 b8000017 ................0005c0 470ca361 11000300 00001c83 00000000 G..a............0005d0 0000098a 00000000 30464fe4 ffffff00 ........0FO.....0005e0 b8000003 b8000007 b8000003 b8000007 ................0005f0 0b0f0b0f 13911300 b8000013 b8000017 ................000600 470ca361 01000300 00001c86 00000000 G..a............000610 0000098b 00000000 30464fe4 ffffff00 ........0FO.....000620 b8000003 b8000007 b8000003 b8000007 ................000630 0b0f0b0f 13911300 b8000013 b8000017 ................000640 470ca362 11000300 00001c89 00000000 G..b............000650 0000098c 00000000 30464fe4 ffffff00 ........0FO.....000660 b8000003 b8000007 b8000003 b8000007 ................000670 0b0f0b0f 13911300 b8000013 b8000017 ................000680 470ca363 01000300 00001c8c 00000000 G..c............000690 0000098d 00000000 30464fe4 ffffff00 ........0FO.....0006a0 b8000003 b8000007 b8000003 b8000007 ................0006b0 0b0f0b0f 13911300 b8000013 b8000017 ................0006c0 470ca363 11000300 00001c8f 00000000 G..c............0006d0 0000098e 00000000 30464fe4 ffffff00 ........0FO.....






Watchdog Commands on Cisco IOS XR Softwareshow watchdog


OL-17332-01

show watchdog To display information about the memory state or threshold memory, use the show watchdog command in EXEC mode.

show watchdog [memory-state | threshold memory {configured | defaults}] [location node-id]

Syntax Description


Command Modes EXEC

Command History


Use the show watchdog command to display information about the memory states or thresholds for a specified location. You can display the default or configured memory thresholds.

memory-state (Optional) Displays the memory state.

threshold memory (Optional) Displays the memory thresholds.

configured Displays the configured memory thresholds.

defaults Displays the default memory thresholds.

location node-id (Optional) Specifies a node. The node-id argument is entered in the rack/slot/module notation.

The location node-id keyword and argument must be specified if the threshold memory keywords are selected.











Watchdog Commands on Cisco IOS XR Softwareshow watchdog


OL-17332-01

Task ID

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

RP/0/RP0/CPU0:router# show watchdog memory-state

Memory information: Physical Memory: 4096 MB Free Memory: 3170.429 MB Memory State: Normal

Related Commands

Task ID Operations

basic-services read

Command Description

watchdog threshold memory Configures the value of memory available for each alarm threshold.

AR Cisco IOS XR Advanced System Command Reference

HR Cisco IOS XR Interface and Hardware Component Command Reference

IR Cisco IOS XR IP Addresses and Services Command Reference

MCR Cisco IOS XR Multicast Command Reference

MNR Cisco IOS XR System Monitoring Command Reference

MPR Cisco IOS XR MPLS Command Reference

QR Cisco IOS XR Modular Quality of Service Command Reference

RR Cisco IOS XR Routing Command Reference

SMR Cisco IOS XR System Management Command Reference

SR Cisco IOS XR System Security Command Reference


OL-17332-01

I N D E X

A

asic-scan egressq (block number) command AR-2

asic-scan egressq disable command AR-4

asic-scan egressq enable command AR-6

asic-scan egressq help-block command AR-8

asic-scan egressq location command AR-10

asic-scan egressq quick-scan command AR-12

asic-scan pse egress (block number) command AR-14

asic-scan pse egress disable command AR-16

asic-scan pse egress enable command AR-18

asic-scan pse egress help-block command AR-20

asic-scan pse egress location command AR-21

asic-scan pse egress quick-scan command AR-23

asic-scan pse ingress (block number) command AR-25

asic-scan pse ingress disable command AR-27

asic-scan pse ingress enable command AR-29

asic-scan pse ingress help-block command AR-31

asic-scan pse ingress location command AR-32

asic-scan pse ingress quick-scan command AR-34

C

clear controller egressq queue all command AR-38

clear controller egressq queue command AR-36

clear controller egressq statistics command AR-40

clear controller fabricq statistics command AR-138

clear controller fabric statistics command AR-136

clear controller ingressq statistics command AR-140

clear controller pse statistics command AR-42

clear fabricq counters all command AR-142

clear fabricq counters frfab command AR-144

clear fabricq counters tofab command AR-146

controllers fabric bundle port command AR-148

controllers fabric plane oim command AR-149

controllers fabric plane shutdown command AR-151

controllers fabric rack command AR-153

controllers fabric statistics collection command AR-155

S

show arp trace command AR-242

show captured packets command AR-247

show cfgmgr trace command AR-249

show controllers cpuctrl cdma channel command AR-44

show controllers cpuctrl clients command AR-48

show controllers cpuctrl devices command AR-52

show controllers cpuctrl internal command AR-57

show controllers cpuctrl ports command AR-60

show controllers cpuctrl summary command AR-67

show controllers egressq eio links command AR-70

show controllers egressq group command AR-72

show controllers egressq interface command AR-75

show controllers egressq port command AR-79

Index


OL-17332-01

show controllers egressq queue command AR-82

show controllers egressq statistics command AR-85

show controllers fabric bundle command AR-159

show controllers fabric command AR-157

show controllers fabric connectivity command AR-161

show controllers fabric fgid resource command AR-166

show controllers fabric fgid statistics command AR-169

show controllers fabric fsdb-pla all command AR-172

show controllers fabric link port command AR-174

show controllers fabric plane command AR-177

show controllers fabricq barriers command AR-185

show controllers fabricq block command AR-187

show controllers fabricq drop command AR-189

show controllers fabricq eio command AR-193

show controllers fabricq errors command AR-195

show controllers fabricq fabric-backpressure command AR-197

show controllers fabricq frfab command AR-200

show controllers fabricq link-info command AR-189

show controllers fabricq output command AR-206

show controllers fabricq queue command AR-209

show controllers fabricq registers command AR-213

show controllers fabricq statistics command AR-216

show controllers fabricq tofab command AR-219

show controllers fabric rack all command AR-181

show controllers fabric sfe command AR-183

show controllers ingressq capacity command AR-222

show controllers ingressq clients command AR-224

show controllers ingressq eio command AR-226

show controllers ingressq fabric command AR-228

show controllers ingressq interfaces command AR-230

show controllers ingressq queues command AR-232

show controllers ingressq statistics command AR-234

show controllers ingressq vports command AR-238

show controllers plim asic egress-channel bay command AR-88

show controllers plim asic ingress-channel bay command AR-90

show controllers plim asic pla AR-93

show controllers plim asic pla768 AR-95

show controllers plim asic plaspa command AR-97

show controllers plim asic spa bay command AR-99

show controllers plim asic statistics command AR-103

show controllers plim asic summary command AR-107

show controllers pse eio links command AR-110

show controllers pse ipc command AR-113

show controllers pse mp command AR-119

show controllers pse statistics command AR-124

show controllers pse summary command AR-130

show critmon context command AR-430

show critmon deadline command AR-434

show critmon statistics command AR-437

show critmon trace all command AR-445

show critmon trace error command AR-447

show critmon trace info command AR-449

show critmon trace lib-error command AR-451

show critmon trace lib-info command AR-453

show im database command AR-251

show imds interface brief command AR-254

show netio chains command AR-256

show netio clients command AR-260

show netio db command AR-262

show netio idb command AR-264

show netio media-registrations command AR-268

show netio subblock command AR-270

show netio trace command AR-272

show packet-memory command AR-133

show reboot first command AR-455

show reboot graceful command AR-457

show reboot history command AR-459

show reboot last command AR-461

show reboot pcds command AR-464

show sysdb trace verification location command AR-274

show sysdb trace verification shared-plane command AR-277

show tbm hardware command AR-279

show tech-support asic command AR-299

show tech-support bcdl command AR-302

show tech-support bundles command AR-310

Index


OL-17332-01

show tech-support cef command AR-322

show tech-support command AR-294

show tech-support control-ethernet command AR-328

show tech-support dsc command AR-333

show tech-support fabric command AR-338

show tech-support gsp command AR-344

show tech-support install command AR-349

show tech-support mpls rsvp command AR-354

show tech-support multicast command AR-360

show tech-support placement command AR-366

show tech-support platform command AR-369

show tech-support rdsfs command AR-373

show tech-support rib command AR-376

show tech-support routing bfd command AR-378

show tech-support routing isis command AR-383

show tech-support routing ospf command AR-388

show tech-support routing ospfv3 command AR-393

show tech-support routing rpl command AR-398

show tech-support sanitized command AR-404

show tech-support services command AR-410

show tech-support spaipc command AR-414

show tech-support sysdb command AR-419

show tech-support terminal command AR-423

show uidb data command AR-282

show uidb index command AR-287

show uidb trace command AR-285

show watchdog command AR-467

W

watchdog threshold memory command AR-290

Index


OL-17332-01

ar38book

Documents

cisco logo

cisco representative

trademarks of cisco

software license

document files

limited warranty

use of actual ip addresses

actual addresses