Netgear M4200-10MG-PoE+ (GSM4210P) - Multigigabit Managed Switch with 8*2.5G and 2x10G SFP+ Layer 3 소프트웨어 가이드
Use the Auto Install Configuration
29
M4200 and M4300 Series ProSAFE Managed Switches Software Setup Manual
How to Terminate the Auto Install Process
You can terminate the Auto Install process at any time before downloading any configuration
files. Terminate the Auto Install process if the switch is disconnected from the network or if no
configuration files are configured on the TFTP server. Termination of the Auto Install process
ends further periodic requests for a host-specific file.
files. Terminate the Auto Install process if the switch is disconnected from the network or if no
configuration files are configured on the TFTP server. Termination of the Auto Install process
ends further periodic requests for a host-specific file.
About Managing the Downloaded Configuration Files
The configuration files downloaded through Auto Install are stored in nonvolatile memory.
The files can be managed (viewed, displayed, deleted) along with files downloaded through
the configuration scripting utility.
The files can be managed (viewed, displayed, deleted) along with files downloaded through
the configuration scripting utility.
A configuration file is not automatically deleted after it is downloaded. However, the
configuration file does not take effect upon a reboot. If you save the configuration file, the
saved configuration takes effect upon reboot. If you do not save the configuration file, the
saved configuration takes effect upon reboot. If you do not save the configuration file, the
Auto Install process occurs again on a subsequent reboot. A repeated install might cause
previously downloaded files to be overwritten.
About Restarting the Auto Install Process
If the configuration file is not found on the switch, the Auto Install process automatically starts
a subsequent reboot. A restart of the install process can occur if the configuration was never
saved on the switch or if you issued a command to erase the configuration file.
a subsequent reboot. A restart of the install process can occur if the configuration was never
saved on the switch or if you issued a command to erase the configuration file.
During a particular session, you can restart the Auto Install process if you previously stopped
it during the same login session. This action reinitiates the process for that login session only.
We recommend that you restart the install process only when you are certain that the
configuration is clear.
it during the same login session. This action reinitiates the process for that login session only.
We recommend that you restart the install process only when you are certain that the
configuration is clear.
If no configuration file is stored on the switch, reinitialization of the switch after you enter the
erase startup-config
erase startup-config
command automatically activates the Auto Install process.
Event Logging for the Auto Install Process
The switch logs a message for each of the following events:
•
The Auto Install component receives a configuration file name and other options upon
resolving an IP address through a DHCP client. The boot option values are logged.
resolving an IP address through a DHCP client. The boot option values are logged.
•
The Auto Install component initiates a TFTP request for a boot (configuration) file and
receives the file, or the request times out. File names and server IP addresses and host
names are logged.
receives the file, or the request times out. File names and server IP addresses and host
names are logged.
•
The Auto Install component initiates a request for a host name. The IP address and
resolved host name are logged.
resolved host name are logged.
•
The Auto Install component initiates a TFTP request for a hostname.cfg file and
receives the file, or the request times out. File names and server IP addresses and host
names are logged.
receives the file, or the request times out. File names and server IP addresses and host
names are logged.
•
The start of a configuration script is being applied.
•
The CLI scripting utility fails to apply a configuration file.