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

Brocade Mobility RFS Controller System Reference Guide 243
53-1003099-01
5
The evaluation is performed using various matching criteria. The matching criteria supported
include:
Auto Provisioning is the process to discover controllers or service platforms available in the
network, pick the most desirable controller or service platform, establish an association, optionally
obtain an image upgrade and obtain its configuration.
At adoption, an Access Point solicits and receives multiple adoption responses from controllers and
service platforms available on the network. These adoption responses contain loading policy
information the Access Point uses to select the optimum controller or service platform for adoption.
By default, an auto provisioning policy generally distributes AP adoption evenly amongst available
controller or service platform. Modify existing adoption policies or create a new one as needed to
meet the adoption requirements of a device and their assigned profile.
NOTE
A device configuration does not need to be present for an auto provisioning policy to take effect.
Once adopted, and the device’s configuration is defined and applied by the controller or service
platform, the auto provisioning policy mapping does not have impact on subsequent adoptions by
the same device.
An auto provisioning policy enables an administrator to define adoption rules for the supported
Brocade Access Points capable of adoption by a wireless controller.
Auto provisioning policies set the different restrictions on how an Access Point gets adopted to a
wireless controller.
To review existing Auto Provisioning Policy configurations:
MAC Matches the MAC address of a device attempting to be adopted. Either a single MAC address or a
range of MAC addresses can be specified.
VLAN Matches when adoption over a Layer 2 link matches the VLAN ID of an adoption request. Note that
this is a VLAN ID as seen by the recipient of the request, in case of multiple hops over different
VLANs this may different from VLAN ID set by the sender. A single VLAN ID is specified in the rule.
This rule is ignored for adoption attempts over Layer 3.
IP Address Matches when adoption is using a Layer 3 link matches the source IP address of an adoption
request. In case of NAT the IP address may be different from what the sender has used. A single IP,
IP range or IP/mask is specified in the rule. This rule is ignored for adoption attempts over Layer 2.
Serial Number Matches exact serial number (case insensitive).
Model Matches exact model name (case insensitive).
DHCP Option Matches the value found in DHCP vendor option 191 (case insensitive). DHCP vendor option 191
can be setup to communicate various configuration parameters to an AP. The value of the option in
a string in the form of tag=value separated by a semicolon,
e.g.’tag1=value1;tag2=value2;tag3=value3’. The access point includes the value of tag’rf-domain’,
if present. This value is matched against the auto provisioning policy.
FQDN Matches a substring to the FQDN of a device (case insensitive).
CDP Matches a substring in a list of CDP snoop strings (case insensitive). For example, if an access
point snooped 3 devices: controller1.moto.com, controller2.moto.com and
controller3.moto.com,’controller1’,’moto’, ’moto.com’, are examples of the substrings that will
match.
LLDP Matches a substring in a list of LLDP snoop strings (case insensitive). For example, if an Access
Point snooped 3 devices: controller1.moto.com, controller2.moto.com and
controller3.moto.com,’controller1’, ’moto’, ’moto.com’, are substrings match.