Extended Wlans Only - Brocade Communications Systems RFS6000 System Reference Manual

A
How the AP Receives its Adaptive Configuration

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:
•
•
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.
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.
Extended VLAN with Mesh Networking
Mesh networking is an extension of the existing wired network. There is no special configuration
required, with the exception of setting the mesh and using it within one of the two extended VLAN
configurations.
NOTE
The mesh backhaul WLAN must be an independent WLAN mapped to LAN2. The controller enforces
the WLAN be defined as an independent WLAN by automatically setting the WLAN to independent
when backhaul is selected. The AP ensures the backhaul WLAN be put on LAN1.
How the AP Receives its Adaptive Configuration
An AAP does not require a separate "local" or "running" configuration. Once enabled as an AAP, the
AP obtains its configuration from the controller. If the AP's WAN link fails, it continues to operate
using the last valid configuration until its link is re-established and a new configuration is pushed
down from the controller. There is no separate file-based configuration stored on the controller.
532
The AAP's LAN2 subnet becomes enabled
All extended VLANs are mapped to LAN2.
Brocade Mobility RFS6000 and RFS7000 System Reference Guide
53-1001858-01