Specifications

Altitude 3500 Series Access Point Product Reference Guide
561
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,
MU locationing, hotspot on extended WLAN are some of the important wireless features not
supported in an AAP supported deployment.