06-11-2009 12:26 AM - edited 11-18-2020 02:22 AM
The WLC Config Analyzer home has moved to Cisco DEVNET. See:
https://developer.cisco.com/docs/wireless-troubleshooting-tools/#wireless-config-analyzer
We also have a cloud version of the tool: https://cway.cisco.com/tools/WirelessAnalyzer/
(please use new forum for updates)
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.
http://www.microsoft.com/en-us/download/details.aspx?id=17718
News
Enhancements
Fixes
Fixes
Fixes
Enhancements
Fixes
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.
General Usage: wlc-conf-app@external.cisco.com (you can subscribe)
Bug reports/issues/features: wlc-conf-app-dev@cisco.com
Excellent tool, very helpful!
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.
Hi Dale
could you send me the sh run config? you can attach and email towlc-conf-app-dev@cisco.com
That would allow me to do local check on it
Thanks!
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,
Charles
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 :-(
regards
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.
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
Regards
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).
-Dale-
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.
Hi
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
Regards
Javier,
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
https://supportforums.cisco.com/docs/DOC-33276
Eric
Hello Javier,
I wanted to ask, if you plan to add support for the new IOS based WLCs as well?
Thanks
Regards,
Patrick
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
regards
I'm trying to install the latest version of the Configuration Analyzer on a Win 7 laptop and am getting below errors:
OPERATION PROGRESS STATUS
* [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=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil using Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil.
* [9/2/2013 1:18:05 PM] : Detecting dependent assembly System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil.
* [9/2/2013 1:18:05 PM] : Detecting dependent assembly WindowsBase, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=msil using WindowsBase, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=msil.
* [9/2/2013 1:18:05 PM] : Detecting dependent assembly System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Core, Version=3.5.0.0, 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.
ERROR DETAILS
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?
Thanks,
Mike
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).
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: