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

382 Brocade Mobility 5181 Access Point Product Reference Guide
53-1002516-01
Adaptive AP overview
10
• Extended WLANs - Extended WLANs are the centralized WLANs created on the controller
• Independent WLANs - Independent WLANs are local to an AAP and can be configured from the
controller. You must specify a WLAN as independent to stop traffic from being forwarded to the
controller. Independent WLANs behave like WLANs on a standalone access point.
• Both - Extended and independent WLANs are configured from the controller and operate
simultaneously.
NOTE
For a review of some important considerations impacting the use of extended and independent
WLANs within an AAP deployment, see
“Adaptive AP deployment considerations” on page 389.
Configuration updates
An AAP receives its configuration from the controller initially as part of its adoption sequence.
Subsequent configuration changes on the controller are reflected on an AAP when applicable.
An AAP applies the configuration changes it receives from the controller after 30 seconds from the
last received controller configuration message. When the configuration is applied on the AAP, the
radios shutdown and re-initialize (this process takes less than 2 seconds) forcing associated
Clients to be deauthenticated. Clients are quickly able to associate.
Securing data tunnels between the controller and AAP
If a secure link (site-to-site VPN) from a remote site to the central location already exists, the AAP
does not require IPSec be configured for adoption.
For sites with no secure link to the central location, an AAP can be configured to use an IPSec
tunnel (with AES 256 encryption) for adoption. The tunnel configuration is automatic on the AAP
side and requires no manual VPN policy be configured. On the controller side, configuration
updates are required to adopt the AAP using an IPSec tunnel.
To review a sample AAP configuration, see “Sample controller configuration file for IPSec and
independent WLAN” on page 390.
Adaptive AP controller failure
In the event of a controller failure, an AAP's independent WLAN continues to operate without
disruption. The AAP attempts to connect to other controllers (if available) in background. Extended
WLANs are disabled once controller adoption is lost. When a new controller is discovered and a
connection is secured, an extended WLAN can be enabled.
If a new controller is located, the AAP synchronizes its configuration with the located controller once
adopted. If Remote Site Survivability (RSS) is disabled, the independent WLAN is also disabled in
the event of a controller failure.
Remote site survivability (RSS)
RSS can be used to turn off RF activity on an AAP if it loses adoption (connection) to the controller.