#CiscoChampion Radio is a podcast series by technologists for technologists. In this episode, Cisco Champions Rowell Dionicio and Robert Boardman discuss Cisco WiFi Troubleshooting and Optimization with Jerome Henry.
Jerome Henry is a Principal Engineer, Technical Marketing in the Wi-Fi Business Unit. He has extensive experience in troubleshooting wireless networks. In this Cisco Champion Radio episode, we talk Jerome about tools for troubleshooting wifi, packet analysis and MIMO considerations, using Excel to troubleshoot (yes Excel!), access points coverage, most common issues, and Jerome’s process for optimizing a wireless network.
Rowell and Robert host a video channel together called Wi-Fi of Everything. Be sure to check it out and subscribe!
You can catch this episode on Sound Cloud and listen to the other Cisco Champion Radio episodes as well.
Coming off the Cisco Champion Radio podcast, François and Rowell share their RRM experience.
Our Cisco RRM Experience
We use Cisco RRM on a daily basis and in most of the environments we configure and manage. It’s come a long way since it’s introduction but we’re both still learning so much about Cisco RRM.
For a large environment, RRM is a useful tool. But when changes are done on the WLAN, RRM needs to be reset and settled.
In this episode, we talk about our experience using RRM. What does it mean to design with RRM in mind? How does one use RRM with high density, capacity, coverage, etc while keeping ensuring it meets requirements.
We touch upon using design tools such as Ekahau Site Survey and how you use those design tools with RRM. Can it be done?
And what do we think about those who don’t think RRM works at all? We touch on that just a little.
Take a listen to the episode and share your experience in the comments below.
François and I were fortunate to be able to host Cisco Champion Radio this week. We tackled the topic of Cisco Radio Resource Management (RRM) with subject matter expert, Jim Florwick.
Jim is a Technical Marketing Engineer with deep knowledge of how Cisco RRM works.
I started off the conversation by asking Jim what the most common misconceptions are of RRM. He provides a great response because many people seem to leave RRM at its defaults or believe RRM would fix all their RF problems.
Jim provides insight into how the algorithms work and how you should consider them into your design or existing WLAN infrastructure. The important tip he provided was to initiate a DCA restart when major changes have been applied to the WLAN. These changes can be new APs, channel changes, a new controller, you name it.
François asked an important question, how do you perform your validation surveys with RRM in mind? Jim responded with freezing RRM to prevent any changes from occurring while you’re conducting your validation survey. You don’t want to see the same AP shown with two different channels or have transmit power changing while you’re doing your survey.
We then go into the addition of FRA and the complexity it adds to RRM and other topics as well. Give the episode a listen on SoundCloud!
Fred Niehaus and Wes Purvis, of Cisco, discuss how the network sensor brings an impact with Wi-Fi assurance.
The Network Sensor
This episode was all brought together because of a recent announcement of Cisco’s dedicated Wi-Fi network sensor. A smaller AP-looking device, similar to the Cisco 1815, that can be wall-mounted or placed close to the users. It’s purpose is to validate Wi-Fi connectivity.
Named the Cisco Aironet Sensor, there are three components:
Wireless performance analytics
Real-time client troubleshooting
Proactive Health Assessment
Wes Purvis talks about the requirements of running the dedicated sensor:
Cisco WLC with 8.5 MR2
Cisco DNA Center
Cisco Aironet Sensor Tests
François and Rowell ask why even build a sensor with other companies in the market also developing their own kind of sensors. Primarily it was to give more visibility into the network and to do prescribed testing.
The Cisco Aironet Sensor will associate directly with a Cisco AP. Various health checks can be performed by acting like a client device. The results of those tests bypass the Cisco WLC and get reported directly to Cisco DNA Center.
There are three modes to the sensor:
Wave 2 AP as a sensor
Radio as a sensor
Results of the tests ran by the network sensor
Those last two modes are interesting. A Wave 2 AP can stop serving clients and become a sensor itself to run any diagnostic tests. The third option is available to APs with an XOR radio. One of the radios goes out of service to clients and acts as a client itself, connecting to other APs.
In the episode we did speak about turning an AP into a sensor and the cautions there. Because APs are not near the clients, the results may not reflect the experience of a real client.
Currently, Cisco supports a number of different tests on the sensor. There are about 10-15 available with future expansion into custom tests. Some of those tests include:
Connect to an IP address
Download a webpage
Let us know what you think below in the comments after you listen to the episode with Wes Purvis and Fred Niehaus.
This Week In Wireless
New CWNE this week – Oguzhan Eren from Turkey became CWNE #266
CWNP Wi-Fi Trek Registration – The registration for this years CWNP Wi-Fi Trek conference begins on March 12th. Registration Link
T-Mobile Annouces Plans to Deploy 5G in 30 U.S. Cities this year. T-Mobile is already installing 5G equipment as it continues to build its LTE network in the US. The company should be able to deploy a comprehensive 5G layer in time for the debut of 5G consumer devices next year. The service will be used over the 600 MHz spectrum along with spectrum in the 28GHz and 39GHz bands. First cities to be served: New York, Los Angeles, Dallas and Las Vegas. Read more here.
Following a Twitter conversation which happened last weekend driven by Jeremy Ward on Private LTE networks or LTE network in general. Jeremy recommended the lteuniversity.com website to start learning about LTE.
The earliest Cisco WLC version where Cisco CleanAir was released dates back to the 7.0 days. Sometime around the year 2010. Cisco CleanAir is always on within an AP, granted if it is Enabled in the WLC. There is a Spectrum Analysis Engine (SaGE) chip built into the AP. This is important to know because it doesn’t prevent the AP from serving clients. SaGE works alongside the Wi-Fi chip. There is no affect to client throughput or traffic.
To enhance Cisco RRM’s features, CleanAir plays a critical role in allowing RRM to change channels if persistent interference is detected. CleanAir will field the appropriate algorithms to help the WLC make changes to improve an environment.
Cisco CleanAir produces two important elements:
Interference Device Report
Air Quality Index
The Interference Device Report (IDR) provides information on detected interference. It will provide a class type, what band the interference was detected on and on what channel(s), the severity of the interference, it’s duty cycle, and the interference signature.
The Air Quality Index (AQI) provides a quality score, from 0 – 100%, with 100% being good. The index will display total channel power, total channel duty cycle, the power of the interferer and total interference duty cycle.
A benefit of using Cisco CleanAir is having the ability to troubleshoot the shared spectrum remotely and without any additional hardware. A CleanAir supported access point can be utilized for this purpose. Some things to keep in mind when using your CleanAir access point for troubleshooting interference:
There are three modes:
Local – The AP will continue to serve clients on its operating channel. But any spectrum monitoring is performed on that channel only.
Monitor – The AP doesn’t server any clients but provides full time scanning.
Spectrum Expert Connect – This is a dedicated spectrum sensor and doesn’t serve any clients.
In times when the best response is to use technical support hands to troubleshoot the issue, having a method of automatically mitigating an interference issue can be highly beneficial. It can cut time to resolution down and react faster than a support team that is reactionary.
What we’d like to see from CleanAir is the ability to tell an administrator whether any action needs to be performed. While interference and air quality is determined on any given channel, does it even matter? Are any users impacted negatively? A smarter system would be able to detect interference and provide exactly which users are having issues directly related to this interferer and what kind of impact that is. And a step further would be to automatically adjust the system to fix the problem.
We’ve included some images of Cisco CleanAir in action from within Spectrum Expert and Metageek Chanalyzer.