CLI Reference Guide-R01

Chapter 1 | Initial Switch Configuration
Downloading a Configuration File and Other Parameters from a DHCP Server
– 66 –
If the switch receives information that allows it to download the remote bootup file,
it will save this file to a local buffer, and then restart the provision process.
Note the following DHCP client behavior:
◆ To enable dynamic provisioning via a DHCP server, this feature must be
enabled using the ip dhcp dynamic-provision or ipv6 dhcp dynamic-provision
command.
◆ The bootup configuration file received from a (TFTP or HTTP) server is stored on
the switch with the original file name. If this file name already exists in the
switch, the file is overwritten.
◆ If the name of the bootup configuration file is the same as the Factory Default
Configuration file, the download procedure will be terminated, and the switch
will not send any further DHCP client requests.
◆ If the switch fails to download the bootup configuration file based on
information passed by the DHCP server, it will not send any further DHCP client
requests.
◆ If the switch does not receive a DHCP response prior to completing the bootup
process, it will continue to send a DHCP client request once a minute. These
requests will only be terminated if the switch’s address is manually configured,
but will resume if the address mode is set back to DHCP.
To successfully transmit a bootup configuration file to the switch, the DHCP
daemon (using a Linux based system for this example) must be configured with the
following information:
◆ For IPv4 DHCP, options 60, 66 and 67 statements can be added to the daemon’s
configuration file.
Table 1: DHCP Options 60, 66 and 67 Statements
Option
Statement
Keyword Parameter
60 vendor-class-identifier a string indicating the vendor class identifier
66 tftp-server-name a string indicating the tftp server name
67 bootfile-name a string indicating the bootfile name