Руководство По Устранению Ошибки для Cisco Cisco 2000 Series Wireless LAN Controller
The AutoInstall feature can obtain the configuration file for the new controller automatically. When the
controller boots, the AutoInstall process starts with this prompt and stays for 30 seconds:
controller boots, the AutoInstall process starts with this prompt and stays for 30 seconds:
Would you like to terminate autoinstall? [yes]:
If you hit Enter or type 'yes', then AutoInstall ends. Or else after the 30−second abort timeout expires,
AutoInstall starts the DHCP client. You can abort the AutoInstall task even after this 30 second timeout if you
enter Yes at the prompt. However, AutoInstall cannot be aborted if the TFTP task has locked the flash and is
in the process of downloading and installing a valid configuration file.
AutoInstall starts the DHCP client. You can abort the AutoInstall task even after this 30 second timeout if you
enter Yes at the prompt. However, AutoInstall cannot be aborted if the TFTP task has locked the flash and is
in the process of downloading and installing a valid configuration file.
AutoInstall uses these interfaces:
4400 series controllers
eth0Service port (untagged)
♦
dtl0Gigabit port 1 through the NPU (untagged)
♦
•
2100 series controllers
dtl0FastEthernet port 1 (untagged)
♦
•
For the AutoInstall feature to work, the DHCP server should be configured to provide one of these options to
the WLC, along with the IP address and TFTP server information.
the WLC, along with the IP address and TFTP server information.
The filename that is provided by the DHCP Boot File Name option
•
The filename that is provided by the DHCP File field
•
host name−confg
•
host name.cfg
•
base MAC address−confg (for example, 0011.2233.4455−confg)
•
serial number−confg
•
ciscowlc−confg
•
ciscowlc.cfg
•
AutoInstall runs through this list until it finds a configuration file on the TFTP server. AutoInstall performs
three full download iterations on each interface that obtains a DHCP IP address. For example, if a 4400 series
controller obtains DHCP IP addresses on both eth0 and dtl0, each interface tries to download a configuration.
The first configuration file that is downloaded and installed successfully triggers a reboot of the controller.
For more information on the AutoInstall feature, refer to the WLC Configuration Guide 6.0.
three full download iterations on each interface that obtains a DHCP IP address. For example, if a 4400 series
controller obtains DHCP IP addresses on both eth0 and dtl0, each interface tries to download a configuration.
The first configuration file that is downloaded and installed successfully triggers a reboot of the controller.
For more information on the AutoInstall feature, refer to the WLC Configuration Guide 6.0.
Note: In this example, the DHCP Boot File Name option is used.
Note: The downloaded configuration file can be a complete configuration, or it can be a minimal
configuration that provides enough information for the controller to be managed by the WCS. Full
configuration can then be deployed directly from the WCS. WCS release 5.0 or later provides AutoInstall
capabilities for controllers. A WCS administrator can create a filter that includes the host name, the MAC
address, or the serial number of the controller and associate a group of templates (a configuration group) to
this filter rule. The WCS pushes the initial configuration to the controller when the controller boots up
initially. After the controller is discovered, the WCS pushes the templates that are defined in the configuration
group.
configuration that provides enough information for the controller to be managed by the WCS. Full
configuration can then be deployed directly from the WCS. WCS release 5.0 or later provides AutoInstall
capabilities for controllers. A WCS administrator can create a filter that includes the host name, the MAC
address, or the serial number of the controller and associate a group of templates (a configuration group) to
this filter rule. The WCS pushes the initial configuration to the controller when the controller boots up
initially. After the controller is discovered, the WCS pushes the templates that are defined in the configuration
group.
Note: The Cisco WiSM controllers do not support the AutoInstall feature.