The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Your software release may not support all of the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
You can configure Cisco CleanAir only on CleanAir-enabled access points.
Only Cisco CleanAir-enabled access points using the following access point modes can perform Cisco CleanAir spectrum monitoring:
Local—In this mode, each Cisco CleanAir-enabled access point radio provides air quality and interference detection reports for the current operating channel only.
Monitor—When Cisco CleanAir is enabled in monitor mode, the access point provides air quality and interference detection reports for all monitored channels.
The following options are available:
All— All channels
DCA—Channel selection governed by the DCA list
Country—All channel legal within a regulatory domain
 Note |
The access point does not participate in AQ HeatMap in Prime Infrastructure. |
SE-Connect—This mode enables a user to connect a Spectrum Expert application running on an external Microsoft Windows XP or Vista PC to a Cisco CleanAir-enabled access point in order to display and analyze detailed spectrum data. The Spectrum Expert application connects directly to the access point, bypassing the device. An access point in SE-Connect mode does not provide any Wi-Fi, RF, or spectrum data to the device. All CleanAir system functionality is suspended while the AP is in this mode, and no clients are served. This mode is intended for remote troubleshooting only. Up to three active Spectrum Expert connections are possible.
Access points in monitor mode do not transmit Wi-Fi traffic or 802.11 packets. They are excluded from radio resource management (RRM) planning and are not included in the neighbor access point list. IDR clustering depends on the device’s ability to detect neighboring in-network access points. Correlating interference device detections from multiple access points is limited between monitor-mode access points.
Cisco recommends a ratio of 1 monitor mode access point for every 5 local mode access points, this may also vary based on the network design and expert guidance for best coverage.
Spectrum Expert (Windows XP laptop client) and AP should be pingable, otherwise; it will not work.
Cisco CleanAir is a spectrum intelligence solution designed to proactively manage the challenges of a shared wireless spectrum. All of the users of the shared spectrum can be seen (both native devices and foreign interferers). It also enables the network to act upon this information. For example, the interfering device can be manually removed or the system can automatically change the channel away from the interference.
A Cisco CleanAir system consists of CleanAir-enabled access points, wireless controller modules, mobility controllers, mobility anchors and next generation switches. The access points join the mobility controller directly or through the mobility anchor. They collect information about all devices that operate in the industrial, scientific, and medical (ISM) bands, identify and evaluate the information as a potential interference source, and forward it to the device. The device controls the access points, collects spectrum data, and forwards information to Cisco Prime Infrastructure (PI) or a Cisco Mobility Services Engine (MSE) upon request.
Any networking configurations can be performed only on the mobility controller, configurations cannot be performed in the MA mode. However, any radio level CleanAir configurations can be done using mobility anchor.
For every device operating in the unlicensed band, Cisco CleanAir tells what it is, where it is, how it is impacting the wireless network, and what actions should be taken. It simplifies RF.
Wireless LAN systems operate in unlicensed 2.4-GHz and 5-GHz ISM bands. Many devices like microwave ovens, cordless phones, and Bluetooth devices also operate in these bands and can negatively affect the Wi-Fi operations.
Some of the most advanced WLAN services, such as voice over wireless and IEEE 802.11n radio communications, could be significantly impaired by the interference caused by other legal users of the ISM bands. The integration of Cisco CleanAir functionality addresses this problem of radio frequency (RF) interference.
The basic Cisco CleanAir architecture consists of Cisco CleanAir-enabled APs and device. Cisco Prime Infrastructure (PI), Mobility Services Engine (MSE) and Cisco Spectrum Expert are optional system components. Cisco PI and MSE provide user interfaces for advanced spectrum capabilities such as historic charts, tracking interference devices, location services and impact analysis.
An access point equipped with Cisco CleanAir technology collects information about non-Wi-Fi interference sources, processes it, and forwards it to the MA. The access point sends AQR and IDR reports to the controller.
The mobility controller (MC) controls and configures CleanAir-capable access points, collects and processes spectrum data, and provides it to the PI and/or the MSE. The MC provides local user interfaces (GUI and CLI) to configure basic CleanAir features and services and display current spectrum information. The MC also does detection, merging and mitigation of interference devices using RRM TPC and DCM. For details on Interference Device Merging, see Interference Device Merging.
Cisco PI provides advanced user interfaces for CleanAir that include feature enabling and configuration, consolidated display information, historic AQ records and reporting engines. PI also shows charts of interference devices, AQ trends, and alerts.
Cisco MSE is required for location and historic tracking of interference devices, and provides coordination and consolidation of interference reports across multiple controllers. MSE also provides adaptive Wireless Intrusion Prevention System (WIPS) service that provides comprehensive over-the-air threat detection, location and mitigation. MSE also merges all the interference data.
To obtain detailed spectrum data that can be used to generate RF analysis plots similar to those provided by a spectrum analyzer, you can configure a Cisco CleanAir-enabled access point to connect directly to a Microsoft Windows XP or Vista PC running the Cisco Spectrum Expert application.
| Term | Decription |
|---|---|
| AQI | Air Quality Index. The AQI is an indicator of air quality, based on the air pollutants. An AQI of 0 is bad and an AQI > 85 is good. |
| AQR | Air Quality Report. AQRs contain information about the total interference from all identified sources represented by AQI and summary of the most severe interference categories. AQRs are sent every 15 minutes to the Mobility Controller and every 30 seconds in the Rapid mode. |
| DC | Duty Cycle. Percentage of time that the channel is utilized by a device. |
| EDRRM | EDRRM Event Driven RRM. EDRRM allows an access point in distress to bypass normal RRM intervals and immediately change channels. |
| IDR | Interference Device Reports that the access point sends to the controller. |
| ISI | Interference Severity Index. The ISI is an indicator of the severity of the interference. |
| MA | Mobility Agent. An MA is either an access switch that has a wireless module running on it or an MC with an internal MA running on it. An MA is the wireless component that maintains client mobility state machine for a mobile client that is connected to an access point to the device that the MA is running on. |
| MC | Mobility Controller. An MC provides mobility management services for inter-peer group roaming events. The MC provides a central point of contact for management and sends the configuration to all the mobility agents under its sub-domain of their mobility configuration, peer group membership and list of members. |
| RSSI | Received Signal Strength Indicator. RSSI is a measurement of the power present in a received radio signal. It is the power at which an access point sees the interferer device. |
Cisco CleanAir can detect interference, report on the location and severity of the interference, and recommend different mitigation strategies. Two such mitigation strategies are persistent device avoidance and spectrum event-driven RRM. New
Note |
Spectrum event-driven RRM can be triggered only by Cisco CleanAir-enabled access points in local mode. |
Spontaneous interference is interference that appears suddenly on a network, perhaps jamming a channel or a range of channels completely. The Cisco CleanAir spectrum event-driven RRM feature allows you to set a threshold for air quality (AQ) that, if exceeded, triggers an immediate channel change for the affected access point. Most RF management systems can avoid interference, but this information takes time to propagate through the system. Cisco CleanAir relies on AQ measurements to continuously evaluate the spectrum and can trigger a move within 30 seconds. For example, if an access point detects interference from a video camera, it can recover by changing channels within 30 seconds of the camera becoming active. Cisco CleanAir also identifies and locates the source of interference so that more permanent mitigation of the device can be performed at a later time.
In the case of Bluetooth devices, Cisco CleanAir-enabled access points can detect and report interference only if the devices are actively transmitting. Bluetooth devices have extensive power save modes. For example, interference can be detected when data or voice is being streamed between the connected devices.
The Interference Devices (ID) messages are processed on a Mobility Controller (MC). The Mobility Anchor (MA) forwards the ID messages from APs and hence they are processed on the MC. The MC has visibility of the neighbor information across APs connected to different MAs.
ID merging logic requires AP neighbor information. Neighbor information is obtained from the RRM module. This api only gives neighbor information to the APs directly connected to MC.
Currently the AP neighbor list on MA is synced to MC once every 3 minutes; hence the AP neighbor list obtained by this api could be at most 3 mins old. This delay results in delay in merging of Devices as they are discovered. The subsequent periodic merge will pick up the updated neighbor information and merge is performed
Some interference devices such as outdoor bridges and Microwave Ovens only transmit when needed. These devices can cause significant interference to the local WLAN due to short duration and periodic operation remain largely undetected by normal RF management metrics. With CleanAir the RRM DCA algorithm can detect, measure, register and remember the impact and adjust the DCA algorithm. This minimizes the use of channels affected by the persistent devices in the channel plan local to the interference source. Cisco CleanAir detects and stores the persistent device information in the device and this information is used to mitigate interfering channels.
CleanAir-capable Monitor Mode access point collects information about persistent devices on all configured channels and store the information in controller. Local/Bridge mode AP detects interference devices on the serving channels only.
When a Persistent Device (PD) is detected in the CleanAir module, it is reported to the RRM module on the MA. This information is used in the channel selection by the subsequent EDRRM Event Driven RRM (ED-RRM) signal sent to the RRM module.
EDRRM is a feature that allows an access point that is in distress to bypass normal RRM intervals and immediately change channels. A CleanAir access point always monitors AQ and reports the AQ every 15 minutes. AQ only reports classified interference devices. The key benefit of EDRRM is very fast action time. If an interfering device is operating on an active channel and causes enough AQ degradation to trigger an EDRRM, then no clients will be able to use that channel or the access point. You must remove the access point from the channel. EDRRM is not enabled by default, you must first enable CleanAir and then enable EDRRM.
AQRs are only available on the MC. The mode configuration and timers are held in Radio Control Block (RCB) on MA (for APs connected to MA). There is no change to the current API available for EMS/NMS. No change is required for directly connected APs as RCB (spectrum config and timers) is available locally. For remote APs (APs connected to MA), three new control messages are added. These three messages are for enable, restart timer and disable rapid update mode for a given AP MAC address and slot.
CleanAir configuration (network and radio) is stateful during the switchover. On the MC, Embedded Instrumentation Core (EICORE) provides the sync on network configurations across active and standby nodes. The radio configurations are synced using the HA Infrastructure. The CleanAir configurations on MA are pulled from the MC upon joining. The network configuration is not stored in the EICORE on MA, hence it is synced using HA Infrastructure.
CleanAir Data (AQ and IDR) reports are not stateful, that is, the standby and active nodes are not synced. On switchover, the APs send the reports to the current active slot. The RRM Client (HA Infra Client) is used for CleanAir HA sync.
How to Configure CleanAir
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
configure terminal Example: |
Enters global configuration mode. |
| Step 2 |
ap dot11 24ghz cleanair Example: |
Enables the CleanAir feature on 802.11b network. Add no in the command to disable CleanAir on the 802.11b network. |
| Step 3 |
end Example: |
Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
configure terminal Example: |
Enters global configuration mode. |
| Step 2 |
ap dot11 24ghz cleanair alarm air-quality threshold threshold_value Example: |
Configures the alarm for the threshold value for air-quality for all the 2.4-GHz devices. Add the no form of this command to disable the alarm. |
| Step 3 |
ap dot11 24ghz cleanair alarm device {bt-discovery | bt-link | canopy | cont-tx | dect-like | fh | inv | jammer | mw-oven | nonstd | report | superag | tdd-tx | video | wimax-fixed | wimax-mobile | xbox | zigbee } Example: |
|
| Step 4 |
end Example: |
Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
configure terminal Example: |
Enters global configuration mode. |
| Step 2 |
ap dot11 24ghz cleanair device{bt-discovery | bt-link | canopy | cont-tx | dect-like | fh | inv | jammer | mw-oven | nonstd | report | superag | tdd-tx | video | wimax-fixed | wimax-mobile | xbox | zigbee } Example: |
|
| Step 3 |
end Example: |
Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
configure terminal Example: |
Enters global configuration mode. |
| Step 2 |
ap dot11 5ghz cleanair Example: |
Enables the CleanAir feature on 802.11a network. Add no in the command to disable CleanAir on the 802.11a network. |
| Step 3 |
end Example: |
Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
configure terminal Example: |
Enters global configuration mode. |
| Step 2 |
ap dot11 5ghz cleanair alarm air-quality threshold threshold_value Example: |
Configures the alarm for the threshold value for air-quality for all the 5-GHz devices. Add the No form of the command to disable the alarm. |
| Step 3 |
ap dot11 5ghz cleanair alarm device{canopy | cont-tx | dect-like | inv | jammer | nonstd | radar | report | superag | tdd-tx | video | wimax-fixed | wimax-mobile} Example: |
|
| Step 4 |
end Example: |
Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
configure terminal Example: |
Enters global configuration mode. |
| Step 2 |
ap dot11 5ghz cleanair device{canopy | cont-tx | dect-like | inv | jammer | nonstd | radar | report | superag | tdd-tx | video | wimax-fixed | wimax-mobile} Example: |
|
| Step 3 |
end Example: |
Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
configure terminal Example: |
Enters global configuration mode. |
| Step 2 |
ap dot11 { 24ghz | 5ghz} rrm channel cleanair-event Example: |
Enables EDRRM cleanair-event. Add the no form of the command to disable EDRRM. |
| Step 3 |
ap dot11 { 24ghz | 5ghz} rrm channel cleanair-event [sensitivity {high | low | medium}] Example: |
|
| Step 4 |
end Example: |
Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
configure terminal Example: |
Enters global configuration mode. |
| Step 2 |
ap dot11 { 24ghz | 5ghz} rrm channel device Example: |
Enables the persistent non Wi–Fi device avoidance in the 802.11 channel assignment. Add the no form of the command to disable the persistent device avoidance. |
| Step 3 |
end Example: |
Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode. |
Spectrum Expert (Windows XP laptop client) and access point should be pingable, otherwise; it will not work.
Prior to establishing a connection between the Spectrum Expert console and the access point, make sure that IP address routing is properly configured and the network spectrum interface (NSI) ports are open in any intervening firewalls.
The access point must be a TCP server listening on ports 37540 for 2.4-GHz and 37550 for 5-GHz frequencies. These ports must be opened for the spectrum expert application to connect to the access point using the NSI protocol.
You can view the NSI key from the device CLI by using the show ap name ap_name config dot11 { 24ghz | 5ghz} command.
| Step 1 |
To configure the access point for SE-Connect mode, enter this command: ap name ap_name mode se-connect Example: |
| Step 2 |
When prompted to reboot the access point, enter Y. |
| Step 3 |
To view the NSI key for the access point, enter this command: Example: |
On the Windows PC, download Cisco Spectrum Expert:
Access the Cisco Software Center from this URL: http://www.cisco.com/cisco/software/navigator.html
Click Product > Wireless > Cisco Spectrum Intelligence > Cisco Spectrum Expert > Cisco Spectrum Expert Wi-Fi, and then download the Spectrum Expert 4.1.11 executable (*.exe) file.
Run the Spectrum Expert application on the PC.
When the Connect to Sensor dialog box appears, enter the IP address of the access point, choose the access point radio, and enter the 16-byte network spectrum interface (NSI) key to authenticate. The Spectrum Expert application opens a TCP/IP connection directly to the access point using the NSI protocol.
When an access point in SE-Connect mode joins a device, it sends a Spectrum Capabilities notification message, and the device responds with a Spectrum Configuration Request. The request contains the 16-byte random NSI key generated by the device for use in NSI authentication. The device generates one key per access point, which the access point stores until it is rebooted.
Note |
You can establish up to three Spectrum Expert console connections per access point radio. |
Verify that the Spectrum Expert console is connected to the access point by selecting the Slave Remote Sensor text box in the bottom right corner of the Spectrum Expert application. If the two devices are connected, the IP address of the access point appears in this text box.
Use the Spectrum Expert application to view and analyze spectrum data from the access point.
| Commands | Description |
|---|---|
|
show ap dot11 24ghz cleanair air-quality summary |
Displays CleanAir Air Quality (AQ) data for 2.4-GHz band |
|
show ap dot11 24ghz cleanair air-quality worst |
Displays CleanAir Air Quality (AQ) worst data for 2.4-GHz band |
|
show ap dot11 24ghz cleanair config |
Displays CleanAir Configuration for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type all |
Displays all CleanAir Interferers for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type bt-discovery |
Displays CleanAir Interferers of type BT Discovery for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type bt-link |
Displays CleanAir Interferers of type BT Link for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type canopy |
Displays CleanAir Interferers of type Canopy for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type cont-tx |
Displays CleanAir Interferers of type Continuous transmitter for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type dect-like |
Displays CleanAir Interferers of type DECT Like for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type fh |
Displays CleanAir Interferers of type 802.11FH for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type inv |
Displays CleanAir Interferers of type WiFi Inverted for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type jammer |
Displays CleanAir Interferers of type Jammer for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type mw-oven |
Displays CleanAir Interferers of type MW Oven for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type nonstd |
Displays CleanAir Interferers of type WiFi Inv. Ch for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type persistent |
Displays CleanAir Interferers of type Persistent for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type superag |
Displays CleanAir Interferers of type SuperAG for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type tdd-tx |
Displays CleanAir Interferers of type TDD Transmit for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type video |
Displays CleanAir Interferers of type Video Camera for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type wimax-fixed |
Displays CleanAir Interferers of type WiMax Fixed for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type wimax-mobile |
Displays CleanAir Interferers of type WiMax Mobile for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type xbox |
Displays CleanAir Interferers of type Xbox for 2.4-GHz band |
|
show ap dot11 24ghz cleanair device type zigbee |
Displays CleanAir Interferers of type zigbee for 2.4-GHz band |
|
show ap dot11 5ghz cleanair air-quality summary |
Displays CleanAir Air Quality (AQ) data for 5-GHz band |
|
show ap dot11 5ghz cleanair air-quality worst |
Displays CleanAir Air Quality (AQ) worst data for 5-GHz band |
|
show ap dot11 5ghz cleanair config |
Displays CleanAir Configuration for 5-GHz band |
|
show ap dot11 5ghz cleanair device type all |
Displays all CleanAir Interferers for 5-GHz band |
|
show ap dot11 5ghz cleanair device type canopy |
Displays CleanAir Interferers of type Canopy for 5-GHz band |
|
show ap dot11 5ghz cleanair device type cont-tx |
Displays CleanAir Interferers of type Continuous TX for 5-GHz band |
|
show ap dot11 5ghz cleanair device type dect-like |
Displays CleanAir Interferers of type DECT Like for 5-GHz band |
|
show ap dot11 5ghz cleanair device type inv |
Displays CleanAir Interferers of type WiFi Inverted for 5-GHz band |
|
show ap dot11 5ghz cleanair device type jammer |
Displays CleanAir Interferers of type Jammer for 5-GHz band |
|
show ap dot11 5ghz cleanair device type nonstd |
Displays CleanAir Interferers of type WiFi Inv. Ch for 5-GHz band |
|
show ap dot11 5ghz cleanair device type persistent |
Displays CleanAir Interferers of type Persistent for 5-GHz band |
|
show ap dot11 5ghz cleanair device type superag |
Displays CleanAir Interferers of type SuperAG for 5-GHz band |
|
show ap dot11 5ghz cleanair device type tdd-tx |
Displays CleanAir Interferers of type TDD Transmit for 5-GHz band |
|
show ap dot11 5ghz cleanair device type video |
Displays CleanAir Interferers of type Video Camera for 5-GHz band |
|
show ap dot11 5ghz cleanair device type wimax-fixed |
Displays CleanAir Interferers of type WiMax Fixed for 5-GHz band |
|
show ap dot11 5ghz cleanair device type wimax-mobile |
Displays CleanAir Interferers of type WiMax Mobile for 5-GHz band |
When a CleanAir-enabled access point detects interference devices, detections of the same device from multiple sensors are merged together to create clusters. Each cluster is given a unique ID. Some devices conserve power by limiting the transmit time until actually needed which results in the spectrum sensor to temporarily stop detecting the device. This device is then correctly marked as down. A down device is correctly removed from the spectrum database. In cases when all the interferer detections for a specific devices are reported, the cluster ID is kept alive for an extended period of time to prevent possible device detection bouncing. If the same device is detected again, it is merged with the original cluster ID and the device detection history is preserved.
For example, some bluetooth headsets operate on battery power. These devices employ methods to reduce power consumption, such as turning off the transmitter when not actually needed. Such devices can appear to come and go from the classification. To manage these devices, CleanAir keeps the cluster IDs longer and they are remerged into a single record upon detection. This process smoothens the user records and accurately represents the device history.
This example shows how to enable CleanAir on the 2.4-GHz band and an access point operating in the channel:
Device#configure terminal
Device(config)#ap dot11 24ghz cleanair
Device(config)#exit
Device#ap name TAP1 dot11 24ghz cleanair
Device#end
This example shows how to configure a CleanAir Alarm for 2.4-GHz Air-Quality threshold of 50 dBm and an Xbox device:
Device#configure terminal
Device(config)#ap dot11 24ghz cleanair alarm air-quality threshold 50
Device(config)#ap dot11 24ghz cleanair alarm device xbox
Device(config)#end
This example shows how to configure interference reporting for 5-GHz devices:
Device#configure terminal
Device(config)#ap dot11 5ghz cleanair alarm device xbox
Device(config)#end
This example shows how to enable an EDRRM cleanair-event in the 2.4-GHz band and configure high sensitivity to non Wi–Fi interference:
Device#configure terminal
Device(config)#ap dot11 24ghz rrm channel cleanair-event
Device(config)#ap dot11 24ghz rrm channel cleanair-event sensitivity high
Device(config)#end
This example shows how to enable persistent non Wi–Fi device avoidance in the 2.4-GHz band:
Device#configure terminal
Device(config)#ap dot11 24ghz rrm channel device
Device(config)#end
This example shows how to configure an access point in the SE-Connect mode:
Device#ap name Cisco_AP3500 mode se-connect|
Q. |
How do I check if my MC is up? |
|
A. |
To check if the MC is up, use the command: show wireless mobility summary . This example shows how to display the mobility summary: |
|
Q. |
Multiple access points detect the same interference device, however, the device shows them as separate clusters or different suspected devices clustered together. Why does this happen? |
|
A. |
Access points must be RF neighbors for the device to consider the merging of devices that are detected by these access points. The access point takes time to establish neighbor relationships. A few minutes after the device reboots or a change in the RF group and similar events, clustering will not be very accurate. |
|
Q. |
Can I merge two monitor mode access points using a device? |
|
A. |
No, you cannot merge two monitor mode access points using a device. You can merge the monitor mode access points only using MSE. |
|
Q. |
How do I view neighbor access points? |
|
A. |
To view neighbor access points, use the command: show ap ap_name auto-rf dot11{ 24ghz | 5ghz} This example shows how to display the neighbor access points: |
|
Q. |
What are the debug commands available for CleanAir? |
|
A. |
The debug commands for CleanAir are: debug cleanair { all | error | event | internal-event | nmsp | packet} debug rrm { all | channel | detail | error | group | ha | manager | message | packet | power | prealarm | profile | radar | rf-change | scale | spectrum} |
|
Q. |
Why are CleanAir Alarms not generated for interferer devices? |
|
A. |
Verify that the access points are CleanAir-capable and CleanAir is enabled both on the access point and the device. |
|
Q. |
Can the Cisco Catalyst 3850 and 3650 Series Switches function as a Mobility Agent (MA)? |
|
A. |
Yes, the Cisco Catalyst 3850 and 3650 Series Switches can function as an MA. |
|
Q. |
Are CleanAir configurations available on the MA? |
|
A. |
|
| Related Topic | Document Title |
|---|---|
|
CleanAir commands and their details |
CleanAir Command Reference, Cisco IOS XE Release 3SE (Catalyst 3650 Switches) |
|
High Availability configurations |
High Availability Configuration Guide, Cisco IOS XE Release 3SE (Cisco 5700 Series Wireless Controllers) |
|
High Availability commands and their details |
High Availability Command Reference, Cisco IOS XE Release 3SE (Cisco 5700 Series Wireless Controllers) |
| Description | Link |
|---|---|
|
To help you research and resolve system error messages in this release, use the Error Message Decoder tool. |
https://www.cisco.com/cgi-bin/Support/Errordecoder/index.cgi |
| MIB | MIBs Link |
|---|---|
| All supported MIBs for this release. |
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
| Description | Link |
|---|---|
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
Feedback