Cisco IOS XR Getting Started Guide, Release 3.3
Chapter 8 - Managing the Router Hardware
Downloads: This chapterpdf (PDF - 624.0KB) The complete bookPDF (PDF - 6.76MB) | Feedback

Managing the Router Hardware

Table Of Contents

Managing the Router Hardware

Contents

Displaying Hardware Status

Displaying Secure Domain Router Hardware Version Information

Displaying System Hardware Version Information

Displaying the Chassis Serial Numbers (Cisco CRS-1 Routers)

Displaying the Configured Chassis Serial Numbers

Displaying Software and Hardware Information

Displaying SDR Node IDs and Status

Displaying Router Node IDs and Status

Displaying Router Environment Information

Displaying RP Redundancy Status

RP Redundancy and Switchover

Establishing RP Redundancy on the Cisco CRS-1 Router

Establishing RP Redundancy on Cisco XR 12000 Series Routers

Determining the Active RP in a Redundant Pair

Role of the Standby RP

Summary of Redundancy Commands

Automatic Switchover

RP Redundancy During RP Reload

Manual Switchover

Communicating with a Standby RP

DSC Migration on Cisco CRS-1 Multishelf Systems

Reloading, Shutting Down, or Power Cycling a Node

Reloading the Active RP

Administratively Shutting Down or Powering On or Off a Node

Using Controller Commands to Manage Hardware Components

Formatting Hard Drives, Flash Drives, and Other Storage Devices

Removing and Replacing Cards

Removing Line Cards, MSCs, or PLIMs

Replacing an MSC

Replacing a Line Card or PLIM with the Same Media Type and Port Count

Replacing a Line Card or PLIM with the Same Media Type and a Different Port Count

Replacing a Line Card or PLIM with a Different Media Type

Removing and Replacing Cisco CRS-16-FC Switch Fabric Cards

Prerequisites

Examples

Removing and Replacing Cisco CRS-8-FC/S Switch Fabric Cards

Prerequisites

Examples

Removing and Replacing CSC and SFC Cards

Prerequisites

Examples

Removing and Replacing CSFC Cards

Adding a Standby PRP to a Cisco 12000 Series Router

Prerequisites


Managing the Router Hardware


This chapter describes the command-line interface (CLI) techniques and commands used to manage and configure the hardware components of a router running the Cisco IOS XR software.

Contents

This chapter contains the following sections:

Displaying Hardware Status

RP Redundancy and Switchover

DSC Migration on Cisco CRS-1 Multishelf Systems

Reloading, Shutting Down, or Power Cycling a Node

Using Controller Commands to Manage Hardware Components

Formatting Hard Drives, Flash Drives, and Other Storage Devices

Removing and Replacing Cards

Displaying Hardware Status

The following sections describe how to display different types of hardware status information:

Displaying Secure Domain Router Hardware Version Information

Displaying System Hardware Version Information

Displaying the Chassis Serial Numbers (Cisco CRS-1 Routers)

Displaying the Configured Chassis Serial Numbers

Displaying Software and Hardware Information

Displaying SDR Node IDs and Status

Displaying Router Environment Information

Displaying RP Redundancy Status

Displaying Secure Domain Router Hardware Version Information

To display hardware version information for the components assigned to a Secure Domain Router (SDR), connect to the appropriate DSDRSC and enter the show diag command in EXEC mode. The displayed information includes the card serial number and the ROMMON software version.

The syntax for the show diag command in EXEC mode is:

show diag [nodeID | details | summary]


Note The show diag command output is different for Cisco CRS-1 routers and Cisco XR 12000 Series Routers.


In the following example, the show diag command displays information for all nodes in the SDR:

RP/0/RP0/CPU0:Router# show diag
 
   
PLIM 0/1/CPU0 : JACKET CARD
  MAIN:  board type 580070
         800-23819-03 rev C0
         dev N/A
         S/N SAD094401CR
  PCA:   73-8982-06 rev C0
  PID:   CRS1-SIP-800
  VID:   V01
  CLEI:  COUIAAMCAA
  ECI:   134912
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x0025, Processor: 0xda13, Power: N/A
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193559)  [CRS-1 ROMMON]
  Interface port config:  0 Ports
  Optical reach type:  Unknown
  Connector type:  MT-P
 
   
NODE 0/1/0 : 4xOC3 POS SPA
  MAIN:  board type 0440
         68-2169-01 rev C0
         dev N/A
         S/N JAB093309PA
  PCA:   73-9313-04 rev B0 
  PID:   SPA-4XOC3-POS 
  VID:   V01 
  CLEI:  IPUIAFNRAA
 
   
NODE 0/1/5 : 8xGE SPA
  MAIN:  board type 044f
         68-2239-01 rev A0
         dev N/A
         S/N SAD0937022J
  PCA:   73-8557-03 rev A0 
  PID:   SPA-8X1GE 
  VID:   V01 
  CLEI:  CNUIAH6AAA
 
   
PLIM 0/6/CPU0 : JACKET CARD
  MAIN:  board type 580070
         800-23819-03 rev C0
         dev N/A
         S/N SAD094203W2
  PCA:   73-8982-06 rev C0
  PID:   CRS1-SIP-800
  VID:   V01
  CLEI:  COUIAAMCAA
  ECI:   134912
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x0025, Processor: 0xda13, Power: N/A
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193559)  [CRS-1 ROMMON]
  Interface port config:  0 Ports
  Optical reach type:  Unknown
  Connector type:  MT-P
 
   
NODE 0/6/0 : 4xOC3 POS SPA
  MAIN:  board type 0440
         68-2169-01 rev C0
         dev N/A
         S/N JAB093309MG
  PCA:   73-9313-04 rev B0 
  PID:   SPA-4XOC3-POS 
  VID:   V01 
  CLEI:  IPUIAFNRAA
 
   
NODE 0/6/4 : 8xOC3/OC12 POS SPA
  MAIN:  board type 0404
         68-2164-01 rev 34
         dev N/A
         S/N JAB094706L9
  PCA:   73-9941-02 rev 04 
  PID:   SPA-8XOC12-POS 
  VID:   V01 
  CLEI:  SOUIAA8BAA
 
   
NODE 0/6/5 : 8xGE SPA
  MAIN:  board type 044f
         68-2239-01 rev A0
         dev N/A
         S/N SAD093909GM
  PCA:   73-8557-03 rev A0 
  PID:   SPA-8X1GE 
  VID:   V01 
  CLEI:  CNUIAH6AAA
 
   
NODE 0/RP0/CPU0 : RP
  MAIN:  board type 100002
         800-22921-10 rev B0
         dev 080366, 080181
         S/N SAD093507J8
  PCA:   73-8564-10 rev B0
  PID:   CRS-8-RP
  VID:   V01
  CLEI:  IPUCABWBAA
  ECI:   129507
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x0038, Processor: 0x0038, Power: 0x0000
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193559)  [CRS-1 ROMMON]
 
   
NODE 0/RP1/CPU0 : RP
  MAIN:  board type 100002
         800-22921-10 rev B0
         dev 080366, 080181
         S/N SAD093507JP
  PCA:   73-8564-10 rev B0
  PID:   CRS-8-RP
  VID:   V01
  CLEI:  IPUCABWBAA
  ECI:   129507
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x0038, Processor: 0x0038, Power: 0x0000
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193559)  [CRS-1 ROMMON]
 
   

In the following example, the show diag command displays information for a single node:

RP/0/RP0/CPU0:router# show diag 0/RP0/CPU0
 
   
NODE 0/RP0/CPU0 : RP
  MAIN:  board type 100002
         800-22921-10 rev B0
         dev 080366, 080181
         S/N SAD093507J8
  PCA:   73-8564-10 rev B0
  PID:   CRS-8-RP
  VID:   V01
  CLEI:  IPUCABWBAA
  ECI:   129507
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x0038, Processor: 0x0038, Power: 0x0000
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193559)  [CRS-1 ROMMON]
 
   
 
   

Displaying System Hardware Version Information

To display hardware version information for all or some of the components assigned in a system, connect to the DSC and enter the show diag command in administration EXEC mode. When this command is entered in administration EXEC mode, you can display information on RPs, MSCs or line cards, fabric cards, and system components such as the chassis, fan trays, and power supplies.


Note If you enter the show diag command in EXEC mode, the software displays only the hardware assigned to the SDR to which you are connected.


The syntax for the show diag command in administration EXEC mode is:

show diag [nodeID | chassis | details | fans | power-supply | summary]


Tip For information on the software version, use the show version command.


In the following example, the show diag command displays information for all nodes in the system:

RP/0/RP1/CPU0:router(admin)# show diag 
 
   
NODE 0/1/SP : MSC(SP)
  MAIN:  board type 500060
         800-25021-05 rev B0
         dev 079239
         S/N SAD09280BS9
  PCA:   73-7648-08 rev B0
  PID:   CRS-MSC
  VID:   V02
  CLEI:  IPUCAC1BAA
  ECI:   132502
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x0025, Processor: 0xda13, Power: N/A
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193402)  [CRS-1 ROMMON]
 
   
PLIM 0/1/CPU0 : JACKET CARD
  MAIN:  board type 580070
         800-23819-03 rev C0
         dev N/A
         S/N SAD094401CR
  PCA:   73-8982-06 rev C0
  PID:   CRS1-SIP-800
  VID:   V01
  CLEI:  COUIAAMCAA
  ECI:   134912
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x0025, Processor: 0xda13, Power: N/A
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193559)  [CRS-1 ROMMON]
  Interface port config:  0 Ports
  Optical reach type:  Unknown
  Connector type:  MT-P
 
   
NODE 0/1/0 : 4xOC3 POS SPA
  MAIN:  board type 0440
         68-2169-01 rev C0
         dev N/A
         S/N JAB093309PA
  PCA:   73-9313-04 rev B0 
  PID:   SPA-4XOC3-POS 
  VID:   V01 
  CLEI:  IPUIAFNRAA
 
   
NODE 0/1/5 : 8xGE SPA
  MAIN:  board type 044f
         68-2239-01 rev A0
         dev N/A
         S/N SAD0937022J
  PCA:   73-8557-03 rev A0 
  PID:   SPA-8X1GE 
  VID:   V01 
  CLEI:  CNUIAH6AAA
 
   
NODE 0/6/SP : MSC(SP)
  MAIN:  board type 500060
         800-25021-06 rev A0
         dev 080229
         S/N SAD093702ES
  PCA:   73-7648-08 rev C0
  PID:   CRS-MSC
  VID:   V03
  CLEI:  IPUCAD0BAA
  ECI:   135786
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x0025, Processor: 0xda13, Power: N/A
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193402)  [CRS-1 ROMMON]
 
   
PLIM 0/6/CPU0 : JACKET CARD
  MAIN:  board type 580070
         800-23819-03 rev C0
         dev N/A
         S/N SAD094203W2
  PCA:   73-8982-06 rev C0
  PID:   CRS1-SIP-800
  VID:   V01
  CLEI:  COUIAAMCAA
  ECI:   134912
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x0025, Processor: 0xda13, Power: N/A
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193559)  [CRS-1 ROMMON]
  Interface port config:  0 Ports
  Optical reach type:  Unknown
  Connector type:  MT-P
 
   
NODE 0/6/0 : 4xOC3 POS SPA
  MAIN:  board type 0440
         68-2169-01 rev C0
         dev N/A
         S/N JAB093309MG
  PCA:   73-9313-04 rev B0 
  PID:   SPA-4XOC3-POS 
  VID:   V01 
  CLEI:  IPUIAFNRAA
 
   
NODE 0/6/4 : 8xOC3/OC12 POS SPA
  MAIN:  board type 0404
         68-2164-01 rev 34
         dev N/A
         S/N JAB094706L9
  PCA:   73-9941-02 rev 04 
  PID:   SPA-8XOC12-POS 
  VID:   V01 
  CLEI:  SOUIAA8BAA
 
   
NODE 0/6/5 : 8xGE SPA
  MAIN:  board type 044f
         68-2239-01 rev A0
         dev N/A
         S/N SAD093909GM
  PCA:   73-8557-03 rev A0 
  PID:   SPA-8X1GE 
  VID:   V01 
  CLEI:  CNUIAH6AAA
 
   
NODE 0/RP0/CPU0 : RP
  MAIN:  board type 100002
         800-22921-10 rev B0
         dev 080366, 080181
         S/N SAD093507J8
  PCA:   73-8564-10 rev B0
  PID:   CRS-8-RP
  VID:   V01
  CLEI:  IPUCABWBAA
  ECI:   129507
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x0038, Processor: 0x0038, Power: 0x0000
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193559)  [CRS-1 ROMMON]
 
   
NODE 0/RP1/CPU0 : RP
  MAIN:  board type 100002
         800-22921-10 rev B0
         dev 080366, 080181
         S/N SAD093507JP
  PCA:   73-8564-10 rev B0
  PID:   CRS-8-RP
  VID:   V01
  CLEI:  IPUCABWBAA
  ECI:   129507
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x0038, Processor: 0x0038, Power: 0x0000
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193559)  [CRS-1 ROMMON]
 
   
NODE 0/SM0/SP : FC/S
  MAIN:  board type 400035
         800-23168-05 rev B0
         dev N/A
         S/N SAD0933081S
  PCA:   73-8682-05 rev B0
  PID:   CRS-8-FC/S
  VID:   V01
  CLEI:  IPUCABXBAA
  ECI:   129510
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x001e, Processor: 0x0000, Power: N/A
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193402)  [CRS-1 ROMMON]
          
NODE 0/SM1/SP : FC/S
  MAIN:  board type 400035
         800-23168-05 rev B0
         dev N/A
         S/N SAD09300492
  PCA:   73-8682-05 rev B0
  PID:   CRS-8-FC/S
  VID:   V01
  CLEI:  IPUCABXBAA
  ECI:   129510
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x001e, Processor: 0x0000, Power: N/A
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193402)  [CRS-1 ROMMON]
 
   
NODE 0/SM2/SP : FC/S
  MAIN:  board type 400035
         800-23168-05 rev B0
         dev N/A
         S/N SAD09330830
  PCA:   73-8682-05 rev B0
  PID:   CRS-8-FC/S
  VID:   V01
  CLEI:  IPUCABXBAA
  ECI:   129510
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x001e, Processor: 0x0000, Power: N/A
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193402)  [CRS-1 ROMMON]
 
   
NODE 0/SM3/SP : FC/S
  MAIN:  board type 400035
         800-23168-05 rev B0
         dev N/A
         S/N SAD0933081W
  PCA:   73-8682-05 rev B0
  PID:   CRS-8-FC/S
  VID:   V01
  CLEI:  IPUCABXBAA
  ECI:   129510
  Board State : IOS XR RUN
  PLD:   Motherboard: 0x001e, Processor: 0x0000, Power: N/A
  MONLIB: QNXFFS Monlib Version 3.0
  ROMMON: Version 1.38(20050525:193402)  [CRS-1 ROMMON]
 
   
Rack 0:   
 
   
Fan Tray 0 : Fan Tray Upper
  MAIN:  board type 900160
         800-23275-05 rev A0
         dev N/A
         S/N TBA09370056
  PCA:   0-0-00 rev 00
  PID:   CRS-8-LCC-FAN-TR
  VID:   V01
  CLEI:  IPPQAGWJAB
  ECI:   133434
 
   
Fan Tray 1 : Fan Tray Lower
  MAIN:  board type 900160
         800-23275-05 rev A0
         dev N/A
         S/N TBA09370055
  PCA:   0-0-00 rev 00
  PID:   CRS-8-LCC-FAN-TR
  VID:   V01
  CLEI:  IPPQAGWJAB
  ECI:   133434
          
Rack 0:
 
   
Power Supply A : 
  MAIN:  board type b00181
         341-112-01 rev C0
         dev N/A
         S/N TD109320008
  PCA:   0-0-00 rev 00
  PID:   CRS-8-AC-RECT
  VID:   V01
  CLEI:  IPP1D0WAAA
  ECI:   129500
 
   
Power Supply B : 
  MAIN:  board type b00181
         341-112-01 rev C0
         dev N/A
         S/N TD10931000X
  PCA:   0-0-00 rev 00
  PID:   CRS-8-AC-RECT
  VID:   V01
  CLEI:  IPP1D0WAAA
  ECI:   129500
 
   
RACK   0 : 
  MAIN:  board type 0001e4
         800-23271-04 rev F0
         dev 076763
         S/N TBA09370035
  PCA:   73-8696-03 rev A0
  PID:   CRS-8-LCC
  VID:   V01
  CLEI:  IPMEZ10BRA
  ECI:   446387
  RACK NUM: 0
 
   

Note Line cards in Cisco CRS-1 routers are called modular services cards (MSCs). The show diag command output is different for Cisco CRS-1 routers and Cisco XR 12000 Series Routers.


In the following example, the show diag command displays information for a single system component:

RP/0/RP1/CPU0:router(admin)# show diag chassis
 
   
RACK   0 : 
  MAIN:  board type 0001e4
         800-23271-04 rev F0
         dev 076763
         S/N TBA09370035
  PCA:   73-8696-03 rev A0
  PID:   CRS-8-LCC
  VID:   V01
  CLEI:  IPMEZ10BRA
  ECI:   446387
  RACK NUM: 0
 
   

Displaying the Chassis Serial Numbers (Cisco CRS-1 Routers)

Each chassis serial number must be defined during the configuration of multishelf routers. To view the actual serial number for each chassis in the system, enter the command show diag chassis in administration EXEC mode.

The chassis serial numbers are displayed in the "Main" category for each chassis.

The "Rack Num" field displays the rack number assigned to that serial number.

For example:

RP/0/RP0/CPU0:router# admin 
RP/0/RP0/CPU0:router(admin)# show diag chassis                                            
 
   
RACK   0 :          
  MAIN:  board type 0001e0                          
         800-24872                 
         dev 075078                   
         S/N TBA00000001 
  PCA:   73-7640-05 rev 20                          
  PID:   CRS-16-LCC                   
  VID:   V01            
  CLEI:  IPM6700DRA                   
  ECI:   445022               
  RACK NUM: 0             
 
   
RACK   1 :          
  MAIN:  board type 0001e0
         800-24872-01 rev 20
         dev 075078
         S/N TBA00000002
  PCA:   73-7640-05 rev 20
  PID:   CRS-16-LCC
  VID:   V01
  CLEI:  IPM6700DRA
  ECI:   445022
  RACK NUM: 1
 
   
 
   
--MORE--
 
   

Displaying the Configured Chassis Serial Numbers

Enter the command show running-config | include dsc in administration EXEC mode to display the serial number configured for each rack number.

This command is used to verify that the configuration is correct. The serial numbers displayed are those entered by an operator. If this number if wrong due to an entry error, the number is still displayed, but the DSC does not recognize the chassis.


Note This command can also be entered in administration configuration mode.


For example:

RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# show running-config | include dsc
 
   
Building configuration...
dsc serial TBA00000003 rack F0
dsc serial TBA00000001 rack 0
dsc serial TBA00000002 rack 1
RP/0/RP0/CPU0:router(admin)#

Displaying Software and Hardware Information

The show version command displays a variety of system information, including the hardware and software versions, router uptime, boot settings (including the configuration register), and active software.

The syntax for the show version command is:

show version

The following is sample output from the show version command:

RP/0/RP1/CPU0:router# show version
 
   
Cisco IOS XR Software, Version 3.3.0[2I]
Copyright (c) 2006 by cisco Systems, Inc.
 
   
ROM: System Bootstrap, Version 1.38(20050525:193559) [CRS-1 ROMMON],  
 
   
router uptime is 1 week, 1 day, 17 hours, 1 minute
System image file is "disk0:hfr-os-mbi-3.3.0/mbihfr-rp.vm"
 
   
cisco CRS-8/S (7457) processor with 4194304K bytes of memory.
7457 processor at 1197Mhz, Revision 1.2
 
   
16 Packet over SONET/SDH network interface(s)
16 SONET/SDH Port controller(s)
2 Ethernet/IEEE 802.3 interface(s)
16 GigabitEthernet/IEEE 802.3 interface(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).
 
   
Package active on node 0/1/SP:
hfr-diags, V 3.3.0[2I], Cisco Systems, at disk0:hfr-diags-3.3.0
    Built on Mon Mar 13 12:58:02 UTC 2006
    By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8
 
   
hfr-admin, V 3.3.0[2I], Cisco Systems, at disk0:hfr-admin-3.3.0
    Built on Mon Mar 13 11:46:36 UTC 2006
    By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8
 
   
hfr-base, V 3.3.0[2I], Cisco Systems, at disk0:hfr-base-3.3.0
    Built on Mon Mar 13 11:43:22 UTC 2006
    By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8
 
   
hfr-os-mbi, V 3.3.0[2I], Cisco Systems, at disk0:hfr-os-mbi-3.3.0
    Built on Mon Mar 13 11:27:02 UTC 2006
    By iox8.cisco.com in /auto/ioxws48/production/3.3.0.2I/hfr/workspace for c8
 
   
 --More--

Displaying SDR Node IDs and Status

In EXEC mode, the show platform command displays information for all nodes assigned to a secure domain router (SDR). For each node, this information includes the host card type, the operational state, and the configuration state. To display information on a single node, enter the command with a node ID.

The syntax for the show platform command on Cisco CRS-1 routers is:

show platform [nodeID]

The syntax for the show platform command on Cisco XR 12000 Series Routers is:

show platform

The following example displays the status for all nodes in the SDR to which you are connected:

RP/0/RP0/CPU0:router# show platform
 
   
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/0/CPU0        MSC             16OC48-POS/DPT  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
 
   

Note Line cards in Cisco CRS-1 routers are called modular services cards (MSCs). The show platform command output is different for Cisco CRS-1 routers and Cisco XR 12000 Series Routers.


The nodeID appears in the rack/slot/module notation, and the nodeID components are as follows:

The rack number in a single-shelf system is always "0." In a multishelf system, the line card chassis (LCC) rack number range is 0 to 255 and the FCC rack number range is F0 to F7.

The slot is the number of the physical slot in which the card is installed.

The module identifies a system hardware component.

Table 8-1 summarizes the nodeID for each type of card in a Cisco CRS-1 system, and Table 8-2 summarizes the nodeID for each type of card in a Cisco XR 12000 Series Router.

Table 8-1 Node ID Components on Cisco CRS-1 Routers 

Card Type
(the card type to which you are issuing commands)
Rack
(always "0" in a single-shelf system)
Slot
(the physical slot in which the card is installed)
Module
(the entity on the card that is the target of the command)

Route processor

0-255

RP0 and RP1

CPU0

DRP

0-255

0-7 (8-slot chassis)

0-15 (16-slot chassis)

CPU0 or CPU1

MSC

0-255

0-7 (8-slot chassis)

0-15 (16-slot chassis)

Service processor (SP)

PLIM

0-255

0-7 (8-slot chassis)

0-15 (16-slot chassis)

CPU0

Cisco CRS-1 SPA Interface Processor (SIP)-800

0-255

0-7 (8-slot chassis)

0-15 (16-slot chassis)

CPU0

1-Port OC-192c/STM-64c Packet-over-SONET/SDH (POS) XFP SPA

4-Port OC-3c/STM-1 POS SPA

8-Port Gigabit Ethernet SPA

0-255

0-7 (8-slot chassis)

0-15 (16-slot chassis)

0-5 (SPA module number on the Cisco CRS-1 SIP-800)

Switch fabric module

0-255

SM0-SM3 (8-slot chassis)

SM0-SM7 (16-slot chassis)

SP

Alarm cards

0-255

AM0-AM1 (16-slot chassis)

SP

Fan controller cards

0-255

FC0-FC1 (16-slot chassis)

SP


Table 8-2 Node ID Components on Cisco XR 12000 Series Routers 

Card Type
(the card type to which you are issuing commands)
Rack
(always "0" in a single-shelf system)
Slot
(the logical slot number reported in command displays)
Module
(the entity on the card that executes the commands)

Route processor

0

0-151 , 2

CPU0

Cisco XR 12000 and 12000 Series line cards

0

0-151

CPU0

Cisco XR 12000 and 12000 Series SPA Interface Processor (SIP)-600

0

0-151

CPU0

1-Port 10-Gigabit Ethernet SPA

5-Port Gigabit Ethernet SPA

10-Port Gigabit Ethernet SPA

1-Port OC-192c/STM-64c POS/RPR SPA

0

0-151

0-1 (SPA module number on the Cisco XR 12000 and 12000 Series SIP-600)

Clock and scheduler cards (CSCs)

0

CSC 0 and 13

CPU0

Switch fabric cards (SFCs)

0

SFC 0, 1, 2, 3, and 43, 4

CPU0

Consolidated switch fabric (CSF) card

0

Dedicated slot 175

CPU0

1 Depends on router model.

2 RP pairs can be in any adjacent slot pairs as long as the even-numbered slot is the smaller slot number. For example, an RP pair can be installed in slots 0 and 1, 2 and 3, or 14 and 15.

3 Not used on Cisco XR 12404 routers.

4 Total number of SFC slots depends on router model.

5 Used only on Cisco XR 12404 routers.


Displaying Router Node IDs and Status

In administration EXEC mode, the show platform command displays information for all router nodes, which include nodes in all chassis and SDRs. In administration EXEC mode, the command display also includes additional node IDs such as those for fabric cards, alarm modules, and fan controllers. For each node, this information includes the host card type, the operational state, and the configuration state. To display information on a single node, enter the command with a node ID.

The syntax for the show platform command on Cisco CRS-1 routers is:

show platform [nodeID]

The syntax for the show platform command on Cisco XR 12000 Series Routers is:

show platform

The following example displays the status for all nodes in a Cisco CRS-1 Multishelf System:

RP/0/RP0/CPU0:router(admin)# show platform
 
   
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/5/SP          MSC(SP)         N/A             IOS XR RUN      PWR,NSHUT,MON
0/5/CPU0        MSC             4OC192-POS/DPT  IOS XR RUN      PWR,NSHUT,MON
0/7/SP          DRP(SP)         N/A             IOS XR RUN      PWR,NSHUT,MON
0/7/CPU0        DRP(Active)     DRP-ACC         IOS XR RUN      PWR,NSHUT,MON
0/7/CPU1        DRP(Active)     DRP-ACC         IOS XR RUN      PWR,NSHUT,MON
0/14/SP         MSC(SP)         N/A             IOS XR RUN      PWR,NSHUT,MON
0/14/CPU0       MSC             8-10GbE         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/AM0/SP        ALARM(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/SM2/SP        FC/M(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/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
0/SM6/SP        FC/M(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/M(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
1/4/SP          MSC(SP)         N/A             IOS XR RUN      PWR,NSHUT,MON
1/4/CPU0        MSC             4OC192-POS/DPT  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/AM0/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/SM3/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
1/SM6/SP        FC/M(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
1/SM7/SP        FC/M(SP)        N/A             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)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SM6/SP       FCC-SFC(SP)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SM7/SP       FCC-SFC(SP)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SC0/CPU0     FCC-SC(Active)  N/A             IOS XR RUN      PWR,NSHUT,MON
F0/SC1/CPU0     FCC-SC(Standby) N/A             IOS XR RUN      PWR,NSHUT,MON
F0/AM0/SP       ALARM(SP)       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
F0/LM1/SP       UNKNOWN(SP)     N/A             IN-RESET        PWR,NSHUT,MON
 
   

Note Line cards in Cisco CRS-1 routers are called modular services cards (MSCs). The show platform command output is different for Cisco CRS-1 routers and Cisco XR 12000 Series Routers.


The nodeID appears in the rack/slot/module notation, and the nodeID components are as follows:

The rack number in a single-shelf system is always "0." In a multishelf system, the LCC rack number range is 0 to 255 and the FCC rack number range is F0 to F7.

The slot is the number of the physical slot in which the card is installed.

The module identifies a system hardware component.

Table 8-1 summarizes the nodeID for each type of card in a Cisco CRS-1 router, and Table 8-2 summarizes the nodeID for each type of card in a Cisco XR 12000 Series Router.

Displaying Router Environment Information

The show environment command displays hardware information for the system, including fan speeds, LED indications (Cisco CRS-1 routers only), power supply voltage and current information, and temperatures.

The syntax for the show environment command is:

show environment [options]

You can use the show environment command options to limit the detail in the command display. To view the command options, enter the show environment ? command. The following example shows the full environment status report:

RP/0/0/CPU0:router# show environment
 
   
Temperature Information
---------------------------------------------
 
   
R/S/I   Modules Sensor          Temp. (deg C)
 
   
0/0/*     host  Inlet              23.0
          host  Hot                23.0
0/3/*     host  Inlet              24.0
          host  Hot                33.0
0/4/*     host  Inlet              24.5
          host  Hot                31.5
0/5/*     host  Inlet              23.5
          host  Hot                30.5
0/6/*     host  Hot                31.5
          host  Inlet              22.5
0/7/*     host  Inlet              20.0
          host  Hot                29.5
0/8/*     host  Inlet              20.5
          host  Hot                32.0
 
   
Threshold Information
---------------------------------------------
 
   
R/S/I   Modules Sensor          Minor           Major           Critical
                                (Lo/Hi)         (Lo/Hi)         (Lo/Hi)
 
   
0/0/*     host  InletTemp        --/  55          --/  60          --/  --
          host  HotTemp          --/  66          --/  69          --/  --
          host  PLIM_V4_1.6V     --/  --          --/  --          --/  --
          host  PLIM_V5_1.8V     --/  --          --/  --          --/  --
          host  PLIM_V3_2.5V     --/  --          --/  --          --/  --
          host  3.3V           2950/3500        2900/3600          --/  --
          host  5V             4800/5150        4700/5200          --/  --
          host  Mbus5V         4700/5300        4500/5500          --/  --
0/3/*     host  InletTemp        --/  55          --/  60          --/  70
          host  HotTemp          --/  66          --/  69          --/  75
          host  PLIM_V3_1.5V     --/  --          --/  --          --/  --
          host  PLIM_V8_1.8V     --/  --          --/  --          --/  --
          host  PLIM_V7_2.5V     --/  --          --/  --          --/  --
          host  3.3V             --/  --          --/  --          --/  --
          host  5V             4800/5200        4700/5300        4600/5400
          host  Mbus5V         4700/5300        4600/5400        4500/5500
0/4/*     host  InletTemp        --/  55          --/  60          --/  70
          host  HotTemp          --/  66          --/  69          --/  75
          host  PLIM_V3_1.5V     --/  --          --/  --          --/  --
          host  PLIM_V8_1.8V     --/  --          --/  --          --/  --
          host  PLIM_V7_2.5V     --/  --          --/  --          --/  --
          host  PLIM_V6_1.5V     --/  --          --/  --          --/  --
          host  5V               --/  --          --/  --          --/  --
          host  3.3V             --/  --          --/  --          --/  --
          host  Mbus5V         4700/5300        4600/5400        4500/5500
0/5/*     host  InletTemp        --/  55          --/  60          --/  70
          host  HotTemp          --/  66          --/  69          --/  75
          host  PLIM_V3_1.5V     --/  --          --/  --          --/  --
          host  PLIM_V8_1.8V     --/  --          --/  --          --/  --
          host  PLIM_V7_2.5V     --/  --          --/  --          --/  --
          host  PLIM_V6_1.5V     --/  --          --/  --          --/  --
          host  5V               --/  --          --/  --          --/  --
          host  3.3V             --/  --          --/  --          --/  --
          host  Mbus5V         4700/5300        4600/5400        4500/5500
0/6/*     host  HotTemp          --/  66          --/  69          --/  75
          host  InletTemp        --/  55          --/  60          --/  70
          host  PLIM_V3_1.5V     --/  --          --/  --          --/  --
          host  PLIM_V8_1.8V     --/  --          --/  --          --/  --
          host  PLIM_V7_2.5V     --/  --          --/  --          --/  --
          host  3.3V             --/  --          --/  --          --/  --
          host  Mbus5V         4700/5300        4600/5400        4500/5500
0/7/*     host  InletTemp        --/  55          --/  60          --/  70
          host  HotTemp          --/  66          --/  69          --/  75
          host  PLIM_V3_1.5V     --/  --          --/  --          --/  --
          host  PLIM_V8_1.8V     --/  --          --/  --          --/  --
          host  PLIM_V7_2.5V     --/  --          --/  --          --/  --
          host  PLIM_V6_1.5V     --/  --          --/  --          --/  --
          host  5V               --/  --          --/  --          --/  --
          host  3.3V             --/  --          --/  --          --/  --
          host  Mbus5V         4700/5300        4600/5400        4500/5500
0/8/*     host  InletTemp        --/  55          --/  60          --/  70
          host  HotTemp          --/  66          --/  69          --/  75
          host  PLIM_V3_1.5V     --/  --          --/  --          --/  --
          host  PLIM_V8_1.8V     --/  --          --/  --          --/  --
          host  PLIM_V7_2.5V     --/  --          --/  --          --/  --
          host  3.3V             --/  --          --/  --          --/  --
          host  5V             4800/5200        4700/5300        4600/5400
          host  Mbus5V         4700/5300        4600/5400        4500/5500
Voltage Information
---------------------------------------------
 
   
R/S/I   Modules Sensor          Voltage (mV)    Margin
 
   
0/0/*     host  PLIM_V4_1.6V     1612           nominal
          host  PLIM_V5_1.8V     1804           nominal
          host  PLIM_V3_2.5V     2504           nominal
          host  3.3V             3296           nominal
          host  5V               5048           nominal
          host  Mbus5V           5048           n/a
0/3/*     host  PLIM_V3_1.5V     1496           nominal
          host  PLIM_V8_1.8V     1788           nominal
          host  PLIM_V7_2.5V     2492           nominal
          host  3.3V             3284           nominal
          host  5V               5000           nominal
          host  Mbus5V           5024           n/a
0/4/*     host  PLIM_V3_1.5V     1500           nominal
          host  PLIM_V8_1.8V     1796           nominal
          host  PLIM_V7_2.5V     2488           nominal
          host  PLIM_V6_1.5V     1508           nominal
          host  5V               4976           nominal
          host  3.3V             3288           nominal
          host  Mbus5V           5048           n/a
0/5/*     host  PLIM_V3_1.5V     1504           nominal
          host  PLIM_V8_1.8V     1792           nominal
          host  PLIM_V7_2.5V     2488           nominal
          host  PLIM_V6_1.5V     1504           nominal
          host  5V               4976           nominal
          host  3.3V             3284           nominal
          host  Mbus5V           4984           n/a
0/6/*     host  PLIM_V3_1.5V     1496           nominal
          host  PLIM_V8_1.8V     1792           nominal
          host  PLIM_V7_2.5V     2476           nominal
          host  3.3V             3300           nominal
          host  Mbus5V           5016           n/a
0/7/*     host  PLIM_V3_1.5V     1504           nominal
          host  PLIM_V8_1.8V     1796           nominal
          host  PLIM_V7_2.5V     2484           nominal
          host  PLIM_V6_1.5V     1504           nominal
          host  5V               4976           nominal
          host  3.3V             3276           nominal
          host  Mbus5V           4984           n/a
0/8/*     host  PLIM_V3_1.5V     1496           nominal
          host  PLIM_V8_1.8V     1792           nominal
          host  PLIM_V7_2.5V     2492           nominal
          host  3.3V             3280           nominal
          host  5V               5000           nominal
          host  Mbus5V           5024           n/a
 
   

Displaying RP Redundancy Status

The show redundancy command displays the redundancy status of the route processors (RPs). This command also displays the boot and switch-over history for the RPs.

The show redundancy operates in EXEC or administration EXEC mode.

In the following example, the show redundancy command displays the redundancy status for a redundant RP pair:

RP/0/RP0/CPU0:router# show redundancy
 
   
This 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
 
   
Reload and boot info
----------------------
RP reloaded Fri Apr  9 03:44:28 2004: 16 hours, 51 minutes ago
This node booted Fri Apr  9 06:19:05 2004: 14 hours, 16 minutes ago
Last switch-over Fri Apr  9 06:53:18 2004: 13 hours, 42 minutes ago
Standby node boot Fri Apr  9 06:54:25 2004: 13 hours, 41 minutes ago
Standby node last not ready Fri Apr  9 20:35:23 2004: 0 minutes ago
Standby node last ready Fri Apr  9 20:35:23 2004: 0 minutes ago
There have been 2 switch-overs since reload

RP Redundancy and Switchover

RP redundancy is established differently between the Cisco CRS-1 routers and Cisco XR 12000 Series Routers. After redundancy is established, redundancy management is the same for all routers. The following sections describe RP redundancy and switchover:

Establishing RP Redundancy on the Cisco CRS-1 Router

Establishing RP Redundancy on Cisco XR 12000 Series Routers

Determining the Active RP in a Redundant Pair

Role of the Standby RP

Summary of Redundancy Commands

Automatic Switchover

RP Redundancy During RP Reload

Manual Switchover

Communicating with a Standby RP

Reloading the Active RP

Establishing RP Redundancy on the Cisco CRS-1 Router

Cisco CRS-1 routers have two slots for RPs: RP0 and RP1 (see Figure 8-1). These slots are configured for redundancy by default, and the redundancy cannot be eliminated. To establish RP redundancy, install RPs into both slots.

Figure 8-1 Redundant Set of RPs Installed in Slots RP0 and RP1 in a 16-Slot Chassis

Establishing RP Redundancy on Cisco XR 12000 Series Routers

In a Cisco XR 12000 Series Router, redundant RPs are formed when you insert two RP cards into paired redundancy slots. Redundancy slots are paired as follows:

Slot 0 and Slot 1

Slot 2 and Slot 3

Slot 4 and Slot 5

Slot 6 and Slot 7

Slot 8 and Slot 9

Slot 10 and Slot 11

Slot 12 and Slot 13

Slot 14 and Slot 15

RPs that are seated in paired redundancy slots cannot be assigned to different SDRs. For example, an RP that is installed in Slot 3 can be assigned to one SDR, while an RP that is installed in Slot 4 can be assigned to a different SDR because Slot 3 and Slot 4 are not a redundant pair. However, you cannot have the RP in Slot 3 assigned to a different SDR than the RP in Slot 2 because Slot 2 and Slot 3 are a redundant pair.

RP redundancy is established when the Cisco IOS XR software is brought up on both cards in paired redundancy slots. For example, if you install the Cisco IOS XR software on the DSC, an RP in the paired redundancy slot comes up as the standby DSC after the minimum boot image (MBI) is loaded and the redundant RP synchronizes with the DSC.

Determining the Active RP in a Redundant Pair

During system startup, the software configuration (redundancy reddrv command) determines which RP in each redundant pair becomes the active RP. You can tell which RP is the active RP in the following ways:

On Cisco CRS-1 routers, the active RP can be identified by the green Primary LED on the faceplate of the card. The active RP is indicated when the Primary LED is on. The alphanumeric LED display on the RP displays ACTV RP.

On Cisco XR 12000 Series Routers, the alphanumeric LED display on the active PRP displays: PRI RP.

The slot of the active RP is indicated in the CLI prompt. For example:

RP/0/RP1/CPU0:router#
 
   

In this example, the prompt indicates that you are communicating with the active RP in slot RP1. See the "CLI Prompt" section for a complete description of the CLI prompt.

Enter the show redundancy command in EXEC mode to display a summary of the active and standby RP status. For example:

RP/0/0/CPU0:router# show redundancy
 
   
Redundancy information for node 0/0/CPU0:
==========================================
Node 0/0/CPU0 is in ACTIVE role
Partner node (0/1/CPU0) is in STANDBY role
Standby node in 0/1/CPU0 is ready
 
   
Reload and boot info
----------------------
PRP reloaded Thu Jan 12 05:51:33 2006: 11 hours, 19 minutes ago
Active node booted Thu Jan 12 05:51:33 2006: 11 hours, 19 minutes ago
Standby node boot Thu Jan 12 06:28:15 2006: 10 hours, 43 minutes ago
Standby node last went not ready Thu Jan 12 06:31:16 2006: 10 hours, 40 minutes ago
Standby node last went ready Thu Jan 12 06:31:16 2006: 10 hours, 40 minutes ago
There have been 0 switch-overs since reload
 
   

Role of the Standby RP

The second RP to boot in a redundant pair automatically becomes the "standby RP." While the active RP manages the system and communicates with the user interface, the standby RP maintains a complete backup of the software and configurations for all cards in the system. If the active RP fails or goes off line for any reason, the standby RP immediately takes control of the system.

Summary of Redundancy Commands

RP redundancy is enabled by default in the Cisco IOS XR software, but you can use the commands described in Table 8-3 to display the redundancy status of the cards or force a manual switchover.

Table 8-3

Command
Description

show redundancy

Displays the redundancy status of the RPs. This command also displays the boot and switch-over history for the RPs.

redundancy switchover

Forces a manual switchover to the standby RP. This command works only if the standby RP is installed and in the "ready" state.

show platform

Displays the status for node, including the redundancy status of the RP cards. In EXEC mode, this command displays status for the nodes assigned to the SDR. In administration EXEC mode, this command displays status for all nodes in the system.


RP Redundancy Commands

Automatic Switchover

Automatic switchover from the active RP to the standby RP occurs only if the active RP encounters a serious system error, such as the loss of a mandatory process or a hardware failure. When an automatic switchover occurs, the RPs respond as follows:

If a standby RP is installed and "ready" for switchover, the standby RP becomes the active RP. The original active RP attempts to reboot.

If the standby RP is not in "ready" state, then both RPs reboot. The first RP to boot successfully assumes the role of active RP.

RP Redundancy During RP Reload

The reload command causes the active RP to reload the Cisco IOS XR software. When an RP reload occurs, the RPs respond as follows:

If a standby RP is installed and "ready" for switchover, the standby RP becomes the active RP. The original active RP reboots and becomes the standby RP.

If the standby RP is not in the "ready" state, then both RPs reboot. The first RP to boot successfully assumes the role of active RP.


Caution You should not use the reload command to force an RP switchover because the result could be a significant loss of router operations. Instead, use the redundancy switchover command to fail over to the standby RP, then use the hw-module location nodeID reload command to reload the new standby RP. See the "Reloading, Shutting Down, or Power Cycling a Node" section for more information.

Manual Switchover

You can force a manual switchover from the active RP to the standby RP using the redundancy switchover command.

If a standby RP is installed and ready for switchover, the standby RP becomes the active RP. The original active RP becomes the standby RP. In the following example, partial output for a successful redundancy switchover operation is shown:

RP/0/RP0/CPU0:router# show redundancy
 
   
This 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
 
   
RP/0/RP0/CPU0:router# redundancy switchover
Updating Commit Database.  Please wait...[OK]
Proceed with switchover 0/RP0/CPU0 -> 0/RP1/CPU0? [confirm]
Initiating switch-over.
RP/0/RP0/CPU0:router#
 
   
<Your 'TELNET' connection has terminated>
 
   

In the preceding example, the Telnet connection is lost when the previously active RP resets. To continue management of the router, you must connect to the newly activated RP as shown in the following example:

User Access Verification
 
   
Username: cisco
Password: 
Last switch-over Sat Apr 15 12:26:47 2006: 1 minute ago
 
   
RP/0/RP1/CPU0:router#
 
   

If the standby RP is not in "ready" state, the switchover operation is not allowed. In the following example, partial output for a failed redundancy switchover attempt is shown:

RP/0/RP1/CPU0:router# show redundancy 
 
   
Redundancy information for node 0/RP0/CPU0:
==========================================
Node 0/RP1/CPU0 is in ACTIVE role
Partner node (0/RP0/CPU0) is in UNKNOWN role
 
   
Reload and boot info
----------------------
RP reloaded Wed Mar 29 17:22:08 2006: 2 weeks, 2 days, 19 hours, 14 minutes ago
Active node booted Sat Apr 15 12:27:58 2006: 8 minutes ago
Last switch-over Sat Apr 15 12:35:42 2006: 1 minute ago
There have been 4 switch-overs since reload
 
   
RP/0/RP1/CPU0:router# redundancy switchover
 
   
Switchover disallowed: Standby node is not ready.
 
   

Communicating with a Standby RP

The active RP automatically synchronizes all system software, settings, and configurations with the standby RP.

If you connect to the standby RP through the console port, you can view the status messages for the standby RP. The standby RP does not display a CLI prompt, so you cannot manage the standby card while it is in standby mode.

If you connect to the standby RP through the management Ethernet port, the prompt that appears is for the active RP, and you can manage the router the same as if you had connected through the management Ethernet port on the active RP.

DSC Migration on Cisco CRS-1 Multishelf Systems

Designated Shelf Controller (DSC) migration is the act of moving the DSC role to a different part of the router. The DSC role automatically migrates when the DSC cannot perform its function on the shelf in which it currently resides. The cause of a DSC migration can be a failure of both of the RPs in the DSC shelf or any event that removes power from the DSC line card chassis (LCC).

DSC migration can be triggered by the following methods:

1. Shutdown power to DSC LCC. (Recommended)

2. Hardware-module reset or shutdown of a standby RP then an active RP in a DSC LCC. (Not recommended)

3. Online, insertion, removal (OIR) for an active RP and standby RP in a DSC LCC simultaneously. (Not recommended)

4. Removal of control Ethernet connectivity to both RPs in a DSC LCC. (Not recommended)


Note If planned downtime of a DSC LCC occurs, the recommended method of triggering DSC migration is to shutdown the power to the DSC LCC. The methods, which are not recommended, shutdown only one transport medium in the system. For example, control Ethernet but fabric medium can still be up for another 30 seconds. This causes an inconsistent system view in the named SDR using DRP paired across the rack in which the DRP loses control Ethernet connectivity, but the LR plane is still working and can bring the named SDR into an inconsistent view if the named SDR is across the rack.


To support DSC migration in Cisco IOS XR Software Release 3.3.2 and higher, we recommend that you:

Keep the default placement of all four RPs in the owner SDR. When the owner SDR spans both LCCs, the impact on the SDR resources is minimal in the remaining rack. Existing connections are not interrupted for the resources in the remaining rack, but a delay in routing new connections can occur while the routing tables are updated.

Run all routing protocols in a named SDR. In addition, by running all routing protocols in a named SDR, which requires a distributed route processor (DRP) paired across the rack, the operation of Cisco Nonstop Forwarding (NSF) and Cisco Nonstop Routing (NSR) continues.

An election process selects the node that is to receive the DSC role upon DSC migration. The basis of the election is the shelf number. The shelf with the lowest number is designated to receive the DSC role.

DSC migration can cause a very short interruption to traffic flowing through the owner SDR. Although the time can vary with the addition of new features to DSC management and other factors, in the current release the time is likely to be around 20 to 30 seconds.

The reason for the traffic loss is because virtual Interfaces (VI), such as loopback, null, tunnels, and bundles are hosted on the DSDRSC of an SDR. For the owner SDR, the DSDRSC is the same node as the DSC itself. For DSC migration to occur, both active and standby DSC must be lost. Therefore, for the owner SDR, both active and standby DSDRSC are lost. VI's must be recreated on the new DSC, which is also the new DSDRSC. This operation takes some time, during which routing protocols such as BGP that use loopback or null interfaces are affected. Similarly, tunnels and bundles must also be recreated, affecting protocols such as MPLS. As a result, there is a drop in traffic in the default or owner SDR.


Note In Cisco IOS XR Software Release 3.3.0 and higher, DSC migration is disabled if the RPs in both LCCs are assigned to different SDRs.


To minimize the impact of DSC migration, create named SDRs that operate on DRP in each LCC. If the DSC rack fails, any named SDRs on the failed rack also fail. However, named SDRs on the unaffected rack can continue through DSC migration without any interruption in service. If the failure in the DSC rack affects only the RP cards, the named SDR in the affected rack cannot function after the RPs on that rack go down.

Reloading, Shutting Down, or Power Cycling a Node

Use the commands described in this section to reload the Cisco IOS XR software on the active RP or on any specified node in the system. This section also describes the commands used to administratively shut down a node and power a node on or off.

Table 8-4 summarizes the commands described in this section.

Table 8-4 Commands to Reload, Shut Down, or Power Cycle a Node 

Command
Description

hw-module location nodeID power disable

This command must be entered in administration configuration mode and administratively turns the power off for a Cisco XR 12000 Series Router node. The changes do not take effect until you enter the commit command.

To power on a node, use the no form of this command.

Note This command applies only to Cisco XR 12000 Series Routers and cannot be used to disable power on the RP from which the command is entered.

hw-module location nodeID reload

This command works in EXEC mode and reloads the Cisco IOS XR software on a specific node or all nodes. To specify all nodes, enter all for the nodeID. The node reloads with the current running configuration and active software set for that node.

hw-module location nodeID shutdown

This command must be entered in administration configuration mode and administratively shuts down a specified node on a Cisco XR 12000 Series Router. Nodes that are shut down still have power, but cannot load or operate Cisco IOS XR software.

To return a node to the up state, use the no form of this command.

Note This command applies only to Cisco XR 12000 Series Routers and cannot be used to shut down the RP from which the command is entered.

reload

Causes the active RP to reload the Cisco IOS XR software according to the configuration register setting (for example, 0x0 to enter ROMMON bootstrap mode and 0x2102 to reload the RP to EXEC mode). The reload command can be entered in EXEC or administration EXEC modes, and you can see additional options by entering the reload ? command. See the "Reloading the Active RP" section for more information.

show variables boot

Displays the configuration register setting for the router.

Use this command in administration EXEC mode to see the variables for both RPs.

The configuration register setting determines how the router boots during a system reset. The most common configuration register settings are:

0x2102: The active RP loads the Cisco IOS XR software and default configuration on the next system boot. After logging in, the user can access EXEC mode.

0x0: The active RP enters the bootstrap ROM Monitor (rommon B1>) on the next system boot.


Reloading the Active RP

The reload command causes the active RP to reload the Cisco IOS XR software according to the configuration register setting. This setting determines how the active RP acts when reloaded.

This section contains instructions to reload the Cisco IOS XR software and return to EXEC mode. For instructions to use the reload command for entering ROM Monitor bootstrap mode, see Cisco IOS XR ROM Monitor Guide.


Caution Because the reload command causes the active RP to go off line and either reload Cisco IOS XR software or enter ROM Monitor mode, the router experiences a loss of service unless a redundant standby RP is installed and in "ready" state. To display the status of the standby RP, type the show redundancy command in EXEC mode.

SUMMARY STEPS

1. show redundancy

2. admin

3. show variables boot

4. (Optional) config-register 0x2102

5. exit

6. reload

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show redundancy

Example:

RP/0/RP0/CPU0:router# show redundancy

Displays the RP redundancy status.

If a standby RP is in "ready" redundancy state, the reload command also causes the router to gracefully fail over to the standby RP.

Step 2 

admin

Example:

RP/0/RP0/CPU0:router# admin

Enters administration EXEC mode.

Step 3 

show variables boot

Example:

RP/0/RP0/CPU0:router(admin)# show variables boot

Displays the configuration register setting.

Enter this command in administration EXEC mode.

For normal operations, the configuration register setting is 0x2102, which causes the active RP to reload the Cisco IOS XR software.

Verify that the configuration register setting is 0x2102. If it is not, complete Step 3 to reset the configuration register to 0x2102.

Note For instructions on how to enter ROM Monitor bootstrap mode, see Cisco IOS XR ROM Monitor Guide.

Step 4 

config-register 0x2102

Example:
RP/0/RP0/CPU0:router(admin)# config-register 
0x2102

(Optional) Sets the configuration register to 0x2102.

This step is necessary only if the register is not set to 0x2102 in the running configuration.

Step 5 

exit

Example:

RP/0/RP0/CPU0:router(admin)# exit

Exits administration EXEC mode.

Step 6 

reload

Example:

RP/0/RP0/CPU0:router# reload

Reloads the active RP according to the configuration register setting.

If the setting is 0x2102, then the RP reloads the Cisco IOS XR software.

If the standby RP is in "ready" redundancy state, the router switches over to the standby RP.

If a standby RP is not installed or not in a "ready" state, the router experiences a loss of service while the active RP is reloading the Cisco IOS XR software.

Administratively Shutting Down or Powering On or Off a Node

A Cisco XR 12000 Series Router node can be administratively shut down by entering the hw-module location nodeID shutdown command in administration configuration mode. A node that is shut down still has power, but cannot load or run the Cisco IOS XR software.

You can also administratively turn power off for a Cisco XR 12000 Series Router node using the hw-module location nodeID power disable command in administration configuration mode.

For more information on the use of these commands, see Cisco IOS XR Interface and Hardware Component Command Reference.

Using Controller Commands to Manage Hardware Components

The controller, controllers, and show controllers commands are used to manage and display settings for various hardware components, including the switch fabric management, Ethernet control plane, and interface manager. These commands are primarily diagnostic and related to driver-level details. The information available with these commands varies widely and is hardware specific.

For information on the use of these commands, see the Cisco IOS XR Interface and Hardware Component Command Reference.

Formatting Hard Drives, Flash Drives, and Other Storage Devices

To format a storage device on the router, use the format command in EXEC mode.


Caution Formatting a storage device deletes all data on that device.

The following command syntax is used:

format filesystem: [options]

Table 8-5 describes the format command syntax.

Table 8-5 format command Syntax Description

Variable
Description

filesystem

Specifies the memory device to format, followed by a colon. The supported file systems are bootflash:, compactflash:, flash:, harddisk:, harddiska:, disk0:, and disk1:. Enter format ? to see the devices supported on your router.

options

Enter format filesystem: ? to see the available options.

For more information, see Cisco IOS XR System Management Command Reference.


In the following example, the format command is used to format the hard disk:

RP/0/RP0/CPU0:router# format harddisk:
 
   

Removing and Replacing Cards

This section describes card replacement issues and procedures for the following tasks:

Removing Line Cards, MSCs, or PLIMs

Replacing an MSC

Replacing a Line Card or PLIM with the Same Media Type and Port Count

Replacing a Line Card or PLIM with the Same Media Type and a Different Port Count

Replacing a Line Card or PLIM with a Different Media Type

Removing and Replacing Cisco CRS-16-FC Switch Fabric Cards

Removing and Replacing Cisco CRS-8-FC/S Switch Fabric Cards

Removing and Replacing CSC and SFC Cards

Removing and Replacing CSFC Cards

Adding a Standby PRP to a Cisco 12000 Series Router

Removing Line Cards, MSCs, or PLIMs

Line cards, modular services cards (MSCs), and physical layer interface modules (PLIMs) are designed for online insertion and removal (OIR). On Cisco XR 12000 Series Routers, a line card is a single card that contains all service processing functions and physical line interfaces. On Cisco CRS-1 routers, the service processing functions are provided on the MSC, and the physical line interface is provided on a separate card that connects the physical lines to the MSC.

The OIR feature allows you to remove and replace cards without removing power to the card or chassis. Removing a card interrupts all traffic passing through the card, but it does not remove the card configuration.

When you remove a card, the configuration remains for all interfaces, but the interfaces do not appear in the output of the show interfaces command. You can view interface configurations by entering the show running-config command. The following example shows how the configuration appears when a card is removed:

RP/0/0/CPU0:router# show running-config
 
   
Building configuration...
hostname router
router ospf 3269
 area 0
  interface POS0/3/0/0
   cost 20
!
interface preconfigure POS0/3/0/0
 ipv4 address 10.10.50.1 255.255.255.0
!
interface preconfigure POS0/3/0/1
 description POS0/3/0/1
 shutdown
!
interface preconfigure POS0/3/0/2
 description POS0/3/0/2
 shutdown
!
interface preconfigure POS0/3/0/3
 description POS0/3/0/3
 shutdown
!
 
   

In this example, the MSC in slot 3 is removed, and the interface configuration for all four interfaces changes to interface preconfigure. However, the router ospf reference to a slot 3 interface does not change. If you replace a PLIM with another PLIM that uses the same media type and port count, the configuration becomes active on the replacement card.

To remove the configuration for a slot after a card is removed, use the no interface preconfigure command to remove all interface configuration statements for that card in the running configuration. In addition, search the configuration for any references to the removed interfaces, such as the router ospf reference to slot 3 in the preceding example.

To remove the configuration for a slot when a card is installed, use the no interface command to remove all interface configuration statements for that card in the running configuration. In addition, search the configuration for any references to the removed interfaces.

Each PLIM supports a specific media type (POS or Ethernet, for example) and port count. If you replace a PLIM with one that supports a different media type or port count, you should review the configuration and revise it to support the replacement PLIM.

Replacing an MSC

When you replace an MSC, the guidelines in the "Removing Line Cards, MSCs, or PLIMs" section apply. Because only one type of MSC exists, no special procedures are required for card removal and replacement.

Replacing a Line Card or PLIM with the Same Media Type and Port Count

When you replace a line card or PLIM with a card that is of the same media type and has the same port count as the replaced card, the guidelines in the "Removing Line Cards, MSCs, or PLIMs" section apply. Because the replacement card is of the same media type and port count, no special procedures are required for card removal and replacement.

Replacing a Line Card or PLIM with the Same Media Type and a Different Port Count

When you replace a line card or PLIM with a card that is of the same media type with a different port count, the guidelines in the "Removing Line Cards, MSCs, or PLIMs" section apply.

If the new card has a greater port count than the replaced card, the configuration applies to the corresponding lower port numbers, and the ports that did not exist on the replaced card have no configuration and come up in the shutdown state.

If the new card supports fewer ports, the existing configuration for the corresponding number of ports on the new card set is applied. The previous configuration for the removed ports remains in interface preconfigure state, as shown in the following example:

RP/0/0/CPU0:router# show running-config
 
   
Building configuration...
hostname rtp-gsr1
interface POS0/3/0/0
 ipv4 address 10.10.50.1 255.255.255.0
!
interface preconfigure POS0/3/0/1
 description POS0/3/0/1
 shutdown
!
interface preconfigure POS0/3/0/2
 description POS0/3/0/2
 shutdown
!
interface preconfigure POS0/3/0/3
 description POS0/3/0/3
 shutdown
!
 
   

In the preceding example, a four-port card has been replaced with a single-port card. The configuration from port 1 on the four-port card is applied to the single port on the replacement card, and the remaining port configurations change to interface preconfigure. To remove the configuration for the missing interfaces, use the no interface preconfigure command. In addition, search for and remove any configuration references to the removed interfaces.

Whenever you replace a line card or PLIM with the same media type and a different port count, review the running configuration in the router and revise the configuration as necessary.

Replacing a Line Card or PLIM with a Different Media Type

When you replace a line card or PLIM with a card that is of a different media type (for example, if you replace a POS PLIM with an Ethernet PLIM), the guidelines in the "Removing Line Cards, MSCs, or PLIMs" section apply. Review the running configuration in the router and revise the configuration as necessary for the new media type.

Removing and Replacing Cisco CRS-16-FC Switch Fabric Cards

The 16-slot LCCs support two switch fabric cards: the CRS-16-FC/S and the CRS-16-FC/M. The CRS-16-FC/S switch fabric card provides the Stage 1, 2, and 3 switch fabric for one fabric plane in a standalone Cisco CRS-1 Carrier Routing System 16-Slot Line Card Chassis. The CRS-16-FC/M switch fabric card provides the Stage 1 and 3 switch fabric for one fabric plane in a Cisco CRS-1 LCC within a multishelf system.

The Cisco CRS-1 16-Slot LCC can support the maximum throughput with seven of the eight fabric planes. To prevent traffic loss, we recommend that you shut the power down on a fabric plane for a switch fabric card before you remove it. If a switch fabric card is removed with the power on, the card is not harmed, but some traffic may be lost. When the replacement card is inserted, you can restore the power to the fabric plane and bring up the replacement card. This section describes how to properly remove and replace Cisco CRS-16-FC/S and Cisco CRS-16-FC/M cards for upgrades or repairs.


Note The process of removing and replacing cards while the router power is on is called online insertion and removal (OIR). This procedure removes power to a specific slot before the switch fabric card is replaced. The power remains on for all other slots.



Tip For more information about switch fabric cards, see the hardware documentation listed in the "Related Documents" section.



Note This procedure does not apply when starting the router for the first time or after a power cycle or reload.


Prerequisites

You should have a working knowledge of Cisco IOS XR software and have sufficient permissions to configure the software.

You must log in as root-system before starting the procedure. To confirm your login status, use the
show user group command:

RP/0/RP1/CPU0:router# show user group
 
   
root-system, cisco-support
 
   

To confirm your login status including root, use the show user all | include root command:

RP/0/RP1/CPU0:router# show user all | include root
 
   
Groups: root-system, cisco-support
Task:              root-lr  : READ    WRITE    EXECUTE    DEBUG (reserved)
Task:          root-system  : READ    WRITE    EXECUTE    DEBUG (reserved)

SUMMARY STEPS

1. admin

2. show platform

3. show controllers fabric plane all

4. configure

5. controllers fabric plane plane_number shutdown

6. commit

7. end

8. show controllers fabric plane all

9. configure

10. hw-module power disable location nodeID

11. commit

12. end

13. show platform

14. When the fabric card state changes to UNPOWERED, replace the fabric card.

15. configure

16. no hw-module power disable location nodeID

17. commit

18. end

19. show platform

20. configure

21. no controllers fabric plane plane_number shutdown

22. commit

23. end

24. show controllers fabric plane all

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

admin

Example:

RP/0/RP0/CPU0:router# admin

Enters administration EXEC mode.

Step 2 

show platform

Example:

RP/0/RP0/CPU0:router(admin)# show platform

Displays all cards on the router.

Allows you to identify a fabric card (identified with an SM prefix).

The number following the SM prefix identifies the corresponding fabric plane, as follows:

Slot SM0: fabric plane 0

Slot SM1: fabric plane 1

Slot SM2: fabric plane 2

Slot SM3: fabric plane 3

Slot SM4: fabric plane 4

Slot SM5: fabric plane 5

Slot SM6: fabric plane 6

Slot SM7: fabric plane 7

Step 3 

show controllers fabric plane all

Example:

RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all

Displays the status of each fabric plane.

Step 4 

configure

Example:

RP/0/RP0/CPU0:router(admin)# configure

Enters administration configuration mode.

Step 5 

controllers fabric plane plane_number shutdown

Example:

RP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 0 shutdown

Shuts down the fabric plane.

Step 6 

commit

Example:

RP/0/RP0/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 7 

end

Example:

RP/0/RP0/CPU0:router(admin-config)# end

Exits administration configuration mode and returns to administration EXEC mode.

Step 8 

show controllers fabric plane all

Example:

RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all

Displays the status of each fabric plane.

The Admin State and Oper State columns should read DOWN.

Step 9 

configure

Example:

RP/0/RP0/CPU0:router(admin)# configure

Enters administration configuration mode.

Step 10 

hw-module power disable location nodeID

Example:

RP/0/RP0/CPU0:router(admin-config)# hw-module power disable location 0/SM0/SP

Sets the target configuration to remove power from the fabric card.

Step 11 

commit

Example:

RP/0/RP0/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 12 

end

Example:

RP/0/RP0/CPU0:router(admin-config)# end

Exits administration configuration mode and returns to administration EXEC mode.

Step 13 

show platform

Example:

RP/0/RP0/CPU0:router(admin)# show platform

Displays the status of all cards on the router.

Check the State column for the status of the fabric card.

Do not continue to the next step until the status in the State column changes to UNPOWERED.

It takes some time for the card to shut down. Repeat the show platform command to check the card state.

Step 14 

When the fabric card state changes to UNPOWERED, replace the fabric card.

Replaces the physical card.

Step 15 

configure

Example:

RP/0/RP0/CPU0:router(admin)# configure

Enters administration configuration mode.

Step 16 

no hw-module power disable location nodeID

Example:

RP/0/RP0/CPU0:router(admin-config)# no hw-module power disable location 0/SM0/SP

Sets the target configuration to restore power to the fabric card.

Step 17 

commit

Example:

RP/0/RP0/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 18 

end

Example:

RP/0/RP0/CPU0:router(admin-config)# end

Ends the configuration session and returns to administration EXEC mode.

Step 19 

show platform

Example:

RP/0/RP0/CPU0:router(admin)# show platform

Displays the status of all cards on the router.

Check the State column for the status of the fabric card.

Do not continue to the next step until the status in the State column changes to IOS XR RUN.

It takes some time for the card to start up. Repeat the show platform command to check the card state.

Step 20 

configure

Example:

RP/0/RP0/CPU0:router(admin)# configure

Enters administration configuration mode.

Step 21 

no controllers fabric plane plane_number shutdown

Example:

RP/0/RP0/CPU0:router(admin-config)# no controllers fabric plane 0 shutdown

Sets the target configuration to bring up the fabric plane.

Step 22 

commit

Example:

RP/0/RP0/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 23 

end

Example:

RP/0/RP0/CPU0:router(admin-config)# end

Exits administration configuration mode and returns to administration EXEC mode.

Step 24 

show controllers fabric plane all

Example:

RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all

Displays the fabric plane status.

The Admin State and Oper State columns should read UP.

Examples

The following example shows the commands and command responses for replacing a CRS-16-FC/S card:

RP/0/RP1/CPU0:router# admin
 
   
RP/0/RP1/CPU0:router(admin)# 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             16OC48-POS/DPT  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
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
0/SM4/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
 
   
RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all
 
   
  Flags: P - plane admin down,       p - plane oper down
 
   
         C - card admin down,        c - card  oper down
         L - link port admin down,   l - linkport oper down
         A - asic admin down,        a - asic oper down
         B - bundle port admin Down, b - bundle port oper down
         I - bundle admin down,      i - bundle oper down
         N - node admin down,        n - node down
         o - other end of link down  d - data down
         f - failed component downstream
         m - plane multicast down
 
   
 Plane  Admin   Oper
 
   
 Id     State   State
 --------------------
 0      UP      UP
 1      UP      UP
 2      UP      UP
 3      UP      UP
 4      UP      UP
 5      UP      UP
 6      UP      UP
 7      UP      UP
 
   
RP/0/RP1/CPU0:router(admin)# configure
 
   
RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 0 shutdown
 
   
RP/0/RP1/CPU0:router(admin-config)# commit
 
   
RP/0/RP1/CPU0:Oct  5 02:15:09.265 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO
WN : Plane 0 state changed to DOWN:
RP/0/RP1/CPU0:Oct  5 02:15:09.319 : config[65734]: %MGBL-LIBTARCFG-6-ADMIN_COMMI
T : Administration configuration committed by user 'jim'.
 
   
RP/0/RP1/CPU0:router(admin-config)# end
 
   
RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all
 
   
  Flags: P - plane admin down,       p - plane oper down
         C - card admin down,        c - card  oper down
         L - link port admin down,   l - linkport oper down
         A - asic admin down,        a - asic oper down
         B - bundle port admin Down, b - bundle port oper down
         I - bundle admin down,      i - bundle oper down
         N - node admin down,        n - node down
         o - other end of link down  d - data down
         f - failed component downstream
         m - plane multicast down
 
   
 Plane  Admin   Oper
 Id     State   State
 --------------------
 0      DOWN    DOWN
 1      UP      UP
 2      UP      UP
 3      UP      UP
 4      UP      UP
 5      UP      UP
 6      UP      UP
 7      UP      UP
 
   
RP/0/RP1/CPU0:router(admin)# configure
 
   
RP/0/RP1/CPU0:router(admin-config)# hw-module power disable location 0/SM0/SP
 
   
RP/0/RP1/CPU0:router(admin-config)# commit
 
   
RP/0/RP1/CPU0:Oct  5 02:18:24.774 : config[65734]: %MGBL-LIBTARCFG-6-COMMIT : Co
nfiguration committed by user 'jim'.   Use 'show configuration commit changes 10
00000142' to view the changes.
RP/0/RP1/CPU0:router(config)#LC/0/1/CPU0:Oct  5 02:18:26.873 : fabricq_mgr[
127]: %FABRIC-FABRICQ-3-FI_UNCORR_ERROR : fabricq: Major error in Fabric Interfa
ce : RS Uncorrectable errors on Fabricq ASIC 0 link 3
RP/0/RP1/CPU0:Oct  5 02:18:28.959 : shelfmgr[284]: %PLATFORM-SHELFMGR-3-POWERDOW
N_RESET : Node 0/SM0/SP is powered off due to admin power off request
 
   
RP/0/RP1/CPU0:router(admin-config)# end
 
   
RP/0/RP1/CPU0:router(admin)# 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             16OC48-POS/DPT  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             UNPOWERED       NPWR,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
0/SM4/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
 
   

When the state of the fabric card changes to UNPOWERED, replace the fabric card.

RP/0/RP1/CPU0:router# configure
 
   
RP/0/RP1/CPU0:router(admin-config)# no hw-module power disable location 0/SM0/SP
 
   
RP/0/RP1/CPU0:router(admin-config)# commit
 
   
RP/0/RP1/CPU0:Oct  5 02:19:30.472 : config[65734]: %MGBL-LIBTARCFG-6-COMMIT : Co
nfiguration committed by user 'jim'.   Use 'show configuration commit changes 10
00000143' to view the changes.
RP/0/RP1/CPU0:router(config)#RP/0/RP1/CPU0:Oct  5 02:19:42.747 : shelfmgr[2
84]: %PLATFORM-MBIMGR-7-IMAGE_VALIDATED : 0/SM0/SP: MBI tftp:/hfr-os-mbi-3.3.0/
sp/mbihfr-sp.vm validated
 
   
RP/0/RP1/CPU0:router(admin-config)# end
 
   
RP/0/RP1/CPU0:router(admin)# 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             16OC48-POS/DPT  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             MBI-BOOTING     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
0/SM4/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
 
   
RP/0/RP1/CPU0:router(admin)# 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             16OC48-POS/DPT  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             MBI-RUNNING     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
0/SM4/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
 
   
RP/0/RP1/CPU0:router(admin)# 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             16OC48-POS/DPT  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
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
0/SM4/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
 
   
RP/0/RP1/CPU0:router(admin)# configure
 
   
RP/0/RP1/CPU0:router(admin-config)#SP/0/SM0/SP:Oct  5 02:20:19.102 : init[6
 
   
5541]: %OS-INIT-7-MBI_STARTED : total time 7.678 seconds
SP/0/SM0/SP:Oct  5 02:20:21.361 : insthelper[60]: %INSTALL-INSTHELPER-7-PKG_DOWN
LOAD : MBI running; starting software download
SP/0/SM0/SP:Oct  5 02:22:23.458 : init[65541]: %OS-INIT-7-INSTALL_READY : total
time 132.060 seconds
SP/0/SM0/SP:Oct  5 02:22:39.329 : sfe_drvr[108][120]: Board revision : 0x06.
SP/0/SM0/SP:Oct  5 02:22:47.306 : sfe_drvr[108]: %FABRIC-FABRIC_DRVR-6-ASIC_IN
ITIALIZED : Fabric ASICs initialized
SP/0/SM0/SP:Oct  5 02:23:06.316 : alphadisplay[100]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/SM0/SP changed to IOS-XR   in state default
 
   
RP/0/RP1/CPU0:router(admin-config)# no controllers fabric plane 0 shutdown
 
   
RP/0/RP1/CPU0:router(admin-config)# commit
RP/0/RP1/CPU0:Oct  5 02:25:15.736 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO
WN : Plane 0 state changed to UP:
RP/0/RP1/CPU0:Oct  5 02:25:15.759 : config[65734]: %MGBL-LIBTARCFG-6-ADMIN_COMMI
T : Administration configuration committed by user 'jim'.
 
   
RP/0/RP1/CPU0:router(admin-config)# end
 
   
RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all
  Flags: P - plane admin down,       p - plane oper down
         C - card admin down,        c - card  oper down
 
   
         L - link port admin down,   l - linkport oper down
         A - asic admin down,        a - asic oper down
         B - bundle port admin Down, b - bundle port oper down
         I - bundle admin down,      i - bundle oper down
         N - node admin down,        n - node down
         o - other end of link down  d - data down
         f - failed component downstream
         m - plane multicast down
 
   
 Plane  Admin   Oper
 Id     State   State
 --------------------
 0      UP      UP
 1      UP      UP
 2      UP      UP
 3      UP      UP
 4      UP      UP
 5      UP      UP
 6      UP      UP
 7      UP      UP
 
   

Removing and Replacing Cisco CRS-8-FC/S Switch Fabric Cards

Each CRS-8-FC/S switch fabric card provides the Stage 1, 2, and 3 switch fabric for two fabric planes in a standalone Cisco CRS-1 Carrier Routing System 8-Slot Line Card Chassis.

The Cisco CRS-1 8-Slot LCC can support the maximum throughput with seven of the eight fabric planes. However, because each CRS-8-FC/S switch fabric card hosts two fabric planes, replacing a fabric card does reduce the maximum throughput and impacts router traffic if the router is operating at maximum capacity. To minimize traffic loss, we recommend that you shut the power down for the switch fabric card before you remove it. If a switch fabric card is removed with power on, the card is not harmed, but the traffic impact may be greater than if the card power were removed. When the replacement card is inserted, you can restore the power and bring up the replacement card. This section describes how to properly remove and replace a Cisco CRS-8-FC/S switch fabric card for upgrades or repairs.


Note The process of removing and replacing cards while the router power is on is called online insertion and removal (OIR). This procedure removes power to a specific slot before the switch fabric card is replaced. The power remains on for all other slots.



Tip For more information about switch fabric cards, see the hardware documentation listed in the "Related Documents" section.



Note This procedure does not apply when starting the router for the first time or after a power cycle or reload.


Prerequisites

You should have a working knowledge of Cisco IOS XR software and have sufficient permissions to configure the software.

You must log in as root-system before starting the procedure. To confirm your login status, use the
show user group command:

RP/0/RP1/CPU0:router# show user group
 
   
root-system, cisco-support
 
   

To confirm your login status including root, use the show user all | include root command:

RP/0/RP1/CPU0:router# show user all | include root
 
   
Groups: root-system, cisco-support
Task:              root-lr  : READ    WRITE    EXECUTE    DEBUG (reserved)
Task:          root-system  : READ    WRITE    EXECUTE    DEBUG (reserved)
 
   

SUMMARY STEPS

1. admin

2. show platform

3. show controllers fabric plane all

4. configure

5. controllers fabric plane plane_number shutdown

6. controllers fabric plane plane_number shutdown

7. commit

8. end

9. show controllers fabric plane all

10. configure

11. hw-module power disable location nodeID

12. commit

13. end

14. show platform

15. When the fabric card state changes to UNPOWERED, replace the fabric card.

16. configure

17. no hw-module power disable location nodeID

18. commit

19. end

20. show platform

21. configure

22. no controllers fabric plane plane_number shutdown

23. no controllers fabric plane plane_number shutdown

24. commit

25. end

26. show controllers fabric plane all

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

admin

Example:

RP/0/RP0/CPU0:router# admin

Enters administration EXEC mode.

Step 2 

show platform

Example:

RP/0/RP0/CPU0:router(admin)# show platform

Displays all cards on the router.

Allows you to identify a fabric card (identified with an SM prefix).

The number following the SM prefix identifies the corresponding fabric planes, as follows:

Slot SM0: fabric planes 0 and 1

Slot SM1: fabric planes 2 and 3

Slot SM2: fabric planes 4 and 5

Slot SM3: fabric planes 6 and 7

Step 3 

show controllers fabric plane all

Example:

RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all

Displays the status of each fabric plane.

Step 4 

configure

Example:

RP/0/RP0/CPU0:router(admin)# configure

Enters administration configuration mode.

Step 5 

controllers fabric plane plane_number shutdown

Example:

RP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 0 shutdown

Shuts down one of the two fabric planes on a CRS-8-FC/S card.

Before removing a CRS-8-FC/S card, shut down both planes for the fabric card. The fabric planes are assigned to fabric cards as follows:

Slot SM0: fabric planes 0 and 1

Slot SM1: fabric planes 2 and 3

Slot SM2: fabric planes 4 and 5

Slot SM3: fabric planes 6 and 7

Step 6 

controllers fabric plane plane_number shutdown

Example:

RP/0/RP0/CPU0:router(admin-config)# controllers fabric plane 1 shutdown

Shuts down one of the two fabric planes on a CRS-8-FC/S card.

Shut down the companion plane to the plane shut down in the previous step.

Step 7 

commit

Example:

RP/0/RP0/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 8 

end

Example:

RP/0/RP0/CPU0:router(admin-config)# end

Exits administration configuration mode and returns to administration EXEC mode.

Step 9 

show controllers fabric plane all

Example:

RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all

Displays the status of each fabric plane.

The Admin State and Oper State columns should read DOWN for both of the shutdown planes.

Step 10 

configure

Example:

RP/0/RP0/CPU0:router(admin)# configure

Enters administration configuration mode.

Step 11 

hw-module power disable location nodeID

Example:

RP/0/RP0/CPU0:router(admin-config)# hw-module power disable location 0/SM0/SP

Sets the target configuration to remove power from the fabric card.

Step 12 

commit

Example:

RP/0/RP0/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 13 

end

Example:

RP/0/RP0/CPU0:router(admin-config))# end

Exits administration configuration mode and returns to administration EXEC mode.

Step 14 

show platform

Example:

RP/0/RP0/CPU0:router(admin)# show platform

Displays the status of all cards on the router.

Check the State column for the status of the fabric card.

Do not continue to the next step until the status in the State column changes to UNPOWERED.

It takes some time for the card to shut down. Repeat the show platform command to check the card state.

Step 15 

When the fabric card state changes to UNPOWERED, replace the fabric card.

Replaces the physical card.

Step 16 

configure

Example:

RP/0/RP0/CPU0:router(admin)# configure

Enters administration configuration mode.

Step 17 

no hw-module power disable location nodeID

Example:

RP/0/RP0/CPU0:router(admin-config)# no hw-module power disable location 0/SM0/SP

Sets the target configuration to restore power to the fabric card.

Step 18 

commit

Example:

RP/0/RP0/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 19 

end

Example:

RP/0/RP0/CPU0:router(admin)# end

Ends the configuration session and returns to administration EXEC mode.

Step 20 

show platform

Example:

RP/0/RP0/CPU0:router(admin)# show platform

Displays the status of all cards on the router.

Check the State column for the status of the fabric card.

Do not continue to the next step until the status in the State column changes to IOS XR RUN.

It takes some time for the card to start up. Repeat the show platform command to check the card state.

Step 21 

configure

Example:

RP/0/RP0/CPU0:router(admin)# configure

Enters administration configuration mode.

Step 22 

no controllers fabric plane plane_number shutdown

Example:

RP/0/RP0/CPU0:router(admin-config)# no controllers fabric plane 0 shut

Sets the target configuration to bring up one of the two fabric planes on the card.

Step 23 

no controllers fabric plane plane_number shutdown

Example:

RP/0/RP0/CPU0:router(admin-config)# no controllers fabric plane 1 shut

Sets the target configuration to bring up one of the two fabric planes on the card.

Step 24 

commit

Example:

RP/0/RP0/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 25 

end

Example:

RP/0/RP0/CPU0:router(admin-config)# end

Exits administration configuration mode and returns to administration EXEC mode.

Step 26 

show controllers fabric plane all

Example:

RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all

Displays the fabric plane status.

The Admin State and Oper State columns should read UP for both fabric planes on the fabric card.

Examples

The following example shows the commands and command responses for replacing a CRS-8-FC/S card:

RP/0/RP1/CPU0:router# admin
 
   
RP/0/RP1/CPU0:router(admin)# 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             16OC48-POS/DPT  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
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
 
   
RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all
 
   
  Flags: P - plane admin down,       p - plane oper down
 
   
         C - card admin down,        c - card  oper down
         L - link port admin down,   l - linkport oper down
         A - asic admin down,        a - asic oper down
         B - bundle port admin Down, b - bundle port oper down
         I - bundle admin down,      i - bundle oper down
         N - node admin down,        n - node down
         o - other end of link down  d - data down
         f - failed component downstream
         m - plane multicast down
 
   
 Plane  Admin   Oper
 
   
 Id     State   State
 --------------------
 0      UP      UP
 1      UP      UP
 2      UP      UP
 3      UP      UP
 4      UP      UP
 5      UP      UP
 6      UP      UP
 7      UP      UP
 
   
RP/0/RP1/CPU0:router(admin)# configure
 
   
RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 0 shutdown
 
   
RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 1 shutdown
 
   
RP/0/RP1/CPU0:router(admin-config)# commit
 
   
RP/0/RP1/CPU0:Oct  5 02:15:09.265 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO
WN : Plane 0 state changed to DOWN:
RP/0/RP1/CPU0:Oct  5 02:15:09.265 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO
WN : Plane 1 state changed to DOWN:
RP/0/RP1/CPU0:Oct  5 02:15:09.319 : config[65734]: %MGBL-LIBTARCFG-6-ADMIN_COMMI
T : Administration configuration committed by user 'jim'.
 
   
RP/0/RP1/CPU0:router(admin-config)# end
 
   
RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all
 
   
  Flags: P - plane admin down,       p - plane oper down
         C - card admin down,        c - card  oper down
         L - link port admin down,   l - linkport oper down
         A - asic admin down,        a - asic oper down
         B - bundle port admin Down, b - bundle port oper down
         I - bundle admin down,      i - bundle oper down
         N - node admin down,        n - node down
         o - other end of link down  d - data down
         f - failed component downstream
         m - plane multicast down
 
   
 Plane  Admin   Oper
 Id     State   State
 --------------------
 0      DOWN    DOWN
 1      DOWN    DOWN
 2      UP      UP
 3      UP      UP
 4      UP      UP
 5      UP      UP
 6      UP      UP
 7      UP      UP
 
   
RP/0/RP1/CPU0:router(admin)# configure
 
   
RP/0/RP1/CPU0:router(admin-config)# hw-module power disable location 0/SM0/SP
 
   
RP/0/RP1/CPU0:router(admin-config)# commit
 
   
RP/0/RP1/CPU0:Oct  5 02:18:24.774 : config[65734]: %MGBL-LIBTARCFG-6-COMMIT : Co
nfiguration committed by user 'jim'.   Use 'show configuration commit changes 10
00000142' to view the changes.
RP/0/RP1/CPU0:router(config)#LC/0/1/CPU0:Oct  5 02:18:26.873 : fabricq_mgr[
127]: %FABRIC-FABRICQ-3-FI_UNCORR_ERROR : fabricq: Major error in Fabric Interfa
ce : RS Uncorrectable errors on Fabricq ASIC 0 link 3
RP/0/RP1/CPU0:Oct  5 02:18:28.959 : shelfmgr[284]: %PLATFORM-SHELFMGR-3-POWERDOW
N_RESET : Node 0/SM0/SP is powered off due to admin power off request
 
   
RP/0/RP1/CPU0:router(admin-config)# end
 
   
RP/0/RP1/CPU0:router(admin)# 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             16OC48-POS/DPT  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             UNPOWERED       NPWR,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
 
   

When the State for the fabric card changes to UNPOWERED, replace the fabric card.

RP/0/RP1/CPU0:router(admin)# configure
 
   
RP/0/RP1/CPU0:router(admin-config)# no hw-module power disable location 0/SM0/SP
 
   
RP/0/RP1/CPU0:router(admin-config)# commit
 
   
RP/0/RP1/CPU0:Oct  5 02:19:30.472 : config[65734]: %MGBL-LIBTARCFG-6-COMMIT : Co
nfiguration committed by user 'jim'.   Use 'show configuration commit changes 10
00000143' to view the changes.
RP/0/RP1/CPU0:router(config)#RP/0/RP1/CPU0:Oct  5 02:19:42.747 : shelfmgr[2
84]: %PLATFORM-MBIMGR-7-IMAGE_VALIDATED : 0/SM0/SP: MBI tftp:/hfr-os-mbi-3.3.0/
sp/mbihfr-sp.vm validated
 
   
RP/0/RP1/CPU0:router(admin-config)# end
 
   
RP/0/RP1/CPU0:router(admin)# 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             16OC48-POS/DPT  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             MBI-BOOTING     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
 
   
RP/0/RP1/CPU0:router(admin)# 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             16OC48-POS/DPT  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             MBI-RUNNING     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
 
   
RP/0/RP1/CPU0:router(admin)# 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             16OC48-POS/DPT  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
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
 
   
RP/0/RP1/CPU0:router(admin)# configure
 
   
RP/0/RP1/CPU0:router(admin-config)#SP/0/SM0/SP:Oct  5 02:20:19.102 : init[6
 
   
5541]: %OS-INIT-7-MBI_STARTED : total time 7.678 seconds
SP/0/SM0/SP:Oct  5 02:20:21.361 : insthelper[60]: %INSTALL-INSTHELPER-7-PKG_DOWN
LOAD : MBI running; starting software download
SP/0/SM0/SP:Oct  5 02:22:23.458 : init[65541]: %OS-INIT-7-INSTALL_READY : total
time 132.060 seconds
SP/0/SM0/SP:Oct  5 02:22:39.329 : sfe_drvr[108][120]: Board revision : 0x06.
SP/0/SM0/SP:Oct  5 02:22:47.306 : sfe_drvr[108]: %FABRIC-FABRIC_DRVR-6-ASIC_IN
ITIALIZED : Fabric ASICs initialized
SP/0/SM0/SP:Oct  5 02:23:06.316 : alphadisplay[100]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/SM0/SP changed to IOS-XR   in state default
 
   
RP/0/RP1/CPU0:router(admin-config)# no controllers fabric plane 0 shutdown
 
   
RP/0/RP1/CPU0:router(admin-config)# no controllers fabric plane 1 shutdown
 
   
RP/0/RP1/CPU0:router(admin-config)# commit
RP/0/RP1/CPU0:Oct  5 02:25:15.736 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO
WN : Plane 0 state changed to UP:
RP/0/RP1/CPU0:Oct  5 02:25:15.736 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDO
WN : Plane 1 state changed to UP:
RP/0/RP1/CPU0:Oct  5 02:25:15.759 : config[65734]: %MGBL-LIBTARCFG-6-ADMIN_COMMI
T : Administration configuration committed by user 'jim'.
 
   
RP/0/RP1/CPU0:router(admin-config)# end
RP/0/RP1/CPU0:Oct  5 02:25:41.891 : config[65734]: %MGBL-SYS-5-CONFIG_I : Config
ured from console by jim
 
   
RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all
  Flags: P - plane admin down,       p - plane oper down
         C - card admin down,        c - card  oper down
 
   
         L - link port admin down,   l - linkport oper down
         A - asic admin down,        a - asic oper down
         B - bundle port admin Down, b - bundle port oper down
         I - bundle admin down,      i - bundle oper down
         N - node admin down,        n - node down
         o - other end of link down  d - data down
         f - failed component downstream
         m - plane multicast down
 
   
 Plane  Admin   Oper
 Id     State   State
 --------------------
 0      UP      UP
 1      UP      UP
 2      UP      UP
 3      UP      UP
 4      UP      UP
 5      UP      UP
 6      UP      UP
 7      UP      UP
 
   

Removing and Replacing CSC and SFC Cards

On Cisco XR 12000 Series Routers that use clock and scheduler cards (CSCs) and switch fabric cards (SFCs), the CSCs and SFCs work together to provide the switch fabric for the router. Although some router cards can be removed without software preparation, it is best to shut down and remove the power from a CSC or an SFC slot before removing a card. When the new card is inserted, you can restore the power to the slot and bring up the replacement card. This section describes how to properly remove and replace CSCs and SFCs for repairs.

Prerequisites

You should have a working knowledge of Cisco IOS XR software and have sufficient permissions to configure the software.

You must log in as root-system before starting the procedure. To confirm your login status, use the
show user group command:

RP/0/RP1/CPU0:router# show user group
 
   
root-system, cisco-support
 
   

To confirm your login status including root, use the show user all | include root command:

RP/0/RP1/CPU0:router# show user all | include root
 
   
Groups: root-system, cisco-support
Task:              root-lr  : READ    WRITE    EXECUTE    DEBUG (reserved)
Task:          root-system  : READ    WRITE    EXECUTE    DEBUG (reserved)
 
   

SUMMARY STEPS

1. admin

2. show platform

3. configure

4. hw-module location slot shutdown

5. hw-module location slot power disable

6. commit

7. end

8. show platform

9. Remove and replace the CSC or SFC.

10. configure

11. no hw-module location slot power disable

12. commit

13. end

14. show platform

15. configure

16. no hw-module location slot shutdown

17. commit

18. end

19. show platform

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

admin

Example:

RP/0/0/CPU0:router# admin

Enters administration EXEC mode.

Step 2 

show platform

Example:

RP/0/0/CPU0:router(admin)# show platform

Displays the state of all cards on the router.

Allows you to identify the CSC or SFC you want to replace.

Note the node ID (in the first column) for the card you want to replace. You need to enter this ID later in this procedure.

Step 3 

configure

Example:

RP/0/0/CPU0:router(admin)# configure

Enters administration configuration mode.

Step 4 

hw-module location slot shutdown

Example:

RP/0/0/CPU0:router(admin-config)# hw-module location 0/16/CPU0 shutdown

Configures a slot to shut down when the configuration is committed.


Caution Shut down only one CSC or SFC from the combined set of CSCs and SFCs at a time. For example, shut down one CSC or one SFC, but do not shut down two CSCs, two or more SFCs, or cards of both types at the same time. When shutting down a CSC, shutdown the standby CSC.

Step 5 

hw-module location slot power disable

Example:

RP/0/0/CPU0:router(admin-config)# hw-module location 0/16/CPU0 power disable

Configures a slot to power down when the configuration is committed.

Step 6 

commit

Example:

RP/0/0/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Note You do not need to enter the end or exit command or press Ctrl-Z to exit administration configuration mode until the end of this procedure. If you exit administration configuration mode, you must re-enter this mode to complete the procedure.

Step 7 

end

Example:

RP/0/RP0/CPU0:router(admin-config)# end

Exits administration configuration mode and returns to administration EXEC mode.

Step 8 

show platform

Example:

RP/0/0/CPU0:router(admin)# show platform

(Optional) Displays the state of all cards on the router.

Allows you to verify that the CSC or SFC you want to replace is shut down and the power is off.

Step 9 

Remove and replace the CSC or SFC.

Replaces the physical card.

Step 10 

configure

Example:

RP/0/0/CPU0:router(admin)# configure

Enters administration configuration mode.

Step 11 

no hw-module location slot power disable

Example:

RP/0/0/CPU0:router(admin-config)# no hw-module location 0/16/CPU0 power disable

Configures a slot to power up when the configuration is committed.

Step 12 

commit

Example:

RP/0/0/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 13 

end

Example:

RP/0/RP0/CPU0:router(admin-config)# end

Exits administration configuration mode and returns to administration EXEC mode.

Step 14 

show platform

Example:

RP/0/0/CPU0:router(admin)# show platform

(Optional) Displays the state of all cards on the router.

Allows you to verify that the replacement CSC or SFC has power.

Step 15 

configure

Example:

RP/0/0/CPU0:router(admin)# configure

Enters administration configuration mode.

Step 16 

no hw-module location slot shutdown

Example:

RP/0/0/CPU0:router(admin-config)# no hw-module location 0/16/CPU0 shutdown

Configures a slot to start when the configuration is committed.

Step 17 

commit

Example:

RP/0/0/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 18 

end

Example:

RP/0/RP0/CPU0:router(admin-config)# end

Exits administration configuration mode and returns to administration EXEC mode.

Step 19 

show platform

Example:

RP/0/0/CPU0:router(admin)# show platform

(Optional) Displays the state of all cards on the router.

Allows you to verify that the replacement CSC or SFC has power and has been brought up.

Examples

Replacing a CSC: Example

The following example shows commands to change a CSC:

RP/0/0/CPU0:router# admin
 
   
RP/0/0/CPU0:router(admin)# show platform
 
   
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/0/CPU0        PRP(Active)     N/A             IOS XR RUN      PWR,NSHUT,MON
0/3/CPU0        L3LC Eng 3      OC3-POS-8       IOS XR RUN      PWR,NSHUT,MON
0/4/CPU0        L3LC Eng 3      GE-4            IOS XR RUN      PWR,NSHUT,MON
0/5/CPU0        L3LC Eng 3      GE-4            IOS XR RUN      PWR,NSHUT,MON
0/6/CPU0        L3LC Eng 3      OC48-POS        IOS XR RUN      PWR,NSHUT,MON
0/7/CPU0        L3LC Eng 3      GE-4            IOS XR RUN      PWR,NSHUT,MON
0/8/CPU0        L3LC Eng 3      OC12-POS-4      IOS XR RUN      PWR,NSHUT,MON
0/16/CPU0       CSC10           N/A             PWD             PWR,NSHUT,MON
0/17/CPU0       CSC10(P)        N/A             PWD             PWR,NSHUT,MON
0/18/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/19/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/20/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/21/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/22/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/24/CPU0       ALARM10         N/A             PWD             PWR,NSHUT,MON
0/25/CPU0       ALARM10         N/A             PWD             PWR,NSHUT,MON
0/29/CPU0       GSR16-BLOWER    N/A             PWD             PWR,NSHUT,MON
 
   
RP/0/0/CPU0:router(admin)# configure
 
   
RP/0/0/CPU0:router(admin-config)# hw-module location 0/16/CPU0 shutdown
 
   
RP/0/0/CPU0:router(admin-config)# hw-module location 0/16/CPU0 power disable
 
   
RP/0/0/CPU0:router(admin-config)# commit
 
   
 
   
Primary Clock is CSC_1
Fabric Clock is Non Redundant
Bandwidth Mode : Full Bandwidth
 
   
RP/0/0/CPU0:router(admin-config)# end
 
   
RP/0/0/CPU0:router(admin)# show platform
 
   
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/0/CPU0        PRP(Active)     N/A             IOS XR RUN      PWR,NSHUT,MON
0/3/CPU0        L3LC Eng 3      OC3-POS-8       IOS XR RUN      PWR,NSHUT,MON
0/4/CPU0        L3LC Eng 3      GE-4            IOS XR RUN      PWR,NSHUT,MON
0/5/CPU0        L3LC Eng 3      GE-4            IOS XR RUN      PWR,NSHUT,MON
0/6/CPU0        L3LC Eng 3      OC48-POS        IOS XR RUN      PWR,NSHUT,MON
0/7/CPU0        L3LC Eng 3      GE-4            IOS XR RUN      PWR,NSHUT,MON
0/8/CPU0        L3LC Eng 3      OC12-POS-4      IOS XR RUN      PWR,NSHUT,MON
0/16/CPU0       CSC10           N/A             Admin Down      NPWR,SHUT,MON
0/17/CPU0       CSC10(P)        N/A             PWD             PWR,NSHUT,MON
0/18/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/19/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/20/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/21/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/22/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/24/CPU0       ALARM10         N/A             PWD             PWR,NSHUT,MON
0/25/CPU0       ALARM10         N/A             PWD             PWR,NSHUT,MON
0/29/CPU0       GSR16-BLOWER    N/A             PWD             PWR,NSHUT,MON
 
   

Replace the CSC or SFC at this point.

 
   
RP/0/0/CPU0:router(admin)# configure
 
   
RP/0/0/CPU0:router(admin-config)# no hw-module location 0/16/CPU0 power disable
 
   
RP/0/0/CPU0:router(admin-config)# commit
 
   
 
   
Primary Clock is CSC_1
Fabric Clock is Redundant
Bandwidth Mode : Full Bandwidth
 
   
RP/0/0/CPU0:router(admin-config)# end
 
   
RP/0/0/CPU0:router(admin)# show platform
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/0/CPU0        PRP(Active)     N/A             IOS XR RUN      PWR,NSHUT,MON
0/3/CPU0        L3LC Eng 3      OC3-POS-8       IOS XR RUN      PWR,NSHUT,MON
0/4/CPU0        L3LC Eng 3      GE-4            IOS XR RUN      PWR,NSHUT,MON
0/5/CPU0        L3LC Eng 3      GE-4            IOS XR RUN      PWR,NSHUT,MON
0/6/CPU0        L3LC Eng 3      OC48-POS        IOS XR RUN      PWR,NSHUT,MON
0/7/CPU0        L3LC Eng 3      GE-4            IOS XR RUN      PWR,NSHUT,MON
0/8/CPU0        L3LC Eng 3      OC12-POS-4      IOS XR RUN      PWR,NSHUT,MON
0/16/CPU0       CSC10           N/A             Admin Down      PWR,SHUT,MON
0/17/CPU0       CSC10(P)        N/A             PWD             PWR,NSHUT,MON
0/18/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/19/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/20/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/21/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/22/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/24/CPU0       ALARM10         N/A             PWD             PWR,NSHUT,MON
0/25/CPU0       ALARM10         N/A             PWD             PWR,NSHUT,MON
0/29/CPU0       GSR16-BLOWER    N/A             PWD             PWR,NSHUT,MON
 
   
RP/0/0/CPU0:router(admin)# configure
 
   
RP/0/0/CPU0:router(admin-config)# no hw-module location 0/16/CPU0 shutdown
 
   
RP/0/0/CPU0:router(admin-config)# commit
 
   
RP/0/0/CPU0:router(admin-config)# end
 
   
RP/0/0/CPU0:router(admin)# show platform
 
   
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/0/CPU0        PRP(Active)     N/A             IOS XR RUN      PWR,NSHUT,MON
0/3/CPU0        L3LC Eng 3      OC3-POS-8       IOS XR RUN      PWR,NSHUT,MON
0/4/CPU0        L3LC Eng 3      GE-4            IOS XR RUN      PWR,NSHUT,MON
0/5/CPU0        L3LC Eng 3      GE-4            IOS XR RUN      PWR,NSHUT,MON
0/6/CPU0        L3LC Eng 3      OC48-POS        IOS XR RUN      PWR,NSHUT,MON
0/7/CPU0        L3LC Eng 3      GE-4            IOS XR RUN      PWR,NSHUT,MON
0/8/CPU0        L3LC Eng 3      OC12-POS-4      IOS XR RUN      PWR,NSHUT,MON
0/16/CPU0       CSC10           N/A             PWD             PWR,NSHUT,MON
0/17/CPU0       CSC10(P)        N/A             PWD             PWR,NSHUT,MON
0/18/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/19/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/20/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/21/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/22/CPU0       SFC10           N/A             PWD             PWR,NSHUT,MON
0/24/CPU0       ALARM10         N/A             PWD             PWR,NSHUT,MON
0/25/CPU0       ALARM10         N/A             PWD             PWR,NSHUT,MON
0/29/CPU0       GSR16-BLOWER    N/A             PWD             PWR,NSHUT,MON
 
   

Removing and Replacing CSFC Cards

On Cisco XR 12404 routers, which use consolidated switch fabric cards (CSFCs), you must power off the router before changing a CSFC card. For more information about removing and replacing CSFCs, see the hardware documentation listed in the "Related Documents" section.

Adding a Standby PRP to a Cisco 12000 Series Router

A second PRP card can be added to a Cisco 12000 Series Router for redundancy. To add a standby PRP, boot the card from ROMMON mode with the minimum boot image (MBI) software package. This will bring up the PRP so it can be recognized by the DSC. The new standby PRP will download the appropriate software and configurations from the DSC, and reboot.

This section provides instructions to boot the standby RP after it is installed in the chassis. See the "Related Documents" section for more information on installing PRP cards.

Prerequisites

The standby PRP must be installed in a slot next to the active PRP. For example, the PRPs can be installed in slot 0 and slot 1, slot 2 and slot 3, slot 4 and slot 5, slot 6 and slot 7, slot 8 and slot 9, and so on.

MBI software package mbiprp-rp.vm. This package is used to boot any PRP other than the DSC, including the standby PRP and PRPs in named SDRs.

ROMMON version bfprp_romupgrade-1.14.0.91 or higher

Boothelper version c12kprp-boot-mz.120-30.S or higher

The boothelper must be stored as the first file in the bootflash, or the ROMMON variable must be set to point to the boothelper. To set the ROMMON variable, enter the following command in ROM Monitor mode: BOOTLDR=bootflash:/c12kprp-boot-mz.120-30.S

Each PRP must have at least 1024 MB of memory installed. The PRP-2 ships with 1024 MB of memory. Upgrade the memory in your PRP, if necessary.

Flash disks:

The recommended flash disk setup for all PRPs is two 512-MB Sandisk flash disk in PCMCIA slot 0 and slot 1. The minimum requirement is one 512-MB Sandisk flash disk installed in slot 0 on every physical PRP card in the system. PRP cards use the flash disk to store the Cisco IOS XR software and running configurations.

The same flash disk size must be used in all PRPs in the Cisco XR 12000 Series Router.

Each flash disk must be formatted by the Cisco IOS XR software before use. To format a disk, insert the disk into a running PRP and enter the command format disknumber:.
Example: format disk0:.

Summary Steps

1. Attach a terminal to the standby PRP console port, and place the PRP in ROM Monitor mode.

2. unset TURBOBOOT

3. unset BOOT

4. sync

5. boot tftp://server/directory/filename

6. Wait for boot process to complete.

7. show platform

8. show redundancy

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

Attach a terminal to the standby PRP console port, and place the PRP in ROM Monitor mode.

Refer to Cisco IOS XR ROM Monitor Guide for more information.

Step 2 

unset TURBOBOOT

Example:

rommon># unset turboboot

Clears the TURBOBOOT variable. The TURBOBOOT variable is only used on the DSC.

Step 3 

unset BOOT

Example:

rommon># unset BOOT

Clears the boot variable.

Step 4 

sync

Example:

rommon># sync

Saves the changes.

Step 5 

boot tftp://server/directory/filename

Example:

rommon># boot tftp://192.168.1.1/dir/mbiprp-rp.vm

Retrieves the file from the TFTP server and installs it on disk0.

Step 6 

Wait for boot process to complete.

The standby PRP will boot and all ROMMON variables (such as confreg and BOOT) will be set. Once the standby PRP is recognized by the DSC, the appropriate software will download and the standby PRP card will reload the Cisco IOS XR software from disk.

Step 7 

show platform

Example:

RP/0/0/CPU0:router# show platform

Displays the status of all cards.

Enter this command on the active PRP.

The active and standby PRPs are operating properly when the state for each card is "IOS XR RUN."

Step 8 

show redundancy

Example:

RP/0/0/CPU0:router# show redundancy

Displays the redundancy status of the PRP cards.

Enter this command on the active PRP.

When redundancy is fully established, the partner node is in "Standby role" and the standby node is "ready."