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

Similar Messages

WLC/WCS vs WLSE

ok..
I'm looking at these solutions and I'm very puzzled why I would purchase a WLC/WCS/AP vs a WLSE/AP solution.
First with WLC, i have to deploy multiple WLC's to get global redundancy. Don't need that with AP/WLSE combo. WLSE isn't a global failure point that takes down all my AP's.
Second, While deploying a WLC is easier as WLSE takes an ACS server and ability to read and deploy WDS services, I can buy a WLSE and ACS server/hardware for less than the cost of one 4400 controller.
Third - WLSE handles 2500 access points, does heat maps, something I would have to spend extra money and buy WCS for with the WLC. WLSE does the auto-reconfiguration and site survey.
Seems to me WLC is similar to cars where they took the gauges out and just give you warning lights way of deploying wireless. Don't worry about what it does, just put it in and only pay attention if a red light appears while WLSE takes more knowledge of ACS and WDS, shows you more details, gives you greater control, autonomy and failure redundancy.
Did I miss something??? It seems like WLC is 3 times as expensive yet doesn't provide anything other than easier deployment.

Hi,
Thank you Rpaquin, I also need answer which is better and which one is more sutabile for small wlan ?
Regards
Saher

WLC, WCS

Sorry I am new with WLC. Can we access WLC from WCS? Are they the same functions? how is the differents WCS vs WLC?
Thanks

WLC controls LWAP-imaged WAP.
WCS "controls" the WLC.
WCS can do more than just controlling WLC. They can do this fancy "reporting".
If you are new to WLC/WCS then I'd recommend you look at Cisco Prime Network Control System. It comes in two "flavours": appliance or VMware.

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

Certificate problem (webauth and WLC/WCS login pages)

Hello,
When I try to web in to the WCS or the WLC controls I get a message saying that the certificate could not be verified. I can add it into the trusted CA on IE6 but the message will still pop up anyway. It also says "The name on the security certificate is invalid or does not match the name of the site".
This problem is also happening for the WebAuth login page. This is more critical for me, as we have two WLANs which require WebAuth. When the clients use IE6 or Firefox it's not an issue, but when using IE7 it seems to randomly drop their connection due to the certificate being viewed as 'invalid' by the browser, forcing them to reauthenticate. I need to get this figured out and resolved so that the wireless webauth network is more reliable - I can't expect people to not upgrade to IE7.
Has anyone managed to get through this problem without purchasing a valid certificate from a CA like Verisign? Let me know please!
Thanks,
Jeff
P.S. My WCS is version 4.0.97.0 and I just upgraded my WLCs to 4.0.217.0 with plans to upgrade to the new 4.1.171.0 in the next week.

Recieved this from TAC which may play into your issue.
The description of the Microsoft post-login bug is as follows but we have the code with this fix in the attached:
There is known bug filed with Microsoft in reference to the tag. There
is also one with Netscape. The work-around is below:
The Pragma statement fails in IE because of the way IE caches files.
There is a 64K buffer that must be filled before a page is cached in
IE. The problem is that the vast majority of the pages using the Pragma
statement put it between the HEAD tags.
The HEAD loads and the Pragma comes into play. The browser gets the go
ahead to not cache the page, however there is not yet a page to not
cache. Since the page hasn't filled the 64K buffer, there's no page so
the Pragma is ignored. Thus...the page is cached.
The solution is to play to the buffer. If you're really serious about
the Pragma working, place another set of HEAD tags at the bottom of the
document, before the end HTML tag and re-enter the Pragma. This is a
suggestion straight from Microsoft Support. The page would look like
this:
Text in the Browser Window

WLC & WCS - who was logged in...

Hello,
I need to know which users used our wireless lan on sunday. To connect to the wlan they have to type in the wpa2 networkkey and then authenticate with username and password (web authentic.).
I could not find a logfile with this informations.
We are using WLC 4400 and WCS 5.0.56.2
Please help me,
greetings Lydia

Hi,
yes it helps, mainly for the future because the Authentication-option was disabled and so I can't get information about last sunday. But referring to this I found out something with the "busiest client"-report.
Thank you.

WLC/WCS Guest Access and Audit trail

I am currently using WLC version 4.2.112.0 and WCS version 5.0.56.2 and am looking for a way to keep an audit trail for assigned Guests rather than for the LobbyAdministrator creation and deletion of accouts...is this a feature of the WCS?
I know that i could use AD and use accounting portion of AAA of the radius server but is this function available on the WCS?

@Jacobt777 Thank you so much. Your solution took me about two seconds and the problem is fixed.
Should have checked this forum an hour ago when I was about ready to throw the phone against the wall, but i love my iphone too much.

NAC Guest Server and WLC, WCS

I have setup a NAC Guest Server to allow users to sign up guest account via Active Directory. How do I tight this into WLC or WCS?

Hi
Try this:
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00809d6b9a.shtml
Regards
Greg

WLC, WCS. Location Appliance upgrade order

Folks -
I am about to upgrade my system from 4.1 code to 4.2 code. I am wondering if it's possible to have the WCS and 2700 Location Appliance upgraded to 4.2 d-cubed revs first while still running Concannon WLC code 4.1.185? I am hoping to be able to upgrade WCS/2700 several days before doing all of my controllers.
So in summary, will the following combo work? WCS-4.2.97, 2700-3.1.38.0, WLCs-4.1.185.

Hi Charles,
Yes, this would be the supported method :)
Upgrading to a New Software Release
The Cisco WCS release must be the same or more recent than the controller software release. **Upgrade the Cisco WCS first to prevent any unexpected problems. Cisco WCS supports database upgrades only from the following official Cisco WCS releases:
â¢4.0.66.0
â¢4.0.81.0
â¢4.0.87.0
â¢4.0.96.0
â¢4.0.97.0
â¢4.0.100.0
â¢4.1.83.0
â¢4.1.91.0
â¢4.2.62.0
â¢4.2.62.11
â¢4.2.81.0
Wireless LAN Controller Requirements
Cisco WCS 4.2.97.0 supports management of the following wireless LAN controllers:
â¢4.0.155
â¢4.0.179.8
â¢4.0.179.11
â¢4.0.206.0
â¢4.0.216.0
â¢4.1.171.0
â¢4.1.185.0
â¢4.2.61.0
â¢4.2.99.0
â¢4.2.112.0
â¢4.2.130.0
â¢4.2.172.0
http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS4_2MR2.html#wp69815
Hope this helps!
Rob

WLC version compatibility

Dear All,
We plan to upgrade one WLC from the mobility group, code from 7.0.116.0 to 7.0.240.0. Can we upgrade like this when its a part of mobility group?
Shall the latest one supports WCS or NCS..? What and all to be taken into consideration before doing this upgrade..?
Please suggest...

Rule of thumb for WCS is that the WCS should be at equal or higher version than the WLC. This rule changes with NCS and Prime infrastructure. You might want to look at getting a WCS to Prime infrastructure migration while they still have a good pricing for that. WCS was replaced by NCS and NCS is replaced by Prime Infrastructure. PI supports the WLC that you are running.
Sent from Cisco Technical Support iPhone App

WLC/WCS question...

I have inherited some minor admin tasks for one WCS and 4 WLC. The issue is that when onsite techs run reports it shows an AP down say in room 101. The real issue I think is that in room 101 the MAC address listed for that room in the WLC is not that same as the one listed in the WCS, how do these get updated?

Ok. When you say the mac addy is different do you mean the addy of the hardwire ethernet adapter or the radios? They will show as different based on the base address and then the radio base addresses. If non of those match then you have assigned the wrong AP to the maps section of the WCS. Verify the serial number as a quick way to make sure the right AP is in the right physical location. You can get it in the WCS and then compare it to the label on the actual AP in the room.

WLC/WCS upgrade questions

Hi, we have 2 4402 controllers running with system software 4.2.130.0. The WCS is running 4.2.110.0.
I would like to upgrade but are a bit confused about all the different versions.
Is it recomended that I upgrade directly to the latest 6.0.182(WCS)/132(WLC) ?
And how do I upgrade ? the controllers first and then the WCS ?
Regards
Johann Folkestad

If you are considering upgrading to 6.0, here is the section of the release notes for the WCS that concerns that:
http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN6_0.html#wp44448
As for the WLC, here is that section:
http://www.cisco.com/en/US/partner/docs/wireless/controller/release/notes/crn601820.html#wp472449
As already stated, be sure to read the release notes to find which version is best for you.
List of Release Notes for WCS Versions:
http://www.cisco.com/en/US/products/ps6305/prod_release_notes_list.html
List of Release Notes for WLC Versions:
http://www.cisco.com/en/US/products/ps6366/prod_release_notes_list.html

WLC, WCS and WCS Navigator

I would like to know what is the difference between the Wireless Lan Controller and the Wireless Controller System.
Need I WLC if I want deploy WCS.
Can I use WCS without Wireless LAN Controllers?.
What is the diference between WCS and WCS Navigator?

You don't need a WCS server however you will require WLC's to control your Wireless WAP's. The WCS allows you to add multiple WLC's into one view along with floor plans and floor layouts and alerts. Without a WCS server you would have to manually login to each WLC controller to see what the WAP's are doing. It really depends on how big your site is and how many WAP's you have to deploy after a site survey is done.

Upgrade to WLC & WCS 5.x

I've recently upgraded from 4.2 to 5.0, and started getting these alarms
AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:46:fd:f4:b0 Cause=Admin Configured
I've seen some issues with some clients deauthenticating, does this means the radio is actually going down or is just a bug? The alarms is showing up all day longs.
Appreciate your help.

I am not sure. I will look into it. It appears you have become the first christian thrown to the lions and they are hungry. I wouldn't be so alarmed by a state up alarm as you would be if you see a state down alarm. Are you seeing any of those? Also, any disassociation from the controller?

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

AP - WLC - WCS - Compatibility

Similar Messages

Maybe you are looking for