cc/td/doc/product/core/cis12000/xr12000
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Flash Disk Upgrade Tasks

Flash Disk Graceful Upgrade Procedure

Flash Disk Upgrade Abort Procedure


Flash Disk Upgrade Tasks

The flash disk on the route processor stores Cisco IOS XR software images and the configuration information that is used to boot up the system on a Cisco XR 12000 router. The current flash disk size is 1 gigabyte (GB). A typical flash disk stores two releases (the current release and the previous release) of Cisco IOS XR system software images and software maintenance updates (SMUs).

The total flash disk storage used for Cisco IOS XR Releases 3.5 and 3.6 system software images and SMUs is nearly 1 GB. While formatting, the flash disk is partitioned into two parts:

•80 percent—The boot/config/system files are stored here.

•20 percent—Logs system-critical information.

The current available flash disk size of 1 GB is not sufficient to store Cisco IOS XR system software images of both versions and to log system critical information. For this reason, it is important to upgrade flash disk from 1 GB to 2 GB.

Note The upgrade procedure works only if the disks are not corrupt. If the disks are corrupt, we recommend that you perform a new turbo-boot using the new flash cards.

The following sections describe guidelines for resolving flash disk problems, prerequisites for upgrading, and a flash disk upgrade procedure.

Resolving Flash Disk Space Shortage

When you attempt to resolve a flash disk space shortage, use the following guidelines:

•Do not turn on the disk mirroring feature in Cisco IOS XR software Release 3.6. If the flash disk mirroring feature is not turned on, Cisco IOS XR Release 3.6 can use the full 1 GB disk space for image and configuration storage.

•If 1 GB is not enough disk space, trim down the image and remove software maintenance updates that are not currently being used to conserve flash disk space.

Prerequisites for Upgrading a Flash Disk

The prerequisites for upgrading a flash disk from 1 GB to 2 GB are as follows:

•Physical access to the router

•Console access to the Active (ACTV) and Standby (STBY) route processor

•Two new replacement flash disks; each with 2 GB space

•Phillips screw driver in case the disk cover is screwed in place

Flash Disk Graceful Upgrade Procedure

You must perform the flash disk upgrade by first upgrading the standby route processor to 2 GB, so that system production is not affected. A summary of high-level steps for an upgrade flash disk procedure follows:

1. Copy the mbi image from the active disk0 to each of the new 2 GB flashes on disk1.

2. Take the standby route processor to ROMMON.

3. Insert one of the 2 GB flashes to standby in ROMMON and boot from the copied mbi image.

4. When standby comes up and is ready, execute the redundancy switchover command.

5. Ensure that the new active and standby flash disks are up.

6. Take the new standby flash disk to ROMMON, remove the old disk0, and replace it with the second 2 GB flash disk.

7. Boot the standby from the disk0:mbi image that was copied in Step 1.

Warning Upgrading existing disk0 could result in a catastrophic state. Before upgrading the disks, you must back up all files and follow the upgrade procedure carefully.

The examples below are from console port sessions on a Cisco 12000 router running Cisco IOS XR with the active route processor installed in slot 5 and the standby route processor installed in slot 0.

Step 1 Use the show version | inc register command on the active route processor in slot 5 to record the configuration register setting of the router:

RP/0/5/CPU0:router# show version | inc register
Configuration register on node 0/0/CPU0 is 0x102
Configuration register on node 0/5/CPU0 is 0x102
RP/0/5/CPU0:router#

Note Configuration register settings may vary from customer to customer.

Step 2 In admin mode, enter the config-register command on the active route processor in slot 5 to change the configuration registers of both the active and standby route processors to 0x0:

RP/0/5/CPU0:router# admin
RP/0/5/CPU0:router(admin)# config-register 0x0
Successfully set config-register to 0x0 on node 0/0/CPU0
Successfully set config-register to 0x0 on node 0/5/CPU0
RP/0/5/CPU0:router(admin)#

Step 3 To determine the location of the mbi image in the BOOT variable, use the rommon set command on the standby route processor in slot 0:

rommon 1 > set
PS1=rommon ! >
NT_K=0:0:0:0
CONFIG_FILE=
CONFGEN=145
CHASSIS_SN=TBA09170127
SUBNET_MASK=255.255.255.0
IP_DEFAULT_GATEWAY=10.234.5.1
RET_2_RUTC=1191343331
RET_2_RTS=16:43:48 UTC Tue Oct 2 2007
RET_2_RCALTS=1191343428
BOOTLDR=bootflash:c12kprp-boot-mz.120-32.S7.bin
IOX_ADMIN_CONFIG_FILE=
TURBOBOOT=
IP_ADDRESS=10.234.5.16
?=0
BSI=0
BOOT=disk0:c12k-os-mbi-3.6.0.16I/mbiprp-rp.vm,1;
MIRROR_ENABLE=
BOOT_DEV_SEQ_CONF=
BOOT_DEV_SEQ_OPER=
ReloadReason=79
rommon 2 >

The BOOT variable indicates the location of the mbi image is located at disk0:c12k-os-mbi-3.6.0.16I/mbiprp-rp.vm. Copy this location into a file. If the old flash disk needs to be restored, you may need this location.

Step 4 Remove the flash disk from slot0: on the standby route processor in slot 0. Label this flash disk and store it in a safe place. If the old flash disk needs to be restored, you will need this flash disk.

Step 5 Insert the new replacement flash disk into slot1: of the active route processor in slot 5.

Step 6 Format the new flash disk in slot1 using the format command on the active route processor in slot 5:

RP/0/5/CPU0:router# format disk1:

Format will destroy all data on "disk1:". Continue? [confirm]

Device partition disk1: is now formated and is available for use.
RP/0/5/CPU0:router#

Step 7 Run a consistency check on the file system created on the new flash disk in slot1 by entering the run chkdosfs -n command on the active route processor in slot 5:

RP/0/5/CPU0:router# run chkdosfs -n disk1:
Phase 1 - Read and compare FATs
Phase 2 - Check cluster chains
Phase 3 - Check directories
Phase 4 - Check for lost files

96 kb used, 2049888 kb free, 0 files, 2 directories
Filesystem is clean.
RP/0/5/CPU0:router#

Note The boot media could be disk0 or disk1. This document is based on disk0 as a boot media.

Step 8 Copy the mbi image from disk0: on the active route processor in slot 5 to the new flash disk in slot1: using the location of the mbi image in Step 3 of this procedure:

RP/0/5/CPU0:router# copy disk0:c12k-os-mbi-3.6.0.16I/mbiprp-rp.vm disk1:
Destination filename [/disk1:/mbiprp-rp.vm]?
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCC
10298984 bytes copied in 16 sec ( 633744)bytes/sec
RP/0/5/CPU0:router#

To verify that the mbi image is on the new flash disk in slot1, use the dir command on the active route processor in slot 5:

RP/0/5/CPU0:router# dir disk1:

Directory of disk1:

2 drwx 32768 Tue Oct 23 00:56:29 2007 LOST.DIR
65632 -rwx 10298984 Tue Oct 23 00:54:48 2007 mbiprp-rp.vm

2099118080 bytes total (2088763392 bytes free)
RP/0/5/CPU0:router#

Step 9 Remove the new flash disk from slot1: on the active route processor in slot 5 and insert it into slot0: on the standby route processor in slot 0.

Step 10 Insert the second new replacement flash disk into slot1: of the active route processor in slot 5.

Step 11 To format the second new flash disk in slot1, use the format command on the active route processor in slot 5:

RP/0/5/CPU0:router# format disk1:

Format will destroy all data on "disk1:". Continue? [confirm]

Device partition disk1: is now formatted and is available for use.
RP/0/5/CPU0:router#

Step 12 Run a consistency check on the file system created on the second new flash disk in slot1 by entering the run chkdosfs -n command on the active route processor in slot 5:

RP/0/5/CPU0:router# run chkdosfs -n disk1:
Phase 1 - Read and compare FATs
Phase 2 - Check cluster chains
Phase 3 - Check directories
Phase 4 - Check for lost files

96 kb used, 2049888 kb free, 0 files, 2 directories
Filesystem is clean.
RP/0/5/CPU0:router#

Step 13 Copy the mbi image from disk0: on the active route processor in slot 5 to the second new flash disk in slot1: using the location of the mbi image in Step 3 of this procedure:

RP/0/5/CPU0:router# copy disk0:c12k-os-mbi-3.6.0.16I/mbiprp-rp.vm disk1:
Destination filename [/disk1:/mbiprp-rp.vm]?
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCC
10298984 bytes copied in 16 sec ( 633744)bytes/sec
RP/0/5/CPU0:router#

Verify that the mbi image is on the second new flash disk in slot1 using the dir command on the active route processor in slot 5:

RP/0/5/CPU0:router# dir disk1:

Directory of disk1:

2 drwx 32768 Tue Oct 23 00:56:29 2007 LOST.DIR
65632 -rwx 10298984 Tue Oct 23 00:54:48 2007 mbiprp-rp.vm

2099118080 bytes total (2088763392 bytes free)
RP/0/5/CPU0:router#

Step 14 Bring the standby route processor in slot 0 to rommon mode using the reload location command in admin mode on the active route processor in slot 5:

RP/0/5/CPU0:router(admin)# reload location 0/0/CPU0
Preparing system for backup. This may take a few minutes [done]
Proceed with reload? [confirm]

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

Verify that the standby route processor in slot 0 is in rommon mode using the show platform command on the active route processor in slot 5:

RP/0/5/CPU0:router(admin)# show platform
Node Type PLIM State Config State
-----------------------------------------------------------------------------
0/0/CPU0 PRP N/A Card Present PWR,NSHUT,MON
0/2/CPU0 L3LC Eng 5+ Jacket Card IOS XR RUN PWR,NSHUT,MON
0/2/3 SPA SPA-8XCHT1/E1 READY PWR,NSHUT
0/3/CPU0 L3LC Eng 5 Jacket Card IOS XR RUN PWR,NSHUT,MON
0/3/0 SPA SPA-5X1GE-V2 READY PWR,NSHUT
0/5/CPU0 PRP(Active) N/A IOS XR RUN PWR,NSHUT,MON
0/16/CPU0 CSC6(P) N/A PWD PWR,NSHUT,MON
0/18/CPU0 SFC6 N/A PWD PWR,NSHUT,MON
0/19/CPU0 SFC6 N/A PWD PWR,NSHUT,MON
0/20/CPU0 SFC6 N/A PWD PWR,NSHUT,MON
0/24/CPU0 ALARM6 N/A PWD PWR,NSHUT,MON
0/25/CPU0 ALARM6 N/A PWD PWR,NSHUT,MON
0/28/CPU0 GSR6-BLOWER N/A PWD PWR,NSHUT,MON
RP/0/5/CPU0:router(admin)#

Step 15 Locate the mbi image on the new flash disk in slot0 using the rommon dir command on the standby route processor in slot 0:

rommon 1 > dir disk0:
File size Perms File name
0 drw- LOST.DIR
10298984 -rw- mbiprp-rp.vm
rommon 2 >

Step 16 Boot the mbi image on the new flash disk in slot0 by using the rommon boot command on the standby route processor in slot 0:

rommon 2 > boot disk0:mbiprp-rp.vm

Wait for the standby route processor in slot 0 to install all Cisco IOS XR software, sync up with the active route processor in slot 5, and become ready.

Note The standby route processor may take 1+ hour to become ready, depending upon the size of the configuration and routing table.

Step 17 Determine if the standby route processor in slot 0 is in the ready state using the show redundancy command on the active route processor in slot 5:

The following example shows the standby route processor in slot 0 is not ready:

RP/0/5/CPU0:router# show redundancy
Redundancy information for node 0/5/CPU0:
==========================================
Node 0/5/CPU0 is in ACTIVE role
Node 0/5/CPU0 has no valid partner

Reload and boot info
----------------------
PRP reloaded Fri Oct 12 19:24:14 2007: 1 week, 3 days, 6 hours, 25 minutes ago
Active node booted Fri Oct 12 19:24:14 2007: 1 week, 3 days, 6 hours, 25 minutes ago
Standby node lost Tue Oct 23 00:19:12 2007: 1 hour, 30 minutes ago

RP/0/5/CPU0:router#

The following example shows the standby route processor in slot 0 is ready:

RP/0/5/CPU0:router# show redundancy
Redundancy information for node 0/5/CPU0:
==========================================
Node 0/5/CPU0 is in ACTIVE role
Partner node (0/0/CPU0) is in STANDBY role
Standby node in 0/0/CPU0 is ready
Standby node in 0/0/CPU0 is NSR-ready

Reload and boot info
----------------------
PRP reloaded Fri Oct 12 19:24:14 2007: 1 week, 3 days, 6 hours, 36 minutes ago
Active node booted Fri Oct 12 19:24:14 2007: 1 week, 3 days, 6 hours, 36 minutes ago
Standby node boot Tue Oct 23 01:54:55 2007: 5 minutes ago
Standby node last went not ready Tue Oct 23 02:00:01 2007: 27 seconds ago
Standby node last went ready Tue Oct 23 02:00:01 2007: 27 seconds ago
Standby node last went not NSR-ready Tue Oct 23 02:00:01 2007: 27 seconds ago
Standby node last went NSR-ready Tue Oct 23 02:00:01 2007: 27 seconds ago
There have been 0 switch-overs since reload

RP/0/5/CPU0:router#

Note After the standby route processor enters the ready state, go to the next step in this procedure. If the standby route processor does not enter the ready state, use the "Flash Disk Upgrade Abort Procedure" section to restore the old standby flash disk.

Step 18 After the standby route processor in slot 0 is in the ready state, enter the config-register command in admin mode on the active route processor in slot 5 to change the configuration register of the standby route processor in slot 0 to the value recorded in Step 1 of this procedure:

RP/0/5/CPU0:router(admin)# config-register 0x102 location 0/0/CPU0
Successfully set config-register to 0x102 on node 0/0/CPU0
RP/0/5/CPU0:router(admin)#

Step 19 Reset the standby route processor in slot 0 to become the new active route processor using the redundancy switchover command on the active route processor in slot 5:

RP/0/5/CPU0:router# redundancy switchover
Proceed with switchover 0/5/CPU0 -> 0/0/CPU0? [confirm]
Initiating switch-over.

The route processor in slot 5 is now the new standby route processor and is in rommon mode. Verify that the standby route processor in slot 5 is in rommon mode using the show platform command on the new active route processor in slot 0:

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/2/CPU0 L3LC Eng 5+ Jacket Card IOS XR RUN PWR,NSHUT,MON
0/2/3 SPA SPA-8XCHT1/E1 READY PWR,NSHUT
0/3/CPU0 L3LC Eng 5 Jacket Card IOS XR RUN PWR,NSHUT,MON
0/3/0 SPA SPA-5X1GE-V2 READY PWR,NSHUT
0/5/CPU0 PRP N/A Card Present PWR,NSHUT,MON
0/16/CPU0 CSC6(P) N/A PWD PWR,NSHUT,MON
0/18/CPU0 SFC6 N/A PWD PWR,NSHUT,MON
0/19/CPU0 SFC6 N/A PWD PWR,NSHUT,MON
0/20/CPU0 SFC6 N/A PWD PWR,NSHUT,MON
0/24/CPU0 ALARM6 N/A PWD PWR,NSHUT,MON
0/25/CPU0 ALARM6 N/A PWD PWR,NSHUT,MON
0/28/CPU0 GSR6-BLOWER N/A PWD PWR,NSHUT,MON
RP/0/0/CPU0:router(admin)#

Step 20 Remove the flash disk from slot0: on the standby route processor in slot 5. Label this flash disk and store it in a safe place. If the old flash disk needs to be restored, you will need this flash disk.

Step 21 Remove the second, new replacement flash disk from slot1: on the standby route processor in slot 5 and insert it into slot0: of the standby route processor in slot 5.

Step 22 Locate the mbi image on the second, new flash disk in slot0 using the rommon dir command on the standby route processor in slot 5:

rommon 1 > dir disk0:
File size Perms File name
0 drw- LOST.DIR
10298984 -rw- mbiprp-rp.vm
rommon 2 >

Step 23 Boot the mbi image on the second new flash disk in slot0 by using the rommon boot command on the standby route processor in slot 5:

rommon 2 > boot disk0:mbiprp-rp.vm

Wait for the standby route processor in slot 5 to install all Cisco IOS XR software, sync up with the active route processor in slot 0, and become ready.

Note The standby route processor may take 1+ hour to become ready, depending upon the size of the configuration and routing table.

Step 24 Determine if the standby route processor in slot 5 is in the ready state using the show redundancy command on the active route processor in slot 0. This example shows that the standby route processor in slot 5 is not ready:

RP/0/0/CPU0:router# show redundancy
Redundancy information for node 0/0/CPU0:
==========================================
Node 0/0/CPU0 is in ACTIVE role
Node 0/0/CPU0 has no valid partner

Reload and boot info
----------------------
PRP reloaded Fri Oct 12 19:24:14 2007: 1 week, 3 days, 9 hours, 13 minutes ago
Active node booted Tue Oct 23 01:54:55 2007: 2 hours, 42 minutes ago
Last switch-over Tue Oct 23 03:21:15 2007: 1 hour, 16 minutes ago

RP/0/0/CPU0:router#

This example shows that the standby route processor in slot 5 is ready:

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/5/CPU0) is in STANDBY role
Standby node in 0/5/CPU0 is ready
Standby node in 0/5/CPU0 is NSR-ready
Reload and boot info
----------------------
PRP reloaded Fri Oct 12 19:24:14 2007: 1 week, 3 days, 9 hours, 30 minutes ago
Active node booted Tue Oct 23 01:54:55 2007: 2 hours, 59 minutes ago
Last switch-over Tue Oct 23 03:21:15 2007: 1 hour, 33 minutes ago
Standby node boot Tue Oct 23 04:50:20 2007: 4 minutes ago
Standby node last went not ready Tue Oct 23 04:54:05 2007: 32 seconds ago
Standby node last went ready Tue Oct 23 04:54:05 2007: 32 seconds ago
Standby node last went not NSR-ready Tue Oct 23 04:54:05 2007: 32 seconds ago
Standby node last went NSR-ready Tue Oct 23 04:54:05 2007: 32 seconds ago
There has been 1 switch-over since reload

RP/0/0/CPU0:router#

Step 25 After the standby route processor in slot 5 enters the ready state, enter the config-register command in admin mode on the active route processor in slot 0. This changes the configuration register of both the active route processor in slot 0 and the standby route processor in slot 5 to the value recorded in Step 1 of this procedure:

RP/0/0/CPU0:router(admin)# config-register 0x102 location all
Successfully set config-register to 0x102 on node 0/0/CPU0
Successfully set config-register to 0x102 on node 0/5/CPU0
RP/0/0/CPU0:router(admin)#

Step 26 Verify the status of both RPs by entering the show platform command from the active route processor in slot 0:

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/2/CPU0 L3LC Eng 5+ Jacket Card IOS XR RUN PWR,NSHUT,MON
0/2/3 SPA SPA-8XCHT1/E1 READY PWR,NSHUT
0/3/CPU0 L3LC Eng 5 Jacket Card IOS XR RUN PWR,NSHUT,MON
0/3/0 SPA SPA-5X1GE-V2 READY PWR,NSHUT
0/5/CPU0 PRP(Standby) N/A IOS XR RUN PWR,NSHUT,MON
0/16/CPU0 CSC6(P) N/A PWD PWR,NSHUT,MON
0/18/CPU0 SFC6 N/A PWD PWR,NSHUT,MON
0/19/CPU0 SFC6 N/A PWD PWR,NSHUT,MON
0/20/CPU0 SFC6 N/A PWD PWR,NSHUT,MON
0/24/CPU0 ALARM6 N/A PWD PWR,NSHUT,MON
0/25/CPU0 ALARM6 N/A PWD PWR,NSHUT,MON
0/28/CPU0 GSR6-BLOWER N/A PWD PWR,NSHUT,MON
RP/0/0/CPU0:router(admin)#

Both route processors should be in the IOS XR RUN state and the active and standby route processor roles should be reversed. Optionally, if the route processor in slot 5 is the preferred active route processor, enter the redundancy switchover command on the active route processor in slot 0 to reverse the current roles to the original route processor redundancy configuration.

Flash Disk Upgrade Abort Procedure

If the standby route processor in slot 0 fails to come up to a ready state as shown the "Flash Disk Graceful Upgrade Procedure" section, Step 17, and it is necessary to restore the old flash disk, use this procedure.

The examples in this procedure are from console port sessions on a Cisco 12000 router running Cisco IOS XR software with the active route processor installed in slot 5 and the standby route processor installed in slot 0.

Step 1 To change the configuration register of the standby route processor in slot 0 to the value of 0x0, enter the config-register command in admin mode on the active route processor in slot 5:

RP/0/5/CPU0:router(admin)# config-register 0x0 location 0/0/CPU0
Successfully set config-register to 0x0 on node 0/0/CPU0
RP/0/5/CPU0:router(admin)#

Step 2 Bring the standby route processor in slot 0 to rommon mode using the reload location command in admin mode on the active route processor in slot 5:

RP/0/5/CPU0:router(admin)# reload location 0/0/CPU0
Preparing system for backup. This may take a few minutes [done]
Proceed with reload? [confirm]

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

Verify that the standby route processor in slot 0 is in rommon mode using the show platform command on the active route processor in slot 5:

RP/0/5/CPU0:router(admin)# show platform
Node Type PLIM State Config State
-----------------------------------------------------------------------------
0/0/CPU0 PRP N/A Card Present PWR,NSHUT,MON
0/2/CPU0 L3LC Eng 5+ Jacket Card IOS XR RUN PWR,NSHUT,MON
0/2/3 SPA SPA-8XCHT1/E1 READY PWR,NSHUT
0/3/CPU0 L3LC Eng 5 Jacket Card IOS XR RUN PWR,NSHUT,MON
0/3/0 SPA SPA-5X1GE-V2 READY PWR,NSHUT
0/5/CPU0 PRP(Active) N/A IOS XR RUN PWR,NSHUT,MON
0/16/CPU0 CSC6(P) N/A PWD PWR,NSHUT,MON
0/18/CPU0 SFC6 N/A PWD PWR,NSHUT,MON
0/19/CPU0 SFC6 N/A PWD PWR,NSHUT,MON
0/20/CPU0 SFC6 N/A PWD PWR,NSHUT,MON
0/24/CPU0 ALARM6 N/A PWD PWR,NSHUT,MON
0/25/CPU0 ALARM6 N/A PWD PWR,NSHUT,MON
0/28/CPU0 GSR6-BLOWER N/A PWD PWR,NSHUT,MON
RP/0/5/CPU0:router(admin)#

Step 3 Replace the new flash disk in slot0: with the old flash disk on the standby route processor in slot 0.

Step 4 Boot the mbi image located on the old flash disk in slot0: using the rommon boot command on the standby route processor in slot 0. Use the BOOT variable from "Flash Disk Graceful Upgrade Procedure" section, Step 4:

rommon 2 > boot disk0:c12k-os-mbi-3.6.0.16I/mbiprp-rp.vm

Wait for the standby route processor in slot 0 to sync up with the active route processor in slot 5 and become ready.

Step 5 Determine if the standby route processor in slot 0 is in the ready state using the show redundancy command on the active route processor in slot 5. This example shows the standby route processor in slot 0 is not ready:

RP/0/5/CPU0:router(admin)# show redundancy
Redundancy information for node 0/5/CPU0:
==========================================
Node 0/5/CPU0 is in ACTIVE role
Partner node (0/0/CPU0) is in STANDBY role
Standby node in 0/0/CPU0 is not ready
Standby node in 0/0/CPU0 is NSR-ready

Details
--------
Current active redcon state: 4 (I_READY)
<jid> <node> <name> Reason for standby not ready
413 0/0/CPU0 vi_config_replicator VICR copying Virtual Interface config to standby
Not ready set Tue Oct 23 06:28:24 2007: 12 seconds ago
87 0/0/CPU0 sysmgr Software activation in progress
Not ready set Tue Oct 23 06:25:11 2007: 3 minutes ago

Current active redcon state for NSR: Ready
All not-ready NSR bits clear - standby should be NSR-ready

Reload and boot info
----------------------
PRP reloaded Fri Oct 12 19:24:14 2007: 1 week, 3 days, 11 hours, 4 minutes ago
Active node booted Tue Oct 23 04:49:07 2007: 1 hour, 39 minutes ago
Last switch-over Tue Oct 23 05:53:08 2007: 35 minutes ago
Standby node boot Tue Oct 23 06:24:00 2007: 4 minutes ago
Standby node last went not ready Tue Oct 23 06:25:08 2007: 3 minutes ago
Standby node last went ready Tue Oct 23 05:58:31 2007: 30 minutes ago
Standby node last went not NSR-ready Tue Oct 23 05:58:30 2007: 30 minutes ago
Standby node last went NSR-ready Tue Oct 23 05:58:30 2007: 30 minutes ago
There have been 2 switch-overs since reload

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

This example shows the standby route processor in slot 0 is ready:

RP/0/5/CPU0:router(admin)# show redundancy
Redundancy information for node 0/5/CPU0:
==========================================
Node 0/5/CPU0 is in ACTIVE role
Partner node (0/0/CPU0) is in STANDBY role
Standby node in 0/0/CPU0 is ready
Standby node in 0/0/CPU0 is NSR-ready

Reload and boot info
----------------------
PRP reloaded Fri Oct 12 19:24:14 2007: 1 week, 3 days, 11 hours, 6 minutes ago
Active node booted Tue Oct 23 04:49:07 2007: 1 hour, 41 minutes ago
Last switch-over Tue Oct 23 05:53:08 2007: 37 minutes ago
Standby node boot Tue Oct 23 06:24:00 2007: 7 minutes ago
Standby node last went not ready Tue Oct 23 06:29:22 2007: 1 minute ago
Standby node last went ready Tue Oct 23 06:29:22 2007: 1 minute ago
Standby node last went not NSR-ready Tue Oct 23 06:29:29 2007: 1 minute ago
Standby node last went NSR-ready Tue Oct 23 06:29:29 2007: 1 minute ago
There have been 2 switch-overs since reload

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

Step 6 After the standby route processor in slot 0 enters the ready state, enter the config-register command in admin mode on the active route processor in slot 5. This changes the configuration register of the standby route processor in slot 0 to the value recorded in the "Flash Disk Graceful Upgrade Procedure" section, Step 1:

RP/0/5/CPU0:router(admin)# config-register 0x102 location 0/0/CPU0
Successfully set config-register to 0x102 on node 0/0/CPU0
RP/0/5/CPU0:router(admin)#

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2007 Cisco Systems, Inc. All rights reserved

hometocprevnextglossaryfeedbacksearchhelp

Posted: Thu Dec 20 02:30:27 PST 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.