|
|
This document describes how to upgrade the software images on the Cisco 6400 universal access concentrator (UAC) and contains the following sections:
For general information on Cisco IOS software, see the "Cisco IOS File Management" chapter of the Cisco IOS Configuration Fundamentals Configuration Guide for your software release level.
Cisco highly recommends that all images used on your Cisco 6400 system have the same version level, specifically:
This section describes how to upgrade software on an NRP that is not configured for redundancy. To upgrade software on redundant NRPs, see the "Upgrading Software on Redundant NRPs" section.
To upgrade the software images on the NRP, complete the following steps:
Router# dir flash: Router# dir bootflash:
Step 2 Use the copy EXEC command to backup the system and boothelper images to a TFTP server.
Router# copy flash:c6400r-g4p5-mz.120-7.DC tftp://10.1.1.1/c6400r-g4p5-mz.120-7.DC Router# copy bootflash:c6400r-boot-mz.120-7.DC tftp://10.1.1.1/c6400r-boot-mz.120-7.DC
Step 3 Use the delete EXEC command to mark the old images for deletion.
Router# delete flash:c6400r-g4p5-mz.120-7.DC Router# delete bootflash:c6400r-boot-mz.120-7.DC
Step 4 Use the squeeze EXEC command to permanently delete the images marked for deletion.
Router# squeeze flash: Router# squeeze bootflash:
Step 5 Use the copy EXEC command to load the new images.
Router# copy tftp://10.1.1.1/c6400r-g4p5-mz.121-1.DC1 flash:c6400r-g4p5-mz.121-1.DC1 Router# copy tftp://10.1.1.1/c6400r-boot-mz.121-1.DC1 bootflash:c6400r-boot-mz.121-1.DC1
Step 6 Use the no boot system global configuration command to remove the old startup image configuration.
Router(config)# no boot system flash:c6400r-g4p5-mz.120-7.DC
Step 7 Use the boot system global configuration command to add the new startup image configuration.
Router(config)# boot system flash:c6400r-g4p5-mz.121-1.DC1
Step 8 Use the config-register global configuration command to do one of the following:
a. Set the config register to 0x2 for automatic boot.
Router(config)# config-register 0x2
b. Set the config register to 0x0 to boot manually from the ROMMON prompt.
Router(config)# config-register 0x0
Step 9 Use the copy system:running-config nvram:startup-config EXEC command to save the running configuration.
Router# copy system:running-config nvram:startup-config
Step 10 Use the reload EXEC command to reload the NRP. This will automatically reboot the NRP if you set the config register to 0x2 in Step 8.
Router# reload
Step 11 If you set the config register to 0x0 in Step 8, you will see the rommon prompt after completion of the NRP reload. Complete the following steps to manually boot the NRP and set it up for automatic reboot.
a. Use the dir command to locate and identify the new image.
rommon 1 > dir flash:
b. Use the boot command to manually boot the NRP.
rommon 2 > boot flash:c6400r-g4p5-mz.121-1.DC1
In the following example, the NRP system image is upgraded from Cisco IOS Release 12.0(7) DC to Cisco IOS Release 12.1(1) DC1:
Router# dir flash: Directory of flash:/ 1 -rw- 94074 Jul 26 2000 17:11:46 lns.cfg 2 -rw- 96278 Jul 26 2000 17:14:46 ip_route.cfg 3 -rw- 190480 Jul 27 2000 10:14:08 work.cfg 4 -rw- 5018040 Aug 08 2000 15:23:34 c6400r-g4p5-mz.120-7.DC 15990784 bytes total (10591396 bytes free) Router# ping 10.2.16.99 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.2.16.99, timeout is 2 seconds: .!!!! Success rate is 80 percent (4/5), round-trip min/avg/max = 1/2/4 ms Router# delete flash:c6400r-g4p5-mz.120-7.DC Delete filename [c6400r-g4p5-mz.120-7.DC]? Delete flash:c6400r-g4p5-mz.120-7.DC? [confirm] Router# squeeze flash: All deleted files will be removed. Continue? [confirm] Squeeze operation may take a while. Continue? [confirm] Squeezing...Erasing squeeze bufferWriting squeeze bufferErasing sector:2 Writing sector:2Erasing squeeze log Squeeze of flash complete Router# copy tftp:flash: Address or name of remote host []? 10.2.16.99 Source filename []? c6400r-g4p5-mz.121-1.DC1 Destination filename [c6400r-g4p5-mz.121-1.DC1]? Accessing tftp://10.2.16.99/c6400r-g4p5-mz.121-1.DC1... Loading c6400r-g4p5-mz.121-1.DC1 from 10.2.16.99 (via Ethernet0/0/1):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [snip]
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!! [OK - 5215272/10430464 bytes] 5215272 bytes copied in 87.740 secs (59945 bytes/sec) Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# no boot system flash c6400r-g4p5-mz.120-7.DC Router(config)# boot system flash c6400r-g4p5-mz.121-1.DC1 Router(config)# config-register 0x2 Router(config)# end Router# copy system:running-config nvram:startup-config 00:03:03:%SYS-5-CONFIG_I:Configured from console by console mem Warning:Attempting to overwrite an NVRAM configuration previously written by a different version of the system image. Overwrite the previous NVRAM configuration?[confirm] Building configuration... [OK] Router# reload Proceed with reload? [confirm] 00:03:16:%SYS-5-RELOAD:Reload requested System Bootstrap, Version 11.3(5)DB2, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) Copyright (c) 1998 by cisco Systems, Inc. Reset Reason Register = REASON_WARM (0x2) C6400R platform with 131072 Kbytes of main memory Self decompressing the image [snip] Press RETURN to get started!
This section describes how to upgrade software on an NSP that is not configured for redundancy. To upgrade software on redundant NSPs, see the "Upgrading Software on Redundant NSPs" section.
To upgrade the software images on the NSP, complete the following steps:
Switch# dir disk0: Switch# dir disk1: Switch# dir bootflash:
Step 2 Use the copy EXEC command to backup the images to a TFTP server.
Switch# copy disk0:c6400s-wp-mz.120-7.DB tftp://10.1.1.1/c6400s-wp-mz.120-7.DB Switch# copy disk0:c6400s-html.tar.120-5.DB tftp://10.1.1.1/c6400s-html.tar.120-5.DB Switch# copy bootflash:c6400s-wp-mz.120-5.DB tftp://10.1.1.1/c6400s-wp-mz.120-5.DB
Step 3 Use the delete EXEC command to mark the old images for deletion.
Switch# delete disk0:c6400s-wp-mz.120-7.DB Switch# delete disk0:c6400s-html.tar.120-5.DB Switch# delete bootflash:c6400s-wp-mz.120-5.DB
Step 4 Use the copy EXEC command to load the new images.
Switch# copy tftp://10.1.1.1/c6400s-wp-mz.DB1 disk0:c6400s-wp-mz.DB1 Switch# copy tftp://10.1.1.1/c6400s-html.tar.DB1 disk0:c6400s-html.tar.DB1 Switch# copy tftp://10.1.1.1/c6400s-wp-mz.DB1 bootflash:c6400s-wp-mz.DB1
Step 5 Use the no boot system global configuration command to remove the old startup image configuration.
Switch(config)# no boot system flash:c6400s-wp-mz.120-7.DB
Step 6 Use the boot system global configuration command to add the new startup image configuration.
Switch(config)# boot system flash:c6400s-wp-mz.DB1
Step 7 Use the config-register global configuration command to do one of the following:
a. Set the config register to 0x2 for automatic boot.
Switch(config)# config-register 0x2
b. Set the config register to 0x0 to boot manually from the ROMMON prompt.
Switch(config)# config-register 0x0
Step 8 Use the copy EXEC command to save the running configuration as the startup configuration.
Switch# copy system:running-config nvram:startup-config
Step 9 Use the reload EXEC command to reload the NSP. This will automatically reboot the NSP if you set the config register to 0x2 in Step 7.
Switch# reload
Step 10 If you set the config register to 0x0 in Step 7, you will see the rommon prompt after completion of the NSP reload. Complete the following steps to manually boot the NSP and set it up for automatic reboot:
a. Use the dir command to locate and identify the new image.
rommon 1 > dir flash:
b. Use the boot command to manually boot the NRP.
rommon 2 > boot flash:c6400s-wp-mz.DB1
In the following example, the NSP image is upgraded from Cisco IOS Release 12.0(7) DB to Cisco IOS Release 12.1(1) DB1:
nsp# ping 10.1.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms nsp# dir disk0: Directory of disk0:/ 2222 -rw- 1944 Jul 27 2000 09:41:45 pvp-config 2254 -rw- 91833 Jul 27 2000 10:24:47 running-config 2277 -rw- 91833 Jul 27 2000 10:25:19 pvc-config 2223 -rw- 4504276 Aug 03 2000 09:44:01 c6400s-wp-mz.120-7.DB
20819968 bytes total (16121856 bytes free) nsp# show version Cisco Internetwork Operating System Software IOS (tm) C6400 Software (C6400S-WP-M), Version 12.0(7)DB, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) TAC:Home:SW:IOS:Specials for info Copyright (c) 1986-2000 by cisco Systems, Inc. Compiled Wed 22-Mar-00 11:47 by beliu Image text-base:0x60010908, data-base:0x6081E000 ROM:System Bootstrap, Version 12.0(1)DB [gmgreen-fcs 102], RELEASE SOFTWARE ROM:C6400 Software (C6400S-WP-M), Version 12.0(7)DB, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) nsp uptime is 2 minutes System returned to ROM by reload System image file is "disk0:c6400s-wp-mz.120-7.DB" cisco C6400S (R4600) processor with 131072K bytes of memory. R4700 CPU at 100Mhz, Implementation 33, Rev 1.0 Last reset from s/w peripheral Bridging software. 2 Ethernet/IEEE 802.3 interface(s) 8 ATM network interface(s) 507K bytes of non-volatile configuration memory. --More-- 20480K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes). 8192K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x0 2254 -rw- 91833 Jul 27 2000 10:24:47 running-config 2277 -rw- 91833 Jul 27 2000 10:25:19 pvc-config 2223 -rw- 4504276 Aug 03 2000 09:44:01 c6400s-wp-mz.120-7.DB 20819968 bytes total (16121856 bytes free) nsp# copy tftp:disk0: Address or name of remote host []? 10.1.1.1 Source filename []? c6400s-wp-mz.DB1 Accessing tftp://10.1.1.1/c6400s-wp-mz.DB1... Loading c6400s-wp-mz.121-1.DB1 from 10.1.1.1 (via BVI1):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [snip] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!! [OK - 4575296/9150464 bytes] 4575296 bytes copied in 141.700 secs (32448 bytes/sec) nsp# configure terminal Enter configuration commands, one per line. End with CNTL/Z. nsp(config)# no boot system disk0:c6400s-wp-mz.120-7.DB nsp(config)# boot system disk0:c6400s-wp-mz.121-1.DB1 nsp(config)# config-register 0x2 nsp(config)# end nsp# copy system:running-config nvram:startup-config Building configuration... [OK] nsp# reload Proceed with reload? [confirm]
This section describes how to upgrade software on redundant NRPs. To upgrade software on a nonredundant NRP, see the "Upgrading Software on Nonredundant NRPs" section.
To upgrade the software images on redundant NRPs, perform the following tasks in the specified order. Each task in the list identifies the device used to perform the task:
1. Upgrade the Images on the Secondary NRP (primary NRP)
2. Identify the New System Image as the Startup Image for the Secondary NRP (primary NRP)
3. Reload the Secondary NRP (NSP)
4. Upgrade the Images on the Primary NRP (primary NRP)
5. Identify the New System Image as the Startup Image for the Primary NRP (primary NRP)
In the following instructions and examples, NRP-1 is the device in slot 1 of the Cisco 6400 chassis, and NRP-2 is the device in slot 2.
Complete the following steps from the primary NRP to upgrade the secondary NRP images. NRP1 in slot 1 is currently the primary device, and NRP2 in slot 2 is currently the secondary device.
NRP1# dir sec-flash: NRP1# dir sec-bootflash:
Step 2 Use the copy EXEC command to backup the secondary NRP's system and boothelper images to a TFTP server.
NRP1# copy sec-flash:c6400r-g4p5-mz.120-7.DC tftp://10.1.1.1/c6400r-g4p5-mz.120-7.DC NRP1# copy sec-bootflash:c6400r-boot-mz.120-7.DC tftp://10.1.1.1/c6400r-boot-mz.120-7.DC
Step 3 Use the delete EXEC command to mark the secondary NRP's old images for deletion.
NRP1# delete sec-flash:c6400r-g4p5-mz.120-7.DC NRP1# delete sec-bootflash:c6400r-boot-mz.120-7.DC
Step 4 Use the squeeze EXEC command to permanently delete the secondary NRP's images marked for deletion.
NRP1# squeeze sec-flash: NRP1# squeeze sec-bootflash:
Step 5 Use the copy EXEC command to load the new images to the secondary NRP.
NRP1#copy tftp://10.1.1.1/c6400r-g4p5-mz.121-1.DC1 sec-flash:c6400r-g4p5-mz.121-1.DC1 NRP1#copy tftp://10.1.1.1/c6400r-boot-mz.121-1.DC1 sec-bootflash:c6400r-boot-mz.121-1.DC1
To ensure that the new image is used upon system reload, choose one of the following methods:
Complete the following steps to make sure that the new image is the first file on the secondary NRP Flash disk. NRP1 in slot 1 is still the primary device, and NRP2 in slot 2 is still the secondary device.
NRP1# dir sec-flash:
Step 2 If the new system image is the first file listed, the image is already the startup image. Continue with the "Reload the Secondary NRP" section.
If the new system image is not at the top of the list, and you want save the files that are listed above the new image, continue with Step 3.
If you want to delete the files listed above the new image, continue with Step 4.
Step 3 Use the copy EXEC command to backup the secondary NRP Flash files to a TFTP server.
NRP1# copy sec-flash:filename tftp://10.1.1.1/filename1 NRP1# copy sec-flash:filename tftp://10.1.1.1/filename2 NRP1# copy sec-flash:filename tftp://10.1.1.1/filename3 ...
Step 4 Use the delete EXEC command to mark the unwanted secondary NRP files for deletion.
NRP1# delete sec-flash:filenames
Step 5 Use the squeeze EXEC command to permanently delete the secondary NRP images that are marked for deletion.
NRP1# squeeze sec-flash: NRP1# squeeze sec-bootflash:
Step 6 If you performed Step 3, use the copy EXEC command to transfer the files back from the TFTP server to the secondary NRP Flash disk.
NRP1# copy tftp://10.1.1.1/filename1 sec-flash:filename1 NRP1# copy tftp://10.1.1.1/filename2 sec-flash:filename2 NRP1# copy tftp://10.1.1.1/filename3 sec-flash:filename3 ...
Step 7 Use the dir EXEC command to verify that the new system image is the first file listed on the secondary NRP Flash disk.
NRP1# dir sec-flash:
If you completed the steps described in the previous section, continue with the "Reload the Secondary NRP" section.
Complete the following steps from the primary NRP to update both the primary and secondary NRP configurations to reflect the new startup image. NRP1 in slot 1 is still the primary device, and NRP2 in slot 2 is still the secondary device.
NRP1# no boot system flash:c6400r-g4p5-mz.120-7.DC
Step 2 Use the boot system global configuration command to add the new startup image configuration to the primary NRP.
NRP1# boot system flash:c6400r-g4p5-mz.121-1.DC1
Step 3 Use the copy EXEC command to save the primary NRP running configuration as the startup configuration. This step also updates the startup configuration on the secondary NRP.
NRP1# copy system:running-config nvram:startup-config
Complete the following step from the NSP to reload the secondary NRP. NRP1 in slot 1 is still the primary device, and NRP2 in slot 2 is still the secondary device.
NSP# hw-module slot 2 reset
The secondary NRP is now running the new image in standby mode.
Complete the following steps from the primary NRP to upgrade the primary NRP images. NRP1 in slot 1 is still the primary device, and NRP2 in slot 2 is still the secondary device.
NRP1# dir flash: NRP1# dir bootflash:
Step 2 Use the copy EXEC command to backup the system and boothelper images to a TFTP server.
NRP1# copy flash:c6400r-g4p5-mz.120-7.DC tftp://10.1.1.1/c6400r-g4p5-mz.120-7.DC NRP1# copy bootflash:c6400r-boot-mz.120-7.DC tftp://10.1.1.1/c6400r-boot-mz.120-7.DC
Step 3 Use the delete EXEC command to mark the old images for deletion.
NRP1# delete flash:c6400r-g4p5-mz.120-7.DC NRP1# delete bootflash:c6400r-boot-mz.120-7.DC
Step 4 Use the squeeze EXEC command to permanently delete the images marked for deletion.
NRP1# squeeze flash: NRP1# squeeze bootflash:
Step 5 Use the copy EXEC command to load the new images from the secondary NRP.
NRP1# copy sec-flash:c6400r-g4p5-mz.121-1.DC1 flash:c6400r-g4p5-mz.121-1.DC1 NRP1# copy sec-bootflash:c6400r-boot-mz.121-1.DC1 bootflash:c6400r-boot-mz.121-1.DC1
To ensure that the new image is used at system reload, choose the same method that you used in the "Identify the New System Image as the Startup Image for the Secondary NRP" section, specifically:
Complete the following steps to make sure that the new image is the first file on the secondary NRP Flash disk. NRP1 in slot 1 is still the primary device, and NRP2 in slot 2 is still the secondary device.
NRP1# dir flash:
Step 2 If the new system image is the first file listed, the image is already the startup image. Continue with the "Switch the Primary and Secondary NRPs" section.
If the new system image is not at the top of the list, and you want save the files that are listed above the new image, continue with Step 3.
If you want to delete the files listed above the new image, continue with Step 4.
Step 3 Use the copy EXEC command to backup the primary NRP Flash files to a TFTP server.
NRP1# copy flash:filename tftp://10.1.1.1/filename1 NRP1# copy flash:filename tftp://10.1.1.1/filename2 NRP1# copy flash:filename tftp://10.1.1.1/filename3 ...
Step 4 Use the delete EXEC command to mark the unwanted primary NRP files for deletion.
NRP1# delete flash:filename1 NRP1# delete flash:filename2 NRP1# delete flash:filename3 ...
Step 5 Use the squeeze EXEC command to permanently delete the primary NRP images that are marked for deletion.
NRP1# squeeze flash: NRP1# squeeze bootflash:
Step 6 If you performed Step 3, use the copy EXEC command to transfer the files back from the TFTP server to the primary NRP Flash disk.
NRP1# copy tftp://10.1.1.1/filename1 flash:filename1 NRP1# copy tftp://10.1.1.1/filename2 flash:filename2 NRP1# copy tftp://10.1.1.1/filename3 flash:filename3 ...
Step 7 Use the dir EXEC command to verify that the new system image is the first file listed on the primary NRP Flash disk.
NRP1# dir flash:
If you completed the instructions in the "Updating the Boot System Variable" section, then both the primary and secondary NRP configurations already reflect the new startup image.
Complete the following step from the NSP to switch the primary and secondary NRPs. Before you begin this task, NRP1 in slot 1 is still the primary device, and NRP2 in slot 2 is still the secondary device.
NSP# redundancy force-failover slot 1
NRP1 in slot 1 is now the secondary device, and NRP2 in slot 2 is the primary device. NRP1 automatically resets itself, and runs the new image in standby mode. Both the primary and secondary NRPs are now running the new image.
This section presents an example of upgrading redundant NRP images from Cisco IOS Release 12.0(7) DC to Cisco IOS Release 12.1(1) DC1.
This section contains the following task examples:
1. Upgrading the Images on the Secondary NRP
2. Identifying the New Image as the Startup Image
3. Reloading the Secondary NRP
In the following example, the secondary NRP system image is upgraded from Cisco IOS Release 12.0(7) DC to Cisco IOS Release 12.1(1) DC1. NRP5 in slot 5 is the primary device, and NRP6 in slot 6 is the secondary device.
nrp5# dir sec-flash: Directory of sec-flash:/ 1 -rw- 5018040 Aug 09 2000 12:47:44 c6400r-g4p5-mz.120-7.DC 7602176 bytes total (2584008 bytes free) nrp5# delete sec-flash:c6400r-g4p5-mz.120-7.DC Delete filename [c6400r-g4p5-mz.120-7.DC]? Delete sec-flash:c6400r-g4p5-mz.120-7.DC? [confirm] nrp5# copy tftp:sec-flash: Address or name of remote host []? 10.1.1.1 Source filename []? c6400r-g4p5-mz.121-1.DC1 Destination filename [c6400r-g4p5-mz.121-1.DC1]? Accessing tftp://10.1.1.1/c6400r-g4p5-mz.121-1.DC1... Loading c6400r-g4p5-mz.121-1.DC1 from 10.1.1.1 (via Ethernet0/0/1):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [snip]
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!! [OK - 5215184/10429440 bytes] 5215184 bytes copied in 125.792 secs (41721 bytes/sec)
In the following example, the boot system variable is updated to reflect the new startup image.
nrp5(config)# no boot system flash:c6400r-g4p5-mz.120-7.DC nrp5(config)# boot system flash:c6400r-g4p5-mz.121-1.DC1 nrp5(config)# config-register 0x2 nrp5(config)# end nrp5# nrp5# copy system:running-config nvram:startup-config Destination filename [startup-config]? Building configuration... [OK]
In the following example, the secondary NRP is reset from the NSP. NRP5 in slot 5 is the primary device, and NRP6 in slot 6 is the secondary device.
nsp# hw-module slot 6 reset 20:21:05:%NSP_OIR-6-FULL_CREM:Card NRP removed from slot:6 nsp# 20:21:06:%NSP_OIR-6-FULL_CINS:Card NRP inserted into slot:6 20:21:06:%NSP_OIR-6-FULL_ONLINE:Card NRP, slot:6, being brought online 20:21:08:%LINK-3-UPDOWN:Interface ATM6/0/0, changed state to down
In the following example, the primary NRP system image is upgraded from Cisco IOS Release 12.0(7) DC to Cisco IOS Release 12.1(1) DC1. NRP5 in slot 5 is the primary device, and NRP6 in slot 6 is the secondary device.
nrp5# dir sec-flash: Directory of sec-flash:/ 1 -rw- 5215184 Aug 09 2000 13:09:38 c6400r-g4p5-mz.121-1.DC1 7602176 bytes total (2386864 bytes free) nrp5# dir flash: Directory of flash:/ 1 -rw- 94074 Jul 26 2000 17:11:46 lns.cfg 2 -rw- 96278 Jul 26 2000 17:14:46 ip_route.cfg 3 -rw- 190480 Jul 27 2000 10:14:08 work.cfg 4 -rw- 5018040 Aug 09 2000 12:55:27 c6400r-g4p5-mz.120-7.DC 15990784 bytes total (10591396 bytes free) nrp5# delete flash:c6400r-g4p5-mz.120-7.DC Delete filename [c6400r-g4p5-mz.120-7.DC]? Delete flash:c6400r-g4p5-mz.120-7.DC? [confirm]
nrp5# squeeze flash:
All deleted files will be removed. Continue? [confirm]
Squeeze operation may take a while. Continue? [confirm]
Squeeze of flash complete
nrp5# copy sec-flash:c6400r-g4p5-mz.121-1.DC1 flash:
Destination filename [c6400r-g4p5-mz.121-1.DC1]?
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
[snip]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCC
5215184 bytes copied in 67.228 secs (77838 bytes/sec)
In the following example, the primary and secondary NRPs are switched. NRP5 in slot 5 is now the secondary device, and NRP6 in slot 6 is now the primary device.
nsp# redundancy force-failover slot 5 nsp#
This section describes how to upgrade software on redundant NSPs. To upgrade software on an NSP that is not configured for redundancy, see the "Upgrading Software on Nonredundant NSPs" section.
To upgrade the software images on redundant NSPs, perform the following tasks in the specified order. Each task in the list must be performed on the primary NSP.
1. Upgrade the Secondary NSP Images
3. Disable Automatic Configuration Synchronization
4. Switch the Primary and Secondary NSPs
5. Upgrade the Now-Secondary NSP Images
In the following instructions and examples, NSP-A is the device in slot 0A of the Cisco 6400 chassis, and NSP-B is the device in slot 0B.
Complete the following steps to upgrade the secondary NSP images. NSP-A in slot 0A is the primary device, and NSP-B in slot 0B is the secondary device.
NSP# dir sec-disk0: NSP# dir sec-disk1: NSP# dir sec-bootflash:
Step 2 Use the copy EXEC command to backup the secondary NSP images to a TFTP server.
NSP# copy sec-disk0:c6400s-wp-mz.120-7.DB tftp://10.1.1.1/c6400s-wp-mz.120-7.DB NSP# copy sec-disk0:c6400s-html.tar.120-5.DB tftp://10.1.1.1/c6400s-html.tar.120-5.DB NSP# copy sec-bootflash:c6400s-wp-mz.120-5.DB tftp://10.1.1.1/c6400s-wp-mz.120-5.DB
Step 3 Use the delete EXEC command to mark the secondary NSP's old images for deletion.
NSP# delete sec-disk0:c6400s-wp-mz.120-7.DB NSP# delete sec-disk0:c6400s-html.tar.120-5.DB NSP# delete sec-bootflash:c6400s-wp-mz.120-5.DB
Step 4 Use the copy EXEC command to load the new images onto the secondary NSP.
NSP# copy tftp://10.1.1.1/c6400s-wp-mz.DB1 sec-disk0:c6400s-wp-mz.DB1 NSP# copy tftp://10.1.1.1/c6400s-html.tar.DB1 sec-disk0:c6400s-html.tar.DB1 NSP# copy tftp://10.1.1.1/c6400s-wp-mz.DB1 sec-bootflash:c6400s-wp-mz.DB1
Complete the following step to reload the secondary NSP. NSP-A in slot 0A is still the primary device, and NSP-B in slot 0B is still the secondary device.
NSP# hw-module nsp B reset
The secondary NSP is now running the new image.
Complete the following steps to disable automatic configuration synchronization between the redundant NSPs. NSP-A in slot 0A is still the primary device, and NSP-B in slot 0B is still the secondary device.
NSP(config)# redundancy
Step 2 Use the main-cpu redundancy mode command to enter the main-cpu redundancy mode.
NSP(config-r)# main-cpu
Step 3 Use the no auto-sync standard main-cpu redundancy mode command to disable automatic synchronization between the redundant NSPs.
NSP(config-r-mc)# no auto-sync standard
Step 4 Use the end command to return to EXEC mode.
NSP(config-r-mc)# end
Step 5 Use the copy EXEC command to save the running configuration as the startup configuration.
NSP# copy system:running-config nvram:startup-config
Step 6 Use the configure terminal, redundancy, and main-cpu commands to enter the main-cpu redundancy mode.
NSP# configure terminal NSP(config)# redundancy NSP(config-r)# main-cpu NSP(config-r-mc)#
Step 7 Use the auto-sync standard main-cpu redundancy mode command to force a manual configuration synchronization.
NSP(config-r-mc)# auto-sync standard
Step 7 ensures that the secondary NSP also has automatic configuration synchronization disabled in its startup configuration.
Step 8 Use the no auto-sync standard main-cpu redundancy mode command to disable automatic synchronization between the redundant NSPs.
NSP(config-r-mc)# no auto-sync standard
Complete the following steps to switch the primary and secondary NSPs. Before this task is completed, NSP-A in slot 0A is the primary device, and NSP-B in slot 0B is the secondary device.
NSP# redundancy force-failover main-cpu
NSP-A in slot 0A is now the secondary device, and NSP-B in slot 0B is now the primary device. NSP-A is still running the old image, and NSP-B is running the new image.
Complete the following steps to upgrade the secondary NSP images. NSP-A in slot 0A is the secondary device, and NSP-B in slot 0B is the primary device.
NSP# dir sec-disk0: NSP# dir sec-disk1: NSP# dir sec-bootflash:
Step 2 Use the copy EXEC command to backup the secondary NSP images to a TFTP server.
NSP# copy sec-disk0:c6400s-wp-mz.120-7.DB tftp://10.1.1.1/c6400s-wp-mz.120-7.DB NSP# copy sec-disk0:c6400s-html.tar.120-5.DB tftp://10.1.1.1/c6400s-html.tar.120-5.DB NSP# copy sec-bootflash:c6400s-wp-mz.120-5.DB tftp://10.1.1.1/c6400s-wp-mz.120-5.DB
Step 3 Use the delete EXEC command to mark the secondary NSP's old images for deletion.
NSP# delete sec-disk0:c6400s-wp-mz.120-7.DB NSP# delete sec-disk0:c6400s-html.tar.120-5.DB NSP# delete sec-disk0:c6400s-wp-mz.120-5.DB
Step 4 Use the squeeze EXEC command to permanently delete the secondary NSP files marked for deletion.
NSP# squeeze sec-disk0:
Step 5 Use the copy EXEC command to load the new images onto the secondary NSP.
NSP# copy tftp://10.1.1.1/c6400s-wp-mz.DB1 sec-disk0:c6400s-wp-mz.DB1 NSP# copy tftp://10.1.1.1/c6400s-html.tar.DB1 sec-disk0:c6400s-html.tar.DB1 NSP# copy tftp://10.1.1.1/c6400s-wp-mz.DB1 sec-bootflash:c6400s-wp-mz.DB1
Complete the following step to reload the secondary NSP. NSP-B in slot 0B is the primary device, and NSP-A in slot 0A is the secondary device.
NSP# hw-module nsp A reset
Both NSPs are now running the new image.
Complete the following steps to enable automatic configuration synchronization between the redundant NSPs. NSP-B in slot 0B is still the primary device, and NSP-A in slot 0A is still the secondary device.
NSP(config)# redundancy
Step 2 Use the main-cpu redundancy mode command to enter the main-cpu redundancy mode.
NSP(config-r)# main-cpu
Step 3 Use the auto-sync standard main-cpu redundancy mode command to enable automatic configuration synchronization.
NSP(config-r-mc)# auto-sync standard
Step 4 Use the no auto-sync standard main-cpu redundancy mode command to enable automatic synchronization between the redundant NSPs.
NSP(config-r-mc)# no auto-sync standard
Step 5 Use the end command to return to EXEC mode.
NSP(config-r-mc)# end
Step 6 Use the copy EXEC command to save the primary NRP running configuration as the startup configuration. This step also updates the startup configuration on the secondary NRP.
NSP# copy system:running-config nvram:startup-config
Both the primary device (NSP-B) and the secondary device (NSP-A) are running the new images, and the upgrade is complete.
This section presents an example of upgrading redundant NSP images from Cisco IOS Release 12.0(7) DB to Cisco IOS Release 12.1(1) DB1.
This section contains the following task examples:
1. Upgrading the Secondary NSP Images
2. Reloading the Secondary NSP
3. Disabling Automatic Configuration Synchronization
4. Switching the Primary and Secondary NSPs
5. Upgrading the Now-Secondary NSP Images
In the following example, the secondary NSP image is upgraded from Cisco IOS Release 12.0(7) DB to Cisco IOS Release 12.1(1) DB1. NSP-A in slot 0A is the primary device, and NSP-B in slot 0B is the secondary device.
NSP# show redundancy NSP A :Primary NSP B :Secondary NSP# dir sec-disk0: Directory of sec-disk0:/ 1151 -rw- 4504276 Aug 07 2000 17:32:28 c6400s-wp-mz.120-7.DB 20819968 bytes total (16314368 bytes free) NSP# delete sec-disk0:c6400s-wp-mz.120-7.DB Delete sec-disk0:c6400s-wp-mz.120-7.DB? [confirm] NSP# copy tftp:sec-disk0: Address or name of remote host []? 10.1.1.1 Source filename []? c6400s-wp-mz.121-1.DB1 Accessing tftp://10.1.1.1/c6400s-wp-mz.121-1.DB1... Loading c6400s-wp-mz.121-1.DB1 from 10.1.1.1 (via BVI1):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [snip]
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!! [OK - 4575296/9150464 bytes] 4575296 bytes copied in 256.468 secs (17872 bytes/sec)
In the following example, the secondary NSP is reset from the primary NSP. NSP-A in slot 0A is the primary device, and NSP-B in slot 0B is the secondary device.
NSP# hw-module nsp B reset NSP# 00:19:47:%EHSA-5-PEER_MONITOR_EVENT:Master detected a secondary crash (raw-event=PEER_DOWN(2)) 00:19:47:%EHSA-5-PEER_MONITOR_EVENT:Master detected a secondary removal (raw-event=PEER_EHSA_STATE_CHANGE(5)) 00:19:48:%EHSA-5-PEER_MONITOR_EVENT:Master detected a secondary insertion (raw-event=PEER_EHSA_STATE_CHANGE(5))
The following example illustrates the following steps:
1. Automatic configuration synchronization is disabled
2. Primary NSP's running configuration is saved as the startup configuration
3. Automatic configuration synchronization is enabled so that the primary and secondary NSPs' startup configurations have automatic synchronization disabled
4. Automatic configuration synchronization is disabled
NSP# configure terminal Enter configuration commands, one per line. End with CNTL/Z. NSP(config)# redundancy NSP(config-r)# main-cpu NSP(config-r-mc)# no auto-sync standard NSP(config-r-mc)# end NSP# copy running-config nvram:startup-config Destination filename [startup-config]? Building configuration... [OK] NSP# configure terminal Enter configuration commands, one per line. End with CNTL/Z. NSP(config)# redundancy NSP(config-r)# main-cpu NSP(config-r-mc)# auto-sync standard NSP(config-r-mc)# end NSP# configure terminal Enter configuration commands, one per line. End with CNTL/Z. NSP(config)# redundancy NSP(config-r)# main-cpu NSP(config-r-mc)# no auto-sync standard NSP(config-r-mc)# end
In the following example, NSP-A becomes the secondary device and NSP-B becomes the primary device. NSP-B is running the new image, and the secondary device NSP-A is running the old image.
NSP# redundancy force-failover main-cpu 00:33:38:%SYS-5-RELOAD:Reload requested
In the following example, the secondary NSP image is upgraded from Cisco IOS Release 12.0(7) DB to Cisco IOS Release 12.1(1) DB1. NSP-A in slot 0A is now the secondary device, and NSP-B in slot 0B is now the primary device.
NSP# show redundancy NSP A :Secondary NSP B :Primary NSP# dir sec-disk0: Directory of sec-disk0:/ 1151 -rw- 4504276 Aug 07 2000 17:32:28 c6400s-wp-mz.120-7.DB 20819968 bytes total (16314368 bytes free) NSP# delete sec-disk0:c6400s-wp-mz.120-7.DB Delete sec-disk0:c6400s-wp-mz.120-7.DB? [confirm] NSP# copy tftp:sec-disk0: Address or name of remote host []? 10.1.1.1 Source filename []? c6400s-wp-mz.121-1.DB1 Accessing tftp://10.1.1.1/c6400s-wp-mz.121-1.DB1...
Loading c6400s-wp-mz.121-1.DB1 from 10.1.1.1 (via BVI1):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [snip] !!!!!!!!!! [OK - 4575296/9150464 bytes] 4575296 bytes copied in 256.468 secs (17872 bytes/sec)
In the following example, the secondary device NSP-A reloads, boots with the new image, and goes to standby mode. NSP-B remains the primary device.
NSP# hw-module nsp A reset NSP# 00:07:27:%EHSA-5-PEER_MONITOR_EVENT:Master detected a secondary crash (raw-event=PEER_DOWN(2)) 00:07:27:%EHSA-5-PEER_MONITOR_EVENT:Master detected a secondary removal (raw-event=PEER_EHSA_STATE_CHANGE(5)) 00:07:28:%EHSA-5-PEER_MONITOR_EVENT:Master detected a secondary insertion (raw-event=PEER_EHSA_STATE_CHANGE(5)))
In the following example, automatic configuration synchronization between the redundant NSPs is once again enabled, and both NSPs' startup configurations are updated.
NSP# configure terminal Enter configuration commands, one per line. End with CNTL/Z. NSP(config)# redundancy NSP(config-r)# main-cpu NSP(config-r-mc)# auto-sync standard NSP(config-r-mc)# end NSP# copy system:running-config nvram:startup-config Destination filename [startup-config]? Building configuration... [OK]
Both the primary device (NSP-B) and the secondary device (NSP-A) are now running the new image.
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
You can e-mail questions about using CCO to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
Language | E-mail Address |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
This document is to be used in conjunction with the C isco 6400 Software Configuration Guide and Command Reference publication.
Access Registrar, AccessPath, Any to Any, Are You Ready, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, IQ Breakthrough, IQ Expertise, IQ FastTrack, IQ Readiness Scorecard, The IQ Logo, Kernel Proxy, MGX, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, RateMux, ReyMaster, ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, VlanDirector, Voice LAN, Wavelength Router, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and Aironet, ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, CollisionFree, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0005R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.
Posted: Fri Sep 29 09:03:19 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.