Securing A Configuration Channel Between Controller And Ap - Brocade Communications Systems RFS6000 System Reference Manual

A
Adaptive AP Overview
Manual Adoption Configuration
A manual controller adoption of an AAP can be conducted using:
•
•
NOTE
For a review of some important considerations impacting the use of extended and independent
WLANs within an AAP deployment, see
The WAN has no PoE support and has a default static AP address of 10.1.1.1/8.

Securing a Configuration Channel Between Controller and AP

Once an Access Point obtains a list of available controllers, it begins connecting to each. The
controller can be either on the LAN or WAN side of the Access Point to provide flexibility in the
deployment of the network. If the controller is on the Access Point's LAN, ensure the LAN subnet is
on a secure channel. The AP will connect to the controller and request a configuration.
Adaptive AP WLAN Topology
An AAP can be deployed in the following WLAN topologies:
•
526
Static FQDN - A controller fully qualified domain name can be specified to perform a DNS
lookup and controller discovery.
Static IP addresses - Up to 12 controller IP addresses can be manually specified in an ordered
list the AP can choose from. When providing a list, the AAP tries to adopt based on the order in
which they are listed (from 1-12).
Extended WLANs - Extended WLANs are centralized WLANs created on the controller
Adaptive AP Deployment Considerations.
Brocade Mobility RFS6000 and RFS7000 System Reference Guide
53-1001858-01