|
|
This publication describes how to upgrade run-from-RAM and run-from-Flash software images on a Cisco 3000 router. Read this entire publication before attempting any of its procedures.
The following list shows the product numbers for each image available on the Cisco 3000. Find the product number for your image in this list, then refer to the section that describes how to upgrade your system image type.
Run-from-Flash Product Numbers: | Run-from-RAM Product Numbers: |
|---|---|
| SW-G3-9.1.x= | SW-G3-9.1.x= |
| SW-G3A-9.21.x= | SW-G3RA-9.14.x= |
| SW-G3B-9.21.x= | SW-G3RB-9.14.x= |
| SW-G3C-9.21.x= | SW-G3RC-9.14.x= |
| SW-G3A-10.0.x= | SW-G3RA-9.21.x= |
| SW-G3B-10.0.x= | SW-G3RB-9.21.x= |
| SW-G3C-10.0.x= | SW-G3RC-9.21.x= |
| SW-G3RA-10.0.x= | |
| SW-G3RB-10.0.x= | |
| SW-G3RC-10.0.x= |
The information in this publication is organized within the following sections:
The Cisco 3000 supports Flash memory downloading for software images. Downloadable images enable you to download new images over the network, store the images in the router's Flash memory, and load images from Flash at system startup without having to physically access the router.
Some Cisco routers, including the Cisco 3000, are able to run from Flash memory and can only boot from the first file in Flash memory. To upgrade the system software image on such a router, you must erase the contents of Flash memory so the new system image can be written as the first file. The process you use depends on the type of image you are upgrading.
The rxboot image is a bootable image stored in ROM on a Cisco 3000. It is limited in size, and therefore, has only a limited subset of the functionality of a complete router system image.
The following functions are supported by the rxboot image:
The following functions are not supported by the rxboot image:
 | Caution When upgrading a run-from-Flash image, if there are any interfaces with the IP unnumbered option enabled on a router to be upgraded, IP routes will not be complete between the TFTP server and the router. Explicit IP numbers must be entered for an interface configured with the IP unnumbered option before the upgrade. You will otherwise be locked out of the connection from the TFTP server to your router. If this occurs, you must use a modem to connect to the console port on the router. |
To successfully upgrade system software on your Cisco 3000 routers, you should observe the following prerequisites and caveats.
This section describes the general steps required to upgrade your system software on a Cisco 3000 router. The sections that follow describe these steps in greater detail.
Step 1 Establish a route from a TFTP server to the routers to be upgraded.
Step 2 Install the system software from the 3.5-inch floppy disk onto your PC or UNIX machine into the TFTP server directory.
Step 3 Start the TFTP server if it is not already active.
Step 4 If you do not have a console port connection to the router you plan to upgrade, establish a Telnet session with the router.
Step 5 Back up the existing working system software image currently in Flash memory by copying it to the TFTP server.
Step 6 If you are loading a run-from-Flash image, reload the router so it boots to the boot ROM prompt (router(boot)#).
Step 7 If you are loading a run-from-Flash image, Telnet again to the router running in boot-ROM mode that is to be upgraded.
Step 8 Copy the system software image from the TFTP server into Flash memory.
Step 9 Ensure that the checksum listed on the bottom line of the output for the copy tftp flash command matches the checksum listed in the README file on the upgrade disk. If it does not, you must invoke the copy tftp flash command again before booting from Flash memory.
Step 10 If you are loading a run-from-Flash image, you will return the router to its original state (change the booting instructions so it reloads from Flash memory, not from boot ROM mode).
Step 11 Make sure your system is configured to boot from the new image in Flash memory.
Step 12 Boot the router from Flash.
Step 13 Check all network connections to make sure the router with the upgraded system software is up and functioning properly. Repeat these steps to upgrade subsequent routers.
You need a TFTP server to download a new system image. This server can also hold original system images for backup purposes. This section describes how to ensure a route is established between the TFTP server and the router to be upgraded.
Step 1 Log in to the console port of each router to be upgraded (using Telnet or a modem).
Step 2 Add the command ip default-gateway to each router's configuration file.
Step 3 If you have a serial link to the TFTP server, make sure that all other serial lines for each router are temporarily shut down, or else the route to the server might be broken.
Figure 1 shows an example of a router named Cancun being upgraded with a system software image stored on the TFTP server named Lahonda.
To configure the router Cancun to guarantee a route to Lahonda, whether Cancun is in boot ROM mode or in normal operating mode, you would follow these steps:
cancun>enablePassword:<password>cancun#
cancun#configure terminalEnter configuration commands, one per line. Edit with DELETE, CTRL/W, and CTRL/U; end with CTRL/Zinterface serial 1shutdowninterface serial 0shutdownip default-gateway 144.254.100.1^Zcancun#write memory[ok] cancun#
Having established a route from the TFTP server to each router to be upgraded, refer to the next section "Installing System Software onto Your TFTP Server."
This section describes how to use the installation program on the disk with your software upgrade to install the system software onto your DOS-based PC or your desktop SPARCstation.
Refer to the online README file on the software upgrade disk for details about the image for the routers to be upgraded. The README file lists details such as product number, image type, file size, and checksum of the compressed or uncompressed image.
To copy your system software upgrade into the appropriate directory on the PC you plan to use as the TFTP server, follow this procedure. Allow five minutes to complete this procedure.
| Caution Do not install the system software image to the TFTP server a first time, then install it again. If you do, the system appends the second image to the first image rather than writing over it, and the altered image will not function in your routers. If you want to install the image a second time, first delete the image from the destination directory on the TFTP server, then reinstall it. |
Step 1 Make a backup copy of the master system software upgrade distribution disk and work from the backup copy. Archive the master disk.
Step 2 Insert the upgrade disk containing the system software upgrade into your 3.5-inch disk drive.
Step 3 Type the following command and press Enter.
install
where a is the drive in which you insert the source disk. The drive letter can be either a or b.
A screen similar to the following appears. This screen is for a 9.21(3) image on a Cisco 3000. If you are upgrading to a different release of router software, the header fields (first four lines in the display) will be different.
********************** IJ92130N.DOC **********************************
PRODUCT NO. SW-G3B-9.21.3=
System Software Image IJ92130N, IGS-BPX Version 9.21(3)
Uncompressed size = 1989999 bytes; Checksum=0x5alc
Copyright (c) 1994 Cisco Systems, Inc.
File IJ92130N contains an uncompressed image that supports all software
capabilities for the Cisco 3000 except booting from ROM.
To install this software in a PCDOS environment enter:
A:install (or use the appropriate drive letter)
To install this software in a UNIX environment enter:
#mount -rt pcfs /dev/fd0 /pcfs
#/pcfs/install.unx (where the user has root privileges)
To install this software onto a router, follow the procedures in the
accompanying publication, "Upgrading System Software in the Cisco 3000."
**********************************************************************
Step 4 A prompt appears asking if you want to continue with the installation. Press Y (or Enter) to continue, or N to abort.
Step 5 A prompt appears asking where the files will be installed. The default directory is C:\TFTPBOOT. To accept this directory, press Enter. To specify a different directory, type the full pathname, then press Enter.
If the nondefault directory you specify does not already exist, a message appears asking if you want to create the directory.
Step 6 To create the directory, press Y. If you do not want to create a new directory on your PC and want to abort this process, press N.
The software displays a set of messages indicating the status of the installation. The copy process takes about one minute.
Step 7 If you have multiple disks, the system prompts you to insert the second disk and press Enter.
When the process is complete, the following message appears. This example shows the 10.0(1) image for the Cisco 3000--IC10010N.
Step 8 Eject the disk from the disk drive and keep it in a safe place.
Step 9 Change to the directory in which you installed the software image. For example, if you installed it in the default directory, type the following command and press Enter:
Step 10 List the contents of the images in this directory. For example, if you installed a 10.0(1) run-from-Flash image for the Cisco 3000, type the following command and press Enter:
dir ic10010n.*
The following two files should appear:
Refer to the section "Establishing a TFTP Session" on page 12.
The following procedures describe how to install the system software upgrade onto a desktop SPARCstation with SunOS 4.1.x. The workstation must have a 3.5-inch, 1.44-MB floppy disk drive. Allow ten minutes to complete this procedure.
You must have superuser (SU) access to install the router system software to the UNIX system.
Use the following procedure to create a mount point and install the system software image on your TFTP server. Note that filenames are case sensitive.
| Caution Do not install the system software image to the TFTP server a first time, then install it again. If you do, the system appends the second image to the first image rather than writing over it, and the altered image will not function in your routers. If you want to install the image a second time, first delete the image from the destination directory on the TFTP server, then reinstall it. |
Step 1 Create a directory named pcfs as follows (you must have superuser capability to execute this instruction):
hostname# mkdir /pcfs
Step 2 Insert the disk containing the system software upgrade into your 3.5-inch floppy disk drive.
Step 3 Mount the floppy disk drive as a device by entering the following command:
hostname# mount -t pcfs /dev/fd0 /pcfs
If the disk is write-protected, you should enter the following command:
hostname# mount -rt pcfs /dev/fd0 /pcfs
The floppy is now set up as the device /pcfs.
Step 4 Copy the router system software to your TFTP directory. To copy it to the default (/tftpboot) directory, enter the following command:
hostname# /pcfs/install.unx
Step 5 A message appears prompting you to specify the device from which the software is being installed. The default is /dev/fd0. To accept the default, press Return. To specify a different directory, type the name of the built-in floppy drive on the SPARCstation.
Step 6 A message appears prompting you to specify the path from the mounted floppy drive. The default is /pcfs. To accept the default, press Return. To specify a different path, type the full pathname.
A screen similar to the following appears. This screen is for a 9.21(3) software image on a Cisco 3000. If you are upgrading to a different release of router software, the header fields (first four lines in the display) will be different.
********************** IJ92130N.DOC **********************************
PRODUCT NO. SW-G3B-9.21.3=
System Software Image IJ92130N, IGS-BPX Version 9.21(3)
Uncompressed size = 1989999 bytes; Checksum=0x5alc
Copyright (c) 1994 Cisco Systems, Inc.
File IJ92130N contains an uncompressed image that supports all software
capabilities for the Cisco 3000 except booting from ROM.
To install this software in a PCDOS environment enter:
A:install (or use the appropriate drive letter)
To install this software in a UNIX environment enter:
#mount -rt pcfs /dev/fd0 /pcfs
#/pcfs/install.unx (where the user has root privileges)
To install this software onto a router, follow the procedures in the
accompanying publication, "Upgrading System Software in the Cisco 3000."
**********************************************************************
Step 7 Print the README file screen, or note the filename, checksum, and image size on a piece of paper for later reference.
Step 8 A prompt appears asking if you want to continue with the installation. Press Y (or Enter) to continue, or N to abort.
The screen displays a set of messages indicating the status of the installation. The copy process takes five minutes.
Step 9 If you have multiple floppy disks, the system prompts you to insert the second disk and press Enter.
After the image is installed on your TFTP server, the disk is automatically ejected and the disk drive is automatically unmounted. The following message appears. This example shows the 9.21(3) image for a Cisco 3000--ij92130n.
Step 10 Eject the disk from the disk drive and keep it in a safe place.
Step 11 Change to the directory in which you installed the system software image. For example, if you installed it in the default directory, enter the following command:
hostname# cd /tftpboot
Step 12 List the contents of the images in this directory. For example, for a 9.21(3) run-from-RAM image for a Cisco 3000, enter the following command:
hostname# ls -l ij92130n.*
The following two files should appear for the 9.21 run-from-RAM image on a Cisco 3000. Other image names would be different, such as ic91460z for a 9.14(6) run-from-Flash image:
Refer to the next section, "Making Your Network Connections."
This section describes the following topics:
After installing the TCP/IP software you will use to copy the Cisco 3000 software image to the routers on your network, make sure it functions properly by following this procedure:
Step 1 Make sure a router with which you plan to communicate is up and running by transmitting an IP ping from that router to the TFTP server on the network. Use the following syntax for the ping command:
ping ip-address
If the router is appropriately connected, you see a series of exclamation points (!!!!!). However, the following messages indicate that you have no connection:
[timed out]
[failed]
Step 2 Verify the connection to the TFTP file server by transmitting a ping from the TFTP file server to the router.
If the connection fails, make sure you reconfigure the interface, check the physical connection to the TFTP file server, and retransmit the ping.
If you are using PC/TCP Network Software for DOS from FTP Software, Inc., you can verify the appropriate driver and IP address by entering the following command:
C:\> ifconfig drivers\drivername show
You can verify your IP configuration by entering the following command:
C:\> ipconfig ftp_3c\ipcust.sys show
If you are using Chameleon TCP/IP for Windows from NetManage, Inc., run its Setup program to verify that you are using the appropriate driver and have configured the TCP/IP software properly.
This section describes how to set up your UNIX system or PC as a TFTP server and start a TFTP session with the router you want to upgrade remotely.
If you are using a PC and do not already have TFTP software, we recommend the following two TCP/IP software packages:
The section "Prerequisites and Caveats" on page 4 lists some issues to keep in mind while installing the software.
To set up the Sun system as a TFTP server, you must verify that the TFTP daemon is enabled, the TFTP environment variable is set correctly, and a tftpboot directory exists. To see if TFTP is enabled, enter the following command:
hostname# netstat -a | grep tftp
If the TFTP daemon is already enabled, skip to "Creating a tftpboot Directory" on page 13.
The TFTP daemon (tftpd) permits the system to be a TFTP server. If you are using the standard Sun software, verify that tftpd is enabled by completing the following steps:
Step 1 Log in as a superuser.
Step 2 Using a text editor such as vi, edit the /etc/inetd.conf file.
Step 3 Look in the file /etc/inetd.conf for the line that invokes tftpd. If the line is commented out (starts with a pound sign [#]), remove the pound sign with an editor. This example shows sample output for the /etc/inetd.conf file.
# tftp dgram udp wait root /user/etc/in.tftpd
in.tftpd -s /tftpboot
Step 4 Save the changes in the edited file and exit.
Step 5 At the UNIX prompt, enter the following command to display the process ID number for the inetd configuration:
ps -ax | grep -v grep | grep inetd
The system response is similar to the following:
The first number in the output is the process ID of the inetd process. You must kill this inetd process by entering the following command:
kill -HUP 119
Step 6 Verify that TFTP is enabled by entering the following command:
netstat -a | grep tftp
The output should be similar to the following:
If there is no output, tftpd is not enabled. For additional information about TFTP, refer to the UNIX man pages about tftp and tftpd.
The tftpboot directory can be used to save and store configuration files that are loaded to a device. Device configuration files can be saved as TFTP boot files.
You must have superuser (SU) access to perform the following steps. These steps describe how to create a tftpboot directory.
Step 1 If the tftpboot directory does not exist, use the following command to create it:
hostname# mkdir /tftpboot
Step 2 The tftpboot directory must have the appropriate permissions. Modify the permissions with the following command:
hostname# chmod 777 /tftpboot
As a result, all users accessing this directory will have read, write, and execute permissions.
After completing all the preparations required to set up the Sun system as a TFTP server, refer to "Testing the TCP/IP Software" on page 11.
You must be able to issue commands to the router you plan to upgrade. For example, this publication will tell you to issue a command to download the image from the TFTP server to the router.
If you have a console port connection to the router, you need not invoke a Telnet session.
If you do not have a console port connection to the router, you must establish a Telnet session with it so that you can issue commands.
You can set up a Telnet session from a Sun workstation or from a PC.
This section describes how to load your Cisco 3000 software image. The first section describes the steps for loading run-from-Flash images. The next describes how to load run-from-RAM software images. Read the section appropriate to your type of software image.
This section describes how to load a run-from-Flash software image onto a Cisco 3000 router. Specifically, it presents the following topics:
If you do not already have the current system software image on your TFTP server, make sure you back up this image before copying the new system software image to Flash memory on your router.
First, you must know the exact spelling of the image name. To learn the image name, issue the show flash all command. The following sample output for a compressed Cisco 3000 image (System Software Release 9.14(4)) displays an image name of ic91440z near the bottom of the screen.
router# show flash all
2048K bytes of Flash address space sized on CPU board.
Memory type is Flash.
Chip socket code bytes name
0 U42 89BD 0x040000 INTEL 28F020
1 U44 89BD 0x040000 INTEL 28F020
2 U46 89BD 0x040000 INTEL 28F020
3 U48 89BD 0x040000 INTEL 28F020
4 U41 89BD 0x040000 INTEL 28F020
5 U43 89BD 0x040000 INTEL 28F020
6 U45 89BD 0x040000 INTEL 28F020
7 U47 89BD 0x040000 INTEL 28F020
Flash address space file directory:
File name/status
addr length fcksum ccksum
0 ic91440z
0x3000040 1337256 0x5A1C 0x5A1C
[759832/2097152 bytes free/total]
router#
Use the name near the bottom of your router's show flash all command (in this case, xk91420z) when you back up the image.
To copy an image from Flash memory to a TFTP server, use the copy flash tftp command:
router# copy flash tftp filename
The router asks you for the IP address of the TFTP server and the name of the image file you are copying to the server.
A sample of the output for this command using IP address 131.108.10.6 and filename ic92130n follows:
IP address of remote host [255.255.255.255]?131.108.10.6Name of file to copy []?ic92130nwriting ic92130n !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! router#
Use the image you backed up to the TFTP server in case the upgrade image becomes damaged.
To reboot the router to the boot ROM prompt, you first set the configuration register to 0x101, then issue the reload command, as shown in the following example. This example shows the command parser for Software Release 9.21 and later.
router#configure terminalEnter configuration commands, one per line. Edit with DELETE, CTRL/W, and CTRL/U; end with CTRL/Zrouter(config)#config-reg 0x101router(config)#^Zrouter# %SYS-5-CONFIG_I: Configured from console by console () router#reload[confirm]
If the following message appears, you can ignore it:
Bad arguments to line command
If you had connected to the router using Telnet, your Telnet session is disconnected after the router is reloaded. Wait for the router to complete reloading and log in to it again. When you do, the following prompt appears:
router(boot)#
| Caution While at the boot ROM prompt, do not change your configuration. If you have to change something in the configuration, return to the full system image (operating mode). You could make the change while at the boot ROM prompt, but do not save the changes to NVRAM. Saving configuration changes to NVRAM while at the boot ROM prompt permanently erases your original router configuration file. |
The copy tftp flash command retrieves an image from a TFTP server and copies (writes) the image into the router's Flash memory. The TFTP server can be another Cisco router serving ROM or Flash system software images, or a PC or UNIX workstation set up as a server for remotely downloading new images to routers on the network. If you have already established a connection with the remote server, refer to "Loading a Run-from-Flash Software Image" on page 14.
In some cases, primarily outside of North America, Cisco Systems distributors may choose not to distribute the new software image on floppy disk. Instead, they can place the new image on TFTP servers and provide their customers with the information they will need to access and download the new image. If you are downloading the new image from your distributor with this process, ensure that your distributor has provided you with all of the following information:
You must have all of this information from your distributor before you can complete the upgrade. Refer to the next section, "Verifying the Connection (Run-from-Flash)."
Verify the connection between your router and the remote server by pinging the server using the IP address (this may be provided by your distributor). Following is an example of a successful ping command to a remote server with the address 131.131.101.101:
router(boot)#ping 131.131.101.101<Return>Type escape sequence to abort. Sending 5, 100-byte ICMP Echoes to 131.131.101.101, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/15/64 ms router(boot)#
The console displays either a series of exclamation points (!!!!!) to indicate a good connection between your router and the server or a series of periods (.....) or the messages [timed out] or [failed] to indicate that the connection failed. If the connection fails, verify that you have the correct IP address for the server and that the server is active (powered on), and repeat the ping command.
To download the new image from the TFTP server to your router, issue the copy tftp flash command. When you do, you are prompted for the IP address (or domain name) of the TFTP server. This can be another Cisco router serving ROM or Flash system software images. You are then prompted for the filename of the software image and given the option to erase the existing Flash memory. Type Y. The filename can be lower- or uppercase; the router will see the name as lowercase. The system clears and initializes Flash memory. The entire copying process takes several minutes. This time differs from network to network.
| Caution Do not make any typographical errors while using the copy tftp flash command in selecting the filename of the system software image you are copying. If you type a filename that does not exist when using the copy tftp flash command, then tell the system to erase the current image, the router erases the existing image in Flash memory. If this happens, you will not have a functional image in Flash memory and when you boot the router from Flash, it will not boot and will have to be reconfigured from a direct console-port connection. To make sure your image is a good one, refer to the following section "Verifying Run-from-Flash Images in Flash Memory." |
The following sample output shows a system image named ic91470n copied into the current Flash configuration:
router(boot)#copy tftp flashFile name/status 0 igs-bfpx.914-11 [123816/2097152 bytes free/total] IP address or name of remote host [255.255.255.255]?131.108.1.111Name of file to copy?ic91470nCopy ic91470n from 131.108.1.111 into Flash address space? [confirm] <Return> 123752 bytes available for writing without erasure. Erase Flash address space before writing? [confirm] <Return> bank 0...zzzzzzzzzzzzzzzzvvvvvvvvvvvvvvvveeeeeeeeeeeeeeee bank 1...zzzzzzzzzzzzzzzzvvvvvvvvvvvvvvvveeeeeeeeeeeeeeee Loading from 131.108.1.111: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK - 1337256/2097088 bytes] Verify checksum...vvvvvvvvvvvvvvvvvvvv Verification successful: Length = 1999845, checksum = 0x5A1C
The series of exclamation points (!) in the preceding sample output indicates that the copying process is taking place. The series of Vs indicates that a checksum is being calculated. The last line in the sample configuration indicates that the file transfer is complete.
If the process was successful, refer to the next section, "Verifying Run-from-Flash Images in Flash Memory." If it was not successful, refer to the section "Recovering from a Flash Memory Failure" on page 24.
Before booting from Flash memory, you must verify that the checksum of the compressed image shown at the bottom of the screen after you issue the copy tftp flash command matches the checksum listed in the README file on the software upgrade disk.
If the checksum value is not correct according to the value in the README file on the system upgrade disk, enter the copy tftp flash command and compare the checksums again. If the checksum is repeatedly wrong, copy the original system software image back into Flash memory before you reboot the router from Flash memory.
Before your router can return to normal operation, you must change the configuration register back to its original state (the boot-from-Flash setting is 0x102) and reload the router, as shown in the following example:
router(boot)#configure terminalEnter configuration commands, one per line. Edit with DELETE, CTRL/W, and CTRL/U; end with CTRL/Zrouter(config)#config-reg 0x102router(config)#^Zrouter# %SYS-5-CONFIG_I: Configured from console by console () router#reload[confirm]
After the router is reloaded with the new software, be sure to make the following changes:
At this point, ensure that your router is set to boot from Flash memory. Refer to the section "Booting from Flash Memory" on page 22."
This section describes how to load a run-from-RAM software image onto a Cisco 3000 router. Specifically, it presents the following topics:
If you do not already have the current system software image on your TFTP server, make sure you back up this image before copying the new system software image to Flash memory on your router.
First, you must know the exact spelling of the image name. To learn the image name, issue the show flash all command. The following sample output for a compressed Cisco 3000 image (System Software Release 9.14(4)) displays an image name of ij91440z near the bottom of the screen.
router# show flash all
2048K bytes of Flash address space sized on CPU board.
Memory type is Flash.
Chip socket code bytes name
0 U42 89BD 0x040000 INTEL 28F020
1 U44 89BD 0x040000 INTEL 28F020
2 U46 89BD 0x040000 INTEL 28F020
3 U48 89BD 0x040000 INTEL 28F020
4 U41 89BD 0x040000 INTEL 28F020
5 U43 89BD 0x040000 INTEL 28F020
6 U45 89BD 0x040000 INTEL 28F020
7 U47 89BD 0x040000 INTEL 28F020
Flash address space file directory:
File name/status
addr length fcksum ccksum
0 ij91440z
0x3000040 1337256 0x5A1C 0x5A1C
[759832/2097152 bytes free/total]
router#
Use the name near the bottom of your router's show flash all command (in this case, ij91440z) when you back up the image.
To copy an image from Flash memory to a TFTP server, use the copy flash tftp command:
router# copy flash tftp filename
The router asks you for the IP address of the TFTP server and the name of the image file you are copying to the server.
A sample of the output for this command using IP address 131.108.10.6 and filename ij92130n follows:
IP address of remote host [255.255.255.255]?131.108.10.6Name of file to copy []?ij92130nwriting ic92130n !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! router#
Use the image you backed up to the TFTP server in case the upgrade image becomes damaged.
The copy tftp flash command retrieves an image from a TFTP server and copies (writes) the image into the router's Flash memory. The TFTP server can be another Cisco router serving ROM or Flash system software images, or a PC or UNIX workstation set up as a server for remotely downloading new images to routers on the network. If you have already established a connection with the remote server, refer to "Loading a Run-from-RAM Image" on page 18.
In some cases, primarily outside of North America, Cisco Systems distributors may choose not to distribute the new software image on floppy disk. Instead, they can place the new image on TFTP servers and provide their customers with the information they will need to access and download the new image. If you are downloading the new image from your distributor with this process, ensure that your distributor has provided you with all of the following information:
You must have all of this information from your distributor before you can complete the upgrade. Refer to the next section, "Verifying the Connection (Run-from-RAM)."
Verify the connection between your router and the remote server by pinging the server using the IP address (this may be provided by your distributor). Following is an example of a successful ping command to a remote server with the address 131.131.101.101:
router(boot)#ping 131.131.101.101<Return>Type escape sequence to abort. Sending 5, 100-byte ICMP Echoes to 131.131.101.101, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/15/64 ms router(boot)#
The console displays either a series of exclamation points (!!!!!) to indicate a good connection between your router and the server or a series of periods (.....) or the messages [timed out] or [failed] to indicate that the connection failed. If the connection fails, verify that you have the correct IP address for the server and that the server is active (powered on), and repeat the ping command.
To download the new image from the TFTP server to your router, issue the copy tftp flash command. When you do, you are prompted for the IP address (or domain name) of the TFTP server. This can be another Cisco router serving ROM or Flash system software images. You are then prompted for the filename of the software image and given the option to erase the existing Flash memory. Type Y. The filename can be lower- or uppercase; the router will see the name as lowercase. The system clears and initializes Flash memory. The entire copying process takes several minutes. This time differs from network to network.
| Caution Do not make any typographical errors while using the copy tftp flash command in selecting the filename of the system software image you are copying. If you type a filename that does not exist when using the copy tftp flash command, then tell the system to erase the current image, the router erases the existing image in Flash memory. If this happens, you will not have a functional image in Flash memory and when you boot the router from Flash, it will not boot and will have to be reconfigured from a direct console-port connection. To make sure your image is a good one, refer to the following section "Verifying the Run-from-RAM Software Image in Flash Memory." |
The following sample output shows a system image named ij91470n copied into the current Flash configuration:
router(boot)#copy tftp flashFile name/status 0 igs-bpx.914-11 [123816/2097152 bytes free/total] IP address or name of remote host [255.255.255.255]?131.108.1.111Name of file to copy?ij91470nCopy ij91470n from 131.108.1.111 into Flash address space? [confirm] <Return> 123752 bytes available for writing without erasure. Erase Flash address space before writing? [confirm] <Return> bank 0...zzzzzzzzzzzzzzzzvvvvvvvvvvvvvvvveeeeeeeeeeeeeeee bank 1...zzzzzzzzzzzzzzzzvvvvvvvvvvvvvvvveeeeeeeeeeeeeeee Loading from 131.108.1.111: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK - 1337256/2097088 bytes] Verify checksum...vvvvvvvvvvvvvvvvvvvv Verification successful: Length = 1999845, checksum = 0x5A1C
The series of exclamation points (!) in the preceding sample output indicates that the copying process is taking place. The series of Vs indicates that a checksum is being calculated. The last line in the sample configuration indicates that the file transfer is complete.
If the process was successful, refer to the next section, "Copying the Run-from-RAM Image from a TFTP Server to Flash Memory." If it was not successful, refer to the section "Recovering from a Flash Memory Failure" on page 24.
Before booting from Flash memory, you must verify that the checksum of the compressed image shown at the bottom of the screen after you issue the copy tftp flash command matches the checksum listed in the README file on the software upgrade disk.
If the checksum value is not correct according to the value in the README file on the system upgrade disk, enter the copy tftp flash command and compare the checksums again. If the checksum is repeatedly wrong, copy the original system software image back into Flash memory before you reboot the router from Flash memory.
At this point, ensure that your router is set to boot from Flash memory. Refer to the following section "Booting from Flash Memory."
The following sections describe how to boot from Flash, both automatically and manually. The Cisco 3000 offers both run-from-Flash and run-from-RAM software images. The process of booting the router in each case is the same, though the router processes the different images as follows:
| Caution If the NVRAM-stored configuration file on your router has the line boot system flash filename, then each time you write a new software image to Flash memory, you must delete this line by issuing the no boot system flash filename system configuration command. Then add a line that reads boot system flash or boot system flash filename, where the filename is the exact name of the new system software image. If you do not do this, the router will repeatedly try to reboot from the now-erased file. If the configuration file includes boot system flash with no argument, you do not need to take these steps. In this case, the router will boot from the first system image in Flash memory by default. |
From the enable-mode prompt on the router, enter the EXEC command write terminal to see whether the boot system flash command line in the configuration file has the filename argument, as follows:
router> enable
Password:
router# wr term
Current configuration:
!
(text deleted)
boot system flash
(text deleted)
You can configure the router to automatically boot from the image in Flash memory by following this procedure:
Step 1 Issue the configure terminal command in EXEC mode (at the enable [#] prompt).
Step 2 Add the boot system flash filename system configuration command to the router's configuration, where filename is the name of the new software image. If a filename already appears in the configuration file, remove it with the no boot system flash filename command.
Step 3 Make sure the configuration register is set to 0x102. This command causes the router to be booted from Flash memory and the Break key to be ignored.
Step 4 Write the configuration to NVRAM with the write memory command.
The following example shows the sequence of steps for replacing a 9.21(3) image with a 10.0(2) image. If you are replacing different images, substitute the different image names.
configure terminal
write memory
Step 5 At this point, you can reboot the router with the reload command. The router will boot the new software image from Flash memory. The following example shows the output of the reload command.
reload
If you do not have your router set up to automatically boot from Flash, as specified in the previous section, you can manually boot a run-from-RAM image from Flash by following this procedure.
Step 1 Make sure the configuration register on the router is set to boot from ROM when you reboot the router using the reload command. If you are not sure whether this value is correct on your router, enter configuration mode and issue the config-reg 0x0 command. This setting causes the system to boot into ROM monitor level.
Step 2 Write this configuration to NVRAM by issuing the write-memory EXEC command.
Step 3 Enter privileged user mode and issue the reload command, as specified in the previous section.
Step 4 The system enters ROM monitor level. At this point, initialize the system by typing i at the ROM monitor prompt, as shown in the following example:
i
Step 5 Boot the router manually by issuing the b flash command.
b flash
Cisco Systems, Inc.
170 W. Tasman Drive
San Jose, California
If the image fails to load properly into Flash memory, the following error message appears:
Error programming flash memory
If you try loading the image into Flash memory three or more times and repeatedly see this message, contact technical support immediately and inform them of the situation. In an attempt to recover from the error, you can also repeat the upgrade procedure described in this publication.
Before repeating the system software upgrade process on subsequent machines, make sure the upgraded router functions properly by performing the following steps:
Step 1 Ping from the upgraded router to a system on the local network to make sure you have network connectivity. Refer to "Testing the TCP/IP Software" on page 11.
Step 2 Look at the routing tables in the updated router. To review all of the routes established in your router, issue the show route EXEC command, which has the following syntax: show protocol route network.
Step 3 Make sure the upgraded router is listed properly in the routing tables of nearby routers.
Only if the ping and show route commands generate positive results should you upgrade subsequent routers.
This section provides information for obtaining technical assistance.
Cisco Systems' Customer Information Online (CIO) system provides online information and electronic services to Cisco direct customers and business partners. Basic CIO services include general Cisco information, product announcements, descriptions of service offerings, and download access to public and authorized files, including release notes, and software. Maintenance customers receive a much broader offering, including technical notes, the bug database, and electronic mail access to the TAC. (Maintenance customers must have authorization from their Cisco contract administrators to receive these privileges.)
For dialup or Internet users, CIO supports Zmodem, Kermit, Xmodem, FTP PUT, Internet e-mail, Telnet, rlogin, and fax download options. Internet users also can retrieve files from CIO using FTP.
Registration for CIO is handled on line. To reach CIO via the Internet, use Telnet or FTP to cio.cisco.com (131.108.89.33). To reach CIO by dialup, use 415 903-8070 (Mountain View, California) or 33 1 6446 4082 (Paris, France).
|
|