Brocade Mobility 7131N-FGR Access Point Product Reference Guide (Supporting software release 4.0.0.0-35GRN and later) - Manual (Page 569)

Brocade Mobility 7131N-FGR Product Reference Guide 557
53-1001947-01
Establishing basic adaptive AP connectivity
10
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 L2/L3 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, L3 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.
Sample switch configuration file for IPSec and independent WLAN
The following constitutes a sample Brocade Mobility RFS7000 Controller configuration file
supporting an AAP IPSec with Independent WLAN configuration. Please note new AAP specific CLI
commands in
red and relevant comments in blue .