-
Cisco IOS XR Troubleshooting Guide for the Cisco CRS-1 Router
-
Preface
-
General Troubleshooting
-
Troubleshooting Booting
-
Troubleshooting Forwarding
-
Troubleshooting Router Switch Fabric
-
Troubleshooting Interfaces
-
Troubleshooting the Control Plane Ethernet Network
-
Collecting System Information
-
Process Monitoring and Troubleshooting
-
Troubleshooting Memory
-
Troubleshooting Upgrading and Downgrading Software
-
Troubleshooting the Statistics Infrastructure
-
Multiprotocol Label Switching Checklist
-
Troubleshooting Load Balancing
-
Index
-
Feedback
Table Of Contents
Troubleshooting the Control Plane Ethernet Network
Cisco CRS-1 Control Plane Ethernet Network Overview
Using the Online Diagnostics Tools
Troubleshooting Booting the System Control Plane Ethernet Network
Troubleshooting the Multishelf System Router Topology
Troubleshooting the Catalyst Switch
Troubleshooting the CRS-1, 4-slot, 8-slot, or 16-slot System Router Topology
Troubleshooting the Control Plane Ethernet Network
This chapter describes techniques that you can use to troubleshoot the control plane Ethernet network on routers using Cisco IOS XR software. It includes the following sections:
•
Cisco CRS-1 Control Plane Ethernet Network Overview
•
•
•
•
Cisco CRS-1 Control Plane Ethernet Network Overview
The system control plane Ethernet network is used for processes on different devices to communicate for functions such as system device discovery, image transfers, heartbeat messages, alarms, and configuration management.
All devices in a system using Cisco IOS XR software connect to the system control plane Ethernet network. There are two control planes in the control Ethernet topology:
•
•
See Figure 6-1 for an illustration of the Cisco CRS-1 control plane Ethernet network
See Figure 6-2 for an illustration of the Cisco CRS-1 Multishelf System control plane Ethernet network. Two external Catalyst switches (WS-C6509-NEB-A) are used to provide connectivity between the FCC and LCCs. In the Cisco CRS-1 Multishelf System, the system control plane links from each route processor (RP) and shelf controller (SC) connect to an external Catalyst switch. RPs and SCs are not directly connected to each other. See Figure 6-2.
Figure 6-1 Cisco CRS-1 Control Ethernet Topology
Figure 6-2 Cisco CRS-1 Multishelf System Control Ethernet Topology
Using the Online Diagnostics Tools
The online diagnostics tools can alert you to potential problems in the control plane connections between the Fabric Card Chassis and the Line Card Chassis. For information on using the online diagnostics, see the "Using Diagnostic Commands" section.
Troubleshooting Booting the System Control Plane Ethernet Network
To verify and troubleshoot booting the Cisco CRS-1 system control plane Ethernet network, perform the following procedures.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
a.
b.
c.
d.
7.
8.
a.
b.
9.
DETAILED STEPS
Step 1
show platform
Example:RP/0/RP0/CPU0:router# show platform
Displays information about the status of cards and modules installed in the router.
Verify that the expected nodes display IOS XR RUN under the State column of the command output.
Step 2
admin debug shelfmgr boot
Example:RP/0/RP0/CPU0:router# admin debug shelfmgr boot
If no output is displayed, the shelfmgr is not receiving boot requests.
Step 3
show controllers backplane ethernet clients all location node-id
Example:RP/0/RP0/CPU0:router# show controllers backplane ethernet clients all location 0/RP1/CPU0
Displays information about all local client applications. Each row contains the client ID, product identifier (PID) of the process that is registered to receive packets with that client ID and a description of the client.
The eth_server allows client processes to send and receive packets over the control Ethernet. eth_server uses client IDs to demultiplex packets that arrive at the node.
Two client IDs in the output are important for troubleshooting boot problems:
•
•
Step 4
show controllers backplane ethernet local clients 13 statistics location node-id
Example:RP/0/RP0/CPU0:router# show controllers backplane ethernet clients 13 statistics location 0/RP1/CPU0
Displays a list of client statistics for the specified client ID.
Check the values for:
•
•
If they contain values other than 0, boot requests have been received and replies have been sent (packets output). Proceed to Step 5.
If they contain values of 0, check the system control plane Ethernet network physical connectivity. See Cisco CRS-1 Carrier Routing System Multishelf System Interconnection and Cabling Guide for details on system control plane Ethernet network cabling.
If there are no problems with the physical connectivity, contact Cisco Technical Support. For Cisco Technical Support contact information, see the "Obtaining Documentation and Submitting a Service Request" section in the Preface.
Step 5
show controllers switch {0 | 1} statistics location node-id
Example:RP/0/RP0/CPU0:router# show controllers switch 0 statistics location 0/RP1/CPU0
Display statistics on all ports on the switch controllers. The location node-id keyword and argument are required for obtaining information on the remote RPs and SCs.
Step 6
admin
config-register 0x0
exit
reload
Example:RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# config-register 0x0
RP/0/RP0/CPU0:router(admin)# exit
RP/0/RP0/CPU0:router# reload
Places the DSC in ROMMON mode.
Step 7
show_bcm_links
Example:rommon B1 > show_bcm_links
Note
This command is used to confirm connectivity from the RP or SC to the Catalyst switch in ROM monitor (ROMMON) mode. See Cisco IOS XR ROM Monitor Guide for the Cisco CRS-1 Router for detailed information on entering ROMMON mode.
Displays the connectivity state of the links to the onboard Ethernet switch as well as the system control plane links to the standby RP and remote Catalyst switch.
Verify that all expected active ports are displayed. If no connectivity is detected by a particular port, it is not displayed in the output. GE Port 1 must be active, because this is the port on the switch used for external connectivity. GE Port 2 is the link to the secondary switch, so it should also be active.
Step 8
confreg 0x102
reset
Example:rommon B2 > confreg 0x102
rommon B3 > reset
Exits ROMMON mode, resetting and initializing the router.
Step 9
Contact Cisco Technical Support if the problem is not resolved.
If the problem is not resolved, contact Cisco Technical Support. For Cisco Technical Support contact information, see the "Obtaining Documentation and Submitting a Service Request" section in the Preface.
Examples
The following example shows that all expected nodes in the Cisco CRS-1 Multishelf System are in the run state:
RP/0/RP0/CPU0:router# show platformNode Type PLIM State Config State-----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON0/1/CPU0 MSC 4OC192-POS/DPT IOS XR RUN PWR,NSHUT,MON0/8/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON0/8/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON0/FC0/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON0/FC1/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON0/AM1/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM0/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON1/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON1/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON1/FC0/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON1/FC1/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON1/AM1/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON1/SM0/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON1/SM1/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON1/SM4/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MON1/SM5/SP FC/M(SP) N/A IOS XR RUN PWR,NSHUT,MONF0/SM0/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM1/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM4/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM5/SP FCC-SFC(SP) N/A IOS XR RUN PWR,NSHUT,MONF0/SC0/CPU0 FCC-SC(Standby) N/A IOS XR RUN PWR,NSHUT,MONF0/SC1/CPU0 FCC-SC(Active) N/A IOS XR RUN PWR,NSHUT,MONF0/AM1/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MONF0/LM0/SP FCC-LED(SP) N/A IOS XR RUN PWR,NSHUT,MONThe following example shows the current state of each eth_server client in the Cisco CRS-1 Multishelf System:
RP/0/RP0/CPU0:router# show controllers backplane ethernet clients allIntf Client ethernet Client DescriptionName server id Process Id------------------------------------------------------------------------------FE0_RP1_0 1 24601 QNX network manager2 53317 Group services3 0 Reserved for Attach4 53338 Plugin controller5 53298 Designated SC... ... ...13 53338 Card Configuration Protocol... ... ...22 0 Test client out-of-bandThe following example shows that there are 18 nodes in the Cisco CRS-1 Multishelf System in the run state, which means that 18 boot requests have been received by eth_server and 18 replies have been sent:
RP/0/RP0/CPU0:router# show controller backplane ethernet clients 13 statistics location 0/RP1/CPU0Client ShelfMgr, ES Client Id 13, PID 53338 running on FastEthernet0_RP1_018 packets input, 8676 bytes18 packets delivered, 8676 bytes0 packets discarded (0 bytes) in garbage collection0 (0 bytes) unicast packets filtered0 (0 bytes) multicast packets filtered0 (0 bytes) buffer mgmt policy discards0 (0 bytes) locking error discards18 packets output, 8676 bytes, 0 could not be transmittedThe following example shows that the switch located on the RP sent data towards Port 2 that connects to line card 1 (LC1) in the Cisco CRS-1 Multishelf System:
RP/0/RP0/CPU0:router# show controllers switch 1 statisticsPort Tx Frames Tx Errors Rx Frames Rx Errors Connects----------------------------------------------------------------1 : 382714 0 132876 2 0/LC02 : 0 0 0 0 0/LC1The following example shows how to place the DSC in ROMMON mode:
RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# config-register 0x0Successfully set config-register to 0x0 on node 0/0/CPU0RP/0/RP0/CPU0:router(admin)# exitRP/0/RP0/CPU0:router# reloadProceed with reload? [confirm]System Bootstrap, Version 12.0(20040624:164256) [assafb-misc1 1.14dev(0.91)] DEVELOPMENT SOFTWARECopyright (c) 1994-2004 by cisco Systems, Inc.DRAM DIMM Slot 1: 512M found, Slot 2: EmptyMPC7450 platform with 524288 Kbytes of main memoryrommon 1 >The show_bcm_links command, run in ROMMON mode, shows that all expected links are active on the Cisco CRS-1 Multishelf System:
rommon B1 > show_bcm_linksPorts Active on Switch 0FE Port 1GE Port 1GE Port 2Ports Active on Switch 1GE Port 2The following example shows how to exit ROMMMON mode:
rommon B1> confregConfiguration Summary(Virtual Configuration Register: 0x0)enabled are:console baud: 9600boot: the ROM Monitordo you wish to change the configuration? y/n [n]: yenable "diagnostic mode"? y/n [n]: nchange console baud rate? y/n [n]: nchange the boot characteristics? y/n [n]: yenter to boot:0 = ROM Monitor1 = MBI Validation Boot Mode[0]: 1Configuration Summary(Virtual Configuration Register: 0x102)enabled are:console baud: 9600boot: image specified by the boot system commandsdo you wish to change the configuration? y/n [n]: nYou must reset or power cycle for new config to take effectrommon B2> resetTroubleshooting the Multishelf System Router Topology
To verify and troubleshoot the Cisco CRS-1 Multishelf System router topology, perform the following procedures.
Each SC and RP has two internal switches (0 and 1). Each internal switch has two Gigabit Ethernet control ports. Port 1 is on the front panel and is used as a control port for interchassis connectivity (Gigabit Ethernet control). Port 2 is used to connect between the two internal switches in the SC. The Fast Ethernet (FE) ports of the switches are used within the chassis to connect to other nodes (intrachassis connections).
If an external Catalyst 6000 Series Switches or Integrated Control Switches (SC-GE-22) are used, use the show spantree mst 1 or show udld gigabit ethernet command to show the ports.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
a.
b.
c.
d.
10.
11.
a.
b.
12.
DETAILED STEPS
Step 1
show platform
Example:RP/0/RP0/CPU0:router# show platform
Displays information and status on each node in the system.
Verify that all components in the router are visible and that the components are in the run state.
If components are not visible in the command output, proceed to Step 3 and check the GE switch connections as illustrated in Figure 6-2.
Step 2
Check that all external Catalyst switches are connected to the RPs and SCs as illustrated in Figure 6-2.
Ensures that the connections for the control plane Ethernet network are made. See Cisco CRS-1 Carrier Routing System Multishelf System Interconnection and Cabling Guide for details on system control plane Ethernet network to cabling.
Step 3
show controllers switch 0 ports location node-id
Example:RP/0/RP0/CPU0:router# show controllers switch 0 ports location 0/RP1/CPU0
Displays status on a Switch Port 0.
Verify that all ports are in the forwarding state.
Step 4
show controllers switch 1 ports location node-id
Example:RP/0/RP0/CPU0:router# show controllers switch 1 ports location 0/RP1/CPU0
Displays status on a switch port 1.
Verify that all ports are in the forwarding state.
Step 5
show spantree mst 1 brief location node-id
Example:RP/0/RP0/CPU0:router# show spantree mst 1 brief location 0/RP1/CPU0
Displays the spanning tree port details.
Verify that the designated root MAC address is the MAC address of the external Catalyst switch. Use the show running-config command to display the MAC address of the external Catalyst switch.
Step 6
show controllers switch 0 statistics location node-id
Example:RP/0/RP0/CPU0:router# show controllers switch 0 statistics location 0/RP1/CPU0
Displays statistics on Switch Port 0.
Verify that the expected internal switch ports are carrying traffic (Tx and Rx frames).
Step 7
show controllers switch 1 statistics location node-id
Example:RP/0/RP0/CPU0:router# show controllers switch 1 statistics location 0/RP1/CPU0
Displays statistics on Switch Port 1.
Verify that the expected internal switch ports are carrying traffic (Tx and Rx frames).
Step 8
show controllers backplane ethernet detail location node-id
Example:RP/0/RP0/CPU0:router# show controllers backplane ethernet detail location 0/RP1/CPU0
Displays detailed information about backplane interfaces in a specific location.
Step 9
admin
config-register 0x0
exit
reload
Example:RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# config-register 0x0
RP/0/RP0/CPU0:router(admin)# exit
RP/0/RP0/CPU0:router# reload
Places the DSC in ROMMON mode.
Step 10
show_bcm_links
Example:rommon B1 > show_bcm_links
This command is used to confirm connectivity from the RP or SC to the Catalyst switch in ROM monitor (ROMMON) mode. See Cisco IOS XR ROM Monitor Guide for the Cisco CRS-1 Router for information on entering ROMMON mode.
Displays the connectivity state of the links to the onboard Ethernet switch as well as the system control Ethernet plane links to the standby RP and remote Catalyst switch.
Verify that all expected active ports are displayed. If no connectivity is detected by a particular port, it will not be displayed in the output. GE Port 1 must be active as this is the port on the switch used for external connectivity. GE Port 2 is the link to the secondary switch, so it should also be active.
Step 11
confreg 0x102
reset
Example:rommon B2 > confreg 0x102
rommon B3 > reset
Exits ROMMON mode, resetting and initializing the router.
Step 12
Contact Cisco Technical Support.
If the problem is not resolved, contact Cisco Technical Support. For Cisco Technical Support contact information, see the "Obtaining Documentation and Submitting a Service Request" section in the Preface.
Examples
The output from the show platform command indicates that all expected nodes are in the IOS XR RUN state:
RP/0/RP0/CPU0:router# show platformNode Type PLIM State Config State-----------------------------------------------------------------------------0/0/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON0/0/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON0/2/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON0/2/CPU0 MSC 16OC48-POS/DPT IOS XR RUN PWR,NSHUT,MON0/RP0/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MONThe following example shows that the appropriate ports on Switch Port 1 are forwarding:
RP/0/RP0/CPU0:router# show controllers switch 1 ports location 0/RP1/CPU0Ports Active on Switch 1FE Port 1 STP State : FORWARDING (Connected to - 0/RP0)FE Port 2 STP State : FORWARDING (Connected to - 0/RP1)FE Port 9 STP State : FORWARDING (Connected to - 0/SM0)GE Port 1 STP State : FORWARDING // connected to External switch through the front panelGE Port 2 STP State : FORWARDING // connected to the other Internal switchThe following example displays the spanning tree details including the designated root (expected MAC address for the external Catalyst switch):
RP/0/RP0/CPU0:router# show spantree mst 1 brief location 0/rp1/cpu0Instance 1Vlans mapped: 1Designated Root 00-0e-39-fe-70-00Designated Root Priority 1 (0 + 1)Designated Root Port GE_Port_0Bridge ID MAC ADDR 00-05-9a-3e-89-55Bridge ID Priority 32769 (32768 + 1)Bridge Max Age 20 sec Hello Time 2 sec Forward Delay 15 sec Max Hops 4Switched Interface State Role Cost Prio Type-------------------- ----- ---- --------- ---- --------------------------------FE_Port_0 FWD desg 200000 128 P2PGE_Port_0 FWD root 20000 128 P2PGE_Port_1 DWN desg 20000 128 P2PThe following example shows the statistics for Switch Port 0:
RP/0/RP0/CPU0:router# show controllers switch 0 statistics location 0/RP1/CPU0Port Tx Frames Tx Errors Rx Frames Rx Errors Connects----------------------------------------------------------------1 : 0 0 0 0 0/LC02 : 0 0 164794 1 0/LC13 : 0 0 0 0 0/LC24 : 0 0 0 0 0/LC35 : 0 0 0 0 0/LC46 : 0 0 0 0 0/LC57 : 0 0 0 0 0/LC68 : 0 0 0 0 0/LC79 : 0 0 164799 1 0/LC810 : 0 0 0 0 0/LC911 : 0 0 0 0 0/LC1012 : 0 0 0 0 0/LC1113 : 0 0 0 0 0/LC1214 : 0 0 0 0 0/LC1315 : 0 0 0 0 0/LC1416 : 0 0 0 0 0/LC1525 : 0 0 0 0 GE_126 : 0 0 4370089 0 Switch 0The following example shows output from the show controller backplane ethernet location detail command:
RP/0/RP0/CPU0:router# show controllers backplane ethernet detail location 0/1/0FastEthernet0_1_0 is upHardware is 10/100 Ethernet, H/W address is 5246.4800.0010Internet address is 10.0.0.16MTU 1514 bytesEncapsulation HFRIES (HFR Internal Ethernet Server)Mode : Full Duplex, Rate : 100Mb/s426422 packets input, 0 bytes, 1 total input drops14170 packets discarded (935122 bytes) in garbage collection16 packets discarded (5344 bytes) in recv processingReceived 0 broadcast packets, 0 multicast packetsInput errors: 0 CRC, 0 overrun, 0 alignment, 0 length, 0 collision440272 packets output, 0 bytes, 0 total output dropsOutput 0 broadcast packets, 0 multicast packetsOutput errors: 0 underruns, 0 aborts, 0 loss of carrierTroubleshooting the Catalyst Switch
To troubleshoot the Catalyst switch running Cisco IOS software, perform the following procedure.
Note
Restrictions
The external Catalyst switches must operate with the same software version: Cisco IOS software release 12.2 with Sup720 engine. Please note that older hardware can also use the CatOS software, but Cisco strongly recommends using the Cisco IOS software.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Step 1
Check that all external GE switches are connected to the RPs and SCs as illustrated in Figure 6-2.
Ensures that the connections for the control plane Ethernet network are made. See Cisco CRS-1 Carrier Routing System Multishelf System Interconnection and Cabling Guide for details on system control plane Ethernet network to RP and SC cabling.
Step 2
Connect to the console port of an external Catalyst switch.
Provides connection to the control plane Ethernet network.
See Cisco CRS-1 Carrier Routing System Multishelf System Interconnection and Cabling Guide for details on connecting to the external switch.
Step 3
enable
Example:CAT6k-1# enable
Enters enter privileged EXEC mode.
Step 4
show running-config
Example:CAT6k-1# show running-config
Displays the contents of the currently running configuration file on the external Catalyst switch.
Check the running configuration to ensure it is the expected configuration. Also, check the following:
•
•
•
•
Step 5
Verify communication between the Catalyst switch and the RPs and SCs.
See Cisco CRS-1 Carrier Routing System Multishelf System Upgrade and Conversion Guide for information on verifying communication between the Catalyst switch and the RPs and SCs.
Step 6
Contact Cisco Technical Support.
If the problem is not resolved, contact Cisco Technical Support. For Cisco Technical Support contact information, see the "Obtaining Documentation and Submitting a Service Request" section in the Preface.
Troubleshooting the CRS-1, 4-slot, 8-slot, or 16-slot System Router Topology
To verify and troubleshoot the Cisco CRS-1 8-Slot Line Card Chassis, Cisco CRS-1 8-Slot Line Card Chassis, or Cisco CRS-1 16-Slot Line Card Chassis router topology, perform the following procedures.
Each SC and RP has two internal switches (0 and 1). Each internal switch has two Gigabit Ethernet control ports. Port 1 is on the front panel and is used as a control port for interchassis connectivity (Gigabit Ethernet control). Port 2 is used to connect between the two internal switches in the SC. The Fast Ethernet (FE) ports of the switches are used within the chassis to connect to other nodes (intrachassis connections).
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
a.
b.
c.
d.
8.
a.
b.
9.
DETAILED STEPS
Step 1
show platform
Example:RP/0/RP0/CPU0:router# show platform
Displays information and status on each node in the system.
Verify that all components in the router are visible and that the components are in the run state.
If components are not visible in the command output, proceed to Step 3 and check the GE switch connections as illustrated in Figure 6-2.
Step 2
show controllers switch 0 ports location node-id
Example:RP/0/RP0/CPU0:router# show controllers switch 0 ports location 0/RP1/CPU0
Displays status on a Switch Port 0.
Verify that all ports are in the forwarding state.
Step 3
show controllers switch 1 ports location node-id
Example:RP/0/RP0/CPU0:router# show controllers switch 1 ports location 0/RP1/CPU0
Displays status on a switch port 1.
Note
Verify that all ports are in the forwarding state.
Step 4
show controllers switch 0 statistics location node-id
Example:RP/0/RP0/CPU0:router# show controllers switch 0 statistics location 0/RP1/CPU0
Displays statistics on Switch Port 0.
Verify that the expected internal switch ports are carrying traffic (Tx and Rx frames).
Step 5
show controllers switch 1 statistics location node-id
Example:RP/0/RP0/CPU0:router# show controllers switch 1 statistics location 0/RP1/CPU0
Displays statistics on Switch Port 1.
Note
Verify that the expected internal switch ports are carrying traffic (Tx and Rx frames).
Step 6
show controllers backplane ethernet detail location node-id
Example:RP/0/RP0/CPU0:router# show controllers backplane ethernet detail location 0/RP1/CPU0
Displays detailed information about backplane interfaces in a specific location.
Step 7
admin
config-register 0x0
exit
reload
Example:RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# config-register 0x0
RP/0/RP0/CPU0:router(admin)# exit
RP/0/RP0/CPU0:router# reload
Places the DSC in ROMMON mode.
Step 8
confreg 0x102
reset
Example:rommon B2 > confreg 0x102
rommon B3 > reset
Exits ROMMON mode, resetting and initializing the router.
Step 9
Contact Cisco Technical Support.
If the problem is not resolved, contact Cisco Technical Support. For Cisco Technical Support contact information, see the "Obtaining Documentation and Submitting a Service Request" section in the Preface.
Examples
The output from the show platform command indicates that all expected nodes are in the IOS XR RUN state:
RP/0/RP0/CPU0:router# show platformNode Type PLIM State Config State-----------------------------------------------------------------------------0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/1/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON0/1/4 MSC(SPA) 4XOC48-POS OK PWR,NSHUT,MON0/1/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON0/3/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/3/4 MSC(SPA) 8X1GE OK PWR,NSHUT,MON0/6/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/6/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON0/6/4 MSC(SPA) 8XOC3/OC12-POS OK PWR,NSHUT,MON0/6/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MONThe following example shows that the appropriate ports on Switch Port 0 are forwarding:
RP/0/RP0/CPU0:router# show controllers switch 0 ports location 0/RP1/CPU0Ports Active on Switch 0FE Port 0 : Up, STP State : FORWARDING (Connects to - 0/RP0)FE Port 1 : Up, STP State : FORWARDING (Connects to - 0/RP1)FE Port 2 : Up, STP State : FORWARDING (Connects to - 0/SM0)FE Port 3 : Up, STP State : FORWARDING (Connects to - 0/SM1)FE Port 4 : Up, STP State : FORWARDING (Connects to - 0/SM2)FE Port 5 : Up, STP State : FORWARDING (Connects to - 0/SM3)FE Port 6 : Down (Connects to - )FE Port 7 : Down (Connects to - )FE Port 8 : Down (Connects to - 0/LC0)FE Port 9 : Up, STP State : FORWARDING (Connects to - 0/LC1)FE Port 10 : Down (Connects to - 0/LC2)FE Port 11 : Up, STP State : FORWARDING (Connects to - 0/LC3)FE Port 12 : Down (Connects to - 0/LC4)FE Port 13 : Down (Connects to - 0/LC5)FE Port 14 : Up, STP State : FORWARDING (Connects to - 0/LC6)FE Port 15 : Down (Connects to - 0/LC7)GE Port 0 : Down (Connects to - GE_0)GE Port 1 : Down (Connects to - GE_1)The following example shows the statistics for Switch Port 0:
RP/0/RP0/CPU0:router# show controllers switch 0 statistics location 0/RP1/CPU0Port Tx Frames Tx Errors Rx Frames Rx Errors Connects----------------------------------------------------------------0 : 670451 1 236107 46 0/RP01 : 420259 1 876822 64 0/RP12 : 865909 0 922949 66 0/SM03 : 864762 2049 789500 591 0/SM14 : 865011 1877 789172 325 0/SM25 : 870186 1 796699 66 0/SM36 : 0 512 0 31337 : 0 513 1 58 : 33 0 0 1103 0/LC09 : 234601 1 254274 1671 0/LC110 : 1025 0 1 421 0/LC211 : 84842 257 104034 461 0/LC312 : 0 0 0 1063 0/LC413 : 0 1 0 0 0/LC514 : 146808 0 172052 599 0/LC615 : 0 0 0 16 0/LC724 : 29250 0 1499184 632 GE_025 : 0 0 32784 32784 GE_1The following example shows output from the show controller backplane ethernet location detail command:
RP/0/RP0/CPU0:router# show controllers backplane ethernet detail location 0/1/0FastEthernet0_RP0_CPU0 is upHardware is 10/100 Ethernet, H/W address is 5246.4800.0201Internet address is 10.0.2.1MTU 1514 bytesEncapsulation HFRIES (HFR Internal Ethernet Server)Mode : Full Duplex, Rate : 100Mb/s68732206 packets input, 3398506674 bytes, 0 total input drops0 packets discarded (0 bytes) in garbage collection267 packets discarded (95502 bytes) in recv processing0 incomplete frames discarded0 packets discarded due to bad headers2 packets waiting for clients0 packets waiting on RxReceived 16 broadcast packets, 14516874 multicast packetsInput errors: 0 CRC, 0 overrun, 0 alignment, 0 length, 0 collision60733356 packets output, 1676989930 bytes, 0 total output dropsOutput 6904806 broadcast packets, 6904806 multicast packetsOutput errors: 0 underruns, 0 aborts, 0 loss of carrierWrite rejects : 0
