Extended wlans only, Independent wlans only, Extended wlans with independent wlans – Brocade Mobility RFS7000-GR Controller System Reference Guide (Supporting software release 4.1.0.0-040GR and later) User Manual
Page 509: Extended vlan with mesh networking, How the ap receives its adaptive configuration

Brocade Mobility RFS7000-GR Controller System Reference Guide
495
53-1001944-01
How the AP receives its adaptive configuration
A
Extended WLANs only
An extended WLAN configuration forces all MU traffic through the switch. 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 switch, the following configuration
updates are made automatically:
•
The AAP’s LAN2 subnet becomes enabled
•
All extended VLANs are mapped to LAN2.
NOTE
MUs on the same WLAN associated to the AAP can communicate locally at the AP Level without
going through the switch. If this scenario is undesirable, the Access Point's MU-to-MU disallow option
should be enabled.
Independent WLANs only
An independent WLAN configuration forces all MU traffic be bridged locally by the AAP. No wireless
traffic is tunneled back to the switch. Each extended WLAN is mapped to the Access Point's LAN1
interface. The only traffic between the switch 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, MU traffic from extended WLANs go back to the switch 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 switch 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 switch. 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 switch. There is no separate file-based configuration stored on the switch.