|
|
This chapter describes the function and displays the syntax for additional file transfer function commands. For more information about defaults and usage guidelines, see the corresponding chapter of the Configuration Fundamentals Command Reference.
To configure extended BOOTP requests for asynchronous interfaces as defined in RFC 1084, use the async-bootp global configuration command. Use the no form of this command to restore the default.
async-bootp tag [:hostname] data| tag | Item being requested; expressed as filename, integer, or IP dotted-decimal address. |
| :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. |
Use the ip rarp-server interface configuration command to enable the router to act as a Reverse Address Resolution Protocol (RARP) server. Use the no form of this command to restore the interface to the default of no RARP server support.
ip rarp-server ip-address| 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. |
Use the ip rcmd domain-lookup global configuration command to enable Domain Name System (DNS) security for rcp and rsh. To bypass DNS security for rcp and rsh, use the no form of this command.
ip rcmd domain-lookupTo configure the Cisco IOS software to allow remote users to copy files to and from the router, use the ip rcmd rcp-enable global configuration command. Use the no form of this command to disable a router that is enabled for rcp.
ip rcmd rcp-enableTo create 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, use the ip rcmd remote-host global configuration command. Use the no form of this command to remove an entry for a remote user from the local authentication database.
ip rcmd remote-host local-username {ip-address | host} remote-username [enable [level]]| 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 Security Command Reference. |
To configure the remote username to be used when requesting a remote copy using rcp, use the ip rcmd remote-username global configuration command. To remove from the configuration the remote username, use the no form of this command.
ip rcmd remote-username username| username | Name of the remote user on the server. This name is used for rcp copy requests. All files and images to be copied are searched for or written relative to the directory of the remote user's account, if the server has a directory structure, for example, as do UNIX systems. |
To configure the router to allow remote users to execute commands on it using rsh, use the ip rcmd rsh-enable global configuration command. Use the no form of this command to disable a router that is enabled for rsh.
ip rcmd rsh-enableTo identify the type of device sending MOP sysid messages and request program messages, use the mop device-code global configuration command. Use the no form of this command to set the identity to the default value.
mop device-code {cisco | ds200}| cisco | Denotes a Cisco device code. |
| ds200 | Denotes a DECserver 200 device code. |
To configure the length of time that the Cisco IOS software waits before retransmitting boot requests to a MOP server, use the mop retransmit-timer global configuration command. Use the no form of this command to reinstate the default value.
mop retransmit-timer seconds| seconds | Sets the length of time, in seconds, that the software waits before retransmitting a message. The value is a number from 1 to 20. |
To configure the number of times the Cisco IOS software will retransmit boot requests to a MOP server, use the mop retries global configuration command. Use the no form of this command to reinstate the default value.
mop retries count| count | Indicates the number of times the software will retransmit a MOP boot request. The value is a number from 3 to 24. |
To execute a command remotely on a remote rsh host, use the rsh privileged EXEC command.
rsh {ip-address | host} [/user username] remote-command| 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. |
To display the extended BOOTP request parameters that have been configured for asynchronous interfaces, use the show async-bootp privileged EXEC command.
show async-bootpTo configure a router or a Flash memory device on the router as a TFTP server, use one of the following tftp-server global configuration commands. This command replaces the tftp-server system command. To remove a previously defined filename, use the no tftp-server command with the appropriate filename.
tftp-server flash [partition-number:]filename1 [alias filename2] [access-list-number] (all others)| 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: | 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. |
|
|