Application Notes - How to Configure Auto-install on Managed Switches

The following table displays the determining factors for issuing unicast TFTP requests.
Monitoring and Completing the Auto Install Process
Upon boot-up in the absence of a saved config file, a message displays on the console stating that the Auto Install
procedure is beginning. A message subsequently displays when Auto Install is complete. The message also indicates that
configuration must be saved to avoid performing Auto Install on the next reboot.
When Auto Install has been successfully completed, the messages are in buffered log, not on the console. You can execute
a show running-config command to validate the contents of configuration. You must be logged in as administrator.
Saving Configuration
An administrator must explicitly save the downloaded configuration in nonvolatile memory so that the configuration will
be available on the next reboot. If you are using the CLI, first make sure the configuration is correct, then issue a copy
running-config startup-config command.
Host-Specific Config File Not Found
If the Auto Install process fails to download any configuration file, a message is logged. If a “final” configuration file is
not downloaded, as described above, the entire process continues every 10 minutes.
Terminating the Auto Install Process
You can terminate the Auto Install process at any time prior to the downloading of the config file. This is most optimally
done when the switch is disconnected from the network, or if the requisite configuration files have not been configured on
TFTP servers. Termination of the Auto Install process ends further periodic requests for a host-specific file.
Managing Downloaded Config Files
The configuration files downloaded through Auto Install are stored in the nonvolatile memory. The files can be managed
(viewed, displayed, deleted) along with files downloaded through the configuration scripting utility. A file is not automatically
deleted after it is downloaded. However, the file does not take effect upon a reboot. If you opt to save the config file, the
saved configuration takes effect upon reboot. If you do not opt to save the config file, the Auto Install process occurs
again on a subsequent reboot. This might result in a previously downloaded files being overwritten.
5
Application Notes
Order
Sought
File Name Description Final File
Sought
1
<bootfile>.cfg
Host-specific config file, ending in a *.cfg file
extension
Yes
2
fp-net.cfg
Default network config file No
3
<hostname>.cfg
Host-specific config file, associated with
host name
Yes
4
host.cfg
seYelif gifnoc tluafeD
TFTP Server
Address
Available
Host-Specific Router
Config File Name
Available
TFTP Request Method
gifnoc retuor cificeps-tsoh eht rof tseuqer tsacinu a eussIseYseY
file to the TFTP server.
retuor ro krowten tluafed a rof tseuqer tsacinu a eussIoNseY
config file to the TFTP server.