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

Brocade Mobility RFS Controller CLI Reference Guide 853
53-1003098-01
Chapter
9
AUTO-PROVISIONING-POLICY
This chapter summarizes the auto provisioning policy commands in the CLI command structure.
Wireless devices can adopt and manage other wireless devices. For example, a wireless controller
can adopt multiple access points. When a device is adopted, the device configuration is
provisioned by the adopting device. Since multiple configuration policies are supported, an
adopting device uses auto provisioning policies to determine which configuration policies are
applied to an adoptee based on its properties. For example, a configuration policy could be
assigned based on MAC address, IP address, CDP snoop strings, etc.
Auto provisioning or adoption is the process by which an access point discovers controllers in the
network, identifies the most desirable controller, associates with the identified controller, and
optionally obtains an image upgrade, obtains its configuration and considers itself provisioned.
At adoption, an access point solicits and receives multiple adoption responses from controllers
available on the network. These adoption responses contain loading policy information the access
point uses to select the optimum controller for adoption. An auto-provisioning policy maps a new AP
to a profile and RF Domain based on various parameters related to the AP and where it is
connected. By default a new AP will be mapped to the default profile and default RF Domain.
Modify existing
auto-provisioning policies or create a new one as needed to meet the configuration requirements of
a device.
An auto-provisioning policy enables an administrator to define rules for the supported Brocade
access points capable of being adopted by a controller. The policy determines which configuration
policies are applied to an adoptee based on its properties. For example, a configuration policy
could be assigned based on MAC address, IP address, CISCO Discovery Protocol (CDP) snoop
strings, etc. Once created an auto provisioning policy can be used in profiles or device configuration
objects. The policy contains a set of rules (ordered by precedence) that either deny or allow
adoption based on potential adoptee properties and a catch-all variable that determines if the
adoption should be allowed when none of the rules is matched. All rules (both deny and allow) are
evaluated sequentially starting with the rule with the lowest precedence. The evaluation stops as
soon as a rule has been matched, no attempt is made to find a better match further down in the
set.
For example,
rule #1 adopt br7131 10 profile default vlan 10
rule #2 adopt br650 20 profile default vlan 20
rule #3 adopt br7131 30 profile default serial-number
rule #4 adopt br7131 40 p d mac aa bb
Brocade Mobility 7131 Access Point L2 adoption, VLAN 10 - will use rule #1
Brocade Mobility 7131 Access Point L2 adoption, VLAN 20 - will not use rule #2 (wrong type), may
use rule #3 if the serial number matched, or rule #4
If aa<= MAC <= bb, or else default.
With the implementation of the hierarchically managed (HM) network, the auto-provisioning policy
has been modified to enable controllers to adopt other controllers in addition to access points.