RF Domain Deployment Considerations

Before settings RF Domains for controllers, service platforms and access points, refer to the following deployment guidelines to ensure the configurations are optimally effective:

• Each controller utilizes a default RF Domain. Access points are assigned to this default RF Domain as they are discovered. The default RF Domain can be used for single site deployments, where regional, regulatory and RF policies are common between devices.
• User defined RF Domains must be manually assigned to controllers, but can be manually or automatically assigned to access points.
• A Rogue AP detection configuration is a central component of an RF Domain policy, as it provides the RF Domain policy with the means to filter potentially threatening devices from operating with devices approved within the managed network.
• WIPS is not supported on a WLAN basis, rather sensor functionality is supported on the radio(s) available to each WLAN.
• When planning sensor coverage, a minimum of 1 detector radio is recommended per 4 access points. To ensure effective placement, LANPlanner can be used to provide predictive planning services and visualization to ensure adequate radio coverage is provided based on site application and device requirements. LANPlanner provides visualization tools ensuring adequate radio coverage for client radios and sensors. A physical site survey should also be performed to verify client radio coverage, before a final deployment.
• Both default and user defined RF Domains contain policies and configuration parameters. Changes made to policies or configuration parameters are automatically inherited by all the controllers and access points assigned to the RF Domain.