cc/td/doc/product/software/ios113ed/113ed_cr/fun_c
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Loading and Maintaining System Images and Microcode

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. Table 7 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.


Table 7: Mapping Old Commands to New Commands
Old Command New Command
copy erase flash erase flash
copy verify or copy verify flash verify flash (on all systems except Cisco 1600 series, Cisco 3600 series, Cisco 7000 family)

verify (on Cisco 1600 series, Cisco 3600 series, Cisco 7000 family)

copy verify bootflash verify bootflash

System Images and Microcode Task List

You can perform the tasks involving images described in the following sections:

Note These tasks assume you have a minimal configuration that you want to modify.

Display System Image Information

Perform the following tasks in EXEC mode to display information about system software:

Task Command
List the contents of the BOOT environment variable, the name of the configuration file pointed to by the CONFIG_FILE environment variable, and the contents of the BOOTLDR environment variable. show boot (Cisco 3600 series, Cisco 7000 family only)
List information about Flash memory, including system image filenames and amounts of memory used and remaining. show flash
List the names of the Flash devices currently supported on the router. show flash devices (Cisco 7000 family only)
List information about Flash memory, including system image filenames, amounts of memory used and remaining, and Flash partitions. show device: [all | chips | detailed | err | partition number | summary] (Cisco 1600 series and Cisco 3600 series)

show flash [all | chips | filesys] [device:] (Cisco 7000 family only)

show flash [all | chips | detailed | err | partition number [all | chips | detailed | err] | summary] (all other platforms)

Display microcode information. show microcode
List the system software release version, configuration register setting, and other information. show version

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 all platforms except the Cisco 1600 series, Cisco 3600 series, and Cisco 7000 family, the image is located in Flash memory. See Table 8 for places where the images can be located on the Cisco 1600 series, Cisco 3600 series, and Cisco 7000 family routers.

Table  8: Possible System and Boot Image Locations
Router Flash (flash:) Bootflash (bootflash:) first PCMCIA slot (slot0:) Second PCMCIA slot (slot1:)
Cisco 7000 family - yes yes yes
Cisco 3600 series yes - yes yes
Cisco 1600 series yes - - -
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 (see the "Set the BOOTLDR Environment Variable" section for details).
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), c1005 (Cisco 1005).

The feature variable identifies the feature sets supported by the image.

The type field can contain the following characters:

Copy Images from Flash Memory to a Network Server

You can copy system images from Flash memory to a TFTP server or to an rcp 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 rcp transport mechanism provides faster performance and more reliable delivery of data than TFTP. These improvements are possible because the rcp transport mechanism is built on and uses the Transmission Control Protocol/Internet Protocol (TCP/IP) stack, which is connection-oriented.

Copy an Image from Flash or Bootflash 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, perform the following task in EXEC mode:

Task Command
Step 1 (Optional) If you do not already know it, learn the exact spelling of the system image filename in Flash memory.

On the Cisco 1600 series, Cisco 3600 series, and Cisco 7000 family, you can learn the spelling of the system image filename on a specified Flash memory device.

On a Cisco 4500 series, you can learn the spelling of the boot image filename in boot Flash memory

 show flash all

show flash [device:] (Cisco 7000 family only)

show device: all (Cisco 1600 series and Cisco 3600 series)

show bootflash (Cisco 4500 series only)

Step 2 Copy the system image from Flash memory to a TFTP server.

On the Cisco 1600 series, Cisco 3600 series, and Cisco 7000 family, you can copy the system image from a specified Flash memory device to a TFTP server.

On the Cisco 4500 series, you can copy the boot image from boot Flash memory to a TFTP server.

 copy flash tftp

copy device:[partition-number:][filename] tftp (Cisco 1600 series and Cisco 3600 series only)

copy file-id tftp (Cisco 7000 family only)

or

copy bootflash tftp (Cisco 4500 series only)

Step 3 When prompted, enter the IP address or domain name of the TFTP server. ip-address or name
Step 4 When prompted, enter the filename of the system image in Flash memory. filename

To stop the copy process, press Ctrl-^.

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 Flash TFTP Example Using Show Flash All

The following example uses the show flash all 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. The name of the system image file (xk09140z) is listed near the end of the show flash all output.

Router# show flash all
2048K bytes of flash memory on embedded flash (in XX).
   ROM   socket    code    bytes       name
    0      U42     89BD   0x40000     INTEL 28F020
    1      U44     89BD   0x40000     INTEL 28F020
    2      U46     89BD   0x40000     INTEL 28F020
    3      U48     89BD   0x40000     INTEL 28F020
    4      U41     89BD   0x40000     INTEL 28F020
    5      U43     89BD   0x40000     INTEL 28F020
    6      U45     89BD   0x40000     INTEL 28F020
    7      U47     89BD   0x40000     INTEL 28F020
  security jumper(12V) is installed,
  flash memory is programmable.
file  offset      length        name
 0     0x40        1204637     xk09140z
  [903848/2097152 bytes free]
Router# copy flash tftp
IP address of remote host [255.255.255.255]? 172.16.13.110
filename to write on tftp host? xk09140z
writing xk09140z !!!!...
successful tftp write.
Router#
Copy Flash TFTP Example for Cisco 7000 Family

The following example uses the show flash [device:] command on a Cisco 7000 familty to display the name of the system image file to copy. In the example, the Flash memory device containing the system image is the second PCMCIA slot. The file to copy is test. The example uses the copy file-id tftp command to copy test to a TFTP server.

Router#show flash slot1:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1   .. 1        46A11866 2036C   4    746      May 16 1995 16:24:37 test
Router#copy slot1:test tftp
IP address of remote host [255.255.255.255]? 172.16.13.110
filename to write on tftp host? [test]y
writing test!!!!...
successful tftp write.
Copy by Specifying a Source Partition Number (Cisco 1600 series and Cisco 3600 series) Example

In this example, the file your-ios is copied from partition 2 of the Flash memory PC card in slot 0 of a Cisco 3600 series router to the TFTP server at 172.23.1.129. The source partition number is specified in the command line. The file will be saved with the name server-ios in the /sysadmin/images directory.

For the Cisco 1600 series router, the process will be the same except the device used in the copy command must be flash: and the directory listed will show System Flash rather than slot 0.

Router# copy slot0:2 tftp
PCMCIA Slot0 flash directory, partition 2:
File  Length   Name/status
  1   3141700 your-ios
[3141764 bytes used, 1052540 available, 4194304 total]
Address or name of remote host [172.23.1.129]? 
Source file name? your-ios
Destination file name [your-ios]? /sysadmin/images/server-ios
Verifying checksum for 'your-ios' (file # 1)...  OK
Copy 'your-ios' from Flash to server
  as '/sysadmin/images/server-ios'? [yes/no] yes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upload to server done
Flash device copy took 00:00:41 [hh:mm:ss]
Copy by Specifying a Source Partition and Filename (Cisco 1600 series and Cisco 3600 series)

In this example, the file your-ios is copied from partition 4 of the Flash memory PC card in slot 0 of a Cisco 3600 series router to the TFTP server at 172.23.1.129. Since all required information is specified in the command line, the software does not display Flash memory contents. The file will be saved with the name c3640-j-mz in the dirt/images directory relative to the directory of the remote username.

For the Cisco 1600 series router, the process will be the same except the device used in the copy command must be flash:

Router# copy slot0:4:your-ios tftp
Address or name of remote host [172.23.1.129]? 
Destination file name [your-ios]? dirt/images/c3640-j-mz
Verifying checksum for 'your-ios' (file # 2)...  OK
Copy 'your-ios' from Flash to server
  as 'dirt/images/c3640-j-mz'? [yes/no] yes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upload to server done
Flash device copy took 00:00:20 [hh:mm:ss]
Copy by Not Specifying a Source Partition (Cisco 1600 series and Cisco 3600 series)

In this example, the file your-ios is copied from partition 1 of the Flash memory PC card in slot 0 of a Cisco 3600 series router to the TFTP server at 172.23.1.129. Because the partition number and filename are not specified, the software displays the contents of the Flash memory PC card. The file will be saved with the name your-ios in the dirt/sysadmin directory relative to the directory of the remote username.

For the Cisco 1600 series router, the process will be the same except the device used in the copy command must be flash: and the directories listed will show System Flash rather than slot 0.

Router# copy slot0: tftp
PCMCIA Slot0 flash
Partition   Size    Used      Free      Bank-Size  State          Copy Mode
  1         4096K   1671K     2424K     4096K      Read/Write     Direct
  2         4096K   3068K     1027K     4096K      Read/Write     Direct
  3         4096K   1671K     2424K     4096K      Read/Write     Direct
  4         4096K   3825K      270K     4096K      Read/Write     Direct
[Type ? for partition directory; ? for full directory; q to abort]
Which partition? [default = 1]
PCMCIA Slot0 flash directory, partition 1:
File  Length   Name/status
  1   1711088 your-ios 
[1711152 bytes used, 2483152 available, 4194304 total]
Address or name of remote host [172.23.1.129]? 
Source file name? your-ios
Destination file name [your-ios]? dirt/sysadmin/your-ios
Verifying checksum for 'your-ios' (file # 1)...  OK
Copy 'your-ios' from Flash to server
  as 'dirt/sysadmin/ios-2'? [yes/no] yes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upload to server done
Flash 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.

To stop the copy process, press Ctrl-^.

Refer to the Internetwork Troubleshooting Guide publication for procedures on how to resolve Flash memory problems.

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. The username set by the ip rcmd remote-username command, if the command is configured.

  2. The remote username associated with the current TTY (terminal) process. For example, if the user is connected to the router through Telnet and was authenticated through the username command, the router software sends the Telnet username as the remote username.

  3. The router host name.

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. Use the ip rcmd remote-username command to specify which directory on the server to use. For example, if the system image resides in the home directory of a user on the server, you can 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 Rtr1
ip rcmd remote-username User0

If the router's IP address translates to Router1.company.com, then the .rhosts file for User0 on the rcp server should contain the following line:

Router1.company.com Rtr1

Refer 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, perform the following tasks:

Task Command
Step 1 (Optional) If you do not already know it, learn the exact spelling of the system image filename in Flash memory.

On the Cisco 1600 series, Cisco 3600 series, and Cisco 7000 family, you can learn the spelling of the system image filename on a specified Flash memory device.

On a Cisco 4500 series, you can learn the spelling of the boot image filename in boot Flash memory

 show flash all

show flash [device:] (Cisco 7000 family only)

show device: all (Cisco 1600 series and Cisco 3600 series)

show bootflash (Cisco 4500 series only)

Step 2 Enter configuration mode from the terminal. This step is required only if you are going to override the default remote username (see Step 3). configure terminal
Step 3 Specify the remote username. This step is optional, but recommended. ip rcmd remote-username username
Step 4 Exit configuration mode. end
Step 5 Copy the system image from Flash memory to a network server using rcp.

On the Cisco 1600 series, Cisco 3600 series, and Cisco 7000 family, you can copy the system image from a specified Flash memory device to an rcp server.

On the Cisco 4500 series, you can copy the boot image from boot Flash memory to an rcp server.

 copy flash rcp

copy device:[partition-number:][filename] rcp (Cisco 1600 series and Cisco 3600 series only)

copy file-id rcp (Cisco 7000 family only)

or

copy bootflash rcp (Cisco 4500 series only)

Step 6 When prompted, enter the IP address or domain name of the rcp server. ip-address or name
Step 7 When prompted, enter the filename of the system image in Flash memory. filename

To stop the copy process, press Ctrl-^.

Refer to the Internetwork Troubleshooting Guide publication for procedures on how to resolve Flash memory problems.

Copy Flash RCP Example

The following example copies the system image c5200-ds-l to a network server using rcp:

Router# configure terminal
Router(config)# ip rcmd remote-username netadmin1
Router(config)# end
Router# copy flash rcp
System flash directory:
File name/status
  1 c5200-ds-l
[2076072 bytes used, 21080 bytes available]
Name of file to copy? c5200-ds-l
Address or name of remote host [UNKNOWN]? 172.16.1.111
File name to write to? c5200-ds-l
Verifying checksum for 'c5200-ds-l' (file # 1)...[OK] 
Writing c5200-ds-l -
Copy File-id RCP Example for Cisco 7000 Family

The following example copies a system image file called test from the second PCMCIA slot on a Cisco 7000 family router to a network server using rcp:

Router# configure terminal
Router(config)# ip rcmd remote-username netadmin1
Router(config)# end
Router# copy slot1:test rcp
System flash directory:
File name/status
  1 test
[2076072 bytes used, 21080 bytes available]
Name of file to copy? [test] y
Address or name of remote host [UNKNOWN]? 172.16.1.111
File name to write to? test
Verifying checksum for 'test' (file # 1)...[OK] 
Writing test!!!!...

The exclamation point (!) indicates that the copy process is taking place. Each exclamation point (!) indicates that ten packets have been transferred successfully.

Copy by not Specifying a Source Partition and Filename (Cisco 1600 series and Cisco 3600)

In this example, the file your-ios is copied from partition 1 of the Flash memory PC card in slot 1 of a Cisco 3600 series router to the rcp server at 172.23.1.129. Since the partition number and filename are not specified, the software displays the contents of the Flash memory PC card. The file will be saved with the name your-ios in the /sysadmin/images directory.

For the Cisco 1600 series router, the process will be the same except the device used in the copy command must be flash: and the directory listed will be the "System flash directory."

Router# copy slot1: rcp
PCMCIA Slot1 flash directory:
File  Length   Name/status
  1   1711088 your-ios
[1711152 bytes used, 2483152 available, 4194304 total]
Address or name of remote host [172.23.1.129]? 
Source file name? your-ios
Destination file name [your-ios]? /sysadmin/images/your-ios
Verifying checksum for 'your-ios' (file # 1)...  OK
Copy 'your-ios' from Flash to server
  as '/sysadmin/images/your-ios'? [yes/no] yes
Writing /sysadmin/images/your-ios !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upload to server done
Flash device copy took 00:00:08 [hh:mm:ss]
Copy by Specifying a Source Partition and Filename (Cisco 1600 series and Cisco 3600 series)

In this example, the file your-ios is copied from partition 1 of the Flash memory PC card in slot 1 of a Cisco 3600 series router to the rcp server at 172.23.1.129. Because all required information is specified in the command line, the software does not display Flash memory contents. The file will be saved with the name your-ios in the /sysadmin/images directory.

For the Cisco 1600 series router, the process will be the same except the device used in the copy command must be flash:

Router# copy slot1:1:your-ios rcp
Address or name of remote host [172.23.1.129]? 
Destination file name [your-ios]? /sysadmin/images/your-ios
Verifying checksum for 'your-ios' (file # 1)...  OK
Copy 'your-ios' from Flash to server
  as '/sysadmin/images/your-ios'? [yes/no] yes
Writing /sysadmin/images/your-ios !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upload to server done
Flash device copy took 00:00:08 [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 MOP server to Flash memory or boot Flash memory to upgrade or change the IOS software or boot image on your router.

The protocol you use depends on which type of server you are using. The rcp transport mechanism provides faster performance and more reliable delivery of data than TFTP. These improvements are possible because the rcp transport mechanism is built on and uses 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.

Refer to the "Maintain Router Memory" chapter for an explanation of the Flash memory card that can be used on the Cisco 3600 series and Cisco 7000 family.

Note When you are upgrading or changing to a different Cisco IOS release, refer to the appropriate release notes for information on system requirements and limitations.

Filenames in Flash memory can be up to 63 characters long; they are not case-sensitive and are always converted to lowercase.

Note The destination filename must be an alphanumeric expression. For example, the filename 1 is invalid.

Understand Flash Memory Space Considerations

Be sure there is enough space available before copying a file to Flash memory. Use the show flash 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.

Caution Do not reboot the router if there is no valid image in Flash memory.
Note For the Cisco 3600 series, if you do not have access to a network server and need to download a system image, you can copy an image from a local or remote computer (such as a PC, UNIX workstation, or Macintosh) using the Xmodem or Ymodem protocols. See the section "Recovering a System Image Using Xmodem or Ymodem (Cisco 1600 series and Cisco 3600 series only)" later in this chapter.

The copy command automatically displays the Flash memory directory, including the amount of free space. 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.

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 enter n after the "Erase flash before writing?" prompt, the copy process continues. If you enter y and confirm the erasure, the erase routine begins. Be sure to have ample Flash memory space before entering n at the erasure prompt.

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. The first copy of the file still resides within Flash memory, but it is rendered unusable in favor of the newest version, and is listed with the "deleted" tag when you use the show flash command. If you terminate the copy process, the newer file is marked "deleted" because the entire file was not copied and is not valid. In this case, the original file in Flash memory is valid and available to the system.

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:

General Output Conventions

During a copy operation, a pound sign (#) generally means that a Flash memory device is being cleared and initialized. (Different platforms use different ways of indicating that Flash is being cleared.) An exclamation point (!) means that ten packets have been transferred successfully. A series of "V" characters means that a checksum verification of the file is occurring after the file is written to Flash memory. An "O" means an out-of-order packet. A period (.) means a timeout. 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 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 which 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 Flash Memory or Boot Flash Memory

To copy a system image from a Trivial File Transfer Protocol (TFTP) server to Flash memory or to copy a boot image to boot Flash memory (Cisco 4500 Series only), complete the following tasks:

Task Command
Step 1 Make a backup copy of the current software image or bootstrap image. See the instructions in the section "Copy Images from Flash Memory to a Network Server."
Step 2 Copy a system image to Flash memory

or

Copy a boot image to boot Flash memory (Cisco 4500 Series only)

 copy tftp flash

copy tftp file-id (Cisco 7000 family only)

copy tftp bootflash (Cisco 4500 Series only)

copy tftp device:[partition-number:][filename] (Cisco 1600 series and Cisco 3600 series)

Step 3 When prompted, enter the IP address or domain name of the server. ip-address or name
Step 4 If prompted, enter the filename of the server system image. filename
Step 5 If prompted, enter the Flash memory device that is to receive the copy of the system image. device

For the Cisco 7000 family, the file-id argument of the copy tftp file-id command specifies a device and filename as the destination of the copy operation. You can omit the device, entering only copy tftp filename. When you omit the device, the system uses the default device specified by the cd command.

Copy TFTP Flash Example

The following example shows how to use the copy tftp flash command to copy a system image named igs-p-l when Flash memory is too full to copy the file. The filename igs-p-l can be in either lowercase or uppercase; the system sees IGS-P-L as igs-p-l. If more than one file of the same name is copied to Flash, regardless of case, the last file copied becomes the valid file.

Router# copy tftp flash
IP address or name of remote host [255.255.255.255]? dirt
Translating "DIRT"...domain server (255.255.255.255) [OK]
Name of file to copy? igs-p-l
Copy 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 0
Zeroing bank...zzzzzzzzzzzzzzzz
Verify zeroed...vvvvvvvvvvvvvvvv
Erasing bank...eeeeeeeeeeeeeeee
Erasing flash EPROMs bank 1
Zeroing bank...zzzzzzzzzzzzzzzz
Verify zeroed...vvvvvvvvvvvvvvvv
Erasing bank...eeeeeeeeeeeeeeee
Erasing flash EPROMs bank 2
Zeroing bank...zzzzzzzzzzzzzzzz
Verify zeroed...vvvvvvvvvvvvvvvv
Erasing bank...eeeeeeeeeeeeeeee
Erasing flash EPROMs bank 3
Zeroing bank...zzzzzzzzzzzzzzzz
Verify zeroed...vvvvvvvvvvvvvvvv
Erasing bank...eeeeeeeeeeeeeeee
Loading from 172.16.1.111:!!!!...
 [OK - 1906676/4194240 bytes]
Verifying via checksum...
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvv
Flash verification successful. Length = 1906676, checksum = 0x12AD
Copy TFTP 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 flash
IP address or name of remote host [172.16.13.111]?
Name of file to copy? igs-p-l
File 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]n
Loading from 172.16.1.111:!!!!...
[OK - 1906676/2287500 bytes]
Verifying via checksum...
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvv
Flash verification successful. Length = 1902192, checksum = 0x12AD
Copy TFTP Flash Example with Security Jumper not 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 memory
Copy by Specifying Destination Partition and Filename for Cisco 1600 series and Cisco 3600 series

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 of a Cisco 3600 series router.

For the Cisco 1600 series router, the process will be the same except the device used in the copy command must be flash: and the directory listed will be the "System flash directory."

Router# copy tftp flash:1:c3600-i-mz
System flash directory, partition 1:
File  Length   Name/status
  1   1711088  current-ios 
[1711152 bytes used, 2483152 available, 4194304 total]
Address or name of remote host [172.23.1.129]? 
Source file name [c3600-i-mz]? 
Accessing 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 server
  as 'c3600-i-mz' into Flash WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeee ...erased
Loading 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 by Not Specifying Destination Partition and Filename for Cisco 1600 series and Cisco 3600 series

In the following example, the file images/3600/c3600-i-mz on the TFTP server at 172.23.1.129 is copied to the first partition of internal Flash Memory of a Cisco 3600 series router. The software prompts for the destination partition since it was not provided in the command line.

For the Cisco 1600 series router, the process will be the same except the device used in the copy command must be flash: and the directory listed will be the "System flash directory."

Router# copy tftp flash:
System flash
Partition   Size    Used      Free      Bank-Size  State          Copy Mode
  1         4096K   1671K     2424K     4096K      Read/Write     Direct
  2        16384K   1671K    14712K     8192K      Read/Write     Direct
[Type ? for partition directory; ? for full directory; q to abort]
Which partition? [default = 1] 
System flash directory, partition 1:
File  Length   Name/status
  1   1711088 c3600-i-mz  
[1711152 bytes used, 2483152 available, 4194304 total]
Address or name of remote host [172.23.1.129]? 
Source file name? images/3600/c3600-i-mz  
Destination file name [images/3600/c3600-i-mz]? 
Accessing file 'images/3600/c3600-i-mz' on 172.23.1.129...
Loading images/3600/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 'images/3600/c3600-i-mz' from server
  as 'images/3600/c3600-i-mz' into Flash WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeee ...erased
Loading images/3600/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 Flash Memory or Boot Flash Memory

You can copy a system image from an rcp network server to Flash memory. You can also copy a boot image from an rcp network server to boot Flash memory.

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 a configuration file from the router to a server using rcp, the Cisco IOS software sends the first valid username in the following list:


  1. The username set by the ip rcmd remote-username command, if the command is configured.

  2. The remote username associated with the current TTY (terminal) process. For example, if the user is connected to the router through Telnet and was authenticated through the username command, the router software sends the Telnet username as the remote username.

  3. The router host name.

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 to or copied from the directory associated with the remote username on the server. Use the ip rcmd remote-username command to specify which directory on the server to use. For example, if the system image resides in the home directory of a user on the server, you can specify that user's name as the remote username.

Copy from an rcp Server to Flash Memory Tasks

To copy a system image from an rcp server to Flash memory or to copy a boot image to boot Flash memory, complete the following tasks:

Task Command
Step 1 Make a backup copy of the current system or bootstrap software image. See the instructions in the section "Copy Images from Flash Memory to a Network Server."
Step 2 Enter configuration mode from the terminal.

This step is required only if you override the default remote username (see Step 3).

configure terminal
Step 3 Specify the remote username. This step is optional, but recommended. ip rcmd remote-username username
Step 4 Exit configuration mode. end
Step 5 Copy the system image from an rcp server to Flash memory,

or

Copy the boot image from an rcp server to boot Flash memory.

 copy rcp flash

copy rcp bootflash

copy rcp file-id (Cisco 7000 family only)

copy rcp device:[partition-number:][filename] (Cisco 1600 series and Cisco 3600 series)

Step 6 When prompted, enter the IP address or domain name of the network server. ip-address or name
Step 7 When prompted, enter the filename of the server system image to be copied. filename
Copy rcp Flash Example

The following example shows how to copy 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 terminal
Router1(config)# ip rcmd remote-username netadmin1
Router1(config)# end
Router# copy rcp flash
 
System flash directory:
File name/status
   1 mysysim1
[2076072 bytes used, 21080 bytes available]
Address or name of remote host[UNKNOWN]? 172.16.101.101
Name of file to copy? mysysim1
Copy mysysim1 from SERVER1.CISCO.COM?[confirm]
Checking for file 'mysysim1' on SERVER1.CISCO.COM...[OK]
Erase Flash device before writing?[confirm]
Are you sure?[confirm]
Erasing device...ezeeze...erased.
Connected to 172.16.101.101
Loading 2076007 byte file mysysim1:!!!!...
[OK]
Verifying checksum... (0x87FD)...[OK] 
Router#
Copy rcp Example Using RSP Card

The following example uses the copy rcp file-id command to copy the router-image file from a network server using rcp to the Flash memory card inserted in slot 0 of the RSP card:

Router1# configure terminal
Router1(config)# ip rcmd remote-username netadmin1
Router1(config)# end
Router1# copy rcp slot0:router-image
Copy rcp Bootflash Example

The following copies a bootstrap image from the rcp server to boot Flash memory:

Router1# configure terminal
Router1(config)# ip rcmd remote-username netadmin1
Router1(config)# end
Router1# copy rcp bootflash
 
System flash directory:
File name/status
   1 btxx
[2076072 bytes used, 21080 bytes available]
Address or name of remote host[UNKNOWN]? 172.16.1.111
Name of file to copy? btxx
Copy btxx from UTOPIA.CISCO.COM?[confirm]
Checking for file 'btxx' on UTOPIA.CISCO.COM...[OK]
Erase flash device before writing?[confirm]
Are you sure?[confirm]
Erasing device...ezeeze...erased.
Connected to 172.16.1.111
Loading 2076007 byte file btxx:!!!!...
[OK]
Verifying checksum... (0x87FD)...[OK]
Copy by Specifying a Destination Partition (Cisco 1600 series and Cisco 3600 series)

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 of a Cisco 3600 series router.

For the Cisco 1600 series router, the process will be the same except the device used in the copy command must be flash: and the directory listed will be the "System flash directory."

Router# copy rcp slot0:3
PCMCIA Slot0 flash directory, partition 3:
File  Length   Name/status
  1   426      running-config  
[492 bytes used, 4193812 available, 4194304 total]
Address or name of remote host [172.23.1.129]? 
Source file name? /tftpboot/gate/c3600-i-mz
Destination file name [/tftpboot/gate/c3600-i-mz]? 
Accessing file '/tftpboot/gate/c3600-i-mz' on 172.23.1.129...
Connected to 172.23.1.129
Loading 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 server
  as '/tftpboot/gate/c3600-i-mz' into Flash WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Connected to 172.23.1.129
Loading 1711088 byte file c3600-i-mz: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK]
Verifying checksum...  OK (0xF89A)
Flash device copy took 00:00:16 [hh:mm:ss]
Copy by not Specifying a Destination Partition (Cisco 1600 series and Cisco 3600 series)

In the following example, the file /tftpboot/gate/c3600-i-mz on the rcp server at 172.23.1.129 is copied to the first partition of slot 0 of a Cisco 3600 series router. The software prompts for the destination partition because it was not provided in the command line.

For the Cisco 1600 series router, the process will be the same except the device used in the copy command must be flash: and the directories listed will be for the System Flash directory.

Router# copy rcp slot0:
PCMCIA Slot0 flash
Partition   Size    Used      Free      Bank-Size  State          Copy Mode
  1         4096K   3068K     1027K     4096K      Read/Write     Direct
  2         4096K   1671K     2424K     4096K      Read/Write     Direct
  3         4096K      0K     4095K     4096K      Read/Write     Direct
  4         4096K   3825K      270K     4096K      Read/Write     Direct
[Type ? for partition directory; ? for full directory; q to abort]
Which partition? [default = 1] 
PCMCIA Slot0 flash directory, partition 1:
File  Length   Name/status
  1   3142288  c3600-j-mz
[3142352 bytes used, 1051952 available, 4194304 total]
Address or name of remote host [172.23.1.129]? 
Source file name? /tftpboot/gate/c3600-i-mz
Destination file name [/tftpboot/gate/c3600-i-mz]? 
Accessing file '/tftpboot/gate/c3600-i-mz' on 172.23.1.129...
Connected to 172.23.1.129
Loading 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 server
  as '/tftpboot/gate/c3600-i-mz' into Flash WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Connected to 172.23.1.129
Loading 1711088 byte file c3600-i-mz: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Verifying checksum...  OK (0xF89A)
Flash device copy took 00:00:18 [hh:mm:ss]

Copy an Image from a MOP Server to Flash Memory or Bootflash Memory

On all platforms except the Cisco 7200 series and Cisco 7500 series, you can copy a system image from a Maintenance Operation Protocol (MOP) server to Flash memory or a boot image to boot Flash memory. To do so, perform the following task in EXEC mode:

Task Command
Copy a boot image using MOP to flash

or

Copy a boot image to boot Flash.

 copy mop flash

copy mop bootflash

copy mop device:[partition-number:][filename] (Cisco 3600 series)

Copy MOP Flash Example

The following example shows a sample output from the copy mop flash command. In this example, the system image routerimage, which already exists in Flash memory, is copied to Flash memory. Although there is enough memory to copy the file without erasing any existing files, Flash memory is erased.

Router# copy mop flash
System flash directory:
File  Length   Name/status
  1   984       routerimage[deleted]
  2   984       routerimage 
[2096 bytes used, 8386512 available, 8388608 total]
Source file name? routerimage
Destination file name [routerimage]?
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'routerimage' from server
  as 'routerimage' into Flash WITH erase? [yes/no]yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee...erased
Loading routerimage from 1234.5678.9abc via Ethernet0: !
[OK - 984/8388608 bytes]
Verifying checksum... OK (0x14B3)
Flash copy took 0:00:01 [hh:mm:ss]
Copy MOP Example for the Cisco 1600 Series and Cisco 3600 Series

In the following example, the system image routerimage, which already exists in internal Flash memory, is copied from a MOP server to the first partition of internal Flash memory. Although there is enough memory to copy the file without erasing any existing files, Flash memory is erased. 

Router# copy mop flash:
System flash
Partition   Size    Used      Free      Bank-Size  State          Copy Mode
  1         4096K   1671K     2424K     4096K      Read/Write     Direct
  2        16384K   1671K    14712K     8192K      Read/Write     Direct
[Type ? for partition directory; ? for full directory; q to abort]
Which partition? [default = 1] 
System flash directory, partition 1:
File  Length   Name/status
  1   984       routerimage[deleted]
  2   984       routerimage 
[2096 bytes used, 8386512 available, 8388608 total]
Source file name? routerimage
Destination file name [routerimage]?
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'routerimage' from server
  as 'routerimage' into Flash WITH erase? [yes/no]yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Loading routerimage from 1234.5678.9abc via Ethernet1/0: !
[OK - 984/8388608 bytes]
Verifying checksum...  OK (0x14B3)
Flash copy took 0:00:01 [hh:mm:ss]

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 tftp, copy rcp, copy rcp, or copy mop 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.

Caution If 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, complete the following task in EXEC mode:

Task Command
Recompute and verify the image checksum after the image is copied into Flash memory. See the "Possible System and Boot Image Locations" table for valid Flash devices for the Cisco 1600, Cisco 3600, and Cisco 7000 family. verify flash

verify bootflash (Cisco 4500 Series only)

verify device:[partition-number:][filename] (Cisco 1600 series and Cisco 3600 series only)

verify [device:]filename (Cisco 7000 family)

When you enter the verify flash command, the screen prompts you for the filename to verify. 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 illustrates how to use the verify flash command:

Router# verify flash

Name of file to verify [gsxx]?
Verifying via checksum...
vvvvvvvvvvvvvvvvvvvvvvvvvvvvv

Flash verification successful. Length = 1923712, checksum = 0xA0C1

The following example verifies the gsxx file on the Flash memory card inserted in slot 0 of a Cisco 7000 family:

Router# verify slot0:gsxx
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
File slot0:gsxx verified OK
Verify Checksum Example for Cisco 1600 series and Cisco 3600 series

The following example verifies the checksum of the file c3600-i-mz.test in the fourth partition of the Flash memory card in slot 0. For the Cisco 1600 series router, the process will be the same except the device used in the verify command must be flash: and the directories listed will be for System Flash.

Router# verify slot0:
PCMCIA Slot0 flash
Partition   Size    Used      Free      Bank-Size  State          Copy Mode
  1         4096K   3069K     1026K     4096K      Read/Write     Direct
  2         4096K   3069K     1026K     4096K      Read/Write     Direct
  3         4096K      0K     4096K     4096K      Read/Write     Direct
  4         4096K   3826K      269K     4096K      Read/Write     Direct
[Type ? for partition directory; ? for full directory; q to abort]
Which partition? [default = 1] 4
PCMCIA Slot0 flash directory, partition 4:
File  Length   Name/status
  1   2205860  dirt/images/c3600-d-mz  
  2   1711128  c3600-i-mz.test 
  3   850      alz 
[3918032 bytes used, 276272 available, 4194304 total]
Name of file to verify? c3600-i-mz.test  
Verifying checksum for 'c3600-i-mz.test' (file # 2)...  OK

Copy Images between Local Flash Memory Devices

On Cisco 3600 series and Cisco 7000 family routers, you can copy images from one Flash memory device, such as internal Flash memory or a Flash memory card in a PCMCIA slot, to another Flash memory device, as shown in Figure 8. One reason to copy the image to a different flash device is to make a backup copy of it.


Figure 8:

Copying Images Between Flash Memory Devices on Cisco 3600 Series Routers

To copy an image between Flash memory devices, follow these steps in EXEC mode:

Task Command
Step 1 Display the layout and contents of Flash memory. show device: [all | chips | detailed | err | partition number | summary]
Step 2 Copy an image between Flash memory devices. copy device:[partition-number:][filename] device:[partition-number:][filename]
Step 3 Verify the checksum of the image you copied. verify device: [partition-number:][filename]
Note The source device and the destination device cannot be the same. For example, the command copy slot1: slot1: is invalid.
Copy a File between Local Flash Memory Devices Examples for Cisco 3600--Source Partition Specified

The following example copies the file admin/images/new-ios from partition 1 of internal Flash memory to partition 1 of slot 0.

Router# copy flash:1 slot0:
System flash directory, partition 1:
File  Length   Name/status
  1   3142748 admin/images/new-ios
[3142812 bytes used, 1051492 available, 4194304 total]
PCMCIA Slot0 flash
Partition   Size    Used      Free      Bank-Size  State          Copy Mode
  1         4096K   1671K     2424K     4096K      Read/Write     Direct
  2         4096K   3069K     1026K     4096K      Read/Write     Direct
  3         4096K   1671K     2424K     4096K      Read/Write     Direct
  4         4096K   3826K      269K     4096K      Read/Write     Direct
[Type ? for partition directory; ? for full directory; q to abort]
Which partition? [default = 1] 
PCMCIA Slot0 flash directory, partition 1:
File  Length   Name/status
  1   1711088  /tftpboot/gate/c3600-i-mz 
[1711152 bytes used, 2483152 available, 4194304 total]
Source file name? admin/images/new-ios
Destination file name [admin/images/new-ios]? 
Verifying checksum for 'admin/images/new-ios' (file # 1)...  OK
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'admin/images/new-ios' from flash: device
  as 'admin/images/new-ios' into slot0: device WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 [OK - 3142748/4194304 bytes]
Flash device copy took 00:00:50 [hh:mm:ss]
Verifying checksum...  OK (0xB732)

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 The Cisco 7000 family cannot boot from ROM.

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 Booting from ROM is faster than booting from Flash memory. However, booting from Flash memory is faster and more reliable than booting from a network server.

Load the System Image from Flash Memory

Use the following sections to configure your router to boot from Flash memory. Flash memory can reduce the effects of network failure by reducing dependency on files that can only be accessed over the network.

Flash Memory Configuration Process

To configure the router to load a system image in Flash memory, perform the following steps:

Step 1 (Optional) Copy a system image or boot image to Flash memory using TFTP, rcp, and MOP. See the "Copy Images from a Network Server to Flash Memory" section for more information on performing this step.

Step 2 Configure the system to automatically boot from the desired file and location in Flash memory or bootflash memory. See the "Configure the Router to Automatically Boot from an Image in Flash Memory" section.

Step 3 (Optional) Depending on the current configuration register setting, you may need to change the configuration register value. See the "Modify the Configuration Register Boot Field" section for more information on modifying the configuration register.

Step 4 (Optional) For some platforms, to change the location of the boot image, set the BOOTLDR environment variable. See the "Set the BOOTLDR Environment Variable" section for details.

Step 5 Save your configurations.

Step 6 Power-cycle and reboot your system to ensure that all is working as expected.

Configure the Router to Automatically Boot from an Image in Flash Memory

To configure a router to automatically boot from an image in Flash memory, perform the following tasks:

Task Command
Step 1 Enter configuration mode from the terminal. configure terminal
Step 2 Enter the filename of an image stored in Flash memory. boot system flash [filename]

boot system flash [partition-number:][filename]

boot system flash [device:][filename] (Cisco 7000 family)

boot system flash [device:][partition-number:] filename (Cisco 1600 series and Cisco 3600 series)

Step 3 Set the configuration register to enable loading of the system image specified in the configuration file. config-register value1
Step 4 Exit configuration mode. end
Step 5 Save the configuration file to your startup configuration. copy running-config startup-config
Step 6 Optionally, verify the contents of the startup configuration. show startup-config
Step 7 Power-cycle and reboot the system to ensure that all works as expected. reload

1 Refer to the "Modify the Configuration Register Boot Field" section for more information on systems that can use this command to modify the software configuration register.

For routers which are partitioned, if you do not specify a partition, the router boots from the first partition. If you do not specify a filename, the router boots from the first valid image found in the partition.

If you enter more than one image filename, the router tries them in the order entered.

To remove a filename from the configuration file, enter the no boot system flash command and specify the file location.

Note The no boot system configuration command disables all boot system configuration commands regardless of argument. Specifying the flash keyword or the filename argument with the no boot system command disables only the commands specified by these arguments.

The following example shows how to configure the router to automatically boot from an image in Flash memory: 

Router# configure terminal
Router(config)# boot system flash gsnew-image
Router(config)# config-register 0x010F
Router(config)# end
Router# copy running-config startup-config
[ok]
Router# reload
[confirm]
%SYS-5-RELOAD: Reload requested
System Bootstrap, Version 4.6(0.16), BETA SOFTWARE
Copyright (c) 1986-1995 by cisco Systems
RP1 processor with 16384 Kbytes of memory
F3: 1871404+45476+167028 at 0x1000
Booting gsnew-image from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR [OK - 1916912/13767448 bytes]
F3: 1871404+45476+167028 at 0x1000
              Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
              170 West Tasman Drive
              San Jose, California 95134
GS Software (GS7), Version 10.2, 
Copyright (c) 1986-1995 by cisco Systems, Inc.
Compiled Thu 05-Nov-94 14:16 by mlw

Load the System Image from a Network Server

You can configure the Cisco IOS software to load a system image file from a network server using TFTP, rcp, or MOP.

If you do not boot from a network server using MOP and you do not specify either TFTP or rcp, by default the system image that you specify is booted from a network server via TFTP.

Note If you are using a Sun workstation as a network server and TFTP to transfer the file, set up the workstation to enable verification and generation of User Datagram Protocol (UDP) checksums. See the Sun documentation for details.

For increased performance and reliability, use rcp to boot a system image from a network server. The rcp implementation uses the Transmission Control Protocol (TCP), which ensures reliable delivery of data.

You cannot explicitly specify a remote username when you issue the boot command. Instead, the host name of the router is used. If the remote server has a directory structure, as do UNIX systems, and you boot the router from a network server using rcp, the Cisco IOS software searches for the system image on the server relative to the directory of the remote username.

You can also boot from a compressed image on a network server. One reason to use a compressed image is to ensure that there is enough memory available for storage. On routers that do not contain a run-from-ROM image in EPROM, when the router boots software from a network server, the image being booted and the running image both must fit into memory. If the running image is large, there might not be room in memory for the image being booted from the network server.

If there is not enough room in memory to boot a regular image from a network server, you can produce a compressed software image on any UNIX platform using the compress command. Refer to your UNIX platform's documentation for the exact usage of the compress command.

To specify the loading of a system image from a network server, complete the following tasks:

Task Command
Step 1 Enter configuration mode from the terminal. configure terminal
Step 2 Specify the system image file to be booted from a network server using rcp, TFTP, or MOP. boot system [rcp | tftp] filename [ip-address]

boot system mop filename [mac-address] [interface]

Step 3 Set the configuration register to enable loading of the image specified in the configuration file. config-register value1
Step 4 Exit configuration mode. end
Step 5 Save the configuration file to your startup configuration. copy running-config startup-config

1 Refer to the "Modify the Configuration Register Boot Field" section for more information on systems that can use this command to modify the software configuration register.

In the following example, a router uses rcp to boot from the testme5.tester system image file on a network server at IP address 172.16.0.1:

Router# configure terminal
Router(config)# boot system rcp testme5.tester 172.16.0.1
Router(config)# config-register 0x010F
Router(config)# end
Router# copy running-config startup-config

Load the System Image from ROM

To specify the use of the ROM system image as a backup to other boot instructions in the configuration file, complete the following tasks:

Task Command
Step 1 Enter configuration mode from the terminal. configure terminal
Step 2 Specify use of the ROM system image as a backup image. boot system rom
Step 3 Set the configuration register to enable loading of the system image specified in the configuration file. config-register value1
Step 4 Exit configuration mode. end
Step 5 Save the configuration file to your startup configuration. copy running-config startup-config

1 Refer to the "Modify the Configuration Register Boot Field" section for more information on the configuration register.

In the following example, a router is configured to boot from ROM:

Router# configure terminal
Router(config)# boot system rom 
Router(config)# config-register 0x010F
Router(config)# end
Router# copy running-config startup-config
Note The Cisco 7000 family cannot load from ROM.

Use a Fault-Tolerant Booting Strategy

Occasionally network failures make booting from a network server impossible. To lessen the effects of network failure, consider the following booting strategy. After Flash is installed and configured, you might want to configure the router to boot in the following order:


  1. Boot an image from Flash.

  2. Boot an image from a system file on a network server.

  3. Boot from ROM image.

This boot order provides the most fault-tolerant booting strategy. Perform the following tasks to allow the router to boot first from Flash, then from a system file from a network server, and finally from ROM:

Task Command
Step 1 Enter configuration mode from the terminal configure terminal
Step 2 Configure the router to boot from Flash memory. boot system flash [filename]

boot system flash [partition-number:][filename]

boot system flash [device:][filename] (Cisco 7000 family)

boot system flash [device:][partition-number:] filename (Cisco 1600 series and Cisco 3600 series)

Step 3 Configure the router to boot from a network server. boot system [rcp | tftp] filename [ip-address]
Step 4 Configure the router to boot from ROM. boot system rom
Step 5 Set the configuration register to enable loading of the system image specified in the configuration file. config-register value1
Step 6 Exit configuration mode. end
Step 7 Save the configuration file to your startup configuration. copy running-config startup-config

1 Refer to the "Modify the Configuration Register Boot Field" section for more information on systems that can use this command to modify the software configuration register.

In the example, a router is configured to first boot an internal Flash image called gsxx. Should that image fail, the router will boot the configuration file gsxx from a network server. If that method should fail, then the system will boot from ROM.

Router# configure terminal
Router(config)# boot system flash gsxx
Router(config)# boot system gsxx 172.16.101.101
Router(config)# boot system rom
Router(config)# config-register 0x010F
Router(config)# end
Router# copy running-config startup-config
[ok]

Using this strategy, a router has three alternative sources from which to boot. These alternative sources help lessen the negative effects of a failure on network or file server.

Recovering a System Image Using Xmodem or Ymodem (Cisco 1600 series and Cisco 3600 series only)

If you do not have access to a network server and need to download a system image (to update it, or if all the system images in Flash memory somehow are damaged or erased), you can copy an image from a local or remote computer (such as a PC, UNIX workstation, or Macintosh) using the Xmodem or Ymodem protocols. This functionality primarily serves as a disaster recovery technique and is illustrated in Figure 9.

Xmodem and Ymodem are common protocols used for transferring files and are included in applications such as Windows 3.1 (TERMINAL.EXE), Windows 95 (HyperTerminal), Windows NT 3.5x (TERMINAL.EXE), Windows NT 4.0 (HyperTerminal), and Linux UNIX freeware (minicom).

Cisco 3600 series routers do not support XBOOT functionality, a disaster recovery technique for Cisco IOS software, and do not have a separate boot helper (rxboot) image.

Xmodem and Ymodem downloads are slow, so you should use them only when you do not have access to a network server. You can speed up the transfer by setting the transfer port speed to 115200 bps.

On the Cisco 3600 series, you can perform the file transfer using Cisco IOS software or, if all local system images are damaged or erased, the ROM monitor. When you use Cisco IOS software for an Xmodem or Ymodem file transfer, the transfer can occur on either the AUX port or the console port. The AUX port, which supports hardware flow control, is recommended. File transfers from the ROM monitor must use the console port.

On the Cisco 1600 series, you can only perform the file transfer from the ROM monitor over the console port.


Figure 9: Copying a System Image to a Cisco 3600 Series Router with Xmodem

or Ymodem

To copy a Cisco IOS image from a computer or workstation to a router using the Xmodem or Ymodem protocol, enter one of the following commands:

Task Command
For the Cisco 3600 only, copy a system image from a computer to Flash memory using Cisco IOS software in EXEC mode. copy xmodem device:[partition:][filename]

or

copy ymodem device:[partition:][filename]

Copy a system image from a computer to Flash memory using the ROM monitor. xmodem [-y] [-c] [-e] [-f] [-r] [-x] [-s data-rate][filename] (Cisco 1600 series only)

xmodem [-c | -y | -r | -x] [filename] (Cisco 3600 series only)

The -c option provides CRC-16 checksumming; -y uses the Ymodem protocol; -e erases the first partition in Flash memory; -f erases all of Flash memory; -r downloads the image to DRAM (the default is Flash memory); and -x prevents the image from executing after download; and -s sets the console port data rate.

The computer from which you transfer the Cisco IOS image must be running terminal emulation software and the Xmodem or Ymodem protocol.

For the Cisco 1600 series, if you include the -r option (download to DRAM), your router must have enough DRAM to hold the file being transferred. To run from Flash memory, an image must be positioned as the first file in Flash memory. If you are copying a new image to boot from Flash memory, erase all existing files first.

Xmodem Transfer Example Using the Cisco IOS Software (Cisco 3600 series only)

This example shows a file transfer using Cisco IOS software and the Xmodem protocol. The Ymodem protocol follows a similar procedure, using the copy ymodem command.

To transfer a Cisco IOS image from a computer running terminal emulation software and the Xmodem protocol, follow these steps:

Step 1 Place a Cisco IOS software image on the remote computer's hard drive. You can download an image from Cisco Connection Online.

Step 2 To transfer from a remote computer, connect a modem to the AUX port of your Cisco 3600 series router and to the standard telephone network. The AUX port is set by default to a speed of 9600 bps, 2 stop bits, and no parity. The maximum speed is 115200 bps. Configure the router for both incoming and outgoing calls by entering the modem inout command.

Connect a modem to the remote computer and to the telephone network. The remote computer dials through the telephone network and connects to the router.


To transfer from a local computer, connect the router's AUX port to a serial port on the computer, using a null-modem cable. The AUX speed configured on the router must match the transfer speed configured on the local computer.


Step 3 At the EXEC prompt in the terminal emulator window of the computer, enter the copy xmodem flash: command:

Press Enter to continue.


Step 4 Specify whether to use cyclic redundancy check (CRC) block checksumming, which verifies that your data has been correctly transferred from the computer to the router. If your computer does not support CRC block checksumming, answer no at the prompt:

Step 5 Determine how many times the software should try to receive a bad block of data before it declares the copy operation a failure. The default is 10 retries. A higher number may be needed for noisy telephone lines. You can configure an unlimited number of retries.

Step 6 Decide whether you want to check that the file is a valid Cisco 3600 series image:

After the transfer has begun, and if the image is valid, the software checks to see whether enough Flash memory space exists on the router to accommodate the transfer:


Step 7 Enter the destination filename:

Step 8 If you don't want the contents of internal Flash memory erased before the file transfer, enter no:

Step 9 Start an Xmodem or Ymodem send operation with the terminal emulation software on the computer that is sending the system image to the router. See your emulation software application's manual for instructions on how to execute a file transfer. Depending on the application you use, the emulation software may display the progress of the file transfer.

Xmodem Transfer Example Using the ROM Monitor

This example shows a file transfer using the ROM monitor and the Xmodem protocol. To transmit with the Ymodem protocol, use the xmodem -y command.

For the Cisco 3600, the router must have enough DRAM to hold the file being transferred, even if you are copying to Flash memory. The image is copied to the first file in internal Flash memory. Any existing files in Flash memory are erased. Copying files to Flash partitions or to the second-file position is not supported.

Caution A modem connection from the telephone network to your console port introduces security issues that you should consider before enabling the connection. For example, remote users can dial into your modem and access the router's configuration settings.

Step 1 Place a Cisco IOS software image on the remote computer's hard drive. You can download an image from Cisco Connection Online or from the Feature Pack (Cisco 1600 series only).

Step 2 To transfer from a remote computer, connect a modem to the console port of your router and to the standard telephone network. The modem and console port must communicate at the same speed, which can be from 9600 to 115200 bps (Cisco 3600 series) or from 1200 to 115200 bps (Cisco 1600 series), depending on the speed supported by your modem. Use the confreg ROM monitor command to configure the console port transmission speed for the router. For the Cisco 1600 series, you can also set the transmission speed with the -s option.

Connect a modem to the remote computer and to the telephone network. The remote computer dials through the telephone network and connects to the router.


To transfer from a local computer, connect the router's console port to a serial port on the computer, using a null-modem cable. The console port speed configured on the router must match the transfer speed configured on the local computer.


Step 3 You should see a ROM monitor prompt in the terminal emulation window:

Enter the xmodem ROM monitor command, along with any desired copy options and, optionally, the filename of the Cisco IOS image. The image loads into Flash memory by default; to download to DRAM instead, use the -r option. The image is normally executed on completion of the file transfer; to prevent execution, use the -x option. The -c option specifies CRC-16 checksumming, which is more sophisticated and thorough than standard checksumming, if it is supported by the computer:


Step 4 Start an Xmodem send operation, which is initiated from the terminal emulation software on the remote computer that is sending the system image to the router. See your emulation software application's manual for instructions on how to execute a Xmodem file transfer.

Step 5 The Cisco IOS image is transferred and executed. If you are transferring from a remote computer, the computer maintains control of your console port even after the new Cisco IOS image is running. To release control to a local terminal, reconfigure the speed of the router's console port to match the speed of the local terminal by entering the speed bps configuration command from the remote computer at the router prompt:

The remote connection is broken, and you can disconnect the modem from the console port and reconnect the terminal line.


Load and Display Microcode Images

On the Cisco 7000 series with RSP7000 and Cisco 7500 series, you can also load and display microcode images, as described in the following sections:

Understand Microcode Images

Microcode images contain microcode which runs on various hardware devices. By default, the system loads the microcode bundled with the system software. However, you can configure the router to use microcode stored in Flash.

Cisco 7000 series with a RSP7000 and Cisco 7500 series each have a writable control store (WCS) which stores microcode. You can load updated microcode onto the WCS from bootflash or a Flash memory card inserted in one of the PCMCIA slots of the RSP card.

You can update microcode without having physical access to the router.

Specify the Location of the Microcode Images

By default, the system loads the microcode bundled with the system software. However, you can configure the router to load different microcode.

Specify the location of the microcode to use, complete the following tasks:

Task Command
Step 1 (Optional) Copy microcode files into Flash. You only need to if you are loading the microcode from Flash.

See the section "Copy Images from a Network Server to Flash Memory" for more information about how to copy TFTP images to Flash memory.

 copy tftp flash

or

copy tftp file-id

Step 2 Enter configuration mode. configure terminal
Step 3 Configure the router to load microcode into the WCS from Flash memory or the system image. By default, the microcode bundled with the system image is loaded. microcode interface [flash filename [slot] | system [slot]]

Step 4 Exit configuration mode. end
Step 5 Retain new configuration information when the system is rebooted. copy running-config startup-config

If an error occurs when you are attempting to download microcode, the system loads the default system microcode image, which is bundled with the system software.

Note Microcode images cannot be compressed.

Reload the Microcode Image

The configuration commands specifying the microcode are implemented following one of three events:

After you have entered a microcode configuration command and one of these events has taken place, all cards are reset, loaded with microcode from the appropriate sources, tested, and enabled for operation.

To signal to the system that all microcode configuration commands have been entered and the processor cards should be reloaded, complete the following task in global configuration mode:

Task Command
Notify the system that all microcode configuration commands have been entered and the processor cards should be reloaded. microcode reload

If Flash memory is busy because a card is being removed or inserted, or a microcode reload command is executed while Flash is locked, the files will not be available and the onboard ROM microcode will be loaded. Issue another microcode reload command when Flash memory is available, and the proper microcode will be loaded. The show flash command will show if another user or process has locked Flash memory.

Note The microcode reload command should not be used while Flash is in use. For example, do not use this command when a copy tftp flash or show flash command is active.

The microcode reload command is automatically added to your running configuration when you issue a microcode command that changes the system's default behavior of loading all processors from ROM.

Display Microcode Image Information

To display microcode information, perform the following task in EXEC mode:

Task Command
Display microcode information. show microcode


hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1997 © Cisco Systems Inc.