Adaptive ap deployment considerations – Brocade Mobility RFS7000-GR Controller System Reference Guide (Supporting software release 4.1.0.0-040GR and later) User Manual
Page 516

502
Brocade Mobility RFS7000-GR Controller System Reference Guide
53-1001944-01
Establishing basic Adaptive AP connectivity
A
Once an AAP is adopted by the switch, it displays within the switch Access Port Radios screen
(under the Network parent menu item) as a Brocade Mobility 7131N-FGR Access Point within
the AP Type
column.
Adaptive AP deployment considerations
Before deploying your switch/AAP configuration, refer to the following usage caveats to optimize its
effectiveness:
•
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 Layer 2/Layer 3 switch and appropriate
management and native VLANs are configured.
•
The WLAN used for mesh backhaul must always be an independent WLAN.
•
The switch configures an AAP. If manually changing wireless settings on the AP, they are not
updated on the switch. It's a one way configuration, from the switch to the AP.
•
An AAP always requires a router between the AP and the switch.
•
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, Layer 3 mobility, dynamic VLAN assignment, NAC, self healing, rogue
AP, MU locationing, hotspot on extended WLAN are some of the important wireless features not
supported in an AAP supported deployment.