Brocade Mobility 5181 Access Point Product Reference Guide (Supporting software release 4.4.0.0) - Manual (Page 403)

Brocade Mobility 5181 Access Point Product Reference Guide 389
53-1002516-01
Establishing basic adaptive AP connectivity
10
Any WLAN configured on the controller becomes an extended WLAN by default for an AAP.
4. Select Network > Wireless LANs from the controller main menu tree.
5. Select the target WLAN you would like to use for AAP support from those displayed and click
the Edit button.
6. Select the Independent Mode (AAP Only) checkbox.
Selecting the checkbox designates the WLAN as independent and prevents traffic from being
forwarded to the controller. Independent WLANs behave like WLANs as used on a a standalone
access point. Leave this option unselected (as is by default) to keep this WLAN an extended
WLAN (a typical centralized WLAN created on the controller).
NOTE
Additionally, a WLAN can be defined as independent using the "wlan <index> independent"
command from the config-wireless context.
Once an AAP is adopted by the controller, it displays within the controller Access Point Radios
screen (under the Network parent menu item) as a Product Name within the AP Type
column.
Adaptive AP deployment considerations
Before deploying your controller/AAP configuration, refer to the following usage caveats to optimize
its effectiveness:
• If deploying the access point as an AAP with a remote layer 3 configuration and the AAP is set
for controller auto discovery (primary/standby), the access point will un-adopt from its
controller after a few moments. To remedy this problem, ensure LAN1 has 802.1q trunking
enabled and the correct management VLAN defined.
• Extended WLANs are mapped to the AP’s LAN2 interface and all independent WLANs are
mapped to the AP’s LAN1 Interface.
• If deploying multiple independent WLANs mapped to different VLANs, ensure the AP’s LAN1
interface is connected to a trunk port on the L2/L3 controller and appropriate management
and native VLANs are configured.
• The WLAN used for mesh backhaul must always be an independent WLAN.
• The controller configures an AAP. If manually changing wireless settings on the AP, they are not
updated on the controller. It's a one way configuration, from the controller to the AP.
• An AAP always requires a router between the AP and the controller.
• An AAP can be used behind a NAT.
• An AAP uses UDP port 24576 for control frames and UDP port 24577 for data frames.
• Multiple VLANs per WLAN, L3 mobility, dynamic VLAN assignment, NAC, self healing, rogue AP,
Client locationing, hotspot on extended WLAN are some of the important wireless features not
supported in an AAP supported deployment.