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

388 Brocade Mobility 5181 Access Point Product Reference Guide
53-1002516-01
Establishing basic adaptive AP connectivity
10
Either import the configuration manually to other APs or the same AP later (if you elect to
default its configuration). Use DHCP option 186 and 187 to force a download of the
configuration file during startup (when it receives a DHCP offer).
For instruction on how to use the access point’s configuration import/export functionality, see
“Importing/exporting configurations” on page 81.
For information on updating the access point’s firmware, see
“Updating device firmware” on page 86.
Adopting an adaptive AP using DHCP options
An AAP can be adopted to a wireless controller by providing the following options in the DHCP Offer:
NOTE
Options 189 and 192 are mandatory to trigger adoption using DHCP options. Unlike a Mobility 300,
option 189 alone won’t work. These options can be embedded in Vendor Specific Option 43 and
sent in the DHCP Offer.
Controller configuration
A Mobility RFS6000 Controller and a Mobility RFS7000 Controller require an explicit adaptive
configuration to adopt an access point (if IPSec is not used for adoption). The same licenses
currently used for Mobility 300 adoption can be used for an AAP.
Disable the controller’s Adopt unconfigured radios automatically option and manually add AAPs
requiring adoption, or leave as default. In default mode, any AAP adoption request is honored until
the current controller license limit is reached.
To disable automatic adoption on the controller:
1. Select Network > Access Point Radios from the controller main menu tree.
2. Select the Configuration tab (should be displayed be default) and click the Global Settings
button.
3. Ensure the Adopt unconfigured radios automatically option is NOT selected.
When disabled, there is no automatic adoption of non-configured radios on the network.
Additionally, default radio settings will NOT be applied to access points when automatically
adopted.
NOTE
For IPSec deployments, refer to “Sample controller configuration file for IPSec and
independent WLAN” on page 390 and take note of the CLI commands in red and associated
comments in green.
Option Data Type Value
189 String <Controller IP Address or Range of IP addresses separated by [, ; <space>]>
190 String <Fully qualified Domain Name for the Wireless Controller>
191 String <Hashed IPSec Passkey - configure on 1 AP and export to get hashed key>
192 String <Value of "1" denotes Non-IPSec Mode and "2" denotes IPSec Mode>