Cisco 3600 Series Routers (with PCMCIA cards) Upgrade Procedure
Establish a console session to the router
Verify the amount of free space on the Flash memory card (PCMCIA slot)
Verify that the TFTP server has IP connectivity to the router
Copy the new image into the Flash memory card through the TFTP server
Set boot statements to load the new image upon startup
Reboot the router to load the new image
Verify the upgrade
Step 1: Establish a console session to the router
See Establish a console session to the router for more information.
Note: Once connected to the router through the console port, if you get a ">" or "rommon >" prompt, your router is in ROM monitor (ROMmon) mode. If the router is showing the "router (boot)>" prompt, then the router is in boot mode. See booting problems for steps to handle either of these situations.
Step 2: Verify the amount of free space on the Flash memory card (PCMCIA slot)
At this point, you need to verify that you have enough space in the Flash memory card to copy the new image. If there is not enough memory, you need to delete some files to make enough space. In some situations, if the image is very large, you may need to delete the current image in the Flash memory card.
To determine the amount of free space, and to show files currently located in slot0: or slot1:, issue the dir{device:} command.
3600#dir slot1:
Directory of slot1:/
1 -rw- 2779832 c3640-i-mz.113-11c.bin
2 -rw- 3748760 c3640-i-mz.120-22.bin
Verify that the name and the file size are correct.
If you find that there is not enough space, you can delete the file. The delete{device:}[filename] command deletes the file.
3600#delete slot1:
Delete filename []? c3640-i-mz.113-11c.bin
Delete slot1:c3640-i-mz.113-11c.bin? [confirm]y
Note: Do not reload or powercycle the router if there is not a valid image in the Flash; this causes the router to boot into rommon or bootmode.
Step 3: Verify that the TFTP server has IP connectivity to the router
The TFTP server must have a network connection to the router and must be able to ping the IP address of the router targeted for a TFTP software upgrade. To achieve this, the router interface and the TFTP server must have:
an IP address in the same range, or
a default gateway configured
To verify this, check the IP address of the TFTP server.
Step 4: Copy the new image into the Flash memory card through the TFTP server
Now that you have IP connectivity and can ping between the computer acting as a TFTP server and the router, you can copy the image into the right slot.
Note: Before copying, make sure you have started the TFTP server software on your PC and that you have the filename mentioned in the TFTP server root directory. We recommend that you keep a backup of the router/access server configuration before upgrading. The upgrade itself does not affect the configuration (which is stored in nonvolatile RAM -NVRAM). However, this may happen if the right steps are not followed properly.
For RCP applications, substitute RCP for every occurrence of TFTP. For example, use the copy rcp {device:} command instead of the copy tftp {device:} command.
If necessary, you can copy an image from one device to another.
3600#copy tftp: slot1:
Address or name of remote host []? 171.68.173.10
Source filename []? c3640-i-mz.122-7b.bin
Destination filename [c3640-i-mz.122-7b.bin]?
Accessing tftp://171.68.173.10/c3640-i-mz.122-7b.bin...
Erase slot1: before copying? [confirm]n !--- Here you are specifying "n"
!--- because there is enough memory available.
Loading c3640-i-mz.122-7b.bin from 171.68.173.10 (via Ethernet1/0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!
[OK - 5996844/11993088 bytes]
Verifying checksum... OK (0x13F0)
5996844 bytes copied in 67.708 secs (89505 bytes/sec)
3600#
Use the dir slot1: command to check whether the image has been copied to slot1. Below, you can see that the new image c3640-i-mz.122-7b.bin has been copied on the PCMCIA slot1:
3600#dir slot1:
Directory of slot1:/
2 -rw- 3748760 c3640-i-mz.120-22.bin
3 -rw- 5996844 c3640-i-mz.122-7b.bin
Step 5: Set boot statements to load the new image upon startup
After copying the image through TFTP, you may need to tell the router which image to load upon boot up.
Checking Current Boot Statements
At this point, the new image is now in the slot1. You need to set the router to boot the new image. By default, the router boots the first available image (the default is enabled when there are no boot statements in the configuration).
3600#show running-config
Building configuration...
Current configuration:
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname 3600
!
boot system flash slot1:c3640-i-mz.120-22.bin
!
ip subnet-zero
!
The commands appear at the begginning of the configuration. In our example above, it shows the router has a boot system command configured as boot system flash slot1:c3640-i-mz.120-22.bin.
If you have boot system command entries in your configuration, you need to remove them from the configuration. For more information on removing boot entries, refer to the next section.
Removing Previous Boot Statements
To remove the commands, enter into configuration terminal mode. From the configuration mode, you can negate any command by typing "no" in front of each boot statement. The following example illustrates the removal of an existing boot statement.
3600#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
3600(config)#no boot system flash slot1:c3640-i-mz.120-22.bin
3600(config)#^Z
3600#
The statement "no boot system flash slot1:c3640-i-mz.120-22.bin" is removed from the configuration. Verify that the command has been removed by issuing the show running-config command.
Setting New Boot Statements
Now set the router to boot the new image. Issue the following command to set the boot system parameter:
boot system flash slot#:{imagename} (imagename = name of the new Cisco IOS software image)
3600#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
3600(config)#boot system flash slot1:c3640-i-mz.122-7b.bin
3600(config)#^Z
3600#write memory
3d01h: %SYS-5-CONFIG_I: Configured from console by vty0
Building configuration...
3600#
Be sure to verify that you are using config-register 0x2102 by issuing the show version command. If it is set up differently, you can change it by issuing the following command in configuration mode:
3600#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
3600(config)#config-register 0x2102
3600(config)#^Z
After changing the config-register, the change takes place at the next reload.
Step 6: Reboot the router to load the new image
For the router to run the new Cisco IOS software image, you need to reload the router. Make sure you have saved the configuration by issuing the copy running-config starting-config or write memory commands.
3600#write memory
3d01h: %SYS-5-CONFIG_I: Configured from console by vty0 (127.0.0.11)
Building configuration...
3600#reload
Step 7: Verify the upgrade
After the router comes up, make sure you are currently running the new version of code, by issuing the show version command.
3640#show version
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3640-I-M), Version 12.2(7b), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Mon 04-Mar-02 20:23 by pwade
Image text-base: 0x600089A8, data-base: 0x60A6A000
ROM: System Bootstrap, Version 11.1(19)AA, EARLY DEPLOYMENT RELEASE SOFTWARE (f)
Router uptime is 2 minutes
System returned to ROM by reload
System image file is "slot1:c3640-i-mz.122-7b.bin"
cisco 3640 (R4700) processor (revision 0x00) with 59392K/6144K bytes of memory.
Processor board ID 10524422
R4700 CPU at 100Mhz, Implementation 33, Rev 1.0
Bridging software.
X.25 software, Version 3.0.0.
4 Ethernet/IEEE 802.3 interface(s)
DRAM configuration is 64 bits wide with parity disabled.
125K bytes of non-volatile configuration memory.
4096K bytes of processor board System flash (Read/Write)
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
20480K bytes of processor board PCMCIA Slot1 flash (Read/Write)
Configuration register is 0x2102
Verify that the version 12.2(7b) is correct and the config-register is set to 0x2102.
Page last updated on: 05/19/2007 09:53:42
All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved.
Establish a console session to the router
Verify the amount of free space on the Flash memory card (PCMCIA slot)
Verify that the TFTP server has IP connectivity to the router
Copy the new image into the Flash memory card through the TFTP server
Set boot statements to load the new image upon startup
Reboot the router to load the new image
Verify the upgrade
Step 1: Establish a console session to the router
See Establish a console session to the router for more information.
Note: Once connected to the router through the console port, if you get a ">" or "rommon >" prompt, your router is in ROM monitor (ROMmon) mode. If the router is showing the "router (boot)>" prompt, then the router is in boot mode. See booting problems for steps to handle either of these situations.
Step 2: Verify the amount of free space on the Flash memory card (PCMCIA slot)
At this point, you need to verify that you have enough space in the Flash memory card to copy the new image. If there is not enough memory, you need to delete some files to make enough space. In some situations, if the image is very large, you may need to delete the current image in the Flash memory card.
To determine the amount of free space, and to show files currently located in slot0: or slot1:, issue the dir{device:} command.
3600#dir slot1:
Directory of slot1:/
1 -rw- 2779832 c3640-i-mz.113-11c.bin
2 -rw- 3748760 c3640-i-mz.120-22.bin
Verify that the name and the file size are correct.
If you find that there is not enough space, you can delete the file. The delete{device:}[filename] command deletes the file.
3600#delete slot1:
Delete filename []? c3640-i-mz.113-11c.bin
Delete slot1:c3640-i-mz.113-11c.bin? [confirm]y
Note: Do not reload or powercycle the router if there is not a valid image in the Flash; this causes the router to boot into rommon or bootmode.
Step 3: Verify that the TFTP server has IP connectivity to the router
The TFTP server must have a network connection to the router and must be able to ping the IP address of the router targeted for a TFTP software upgrade. To achieve this, the router interface and the TFTP server must have:
an IP address in the same range, or
a default gateway configured
To verify this, check the IP address of the TFTP server.
Step 4: Copy the new image into the Flash memory card through the TFTP server
Now that you have IP connectivity and can ping between the computer acting as a TFTP server and the router, you can copy the image into the right slot.
Note: Before copying, make sure you have started the TFTP server software on your PC and that you have the filename mentioned in the TFTP server root directory. We recommend that you keep a backup of the router/access server configuration before upgrading. The upgrade itself does not affect the configuration (which is stored in nonvolatile RAM -NVRAM). However, this may happen if the right steps are not followed properly.
For RCP applications, substitute RCP for every occurrence of TFTP. For example, use the copy rcp {device:} command instead of the copy tftp {device:} command.
If necessary, you can copy an image from one device to another.
3600#copy tftp: slot1:
Address or name of remote host []? 171.68.173.10
Source filename []? c3640-i-mz.122-7b.bin
Destination filename [c3640-i-mz.122-7b.bin]?
Accessing tftp://171.68.173.10/c3640-i-mz.122-7b.bin...
Erase slot1: before copying? [confirm]n !--- Here you are specifying "n"
!--- because there is enough memory available.
Loading c3640-i-mz.122-7b.bin from 171.68.173.10 (via Ethernet1/0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!
[OK - 5996844/11993088 bytes]
Verifying checksum... OK (0x13F0)
5996844 bytes copied in 67.708 secs (89505 bytes/sec)
3600#
Use the dir slot1: command to check whether the image has been copied to slot1. Below, you can see that the new image c3640-i-mz.122-7b.bin has been copied on the PCMCIA slot1:
3600#dir slot1:
Directory of slot1:/
2 -rw- 3748760 c3640-i-mz.120-22.bin
3 -rw- 5996844 c3640-i-mz.122-7b.bin
Step 5: Set boot statements to load the new image upon startup
After copying the image through TFTP, you may need to tell the router which image to load upon boot up.
Checking Current Boot Statements
At this point, the new image is now in the slot1. You need to set the router to boot the new image. By default, the router boots the first available image (the default is enabled when there are no boot statements in the configuration).
3600#show running-config
Building configuration...
Current configuration:
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname 3600
!
boot system flash slot1:c3640-i-mz.120-22.bin
!
ip subnet-zero
!
The commands appear at the begginning of the configuration. In our example above, it shows the router has a boot system command configured as boot system flash slot1:c3640-i-mz.120-22.bin.
If you have boot system command entries in your configuration, you need to remove them from the configuration. For more information on removing boot entries, refer to the next section.
Removing Previous Boot Statements
To remove the commands, enter into configuration terminal mode. From the configuration mode, you can negate any command by typing "no" in front of each boot statement. The following example illustrates the removal of an existing boot statement.
3600#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
3600(config)#no boot system flash slot1:c3640-i-mz.120-22.bin
3600(config)#^Z
3600#
The statement "no boot system flash slot1:c3640-i-mz.120-22.bin" is removed from the configuration. Verify that the command has been removed by issuing the show running-config command.
Setting New Boot Statements
Now set the router to boot the new image. Issue the following command to set the boot system parameter:
boot system flash slot#:{imagename} (imagename = name of the new Cisco IOS software image)
3600#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
3600(config)#boot system flash slot1:c3640-i-mz.122-7b.bin
3600(config)#^Z
3600#write memory
3d01h: %SYS-5-CONFIG_I: Configured from console by vty0
Building configuration...
3600#
Be sure to verify that you are using config-register 0x2102 by issuing the show version command. If it is set up differently, you can change it by issuing the following command in configuration mode:
3600#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
3600(config)#config-register 0x2102
3600(config)#^Z
After changing the config-register, the change takes place at the next reload.
Step 6: Reboot the router to load the new image
For the router to run the new Cisco IOS software image, you need to reload the router. Make sure you have saved the configuration by issuing the copy running-config starting-config or write memory commands.
3600#write memory
3d01h: %SYS-5-CONFIG_I: Configured from console by vty0 (127.0.0.11)
Building configuration...
3600#reload
Step 7: Verify the upgrade
After the router comes up, make sure you are currently running the new version of code, by issuing the show version command.
3640#show version
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3640-I-M), Version 12.2(7b), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Mon 04-Mar-02 20:23 by pwade
Image text-base: 0x600089A8, data-base: 0x60A6A000
ROM: System Bootstrap, Version 11.1(19)AA, EARLY DEPLOYMENT RELEASE SOFTWARE (f)
Router uptime is 2 minutes
System returned to ROM by reload
System image file is "slot1:c3640-i-mz.122-7b.bin"
cisco 3640 (R4700) processor (revision 0x00) with 59392K/6144K bytes of memory.
Processor board ID 10524422
R4700 CPU at 100Mhz, Implementation 33, Rev 1.0
Bridging software.
X.25 software, Version 3.0.0.
4 Ethernet/IEEE 802.3 interface(s)
DRAM configuration is 64 bits wide with parity disabled.
125K bytes of non-volatile configuration memory.
4096K bytes of processor board System flash (Read/Write)
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
20480K bytes of processor board PCMCIA Slot1 flash (Read/Write)
Configuration register is 0x2102
Verify that the version 12.2(7b) is correct and the config-register is set to 0x2102.
Page last updated on: 05/19/2007 09:53:42
All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved.
No comments:
Post a Comment