Managing The Router Hardware: Cisco IOS XR Getting Started Guide
Managing The Router Hardware: Cisco IOS XR Getting Started Guide
Managing The Router Hardware: Cisco IOS XR Getting Started Guide
Contents
This chapter contains the following sections:
Formatting Hard Drives, Flash Drives, and Other Storage Devices, page 8-27
Displaying the Chassis Serial Numbers (Cisco CRS-1 Routers), page 8-10
8-1
Chapter 8
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
8-2
Chapter 8
8-3
Chapter 8
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]
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.
8-4
Chapter 8
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
8-5
Chapter 8
Displaying Hardware Status
8-6
Chapter 8
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]
8-7
Chapter 8
Displaying Hardware Status
8-8
Chapter 8
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
8-9
Chapter 8
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--
Note
8-10
Chapter 8
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)#
8-11
Chapter 8
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.
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
Card Type
(the card type to which you are
issuing commands)
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
Rack
(always 0 in a
single-shelf system)
0255
CPU0
DRP
0-255
07 (8-slot chassis)
CPU0 or CPU1
MSC
0255
0255
0255
07 (8-slot chassis)
CPU0
8-12
07 (8-slot chassis)
015 (16-slot chassis)
CPU0
Chapter 8
Table 8-1
Card Type
(the card type to which you are
issuing commands)
1-Port OC-192c/STM-64c
Packet-over-SONET/SDH (POS)
XFP SPA
Rack
(always 0 in a
single-shelf system)
0255
Slot
(the physical slot in which the
card is installed)
Module
(the entity on the card that is
the target of the command)
07 (8-slot chassis)
0255
SP
0255
SP
0255
SP
Table 8-2
Card Type
(the card type to which you are
issuing commands)
Route processor
Rack
(always 0 in a single-shelf
system)
0
Slot
(the logical slot number
reported in command
displays)
Module
(the entity on the card that
executes the commands)
0151, 2
CPU0
CPU0
0151
CPU0
0151
015
CSC 0 and 13
CPU0
SFC 0, 1, 2, 3, and 4
Dedicated slot 17
3, 4
CPU0
CPU0
8-13
Chapter 8
8-14
Chapter 8
F0/AM1/SP
F0/LM0/SP
F0/LM1/SP
Note
ALARM(SP)
FCC-LED(SP)
UNKNOWN(SP)
N/A
N/A
N/A
IOS XR RUN
IOS XR RUN
IN-RESET
PWR,NSHUT,MON
PWR,NSHUT,MON
PWR,NSHUT,MON
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.
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.
Modules Sensor
host
host
host
host
host
host
host
host
host
host
host
host
host
host
Inlet
Hot
Inlet
Hot
Inlet
Hot
Inlet
Hot
Hot
Inlet
Inlet
Hot
Inlet
Hot
Temp. (deg C)
23.0
23.0
24.0
33.0
24.5
31.5
23.5
30.5
31.5
22.5
20.0
29.5
20.5
32.0
8-15
Chapter 8
Threshold Information
--------------------------------------------R/S/I
0/0/*
0/3/*
0/4/*
0/5/*
0/6/*
0/7/*
0/8/*
Modules Sensor
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
InletTemp
HotTemp
PLIM_V4_1.6V
PLIM_V5_1.8V
PLIM_V3_2.5V
3.3V
5V
Mbus5V
InletTemp
HotTemp
PLIM_V3_1.5V
PLIM_V8_1.8V
PLIM_V7_2.5V
3.3V
5V
Mbus5V
InletTemp
HotTemp
PLIM_V3_1.5V
PLIM_V8_1.8V
PLIM_V7_2.5V
PLIM_V6_1.5V
5V
3.3V
Mbus5V
InletTemp
HotTemp
PLIM_V3_1.5V
PLIM_V8_1.8V
PLIM_V7_2.5V
PLIM_V6_1.5V
5V
3.3V
Mbus5V
HotTemp
InletTemp
PLIM_V3_1.5V
PLIM_V8_1.8V
PLIM_V7_2.5V
3.3V
Mbus5V
InletTemp
HotTemp
PLIM_V3_1.5V
PLIM_V8_1.8V
PLIM_V7_2.5V
PLIM_V6_1.5V
5V
3.3V
Mbus5V
InletTemp
HotTemp
PLIM_V3_1.5V
PLIM_V8_1.8V
PLIM_V7_2.5V
3.3V
5V
Mbus5V
8-16
Minor
(Lo/Hi)
--/ 55
--/ 66
--/ ---/ ---/ -2950/3500
4800/5150
4700/5300
--/ 55
--/ 66
--/ ---/ ---/ ---/ -4800/5200
4700/5300
--/ 55
--/ 66
--/ ---/ ---/ ---/ ---/ ---/ -4700/5300
--/ 55
--/ 66
--/ ---/ ---/ ---/ ---/ ---/ -4700/5300
--/ 66
--/ 55
--/ ---/ ---/ ---/ -4700/5300
--/ 55
--/ 66
--/ ---/ ---/ ---/ ---/ ---/ -4700/5300
--/ 55
--/ 66
--/ ---/ ---/ ---/ -4800/5200
4700/5300
Major
(Lo/Hi)
--/ 60
--/ 69
--/ ---/ ---/ -2900/3600
4700/5200
4500/5500
--/ 60
--/ 69
--/ ---/ ---/ ---/ -4700/5300
4600/5400
--/ 60
--/ 69
--/ ---/ ---/ ---/ ---/ ---/ -4600/5400
--/ 60
--/ 69
--/ ---/ ---/ ---/ ---/ ---/ -4600/5400
--/ 69
--/ 60
--/ ---/ ---/ ---/ -4600/5400
--/ 60
--/ 69
--/ ---/ ---/ ---/ ---/ ---/ -4600/5400
--/ 60
--/ 69
--/ ---/ ---/ ---/ -4700/5300
4600/5400
Critical
(Lo/Hi)
--/ ---/ ---/ ---/ ---/ ---/ ---/ ---/ ---/ 70
--/ 75
--/ ---/ ---/ ---/ -4600/5400
4500/5500
--/ 70
--/ 75
--/ ---/ ---/ ---/ ---/ ---/ -4500/5500
--/ 70
--/ 75
--/ ---/ ---/ ---/ ---/ ---/ -4500/5500
--/ 75
--/ 70
--/ ---/ ---/ ---/ -4500/5500
--/ 70
--/ 75
--/ ---/ ---/ ---/ ---/ ---/ -4500/5500
--/ 70
--/ 75
--/ ---/ ---/ ---/ -4600/5400
4500/5500
Chapter 8
Voltage Information
--------------------------------------------R/S/I
0/0/*
0/3/*
0/4/*
0/5/*
0/6/*
0/7/*
0/8/*
Modules Sensor
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
PLIM_V4_1.6V
PLIM_V5_1.8V
PLIM_V3_2.5V
3.3V
5V
Mbus5V
PLIM_V3_1.5V
PLIM_V8_1.8V
PLIM_V7_2.5V
3.3V
5V
Mbus5V
PLIM_V3_1.5V
PLIM_V8_1.8V
PLIM_V7_2.5V
PLIM_V6_1.5V
5V
3.3V
Mbus5V
PLIM_V3_1.5V
PLIM_V8_1.8V
PLIM_V7_2.5V
PLIM_V6_1.5V
5V
3.3V
Mbus5V
PLIM_V3_1.5V
PLIM_V8_1.8V
PLIM_V7_2.5V
3.3V
Mbus5V
PLIM_V3_1.5V
PLIM_V8_1.8V
PLIM_V7_2.5V
PLIM_V6_1.5V
5V
3.3V
Mbus5V
PLIM_V3_1.5V
PLIM_V8_1.8V
PLIM_V7_2.5V
3.3V
5V
Mbus5V
Voltage (mV)
1612
1804
2504
3296
5048
5048
1496
1788
2492
3284
5000
5024
1500
1796
2488
1508
4976
3288
5048
1504
1792
2488
1504
4976
3284
4984
1496
1792
2476
3300
5016
1504
1796
2484
1504
4976
3276
4984
1496
1792
2492
3280
5000
5024
Margin
nominal
nominal
nominal
nominal
nominal
n/a
nominal
nominal
nominal
nominal
nominal
n/a
nominal
nominal
nominal
nominal
nominal
nominal
n/a
nominal
nominal
nominal
nominal
nominal
nominal
n/a
nominal
nominal
nominal
nominal
n/a
nominal
nominal
nominal
nominal
nominal
nominal
n/a
nominal
nominal
nominal
nominal
nominal
n/a
8-17
Chapter 8
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
8-18
Chapter 8
B2
AM1
Line card
PLIM
PLIM
PL PL PL PL
12 13 14 15
116536
PL PL
PL8 PL9 10 11
PLIM
PLIM
RP0
RP1
PLIM
PLIM
PLIM
PLIM
PLIM
B1
PLIM
B0
PLIM
AM0
PLIM
FC0
FC1
PLIM
A2
PLIM
A1
Line card
Redundant Set of RPs Installed in Slots RP0 and RP1 in a 16-Slot Chassis
A0
PLIM
PLIM
Figure 8-1
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.
8-19
Chapter 8
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.
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 on page 4-12 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:
8-20
Chapter 8
RP Redundancy Commands
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.
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.
Caution
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.
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 on page 8-24 for more
information.
8-21
Chapter 8
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.
8-22
Chapter 8
Note
1.
2.
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)
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.
8-23
Chapter 8
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.
Command
Description
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.
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.
8-24
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.
Chapter 8
Table 8-4
Command
Description
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 on
page 8-25 for more information.
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
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.
4.
5.
exit
6.
reload
8-25
Chapter 8
DETAILED STEPS
Step 1
Command or Action
Purpose
show redundancy
Example:
RP/0/RP0/CPU0:router# show redundancy
Step 2
admin
Example:
RP/0/RP0/CPU0:router# admin
Step 3
Example:
RP/0/RP0/CPU0:router(admin)# show variables
boot
Step 4
config-register 0x2102
Note
Example:
RP/0/RP0/CPU0:router(admin)# config-register
0x2102
Step 5
exit
Example:
RP/0/RP0/CPU0:router(admin)# exit
Step 6
reload
Example:
RP/0/RP0/CPU0:router# reload
8-26
Chapter 8
Caution
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
In the following example, the format command is used to format the hard disk:
RP/0/RP0/CPU0:router# format harddisk:
8-27
Chapter 8
Replacing a Line Card or PLIM with the Same Media Type and Port Count, page 8-29
Replacing a Line Card or PLIM with the Same Media Type and a Different Port Count, page 8-29
Replacing a Line Card or PLIM with a Different Media Type, page 8-30
Removing and Replacing Cisco CRS-16-FC Switch Fabric Cards, page 8-30
Removing and Replacing Cisco CRS-8-FC/S Switch Fabric Cards, page 8-38
8-28
Chapter 8
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 on
page 8-28 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 on
page 8-28 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 on page 8-28 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
8-29
Chapter 8
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.
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.
8-30
Chapter 8
Tip
For more information about switch fabric cards, see the hardware documentation listed in the Related
Documents section on page xiii.
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
Task:
root-system : READ
WRITE
WRITE
EXECUTE
EXECUTE
DEBUG (reserved)
DEBUG (reserved)
SUMMARY STEPS
1.
admin
2.
show platform
3.
4.
configure
5.
6.
commit
7.
end
8.
9.
configure
8-31
Chapter 8
DETAILED STEPS
Step 1
Command or Action
Purpose
admin
Example:
RP/0/RP0/CPU0:router# admin
Step 2
show platform
Example:
RP/0/RP0/CPU0:router(admin)# show platform
Example:
RP/0/RP0/CPU0:router(admin)# show controllers
fabric plane all
Step 4
configure
Example:
RP/0/RP0/CPU0:router(admin)# configure
Step 5
Example:
RP/0/RP0/CPU0:router(admin-config)#
controllers fabric plane 0 shutdown
8-32
Chapter 8
Step 6
Command or Action
Purpose
commit
Example:
RP/0/RP0/CPU0:router(admin-config)# commit
Step 7
end
Example:
RP/0/RP0/CPU0:router(admin-config)# end
Step 8
Example:
Step 9
configure
Example:
RP/0/RP0/CPU0:router(admin)# configure
Step 10
Example:
RP/0/RP0/CPU0:router(admin-config)# hw-module
power disable location 0/SM0/SP
Step 11
commit
Example:
RP/0/RP0/CPU0:router(admin-config)# commit
Step 12
end
Example:
RP/0/RP0/CPU0:router(admin-config)# end
Step 13
show platform
Example:
RP/0/RP0/CPU0:router(admin)# show platform
Check the State column for the status of the fabric card.
It takes some time for the card to shut down. Repeat the
show platform command to check the card state.
Step 14
Step 15
configure
Example:
RP/0/RP0/CPU0:router(admin)# configure
8-33
Chapter 8
Step 16
Command or Action
Purpose
Example:
RP/0/RP0/CPU0:router(admin-config)# no
hw-module power disable location 0/SM0/SP
Step 17
commit
Example:
RP/0/RP0/CPU0:router(admin-config)# commit
Step 18
end
Example:
RP/0/RP0/CPU0:router(admin-config)# end
Step 19
show platform
Example:
RP/0/RP0/CPU0:router(admin)# show platform
Step 20
configure
Check the State column for the status of the fabric card.
It takes some time for the card to start up. Repeat the
show platform command to check the card state.
Example:
RP/0/RP0/CPU0:router(admin)# configure
Step 21
Example:
RP/0/RP0/CPU0:router(admin-config)# no
controllers fabric plane 0 shutdown
Step 22
commit
Example:
RP/0/RP0/CPU0:router(admin-config)# commit
Step 23
end
Example:
RP/0/RP0/CPU0:router(admin-config)# end
Step 24
Example:
RP/0/RP0/CPU0:router(admin)# show controllers
fabric plane all
8-34
The Admin State and Oper State columns should read UP.
Chapter 8
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,
C
L
A
B
I
N
o
f
m
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
WN : Plane 0 state
RP/0/RP1/CPU0:Oct
T : Administration
RP/0/RP1/CPU0:router(admin-config)# end
8-35
Chapter 8
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
8-36
Chapter 8
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
8-37
Chapter 8
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
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
8-38
Chapter 8
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 on page xiii.
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
Task:
root-system : READ
WRITE
WRITE
EXECUTE
EXECUTE
DEBUG (reserved)
DEBUG (reserved)
SUMMARY STEPS
1.
admin
2.
show platform
3.
4.
configure
5.
6.
7.
commit
8-39
Chapter 8
8.
end
9.
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
Step 1
Command or Action
Purpose
admin
Example:
RP/0/RP0/CPU0:router# admin
8-40
Chapter 8
Step 2
Command or Action
Purpose
show platform
Example:
RP/0/RP0/CPU0:router(admin)# show platform
Example:
RP/0/RP0/CPU0:router(admin)# show controllers
fabric plane all
Step 4
configure
Example:
RP/0/RP0/CPU0:router(admin)# configure
Step 5
Example:
RP/0/RP0/CPU0:router(admin-config)#
controllers fabric plane 0 shutdown
Step 6
Example:
RP/0/RP0/CPU0:router(admin-config)#
controllers fabric plane 1 shutdown
Step 7
commit
Example:
RP/0/RP0/CPU0:router(admin-config)# commit
Step 8
end
Example:
RP/0/RP0/CPU0:router(admin-config)# end
8-41
Chapter 8
Step 9
Command or Action
Purpose
Example:
Step 10
configure
Example:
RP/0/RP0/CPU0:router(admin)# configure
Step 11
Example:
RP/0/RP0/CPU0:router(admin-config)# hw-module
power disable location 0/SM0/SP
Step 12
commit
Example:
RP/0/RP0/CPU0:router(admin-config)# commit
Step 13
end
Example:
RP/0/RP0/CPU0:router(admin-config))# end
Step 14
show platform
Example:
RP/0/RP0/CPU0:router(admin)# show platform
Check the State column for the status of the fabric card.
It takes some time for the card to shut down. Repeat the
show platform command to check the card state.
Step 15
Step 16
configure
Example:
RP/0/RP0/CPU0:router(admin)# configure
Step 17
Example:
RP/0/RP0/CPU0:router(admin-config)# no
hw-module power disable location 0/SM0/SP
Step 18
commit
Example:
RP/0/RP0/CPU0:router(admin-config)# commit
8-42
Chapter 8
Step 19
Command or Action
Purpose
end
Example:
RP/0/RP0/CPU0:router(admin)# end
Step 20
show platform
Example:
RP/0/RP0/CPU0:router(admin)# show platform
Step 21
Check the State column for the status of the fabric card.
It takes some time for the card to start up. Repeat the
show platform command to check the card state.
configure
Example:
RP/0/RP0/CPU0:router(admin)# configure
Step 22
Example:
RP/0/RP0/CPU0:router(admin-config)# no
controllers fabric plane 0 shut
Step 23
Example:
RP/0/RP0/CPU0:router(admin-config)# no
controllers fabric plane 1 shut
Step 24
commit
Example:
RP/0/RP0/CPU0:router(admin-config)# commit
Step 25
end
Example:
RP/0/RP0/CPU0:router(admin-config)# end
Step 26
Example:
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
8-43
Chapter 8
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,
C
L
A
B
I
N
o
f
m
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
WN : Plane 0 state
RP/0/RP1/CPU0:Oct
WN : Plane 1 state
RP/0/RP1/CPU0:Oct
T : Administration
RP/0/RP1/CPU0:router(admin-config)# end
RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all
Flags: P
C
L
A
B
I
N
8-44
p
c
l
a
b
i
n
Chapter 8
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
8-45
Chapter 8
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
8-46
Chapter 8
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
A
B
I
N
o
f
m
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
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
Task:
root-system : READ
WRITE
WRITE
EXECUTE
EXECUTE
DEBUG (reserved)
DEBUG (reserved)
8-47
Chapter 8
SUMMARY STEPS
1.
admin
2.
show platform
3.
configure
4.
5.
6.
commit
7.
end
8.
show platform
9.
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
Step 1
Command or Action
Purpose
admin
Example:
RP/0/0/CPU0:router# admin
Step 2
show platform
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.
Example:
RP/0/0/CPU0:router(admin)# show platform
8-48
Chapter 8
Step 3
Command or Action
Purpose
configure
Example:
RP/0/0/CPU0:router(admin)# configure
Step 4
Example:
RP/0/0/CPU0:router(admin-config)# hw-module
location 0/16/CPU0 shutdown
Step 5
Caution
Example:
RP/0/0/CPU0:router(admin-config)# hw-module
location 0/16/CPU0 power disable
Step 6
commit
Example:
Note
RP/0/0/CPU0:router(admin-config)# commit
Step 7
end
Example:
RP/0/RP0/CPU0:router(admin-config)# end
Step 8
show platform
Example:
Step 9
Step 10
configure
Example:
RP/0/0/CPU0:router(admin)# configure
Step 11
Example:
RP/0/0/CPU0:router(admin-config)# no
hw-module location 0/16/CPU0 power disable
8-49
Chapter 8
Step 12
Command or Action
Purpose
commit
Example:
RP/0/0/CPU0:router(admin-config)# commit
Step 13
end
Example:
RP/0/RP0/CPU0:router(admin-config)# end
Step 14
show platform
Example:
Step 15
configure
Example:
RP/0/0/CPU0:router(admin)# configure
Step 16
Example:
RP/0/0/CPU0:router(admin-config)# no
hw-module location 0/16/CPU0 shutdown
Step 17
commit
Example:
RP/0/0/CPU0:router(admin-config)# commit
Step 18
end
Example:
RP/0/RP0/CPU0:router(admin-config)# end
Step 19
show platform
Example:
RP/0/0/CPU0:router(admin)# show platform
8-50
Chapter 8
Examples
Replacing a CSC: Example
8-51
Chapter 8
8-52
Chapter 8
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
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.
8-53
Chapter 8
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.
7.
show platform
8.
show redundancy
DETAILED STEPS
Command or Action
Purpose
Step 1
Step 2
unset TURBOBOOT
Example:
rommon># unset turboboot
Step 3
unset BOOT
Example:
rommon># unset BOOT
Step 4
sync
Example:
rommon># sync
8-54
Chapter 8
Step 5
Command or Action
Purpose
boot tftp://server/directory/filename
Example:
rommon># boot
tftp://192.168.1.1/dir/mbiprp-rp.vm
Step 6
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
Step 8
show redundancy
Example:
RP/0/0/CPU0:router# show redundancy
8-55
Chapter 8
Removing and Replacing Cards
8-56