Wireless devices can adopt and manage other wireless devices. For example, a wireless controller can adopt any number of 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 needs to define which configuration policies are used for a given adoptee. Auto-provisioning policies determine which configuration policies are applied to an adoptee based its properties. For example, a configuration policy could be assigned based on MAC address, IP address, CDP snoop strings, etc.
Once created an auto-provisioning policy can be used in profiles or device configuration objects. An Auto-Provisioning policy contains a set of ordered by precedence rules 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.
| Setting | Description |
|---|---|
| Auto-Provisioning Policy | Lists the name of each policy when it was created. It cannot be modified as part of the Auto-provisioning policy‘s edit process |
| Adopt if no Rules Match | Displays whether this policy will adopt devices if no adoption rules apply. The result is displayed as a green checkmark. This feature is not activated by default |
| Rerun Policy Rules Every Time AP Adopts | Displays whether this policy will be run every time an AP is adopted. The result is displayed as a green checkmark. This feature is not activated by default |
| Action | Edit or delete an existing auto-provisioning policy |