Extended wlan with mesh networking, How the ap receives its adaptive configuration – Brocade Mobility 5181 Access Point Product Reference Guide (Supporting software release 4.4.0.0) User Manual
Page 399
Brocade Mobility 5181 Access Point Product Reference Guide
385
53-1002516-01
How the AP receives its adaptive configuration
10
Extended WLAN with mesh networking
Mesh networking is an extension of the existing wired network. There is no special configuration
required, with the exceptions of setting the mesh and using it within one of the two extended VLAN
configurations and defining an access point radio as a preferred base bridge.
NOTE
The mesh backhaul WLAN must be an independent WLAN mapped to LAN1. 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.
Only WLAN, VLAN extension and radio configuration items are defined for the AAP by its connected
controller. None of the other access point configuration items (RADIUS, DHCP, NAT, Firewall etc.)
are configurable from the connected controller.
After the AP downloads a configuration file from the controller, it obtains the version number of the
image it should be running. The controller does not have the capacity to hold the access point’s
firmware image and configuration. The access point image must be downloaded using a means
outside the controller. If there is still an image version mismatch between what the controller
expects and what the AAP is running, the controller will deny adoption.
Adaptive AP pre-requisites
Converting a Product Name model access point into an AAP requires:
•
A version 2.3.2.0 or higher firmware running on the access point.
•
A Brocade Mobility RFS6000 Controller or a Mobility RFS7000 Controller.
•
The appropriate controller licenses providing AAP functionality on the controller.
•
The correct password to authenticate and connect the adaptive to the controller.
Configuring the adaptive AP for adoption by the controller
1. An AAP needs to find and connect to the controller. To ensure this connection:
•
Configure the controller’s IP address on the AAP
•
Provide the controller IP address using DHCP option 189 on a DHCP server. The IP address
is a comma delimited string of IP addresses. For example "157.235.94.91, 10.10.10.19".
There can be a maximum of 12 IP addresses.
•
Configure the controller’s FQDN on the AAP. The AAP can use this to resolve the IP address
of the controller.
2. Use the controller’s secret password on the AAP for the controller to authenticate it.
For additional information on defining the connection medium used by the access point t to
receive an AAP configuration, see