Feedback
Contents
Tech-Support Commands
This module describes commands used for displaying the output of show commands using Cisco IOS XR software 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.
- show system verify
- show tech-support
- show tech-support aps
- show tech-support asic
- show tech-support bcdl
- show tech-support bundles
- show tech-support cef
- show tech-support cfgmgr
- show tech-support chdlc
- show tech-support control-ethernet
- show tech-support dsc
- show tech-support ethernet
- show tech-support fabric
- show tech-support gsp
- show tech-support igmp snooping
- show tech-support install
- show tech-support l2tp
- show tech-support l2vpn
- show tech-support lrd
- show tech-support mpls ldp
- show tech-support mpls optical-uni
- show tech-support mpls rsvp
- show tech-support mpls traffic-eng
- show tech-support multicast
- show tech-support netflow
- show tech-support nrs
- show tech-support password
- show tech-support pfi
- show tech-support placement
- show tech-support pos
- show tech-support ppp
- show tech-support qos
- show tech-support rdsfs
- show tech-support rib
- show tech-support routing bfd
- show tech-support routing isis
- show tech-support routing ospf
- show tech-support routing ospfv3
- show tech-support routing rpl
- show tech-support serial
- show tech-support sanitized
- show tech-support services
- show tech-support snmp
- show tech-support spaipc
- show tech-support sysdb
- show tech-support terminal
show system verify
Syntax Description
start
(Optional) Performs an initial analysis of the system and stores the information for subsequent verification.
detail
(Optional) Generates a detailed report for the system verification process.
report
(Optional) Generates a report for the system verification process.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
You must run the show system verify command with the start keyword before generating any reports.
Task ID
Examples
The following example shows how to prepare for system verification:
RP/0/0/CPU0:router# show system verify start Storing initial router status ... done.The following example shows output from running the show system verify command:
RP/0/0/CPU0:router# show system verify Getting current router status ... System Verification Report ========================== - Verifying Memory Usage - Verified Memory Usage : [OK] - Verifying CPU Usage - Verified CPU Usage : [OK] - Verifying Blocked Processes - Verified Blocked Processes : [OK] - Verifying Aborted Processes - Verified Aborted Processes : [OK] - Verifying Crashed Processes - Verified Crashed Processes : [OK] - Verifying LC Status - Verified LC Status : [OK] - Verifying QNET Status Unable to get current LC status info - Verified QNET Status : [FAIL] - Verifying GSP Fabric Status - Verified GSP Fabric Status : [OK] - Verifying GSP Ethernet Status gsp WARNING messages for router Current set of gsp ping nodes does not match initial set of nodes - Verified GSP Ethernet Status : [WARNING] - Verifying POS interface Status - Verified POS interface Status : [OK] - Verifying TenGigE interface Status - Verified TenGigE interface Status : [OK] - Verifying TCP statistics - Verified TCP statistics : [OK] - Verifying UDP statistics tcp_udp_raw WARNING messages for router UDP Packets sent has not increased during this period. - Verified UDP statistics : [WARNING] - Verifying RAW statistics - Verified RAW statistics : [OK] - Verifying RIB Status - Verified RIB Status : [OK] - Verifying CEF Status - Verified CEF Status : [OK] - Verifying CEF Consistency Status - Verified CEF Consistency Status : [OK] - Verifying BGP Status - Verified BGP Status : [OK] - Verifying ISIS Status - Verified ISIS Status : [OK] - Verifying OSPF Status - Verified OSPF Status : [OK] - Verifying Syslog Messages - Verified Syslog Messages : [OK] System may not be stable. Please look into WARNING messages.
This table describes the significant fields shown in the display.
Table 1 show system verify Field DescriptionsField
Description
Type
Type of memory
Initial
Initial usage determined when the command is run with the start keyword
Current
Current usage
Application
Memory used for applications
Available
Memory available for applications
Physical
Total physical memory
nodes
Devices in the system such as linecards, route processors, fabric cards, and so forth
blocked processes
Number of blocked processes on the router
aborted processes
Number of aborted processes on the router
crashed processes
Number of crashed processes on the router
LC Status on Router
Linecard status
QNET Status on router
Internal communications protocol status
GSP Fabric Status on router
Internal communications protocol status
GSP Ethernet Status on router
Internal communications protocol status
POS Interface Status on router
Packet-over-SONET status
Protocol
Protocol on the interface
IP address
IP Address of the interface
Encapsulation
Encapsulation method used on the interface
MTU
Maximum Transmission Units for the interface
Keep alive
Keep alives messages on the interface
Packets Input
Total number packets input to the interface
Bytes Input
Total number of bytes input to the interface
Packets Output
Total number of packets output by the interface
Byte Output
Total number of bytes output by the interface
TenGigE interface Status on router
10 Gigabit Ethernet interface status
TCP statistics on router
Transmission Control Protocol statistics
UDP statistics on router
User Datagram Protocol statistics
RAW statistics on router
RAW statistics
PCBs
Protocol Control Blocks
RIB Status on router
Routing Information Base status
CEF Status on node......
Cisco Express Forwarding status
CEF Consistency Status on router
Cisco Express Forwarding consistency status
BGP Status on router
Border Gateway Protocol status
neighbors
Number of BGP neighbors
established
Number of BGP neighbors in ‘established’ state
ISIS Status on router
Intermediate System-to-Intermediate System status
up
Number of ISIS links up
failed
Number of failed ISIS links
init
Initial number of ISIS links
OSPF Status on router
Open Shortest Path First status
interfaces
Number of interfaces configured in OSPF
interfaces_up
Number of interfaces configured in OSPF that are in the ‘up’ state
virtual_int
Number of virtual interfaces
neighbors
Number of OSPF neighbors configured
neighbors_adj
Number of OSPF configured neighbors that are ‘adjacent’
Syslog Messages on router
Number of syslog messages
show tech-support
To 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:
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.
Command Default
The command output is not compressed.
Passwords and other security information are not displayed.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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
- 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 lpts ifib brief
- show im database 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
- admin show controllers fabric sfe s2 all detail
- admin show controllers fabric sfe s3 all detail
- show environment all
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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/0/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-1 line console exec-timeout 600 0 session-timeout 600 ! line default exec-timeout 600 0 session-timeout 600 ! clock timezone PST 8 clock summer-time DST recurring 2 sunday march 02:00 first sunday november 02:00 logging console informational telnet vrf default ipv4 server max-servers no-limit domain ipv4 host p1 172.16.52.72 domain ipv4 host p2 172.16.52.77 domain ipv4 host ce6 172.16.52.73 domain ipv4 host ce7 172.16.52.78 domain ipv4 host pe6 172.16.52.128 domain ipv4 host pe7 172.16.52.182 domain ipv4 host pe11 172.16.52.83 domain lookup disable username 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 alias cr copy run disk0:/usr/base_config alias sa show alias alias sc show config commit list alias sd show diag alias si show ip int brief alias sl show led alias sm show mpls forwarding alias sp show platform alias sr show run alias su show users alias sv show version alias sir show ip route ipv4 virtual address 172.16.52.72 255.255.255.0 hw-module service sbc location 0/4/CPU0 hw-module service sbc location 0/4/CPU1 interface 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 . .show tech-support aps
To automatically run show commands that display debugging information related to automatic protection switching (APS), use the show tech-support aps command in the EXEC mode. This command collects APS traces and sonet local traces across all locations and also show controller and show aps commands for all ports and groups.
Syntax Description
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
group
(Optional) Displays the show group commands with no trace for APS debugging.
show-only
(Optional) Displays the show commands with no trace for APS debugging.
terminal
(Optional) Specifies that the command output is displayed on the terminal.
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 aps command to run show commands that display APS debugging 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.
Task ID
Examples
The following example shows a truncated output of the show tech-support aps command:
RP/0/0/CPU0:router# show tech-support aps show-only terminal ------------------------------------------------------------------------------- show tech-support aps ------------------------------------------------------------------------------- ---------------------------------- show aps ----------------------------------- no aps group found ------------------------------- show aps agents ------------------------------- APS shows Agent: sysdb_datalist failed: ('sysdb' detected the 'warning' conditi) --------------------------- show controller sonet * --------------------------- Port SONET0/6/0/0: Status: Up Loopback: None SECTION LOF = 0 LOS = 1 BIP(B1) = 0 LINE AIS = 0 RDI = 1 FEBE = 0 BIP(B2) = 0 PATH AIS = 0 RDI = 1 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 PLM = 0 TIM = 0 UNEQ = 0 Line delays trigger: 0 ms clear: 10000 ms Path delays trigger: 0 ms, 0 ms (configured), clear: 10000 ms Last clearing of "show controllers SONET" counters never Detected Alarms: None Asserted Alarms: None Mask for Detected->Asserted: None Detected Alerts: None Reported Alerts: None Mask for Detected->Reported: None Alarm reporting enabled for: SLOS SLOF SF_BER PLOP Alert reporting enabled for: B1-TCA B2-TCA B3-TCA Framing: SONET SPE Scrambling: Enabled C2 State: Stable C2_rx = 0x16 (22) C2_tx = 0x16 (22) / Scrambling Derived S1S0(tx): 0x0 S1S0(rx): 0x0 / Framing Derived PATH TRACE BUFFER : STABLE Remote hostname : P11_CRS-4 Remote interface: POS0/2/0/0 Remote IP addr : 10.111.4.11 APS No APS Group Configured Rx(K1/K2) : 0x00/0x00 Tx(K1/K2) : 0x00/0x00 Remote Rx(K1/K2): 01/0 Remote Tx(K1/K2): 01/0 BER thresholds: SF = 10e-3 SD = 10e-6 TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6 Optics type: OC3 SR-1/STM1 MM Clock source: internal (actual) internal (configured) Rx S1: 0xf Tx S1: 0xf Optical Power Monitoring (accuracy: +/- 1dB) Rx power = 0.0160 mW, -18.0 dBm Tx power = 0.0000 mW, -inf dBm Tx laser current bias = 0.0 mA Port SONET0/6/0/1: Status: Up Loopback: None SECTION LOF = 0 LOS = 1 BIP(B1) = 0 LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0 PATH AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 PLM = 0 TIM = 0 UNEQ = 0 Line delays trigger: 0 ms clear: 10000 ms Path delays trigger: 0 ms, 0 ms (configured), clear: 10000 ms Last clearing of "show controllers SONET" counters never Detected Alarms: None Asserted Alarms: None Mask for Detected->Asserted: None Detected Alerts: None Reported Alerts: None Mask for Detected->Reported: None Alarm reporting enabled for: SLOS SLOF SF_BER PLOP Alert reporting enabled for: B1-TCA B2-TCA B3-TCA Framing: SONET SPE Scrambling: Enabled C2 State: Stable C2_rx = 0x16 (22) C2_tx = 0x16 (22) / Scrambling Derived S1S0(tx): 0x0 S1S0(rx): 0x0 / Framing Derived PATH TRACE BUFFER : STABLE Remote hostname : P2_CRS-8 Remote interface: POS0/6/0/1 Remote IP addr : 10.12.8.2 APS No APS Group Configured Protect Channel 0 DISABLED Rx(K1/K2) : 0x00/0x00 Tx(K1/K2) : 0x00/0x00 Remote Rx(K1/K2): 01/0 Remote Tx(K1/K2): 01/0 BER thresholds: SF = 10e-3 SD = 10e-6 TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6 Optics type: OC3 SR-1/STM1 MM Clock source: internal (actual) internal (configured) Rx S1: 0xf Tx S1: 0xf Optical Power Monitoring (accuracy: +/- 1dB) Rx power = 0.0223 mW, -16.5 dBm Tx power = 0.0000 mW, -inf dBm Tx laser current bias = 0.0 mA Port SONET0/6/0/2: Status: Down Loopback: None SECTION LOF = 0 LOS = 1 BIP(B1) = 0 LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0 PATH AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 PLM = 0 TIM = 0 UNEQ = 0 Line delays trigger: 0 ms clear: 10000 ms Path delays trigger: 0 ms, 0 ms (configured), clear: 10000 ms Last clearing of "show controllers SONET" counters never Detected Alarms: SLOS Asserted Alarms: SLOS Mask for Detected->Asserted: SLOF LAIS SF_BER SD_BER LRDI PLOP PAIS PRDI PUNEQ Detected Alerts: None Reported Alerts: None Mask for Detected->Reported: B1-TCA B2-TCA B3-TCA Alarm reporting enabled for: SLOS SLOF SF_BER PLOP Alert reporting enabled for: B1-TCA B2-TCA B3-TCA Framing: SONET SPE Scrambling: Enabled C2 State: Stable C2_rx = 0x6D (109) C2_tx = 0x16 (22) / Scrambling Derived S1S0(tx): 0x0 S1S0(rx): 0x2 / Framing Derived PATH TRACE BUFFER : UNSTABLE Remote hostname : Remote interface: Remote IP addr : APS No APS Group Configured Protect Channel 0 DISABLED Rx(K1/K2) : 0x00/0x00 Tx(K1/K2) : 0x00/0x00 Remote Rx(K1/K2): 1/ Remote Tx(K1/K2): 1/ BER thresholds: SF = 10e-3 SD = 10e-6 TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6 Optics type: None Clock source: internal (actual) line (configured) Rx S1: 0xe Tx S1: 0xf Optical Power Monitoring (accuracy: +/- 1dB) Not Supported Port SONET0/6/0/3: Status: Up Loopback: None SECTION LOF = 0 LOS = 0 BIP(B1) = 0 LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0 PATH AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 PLM = 0 TIM = 0 UNEQ = 0 Line delays trigger: 0 ms clear: 10000 ms Path delays trigger: 0 ms, 0 ms (configured), clear: 10000 ms Last clearing of "show controllers SONET" counters never Detected Alarms: None Asserted Alarms: None Mask for Detected->Asserted: None Detected Alerts: None Reported Alerts: None Mask for Detected->Reported: None Alarm reporting enabled for: SLOS SLOF SF_BER PLOP Alert reporting enabled for: B1-TCA B2-TCA B3-TCA Framing: SONET SPE Scrambling: Enabled C2 State: Stable C2_rx = 0x16 (22) C2_tx = 0x16 (22) / Scrambling Derived S1S0(tx): 0x0 S1S0(rx): 0x0 / Framing Derived PATH TRACE BUFFER : STABLE Remote hostname : PE21_C12406 Remote interface: POS0/2/0/3 Remote IP addr : 10.121.4.21 APS No APS Group Configured Protect Channel 0 DISABLED Rx(K1/K2) : 0x00/0x00 Tx(K1/K2) : 0x00/0x00 Remote Rx(K1/K2): 01/0 Remote Tx(K1/K2): 01/0 BER thresholds: SF = 10e-3 SD = 10e-6 TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6 Optics type: OC3 SR-1/STM1 MM Clock source: internal (actual) internal (configured) Rx S1: 0xf Tx S1: 0xf Optical Power Monitoring (accuracy: +/- 1dB) Rx power = 0.0206 mW, -16.9 dBm Tx power = 0.0000 mW, -inf dBm Tx laser current bias = 0.0 mA Port SONET0/6/4/0: Status: Down Loopback: None SECTION LOF = 0 LOS = 1 BIP(B1) = 0 LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0 PATH AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 PLM = 0 TIM = 0 UNEQ = 0 Line delays trigger: 0 ms clear: 10000 ms Path delays trigger: 0 ms, 0 ms (configured), clear: 10000 ms Last clearing of "show controllers SONET" counters never Detected Alarms: SLOS Asserted Alarms: SLOS Mask for Detected->Asserted: SLOF LAIS SF_BER SD_BER LRDI PLOP PAIS PRDI PUNEQ Detected Alerts: None Reported Alerts: None Mask for Detected->Reported: B1-TCA B2-TCA B3-TCA Alarm reporting enabled for: SLOS SLOF SF_BER PLOP Alert reporting enabled for: B1-TCA B2-TCA B3-TCA Framing: SONET SPE Scrambling: Enabled C2 State: Stable C2_rx = 0xFF (255) C2_tx = 0x16 (22) / Scrambling Derived S1S0(tx): 0x0 S1S0(rx): 0x0 / Framing Derived PATH TRACE BUFFER : UNSTABLE Remote hostname : Remote interface: Remote IP addr : APS No APS Group Configured Rx(K1/K2) : 0x00/0x00 Tx(K1/K2) : 0x00/0x00 Remote Rx(K1/K2): 1/ Remote Tx(K1/K2): 1/ BER thresholds: SF = 10e-3 SD = 10e-6 TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6 Optics type: None Clock source: internal (actual) line (configured) Rx S1: 0x0 Tx S1: 0xf Optical Power Monitoring (accuracy: +/- 1dB) Not Supported Port SONET0/6/4/1: Status: Down Loopback: None SECTION LOF = 0 LOS = 1 BIP(B1) = 0 LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0 PATH AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 PLM = 0 TIM = 0 UNEQ = 0 Line delays trigger: 0 ms clear: 10000 ms Path delays trigger: 0 ms, 0 ms (configured), clear: 10000 ms Last clearing of "show controllers SONET" counters never Detected Alarms: SLOS Asserted Alarms: SLOS Mask for Detected->Asserted: SLOF LAIS SF_BER SD_BER LRDI PLOP PAIS PRDI PUNEQ Detected Alerts: None Reported Alerts: None Mask for Detected->Reported: B1-TCA B2-TCA B3-TCA Alarm reporting enabled for: SLOS SLOF SF_BER PLOP Alert reporting enabled for: B1-TCA B2-TCA B3-TCA Framing: SONET SPE Scrambling: Enabled C2 State: Stable C2_rx = 0xFF (255) C2_tx = 0x16 (22) / Scrambling Derived S1S0(tx): 0x0 S1S0(rx): 0x0 / Framing Derived PATH TRACE BUFFER : UNSTABLE Remote hostname : Remote interface: Remote IP addr : APS No APS Group Configured Protect Channel 0 DISABLED Rx(K1/K2) : 0x00/0x00 Tx(K1/K2) : 0x00/0x00 Remote Rx(K1/K2): 1/ Remote Tx(K1/K2): 1/ BER thresholds: SF = 10e-3 SD = 10e-6 TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6 Optics type: None Clock source: internal (actual) line (configured) Rx S1: 0x0 Tx S1: 0xf Optical Power Monitoring (accuracy: +/- 1dB) Not Supported Port SONET0/6/4/2: Status: Down Loopback: None SECTION LOF = 0 LOS = 1 BIP(B1) = 0 LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0 PATH AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 PLM = 0 TIM = 0 UNEQ = 0 Line delays trigger: 0 ms clear: 10000 ms Path delays trigger: 0 ms, 0 ms (configured), clear: 10000 ms Last clearing of "show controllers SONET" counters never Detected Alarms: SLOS Asserted Alarms: SLOS Mask for Detected->Asserted: SLOF LAIS SF_BER SD_BER LRDI PLOP PAIS PRDI PUNEQ Detected Alerts: None Reported Alerts: None Mask for Detected->Reported: B1-TCA B2-TCA B3-TCA Alarm reporting enabled for: SLOS SLOF SF_BER PLOP Alert reporting enabled for: B1-TCA B2-TCA B3-TCA Framing: SONET SPE Scrambling: Enabled C2 State: Stable C2_rx = 0xEF (239) C2_tx = 0x16 (22) / Scrambling Derived S1S0(tx): 0x0 S1S0(rx): 0x0 / Framing Derived PATH TRACE BUFFER : UNSTABLE Remote hostname : Remote interface: Remote IP addr : APS No APS Group Configured Protect Channel 0 DISABLED Rx(K1/K2) : 0x00/0x00 Tx(K1/K2) : 0x00/0x00 Remote Rx(K1/K2): 1/ Remote Tx(K1/K2): 1/ BER thresholds: SF = 10e-3 SD = 10e-6 TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6 Optics type: None Clock source: internal (actual) line (configured) Rx S1: 0x0 Tx S1: 0xf Optical Power Monitoring (accuracy: +/- 1dB) Not Supported Port SONET0/6/4/3: Status: Down Loopback: None SECTION LOF = 0 LOS = 1 BIP(B1) = 0 LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0 PATH AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 PLM = 0 TIM = 0 UNEQ = 0 Line delays trigger: 0 ms clear: 10000 ms Path delays trigger: 0 ms, 0 ms (configured), clear: 10000 ms Last clearing of "show controllers SONET" counters never Detected Alarms: SLOS Asserted Alarms: SLOS Mask for Detected->Asserted: SLOF LAIS SF_BER SD_BER LRDI PLOP PAIS PRDI PUNEQ Detected Alerts: None Reported Alerts: None Mask for Detected->Reported: B1-TCA B2-TCA B3-TCA Alarm reporting enabled for: SLOS SLOF SF_BER PLOP Alert reporting enabled for: B1-TCA B2-TCA B3-TCA Framing: SONET SPE Scrambling: Enabled C2 State: Stable C2_rx = 0xFF (255) C2_tx = 0x16 (22) / Scrambling Derived S1S0(tx): 0x0 S1S0(rx): 0x0 / Framing Derived PATH TRACE BUFFER : UNSTABLE Remote hostname : Remote interface: Remote IP addr : APS No APS Group Configured Protect Channel 0 DISABLED Rx(K1/K2) : 0x00/0x00 Tx(K1/K2) : 0x00/0x00 Remote Rx(K1/K2): 1/ Remote Tx(K1/K2): 1/ BER thresholds: SF = 10e-3 SD = 10e-6 TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6 Optics type: None Clock source: internal (actual) line (configured) Rx S1: 0x0 Tx S1: 0xf Optical Power Monitoring (accuracy: +/- 1dB) Not Supported Port SONET0/6/4/4: Status: Up Loopback: None SECTION LOF = 0 LOS = 0 BIP(B1) = 0 LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0 PATH AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 PLM = 0 TIM = 0 UNEQ = 0 Line delays trigger: 0 ms clear: 10000 ms Path delays trigger: 0 ms, 0 ms (configured), clear: 10000 ms Last clearing of "show controllers SONET" counters never Detected Alarms: None Asserted Alarms: None Mask for Detected->Asserted: None Detected Alerts: None Reported Alerts: None Mask for Detected->Reported: None Alarm reporting enabled for: SLOS SLOF SF_BER PLOP Alert reporting enabled for: B1-TCA B2-TCA B3-TCA Framing: SONET SPE Scrambling: Enabled C2 State: Stable C2_rx = 0x16 (22) C2_tx = 0x16 (22) / Scrambling Derived S1S0(tx): 0x0 S1S0(rx): 0x0 / Framing Derived PATH TRACE BUFFER : STABLE Remote hostname : P4_C12810 Remote interface: POS0/3 Remote IP addr : 10.14.4.4 APS No APS Group Configured Protect Channel 0 DISABLED Rx(K1/K2) : 0x00/0x00 Tx(K1/K2) : 0x00/0x00 Remote Rx(K1/K2): F1/F Remote Tx(K1/K2): 00/0 BER thresholds: SF = 10e-3 SD = 10e-6 TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6 Optics type: OC12 SR-1/STM4 MM Clock source: internal (actual) internal (configured) Rx S1: 0xf Tx S1: 0xf Optical Power Monitoring (accuracy: +/- 1dB) Rx power = 0.0184 mW, -17.4 dBm Tx power = 0.0000 mW, -inf dBm Tx laser current bias = 0.0 mA Port SONET0/6/4/5: Status: Up Loopback: None SECTION LOF = 0 LOS = 1 BIP(B1) = 0 LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0 PATH AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 PLM = 0 TIM = 0 UNEQ = 0 Line delays trigger: 0 ms clear: 10000 ms Path delays trigger: 0 ms, 0 ms (configured), clear: 10000 ms Last clearing of "show controllers SONET" counters never Detected Alarms: None Asserted Alarms: None Mask for Detected->Asserted: None Detected Alerts: None Reported Alerts: None Mask for Detected->Reported: None Alarm reporting enabled for: SLOS SLOF SF_BER PLOP Alert reporting enabled for: B1-TCA B2-TCA B3-TCA Framing: SONET SPE Scrambling: Enabled C2 State: Stable C2_rx = 0x16 (22) C2_tx = 0x16 (22) / Scrambling Derived S1S0(tx): 0x0 S1S0(rx): 0x0 / Framing Derived PATH TRACE BUFFER : STABLE Remote hostname : P2_CRS-8 Remote interface: POS0/6/4/5 Remote IP addr : 10.12.4.2 APS No APS Group Configured Protect Channel 0 DISABLED Rx(K1/K2) : 0x00/0x00 Tx(K1/K2) : 0x00/0x00 Remote Rx(K1/K2): 01/0 Remote Tx(K1/K2): 01/0 BER thresholds: SF = 10e-3 SD = 10e-6 TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6 Optics type: OC12 SR-1/STM4 MM Clock source: internal (actual) internal (configured) Rx S1: 0xf Tx S1: 0xf Optical Power Monitoring (accuracy: +/- 1dB) Rx power = 0.0193 mW, -17.1 dBm Tx power = 0.0000 mW, -inf dBm Tx laser current bias = 0.0 mA Port SONET0/6/4/6: Status: Up Loopback: None SECTION LOF = 1 LOS = 0 BIP(B1) = 0 LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0 PATH AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 PLM = 0 TIM = 0 UNEQ = 0 Line delays trigger: 0 ms clear: 10000 ms Path delays trigger: 0 ms, 0 ms (configured), clear: 10000 ms Last clearing of "show controllers SONET" counters never Detected Alarms: None Asserted Alarms: None Mask for Detected->Asserted: None Detected Alerts: None Reported Alerts: None Mask for Detected->Reported: None Alarm reporting enabled for: SLOS SLOF SF_BER PLOP Alert reporting enabled for: B1-TCA B2-TCA B3-TCA Framing: SONET SPE Scrambling: Enabled C2 State: Stable C2_rx = 0x16 (22) C2_tx = 0x16 (22) / Scrambling Derived S1S0(tx): 0x0 S1S0(rx): 0x0 / Framing Derived PATH TRACE BUFFER : STABLE Remote hostname : P3_C12008 Remote interface: POS5/2 Remote IP addr : 10.13.4.3 APS No APS Group Configured Protect Channel 0 DISABLED Rx(K1/K2) : 0x00/0x00 Tx(K1/K2) : 0x00/0x00 Remote Rx(K1/K2): 00/0 Remote Tx(K1/K2): 00/0 BER thresholds: SF = 10e-3 SD = 10e-6 TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6 Optics type: OC12 SR-1/STM4 MM Clock source: internal (actual) internal (configured) Rx S1: 0xf Tx S1: 0xf Optical Power Monitoring (accuracy: +/- 1dB) Rx power = 0.0142 mW, -18.5 dBm Tx power = 0.0000 mW, -inf dBm Tx laser current bias = 0.0 mA Port SONET0/6/4/7: Status: Down Loopback: None SECTION LOF = 0 LOS = 1 BIP(B1) = 0 LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0 PATH AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 PLM = 0 TIM = 0 UNEQ = 0 Line delays trigger: 0 ms clear: 10000 ms Path delays trigger: 0 ms, 0 ms (configured), clear: 10000 ms Last clearing of "show controllers SONET" counters never Detected Alarms: SLOS Asserted Alarms: SLOS Mask for Detected->Asserted: SLOF LAIS SF_BER SD_BER LRDI PLOP PAIS PRDI PUNEQ Detected Alerts: None Reported Alerts: None Mask for Detected->Reported: B1-TCA B2-TCA B3-TCA Alarm reporting enabled for: SLOS SLOF SF_BER PLOP Alert reporting enabled for: B1-TCA B2-TCA B3-TCA Framing: SONET SPE Scrambling: Enabled C2 State: Stable C2_rx = 0xF7 (247) C2_tx = 0x16 (22) / Scrambling Derived S1S0(tx): 0x0 S1S0(rx): 0x0 / Framing Derived PATH TRACE BUFFER : UNSTABLE Remote hostname : Remote interface: Remote IP addr : APS No APS Group Configured Protect Channel 0 DISABLED Rx(K1/K2) : 0x00/0x00 Tx(K1/K2) : 0x00/0x00 Remote Rx(K1/K2): 1/ Remote Tx(K1/K2): 1/ BER thresholds: SF = 10e-3 SD = 10e-6 TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6 Optics type: None Clock source: internal (actual) internal (configured) Rx S1: 0x0 Tx S1: 0xf Optical Power Monitoring (accuracy: +/- 1dB) Not Supported ------------------------------------------------------------------------------- show tech-support aps complete -------------------------------------------------------------------------------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
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.
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
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 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
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 asic command output:
RP/0/0/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 -lrt total 980 . . .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
bcdl-group
(Optional) Name of the BCDL group.
terminal
Displays the 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.
sent-to
Name of the file. The following valid options are listed:
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
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 bcdl command:
See the Cisco IOS XR Software command references for information about these commands and descriptions of their command output. The Cisco IOS XR Software 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 the truncated output of the show tech-support bcdl command:
RP/0/0/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/ 0 /CPU0, pulse 0, ne0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2105 16 6 no yes no 0 0 0 0 grp ipv4_mrib, gid 2102, sg cnt 1, agent jid 116, node 0/ 0 /CPU0, pulse 0, new0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2103 16 6 no yes no 0 0 0 0 grp ipv4_rib, gid 2049, sg cnt 1, agent jid 111, node 0/ 0 /CPU0, pulse 38335, 0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2050 16 6 no no no 0 38387 38330 0 grp ipv6_mrib, gid 2100, sg cnt 1, agent jid 115, node 0/ 0 /CPU0, pulse 0, new0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2101 16 6 no yes no 0 0 0 0 grp ipv6_rib, gid 2051, sg cnt 1, agent jid 112, node 0/ 0 /CPU0, pulse 6, new 0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2052 16 6 no no no 0 1 1 0 grp mpls_lsd_v4, gid 2060, sg cnt 1, agent jid 113, node 0/ 0 /CPU0, pulse 38430 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2061 17 6 no no no 0 38431 38432 0 grp mpls_lsd_v6, gid 2062, sg cnt 1, agent jid 114, node 0/ 0 /CPU0, pulse 7, n0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2063 17 6 no no no 0 1 2 0 grp pa_ff, gid 2021, sg cnt 1, agent jid 110, node 0/ 0 /CPU0, pulse 271, new m0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 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 name 458887 0/RP0/CPU0 0 0 2105 N 0 0 0 fib_mgr 209032 0/RP1/CPU0 0 0 2105 N 0 0 0 fib_mgr 90198 0/6/CPU0 0 0 2105 N 0 0 0 fib_mgr 106592 0/4/CPU0 0 0 2105 N 0 0 0 fib_mgr 114782 0/4/CPU1 0 0 2105 N 0 0 0 fib_mgr 90198 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 name 790787 0/RP0/CPU0 0 0 2103 N 0 0 0 ipv4_mfwd_pare 262380 0/RP1/CPU0 0 0 2103 N 0 0 0 ipv4_mfwd_pare 127125 0/1/CPU0 0 0 2103 N 0 0 0 ipv4_mfwd_pare 139404 0/4/CPU1 0 0 2103 N 0 0 0 ipv4_mfwd_pare 127114 0/6/CPU0 0 0 2103 N 0 0 0 ipv4_mfwd_pare 131214 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 name 458887 0/RP0/CPU0 0 0 2050 N 38387 4599212 0 fib_mgr 209032 0/RP1/CPU0 0 0 2050 N 38385 4599156 0 fib_mgr 114782 0/4/CPU1 0 0 2050 N 38330 4574016 0 fib_mgr 90198 0/6/CPU0 0 0 2050 N 38363 4597820 0 fib_mgr 90198 0/1/CPU0 0 0 2050 N 38385 4599156 0 fib_mgr 106592 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 name 790788 0/RP0/CPU0 0 0 2101 N 0 0 0 ipv6_mfwd_pare 262381 0/RP1/CPU0 0 0 2101 N 0 0 0 ipv6_mfwd_pare 127126 0/1/CPU0 0 0 2101 N 0 0 0 ipv6_mfwd_pare 127115 0/6/CPU0 0 0 2101 N 0 0 0 ipv6_mfwd_pare 139405 0/4/CPU1 0 0 2101 N 0 0 0 ipv6_mfwd_pare 131215 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 name 458887 0/RP0/CPU0 0 0 2052 N 1 28 0 fib_mgr 209032 0/RP1/CPU0 0 0 2052 N 2 56 0 fib_mgr 90198 0/1/CPU0 0 0 2052 N 2 56 0 fib_mgr 106592 0/4/CPU0 0 0 2052 N 2 56 0 fib_mgr 90198 0/6/CPU0 0 0 2052 N 2 56 0 fib_mgr 114782 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 name 458887 0/RP0/CPU0 0 0 2061 N 38431 6895816 0 fib_mgr 209032 0/RP1/CPU0 0 0 2061 N 38431 6895816 0 fib_mgr 90198 0/1/CPU0 0 0 2061 N 38431 6895816 0 fib_mgr 90198 0/6/CPU0 0 0 2061 N 38431 6895816 0 fib_mgr 106592 0/4/CPU0 0 0 2061 N 38431 6895816 0 fib_mgr 114782 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 name 458887 0/RP0/CPU0 0 0 2063 N 1 228 0 fib_mgr 209032 0/RP1/CPU0 0 0 2063 N 1 228 0 fib_mgr 90198 0/1/CPU0 0 0 2063 N 1 228 0 fib_mgr 90198 0/6/CPU0 0 0 2063 N 1 228 0 fib_mgr 106592 0/4/CPU0 0 0 2063 N 1 228 0 fib_mgr 114782 0/4/CPU1 0 0 2063 N 1 228 0 fib_mgr 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 name 471193 0/RP0/CPU0 0 0 2022 N 260 52876 0 pifibm_server 90221 0/6/CPU0 0 0 2022 N 33 18516 0 pifibm_server 90214 0/1/CPU0 0 0 2022 N 33 18516 0 pifibm_server 110695 0/4/CPU0 0 0 2022 N 209 48132 0 pifibm_server 118885 0/4/CPU1 0 0 2022 N 224 50052 0 pifibm_server 221341 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, ne0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2105 16 6 no yes no 0 0 0 0 sgs: 1, table_cnt: 0, table_mid_cnt: 0, buf size: 20 Showing table info for 1 subgroups sg 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, new0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2103 16 6 no yes no 0 0 0 0 sgs: 1, table_cnt: 0, table_mid_cnt: 0, buf size: 20 Showing table info for 1 subgroups sg 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, 0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2050 16 6 no no no 0 38387 38330 0 sgs: 1, table_cnt: 1, table_mid_cnt: 6, buf size: 124 Showing table info for 1 subgroups sg 0: has 1 tables (messages: 0, bytes: 0) table 0xe0000000: 6 members, dnld act: 0, messages: 38387, bytes: 4599212 cnsmr 0: pid 458887 on node 0/RP0/CPU0 cnsmr 1: pid 209032 on node 0/RP1/CPU0 cnsmr 2: pid 90198 on node 0/1/CPU0 cnsmr 3: pid 90198 on node 0/6/CPU0 cnsmr 4: pid 106592 on node 0/4/CPU0 cnsmr 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, new0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2101 16 6 no yes no 0 0 0 0 sgs: 1, table_cnt: 0, table_mid_cnt: 0, buf size: 20 Showing table info for 1 subgroups sg 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 0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2052 16 6 no no no 0 1 1 0 sgs: 1, table_cnt: 1, table_mid_cnt: 6, buf size: 124 Showing table info for 1 subgroups sg 0: has 1 tables (messages: 0, bytes: 0) table 0xe0800000: 6 members, dnld act: 0, messages: 1, bytes: 28 cnsmr 0: pid 458887 on node 0/RP0/CPU0 cnsmr 1: pid 209032 on node 0/RP1/CPU0 cnsmr 2: pid 90198 on node 0/1/CPU0 cnsmr 3: pid 90198 on node 0/6/CPU0 cnsmr 4: pid 106592 on node 0/4/CPU0 cnsmr 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 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2061 17 6 no no no 0 38431 38432 0 sgs: 1, table_cnt: 0, table_mid_cnt: 0, buf size: 20 Showing table info for 1 subgroups sg 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, n0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2063 17 6 no no no 0 1 2 0 sgs: 1, table_cnt: 0, table_mid_cnt: 0, buf size: 20 Showing table info for 1 subgroups sg 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 m0 sg lwg fd csmr hdlr-act dnld-act susp wait-lck seq pulse-tot pulse-out 0 2022 16 6 no no no 0 260 259 0 sgs: 1, table_cnt: 0, table_mid_cnt: 0, buf size: 20 Showing table info for 1 subgroups sg 0: has 0 tables (messages: 260, bytes: 52876) Mon Nov 10 18:29:15.426 PST DST --------------------------- show process bcdl_agent --------------------------- Job Id: 110 PID: 462997 Executable path: /disk0/hfr-base-3.8.0.20I/sbin/bcdl_agent Instance #: 1 Args: -p pa_ff -m 0 -b 0 -d libbcdl_pa_ff.dll Version ID: 00.00.0000 Respawn: ON Respawn count: 1 Max. spawns per minute: 12 Last started: Tue Nov 4 02:01:52 2008 Process state: Run Package state: Normal core: MAINMEM Max. core: 0 startup_path: /pkg/startup/bcdl_agent.startup Ready: 2.321s Process cpu time: 3.115 user, 0.421 kernel, 3.536 total JID TID Stack pri state TimeInState HR:MM:SS:MSEC NAME 110 1 44K 10 Receive 160:27:23:0754 0:00:00:0053 bcdl_agent 110 2 44K 10 Condvar 89:29:17:0305 0:00:00:0003 bcdl_agent 110 3 44K 10 Receive 0:00:00:0745 0:00:01:0815 bcdl_agent 110 4 44K 10 Nanosleep 0:00:06:0200 0:00:00:0025 bcdl_agent 110 5 44K 10 Receive 0:00:12:0728 0:00:00:0000 bcdl_agent ------------------------------------------------------------------------------- Job Id: 111 PID: 479442 Executable path: /disk0/hfr-base-3.8.0.20I/sbin/bcdl_agent Instance #: 2 Args: -p ipv4_rib -m 0 -b 65200 Version ID: 00.00.0000 Respawn: ON Respawn count: 1 Max. spawns per minute: 12 Last started: Tue Nov 4 02:02:35 2008 Process state: Run Package state: Normal core: MAINMEM Max. core: 0 startup_path: /pkg/startup/bcdl_agent.startup Ready: 3.682s Process cpu time: 14.430 user, 1.416 kernel, 15.846 total 111 2 52K 10 Condvar 155:55:15:0696 0:00:00:0012 bcdl_agent 111 3 52K 10 Receive 160:25:30:0729 0:00:00:0000 bcdl_agent 111 4 52K 10 Nanosleep 0:00:01:0628 0:00:00:0026 bcdl_agent 111 5 52K 10 Receive 0:00:01:0441 0:00:08:0542 bcdl_agent 111 6 52K 10 Receive 0:00:13:0163 0:00:00:0000 bcdl_agent ------------------------------------------------------------------------------- Job Id: 112 PID: 479443 Executable path: /disk0/hfr-base-3.8.0.20I/sbin/bcdl_agent Instance #: 3 Args: -p ipv6_rib -m 0 -b 65200 Version ID: 00.00.0000 Respawn: ON Respawn count: 1 Max. spawns per minute: 12 Last started: Tue Nov 4 02:02:36 2008 Process state: Run Package state: Normal core: MAINMEM Max. core: 0 startup_path: /pkg/startup/bcdl_agent.startup Ready: 3.545s Process cpu time: 3.695 user, 0.428 kernel, 4.123 total 112 1 48K 10 Receive 160:26:39:0019 0:00:00:0054 bcdl_agent 112 2 48K 10 Condvar 155:55:17:0392 0:00:00:0002 bcdl_agent 112 3 48K 10 Receive 0:00:14:0512 0:00:03:0983 bcdl_agent 112 4 48K 10 Nanosleep 0:00:02:0509 0:00:00:0030 bcdl_agent 112 6 48K 10 Receive 0:00:02:0001 0:00:00:0001 bcdl_agent ------------------------------------------------------------------------------- Job Id: 113 PID: 483569 Executable path: /disk0/hfr-base-3.8.0.20I/sbin/bcdl_agent Instance #: 4 Args: -p mpls_lsd_v4 -m 10 -b 32768 Version ID: 00.00.0000 Respawn: ON Respawn count: 1 Max. spawns per minute: 12 Last started: Tue Nov 4 02:03:06 2008 Process state: Run Package state: Normal core: MAINMEM Max. core: 0 startup_path: /pkg/startup/bcdl_agent.startup Ready: 1.987s Process cpu time: 18.238 user, 1.777 kernel, 20.015 total 113 2 48K 10 Condvar 160:22:55:0518 0:00:00:0002 bcdl_agent 113 3 48K 10 Receive 160:26:09:0157 0:00:00:0000 bcdl_agent 113 4 48K 10 Nanosleep 0:00:16:0592 0:00:00:0018 bcdl_agent 113 5 48K 10 Receive 0:00:00:0289 0:00:00:0002 bcdl_agent 113 6 48K 10 Receive 0:00:15:0924 0:00:01:0234 bcdl_agent ------------------------------------------------------------------------------- Job Id: 114 PID: 487660 Executable path: /disk0/hfr-base-3.8.0.20I/sbin/bcdl_agent Instance #: 5 Args: -p mpls_lsd_v6 -m 10 -b 32768 Version ID: 00.00.0000 Respawn: ON Respawn count: 1 Max. spawns per minute: 12 Last started: Tue Nov 4 02:03:06 2008 Process state: Run Package state: Normal core: MAINMEM Max. core: 0 startup_path: /pkg/startup/bcdl_agent.startup Ready: 2.145s Process cpu time: 4.206 user, 0.496 kernel, 4.702 total 114 1 52K 10 Receive 0:00:04:0881 0:00:04:0595 bcdl_agent 114 2 52K 10 Condvar 160:22:56:0168 0:00:00:0003 bcdl_agent 114 3 52K 10 Receive 160:26:09:0766 0:00:00:0000 bcdl_agent 114 4 52K 10 Nanosleep 0:00:16:0666 0:00:00:0019 bcdl_agent 114 5 52K 10 Receive 0:00:16:0589 0:00:00:0001 bcdl_agent --More--. . .show tech-support bundles
To 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 [ interface type interface-path-id ] [ file sent-to ] [background] [ compressed | uncompressed ] [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.
sent-to
Name of the file. The following valid options are listed:
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.
interface
(Optional) Collects information about a specific interface.
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.
show-only
(Optional) Collects only show command information.
terminal
Displays the command output on the terminal.
trace-only
(Optional) Collects only trace information.
vrf
(Optional) Specifies a VPN routing and forwarding (VRF) instance.
vrf-name
(Optional) Name of VRF.
location
(Optional) Specifies a node.
node-id
(Optional). Node ID. The node-id argument is entered in the rack/slot/module notation.
all
(Optional) Specifies all locations.
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
See the Cisco IOS XR Software command references for information about these commands and descriptions of their command output. The Cisco IOS XR Software 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 shows some of the show tech-support bundles command output that is displayed for the terminal:
RP/0/0/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-8 line console exec-timeout 600 0 session-timeout 600 ! line default exec-timeout 600 0 session-timeout 600 ! clock timezone PST 8 clock summer-time DST recurring 2 sunday march 02:00 first sunday november 02:00 logging console informational telnet vrf default ipv4 server max-servers no-limit domain ipv4 host p1 172.29.52.72 domain ipv4 host p2 172.29.52.77 domain ipv4 host ce6 172.29.52.73 domain ipv4 host ce7 172.29.52.78 domain ipv4 host p11 172.29.52.83 domain ipv4 host pe6 172.29.52.128 domain ipv4 host pe7 172.29.52.182 domain ipv4 host ce25 172.29.52.85 domain ipv4 host ce28 172.29.52.1 domain ipv4 host ce29 172.29.52.178 domain ipv4 host pe21 172.29.52.163 domain ipv4 host pe22 172.29.52.219 domain ipv4 host ce28_nme 172.29.52.177 domain ipv4 host ce29_nme 172.29.52.179 domain lookup disable username 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 25 alias cr copy run disk0:/usr/P1_base_config alias sa show alias alias sc show config commit list alias sd show diag alias si show ip int brief alias sl show led alias sm show mpls forwarding alias sp show platform alias sr show run alias su show users alias sv show version alias sir show ip route control-plane management-plane inband interface all allow all ! ! ! ! ipv4 virtual address 172.29.52.72 255.255.255.0 hw-module service sbc location 0/4/CPU0 hw-module service sbc location 0/4/CPU1 interface 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 ! 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 ! 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 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 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 ! 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 server xml agent tty xml agent corba http server sbc service-1 service-location preferred-active 0/4/CPU0 ! sbc service-2 service-location preferred-active 0/4/CPU1 ! end ---------------------- 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 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/CPUv 65643 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_server 65796 966916 1 showtech_helper Reply 0:00:05:0243 1 kernel 65801 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 = 5 Crash time: Mon Oct 15, 2007: 04:54:16 Core 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 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 0show tech-support cef
To 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 ] [ A .B .C .D | A .B .C .D /length | detail | brief | interface | rack ] ] [ 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.
A.B.C.D
(Optional) Specifies IPv4 Prefix entries.
A.B.C.D/length
(Optional) Specifies IPv4 Prefix mask.
detail
(Optional) Specifies detailed CEF debugging information.
brief
(Optional) Specifies a 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:
compress
(Optional) Specifies compression for the trace file.
interface
(Optional) Specifies CEF interface status and configuration.
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
rack
(Optional) Specifies a list of racks.
terminal
Displays the 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.
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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..
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 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)
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 a truncated output of the show tech-support cef command:
RP/0/0/CPU0:router# show tech-support cef terminal page ------------------------------------------------------------------------------- show tech-support cef ipv4 brief ------------------------------------------------------------------------------- -------------------------------- show version -------------------------------- Cisco IOS XR Software, Version 3.9.0 Copyright (c) 2007 by Cisco Systems, Inc. ROM: System Bootstrap, Version 1.43(20061109:045749) [CRS-1 ROMMON], CRS-1 uptime is 1 week, 2 days, 20 hours, 29 minutes System 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 0x102 Boot 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 2007 By 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 2007 By 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-1 line console exec-timeout 600 0 session-timeout 600 ! line default exec-timeout 600 0 session-timeout 600 ! logging console informational telnet vrf default ipv4 server max-servers no-limit domain ipv4 host p1 172.16.52.72 domain ipv4 host p2 172.16.52.77 domain ipv4 host ce6 172.16.52.73 domain ipv4 host ce7 172.16.52.78 domain ipv4 host pe6 172.16.52.128 domain ipv4 host pe7 172.16.52.182 domain ipv4 host pe11 172.16.52.83 domain lookup disable vty-pool default 0 25 ipv4 virtual address 172.16.52.72 255.255.255.0 interface Loopback0 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 server xml agent tty xml agent corba http server sbc 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 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_servershow tech-support cfgmgr
To automatically run show commands that display information to gather information about the configuration manager, use the show tech-support cfgmgr command in EXEC mode.
show tech-support cfgmgr { file send-to [background] [ compressed | uncompressed ] | terminal [page] }
Syntax Description
file
Specifies that the command output is saved to a specified file.
sent-to
Name of the file. The following valid options are listed:
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.
terminal
Specifies that the command output is displayed on the terminal.
page
(Optional) Specifies that the command output is displayed one 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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 cfgmgr command to gather information about the configuration manager. This command is used to locate any issues in regards to executing configuration commands or problems. See 'Obtaining Documentation and Submitting a Service Request' section on page iii in the Preface for Cisco Technical Support contact information.
See the Cisco IOS XR Software command references for information about these commands and descriptions of their command output. The Cisco IOS XR Software 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 cfgmgr command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support cfgmgr terminal ------------------------------------------------------------------------------ show tech-support cfgmgr ------------------------------------------------------------------------------- -------------------------------- show platform -------------------------------- Node Type PLIM State Config State ----------------------------------------------------------------------------- 0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON 0/1/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON 0/1/1 MSC(SPA) 4T3E3 OK PWR,NSHUT,MON 0/1/4 MSC(SPA) 4XOC48-POS OK PWR,NSHUT,MON 0/1/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON 0/4/CPU0 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON 0/4/CPU1 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON 0/6/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON 0/6/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON 0/6/4 MSC(SPA) 8XOC3/OC12-POS OK PWR,NSHUT,MON 0/6/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON 0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON ----------------------------- show running-config ----------------------------- Building configuration... !! Last configuration change at Wed Oct 10 20:05:13 2007 ! hostname P1_CRS-8 line console exec-timeout 600 0 session-timeout 600 ! line default exec-timeout 600 0 session-timeout 600 ! clock timezone PST 8 clock summer-time DST recurring 2 sunday march 02:00 first sunday november 02:00 logging console informational telnet vrf default ipv4 server max-servers no-limit domain ipv4 host p1 172.29.52.72 domain ipv4 host p2 172.29.52.77 domain ipv4 host ce6 172.29.52.73 domain ipv4 host ce7 172.29.52.78 domain ipv4 host p11 172.29.52.83 domain ipv4 host pe6 172.29.52.128 domain ipv4 host pe7 172.29.52.182 domain ipv4 host ce25 172.29.52.85 domain ipv4 host ce28 172.29.52.1 domain ipv4 host ce29 172.29.52.178 domain ipv4 host pe21 172.29.52.163 domain ipv4 host pe22 172.29.52.219 domain ipv4 host ce28_nme 172.29.52.177 domain ipv4 host ce29_nme 172.29.52.179 domain lookup disable username 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 25 alias cr copy run disk0:/usr/P1_base_config alias sa show alias alias sc show config commit list alias sd show diag alias si show ip int brief alias sl show led alias sm show mpls forwarding alias sp show platform alias sr show run alias su show users alias sv show version alias sir show ip route control-plane management-plane inband interface all allow all ! ! ! ! ipv4 virtual address 172.29.52.72 255.255.255.0 hw-module service sbc location 0/4/CPU0 hw-module service sbc location 0/4/CPU1 interface 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 ! 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 ! 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 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 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 ! 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 server xml agent tty xml agent corba http server sbc service-1 service-location preferred-active 0/4/CPU0 ! sbc service-2 service-location preferred-active 0/4/CPU1 ! end ---------------------- show configuration failed startup ---------------------- !!10:28:35 UTC Thu Oct 11 2007show tech-support chdlc
To automatically run show commands that display debugging information related to Cisco high-level data link control (CHDLC) protocol, use the show tech-support chdlc command in the EXEC mode.
Syntax Description
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
interface
(Optional) Displays information about a specific interface.
slow
(Optional) Displays the debugging output of chdlc.
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
rack
(Optional) Displays a list of racks.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 chdlc command to run show commands that display CHDLC debugging 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.
Task ID
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 [fast] [ location node-id ] { terminal [page] | file send-to [background] [ compressed | uncompressed ] }
Syntax Description
fast
(Optional) Collects the output simultaneously from multiple line cards ina multi-chassis router.
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
terminal
Displays the 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.
sent-to
Name of the file. The following valid options are listed:
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
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 control-ethernet command:
- show version
- 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
- 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
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software command references are located at the following URL:
http://www.cisco.com/en/US/products/ps5845/prod_command_reference_list.html
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 a truncated version of the show tech-support control-ethernet command output:
RP/0/0/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/ 0 /CPU0 Node - 0/ 0 /CPU0 Node - 0/SM0/SP Node - 0/SM1/SP Node - 0/SM2/SP Node - 0/SM3/SP ------------------------------------------------------------------------------- show tech-support control-ethernet ------------------------------------------------------------------------------- ------------------- show version --------------------------------- Cisco IOS XR Software, Version 3.9.0.20I[DT_IMAGE] Copyright (c) 2009 by Cisco Systems, Inc. ROM: System Bootstrap, Version 1.51(20080807:092259) [CRS-1 ROMMON], P2_CRS-8 uptime is 1 day, 18 hours, 10 minutes System 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 Ethernet 16 GigabitEthernet 20 SONET/SDH 20 Packet over SONET/SDH 1019k 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.20I Built on Wed Oct 29 17:24:33 DST 2008 By 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.20I Built on Wed Oct 29 17:02:19 DST 2008 By 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.20I Built on Wed Oct 29 17:02:01 DST 2008 By 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.20I Built on Wed Oct 29 16:08:13 DST 2008 By 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.20I Built on Wed Oct 29 16:07:35 DST 2008 By 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.20I Built on Wed Oct 29 15:45:48 DST 2008 By iox30.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0 Configuration register on node 0/1/CPU0 is 0x102 Boot 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.0I Built on Wed Oct 29 17:03:08 DST 2008 By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0 hfr-pagent, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-pagent-3.8.0.20I Built on Wed Oct 29 17:24:33 DST 2008 By 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.20I Built on Wed Oct 29 17:02:19 DST 2008 By 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.20I Built on Wed Oct 29 17:02:01 DST 2008 By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0 hfr-mcast, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-mcast-3.8.0.20I Built on Wed Oct 29 18:18:37 DST 2008 By 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.20I Built on Wed Oct 29 18:18:25 DST 2008 By 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.20I Built on Wed Oct 29 16:18:36 DST 2008 By 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.20I Built on Wed Oct 29 16:13:27 DST 2008 By iox30.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0 --More--show tech-support dsc
To 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
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
terminal
Displays the 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.
sent-to
Name of the file. The following are valid options:
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
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 dsc command:
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 dsc command output:
RP/0/0/CPU0:router(admin)#show tech-support dsc terminal page ------------------------------------------------------------------------------- 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 Current process = "pkg/bin/dsc", PID = 110638 TID = 2 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 Current process = "pkg/bin/dsc", PID = 110638 TID = 4 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 Current process = "pkg/bin/dsc", PID = 110638 TID = 5 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 Current process = "pkg/bin/dsc", PID = 110638 TID = 6 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 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 total JID TID Stack pri state TimeInState HR:MM:SS:MSEC NAME 155 1 52K 10 Receive 0:00:52:0856 0:00:00:0176 dsc 155 2 52K 10 Receive 326:49:44:0414 0:00:00:0001 dsc 155 4 52K 10 Receive 0:00:00:0083 0:00:01:0127 dsc 155 5 52K 10 Receive 0:00:00:0643 0:00:00:0019 dsc 155 6 52K 55 Receive 0:00:00:0060 0:14:49:0966 dsc . . .show tech-support ethernet
To automatically run show commands that display information specific to ethernet debugging, use the show tech-support ethernet command in EXEC mode.
show tech-support ethernet [ file send-to [background] [ compressed | uncompressed ] ] [ interface | location node-id | rack ]
Syntax Description
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:
interface
(Optional) Collects the status and configuration information about a specific interface.
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
rack
(Optional) Specifies a list of racks.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 ethernet command to run show commands that display information specific to VLAN and ethernet infrastructure debugging. This command generates ethernet 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.
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 ethernet command:
- show version
- show running
- show route {ipv4 | ipv6} unicast
- show proc blocked
- show ethernet {ipv4 | ipv6 | mpls} exceptions
- show ethernet {ipv4 | ipv6 | mpls} drop
- show ipv4 interface brief
- show mpls forwarding (if the mpls keyword is specified)
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 a truncated output of the show tech-support ethernet command:
RP/0/0/CPU0:router# show tech-support ethernet ------------------------------------------------------------------------------- show tech-support ethernet ------------------------------------------------------------------------------- +++++++++++ show process blocked [15:01:51.358 UTC Thu Dec 17 2009] +++++++++++ Jid Pid Tid Name State TimeInState Blocked-on 65549 16397 1 ksh Reply 22:06:27:0772 16396 devc-conaux 65554 69650 2 devb-umass Reply 0:00:00:0259 49194 io-usb 95 45090 2 umass-enum Reply 22:30:23:0232 1 kernel 95 45090 3 umass-enum Reply 22:30:22:0715 1 kernel 95 45090 5 umass-enum Reply 22:30:16:0703 49194 io-usb 95 45090 6 umass-enum Reply 22:30:20:0148 1 kernel 95 45090 7 umass-enum Reply 22:30:18:0707 1 kernel 95 45090 8 umass-enum Reply 22:30:16:0704 1 kernel 65579 69675 2 devb-umass Reply 22:28:55:0126 49194 io-usb 65583 98351 2 devb-umass Reply 0:00:07:0370 49194 io-usb 52 86067 2 attachd Reply 22:30:18:0708 49196 eth_server 52 86067 3 attachd Reply 22:30:18:0708 24595 mqueue 86 86068 6 qnet Reply 0:00:00:0326 49196 eth_server 51 98363 2 attach_server Reply 22:30:17:0894 24595 mqueue 436 213083 1 tftp_server Reply 22:28:25:0936 24595 mqueue 65719 290999 1 exec Reply 0:00:12:0040 1 kernel 294 270546 2 lpts_fm Reply 0:31:02:0906 237695 lpts_pa open /proc/8577304 failed: No such file or directory 65822 8266014 1 showtech_cat Reply 0:00:00:0055 24593 pipe 65823 8454431 1 showtech_cat Reply 0:00:00:0432 24593 pipe 65825 8552737 1 show_processes Reply 0:00:00:0000 1 kernel ----------- show process blocked [15:01:52.688 UTC Thu Dec 17 2009] ----------- +++++++++++++++ show context [15:01:53.014 UTC Thu Dec 17 2009] +++++++++++++++ --------------- show context [15:01:53.820 UTC Thu Dec 17 2009] --------------- ------------------------------------------------------------------------------- show tech-support ether common ------------------------------------------------------------------------------- ++++++++ show ethernet driver trace [15:01:55.942 UTC Thu Dec 17 2009] ++++++++ 152 unique entries (320 possible, 0 filtered) Dec 16 16:33:19.238 gether/0/main 0/RSP0/CPU0 1# t1 ETH_INFO: Allocated port array, size 3 Dec 16 16:33:19.242 gether/0/main 0/RSP0/CPU0 1# t1 ETH_TRACE: ethernet_event_mgr_init: Creating EVM Dec 16 16:33:19.242 gether/0/main 0/RSP0/CPU0 1# t1 ETH_INFO: ethernet_event_mgr_init: EVM created 0x5005a910, msgch 0x5005a9f0, node 0/RSP0/CPU0 Dec 16 16:33:19.260 gether/0/main 0/RSP0/CPU0 1# t1 ETH_INFO: ethernet_chkpt_init: checkpoint init succeeded: restart 0, 0x1f50 Dec 16 16:33:19.261 gether/0/main 0/RSP0/CPU0 1# t1 ETH_INFO: ethernet_timer_system_init: Timer init successful Dec 16 16:33:20.725 gether/0/main 0/RSP0/CPU0 2# t1 ETH_IM: Carrier delay timer created for None (0x00000000) Dec 16 16:33:20.726 gether/0/main 0/RSP0/CPU0 2# t1 ETH_INFO: Port created ok for bay=0, port=1 Dec 16 16:33:20.726 gether/0/main 0/RSP0/CPU0 1# t4 ETH_TRACE: ethernet_evm_thread: Ethernet EVM thread Dec 16 16:33:20.726 gether/0/main 0/RSP0/CPU0 1# t1 ETH_INFO: G-Ether library initialization successful Dec 16 16:33:20.726 gether/0/main 0/RSP0/CPU0 1# t4 Created IDB tree RW lock Dec 16 16:33:20.726 gether/0/main 0/RSP0/CPU0 1# t4 DB: Module initialized: Success Dec 16 16:33:20.726 gether/0/main 0/RSP0/CPU0 1# t1 ETH_INFO: ethernet_netio_connection_init: Connecting to NetIO, dll_name libether_ctrl_mgmt_netio.dll, dll_init_func ether_ctrl_mgmt_netio_init_func, node 1 Dec 16 16:33:20.726 gether/0/main 0/RSP0/CPU0 1# t4 ETH_TRACE: ethernet_im_connection_init: Connecting to IM Dec 16 16:33:20.832 gether/0/main 0/RSP0/CPU0 1# t1 ETH_INFO: ethernet_netio_conn_open: notify event has been created Dec 16 16:33:20.832 gether/0/main 0/RSP0/CPU0 1# t1 ETH_INFO: ethernet_netio_conn_open: Bind & initializaton of netio done Dec 16 16:33:20.832 gether/0/main 0/RSP0/CPU0 1# t1 ETH_INFO: ethernet_netio_conn_notify_handler: load NetIO dll libether_ctrl_mgmt_netio.dll Dec 16 16:33:20.833 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IM: Event conn open to IM failed - retry scheduled Dec 16 16:33:20.833 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IM: ethernet_im_connection_init: IM connection init done Dec 16 16:33:20.833 gether/0/main 0/RSP0/CPU0 1# t4 ETH_INFO: Initializing connection to Cfgmgr Dec 16 16:33:20.974 gether/0/main 0/RSP0/CPU0 1# t4 ETH_INFO: Cfgmgr connection initialization successful Dec 16 16:33:21.397 gether/0/main 0/RSP0/CPU0 1# t4 ETH_TRACE: Successfully initialized PFI protect. Dec 16 16:33:21.397 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IM: ethernet_if_owner_edm_init: Interface owner EDM init Dec 16 16:33:22.161 gether/0/main 0/RSP0/CPU0 1# t1 ETH_INFO: ethernet_netio_connection_init: Netio connection init done, node 1 Dec 16 16:33:23.679 gether/0/main 0/RSP0/CPU0 1# t4 ETH_TRACE: Successfully initialized Attributes Library. Dec 16 16:33:23.684 gether/0/main 0/RSP0/CPU0 1# t4 ETH_SYSDB: ethernet_sysdb_edm_init: Sysdb bind to /oper/ethernet_drvr/if/ successful, node 1 Dec 16 16:33:23.686 gether/0/main 0/RSP0/CPU0 1# t4 ETH_SYSDB: ethernet_sysdb_init: Connecting to Sysdb, config mask 0x0, node 1 Dec 16 16:33:23.686 gether/0/main 0/RSP0/CPU0 2# t4 ETH_SYSDB: ethernet_sysdb_conn_open: Connected to Sysdb, config mask 0x0, node 1 Dec 16 16:33:23.688 gether/0/main 0/RSP0/CPU0 1# t4 ETH_SYSDB: ethernet_sysdb_conn_open: Sysdb bind to /cfg/if/act/ successful, node 1 Dec 16 16:33:23.688 gether/0/main 0/RSP0/CPU0 2# t4 ETH_SYSDB: ethernet_sysdb_init: Sysdb connection init done, node 1 Dec 16 16:33:23.688 gether/0/main 0/RSP0/CPU0 1# t4 ETH_INFO: Initializing termination timers Dec 16 16:33:23.688 gether/0/main 0/RSP0/CPU0 2# t4 ETH_ERR: ethernet_im_conn_open: im_control_server_bind failed: Error: 'ifmgr' detected the 'warning' condition 'Failed to contact the server' Dec 16 16:33:25.690 gether/0/main 0/RSP0/CPU0 3# t4 ETH_IM: ethernet_im_conn_open: Connecting to IM Dec 16 16:33:25.795 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IM: ethernet_im_conn_open: Registered IM control handler Dec 16 16:33:25.795 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IM: ethernet_im_conn_notify_handler: Notify condition is 4096 Dec 16 16:33:25.801 gether/0/main 0/RSP0/CPU0 1# t4 ETH_INFO: Initialising connection to NetIO Dec 16 16:33:25.801 gether/0/main 0/RSP0/CPU0 1# t4 ETH_INFO: Binding to NetIO Dec 16 16:33:25.819 gether/0/main 0/RSP0/CPU0 1# t4 ETH_INFO: Connection to NetIO succeeded Dec 16 16:33:25.852 gether/0/main 0/RSP0/CPU0 1# t4 ETH_STATS: Stats collection initialized Dec 16 16:33:25.852 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IIR: Initializing connection to IIR Dec 16 16:33:25.859 gether/0/main 0/RSP0/CPU0 1# t4 ETH_ERR: IIR connection failed, scheduled for retry, bound=0, ERR: Error: No such file or directory Dec 16 16:33:25.859 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IIR: Initialized connection to IIR Dec 16 16:33:25.859 gether/0/main 0/RSP0/CPU0 2# t4 ETH_INFO: Port pre-enable for port=1 Dec 16 16:33:25.859 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IM: IM pre-create: sorted list of 2 interfaces Dec 16 16:33:25.859 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IM: IM create: about to send batch of 2 interfaces Dec 16 16:33:33.194 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IM: IM create: sent batch of 2 interfaces, return: Success Dec 16 16:33:33.194 gether/0/main 0/RSP0/CPU0 1# t4 DB: physical IDB added for Mg0/RSP0/CPU0/0 (0x00000040) Dec 16 16:33:33.196 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Get BIA called for Mg0/RSP0/CPU0/0 (0x00000040) (bay=0, port=0) MAC address 0024.f716.4b20 Dec 16 16:33:33.207 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Port Create called for Mg0/RSP0/CPU0/0 (0x00000040) (bay=0, port=0) create event Dec 16 16:33:33.207 gether/0/main 0/RSP0/CPU0 2# t4 ETH_INFO: Port post-enable for port=1 Dec 16 16:33:33.208 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Get BIA called for Mg0/RSP0/CPU0/1 (0x00000080) (bay=0, port=1) MAC address 0024.f716.4b21 Dec 16 16:33:33.208 gether/0/main 0/RSP0/CPU0 1# t4 DB: physical IDB added for Mg0/RSP0/CPU0/1 (0x00000080) Dec 16 16:33:33.208 gether/0/main 0/RSP0/CPU0 2# t4 ETH_INFO: ethernet_port_chkpt_recover: checkpoint create succeeded: interface Mg0/RSP0/CPU0/1 (0x00000080), id 0x2fb8 Dec 16 16:33:33.208 gether/0/main 0/RSP0/CPU0 2# t4 ETH_TRACE: ethernet_enable_port: Enabling the interface Mg0/RSP0/CPU0/1 (0x00000080) Dec 16 16:33:33.218 gether/0/main 0/RSP0/CPU0 2# t4 ETH_SYSDB: ethernet_sysdb_edm_init: Sysdb edm reg successful, node 1 Dec 16 16:33:33.222 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Port Create called for Mg0/RSP0/CPU0/1 (0x00000080) (bay=0, port=1) create event Dec 16 16:33:33.222 gether/0/main 0/RSP0/CPU0 2# t4 ETH_INFO: ethernet_enable_port: Interface MgmtEth0_RSP0_CPU0_1 enabled Dec 16 16:33:33.222 gether/0/main 0/RSP0/CPU0 2# t4 ETH_INFO: Port enabled ok for port=1 Dec 16 16:33:33.569 gether/0/main 0/RSP0/CPU0 1# t9 ETH_INFO: Client thread started Dec 16 16:33:33.569 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IM: IM Owned Resource End processing successful Dec 16 16:33:33.570 gether/0/main 0/RSP0/CPU0 2# t4 ETH_IIR: Opening connection to IIR Dec 16 16:33:33.571 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IIR: Successfully opened connection to IIR Dec 16 16:33:33.571 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IIR: 0 bundle member IDBs marked as stale Dec 16 16:33:45.875 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Get MTU called for Mg0/RSP0/CPU0/0 (0x00000040) (bay=0, port=0) MTU 1514 Dec 16 16:33:45.875 gether/0/main 0/RSP0/CPU0 1# t4 ETH_INFO: fwd_specify_plim_interface call for interface Mg0/RSP0/CPU0/0 (bay 0, port 0, fwd port 0, ifh 0x40) delayed Dec 16 16:33:45.937 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Get Loopback called for Mg0/RSP0/CPU0/0 (0x00000040) (bay=0, port=0) Loopback type None Dec 16 16:33:45.961 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Get Autoneg called for Mg0/RSP0/CPU0/0 (0x00000040) (bay=0, port=0) Autoneg configured: speed not restricted, duplex not restricted, flowcontrol not restricted Dec 16 16:33:45.961 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Get Admin State called for Mg0/RSP0/CPU0/0 (0x00000040) (bay=0, port=0) read state: disabled Dec 16 16:33:45.963 gether/0/fast 0/RSP0/CPU0 2# t4 HW API: Get Operational MAC called for Mg0/RSP0/CPU0/0 (0x00000040) (bay=0, port=0) MAC Address 0024.f716.4b20 Dec 16 16:33:46.051 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Get Duplex called for Mg0/RSP0/CPU0/0 (0x00000040) (bay=0, port=0) Duplex type Half Duplex Dec 16 16:33:46.052 gether/0/fast 0/RSP0/CPU0 2# t4 HW API Port Notification batch of size 1 for Port Available event processed successfully Dec 16 16:33:46.052 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Get MTU called for Mg0/RSP0/CPU0/1 (0x00000080) (bay=0, port=1) MTU 1514 Dec 16 16:33:46.052 gether/0/main 0/RSP0/CPU0 1# t4 ETH_INFO: fwd_specify_plim_interface call for interface Mg0/RSP0/CPU0/1 (bay 0, port 1, fwd port 1, ifh 0x80) delayed Dec 16 16:33:46.052 gether/0/main 0/RSP0/CPU0 2# t4 ETH_INFO: Initial notification for Mg0/RSP0/CPU0/1 (0x00000080) ok, (bay=0, port=1) Dec 16 16:33:46.094 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Get Loopback called for Mg0/RSP0/CPU0/1 (0x00000080) (bay=0, port=1) Loopback type None Dec 16 16:33:46.094 gether/0/main 0/RSP0/CPU0 2# t4 ETH_INFO: ethernet_set_autonegotiation: interface Mg0/RSP0/CPU0/1 (0x00000080) autoneg enabled Dec 16 16:33:46.118 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Get Autoneg called for Mg0/RSP0/CPU0/1 (0x00000080) (bay=0, port=1) Autoneg configured: speed not restricted, duplex not restricted, flowcontrol not restricted Dec 16 16:33:46.118 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Get Admin State called for Mg0/RSP0/CPU0/1 (0x00000080) (bay=0, port=1) read state: disabled Dec 16 16:33:46.118 gether/0/fast 0/RSP0/CPU0 2# t4 HW API: Get Operational MAC called for Mg0/RSP0/CPU0/1 (0x00000080) (bay=0, port=1) MAC Address 0024.f716.4b21 Dec 16 16:33:46.118 gether/0/main 0/RSP0/CPU0 2# t4 ETH_INFO: H/W replay successful for Mg0/RSP0/CPU0/1 (0x00000080) Dec 16 16:33:46.206 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Get Duplex called for Mg0/RSP0/CPU0/1 (0x00000080) (bay=0, port=1) Duplex type Half Duplex Dec 16 16:33:46.207 gether/0/main 0/RSP0/CPU0 2# t4 ETH_INFO: 6 attributes published successfully for Mg0/RSP0/CPU0/1 (0x00000080) Dec 16 16:33:46.207 gether/0/main 0/RSP0/CPU0 2# t4 ETH_INFO: Restoring config for Mg0/RSP0/CPU0/1 (0x00000080), current state = Config not applied Dec 16 16:33:46.207 gether/0/main 0/RSP0/CPU0 2# t4 ETH_INFO: Added Mg0/RSP0/CPU0/1 (0x00000080) to cfgmgr restore batch Dec 16 16:33:46.216 gether/0/main 0/RSP0/CPU0 1# t4 ETH_INFO: Cfgmgr restore batch successful for 2 interfaces Dec 16 16:33:46.217 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IIR: IIR RESYNC_END notification received Dec 16 16:33:46.217 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IIR: 0 IIR stale flags cleared Dec 16 16:33:46.217 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IIR: IIR RESYNC_END notification processed ok Dec 16 16:33:57.284 gether/0/main 0/RSP0/CPU0 1# t4 ETH_STATS: Stats type register callback invoked, count=2 Dec 16 16:33:57.284 gether/0/main 0/RSP0/CPU0 1# t4 ETH_STATS: Private stats types registered, type=10002, type=10003 Dec 16 16:34:06.221 gether/0/main 0/RSP0/CPU0 2# t4 ETH_STATS: New periodic block allocated, ptr=0x50036994 Dec 16 16:34:32.828 gether/0/fast 0/RSP0/CPU0 1# t4 HW API Config Restore batch of size 2 processed successfully Dec 16 16:34:32.828 gether/0/main 0/RSP0/CPU0 2# t4 ETH_INFO: Config restore completed ok for Mg0/RSP0/CPU0/0 (0x00000040) Dec 16 16:34:32.846 gether/0/main 0/RSP0/CPU0 3# t4 ETH_INFO: Starting cfgmgr restore batch, size=0, rc=0x0 Dec 16 16:34:32.846 gether/0/main 0/RSP0/CPU0 1# t4 ETH_IM: IM_STATE_DOWN_IMM_ADMIN walk completed for Mg0/RSP0/CPU0/1 (0x00000080) Dec 16 16:34:32.916 gether/0/fast 0/RSP0/CPU0 1# t4 HW API: Port Enable called for Mg0/RSP0/CPU0/0 (0x00000040) (bay=0, port=0) new state: enabled, hw link down Dec 16 16:34:32.916 gether/0/main 0/RSP0/CPU0 1# t4 ETH_EVENTS: FSM action: Port admin state enabled event for Mg0/RSP0/CPU0/0 (0x00000040); succeeded; link state: DOWNshow tech-support fabric
To automatically run show commands that display information specific to fabric debugging, use the show tech-support fabric 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.
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
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.
(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.
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
(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:
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
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 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
- show controllers cpuctrl devices fabricq pdma queue all act
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 fabric multicast command output:
RP/0/0/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_mapping show tech fabric multicast MSC: 0/1/CPU0 is running DRP: 0/4/CPU0 is running MSC: 0/6/CPU0 is running RP: 0/RP0/CPU0 is running RP: 0/RP1/CPU0 is running SM: type: 0, 0/SM0/SP is running SM: type: 0, 0/SM1/SP is running SM: type: 0, 0/SM2/SP is running SM: 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 data Please 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 65 show contr fabric trace fgid-client loc 0/4/CPU0 show contr fabric trace fgid-aggr info loc 0/4/CPU0 show contr fabric trace fgid-aggr err loc 0/4/CPU0 show 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 513 Nodeid 0x513 : sysmgr_show -o -A -p fgid_aggregator -n 513 Nodeid 0x513 : sysmgr_show -o -A -p fgid_server -n 513 show contr fabric trace fgid-client loc 0/RP0/CPU0 show contr fabric trace fgid-alloc info loc 0/RP0/CPU0 show contr fabric trace fgid-alloc err loc 0/RP0/CPU0 show contr fabric trace fgid-alloc dev loc 0/RP0/CPU0 show contr fabric trace fgid-svr info loc 0/RP0/CPU0 show contr fabric trace fgid-svr err loc 0/RP0/CPU0 show contr fabric trace fgid-svr dev loc 0/RP0/CPU0 show contr fabric trace fgid-agg info loc 0/RP0/CPU0 show contr fabric trace fgid-agg err loc 0/RP0/CPU0 show 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 529 Nodeid 0x529 : sysmgr_show -o -A -p fgid_aggregator -n 529 Nodeid 0x529 : sysmgr_show -o -A -p fgid_server -n 529 show contr fabric trace fgid-client loc 0/RP1/CPU0 show contr fabric trace fgid-alloc info loc 0/RP1/CPU0 show contr fabric trace fgid-alloc err loc 0/RP1/CPU0 show contr fabric trace fgid-alloc dev loc 0/RP1/CPU0 show contr fabric trace fgid-svr info loc 0/RP1/CPU0 show contr fabric trace fgid-svr err loc 0/RP1/CPU0 show contr fabric trace fgid-svr dev loc 0/RP1/CPU0 show contr fabric trace fgid-agg info loc 0/RP1/CPU0 show contr fabric trace fgid-agg err loc 0/RP1/CPU0 show 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/SP show 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/SP show 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/SP show 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/SP show 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,MON 0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON 0/1/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON 0/1/4 MSC(SPA) 4XOC48-POS OK PWR,NSHUT,MON 0/1/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON 0/4/SP DRP(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/4/CPU0 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON 0/4/CPU1 DRP DRP-ACC IOS XR RUN PWR,NSHUT,MON 0/6/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/6/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON 0/6/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON 0/6/4 MSC(SPA) 8XOC3/OC12-POS OK PWR,NSHUT,MON 0/6/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON 0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON 0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON 0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON MSC: 0/1/CPU0 is running DRP: 0/4/CPU0 is running MSC: 0/6/CPU0 is running RP: 0/RP0/CPU0 is running RP: 0/RP1/CPU0 is running SM: 0/SM0/SP is running SM: 0/SM1/SP is running SM: 0/SM2/SP is running SM: 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 . . .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 [ client | group | rack ] [ location node-id ] { terminal [page] | file send-to [background] [ compressed | uncompressed ] }
Syntax Description
client
(Optional) Displays the client tech-support information.
group
(Optional) Displays the group tech-support information.
rack
(Optional) Displays the number of racks
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
terminal
Displays the 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.
sent-to
Name of the file. The following valid options are listed:
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
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 gsp command:
- show gsp group addresses
- show gsp group admin addresses
- show gsp group lr-control addresses
- show gsp group gid 0
- show gsp group gid 1000
- show gsp group gid 2000
- show gsp memory
- 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
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 gsp command output:
RP/0/0/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 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 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 :0show tech-support igmp snooping
To automatically run show commands that display debugging information specific to igmp snooping, use the show tech-support igmp snooping command in the EXEC mode.
Syntax Description
file
(Optional) Specifies that the command output is saved to a specified file.
send-to
(Optional) Name of the file. The following valid options are listed:
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
terminal
Specifies that the command output is displayed on the terminal.
page
(Optional) Specifies that the command output is displayed one 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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
This command generates igmp snooping debug 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 igmp snooping command:
- show version
- show running-config sanitize
- show redundancy
- show logging
- show platform
- 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)
See the Cisco IOS XR Software command references for information about these commands and descriptions of their command output. The Cisco IOS XR Software 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 a truncated version of the show tech-support igmp snooping command output:
RP/0/0/CPU0:router# show tech-support igmp snooping terminal ------------------------------------------------------------------------------- show tech-support igmp snooping ------------------------------------------------------------------------------- -------------------------------- show version --------------------------------- Cisco IOS XR Software, Version 3.9.0[00] Copyright (c) 2009 by Cisco Systems, Inc. ROM: System Bootstrap, Version 1.1(20090521:183759) [ASR9K ROMMON], MCAST-6 uptime is 6 days, 20 hours, 50 minutes System image file is "bootflash:disk0/asr9k-os-mbi-3.9.0/mbiasr9k-rp.vm" cisco ASR9K Series (MPC8641D) processor with 4194304K bytes of memory. MPC8641D processor at 1333MHz, Revision 2.2 2 Management Ethernet 45 GigabitEthernet 219k bytes of non-volatile configuration memory. 975M bytes of compact flash card. 33994M bytes of hard disk. 1605616k bytes of disk0: (Sector size 512 bytes). 1605616k bytes of disk1: (Sector size 512 bytes). Configuration register on node 0/RSP0/CPU0 is 0x1922 Boot device on node 0/RSP0/CPU0 is disk0: Package active on node 0/RSP0/CPU0: asr9k-scfclient, V 3.9.0[00], Cisco Systems, at disk0:asr9k-scfclient-3.9.0 Built on Mon Dec 14 12:38:43 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-diags, V 3.9.0[00], Cisco Systems, at disk0:asr9k-diags-3.9.0 Built on Mon Dec 14 12:38:44 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-mcast, V 3.9.0[00], Cisco Systems, at disk0:asr9k-mcast-3.9.0 Built on Mon Dec 14 13:33:02 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-mpls, V 3.9.0[00], Cisco Systems, at disk0:asr9k-mpls-3.9.0 Built on Mon Dec 14 13:31:50 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-rout, V 3.9.0[00], Cisco Systems, at disk0:asr9k-rout-3.9.0 Built on Mon Dec 14 12:38:56 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-lc, V 3.9.0[00], Cisco Systems, at disk0:asr9k-lc-3.9.0 Built on Mon Dec 14 13:28:31 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-fwdg, V 3.9.0[00], Cisco Systems, at disk0:asr9k-fwdg-3.9.0 Built on Mon Dec 14 12:34:50 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-admin, V 3.9.0[00], Cisco Systems, at disk0:asr9k-admin-3.9.0 Built on Mon Dec 14 12:29:39 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-base, V 3.9.0[00], Cisco Systems, at disk0:asr9k-base-3.9.0 Built on Mon Dec 14 12:32:17 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-os-mbi, V 3.9.0[00], Cisco Systems, at disk0:asr9k-os-mbi-3.9.0 Built on Mon Dec 14 12:12:19 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 Boot device on node 0/1/CPU0 is mem: Package active on node 0/1/CPU0: asr9k-scfclient, V 3.9.0[00], Cisco Systems, at disk0:asr9k-scfclient-3.9.0 Built on Mon Dec 14 12:38:43 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-diags, V 3.9.0[00], Cisco Systems, at disk0:asr9k-diags-3.9.0 Built on Mon Dec 14 12:38:44 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-mcast, V 3.9.0[00], Cisco Systems, at disk0:asr9k-mcast-3.9.0 Built on Mon Dec 14 13:33:02 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-mpls, V 3.9.0[00], Cisco Systems, at disk0:asr9k-mpls-3.9.0 Built on Mon Dec 14 13:31:50 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-lc, V 3.9.0[00], Cisco Systems, at disk0:asr9k-lc-3.9.0 Built on Mon Dec 14 13:28:31 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-fwdg, V 3.9.0[00], Cisco Systems, at disk0:asr9k-fwdg-3.9.0 Built on Mon Dec 14 12:34:50 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-admin, V 3.9.0[00], Cisco Systems, at disk0:asr9k-admin-3.9.0 Built on Mon Dec 14 12:29:39 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-base, V 3.9.0[00], Cisco Systems, at disk0:asr9k-base-3.9.0 Built on Mon Dec 14 12:32:17 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-os-mbi, V 3.9.0[00], Cisco Systems, at disk0:asr9k-os-mbi-3.9.0 Built on Mon Dec 14 12:12:19 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 Boot device on node 0/2/CPU0 is mem: Package active on node 0/2/CPU0: asr9k-scfclient, V 3.9.0[00], Cisco Systems, at disk0:asr9k-scfclient-3.9.0 Built on Mon Dec 14 12:38:43 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-diags, V 3.9.0[00], Cisco Systems, at disk0:asr9k-diags-3.9.0 Built on Mon Dec 14 12:38:44 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-mcast, V 3.9.0[00], Cisco Systems, at disk0:asr9k-mcast-3.9.0 Built on Mon Dec 14 13:33:02 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-mpls, V 3.9.0[00], Cisco Systems, at disk0:asr9k-mpls-3.9.0 Built on Mon Dec 14 13:31:50 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-lc, V 3.9.0[00], Cisco Systems, at disk0:asr9k-lc-3.9.0 Built on Mon Dec 14 13:28:31 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-fwdg, V 3.9.0[00], Cisco Systems, at disk0:asr9k-fwdg-3.9.0 Built on Mon Dec 14 12:34:50 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-admin, V 3.9.0[00], Cisco Systems, at disk0:asr9k-admin-3.9.0 Built on Mon Dec 14 12:29:39 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-base, V 3.9.0[00], Cisco Systems, at disk0:asr9k-base-3.9.0 Built on Mon Dec 14 12:32:17 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-os-mbi, V 3.9.0[00], Cisco Systems, at disk0:asr9k-os-mbi-3.9.0 Built on Mon Dec 14 12:12:19 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 ---------------------- show running-config igmp snooping ---------------------- igmp snooping profile prof1 ttl-check disable router-alert-check disable ! ----------------- show igmp snooping summary statistics debug ----------------- Bridge Domains: 1 IGMP Snooping Bridge Domains: 1 Ports: 2 IGMP Snooping Ports: 1 Mrouters: 0 STP Forwarding Ports: 0 IGMP Groups: 0 Member Ports: 0 IGMP Source Groups: 0 Static/Include/Exclude: 0/0/0 Member Ports (Include/Exclude): 0/0 Traffic Statistics (elapsed time since last cleared 6d20h): Received Reinjected Generated Messages: 0 0 0 IGMP General Queries: 0 0 0 IGMP Group Specific Queries: 0 0 0 IGMP G&S Specific Queries: 0 0 0 IGMP V2 Reports: 0 0 0 IGMP V3 Reports: 0 0 0 IGMP V2 Leaves: 0 0 0 IGMP Global Leaves: 0 - 0 PIM Hellos: 0 0 - Rx Packet Treatment: Packets Flooded: 0 Packets Forwarded To Members: 0 Packets Forwarded To Mrouters: 0 Packets Consumed: 0 Rx Errors: None Rx Other: None Tx Errors: None L2FIB Statistics (elapsed time since last cleared 6d20h): BD Created Notifications: 2 BD Deleted Notifications: 1 EFP Added Notifications: 9 EFP Removed Notifications: 2 EFP STP Change Notifications: 4 BD Topology Change Notifications: 0 BD Added: 2 BD Deleted: 1 BD Profile Change: 0 BD Profile Added: 0 BD Profile Removed: 0 BD Batch Start: 4 BD Batch End: 4 BD Mark: 0 BD Sweep: 1 EFP Added: 4 EFP Deleted: 2 EFP Profile Changed: 0 EFP Profile Unchanged: 5 EFP Profile Added: 0 EFP Profile Removed: 0 EFP Oper State To Up: 3 EFP Oper State To Down: 1 EFP STP State To Forwarding: 2 EFP STP State To Blocked: 0 EFP STP State To Not Participating: 0 EFP Batch Start: 10 EFP Batch End: 10 EFP Mark: 0 EFP Sweep: 1 L2FIB Replay: 3 Mroute Msgs Sent: 4 Cfg Msgs Sent: 8 BDXC Send: 8 Errors: None Network Statistics (elapsed time since last cleared 6d20h): Socket Event: 0 Network Connection Open Event: 2 Network Connection Close Event: 0 Packet Event: 2 Packet Event Disconnect: 0 Packet Event Empty: 0 Packet Event Empty Watermark: 2 Rx IGMP Packet Attempt: 0 Rx IGMP Packet Success: 0 Rx PIM Packet Attempt: 0 Rx PIM Packet Success: 0 Tx IGMP Packet Attempt: 0 Tx IGMP Packet Success: 0 Errors: None Internal Data: Ltrace: Enabled Error Debug: Disabled Other Debug: Disabled System Mac: 00:00:00:00:00:00 Internal Statistics (elapsed time since last cleared 6d20h): None ---------- show igmp snooping bridge-domain detail statistics debug ----------- Bridge Domain Profile Act Ver #Ports #Mrtrs #Grps #SGs ------------- ------- --- --- ------ ------ ----- ---- bg:bd prof1 Y -- 2 0 0 0 Profile Configured Attributes: System IP Address: 0.0.0.0 Minimum Version: 2 Report Suppression: Enabled Unsolicited Report Interval: 1000 (milliseconds) TCN Query Solicit: Disabled TCN Flood: Enabled TCN Flood Query Count: 2 Router Alert Check: Disabled TTL Check: Disabled Internal Querier Support: Disabled Querier Query Interval: 60 (seconds) Querier LMQ Interval: 1000 (milliseconds) Querier LMQ Count: 2 Querier Robustness: 2 Querier: Not Present Mrouter Ports: 0 STP Forwarding Ports: 0 Groups: 0 Member Ports: 0 V3 Source Groups: 0 Static/Include/Exclude: 0/0/0 Member Ports (Include/Exclude): 0/0 XID: BD:0x0 Creation Time: 1d00h Snooping Creation Time: 1d00h Flood Mode: Disabled Star Star Mroute PD Data: Size: 4 Data: 0x00 0x00 0x80 0x81 Client L2Info: None MTU: 1400 Traffic Statistics (elapsed time since last cleared 5d20h): Received Reinjected Generated Messages: 0 0 0 IGMP General Queries: 0 0 0 IGMP Group Specific Queries: 0 0 0 IGMP G&S Specific Queries: 0 0 0 IGMP V2 Reports: 0 0 0 IGMP V3 Reports: 0 0 0 IGMP V2 Leaves: 0 0 0 IGMP Global Leaves: 0 - 0 PIM Hellos: 0 0 - Rx Packet Treatment: Packets Flooded: 0 Packets Forwarded To Members: 0 Packets Forwarded To Mrouters: 0 Packets Consumed: 0 Rx Errors: None Rx Other: None Tx Errors: Noneshow tech-support install
To 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.
Syntax Description
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).
file
(Optional) Specifies that the command output is saved to a specified file.
send-to
(Optional) Name of the file. The following valid options are listed:
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
rack
(Optional) Displays the list of racks.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
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 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
- 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)
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 install command output:
RP/0/0/CPU0:router# show tech-support install page ------------------------------------------------------------------------------- SDR show install tech-support ------------------------------------------------------------------------------- ---------------------------- 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. ROM: System Bootstrap, Version 1.43(20061109:045749) [CRS-1 ROMMON], CRS-1 uptime is 1 week, 3 days, 16 hours, 46 minutes System 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 0x102 Boot 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 ------------------------ 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. . . .show tech-support l2tp
To automatically run show commands that display information specific to Layer 2 Tunnel Protocol (L2TP) technical support, use the show tech-support l2tp command in EXEC mode.
show tech-support l2tp { file send-to [background] [ compressed | uncompressed ] | terminal [page] }
Syntax Description
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
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.
terminal
Specifies that the command output is displayed on the terminal.
page
(Optional) Specifies that the command output is displayed one 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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
This command collects relevant data for Layer 2 tunneling protocol-related issues 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.
See the Cisco IOS XR Software command references for information about these commands and descriptions of their command output. The Cisco IOS XR Software 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 l2tp command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support l2tp terminal page ------------------------------------------------------------------------------- show tech-support l2tp (Detailed output with event traces) ------------------------------------------------------------------------------- -------------------------- show l2tp session detail --------------------------- --------------------------- show l2tp tunnel detail --------------------------- ----------------------------- show l2tp internal ------------------------------ L2TP Internal information: L2X information: Rx high water mark : 0 Ave msg process usecs : 0 Num rx messages : 0 Num tx messages : 0 Num reordered msgs : 0 Max reorder deviation : 0 Num ooo msgs : 0 Num rx path drops : 0 Num rx q overflow drops : 0 Num buffered msgs : 0 L2TUN information: Ave msg process usecs : 0 Num rx messages : 1 Num tx messages : 1 ---------------------- show l2tp counters control tunnel ---------------------- Global L2TP tunnel control message statistics: XMIT RE-XMIT RCVD DROP ========== ========== ========== ========== ZLB 0 0 0 0 SCCRQ 0 0 0 0 SCCRP 0 0 0 0 SCCCN 0 0 0 0 StopCCN 0 0 0 0 Hello 0 0 0 0 OCRQ 0 0 0 0 OCRP 0 0 0 0 OCCN 0 0 0 0 ICRQ 0 0 0 0 ICRP 0 0 0 0 ICCN 0 0 0 0 CDN 0 0 0 0 WEN 0 0 0 0 SLI 0 0 0 0 EXP ACK 0 0 0 0 FSQ 0 0 0 0 FSR 0 0 0 0 SRRQ 0 0 0 0 SRRP 0 0 0 0 CiscoACK 0 0 0 0 Total 0 0 0 0 -------------------- show l2tp counters control tunnel all -------------------- -------------- show l2tp counters control tunnel authentication --------------- L2TPv3 Tunnel Authentication Statistics: ------------ show l2tp counters control session fsm state current ------------- Current State Count ====================== Init - Idle - Wt-Sock - Wt-CC - Proc-ICRQ - Wt-Rx-ICCN - Proc-ICCN - Wt-Tx-ICRQ - Wt-Tx-ICRP - Wt-Tx-ICCN - Wt-Rx-ICRP - Proc-ICRP - established - Dead - ----------- show l2tp counters control session fsm state transition ----------- Old State New State Idle Wt Wt Proc Wt Proc Wt Wt Wt Wt Proc esta Dead --More-- Building configuration... Sock CC ICRQ Rx ICCN Tx Tx Tx Rx ICRP ICCN ICRQ ICRP ICCN ICRP ================================================================= Init - - - - - - - - - - - - - Idle - - - - - - - - - - - - - Wt-Sock - - - - - - - - - - - - - Wt-CC - - - - - - - - - - - - - Proc-ICRQ - - - - - - - - - - - - - Wt-Rx-ICCN - - - - - - - - - - - - - Proc-ICCN - - - - - - - - - - - - - Wt-Tx-ICRQ - - - - - - - - - - - - - Wt-Tx-ICRP - - - - - - - - - - - - - Wt-Tx-ICCN - - - - - - - - - - - - - Wt-Rx-ICRP - - - - - - - - - - - - - Proc-ICRP - - - - - - - - - - - - - establishe - - - - - - - - - - - - - Dead - - - - - - - - - - - - - ---------------- show l2tp counters control session fsm event ----------------- Event State event occurred in Idle Wt Wt Proc Wt Proc Wt Wt Wt Wt Proc esta Dead Sock CC ICRQ Rx ICCN Tx Tx Tx Rx ICRP ICCN ICRQ ICRP ICCN ICRP ================================================================= Invalid - - - - - - - - - - - - - CC-Up - - - - - - - - - - - - - CC-Down - - - - - - - - - - - - - Sock-Ready - - - - - - - - - - - - - Sock-Down - - - - - - - - - - - - - Sock-Error - - - - - - - - - - - - - App-Conn - - - - - - - - - - - - - App-Disc - - - - - - - - - - - - - Local-Cont - - - - - - - - - - - - - Local-Up - - - - - - - - - - - - - Local-Down - - - - - - - - - - - - - DP-Setup - - - - - - - - - - - - - Rx-ICRQ - - - - - - - - - - - - - ICRQ-OK - - - - - - - - - - - - - ICRQ-ERR - - - - - - - - - - - - - Rx-ICRP - - - - - - - - - - - - - ICRP-OK - - - - - - - - - - - - - ICRP-ERR - - - - - - - - - - - - - Rx-ICCN - - - - - - - - - - - - - ICCN-OK - - - - - - - - - - - - - ICCN-ERR - - - - - - - - - - - - - Rx-CDN - - - - - - - - - - - - - Establishe - - - - - - - - - - - - - Shut - - - - - - - - - - - - - Destroy - - - - - - - - - - - - - --------------------------- show processes l2tp_mgr --------------------------- Job Id: 263 PID: 405734 Executable path: /disk0/hfr-fwdg-3.6.0.16I/bin/l2tp_mgr Instance #: 1 Version ID: 00.00.0000 Respawn: ON Respawn count: 1 Max. spawns per minute: 12 Last started: Thu Oct 11 19:25:05 2007 Process state: Run Package state: Normal core: TEXT SHAREDMEM MAINMEM Max. core: 0 Level: 999 Placement: ON startup_path: /pkg/startup/l2tp.startupshow tech-support l2vpn
To automatically run show commands that display information specific to Layer 2 Virtual Private Network (L2VPN) debugging, use the show tech-support l2vpn command in EXEC mode.
show tech-support l2vpn { file send-to [background] [ compressed | uncompressed ] | terminal [page] [rack] }
Syntax Description
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
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.
terminal
Specifies that the command output is displayed on the terminal.
page
(Optional) Specifies that the command output is displayed one 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.
rack
(Optional) Displays the list of racks.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
This command collects information for Layer 2 VPN related issues 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.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 l2vpn command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support l2vpn terminal page ------------------------------------------------------------------------------- show tech-support l2vpn (Detail with Event traces) ------------------------------------------------------------------------------- -------------------------------- show version --------------------------------- Cisco IOS XR Software, Version 3.6.0.16I[SIT1_IMAGE1] Copyright (c) 2007 by Cisco Systems, Inc. ROM: System Bootstrap, Version 1.48(20070928:224557) [CRS-1 ROMMON], P1_CRS-8 uptime is 4 days, 20 hours, 49 minutes System image file is "disk0:hfr-os-mbi-3.6.0.16I/mbihfr-rp.vm" cisco CRS-8/S (7457) processor with 4194304K bytes of memory. 7457 processor at 1197Mhz, Revision 1.2 4 T3 Port controller(s) 20 Packet over SONET/SDH network interface(s) 20 SONET/SDH Port controller(s) 4 Serial network interface(s) 4 Ethernet/IEEE 802.3 interface(s) 16 GigabitEthernet/IEEE 802.3 interface(s) 1019k 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 0x102 Boot device on node 0/1/CPU0 is mem: Package active on node 0/1/CPU0: hfr-sbc, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-sbc-3.6.0.16I Built on Tue Oct 2 15:07:32 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-pagent, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-pagent-3.6.0.I Built on Tue Oct 2 15:58:47 DST 2007 By iox42.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-fpd, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-fpd-3.6.0.16I Built on Tue Oct 2 14:48:41 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-diags, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-diags-3.6.0.16I Built on Tue Oct 2 14:48:32 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-mcast, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-mcast-3.6.0.16I Built on Tue Oct 2 14:26:29 DST 2007 By sjce-gf-061.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-mpls, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-mpls-3.6.0.16I Built on Tue Oct 2 14:22:48 DST 2007 By sjce-gf-061.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-lc, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-lc-3.6.0.16I Built on Tue Oct 2 14:02:24 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-fwdg, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-fwdg-3.6.0.16I Built on Tue Oct 2 13:57:12 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-admin, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-admin-3.6.0.16I Built on Tue Oct 2 13:53:07 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-base, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-base-3.6.0.16I Built on Tue Oct 2 13:51:10 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-os-mbi, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-os-mbi-3.6.0.I Built on Tue Oct 2 13:28:38 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 Configuration register on node 0/4/CPU0 is 0x102 Boot device on node 0/4/CPU0 is disk0: Package active on node 0/4/CPU0: hfr-sbc, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-sbc-3.6.0.16I Built on Tue Oct 2 15:07:32 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-pagent, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-pagent-3.6.0.I Built on Tue Oct 2 15:58:47 DST 2007 By iox42.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-fpd, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-fpd-3.6.0.16I Built on Tue Oct 2 14:48:41 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-doc, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-doc-3.6.0.16I Built on Tue Oct 2 14:48:52 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-diags, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-diags-3.6.0.16I Built on Tue Oct 2 14:48:32 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-mgbl, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-mgbl-3.6.0.16I Built on Tue Oct 2 14:20:33 DST 2007 By sjce-gf-061.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-mcast, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-mcast-3.6.0.16I Built on Tue Oct 2 14:26:29 DST 2007 By sjce-gf-061.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-mpls, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-mpls-3.6.0.16I Built on Tue Oct 2 14:22:48 DST 2007 By sjce-gf-061.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-rout, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-rout-3.6.0.16I Built on Tue Oct 2 14:06:14 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-k9sec, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-k9sec-3.6.0.16I Built on Tue Oct 2 14:43:56 DST 2007 By sjce-gf-074.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-lc, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-lc-3.6.0.16I Built on Tue Oct 2 14:02:24 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-fwdg, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-fwdg-3.6.0.16I Built on Tue Oct 2 13:57:12 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-admin, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-admin-3.6.0.16I Built on Tue Oct 2 13:53:07 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-base, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-base-3.6.0.16I Built on Tue Oct 2 13:51:10 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-os-mbi, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-os-mbi-3.6.0.I Built on Tue Oct 2 13:28:38 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 Configuration register on node 0/4/CPU1 is 0x102 Boot device on node 0/4/CPU1 is disk0: Package active on node 0/4/CPU1: hfr-sbc, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-sbc-3.6.0.16I Built on Tue Oct 2 15:07:32 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-pagent, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-pagent-3.6.0.I Built on Tue Oct 2 15:58:47 DST 2007 By iox42.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-fpd, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-fpd-3.6.0.16I Built on Tue Oct 2 14:48:41 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-doc, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-doc-3.6.0.16I Built on Tue Oct 2 14:48:52 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-diags, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-diags-3.6.0.16I Built on Tue Oct 2 14:48:32 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-mgbl, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-mgbl-3.6.0.16I Built on Tue Oct 2 14:20:33 DST 2007 By sjce-gf-061.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-mcast, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-mcast-3.6.0.16I Built on Tue Oct 2 14:26:29 DST 2007 By sjce-gf-061.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-mpls, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-mpls-3.6.0.16I Built on Tue Oct 2 14:22:48 DST 2007 By sjce-gf-061.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-rout, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-rout-3.6.0.16I Built on Tue Oct 2 14:06:14 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-k9sec, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-k9sec-3.6.0.16I Built on Tue Oct 2 14:43:56 DST 2007 By sjce-gf-074.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-lc, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-lc-3.6.0.16I Built on Tue Oct 2 14:02:24 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-fwdg, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-fwdg-3.6.0.16I Built on Tue Oct 2 13:57:12 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-admin, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-admin-3.6.0.16I Built on Tue Oct 2 13:53:07 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-base, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-base-3.6.0.16I Built on Tue Oct 2 13:51:10 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-os-mbi, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-os-mbi-3.6.0.I Built on Tue Oct 2 13:28:38 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 Configuration register on node 0/6/CPU0 is 0x102 Boot device on node 0/6/CPU0 is mem: Package active on node 0/6/CPU0: hfr-sbc, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-sbc-3.6.0.16I Built on Tue Oct 2 15:07:32 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-pagent, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-pagent-3.6.0.I Built on Tue Oct 2 15:58:47 DST 2007 By iox42.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-fpd, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-fpd-3.6.0.16I Built on Tue Oct 2 14:48:41 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-diags, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-diags-3.6.0.16I Built on Tue Oct 2 14:48:32 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-mcast, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-mcast-3.6.0.16I Built on Tue Oct 2 14:26:29 DST 2007 By sjce-gf-061.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8show tech-support lrd
To automatically run show commands that display information specific to logical router daemon (LRD) debugging, use the show tech-support lrd command in EXEC mode.
show tech-support lrd { file send-to [background] [ compressed | uncompressed ] | terminal [page] | location { node-id | all } [rack] }
Syntax Description
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
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.
terminal
Specifies that the command output is displayed on the terminal.
page
(Optional) Specifies that the command output is displayed one 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.
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
all
(Optional) Specifies all locations.
rack
(Optional) Displays the list of racks.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 lrd command for the LRD debugging, which controls the Secure Domain Router (SDR) architecture. The system always has at least one SDR at any time. It collects relevant information when issues arise with the SDR management within the system. This command 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.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 lrd command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support lrd terminal page ------------------------------------------------------------------------------- show tech-support lrd ------------------------------------------------------------------------------- lrdbg 'i' getting CONFIG INFO Starting lrdbg commands for local node. node_name = node0_RP0_CPU0 chan_name is /net/node0_RP0_CPU0/dev/lrd_local Local nodeid=513 Local lrname=Owner Local lrid = 0 lrdbg: Successfully connected to channel /net/node0_RP0_CPU0/dev/lrd_local Starting lrdbg commands for node = node0_RP0_CPU0 lrid = 0 DLRSC Info for Node = node0_RP0_CPU0 Nodeid = 0x201 lrid = 0 We are the dLRSC, Backup dLRSC is 0x211 --More-- liblrd_dl_node_state_0.dll 0.0 liblrd_dl_sw_state_0.dll 0.0 liblrd_dl_fwd_ldr_0.dll 0.0 liblrd_alpha_fwd.dll 1.0 liblrd_envmon_fwd.dll 1.0 liblrd_invmgr_fwd.dll 1.0 Inventory Info for Node = node0_RP0_CPU0 lrid = 0 Success: node_count=6, ready=1 node=0x11, type=2, memsize=256, cpus=1, speed=100, sw_state=6, red_state=0 lr_n0 node=0x41, type=1, memsize=256, cpus=1, speed=100, sw_state=6, red_state=1 lr_nf node=0x42, type=1, memsize=256, cpus=1, speed=100, sw_state=6, red_state=1 lr_nf node=0x61, type=2, memsize=256, cpus=1, speed=100, sw_state=6, red_state=0 lr_n0 node=0x201, type=0, memsize=256, cpus=1, speed=100, sw_state=6, red_state=1 lr_1 node=0x211, type=0, memsize=256, cpus=1, speed=100, sw_state=6, red_state=2 lr_1 LR name Info for Node = node0_RP0_CPU0 dSC node: 0/RP0/CPU0 standby dSC node: 0/RP1/CPU0 LRs (Configured, pre-existing) basic info: Name LRid dLRSC backup_dLRSC --------------------------------------------------------------------- Owner 0 0/RP0/CPU0 0/RP1/CPU0 LRs (Configured, pre-existing) basic info: Lr-Names LRid dLRSC StbydLRSC Primary Primary1 McastAddr -------------------------------------------------------------------------------- Owner 0 0/RP0/CPU0 0/RP1/CPU0 0/RP0/CPU0 0/RP1/CPU0 0 0 Client Vector for Node = node0_RP0_CPU0 Received 23 currently connected lrd clients PID op eFLAGS cFLAGS _______________________________ 168027 0x1 0x4 0x3 77863 0x11 0x204 0x1 81963 0x10 0x200 0x0 168024 0x2 0x0 0x0 168026 0x2 0x0 0x0 200800 0x1 0x4 0x1f 204909 0x1 0x4 0xb 209006 0x23 0x84 0xb 385148 0x1 0x4 0x7 385149 0x1 0x4 0x7 381047 0x41 0x25 0x3 381043 0x1 0x4 0x3 381041 0x1 0x4 0x7 397456 0x1 0x4 0x3 397485 0x1 0x14 0x4 397484 0x1 0x14 0x4 397498 0x1 0x4 0x4 405725 0x1 0x4 0x7 405735 0x1 0x4 0x4 405744 0x40 0x1 0x0 434434 0x1 0x4 0x7 434435 0x1 0x4 0x7 434433 0x1 0x4 0x7 DLL loaded for Node = node0_RP0_CPU0 dll name version _________________________________________________ Node State Info for Node = node0_RP0_CPU0 Type Node Nodeid Prev State Cur State LRid (PD c) ------------------------------------------------------------------------------- LC(2) 0/1/CPU0 0x11 RUNNING_MBI(5) RUNNING_ENA(6) 0 (5242) DRP(1) 0/4/CPU0 0x41 RUNNING_MBI(5) RUNNING_ENA(6) 0 (119)) DRP(1) 0/4/CPU1 0x42 RUNNING_MBI(5) RUNNING_ENA(6) 0 (119)) LC(2) 0/6/CPU0 0x61 RUNNING_MBI(5) RUNNING_ENA(6) 0 (5242) RP(0) 0/RP0/CPU0 0x201 RUNNING_MBI(5) RUNNING_ENA(6) 0 (19) ) RP(0) 0/RP1/CPU0 0x211 PRESENT(1) RUNNING_ENA(6) 0 (19) ) Sw State Info for Node = node0_RP0_CPU0 ------------------------------------------------------------------------------- Type Node Nodeid PrevState CurState Red-Role/ Partner Par (BAND) (BAND) Red-State node nae ------------------------------------------------------------------------------- LC(2) 0/1/CPU0 0x11 INFRA FINAL Active/Down 0xffffffff DRP(1) 0/4/CPU0 0x41 INFRA FINAL Active/Down 0xffffffff DRP(1) 0/4/CPU1 0x42 INFRA FINAL Active/Down 0xffffffff LC(2) 0/6/CPU0 0x61 INFRA FINAL Active/Down 0xffffffff RP(0) 0/RP0/CPU0 0x201 INFRA FINAL Active/Down 0x211 RP(0) 0/RP1/CPU0 0x211 INFRA FINAL Standby/Down 0x201 Config Info for Node = node0_RP0_CPU0 LRd basic configuration data: __________________________________________________ node : 0x201 lr_id : 0 lr_name : Owner dsc node : 0x201 dsc partner node : 0x211 dlrsc node : 0x201 dlrsc partner node : 0x211 am I dSC : Yes am I STBY dSC : NO am I dLRSC : Yes am I STBY dLRSC : NO primary node : 0x201 primary node1 : 0x211 mcast addr : 0x0 mac addr : 0x01563c0b00 __________________________________________________ ADMIN CONFIG is APPLIED __________________________________________________ lrd log file path is /net/node0_RP0_CPU0/tmp/lrd.log ------------LRD LOG START FOR NODE node0_RP0_CPU0------------ 10/11 10:19:16.309 1 main: ---LRD starting--- 10/11 10:19:16.325 1 main: **********LRD on Node=0x201********** 10/11 10:19:16.327 1 main: mutex init for inv_mutex DONE. 10/11 10:19:17.772 1 lrd_get_dsc: dSC = 201 10/11 10:19:17.774 1 main: We are dSC. 10/11 10:19:17.776 1 main: Registering with SSM as service provider. Once ------------------------------------------------------------------------------- show tech-support lrd ------------------------------------------------------------------------------- ++++ lrdbg -I -1: lrd server inventory [17:21:35.603 UTC Fri Dec 18 2009] +++++ Success: node_count=8, ready=1 node=0x1(0/RSP0/CPU0), type=0, memsize=256, cpus=1, speed=100, sw_state=6, red_state=1 lr_name=Owner pd_card_type=0x100302, partner=0x11 node=0x11(0/RSP1/CPU0), type=0, memsize=256, cpus=1, speed=100, sw_state=6, red_state=2 lr_name=Owner pd_card_type=0x100302, partner=0x1 node=0x4a0(0/FT0/SP), type=5, memsize=256, cpus=1, speed=100, sw_state=1, red_state=0 lr_name=Owner pd_card_type=0x0 node=0x4b0(0/FT1/SP), type=5, memsize=256, cpus=1, speed=100, sw_state=1, red_state=0 lr_name=Owner pd_card_type=0x0 node=0x821(0/0/CPU0), type=2, memsize=256, cpus=1, speed=100, sw_state=6, red_state=0 lr_name=Owner pd_card_type=0x30207 node=0x841(0/2/CPU0), type=2, memsize=256, cpus=1, speed=100, sw_state=6, red_state=0 lr_name=Owner pd_card_type=0x30207 node=0x851(0/3/CPU0), type=2, memsize=256, cpus=1, speed=100, sw_state=0, red_state=0 lr_name=Owner pd_card_type=0x3020a node=0xe10(0/PM1/SP), type=5, memsize=256, cpus=1, speed=100, sw_state=1, red_state=0 lr_name=Owner pd_card_type=0xf00188 ---- lrdbg -I -1: lrd server inventory [17:21:36.023 UTC Fri Dec 18 2009] ----- +++ lrdbg -L local_node_lrd: local LR config info [17:21:36.215 UTC Fri Dec 18 2009] ++++ lrdbg 'i' getting CONFIG INFO Starting lrdbg commands for node = 0/RSP0/CPU0 lrdbg: temp_node_name copied is 0/RSP0/CPU0 node_name = node0_RSP0_CPU0 chan_name = /net/node0_RSP0_CPU0/dev/lrd_local user_nodeid=1 user_lrname = Owner Local nodeid=1 Local lrname=Owner User nodeid=1 User lrname = Owner User lrid=0 lrdbg: Successfully connected to channel /net/node0_RSP0_CPU0/dev/lrd_local Starting lrdbg commands for node = node0_RSP0_CPU0 lrid = 0 DLRSC Info for Node = node0_RSP0_CPU0 Nodeid = 0x1 lrid = 0 We are the dLRSC, Backup dLRSC is 0x11 Inventory Info for Node = node0_RSP0_CPU0 lrid = 0 Success: node_count=5, ready=1 node=0x1(0/RSP0/CPU0), type=0, memsize=256, cpus=1, speed=100, sw_state=6, red_state=1 lr_name=Owner pd_card_type=0x100302, partner=0x11 node=0x11(0/RSP1/CPU0), type=0, memsize=256, cpus=1, speed=100, sw_state=6, red_state=2 lr_name=Owner pd_card_type=0x100302, partner=0x1 node=0x821(0/0/CPU0), type=2, memsize=256, cpus=1, speed=100, sw_state=6, red_state=0 lr_name=Owner pd_card_type=0x30207 node=0x841(0/2/CPU0), type=2, memsize=256, cpus=1, speed=100, sw_state=6, red_state=0 lr_name=Owner pd_card_type=0x30207 node=0x851(0/3/CPU0), type=2, memsize=256, cpus=1, speed=100, sw_state=0, red_state=0 lr_name=Owner pd_card_type=0x3020a LR name Info for Node = node0_RSP0_CPU0 dSC node: 0/RSP0/CPU0 standby dSC node: 0/RSP1/CPU0 LRs (Configured, pre-existing) basic info: Name LRid dLRSC backup_dLRSC --------------------------------------------------------------------- Owner 0 0/RSP0/CPU0 0/RSP1/CPU0 LRs (Configured, pre-existing) basic info: Lr-Names LRid dLRSC StbydLRSC Primary Primary1 McastAddr MacAddr ----------------------------------------------------------------------------------------------- Owner 0 0/RSP0/CPU0 0/RSP1/CPU0 0/RSP0/CPU0 0/RSP1/CPU0 0 0211bfcfe7e Client Vector for Node = node0_RSP0_CPU0 Received 25 currently connected lrd clients PID op eFLAGS cFLAGS _______________________________ 213071 0x40 0x1 0x0 213090 0x1 0x4 0x3 163876 0x11 0x204 0x1 176173 0x10 0x200 0x0 184381 0x1 0x4 0x1 213089 0x2 0x0 0x0 208966 0x23 0x84 0x1 229494 0x1 0x4 0x1 221289 0x1 0x4 0x1f 241796 0x41 0x15 0x3 245905 0x40 0x1 0x0 245902 0x1 0x14 0x7 245901 0x1 0x14 0x7 237682 0x1 0x4 0x7 237695 0x1 0x4 0x3 245908 0x40 0x1 0x0 245907 0x40 0x1 0x0 213092 0x1 0x14 0x3 254123 0x1 0x14 0x3 254124 0x1 0x4 0x4 262347 0x1 0x4 0x4 262351 0x1 0x14 0x4 270550 0x1 0x4 0x7 254139 0x40 0x1 0x4 270596 0x40 0x1 0x0 DLL loaded for Node = node0_RSP0_CPU0 liblrd_dl_node_state_0.dll 0.0 liblrd_dl_sw_state_0.dll 0.0 liblrd_dl_fwd_ldr_0.dll 0.0 liblrd_alpha_fwd.dll 1.0 liblrd_envmon_fwd.dll 1.0 liblrd_invmgr_fwd.dll 1.0 dll name version _________________________________________________ Node State Info for Node = node0_RSP0_CPU0 Type Node Nodeid Prev State Cur State LRid (PD ctype) (old-lr-id) --------------------------------------------------------------------------------- RP(0) 0/RSP0/CPU0 0x1 RUNNING_MBI(5) RUNNING_ENA(6) 0 (0x100302) (-1) RP(0) 0/RSP1/CPU0 0x11 RUNNING_MBI(5) RUNNING_ENA(6) 0 (0x100302) (-1) LC(2) 0/0/CPU0 0x821 RUNNING_MBI(5) RUNNING_ENA(6) 0 (0x30207) (-1) LC(2) 0/2/CPU0 0x841 RUNNING_MBI(5) RUNNING_ENA(6) 0 (0x30207) (-1) LC(2) 0/3/CPU0 0x851 BRINGDOWN(7) NOT_PRESENT(0) 0 (0x3020a) (-1) Sw State Info for Node = node0_RSP0_CPU0 ----------------------------------------------------------------------------------- Type Node Nodeid PrevState CurState Red-Role/ Partner Pair (BAND) (BAND) Red-State node name ----------------------------------------------------------------------------------- RP(0) 0/RSP0/CPU0 0x1 INFRA FINAL Active/Down 0x11 RP(0) 0/RSP1/CPU0 0x11 INFRA FINAL Standby/Down 0x1 LC(2) 0/0/CPU0 0x821 INFRA FINAL Active/Down 0xffffffff LC(2) 0/2/CPU0 0x841 INFRA FINAL Active/Down 0xffffffff LC(2) 0/3/CPU0 0x851 INFRA -- Unknown/Down 0xffffffff Config Info for Node = node0_RSP0_CPU0 LRd basic configuration data: __________________________________________________ node : 0x1 lr_id : 0 lr_name : Owner dsc node : 0x1 dsc partner node : 0x11 dlrsc node : 0x1 dlrsc partner node : 0x11 am I dSC : Yes am I STBY dSC : NO am I dLRSC : Yes am I STBY dLRSC : NO primary node : 0x1 primary node1 : 0x11 mcast addr : 0x0 mac addr : 0x0211bfcfe7e __________________________________________________ ADMIN CONFIG is APPLIED __________________________________________________ --- lrdbg -L local_node_lrd: local LR config info [17:21:36.695 UTC Fri Dec 18 2009] ---- ++++ lrd_show -I for this SDR-s DSDRSC [17:21:36.846 UTC Fri Dec 18 2009] +++++ Success: node_count=5, ready=1 node=0x1, type=0, memsize=256, cpus=1, speed=100, sw_state=6, red_state=1, lr_name=Owner, pd_card_type=0x100302, partner=0x11 node=0x11, type=0, memsize=256, cpus=1, speed=100, sw_state=6, red_state=2, lr_name=Owner, pd_card_type=0x100302, partner=0x1 node=0x821, type=2, memsize=256, cpus=1, speed=100, sw_state=6, red_state=0, lr_name=Owner, pd_card_type=0x30207 node=0x841, type=2, memsize=256, cpus=1, speed=100, sw_state=6, red_state=0, lr_name=Owner, pd_card_type=0x30207 node=0x851, type=2, memsize=256, cpus=1, speed=100, sw_state=0, red_state=0, lr_name=Owner, pd_card_type=0x3020a ---- lrd_show -I for this SDR-s DSDRSC [17:21:37.240 UTC Fri Dec 18 2009] ----- +++ lrdbg -n -1: lrd server node states [17:21:37.386 UTC Fri Dec 18 2009] ++++ Type Node Nodeid Prev State Cur State LRid (PD ctype) (old-lr-id) --------------------------------------------------------------------------------- RP(0) 0/RSP0/CPU0 0x1 RUNNING_MBI(5) RUNNING_ENA(6) 0 (0x100302) (-1) RP(0) 0/RSP1/CPU0 0x11 RUNNING_MBI(5) RUNNING_ENA(6) 0 (0x100302) (-1) LC(2) 0/0/CPU0 0x821 RUNNING_MBI(5) RUNNING_ENA(6) 0 (0x30207) (-1) LC(2) 0/2/CPU0 0x841 RUNNING_MBI(5) RUNNING_ENA(6) 0 (0x30207) (-1) LC(2) 0/3/CPU0 0x851 BRINGDOWN(7) NOT_PRESENT(0) 0 (0x3020a) (-1) --- lrdbg -n -1: lrd server node states [17:21:37.766 UTC Fri Dec 18 2009] ---- +++ lrdbg -s -1: lrd server software states [17:21:37.914 UTC Fri Dec 18 2009] ++++ ----------------------------------------------------------------------------------- Type Node Nodeid PrevState CurState Red-Role/ Partner Pair (BAND) (BAND) Red-State node name ----------------------------------------------------------------------------------- RP(0) 0/RSP0/CPU0 0x1 INFRA FINAL Active/Down 0x11 RP(0) 0/RSP1/CPU0 0x11 INFRA FINAL Standby/Down 0x1 LC(2) 0/0/CPU0 0x821 INFRA FINAL Active/Down 0xffffffff LC(2) 0/2/CPU0 0x841 INFRA FINAL Active/Down 0xffffffff LC(2) 0/3/CPU0 0x851 INFRA -- Unknown/Down 0xffffffff --- lrdbg -s -1: lrd server software states [17:21:38.294 UTC Fri Dec 18 2009] ---- ++++++++++ show ltrd-trace server [17:21:38.439 UTC Fri Dec 18 2009] ++++++++++ lrd_show_ltrace -F lrd/sntf -TP1 41 wrapping entries (1024 possible, 0 filtered, 41 total) Shelfmgr Notfs Rcvd: R/S/I node_state cardstate adminpower adminshut ---------------------------------------------------------- Dec 14 11:19:58.255 lrd/sntf 0/RSP0/CPU0 t13 : 0/0/1 RUNNING_ENA 6 1 0 Dec 14 11:19:58.259 lrd/sntf 0/RSP0/CPU0 t13 : 0/132/1 PRESENT 1 1 0 Dec 14 11:19:58.264 lrd/sntf 0/RSP0/CPU0 t13 : 0/130/1 BOOTING 3 1 0 Dec 14 11:19:58.267 lrd/sntf 0/RSP0/CPU0 t13 : 0/75/0 PRESENT 1 1 0 Dec 14 11:19:58.268 lrd/sntf 0/RSP0/CPU0 t13 : 0/74/0 PRESENT 1 1 0 Dec 14 11:19:59.320 lrd/sntf 0/RSP0/CPU0 t13 : 0/1/1 RUNNING_MBI 5 1 0 Dec 14 11:19:59.335 lrd/sntf 0/RSP0/CPU0 t13 : 0/225/0 PRESENT 1 1 0 Dec 14 11:19:59.342 lrd/sntf 0/RSP0/CPU0 t13 : 0/132/1 BOOTING 3 1 0 Dec 14 11:19:59.354 lrd/sntf 0/RSP0/CPU0 t13 : 0/132/1 BOOTING 3 1 0 Dec 14 11:20:23.304 lrd/sntf 0/RSP0/CPU0 t13 : 0/130/1 MBI_BOOTING 4 1 0 Dec 14 11:20:23.314 lrd/sntf 0/RSP0/CPU0 t13 : 0/132/1 MBI_BOOTING 4 1 0 Dec 14 11:21:45.710 lrd/sntf 0/RSP0/CPU0 t13 : 0/130/1 RUNNING_MBI 5 1 0 Dec 14 11:21:46.237 lrd/sntf 0/RSP0/CPU0 t13 : 0/132/1 RUNNING_MBI 5 1 0 Dec 14 11:22:01.426 lrd/sntf 0/RSP0/CPU0 t13 : 0/1/1 RUNNING_ENA 6 1 0 Dec 14 11:23:21.504 lrd/sntf 0/RSP0/CPU0 t13 : 0/130/1 RUNNING_ENA 6 1 0 Dec 14 11:23:21.511 lrd/sntf 0/RSP0/CPU0 t13 : 0/132/1 RUNNING_ENA 6 1 0 Dec 14 15:42:37.504 lrd/sntf 0/RSP0/CPU0 t13 : 0/133/1 PRESENT 1 1 0 Dec 14 15:42:37.608 lrd/sntf 0/RSP0/CPU0 t13 : 0/133/1 BOOTING 3 1 0 Dec 14 15:42:37.614 lrd/sntf 0/RSP0/CPU0 t13 : 0/133/1 BOOTING 3 1 0 Dec 14 15:43:02.999 lrd/sntf 0/RSP0/CPU0 t13 : 0/133/1 MBI_BOOTING 4 1 0 Dec 14 15:43:48.408 lrd/sntf 0/RSP0/CPU0 t13 : 0/133/1 RUNNING_MBI 5 1 0 Dec 14 15:45:05.176 lrd/sntf 0/RSP0/CPU0 t13 : 0/133/1 RUNNING_ENA 6 1 0 Dec 15 14:53:15.444 lrd/sntf 0/RSP0/CPU0 t13 : 0/133/1 BRINGDOWN 7 1 0 Dec 15 14:53:15.461 lrd/sntf 0/RSP0/CPU0 t13 : 0/133/1 NOT_PRESENT 0 1 0 ---------- show ltrd-trace server [17:21:38.840 UTC Fri Dec 18 2009] ---------- ++++++++++ show ltrd-trace server [17:21:38.985 UTC Fri Dec 18 2009] ++++++++++ lrd_show_ltrace -F lrd/sntf -TP2 41 wrapping entries (1024 possible, 0 filtered, 41 total) Shelfmgr Notfs processed: nodeid o-LRid LRid o-state n-state pd-ctype pi-ctype --------------------------------------------------------------------- Dec 14 11:19:58.261 lrd/sntf 0/RSP0/CPU0 t13 : 0/2/CPU0 (0x841) 0 0 NOT_PRESENT PRESENT 0x0 UNKN Dec 14 11:19:58.265 lrd/sntf 0/RSP0/CPU0 t13 : 0/0/CPU0 (0x821) 0 0 NOT_PRESENT BOOTING 0x0 UNKN Dec 14 11:19:58.268 lrd/sntf 0/RSP0/CPU0 t13 : 0/FT1/SP (0x4b0) -1 -1 NOT_PRESENT PRESENT 0x0 UNKN Dec 14 11:19:58.269 lrd/sntf 0/RSP0/CPU0 t13 : 0/FT0/SP (0x4a0) -1 -1 NOT_PRESENT PRESENT 0x0 UNKN Dec 14 11:19:59.327 lrd/sntf 0/RSP0/CPU0 t13 : 0/RSP1/CPU0(0x11 ) 0 0 NOT_PRESENT RUNNING_MBI 0x100000 RP Dec 14 11:19:59.341 lrd/sntf 0/RSP0/CPU0 t13 : 0/PM1/SP (0xe10) -1 -1 NOT_PRESENT PRESENT 0xf00188 UNKN Dec 14 11:19:59.345 lrd/sntf 0/RSP0/CPU0 t13 : 0/2/CPU0 (0x841) 0 0 PRESENT BOOTING 0x0 UNKN Dec 14 11:20:23.306 lrd/sntf 0/RSP0/CPU0 t13 : 0/0/CPU0 (0x821) 0 0 BOOTING MBI_BOOTING 0x30207 LC Dec 14 11:20:23.316 lrd/sntf 0/RSP0/CPU0 t13 : 0/2/CPU0 (0x841) 0 0 BOOTING MBI_BOOTING 0x30207 LC Dec 14 11:21:45.711 lrd/sntf 0/RSP0/CPU0 t13 : 0/0/CPU0 (0x821) 0 0 MBI_BOOTING RUNNING_MBI 0x30207 LC Dec 14 11:21:46.239 lrd/sntf 0/RSP0/CPU0 t13 : 0/2/CPU0 (0x841) 0 0 MBI_BOOTING RUNNING_MBI 0x30207 LC Dec 14 15:42:37.508 lrd/sntf 0/RSP0/CPU0 t13 : 0/3/CPU0 (0x851) 0 0 NOT_PRESENT PRESENT 0x0 UNKN Dec 14 15:42:37.609 lrd/sntf 0/RSP0/CPU0 t13 : 0/3/CPU0 (0x851) 0 0 PRESENT BOOTING 0x0 UNKN Dec 14 15:43:03.000 lrd/sntf 0/RSP0/CPU0 t13 : 0/3/CPU0 (0x851) 0 0 BOOTING MBI_BOOTING 0x3020a LC Dec 14 15:43:48.409 lrd/sntf 0/RSP0/CPU0 t13 : 0/3/CPU0 (0x851) 0 0 MBI_BOOTING RUNNING_MBI 0x3020a LC Dec 15 14:53:15.447 lrd/sntf 0/RSP0/CPU0 t13 : 0/3/CPU0 (0x851) 0 0 RUNNING_ENA BRINGDOWN 0x3020a LC Dec 15 14:53:15.462 lrd/sntf 0/RSP0/CPU0 t13 : 0/3/CPU0 (0x851) 0 0 BRINGDOWN NOT_PRESENT 0x3020a LC ---------- show ltrd-trace server [17:21:39.392 UTC Fri Dec 18 2009] ---------- ++++++++++ show ltrd-trace server [17:21:39.548 UTC Fri Dec 18 2009] ++++++++++ lrd_show_ltrace -F lrd/sreg -TP1 29 wrapping entries (64 possible, 0 filtered, 29 total) Client New Registrations: jid pid Msg-op Event-flags Card-flags ------------------------------------------------------------------ Dec 14 11:19:47.723 lrd/sreg 0/RSP0/CPU0 t15 : 389 213071 DLRSC dlrsc-state Unknwn Dec 14 11:19:47.725 lrd/sreg 0/RSP0/CPU0 t15 : 406 213090 Node State card-state RP DRP Dec 14 11:19:47.727 lrd/sreg 0/RSP0/CPU0 t15 : 95 163876 Pri LR Unknwn Unknwn Dec 14 11:19:47.731 lrd/sreg 0/RSP0/CPU0 t15 : 168 176173 Pri LR Unknwn Unknwn Dec 14 11:19:47.739 lrd/sreg 0/RSP0/CPU0 t15 : 404 184381 Node State card-state RP Dec 14 11:19:47.746 lrd/sreg 0/RSP0/CPU0 t15 : 283 213089 LR Crt/Del Unknwn Unknwn Dec 14 11:19:47.755 lrd/sreg 0/RSP0/CPU0 t15 : 225 208966 Node State card-state RP Dec 14 11:19:55.671 lrd/sreg 0/RSP0/CPU0 t15 : 226 229494 Node State card-state RP Dec 14 11:19:56.522 lrd/sreg 0/RSP0/CPU0 t15 : 335 221289 Node State card-state RP DRP LC Other Dec 14 11:20:00.929 lrd/sreg 0/RSP0/CPU0 t15 : 348 241796 DLRSC dlrsc-state Unknwn Dec 14 11:20:02.842 lrd/sreg 0/RSP0/CPU0 t15 : 245 245905 DLRSC dlrsc-state Unknwn Dec 14 11:20:04.054 lrd/sreg 0/RSP0/CPU0 t15 : 256 245902 Node State card-state sw-state RP DRP LC Dec 14 11:20:04.054 lrd/sreg 0/RSP0/CPU0 t15 : 241 245901 Node State card-state sw-state RP DRP LC Dec 14 11:20:04.699 lrd/sreg 0/RSP0/CPU0 t15 : 219 237682 Node State card-state RP DRP LC Dec 14 11:20:09.686 lrd/sreg 0/RSP0/CPU0 t15 : 289 237695 Node State card-state RP DRP Dec 14 11:20:09.904 lrd/sreg 0/RSP0/CPU0 t15 : 246 245908 DLRSC dlrsc-state Unknwn Dec 14 11:20:11.607 lrd/sreg 0/RSP0/CPU0 t15 : 266 245907 DLRSC dlrsc-state Unknwn Dec 14 11:20:15.748 lrd/sreg 0/RSP0/CPU0 t15 : 155 213092 Node State card-state sw-state RP DRP Dec 14 11:20:20.401 lrd/sreg 0/RSP0/CPU0 t15 : 341 254123 Node State card-state sw-state RP DRP Dec 14 11:20:24.754 lrd/sreg 0/RSP0/CPU0 t15 : 278 254124 Node State card-state LC Dec 14 11:20:29.079 lrd/sreg 0/RSP0/CPU0 t15 : 144 262347 Node State card-state LC Dec 14 11:20:33.883 lrd/sreg 0/RSP0/CPU0 t15 : 342 262351 Node State card-state sw-state LC Dec 14 11:20:34.194 lrd/sreg 0/RSP0/CPU0 t15 : 181 270550 Node State card-state RP DRP LC Dec 14 11:20:36.280 lrd/sreg 0/RSP0/CPU0 t15 : 312 254139 DLRSC dlrsc-state LC Dec 14 11:20:53.951 lrd/sreg 0/RSP0/CPU0 t15 : 398 270596 DLRSC dlrsc-state Unknwn ---------- show ltrd-trace server [17:21:40.125 UTC Fri Dec 18 2009] ---------- ++++++++++ show ltrd-trace server [17:21:40.326 UTC Fri Dec 18 2009] ++++++++++ lrd_show_ltrace -F lrd/sreg -TP2 29 wrapping entries (64 possible, 0 filtered, 29 total) Client re-Registrations: jid pid Curr-msg-op New-Msg-op Event-flags Card-flags ----------------------------------------------------------------------------------- Dec 14 11:19:47.757 lrd/sreg 0/RSP0/CPU0 t15 : 95 163876 Pri LR Node State Unknwn Unknwn Dec 14 11:20:00.940 lrd/sreg 0/RSP0/CPU0 t15 : 348 241796 DLRSC Node State dlrsc-state Unknwn Dec 14 11:20:46.317 lrd/sreg 0/RSP0/CPU0 t15 : 225 208966 Node State LR Crt/Del card-state RP Dec 14 11:20:46.317 lrd/sreg 0/RSP0/CPU0 t15 : 225 208966 unknwn DLSRC Down card-state RP ---------- show ltrd-trace server [17:21:40.774 UTC Fri Dec 18 2009] ---------- ++++++++++ show ltrd-trace server [17:21:40.994 UTC Fri Dec 18 2009] ++++++++++ No messages to display lrd_show_ltrace -F lrd/sdwn -TP1 ---------- show ltrd-trace server [17:21:41.511 UTC Fri Dec 18 2009] ---------- ++++++++++ show ltrd-trace server [17:21:41.653 UTC Fri Dec 18 2009] ++++++++++ No messages to display lrd_show_ltrace -F lrd/sdwn -TP2 ---------- show ltrd-trace server [17:21:42.014 UTC Fri Dec 18 2009] ---------- ++++++++++ show ltrd-trace server [17:21:42.150 UTC Fri Dec 18 2009] ++++++++++ lrd_show_ltrace -F lrd/supd -TP1 20 wrapping entries (1024 possible, 0 filtered, 20 total) SW updates sent: nodeid o-state n-state red-role partner pi-ctype LRid ------------------------------------------------------------------------------------ Dec 14 11:19:47.645 lrd/supd 0/RSP0/CPU0 t3 : 0/RSP0/CPU0(0x1 ) NO STATE ARB BAND Active 0x11 RP 0 Dec 14 11:19:56.368 lrd/supd 0/RSP0/CPU0 t4 : 0/RSP0/CPU0(0x1 ) ARB BAND ADMIN BAND Active 0x11 RP 0 Dec 14 11:20:18.381 lrd/supd 0/RSP0/CPU0 t1 : 0/RSP0/CPU0(0x1 ) ADMIN BAND INFRA BAND Active 0x11 RP 0 Dec 14 11:20:54.823 lrd/supd 0/RSP0/CPU0 t4 : 0/RSP0/CPU0(0x1 ) INFRA BAND FINAL BAND Active 0x11 RP 0show tech-support mpls ldp
To automatically run show commands that display information specific to Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) debugging, use the show tech-support mpls ldp command in EXEC mode.
show tech-support mpls ldp { file send-to [background] [ compressed | uncompressed ] | terminal [page] | location node-id }
Syntax Description
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
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.
terminal
Specifies that the command output is displayed on the terminal.
page
(Optional) Specifies that the command output is displayed one 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.
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
This command generates LDP 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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 a truncated output of the show tech-support mpls ldp command that is displayed for the terminal:
RP/0/0/CPU0:router# show tech-support mpls ldp terminal page ------------------------------------------------------------------------------- show tech-support mpls ldp (Detail with Event traces) ------------------------------------------------------------------------------- -------------------------------- show version --------------------------------- Cisco IOS XR Software, Version 3.9.0.16I[SIT1_IMAGE1] Copyright (c) 2009 by Cisco Systems, Inc. ROM: System Bootstrap, Version 1.48(20070928:224557) [CRS-1 ROMMON], P1_CRS-8 uptime is 4 days, 21 hours, 43 minutes System image file is "disk0:hfr-os-mbi-3.6.0.16I/mbihfr-rp.vm" cisco CRS-8/S (7457) processor with 4194304K bytes of memory. 7457 processor at 1197Mhz, Revision 1.2 4 T3 Port controller(s) 20 Packet over SONET/SDH network interface(s) 20 SONET/SDH Port controller(s) 4 Serial network interface(s) 4 Ethernet/IEEE 802.3 interface(s) 16 GigabitEthernet/IEEE 802.3 interface(s) 1019k 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 0x102 Boot device on node 0/1/CPU0 is mem: Package active on node 0/1/CPU0: hfr-sbc, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-sbc-3.6.0.16I Built on Tue Oct 2 15:07:32 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-pagent, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-pagent-3.6.0.I Built on Tue Oct 2 15:58:47 DST 2007 By iox42.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-fpd, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-fpd-3.6.0.16I Built on Tue Oct 2 14:48:41 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-diags, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-diags-3.6.0.16I Built on Tue Oct 2 14:48:32 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-mcast, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-mcast-3.6.0.16I Built on Tue Oct 2 14:26:29 DST 2007 By sjce-gf-061.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-mpls, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-mpls-3.6.0.16I Built on Tue Oct 2 14:22:48 DST 2007 By sjce-gf-061.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-lc, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-lc-3.6.0.16I Built on Tue Oct 2 14:02:24 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-fwdg, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-fwdg-3.6.0.16I Built on Tue Oct 2 13:57:12 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-admin, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-admin-3.6.0.16I Built on Tue Oct 2 13:53:07 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-base, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-base-3.6.0.16I Built on Tue Oct 2 13:51:10 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-os-mbi, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-os-mbi-3.6.0.I Built on Tue Oct 2 13:28:38 DST 2007 By iox26.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 Configuration register on node 0/4/CPU0 is 0x102 Boot device on node 0/4/CPU0 is disk0: Package active on node 0/4/CPU0: hfr-sbc, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-sbc-3.6.0.16I Built on Tue Oct 2 15:07:32 DST 2007 By sjce-gf-071.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE8 hfr-pagent, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-pagent-3.6.0.I Built on Tue Oct 2 15:58:47 DST 2007 By iox42.cisco.com in /auto/ioxbuild2/production/3.6.0.16I.SIT1_IMAGE1/hfr/8 hfr-fpd, V 3.6.0.16I[SIT1_IMAGE1], Cisco Systems, at disk0:hfr-fpd-3.6.0.16Ishow tech-support mpls optical-uni
To automatically run show commands that display information specific to Multiprotocol Label Switching (MPLS) Optical User Network Interface (O-UNI) debugging, use the show tech-support mpls optical-uni command in EXEC mode.
show tech-support mpls optical-uni { file send-to [background] [ compressed | uncompressed ] | terminal [page] }
Syntax Description
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
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.
terminal
Specifies that the command output is displayed on the terminal.
page
(Optional) Specifies that the command output is displayed one 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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
This command generates O-UNI 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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 mpls optical-uni command output that is displayed for the terminal:
RP/0/0/CPU0:router# show tech-support mpls optical-uni terminal page ------------------------------------------------------------------------------- show tech-support mpls optical-uni (Detail with Event traces) ------------------------------------------------------------------------------- ------------------------- show mpls interfaces detail ------------------------- Interface Bundle-POS24: LDP labelling enabled LSP labelling not enabled MPLS enabled Interface GigabitEthernet0/1/5/1: LDP labelling enabled LSP labelling not enabled MPLS enabled Interface GigabitEthernet0/1/5/2: LDP labelling enabled LSP labelling enabled (TE-Control) MPLS enabled Interface POS0/1/0/1: LDP labelling enabled LSP labelling not enabled MPLS enabled Interface GigabitEthernet0/6/5/1: LDP labelling enabled LSP labelling enabled (TE-Control) MPLS enabled Interface GigabitEthernet0/6/5/2: LDP labelling enabled LSP labelling enabled (TE-Control) MPLS enabled Interface POS0/6/0/0: LDP labelling enabled LSP labelling not enabled MPLS enabled Interface POS0/6/0/1: LDP labelling enabled LSP labelling enabled (TE-Control) MPLS enabled Interface POS0/6/0/3: LDP labelling enabled LSP labelling enabled (TE-Control) MPLS enabled Interface POS0/6/4/4: LDP labelling enabled LSP labelling not enabled MPLS enabled Interface POS0/6/4/6: LDP labelling enabled LSP labelling not enabled MPLS enabled Interface POS0/6/4/7: LDP labelling enabled LSP labelling enabled (TE-Control) MPLS enabled ---------------------------- show mpls optical-uni ---------------------------- Index of abreviations: ---------------------- M=O-UNI configuration Mode. P=Passive AR =active/receiver AS=active/sender U=Unknown Interface TunID M Sig State CCT Up Since TNA --------------- ------ -- --------------- ------------------- ---------------- --------------------- show mpls optical-uni lmp neighbor ---------------------- ----------------------- show mpls optical-uni lmp ipcc ------------------------ ---------------------------- show mpls lmp clients ---------------------------- -------------------- show mpls optical-uni diagnostics All -------------------- ---------------------- show mpls optical-uni timers all ----------------------- Present Time: 16/10/2007 17:09:06 O-UNI timers presently active for nodes: IP addr. Type Name Set@ Timeout ---------- -------- ------------ -------------------- ------- Present Time: 16/10/2007 17:09:06show tech-support mpls rsvp
To 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
terminal
Displays the 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.
sent-to
Name of the file. The following valid options are listed:
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
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 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
- 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
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 mpls rsvp command output:
RP/0/0/CPU0:router# show tech-support mpls rsvp terminal page ------------------------------------------------------------------------------- show tech-support mpls rsvp (Detail with Event traces) ------------------------------------------------------------------------------- ------------------------- show rsvp interface detail -------------------------- INTERFACE: GigE0/1/0/0 (ifh=0x1180060). VRF ID: 0x0 (Default). BW (bits/sec): Max=1230M. MaxFlow=1230M. 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=0 Number of pak events received from raw=1 Number of spurious events received from raw=1 Number of packets received from raw=0 Number of errored drops=0 Authentication queue: Number of enqueues=0 Number of drops due to max q size=0 High water mark=0 Current queue size=0 High priority queue: Number of enqueues=0 Number of drops due to max q size=0 High water mark=0 Current queue size=0 Low 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: 0 Locally 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 --------------------- 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 0 48 0 96 0 128 0 192 0 256 0 Dynamic 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 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 0show tech-support mpls traffic-eng
To automatically run show commands that display information specific to Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) debugging, use the show tech-support mpls traffic-eng command in EXEC mode.
show tech-support mpls traffic-eng { terminal [page] | file send-to [background] [ compressed | uncompressed ] } [ forwarding tunnel-name tunnel name ] [ tunnel-number number ]
Syntax Description
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
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.
forwarding
(Optional) Displays forwarding information for a tunnel.
tunnel-name
(Optional) Displays the tunnel name that is used by the RSVP process.
tunnel name
(Optional) Name for the tunnel.
terminal
Specifies that the command output is displayed on the terminal.
page
(Optional) Specifies that the command output is displayed one 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.
tunnel-number
(Optional) Specifies the tunnel number that is used by the RSVP process.
number
(Optional) Number for the tunnel. The range is from 0 to 65535.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
This command generates MPLS-TE 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.
See the Cisco IOS XR Software command references for information about these commands and descriptions of their command output. The Cisco IOS XR Software 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 mpls traffic-eng command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support mpls traffic-eng terminal page ------------------------------------------------------------------------------- show tech-support mpls traffic-eng ------------------------------------------------------------------------------- -------------------- show mpls traffic-eng tunnels summary -------------------- Signalling Summary: LSP Tunnels Process: running RSVP Process: running Forwarding: enabled Head: 0 interfaces, 0 active signalling attempts, 0 established 0 explicit, 0 dynamic 0 activations, 0 deactivations 0 recovering, 0 recovered Mids: 2 Tails: 0 Periodic reoptimization: every 3600 seconds, next in 2703 seconds Periodic FRR Promotion: every 300 seconds, next in 106 seconds Periodic auto-bw collection: disabled Fast ReRoute Summary: Head: 0 FRR tunnels, 0 protected, 0 rerouted Mid: 0 FRR tunnels, 0 protected, 0 rerouted Summary: 0 protected, 0 link protected, 0 node protected, 0 bw protected Backup: 0 tunnels, 0 assigned Interface: 0 protected, 0 rerouted --------------- show mpls traffic-eng counters tunnels summary ---------------- Head: Mid: Tail: Total: 0 Total: 8 Total: 0 Sender Create: 0 Path Create: 2 Path Create: 0 Sender Modify: 0 Path Change: 0 Path Change: 0 Sender Delete: 0 Path Delete: 0 Path Delete: 0 RESV Create: 0 Receiver Create: 2 Receiver Create: 0 RESV Change: 0 Receiver Modify: 0 Receiver Modify: 0 RESV Delete: 0 Receiver Delete: 0 Receiver Delete: 0 Path Delete: 0 RESV Create: 2 RESV Create: 0 Path Error: 0 RESV Delete: 0 RESV Delete: 0 Path Change: 0 RESV Change: 0 RESV Change: 0 Path Create: 0 Sender Create: 2 RESV Error: 0 RESV Confirm: 0 Sender Modify: 0 Sender Delete 0 Other: 0 Other: 0 Other: 0 -------------------- show mpls traffic-eng counters batch --------------------- Messages Batches MinSize MaxSize AverageSize Description -------- ------- ------- ------- ----------- ----------- 0 0 0 0 0 IF CREATE 0 0 0 0 0 CAPS ADD 0 0 0 0 0 MTU UPDATE 0 0 0 0 0 STATE UPDATE 0 0 0 0 0 IF REPLICATE 0 0 0 0 0 IF DEL CONFIRM 0 0 0 0 0 IF DELETE 25 23 1 2 1 NOTFN from IM 4 2 2 2 2 MESSAGE to RSVP 9 6 1 2 1 MESSAGES from RSVP 0 0 0 0 0 MESSAGES to IGP 0 0 0 0 0 SYSDB VRFNs 0 0 0 0 0 SYSDB APPLYs 2 1 2 2 2 MESSAGE to LSD 2 2 2 2 1 MESSAGES from LSD 12 6 1 6 2 MESSAGES to IPARM ---------- show mpls traffic-eng link-management statistics summary ----------- LSP Admission Statistics:: Setup Setup Setup Setup Tear Tear Tear Requests Admits Rejects Errors Requests Preempts Errors -------- -------- -------- -------- -------- -------- -------- Path 2 2 0 0 0 0 0 Resv 2 2 0 0 0 0 0 ---------------- show mpls traffic-eng link-management summary ---------------- System Information:: Links Count : 6 (Maximum Links Supported 100) Flooding System : enabled IGP Areas Count : 1 IGP Areas ---------- IGP Area[1]:: OSPF 100 area 0 Flooding Protocol : OSPF Flooding Status : flooded --More-- Zero Nodes Found. Periodic Flooding : enabled (every 180 seconds) Flooded Links : 6 IGP System ID : 10.1.1.1 MPLS TE Router ID : 10.1.1.1 IGP Neighbors : 6 ------------- show mpls traffic-eng fast-reroute database summary ------------- Status Count ---------- ---------- Active 0 Ready 0 Partial 0 ------------------------ show mpls forwarding summary ------------------------- Forwarding entries: Label switching: 60 MPLS TE tunnel head: 0 MPLS TE fast-reroute: 0 via 0 protected next-hops MPLS TE internal: 0 Forwarding updates: 392 updates, 37 messages Labels in use: Reserved: 3 Lowest: 0 Highest: 16059 Deleted stale label entries: 0 Pkt drops=0, fragm=0, fail_look=0 Pkts dropped: 0 Pkts fragmented: 0 Failed lookups: 0 ----------------------- show cef drop location 0/0/cpu0 ----------------------- CEF Drop Statistics ----------------------- show cef drop location 0/1/cpu0 ----------------------- CEF Drop Statistics Node: 0/1/CPU0 Unresolved drops packets : 0 Unsupported drops packets : 0 Null0 drops packets : 0 No route drops packets : 0 No Adjacency drops packets : 0 Checksum error drops packets : 0show 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 [ address-family | classic ] [ group group-address ] { terminal [page] | file send-to } [ background | compressed | uncompressed ] [ source source address ] [ location node-id ] [rack] [ vrf vrf-name ]
Syntax Description
address-family
(Optional) Collects address family specific information. It can be either ipv4 or ipv6.
classic
(Optional) Retrieves multicast related information using the non-fast method.
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.
terminal
Displays the 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).
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:
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.
source
(Optional) Displays the multicast source address.
source address
(Optional) Source address for multicast.
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
rack
(Optional) Displays the list of racks.
vrf
(Optional) Specifies a VPN routing and forwarding (VRF) instance.
vrf-name
(Optional) Name of VRF.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
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 multicast command:
- show version
- show running-config
- show ip interface brief
- show install
- show processes aborts location all
- show processes blocked location all
- show context location all
- show memory summary 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
- show mfib hardware route mofrr location node-id
- 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
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 multicast command output:
RP/0/0/CPU0:router# show tech-support multicast terminal page ------------------------------------------------------------------------------- show tech-support multicast location all ------------------------------------------------------------------------------- -------------------------------- show version -------------------------------- Cisco IOS XR Software, Version 3.9.0 Copyright (c) 2009 by Cisco Systems, Inc. ROM: System Bootstrap, Version 1.43(20061109:045749) [CRS-1 ROMMON], Router uptime is 1 week, 4 days, 19 hours, 57 minutes System image file is "disk0:hfr-os-mbi-3.8.0/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 0x102 Boot 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 10:47:29 DST 2007 By cisco.com in /auto/3.8.0 . . . --------------------------- show ip interface brief --------------------------- Interface IP-Address Status Protocol Loopback0 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: 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 scheduled 03/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 . . .show tech-support netflow
To automatically run show commands that display information specific to netflow debugging, use the show tech-support netflow command in EXEC mode.
Syntax Description
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
rack
(Optional) Displays the list of racks.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
This command generates netflow 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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 netflow command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support netflow ------------------------------------------------------------------------------- show tech-support netflow ------------------------------------------------------------------------------- Summary ALL ----------------------------------- show process blocked show flow trace all Summary LC ----------------------------------- show im trace operation all | include netflow show process nfma show process nfea show process nfsvr follow process 4116614 verbose iteration 1 follow process 4116615 verbose iteration 1 follow process 4116616 verbose iteration 1 show flow exporter show flow monitor show flow monitor cache IRP data +++++++++++ show process blocked [09:29:25.008 UTC Mon Jan 18 2010] +++++++++++ Jid Pid Tid Name State TimeInState Blocked-on 88 36889 2 umass-enum Reply 165:49:43:0995 1 kernel 88 36889 3 umass-enum Reply 165:49:43:0787 1 kernel 88 36889 5 umass-enum Reply 165:49:33:0152 40992 io-usb 88 36889 6 umass-enum Reply 165:49:33:0152 1 kernel 52 36890 1 ksh Reply 165:49:44:0049 12296 serdrvr 51 53276 2 attachd Reply 165:49:42:0534 40996 eth_server 51 53276 3 attachd Reply 165:49:42:0533 16397 mqueue 65569 49185 2 devb-umass Reply 165:49:33:0152 40992 io-usb 80 53282 6 qnet Reply 0:00:01:0314 40996 eth_server 50 53288 2 attach_server Reply 165:49:42:0472 16397 mqueue 65676 13709452 1 showtech_cat Reply 0:00:00:0197 16396 pipe 65678 13914254 1 show_processes Reply 0:00:00:0000 1 kernel ----------- show process blocked [09:29:25.302 UTC Mon Jan 18 2010] ----------- +++++++++++ show flow trace all [09:29:25.408 UTC Mon Jan 18 2010] ++++++++++++ 137 wrapping entries (4352 possible, 0 filtered, 137 total) Jan 18 07:41:39.745 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x4000004e for classname=NetflowFlowRecordMapClass. Jan 18 07:41:39.746 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x4000004f for classname=NetflowFlowExportMapClass. Jan 18 07:41:39.748 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000050 for classname=NetflowFlowSampleMapClass. Jan 18 07:41:39.749 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000051 for classname=NetflowFlowMonitorMapClass. Jan 18 07:41:39.750 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000052 for classname=NetflowRtrIdClass. Jan 18 07:41:39.752 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000053 for classname=NetflowIRPClass. Jan 18 07:41:39.753 netflow/nfmgr 0/1/CPU0 t1 nrs_register() suceeded. (handle=40000053:1) Jan 18 07:41:39.755 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000054 for classname=NetflowControlClass. Jan 18 07:41:39.756 netflow/nfmgr 0/1/CPU0 t1 nrs_register() suceeded. (handle=40000053:1) Jan 18 07:41:39.789 netflow/nfma 0/1/CPU0 t1 DLSRC is virtual active Jan 18 07:41:39.791 netflow/nfma 0/1/CPU0 t1 Ready for processing events Jan 18 07:41:39.803 netflow/nfma 0/1/CPU0 t1 Fmon verify item[1]. Batchsz=1 proto=ipv4 dir=input Jan 18 07:41:39.803 netflow/nfma 0/1/CPU0 t1 Verifying fmon tuple. {ifname=GigabitEthernet0_1_0_28,proto=ipv4,fmm_name=fmm,dir=input,fsm_name=smm,opc=0} Jan 18 07:41:39.804 netflow/nfma 0/1/CPU0 t1 Batch dpc for {proto=ipv4, dir=input, cmnd=0, count=1} Jan 18 07:41:39.926 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x4000004e for classname=NetflowFlowRecordMapClass. Jan 18 07:41:39.927 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x4000004f for classname=NetflowFlowExportMapClass. Jan 18 07:41:39.929 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000050 for classname=NetflowFlowSampleMapClass. Jan 18 07:41:39.931 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000051 for classname=NetflowFlowMonitorMapClass. Jan 18 07:41:39.932 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000052 for classname=NetflowRtrIdClass. Jan 18 07:41:39.934 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000053 for classname=NetflowIRPClass. Jan 18 07:41:39.935 netflow/nfmgr 0/1/CPU0 t1 nrs_register() suceeded. (handle=40000053:1) Jan 18 07:41:39.938 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000054 for classname=NetflowControlClass. Jan 18 07:41:39.939 netflow/nfmgr 0/1/CPU0 t1 nrs_register() suceeded. (handle=40000053:1) Jan 18 07:41:39.953 netflow/nfsvr 0/1/CPU0 t1 Maximum number of threads allowed: 2147483647 Jan 18 07:41:39.970 netflow/nfsvr 0/1/CPU0 t1 Successful completion of nfsvr_pak_connect initialization Jan 18 07:41:39.978 netflow/nfsvr 0/1/CPU0 t1 Successful completion of nfsvr_netio_connect initialization Jan 18 07:41:39.978 netflow/nfsvr 0/1/CPU0 t1 Successful completion of nfsvr_setup_netio_connection initialization Jan 18 07:41:40.057 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x4000004e for classname=NetflowFlowRecordMapClass. Jan 18 07:41:40.059 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x4000004f for classname=NetflowFlowExportMapClass. Jan 18 07:41:40.060 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000050 for classname=NetflowFlowSampleMapClass. Jan 18 07:41:40.062 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000051 for classname=NetflowFlowMonitorMapClass. Jan 18 07:41:40.063 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000052 for classname=NetflowRtrIdClass. Jan 18 07:41:40.064 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000053 for classname=NetflowIRPClass. Jan 18 07:41:40.066 netflow/nfmgr 0/1/CPU0 t1 nrs_register() suceeded. (handle=40000053:1) Jan 18 07:41:40.068 netflow/nfmgr 0/1/CPU0 t1 Got NRS class handle=0x40000054 for classname=NetflowControlClass. Jan 18 07:41:40.069 netflow/nfmgr 0/1/CPU0 t1 nrs_register() suceeded. (handle=40000053:1) Jan 18 07:41:40.069 netflow/nfmgr 0/1/CPU0 t1 Registering for RTRID{RouterId} with ENS/NRS. Jan 18 07:41:40.071 netflow/nfmgr 0/1/CPU0 t1 nrs_register() suceeded. (handle=40000052:1) Jan 18 07:41:40.071 netflow/nfmgr 0/1/CPU0 t1 Fobj reference 0x5000c09c was added successfully Jan 18 07:41:40.071 netflow/nfmgr 0/1/CPU0 t1 ENS Query Producer status = No error after 0 attempts Jan 18 07:41:40.071 netflow/nfmgr 0/1/CPU0 t1 Fobjget Req for RTRID{RouterId}. Jan 18 07:41:40.071 netflow/nfmgr 0/1/CPU0 t1 No data in fobjp. Pulling from producer via ens_read() Jan 18 07:41:40.074 netflow/nfmgr 0/1/CPU0 t1 Get Req status = No error Jan 18 07:41:40.074 netflow/nfsvr 0/1/CPU0 t1 Router ID changed from 0.0.0.0 to 2.2.2.2 Jan 18 07:41:40.098 netflow/nfsvr 0/1/CPU0 t1 Context at 0x6262c000, input ring at 0x6262c02c Jan 18 07:41:40.098 netflow/nfsvr 0/1/CPU0 t1 Initializing shared memory - must not be a restart Jan 18 07:41:40.099 netflow/nfsvr 0/1/CPU0 t1 Shared memory magic1: 0xbabeface magic2: 0xbefaceba, version: 0x7d901 Jan 18 07:41:40.100 netflow/nfsvr 0/1/CPU0 t1 IRP initialization for thread 1 completed: ok Jan 18 07:41:40.114 netflow/nfsvr 0/1/CPU0 t1 Ready for processing events Jan 18 07:41:40.115 netflow/nfsvr 0/1/CPU0 t1 Rcvd code 0x7c, event 0xd9bfff418 from client Jan 18 07:41:40.116 netflow/nfea 0/1/CPU0 t1 Connection with NFSVR is UP Jan 18 07:41:40.116 netflow/nfea 0/1/CPU0 t1 Bulk downloading fmons to NFSVR Jan 18 07:41:40.142 netflow/nfea 0/1/CPU0 t1 imp ECM CONN-OPEN event Jan 18 07:41:40.142 netflow/nfea 0/1/CPU0 t1 Ready for processing events Jan 18 07:41:40.144 netflow/nfmgr 0/1/CPU0 t1 Registering for FSM{smm} with ENS/NRS. Jan 18 07:41:40.144 netflow/nfea 0/1/CPU0 t1 Processing dpc batch. caps=10, proto=12, count=1, cmnd=0 Jan 18 07:41:40.144 netflow/nfea 0/1/CPU0 t1 Processing dpc[0]={ifh=0x6000780,cmd=0,proto=12,caps=10} Jan 18 07:41:40.144 netflow/nfea 0/1/CPU0 t1 Verifying 1 fmons for proto=ipv4, insz=76 Jan 18 07:41:40.144 netflow/nfea 0/1/CPU0 t1 Verifying limit check fmon={opc=ADD,ifh=0x6000780,proto=ipv4,dir=input,fmm=fmm,fsm=smm} Jan 18 07:41:40.144 netflow/nfea 0/1/CPU0 t1 Reg fsm fmon_oper=0x50020af4 for smm Jan 18 07:41:40.146 netflow/nfmgr 0/1/CPU0 t1 nrs_register() suceeded. (handle=40000050:1) Jan 18 07:41:40.146 netflow/nfmgr 0/1/CPU0 t1 Fobj reference 0x50020af4 was added successfully Jan 18 07:41:40.146 netflow/nfmgr 0/1/CPU0 t1 ENS Query Producer status = No error after 0 attempts Jan 18 07:41:40.146 netflow/nfmgr 0/1/CPU0 t1 Fobjget Req for FSM{smm}. Jan 18 07:41:40.146 netflow/nfmgr 0/1/CPU0 t1 No data in fobjp. Pulling from producer via ens_read() Jan 18 07:41:40.149 netflow/nfmgr 0/1/CPU0 t1 Get Req status = No error Jan 18 07:41:40.149 netflow/nfmgr 0/1/CPU0 t1 Registering for FMM{fmm} with ENS/NRS. Jan 18 07:41:40.149 netflow/nfea 0/1/CPU0 t1 Reg fmm fmon_oper=0x50020af4 for fmm Jan 18 07:41:40.150 netflow/nfmgr 0/1/CPU0 t1 nrs_register() suceeded. (handle=40000051:1) Jan 18 07:41:40.151 netflow/nfmgr 0/1/CPU0 t1 Fobj reference 0x50020af4 was added successfully Jan 18 07:41:40.151 netflow/nfmgr 0/1/CPU0 t1 ENS Query Producer status = No error after 0 attempts Jan 18 07:41:40.151 netflow/nfmgr 0/1/CPU0 t1 Fobjget Req for FMM{fmm}. Jan 18 07:41:40.151 netflow/nfmgr 0/1/CPU0 t1 No data in fobjp. Pulling from producer via ens_read() Jan 18 07:41:40.153 netflow/nfmgr 0/1/CPU0 t1 Get Req status = No error Jan 18 07:41:40.153 netflow/nfmgr 0/1/CPU0 t1 Unregistering from FSM{smm} with ENS/NRS. Jan 18 07:41:40.153 netflow/nfmgr 0/1/CPU0 t1 Fobj reference 0x50020af4 was deleted successfully Jan 18 07:41:40.153 netflow/nfmgr 0/1/CPU0 t1 Fobj has no more references. Doing cleanup.... Jan 18 07:41:40.153 netflow/nfmgr 0/1/CPU0 t1 Cleaning up FSM{smm} Jan 18 07:41:40.153 netflow/nfea 0/1/CPU0 t1 Fmon limit check: index=0,ifh=0x6000780,fmm=fmm,proto=ipv4,dir=input Jan 18 07:41:40.153 netflow/nfea 0/1/CPU0 t1 Found 0 fmons in idb Jan 18 07:41:40.153 netflow/nfea 0/1/CPU0 t1 Verifying hw fmon={opc=ADD,ifh=0x6000780,proto=ipv4,dir=input,fmm=fmm,fsm=smm} Jan 18 07:41:40.153 netflow/nfea 0/1/CPU0 t1 Fmon verification Verify requests to batched message hw verify config FAILED. 'nfea' detected the 'warning' condition 'Requested operation not supported' Jan 18 07:41:40.153 netflow/nfea 0/1/CPU0 t1 Verifying nfsvr msg fmon={opc=SKIP-OPC,ifh=0x6000780,proto=ipv4,dir=input,fmm=fmm,fsm=smm} Jan 18 07:41:40.154 netflow/nfmgr 0/1/CPU0 t1 Unregistering from FMM{fmm} with ENS/NRS. Jan 18 07:41:40.154 netflow/nfmgr 0/1/CPU0 t1 Fobj reference 0x50020af4 was deleted successfully Jan 18 07:41:40.154 netflow/nfmgr 0/1/CPU0 t1 Fobj has no more references. Doing cleanup.... Jan 18 07:41:40.154 netflow/nfmgr 0/1/CPU0 t1 Cleaning up FMM{fmm} Jan 18 07:41:40.154 netflow/nfea 0/1/CPU0 t1 imp_caps_dpc_distribute() api failed for caps=10, proto=12, count=1. Cerr='ifmgr' detected the 'warning' condition 'One of the arguments is invalid' Jan 18 07:41:40.155 netflow/nfma 0/1/CPU0 t1 Fmon cfg apply rejected in batched EA status for opc=0 fmm=fmm fsm=smm proto=ipv4 dir=input on ifh=0x6000780. Cerr='nfea' detected the 'warning' condition 'Requested operation not supported' Jan 18 07:41:40.155 netflow/nfma 0/1/CPU0 t1 Batch dpc for {proto=ipv4, dir=input, cmnd=2, count=1} Jan 18 07:41:40.155 netflow/nfea 0/1/CPU0 t1 Processing dpc batch. caps=10, proto=12, count=1, cmnd=2 Jan 18 07:41:40.155 netflow/nfea 0/1/CPU0 t1 Processing dpc[0]={ifh=0x6000780,cmd=2,proto=12,caps=10} Jan 18 07:41:40.155 netflow/nfea 0/1/CPU0 t1 imp_caps_dpc_distribute() api failed for caps=10, proto=12, count=1. Cerr='ifmgr' detected the 'warning' condition 'One of the arguments is invalid' Jan 18 07:41:40.156 netflow/nfma 0/1/CPU0 t1 Fmon vrfn status[1] = 'nfea' detected the 'warning' condition 'Requested operation not supported' Jan 18 07:43:41.911 netflow/nfmgr 0/1/CPU0 t1 Registering for FSM{smm} with ENS/NRS. Jan 18 07:43:41.911 netflow/nfma 0/1/CPU0 t1 Fmon verify item[1]. Batchsz=1 proto=ipv4 dir=input Jan 18 07:43:41.911 netflow/nfma 0/1/CPU0 t1 Verifying fmon tuple. {ifname=GigabitEthernet0_1_0_28,proto=ipv4,fmm_name=fmm,dir=input,fsm_name=smm,opc=0} Jan 18 07:43:41.911 netflow/nfma 0/1/CPU0 t1 Batch dpc for {proto=ipv4, dir=input, cmnd=0, count=1} Jan 18 07:43:41.911 netflow/nfea 0/1/CPU0 t1 Processing dpc batch. caps=10, proto=12, count=1, cmnd=0 Jan 18 07:43:41.911 netflow/nfea 0/1/CPU0 t1 Processing dpc[0]={ifh=0x6000780,cmd=0,proto=12,caps=10} Jan 18 07:43:41.911 netflow/nfea 0/1/CPU0 t1 Verifying 1 fmons for proto=ipv4, insz=76 Jan 18 07:43:41.911 netflow/nfea 0/1/CPU0 t1 Verifying limit check fmon={opc=ADD,ifh=0x6000780,proto=ipv4,dir=input,fmm=fmm,fsm=smm} Jan 18 07:43:41.911 netflow/nfea 0/1/CPU0 t1 Reg fsm fmon_oper=0x50020af4 for smm Jan 18 07:43:41.913 netflow/nfmgr 0/1/CPU0 t1 nrs_register() suceeded. (handle=40000050:1) Jan 18 07:43:41.913 netflow/nfmgr 0/1/CPU0 t1 Fobj reference 0x50020af4 was added successfully Jan 18 07:43:41.913 netflow/nfmgr 0/1/CPU0 t1 ENS Query Producer status = No error after 0 attempts Jan 18 07:43:41.913 netflow/nfmgr 0/1/CPU0 t1 Fobjget Req for FSM{smm}. Jan 18 07:43:41.913 netflow/nfmgr 0/1/CPU0 t1 No data in fobjp. Pulling from producer via ens_read() Jan 18 07:43:41.916 netflow/nfmgr 0/1/CPU0 t1 Get Req status = No error Jan 18 07:43:41.916 netflow/nfmgr 0/1/CPU0 t1 Registering for FMM{fmm} with ENS/NRS. Jan 18 07:43:41.916 netflow/nfea 0/1/CPU0 t1 Reg fmm fmon_oper=0x50020af4 for fmm Jan 18 07:43:41.917 netflow/nfmgr 0/1/CPU0 t1 nrs_register() suceeded. (handle=40000051:1) Jan 18 07:43:41.917 netflow/nfmgr 0/1/CPU0 t1 Fobj reference 0x50020af4 was added successfully Jan 18 07:43:41.917 netflow/nfmgr 0/1/CPU0 t1 ENS Query Producer status = No error after 0 attempts Jan 18 07:43:41.917 netflow/nfmgr 0/1/CPU0 t1 Fobjget Req for FMM{fmm}. Jan 18 07:43:41.917 netflow/nfmgr 0/1/CPU0 t1 No data in fobjp. Pulling from producer via ens_read() Jan 18 07:43:41.920 netflow/nfmgr 0/1/CPU0 t1 Get Req status = No error Jan 18 07:43:41.920 netflow/nfmgr 0/1/CPU0 t1 Unregistering from FSM{smm} with ENS/NRS. Jan 18 07:43:41.920 netflow/nfmgr 0/1/CPU0 t1 Fobj reference 0x50020af4 was deleted successfully Jan 18 07:43:41.920 netflow/nfmgr 0/1/CPU0 t1 Fobj has no more references. Doing cleanup.... Jan 18 07:43:41.920 netflow/nfmgr 0/1/CPU0 t1 Cleaning up FSM{smm} Jan 18 07:43:41.920 netflow/nfmgr 0/1/CPU0 t1 Unregistering from FMM{fmm} with ENS/NRS. Jan 18 07:43:41.920 netflow/nfmgr 0/1/CPU0 t1 Fobj reference 0x50020af4 was deleted successfully Jan 18 07:43:41.920 netflow/nfmgr 0/1/CPU0 t1 Fobj has no more references. Doing cleanup.... Jan 18 07:43:41.920 netflow/nfmgr 0/1/CPU0 t1 Cleaning up FMM{fmm} Jan 18 07:43:41.920 netflow/nfea 0/1/CPU0 t1 Fmon limit check: index=0,ifh=0x6000780,fmm=fmm,proto=ipv4,dir=input Jan 18 07:43:41.920 netflow/nfea 0/1/CPU0 t1 Found 0 fmons in idb Jan 18 07:43:41.920 netflow/nfea 0/1/CPU0 t1 Verifying hw fmon={opc=ADD,ifh=0x6000780,proto=ipv4,dir=input,fmm=fmm,fsm=smm} Jan 18 07:43:41.920 netflow/nfea 0/1/CPU0 t1 Fmon verification Verify requests to batched message hw verify config FAILED. 'nfea' detected the 'warning' condition 'Requested operation not supported' Jan 18 07:43:41.920 netflow/nfea 0/1/CPU0 t1 Verifying nfsvr msg fmon={opc=SKIP-OPC,ifh=0x6000780,proto=ipv4,dir=input,fmm=fmm,fsm=smm} Jan 18 07:43:41.920 netflow/nfea 0/1/CPU0 t1 imp_caps_dpc_distribute() api failed for caps=10, proto=12, count=1. Cerr='ifmgr' detected the 'warning' condition 'One of the arguments is invalid' Jan 18 07:43:41.921 netflow/nfma 0/1/CPU0 t1 Fmon cfg apply rejected in batched EA status for opc=0 fmm=fmm fsm=smm proto=ipv4 dir=input on ifh=0x6000780. Cerr='nfea' detected the 'warning' condition 'Requested operation not supported' Jan 18 07:43:41.921 netflow/nfma 0/1/CPU0 t1 Batch dpc for {proto=ipv4, dir=input, cmnd=2, count=1} Jan 18 07:43:41.921 netflow/nfma 0/1/CPU0 t1 Fmon vrfn status[1] = 'nfea' detected the 'warning' condition 'Requested operation not supported' Jan 18 07:43:41.921 netflow/nfea 0/1/CPU0 t1 Processing dpc batch. caps=10, proto=12, count=1, cmnd=2 Jan 18 07:43:41.921 netflow/nfea 0/1/CPU0 t1 Processing dpc[0]={ifh=0x6000780,cmd=2,proto=12,caps=10} Jan 18 07:43:41.921 netflow/nfea 0/1/CPU0 t1 imp_caps_dpc_distribute() api failed for caps=10, proto=12, count=1. Cerr='ifmgr' detected the 'warning' condition 'One of the arguments is invalid' ----------- show flow trace all [09:29:25.734 UTC Mon Jan 18 2010] ------------show tech-support nrs
To automatically run show commands that display information specific to the name registration service (NRS) information, use the show tech-support nrs command in EXEC mode.
show tech-support nrs { file send-to [ background | compressed | uncompressed ] | terminal [page] [rack] }
Syntax Description
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
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.
terminal
Specifies that the command output is displayed on the terminal.
page
(Optional) Specifies that the command output is displayed one 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.
rack
(Optional) Displays the list of racks.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 nrs command to collect data for the NRS. The NRS is a central registration authority and is used by the Replication Data Services (RDS) and the Event Notification Services (ENS). This command generates NRS 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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR Software command references for information about these commands and descriptions of their command output. The Cisco IOS XR Software 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 nrs command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support nrs terminal page ------------------------------------------------------------------------------- show tech-support nrs ------------------------------------------------------------------------------- -------------------------------- show platform -------------------------------- Node Type PLIM State Config State ----------------------------------------------------------------------------- 0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON 0/1/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON 0/1/1 MSC(SPA) 4T3E3 OK PWR,NSHUT,MON 0/1/4 MSC(SPA) 4XOC48-POS OK PWR,NSHUT,MON 0/1/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON 0/4/CPU0 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON 0/4/CPU1 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON 0/6/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON 0/6/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON 0/6/4 MSC(SPA) 8XOC3/OC12-POS OK PWR,NSHUT,MON 0/6/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON 0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON ---------------------------- follow NRS 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 155731 iteration 1 verbose ------------------ Attaching to process pid = 155731 (pkg/bin/nrssvr) 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/libchkpt.dll 0xfc5e4000 0x000436f0 0xfc628000 0x00000b3c 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 0x00000show tech-support password
To automatically run show commands that display information to include the password in the output for debugging, use the show tech-support password command in EXEC mode.
show tech-support password { file send-to [ background | compressed | uncompressed ] | terminal [page] } [ location { node-id | all } ]
Syntax Description
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
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.
terminal
Specifies that the command output is displayed on the terminal.
page
(Optional) Specifies that the command output is displayed one 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.
location
(Optional) Specifies a node.
node-id
(Optional) Node ID. The node-id argument is entered in the rack/slot/module notation.
all
(Optional) Specifies all locations.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
This command generates output to include the password 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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 password command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support password terminal page ------------------------------------------------------------------------------- show tech-support ------------------------------------------------------------------------------- ----------------------------- show running-config ----------------------------- Building configuration... !! Last configuration change at Wed Oct 10 20:05:13 2007 ! hostname P1_CRS-8 line console exec-timeout 600 0 session-timeout 600 ! line default exec-timeout 600 0 session-timeout 600 ! clock timezone PST 8 clock summer-time DST recurring 2 sunday march 02:00 first sunday november 02:00 logging console informational telnet vrf default ipv4 server max-servers no-limit domain ipv4 host p1 172.29.52.72 domain ipv4 host p2 172.29.52.77 domain ipv4 host ce6 172.29.52.73 domain ipv4 host ce7 172.29.52.78 domain ipv4 host p11 172.29.52.83 domain ipv4 host pe6 172.29.52.128 domain ipv4 host pe7 172.29.52.182 domain ipv4 host ce25 172.29.52.85 domain ipv4 host ce28 172.29.52.1 domain ipv4 host ce29 172.29.52.178 domain ipv4 host pe21 172.29.52.163 domain ipv4 host pe22 172.29.52.219 domain ipv4 host ce28_nme 172.29.52.177 domain ipv4 host ce29_nme 172.29.52.179 domain lookup disable username 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 25 alias cr copy run disk0:/usr/P1_base_config alias sa show alias alias sc show config commit list alias sd show diag alias si show ip int brief alias sl show led alias sm show mpls forwarding alias sp show platform alias sr show run alias su show users alias sv show version alias sir show ip route control-plane management-plane inband interface all allow all ! ! ! ! ipv4 virtual address 172.29.52.72 255.255.255.0 hw-module service sbc location 0/4/CPU0 hw-module service sbc location 0/4/CPU1 interface 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.3show tech-support pfi
To automatically run show commands that display information specific to Packet Forwarding Infrastructure (PFI) debugging for all components, use the show tech-support pfi command in EXEC mode.
show tech-support pfi { file send-to [ background | compressed | uncompressed ] | terminal [page] | trace-only } [ location { node-id | all } ]
Syntax Description
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
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.
terminal
Specifies that the command output is displayed on the terminal.
page
(Optional) Specifies that the command output is displayed one 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.
location
(Optional) Specifies a node.
node-id
Node ID. The node-id argument is entered in the rack/slot/module notation.
all
Specifies all locations.
trace-only
Displays only trace information.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 pfi command to collect information for the PFI, which consists of interface-related date with regards to netio and interface manager. This command generates output PFI 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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR Software command references for information about these commands and descriptions of their command output. The Cisco IOS XR Software 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 pfi command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support pfi terminal page ------------------------------------------------------------------------------- show tech-support pfi control ------------------------------------------------------------------------------- ------------------------- show im trace location all -------------------------- 11 wrapping entries (1024 possible, 0 filtered, 11 total) 7 unique entries (384 possible, 0 filtered) Oct 11 19:24:10.699 ifmgr/errors 0/RP0/CPU0 2# t1 Failed to bind to pfi_ifh se' Oct 11 19:26:02.019 ifmgr/errors 0/6/CPU0 2# t1 Failed to bind to pfi_ifh serv' Oct 11 19:26:02.694 ifmgr/errors 0/1/CPU0 2# t1 Failed to bind to pfi_ifh serv' Oct 11 19:26:48.033 ifmgr/errors 0/4/CPU1 2# t1 Failed to bind to pfi_ifh serv' Oct 11 19:26:49.737 ifmgr/errors 0/RP1/CPU0 2# t1 Failed to bind to pfi_ifh se' Oct 11 19:26:50.199 ifmgr/errors 0/4/CPU0 2# t1 Failed to bind to pfi_ifh serv' Oct 11 19:30:34.372 ifmgr/errors 0/RP0/CPU0 13# t10 Cannot send async download y 10503 wrapping entries (89088 possible, 0 filtered, 60319 total) Oct 11 19:23:57.839 ifmgr/mdr 0/RP0/CPU0 t1 IM is (re)starting Oct 11 19:24:06.442 ifmgr/iir 0/RP0/CPU0 t1 IIR initialisation successful Oct 11 19:24:06.458 ifmgr/mdr 0/RP0/CPU0 t1 IM received LR state 0x5 from sysmr Oct 11 19:24:06.744 ifmgr/iir 0/RP0/CPU0 t6 Opening IIR to IM connection Oct 11 19:24:06.747 ifmgr/iir 0/RP0/CPU0 t6 Failed to open IM connection: No sy Oct 11 19:24:06.748 ifmgr/iir_resync 0/RP0/CPU0 t6 IIR resync message entry co0 Oct 11 19:24:06.748 ifmgr/iir 0/RP0/CPU0 t6 IIR sending GSP message 1 to ALL Is Oct 11 19:24:07.749 ifmgr/iir 0/RP0/CPU0 t6 Opening IIR to IM connection Oct 11 19:24:07.755 ifmgr/iir 0/RP0/CPU0 t6 Failed to open IM connection: No sy Oct 11 19:24:08.756 ifmgr/iir 0/RP0/CPU0 t6 Opening IIR to IM connection Oct 11 19:24:08.758 ifmgr/iir 0/RP0/CPU0 t6 Failed to open IM connection: No sy Oct 11 19:24:09.340 ifmgr/create 0/RP0/CPU0 t1 im_tree_id_array_init: Virtual 2 Oct 11 19:24:09.340 ifmgr/mdr 0/RP0/CPU0 t1 IM is going active physical Oct 11 19:24:09.378 ifmgr/create 0/RP0/CPU0 t1 Registered chkpt table with ID E Oct 11 19:24:09.378 ifmgr/create 0/RP0/CPU0 t1 Registered chkpt table with ID E Oct 11 19:24:09.378 ifmgr/create 0/RP0/CPU0 t1 Registered chkpt table with ID E Oct 11 19:24:09.378 ifmgr/create 0/RP0/CPU0 t1 Registered chkpt table with ID E Oct 11 19:24:09.383 ifmgr/iir 0/RP0/CPU0 t6 Received IM request for op IFMGR_A0 Oct 11 19:24:09.383 ifmgr/iir 0/RP0/CPU0 t6 IIR: Going active Oct 11 19:24:09.533 ifmgr/errors 0/RP0/CPU0 t1 Failed to bind to pfi_ifh serve' Oct 11 19:24:09.534 ifmgr/bundle 0/RP0/CPU0 t1 im_bundle_gsp_init complete Oct 11 19:24:09.555 ifmgr/mdr 0/RP0/CPU0 t1 IM is going active virtual on RESTT Oct 11 19:24:09.569 ifmgr/bundle 0/RP0/CPU0 t1 Recovering bundles info from ch. Oct 11 19:24:09.569 ifmgr/create 0/RP0/CPU0 t1 Registered chkpt table with ID E Oct 11 19:24:09.569 ifmgr/create 0/RP0/CPU0 t1 Registered chkpt table with ID E Oct 11 19:24:09.569 ifmgr/create 0/RP0/CPU0 t1 Registered chkpt table with ID E Oct 11 19:24:09.569 ifmgr/create 0/RP0/CPU0 t1 Registered chkpt table with ID E Oct 11 19:24:09.571 ifmgr/iir 0/RP0/CPU0 t1 Blast mode start. Main intf 0x00000 Oct 11 19:24:09.579 ifmgr/imd 0/RP0/CPU0 t9 Successfully transmitted message t2 Oct 11 19:24:09.581 ifmgr/imd 0/RP0/CPU0 t9 Successfully transmitted message t2 Oct 11 19:24:09.763 ifmgr/iir 0/RP0/CPU0 t6 Opening IIR to IM connection Oct 11 19:24:09.780 ifmgr/iir 0/RP0/CPU0 t6 Failed to open IM connection: No sy Oct 11 19:24:10.638 ifmgr/mdr 0/RP0/CPU0 t1 Letting IM connect to IMP Oct 11 19:24:10.670 ifmgr/repl 0/RP0/CPU0 t1 Storing NOTIFY DPC info: gnid 0x01 Oct 11 19:24:10.670 ifmgr/download 0/RP0/CPU0 t1 Produced download element intr Oct 11 19:24:10.670 ifmgr/download 0/RP0/CPU0 t1 Sending pulse code 124 to imp0 Oct 11 19:24:10.670 ifmgr/repl 0/RP0/CPU0 t1 Storing NOTIFY DPC info: gnid 0xf3 Oct 11 19:24:10.670 ifmgr/download 0/RP0/CPU0 t1 Download empty (cb idx 1 (INIg Oct 11 19:24:10.670 ifmgr/download 0/RP0/CPU0 t1 Produced download element intr Oct 11 19:24:10.670 ifmgr/download 0/RP0/CPU0 t1 Outstanding pulse to improxy.1 Oct 11 19:24:10.671 ifmgr/mdr 0/RP0/CPU0 t1 Publishing lwm channel Oct 11 19:24:10.691 ifmgr/iir 0/RP0/CPU0 t6 Received IM request for op PEER_NO0 Oct 11 19:24:10.694 ifmgr/create 0/RP0/CPU0 t1 PFI_IFH broadcast success snv=0r Oct 11 19:24:10.696 ifmgr/mdr 0/RP0/CPU0 t10 IM entering event loop Oct 11 19:24:10.699 ifmgr/errors 0/RP0/CPU0 t1 Failed to bind to pfi_ifh serve' Oct 11 19:24:10.699 ifmgr/mdr 0/RP0/CPU0 t1 IM received LR state 0x4 from sysmr Oct 11 19:24:10.717 ifmgr/repl 0/RP0/CPU0 t1 Received GSP notification 16 (NEWP Oct 11 19:24:10.717 ifmgr/download 0/RP0/CPU0 t10 Received notification - proce1 Oct 11 19:24:10.717 ifmgr/download 0/RP0/CPU0 t10 Download result: element ID 0r Oct 11 19:24:10.717 ifmgr/download 0/RP0/CPU0 t10 Async rules download complete Oct 11 19:24:10.717 ifmgr/download 0/RP0/CPU0 t10 Completed processing of 1 dow1 Oct 11 19:24:10.736 ifmgr/download 0/RP0/CPU0 t10 Received notification - proce0 Oct 11 19:24:10.736 ifmgr/download 0/RP0/CPU0 t10 Download result: element ID 0r Oct 11 19:24:10.736 ifmgr/download 0/RP0/CPU0 t10 Async initial download compler Oct 11 19:24:10.736 ifmgr/download 0/RP0/CPU0 t10 Completed processing of 1 dow0 Oct 11 19:24:10.782 ifmgr/iir 0/RP0/CPU0 t6 Opening IIR to IM connection Oct 11 19:24:10.790 ifmgr/iir 0/RP0/CPU0 t6 Successfully opened IM connection Oct 11 19:24:10.792 ifmgr/iir 0/RP0/CPU0 t6 IIR Publishing channel: No error Oct 11 19:24:11.456 ifmgr/register 0/RP0/CPU0 t10 im_notify_queue: Inserting ca] Oct 11 19:24:11.458 ifmgr/register 0/RP0/CPU0 t10 Returned TRUE for ACTIVE_VIRT0 Oct 11 19:24:11.556 ifmgr/iir_notify 0/RP0/CPU0 t6 Adding 1 wildcard registratf Oct 11 19:24:11.556 ifmgr/iir_notify 0/RP0/CPU0 t6 Sending RESYNC_END notifica0 Oct 11 19:24:11.828 ifmgr/create 0/RP0/CPU0 t10 grow_id_array: Growing id array8 Oct 11 19:24:11.830 ifmgr/intf_exist 0/RP0/CPU0 t10 create (bulk 7) intf:0x00083 Oct 11 19:24:11.830 ifmgr/caps_exist 0/RP0/CPU0 t10 bulk 7[0] base caps defined' Oct 11 19:24:11.830 ifmgr/mdr 0/RP0/CPU0 t10 Marking client with handle 0x30000r Oct 11 19:24:11.830 ifmgr/create 0/RP0/CPU0 t10 grow_id_array: Growing id array4 Oct 11 19:24:11.831 ifmgr/create 0/RP0/CPU0 t10 PFI_IFH broadcast success snv=0r Oct 11 19:24:11.831 ifmgr/download 0/RP0/CPU0 t10 Produced download element intr Oct 11 19:24:11.831 ifmgr/download 0/RP0/CPU0 t10 Sending pulse code 124 to imp0 Oct 11 19:24:12.008 ifmgr/register 0/RP0/CPU0 t10 im_notify_queue: Inserting ca] Oct 11 19:24:12.331 ifmgr/register 0/RP0/CPU0 t10 im_notify_queue: Inserting ca]show tech-support placement
To 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
terminal
Displays the 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.
sent-to
Name of the file. The following valid options are listed:
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 placement command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support placement terminal page ------------------------------------------------------------------------------- show tech-support placement ------------------------------------------------------------------------------- ------------------------------- run lrd_show -I ------------------------------- Success: node_count=6, ready=1 node=0x11, type=2, memsize=256, cpus=1, speed=100, sw_state=6, red_state=0, lr_0 node=0x41, type=1, memsize=256, cpus=1, speed=100, sw_state=6, red_state=1, lr_f node=0x42, type=1, memsize=256, cpus=1, speed=100, sw_state=6, red_state=1, lr_f node=0x61, type=2, memsize=256, cpus=1, speed=100, sw_state=6, red_state=0, lr_0 node=0x201, type=0, memsize=256, cpus=1, speed=100, sw_state=6, red_state=1, lr1 node=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 er Oct 11 19:23:59.980 main bag_register_all_placed_mgmnt_bags rc = No error Oct 11 19:24:06.420 main Checkpoint initialization succeeded Oct 11 19:24:06.665 main Starting for the first time in this LR Oct 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/CPU0 Oct 11 19:24:06.734 nodes lrd_register_card_state ok Oct 11 19:24:06.734 nodes Setting timer for 70 seconds, thread 1 Oct 11 19:24:06.748 nodes Successfully got inventory (attempt 1 of 30) Oct 11 19:24:06.748 nodes Stopping timer Oct 11 19:24:06.748 nodes LR inventory has 4 RP/DRP nodes Oct 11 19:24:06.850 nodes update_node: nodeid 0/4/CPU0, pnodeid [NODEID_INV0 Oct 11 19:24:06.850 nodes Creating new node Oct 11 19:24:06.877 nodes update_node: nodeid 0/4/CPU1, pnodeid [NODEID_INV0 Oct 11 19:24:06.877 nodes Creating new node Oct 11 19:24:06.877 nodes update_node: nodeid 0/RP0/CPU0, pnodeid 0/RP1/CPU1 Oct 11 19:24:06.877 nodes Creating new node Oct 11 19:24:06.877 nodes node::_get_active_nodeid(Placed_node (482c1088) (0 Oct 11 19:24:06.917 nodes update_node: nodeid 0/RP1/CPU0, pnodeid 0/RP0/CPU2 Oct 11 19:24:06.917 nodes Nodeid 0/RP1/CPU0 is already in node object Place) Oct 11 19:24:06.917 nodes Information differs Oct 11 19:24:06.917 nodes node 0/RP0/CPU0 is active Oct 11 19:24:06.917 nodes node::_get_active_nodeid(Placed_node (482c1088) (0 Oct 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 succeeded Oct 11 19:24:07.086 properties Inserting Classaffinity (482827b8) (value 250.00g Oct 11 19:24:07.086 properties Inserting Classaffinity (48282830) (value 250.00i Oct 11 19:24:07.086 properties Inserting Classaffinity (4828286c) (value 250.00g Oct 11 19:24:07.086 properties Inserting Classaffinity (482828a8) (value 250.00i Oct 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)i Oct 11 19:24:07.131 properties Inserting Classaffinity (48282920) (value 70.00)i Oct 11 19:24:07.131 properties Inserting Classaffinity (4828295c) (value 70.00)i Oct 11 19:24:07.132 properties Inserting Classaffinity (4832b048) (value 70.00)i Oct 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 -402 Oct 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 -402 Oct 11 19:24:07.402 properties Inserting Nodetypeaffinity (4832b9b8) (value -40) Oct 11 19:24:07.562 properties Inserting Nodetypeaffinity (4832baf0) (value 100)show tech-support pos
To automatically run show commands that display information specific to Packet over SONET /SDH (POS) debugging, use the show tech-support pos command in EXEC mode.
show tech-support pos { terminal [page] | file send-to [background] [ compressed | uncompressed ] } interface type instance [show-only] [trace-only] [ location node-id | all ] [rack]
Syntax Description
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
This command generates POS 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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR Software command references for information about these commands and descriptions of their command output. The Cisco IOS XR Software 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 routing pos command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support pos ------------------------------------------------------------------------------- show tech-support pos ------------------------------------------------------------------------------- ----------------------------- show running-config ----------------------------- Building configuration... !! Last configuration change at Wed Oct 10 20:05:13 2007 ! hostname P1_CRS-8 line console exec-timeout 600 0 session-timeout 600 ! line default exec-timeout 600 0 session-timeout 600 ! clock timezone PST 8 clock summer-time DST recurring 2 sunday march 02:00 first sunday november 02:00 logging console informational telnet vrf default ipv4 server max-servers no-limit domain ipv4 host p1 172.29.52.72 domain ipv4 host p2 172.29.52.77 domain ipv4 host ce6 172.29.52.73 domain ipv4 host ce7 172.29.52.78 domain ipv4 host p11 172.29.52.83 domain ipv4 host pe6 172.29.52.128 domain ipv4 host pe7 172.29.52.182 domain ipv4 host ce25 172.29.52.85 domain ipv4 host ce28 172.29.52.1 domain ipv4 host ce29 172.29.52.178 domain ipv4 host pe21 172.29.52.163 domain ipv4 host pe22 172.29.52.219 domain ipv4 host ce28_nme 172.29.52.177 domain ipv4 host ce29_nme 172.29.52.179 domain lookup disable username 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 25 alias cr copy run disk0:/usr/P1_base_config alias sa show alias alias sc show config commit list alias sd show diag alias si show ip int brief alias sl show led alias sm show mpls forwarding alias sp show platform alias sr show run alias su show users alias sv show version alias sir show ip route control-plane management-plane inband interface all allow all ! ! ! ! ipv4 virtual address 172.29.52.72 255.255.255.0 hw-module service sbc location 0/4/CPU0 hw-module service sbc location 0/4/CPU1 interface 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 !show tech-support ppp
To automatically run show commands that display information specific to Point to Point Protocol (PPP) debugging, use the show tech-support ppp command in EXEC mode.
show tech-support ppp [ file send-to ] [background] [ compressed | uncompressed ] [ interface type instance ] [ location node-id | all ] [rack]
Syntax Description
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
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.
interface
Collects information about a specific interface.
type
Interface type. For more information, use the question mark (?) online help function.
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.
For more information about the syntax for the router, use the question mark (?) online help function.
location
(Optional) Specifies a node.
node-id
(Optional). Node ID. The node-id argument is entered in the rack/slot/module notation.
all
(Optional) Specifies all locations.
rack
(Optional) Displays the list of racks.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
This command generates PPP 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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 routing ppp command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support ppp ------------------------------------------------------------------------------- show tech-support ppp ------------------------------------------------------------------------------- ----------------------------- show running-config ----------------------------- Building configuration... !! Last configuration change at Wed Oct 10 20:05:13 2007 ! hostname P1_CRS-8 line console exec-timeout 600 0 session-timeout 600 ! line default exec-timeout 600 0 session-timeout 600show tech-support qos
To automatically run show commands that display platform independent Quality of Service (QoS) debugging information, use the show tech-support qos command in EXEC mode.
show tech-support qos pi [ file send-to ] [background] [ compressed | uncompressed ] [ location node-id | all ] [rack]
Syntax Description
pi
Collects platform independent QOS related information and saves to disk.
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
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.
rack
(Optional) Displays the list of racks.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
This command generates QoS 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.
Note
This command is not required during normal use of the router.
Task ID
Examples
The following example shows a sample output of platform independent QoS information for the show tech-support routing qos command:
RP/0/0/CPU0:router# show tech-support qos pi ------------------------------------------------------------------------------- show tech-support qos pi ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- show tech-support qos pi ------------------------------------------------------------------------------- +++++++++++++++ show version [09:11:30.767 UTC Mon Jan 18 2010] +++++++++++++++ Cisco IOS XR Software, Version 3.9.0[00] Copyright (c) 2009 by Cisco Systems, Inc. ROM: System Bootstrap, Version 1.1(20090521:183759) [ASR9K ROMMON], MCAST-6 uptime is 6 days, 21 hours, 34 minutes System image file is "bootflash:disk0/asr9k-os-mbi-3.9.0/mbiasr9k-rp.vm" cisco ASR9K Series (MPC8641D) processor with 4194304K bytes of memory. MPC8641D processor at 1333MHz, Revision 2.2 2 Management Ethernet 45 GigabitEthernet 219k bytes of non-volatile configuration memory. 975M bytes of compact flash card. 33994M bytes of hard disk. 1605616k bytes of disk0: (Sector size 512 bytes). 1605616k bytes of disk1: (Sector size 512 bytes). Configuration register on node 0/RSP0/CPU0 is 0x1922 Boot device on node 0/RSP0/CPU0 is disk0: Package active on node 0/RSP0/CPU0: asr9k-scfclient, V 3.9.0[00], Cisco Systems, at disk0:asr9k-scfclient-3.9.0 Built on Mon Dec 14 12:38:43 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-diags, V 3.9.0[00], Cisco Systems, at disk0:asr9k-diags-3.9.0 Built on Mon Dec 14 12:38:44 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-mcast, V 3.9.0[00], Cisco Systems, at disk0:asr9k-mcast-3.9.0 Built on Mon Dec 14 13:33:02 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-mpls, V 3.9.0[00], Cisco Systems, at disk0:asr9k-mpls-3.9.0 Built on Mon Dec 14 13:31:50 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-rout, V 3.9.0[00], Cisco Systems, at disk0:asr9k-rout-3.9.0 Built on Mon Dec 14 12:38:56 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-lc, V 3.9.0[00], Cisco Systems, at disk0:asr9k-lc-3.9.0 Built on Mon Dec 14 13:28:31 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-fwdg, V 3.9.0[00], Cisco Systems, at disk0:asr9k-fwdg-3.9.0 Built on Mon Dec 14 12:34:50 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-admin, V 3.9.0[00], Cisco Systems, at disk0:asr9k-admin-3.9.0 Built on Mon Dec 14 12:29:39 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-base, V 3.9.0[00], Cisco Systems, at disk0:asr9k-base-3.9.0 Built on Mon Dec 14 12:32:17 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-os-mbi, V 3.9.0[00], Cisco Systems, at disk0:asr9k-os-mbi-3.9.0 Built on Mon Dec 14 12:12:19 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 Boot device on node 0/1/CPU0 is mem: Package active on node 0/1/CPU0: asr9k-scfclient, V 3.9.0[00], Cisco Systems, at disk0:asr9k-scfclient-3.9.0 Built on Mon Dec 14 12:38:43 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-diags, V 3.9.0[00], Cisco Systems, at disk0:asr9k-diags-3.9.0 Built on Mon Dec 14 12:38:44 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-mcast, V 3.9.0[00], Cisco Systems, at disk0:asr9k-mcast-3.9.0 Built on Mon Dec 14 13:33:02 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-mpls, V 3.9.0[00], Cisco Systems, at disk0:asr9k-mpls-3.9.0 Built on Mon Dec 14 13:31:50 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-lc, V 3.9.0[00], Cisco Systems, at disk0:asr9k-lc-3.9.0 Built on Mon Dec 14 13:28:31 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-fwdg, V 3.9.0[00], Cisco Systems, at disk0:asr9k-fwdg-3.9.0 Built on Mon Dec 14 12:34:50 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-admin, V 3.9.0[00], Cisco Systems, at disk0:asr9k-admin-3.9.0 Built on Mon Dec 14 12:29:39 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-base, V 3.9.0[00], Cisco Systems, at disk0:asr9k-base-3.9.0 Built on Mon Dec 14 12:32:17 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-os-mbi, V 3.9.0[00], Cisco Systems, at disk0:asr9k-os-mbi-3.9.0 Built on Mon Dec 14 12:12:19 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 Boot device on node 0/2/CPU0 is mem: Package active on node 0/2/CPU0: asr9k-scfclient, V 3.9.0[00], Cisco Systems, at disk0:asr9k-scfclient-3.9.0 Built on Mon Dec 14 12:38:43 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-diags, V 3.9.0[00], Cisco Systems, at disk0:asr9k-diags-3.9.0 Built on Mon Dec 14 12:38:44 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-mcast, V 3.9.0[00], Cisco Systems, at disk0:asr9k-mcast-3.9.0 Built on Mon Dec 14 13:33:02 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-mpls, V 3.9.0[00], Cisco Systems, at disk0:asr9k-mpls-3.9.0 Built on Mon Dec 14 13:31:50 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-lc, V 3.9.0[00], Cisco Systems, at disk0:asr9k-lc-3.9.0 Built on Mon Dec 14 13:28:31 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-fwdg, V 3.9.0[00], Cisco Systems, at disk0:asr9k-fwdg-3.9.0 Built on Mon Dec 14 12:34:50 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-admin, V 3.9.0[00], Cisco Systems, at disk0:asr9k-admin-3.9.0 Built on Mon Dec 14 12:29:39 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-base, V 3.9.0[00], Cisco Systems, at disk0:asr9k-base-3.9.0 Built on Mon Dec 14 12:32:17 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 asr9k-os-mbi, V 3.9.0[00], Cisco Systems, at disk0:asr9k-os-mbi-3.9.0 Built on Mon Dec 14 12:12:19 UTC 2009 By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/asr9k/workspace for c4.2.1-p0 --------------- show version [09:11:31.646 UTC Mon Jan 18 2010] --------------- +++++++++++++++ show logging [09:11:31.751 UTC Mon Jan 18 2010] +++++++++++++++ Syslog logging: enabled (33 messages dropped, 0 flushes, 0 overruns) Console logging: Disabled Monitor logging: level debugging, 0 messages logged Trap logging: level informational, 0 messages logged Buffer logging: level debugging, 319 messages logged Log Buffer (10000000 bytes): RP/0/RSP0/CPU0::Jan 18 09:09:59.858 : config[65761]: %MGBL-SYS-5-CONFIG_I : Configured from console by lab RP/0/RSP0/CPU0::Jan 18 09:10:14.046 : config[65761]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'lab'. Use 'show configuration commit changes 1000000094' to view the changes. RP/0/RSP0/CPU0::Jan 18 09:10:14.066 : config[65761]: %MGBL-SYS-5-CONFIG_I : Configured from console by lab --------------- show logging [09:11:32.077 UTC Mon Jan 18 2010] --------------- +++++++++ show interfaces summary [09:11:32.183 UTC Mon Jan 18 2010] ++++++++++ Interface Type Total UP Down Admin Down -------------- ----- -- ---- ---------- ALL TYPES 49 5 1 43 -------------- IFT_GETHERNET 45 2 1 42 IFT_LOOPBACK 1 1 0 0 IFT_ETHERNET 2 1 0 1 IFT_NULL 1 1 0 0 --------- show interfaces summary [09:11:32.512 UTC Mon Jan 18 2010] ---------- ++++++++++ show interfaces brief [09:11:32.629 UTC Mon Jan 18 2010] +++++++++++ Intf Intf LineP Encap MTU BW Name State State Type (byte) (Kbps) -------------------------------------------------------------------------------- Lo0 up up Loopback 1500 Unknown Nu0 up up Null 1500 Unknown Mg0/RSP0/CPU0/0 up up ARPA 1514 100000 Mg0/RSP0/CPU0/1 admin-down admin-down ARPA 1514 10000 Gi0/1/0/0 down down ARPA 1514 1000000 Gi0/1/0/1 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/2 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/3 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/4 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/5 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/6 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/7 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/8 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/9 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/10 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/11 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/12 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/13 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/14 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/15 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/16 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/17 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/18 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/19 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/20 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/21 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/22 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/23 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/24 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/25 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/26 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/27 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/28 up up ARPA 1514 1000000 Gi0/1/0/29 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/30 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/31 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/32 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/33 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/34 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/35 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/36 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/37 admin-down admin-down ARPA 1514 1000000 Gi0/1/0/38 up up ARPA 1514 1000000 Gi0/1/0/39 admin-down admin-down ARPA 1514 1000000 Gi0/2/0/0 admin-down admin-down ARPA 1514 1000000 Gi0/2/0/1 admin-down admin-down ARPA 1514 1000000 Gi0/2/0/2 admin-down admin-down ARPA 1514 1000000 Gi0/2/0/3 admin-down admin-down ARPA 1514 1000000 Gi0/2/0/4 admin-down admin-down ARPA 1514 1000000 ---------- show interfaces brief [09:11:33.216 UTC Mon Jan 18 2010] ----------- +++++++++++ show running-config [09:11:33.325 UTC Mon Jan 18 2010] ++++++++++++ Building configuration... !! IOS XR Configuration 3.9.0 !! Last configuration change at Mon Jan 18 09:10:13 2010 by lab ! service unsupported-transceiver hostname MCAST-6 clock timezone UTC 5 logging console disable logging buffered 10000000 telnet vrf default ipv4 server max-servers 5 line console exec-timeout 0 0 ! ntp interface GigabitEthernet0/1/0/28 broadcast destination 10.0.0.1 ! server 8.42.10.1 master 6 ! ! class-map match-any a match precedence 1 end-class-map ! class-map match-any b match precedence 1 end-class-map ! policy-map a class b set dscp af11 ! class class-default ! end-policy-map ! flow monitor-map fmm record ipv4 cache entries 10000 cache timeout active 70 ! sampler-map smm random 1 out-of 1 ! interface Loopback0 ipv4 address 2.2.2.2 255.255.255.255 ! interface MgmtEth0/RSP0/CPU0/0 ipv4 address 8.42.10.12 255.255.255.0 ! interface MgmtEth0/RSP0/CPU0/1 shutdown ! interface GigabitEthernet0/1/0/0 negotiation auto l2transport ! ! interface GigabitEthernet0/1/0/1 shutdown ! interface GigabitEthernet0/1/0/2 shutdown ! interface GigabitEthernet0/1/0/3 shutdown ! interface GigabitEthernet0/1/0/4 shutdown ! interface GigabitEthernet0/1/0/5 shutdown ! interface GigabitEthernet0/1/0/6 shutdown ! interface GigabitEthernet0/1/0/7 shutdown ! interface GigabitEthernet0/1/0/8 shutdown ! interface GigabitEthernet0/1/0/9 shutdown ! interface GigabitEthernet0/1/0/10 shutdown ! interface GigabitEthernet0/1/0/11 shutdown ! interface GigabitEthernet0/1/0/12 shutdown ! interface GigabitEthernet0/1/0/13 shutdown ! interface GigabitEthernet0/1/0/14 shutdown ! interface GigabitEthernet0/1/0/15 shutdown ! interface GigabitEthernet0/1/0/16 shutdown ! interface GigabitEthernet0/1/0/17 shutdown ! interface GigabitEthernet0/1/0/18 shutdown ! interface GigabitEthernet0/1/0/19 shutdown ! interface GigabitEthernet0/1/0/20 shutdown ! interface GigabitEthernet0/1/0/21 shutdown ! interface GigabitEthernet0/1/0/22 shutdown ! interface GigabitEthernet0/1/0/23 shutdown ! interface GigabitEthernet0/1/0/24 shutdown ! interface GigabitEthernet0/1/0/25 shutdown ! interface GigabitEthernet0/1/0/26 shutdown ! interface GigabitEthernet0/1/0/27 shutdown ! interface GigabitEthernet0/1/0/28 service-policy input a ipv4 address 10.0.0.2 255.255.255.0 ! interface GigabitEthernet0/1/0/29 shutdown ! interface GigabitEthernet0/1/0/30 shutdown ! interface GigabitEthernet0/1/0/31 shutdown ! interface GigabitEthernet0/1/0/32 shutdown ! interface GigabitEthernet0/1/0/33 shutdown ! interface GigabitEthernet0/1/0/34 shutdown ! interface GigabitEthernet0/1/0/35 shutdown ! interface GigabitEthernet0/1/0/36 shutdown ! interface GigabitEthernet0/1/0/37 shutdown ! interface GigabitEthernet0/1/0/38 negotiation auto l2transport ! ! interface GigabitEthernet0/1/0/39 shutdown ! interface GigabitEthernet0/2/0/0 shutdown ! interface GigabitEthernet0/2/0/1 shutdown ! interface GigabitEthernet0/2/0/2 shutdown ! interface GigabitEthernet0/2/0/3 shutdown ! interface GigabitEthernet0/2/0/4 shutdown ! router static address-family ipv4 unicast 1.1.1.1/32 GigabitEthernet0/1/0/38 202.153.0.0/16 MgmtEth0/RSP0/CPU0/0 ! ! router ospf 100 router-id 2.2.2.2 area 0 interface Loopback0 ! interface GigabitEthernet0/1/0/28 ! ! ! l2vpn bridge group bg bridge-domain bd igmp snooping profile prof1 interface GigabitEthernet0/1/0/0 ! interface GigabitEthernet0/1/0/38 ! ! ! ! igmp snooping profile prof1 ttl-check disable router-alert-check disable ! end ----------- show running-config [09:11:33.742 UTC Mon Jan 18 2010] ------------ ++++++++++++++ show platform [09:11:33.851 UTC Mon Jan 18 2010] +++++++++++++++ Failed to spawn executable shelfmgr_show_hfr: 2, No such file or directory The following show command failed: show platform -------------- show platform [09:11:34.068 UTC Mon Jan 18 2010] --------------- ++++++++++ show policymap targets [09:11:34.177 UTC Mon Jan 18 2010] ++++++++++ 1) Policymap: a Type: qos Targets (applied as main policy): GigabitEthernet0/1/0/28 input Total targets: 1 Targets (applied as child policy): Total targets: 0 ---------- show policymap targets [09:11:35.467 UTC Mon Jan 18 2010] ----------show tech-support rdsfs
To 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 ] [rack] }
Syntax Description
terminal
Displays the 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:
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.
rack
(Optional) Displays the list of racks.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software command references are located at the following URL:
http://www.cisco.com/en/US/products/ps5845/prod_command_reference_list.html
Task ID
show tech-support rib
To 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
terminal
Displays the 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:
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.
ipv4
(Optional) Displays the IPv4 command output.
ipv6
(Optional) Displays the IPv6 command output.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software command references are located at the following URL:
http://www.cisco.com/en/US/products/ps5845/prod_command_reference_list.html
Task ID
show tech-support routing bfd
To 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 ] [rack] }
Syntax Description
terminal
Displays the 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.
sent-to
Name of the file. The following valid options are listed:
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.
rack
(Optional) Displays the list of racks.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
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 routing bfd command:
- show bfd session
- show bfd
- show memory heap fail all
- show memory summary location all
- show process blocked location all
- show adjacency
- show bfd location
- show bfd session detail location node-id
- show bfd session agent detail location
- 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
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 routing bfd command output:
RP/0/0/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 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_4_CPU1 ------------------------------------------------------------------ Physical Memory: 4096M total Application Memory : 3947M (3518M available) Image: 19M (bootram: 19M) Reserved: 128M, IOMem: 2028M, flashfsys: 0 Total shared window: 21M node: node0_6_CPU0 ------------------------------------------------------------------ Physical Memory: 2048M total Application Memory : 1905M (1408M available) Image: 14M (bootram: 14M) Reserved: 128M, IOMem: 2028M, flashfsys: 0 Total shared window: 55M 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 ------------------------------ Location: 0/1/CPU0 IPV4 Sessions Up: 0, Down: 0, Standby: 0, Total: 0 Location: 0/1/SP . . .show tech-support routing isis
To 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
terminal
Displays the 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.
sent-to
Name of the file. The following valid options are listed:
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
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 routing isis command:
- show isis trace all location 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
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 routing isis command output:
RP/0/0/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_START Mar 29 08:38:18.437 isis/isp/sev 0/RP0/CPU0 t1 STARTUP_MODULE Mar 29 08:38:18.438 isis/isp/sev 0/RP0/CPU0 t1 STARTUP_MODULE Mar 29 08:38:18.438 isis/isp/sev 0/RP0/CPU0 t1 THREAD_CREATING Mar 29 08:38:18.451 isis/isp/det 0/RP0/CPU0 t1 THREAD_THREAD_ID Mar 29 08:38:18.451 isis/isp/sev 0/RP0/CPU0 t1 THREAD_CREATING Mar 29 08:38:18.451 isis/isp/sev 0/RP0/CPU0 t1 THREAD_CREATING Mar 29 08:38:18.452 isis/isp/sev 0/RP0/CPU0 t1 THREAD_CREATING Mar 29 08:38:18.452 isis/isp/sev 0/RP0/CPU0 t1 THREAD_CREATING Mar 29 08:38:18.536 isis/isp/sev 0/RP0/CPU0 t1 STARTUP_MODULE Mar 29 08:38:19.274 isis/isp/sev 0/RP0/CPU0 t1 STARTUP_MODULE Mar 29 08:38:19.470 isis/isp/sev 0/RP0/CPU0 t1 IO_PAK_SERVER_CONNECTED Mar 29 08:38:19.551 isis/isp/det 0/RP0/CPU0 t1 IO_SOCKET_CREATE_SUCCESS Mar 29 08:38:19.555 isis/isp/sev 0/RP0/CPU0 t1 IO_SOCKET_CONN_OPEN Mar 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_PROCESS Mar 29 08:38:27.622 isis/isp/det 0/RP0/CPU0 t4 SSM_TICK_TIMER_FIRES CR-SYNC-LSPDB Mar 29 08:38:27.622 isis/isp/det 0/RP0/CPU0 t4 SSM_STATE_RESULT CR-SYNC-LSPDB Mar 29 08:38:27.622 isis/isp/det 0/RP0/CPU0 t4 SSM_STATE_TIME_BUDGET CR-SYNC-LSPDB Mar 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 found No IS-IS isp levels found No IS-IS isp levels found No IS-IS isp levels found No IS-IS isp levels found No IS-IS isp levels found No IS-IS isp levels found No IS-IS isp levels found No IS-IS isp levels found No IS-IS isp IPv4 Unicast levels found No IS-IS isp IPv4 Unicast levels found No IS-IS isp IPv4 Unicast levels found No IS-IS isp IPv4 Unicast levels found No IS-IS isp IPv4 Unicast levels found IS-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): 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 Interfaces POS0/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 L1L2 Up 0 0 0 Init 0 0 0 Failed 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 0 Pseudo nodes: 0 0 0 0 0 0 Total nodes: 0 0 0 0 0 0 IS-IS isp IPv4 Unicast routes 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 interface Interface Handle CircNum DIS Areas Adj Chkpt ID No 'checkpoint interfaces' found in IS-IS isp IS-IS isp checkpoint adjacencies System ID Interface SNPA Lvl Hold Pri CID Chkpt ID Nexthops No 'checkpoint adjacencies' found in IS-IS isp IS-IS isp checkpoint LSPs Level 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 ago Total number of packets sent: 0 Total number of packets received: 0 Send packets dropped, total: 0 Send packets dropped, buffer overflow: 0 Send packets dropped, out of memory: 0 Send packets dropped, netio: 0 Send packets dropped, other: 0 Receive socket max queue size: 0 Receive packets dropped, total: 0 Receive packets dropped, other: 0 Receive packets dropped per pdu class: Class Overflow/Max Rate Limit/Max IIH 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: 4 control parent: 0x00000000 data parent: 0x00000000 protocol capsulation state mtu --------------- -------------------- --------------- -------- 7 (arp) .show tech-support routing ospf
To 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] [no-trace] [ active | standby ] { terminal [page] | file send-to [background] [ compressed | uncompressed ] }
Syntax Description
process-id
(Optional) Name of the OSPF process.
no-trace
(Optional) Excludes trace information from the command output.
active
(Optional) Displays information from active route processor only.
standby
(Optional) Displays information from standby route processor only.
terminal
Displays the 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.
sent-to
Name of the file. The following valid options are listed:
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
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 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
- 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
Note
- If you do not specify any options, all information is collected by default.
- Active and standby options are exclusive and only one of them can be used. When neither active or standby is used, the information is collected from both RPs.
- The no-trace option can be used with or without specifying the active or standby options.
- When standby option is specified, only ospf- related information from the standby RP is included in the output. The common non-ospf information such as version, placement info, logging and so on are not included.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 routing ospf command output:
RP/0/0/CPU0:router# show tech-support routing ospf terminal page ------------------------------------------------------------------------------- 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 12 Number of OSPF interfaces up 12 Number of OSPF virtual interfaces up 0 Number of neighbors 9 Number of neighbors adjacent 9 Number 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 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 0 GigabitEthernet0/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 0 GigabitEthernet0/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 0 POS0/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 . .show tech-support routing ospfv3
To 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
instance
(Optional) Name of the OSPFv3 instance.
detail
(Optional) Displays all available OSPFv3 information.
terminal
Displays the 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.
sent-to
Name of the file. The following valid options are listed:
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
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 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
- show ospfv3 database
- show ospfv3 route
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 a truncated output of the show tech-support routing ospfv3 command:
RP/0/0/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.9.0 Copyright (c) 2009 by Cisco Systems, Inc. ROM: System Bootstrap, Version 1.51(20080807:092259) [<router_type> ROMMON], Router uptime is 6 days, 16 hours, 38 minutes System 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 Ethernet 16 GigabitEthernet 20 SONET/SDH 20 Packet over SONET/SDH 1019k 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 0x102 Boot 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.0I Built on Wed Oct 29 17:03:08 DST 2008 By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0 hfr-pagent, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-pagent-3.8.0.20I Built on Wed Oct 29 17:24:33 DST 2008 By 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.20I Built on Wed Oct 29 17:02:19 DST 2008 By 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.20I Built on Wed Oct 29 17:02:01 DST 2008 By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0 hfr-mcast, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-mcast-3.8.0.20I Built on Wed Oct 29 18:18:37 DST 2008 By 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.20I Built on Wed Oct 29 18:18:25 DST 2008 By 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.20I Built on Wed Oct 29 16:18:36 DST 2008 By 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.20I Built on Wed Oct 29 16:13:27 DST 2008 By iox30.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0 hfr-admin, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-admin-3.8.0.20I Built on Wed Oct 29 16:08:13 DST 2008 By 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.20I Built on Wed Oct 29 16:07:35 DST 2008 By 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.20I Built on Wed Oct 29 15:45:48 DST 2008 By iox30.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0 Configuration register on node 0/4/CPU0 is 0x102 Boot 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.0I Built on Wed Oct 29 17:03:08 DST 2008 By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0 hfr-pagent, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-pagent-3.8.0.20I Built on Wed Oct 29 17:24:33 DST 2008 By iox13.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0 hfr-doc, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-doc-3.8.0.20I Built on Wed Oct 29 17:02:31 DST 2008 By 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 Built on Wed Oct 29 17:02:19 DST 2008 By 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.20I Built on Wed Oct 29 17:02:01 DST 2008 By 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.20I Built on Wed Oct 29 16:59:58 DST 2008 By 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.20I Built on Wed Oct 29 16:31:48 DST 2008 By sjc5-gf-021.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/h0 hfr-mcast, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-mcast-3.8.0.20I Built on Wed Oct 29 18:18:37 DST 2008 By 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.20I Built on Wed Oct 29 18:18:25 DST 2008 By iox22.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0 hfr-rout, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-rout-3.8.0.20I Built on Wed Oct 29 16:21:29 DST 2008 By iox30.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.20I Built on Wed Oct 29 16:18:36 DST 2008 By 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.20I Built on Wed Oct 29 16:13:27 DST 2008 By iox30.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0 hfr-admin, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-admin-3.8.0.20I Built on Wed Oct 29 16:08:13 DST 2008 By 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.20I Built on Wed Oct 29 16:07:35 DST 2008 By 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.20I Built on Wed Oct 29 15:45:48 DST 2008 By iox30.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0 Configuration register on node 0/4/CPU1 is 0x102 Boot 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.0I Built on Wed Oct 29 17:03:08 DST 2008 By iox3.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/work0 hfr-pagent, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-pagent-3.8.0.20I Built on Wed Oct 29 17:24:33 DST 2008 By iox13.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0 hfr-doc, V 3.8.0.20I[DT_IMAGE], Cisco Systems, at disk0:hfr-doc-3.8.0.20I Built on Wed Oct 29 17:02:31 DST 2008 By 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 Built on Wed Oct 29 17:02:19 DST 2008 By 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.20I Built on Wed Oct 29 17:02:01 DST 2008 By 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.20I Built on Wed Oct 29 16:59:58 DST 2008 By iox26.cisco.com in /auto/ioxbuild6/production/3.8.0.20I.DT_IMAGE/hfr/wor0 --More--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
terminal
Displays the 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.
sent-to
Name of the file. The following valid options are listed:
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
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 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
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 routing rpl command output:
RP/0/0/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 100 router-id 10.2.2.2 nsf cisco area 0 mpls traffic-eng interface Bundle-POS24 ! interface Loopback0 passive enable ! interface GigabitEthernet0/1/5/1 ! interface GigabitEthernet0/1/5/2 bfd 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 DST router isis lab is-type level-2-only net 49.1122.0000.0000.0002.00 interface Loopback0 passive address-family ipv4 unicast ! ! interface POS0/1/0/2 address-family ipv4 unicast ! ! interface POS0/1/0/3 address-family ipv4 unicast ! ! ! Mon Nov 10 18:53:04.699 PST DST % No such configuration item(s) Mon Nov 10 18:53:05.457 PST DST router eigrp 24 vrf vrf_1 address-family ipv4 router-id 172.20.0.0 default-metric 100000 4000 200 45 4470 autonomous-system 6 redistribute connected interface GigE0/1/0/0 site-of-origin 201:1 ! ! ! ! Mon Nov 10 18:53:06.181 PST DST % No such configuration item(s) Mon Nov 10 18:53:07.004 PST DST ------------------------------------------------------------------------------- show process policy_repository ------------------------------------------------------------------------------- Job Id: 312 PID: 794895 Executable path: /disk0/hfr-rout-3.8.0.20I/bin/policy_repository Instance #: 1 Version ID: 00.00.0000 Respawn: ON Respawn count: 2 Max. spawns per minute: 12 Last started: Tue Nov 4 02:56:20 2008 Process state: Run (last exit status : 203) Package state: Normal Started on config: cfg/gl/policy_lang/policies/ core: MAINMEM Max. core: 0 Level: 172 Placement: ON startup_path: /pkg/startup/pr.startup Ready: 10.672s Process cpu time: 0.198 user, 0.046 kernel, 0.244 total JID TID Stack pri state TimeInState HR:MM:SS:MSEC NAME 312 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 DST SysDB 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' 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/.' --More-show tech-support serial
To automatically run show commands that display information specific to serial debugging, use the show tech-support serial command in EXEC mode.
show tech-support serial { terminal [page] | file send-to [background] [ compressed | uncompressed ] } [ interface type instance ] [show-only] [trace-only] [ location node-id | all ]
Syntax Description
file
Specifies that the command output is saved to a specified file.
sent-to
Name of the file. The following valid options are listed:
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.
interface
(Optional) Collects information about a specific interface.
type
Interface type. For more information, use the question mark (?) online help function.
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.
For more information about the syntax for the router, use the question mark (?) online help function.
show-only
(Optional) Collects only show command information.
terminal
Specifies that the command output is displayed on the terminal.
trace-only
(Optional) Collects only trace information.
location
(Optional) Specifies a node.
node-id
(Optional). Node ID. The node-id argument is entered in the rack/slot/module notation.
all
(Optional) Specifies all locations.
page
(Optional) Specifies that the command output is displayed one 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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 serial command for serial-related data, such as T1/E1. This command generates serial 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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 serial command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support serial terminal page ------------------------------------------------------------------------------- show tech-support serial ------------------------------------------------------------------------------- ----------------------------- show running-config ----------------------------- Building configuration... !! Last configuration change at Wed Oct 10 20:05:13 2007 ! hostname P1_CRS-8 line console exec-timeout 600 0 session-timeout 600 ! line default exec-timeout 600 0 session-timeout 600 ! clock timezone PST 8 clock summer-time DST recurring 2 sunday march 02:00 first sunday november 02:00 logging console informational telnet vrf default ipv4 server max-servers no-limit domain ipv4 host p1 172.29.52.72 domain ipv4 host p2 172.29.52.77 domain ipv4 host ce6 172.29.52.73 domain ipv4 host ce7 172.29.52.78 domain ipv4 host p11 172.29.52.83 domain ipv4 host pe6 172.29.52.128 domain ipv4 host pe7 172.29.52.182 domain ipv4 host ce25 172.29.52.85 domain ipv4 host ce28 172.29.52.1 domain ipv4 host ce29 172.29.52.178 domain ipv4 host pe21 172.29.52.163 domain ipv4 host pe22 172.29.52.219 domain ipv4 host ce28_nme 172.29.52.177 domain ipv4 host ce29_nme 172.29.52.179 domain lookup disable username 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 25 alias cr copy run disk0:/usr/P1_base_config alias sa show alias alias sc show config commit list alias sd show diag alias si show ip int brief alias sl show led alias sm show mpls forwarding alias sp show platform alias sr show run alias su show users alias sv show version alias sir show ip route control-plane management-plane inband interface all allow all ! ! ! ! ipv4 virtual address 172.29.52.72 255.255.255.0 hw-module service sbc location 0/4/CPU0 hw-module service sbc location 0/4/CPU1 interface 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.0show tech-support sanitized
To 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 ] [rack]
Syntax Description
terminal
Displays the 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.
sent-to
Name of the file. The following valid options are listed:
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.
all
(Optional) Specifies all locations.
rack
(Optional) Displays the list of racks.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 sanitized command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support sanitized terminal page ------------------------------------------------------------------------------- show tech-support ------------------------------------------------------------------------------- ----------------------- 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> 8 clock summer-time <removed> recurring 2 sunday march 02:00 first sunday novembe0 logging console informational telnet vrf <removed> ipv4 server max-servers no-limit domain ipv4 host <removed> 10.0.0.1 domain ipv4 host <removed> 10.0.0.2 domain ipv4 host <removed> 10.0.0.3 domain ipv4 host <removed> 10.0.0.4 domain ipv4 host <removed> 10.0.0.5 domain ipv4 host <removed> 10.0.0.6 domain ipv4 host <removed> 10.0.0.7 domain ipv4 host <removed> 10.0.0.8 domain ipv4 host <removed> 10.0.0.9 domain ipv4 host <removed> 10.0.0.10 domain ipv4 host <removed> 10.0.0.11 domain ipv4 host <removed> 10.0.0.12 domain ipv4 host <removed> 10.0.0.13 domain ipv4 host <removed> 10.0.0.14 domain lookup disable username <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 25 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> alias <removed> <removed> control-plane management-plane inband interface all allow all ! ! ! ! ipv4 virtual address 10.0.0.14 255.0.0.0 hw-module service sbc location 0/4/CPU0 hw-module service sbc location 0/4/CPU1 interface 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 ! 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 ! 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/0show tech-support services
To 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
diversion
Collects information about packet diversion.
terminal
Displays the 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.
sent-to
Name of the file. The following valid options are listed:
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.
all
(Optional) Specifies all locations.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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 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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 services command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support services diversion terminal page ------------------------------------------------------------------------------- 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,MON 0/1/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON 0/1/1 MSC(SPA) 4T3E3 OK PWR,NSHUT,MON 0/1/4 MSC(SPA) 4XOC48-POS OK PWR,NSHUT,MON 0/1/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON 0/4/CPU0 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON 0/4/CPU1 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON 0/6/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON 0/6/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON 0/6/4 MSC(SPA) 8XOC3/OC12-POS OK PWR,NSHUT,MON 0/6/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON 0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 0/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 role Node 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 ago Active 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 role Node 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 ago Active 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 role Partner node (0/RP1/CPU0) is in STANDBY role Standby node in 0/RP1/CPU0 is ready Standby 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 ago Active node booted Thu Oct 11 19:18:01 2007: 6 days, 17 hours, 31 minutes ago Standby node boot Thu Oct 11 19:17:51 2007: 6 days, 17 hours, 31 minutes ago Standby node last went not ready Thu Oct 11 20:13:05 2007: 6 days, 16 hours, 36o Standby node last went ready Thu Oct 11 20:13:06 2007: 6 days, 16 hours, 36 mino Standby node last went not NSR-ready Thu Oct 11 19:29:45 2007: 6 days, 17 hourso Standby node last went NSR-ready Thu Oct 11 19:29:45 2007: 6 days, 17 hours, 19o There 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 = 5 Crash time: Mon Oct 15, 2007: 04:54:16 Core 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 00000000show tech-support snmp
To automatically run show commands that display information specific to tech-support information related to Simple Network Management Protocol (SNMP) agent, use the show tech-support snmp command in EXEC mode.
Syntax Description
entitymib
(Optional) Displays the entitymib debugging information.
ifmib
(Optional) Displays the ifmib debugging information.
rack
(Optional) Displays the list of racks.
file
Specifies that the command output is saved to a specified file.
send-to
Name of the file. The following valid options are listed:
location
(Optional) Specifies a node.
node-id
(Optional). Node ID. The node-id argument is entered in the rack/slot/module notation.
all
(Optional) Specifies all locations.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR Software command references for information about these commands and descriptions of their command output. The Cisco IOS XR Software command references are located at the following URL:
http://www.cisco.com/en/US/products/ps5845/prod_command_reference_list.html
Task ID
show tech-support spaipc
To 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.
sent-to
Name of the file. The following valid options are listed:
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.
interface
(Optional) Collects information about a specific interface.
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.
show-only
(Optional) Collects only show command information.
terminal
Displays the command output on the terminal.
trace-only
(Optional) Collects only trace information.
location
(Optional) Specifies a node.
node-id
(Optional). Node ID. The node-id argument is entered in the rack/slot/module notation.
all
(Optional) Specifies all locations.
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 how to run the show tech-support spaipc command:
RP/0/0/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-8 line console exec-timeout 600 0 session-timeout 600 ! line default exec-timeout 600 0 session-timeout 600 ! clock timezone PST 8 clock summer-time DST recurring 2 sunday march 02:00 first sunday november 02:00 logging console informational telnet vrf default ipv4 server max-servers no-limit domain ipv4 host p1 172.29.52.72 domain ipv4 host p2 172.29.52.77 domain ipv4 host ce6 172.29.52.73 domain ipv4 host ce7 172.29.52.78 domain ipv4 host p11 172.29.52.83 domain ipv4 host pe6 172.29.52.128 domain ipv4 host pe7 172.29.52.182 domain ipv4 host ce25 172.29.52.85 domain ipv4 host ce28 172.29.52.1 domain ipv4 host ce29 172.29.52.178 domain ipv4 host pe21 172.29.52.163 domain ipv4 host pe22 172.29.52.219 domain ipv4 host ce28_nme 172.29.52.177 domain ipv4 host ce29_nme 172.29.52.179 domain lookup disable username 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 25 alias cr copy run disk0:/usr/P1_base_config alias sa show alias alias sc show config commit list alias sd show diag alias si show ip int brief alias sl show led alias sm show mpls forwarding alias sp show platform alias sr show run alias su show users alias sv show version alias sir show ip route control-plane management-plane inband interface all allow all ! ! ! ! ipv4 virtual address 172.29.52.72 255.255.255.0 hw-module service sbc location 0/4/CPU0 hw-module service sbc location 0/4/CPU1 interface 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 ! 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/5show tech-support sysdb
To 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 | rack ] [ location node-id ]
Syntax Description
terminal
Displays the 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.
sent-to
Name of the file. The following valid options are listed:
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.
shared-plane
(Optional) Displays the data for the shared plane.
rack
(Optional) Displays the list of racks.
location
(Optional) Specifies a node.
node-id
(Optional). Node ID. The node-id argument is entered in the rack/slot/module notation.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 sysdb command output that is displayed on the terminal:
RP/0/0/CPU0:router# show tech-support sysdb terminal page ------------------------------------------------------------------------------- show tech-support sysdb on location all ------------------------------------------------------------------------------- -------------------------------- show platform -------------------------------- Node Type PLIM State Config State ----------------------------------------------------------------------------- 0/1/CPU0 L3 Service Eng N/A IOS XR RUN PWR,NSHUT,MON 0/2/CPU0 L3LC Eng 5+ Jacket Card IOS XR RUN PWR,NSHUT,MON 0/2/0 SPA SPA-4XOC3-POS-V READY PWR,NSHUT 0/2/1 SPA SPA-IPSEC-2G-2 READY PWR,NSHUT 0/4/CPU0 L3LC Eng 5+ Jacket Card IOS XR RUN PWR,NSHUT,MON 0/4/0 SPA SPA-2X1GE-V2 READY PWR,NSHUT 0/4/1 SPA SPA-8X1FE-TX-V2 READY PWR,NSHUT 0/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 role Node 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 ago Active 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 /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 r3 registers_info: R0 00000020 481ffad0 4823b6c0 481ffb38 registers_info: r4 r5 r6 r7 registers_info: R4 00000000 0000000c 00000000 fc24c618 registers_info: r8 r9 r10 r11 registers_info: R8 fc250000 fc250000 481fffc0 00000000 registers_info: r12 r13 r14 r15 registers_info: R12 48231ee8 4823b510 481ffbb0 00000002 registers_info: r16 r17 r18 r19 registers_info: R16 481ffbc4 00000001 00000000 00000000 registers_info: r20 r21 r22 r23 registers_info: R20 00000001 481ffb38 00000001 48230000 registers_info: r24 r25 r26 r27 registers_info: R24 48220000 24000024 48238e60 00000000 registers_info: r28 r29 r30 r31 registers_info: R28 00000001 481ffaf8 48230000 00000000show tech-support terminal
To automatically run show commands that display information specific to the terminal, use the show tech-support terminal command in EXEC mode.
Syntax Description
location
(Optional) Specifies a node.
node-id
(Optional). Node ID. The node-id argument is entered in the rack/slot/module notation.
all
(Optional) Specifies all locations.
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.
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
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.
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.
Note
This command is not required during normal use of the router.
See the Cisco IOS XR software command references for information about these commands and descriptions of their command output. The Cisco IOS XR software 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 terminal command output:
RP/0/0/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-8 line console exec-timeout 600 0 session-timeout 600 ! line default exec-timeout 600 0 session-timeout 600 ! clock timezone PST 8 clock summer-time DST recurring 2 sunday march 02:00 first sunday november 02:00 logging console informational telnet vrf default ipv4 server max-servers no-limit domain ipv4 host p1 172.29.52.72 domain ipv4 host p2 172.29.52.77 domain ipv4 host ce6 172.29.52.73 domain ipv4 host ce7 172.29.52.78 domain ipv4 host p11 172.29.52.83 domain ipv4 host pe6 172.29.52.128 domain ipv4 host pe7 172.29.52.182 domain ipv4 host ce25 172.29.52.85 domain ipv4 host ce28 172.29.52.1 domain ipv4 host ce29 172.29.52.178 domain ipv4 host pe21 172.29.52.163 domain ipv4 host pe22 172.29.52.219 domain ipv4 host ce28_nme 172.29.52.177 domain ipv4 host ce29_nme 172.29.52.179 domain lookup disable username 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 25 alias cr copy run disk0:/usr/P1_base_config alias sa show alias alias sc show config commit list alias sd show diag alias si show ip int brief alias sl show led alias sm show mpls forwarding alias sp show platform alias sr show run alias su show users alias sv show version alias sir show ip route control-plane management-plane inband interface all allow all ! ! ! ! ipv4 virtual address 172.29.52.72 255.255.255.0 hw-module service sbc location 0/4/CPU0 hw-module service sbc location 0/4/CPU1 interface 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 ! 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.2
