Welcome to the Cisco Networking Professionals Ask the Expert conversation. This is an opportunity to learn how to configure and troubleshoot WCS related issues with Cisco expert Lucien Avramov. Lucien is a Customer Support Engineer working in San Jose TAC center. He is a technical leader within the Network Management Team and has been supporting WCS for about 2 years. He handles world-wide escalations related to Network Management, including WCS. He has a Bachelor Degree in General Engineering and a Master's Degree in Computer Science from the French prestigious Ecole des Mines (Mining School). Lucien holds a CCIE in Routing and Switching (CCIE #19945).
Remember to use the rating system to let Lucien know if you have received an adequate response.
Lucien might not be able to answer each question due to the volume expected during this event. Our moderators will post many of the unanswered questions in other discussion forums shortly after the event. This event lasts through April 30, 2010. Visit this forum often to view responses to your questions and the questions of other community members.
This event is following the webcast about WCS:
Feel free to post questions.
Your license file seems correct for a MSE version 6.0.
Can you please upgrade your MSE to an MSE version 6.0 that will be compatible with your WCS and try again?
Here are the release notes of WCS, go to section : Location Server, Mesh, MSE
we have deployed:
- 2x WLCs 4402-50-k9 software version 184.108.40.206
- 1x WCS software version 220.127.116.11
- up to 25x 1242AG autonomous APs being migrated to LAP. Till now I have migrated 2 of them in the Production environment
- The solution is configured that all APs will register with the same WLC, the second one is secondary for all. The WLAN is the same than the one configured in the autonomous APs in order to facilitate a progressive migration, but it is a problem cos I found out that roaming is not allowed between a LAP and an autonomous AP. However, our application doesnt use a terminal session or telnet so is not a big problem. The only issue is that WLC keeps the client associated when the wifi client has already migrated from a LAP to the Autonomous AP, the result is some MAC flappings in the core. I configured the Idle Time Out the mininum 90s, still too high...
- WiFi clients are industrial ones, they dont support CCX.
My concern is about some logs that I see in the WLC and the WCS:
These ones happening all the time... (the MAC address belongs to one of the 2 LAPs
|12||Thu Apr 29 15:02:33 2010||Load Profile Failed for Base Radio MAC: 00:22:0c:25:68:40 and slotNo: 1|
|13||Thu Apr 29 14:56:33 2010||Load Profile Updated to Pass for Base Radio MAC: 00:22:0c:25:68:40 and slotNo: 1|
|14||Thu Apr 29 14:48:33 2010||Load Profile Failed for Base Radio MAC: 00:22:0c:25:68:40 and slotNo: 1|
|15||Thu Apr 29 14:27:34 2010||Load Profile Updated to Pass for Base Radio MAC: 00:22:0c:25:68:40 and slotNo: 1|
|16||Thu Apr 29 14:22:34 2010||Load Profile Failed for Base Radio MAC: 00:22:0c:25:68:40 and slotNo: 1|
|17||Thu Apr 29 13:00:34 2010||Load Profile Updated to Pass for Base Radio MAC: 00:22:0c:25:68:40 and slotNo: 1|
And these ones happening randomly:
|85||Wed Apr 28 14:35:35 2010||Decrypt errors occurred for client 00:02:6f:5c:2b:f6 using WEP key on 802.11a interface of AP 00:22:0c:25:68:40|
- Please note that Roaming may happen only INTRA-CONTROLLER, or a "false roaming" between LAP and Autonomous (or opposite)
Q1- Could you bring some light about how to interprete the above messages, and in case, solve them?
Q2- Shall I migrate the other 23 autonomous to LAP in a single migration or better can I follow on with a progressive migration??
thanks a lot for your help!!
Looking at the errors, refer to this useful document:
Your load profile failed error message is also knowned as : LRADIF_LOAD_PROFILE_FAILED
A radio interface of an access point is reporting that the client load has crossed a configured threshold.
There are too many clients associated with this radio interface.
•Verify the client count on this radio interface. If the threshold for this trap is too low, you may need to readjust it.
•Add new capacity to the physical location if the client count is a frequent issue on this radio.
For your WEP error: it means that when the AP decrypts a packet received from a client with the key it should be received, the packed contents were not recognizable after decryption. This could be due to the client using an incorrect key. The packet was therefore encrypted incorrectly with a flawed algorithm, or the packet was corrupted in transit or decrypted improperly. I do suggest that you make sure your client is using a latest wireless driver and that the wireless encryption configuration is properly configured on the client and WLC.
The error does not affect the client authentication and connection but produces a lot of messages in the trap logs. You can disable the error message from: WLC GUI -> Management -> SNMP -> Trap Console -> 802.11, Security traps. Uncheck WEP decrypt error.
On a side note I don't recommend you to use 5.1 code on WLC / WCS. I strongly encourage you to think about upgrading to 6.0 codes.
I want to disable 802.11b but leave g/n prevent old legacy b devices from greatly slowing n preformance.
I have been told that to disable b and leave g/n, that I should go to 802.11b/g/n Parameters and disable the 1,2, 5.5 and 11 Mbps data rates.
Is that the best way to do it?
WCS version is 18.104.22.168 and my WLC 5508 is running 22.214.171.124
On WCS, go to Configure -> AP Configuration Template -> Lightweight AP
Select the radio tab and check the checkbox admin status and leave enable unchecked to have a radio shut down.
I attach here a screenshot to illustrate it.
Also take a look at the AP template configuration guide :
Good job last week.
Not a controller issue a such, but got 2 AP, 1200 and a 1240. Trying to convert these from LWAPP mode to autonomous, following the instrauctions on the cisco web site.
Using 3cdaemon for tftp server not anti virus or firewall enabled, but keep getting "could not oped requested file for reading" Tried this on 2 different PCs
Any help would be appreciated
2 things I'd like you to try:
- Install TFTPD (http://tftpd32.jounin.net/tftpd32_download.html) and try this tftp server. Make sure to select the proper folder where your image is.
- run a packet capture on the PC to see whats failing if you get the same error with TFTPD.
I have a problem I don't know how to solve with WCS 6.0 and MSE (Aeroscout engine) 6.0
I have many tags around moving.
When I tried to locate a tag on a WCS' map the system reports:
"the floor reported by MSE could not be found in WCS.
Please synchronize your MSE(s)"
The synchronization is OK, the tag is on the system, but is not printed on any map.
Can anybody help me to troubleshoot the problem?
Thanks and best regards
Version - 126.96.36.199
Feature - Plus
AP Limit - 2500 (Actually 1151 APs registered)
Version - 188.8.131.52
Tag Elements Limit - 6000 (Actually 2398 tags counted)
2710 Location Server
Version - 184.108.40.206
1. We need to have your WCS and MSE version to be matching the release notes.
Either you upgrade WCS to 220.127.116.11 so it works with MSE 18.104.22.168.
Either you downgrade MSE to 22.214.171.124 so it's supported by WCS 126.96.36.199
2. Once this is done, go ahead and re-init the db of your MSE:
Under the MSE CLI:
mv /opt/mse/db/linux/server-eng.db /opt/mse/db/linux/server-eng.db.old
This should resolve your issue with the tags. Give 15 minutes for the tags to show on your maps after you re-sync the design and controllers with the MSE
Actually I have MSE version 188.8.131.52 (interim version solving a bug). I can't downgrade MSE because this bug.
The only solution is to upgrade WCS to 184.108.40.206. As I have MSE 220.127.116.11, do I need to upgrade MSE to 18.104.22.168?
MSE 22.214.171.124 has the bugs solved on MSE 126.96.36.199?
Thanks and best regards
Please upgrade the MSE to 188.8.131.52 as well. The bugs fixed in 184.108.40.206 should be fixed in 220.127.116.11 except if there is a regression which I highly doubt.
We've added a secondary DHCP server to our network so that if one fails or is taken down for maintenance, we don't have a gap in service. I need to add this new DHCP address to each interface for each controller in WCS. I have 4 WLC's with 9 interfaces per. That's 36 slow UI copy and pastes I'm not looking forward too. Is there a quick way to propogate this secondary DNS to all interfaces?
I've looked at Controller Templates and Controller Config Groups but can't seem to find my way through either to a solution to my situation. Can you offer any advice?
Use the controller template launch pad.
Go to System -> Dynamic Interfaces and create templates for your dynamic interfaces of your WLC and add the information regarding DHCP there and push it to the controllers.
Ok. In the teplate it seems I have to recreate each of the interfaces. Is this correct or am I missing something? That would be 4 fields by 9 interfaces (still 36 entries). I guess there isn't really a faster way except if someone had used a template in our initial deployment.
If you refresh your configuration from controllers, do you see any new template added?
If you did not use templates before, yes then you will have to make all those changes.
It's good practice to use templates from the beginning to avoid those large numbers of repetitive actions.
We are in the process of migrating our AP's from autonomous mode to Lightweight mode and are using the Cisco 3750 WLC and WC v 6.0S. The AP's are Cisco 1252's and 1121's. The issue I'm having is that when I convert the AP's using templates I loose any ability to have my clients connect at any 802.11n speeds on 1252's. i have the lastest versions of everything on all components and have checked everything I can think. What do you think I might have missed here? I've run it through WLC config anlyzer and theres no problems from that. What further info do you need?
Any assistance appreciated
I've answerewd my own question. I did not have WMM enabled under QOS for that WLAN.
Message was edited by: email@example.com
Example about how WMM works:
1. While Station X is transmitting its frame, three other stations determine that they must send a frame.
Each station defers because a frame was already being transmitted, and each station generates a
2. Because the Voice station has a traffic classification of voice, it has an arbitrated interframe space
(AIFS) of 2, and uses an initial CWmin of 3, and therefore must defer the countdown of its random
backoff for 2 slot times, and has a short random backoff value.
3. Best-effort has an AIFS of 3 and a longer random backoff time, because its CWmin value is 5.
4. Voice has the shortest random backoff time, and therefore starts transmitting first. When Voice starts
transmitting, all other stations defer.
5. After the Voice station finishes transmitting, all stations wait their AIFS, then begin to decrement
the random backoff counters again.
6. Best-effort then completes decrementing its random backoff counter and begins transmission. All
other stations defer. This can happen even though there might be a voice station waiting to transmit.
This shows that best-effort traffic is not starved by voice traffic because the random backoff
decrementing process eventually brings the best-effort backoff down to similar sizes as high priority
traffic, and that the random process might, on occasion, generate a small random backoff number
for best-effort traffic.
7. The process continues as other traffic enters the system. The AC settings shown in Table 2-3 and
Table 2-4 are, by default, the same for an 802.11a radio, and are based on formulas defined in
Look at page 2-11:
Great, Im glad you found this out, it is not an obvious thing to check at first.
Feel free to ask If you have any other questions related to WCS here.
We've got a member of staff wanting details on certain devies we have using wireless, is there a way of running custom reports on a group of devices?
We are using WCS 6.0.181.
Or is it possible to interrigate the database directly to get this information?
You can query the db directly, I encourage to look at the steps I mentioned on this webcast to do so:
You can run a database dump and then query the tables and make a sql script to get the data you need.
WCS 6.0 offers you a few options to customize your reports.
You can go to the report launch pad and there click on new and create your report. You cant select certain clients however you can select how to display them and sort them (by mac address for example), this can help you create reports that will display first the information required if sorted properly.
Attaching screenshots to illustrate.