|
|
Cisco IOS Release 11.2(5)P provides software support for the Cisco 3600 series of modular access routers, comprising the Cisco 3640 and Cisco 3620 routers. This feature chapter explains how to display information about system images and configuration files; how to copy these images and files to and from Flash memory, network servers, and remote PCs; how to configure the boot device; and how to reallocate main memory and shared memory. It also contains an update to the command reference publications.
The modular design of Cisco 3600 series routers allows you to configure or reconfigure the router with the types of interfaces that your network needs.
This document makes use of the following term:
Image or system image--The Cisco IOS image.
Flash memory PC card or PCMCIA card--A Flash memory card that is inserted in to a Personal Computer Memory Card International Association (PCMCIA) slot. This card is used to store system images and configuration files.
Cisco 3600 series routers contain the following memory systems:
The following platforms are supported:
This section explains optional Cisco 3600 series configuration tasks and gives examples of them. It contains the following topics:
Many commands use the device: argument to specify a Flash memory device. In Cisco 3600 series routers, the device can be internal Flash memory (flash:) or a Flash memory PC card inserted in one of the PCMCIA slots (slot0: or slot1:). A colon (:) always follows the device type.
Some commands also include a partition number or a filename, in the form device:[partition-number:][filename]. If a filename follows the partition number, you must also enter a colon after the partition number.
For example, flash: means internal Flash memory; flash:1 means the first partition in internal Flash memory; and flash:1:c3620-i-mz.112-5P means a particular file in the first partition in internal Flash memory.
To display information about system software, system image files, and configuration files, enter the following commands in EXEC mode:
Refer to the Cisco IOS Release 11.2 configuration guides and command references for examples of these commands.
The Flash memory content listing does not include the checksum of individual files. To recompute and verify the image checksum after the image is copied into Flash memory, enter the following command in EXEC mode:
| Task | Command |
|---|---|
| Recompute and verify the image checksum after the image is copied into a Flash memory device. | verify device:[partition-number:][filename] |
For an example of how to verify the checksum of a file, see the "Configuration Examples" section later in this chapter.
To partition Flash memory, enter the following command in global configuration mode:
| Task | Command |
|---|---|
| Partition Flash memory | partition device: [number-of-partitions][partition-size] |
The number of partitions that you can create in a Flash memory device equals the number of banks in the device. Enter the show device: all command to view the number of banks on the Flash memory device. The number of partition size entries you set must be equal to the number of specified partitions. For example, the partition slot0: 2 8 8 command configures two partitions to be 8 MB in size each. The first 8 corresponds to the first partition; the second 8 corresponds to the second partition.
This task succeeds only if the router has at least two banks of Flash memory and the partitioning does not split an existing file in Flash memory across two or more partitions.
You can download a file, such as a configuration file or a Cisco IOS image, from a Trivial File Transfer Protocol (TFTP), remote copy protocol (rcp), or Maintenance Operation Protocol (MOP) network server to a local Flash memory device. To download the file, enter one of the following commands in EXEC mode:
| Task | Command |
|---|---|
| Download a file from a TFTP server into a Flash partition. | copy tftp device:[partition-number:][filename] |
| Download a file from an rcp server into a Flash partition. | copy rcp device:[partition-number:][filename] |
| Download a file from a MOP server into a Flash partition. | copy mop device:[partition-number:][filename] |
For examples of how to copy files from remote TFTP, rcp, or MOP servers to Flash memory, see the "Configuration Examples" section later in this chapter.
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:
During a copy operation, a pound sign (#) means that a Flash memory device is being cleared and initialized. 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.
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.
The minimum version of Cisco IOS software that runs on a Cisco 3600 series router depends on the network modules and WAN interface cards installed in the router. See your router installation guide and configuration notes for further information.
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. If internal Flash memory does not contain a valid image, you must boot from an image on a Flash memory PC card, or download an image using Xmodem or Ymodem. |
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. The software informs you of these conditions and prompts you for a response.
Filenames in Flash memory can be up to 63 characters long; they are not case-sensitive and are always converted to lowercase. A prompt alerts you when a file with the same name as the one you want to copy (regardless of case) already exists in Flash memory. If you proceed with the copy, the old file is "deleted." The old file still resides in Flash memory, but it is rendered unusable in favor of the newer version, and the show flash command lists it with a "deleted" tag. If you terminate the copy process before it is finished, the newer file is marked "deleted" because the file was not copied completely and is not valid. In this case, the original file in Flash memory remains valid.
To clear the contents of your startup configuration, enter the following command in EXEC mode:
| Task | Command |
|---|---|
| Clear the contents of your startup configuration. This command erases the contents of NVRAM. | erase startup-config |
To erase a saved configuration from a specific Flash memory device, enter the erase command beginning in EXEC mode:
| Task | Command |
|---|---|
| Erase a specified configuration file, all files on a device, or all files in a partition. | erase device:[partition-number] |
When you erase (or, equivalently, delete) a file, the system software marks the file as deleted, allowing you to recover it later with the undelete command as long as the file has not been overwritten.
For an example of how to erase a file from Flash memory, see the "Configuration Examples" section later in this chapter.
To copy a configuration file from a TFTP server, rcp server, or Flash memory directly to your startup configuration in NVRAM or your running configuration, enter one of the following commands in EXEC mode:
| Task | Command |
|---|---|
| Load a configuration file directly into NVRAM. | Choose one of the following commands. Your choice is dependent on where the source file is located: |
For an example of how to copy a file from a local Flash memory device to the startup configuration, see the "Configuration Examples" section later in this chapter.
On Cisco 3600 series routers, you can copy files from one Flash memory device, such as internal Flash memory or a Flash memory card in a PCMCIA slot, to another Flash memory device. Copying files to different Flash memory devices lets you create backup copies of working configurations and duplicate configurations for other routers. See Figure 1.
To copy a configuration file 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 a system image between Flash memory devices. | copy device:[partition-number:][filename] device:[partition-number:][filename] |
| Step 3 Verify the checksum of the file you copied. | verify device: [partition-number:][filename] |
Use the copy device:[partition-number:][filename] device:[partition-number:][filename] command to copy files between Flash memory devices. The first device argument in the command identifies the source device; the second identifies the destination device.
For an example of how to copy a file between local Flash memory devices, see the "Configuration Examples" section later in this chapter.
To configure the router to function as a TFTP server and specify a Flash memory device and filename, enter the following command in global configuration mode:
| Task | Command |
|---|---|
| Configure the router and specify a Flash memory device and filename. | tftp-server flash [device:][partition-number:]filename |
Exit configuration mode and save the configuration information to your startup configuration.
This section explains how to configure your Cisco 3600 series router to boot from Flash memory, either internal Flash memory or a Flash memory PC card, or from a network server.
If your router is configured to boot automatically, but it does not find a valid system image, or if its configuration file is corrupted at startup, it enters ROM monitor mode. You can use the ROM monitor to load a system image manually from one of the following devices:
The Cisco 3600 series does not use a dedicated boot helper image such as rxboot, which many other routers use to help with the boot process. Instead, the first system image in Flash memory is identified as the default boot helper. You can override this default by setting the ROM monitor environment variable BOOTLDR to point to another system image. The boot helper image is invoked any time the ROM monitor does not recognize the specified Flash memory device as valid for the boot process, whether booting is performed manually or automatically.
You can also configure the router to enter ROM monitor mode directly by setting the boot bits to 0 in the configuration register.
To boot manually from Flash memory, complete the following tasks:
For examples on how to boot from Flash memory, see the "Configuration Examples" section later in this document.
To configure a router to boot automatically from an image in Flash memory, perform the following tasks:
| Task | Command |
|---|---|
| Step 1 Enter global configuration mode. | configure terminal |
| Step 2 Enter the filename of an image in internal Flash memory or a Flash memory PC card. | Enter one of the following commands:
|
|
Step 3 Set the configuration register to enable loading of the system image from Flash memory. | config-register value |
| Step 4 Exit configuration mode. | ^Z |
| Step 5 Save the configuration file to your startup configuration in NVRAM. | copy running-config startup-config1 |
| Step 6 Optionally, verify the contents of the startup configuration. | show startup-config |
| Step 7 Power-cycle and reboot the router to ensure that it boots properly. | reload |
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 filename command.
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 2.
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.
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.
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 |
| 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 [-c | -y | -r | -x] [filename]
The -c option provides CRC-16 checksumming; -y uses the Ymodem protocol; -r downloads the image to DRAM (the default is Flash memory); and -x prevents the image from executing after download. |
The computer from which you transfer the Cisco IOS image must be running terminal emulation software and the Xmodem or Ymodem protocol.
For an example of how to download a system image using the Xmodem or Ymodem protocol, refer to the "Configuration Examples" section later in this chapter.
DRAM memory in Cisco 3600 series routers is organized as one contiguous address space divided between processor memory and I/O memory. Depending on the type and number of network interfaces you have configured in the router, you may need to reallocate the DRAM memory partitioned to processor memory and I/O memory.
Cisco manufacturing configures most Cisco 3600 series routers to have 25 percent of the address space allocated to I/O memory and 75 percent allocated to processor memory. But for customer orders that require two or more ISDN PRI interfaces, DRAM memory is configured to provide 40 percent of the address space for I/O memory and 60 percent for processor memory. (See Figure 3.) Cisco Systems performs these DRAM memory adjustments before it ships each router.
However, there are cases where you may have to manually reallocate the DRAM memory split between processor memory and I/O memory after you have received a router from Cisco Systems.
For example, suppose you receive a Cisco 3640 router with the following running configuration:
Later on however, you add a 4-port ISDN BRI network module to the router. You now have a total of 12 ISDN BRI interfaces running on the router. At this point, you must use the memory-size iomem command to configure 40 percent of the address space for I/O memory and 60 percent for processor memory.
To view your current mix of processor and I/O memory and reassign memory distribution accordingly, enter the following commands beginning in privileged EXEC mode:
| Task | Command |
|---|---|
| Step 1 View the total amount of memory loaded on the router. | show version |
| Step 2 Determine the amount of free memory. | show memory1 |
| Step 3 Enter global configuration mode. | configure terminal |
| Step 4 Allocate processor memory and I/O memory. | memory-size iomem I/O-memory-percentage2 |
| Step 5 Exit global configuration mode. | exit |
| Step 6 Write the new configuration to NVRAM. | copy running-config startup-config |
| Step 7 Reload the router to run the new image. | reload |
Valid I/O memory percentage values are 25, 30, 40 (the default), and 50. I/O memory size is the specified percentage of total memory size, rounded down to the nearest multiple of 1 MB. The remaining memory is processor memory.
The memory-size iomem command does not take effect until you save it to NVRAM using the copy running-config startup-config EXEC command and reload the router. However, when you enter the command, the software checks whether the new memory distribution leaves enough processor memory for the currently running Cisco IOS image. If not, the following message appears:
Warning: Attempting a memory partition that does not provide enough Processor memory for the current image.If you write memory now, this version of software may not be able to run.
When you enter the reload command to run a new image, the software calculates the new processor and I/O memory split. If there is not enough processor memory, it automatically reduces I/O memory to an alternative setting to load the image. If there is still not enough processor memory for the image to run, then you do not have enough DRAM.
See the next section "Configuration Examples" for an example of how to configure the memory-size iomem command.
This section provides configuration examples for the new software features introduced for Cisco 3600 series routers.The following examples are described:
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:
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 ?<no> for partition directory; ? for full directory; q to abort] Which partition? [default = 1]4PCMCIA 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.testVerifying checksum for 'c3600-i-mz.test' (file # 2)... OK
You can copy a configuration file or Cisco IOS image from a TFTP server either with or without specifying its destination partition and filename in the command line. This section describes both methods.
To copy a file from a TFTP server to a Flash memory location specified in the command line, follow these steps:
Step 1 If you are copying a system software image, make a backup copy of the current image. See the section "Copy a File from a Flash Memory Device to a Server Examples" later in this chapter for instructions.
Step 2 From EXEC mode, enter the copy tftp flash: command, and include the destination partition and destination filename options in the command line:
copy tftp flash:1:c3600-i-mz
In this example, the router reports one partition and one file in internal Flash memory:
Step 3 Enter or confirm the IP address of the remote TFTP server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 4 Enter or confirm the source filename on the remote server:
If you entered a destination filename in the command line, this filename is interpreted as the source filename by default. In this case, press Enter. If you want to specify a source filename, enter the complete UNIX path name, such as newios/3600/c3600-i-mz, after the question mark (?).
Step 5 Decide whether you want to erase existing files in Flash memory during the copy operation. Press Enter to confirm erasing the files:
Step 6 You are asked again to confirm erasing the files in Flash memory:
The system software asks you one more time to confirm the copy operation before the file is copied:
yes
The system software loads the file from the remote server, copies it into the router's internal Flash memory, and verifies the copy:
The duration of the copy operation is displayed in hours, minutes, and seconds:
To copy a file from a TFTP server to a Flash memory location that is not specified in the command line, follow these steps:
Step 1 If you are copying a system software image, make a backup copy of the current image. See the section "Copy a File from a Flash Memory Device to a Server Examples" for instructions.
Step 2 From EXEC mode, enter the copy tftp flash: command without specifying the destination partition and destination filename:
copy tftp flash:
The contents of Flash memory are displayed. In this case, two partitions are present:
Step 3 Specify the destination partition to copy the remote file into. The first partition is the default. Press Enter to accept the default setting:
The file c3600-i-mz already exists in this partition:
Step 4 Enter or confirm the IP address of the remote TFTP server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 5 Enter the complete UNIX path name of the source file. In this example, the path name /images/3600/c3600-i-mz is entered to copy the file c3600-i-mz:
images/3600/c3600-i-mz
Step 6 By default, the entire source path name is entered as the destination filename. To shorten or change this filename, enter the new name after the question mark (?) and press Enter:
images/3600/c3600-i-mz]?
The remote file is accessed and loaded using interface Ethernet 1/0:
Step 7 Decide whether you want to erase the existing files in Flash memory during the copy operation. Press Enter to confirm erasing the files:
Step 8 You are asked again to confirm erasing the files in Flash memory:
Step 9 The system software asks you one more time to confirm the copy operation before Flash memory is erased and the file is copied:
yes
You can copy a file from a remote rcp server either with or without specifying its destination partition (and, optionally, its filename) in the command line. This section describes both methods.
For the copy rcp command to execute properly, an account must be defined on the network server for the remote username configured on the router. The path for all files and images to be copied begins at the remote user's home directory.
By default, the router software sends the remote username associated with the current TTY process, if that name is valid. 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. If the remote username is invalid, the software uses the router host name as both the remote and local usernames.
You can override the default remote username by using the ip rcmd remote-username command. 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.
To copy a file from a remote rcp server to a Flash partition specified in the command line, follow these steps:
Step 1 If you are copying a system software image, make a backup copy of the current image. See the section "Copy a File from a Flash Memory Device to a Server Examples" later in this chapter for instructions.
Step 2 From EXEC mode, enter the copy rcp command, specifying the destination device (slot0: in this example) and partition (3 in this example):
copy rcp slot0:3
Step 3 Enter or confirm the IP address of the remote rcp server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 4 Enter the complete UNIX path name of the source file. In this example, the path name /tftpboot/gate/c3600-i-mz is entered to copy the file c3600-i-mz:
/tftpboot/gate/c3600-i-mz
Step 5 By default, the entire source path name is entered as the destination filename. To shorten or change this filename, enter the new name after the question mark (?) and press Enter:
Step 6 Decide whether you want to erase the existing files in Flash memory during the copy operation. Press Enter to confirm erasing the files:
Step 7 You are asked again to confirm erasing the files in Flash memory:
Step 8 The system software asks you one more time to confirm the copy operation before Flash memory is erased and the file is copied:
yes
To copy a file from a remote rcp server to a Flash memory PC card in slot 0 without specifying a destination partition and filename, follow these steps:
Step 1 If you are copying a system software image, make a backup copy of the current image. See the section "Copy a File from a Flash Memory Device to a Server Examples" for instructions.
Step 2 From EXEC mode, enter the copy rcp slot0: command:
copy rcp slot0:
Because a destination partition and destination filename were not specified in the command line, you will be prompted for these values during the copy operation. The router reports that there are four partitions in the PC card and lists their read and write permissions:
Step 3 Specify the destination partition to copy the remote file into. The first partition is the default. Press Enter to accept the default setting:
The file c3600-j-mz already exists in partition 1:
Step 4 Enter or confirm the IP address of the remote rcp server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 5 Enter the complete UNIX path name of the source file. In this example, the path name /tftpboot/gate/c3600-i-mz is entered to copy the file c3600-i-mz:
/tftpboot/gate/c3600-i-mz
Step 6 By default, the entire source path name is entered as the destination filename. To shorten or change this filename, enter the new name after the question mark (?) and press Enter:
Step 7 Decide whether you want to erase the existing files in Flash memory during the copy operation. Press Enter to confirm erasing the files:
Step 8 You are asked again to confirm erasing the files in Flash memory:
Step 9 The system software asks you one more time to confirm the copy operation before Flash memory is erased and the file is copied:
yes
In the following example, the system image routerimage, which already exists in internal Flash memory, is copied from a MOP server. There is enough space in Flash memory to copy the new file without erasing any existing files.
Step 1 If you are copying a system software image, make a backup copy of the current image. See the section "Copy a File from a Flash Memory Device to a Server Examples" later in this chapter for instructions.
Step 2 From EXEC mode, enter the copy mop flash: command:
copy mop flash:
The contents of Flash memory are displayed. In this case, two partitions are present:
Step 3 Specify the partition device you want to copy the remote file into. The first partition is the default. Press Enter to accept the default setting:
The router reports that one partition and two files exist in internal Flash memory:
Step 4 Enter the name of the source file:
routerimage
Step 5 By default, the source filename is entered as the destination filename. To shorten or change this filename, enter the new name after the question mark (?) and press Enter:
Step 6 Decide whether you want to erase the existing files in Flash memory during the copy operation. Press Enter to confirm erasing the files:
Step 7 You are asked again to confirm erasing the files in Flash memory:
Step 8 The system software asks you one more time to confirm the copy operation before Flash memory is erased and the file is copied:
yes
The following example erases all files in the second partition in internal Flash memory:
Router#erase flash:2System flash directory, partition 2: File Length Name/status 1 1711088 dirt/gate/c3600-i-mz [1711152 bytes used, 15066064 available, 16777216 total] Erase flash device, partition 2? [confirm] Are you sure? [yes/no]:yesErasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
The following example copies the file ios-upgrade-1 from partition 4 of the Flash memory PC Card in slot 0 to the router's startup configuration:
Router#copy slot0:4:ios-upgrade-1 startup-configCopy 'ios-upgrade-1' from flash device as 'startup-config' ? [yes/no]yes[OK]
You can copy a file between devices either with or without specifying partitions (and, optionally, filenames) in the command line. This section describes both methods.
To copy a file from a specified partition on one Flash memory device to another Flash memory device on the same router, follow these steps:
Step 1 From EXEC mode, enter the copy command, specifying the source Flash memory device, source partition, and destination Flash memory device:
copy flash:1 slot0:
The file structure for partition 1 of the source device (internal Flash memory) is displayed first:
Step 2 The partition structure for the destination device (the Flash memory card in slot 0) is displayed next. All partitions are shown because none was specified:
Specify the destination partition to copy the file into. The first partition is the default. Press Enter to accept the default setting.
Step 3 Enter the UNIX path name that leads to the source file (new-ios in this example):
dirt/admin/images/new-ios
Step 4 Enter or confirm the destination filename. The source path name and filename, shown in brackets, is the default:
Step 5 Decide whether to erase the Flash memory PC card:
Step 6 Confirm that the source filename, destination filename, and erase Flash options are correct:
yes
To copy a file from internal Flash memory to a PC card without specifying a partition number or filename in the command line, follow these steps:
Step 1 From EXEC mode, enter the copy command, specifying the source and destination Flash memory devices:
copy flash: slot1:
Step 2 The contents of the source device (internal Flash memory) are displayed:
Specify the source partition that contains the source file. The default is the first partition:
Step 3 The contents of the destination device (Flash memory on the PC card in slot 1) are displayed:
Specify the source filename:
running-config
Step 4 Enter or confirm the destination filename. The source filename, shown in brackets, is the default setting. Press Enter to accept the default setting.
Step 5 Decide whether to erase the Flash memory PC card:
yes
You can copy a file or system image from a Flash memory device to a TFTP or rcp network server for distribution or backup.
In some implementations of TFTP, you must 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.
You can copy a configuration file or Cisco IOS image to a TFTP server either with or without specifying the source partition and filename in the command line. This section gives examples of several alternatives.
In this example, the source partition number is specified in the command line.
Step 1 Enter the copy slot0:2 tftp command, identifying the source partition as partition 2 of the Flash memory PC card in slot 0:
copy slot0:2 tftp
Step 2 Enter or confirm the IP address of the remote TFTP server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 3 Enter the source filename:
your-ios
Step 4 Enter the destination UNIX path name on the TFTP server:
/sysadmin/images/server-ios
yes
In this example, the source partition number and filename are specified in the command line.
Step 1 Enter the copy slot0: tftp command, including the source partition and filename:
copy slot0:4:your-ios tftp
The system software does not display Flash memory contents, because all required information is specified in the command line.
Step 2 Enter or confirm the IP address of the remote TFTP server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 3 Enter the destination UNIX path name on the TFTP server:
dirt/images/c3640-j-mz
yes
To copy a system image from a Flash memory card in slot 0 to a remote TFTP server, follow these steps:
Step 1 Enter the copy slot0: tftp command:
copy slot0: tftp
The system software displays the contents of the Flash memory PC card.
Step 2 Specify the partition that contains the source file. Partition 1 is the default. Press Enter to accept the bracketed value.
The file "your-ios" is shown in partition 1:
Step 3 Enter or confirm the IP address of the remote TFTP server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 4 Enter the source filename:
your-ios
Step 5 Enter the destination UNIX path name on the TFTP server:
dirt/sysadmin/your-ios
Step 6 Confirm that the copy settings are correct:
yes
You can also copy a system image from Flash memory to an rcp network server. If you copy the system image to a personal computer used as a file server, the computer must support the rcp protocol.
For the rcp command to execute properly, an account must be defined on the network server for the remote username configured on the router. The path for all files and images to be copied begins at the remote user's home directory.
By default, the router software sends the remote username associated with the current TTY process, if that name is valid. 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. If the remote username is invalid, the software uses the router host name as both the remote and local usernames.
You can override the default remote username by using the ip rcmd remote-username command. 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.
You can copy a Cisco IOS image to an rcp server either with or without specifying the source partition and filename in the command line. This section describes both methods.
To copy a file from the Flash memory PC card in slot 1 to an rcp server without specifying the source partition and filename in the command line, follow these steps:
Step 1 Enter the copy slot1: rcp command:
copy slot1: rcp
Step 2 Enter the IP address of the remote host. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 3 Enter the source file that you want to copy from the Flash memory PC card:
your-ios
Step 4 Confirm or rename the UNIX destination path name and filename:
/sysadmin/images/your-ios
Step 5 Confirm that the copy settings are correct:
yes
In this example, the source partition number and filename are specified in the command line.
Step 1 Enter the copy slot1:1:your-ios rcp command, specifying the partition number and filename:
copy slot1:1:your-ios rcp
Step 2 Enter the IP address of the rcp server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 3 Enter the destination path name and filename:
/sysadmin/images/your-ios
Step 4 Confirm that the copy settings are correct:
yes
The following command instructs the ROM monitor to boot the first file in the first partition of internal Flash memory:
> boot flash:
This command instructs the ROM monitor to boot the first file in the first partition of the Flash memory card in slot 0:
> boot slot0:
This command instructs the ROM monitor to boot the first file in the second partition of the Flash memory card in slot 0:
> boot slot0:2:
In this example, the ROM monitor boots the file named imagename from the third partition of the Flash memory card in slot 0:
> boot slot0:3:imagename
The following command fails to specify a valid device type (flash:, slot0:, or slot1:), so the ROM monitor invokes the boot helper to boot a system image.
> boot flash
You can copy files using the Cisco IOS software or the ROM monitor. Both methods are described in this section.
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 or from the Documentation CD-ROM.
The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
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:
copy xmodem flash:
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:
no
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.
7
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:
new-ios-image
Step 8 If you don't want the contents of internal Flash memory erased before the file transfer, enter no:
no
yes
Step 9 Start an Xmodem or Ymodem send operation with the computer's terminal emulation software. This is 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.
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.
Your 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 Documentation CD-ROM.
The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Step 2 To transfer from a remote computer, connect a modem to the console port of your Cisco 3600 series 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, depending on the speed supported by your modem. Use the confreg ROM monitor command to configure the console port transmission speed for the router.
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:
xmodem -c new-ios-image
yes
Step 4 Start an Xmodem send operation, which is initiated from the remote computer's terminal emulation software. This is 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 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:
configure terminal
line 0
speed 9600
The remote connection is broken, and you can disconnect the modem from the console port and reconnect the terminal line.
The percentage of DRAM allocated to I/O memory and processor memory is configurable.
The following example allocates 40% of DRAM to I/O memory and the remaining 60% to processor memory:
Step 1 From EXEC mode, enter the show memory command to see whether you need to allocate different percentages of processor and I/O memory. The Free(b) column shows how much I/O memory is available:
show memory
Step 2 Enter global configuration mode and configure the memory-size iomem command.
configure terminal
memory-size iomem 40
exit
Step 3 Write the new configuration to NVRAM:
copy running-config startup-config
Step 4 Enter the reload command to run the new image and boot the router from ROM monitor mode:
reload
boot
This section describes ROM monitor and Cisco IOS commands that are new or modified, or have special syntax or usage for Cisco 3600 series routers. All other commands used with these routers are documented in the Cisco IOS Release 11.2 command references.
This section includes the following commands:
To boot the router manually, use the boot ROM monitor command:
boot [device:][partition-number:][filename]If you enter the boot command and press Enter, the router boots the first image in Flash memory. For other defaults, see the previous section "Syntax Description."
Enter this command when your router cannot find boot configuration information in NVRAM. To reach the ROM monitor prompt (>), use one of the following methods:
In this example, the router is booted manually from ROM:
> boot
In the following example, a router boots the file routertest from a network server with IP address 172.19.15.112:
> boot routertest 172.19.15.112
The following example shows the ROM monitor booting the first file in the first partition of internal Flash memory:
> boot flash:
This example boots the first image file in the first partition of the Flash memory card in slot 0:
> boot slot0:
continue
To specify the system image that the router loads at startup, use the boot system global configuration command. Use the no form of this command to remove the startup image specification.
boot system flash [device:][partition-number:] filename| flash | Boots the router from Flash memory. If you omit all optional arguments, the router searches internal Flash memory for the first bootable image. |
| device | (Optional) One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory |
| · slot0--Flash memory card in slot 0
· slot1--Flash memory card in slot 1 | |
| partition-number | (Optional) Boots the router from the specified Flash memory partition. If you do not specify a filename, the first valid file in the partition is loaded. |
| rcp | (Optional) Boots the router from a system image stored on a network server using rcp. If you omit this keyword, the transport mechanism defaults to tftp. |
| tftp | (Optional) Boots the router from a system image stored on a TFTP server. This is the default when you do not specify any keyword (flash, mop, rom, tftp, or rcp). |
| ip-address | (Optional) IP address of the TFTP or rcp server containing the system image file. If omitted, this value defaults to the IP broadcast address of 255.255.255.255. |
| filename | Name of the image file to load at startup (case sensitive for network files). |
If you configure the router to boot from a network server, but do not specify a system image file, the router uses the configuration register settings to determine a default filename. The default boot filename starts with the word cisco, followed by the octal equivalent of the boot field number in the configuration register, followed by a hyphen (-) and the router model (cisconn-3620 or cisconn-3640). See your router installation and configuration guide for further information on the configuration register and default filename. See also the confreg and config-register commands in the Cisco IOS command references.
If you omit all keywords (flash, mop, rcp, or tftp) from the boot system command, the router defaults to booting from an image stored on a TFTP server.
Global configuration
You can enter several boot system commands to provide alternative methods for booting your router. The router stores and executes boot system commands in the order in which you enter them in the configuration file, including multiple commands of the same type--for example, two commands that instruct the router to boot from different network servers. The configuration register value must be set properly for the boot system command to work as expected.
The boot system command modifies the BOOT environment variable in the running configuration. This variable specifies a list of bootable images on various devices. You must save the environment variable to your startup configuration, using the copy running-config startup-config command, to place the information under ROM monitor control the next time you reboot.
To view the contents of the BOOT environment variable, use the show boot command.
If an entry in the BOOT environment variable list does not specify a device, the router assumes the device is TFTP. When the device is TFTP, the router loads the boot helper image to boot the system image file from a network server.
If an entry in the BOOT environment variable list specifies an invalid device, the router skips that entry.
Each time you write a new software image to Flash memory, you must delete the existing filename in the configuration file and then add a new line. To remove a single entry from the bootable image list, use the no form of the command to add it. To eliminate all entries in the bootable image list, use the no boot system command. Entering this command sets the BOOT environment variable to a null string. You can then redefine the list of bootable images using boot system commands. Remember to save your changes to the startup configuration with the copy running-config startup-config command.
To rearrange the order of the entries in the BOOT environment variable, enter the no boot system command and then reenter the list.
For the rcp protocol to execute properly, an account must be defined on the network server for the remote username configured on the router. The path for all files and images to be copied begins at the remote user's home directory.
By default, the router software sends the remote username associated with the current TTY process, if that name is valid. 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. If the remote username is invalid, the software uses the router host name as both the remote and local usernames.
You can override the default remote username by using the ip rcmd remote-username command. 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.
This example specifies the file new-ios-image as the system image for a Cisco 3600 series router to load at startup. This file is located in the fourth partition of the Flash memory card in slot 0:
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#boot system flash slot0:4:dirt/images/new-ios-image
This example boots from the image file igs-bpx-l in partition 2 of internal Flash memory:
boot system flash flash:2:igs-bpx-l
This example lists two possible internetwork locations for a system image:
boot system cs3-rx.90-1 192.31.7.24 boot system cs3-rx.83-2 192.31.7.19
config-register
copy
ip rcmd remote-username
show boot
To copy any file from a Flash device or NVRAM to another destination, use the following copy EXEC command.
copy device:[partition-number:][filename] {device:[partition-number:][filename] | tftp | rcp | running-config | startup-config}| device | One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory |
| · slot0--Flash memory card in PCMCIA slot 0
· slot1--Flash memory card in PCMCIA slot 1 | |
| partition-number | (Optional) Partition number of the source or destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the source or destination file. |
| tftp | Copy to a TFTP server. |
| rcp | Copy to a rcp server. |
| running-config | Copy to the currently running configuration. |
| startup-config | Copy to the startup configuration in NVRAM. |
If you omit the destination filename, the software uses the source filename.
EXEC
You can identify the available device partitions by entering the show flash:, show slot0:, or show slot1: command.
The copy command copies a file from a source to a destination. If you do not specify a filename, the router prompts you for it. Some combinations are invalid: you cannot copy a running configuration to a running configuration, a startup configuration to a startup configuration, or TFTP to rcp.
When the destination is specified by the CONFIG_FILE or BOOTLDR environment variable, the router prompts you for confirmation before proceeding with the copy. When the destination is the only valid image in the BOOT environment variable, the router also prompts you for confirmation before proceeding with the copy.
Cisco 3600 routers do not use a dedicated boot helper image (rxboot), which many other routers use to help with the boot process. Instead, the BOOTLDR ROM monitor environment variable identifies the Flash memory device and filename that are used as the boot helper; the default is the first system image in Flash memory. When the BOOTLDR environment variable points to the copy destination, the router prompts you for confirmation before proceeding with the copy.
The BOOT environment variable specifies a list of bootable images on various devices. When the destination is the only valid image in the BOOT environment variable, the router also prompts you for confirmation before proceeding with the copy.
To view the contents of environment variables, use the show boot command. To modify the BOOTLDR environment variable, use the boot bootldr command. To modify the BOOT environment variable, use the boot system command. To save your modifications, use the copy running-config startup-config command.
The following example copies the file c3600-i-mz from partition 1 of the Flash memory card in slot 0 to the filename c3700-i-mz on a TFTP server that has IP address 172.23.1.129. Because the Flash memory card has multiple partitions, and a partition number and filename are not specified in the command line, you must provide this information during the copy operation:
Router#copy slot0: tftpPCMCIA 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 ?<no> for partition directory; ? for full directory; q to abort] Which partition? [default = 1]1PCMCIA Slot0 flash directory, partition 1: File Length Name/status 1 1711088 /tftpboot/cisco_rules/c3600-i-mz [1711152 bytes used, 2483152 available, 4194304 total] Address or name of remote host [172.23.1.129]? Source file name?/tftpboot/cisco_rules/c3600-i-mzDestination file name [/tftpboot/cisco_rules/c3600-i-mz]?dirt/cisco_rules/c3700-i-mzVerifying checksum for '/tftpboot/cisco_rules/c3600-i-mz' (file # 1)... OK Copy '/tftpboot/cisco_rules/c3600-i-mz' from Flash to server as 'dirt/cisco_rules/c3700-i-mz'? [yes/no]yes!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Upload to server done Flash device copy took 00:00:23 [hh:mm:ss]
The next example copies the file ios-upgrade-1 from the Flash memory card in slot 0 to the running configuration.
Router#copy slot0:4:ios-upgrade-1 running-configCopy'ios-upgrade-1' from flash device as 'running-config' ? [yes/no]yes
This example copies the file running-config from the first partition in internal Flash memory to the Flash memory PC card in slot 1. The file's checksum is verified, and its copying time of 30 seconds is displayed:
Router#copy flash: slot1:System flash Partition Size Used Free Bank-Size State Copy Mode 1 4096K 3070K 1025K 4096K Read/Write Direct 2 16384K 1671K 14712K 8192K Read/Write Direct [Type ?<no> for partition directory; ? for full directory; q to abort] Which partition? [default = 1] System flash directory, partition 1: File Length Name/status 1 3142748 dirt/images/mars-test/c3600-j-mz.latest 2 850 running-config [3143728 bytes used, 1050576 available, 4194304 total] PCMCIA Slot1 flash directory: File Length Name/status 1 1711088 dirt/images/c3600-i-mz 2 850 running-config [1712068 bytes used, 2482236 available, 4194304 total] Source file name?running-configDestination file name [running-config]? Verifying checksum for 'running-config' (file # 2)... OK Erase flash device before writing? [confirm] Flash contains files. Are you sure you want to erase? [confirm] Copy 'running-config' from flash: device as 'running-config' into slot1: device WITH erase? [yes/no]yesErasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased ! [OK - 850/4194304 bytes] Flash device copy took 00:00:30 [hh:mm:ss] Verifying checksum... OK (0x16)
To copy a file from a MOP server to the router, use one of the following the copy mop EXEC commands:
copy mop device:[partition-number:][filename]| device | One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory |
| · slot0--Flash memory card in PCMCIA slot 0
· slot1--Flash memory card in PCMCIA slot 1 | |
| partition-number | (Optional) Partition number of the source or destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the source or destination file. |
EXEC
You do not need to specify the address of a MOP server. The Cisco IOS software automatically solicits a MOP boot server for the specified file by sending a multicast file-request message.
The copying process takes several minutes; the actual time differs from network to network.
In this example, a new version of the system image file1, which already exists in Flash memory, is copied from a MOP server. There is enough memory to copy the file without erasing existing files:
Router#copy mop flash:System flash directory: File Length Name/status 1 984 file1 [deleted] 2 984 file1 [2096 bytes used, 8386512 available, 8388608 total] Source file name?file1Destination file name [file1]? Erase flash device before writing? [confirm] Flash contains files. Are you sure you want to erase? [confirm] Copy 'file1' from server as 'file1' into Flash WITH erase? [yes/no]yesErasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased Loading file1 from 1234.5678.9abc via Ethernet0: ! [OK - 984/8388608 bytes] Verifying checksum... OK (0x14B3) Flash copy took 0:00:01 [hh:mm:ss]
copy xmodem flash
copy ymodem flash
verify
To copy a file from a network server to the router or to another destination using rcp, use the copy rcp command:
copy rcp {device:[partition-number:][filename] | running-config | startup-config}| device | One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory |
| · slot0--Flash memory card in PCMCIA slot 0
· slot1--Flash memory card in PCMCIA slot 1 | |
| partition-number | (Optional) Partition number of the source or destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the source or destination file. |
| running-config | Specifies the currently running configuration as the destination of the copy operation. |
| startup-config | Specifies the configuration used for initialization as the destination of the copy operation. |
If you omit the destination filename, the router uses the source filename.
EXEC
The rcp protocol requires that a client send the remote username of an rcp request to the server. When you issue one of the copy rcp commands, by default the Cisco IOS software sends the username associated with the current TTY, if that name is valid. For example, if the user is connected to the router through Telnet and the user was authenticated through the username command, then the software sends that username as the remote username.
If the TTY username is invalid, the software uses the host name as both the remote and local usernames. To specify a different remote username to be sent to the rcp server, use the ip rcmd remote-username command. You can also specify the path of an existing directory along with the remote username.
| Caution The remote username must be associated with an account on the destination server. If you do not use the ip rcmd remote-username command to specify the name of a remote user associated with an account on the server, then the remote username associated with the current TTY process must be associated with an account on the server. If there is no username for the current TTY process, then the host name must be associated with an account on the server. If the network administrator of the destination server did not establish accounts for the remote username used, this command will not execute successfully when a default remote username is used. |
The following example copies the file c3600-i-mz from the rcp server at IP address 172.23.1.129 to the Flash memory card in slot 0, which has only one partition. As the operation progresses, the Cisco IOS software asks you to erase the files on the Flash memory PC card to accommodate the incoming file.
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 ?<no> 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.test [3142352 bytes used, 1051952 available, 4194304 total] Address or name of remote host [172.23.1.129]? Source file name? /tftpboot/images/c3600-i-mz Destination file name [/tftpboot/images/c3600-i-mz]? Accessing file '/tftpboot/images/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/images/c3600-i-mz' from server as '/tftpboot/images/c3600-i-mz' into Flash WITH erase? [yes/no]yesErasing 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]
To copy the running configuration file to another destination, use the copy running-config command:
copy running-config device:[partition-number:][filename]| device | One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory |
| · slot0--Flash memory card in PCMCIA slot 0
· slot1--Flash memory card in PCMCIA slot 1 | |
| partition-number | (Optional) Partition number of the source or destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the source or destination file. |
If you omit the destination filename, the router uses the source filename.
EXEC
With the Cisco 3600 series routers, you can copy the running configuration to the internal Flash memory or to a Flash memory PC card inserted in PCMCIA slot 1 or slot 0. During the copy operation, you have the opportunity to assign a new destination filename and erase the contents of the destination device.
You cannot copy a running configuration to a Flash partition from which you are currently running. For example, copy the new image to partition 2 if partition 1 is running the current system image. Otherwise, the copy operation will fail.
The following example copies the running configuration from the router to the Flash memory PC card in slot 1:
Router#copy running-config slot1:PCMCIA Slot1 flash directory: File Length Name/status 1 1711088 dirt/images/c3600-i-mz [1711152 bytes used, 2483152 available, 4194304 total] Destination file name [running-config]? Building configuration... Erase flash device before writing? [confirm]noCopy 'running-config' as 'running-config' into flash device WITHOUT erase? [yes/no] % Please answer 'yes' or 'no'.yes! [OK - 850/2483152 bytes] Verifying checksum... OK (0x16) Flash device copy took 00:00:00 [hh:mm:ss]
copy xmodem flash
copy ymodem flash
verify
To copy startup configuration file to another destination, use the copy startup-config EXEC command:
copy startup-config device:[partition-number:][filename]| device | One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory |
| · slot0--Flash memory card in PCMCIA slot 0
· slot1--Flash memory card in PCMCIA slot 1 | |
| partition-number | (Optional) Partition number of the source or destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the source or destination file. |
If you omit the destination filename, the router uses the source filename.
EXEC
With the Cisco 3600 series routers, you can copy the startup configuration to the internal Flash memory or to a Flash memory PC card inserted in PCMCIA slot 1 or slot 0. During the copy operation, you have the opportunity to assign a new destination filename and erase the contents of the destination device.
You cannot copy a startup configuration to a Flash partition from which you are currently running. For example, copy the new image to partition 2 if partition 1 is running the current system image. Otherwise, the copy operation will fail.
The following example copies the startup configuration to the second partition on the Flash memory card in slot 0:
Router#copy startup-config slot0:2PCMCIA Slot0 flash directory, partition 2: File Length Name/status 1 3141700 /tftpboot/images/c3600-j-mz [3141764 bytes used, 1052540 available, 4194304 total] Destination file name [startup-config]? Erase flash device before writing? [confirm]nCopy 'startup-config' as 'startup-config' into flash device WITHOUT erase? [yes/no]yes! [OK - 850/1052540 bytes] Verifying checksum... OK (0x16) Flash device copy took 00:00:00 [hh:mm:ss]
copy xmodem flash
copy ymodem flash
verify
To copy a file from a TFTP server to the router or to another destination, use the copy tftp command:
copy tftp {device:[partition-number:][filename] | running-config | startup-config}| device | One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory |
| · slot0--Flash memory card in PCMCIA slot 0
· slot1--Flash memory card in PCMCIA slot 1 | |
| partition-number | (Optional) Partition number of the source or destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the source or destination file. |
| running-config | Specifies the currently running configuration as the destination of the copy operation. |
| startup-config | Specifies the configuration used for initialization as the destination of the copy operation. |
If you omit the destination filename, the router uses the source filename.
EXEC
The system prompts for the address of the TFTP server and TFTP filename if you do not provide them at the command line. When copying to internal Flash memory, the system provides an option to erase existing internal Flash memory before writing onto it. The entire copying process takes several minutes and differs from network to network.
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. The checksum of the image in Flash memory is displayed at the bottom of the screen when you issue the copy tftp command. The README file was copied to the TFTP server automatically when you installed the system software image.
The following example shows you how to copy the file c3600-i-mz from the TFTP server at IP address 171.69.1.129 to the internal Flash memory, which has one partition, in a Cisco 3600 series router. This entire operation takes 17 seconds to perform as indicated at the end of the example.
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 ?<no> for partition directory; ? for full directory; q to abort] Which partition? [default = 1] System flash directory, partition 1: File Length Name/status 1 1711088 dirt/images/c3600-i-mz [1711152 bytes used, 2483152 available, 4194304 total] Address or name of remote host [171.69.1.129]? Source file name?dirt/images/c3600-i-mzDestination file name [dirt/images/c3600-i-mz]? Accessing file 'dirt/images/c3600-i-mz' on 171.69.1.129... Loading dirt/images/c3600-i-mz from 171.69.1.129 (via Ethernet1/0): ! [OK] Erase flash device before writing? [confirm] Flash contains files. Are you sure you want to erase? [confirm] Copy 'dirt/images/c3600-i-mz' from server as 'dirt/images/c3600-i-mz' into Flash WITH erase? [yes/no]yesErasing device... eeeeeeeeeeeeeeee ...erased Loading dirt/images/c3600-i-mz from 171.69.1.129 (via Ethernet1/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK - 1711088/4194304 bytes] Verifying checksum... OK (0xF89A) Flash device copy took 00:00:17 [hh:mm:ss]
To copy a Cisco IOS image from a local or remote computer (such as a PC, Macintosh, or UNIX workstation) to Flash memory using the Xmodem protocol, use the copy xmodem EXEC command:
copy xmodem device:[partition-number:][filename]| device | (Optional) One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory |
| · slot0--Flash memory card in PCMCIA slot 0
· slot1--Flash memory card in PCMCIA slot 1 | |
| partition-number | (Optional) Partition number of the destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the destination file. |
EXEC
This command first appeared in Cisco IOS Release 11.2 P.
The copy tftp flash: and copy rcp flash: commands are much faster than the copy xmodem flash: command. Use the copy xmodem flash: command only if you do not have access to a TFTP or rcp server.
This copy operation is performed through the console or AUX port. The AUX port, which supports hardware flow control, is recommended.
No output is displayed on the port over which the transfer is occurring. You can use the logging buffered command to log all router messages sent to the console port during the file transfer.
The following command initiates a file transfer from a local or remote computer to the router's internal Flash memory using the Xmodem protocol:
Router> enable
Password:letmein
Router# copy xmodem flash:
To copy a Cisco IOS image from a local or remote computer (such as a PC, Macintosh, or UNIX workstation) to Flash memory using the Ymodem protocol, use the copy ymodem EXEC command:
copy ymodem device:[partition-number:][filename]| device | (Optional) One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory |
| · slot0--Flash memory card in PCMCIA slot 0
· slot1--Flash memory card in PCMCIA slot 1 | |
| partition-number | (Optional) Partition number of the destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the destination file. |
EXEC
This command first appeared in Cisco IOS Release 11.2 P.
The copy tftp flash: and copy rcp flash: commands are much faster than the copy ymodem flash: command. Use the copy ymodem flash: command only if you do not have access to a TFTP or rcp server.
This copy operation is performed through the console or AUX port. The AUX port, which supports hardware flow control, is recommended.
No output is displayed on the port over which the transfer is occurring. You can use the logging buffered command to log all router messages sent to the console port during the file transfer.
The following command initiates a file transfer from a local or remote computer to the router's internal Flash memory using the Ymodem protocol:
Router> enable
Password:letmein
Router# copy ymodem flash:
To erase a stored configuration, use the erase EXEC command:
erase device:[partition-number]| device | One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory |
| · slot0--Flash memory card in PCMCIA slot 0
· slot1--Flash memory card in PCMCIA slot 1 | |
| partition-number | (Optional) Partition number to erase. |
EXEC
You cannot erase a single filename. You can erase only an entire Flash memory device or a specified partition.
The following example erases all of partition 2 in internal Flash memory:
Router#erase flash:2System flash directory, partition 2: File Length Name/status 1 1711088 dirt/images/c3600-i-mz [1711152 bytes used, 15066064 available, 16777216 total] Erase flash device, partition 2? [confirm] Are you sure? [yes/no]:yesErasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
boot config
delete
show boot
show startup-config
undelete
To reallocate the percentage of DRAM memory to use for I/O memory and processor memory on Cisco 3600 series routers, use the memory-size iomem global configuration command. The no form of this command reverts to the default allocation of 25 percent I/O memory and 75 percent processor memory.
memory-size iomem I/O-memory-percentage| I/O-memory-percentage | The percentage of DRAM allocated to I/O memory. The values permitted are 25, 30, 40, and 50 percent. |
The default allocation is 25 percent I/O memory and 75 percent processor memory.
Global configuration
This command first appeared in Cisco IOS Release 11.2 P.
When you specify the percentage of I/O memory in the command line, processor memory automatically aquires the remaining percentage of DRAM memory.
The following configuration allocates 40 percent of the DRAM memory to I/O memory and the remaining 60 percent to processor memory.
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#memory-size iomem 40Router(config)#exitRouter#copy running-config startup-configBuilding configuration... [OK] Router#reloadrommon 1 >bootprogram load complete, entry point: 0x80008000, size: 0x32ea24 Self decompressing the image : ###################################################################################################################################################################################################################################################### [OK]
To separate Flash memory into partitions, use the partition global configuration command. Use the no form of this command to undo partitioning and to restore Flash memory to one partition.
partition device: [number-of-partitions][partition-size]| device | One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory |
| · slot0--Flash memory card in PCMCIA slot 0
· slot1--Flash memory card in PCMCIA slot 1 | |
| number-of-partitions | (Optional) Number of partitions in Flash memory. |
| partition-size | (Optional) Size of each partition. The number of partition size entries must be equal to the number of specified partitions. |
Flash memory consists of one partition.
If the partition size is not specified, partitions of equal size are created.
Global configuration
To undo partitioning, use the partition device:1 or no partition device: command. If there are files in a partition other than the first, you must use the command erase device:partition-number to erase the partition before reverting to a single partition.
When creating two partitions, you must not truncate a file or cause a file to spill over into the second partition.
The following example divides the Flash memory card in slot 0 into two partitions, each 8 MB in size:
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#partition slot0: 2 8 8
The following example creates four partitions of equal size in the card in slot 0.
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#partitionslot0: 4
To display the contents of Flash memory, use the show device: command:
show device: [all | chips | detailed | err | partition number | summary]| device | (Optional) One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory |
| · slot0--Flash memory card in PCMCIA slot 0
· slot1--Flash memory card in PCMCIA slot 1 | |
| all | (Optional) Shows names and sizes of all system image files stored in Flash memory, including those that are invalid. |
| chips | (Optional) Shows the bank each chip is in, and its code, size, and name. |
| detailed | (Optional) Shows detailed file directory information, including file length, address, name, Flash memory checksum, computer checksum, bytes used, bytes available, total bytes, and bytes of system Flash memory. |
| err | (Optional) Shows write or erase failures in the form of number of retries. |
| partition number | (Optional) Displays file memory information for the specified partition. You can use this keyword only when Flash memory has multiple partitions. |
| summary | (Optional) Shows summary information, including partition size, bank size, state, and method by which files can be copied into each partition. You can use this keyword only when Flash memory has multiple partitions. |
EXEC
The show device: command displays the type of Flash memory, the files in Flash memory, and the amount of Flash memory used and remaining.
The following is sample output for the show flash: all command on a Cisco 3600 series router with partitioned Flash memory.
Router#show flash allSystem flash partition information: PartitionSize Used Free Bank-Size State Copy-Mode 14096K 3459K 637K 4096K Read Only RXBOOT-FLH 24096K 3224K 872K 4096K Read/Write Direct System flash directory, partition 1: File Length Name/status addr fcksum ccksum 1 3459720 master/igs-bfpx.100-4.3 0x40 0x3DE1 0x3DE1 [3459784 bytes used, 734520 available, 4194304 total] 4096K bytes of processor board System flash (Read ONLY) Chip Bank Code Size Name 1 1 89A2 1024KB INTEL 28F008SA 2 1 89A2 1024KB INTEL 28F008SA 3 1 89A2 1024KB INTEL 28F008SA 4 1 89A2 1024KB INTEL 28F008SA Executing current image from System flash [partition 1] System flash directory, partition2: File Length Name/status addr fcksum ccksum 1 3224008 igs-kf.100 0x40 0xEE91 0xEE91 [3224072 bytes used, 970232 available, 4194304 total] 4096K bytes of processor board System flash (Read/Write) Chip Bank Code Size Name 1 2 89A2 1024KB INTEL 28F008SA 2 2 89A2 1024KB INTEL 28F008SA 3 2 89A2 1024KB INTEL 28F008SA 4 2 89A2 1024KB INTEL 28F008SA
Table 5 describes the additional fields in the display.
| Field | Description |
|---|---|
| Partition | Partition number in Flash memory. |
| Size | Size of partition in bytes. |
| Used | Number of bytes used in partition. |
| Free | Number of bytes free in partition. |
| Bank-Size | Size of bank in bytes. |
| State | State of the partition. It can be one of the following values:
|
|
Copy-Mode | Method by which the partition can be copied to:
|
|
System flash directory, partition 1 | Flash directory and its contents. |
| File | Number of the system image file. If no filename is specified in the boot system flash command, the router boots the system image file with the lowest file number. |
| length | Size of the system image file (in bytes). |
| name/status | Filename and status of a system image file. The status [invalidated] appears when a file has been rewritten (recopied) into Flash memory. The first (now invalidated) copy of the file is still present within Flash memory, but it is rendered unusable in favor of the newest version. The [invalidated] status can also indicate an incomplete file that results from the user abnormally terminating the copy process, a network timeout, or a Flash memory overflow. |
| addr | Address of the file in Flash memory. |
| fcksum | Checksum recorded in Flash memory. |
| ccksum | Computer checksum. |
| Chip | Chip number. |
| Bank | Bank number. |
| Code | Code number. |
| Size | Size of chip. |
| Name | Name of chip manufacturer and the chip type. |
The following example illustrates the show flash: chips command on a router that has Flash memory partitioned:
Router# show flash: chips
System flash partition 1:
4096K bytes of processor board System flash (Read ONLY)
Chip Bank Code Size Name
1 1 89A2 1024KB INTEL 28F008SA
2 1 89A2 1024KB INTEL 28F008SA
3 1 89A2 1024KB INTEL 28F008SA
4 1 89A2 1024KB INTEL 28F008SA
Executing current image from System flash [partition 1]
System flash partition 2:
4096K bytes of processor board System flash (Read/Write)
Chip Bank Code Size Name
1 2 89A2 1024KB INTEL 28F008SA
2 2 89A2 1024KB INTEL 28F008SA
3 2 89A2 1024KB INTEL 28F008SA
4 2 89A2 1024KB INTEL 28F008SA
The following example illustrates the show flash: detailed command on a router that has Flash memory partitioned:
Router# show flash: detailed
System flash directory, partition 1:
File Length Name/status
addr fcksum ccksum
1 3224008 igs-kf.100
0x40 0xEE91 0xEE91
[3224072 bytes used, 970232 available, 4194304 total]
4096K bytes of processor board System flash (Read/Write)
System flash directory, partition 2:
File Length Name/status
addr fcksum ccksum
1 3224008 igs-kf.100
0x40 0xEE91 0xEE91
[3224072 bytes used, 970232 available, 4194304 total]
4096K bytes of processor board System flash (Read/Write)
This example shows detailed information about the Flash memory PC card in slot 0, which has four partitions:
Router# show slot0: detailed
PCMCIA Slot0 flash directory, partition 1:
File Length Name/status
addr fcksum ccksum
1 3142748 dirt/images/mars-test/c3600-j-mz.latest
0x40 0xB732 0xB732
[3142812 bytes used, 1051492 available, 4194304 total]
4096K bytes of processor board PCMCIA Slot0 flash (Read/Write)
PCMCIA Slot0 flash directory, partition 2:
File Length Name/status
addr fcksum ccksum
1 3141700 /tftpboot/images/c3600-j-mz
0x40 0x84E 0x84E
2 850 startup-config
0x2FF0C4 0x16 0x16
[3142680 bytes used, 1051624 available, 4194304 total]
4096K bytes of processor board PCMCIA Slot0 flash (Read/Write)
PCMCIA Slot0 flash directory, partition 3:
File Length Name/status
addr fcksum ccksum
1 1711088 /tftpboot/images/c3600-i-mz
0x40 0xF89A 0xF89A
[1711152 bytes used, 2483152 available, 4194304 total]
4096K bytes of processor board PCMCIA Slot0 flash (Read/Write)
PCMCIA Slot0 flash directory, partition 4:
File Length Name/status
addr fcksum ccksum
1 2205860 dirt/images/c3600-d-mz
0x40 0x9501 0x9501
2 1711128 dirt/images/c3600-i-mz.test
0x21A924 0xDFE9 0xDFE9
3 850 alz
0x3BC57C 0x16 0x16
[3918032 bytes used, 276272 available, 4194304 total]
4096K bytes of processor board PCMCIA Slot0 flash (Read/Write)
The following example illustrates the show flash: err command on a router that has Flash memory partitioned:
Router# show flash: err
System flash directory, partition 1:
File Length Name/status
1 37376 master/igs-bfpx.100-4.3 [invalid checksum]
[37440 bytes used, 4156864 available, 4194304 total]
4096K bytes of processor board System flash (Read/Write)
Chip Bank Code Size Name erase write
1 1 89A2 1024KB INTEL 28F008SA 0 0
2 1 89A2 1024KB INTEL 28F008SA 0 0
3 1 89A2 1024KB INTEL 28F008SA 0 0
4 1 89A2 1024KB INTEL 28F008SA 0 0
Executing current image from System flash [partition 1]
System flash directory, partition 2:
File Length Name/status
1 37376 master/igs-bfpx.100-4.3 [invalid checksum]
[37440 bytes used, 4156864 available, 4194304 total]
4096K bytes of processor board System flash (Read/Write)
Chip Bank Code Size Name erase write
1 2 89A2 1024KB INTEL 28F008SA 0 0
2 2 89A2 1024KB INTEL 28F008SA 0 0
3 2 89A2 1024KB INTEL 28F008SA 0 0
4 2 89A2 1024KB INTEL 28F008SA 0 0
The following example shows detailed information about the second partition in internal Flash memory:
Router# show flash: partition 2
System flash directory, partition 2:
File Length Name/status
1 1711088 dirt/images/c3600-i-mz
[1711152 bytes used, 15066064 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
The following example illustrates the show flash: summary command on a router that has internal Flash memory partitioned. The partition in the Read Only state is the partition from which the Cisco IOS image is being executed:
Router# show flash: summary
System flash partition information:
Partition Size Used Free Bank-Size State Copy-Mode
1 4096K 2048K 2048K 2048K Read Only RXBOOT-FLH
2 4096K 2048K 2048K 2048K Read/Write Direct
The following example shows copy and file space information about each partition in the card in slot 1:
Router# show slot1: summary
Partition Size Used Free Bank-Size State Copy Mode
1 4096K 0K 4095K 2048K Read/Write Direct
To configure a router or a Flash memory device on the router as a TFTP server, enter the tftp-server global configuration command. This command replaces the tftp-server system command. To remove a previously defined filename, use the no tftp-server flash version of this command.
tftp-server flash [device:][partition-number:]filename| flash | Assigns TFTP service to a file in Flash memory. |
| device | (Optional) One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory |
| · slot0--Flash memory card in PCMCIA slot 0
· slot1--Flash memory card in PCMCIA slot 1 | |
| partition-number | (Optional) Partition number of the Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. If a partition is not specified, the first partition is used. |
| filename | File the TFTP server uses in answering TFTP Read Requests. |
Disabled
Global configuration
You can specify multiple filenames by repeating the tftp-server command. The router sends a copy of the image in Flash memory to any client that sends a TFTP Read Request with this filename.
The following example enables a Cisco 3600 series router to operate as a TFTP server. The source file c3640-i-mz is in the second partition of internal Flash memory:
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. router(config)#tftp-server flash flash:2:dirt/gate/c3640-i-mz
In the next example, the source file is in the second partition of the Flash memory PC card in slot 0:
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. router(config)#tftp-server flash slot0:2:dirt/gate/c3640-j-mz
access-list
To verify the checksum of a file on a Flash memory device, use the verify EXEC command. This command replaces the copy verify and copy verify flash commands.
verify device:[partition-number:][filename]| device | (Optional) One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory · slot0--Flash memory card in PCMCIA slot 0 · slot1--Flash memory card in PCMCIA slot 1 |
| partition-number | (Optional) Partition number to verify. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of a file on the specified Flash memory device. |
The default device is the current working device.
EXEC
Use the verify command to verify the checksum of a file before using it. When you omit the device: argument, the router verifies the checksum of the specified file on the current working device.
The following example verifies the file gsxx on the Flash memory card in slot 0:
verify slot0:gsxx
The following example verifies the checksum of the file alz, located in the fourth partition of the Flash memory card in slot 0:
Router#verify slot0:4PCMCIA Slot0 flash directory, partition 4: File Length Name/status 1 2205860 dirt/images/c3600-d-mz 2 1711128 dirt/images/c3600-i-mz.test 3 850 alz [3918032 bytes used, 276272 available, 4194304 total] Name of file to verify?alzVerifying checksum for 'alz' (file # 3)... OK
copy rcp
ip rcmd remote-username
pwd
show flash
To copy a Cisco IOS image to a Cisco 3600 series router using the ROM monitor and the Xmodem or Ymodem protocol, use the xmodem ROM monitor command:
xmodem [-c] [-y] [-r] [-x] [filename]| -c | (Optional) CRC-16 checksumming, which is more sophisticated and thorough than standard checksumming. |
| -y | (Optional) Uses Ymodem protocol for higher throughput. |
| -r | (Optional) Downloads the file to DRAM. The default is Flash memory. |
| -x | (Optional) Do not execute Cisco IOS image on completion of the download. |
| filename | (Optional) Filename to copy. This argument is ignored when -r is specified, because only one file can be copied to DRAM. |
ROM monitor
Xmodem protocol with 8-bit CRC, file downloaded into Flash memory and executed on completion.
This command first appeared in Cisco IOS Release 11.2 P.
The Cisco 3600 series does not support XBOOT functionality. If your Cisco IOS image is erased or damaged, you cannot load a new image over the network.
Use the xmodem ROM monitor command to download a new system image to your router from a local personal computer (such as a PC, Mac, or UNIX workstation), or a remote computer over a modem connection, to the router's console port. The computer must have a terminal emulation application that supports these protocols.
Your 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. There is no support for partitions or copying as a second file.
| 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. |
The following example uses the xmodem -c filename ROM monitor command to copy the file new-ios-image from a remote or local computer:
rommon >xmodem -c new-ios-imageDo not start the sending program yet... File size Checksum File name 1738244 bytes (0x1a8604) 0xdd25 george-admin/c3600-i-mz WARNING: All existing data in bootflash will be lost! Invoke this application only for disaster recovery. Do you wish to continue? y/n [n]:yesReady to receive file new-ios-image...
For additional software configuration information for the Cisco 3600 series routers, refer to the following documents:
|
|