WLC Config Analyzer


Jun 11, 2009 12:26 AM
Jun 11th, 2009

Wireless LAN Controller (WLC) Config Analyzer


1. Download


Click here to Download


To request access, send an e-mail to wlc-conf-app-dev@cisco.com. Please include your Cisco.com username. Cisco employees do not need to request.


  • New version 3.1.1 March 2014


  • You may need to install .NET 4.0before using it.External link to download:




2. News

March 21, 2014. Version 3.1.1


  •  Aplication 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




Webex Recording explaining the tool, how to use it, and some day to day field tips



Tips and Tricks



3. WLC Config Analyzer Checks


4. Support:

General Usage: wlc-conf-app@external.cisco.com (you can subscribe)

Bug reports/issues/features: wlc-conf-app-dev@cisco.com


5. Fixing Voice Error Messages


WLC Config Analyzer FAQ



How to Use



Average Rating: 5 (10 ratings)


Javier Contreras Wed, 09/30/2009 - 09:09 (reply to PatrickRepp)


I will be adding 6.0 specific checks to version 2.0 in the short future... please stay tunned

You can process 6.0 today, just no special checks yet.

kmiller1634 Wed, 09/30/2009 - 12:19

Javier, when I try to install it, it says that it's already installed, do you have any thoughts on this?

Javier Contreras Tue, 02/09/2010 - 08:58 (reply to Joseph.roble)

Hi Joseph

Two ways of doing it:

procedure 1

1. Opening different configuration sets. click on the first icon in the tool bar, load a config file

2. Click again on same icon, it should create a new window, open the second WLC

3. You now have 2 configs showing up in the screen, you can now compare manually

procedure 2

1.  put both config files on same text file

2. load them on the application (it supports up to 24 WLCs per config set)

3. It will do automatic comparision for mobility, wlan, interface, etc

if you load 2 times the same config, you will get several errors on duplicate addreses, system name and/or AP names, but sometimes people do it, so compare wlan configuration over time


muranskycotech Wed, 08/11/2010 - 15:28


Thanks for responding to my email last night about the easiest way to get started. I was able to use this tool to identify several weak areas in my configuration today, and thanks to the tips the utility provided, my wireless network (voice and data) are running better than ever! I noticed dramatically better coverage in a few areas where coverage had previously been low due to some radio misconfigurations, and my call quality while roaming is much improved as well since I was able to identify a few settings that were negatively impacting roaming abilities.

Thanks for this utility, and all your efforts on this project!

nichnw Tue, 12/14/2010 - 22:01

For some reason I'm not able to scroll the AP list in the TPC Prediction dialog.  Both scroll bars are disabled.  At first I thought it might be a Win7 thing but I've had the same issue under XP.  Am I doing something wrong?

Javier Contreras Wed, 12/15/2010 - 00:11 (reply to nichnw)


TPC predictor was a "experimental" test I did time ago for a case. It needs serious re-work, to match the new TPC algorithms in 7.0 and 6.0 latest code. The issue you mention, that the tabs and grid scroll bars are not responsive is fixed on next build (it was minor detail) , but I will disable the  feature altogether until I have time for  2.3   or 2.4  is out, when I plan to introduce several RF analysis ideas I have around.

the current output is not entirely correct. Anyway, if you have ideas or feedback for this feature, feel free to contact me to discuss inclusion on next version.


ericgarnel Tue, 09/06/2011 - 09:56


I cobbled together an expect script to pull the run-config from a controller and all looks well on the output, but config analyzer compains "controller information not found in selected file"  The scripts are at https://supportforums.cisco.com/message/3437283#3437283

I can modify them as needed, but I am not sure where the analyzer is looking for that info.


Eric Garnel

Javier Contreras Wed, 09/07/2011 - 02:02 (reply to ericgarnel)

Hi Eric

Can you send me the resulting output file from your script?

I can have a quick look and see what is missing.

Normally, that message means that WLCCA did not see the "System Inventory"  line on the beginning of the file

(that is used as marker for start or new config)


ericgarnel Wed, 09/07/2011 - 10:34 (reply to Javier Contreras)


I have cleaned up the scripts, and the analyzer recognizes the output, but kicks out parsing errors.

the updated info is at: https://supportforums.cisco.com/message/3438433#3438433

the raw output from the controller is 1 very long line with ^M^Ms sprinkled throughout.  In order to pull out the expect user pass & ip info, the file needs to be massaged

here is a sample of the output:

System Inventory

NAME: "Chassis" , DESCR: "Cisco Wireless Controller"

PID: WS-SVC-WISM-1-K9, VID: V01, SN: FAM121804PT

Burned-in MAC Address............................ 00:1F:CA:BE:C9:E0

Maximum number of APs supported.................. 150

System Information

Manufacturer's Name.............................. Cisco Systems Inc.

Product Name..................................... Cisco Controller

Product Version..................................

RTOS Version.....................................

Bootloader Version...............................

Emergency Image Version..........................

Build Type....................................... DATA + WPS

System Name...................................... WLCNORTH

System Location.................................. North.2nd_floor.Ntelecom

System Contact................................... Eric Garnel

System ObjectID..................................

IP Address.......................................

System Up Time................................... 86 days 3 hrs 41 mins 3 secs


dhurshowy Mon, 01/23/2012 - 09:41

It seems to run OK and outputs the warnings in a browser, but then the program hangs with the task box  "processing: Calculating AP Index" showing. The program is unresponsive and has to be shut down in task manager.

Windows 7 64bit.

Did not chose any audits.

Task manager does not show any processing happening.

Any ideas?

Edit: Since I manually installed .NET 3.5 and rebooted, the program no longer hangs, though it does show me an error message regarding the AP index. (don't know if it was the reboot or .NET that helped).

Config file sent as requested.

Thank you.

Edit 2: The problem as identified by Javier was an AP stuck in a half programmed state. Tried exporting from a different controller and everything worked normally. Thanks for the quick support, it was much appreciated.

luceroc Wed, 04/18/2012 - 15:56

Hello Javier,

Thanks for your hard work and efforts on this config tool. I have a suggestion that might be worth investigating but could be more trouble than it’s worth. I’ll let you decide. I have a guest network (SSID) on my controllers I’m sure like everybody else. When I look at my stats and clients below SNR levels, these are mainly these guests that are using low power devices and might even be grabbing it from next to my facility(read far away from the AP). But that’s another problem for another time. :-)

I was wondering if there’s a way to allow us to selectively exclude the guest SSID which would then allow me to just view my company assets and get the reading based on just those devices on my production SSIDs.

Forgot to specifically mention that the error is 90026,Vocera percentage of clients detected at poor RF coverage.

Thanks again,


Javier Contreras Thu, 04/19/2012 - 00:50 (reply to luceroc)

Hi Charles

     Thanks for the feedback and ideas....

     The SNR/RSSI levels are reported on a per-radio aggregation, not on per-SSID, so there is no direct way to exclude low SNR Clients, depending on which SSID they are...

     We can have how many clients are per SSID from the config, and how many are on the SNR historgram levels... but doing a correlation there, could lead to false negatives (like I can't just substract guest SSID from bad SNR totals... it would give bad results on most deployments)

      your proposal makes total sense... but the current agregation level present on the sh run does not allow that granularity :-(


dhurshowy Fri, 04/27/2012 - 10:19

In the RF summary I see the Client RSSI Distributions for the WLC.  Is there a way to see the RSSI distributions per AP? If not, the Client RSSI for the whole WLC (500 APs across an entire city for us) is of limited use when trying to figure out which APs/installations may need some additional APs added, or a redesign etc.

Javier Contreras Mon, 04/30/2012 - 04:21 (reply to dhurshowy)

Hi Dale

yes, the current RSSI/SNR summary is client focused, not AP, so  it is not useful to find out which APs may be having coverage issues.

RF problem finder does not focus on low SNR, nor the graphs...

so yes, if you want to get APs that have lower than average SNR/RSS count, there is no easy way right now in the WLCCA.

I think I can add a "average SNR" count, then show how APs deviate from this value.  I can explore this, as this tool may be done on different ways: either as SNR/RSSI summaries vs network average, or by a graph showing deviation, etc. Let me see what is best for a large network representation.

I think your usage case makese sense: quick check on which areas may need additional coverage based on persistant low SNR/RSSI count.

One detail: this is covered on WCS/NCS coverage area exceptions, and/or in CHD in WLC


dhurshowy Mon, 04/30/2012 - 08:05

Coverage Hole Detection is a good suggest, we had forgotten about that counter. While it would be nice to see AP RSSI info in WLCCA it would still just be a snapshot of a single point in time, so CHD would be better in that it would capture all clients thoughout the day. Thanks for the tip we'll explore that today.

If you were to add AP RSSI to WLCCA by showing APs deviations from average, it might also be good to show client count for each AP (so the stats/importance is weighted).


jcoune Fri, 05/11/2012 - 02:39

Question: are there also plans to add the settings for the radius server like "fallback mode" in the config analyzer?

We have customers with a few 100 wlc's and this option can be usefull.

Javier Contreras Fri, 05/11/2012 - 22:00 (reply to jcoune)


well, now there are plans :-)

it is a valid request, and makes total sense. Let me add this to the feature list for next releases


ericgarnel Wed, 05/22/2013 - 07:44


I have returned to the forums after a long absence and have started to update some of the scripts I wrote in the past

Here is verison 1 of the script to automate/perform a "transfer upload datatype run-config" to a tftp server for the sake of pushing the output to WLC Config Analyser



patrick.kofler Wed, 06/12/2013 - 06:03

Hello Javier,

I wanted to ask, if you plan to add support for the new IOS based WLCs as well?




Javier Contreras Wed, 06/12/2013 - 07:58 (reply to patrick.kofler)

Hi Patrick

yes for sure!

I am working on a 3.0 version, that will have support for 5760/3780... it is just matter of finding time to complete it

right now is on alpha version, with some missing features


gskkordek Mon, 09/02/2013 - 10:24

I'm trying to install the latest version of the Configuration Analyzer on a Win 7 laptop and am getting below errors:


* [9/2/2013 1:18:00 PM] : Activation of C:\Apps\WLC Analyzer\WLC Config Analyzer.application has started.

* [9/2/2013 1:18:01 PM] : Processing of deployment manifest has successfully completed.

* [9/2/2013 1:18:01 PM] : Installation of the application has started.

* [9/2/2013 1:18:01 PM] : Processing of application manifest has successfully completed.

* [9/2/2013 1:18:05 PM] : Found compatible runtime version 2.0.50727.

* [9/2/2013 1:18:05 PM] : Detecting dependent assembly Sentinel.v3.5Client, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil using Sentinel.v3.5Client, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil.

* [9/2/2013 1:18:05 PM] : Detecting dependent assembly System.Data.Entity, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Data.Entity, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil.

* [9/2/2013 1:18:05 PM] : Detecting dependent assembly WindowsBase, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=msil using WindowsBase, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=msil.

* [9/2/2013 1:18:05 PM] : Detecting dependent assembly System.Core, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Core, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil.

* [9/2/2013 1:18:05 PM] : Request of trust and detection of platform is complete.

* [9/2/2013 1:18:06 PM] : Downloading of subscription dependencies is complete.

* [9/2/2013 1:18:06 PM] : Commit of the downloaded application has started.


Following errors were detected during this operation.

* [9/2/2013 1:18:06 PM] System.Runtime.InteropServices.COMException

- The application binding data format is invalid. (Exception from HRESULT: 0x800736B2)

- Source: System.Deployment

- Stack trace:

at System.Deployment.Internal.Isolation.IEnumSTORE_ASSEMBLY.Next(UInt32 celt, STORE_ASSEMBLY[] rgelt)

at System.Deployment.Internal.Isolation.StoreAssemblyEnumeration.MoveNext()

at System.Deployment.Application.ComponentStore.CollectCrossGroupApplications(Uri codebaseUri, DefinitionIdentity deploymentIdentity, Boolean& identityGroupFound, Boolean& locationGroupFound, String& identityGroupProductName)

at System.Deployment.Application.SubscriptionStore.CommitApplication(SubscriptionState& subState, CommitApplicationParams commitParams)

at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)

at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)

at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

Does anyone have any thoughts on why this is happening?



mikealbano Thu, 11/07/2013 - 17:26

Not sure what the official way to submit a feature request is, but I'd really like to see the "compensated heard power" ported over to the "Highest Rx neighbor on-channel". Would be very useful for determining where too much CCI could occur. As it stands, I think the "Highest Rx Neigh. On Channel" is based on neighbor messages (power level 1).

imuratov Mon, 01/27/2014 - 09:33

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.


a-nilsson Fri, 02/14/2014 - 23:42 (reply to imuratov)

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.

klohse Tue, 02/11/2014 - 02:22


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.


Aaron Leonard Tue, 02/11/2014 - 08:56 (reply to klohse)

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".


locpSGccie Wed, 03/05/2014 - 15:07

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

  What should I do ?



Login or Register to take actions

This Document

Posted June 11, 2009 at 12:26 AM

Related Content

Documents Leaderboard