User's Guide

The Auto-Connect feature is specifically designed to get un-configured APs into AirDefense as Sensors.
After a successful DNS lookup, the un-configured AP attaches to AirDefense. AirDefense must then
have the correct RF-domain setting for the final placement location of the newly added AP and a
Sensor-only policy configured before it will automatically re-configure the AP device to work as a
Sensor.
There are three conditions that must be met before auto-connection will start:
• The AP must have the default password set
• The AP must have the radio set to the default setting
•
The AP can not be adopted to any controller.
If these conditions are met, Auto-Connect will start a DNS lookup for airdefense1 or airdefense2 after
five minutes from booting up into a running state. It goes with out saying that for this feature to work
the network that the AP is connected to must have DHCP and a DNS server with at least the airdefense1
name configured.
Zero Touch WLAN Infrastructure Deployment
Zero Touch configuration enables taking WLAN infrastructure products directly out of the box and
plugging it into the network for operational use.
By coordination with the management platform, the infrastructure is able to automatically receive the
configuration needed to allow it to be used for operational needs. This process eliminates the need for
any manual configuration or staging and thereby greatly simplifying deployments of WLAN
infrastructure for client access and sensors. Zero Touch works through a simple 3 step process.
1. Infrastructure boots and sends a trap to AirDefense to notify it that a new device is available on the
network.
2. AirDefense receives the trap and recognizes that the trap is from an unknown device. AirDefense will
perform a single device discovery to import the newly added device into the management platform.
3. Once placed in the management tree hierarchy at the appropriate location, the system automatically
pushes a configuration template to the new device setting the appropriate configuration for that
device. Once the device imports the configuration, it is now fully up and operational without any
manual staging or configuration.
Deployment Requirements
The following deployment requirements must be met:
• ADSP 8.1.2 or newer
◦ WLAN infrastructure management licenses are required to enable this feature
• WLAN infrastructure running WiNG 5.2 or later
• Network with DHCP enabled
• DNS entry for the host AirDefense1 in the domain of the DHCP scope the WLAN device will be
initially attached to
◦ This solution does support DNS devolution
• Network which is able to route trac and permit the following flows:
◦ SNMP traps (UDP port 162) trac from the infrastructure to the AirDefense appliance
◦ SNMP query trac (UDP port 161) between AirDefense and the infrastructure
◦ SSH application trac between the AirDefense appliance and the infrastructure
Configuration
Tab
Automatic Configuration of WLAN Infrastructure
Devices
Extreme AirDefense User Guide for version 10.5. 721