134
Configuration file acquisition process
The device requests a configuration file from an HTTP server or a TFTP server:
• If the device got a configuration file name during the automatic-configuration parameter acquisition
process, the device examines the form of the configuration file name. If the configuration file name
is a valid HTTP URL, the device tries to download the configuration file from the URL. See Figure 42.
• If the de
vice did not get a configuration file name during the automatic-configuration parameter
acquisition process, or if the device got a configuration file name that is not in the form of a valid
HTTP URL, the device starts to acquire a configuration file from a TFTP server:
{ If the device has got a TFTP server IP address, it unicasts a request to the TFTP server.
{ If not, the device broadcasts a request. In this case, the device resolves only the first reply.
As shown in Figure 44, the
device determines what to request from the TFTP server based on
whether or not it got a configuration file name during the automatic-configuration parameter
acquisition process:
{ If the device got a configuration file name, it requests the specified configuration file.
{ If not, it requests a configuration file named in the format host name.cfg from the TFTP server,
where host name represents the host name of the device. To do so, the device first requests the
host name file network.cfg, which contains mappings between IP addresses and host names. If
the device fails to get the host name file or the file contains no entry for the device's temporary
IP address, it tries to communicate with a DNS server to resolve the temporary IP address to a
host name. After the device gets the host name, it tries to obtain the configuration file for the host
name.
If the device fails to get a configuration file specific for itself, it requests the default configuration
file device.cfg from the TFTP server.
To Next Page
Loading...
Need help?
General
