6
Upgrading to Cisco IOS Release 12.2(28)SB on a Cisco 10000 Series Router
OL-8833-01
Upgrade Option 3: ESR-PRE1 Upgrade with RPR Switchover
To perform the upgrade, follow these steps:
Step 1 On the active ESR-PRE1, issue the write memory command to make sure the startup configuration is
up to date. Save the startup configuration to a TFTP server in case you need to roll back to the previous
version.
Step 2 Remove the standby ESR-PRE1 and insert an ESR-PRE2 into the empty slot.
If the config register on the new ESR-PRE2 is set to 0x2, it will autoboot the eboot image bootflash.
Type no at the ---System Configuration Dialog--- prompt.
If the config register on the new ESR-PRE2 is set to 0x0, it will come up in ROM monitor. Boot the eboot
image from ROM monitor using the boot command. Type no at the ---System Configuration Dialog---
prompt.
Step 3 Access the ESR-PRE2 through the console port and configure the FastEthernet 0/0/0 interface and
gateway IP address the same as they were on the ESR-PRE1 to enable communication with the TFTP
server. Make sure the ESR-PRE2 can ping the TFTP server.
Step 4 From the ESR-PRE2 console, copy the 12.2(28)SB image from the TFTP server to the bootflash using
the copy tftp bootflash:image_name command.
Step 5 From the newly installed ESR-PRE2 console, use the dir bootflash command to verify that the
12.2(28)SB image is in the bootflash. Configure the ESR-PRE2 to autoboot using the boot system
bootflash:image_name and config-register 0x2 commands. Save the configuration using the write
memory command.
Step 6 Copy the ESR-PRE1 startup configuration to the TFTP server and edit the configuration to reflect the
new capabilities of the 12.2(28)SB software. At a minimum, you must configure the ESR-PRE2 to
autoboot using the boot system bootflash:image_name (as in Step 5).
Step 7 Copy the edited startup configuration to the ESR-PRE2 using the copy tftp startup command. Your
startup configuration and boot variable should now be correct. Verify the boot variable using the show
bootvar command.
Step 8 From the ESR-PRE2 console, use the reload command to boot the new ESR-PRE2 image. Wait until the
ESR-PRE2 comes up as standby. At this point the ESR-PRE2 is in cold standby RPR state, and the
console is disabled. The console displays the message
Standby operating in RPR mode, console
disabled
.
Step 9 From the active ESR-PRE1 console, verify that the ESR-PRE1 can communicate with ESR-PRE2 using
the following two commands:
dir stby-bootflash (to verify that the correct image name is present)
show redundancy
The show redundancy command output should include the following information:
• Operating Redundancy Mode: RPR
• State of standby ESR-PRE2: Standby Cold
The command output will also include the message
Communications = Down Reason: Failure. You
can ignore this message; it indicates that some of the inter-PRE communications are disabled to prevent
incompatibilities.
Step 10 From the ESR-PRE1 console in privileged EXEC mode, enter the redundancy force-switchover
main-cpu command. Wait for the ESR-PRE2 to complete its boot sequence, including processing the
startup configurations it has been set to use. The ESR-PRE2 will become the active PRE.
Step 11 As the ESR-PRE2 becomes active, all traffic should resume shortly. Verify that the state of the
ESR-PRE1 is one of the following:
To Next Page
Loading...
