Establishing basic adaptive ap connectivity – Brocade Mobility 5181 Access Point Product Reference Guide (Supporting software release 4.4.0.0) User Manual
Page 400

386
Brocade Mobility 5181 Access Point Product Reference Guide
53-1002516-01
Establishing basic adaptive AP connectivity
10
To avoid a lengthy broken connection with the controller, Brocade recommends generating an
SNMP trap when the AAP loses adoption with the controller.
NOTE
For additional information (in greater detail) on the AP configuration activities described above, see
Configuring the controller for adaptive AP adoption
The tasks described below are configured on a Mobility RFS6000 Controller or a Mobility RFS7000
Controller. For information on configuring the controller for AAP support, see
http://www.brocade.com
.
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 as done today for a Mobility
300 model access point. 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
Establishing basic adaptive AP connectivity
This section defines the activities required to configure basic AAP connectivity with a Mobility
RFS6000 Controller or a Mobility RFS7000 Controller. In establishing a basic AAP connection, both
the access point and controller require modifications to their respective default configurations. For
more information, see:
•
•
NOTE
Refer to
“Adaptive AP deployment considerations”
on page 389 for usage and deployment caveats
that should be considered before defining the AAP configuration. Refer to
configuration file for IPSec and independent WLAN”
on page 390 if planning to deploy an AAP
configuration using IPSec VPN and an extended WLAN.