Configuring Additional File Transfer Functions
Configuring a Router as a Server
Caution For full functionality, the software image sent to the client must be the same type as the ROM software installed on the client router. For example, if the server has X.25 software, and the client does not have X.25 software in ROM, the client will not have X.25 capabilities after booting from the server’s image in Flash memory.
Configuring the Server
To specify TFTP server operation, use the following commands in configuration mode:
| Command | Purpose |
Step 1 |
|
|
configure terminal | Enters global configuration mode from the terminal. | |
Step 2 |
|
|
Specifies the system image to send in response to | ||
| [alias filename2] | Read Requests. You can enter multiple lines to |
| or | specify multiple images. |
|
| |
|
| |
| only) |
|
| or |
|
|
|
|
|
|
|
| (Cisco 1600 series and Cisco 3600 series only) |
|
| or |
|
|
| |
Step 3 |
|
|
end | Exits configuration mode. | |
Step 4 |
|
|
copy | Saves the configuration file to your startup | |
|
| configuration. |
|
|
|
The TFTP session can sometimes fail. TFTP generates the following special characters to help you determine why a TFTP session fails:
•An “E” character indicates that the TFTP server received an erroneous packet.
•An “O” character indicates that the TFTP server received an
•A period (.) indicates a timeout.
For diagnosing any undue delay in the transfer, the output is useful. For troubleshooting procedures, refer to the Internetwork Troubleshooting Guide publication.
In the following example, the system can use TFTP to send copies of the Flash memory file
In the following example, the system can use TFTP to send a copy of the ROM image
Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.1