backhaul radio of the 1552 access points in Bridge mode. In all other AP modes, the 5-GHz backhaul radio
of the 1552 access points operates in CleanAir mode.
Enabling CleanAir
To enable CleanAir functionality in the system, you first need to enable CleanAir on the controller through
Wireless > 802.11a/b > CleanAir
. Although CleanAir is disabled by default, CleanAir is enabled by default
on the AP interface.
After you enable CleanAir, it takes 15 minutes to propagate air quality information because the default reporting
interval is 15 minutes. However, you can see the results instantly at the CleanAir detail level on the radio by
going to
Monitor > Access Points > 802.11a/n
or
802.11b/n
.
Licensing
A CleanAir system requires a CleanAir AP and a controller that is running release 7.0 or later releases. Adding
the Cisco Prime Infrastructure allows the displays to be enhanced and additional information to be correlated
within the system. Adding the MSE further enhances the available features and provides the history and
location of specific interference devices. There is no additional license requirement for the CleanAir feature
because the CleanAir AP is the license. Adding the Prime Infrastructure can be done with a basic license.
Adding the MSE to the system requires a Prime Infrastructure Plus license and a context-aware license selection
for the MSE.
For purposes of interference location with the MSE, each interference device counts as a location target in
Context-Aware. One hundred Permanent Interferer licenses are embedded in the MSE. Interferer Licenses
open as CleanAir APs are detected, in stages of five licenses per CleanAir AP. This process is applicable to
AP1552. An Interference device is the same as a client or a tag from a license quantity standpoint. Only a
small percentage of the available licenses are used because there should be far less interference devices than
clients or tags to track. Users do have control over what types of interference devices to detect and located
from the controller configuration menus.
Cisco context-aware licenses can be managed and limited by the class of target (client, tag, interference),
which gives users complete control over how licenses are used.
Each interference device requires one context-aware service (CAS) license.
Note
If you have too many Bluetooth devices, it is advisable to switch off the tracing of these devices because they
might take up too many CAS licenses.
Wireless Mesh Mobility Groups
A mobility group allows controllers to peer with each other to support seamless roaming across controller
boundaries. APs learn the IP addresses of the other members of the mobility group after the CAPWAP Join
process. A controller can be a member of a single mobility group which can contain up to 24 controllers.
Mobility is supported across 72 controllers. There can be up to 72 members (WLCs) in the mobility list with
up to 24 members in the same mobility group (or domain) participating in client hand-offs. The IP address of
a client does not have to be renewed in the same mobility domain. Renewing the IP address is irrelevant in
the controller-based architecture when you use this feature.
Cisco Mesh Access Points, Design and Deployment Guide, Release 7.3
94
OL-27593-01
Site Preparation and Planning
Wireless Mesh Mobility Groups
