WCS 6.0.132 compatibility

Is this version of WCS compatible with a Controller using 5.2.193? I've checked the released notes and for Controller 5.2.193 it says it needs WCS 5.2.130, but is 6.0.132 WCS also compatible?
Thanks in advance!

Yes 6.0.132.0 is compatible with controller 5.2.193.0

Similar Messages

Can't add Controller over VPN in WCS v6.0.132.0

Hi
I use WCS v6.0.132.0 to manage my 4402 and 2106 controller both running version 6.0.182.0
When I try to add another 2106 over DM-VPN it fails with the following errors:
”No response from device, check SNMP communities, version or network for issues”
If I move the new 2106 controller to LAN with same config there is no problem.
I found this note in the in “Cisco Wireless Control System Configuration Guide, Release 6.0”
“Note If you are adding a controller into WCS across a GRE link using IPsec or a lower MTU link with multiple fragments, you may need to adjust the MaxVar Binds PerPDU. If it is set too high, the controller may fail to be added into WCS. To adjust the MaxVarBindsPerPDU setting, do the following:
1) Stop WCS.
2) Go to the location of the Open SnmpParameters.properties file on the server that is running WCS.
3) Edit MaxVarBindsPerPDU to 50 or lower.
4) Restart WCS.”
On my system I have the “SnmpParameters.properties” file is located //WCS6.0.132.0\webnms\classes\com\cisco\server\resources
But I don’t have “MaxVarBindsPerPDU” settings in the file.
Beside some # explanations text, the only settings I have in the “SnmpParameters.properties” file is:
DebugEnabled                         false
SerializeRequests                    true
MaxRepetitions                       10
MaxRetryTimeout                      60
WlanTimeoutMsecsPerAP                 50
I have tried to add “MaxVarBindsPerPDU” settings, but it have no effect.
Anyone have an idea what to do?
TIA

Thank you so much!
Step 1 solved the issue.
I changed “Maximum VarBinds per Get PDU” from 30 to 20 and “Maximum VarBinds per Set PDU” from 50 to 20.
Thanks

WLC 5.2.193.0 with WCS 6.0.132.0 a supported config?

I know of a large site (not one of mine) that is running WLC 5.2.193.0 code paired up with WCS 6.0.132.0. The release notes for each product make no mention of support for this configuration.
Is this is supported configuration?

Thanks to both of you who replied. I just need to ensure that Cisco will support this scenario. The larger site is actually a "parent" site, and we try to keep our configs in parallel, but I'm not going to put the smaller site into an unsupported configuration.
I found this document, updated September 1st, which still doesn't list WLC 5.2.193.0 and WCS 6.0.132.0 as a supported config:
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a0080af7140.shtml

WCS 6.0.132.0 Error

Hi,
I have a problem with WCS 6.0.132.0.
I get every time I press a link a popup with error: "System Error: Wrong Alarm Type rogueUnclassifiedMinor"
Is this a bug?
Any idea to solve this?
Thanks in advance

Hi Juan,
This bug was supposed to be fixed, but it looks like it may have crept back in 6.x;
CSCsr02317 Bug Details
Getting error message for alarm dashboard after upgrade from D3MR2 to F
Symptom:
Receive error popup constantly that states the following:
System Error: Wrong Alarm Type rogueUnclassifiedMinor
Conditions:
After upgrading the WCS this happens
Workaround:
Clear the browser cache and cookies. Then restart browser and the error message should go away. Status
Fixed
Severity
4 - minor
Last Modified
In Last Year
Product
Cisco Wireless Control System
Technology
1st Found-In
5.1(63.0)
5.1(65.4)
Fixed-In
5.2(44.0)
Hope this helps!
Rob

Reporting in WCS 6.0.132

I recently upgraded from WCS 5.2 to 6.0. I have a number of Client Count reports set up, which are run weekly to generate PDF graphs of usage on all APs in each building. Since the conversion, all of them fail with the message "Failed to run report". I've tried deleting and re-defining them, but get the same result. Running them manually makes no difference. Has anyone seen anything similar? Is there anything I can do, or is reporting just broken in 6.0? The message is singularly unhelpful
Regards
Max Caines
University of Wolverhampton

Have you used a beta version or earlier pre release version?
You have an issue that is related some how to entries that were in beta codes of WCS.
A few things to try, first make a backup of your db.
Then, go on the CLI, bin folder of WCS and after run:
1.StopWCS
2.dbamin checkschema
3.StartWCS
See if this helps.
I dont want to push you for opening a TAC case and would like to avoid it, but if you are concerned about keeping the same db and not loose any data, we need a TAC case to be opened. That will involve that you upload me your database so we can try to fix this manually.
If you dont care about the DB and you are ok to rebuild it then from the CLI
1. StopWCS
2. dbadmin reinitdb
3. StartWCS
Reconfigure your WCS, the issue will be gone.
If you decide that you can not loose the db and the previous steps did not help, open a TAC SR between now and the next couple of hours and ask for lavramov, I can help you out.

WCS 6.0.132.0 Database

Hello,
I've been having some problems with the linux version of WCS. Sometimes, and I still don't know why the Database server stops. To activate it again I need to restart the service using the WCSStart script. Is anyone having similar problems? The service can work for two weeks or a month... then it just stops.
Best regards

Hello,
my database stoped working again... It happened last night.
I got this output from the WCSStatus script.
"Health Monitor is running.
WCS is initialized, but is not serving web pages.
The Server seems to be unavailable. The possible reasons are
1. The server is not running yet.
2. The server is hanging.
3 The server has crashed.
If the server has crashed or is hanging
Please report the issue and follow the instructions to restart it.
1. Run StopWCS to stop all WCS processes.
2. Run StartWCS to start the WCS server.
3. If the server still fails to start, or you still get this
message, then reboot the machine.
Database server is stopped
Apache server is running"
So I think the DBAdmin didn't solve the problem. Any next steps?
Thanks for your help.
Tiago

Anyone running WCS 6 on CentOS 5?

I ran into an issue when trying to install and run WCS 6.0.132.0 on a clean install of CentOS 5 (2.6.18-194.3.1.el5.centos.plus)
After successfully installing WCS using the option "-DCHECK_OS=false" I tried to start the WCS service with the startupscript as root, but got the following error:
[root@wcs WCS6.0.132.0]# ./StartWCS
Starting WCS
The Server seems to be unavailable. The possible reasons are
1. The server is not running yet.
2. The server is hanging.
3 The server has crashed.
If the server has crashed or is hanging
Please report the issue and follow the instructions to restart it.
1. Run StopWCS to stop all WCS processes.
2. Run StartWCS to start the WCS server.
3. If the server still fails to start, or you still get this
message, then reboot the machine.
failed to start WCS on startup Health Monitor
Failed to start WCS. Check hm_launchout.txt for details.
Log files are located under webnms/logs in the WCS install directory.
[root@wcs WCS6.0.132.0]# cat webnms/logs/hm_launchout.txt
JAVA_HOME=./../jre
Starting Health Monitor as a primary
Checking for Port 8082 availability... OK
Starting Health Montior Web Server...
Health Monitor Web Server Started.
Starting Health Monitor Server...
Health Monitor Server Started.
[root@wcs WCS6.0.132.0]#[root@wcs logs]# cat launchout.txt
Invalid OS version detected, can not start Xvfb.
JAVA_HOME=./../jre
Checking for Port 21 availability... OK
Checking for Port 8456 availability... OK
Checking for Port 8457 availability... OK
Checking for Port 1299 availability... OK
Checking for local Port 1299 availability... OK
Checking for Port 6789 availability... OK
Checking for local Port 6789 availability... OK
Checking for UDP Port 69 availability... OK
Checking for Port 8005 availability... OK
Checking for UDP Port 162 availability... OK
Checking for Port 8009 availability... OK
Starting RMI registry on port 1299
Registry started.
DB is already started
Starting NMS Server...
the only error I can interpret is the "can not start Xvfb", but my google foo does not yield any results for this issue, so:
Anyone here successfully running this configuration?
Best regards
-LA
PS: I do realize this is not a Cisco supported OS, but I would like to try it before falling back to RHEL

Editing /etc/redhat-release should allow WCS to start. I run ours on CentOS 5 and I had to make this change.
Just comment out the CentOS line and add the Red Hat line below. You will probably need to be root to do this and
it may require a restart. Also after running updates for CentOS I have notice that the file usually changes back
and WCS does not start again. I keep a copy of the file on the server desktop and copy it over after the updates.
I have not notice any issue with running it on CentOS, just thought I would throw that out there.
Cheers!
Eli
Red Hat Enterprise Linux Server release 5 (Tikanga)
#CentOS release 5.4 (Final)

Can't Modify WCS Report File Destination

Once I upgraded to WCS 6.0.132.0 I can no longer change the destination file location when I run reports. The reports seem to run on schedule but they end up in the default location of C:\WCSFTP\reports\. I would like to change that to my E: where I have more space to save reports. Before version 6.0.132.0 I was able to do this.

Oops, I sent the wrong screenshot.
Go to administration -> settings and you can change the folder there.
You can not customize the file name but surely you can change the location to save the files.
See file attached.

Upgrading WCS from 4.2.62.11 to ?

Hello All,
I recently purchased 6 1142 AP's and added them to my controller, well since these are not LWAP but instead CAPWAP AP's they were not supported by my WLC with code version 4.2 (not the end of the world) so I upgraded the WLC to code 6.0.182 but had to sacrifice managing it from my WCS.
Now I would like to upgrade my WCS to support managing this WLC again and potentially upgrading my remaining WLC's, the thing is I would like to upgrade to the latest WCS version 6.0.132 but need some input as to the ease of upgading, and/or any potential problems that might surface, or if anyone is currently experiencing any issues using this WCS code. Will 6.0 be the best bet or is it sufficient to step up to 5.2? Are you satisfied with this upgrade? How many WLC and AP's are you managing? Is there anything I need to consider that isnt written in the Cisco documentation?
Any input would be greatly appreciated.

You do need WCS 6.0.132.0 to manage your 6.0.182.0 WLC.
To upgrade, its easy, just make a backup of your db, run the installer of 6.0.132.0 and you will be all set. There are not really issues in the upgrade and this should go smooth.
WCS 5.2 will not support your WLC running 6.0
WCS 6.0.132.0 release note:
http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN6_0.html

Upgrading Wireless Infra.

Hi Experts,
I am planning to upgarde current Cisco 5508s and Cisco WCS. We have currently 1142n APs (around 400) and we will be adding 3600 APs to existing network.
I am planning to move from current code to the latest code and I would like to know any considerations or if anyone has done similar upgrades and can share their experience, any bugs or issues encountered.
WLCs 5508 upgrade from 6.0.182.0 (current) to 7.0.220.0 (Intermediate) and the to 7.4.100.60 (Final) with FUS upgrade from 1.3 to 1.7
WCS to Prime Infra 1.2 : WCS 6.0.132.0 (current VM) to 7.0.220.0 then install new NCS 1.1.1.24 (VM) and migrate WCS data to NCS 1.1.1.24 and finally upgrade NCS 1.1.1.24 to Prime Infra 1.2.1.12 (VM) and decommision WCS. I will apply license after upgrade to Prime Infra. (WCS to Prime migration license).
Please share your thoughts.
Thanks in advance.
hardik..

All sound good, If you want to prepare for down the road technology (if is a big structure) you should think that for every 3 ap keep one as 1142, and two of 3600 then in the future you could add the 802.11ac module and the next Wi-Fi/Micro Cell DAS module for 3600 (Still on the works) that should be available Oct-Dec time frame... By using 7.4 or higher on WLC & MSE with Prime 1.3 or higher you will add some other capabilities to your network (Cisco Connected Mobility Experience CME-CMX http://www.cisco.com/en/US/netsol/ns1205/index.html )
If you have any question, comments or concern please contact me...
Thank you,
Manuel Baez
Sales Eng
Need help ? call Sales Acceleration Center(SAC) at Toll Free (USA) :1-800-225-0905 International +1-408-902-4872 or send email to [email protected] or Live Chat: http://tinyurl.com/sacucs

WLC Wired and Wireless Guests

I am using WCS 6.0.132.0 and WLC 6.0.188.0. I am creating guest ID's using the LobbyAmbassador interface, and I would like to allow guest users to use the same ID password either wired or wireless. I cannot see any way to accomplish this, am I missing something? If I use an external Radius server, would that allow me to do it? If I do add a Radius server, do the ID's created in Lobby Ambassador 'flow' to the radius server, or do I need to use the new server interface (whatever it may be) to create them? I know it is a lot of questions, but I am dealing with a few hundred guest users a week, and I am trying to avoid a lot of extra work for staff and inconveience for guests.

If you are using lobby admin to create username and passwords, then you would be creating this on a WLC, either on a foreign or anchor controller. Username and password can be used on either, since the WLC DB has all the info. No need to have a radius unless you do not want to use the lobby admin feature and have your internal IT staff create username/passwords in AD or the local radius DB if it has one. If the username will be used concurrently, then make sure Max Concurrent Logins for a user name is set to the # of concurrent users.

Lobby Ambassador account

I am running WCS 6.0.132. I have a Guest User account where I as the Administrator change the password. I setup a Lobby Ambassador account so I can have our helpdesk change the password. However When I login as the Lobby Ambassador I can not see the guest user account.
What am I missing in the configuration?

There was a version of WCS where they changed how the accounts were visible. I do believe there was a bug in it. I'm just going off of memory of us having a similiar issue and that version is a few rev's old. I would recommend upgrading to the newest version and see if it resolves the problem.

WLC code upgrade path questions

We running WCS 6.0.132(lastest) and our controllers are on 4.2.130, we now want to upgrade to keep up with the times, but don't want to change over to capwap yet.
Question1:What's the latest LWAPP release code??
Question2:Whats the differences between 4.2.207 (cisco's support page says this is the latest release) but there's even releases with much higher versions ie 6.0 how does this work it's very confusing to workout an upgrade path
Cheers

Hi Tyrone,
I'm not an expert on Versioning but here are some basic details in response
to your query
4.2.207 is the latest release on the 4.2 Train and is probably an excellent choice
if you are avoiding CAPWAP for the time being. You will see in the link below that
there are multiple "simultaneous" Trains for the WLC (and most Cisco products). People
were not huge fans of the early 5.x Trains (quite buggy) and CAPWAP was introduced
in 5.2 and forward so this is why 4.2.207 seems like a good fit for you
In controller software release 5.2 or later, Cisco lightweight access points use the IETF standard Control and Provisioning of Wireless Access Points protocol (CAPWAP) in order to communicate between the controller and other lightweight access points on the network. Controller software releases prior to 5.2 use the Lightweight Access Point Protocol (LWAPP) for these communications.
CAPWAP, which is based on LWAPP, is a standard, interoperable protocol that enables a controller to manage a collection of wireless access points. CAPWAP is being implemented in controller software release 5.2 for these reasons:
      To provide an upgrade path from Cisco products that use LWAPP to next-generation Cisco products that use CAPWAP
      To manage RFID readers and similar devices
      To enable controllers to interoperate with third-party access points in the future
LWAPP-enabled access points can discover and join a CAPWAP controller, and conversion to a CAPWAP controller is seamless. For example, the controller discovery process and the firmware downloading process when you use CAPWAP are the same as when you use LWAPP. The one exception is for Layer 2 deployments, which are not supported by CAPWAP.
You can deploy CAPWAP controllers and LWAPP controllers on the same network. The CAPWAP-enabled software allows access points to join either a controller that runs CAPWAP or LWAPP. The only exception is the Cisco Aironet 1140 Series Access Point, which supports only CAPWAP and therefore joins only controllers that run CAPWAP. For example, an 1130 series access point can join a controller that runs either CAPWAP or LWAPP whereas an 1140 series access point can join only a controller that runs CAPWAP.
http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a008064a991.shtml
4.2.207 was released 24/Jul/2009 which does make it the second newest version available in any train.
http://www.cisco.com/en/US/products/ps6366/prod_release_notes_list.html
Cheers!
Rob

WCS & WLC version compatibility

Are there any compatibility issues between WCS version 7.0.164.0 and WLC version 7.0.116.0?

Hi Jason,
Table 1 WCS Versions
WCS Version Supported Controller Versions Supported Location Server Versions Supported MSE Versions Release Date Upgrade Supported From Operating System Requirement
7.0.172.0
7.0.116.0
7.0.98.218
7.0.98.0
6.0.202.0
6.0.199.4
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.202.0
7.0.201.0
April 2011
7.0.164.3
7.0.164.0
6.0.202.0
6.0.196.0
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
7.0.164.3
7.0.98.0
6.0.202.0
6.0.199.4
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.103.0
7.0.105.0
December 2010
7.0.164.0
6.0.196.0
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
7.0.164.0
7.0.98.0
6.0.202.0
6.0.199.4
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.103.0
7.0.105.0
June 2010
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.202.0
6.0.202.0
6.0.199.4
6.0.199.0 (pulled from CCO)
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.202.0
6.0.202.0
April 2011
6.0.196.0
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.196.0
6.0.199.4
6.0.199.0 (pulled from CCO)
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.102.0
6.0.105.0
15 July 2010
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.181.0
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.101.0
6.0.103.0
17 Feb 2010
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.170.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.97.0
6.0.97.0
8 Nov 2009
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.132.0
6.0.182.0
6.0.108.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.85.0
6.0.85.0
11 June 2009
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.2.148.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.2.100.0
5.2.100.0
25 June 2009
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.2.130.0
5.2.178.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.2.91.0
5.2.91.0
21 Feb 2009
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.2.125.0
5.2.178.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.2.91.0
5.2.91.0
10 Feb 2009
5.2.110.0
5.1.65.4
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.2.110.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.2.91.0
5.2.91.0
24 Nov 2008
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.1
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.1.65.4
5.1.163.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.1.35.0
5.1.35.0
9 Jan 2009
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.1.64.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.1.30.0
5.1.30.0
21 July 2008
5.0.56.2
5.0.56.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.1
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.0.72.0
5.0.148.2
5.0.148.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.38.0
Not Applicable
5 Aug 2008
5.0.56.2
5.0.56.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
Windows 2003 SP2 32-bit
RHEL 5.1
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.0.56.2
5.0.148.0
4.2.61.0
4.1.x.x
4.0.33.0
Not Applicable
14 Apr 2008
5.0.56.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
Windows 2003 SP2 32-bit
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.0.56.0
5.0.148.0
4.2.61.0
4.1.x.x
4.0.32.0
Not Applicable
16 Feb 2008
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
Windows 2003 SP2 32-bit
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.128.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.43.0
Not Applicable
13 May 2009
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0
RHEL 5.0 (5.1 and later no supported)
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.110.0
4.2.176.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.42.0
Not Applicable
29 Sep 2008
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.97.0
4.2.176.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.38.0
Not Applicable
3 Jun 2008
4.2.81.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0
RHEL 5.0
Windows/RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.81.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.36.0
Not Applicable
17 Mar 2008
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.62.11
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.35.0
Not Applicable
25 Jan 2008
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0 Update 5
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.62.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.35.0
Not Applicable
9 Nov 2007
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0 Update 5
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN7_0_172.html
Cheers!
Rob
PS: +5 to my friend Leo using the invisible Stars

AP - WLC - WCS - Compatibility

I'm upgrading a WLC4124 wireless controller to a WLC4402 - 50 and hope to use the existing AP1030's I have already installed. I have new AIR-LAP1131AG-A-K9 models to add to the existing AP1030's. I also would like to control this with WCS. My question is where do I find compatibility information with regards to what version of WCS, WLC code(?) and AP's / AP modes (L2,L3) work together?

you can find controller / wcs version in the WCS config document.
http://www.cisco.com/en/US/products/ps6305/products_installation_and_configuration_guides_list.html

WCS 6.0.132 compatibility

Similar Messages

Maybe you are looking for