Specifications

Adaptive AP
Altitude 3500 Series Access Point Product Reference Guide
556
Configuring the Controller for Adaptive AP Adoption
The tasks described below are configured on an Extreme Networks controller. For information on
configuring the controller for AAP support, see
http://www.extremenetworks.com/go/documentation.
To adopt an AAP on a controller:
1 Ensure enough licenses are available on the controller to adopt the required number of AAPs.
2 As soon as the AAP displays in the adopted list:
Adjust each AAP’s radio configuration as required. This includes WLAN-radio mappings and radio
parameters. WLAN-VLAN mappings and WLAN parameters are global and cannot be defined on a
per radio basis. WLANs can be assigned to a radio. Optionally, configure WLANs as independent
and assign to AAPs as needed.
3 Configure each VPN tunnel with the VLANs to be extended to it.
If you do not attach the target VLAN, no data will be forwarded to the AAP, only control traffic
required to adopt and configure the AP.
NOTE
For additional information (in greater detail) on the controller configuration activities described above, see
“Adopting an Adaptive AP Using a Configuration File” on page 558.
Establishing Basic Adaptive AP Connectivity
This section defines the activities required to configure basic AAP connectivity with a Summit WM3400,
Summit WM3600 or Summit WM3700 controller. In establishing a basic AAP connection, both the access
point and controller require modifications to their respective default configurations. For more
information, see:
Adaptive AP Configuration on page 556
Controller Configuration on page 558
NOTE
Refer to “Adaptive AP Deployment Considerations” on page 561 for usage and deployment caveats that
should be considered before defining the AAP configuration. Refer to “Sample Controller Configuration File for
IPSec and Independent WLAN” on page 562 if planning to deploy an AAP configuration using IPSec VPN and an
extended WLAN.
Adaptive AP Configuration
An AAP can be manually adopted by the controller, adopted using a configuration file (consisting of the
adaptive parameters) pushed to the access point or adopted using DHCP options. Each of these
adoption techniques is described in the sections that follow.