Table Of Contents
Loading and Maintaining System Images and Microcode
System Images and Microcode Task List
Display System Image Information
Copy Operation General Output Conventions
Copy Images from Flash Memory to a Network Server
Copy an Image from Flash Memory to a TFTP Server
Copy an Image from Flash Memory to an rcp Server
Copy from Flash Memory to an rcp Server Tasks
Copy an Image from Flash Memory to an FTP Server
Understand the FTP Username and Password
Copy from Flash Memory to an FTP Server Tasks
Copy Images from a Network Server to Flash Memory
Understand Flash Memory Space Considerations
Output for Image Downloading Process
Output for Partitioned Flash Memory
Copy to Flash Memory Tasks for Run-from-Flash Systems
Copy an Image from a TFTP Server to a Flash Memory File System
Copy an Image from an rcp Server to a Flash Memory File System
Copy from an rcp Server to Flash Memory Tasks
Copy an Image from an FTP Server to a Flash Memory File System
Understand the FTP Username and Password
Copy from an FTP Server to Flash Memory Tasks
Verify the Image in Flash Memory
Copy Images between Local Flash Memory Devices
Specify the Startup System Image in the Configuration File
Load the System Image from Flash Memory
Flash Memory Configuration Process
Configure the Router to Automatically Boot from an Image in Flash Memory
Load the System Image from a Network Server
Load the System Image from ROM
Use a Fault-Tolerant Booting Strategy
Recovering a System Image Using Xmodem or Ymodem
Xmodem Transfer Example Using the Cisco IOS Software
(Cisco 3600 series only)Xmodem Transfer Example Using the ROM Monitor
Load and Display Microcode Images
Specify the Location of the Microcode Images
Display Microcode Image Information
Load Cisco IOS Images on the Cisco 12000 GSR
Set the LED Message on a Line Card
Loading and Maintaining System Images and Microcode
This chapter describes how to load and maintain system images and microcode. System images contain the system software. Microcode images contain microcode to be downloaded to various hardware devices.
To benefit most from the instructions and organization of this chapter, your router must contain a minimal configuration that allows you to interact with the system software. You can create a basic configuration file using the setup command facility. See the user guide for your hardware platform for more information on using setup at first-time startup. See the "Using Setup for Configuration Changes" chapter in this publication for information on using setup after first-time startup.
For a complete description of the system image and microcode commands mentioned in this chapter, refer to the "System Image and Microcode Commands" chapter in the Configuration Fundamentals Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
Note
One or more of the commands that previously appeared in this chapter have been replaced by new commands. maps the old commands to their replacements. The old commands continue to perform their normal functions in the current release, but support for these commands will cease in a future release.
System Images and Microcode Task List
You can perform the tasks involving images described in the following sections:
•
•
•
•
•
•
•
•
•
Note
Display System Image Information
Use the following commands in EXEC mode to display information about system software:
Refer to the Configuration Fundamentals Command Reference for examples of these commands.
Understand Images
System images contain the Cisco IOS software. Your router already has an image on it when you receive it. However, you may want to load a different image onto the router at some point. For example, you may wish to upgrade your software to the latest release or use the same version of the software for all the routers in a network.
Types of Images
The following are two main types of images your router may use:
•
On most platforms, the image is located in Flash memory. On platforms with multiple Flash memory file systems (Flash, Bootflash, slot 0, or slot 1), the image can be located in any existing Flash file system. Use the show file systems command to determine which file systems your router supports. Refer to your hardware documentation for information about where these images are located by default.
•
On some platforms, the boot image is contained in ROM. In others, the boot image can be stored in Flash memory. On these platforms, you can specify which image should be used as the boot image using the boot bootldr command.
Refer to your hardware documentation for information about the boot image used on your router.
Image Naming Conventions
You can identify the platform, features, and image location by the name of the image. The naming convention for images that are stored on a UNIX system is as follows:
platform-features-type
The platform variable indicates which platforms can use this image. Examples of platform variables are rsp (Cisco 7000 series with RSP7000 and Cisco 7500 series), c1600 (Cisco 1600 series), and c1005 (Cisco 1005).
The feature variable identifies the feature sets supported by the image.
The type field can contain the following characters:
•
•
•
•
•
•
Copy Operation General Output Conventions
During a copy operation, you may get the following characters:
•
•
•
•
•
The last line in the output indicates whether or not the copy was successful.
To interrupt a copy operation, press Ctrl-^ or Ctrl-Shift-6. The operation terminates, but any partial file copied remains until Flash memory is erased.
Refer to the Internetwork Troubleshooting Guide publication for procedures on how to resolve Flash memory problems.
Copy Images from Flash Memory to a Network Server
You can copy system images from Flash memory to an FTP, rcp, or TFTP server. You can use this server copy of the system image as a backup copy, or you can use it to verify that the copy in Flash is the same as the original file on disk. The following sections describe these tasks:
•
•
•
The protocol you use depends on which type of server you are using. The FTP and rcp transport mechanisms provide faster performance and more reliable delivery of data than TFTP. These improvements are possible because the FTP and rcp transport mechanisms are built on and use the Transmission Control Protocol/Internet Protocol (TCP/IP) stack, which is connection-oriented.
To stop the copy process, press Ctrl-^ or Ctrl-Shift-6.
In the output, an exclamation point (!) indicates that the copy process is taking place. Each exclamation point (!) indicates that ten packets have been transferred successfully.
Refer to the Internetwork Troubleshooting Guide publication for procedures on how to resolve Flash memory problems.
Copy an Image from Flash Memory to a TFTP Server
You can copy a system image to a TFTP network server. In some implementations of TFTP, you must first create a "dummy" file on the TFTP server and give it read, write, and execute permissions before copying a file over it. Refer to your TFTP documentation for more information.
To copy a system image to a TFTP network server, use the following commands in EXEC mode:
Copy from Flash Memory to a TFTP Server Example
The following example uses the show flash: command to learn the name of the system image file and the copy flash: tftp: command to copy the system image to a TFTP server.
RouterB# show flash:System flash directory:File Length Name/status1 4137888 c3640-c2is-mz.Feb24[4137952 bytes used, 12639264 available, 16777216 total]16384K bytes of processor board System flash (Read/Write)\Router# copy flash: tftp:IP address of remote host [255.255.255.255]? 172.16.13.110filename to write on tftp host? c3640-c2is-mz.Feb24writing c3640-c2is-mz.Feb24 !!!!...successful tftp write.Copy from Partitioned Flash Memory to a TFTP Server Example
In this example, the file your-ios is copied from partition 1 of the Flash memory PC card in slot 0 to the TFTP server at 172.23.1.129. The file will be saved with the name your-ios in the dirt/sysadmin directory relative to the directory of the remote username.
Router# copy slot0:1:your-ios tftp://172.23.1.129/dirt/sysadmin/your-iosVerifying checksum for 'your-ios' (file # 1)... OKCopy 'your-ios' from Flash to serveras 'dirt/sysadmin/ios-2'? [yes/no] yes!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Upload to server doneFlash device copy took 00:00:23 [hh:mm:ss]Copy an Image from Flash Memory to an rcp Server
You can copy a system image from Flash memory to an rcp network server.
If you copy the configuration file to a personal computer used as a file server, the computer must support rsh.
Understand the rcp Username
The rcp protocol requires a client to send a remote username on each rcp request to a server. When you copy an image from the router to a server using rcp, the Cisco IOS software sends the first valid username in the following list:
1
2
3
4
For the rcp copy request to execute successfully, an account must be defined on the network server for the remote username. If the server has a directory structure, the configuration file or image is written or copied relative to the directory associated with the remote username on the server. The path for all files and images to be copied begins at the remote user's home directory. For example, if the system image resides in the home directory of a user on the server, specify that user's name as the remote username.
If you are writing to the server, the rcp server must be properly configured to accept the rcp write request from the user on the router. For UNIX systems, you must add an entry to the .rhosts file for the remote user on the rcp server. For example, suppose the router contains the following configuration lines:
hostname Rtr1ip rcmd remote-username User0If the router's IP address translates to Router1.domain.com, then the .rhosts file for User0 on the rcp server should contain the following line:
Router1.domain.com Rtr1Refer to the documentation for your rcp server for more details.
Copy from Flash Memory to an rcp Server Tasks
To copy the system image from Flash memory to a network server, use the following commands:
Copy from Flash to RCP Server Example
The following example copies the system image c5200-ds-l to the network server at 172.16.1.111 using rcp and a username of netadmin:
Router# copy flash:c5200-ds-l rcp:netadmin1@172.16.1.111/c5200-ds-lVerifying checksum for `c5200-ds-l' (file # 1)...[OK]Writing c5200-ds-l -Copy from Slot1 to RCP Server Example
The following example copies a system image file called test from the second PCMCIA slot to a network server using rcp. The remote username is netadmin1. Because the destination address and filename are not specified, the router prompts for this information.
Router# configure terminalRouter(config)# ip rcmd remote-username netadmin1Router(config)# endRouter# copy slot1:test rcp:Address or name of remote host [UNKNOWN]? 172.16.1.111File name to write to? testVerifying checksum for `test' (file # 1)...[OK]Writing test!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Upload to server doneFlash device copy took 00:00:08 [hh:mm:ss]Copy an Image from Flash Memory to an FTP Server
You can copy a system image to an FTP network server.
Understand the FTP Username and Password
The FTP protocol requires a client to send a remote username and password on each FTP request to a server. When you copy a configuration file from the router to a server using FTP, the Cisco IOS software sends the first valid username in the following list:
1
2
3
The router sends the first valid password in the following list:
1
2
3
The username and password must be associated with an account on the FTP server. If you are writing to the server, the FTP server must be properly configured to accept the FTP write request from the user on the router.
If the server has a directory structure, the configuration file or image is written to or copied from the directory associated with the username on the server. For example, if the system image resides in the home directory of a user on the server, specify that user's name as the remote username.
Refer to the documentation for your FTP server for more details.
Use the ip ftp username and ip ftp password commands to specify a username and password for all copies. Include the username in the copy command if you want to specify a username for that copy operation only.
Copy from Flash Memory to an FTP Server Tasks
To copy a system image to an FTP network server, use the following commands in EXEC mode:
Copy from Flash Memory to an FTP Server Example
The following example uses the show flash: command to learn the name of the system image file and the copy flash: tftp: command to copy the system image (c3640-2is-mz) to a TFTP server. The router uses the default username and password.
Router# show flash:System flash directory:File Length Name/status1 4137888 c3640-c2is-mz[4137952 bytes used, 12639264 available, 16777216 total]16384K bytes of processor board System flash (Read/Write)\Router# copy flash: tftp:IP address of remote host [255.255.255.255]? 172.16.13.110filename to write on tftp host? c3600-c2is-mzwriting c3640-c2is-mz !!!!...successful ftp write.Copy from Slot1 to an FTP Server Example
The following example uses the show slot1: command to display the name of the system image file in the second PCMCIA slot and the copies the file (test) to an FTP server.
Router# show slot1:-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name1 .. 1 46A11866 2036C 4 746 May 16 1995 16:24:37 testRouter# copy slot1:test ftp://thisuser:thatpass@172.16.13.110/testwriting test!!!!...successful ftp write.Copy from Partitioned Flash to an FTP Server Example
In this example, the file your-ios is copied from partition 1 of the Flash memory PC card in slot 0 to the TFTP server at 172.23.1.129. The file will be saved with the name your-ios in the dirt/sysadmin directory relative to the directory of the remote username.
Router#show slot0: partition 1PCMCIA Slot0 flash directory, partition 1:File Length Name/status1 1711088 your-ios[1711152 bytes used, 2483152 available, 4194304 total]Router# copy slot0:1:your-ios ftp://myuser:mypass@172.23.1.129/dirt/sysadmin/your-iosVerifying checksum for 'your-ios' (file # 1)... OKCopy 'your-ios' from Flash to serveras 'dirt/sysadmin/ios-2'? [yes/no] yes!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Upload to server doneFlash device copy took 00:00:23 [hh:mm:ss]Copy Images from a Network Server to Flash Memory
You can copy system images or boot image from a TFTP, rcp, or FTP server to a Flash memory file system to upgrade or change the Cisco IOS software or boot image on your router.
The protocol you use depends on which type of server you are using. The FTP and rcp transport mechanisms provide faster performance and more reliable delivery of data than TFTP. These improvements are possible because the FTP and rcp transport mechanisms are built on and use the Transmission Control Protocol/Internet Protocol (TCP/IP) stack, which is connection-oriented.
The following sections describe the copying tasks. The first two tasks and the last task are required. If you have a run-from-Flash system, the third section is required. Perform one of the remaining tasks, depending on which file transfer protocol you use.
•
•
•
•
•
•
•
Note
Restrictions on File Naming
Filenames in Flash memory can be up to 63 characters long; they are not case-sensitive and are always converted to lowercase.
Note
The filename can be in either lowercase or uppercase; the system ignores case. If more than one file of the same name is copied to Flash, regardless of case, the last file copied becomes the valid file.
Understand Flash Memory Space Considerations
Be sure there is enough space available before copying a file to Flash memory. Use the show flash-filesystem: command, and compare the size of the file you want to copy to the amount of Flash memory available. If the space available is less than the amount needed, the copy command is partially executed, but the entire file is not copied into Flash memory. The failure message "buffer overflow - xxxx/xxxx" appears, where xxxx/xxxx is the number of bytes read from the source file and the number of bytes available on the destination device.
CautionDo not reboot the router if there is no valid image in Flash memory.
Note
On Cisco 2500, Cisco 3000, and Cisco 4000 systems, if the file being downloaded to Flash memory is an uncompressed system image, the copy command automatically determines the size of the file being downloaded and validates it with the space available in Flash memory.
On Class B Flash file systems, the router gives you the option of erasing the existing contents of Flash memory before writing to it. If there is no free Flash memory available, or if no files have ever been written to Flash memory, the erase routine is required before new files can be copied. If there is enough free Flash memory, the router gives you the option of erasing the existing Flash memory before writing to it. The system will inform you of these conditions and prompt you for a response.
Note
If you attempt to copy a file into Flash memory that is already there, a prompt informs you that a file with the same name already exists. This file is "deleted" when you copy the new file into Flash.
•
•
You can copy normal or compressed images to Flash memory. You can produce a compressed system image on any UNIX platform using the compress command. Refer to your UNIX platform's documentation for the exact usage of the compress command.
On some platforms, the Flash security jumper must be installed in order to write to Flash memory. In addition, some platforms have a write protect switch which must be set to unprotected in order to write to Flash memory.
Output for Image Downloading Process
The output and dialogue may vary depending on the platform.
Output for Partitioned Flash Memory
One of the following prompts displayed after the command indicates how the file can be downloaded:
•
•
•
•
If the file can be downloaded into more than one partition, you are prompted for the partition number. To obtain help, enter any of the following at the partition number prompt:
•
•
•
•
Copy to Flash Memory Tasks for Run-from-Flash Systems
You cannot run the system from Flash memory and copy to it at the same time. Therefore, for systems that run from Flash, do one of the following before copying to Flash:
•
•
Refer to "Compare Types of Memory" section in the "Maintaining Router Memory" chapter of the Configuration Fundamentals Configuration Guide for more information on run-from-Flash systems.
Refer to the appropriate hardware installation and maintenance publication for information about the jumper settings required for your configuration.
Copy an Image from a TFTP Server to a Flash Memory File System
To copy a system image from a Trivial File Transfer Protocol (TFTP) server to a Flash memory file system, use the following commands in EXEC mode:
1
See the instructions in the section "Copy Images from Flash Memory to a Network Server."
Make a backup copy of the current software image or bootstrap image.
2
copy tftp:[[[//location]/directory]/filename] flash-filesystem:[filename]
Copy a system image or a boot image to Flash memory.
3
Reply to any router prompts for additional information or confirmation. The prompting will depending on how much information you provide in the copy command and the current setting of the file prompt command.
Copy from a TFTP Server to Flash Memory Example
In the following example, a file is copied from a TFTP server to slot1:
Router# copy tftp://theserver/tftpboot/kristen/ken/c7200-js-mz slot1:Destination filename [c7200-js-mz]?Accessing tftp://theserver/tftpboot/kristen/ken/c7200-js-mz...Translating "theserver"...domain server (192.168.2.132) [OK]Loading tftpboot/kristen/ken/c7200-js-mz from 192.168.2.132 (via Ethernet3/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 4823492/9646080 bytes]4823492 bytes copied in 264.312 secs (18270 bytes/sec)The following example copies a system image named igs-p-l from a TFTP server to a Class B Flash file system when Flash memory is too full to copy the file.
Router# copy tftp: flash:IP address or name of remote host [255.255.255.255]? dirtTranslating "DIRT"...domain server (255.255.255.255) [OK]Name of file to copy? igs-p-lCopy igs-p-l from 172.16.13.111 into flash memory? [confirm]Flash is filled to capacity.Erasure is needed before flash may be written.Erase flash before writing? [confirm]Erasing flash EPROMs bank 0Zeroing bank...zzzzzzzzzzzzzzzzVerify zeroed...vvvvvvvvvvvvvvvvErasing bank...eeeeeeeeeeeeeeeeErasing flash EPROMs bank 1Zeroing bank...zzzzzzzzzzzzzzzzVerify zeroed...vvvvvvvvvvvvvvvvErasing bank...eeeeeeeeeeeeeeeeErasing flash EPROMs bank 2Zeroing bank...zzzzzzzzzzzzzzzzVerify zeroed...vvvvvvvvvvvvvvvvErasing bank...eeeeeeeeeeeeeeeeErasing flash EPROMs bank 3Zeroing bank...zzzzzzzzzzzzzzzzVerify zeroed...vvvvvvvvvvvvvvvvErasing bank...eeeeeeeeeeeeeeeeLoading from 172.16.1.111:!!!!...[OK - 1906676/4194240 bytes]Verifying via checksum...vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvFlash verification successful. Length = 1906676, checksum = 0x12ADCopy from a TFTP Server to Flash Example When File by the Same Name Already Exists
The following example shows how to copy a system image named igs-p-l into the current Flash configuration in which a file named igs-p-l already exists:
Router# copy tftp://172.16.13.111/igs-p-l flash:igs-p-lFile igs-p-l already exists; it will be invalidated!Copy igs-p-l from 172.16.13.111 into flash memory? [confirm]2287500 bytes available for writing without erasure.Erase flash before writing? [confirm]nLoading from 172.16.1.111:!!!!...[OK - 1906676/2287500 bytes]Verifying via checksum...vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvFlash verification successful. Length = 1902192, checksum = 0x12ADCopy from TFTP Server to Flash Example without Security Jumper Installed
In the following example, the Flash security jumper is not installed, so you cannot write files to Flash memory.
Router# copy tftp: flash:Flash: embedded flash security jumper(12V)must be strapped to modify flash memoryCopy from TFTP Server to Partitioned Flash Example
In the following example, the file c3600-i-mz on the TFTP server at 172.23.1.129 is copied to the first partition of internal Flash Memory.
Router# copy tftp://172.23.1.129/c3600-i-mz flash:1:c3600-i-mz/c3600-i-mzAccessing file 'c3600-i-mz' on 172.23.1.129...Loading c3600-i-mz from 172.23.1.129 (via Ethernet1/0): ! [OK]Erase flash device before writing? [confirm]Flash contains files. Are you sure you want to erase? [confirm]Copy 'c3600-i-mz' from serveras 'c3600-i-mz' into Flash WITH erase? [yes/no] yesErasing device... eeeeeeeeeeeeeeee ...erasedLoading c3600-i-mz from 172.23.1.129 (via Ethernet1/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 1711088/4194304 bytes]Verifying checksum... OK (0xF89A)Flash device copy took 00:00:17 [hh:mm:ss]Copy an Image from an rcp Server to a Flash Memory File System
You can copy a system image from an rcp network server to a Flash memory file system.
If you copy the configuration file to a personal computer used as a file server, the computer must support rsh.
Understand the rcp Username
The rcp protocol requires a client to send a remote username on each rcp request to a server. When you copy an image from the router to a server using rcp, the Cisco IOS software sends the first valid username in the following list:
1
2
3
4
For the rcp copy request to execute successfully, an account must be defined on the network server for the remote username. If the server has a directory structure, the configuration file or image is written or copied relative to the directory associated with the remote username on the server. The path for all files and images to be copied begins at the remote user's home directory. For example, if the system image resides in the home directory of a user on the server, specify that user's name as the remote username.
Copy from an rcp Server to Flash Memory Tasks
To copy an image from an rcp server to Flash memory, use the following commands, beginning in privileged EXEC mode:
1
See the instructions in the section "Copy Images from Flash Memory to a Network Server."
Make a backup copy of the current system or bootstrap software image.
2
configure terminal
(Optional) Enter configuration mode from the terminal. This step is required only if you override the default remote username (see Step 3).
3
ip rcmd remote-username username
(Optional) Specify the remote username.
4
end
(Optional) Exit configuration mode. This step is required only if you override the default remote username (see Step 3).
5
copy rcp:[[[//[username@]location]/directory]
/filename] flash-filesystem:[filename]Copy the image from an rcp server to a Flash memory file system.
6
Reply to any router prompts for additional information or confirmation. The prompting will depending on how much information you provide in the copy command and the current setting of the file prompt command.
Copy from an rcp Server to Flash Example
The following example copies a system image named mysysim1 from the netadmin1 directory on the remote server named SERVER1.CISCO.COM with an IP address of 172.16.101.101 to Flash memory. To ensure that enough Flash memory is available to accommodate the system image to be copied, the Cisco IOS software allows you to erase the contents of Flash memory first.
Router1# configure terminalRouter1(config)# ip rcmd remote-username netadmin1Router1(config)# endRouter# copy rcp: flash:Copy from an rcp Server to Partitioned Slot0
In the following example, the file /tftpboot/gate/c3600-i-mz on the rcp server at 172.23.1.129 is copied to partition 3 in slot 0. Because no username is specified, the router uses the default rcp remote username.
Router# show slot0: partition 3PCMCIA Slot0 flash directory, partition 3:File Length Name/status1 426 running-config[492 bytes used, 4193812 available, 4194304 total]Router# copy rcp://172.23.1.129/tftpboot/gate/c3600-i-mz slot0:3:/tftpboot/gate/c3600-i-mzAccessing file '/tftpboot/gate/c3600-i-mz' on 172.23.1.129...Connected to 172.23.1.129Loading 1711088 byte file c3600-i-mz: ! [OK]Erase flash device before writing? [confirm]Flash contains files. Are you sure you want to erase? [confirm]Copy '/tftpboot/gate/c3600-i-mz' from serveras '/tftpboot/gate/c3600-i-mz' into Flash WITH erase? [yes/no] yesErasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erasedConnected to 172.23.1.129Loading 1711088 byte file c3600-i-mz: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK]Verifying checksum... OK (0xF89A)Flash device copy took 00:00:16 [hh:mm:ss]Copy an Image from an FTP Server to a Flash Memory File System
You can copy a system image from an FTP server to a Flash memory file system.
Understand the FTP Username and Password
The FTP protocol requires a client to send a remote username and password on each FTP request to a server. When you copy a configuration file from the router to a server using FTP, the Cisco IOS software sends the first valid username in the following list:
1
2
3
The router sends the first valid password in the following list:
1
2
3
The username and password must be associated with an account on the FTP server. If you are writing to the server, the FTP server must be properly configured to accept the FTP write request from the user on the router.
If the server has a directory structure, the configuration file or image is written to or copied from the directory associated with the username on the server. For example, if the system image resides in the home directory of a user on the server, specify that user's name as the remote username.
Refer to the documentation for your FTP server for more details.
Use the ip ftp username and ip ftp password commands to specify a username and password for all copies. Include the username in the copy command if you want to specify a username for that copy operation only.
Copy from an FTP Server to Flash Memory Tasks
To copy a system image from an FTP server to a Flash memory file system, use the following commands in EXEC mode:
1
See the instructions in the section "Copy Images from Flash Memory to a Network Server."
Make a backup copy of the current software image or bootstrap image.
2
configure terminal
(Optional) Enter configuration mode from the terminal. This step is required only if you override the default remote username or password (see Steps 3 and 4).
3
ip ftp username username
(Optional) Change the default remote username.
4
ip ftp password password
(Optional) Change the default password.
5
end
(Optional) Exit configuration mode. This step is required only if you override the default remote username or password (see Steps 3 and 4).
6
copy ftp:[[[//[username[:password]@]location]
/directory]/filename] flash-filesystem:[filename]Using rcp, copy the configuration file from a network server to running memory or the startup configuration.
7
Reply to any router prompts for additional information or confirmation. The prompting will depending on how much information you provide in the copy command and the current setting of the file prompt command.
Copy from FTP Server to Flash Memory Example
The following example copies a the file c7200-js-mz from the FTP server the server using a username of myuser and a password of mypass:
Router# copy ftp://myuser:mypass@theserver/tftpboot/ken/c7200-js-mz slot1:c7200-js-mzAccessing ftp://theserver/tftpboot/ken/c7200-js-mz...Translating "theserver"...domain server (192.168.2.132) [OK]Loading c7200-js-mz from 192.168.2.132 (via Ethernet3/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 4823492/9646080 bytes]4823492 bytes copied in 264.312 secs (18270 bytes/sec)Verify the Image in Flash Memory
Before booting from Flash memory, verify that the checksum of the image in Flash memory matches the checksum listed in the README file that was distributed with the system software image by using the verify command. The checksum of the image in Flash memory is displayed at the bottom of the screen when you issue the copy command to copy an image. The README file was copied to the network server automatically when you installed the system software image on the server.
CautionIf the checksum value does not match the value in the README file, do not reboot the router. Instead, issue the copy 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. If you have a corrupted image in Flash memory and try to boot from Flash, the router will start the system image contained in ROM (assuming that booting from a network server is not configured). If ROM does not contain a fully functional system image, the router will not function and must be reconfigured through a direct console port connection.
The Flash memory content listing does not include the checksum of individual files. To recompute and verify the image checksum after an image is copied into Flash memory or a Flash memory device, use the following EXEC mode command:
verify flash-filesystem:[partition-number:][filename]
Recompute and verify the image checksum after the image is copied into Flash memory.
If you do not provide the filename in the command, the router prompts you. By default, it prompts for the last (most recent) file in Flash. Press Return to recompute the default file checksum, or enter the filename of a different file at the prompt. Note that the checksum for microcode images is always 0x0000.
The following example verifies the image c7200-js-mz in slot0:
Router# verify slot0:c7200-js-mzVerified slot0:c7200-js-mzCopy Images between Local Flash Memory Devices
On routers will multiple Flash memory file systems, you can copy images from one Flash memory file system, such as internal Flash memory or a Flash memory card in a PCMCIA slot, to another Flash memory file system, as shown in . One reason to copy the image to a different flash device is to make a backup copy of it.
Figure 351
Copying Images between Flash Memory File Systems
To copy an image between Flash memory file systems, use these commands in EXEC mode:
Note
Copy a File between Local Flash Memory Devices Example
The following example copies the file admin/images/new-ios from partition 1 of internal Flash memory to slot 0:
Router# show flash: partition 1System flash directory, partition 1:File Length Name/status1 3142748 admin/images/new-ios[3142812 bytes used, 1051492 available, 4194304 total]Router# show slot0:PCMCIA Slot0 flash directoryFile Length Name/status1 1711088 /tftpboot/gate/c3600-i-mz[1711152 bytes used, 2483152 available, 4194304 total]Router# copy flash:1:admin/images/new-ios slot0:admin/images/new-iosVerifying checksum for 'admin/images/new-ios' (file # 1)... OKErase flash device before writing? [confirm]Flash contains files. Are you sure you want to erase? [confirm]Copy 'admin/images/new-ios' from flash: deviceas 'admin/images/new-ios' into slot0: device WITH erase? [yes/no] yesErasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 3142748/4194304 bytes]Flash device copy took 00:00:50 [hh:mm:ss]Verifying checksum... OK (0xB732)Router# show slot0:PCMCIA Slot0 flash directoryFile Length Name/status1 3142748 admin/images/new-ios[3142812 bytes used, 1051492 available, 4194304 total]Specify the Startup System Image in the Configuration File
You can enter multiple boot commands in the startup configuration file or in the BOOT environment variable to provide backup methods for loading a system image onto the router. The following are three ways to load a system image:
•
•
•
Note
You can enter the different types of boot commands in any order in the startup configuration file or in the BOOT environment variable. If you enter multiple boot commands, the Cisco IOS software tries them in the order they are entered.
Note
Lo
