|
|
This chapter provides detailed descriptions of the commands used to load and copy system images, microcode images, and configuration files. Microcode images contain microcode to be downloaded to various hardware devices. System images contain the system software. Configuration files contain commands entered to customize the function of the router.
For router configuration information and examples, refer to the "Loading System Images, Microcode Images, and Configuration Files" chapter in the Router Products Configuration Guide.
Use the async-bootp global configuration command to enable support for extended BOOTP requests as defined in RFC 1084 when the router is configured for SLIP. Use the no async-bootp global configuration command to restore the default.
async-bootp tag [:hostname] data
tag | Item being requested; expressed as filename, integer, or IP dotted-decimal address. See Table 3-1 for possible values. |
:hostname | (Optional) This entry applies only to the host specified. The argument :hostname accepts both an IP address and a logical host name. |
data | List of IP addresses entered in dotted-decimal notation or as logical host names, a number, or a quoted string. |
| Keyword | Description |
|---|---|
bootfile | Specifies use of a server boot file from which to download the boot program. Use the optional :hostname and data arguments to specify the filename. |
subnet-mask mask | Dotted-decimal address specifying the network and local subnetwork mask (as defined by RFC 950). |
time-offset offset | Signed 32-bit integer specifying the time offset of the local subnetwork in seconds from Universal Coordinated Time (UTC). |
gateway address | Dotted-decimal address specifying the IP addresses of gateways for this subnetwork. A preferred gateway should be listed first. |
time-server address | Dotted-decimal address specifying the IP address of time servers (as defined by RFC 868). |
IEN116-server address | Dotted-decimal address specifying the IP address of name servers (as defined by IEN 116). |
DNS-server address | Dotted-decimal address specifying the IP address of Domain Name Servers (as defined by RFC 1034). |
log-server address | Dotted-decimal address specifying the IP address of an MIT-LCS UDP log server. |
quote-server address | Dotted-decimal address specifying the IP address of Quote of the Day servers (as defined in RFC 865). |
lpr-server address | Dotted-decimal address specifying the IP address of Berkeley UNIX Version 4 BSD servers. |
impress-server address | Dotted-decimal address specifying the IP address of Impress network image servers. |
rlp-server address | Dotted-decimal address specifying the IP address of Resource Location Protocol (RLP) servers (as defined in RFC 887). |
hostname name | The name of the client, which may or may not be domain qualified, depending upon the site. |
bootfile-size value | A two-octet value specifying the number of 512-octet (byte) blocks in the default boot file. |
If no extended BOOTP commands are entered, the router software generates a gateway and subnet mask appropriate for the local network.
Global configuration
Use the EXEC command show async-bootp to list the configured parameters. Use the no
async-bootp command to clear the list.
The following example illustrates how to specify different boot files: one for a PC, and one for a Macintosh. With this configuration, a BOOTP request from the host on 128.128.1.1 results in a reply listing the boot filename as pcboot. A BOOTP request from the host named mac results in a reply listing the boot filename as macboot.
async-bootp bootfile :128.128.1.1 "pcboot" async-bootp bootfile :mac "macboot"
The following example specifies a subnet mask of 255.255.0.0:
async-bootp subnet-mask 255.255.0.0
The following example specifies a negative time offset of the local subnetwork of -3600 seconds:
async-bootp time-offset -3600
The following example specifies the IP address of a time server:
async-bootp time-server 128.128.1.1
To boot the router manually, use the boot ROM monitor command.
boot
filename | When used in conjunction with the ip-address argument, the filename argument is the name of the system image file to boot from a network server. The filename is case sensitive. (Optional) When used in conjunction with the flash keyword, the filename argument is the name of the system image file to boot from Flash memory. On all platforms except the Cisco 7500 series, the system obtains the image file from internal Flash memory. On the Cisco 7500 series, the device: argument specifies the Flash memory device from which to obtain the system image. See the device: argument later in this table for valid device values. The filename is case sensitive. Without filename, the first valid file in Flash memory is loaded. |
ip-address | (Optional) IP address of the TFTP server on which the system image resides. If omitted, this value defaults to the IP broadcast address of 255.255.255.255. |
flash | (Optional) Boots the router from Flash memory. |
device: | (Optional on all platforms except the Cisco 7500 series) On all platforms except the Cisco 7500 series, the only valid value is flash. The colon (:) is required. On the Cisco 7500 series, valid devices are as follows: ♦ bootflash: This device is the internal Flash memory in the Cisco 7500 series. ♦ slot0: This device is the first Personal Computer Memory Card International Association (PCMCIA) slot on the Cisco 7500 series Route Switch Processor (RSP) card. ♦ slot1: This device is the second PCMCIA slot on the Cisco 7500 series RSP card. |
partition-number: | Boots the router from Flash memory with the optional filename of the image you want loaded from the specified Flash partition. If you do not specify a filename, the first valid file in the specified partition of Flash memory is loaded. |
If you enter the boot command and press Return, the router boots from ROM by default.
If you enter the boot flash command without a filename, the first valid file in Flash memory is loaded.
For other defaults, see the Syntax Description section.
Use this command only when your router cannot find the configuration information needed in nonvolatile random-access memory (NVRAM). To get to the ROM monitor prompt (>), enter the reload EXEC command, and then press the Break key during the first 60 seconds of startup, or change the boot bits in the configuration register to zero (for manual booting) and then issue the reload command.
Refer to the Cisco 7000 Hardware Installation and Maintenance publication for the correct jumper settings for the Cisco 7000 series.
In the following example, the router is manually booted from ROM:
> boot F3: (ROM Monitor copyrights)
In the following example, a router boots the file routertest from a network server with the IP address 131.108.15.112:
> boot routertest 131.108.15.112 F3: (ROM Monitor copyrights)
The following example shows the boot flash command without the filename argument.The first valid file in Flash memory is loaded.
> boot flash F3: 1858656+45204+166896 at 0x1000 Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR [OK - 1903912/13765276 bytes] F3: 1858676+45204+166896 at 0x1000 (ROM Monitor copyrights)
In the following example, the boot flash command is used with the filename gs7-k. That is the file that will be loaded.
> boot flash gs7-k F3: 1858656+45204+166896 at 0x1000 Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR RRRRRRRRRRRRRR [OK - 1903912/13765276 bytes] F3: 1858676+45204+166896 at 0x1000 (ROM Monitor copyrights)
In the following example, the boot flash flash command boots the relocatable image file igs-bpx-l from partition 2 in Flash memory:
> boot flash flash:2:igs-bpx-l
F3: 3562264+98228+303632 at 0x30000B4
(ROM Monitor copyrights)
To specify a Flash device and filename containing the rxboot image that ROM uses for booting, use the boot bootldr global configuration command. Use the no form of the command to remove this rxboot image specification.
boot bootldr device: filename
device: | Device containing the rxboot image that ROM uses. The colon (:) is required. Valid values are as follows: ♦ bootflash: This device is the internal Flash memory in the Cisco 7500 series. ♦ slot0: This device is the first PCMCIA slot on the Cisco 7500 series Route Switch Processor (RSP) card. ♦ slot1: This device is the second PCMCIA slot on the Cisco 7500 series RSP card. |
filename | Name of the rxboot image file. The maximum filename length is 63 characters. |
There is no default Flash device or filename.
Global configuration
Use this command only with the Cisco 7500 series. The boot bootldr command sets the BOOTLDR environment variable in the current running configuration. You must specify both the device and the filename.
The no form of the command sets the BOOTLDR environment variable to a null string. On the Cisco 7500 series, a null string causes the first image file in bootflash to be used as the rxboot image that ROM uses for booting.
The following example specifies that the Flash memory card inserted in slot 0 of the RSP card contains the rxboot image:
boot bootldr slot0:boot-image
copy running-config startup-config
show boot
show flash
write memory
To configure the filename that is used to boot a secondary bootstrap image, use the boot bootstrap global configuration command. Use the no boot bootstrap command to disable booting from a secondary bootstrap image.
boot bootstrap flash [filename]
flash | Indicates that the router will be booted from Flash memory. |
mop | Indicates that the router will be netbooted from a system image stored on a DEC MOP server. |
tftp | (Optional) Indicates that the router will be netbooted from a system image stored on a TFTP server. |
filename | (Optional with flash.) Name of the system image from which you want to netboot. If you omit the filename when booting from Flash, the router uses the first system image stored in Flash memory. |
ip-address | (Optional) IP address of the TFTP server on which the system image resides. If omitted, this value defaults to the IP broadcast address of 255.255.255.255. |
mac-address | (Optional) MAC address of the MOP server on which the file resides. If the MAC address argument is not included, a broadcast message is sent to all MOP boot servers. The first MOP server to indicate that it has the file will be the server from which the router gets the boot image. |
interface | (Optional) Interface out which the router should send MOP requests to reach the MOP server. The interface options are async, dialer, Ethernet, loopback, null, serial, and tunnel. If the interface argument is not specified, a request will be sent on all interfaces that have MOP enabled, and the interface from which the first response is received will be used to load the software. |
No secondary bootstrap
Global configuration
The boot bootstrap command, in conjunction with setting bit 9 on the configuration register of an AGS, CGS, or MGS router, causes the router to load a secondary bootstrap image over the network. The secondary bootstrap image then loads the specified system image file. The name of the secondary bootstrap file is boot-csc3 or boot-csc4, depending on the router model. See the appropriate hardware installation guide for details on the configuration register and secondary bootstrap filename.
Use this command when you have attempted to load a system image but have run out of memory even after compressing the system image. Secondary bootstrap allows you to load a larger system image through a smaller secondary image.
In the following example, the system image file sysimage-2 will be loaded by using a secondary bootstrap image:
boot bootstrap sysimage-2
To modify the buffer size used to load configuration files, use the boot buffersize global configuration command. Use the no boot buffersize command to return to the default setting.
boot buffersize bytes
bytes | Specifies the size of the buffer to be used. There is no minimum or maximum size that can be specified. |
Buffer size of the NVRAM
Global configuration
Normally, the router uses a buffer the size of the system NVRAM to hold configuration commands read from the network. You can increase this size if you have a very complex configuration.
The following example sets the buffer size to 64000:
configure terminal boot buffersize 64000
To specify the device and filename of the configuration file from which the router configures itself during initialization (startup), use the boot config global configuration command. Use the no form of the command to remove this specification.
boot config device:filename
device: | Device containing the configuration file. The colon (:) is required. Valid devices are as follows: ♦ bootflash. This device is the internal Flash memory in the Cisco 7500 series. ♦ nvram. The device is the router's nonvolatile random-access memory (NVRAM). If you specify NVRAM, omit the filename. The colon (:) is required. ♦ slot0. This device is first PCMCIA slot on the Cisco 7500 series RSP card. ♦ slot1. This device is the second PCMCIA slot on the Cisco 7500 series RSP card. |
filename | Name of the configuration file. The configuration file must be an ASCII file. The maximum filename length is 63 characters. |
NVRAM (nvram:)
Global configuration
Use this command only with the Cisco 7500 series. You set the CONFIG_FILE environment variable in the current running memory when you use the boot config command. This variable specifies the configuration file used for initialization (startup).
If you specify nvram: as the device, and it contains only a distilled version of the configuration, the router displays an error message and does not update the CONFIG_FILE environment variable. (A distilled configuration is one that does not contain access lists.) If you specify a configuration file in the filename argument that does not exist or is not valid, the router displays an error message and does not update the CONFIG_FILE environment variable.
The router uses the NVRAM configuration during initialization when the CONFIG_FILE environment variable does not exist or when it is null (such as at first-time startup). If the router detects a problem with NVRAM or the configuration it contains, the router enters setup mode. Refer to the Router Products Getting Started Guide for more information on the setup command facility.
When you use the no form of this command, the router returns to using the NVRAM configuration as the startup configuration.
The following example instructs a Cisco 7500 series router to use the configuration file router-config located on the Flash memory card inserted in the second PCMCIA slot of the RSP card during initialization. The second line copies the specification to the startup configuration, ensuring that this specification will take effect upon the next reload:
Router (config)# boot config slot1:router-config ^Z Router# copy running-config startup-config
copy running-config startup-config
show boot
show flash
To change the default name of the host configuration filename from which you want to load configuration commands, use the boot host global configuration command. Use the no boot host command to restore the host configuration filename to the default.
boot host mop filename [mac-address] [interface]
mop | Indicates that the router will be configured from a configuration file stored on a DEC MOP server. |
tftp | (Optional) Indicates that the router will be configured from a configuration file stored on a TFTP server. |
rcp | (Optional) Indicates that the router will be configured from a configuration file stored on an rcp server. |
filename | Name of the file from which you want to load configuration commands. |
ip-address | (Optional) IP address of the TFTP server on which the file resides. If omitted, this value defaults to the IP broadcast address of 255.255.255.255. |
mac-address | (Optional) MAC address of the MOP server on which the file resides. If the MAC address argument is not included, a broadcast message is sent to all MOP boot servers. The first MOP server to indicate that it has the file will be the server from which the router gets the boot image. |
interface | (Optional) Interface out which the router should send MOP requests to reach the MOP server. The interface options are async, dialer, ethernet, serial, and tunnel. If the interface argument is not specified, a request will be sent on all interfaces that have MOP enabled, and the interface from which the first response is received will be used to load the software. |
The router uses its host name to form a host configuration filename. To form this name, the router converts its name to all lowercase letters, removes all domain information, and appends -confg.
Global configuration
Use the service config command to enable the loading of the specified configuration file at reboot time. Without this command, the router ignores the boot host command and uses the configuration information in NVRAM. If the configuration information in NVRAM is invalid or missing, the service config command is enabled automatically.
The network server will attempt to load two configuration files from remote hosts. The first is the network configuration file containing commands that apply to all network servers on a network. The second is the host configuration file containing commands that apply to one network server in particular.
The following example sets the host filename to wilma-confg at address 192.31.7.19:
boot host /usr/local/tftpdir/wilma-confg 192.31.7.19
To change the default name of the network configuration file from which you want to load configuration commands, use the boot network global configuration command. Use the no boot network command to restore the network configuration filename to the default.
boot network mop filename [mac-address] [interface]
mop | Configures the router to download the configuration file from a network server using the Digital Maintenance Operation Protocol (MOP) protocol. |
tftp | (Optional) Configures the router to download the configuration file from a network server using TFTP. If omitted and rcp is not specified, defaults to tftp. |
rcp | (Optional) Configures the router to download the configuration file from a network server using rcp. If omitted, defaults to tftp. |
filename | Name of the file from which you want to load configuration commands. The default filename is network-config. |
ip-address | (Optional) If rcp or tftp is specified, the IP address of the network server on which the compressed image file resides. If the IP address is omitted, this value defaults to the IP broadcast address of 255.255.255.255. |
mac-address | (Optional) If MOP is specified, the MAC address of the network server on which the file resides. If the MAC address argument is not included, a broadcast message is sent to all MOP boot servers. The first server to indicate that it has the file will be the server from which the router gets the boot image. |
interface | (Optional) If MOP is specified, interface out which the router should send MOP requests to reach the server. The interface options are async, dialer, ethernet, serial, and tunnel. If the interface argument is not specified, a request will be sent on all interfaces that have MOP enabled, and the interface from which the first response is received will be used to load the software. |
The default filename is network-config. The default transfer protocol type is TFTP, if neither tftp nor rcp is specified.
Global configuration
When booting from a network server, routers ignore routing information, static IP routes, and bridging information. As a result, intermediate routers are responsible for handling rcp or TFTP requests correctly. Before booting from a network server, verify that a server is available by using the ping command.
Use the service config command to enable the loading of the specified configuration file at reboot time. Without this command, the router ignores the boot network command and uses the configuration information in NVRAM. If the configuration information in NVRAM is invalid or missing, the service config command is enabled automatically.
The network server will attempt to load two configuration files from remote hosts. The first is the network configuration file containing commands that apply to all network servers on a network. Use the boot network command to identify the network configuration file.
The rcp software requires that a client send the remote username on each rcp request to the network server. When the boot network rcp command is executed, the router software sends the router host name as the both the remote and local usernames. The rcp implementation searches for the configuration files to be used relative to the account directory of the remote username on the network server, if the server has a directory structure, for example, as do UNIX systems.
If you copy the system image to a personal computer used as a file server, the remote host computer must support the remote shell (rsh) protocol.
The following example changes the network configuration filename to bridge_9.1 and uses the default broadcast address:
boot network bridge_9.1 service config
The following example changes the network configuration filename to bridge_9.1, specifies that rcp is to be used as the transport mechanism, and gives 131.108.1.111 as the IP address of the server on which the network configuration file resides:
boot network rcp bridge_9.1 131.108.1.111 service config
flash | On all platforms except the Cisco 7500 series, this keyword boots the router from internal Flash memory. If you omit all arguments that follow this keyword, the system searches internal Flash for the first bootable image. On the Cisco 7500 series, this keyword boots the router from a Flash device, as specified by the device: argument. On the Cisco 7500 series, when you omit all arguments that follow this keyword, the system searches the PCMCIA slot 0 for the first bootable image. |
device: | (Optional) Device containing the system image to load at startup. The colon (:) is required. Valid devices are as follows: ♦ flash: This device is the internal Flash memory. Optionally, use this device on all platforms except the Cisco 7500 series. The flash option is the only valid device option for all platforms except the Cisco 7500 series. ♦ bootflash: This device is the internal Flash memory in the Cisco 7500 series. ♦ slot0: This device is the first PCMCIA slot on the Cisco 7500 series RSP card. For the Cisco 7500 series, this device is the default if you do not specify a device. ♦ slot1: This device is the second PCMCIA slot on the Cisco 7500 series RSP card. |
partition-number: | (Optional) Number of the Flash memory partition that boots the router with the image specified by the optional filename argument. If you do not specify a filename, the router loads the first valid file in the specified partition of Flash memory. This argument is not used with the Cisco 7000 series and the Cisco 7500 series. |
filename | (Optional when used with boot system flash.) Name of the system image to load at startup. It is case sensitive. If you do not specify a filename, the router loads the first valid file in the specified Flash device, the specified partition of Flash memory, or the default Flash device if you also omit the device: argument. |
mop | Boots the router from a system image stored on a Digital MOP server. Do not use this keyword with the Cisco 7500 series. |
mac-address | (Optional) Media Access Control (MAC) address of the MOP server containing the specified system image file. If you do not include the MAC address argument, the router sends a broadcast message to all MOP boot servers. The first MOP server to indicate that it has the specified file will be the server from which the router gets the boot image. |
interface | (Optional) Interface the router uses to send out MOP requests to the MOP server. The interface options are async, dialer, ethernet, serial, and tunnel. If you do not specify the interface argument, the router sends a request out on all interfaces that have MOP enabled. The interface that receives the first response is the interface the router uses to load the software. |
rom | Boots the router from ROM. Do not use this keyword with the Cisco 7500 series. |
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 server containing the system image file. If omitted, this value defaults to the IP broadcast address of 255.255.255.255. |
If you do not specify a system image file with the boot system command, the router uses the configuration register settings to determine the default system image filename for booting from a network server. The router forms the default boot filename by starting with the word cisco and then appending the octal equivalent of the boot field number in the configuration register, followed by a hyphen (-) and the processor type name (cisconn-cpu). See the appropriate hardware installation guide for details on the configuration register and default filename. See also the command config-register. See also the "Syntax Description" section preceding this section.
On the Cisco 7500 series, if you omit a keyword (flash, mop, rom, rcp, or tftp) from the boot system command, the system defaults to booting from a system image stored on a TFTP server.
Global configuration
For this command to work, the config-register command must be set properly.
Enter several boot system commands to provide a fail-safe method for booting your router. The router stores and executes the boot system commands in the order in which you enter them in the configuration file. If you enter multiple boot commands of the same typefor example, if you enter two commands that instruct the router to boot from different network serversthen the router tries them in the order in which they appear in the configuration file. Use the boot system rom command to specify use of the ROM system image as a backup to other boot commands in the configuration.
Each time you write a new software image to Flash memory, you must delete the existing filename in the configuration file with the no boot system flash filename command. Then add a new line in the configuration file with the boot system flash filename command.
You can boot the router from a compressed image on a network server. When a network server boots software, both the image being booted and the running image must fit into memory. Use compressed images to ensure that enough memory is available to boot the router. You can compress a 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. (You can also uncompress data with the UNIX uncompress command.)
The rcp protocol requires that a client send the remote username in an rcp request to a server. When the router executes the boot system rcp command, by default the router software sends the router host name as the both the remote and local usernames. The rcp software searches for the system image to boot from the remote server relative to the directory of the remote username (if the server has a directory structure as UNIX systems do, for example).
You can force the router to stop booting by pressing the Break key during the first 60 seconds of startup. The router will enter ROM Monitor mode, where you can change the configuration register or boot the router manually.
For the Cisco 7500 series, the boot system command modifies the BOOT environment variable in the running configuration. The BOOT environment variable specifies a list of bootable images on various devices.
For routers with the RSP card (Cisco 7500 series), valid devices are bootflash, slot0, slot1, and tftp. On the Cisco 7500 series, the following forms of the boot system command specify a list of bootable images in the BOOT environment variable:
If an entry in the BOOT environment variable list does not specify a device, the router assumes the device is tftp. When tftp is the device, the router first loads the rxboot 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. To view the contents of the BOOT environment variable, use the show boot command.
To remove a single entry from the bootable image list, use the no form of a specific command. For example, to remove the entry that specifies a bootable image on a Flash memory card inserted in the second slot of the RSP card, use the no boot system flash slot1:[filename] command. All other entries in the list remain.
To eliminate all entries in the bootable image list, use the no boot system command. Issuing this command sets the BOOT environment variable to a null string, wiping out all entries. At this point, you can redefine the list of bootable images using the previous boot system commands. Remember to save your changes to your startup configuration by issuing the write memory or copy running-config startup-config command.
The following example illustrates a list specifying two possible internetwork locations for a system image, with the ROM software being used as a backup:
boot system cs3-rx.90-1 192.31.7.24
boot system cs3-rx.83-2 192.31.7.19
boot system rom
The following example boots the system boot relocatable image file igs-bpx-l from partition 2 of the Flash device:
boot system flash flash:2:igs-bpx-l
The following example instructs the router to boot from an image located on the Flash memory card inserted in slot 0 of the Cisco 7500 series RSP card:
boot system flash slot0:new-config
config-register
copy flash rcp
copy flash tftp
copy rcp flash
copy running-config startup-config
copy tftp flash
ip rcmd remote-username
show boot
write memory
To set the default Flash device for the system, use the cd EXEC command.
cd [device:]
device: | (Optional) Default device. The colon (:) is required. Valid devices are as follows: ♦ bootflash: This device is the internal Flash memory in the Cisco 7500 series. ♦ slot0: This device is the first PCMCIA slot on the Cisco 7500 series RSP card. For the Cisco 7500 series, this device is the initial default device and the default device when you omit the device: argument. ♦ slot1: This device is the second PCMCIA slot on the Cisco 7500 series RSP card. |
For the Cisco 7500 series, slot0 is the initial default device and the default device when you omit the device: argument.
EXEC
Use this command only with the Cisco 7500 series. For all EXEC commands that have an optional device: argument, the system uses the device specified by the cd command when you omit the optional device: argument. For example, the dir command contains an optional device: argument and displays a list of files on a Flash memory device. When you omit this device: argument, the system shows a list of the files on the Flash device specified by the cd command.
The following example sets the default device to the Flash memory card inserted in slot 0 of the RSP card:
cd slot0:
copy
delete
dir
pwd
show flash
undelete
To change the router configuration register settings, use the config-register global configuration command.
config-register value
value | Hexadecimal or decimal value that represents the 16-bit configuration register value you want to use the next time the router is restarted. The value range is from 0x0 to 0xFFFF (0 to 65535 in decimal). |
For the router models without Flash memory, the default is 0x101, which causes the router to boot from ROM and the Break key to be ignored. For router models with Flash memory, the default is 0x10F, which causes the router to boot from Flash memory and the Break key to be ignored.
Global configuration
This command applies only to the Cisco 2000, Cisco 3000, Cisco 4000 series, or to the Cisco 7000 series. All other models use a hardware configuration register.
The lowest four bits of the configuration register (bits 3, 2, 1, and 0) form the boot field. The boot field determines if the router boots manually, from ROM, or from Flash or the network. Bit 8 controls the console Break key; when set to 1, it causes the Break key to be ignored. The remaining bits control other features of the router and are typically set to 0.
To change the boot field value and leave all other bits set to their default values, follow these guidelines:
For more information about the configuration register bit settings and default filenames, see the appropriate router hardware installation guide.
In the following example, the configuration register is set to boot the system image from Flash memory:
config-register 0x010F
To enter global configuration mode, use the configure privileged EXEC command. You must be in global configuration mode to enter global configuration commands.
configure {terminal | memory | network}
terminal | Executes configuration commands from the terminal. |
memory | For all platforms except the Cisco 7500 series, executes the commands stored in NVRAM. For the Cisco 7500 series, executes the configuration specified by the CONFIG_FILE environment variable. |
network | Retrieves and executes the configuration commands stored in a file on a server. |
For all platforms except the Cisco 7500 series, there is no default.
For the Cisco 7500 series, the router uses the NVRAM configuration (if valid) when the CONFIG_FILE environment variable does not exist or is null (such as at first-time startup).
Privileged EXEC
If you do not specify terminal, memory, or network, the router prompts you for the source of configuration commands. If you specify terminal, the router executes the commands you enter at the system prompts.
On all platforms except the Cisco 7500 series, if you specify memory, the router executes the commands located in NVRAM. On the Cisco 7500 series, if you specify memory, the router executes the commands pointed to by the CONFIG_FILE environment variable. The CONFIG_FILE environment variable specifies the device and filename of the configuration file that the router uses to configure itself during initialization. Possible devices are as follows:
When the CONFIG_FILE environment variable specifies NVRAM, the router executes the NVRAM configuration only if it is an entire configuration, not a distilled version. A distilled configuration is one that does not contain access lists.
To view the contents of the CONFIG_FILE environment variable, use the show boot command. To modify the CONFIG_FILE environment variable, use the boot config command and then save your changes by issuing the write memory command.
After you enter the configure command, the system prompt changes from <router-name># to <router-name>(config)#, indicating that you are in global configuration mode. To leave global configuration mode and return to the privileged EXEC prompt, press ^Z.
In the following example, the router is configured from the terminal:
Router# configure
Configuring from terminal, memory, or network [terminal]?
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
In the following example, a Cisco 7500 router executes the commands pointed to by the CONFIG_FILE environment variable:
Router1# configure memory
In the following example, the router is configured from the file tokyo-confg at IP address 131.108.2.155:
Router1# configure network Host or network configuration file [host]? IP address of remote host [255.255.255.255]? 131.108.2.155 Name of configuration file [tokyo-confg]? Configure using tokyo-confg from 131.108.2.155? [confirm] y Booting tokyo-confg from 131.108.2.155:!! [OK - 874/16000 bytes]
boot config
show boot
show configuration
write memory
write terminal
To load a configuration file from a network server directly into NVRAM or to a location specified by the CONFIG_FILE environment variable without affecting the running configuration, use the configure overwrite-network privileged EXEC command.
configure overwrite-networkThis command has no arguments or keywords.
Disabled
Privileged EXEC
The copy tftp startup-config or copy rcp startup-config provides the same functionality as the configure overwrite-network command.
For all platforms except the Cisco 7500 series, the configure overwrite-network command loads a configuration file from a network server directly into NVRAM. The system prompts you to enter a filename of the configuration file to load. Because this command is not run through the parser, use caution when entering the filename. Also be careful not to load a file that is larger than NVRAM.
This command is useful if you are running an older version of software and are going to upgrade to a new Cisco IOS release. For example, if you have Software Release 9.1 ROMs, you can save time by loading a Cisco IOS Release10.2 configuration file before you get the Release 10.2 software. That way, you will be ready to reboot when you receive the Release 10.2 software image.
This command also allows you to replace an entire old configuration and ensure that none of the old configuration will remain.
For the Cisco 7500 series routers, the configure overwrite-network command loads a configuration file from a network server to a location specified by the CONFIG_FILE environment variable. The CONFIG_FILE environment variable specifies the configuration used during router initialization.
If the CONFIG_FILE environment variable does not exist or specifies NVRAM, then the router tries to save the configuration to NVRAM. If the configuration file is too large for NVRAM, the router stops executing the command and displays the message "Configuration too large for Non-volatile configuration memory." To continue use the boot config command to set or modify the CONFIG_FILE environment variable to point to a configuration file located in internal Flash memory or on a Flash memory card inserted in one of the PCMCIA slots. To save your modifications, use the write memory command. To view the contents of the CONFIG_FILE environment variable, use the show boot command.
The following example directly loads the host configuration file doc-ags+1-confg from a remote host into NVRAM:
doc-ags+1# configure overwrite-network Address of remote host [255.255.255.255]? Name of configuration file [doc-ags+1-confg]? Configure using doc-ags+1-confg from 255.255.255.255? [confirm] Loading doc-ags+1-confg...
To return to the EXEC mode from ROM monitor mode, use the continue ROM monitor command.
continueThis command has no arguments or keywords.
ROM monitor
Use this command when you are in ROM monitor mode, and you want to return to EXEC mode to use the system image instead of reloading.
In the following example, the continue command takes you from ROM monitor to EXEC mode:
> continue Router#
On the Cisco 7500 series, to copy any file from a Flash device or NVRAM to another destination, use the following copy EXEC command:
copy file_id {running-config | startup-config | file_id} (Cisco 7500 series only)
file_id | Specifies a device:filename as the source or destination of the copy operation. The device is optional; but when it is used, the colon (:) is required. Valid devices are as follows: ♦ bootflash: This device is the internal Flash memory in the Cisco 7500 series. ♦ slot0: This device is the first PCMCIA slot on the Cisco 7500 series RSP card. ♦ slot1: This device is the second PCMCIA slot on the Cisco 7500 series RSP card. ♦ nvram: This device is the router's NVRAM. If you specify NVRAM, omit the filename. The filename is the name of the source or destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters. |
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. (Note that the CONFIG_FILE environment variable specifies the startup configuration on a Cisco 7500 series.) |
If you omit the source or destination device, the router uses the default device specified by the cd command. If you omit the destination filename, the router uses the source filename.
EXEC
Use this copy command with the Cisco 7500 series.
On the Cisco 7500 series, the copy commands generally copy a file from a source to a destination. Some invalid combinations exist. Specifically, 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.
The CONFIG_FILE environment variable specifies the configuration used during router initialization. The BOOTLDR environment variable specifies the Flash device and filename containing the rxboot image that ROM uses for booting. The BOOT environment variable specifies a list of bootable images on various devices. To view the contents of environment variables, use the show boot command. To modify the CONFIG_FILE environment variable, use the boot config 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 write memory command.
If you do not specify a source or destination device, the router uses the default device specified by the cd command.
The following example copies the router-config1 file from the internal Flash memory of a Cisco 7500 series router to the router-backupconfig file on the Flash memory card inserted in the first slot of the RSP card:
copy bootflash:router-config1 slot0:router-backupconfig
In the following example, the router copies the router-image file from the Flash memory card inserted in slot 0 of the RSP card on a Cisco 7500 series to the startup configuration:
copy slot0:router-image startup-config
The following example copies the NVRAM configuration file to the router-backupconfig file on the Flash memory card inserted in slot 0 of the RSP card:
copy nvram: slot0:router-backupconfig
boot config
delete
dir
show boot
verify
write memory
To copy a bootstrap image from Flash memory to a network server on the Cisco 4500 series, use the copy bootflash EXEC command.
copy bootflash {rcp | tftp}
rcp | Specifies a copy operation to a network server using rcp. |
tftp | Specifies a TFTP server as the destination of the copy operation. |
EXEC
Use this command only on the Cisco 4500 router. You can use the network server copy of the bootstrap image as a backup copy or to verify that the copy in Flash memory is the same as the original file.
Use the copy bootflash rcp command to copy a bootstrap image from Flash memory to a network server using rcp. The rcp protocol requires that a client send the remote username of an rcp request to the server. When you issue the copy bootflash rcp command, by default the router 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 router software sends that username as the remote username.
If the TTY username is invalid, the router software uses the router host name as the 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. The rcp software copies the bootstrap image to an appropriate remote server. 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 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 router 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. |
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, if the router contains the following configuration lines:
hostname Rtr1 ip rcmd remote-username User0
and 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.
If you copy the bootstrap image to a personal computer used as a file server, the remote host computer must support rcp.
Use the copy bootflash tftp command to copy a bootflash image from Flash memory to a TFTP server.
The following example shows how to use the copy bootflash rcp command on a Cisco 4500 router:
Router(config)# ip rcmd remote-username netadmin1
Router# copy bootflash rcp
System flash directory, partition 2: File Length Name/status 1 984 junk [1048 bytes used, 8387560 available, 8388608 total] Address or name of remote host [223.255.254.254]? Source file name? junk Destination file name [junk]? junk Verifying checksum for 'junk' (file # 1)... OK Copy 'junk' from Flash to server as 'junk'? [yes/no]y !!!!!!!!!!!!!!!!!!!!!!!!!!!!! Upload to server done Flash copy took 0:00:00 [hh:mm:ss]
The exclamation points (!) indicate that the copy process is taking place. Each exclamation point (!) indicates that ten packets have been transferred successfully.
The following example illustrates how to use the copy bootflash tftp command on a Cisco 4500 router:
Router# copy bootflash tftp
System flash directory, partition 2: File Length Name/status 1 984 junk [1048 bytes used, 8387560 available, 8388608 total] Address or name of remote host [223.255.254.254]? Source file name? junk Destination file name [junk]? junk Verifying checksum for 'junk' (file # 1)... OK Copy 'junk' from Flash to server as 'junk'? [yes/no]y !!!!!!!!!!!!!!!!!!!!!!!!!!!!! Upload to server done Flash copy took 0:00:00 [hh:mm:ss]
copy mop bootflash
copy rcp bootflash
copy tftp bootflash
copy verify bootflash
erase bootflash
ip rcmd remote-username
show bootflash
To copy a file from Flash memory to another destination, use one of the following copy flash EXEC commands:
copy flash {rcp | tftp}
rcp | Specifies a copy operation to a network server using rcp. |
tftp | Specifies a TFTP server as the destination of the copy operation. |
file_id | Specifies a device:filename as the destination of the copy operation. The device argument is optional; but when it is used, the colon (:) is required. Valid devices are as follows: ♦ bootflash: This device is the internal Flash memory in the Cisco 7500 series. ♦ slot0: This device is the first PCMCIA slot on the Cisco 7500 series RSP card. ♦ slot1: This device is the second PCMCIA slot on the Cisco 7500 series RSP card. ♦ nvram: This device is the router's NVRAM. If you specify NVRAM, omit the filename. The filename argument is the name of the destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters. |
On the Cisco 7500 series, if you omit the destination device, the router uses the default device specified by the cd command. If you omit the destination filename, the router uses the source filename.
EXEC
On all platforms except the Cisco 7500 series, the copy flash command copies from internal Flash memory.
On the Cisco 7500 series, the copy flash command copies from one of the three Flash memory devices on the Cisco 7500 series. The system prompts you to enter a specific device and filename. You can enter one of the following as the source device on the Cisco 7500 series:
You must follow the source device with a colon (:) and a filename.
Use the copy flash rcp command to copy a system image from Flash memory to a network server using rcp. You can use the copy of the system image as a backup copy. You can also use it to verify that the copy in Flash memory is the same as the original file.
The rcp software requires that a client send the remote username on each rcp request to the server. When you issue the copy flash rcp command, by default the router software sends the remote username associated with the current TTY, if that name is valid. For example, if the user is connected to the router through Telnet and was authenticated through the username command, then the router software sends that username as the remote username.
If the TTY username is invalid, the router software uses the router host name as the both the remote and local usernames.
To specify a different remote username to be sent to the server, use the ip rcmd remote-username command. You can also specify the path of an existing directory along with the remote username.
![]() | Caution 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 router 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 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, if the router contains the following configuration lines:
hostname Rtr1 ip rcmd remote-username User0
and 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.
If you copy the system image to a personal computer used as a file server, the computer must support the rsh protocol.
Use the copy flash tftp command to copy a system image from Flash memory to a TFTP server. As with the copy flash rcp command, you can use the copy of the system image as a backup or to verify that the copy in Flash is the same as the original file.
On the Cisco 7500 series, the copy commands generally copy a file from a source to a destination. Some invalid combinations exist. Specifically, you cannot copy a running configuration to a running configuration, a startup configuration to a startup configuration, or TFTP to rcp. If you do not specify a source or destination device, the router uses the default device specified by the cd command.
On the Cisco 7500 series, when the destination is also specified by the CONFIG_FILE environment variable, the router prompts you for confirmation before proceeding with the copy. The CONFIG_FILE environment variable specifies the configuration used during router initialization. To view the contents of the CONFIG_FILE environment variable, use the show boot command. To modify the CONFIG_FILE environment variable, use the boot config command. To save your modifications to the CONFIG_FILE environment variable, use the write memory or copy running-config startup-config command.
The following example shows how to use the copy flash rcp command on a Cisco 4500 router:
Router# configure terminal Router# ip rcmd remote-username netadmin1 ^Z Router# copy flash rcp System flash directory, partition 2: File Length Name/status 1 984 junk [1048 bytes used, 8387560 available, 8388608 total] Address or name of remote host [223.255.254.254]? Source file name? junk Destination file name [junk]? junk Verifying checksum for 'junk' (file # 1)... OK Copy 'junk' from Flash to server as 'junk'? [yes/no]y !!!!!!!!!!!!!!!!!!!!!!!!!!!!! Upload to server done Flash copy took 0:00:00 [hh:mm:ss]
The exclamation points (!) indicate that the copy process is taking place. Each exclamation point (!) indicates that ten packets have been transferred successfully.
The following example illustrates how to use the copy flash rcp command:
Router# copy flash rcp IP address of remote host [255.255.255.255]? 101.2.13.110 Name of file to copy? gsxx writing gsxx !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!copy complete
The following example illustrates how to use the copy flash rcp command when copying from a particular partition of Flash memory:
Router# copy flash rcp 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 [ Type ?<number> for partition directory; ? for full directory; q to abort] Which partition? [default = 1]
The system will prompt if there are two or more partitions. If the partition entered is not valid, the process terminates. You have the option to enter a partition number, a question mark (?) for a directory display of all partitions, or a question mark and a number (?number) for a directory display of a particular partition. The default is the first partition.
System flash directory, partition 2: File Length Name/status 1 3459720 master/igs-bfpx.100-4.3 [3459784 bytes used, 734520 available, 4194304 total] Address or name of remote host [ABC.CISCO.COM]? Source file name?
The file will be copied from the partition given by the user earlier:
Destination file name [default = source name]? Verifying checksum for 'master/igs-bfpx.100-4.3' (file # 1)... OK Copy 'master/igs-bfpx.100-4.3' from Flash to server as 'master/igs-bfpx.100-4.3'? [yes/no] yes
The following example illustrates how to use the copy flash tftp command:
Router# copy flash tftp IP address of remote host [255.255.255.255]? 101.2.13.110 Name of file to copy? gsxx writing gsxx !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!copy complete
The following example illustrates how to use the copy flash tftp command when copying from a particular partition of Flash memory:
Router# copy flash tftp 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 [Type ?<number> for partition directory; ? for full directory; q to abort] Which partition? [default = 1]
The system will prompt if there are two or more partitions. If the partition entered is not valid, the process terminates. You have the option to enter a partition number, a question mark (?) for a directory display of all partitions, or a question mark and a number (?number) for a directory display of a particular partition. The default is the first partition.
System flash directory, partition 2: File Length Name/status 1 3459720 master/igs-bfpx.100-4.3 [3459784 bytes used, 734520 available, 4194304 total] Address or name of remote host [ABC.CISCO.COM]? Source file name?
The file will be copied from the partition given by the user earlier:
Destination file name [default = source name]? Verifying checksum for 'master/igs-bfpx.100-4.3' (file # 1)... OK Copy 'master/igs-bfpx.100-4.3' from Flash to server as 'master/igs-bfpx.100-4.3'? [yes/no] yes
The following example shows how to use the copy flash command on the Cisco 7500 series:
copy flash slot0:new-config
boot config
boot system flash
cd
copy running-config startup-config
ip rcmd remote-username
show boot
write memory
To copy a file from a MOP server to the router, use one of the following the copy mop EXEC commands:
copy mop bootflash (Cisco 4500 series only)
bootflash | Specifies to copy a bootstrap image from a MOP server to internal Flash memory on a Cisco 4500 series. |
flash | Specifies internal Flash memory as the destination of the copy operation. |
None
EXEC
The Cisco 7500 series does not support the copy mop command.
Use the copy mop bootflash command to copy a bootstrap image from a MOP server to the internal Flash memory on a Cisco 4500 series router. The router prompts for the name of the image file. It provides an option to erase the existing boot image in Flash before writing the new image into Flash. If no free space is available, or if files have never been written to Flash memory, you must erase Flash memory before copying the MOP image.
You do not need to specify the address of a MOP server. The router 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.
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 boot software image. The checksum of the boot image in Flash memory is displayed when the copy mop bootflash command completes. The README file was copied to the MOP server automatically when you installed the boot software image.
Use the copy mop flash command to copy a system image from a MOP server to internal Flash memory. MOP must be enabled on the relevant interfaces before you can use this command.
The router prompts for the MOP filename. It provides an option to erase existing Flash memory before writing onto it. The entire copying process takes several minutes and will differ 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 mop flash command.
The following example shows a sample output from the copy mop flash command. In this example, the system image junk, which already exists in Flash memory, is copied to Flash memory, and there is enough memory to copy the file without erasing any existing files.
Router# copy mop flash
System flash directory: File Length Name/status 1 984 junk [deleted] 2 984 junk [2096 bytes used, 8386512 available, 8388608 total] Source file name? junk Destination file name [junk]? Erase flash device before writing? [confirm] Flash contains files. Are you sure you want to erase? [confirm] Copy 'junk' from server as 'junk' into Flash WITH erase? [yes/no]yes Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased Loading junk from 1234.5678.9abc via Ethernet0: ! [OK - 984/8388608 bytes] Verifying checksum... OK (0x14B3) Flash copy took 0:00:01 [hh:mm:ss]
The following example shows sample output resulting from copying a system image into a partition of Flash memory. The system will prompt only if there are two or more read/write partitions or one read-only and one read/write partition and dual Flash bank support in boot ROMs. If the partition entered is not valid, the process terminates. You have the option to enter a partition number, a question mark (?) for a directory display of all partitions, or a question mark and a number (?number) for a directory display of a particular partition. The default is the first read/write partition.
Router# copy mop flash 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 [Type ?<no> for partition directory; ? for full directory; q to abort] Which partition? [default = 2]
If the partition is read-only and has dual Flash bank support in boot ROMs, the session continues as follows:
**** NOTICE **** Flash load helper v1.0 This process will accept the copy options and then terminate the current system image to use the ROM based image for the copy. Routing functionality will not be available during that time. If you are logged in via telnet, this connection will terminate. Users with console access can see the results of the copy operation. ---- ******** ---- Proceed? [confirm] System flash directory, partition 1: File Length Name/status 1 3459720 master/igs-bfpx.100-4.3 [3459784 bytes used, 734520 available, 4194304 total] Source file name? master/igs-bfpx-100.4.3 Destination file name [default = source name]?
The file will be copied into the partition given by the user earlier:
Loading master/igs-bfpx.100-4.3 from 131.108.1.111: ! Erase flash device before writing? [confirm] Flash contains files. Are you sure? [confirm] Copy 'master/igs-bfpx.100-4.3' from MOP server as 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes
If the partition is read-write, the session continues as follows:
System flash directory, partition 2: File Length Name/status 1 3459720 master/igs-bfpx.100-4.3 [3459784 bytes used, 734520 available, 4194304 total] Source file name? master/igs-bfpx.100-4.3 Destination file name [default = source name]?
The file will be copied into the partition given by the user earlier:
Loading master/igs-bfpx.100-4.3 from 131.108.1.111: ! Erase flash device before writing? [confirm] Flash contains files. Are you sure? [confirm] Copy 'master/igs-bfpx.100-4.3' from MOP server as 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes
The following example shows how to use the copy mop bootflash command to copy the bootstrap image junk:
Router# copy mop bootflash
System flash directory: File Length Name/status 1 984 junk [deleted] 2 984 junk [2096 bytes used, 8386512 available, 8388608 total] Source file name? junk Destination file name [junk]? Erase flash device before writing? [confirm] Flash contains files. Are you sure you want to erase? [confirm] Copy 'junk' from server as 'junk' into Flash WITH erase? [yes/no]yes Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased Loading junk from 1234.5678.9abc via Ethernet0: ! [OK - 984/8388608 bytes] Verifying checksum... OK (0x14B3) Flash copy took 0:00:01 [hh:mm:ss]
boot config
boot system flash
cd
copy bootflash tftp
copy flash tftp
copy tftp bootflash
delete
dir
erase bootflash
show boot
show bootflash
verify
copy verify bootflash
verify flash
To copy a file from a network server to the router or to another destination using rcp, use one of the following copy rcp EXEC commands. The copy rcp running-config command provides the same functionality as the configure network command. The copy rcp startup-config command provides the same functionality as the configure overwrite-network command.
copy rcp bootflash (Cisco 4500 series only)
bootflash | Specifies to copy a bootstrap image from a network server to Flash memory on a Cisco 4500 series using rcp. |
flash | Specifies internal Flash memory as the destination of the copy operation. The Cisco 7500 series cannot use this keyword; all other platforms can. |
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. |
file_id | Specifies a device:filename as the destination of the copy operation. The device argument is optional; but when it is used, the colon (:) is required. Valid devices are as follows: ♦ bootflash: This device is the internal Flash memory in the Cisco 7500 series. ♦ slot0: This device is the first PCMCIA slot on the Cisco 7500 series RSP card. ♦ slot1: This device is the second PCMCIA slot on the Cisco 7500 series RSP card. ♦ nvram: This device is the router's NVRAM. If you specify NVRAM, omit the filename. The filename argument is the name of the destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters. |
On the Cisco 7500 series, if you omit the destination device, the router uses the default device specified by the cd command. 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 router 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 router software sends that username as the remote username.
If the TTY username is invalid, the router software uses the router host name as the 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 router 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. |
If you copy a bootstrap image, system image, or configuration file from a personal computer used as a file server, the remote host computer must support rsh protocol.
Use the copy rcp bootflash command to copy a bootstrap image from a network server to Flash memory on a Cisco 4500 router using rcp. The router prompts for the name or address of the server and the name of the file to be copied. It provides an option to erase existing Flash memory before writing onto it, and allows you to confirm the erasure. The entire copying process takes several minutes and differs from network to network.
Before loading the router from Flash memory, verify that the checksum of the bootstrap image in Flash memory matches the checksum listed in the README file that was distributed with the system software image.
The checksum of the bootstrap image in Flash memory is displayed at the bottom of the screen when you issue the copy rcp bootflash command. The README file was copied to the server automatically when you installed the system software.
Use the copy rcp flash to copy a system image from a network server to the router's internal Flash memory using rcp. The router prompts for the address of the rcp server and rcp filename. When you issue this command, the system provides an option to erase existing 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 internal 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 rcp flash command. The README file was copied to the rcp server automatically when you installed the system software image.
Use the copy rcp running-config command to copy a configuration file from a network server to the router's running configuration environment using rcp. You can copy either a host configuration file or a network configuration file. Accept the default value of host to copy and load a host configuration file containing commands that apply to one network server in particular. Enter network to copy and load a network configuration file containing commands that apply to all network servers on a network.
Use the copy rcp startup-config command to copy a configuration file from a network server to the router's startup configuration environment using rcp.
On all platforms except the Cisco 7500 series, the copy rcp startup-config command copies a configuration file from the network server to NVRAM. On the Cisco 7500 series, the command copies a configuration file from the network server to the location specified by the CONFIG_FILE environment variable. The CONFIG_FILE environment variable specifies the configuration used during router initialization.
On the Cisco 7500 series, the copy commands generally copy a file from a source to a destination. Some invalid combinations exist. Specifically, you cannot copy a running configuration to a running configuration, a startup configuration to a startup configuration, or TFTP to rcp.
On the Cisco 7500 series, the copy rcp command generally copies a file from a network server to another destination using rcp. If you do not specify a source or destination device, the router uses the default device specified by the cd command.
On the Cisco 7500 series, when the destination is also specified by the CONFIG_FILE environment variable, the router prompts you for confirmation before proceeding with the copy. To view the contents of the CONFIG_FILE environment variable, use the show boot command. To modify the CONFIG_FILE environment variable, use the boot config command. To save your modifications, use the write memory or copy running-config startup-config command.
The following example shows how to use the copy rcp bootflash command on a Cisco 4500 router:
Router# configure terminal Router(config)# ip rcmd remote-username netadmin1 ^Z Router# copy rcp bootflash
Boot flash directory: File Length Name/status 1 2622607 c4500-xboot [2622672 bytes used, 1571632 available, 4194304 total] Address or name of remote host [255.255.255.255]? 223.255.254.254 Source file name? c4500-xboot.101 Destination file name [c4500-xboot.101]? Accessing file 'c4500-xboot.101' on 223.255.254.254... Loading c4500-xboot.101 from 223.255.254.254 (via Ethernet0): -[OK] Erase flash device before writing? [confirm] Flash contains files. Are you sure you want to erase? [confirm] Copy 'c4500-xboot.101' from TFTP server into bootflash as 'c4500-xboot.101' WITH erase? [yes/no] yes Erasing device... eeeeeeeeeeeeeeee ...erased Loading c4500-xboot.101 from 223.255.254.254 (via Ethernet0): !!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK - 2622607/4194304 bytes] Verifying checksum... OK (0xE408) Flash copy took 0:00:10 [hh:mm:ss]
The exclamation points (!) indicate that the copy process is taking place. Each exclamation point (!) indicates that ten packets have been transferred successfully.
The following example shows how to use the copy rcp flash command on a Cisco 4500 system. The interface might differ slightly on other systems. This example copies a system image named junk from the netadmin1 directory on the remote server named SERVER1.CISCO.COM with an IP address of 131.108.101.101 to the router's Flash memory. To ensure that enough Flash memory is available to accommodate the system image to be copied, the router software allows you to erase the contents of Flash memory first.
Router1# configure terminal Router1(config)# rcmd remote-username netadmin1 ^Z Router# copy rcp flash
System flash directory, partition 2: File Length Name/status 1 984 junk [deleted] 2 984 junk [2096 bytes used, 8386512 available, 8388608 total] Address or name of remote host [255.255.255.255]? 131.108.101.101 Source file name? junk Destination file name [junk]? Accessing file 'junk' on 131.108.101.101... Loading dirt/ssangiah/junk .from 131.108.101.101 (via Ethernet0): ! [OK] Erase flash device before writing? [confirm] Flash contains files. Are you sure you want to erase? [confirm] Copy 'junk' from server as 'junk' into Flash WITH erase? [yes/no]yes Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased Loading junk from 223.255.254.254 (via Ethernet0): ! [OK - 984/8388608 bytes] Verifying checksum... OK (0x14B3) Flash copy took 0:00:01 [hh:mm:ss]
The following example shows sample output resulting from copying a system image into a partition of Flash memory. The system prompts only if there are two or more read/write partitions or one read-only and one read/write partition and dual Flash bank support in boot ROMs. If the partition entered is not valid, the process terminates. You have the option to enter a partition number, a question mark (?) for a directory display of all partitions, or a question mark and a number (?number) for a directory display of a particular partition. The default is the first read/write partition.
Router# copy rcp flash 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 [Type ?<no> for partition directory; ? for full directory; q to abort] Which partition? [default = 2]
If the partition is read-only and has dual Flash bank support in boot ROM, the session continues as follows:
**** NOTICE **** Flash load helper v1.0 This process will accept the copy options and then terminate the current system image to use the ROM based image for the copy. Routing functionality will not be available during that time. If you are logged in via telnet, this connection will terminate. Users with console access can see the results of the copy operation. ---- ******** ---- Proceed? [confirm] System flash directory, partition 1: File Length Name/status 1 3459720 master/igs-bfpx.100-4.3 [3459784 bytes used, 734520 available, 4194304 total] Address or name of remote host [255.255.255.255]? 131.108.1.1 Source file name? master/igs-bfpx-100.4.3 Destination file name [default = source name]?
The file will be copied into the partition given by the user earlier:
Loading master/igs-bfpx.100-4.3 from 131.108.1.111: ! Erase flash device before writing? [confirm] Flash contains files. Are you sure? [confirm] Copy 'master/igs-bfpx.100-4.3' from TFTP server as 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes
If the partition is read-write, the session continues as follows:
System flash directory, partition 2: File Length Name/status 1 3459720 master/igs-bfpx.100-4.3 [3459784 bytes used, 734520 available, 4194304 total] Address or name of remote host [255.255.255.255]? 131.108.1.1 Source file name? master/igs-bfpx.100-4.3 Destination file name [default = source name]?
The file will be copied into the partition given by the user earlier:
Accessing file 'master/igs-bfpx.100-4.3' on ABC.CISCO.COM... Loading master/igs-bfpx.100-4.3 from 131.108.1.111: ! Erase flash device before writing? [confirm] Flash contains files. Are you sure? [confirm] Copy 'master/igs-bfpx.100-4.3' from TFTP server as 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes
Router# configure terminal Router(config)# ip rcmd remote-username netadmin1 ^Z Router# copy rcp running-config
Host or network configuration file [host]? Address of remote host [255.255.255.255]? 131.108.101.101 Name of configuration file [Router-confg]? host1-confg Configure using host1-confg from 131.108.101.101? [confirm] Connected to 131.108.101.101 Loading 1112 byte file host1-confg:![OK] Router# %SYS-5-CONFIG: Configured from host1-config by rcp from 131.108.101.101
The following example shows how to use copy rcp startup-config command on a Cisco 4000 system. The interface might differ slightly on other systems. This example specifies a remote username of netadmin1. Then it copies and stores a host configuration file host2-confg from the netadmin1 directory on the remote server with an IP address of 131.108.101.101.
Router# configure terminal Router(config)# ip rcmd remote-username netadmin1 ^Z Router# copy rcp startup-config
Address of remote host [255.255.255.255]? 131.108.101.101 Name of configuration file[rtr2-confg]? host2-confg Configure using rtr2-confg from 131.108.101.101?[confirm] Connected to 131.108.101.101 Loading 1112 byte file rtr2-confg:![OK] [OK] Router# %SYS-5-CONFIG_NV:Non-volatile store configured from rtr2-config by
rcp from 131.108.101.101
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:
copy rcp slot0:router-image
boot config
boot system flash
cd
copy flash rcp
copy running-config rcp
copy running-config startup-config
copy startup-config rcp
ip rcmd remote-username
show boot
verify flash
write memory
To copy the router's running configuration file to another destination, use one of the following copy running-config EXEC commands. The copy running-config startup-config command provides similar functionality to the write memory command. The copy running-config rcp or copy running-config tftp provides the same functionality as the write network command.
copy running-config {rcp | startup-config | tftp}
rcp | Specifies a copy operation to a network server using rcp. |
startup-config | Specifies the configuration used for initialization as the destination of the copy operation. The Cisco 4500 series cannot use this keyword. |
tftp | Specifies a TFTP server as the destination of the copy operation. |
file_id | Specifies a device:filename as the destination of the copy operation. The device argument is optional; but when it is used, the colon (:) is required. Valid devices are as follows: ♦ bootflash: This device is the internal Flash memory in the Cisco 7500 series. ♦ slot0: This device is the first PCMCIA slot on the Cisco 7500 series RSP card. ♦ slot1: This device is the second PCMCIA slot on the Cisco 7500 series RSP card. ♦ nvram: This device is the router's NVRAM. If you specify NVRAM, omit the filename. The filename argument is the name of the destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters. |
On the Cisco 7500 series, if you omit the destination device, the router uses the default device specified by the cd command. If you omit the destination filename, the router uses the source filename.
EXEC