Adaptive Ap Deployment Considerations - Motorola AP-51 Series Product Reference Manual

10.4.3 Adaptive AP Deployment Considerations

Before deploying your switch/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 switch auto discovery (primary/standby), the access point will un-adopt from its
switch 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 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.
Adaptive AP 10-19