Installation guide

B-8 Motorola RF Switch System Reference Guide
B.2 Supported Adaptive AP Topologies
The following AAP topologies are supported:
• Extended WLANs Only
• Independent WLANs Only
• Extended WLANs with Independent WLANs
• Extended VLAN with Mesh Networking
B.2.1 Topology Deployment Considerations
When reviewing the AAP topologies describes in the section, be cognizant of the following considerations
to optimize the effectiveness of the deployment:
• An AAP firmware upgrade will not be performed at the time of adoption from the wireless switch.
Instead, the firmware is upgraded using the AP-51x1’s firmware update procedure (manually or using the
DHCP Auto Update feature).
• An AAP can use its LAN1 interface or WAN interface for adoption. The default gateway interface is set
to LAN1. If the WAN Interface is used, explicitly configure WAN as the default gateway interface.
• Motorola recommends using the LAN1 interface for adoption in multi-cell deployments.
• If you have multiple independent WLANs mapped to different VLANs, the AAP's LAN1 interface requires
trunking be enabled with the correct management and native VLAN IDs configured. Additionally, the AAP
needs to be connected to a 802.1q trunk port on the wired switch.
• Be aware IPSec Mode supports NAT Traversal (NAT-T).
NOTE: If AAP Proxy Radius is configured, the onboard Radius server has to be enabled. By
default the onboard Radius server is disabled. To enable the onboard Radius server use
the Web UI or issue the “service radius” command in the CLI.