Brocade Mobility 5181 Access Point Product Reference Guide (Supporting software release 4.4.0.0) - Manual (Page 398)

384 Brocade Mobility 5181 Access Point Product Reference Guide
53-1002516-01
Supported adaptive AP topologies
10
• An AAP firmware upgrade will not be performed at the time of adoption from the wireless
controller. 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.
• Brocade 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 controller.
• Be aware IPSec Mode supports NAT Traversal (NAT-T).
Extended WLANs only
An extended WLAN configuration forces all Client traffic through the controller. No wireless traffic is
locally bridged by the AAP.
Each extended WLAN is mapped to the access point's virtual LAN2 subnet. By default, the access
point's LAN2 is not enabled and the default configuration is set to static with IP addresses defined
as all zeros. If the extended VLAN option is configured on the controller, the following configuration
updates are made automatically:
• The AAP’s LAN2 subnet becomes enabled
• All extended VLANs are mapped to LAN2.
NOTE
Clients on the same WLAN associated to the AAP can communicate locally at the AP Level without
going through the controller. If this scenario is undesirable, the access point's Client-to-Client
disallow option should be enabled. To enable the access point’s Client-to-Client disallow option, see
“Creating/editing individual WLANs” on page 107.
Independent WLANs only
An independent WLAN configuration forces all Client traffic be bridged locally by the AAP. No
wireless traffic is tunneled back to the controller. Each extended WLAN is mapped to the access
point's LAN1 interface. The only traffic between the controller and the AAP are control messages
(for example, heartbeats, statistics and configuration updates).
Extended WLANs with independent WLANs
An AAP can have both extended WLANs and independent WLANs operating in conjunction. When
used together, Client traffic from extended WLANs go back to the controller and traffic from
independent WLANs is bridged locally by the AP.
All local WLANs are mapped to LAN1, and all extended WLANs are mapped to LAN2.