Motorola WiNG 4.4, Reference Manual, Page: 553 / 598

B - 21
Once an AAP is adopted by the switch, it displays within the switch Access Port Radios screen (under the Network
parent menu item) as an AP-5131, AP-5181 or AP-7131 within the AP Type column.
B.4.3 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, NAC, and self healing are some of the important wireless features not
supported in an AAP supported deployment.
B.4.4 Sample Switch Configuration File for IPSec and Independent WLAN
The following constitutes a sample switch configuration file supporting an AAP IPSec with Independent WLAN
configuration. Please note new AAP specific CLI commands in
red and relevant comments in blue .
The sample output is as follows:
!
! configuration of RFS6000