Cisco IOS XR Troubleshooting, Release 3.4
Troubleshooting the Control Plane Ethernet Network
Downloads: This chapterpdf (PDF - 272.0KB) The complete bookPDF (PDF - 1.93MB) | Feedback

Troubleshooting the Control Plane Ethernet Network

Table Of Contents

Troubleshooting the Control Plane Ethernet Network

Troubleshooting Booting the System Control Plane Ethernet Network

Examples

Troubleshooting the Multishelf System Router Topology

Examples

Troubleshooting the Catalyst Switch

Restrictions

Troubleshooting the CRS-1 4-slot, 8-slot, or 16-slot System Router Topology

Examples


Troubleshooting the Control Plane Ethernet Network


This chapter describes techniques that you can use to troubleshoot the Cisco CRS-1 control plane Ethernet network on routers using Cisco IOS XR software. It includes the following sections:

Troubleshooting Booting the System Control Plane Ethernet Network

Troubleshooting the Multishelf System Router Topology

Troubleshooting the CRS-1 4-slot, 8-slot, or 16-slot System Router Topology

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:

Intrachassis—Within a chassis, the control plane is provided using Fast Ethernet (FE) links between nodes. The FE links are internal to the chassis and cannot be removed.

Interchassis—System Control Plane connectivity between chassis in the system is provided using Gigabit Ethernet (GE) links. Two links are presented on the front of each of the route processors (active and standby) in each of the line card chassis (LCCs) and shelf controllers (active and standby) in the fabric card chassis (FCC). Two ports are provided for redundancy purposes. This control plane is supported on the Cisco CRS-1 Multishelf System only.

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. show platform

2. admin debug shelfmgr boot

3. show controllers backplane ethernet clients all location node-id

4. show controllers backplane ethernet clients 13 statistics location node-id

5. show controllers switch {0 | 1} statistics location node-id

6. Place the designated shelf controller (DSC) in ROM Monitor (ROMMON) mode:

a. admin

b. config register 0x0

c. exit

d. reload

7. show_bcm_links (Cisco CRS-1 Multishelf System only)

8. Exit ROMMON mode:

a. confreg 0x102

b. reset

9. Contact Cisco Technical Support if the problem is not resolved.

DETAILED STEPS

 
Command or Action
Purpose

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:

Client Ethernet server ID 13—used for boot requests

Client Ethernet server ID 4—used for heartbeats

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:

Packets input

Packets delivered

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 Technical Assistance" 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 step is supported on Cisco CRS-1 Multishelf Systems only.

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 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, contact Cisco Technical Support. For Cisco Technical Support contact information, see the "Obtaining Technical Assistance" 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 platform
 
   
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/1/SP          MSC(SP)         N/A             IOS XR RUN      PWR,NSHUT,MON
0/1/CPU0        MSC             4OC192-POS/DPT  IOS XR RUN      PWR,NSHUT,MON
0/8/SP          MSC(SP)         N/A             IOS XR RUN      PWR,NSHUT,MON
0/8/CPU0        MSC             16OC48-POS/DPT  IOS XR RUN      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/FC0/SP        LCC-FAN-CT(SP)  N/A             IOS XR RUN      PWR,NSHUT,MON
0/FC1/SP        LCC-FAN-CT(SP)  N/A             IOS XR RUN      PWR,NSHUT,MON
0/AM1/SP        ALARM(SP)       N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM0/SP        FC/M(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM1/SP        FC/M(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM4/SP        FC/M(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/M(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
1/RP0/CPU0      RP(Active)      N/A             IOS XR RUN      PWR,NSHUT,MON
1/RP1/CPU0      RP(Standby)     N/A             IOS XR RUN      PWR,NSHUT,MON
1/FC0/SP        LCC-FAN-CT(SP)  N/A             IOS XR RUN      PWR,NSHUT,MON
1/FC1/SP        LCC-FAN-CT(SP)  N/A             IOS XR RUN      PWR,NSHUT,MON
1/AM1/SP        ALARM(SP)       N/A             IOS XR RUN      PWR,NSHUT,MON
1/SM0/SP        FC/M(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
1/SM1/SP        FC/M(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
1/SM4/SP        FC/M(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
1/SM5/SP        FC/M(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
F0/SM0/SP       FCC-SFC(SP)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SM1/SP       FCC-SFC(SP)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SM4/SP       FCC-SFC(SP)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SM5/SP       FCC-SFC(SP)     N/A             IOS XR RUN      PWR,NSHUT,MON
F0/SC0/CPU0     FCC-SC(Standby) N/A             IOS XR RUN      PWR,NSHUT,MON
F0/SC1/CPU0     FCC-SC(Active)  N/A             IOS XR RUN      PWR,NSHUT,MON
F0/AM1/SP       ALARM(SP)       N/A             IOS XR RUN      PWR,NSHUT,MON
F0/LM0/SP       FCC-LED(SP)     N/A             IOS XR RUN      PWR,NSHUT,MON
 
   

The 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 all
 
   
    Intf               Client ethernet         Client              Description
    Name              server id            Process Id
------------------------------------------------------------------------------
  FE0_RP1_0               1                 24601          QNX network manager
                          2                 53317               Group services
                          3                     0               Reserved for Attach
                          4                 53338            Plugin controller
                          5                 53298                Designated SC
                                    ...                  ...                   ...
                         13                 53338    Card Configuration Protocol
                                    ...                  ...                   ...
                         22                     0      Test client out-of-band
 
   

The 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/CPU0
 
   
  Client ShelfMgr, ES Client Id 13, PID 53338 running on FastEthernet0_RP1_0 
    18 packets input, 8676 bytes
    18 packets delivered, 8676 bytes
    0 packets discarded (0 bytes) in garbage collection
    0 (0 bytes) unicast packets filtered
    0 (0 bytes) multicast packets filtered
    0 (0 bytes) buffer mgmt policy discards
    0 (0 bytes) locking error discards
    18 packets output, 8676 bytes, 0 could not be transmitted
 
   

The 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 statistics 
 
   
Port   Tx Frames   Tx Errors   Rx Frames   Rx Errors   Connects 
----------------------------------------------------------------
 1 :      382714           0      132876           2       0/LC0
 2 :           0           0           0           0       0/LC1
 
   

The following example shows how to place the DSC in ROMMON mode:

RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# config-register 0x0
 
   
Successfully set config-register to 0x0 on node 0/0/CPU0
 
   
RP/0/RP0/CPU0:router(admin)# exit
RP/0/RP0/CPU0:router# reload
 
   
Proceed with reload? [confirm]
System Bootstrap, Version 12.0(20040624:164256) [assafb-misc1 1.14dev(0.91)] DEV
ELOPMENT SOFTWARE
Copyright (c) 1994-2004 by cisco Systems, Inc.
DRAM DIMM Slot 1: 512M found, Slot 2: Empty
MPC7450 platform with 524288 Kbytes of main memory
rommon 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_links
 
   
 Ports Active on Switch 0
 FE Port 1
 GE Port 1
 GE Port 2
 Ports Active on Switch 1
 GE Port 2
 
   

The following example shows how to exit ROMMMON mode:

rommon B1> confreg
 
   
Configuration Summary
(Virtual Configuration Register: 0x0)
enabled are:
console baud: 9600
boot: the ROM Monitor
do you wish to change the configuration? y/n [n]: y
enable "diagnostic mode"? y/n [n]: n
change console baud rate? y/n [n]: n
change the boot characteristics? y/n [n]: y
enter to boot:
0 = ROM Monitor
1 = MBI Validation Boot Mode
[0]: 1
Configuration Summary
(Virtual Configuration Register: 0x102)
enabled are:
console baud: 9600
boot: image specified by the boot system commands
do you wish to change the configuration? y/n [n]: n
You must reset or power cycle for new config to take effect
 
   
rommon B2> reset

Troubleshooting 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).

SUMMARY STEPS

1. show platform

2. Verify that all physical Catalyst switch connections are made.

3. show controllers switch 0 ports location node-id

4. show controllers switch 1 ports location node-id

5. show spantree mst 1 brief location node-id

6. show controllers switch 0 statistics location node-id

7. show controllers switch 1 statistics location node-id

8. show controllers backplane ethernet detail location node-id

9. Place the DSC in ROMMON mode:

a. admin

b. config register 0x0

c. exit

d. reload

10. show_bcm_links

11. Exit ROMMON mode:

a. confreg 0x102

b. reset

12. Contact Cisco Technical Support if the problem is not resolved

DETAILED STEPS

 
Command or Action
Purpose

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.

Step 2 

Check that all external Catalyst switches are connected to the RPs and SCs.

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. See the show running-config command for 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 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 Technical Assistance" 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 platform
 
   
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/0/SP          MSC(SP)         N/A             IOS XR RUN      PWR,NSHUT,MON
0/0/CPU0        MSC             16OC48-POS/DPT  IOS XR RUN      PWR,NSHUT,MON
0/2/SP          MSC(SP)         N/A             IOS XR RUN      PWR,NSHUT,MON
0/2/CPU0        MSC             16OC48-POS/DPT  IOS XR RUN      PWR,NSHUT,MON
0/RP0/CPU0      RP(Standby)     N/A             IOS XR RUN      PWR,NSHUT,MON
0/RP1/CPU0      RP(Active)      N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM0/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
 
   

The 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/CPU0
 
   
Ports Active on Switch 1
FE 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 
panel
GE Port  2  STP State : FORWARDING   // connected to the other Internal switch
 
   

The 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/cpu0
 
   
Instance                 1
Vlans mapped:            1
 
   
Designated Root          00-0e-39-fe-70-00 
Designated Root Priority 1 (0 + 1)
Designated Root Port     GE_Port_0
 
   
Bridge ID MAC ADDR       00-05-9a-3e-89-55
Bridge ID Priority       32769 (32768 + 1)
Bridge Max Age 20 sec    Hello Time  2 sec   Forward Delay 15 sec   Max Hops 4
 
   
Switched Interface   State Role   Cost    Prio Type
-------------------- ----- ---- --------- ---- --------------------------------
FE_Port_0              FWD desg    200000  128  P2P
GE_Port_0              FWD root     20000  128  P2P
GE_Port_1              DWN desg     20000  128  P2P
 
   

The following example shows the statistics for Switch Port 0:

RP/0/RP0/CPU0:router# show controllers switch 0 statistics location 0/RP1/CPU0
 
   
Port   Tx Frames   Tx Errors   Rx Frames   Rx Errors   Connects
----------------------------------------------------------------
 1 :           0           0           0           0       0/LC0
 2 :           0           0      164794           1       0/LC1
 3 :           0           0           0           0       0/LC2
 4 :           0           0           0           0       0/LC3
 5 :           0           0           0           0       0/LC4
 6 :           0           0           0           0       0/LC5
 7 :           0           0           0           0       0/LC6
 8 :           0           0           0           0       0/LC7
 9 :           0           0      164799           1       0/LC8
10 :           0           0           0           0       0/LC9
11 :           0           0           0           0      0/LC10
12 :           0           0           0           0      0/LC11
13 :           0           0           0           0      0/LC12
14 :           0           0           0           0      0/LC13
15 :           0           0           0           0      0/LC14
16 :           0           0           0           0      0/LC15
25 :           0           0           0           0        GE_1
26 :           0           0     4370089           0    Switch 0
 
   

The 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/0 
 
   
FastEthernet0_1_0 is up
 Hardware is 10/100 Ethernet, H/W address is 5246.4800.0010
 Internet address is 10.0.0.16
 MTU 1514 bytes 
 Encapsulation HFRIES (HFR Internal Ethernet Server)
 Mode : Full Duplex,  Rate : 100Mb/s 
 426422 packets input, 0 bytes, 1 total input drops 
 14170 packets discarded (935122 bytes) in garbage collection
 16 packets discarded (5344 bytes) in recv processing
 Received 0 broadcast packets, 0 multicast packets
 Input errors: 0 CRC, 0 overrun, 0 alignment, 0 length, 0 collision
 440272 packets output, 0 bytes, 0 total output drops
 Output 0 broadcast packets, 0 multicast packets
 Output errors: 0 underruns, 0 aborts, 0 loss of carrier

Troubleshooting the Catalyst Switch

To troubleshoot the Catalyst switch running Cisco IOS software, perform the following procedure.


Note This procedure is supported on Cisco CRS-1 Multishelf Systems only.


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. Check that all external GE switches are connected to the RPs and SCs.

2. Connect to the external Catalyst switch.

3. enable

4. show running-config

5. Verify communication between the Catalyst switch and the RPs and SCs.

6. Contact Cisco Technical Support if the problem is not resolved

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

Check that all external GE switches are connected to the RPs and SCs.

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:

Spanning tree is enabled

There is one VLAN in the spanning tree configuration

All GE ports are forwarding

The external Catalyst switch is a spanning tree root (MAC address indicated for designated root is the same as the bridge ID MAC ADDR)

Step 5 

Verify communication between the Catalyst switch and the RPs and SCs.

See Cisco IOS XR Getting Started Addendum for Multishelf System for information on verifying communication between the Catalyst switch and the RPs and SCs. The document is located at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/core/crs/beta325/index.htm

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 Technical Assistance" 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 Only the Cisco CRS-1 16-Slot Line Card Chassis contains switch 0 and switch 1. The Cisco CRS-1 8-Slot Line Card Chassis and Cisco CRS-1 4-Slot Line Card Chassis contain switch 0.


SUMMARY STEPS

1. show platform

2. show controllers switch 0 ports location node-id

3. show controllers switch 1 ports location node-id

4. show controllers switch 0 statistics location node-id

5. show controllers switch 1 statistics location node-id

6. show controllers backplane ethernet detail location node-id

7. Place the DSC in ROMMON mode:

a. admin

b. config register 0x0

c. exit

d. reload

8. Exit ROMMON mode:

a. confreg 0x102

b. reset

9. Contact Cisco Technical Support if the problem is not resolved

DETAILED STEPS

 
Command or Action
Purpose

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.

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 Only the Cisco CRS-1 16-Slot Line Card Chassis contains switch 0 and switch 1. The Cisco CRS-1 8-Slot Line Card Chassis and Cisco CRS-1 4-Slot Line Card Chassis contain switch 0.

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 Only the Cisco CRS-1 16-Slot Line Card Chassis contains switch 0 and switch 1. The Cisco CRS-1 8-Slot Line Card Chassis and Cisco CRS-1 4-Slot Line Card Chassis contain switch 0.

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 Technical Assistance" 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 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/4           MSC(SPA)        4XOC48-POS      OK              PWR,NSHUT,MON
0/1/5           MSC(SPA)        8X1GE           OK              PWR,NSHUT,MON
0/3/CPU0        MSC             Jacket Card     IOS XR RUN      PWR,NSHUT,MON
0/3/4           MSC(SPA)        8X1GE           OK              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
 
   

The 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/CPU0
 
   
Ports Active on Switch 0 
 FE 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/CPU0
 
   
Port   Tx Frames   Tx Errors   Rx Frames   Rx Errors   Connects 
----------------------------------------------------------------
 0 :      670451           1      236107          46       0/RP0
 1 :      420259           1      876822          64       0/RP1
 2 :      865909           0      922949          66       0/SM0
 3 :      864762        2049      789500         591       0/SM1
 4 :      865011        1877      789172         325       0/SM2
 5 :      870186           1      796699          66       0/SM3
 6 :           0         512           0        3133            
 7 :           0         513           1           5            
 8 :          33           0           0        1103       0/LC0
 9 :      234601           1      254274        1671       0/LC1
10 :        1025           0           1         421       0/LC2
11 :       84842         257      104034         461       0/LC3
12 :           0           0           0        1063       0/LC4
13 :           0           1           0           0       0/LC5
14 :      146808           0      172052         599       0/LC6
15 :           0           0           0          16       0/LC7
24 :       29250           0     1499184         632        GE_0
25 :           0           0       32784       32784        GE_1
 
   

The 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/0 
 
   
FastEthernet0_RP0_CPU0 is up
  Hardware is 10/100 Ethernet, H/W address is 5246.4800.0201
  Internet address is 10.0.2.1
  MTU 1514 bytes 
  Encapsulation HFRIES (HFR Internal Ethernet Server)
  Mode : Full Duplex,  Rate : 100Mb/s 
    68732206 packets input, 3398506674 bytes, 0 total input drops 
    0 packets discarded (0 bytes) in garbage collection
    267 packets discarded (95502 bytes) in recv processing
    0 incomplete frames discarded
    0 packets discarded due to bad headers
    2 packets waiting for clients 
    0 packets waiting on Rx 
    Received 16 broadcast packets, 14516874 multicast packets
    Input errors: 0 CRC, 0 overrun, 0 alignment, 0 length, 0 collision
    60733356 packets output, 1676989930 bytes, 0 total output drops
    Output 6904806 broadcast packets, 6904806 multicast packets
    Output errors: 0 underruns, 0 aborts, 0 loss of carrier
    Write rejects : 0