WCS 4.1.83.0 - WLC 4.1.171. inconsistencies

Hello,
we upgraded to the above systems in the following order:
WCS to 4.1.83
WLC to 4.0.217
WLC to 4.1.171 (+bootloader update)
Now we have the following issues:
the Controllers pushed the updates towards the APs. We can confirm the 4.1.171 on the APs via the WLCs, but the WCS does always show older versions in the AP summaries, which results in problems with template rollouts (f.e. because the WLC thinks, that a 4.0.xxx AP /controller combo is not able to handle the new 4.1 templates).
When we change an option of an AP via the controller and do an audit on the WCS, THEN the WLC shows the current AP software correctly.
Is is possible to do an general audit, so we dont have to do this on every AP individually?

What happens after you refresh the config from the controllers under WCS?

Similar Messages

I Ask About WCS count Client not same WLC

WCS count Client not same WLC as on WLC count client = 100
on WCS count = 23-23
Wireless Control System Version 5.2.148.0
WLC 7.0.250.0
http://postimg.org/image/9boldeqd5/
http://postimg.org/image/l482i9poz/

Your WCS should have a higher (or not equal) version to your WLC.
I wouldn't even consider troubleshooting WCS problems if your WCS is running 5.X because WCS/WLC firmwares 5.X are very, very buggy.

Update WCS inventory with a replacement WLC

Hi,
We are running WCS Version 6.0.181.0 and had a 5508 WLC fail that was connected to this WCS. The WLC was replaced and is running the same config and Software Version 6.0.196.0.
In WCS the old controller shows up as unreachable which you would expect, but with the new WLC online it does not see it at all. Is there somewhere that I need to change the MAC address or something for WCS to accept the new WLC?
Thanks
Tony

Thanks for that, this worked OK for me. Should you not be able to just update/audit the new one if it is called the same and has the same IP address therefore allowing you to push out the master config from WCS?
Tony

Does WCS come with the 5508 WLC?

Forum
I am providing a quote to a client for a wireless installation. I have two 5508 boxes and about 40 AP's on the quote, as well as associated SmartNet.
I was reading how the Cisco Unified Wireless Network is comprised of:
Controllers
Access Points
The Cisco Wireless Control System (WCS)
Cisco Mobility Services Engine
My questions are:
1. Does WCS come installed on the Controller? Is this something that the customer receives simply by virtue of the fact that they are purchasing the Controller? Or is this a separate piece of software with a cost?
2. What exactly is the Cisco Mobility Services Engine? What does it do that the Controller will not? How would I sell one to a customer?
Thank You
Kevin

WCS is a Windows 2003 application (so not "on the controller") that is completely separate and has to be purchased separately with different levels of licensing for different feature sets.
WCS is most useful when having several WLCs to manage and is offered when you buy a lot of stuff I think.
WCS alone brings better reporting features (graphs, pdf reports, ...) and maps to visualize everything.
MSE is a kind of "calculation appliance" that you link to your WCS to locate all clients and rogues in real-time on the map. Only that. But it's a cool enough feature :-) Without MSE you can only view one client at a time (when entering its mac address in the search field) on WCS maps.
Nicolas

Wireless Migration from WCS to NCS and MSE/WLC 7.0.230 to 7.2.110.0

Hello,
I'm in the process of ripping out all of my wireless network and putting a new one in and have a couple of questions regarding code compatibility between the NCS, WLC, and MSE.
My current infrastructure consists of Wism running 7.0.230.0 code, WCS 7.0.230.0 code, and MSE 7.0.230.0 code. I am planning on migrating my WCS over to NCS 1.1.1.24 while maintaining the 7.0.230.0 code on my WiSM and MSE. Does anyone know if this will function properly and maintain location services?
Also, I am going to be replacing my MSE (3350) 7.0.230 code with redundant MSE (3355) 7.2.110.0 code running high availability. Will I be able to import the backups/config from the 7.0.230 code onto the 7.2.110.0 new servers? Or would it be better for me to load my new servers (3355) with 7.0.230 code, import the backups, and then proceed with the upgrade to 7.2.110.0. What is the best way to migrate my CAS licenses over to the new servers?
Thanks for any suggestions.

Well here is the compatibility matrix:
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
As far as the MSE, I would probably downgrade it to 7.0.230.0 and then import the backup and then upgrade. I guess you can just try it at first if you want, it won't hurt. You can always clear it and then downgrade if you want.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0)

I have som Aironet LAP1131AG accesspoints, that after a upgrade to WCS 5.2 (including upgrade of WLC) will not rejoin the controller.
I have attached a dump of the console. The accesspoints will upgrade the image, if they are hardreset (by holding down reset for some seconds while rebooting), but they will end up i an endless quest to join (last good message is CAPWAP changed state to CFG)...
We have 100+ accesspoints that are unaffected by the upgrade, but 2 accesspoints are giving me the same problem.
Any ideas as what to try ?

Hi
We have 2 WS-SVC-WISM-1-K9 modules. Each able to handle 300 AP's. At the moment only one of the modules are in real production. Each module contains two WLC's (WISM controllers) each capable of 150 APs. At the moment we have 32 AP on WISM-1A and 75 AP on WISM-1B. All WiSM controllers are managed from a WCS with 500 APs licensed at the moment.
Output from dir:
AP001d.e556.bf84#dir
Directory of flash:/
3 -rwx 88598 Apr 22 2009 15:00:14 +00:00 event.log
4 drwx 128 Jan 1 1970 00:02:01 +00:00 c1130-rcvk9w8-mx
9 drwx 256 Apr 22 2009 12:15:03 +00:00 c1130-k9w8-mx.124-18a.JA1
7 -rwx 5144 Apr 22 2009 15:18:20 +00:00 private-multiple-fs
8 -rwx 232 Apr 22 2009 15:18:20 +00:00 env_vars
15998976 bytes total (9431040 bytes free)
In the last days I have tried deleting env_vars, private-multiple-fs and event.log. It seemed to remove the hostname previously configured on the AP, but didn't solve the problem...

WCS 7.0.164.0 - WLCs unreachable

Hi Guys,
For some reason overnight the WCS server can no longer reach the lan controllers.
They are on the same subnet and can ping both ways.
I tried deleting and re-adding but it still cannot find it.
I've tried rebooting everything and still doesnt work.
Anyone have ideas?

audit-1] Configuration Sync for device 10.60.43.253 started.
04/15/11 01:00:00.410 INFO [monitor] [audit-2] Configuration Sync for device 10.60.43.254 started.
04/15/11 01:00:14.410 ERROR [communication] [audit-1] [10.60.43.253] Unable to reach the device: 10.60.43.253/161 using SNMP version v2
04/15/11 01:00:14.410 INFO [config] [audit-1] ConfigSyncHelper auditSwitchTree:+controllerObj.getDeviceIpAddress() com.cisco.server.common.errors.DeviceUnreachableException: MEDIATION-2,10.60.43.253/161
04/15/11 01:00:14.410 ERROR [communication] [audit-2] [10.60.43.254] Unable to reach the device: 10.60.43.254/161 using SNMP version v2
04/15/11 01:00:14.410 INFO [config] [audit-2] ConfigSyncHelper auditSwitchTree:+controllerObj.getDeviceIpAddress() com.cisco.server.common.errors.DeviceUnreachableException: MEDIATION-2,10.60.43.254/161
04/15/11 01:00:14.410 ERROR [general] [audit-1] THROW
So it looks like i'll focus on SNMP?

EAPOL-key M2 with invalid MIC (WLC 4.1.171.0)

I have a lot of client in one configuration who have problem with the message:
EAPOL-key M2 with invalid MIC
Config:
4402-12 in 4.1.171.0 (and ER) sw release
AP1242 with 2 4941 in diversity mode
SSID in WPA-TKIP PSK and DHCP on the WLC.
A lot of client can't connect to the switch. With Intel card, i have try the lasted drivers, and it's ok, but with some device like Intermec on windows mobile, it's not working. You can look the trace in the file log.
Some idea ?

I just had a few problems with the same error. It turned out that this was an issue with the client device NEEDING the key to be entered in HEX (even though it would take an ASCII if you typed it). I converted the ASCII PSK I'd configured on the controller into HEX and entered it on the client, and it works fine. You might want to try that if you haven't already.

7920 jitter on WLC 4.1.171

Hi
We have 2 x 3750 with integrated controllers, 8 x 1131 AP's, and approximately 35 x 7920 phones.
We have an issue with Jitter and occasional phone freeze with no button response for approximately 1 minute.
We are using the following QoS settings:
WMM state: disabled
QoS level: platinum
DSCP: disabled
802.1p Tag: 7
We get the following readings from the phones:
=================
Average Jitter 40
Maximum Jitter 60
RSSI 50
=================
Average Jitter 35
Maximum Jitter 55
RSSI 53
=================
Average Jitter 75
Maximum Jitter 95
RSSI 44
=================
As you see Jitter is always above the 30ms recommended.
Any help would be really appreciated
Regard
David

Sounds like you don't have 3.01 or later deployed on the 7920s.
Suggest using 3.02. Some fixes in 3.01 due to IAPP and MBSSID w/ Airespace 4.0.
Will be some jitter when the phone is scanning off-channel, but will not be noticeable to the human ear.
Also some jitter when roaming from AP to AP depending on the authentication type.
For controller version, would recommend 4.0.217.0 or later.

How can I apply existing WCS "WLAN Config" templates to a new WLC?

We've been running a pair of WLC 4402s managed by WCS, thus we are still on the older 7.0.235.0 (WCS) / 7.0.235.3 (WLC) release. I'm trying to add an additional WLC 4402-50 as a hot spare. I first ran the manual setup steps to give it an IP in our range, and used the WLCs web page to set our SNMP communities and such to the values used by our existing WLCs, then I added the new WLC in WCS.
At this point I could apply most of the "Controller Templates" from our existing configuration to the new unit. However, I can not get it to take our existing interfaces nor our WLAN Configurations. How do I avoid needing to recreate these from scratch on the new WLC?
We only have four dynamic interfaces, and each WLC needs its own IP address for each interface, so I did manually add these via the WLCs web page. However, now when I go to the WCS' "Configure > Contoller Templagte Launch Pad" page, then select "WLANs > WLAN Configuration", I see my usual list of WLANs, but can't figure how to push them to the new WLC.
For all of the other templates on the launch pad, I can select a template, click the "Apply to Controllers..." button, and I get a list that has my existing two and also the new controller. I can select the new controller, and apply the template, and it succeeds.
Yet if I select a specific WLAN config, and press "Apply to Controllers...", the list that appears has only my existing two WLCs, not the the new one.
In small green type at the top it says, "Controllers configured with Interface/Interface Group - 'w-restricted' and selected RADIUS server(s), LDAP servers, ACL Name with rules and Ingress interface are shown."
I have already manually added the interface "w-restricted" to the new controller, and have added the RADIUS servers via the template used by our other two WLCs. Not sure what to do about "LDAP servers, ACL Name with rules and Ingress interface", as we don't have any ACL rules, nor use LDAP directly from the WLCs (as all user ID stuff is via RADIUS).
Any hints on what manual setup I should add to get the new WLC in the list for these WLAN Configs?
Thanks,
Steve

To be honest, if your only adding another WLC, your better off creating the interface and WLAN's manually. I don't like pushing out templates to create new WLAN's. I would use it to adjust an existing WLAN, but that would be it. To me it's safer. Also your new WLC is on the same code? If you really want to figure it out, I would manually add the interfaces first then refresh the co fog from the new WLC and then push out the WLAN SSID and see if it takes. If not, don't waste your time anymore and create it manually.
Sent from Cisco Technical Support iPhone App

License problem with WCS and WLC

Hi All,
I have planned to implement three WLCs and one WCS to manage them.
AP count is as below :-
     WLC #1     -     10 AP
     WLC #2     -     10 AP
     WLC #3     -     20 AP
When WLC #1 is down that connected 10 APs should failover to the WLC #3.
So at normal scenarion, WLC #3 should need 30 AP license; to failover WLC#1 APs properly to the WLC #3
My problem is, Can I load total AP license (40 license) to WCS without installing them to individual WLCs ?
If it is possible i can cut off the additional 10 AP license, required to the HA and failover.
or if I use a WCS may i need to buy additional 40 license to WCS seperately from 40 WLC license ?
Thanks,
Charith

Yes, you required to have seperate licences for WLC & WCS.
You cannot add WLC licence to WCS & vice versa.
HTH
Rasika

WCS Error when adding WLC

We have successfully been managing all our WLC's via WCS. Last week one of the 6500 WiSM Controllers stopped responding to config refreshes from the WCS. When re-freshing the WCS config from the controller got the error message - failed (see logs). Removed controller from WCS and re-added - now get different error - see attachment.
WCS version is 4.2.97
WLC version is 4.2.112
Doco says they are compatible.
WCS is successfully managing other WLC's on the same code.
Can any one help?

What I would do next is to go to the WLC that is having the issue. Delete all the community strings and recreate it. Make sure that you allow the network that the WLC is on. Also, you should change your RW from private..... it's like the first and default snmp RW string that tools use. Along with public as the RO.

Migrating WLC from existing WCS to another WCS

Dear tecahers:
We support a campus with 8 WLC with 600 APs managed by our own WCS.
Recently we are going to support a new site. They have 4 WLC with about 250 APs managed by another WCS.
What we want to do is migrate 4 WLC with 250 APs from their WCS to our own WCS, thus we can use our own WCS to manage all the WLC and APs.
My question is How can we migrate these 4 WLC from the existing WCS to our own WCS with the configuration and maps?
Any help would be really appreciated.
Regards,
Steven

Do you have enough licenses on the new WCS for the additional access points you plan to add ? As for migration, I recall there arent any migration tools from wcs to wcs. I recall there being tools for WLSE to WCS. Depending on how many maps you have, it shouldnt take all that long to import maps and place aps.
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

Management of WLC by two WCS

Hi,
Can one WLC be managed by two WCS?...
There is central WCS and two local WCS in the environment.The local WLC is managemed by local WCS.Now,we want to manage the local WLC through central WCS..So, can one WLC be managed locally and centrally?..We are using WCS 5.1 version...Kindly help urgently...

thanks...
But my question is can one WLC be managed by two WCS?...If yes, then can both WCS be of different version?..
please help...

Resetting WLC password through WCS

Hi,
Can someone please provide me with the steps to follow to reset the WLC credentials using WCS.
Best Regards,

Is there a reason you want to change the password from the WCS and not from the WLC? If you are locked out, here is a good link from George's blog
http://www.my80211.com/home/2009/12/27/recover-your-wlc-password.html
I tend to add another management user from the WLC or WCS and then you delete the old username and create it again with the new password.
Sent from Cisco Technical Support iPhone App

WCS 4.1.83.0 - WLC 4.1.171. inconsistencies

Similar Messages

Maybe you are looking for