-
Access and Communication Servers Command Reference
-
About This Manual
-
Access Server and Communication Server Product Overview
-
User Interface Commands
-
System Image and Configuration File Load Commands
-
Configuring Terminal Lines and Modem Support
-
System Management Commands
-
User Interface Config Commands
-
Dial on Demand Routing Commands
-
X.25 Configuration Commands
-
Frame Relay Commands
-
SMDS Commands
-
Telnet Configuration Commands
-
LAT Configuration Commands
-
TN3270 Configuration
-
AppleTalk Remote Access Commands
-
SLIP and PPP Configuration Commands
-
XRemote Configuration Commands
-
AppleTalk Routing Commands
-
IP Commands
-
IP Routing Protocols Commands
-
Novell IPX Commands
-
Protocol Translation Configuration Commands
-
Appendix A, ASCII Character Set
-
Appendix B, Modem and Chat Script Configuration
-
Appendix C, Regular Expressions
-
Appendix D, Refs and Reading
-
Appendix E, X.3 PAD Parameters
-
Table Of Contents
System Image and Configuration File Load Commands
System Image and Configuration File Load Commands
This chapter provides detailed descriptions of the commands used to load and copy system images and configuration files. System images contain the system software. Configuration files contain commands entered to customize the functions of the access server.
For access server configuration information and examples, refer to the "Loading System Images and Configuration Files" chapter in the Access and Communication Servers Configuration Guide.
Note
Commands in this chapter that have been replaced by new commands continue to perform their normal functions in the current release but are not longer documented. Support for these commands will cease in a future release.
Table 3-1 Mapping Old Commands to New Commands
For access server configuration information and examples, refer to the "Loading System Images, Microcode Images, and Configuration Files" chapter in the Access and Communication Servers Configuration Guide.
async-bootp
Use the async-bootp command to enable support for extended BOOTP requests as defined in RFC 1084 when the access server is configured for SLIP. Use the no form of this command to restore the default.
async-bootp tag [:hostname] data
no async-bootpSyntax Description
Table 3-2 Async-BOOTP Tag Keywords
Default
If no extended BOOTP commands are entered, the access server software generates a gateway and subnet mask appropriate for the local network.
Command Mode
Global configuration
Usage Guidelines
Use the EXEC command show async bootp to list the configured parameters. Use the no
async-bootp command to clear the list.Examples
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 172.30.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 :172.30.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.0The following example specifies a negative time offset of the local subnetwork of -3600 seconds:
async-bootp time-offset -3600The following example specifies the IP address of a time server:
async-bootp time-server 172.30.1.4Related Command
b
To boot the access server manually, use the b ROM monitor command.
b
b filename [ip-address]
b flash [filename]
b flash [device:][partition-number:][filename]Syntax Description
Default
If you enter the b command and press Return, the access server boots from ROM by default.
If you enter the b flash command without specifying a filename, the first valid file in Flash memory is loaded.
For other defaults, see the preceding Syntax Description section.
Command Mode
ROM monitor
Usage Guidelines
Use this command only when your access server cannot find the configuration information needed in nonvolatile memory. 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 for manual booting, change the boot bits in the configuration register to zero and then issue the reload command.
Examples
In the following example, the access server is manually booted from ROM:
> bF3:(ROM Monitor copyrights)In the following example, the file cstest is netbooted from IP address 172.30.15.112:
> b cstest 172.30.15.112F3:(ROM Monitor copyrights)The following example shows the b flash command without the filename argument.The first valid file in Flash memory is loaded.
> b flashF3: 1858656+45204+166896 at 0x1000Booting igs-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR [OK - 1903912/13765276 bytes]F3: 1858676+45204+166896 at 0x1000(ROM Monitor copyrights)In the following example, the b flash command is used with the filename igs-k. This is the file that will be loaded.
> b flash igs-kF3: 1858656+45204+166896 at 0x1000Booting igs-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR [OK - 1903912/13765276 bytes]F3: 1858676+45204+166896 at 0x1000(ROM Monitor copyrights)In the following example, the b flash flash command boots the relocatable image file igs-bpx-l from partition 2 in Flash memory.
> b flash flash:2:igs-bpx-lF3: 3562264+98228+303632 at 0x30000B4(ROM Monitor copyrights)boot bootstrap
To configure the filename that is used to boot a secondary bootstrap image, use the boot bootstrap global configuration command. Use the no form of the command to disable booting from a secondary bootstrap image.
boot bootstrap flash [filename]
no boot bootstrap flash [filename]
boot bootstrap mop filename [mac-address] [interface]
no boot bootstrap mop filename [mac-address] [interface]
boot bootstrap [tftp] filename [ip-address]
no boot bootstrap [tftp] filename [ip-address]Syntax Description
Default
No secondary bootstrap
Command Mode
Global configuration
Usage Guidelines
The boot bootstrap command, in conjunction with setting bit 9 on the configuration register of a access server, causes the access server 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 access server 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.
Example
In the following example, the system image file sysimage-2 will be loaded by using a secondary bootstrap image:
boot bootstrap sysimage-2boot buffersize
To modify the buffer size used to load configuration files, use the boot buffersize global configuration command. Use the no form of the command to return to the default setting.
boot buffersize bytes
no boot buffersizeSyntax Description
bytes
Specifies the size of the buffer to be used. There is no minimum or maximum size that can be specified.
Default
Buffer size of the nonvolatile memory
Command Mode
Global configuration
Usage Guidelines
Normally, the access server uses a buffer the size of the system nonvolatile memory to hold configuration commands read from the network. You can increase this size if you have a very complex configuration. There is no minimum or maximum size that can be specified.
Example
The following example sets the buffer size to 64000:
boot buffersize 64000boot host
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 form of the command to restore the host configuration filename to the default.
boot host mop filename [mac-address] [interface]
no boot host mop filename [mac-address] [interface]
boot host [tftp | rcp] filename [ip-address]
no boot host [tftp | rcp] filename [ip-address]Syntax Description
Default
The access server uses its host name to form a host configuration filename. To form this name, the access server converts its name to all lowercase letters, removes all domain information, and appends -confg.
Command Mode
Global configuration
Usage Guidelines
Use the service config command to enable the loading of the specified configuration file at reboot time. Without this command, the access server ignores the boot host command and uses the configuration information in nonvolatile memory. If the configuration information in nonvolatile memory 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.
Example
The following example sets the host filename to wilma-confg at address 172.30.7.19:
boot host /usr/local/tftpdir/wilma-confg 172.30.7.19Related Commands
boot network
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 form of this command to restore the network configuration filename to the default.
boot network mop filename [mac-address] [interface]
no boot network mop filename [mac-address] [interface]
boot network [tftp | rcp] filename [ip-address]
no boot network [tftp | rcp] filename [ip-address]Syntax Description
Default
The default filename is network-config. The default transfer protocol type is tftp, if neither tftp nor rcp is specified.
Command Mode
Global configuration
Usage Guidelines
When booting from a network server, access servers ignore routing information and static IP routes information. As a result, intermediate access servers 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 access server ignores the boot network command and uses the configuration information in nonvolatile memory. If the configuration information in nonvolatile memory is invalid or missing, the service config command is enabled automatically.
The network server attempts 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 protocol 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 access server software sends the host name as the both the remote and local usernames. The rcp protocol implementation searches for the configuration files to be used relative to the account directory of the remote username on the network server.
If you copy the system image to a PC used as a file server, the remote host computer must support the remote shell (rsh) protocol.
CautionFor rcp, if you do not explicitly specify a remote username by issuing the ip rcmd remote-username command and the access server host name is used, an account for the access server host name must be defined on the destination server. If the network administrator of the destination server did not establish an account for the access server host name, this command will not execute successfully.
If you copy the system image to a personal computer used as a file server, the remote host computer must support the remote shell protocol.
Examples
The following example changes the network configuration filename to bridge_9.1 and uses the default broadcast address:
boot network bridge_9.1service configThe following example changes the network configuration filename to bridge_9.1, specifies that rcp is to be used as the transport mechanism, and gives 172.30.1.111 as the IP address of the server on which the network configuration file resides.
boot network RCP bridge_9.1 172.30.1.111service configRelated Commands
boot host
ip rcmd remote-username
service configboot system
To change the filename of the system image that is loaded onto the access server when it reboots, use the boot system global configuration command. Use the no boot system command to remove the name.
boot system flash [device:][partition-number:][filename]
no boot system flash [filename]
boot system mop filename [mac-address] [interface]
no boot system mop filename [mac-address] [interface]
boot system rom
no boot system rom
boot system [tftp | rcp] filename [ip-address]
no boot system [tftp | rcp] filename [ip-address]
boot system flash [device:][partition-number:][filename]
no boot systemSyntax Description
Default
If you do not specify a system image file with the boot system command, the access server uses the configuration register settings to determine the default system image filename for netbooting. The access server 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.
If neither tftp or rcp is specified, the default transfer protocol type is tftp.
Command Mode
Global configuration
Usage Guidelines
In order 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 access server. Use the boot system rom command to specify use of the ROM system image as a backup to other boot commands in the configuration. The boot system commands are stored and executed on the order in which they are entered. If you enter multiple boot commands of the same type—for example, if you enter two commands that instruct the access server to boot from different network servers—then the access server tries them in the order they are entered.
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.
Note
You can netboot from a compressed image. When a server netboots software, the image being booted and the running image must both fit into memory. Use compressed images to ensure that there is enough available memory to boot the access server. You can produce a compressed software image on any UNIX platform using the compress command. Refer to your UNIX platform's documentation for the exact usage of the compress command. (You can also uncompress data with the UNIX uncompress command.)
The rcp protocol requires that a client send the remote username on an rcp request to a server. When the boot system rcp command is executed, by default the access server software sends the host name as the both the remote and local usernames. The rcp software searches for the system image to be booted from the remote server relative to the directory of the remote username, if the server has a directory structure, for example, as do UNIX systems.
Examples
The following example shows a list specifying two possible internetwork locations for a system image, with the ROM software being used as a backup. When the system image is booted from either of the internetwork locations, TFTP is used as the transport mechanism:
boot system cs3-rx.90-1 172.30.7.24 boot system cs3-rx.83-2 172.30.7.19 boot system romThe 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-lRelated Commands
config-register
copy flash
copy rcp
copy tftp
ip rcmd remote-usernameconfigure
To enter global configuration mode, use the configure privileged EXEC command.
configure {terminal | memory | network}
Syntax Description
Default
None
Command Mode
Privileged EXEC
Usage Guidelines
If you do not specify terminal or memory the access server prompts you for the source of configuration commands. 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 Ctrl-Z. If you specify memory, the access server executes the commands located in NVRAM.
Example
In the following example, the access server is configured from the terminal:
Router# configureConfiguring from terminal, memory, or network [terminal]?Enter configuration commands, one per line. End with CNTL/Z.Related Commands
configure overwrite
copy running-config
show configuration
show running-config
configure overwrite
The copy rcp startup-config or copy tftp startup-config command replaces the configure overwrite command. If you use rcp, see the copy rcp command for more information. If you use TFTP, see the copy tftp command for more information.
config-register
To change the access server configuration register settings, use the config-register global configuration command.
config-register value
Syntax Description
Default
For the access server models without Flash memory, the default is 0x101, which causes the access server to boot from ROM and the Break key to be ignored. For access server models with Flash memory, the default is 0x10F, which causes the access server to boot from Flash memory and the Break key to be ignored.
Command Mode
Global configuration
Usage Guidelines
The lowest four bits of the configuration register (bits 3, 2, 1, and 0) form the boot field. The boot field determines if the access server 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 access server 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 access server hardware installation guide.
Example
In the following example, the configuration register is set to boot the system image from Flash memory:
config-register 0x010FRelated Commands
continue
To return to the EXEC mode from ROM monitor mode, use the continue ROM monitor command.
continue
Syntax Description
This command has no arguments or keywords.
Command Mode
ROM monitor
Usage Guidelines
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. The angle bracket (>) indicates that you are in ROM monitor mode. You are in ROM monitor mode when you manually load a system image or perform diagnostic tests. Otherwise, you will most likely never be in this mode.
CautionWhile in ROM monitor mode, the Cisco IOS system software is suspended until you issue either a reset or the continue command.
Example
In the following example, the continue command takes you from ROM monitor to EXEC mode:
> continueRouter#copy flash
To copy a file from Flash memory to another destination, use one of the following copy flash EXEC commands:
copy flash {rcp | tftp}
Syntax Description
rcp
Specifies a copy operation to a network server using rcp.
tftp
Specifies a TFTP server as the destination of the copy operation.
Command Mode
EXEC
Usage Guidelines
To copy a system image from Flash memory to a network server that is using rcp, use the copy flash rcp EXEC command. To copy a system image from Flash memory to a network server that is using TFTP, use the copy flash tftp command.
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 in the original file on disk.
The rcp protocol 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 access server 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 access server through Telnet and the user was authenticated through the username command, then the Cisco IOS software sends that username as the remote username.
If the TTY username is invalid, the Cisco IOS software uses the access server host name as the both the remote and local usernames.
Note
To specify that a different remote username be sent to the server, use the ip rcmd remote-username command. rcp copies the system image to the remote server relative to the directory of the remote username, if that server has a directory structure (for example, UNIX systems).
Cautionan 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 access server 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 that is used, and if a default remote username is used, this command will not execute successfully.
If you copy the system image to a PC used as a file server, the PC must support the remote shell (rsh) protocol.
Examples
The following example illustrates how to use this command with the tftp keyword:
Router# copy flash tftpIP address of remote host [255.255.255.255]? 172.30.13.110Name of file to copy? igs-kwriting gsxx !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!copy completeThe following example illustrates how to use this command when copying from a particular partition of Flash memory:
Router# copy flash tftpSystem flash partition information:Partition Size Used Free Bank-Size State Copy-Mode1 4096K 2048K 2048K 2048K Read Only RXBOOT-FLH2 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 can enter a partition number, ? for directory display of all partitions, or ?number for directory display of a particular partition. The default is the first partition.
System flash directory, partition 2:File Length Name/status1 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)... OKCopy 'master/igs-bfpx.100-4.3' from Flash to serveras 'master/igs-bfpx.100-4.3'? [yes/no] yesThe following example shows how to copy a system image from Flash memory to a network server using rcp:
Router# configure terminalRouter#config ip rcmd remote-username netadmin1Ctrl-ZRouter# copy flash rcpSystem flash directory, partition 2:File Length Name/status1 984 junk[1048 bytes used, 8387560 available, 8388608 total]Address or name of remote host [223.255.254.254]?Source file name? junkDestination file name [junk]? junkVerifying checksum for 'junk' (file # 1)... OKCopy 'junk' from Flash to serveras 'junk'? [yes/no]y!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Upload to server doneFlash 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 this command with rcp:
Router# copy flash rcpIP address of remote host [255.255.255.255]? 172.30.13.110Name of file to copy? gsxxwriting gsxx !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!copy completeThe following example illustrates how to use this command when copying from a particular partition of Flash memory:
Router# copy flash rcpSystem flash partition information:Partition Size Used Free Bank-Size State Copy-Mode1 4096K 2048K 2048K 2048K Read Only RXBOOT-FLH2 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 you 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, ? for directory display of all partitions, or ?number for directory display of a particular partition. The default is the first partition.
System flash directory, partition 2:File Length Name/status1 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)... OKCopy 'master/igs-bfpx.100-4.3' from Flash to serveras 'master/igs-bfpx.100-4.3'? [yes/no] yesRelated Commands
boot system
copy tftp
copy rcp
ip rcmd remote-usernamecopy mop flash
To copy a system image using MOP into Flash memory, use the copy mop flash EXEC command.
copy mop flash
Syntax Description
This command has no arguments or keywords.
Command Mode
EXEC
Usage Guidelines
The access server 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.
CautionIf the checksum value is not correct according to the value in the README file, do not reboot the access server. Issue the copy mop flash command and compare the checksums again. If the checksum is repeatedly wrong, copy the original system software image back into Flash memory before you reboot the access server from Flash memory. If you have a bad image in Flash memory and try to boot from Flash, and netbooting is not configured, the access server will start the system image contained in ROM. If ROM does not contain a fully functional system image, the access server might not function and will have to be reconfigured through a direct console port connection.
Examples
The following example shows sample output of when copying a system image into a partition of Flash memory:
Router# copy mop flashSystem flash directory:File Length Name/status1 984 junk [deleted]2 984 junk[2096 bytes used, 8386512 available, 8388608 total]Source file name? junkDestination file name [junk]?Erase flash device before writing? [confirm]Flash contains files. Are you sure you want to erase? [confirm]Copy 'junk' from serveras 'junk' into Flash WITH erase? [yes/no]yesErasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erasedLoading 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 of 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 can enter a partition number, ? for directory display of all partitions, or ?number for directory display of a particular partition. The default is the first read/write partition.
Router# copy mop flashSystem flash partition information:Partition Size Used Free Bank-Size State Copy-Mode1 4096K 2048K 2048K 2048K Read Only RXBOOT-FLH2 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.0This process will accept the copy options and then terminatethe 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/status1 3459720 master/igs-bfpx.100-4.3[3459784 bytes used, 734520 available, 4194304 total]Source file name? master/igs-bfpx-100.4.3Destination 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 172.30.1.111: !Erase flash device before writing? [confirm]Flash contains files. Are you sure? [confirm]Copy 'master/igs-bfpx.100-4.3' from MOP serveras 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yesIf the partition is read-write, the session continues as follows:
System flash directory, partition 2:File Length Name/status1 3459720 master/igs-bfpx.100-4.3[3459784 bytes used, 734520 available, 4194304 total]Source file name? master/igs-bfpx.100-4.3Destination 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 172.30.1.111: !Erase flash device before writing? [confirm]Flash contains files. Are you sure? [confirm]Copy 'master/igs-bfpx.100-4.3' from MOP serveras 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yesRelated Commands
copy rcp
To copy a system image from a network server into Flash memory using rcp, use the copy rcp EXEC commands. The copy rcp running-config command replaces the configure network command. The copy rcp startup-config command replaces the configure overwrite-network command.
copy rcp {flash | running-config | startup-config}
Syntax Description
Command Mode
EXEC
Usage Guidelines
The access server prompts you for the address of the rcp server and rcp 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 rcp flash command. The README file was copied to the server automatically when you installed the system software image.
CautionIf the checksum value is not correct according to the value in the README file, do not reboot the access server. Issue the copy rcp flash command and compare the checksums again. If the checksum is repeatedly wrong, copy the original system software image back into Flash memory before you reboot the access server from Flash memory. If you have a bad image in Flash memory and try to boot from Flash, and netbooting is not configured, the access server will start the system image contained in ROM. If ROM does not contain a fully functional system image, the access server will not function and will have to be reconfigured through a direct console port connection.
The rcp protocol requires that a client send the remote username of an rcp request to the server. When you issue the copy rcp flash command, by default the software sends the username associated with the current TTY, if that name is valid. For example, if the user is connected to the access server through Telnet and the user was authenticated through the username command, then the Cisco IOS software sends that username as the remote username.
Note
If the TTY remote username is invalid, the Cisco IOS software uses the access server host name as the both the remote and local usernames. To specify that a different remote username be sent to the network server, use the ip rcmd remote-username command. The rcp protocol copies the system image from the remote server relative to the directory of the remote username, if the server has a directory structure (for example, UNIX systems).
Cautionan 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 access server 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, and if a default remote username is used, this command will not execute successfully.
If you copy the system image from a PC used as a file server, the remote host computer must support the remote shell protocol.
Use the copy rcp flash to copy a system image from a network server to the access server's internal Flash memory using rcp. The access server 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 will differ 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 tftp flash command. The README file was copied to the rcp server automatically when you installed the system software image.
CautionIf the checksum value does not match the value in the README file, do not reboot the access server. Reissue the copy rcp flash command and compare the checksums again. If the checksum is repeatedly wrong, copy the original system software image back into Flash memory before you reboot the access server from Flash memory. If you have a bad image in Flash memory and try to boot from Flash, and booting from a network server is not configured, the access server will start the system image contained in ROM. If ROM does not contain a fully functional system image, the access server will not function and will have to be reconfigured through a direct console port connection.
Use the copy rcp running-config command to copy a configuration file from a network server to the access server'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. Enter network to copy and load a network configuration file containing commands that apply to all network servers on a network.
Note
Use the copy rcp startup-config c
