Showing results for 
Search instead for 
Did you mean: 
Javier Contreras
Cisco Employee
Cisco Employee

The WLC Config Analyzer home has moved to Cisco DEVNET.  See:


We also have a cloud version of the tool:


Historical info

(please use new forum for updates)

Wireless LAN Controller (WLC) Config Analyzer


Click here to Download

To request access, send an e-mail to Please include your username. Cisco employees do not need to request.

  • New version 4.0 Nov 2015
  • You may need to install .NET 3.5 before using it.External link to download:



March 31 2015. Version 3.6.5


  • Tool tips added on AP grid
  • AP MIC expiration warning
  • Flex Policies information on WLAN table


  • Minor parsing errors
  • Wrong text message on 100003
  • Wrong error on missing information on WLANS for custom web profiles

February 04, 2015. Version 3.6.4


  • Typos on messages
  • RF health exception if neighbor  AP had no power level
  • Incorrect calculation of side channel interference could lead to zero health
  • Incorrect parsing of mobility peers when new mobility is enabled
  • No text for message 2005
  • WLAN data rates nor parsed properly, display error
  • Message tab columns had incorrect order
  • NGWC:
    • Parsing error on coverage information line
    • Parsing error on peer to peer  wlan state
    • Corrected WLAN table display
    • Parsing of AP groups

January 15, 2015. Version 3.6.3



  • 11b channel monitor incorrectly parsed, leading to false positive report
  • 11b RF group peers not properly tracked
  • Corrected text for messages 40043, 30062 for clarity
  • Fixed false detection of telnet enabled on WLC
  • Added detection for parsing error on DCA Monitor channel line
  • Fixed password length check (120013)


December 17, 2014. Version 3.6.1



  • IOS-XE improved support: best practices, mobility parsing, GUI display. Partial support for RF summary, 3.7 RF information
  • Serial number in AP summary table
  • Filter per band in AP RF summary table
  • On Channel Neighbors count in AP RF summary



  • Power distribution graph level 1 not displayed
  • Exception while parsing 5760
  • RF Health calculation for Side channel noise in 5 Band
  • RF problem finder window scale issues on VMWare
  • High SNR client stats missing


November 20, 2014. Version 3.5.3

  • Fixed display of WPA AES state 
  • Fixed exception when there is a parsing error on power levels per radio

October 10, 2014. Version 3.5.2

  • Detecting Empty mesh BGN in AP config
  • Incorrect reporting of standalone TKIP in use, when there is no dot1x or PSK policies set
  • Corrected warning for empty IP Address on redundancy interfaces
  • Message wmm required for 11ac/11n not displayed when parsing a single wlc
  • Exception on 7.3 configs without RF profiles
  • Improved error reporting on parsing lines
  • Incorrect parsing of flex AP mode
  • Partial fix for window size problem on rf problem finder tool. Disable Aero interface in Windows if still having problems.
  • Handles gracefully AP list corruptions (adds AP creation in AP group information)
  • Properly parses Channel 14 Interference/Noise data as NA, in ETSI APs
  • Fix on Nearby list processing, if last line in AP is corrupted
  • Fix on parsing of system info\Management IP address
  • Fixed logic of message 30062 (false positive)
  • Fixed duplication of message 30057 for some scenarios
  • Fixed parsing of Static WEP state
  • Null error on best practices checks for some configs
  • Fixed parsing error on incorrect line separator
  • Fixed error on percentage display on best practices summary
  • 43 new checks
  • Best Practices score analysis
  • Flexgroup and FlexAP support
  • Displays DHCP proxy per interface, compares across controllers
  • Parsing, comparison between WLCs, and display of global user idle timeout
  • Parsing, comparison between WLCs, and display of WiFi direct, wlan sleep timer/sleeping client feature
  • Config Comparison across controllers of DCA mode, selection interval, metric contributors, channel list,  and channel width across controllers                   
  • Config Comparison across controllers of TPC mode, power threshold 
  • Mesh security mode parsing, comparison across controllers
  • Displays DCA metric contributions
  • New Security  Checks category
  • WLAN parsing of 11r, SKC, PMF, comparison across controllers
  • Parsing, comparison between WLCs, and display of critical management password policies                           
  • WLAN table rewrote for simplification on information displayed, less columns, adds support for 11r, PMF
  • Show values to the RXSOP and CA info messages
  • AP power state and flex group name to AP config table
  • New AP group CSV export            
  • 8.0 Support. Added RF profile DCA bandwidth, Fixed Parsing error on QinQ AP group info


July 19, 2014. Version 3.4.2

  • New Best Practices analysis tool. Focused on checking if "good to use" features are in place
  • WPS section parsing
  • SSH/Telnet/Fast SSID parsing and display
  • Checks for telnet enabled, DHCP proxy mismatch, NTP sync, Management over Wireless added
  • Improved readability of WLC/Site summary pages
  • Added QoS, Local profiling, dot1x info to wlan table 
  • New Report Center, to launch all supported report files. Disabled default report creation
  • Significant speed improvements for Neighbor calculation on large networks
  • Radius server line parsing error if line was incomplete
  • RF Index calculation exception on some files

June 27, 2014. Version 3.3.1

  • Added message summary per WLC/Site
  • HTML report  ad CSV file generation is now disabled by default
  • New Report Center being added (work in progress)
  • Correct library installation for Chart component on some PCs
  • Moved to .Net 3.5 client profile for lower memory/startup time
  • Exception error on RF Health calculation when unknown nearby data was found
  • Fixed RF Health metric for side channel noise/interference

June 27, 2014. Version 3.3.0

  • Added warning if TKIP standalone is used
  • WLAN table enhancements: displays encryption types, AVC
  • AP graph can be filtered by AP group
  • Improved message 60011 with compensated power data
  • New RF Health metric for ease of detection of problematic areas
  • Corrects parsing of 4.2 WLC files
  • Reduces problem on .Net library load (lower time when opening config set for first time)
  • Fixes problem on  AP manager check with vlan untagged scenario
  • Fixes problem on redundancy parameter parsing
  • Fixes logic of message 30065

April 23, 2014. Version 3.2.4

  • Added partial support for 5760/3850 NGWC controllers. You need to collect "sh tech and sh tech wireless" on same file for each controller (one file per ngwlc)
  • Added parsing and display of wlan count per radio on AP config
  • Updated warning for controllers with deferred or affected by security advisory versions
  • Parses, checks and displays Local EAP status per WLAN
  • Parses, checks and displays Rogue Policies, compares settings between controllers
  • Parses, checks and displays Clean Air config, compares settings between controllers
  • Chart for Client SNR distribution
  • Best practices 2.0 Checks
  1. Recommend to disable 1,2,5.5,11 data rates
  2. Warn if more than 4 SSIDs active per radio
  3. Recommend multicast multicast mode for all cases
  4. Warn if mobility group (same name) > 15 controllers, shows message to reflect that it should cover only the RF roaming space
  5. Recommend low radius timeout depending on usage scenario (not a general change)
  6. Warn if EAP identity if <10 sec, and when is needed
  7. Warn if using internal DHCP server due to scalability issues
  8. Warn if using local EAP, due to scalability on very large networks
  9. Recommend to change EAP retries to 4, timeout to 400ms
  10. Warn if tacacs timeout is short, recommend long times for OTP
  11. Recommend to have minimum rogue RSSI to -80
  12. Recommend to disable all rogue auto contain settings, unless absolutely needed for security reasons
  13. Recommend AVC enabled
  14. Warn if Fast SSID is not enabled for Apple Clients
  15. Warn if cleanair is not enabled
  • Parsing of Tacacs server entries with management timeout values
  • Parsing of User Idle timeout per wlan when it is disabled
  • Wrong detection of AP on high co-channel
  • Corrected redistribution of MS Chart Control (now properly included, and prerequisite)


March 21, 2014. Version 3.1.1

  • Application error when clicking AP name. Slot0 was not parsed
  • Multicast address message only displayed if multicast is enabled (30034)
  • RSSI client count calculation error for RF Summary

March 20, 2014. Version 3.1.0

  • Adds support for 7.4 to 7.6 versions
  • RLAN support
  • Displays Redundancy info for 7.6
  • Almost full parsing of WLAN configuration
  • Displays AP username in AP list
  • Parses and displays 802.11n, 802.11ac network status
  • Changes how text information is displayed, for ease of reading
  • Added Radius Auth Call Station ID support
New Checks
  • Warns if 11ac or 11n radios are present, but WMM is disabled on the WLAN            
  • Warns if 11ac or 11n radios are present, but 11n or 11ac support  is disabled on the controller              
  • Compares Radius Auth Call station ID across controllers
  • 78 parameters compared for matching WLANs across WLCs.
  • Warns if using HA, and no vlan tagging on management interface
  • Error while parsing mobility peers
  • Corrected that RSSI/SNR client percentage on RF summary per controller, are calculated for 1 controller, and not for all loaded
  • Corrected High RSSI client count per controller
  • Fixed wrong info on Radius aggressive failover status
  • Parsing of Radius servers on new versions
  • Parsing error on Mobility peers



RF Health Metric

New in Version 3.3.0

New experimental troubleshooting tool: “RF Health”
This is a modification of the RF index to change the format to a 0 to 100 metric, the higher the better, for a easier to use experience
it should work  properly to isolate what areas/Aps of the deployment are having a bad RF state, affecting clients.

RF Health will try to calculate different metrics applicable to RF quality on the AP, and convert to a single 100 based scale. It takes into consideration things like low SNR client count, co-channel interference, channel utilization for nearby Aps, noise, etc.
It currently supports 20/40 channel width, and handles properly bonding scenarios.
You can open “RF problem finder” to get details on the metric per type, per AP, for in depth analysis
Please provide your feedback on the metric, for additional improvements, change on default values, etc.


WLC Config Analyzer Checks



General Usage: (you can subscribe)

Bug reports/issues/features:

Fixing Voice Error Messages


WLC Config Analyzer FAQ

How to Use


Javier Contreras
Cisco Employee
Cisco Employee

hi Mikel

you can use this mechanism, or write to for feature or bug fixing requests

yes, yoour proposal makes sense and it is relatively easy to add, I marked this for inclusion on next release

Thanks for your feedback

Level 1
Level 1

Awesome, thank you.

Level 1
Level 1

When will WLC Config analyzer support 7.6 code? We are starting to deploye the 3700 series Access Points and require to run 7.6 code of the controller. This tool helps a lot with deployment.


Level 1
Level 1


i can't install the tool, i get the message "System needs Microsoft Common Language Runtime 4.0.30319.0".

I tried XP and Win7 with all patches, .net 3.5 is also installed.

Any idea ?

Tool looks really great and i'd like to use it.


Cisco Employee
Cisco Employee

I believe that this is a component of .NET - note that WLCCA needs .NET 4.0 not 3.5.

For reference, my Win7 PC shows as having "Microsoft .NET Framework 4 Client Profile" and "

"Microsoft .NET Framework 4 Extended".


Me too. I was force to upgrade to 7.6 because the bug fix didn't make the 7.4MR2. Really love this tool. Please please Javier.

Loc Pham
Level 1
Level 1

WLC-crash.jpg  Running into this error upon open a WLC 5760 configuration, I already check 4.0 net.

  What should I do ?

John Ventura
Level 1
Level 1

great document. 

Level 1
Level 1
The config analyzer does not yet support the 5760 platform.
Emanuel Diaz
Level 1
Level 1

I agree. Thanks for keeping it up to day, Javier.

Level 5
Level 5

Hi guys,

A question about the Channel Utilization number reported by the APs in the "show run-config" command (and shown in the WLCCA tool under the RF Summary tab).  The numbers reported by the APs are routinely higher than the utilization percentages I see when walking the same area using Cisco Spectrum Expert/Cognio.  I'd guess they are easily 20% higher than my "eyeball estimate" from CSE, but I've honestly never done a side-by-side comparison.

How is the reported Channel Utilization number derived on the APs?  Is it a timed average (such as a 5-second or a 60-second average), or is it a high-level watermark over the last N seconds?

I'm working with a customer where we are relying on these numbers (collected from the WLCCA tool) to determine which changes are having a positive impact -- and by how much.  More than 45% of their APs are reporting channel utilization over 50%, and at least 15% of the APs are reporting channel utilization higher than 70%.  Compared to other customers I've worked with, those numbers are pretty bad (although they are a distant second to my worst customer, but they are a developer of consumer-based wireless products so that wasn't too much of a surprise with thousands of "rogue APs" being present).

Thanks in advance, as always!


Level 1
Level 1

Some comments which may help Steve:

1) We have noticed the same thing with the Fluke Aircheck (vs CPI / WLCCA)

2) Make sure you are looking at both WiFi and non-WiFi channel utilization with the Spectrum tool (which you probably are using a spectrum tool as oppose to a 'WiFi analyzer')

3) APs are mounted on the ceiling will generally hear more than you walking on the ground with a laptop. (This would lead to higher channel utilization)

4) AP may or may not have higher antenna gain (This would lead to higher channel utilization)

5) RSSI threshold to consider the channel utilized could be different between tools. e.g. The AP says channel utilized if WiFi  packets = -85dBm or stronger, or non-WiFi (& off channel WiFi) energy needs to be -65dBm or stronger (give or take a few dB) What thresholds does Cisco Spectrum Expert/Cognio use?

6) Technical differences in energy sampling methods. DFT vs FFT, filter shapes, etc. could mean you'll get differences in channel utilization between different devices.

7) There is a running averaging involved in the AP utilization number (likely ~60 seconds).

Bottom line is for any optimization, stick to the same sampling method to determine the affect of your changes. Shouldn't matter which one is technically more accurate, an improvement should be an improvement regardless.

I'd probably recommend sticking to the AP numbers as this is what the AP deems to be reality. If you make positive change as measured by CSE but the AP shows the same, then you probably didn't improve the WiFi performance.

If you wanted to discuss how to make changes to lower utilization that would be another discussion.

Hope this helps!

- Dale Hurshowy P.Eng

Level 5
Level 5

Dale, thanks for the feedback!  You bring up a good point about the potential for an RSSI threshold difference between tools -- where one tool might use one value, while the Cisco APs use another to calculate the channel utilization.

I guess I'm still facing the same question as before though: How is the reported Channel Utilization number derived on the Cisco APs?  Is it a timed average (such as a 5-second or a 60-second average), or is it a high-level watermark over the last N seconds?

I really want to know the answer to this, so if anyone knows for certain please let us know!


Level 4
Level 4

Hi Javier,

Thanks for creating this great assessment tool.

Some wish list items:

1. Have the "Compensated Heard Power" in the TX Neighbors reflect the selected APs Transmit Power.

2. Include AP Power, Compensated Heard Power values in the exported AP Nearby/AP Seeme reports in Report Center.

3. A Third loudest Seeme neighbor report.

Thanks for your efforts,

--Bruce Johnson

Javier Contreras
Cisco Employee
Cisco Employee

hi Bruce


Thanks for your comments


on your wish list: yes, they are valid points, let me put them on the tracking list for future version 3.7



Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: