Application Notes - How to Configure Auto-install on Managed Switches
Restarting the Auto Install Process
The Auto Install process is automatically started on a subsequent reboot if the configuration file is not found on the switch.
This can occur if configuration has not ever been saved on the switch, or if the administrator has issued a command to
erase the configuration file.
During a particular session, the Auto Install process can be restarted if the administrator has previously stopped the Auto
Install process, and then chooses to restart it. This action re-initiates the process for this login session only. NETGEAR
recommends that this action be performed only when the administrator is certain that configuration is clear in order to
have predictable results.
Reinitialization of the switch after a clear config automatically activates the Auto Install process if there is no configuration
file stored on the switch.
Logging
A message is logged for each of the following events:
• The Auto Install component receiving a config file name and other options upon resolving an IP address by
DHCP or BOOTP client. The boot option values are logged.
• The Auto Install component initiating a TFTP request for a boot (config) file, receiving the file, or timing out of
that request. File names and server IP addresses and host names are logged.
• The Auto Install component initiating a request for a host name. The IP address and resolved hostname are logged.
• The Auto Install component initiating a TFTP request for a <hostname>.cfg file, receiving the file, or timing out
of that request. File names and server IP addresses and host names are logged.
• The beginning of applying a config script.
• The failure of the CLI scripting utility to apply a config file.
• The completion of AutoInstall.
• A conflict in the name of a config file to be downloaded with a reserved config file name.
Auto Install Configuration
Stacking
The downloaded configuration file is not distributed across a stack. When an administrator saves configuration, the config
file is distributed across a stack.
Figure 1. Configuration File Distrubuted across a Stack
6
Application Notes
192.168.0.1
192.168.0.2
192.168.0.3
DHCP
server
TFTP
server