User defined profiles can be customized and assigned or automatically assigned to access points using an AP Auto-Provisioning policy. User defined profiles should be utilized in larger deployments when groups of devices (on different floors, buildings or sites) share a common configuration. Each default and user defined profile contains policies and configuration parameters. Changes made to these parameters are automatically inherited by the devices assigned to the profile.
Configure profile policies parameters:
| Field | Description |
|---|---|
| Management Policy | Lists the name of Management policies applied to each listed profile. A management policy is a mechanism to allow or deny management access for separate interfaces and protocols (HTTP, HTTPS, Telnet, SSH or SNMP). Management access can be enabled or turned off as required for each policy |
| Firewall Policy | Displays an existing firewall policy, if any, assigned to each listed profile. Firewall policies can be assigned when creating or editing a profile |
| RADIUS Server Policy | Displays the name of the RADIUS Server policy applied to
each listed profile. A RADIUS Server policy provides
customized, profile specific, management of authentication
data such as username and password. This setting is not selected by default |
| Event System Policy | Displays the name of the Event System policy applied to
each listed profile. A Event System Policy allows the
profile to capture system events and append them to a log
file. This option is not selected by default |
| DHCPv4 Policy | Lists the name of the DHCPv4 Policy used with each listed
profile. This option is not selected by default |
| Field | Description |
|---|---|
| Auto-Provisioning Policy | Displays the Auto-Provisioning policy applied to this profile. At adoption, an AP solicits and receives multiple adoption responses. These adoption responses contain preference and loading policy information the AP uses to select the optimum controller or access point for adoption. By default, an Auto-Provisioning policy generally distributes AP adoption evenly amongst available adopters. Modify existing adoption policies or create a new one as needed to meet the adoption requirements of this particular profile |
| Use NOC Auto-Provisioning Policy | Select this option to use the NOC‘s auto provisioning
policy instead of the policy local to the controller or
service platform. The NOC is an elected controller or
service platform capable of provisioning all of its peer
controllers, service platforms and adopted devices. The options are No, Yes, and Always. The default selection is No |
| Learn and Save Network Configuration | Select this option to allow the controller or service platform to maintain a local configuration records of devices requesting adoption and provisioning. This feature is enabled by default |