Provides answers to frequently asked questions about Cisco CleanAir, addressing common operational scenarios, troubleshooting steps, and best practices for efficient RF interference management.
- 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?
-
Access points must be RF neighbors for the device to consider merging the devices that are detected by these access points. An access point takes time to establish neighbor relationships. A few minutes after the device reboots or after there is a change in the RF group, and similar events, clustering will not be very accurate.
- How do I view neighbor access points?
-
To view neighbor access points, use the show ap ap_name auto-rf dot11{ 24ghz | 5ghz} command.
This example shows how to display the neighbor access points:
Device#show ap name AS-5508-5-AP3 auto-rf dot11 24ghz <snippet> Nearby APs AP 0C85.259E.C350 slot 0 : -12 dBm on 1 (10.10.0.5) AP 0C85.25AB.CCA0 slot 0 : -24 dBm on 6 (10.10.0.5) AP 0C85.25C7.B7A0 slot 0 : -26 dBm on 11 (10.10.0.5) AP 0C85.25DE.2C10 slot 0 : -24 dBm on 6 (10.10.0.5) AP 0C85.25DE.C8E0 slot 0 : -14 dBm on 11 (10.10.0.5) AP 0C85.25DF.3280 slot 0 : -31 dBm on 6 (10.10.0.5) AP 0CD9.96BA.5600 slot 0 : -44 dBm on 6 (10.0.0.2) AP 24B6.5734.C570 slot 0 : -48 dBm on 11 (10.0.0.2) <snippet>
- What are the AP debug commands available for CleanAir?
-
The AP debug commands for CleanAir are:
-
debug cleanair { bringup | event | logdebug | low | major | nsi | offchan}
-
debug rrm { neighbor | off-channel | reports}
-