Within a managed network, to facilitate device management, peer devices are assigned a profile or RF Domain. The basic device configuration is driven by the assigned profile or RF Domain settings. However, existing RF Domain or Profile configurations can be modified (overridden) to support a requirement that dictates a device‘s configuration be customized from the configuration shared by its profiled peer devices.
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.
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.
Adoption is the process an access point uses to discover controller or service platforms available in the network, pick the most desirable one, 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 new ones as needed to meet the adoption requirements of a device and its assigned profile.
Lastly, use to define and manage a critical resource policy. A critical resource policy defines a list of device IP addresses on the network (gateways, routers etc.). The support of these IP address is interpreted as critical to the health of the network. These device addresses are pinged regularly by the controller or service platform. If there‘s a connectivity issue, an event is generated stating a critical resource is unavailable.