Brocade Mobility RFS Controller System Reference Guide (Supporting software release 5.5.0.0 and later) - Manual (Page 55)

Brocade Mobility RFS Controller System Reference Guide 43
53-1003099-01
Chapter
5
Device Configuration
Managed devices can either be assigned unique configurations or have existing RF Domain or
Profile configurations modified (overridden) to support a requirement that dictates a device’s
configuration be customized from the configuration shared by its profiled peer devices.
When a device is initially managed by the controller or service platform, it requires several basic
configuration parameters be set (system name, deployment location etc.). Additionally, the number
of permitted device licenses (purchased directly from Brocade) needs to be accessed to determine
whether a new Access Point can be adopted.
Refer to the following to set a device’s basic configuration, license and certificate usage:
• Basic Configuration
• Basic Device Configuration
• License Configuration
• Assigning Certificates
RF Domains allow administrators to assign configuration data to multiple devices deployed in a
common coverage area (floor, building or site). In such instances, there’s many configuration
attributes these devices share as their general client support roles are quite similar. However,
device configurations may need periodic refinement (overrides) from their original RF Domain
administered design. For more information, see
RF Domain Overrides .
Profiles enable administrators to assign a common set of configuration parameters and policies to
controller or service platforms and Access Points. Profiles can be used to assign shared or unique
network, wireless and security parameters to wireless controllers and Access Points across a large,
multi segment, site. The configuration parameters within a profile are based on the hardware
model the profile was created to support. The controller and service platform supports both default
and user defined profiles implementing new features or updating existing parameters to groups of
controllers, service platforms or Access Points.
However, device profile configurations may need periodic refinement from their original
administered configuration. Consequently, a device profile could be applied an override from the
configuration shared amongst numerous peer devices deployed within a particular site. For more
information, see
Profile Overrides .
Adoption is the process an Access Point uses to discover controller or service platforms available in
the network, pick the most desirable, establish an association, obtain its configuration and
consider itself provisioned.
At adoption, an Access Point solicits and receives multiple adoption responses from available
controllers or service platforms on the network. Modify existing adoption policies or create a new
one as needed to meet the adoption requirements of a device and its assigned profile. For more
information, see
Auto Provisioning Policies .