2. Configure IP so that the device can reach each host with the archived
configuration. The
Protocol Configuration and Monitoring Reference
explains
the IP configuration commands.
v The source IP address for TFTP transfers is the device ID. This ID, by default, is
a configured IP address for one of the device’s network interfaces. To change the
router ID, use the set router ID command at the IP Config> prompt.
v All TFTP data transfers are 512 bytes long. A data transfer of less than 512 bytes
indicates an end to the transfer. A protocol, client, or remote host error generates
an error packet which terminates the transfer.
v Download configuration files into the same type of router from which you are
uploading the file.
Note: This implementation of TFTP does not allow you to
copy
to other routers.
Every TFTP transfer has a client and server UDP port number. When a client node
generates an initial request to the server, an unused UDP port number on the client
node is randomly selected as the client port. The server port is the UDP port
number 69 (decimal). If a TFTP server is running on the server, it listens on UDP
port 69. When the server receives a request from the network, a UDP port number
currently unused on the server is randomly selected as the host port. The file
transfers then occur on these two UDP ports.
Accessing Configuration Files From a Remote Host or Router
To access configuration files from a remote host or router:
1. At the Boot config> prompt, type copy and press Enter.
2. At the source filename [CONFIG]? prompt, specify the remote IP address and
the pathname.
This is the TFTP host or another router with the file in its IBD.
3. At the destination filename [Config]? prompt, press Enter.
By pressing Enter you are accepting the default filename, CONFIG. For
example:
Boot config>copy
source filename[CONFIG]?128.185.210.125:loads/configs/vl-28.cfg
destination filename [CONFIG]?
COPYing from "128.185.210.125:loads/configs/vl-28.cfg" to
"CONFIG"
COPY succeeded
Filename Definitions for IBD
Each file or
image
stored on the IBD must have a unique
loadname
associated with
it. The file name for the IBD can contain the complete path name in addition to the
file name.
Example 1: test.cfg
Example 2: /usr/loads/test.ldc
The following example shows how to store a file to the IBD at the Boot config>
prompt:
Example: copy 128.185.210.125:/usr/config/test.cfg ibd/test.cfg
Using the Boot CONFIG Process
Chapter 7. The Boot CONFIG Process 87