Additional File Transfer Function Commands

For configuration information and examples, refer to the "Configuring Additional File Transfer Functions" chapter in the Cisco IOS Configuration Fundamentals Configuration Guide.

Syntax Description

tag	Item being requested; expressed as filename, integer, or IP dotted-decimal address. See Table 37 for possible keywords.
: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.

Table 37: async-bootp Tag Keywords

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).
nbns-server address	Dotted decimal address specifying the IP address of Windows NT servers.
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.

Defaults

If no extended BOOTP commands are entered, the Cisco IOS software generates a gateway and subnet mask appropriate for the local network.

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

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

Related Commands

Command	Description
show async-bootp	Displays the extended BOOTP request parameters that have been configured for asynchronous interfaces.

Syntax Description

type	(Optional) Type of encryption to use on the password. A value of 0 disables encryption. A value of 7 indicates proprietary encryption.
password	Password to use for FTP connections.

Defaults

The router forms a password username@routername.domain. The variable username is the username associated with the current session, routername is the configured host name, and domain is the domain of the router.

Command Modes

Global configuration

Command History

Release	Modification
10.3	This command was introduced.

Examples

The following example configures the router to use the username red and the password blue for FTP connections:

ip ftp username red
ip ftp password blue

Related Commands

Command	Description
ip ftp password	Specifies the password to be used for FTP connections.
ip ftp source-interface	Specifies the source IP address for FTP connections.
ip ftp username	Configures the username for FTP connections.

Syntax Description

username

Username for FTP connections.

Defaults

The Cisco IOS software attempts an anonymous FTP.

Command Modes

Global configuration

Command History

Release	Modification
10.3	This command was introduced.

Usage Guidelines

The remote username must be associated with an account on the destination server.

Examples

The following example configures the router to use the username red and the password blue for FTP connections:

ip ftp username red
ip ftp password blue

Related Commands

Command	Description
ip ftp passive	Configures the router to use only passive FTP connections.
ip ftp password	Specifies the password to be used for FTP connections.
ip ftp source-interface	Specifies the source IP address for FTP connections.

Syntax Description

ip-address

IP address that is to be provided in the source protocol address field of the RARP response packet. Normally, this is set to whatever address you configure as the primary address for the interface.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

This feature makes diskless booting of clients possible between network subnets where the client and server are on separate subnets.

RARP server support is configurable on a per interface basis, so that the router does not interfere with RARP traffic on subnets that do not need RARP assistance.

The Cisco IOS software answers incoming RARP requests only if both of the following two conditions are met:

• The ip rarp-server command has been configured for the interface on which the request was received.

• There is a static entry found in the IP ARP table that maps the MAC address contained in the RARP request to an IP address.

Sun Microsystems, Inc. makes use of RARP and UDP-based network services to facilitate network-based booting of SunOS on their workstations. By bridging RARP packets and using both the ip helper-address interface configuration command and the ip forward-protocol global configuration command, the Cisco IOS software should be able to perform the necessary packet switching to enable booting of Sun workstations across subnets. Unfortunately, some Sun workstations assume that the sender of the RARP response, in this case the router, is the host that the client can contact to TFTP load the bootstrap image. This causes the workstations to fail to boot.

By using the ip rarp-server command, the Cisco IOS software can be configured to answer these RARP requests, and the client machine should be able to reach its server by having its TFTP requests forwarded through the router that acts as the RARP server.

ip forward-protocol udp 111
interface interface name
ip helper-address target-address
 

Examples

The following partial example configures a router to act as a RARP server. The router is configured to use the primary address of the specified interface in its RARP responses.

arp 172.30.2.5 0800.2002.ff5b arpa
interface ethernet 0
ip address 172.30.3.100 255.255.255.0
ip rarp-server 172.30.3.100
 

In the following example, a router is configured to act as a RARP server, with TFTP and portmapper requests forwarded to the Sun server:

! Allow the router to forward broadcast portmapper requests
ip forward-protocol udp 111
! Provide the router with the IP address of the diskless sun
arp 172.30.2.5 0800.2002.ff5b arpa
interface ethernet 0
! Configure the router to act as a RARP server, using the Sun Server's IP
! address in the RARP response packet.
ip rarp-server 172.30.3.100
! Portmapper broadcasts from this interface are sent to the Sun Server.
ip helper-address 172.30.3.100

Related Commands

Command	Description
ip forward-protocol	Speeds up flooding of UDP datagrams using the spanning-tree algorithm.
ip helper-address	Forwards UDP broadcasts, including BOOTP, received on an interface.

Syntax Description

This command has no arguments or keywords.

Defaults

Enabled

Command Modes

Global configuration

Command History

Release	Modification
10.3	This command was introduced.

Usage Guidelines

If you do not want to use DNS for rcmd queries, but DNS has been enabled with the ip domain-lookup command, use the no ip rcmd domain-lookup command.

This command will turn off DNS lookups for rsh and rcp only. The no ip domain-lookup command takes precedence over the ip rcmd domain-lookup command. If the ip domain-lookup command is disabled with the no ip domain-lookup command, DNS will be bypassed for rcp and rsh, even if ip rcmd domain-lookup command is enabled.

Note Cisco IOS Release 10.3 added the ip keyword to rcmd commands. If you are upgrading from Release 10.2 to Release 10.3 or later, this keyword is automatically added to any rcmd commands you have in your Release 10.2 configuration files.

Examples

The following example enables DNS security is for rcp and rsh:

ip rcmd domain-lookup

Related Commands

Command	Description
ip domain-lookup	Enables the IP DNS-based host name-to-address translation.

Syntax Description

This command has no arguments or keywords.

Defaults

To ensure security, the router is not enabled for rcp by default.

Command Modes

Global configuration

Command History

Release	Modification
10.3	This command was introduced.

Usage Guidelines

To allow a remote user to execute rcp commands on the router, you must also create an entry for the remote user in the local authentication database.

The no ip rcmd rcp-enable command does not prohibit a local user from using rcp to copy system images and configuration files to and from the router.

To protect against unauthorized users copying the system image or configuration files, the router is not enabled for rcp by default.

Note Cisco IOS Release 10.3 added the ip keyword to rcmd commands. If you are upgrading from Release 10.2 to Release 10.3 or later, this keyword is automatically added to any rcmd commands you have in your Release 10.2 configuration files.

Examples

The following example shows how to enable the router for rcp:

rcp-enable

Related Commands

Command	Description
ip rcmd remote-host	Creates an entry for the remote user in a local authentication database so that remote users can execute commands on the router using rsh or rcp.

Syntax Description

local-username	Name of the user on the local router. You can specify the router host name as the username. This name needs to be communicated to the network administrator or the user on the remote system. To be allowed to remotely execute commands on the router, the remote user must specify this value correctly.
ip-address	IP address of the remote host from which the local router will accept remotely executed commands. Either the IP address or the host name is required.
host	Name of the remote host from which the local router will accept remotely executed commands. Either the host name or the IP address is required.
remote-username	Name of the user on the remote host from which the router will accept remotely executed commands.
enable level	(Optional) Enables the remote user to execute privileged EXEC commands using rsh or to copy files to the router using rcp. The range is 1 to 15. The default is 15. For information on the enable level, refer to the privilege level global configuration command in the Cisco IOS Security Command Reference.

Defaults

There are no entries in the local authentication database.

Command Modes

Global configuration

Command History

Release	Modification
10.3	This command was introduced.

Usage Guidelines

A TCP connection to a router is established using an IP address. Using the host name is valid only when you are initiating an rcp or rsh command from a local router. The host name is converted to an IP address using DNS or host-name aliasing.

To allow a remote user to execute rcp or rsh commands on a local router, you must create an entry for the remote user in the local authentication database. You must also enable the router to act as an rsh or rcp server.

ip rcmd remote-username netadmin1

Related Commands

Command	Description
boot network rcp	Changes the default name of the network configuration file from which to load configuration commands.
boot system rcp	Specifies the system image that the router loads at startup.
bridge acquire	Forwards any frames for stations that the system has learned about dynamically.
copy	Copies any file from a source to a destination.

Syntax Description

This command has no arguments or keywords.

Defaults

To ensure security, the router is not enabled for rsh by default.

Command Modes

Global configuration

Command History

Release	Modification
10.3	This command was introduced.

Usage Guidelines

Use this command to enable the router to receive rsh requests from remote users. In addition to issuing this command, you must create an entry for the remote user in the local authentication database to allow a remote user to execute rsh commands on the router.

The no ip rcmd rsh-enable command does not prohibit a local user of the router from executing a command on other routers and UNIX hosts on the network using rsh. It disables a router that is enabled for rsh.

Note Cisco IOS Release 10.3 added the ip keyword to rcmd commands. If you are upgrading from Release 10.2 to Release 10.3 or later, this keyword is automatically added to any rcmd commands you have in your Release 10.2 configuration files.

Examples

The following example enablse a router as an rsh server:

ip rcmd rsh-enable

Related Commands

Command	Description
ip rcmd remote-host	Creates an entry for the remote user in a local authentication database so that remote users can execute commands on the router using rsh or rcp.

Syntax Description

cisco	Denotes a Cisco device code.
ds200	Denotes a DECserver 200 device code.

Defaults

Cisco device code

Command Modes

Global configuration

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

The sysid messages and request program messages use the identity information indicated by this command.

Examples

The following example identifies a DECserver 200 device as sending MOP sysid and request program messages:

mop device-code ds200

Related Commands

Command	Description
mop sysid	Enables an interface to send out periodic MOP system identification messages.

Syntax Description

ip-address	IP address of the remote host on which to execute the rsh command. Either the IP address or the host name is required.
host	Name of the remote host on which to execute the command. Either the host name or the IP address is required.
/user username	(Optional) Remote username.
remote-command	Command to be executed remotely. This is a required parameter.

Defaults

If you do not specify the /user keyword and argument, the Cisco IOS software sends a default remote username. As the default value of the remote username, the software sends the username associated with the current TTY process, if that name is valid. For example, if the user is connected to the router through Telnet and the user was authenticated through the username command, then the software sends that username as the remote username. If the TTY username is invalid, the software uses the host name as the both the remote and local usernames.

Note For Cisco, TTY lines are commonly used for access services. The concept of TTY originated with UNIX. For UNIX systems, each physical device is represented in the file system. Terminals are called TTY devices (TTY stands for teletype, the original UNIX terminal).

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

For security reasons, the software does not default to a remote login if no command is specified, as does UNIX. Instead, the router provides Telnet and connect services that you can use rather than rsh.

Examples

Router1# rsh mysys.cisco.com /user sharon ls -a
.
..
.alias
.cshrc
.emacs
.exrc
.history
.login
.mailrc
.newsrc
.oldnewsrc
.rhosts
.twmrc
.xsession
jazz
 

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following is sample output from the show async-bootp command:

Router# show async-bootp
 
The following extended data will be sent in BOOTP responses:
 
bootfile (for address 192.168.1.1) "pcboot"
bootfile (for address 172.16.1.111) "dirtboot"
subnet-mask 255.255.0.0
time-offset -3600
time-server 192.168.1.1
 

Related Commands

Command	Description
async-bootp	Configures extended BOOTP requests for asynchronous interfaces as defined in RFC 1084.

Cisco 1600 series and Cisco 3600 series

tftp-server flash [device:][partition-number:]filename

no tftp-server flash [device:][partition-number:]filename

Cisco 7000 family

tftp-server flash device:filename

no tftp-server flash device:filename

Syntax Description

flash	Specifies TFTP service of a file in Flash memory.
rom	Specifies TFTP service of a file in ROM.
filename1	Name of a file in Flash or in ROM that the TFTP server uses in answering TFTP Read Requests.
alias	Specifies an alternate name for the file that the TFTP server uses in answering TFTP Read Requests.
filename2	Alternate name of the file that the TFTP server uses in answering TFTP Read Requests. A client of the TFTP server can use this alternate name in its Read Requests.
access-list-number	(Optional) Basic IP access-list number. Valid values are 0 to 99.
partition-number:	(Optional) Specifies TFTP service of a file in the specified partition of Flash memory. If the partition number is not specified, the file in the first partition is used. For the Cisco 1600 series and Cisco 3600 series, you must enter a colon (:) after the partition number if a filename follows it.
device:	(Optional) Specifies TFTP service of a file on a Flash memory device in the Cisco 1600 series, Cisco 3600 series and Cisco 7000 family. The colon (:) is required. Valid devices are as follows: flash---Internal Flash memory on the Cisco 1600 series and Cisco 3600 series. This is the only valid device for the Cisco 1600. bootflash---Internal Flash memory in the Cisco 7000 family. slot0---First PCMCIA slot on the Cisco 3600 series and Cisco 7000 family. slot1---Second PCMCIA slot on the Cisco 3600 series and Cisco 7000 family. slavebootflash---Internal Flash memory on the slave RSP card of a Cisco 7507 or Cisco 7513 configured for HSA. slaveslot0---First PCMCIA slot of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA. slaveslot1---Second PCMCIA slot of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA.
filename	Name of the file on a Flash memory device that the TFTP server uses in answering a TFTP Read Request. Use this argument only with the Cisco 1600 series, Cisco 3600 series, Cisco 7000 series or Cisco 7500 series.

Defaults

Disabled

Command Modes

Global configuration

Command History

Release	Modification
11.0	This command was introduced.

Usage Guidelines

You can specify multiple filenames by repeating the tftp-server command. The system sends a copy of the system image contained in ROM or one of the system images contained in Flash memory to any client that issues a TFTP Read Request with this filename.

If the specified filename1 or filename2 argument exists in Flash memory, a copy of the Flash image is sent. On systems that contain a complete image in ROM, the system sends the ROM image if the specified filename1 or filename2 argument is not found in Flash memory.

Images that run from ROM cannot be loaded over the network. Therefore, it does not make sense to use TFTP to offer the ROMs on these images.

On the Cisco 7000 family, the system sends a copy of the file contained on one of the Flash memory devices to any client that issues a TFTP Read Request with its filename.

Examples

In the following example, the system uses TFTP to send a copy of the version-10.3 file located in Flash memory in response to a TFTP Read Request for that file. The requesting host is checked against access list 22.

tftp-server flash version-10.3 22
 

In the following example, the system uses TFTP to send a copy of the ROM image gs3-k.101 in response to a TFTP Read Request for the gs3-k.101 file:

tftp-server rom alias gs3-k.101
 

In the following example, the system uses TFTP to send a copy of the version-11.0 file in response to a TFTP Read Request for that file. The file is located on the Flash memory card inserted in slot 0.

tftp-server flash slot0:version-11.0
 

The following example enables a Cisco 3600 series router to operate as a TFTP server. The source file c3640-i-mz is in the second partition of internal Flash memory.

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
router(config)# tftp-server flash flash:2:dirt/gate/c3640-i-mz
 

In the following example, the source file is in the second partition of the Flash memory PC card in slot 0 on a Cisco 3600 series:

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
router(config)# tftp-server flash slot0:2:dirt/gate/c3640-j-mz
 

The following example enables a Cisco 1600 series router to operate as a TFTP server. The source file c1600-i-mz is in the second partition of Flash memory:

router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
router(config)# tftp-server flash flash:2:dirt/gate/c1600-i-mz

Related Commands

Command	Description
access-list	Creates an extended access list.