For the past few years Cisco has been talking about their CleanAir technology. If you are not familiar with CleanAir, the CleanAir technology will detect wireless interference and some access points (AP) will change channels to get away from the interference. To read more about Cisco’s CleanAir technology click here.
I feel like the ability to view interferes is highly valuable, especially when the site you are supporting is somewhere else. I have sites that are many hours away and with the non-CleanAir APs, I simply guess at interference problems. In these sites, I randomly change the channels when I feel like the problem may be interference. For me, it was very exciting to receive some CleanAir APs and put them into my network.
After digging into the output that I can receive, I wasn’t very impressed, but I didn’t know what to expect either. On the controller, you are able to find the AP that you want, then look at the CleanAir information. It does give you a list of interferes in real time. It gives you a code of what the device is and gives you a few graphs. In the graphs, it will show you the Air Quality, Channel Utilization and Interference Power. All of this is very good information. As you can see in the image below, it also gives you some information on the interferes.
The controller will give you the real time information, but what about historical information? Prime Infrastructure should solve that problem. Prime Infrastructure (PI), used to be WCS, is the management system that manages the wireless controllers and access points. You are able to manage many controllers and access points from PI. PI is Cisco’s preferred way of managing your wireless infrastructure. PI has a section of canned reports ready to be run for CleanAir information. When I ran these reports, I never got any information, nothing was ever found. I figured this was due to a bug in PI, but never had the urgency to open a case on it.
The lack of CleanAir information in PI has nothing to do with a Bug in the software. PI is not the location to store the historical CleanAir information. This explains why PI would never have anything in the CleanAir reports. All of the historical information is stored in the Mobility Services Engine (MSE). Only after purchasing and connecting my MSE to PI, PI was able to provide information in these reports that I tried to run in the past.
If you want your network to automatically change channels to avoid wireless interference, you need an AP that fully supports CleanAir. Some APs like the 1600 series only report the clean air information, they don’t take any action. The 3600 series APs are supposed to automatically change channels to move away from the interference. You need to identify your needs and your budget to figure out what you should get.
If you want historical information, you need to purchase PI and the MSE. It was very disappointing for me to find out that PI is THE MANAGEMENT SYSTEM, but it doesn’t store historical CleanAir information. It runs on a server, can have plenty of disk space, is advertised as the way you should manage your wireless system, but it doesn’t display any useful CleanAir information by itself.
I do have to say that with the MSE connected to PI, there is some really good CleanAir information that can be gathered through PI. In this regard, Cisco did a good job.
Has anybody else run into this same disappointment as I have?
No need for an account to post a response, find the reply button below and leave one!!!