Version of vs WCS WLC
Hi guys,.
can I use the version 5.2.178 on my controller and 4.2.110 on my wcs?
Best:
WLC and WCS to run the same major version (4.2 and 4.2,5.2 and 5.2) or are the wlc and wcs not linked version?
(5.2 and 4.2)
THX...
You need to upgrade your WCS in 5.2.130 for you allows to administering WLC running 5.2.178 or 4.2.176 on your controller with your existing version of WCS.
Tags: Cisco Wireless
Similar Questions
-
Version of the IOS WLC 2125 for L3 ap-mode?
Hello
I tried to search for this topic, but always without success. can someone please tell me if that fix the version of IOS for wlc can I use to support L3 ap-mode?
Here's my current version;
NAME: "Chassis", DESCR: "Cisco wireless controller.
PID: AIR-WLC2125-K9, VID: V05, SN:Built-in MAC address... 68:EF:BD:04:55:2 A
Press Enter to continue or
to abort. Information System
Name of the manufacturer... Cisco Systems Inc..
Product name... Cisco controller
Version of the product... 6.0.188.0
RTOS Version... 6.0.188.0
Bootloader Version... 4.0.191.0
Version of the Image of emergency... N/A
Build Type....................................... DATA + WPSThanks in advance!
see you soon,
Dayve
Hi stephane,
The link below will answer your question...
http://www.Cisco.com/en/us/docs/wireless/controller/5.2/configuration/guide/c52ovrv.html#wp1069102
It's...
Version 5.2 or a later version of the controller software support only mode Layer 3 CAPWAP, versions 5.0 and 5.1 of the controller software load only Layer 3 LWAPP mode and controller software versions prior to 5.0 supports 2 layer or Layer 3 LWAPP mode.Concerning
Surendra
-
WCS & WLC version compatibility
Are there compatibility issues between the 7.0.164.0 of the WCS and WLC version 7.0.116.0 version?
Hi Jason,
Table 1-WCS Versions
WCS versionController supported versionsRental Server Versions supportedVersions supported for MSERelease dateUpgrade took in charge ofOperating system requirement7.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.06.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.0Windows 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.06.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.0Windows 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.06.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.0Windows 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 (taken from EAC)
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.06.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.0Windows 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 (taken from EAC)
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.06.0.102.0
6.0.105.0
July 15, 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.0Windows 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.06.0.101.0
6.0.103.0
February 17, 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.0Windows 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.06.0.97.0
6.0.97.0
November 8, 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.0Windows 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.06.0.85.0
6.0.85.0
June 11, 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.0Windows 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.05.2.100.0
5.2.100.0
June 25, 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.0Windows 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.05.2.91.0
5.2.91.0
February 21, 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.0Windows 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.05.2.91.0
5.2.91.0
February 10, 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.0Windows 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.05.2.91.0
5.2.91.0
November 24, 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.0Windows 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.05.1.35.0
5.1.35.0
January 9, 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.0Windows 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.05.1.30.0
5.1.30.0
July 21, 2008
5.0.56.2
5.0.56.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0Windows 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.04.0.38.0
Does not apply
August 5, 2008
5.0.56.2
5.0.56.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0Windows 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.x4.0.33.0
Does not apply
April 14, 2008
5.0.56.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0Windows 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.x4.0.32.0
Does not apply
February 16, 2008
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0Windows 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.03.1.43.0
Does not apply
May 13, 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.0Windows 2003 SP2 32-bit
RHEL 4.0
RHEL 5.0 (No. 5.1 and later 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.03.1.42.0
Does not apply
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.0Windows 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.03.1.38.0
Does not apply
June 3, 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.0Windows 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.03.1.36.0
Does not apply
March 17, 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.0Windows 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.03.1.35.0
Does not apply
January 25, 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.0Windows 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.03.1.35.0
Does not apply
November 9, 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.0Windows 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
See you soon!
Rob
PS: + 5 to my friend Leo with the invisible stars
-
management of WCS, WLC and H-REAP AP1242
We have chosen to deploy 1 wlc2106(k9-7-0-98-0) and 4 or 5 APs 1242, LAP - AIR and AIR - AP converted to AIR TOURS in each office, with a backup 1 WLC5500, in seat.
We have WCS (v7.0) and in this architecture, 1242 APs will be always connected on 1 of 2 WLC (never in autonomous REAP).
In normal mode, WLAN, working in the central authentication and Central switch. In backup mode, WLAN work in central authentication (backup WLC headquarters) and local switching.
For the configuration of the WLC, is it really necessary to create and REAP H unit for all the Aps or can I leave by default-AP group?
I have a problem with AIR - AP converted it TURN: I can't push a TOUR from the WCS model:
AP0022.90.1b.9d36 is the converter of AIR - AP.
another AP are AIR - LAP: Ok for this model that apply
What can be the problem with this access point?
Thanks for your help.
Lorenzo
The best for homelessness must have WLC, authentication management. Now, if there is a WAN link rather slow in the game, perhaps, he retorted the initial advantage of it.
In this case REAP H groups will allow roaming between aps hreap seemless.
In any case, it does not hurt to combine your APs in Hreap groups. It can only help. So ... :-)
Nicolas
===
Remember responses of the rate that you find useful
-
WLC v4.2.112.0 - IDS Signatures - Deauth/Auth and flooding of the Assoc
Hi all
My apologies if this has already asked. There seems to be several posts with people getting critical alarms and they are due to bugs in Cisco?
Couple of points.
I am under the above version and I'm getting a lot of IDS Deauth Auth and Assoc alarms on WLCs/WCS.
How can I find out if these are some releated bug or not?
Also, does anyone know how these three and the other signature attack work? IE, a deauth is a number of deauth messages sent to an access point, but how much is sent before the WLC reports on them? That is to say, what are the criteria to generate the IDS alarms. Also for other signature attacks?
It doesn't seem to be too docs on the web?
Many thx and sincere friendships,
Ken
Ken:
It is a region that has been a bit murky documentation. There have been a number of requests for better documentation, but we are still waiting to see.
Surprisingly, one of the best forms of
"documentation" is by examining the signature file wireless IDS which has a few comments and explains how settings work. You can see what a little enlightening.
In addition, when it comes to false alarms, we have seen a number of them in various flavors. Here are a few thoughts:
If you run "containment" or rogue APs, wireless ID system currently interprets its own messages of containment as a false-positive/attack. This is a known bug ( CSCsj06015 ) that says: it is fixed, but to my knowledge continues to be a problem.
Here is a link to the bug:
Also, when some brands of customers go out of scope, a string of messages disassociation is sent via the Russia Federation to ensure that the RF connection is broken. However, the number of these legitimate trusts sometimes exceeds the allowed value in the signature CODES of Cisco Wireless file and the WLC erroneously interprets as a false positive / attack, whereas in fact, it's a normal approval. The number of detections per second value can be adjusted (in fact, the proposed TAC make some changes here - but this really needs to be better set at the factory to prevent them to ancestral). One of the links below explains the methodology to change wireless IDs. The most recent versions of the WCS/WLC are supposed to allow a change of parameter/GUI based these parameters vs export/edition/download the signature file wireless IDS on/in each WLC.
For your reading pleasure, here are some links that you might find useful who discuss various wrinkles in wireless IDs:
Thank you
John
(Don't forget to rate helpful messages)
-
Unable to apply the model of WLAN to the controller through WCS
Unable to apply the model of WLAN to the controller through WCS
1 update your config all of your controllers of WCS. Go to configure---> controllers--> select all controllers.
2. in the drop-down "Select", choose "refresh the configuration from the controller and select 'Go'."
3. choose Delete therefore WCS will take the last setting of the WLC and select 'go '.
4. remove the WCS WLC.
5. Add WLC to WCS.
6 try to set up the model again.Also, you can upgrade to 6.0.170 as there are to many model feature bugs that have been fixed in this version.
http://www.Cisco.com/en/us/docs/wireless/WCS/release/notes/WCS_RN6_0_170.html#wp44440
-nael
-
Question of access with WLC 2106
Hi, I have a WLC 2106 and APs 2 1250 connected to it. the controller works really well. all APs are associated.
The problem I have is that, after only a few days I can't connect to the GUI or console.
I can still ping and trace the controller.
After I have turn off the controller and turn on again, it works again.
Show the internal temperature 56 C would this cause the problem?
Hi, there is a known issue with version 5.0 of WLC and the GUI timeout. Cash, http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&topicID=.ee6e8b8&fromOutline=&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.2cc15418
-
Hi, I have a design requiring a WLC 5508 be connected to two separate swithces specific wireless. WLC 1 port is connected to the switch A trunk and WLC Port 2 is connected to the switch B. Each switch has its own local VLANS. When I connect the years 1130 towers they need find the interface of management initially then only use management. AP interfaces since there is only a single management interface, if the assignment of management interface on a VLAN that is configured on the switch then APs on spend a fine join but those switch B continue to ask for the management interface and the version debug capwap on WLC he says that this query Join were received on the bad ineterface...
the only work around that was to do the routing between switch A and switch B for both VLAN residing APs... but for security reasons - customer would like to avoid this
any help is appreciated...
Unfortunately, the initial discovery must arrive in the management interface. Once this has happened the AP expected the second AP manager who is on the subnet of comments, therefore, they are able to stand. But if the AP is restarted, it would need to discover once again and would fail.
What is the concern of customers to have all routable network mgmt AP? guest users can not see anything there.
IMO, let the AP able to connect to the subnet of mgmt, but then put an ACL L3 upward, to block the subnet of comments to achieve anything in the internal network.
-
I find contradictory documentation; the 3500th is supported on the WLC 4400 w / version 7.x code?
Docs, I found say 3500 is CAPWAP only so that only the 5508 CAPWAP.
Thank you.
Anything over version 5.2 software WLC > CAPWAP
Anything below version 5.2 software WLC > LWAPP
Now go back to 3500th... version minimum necessary to get the 3500 AP with WLC is 7.0 and 7.0 is compatible with the 4400... That is why 3500 is supported on 4400 running the WLC version 7.0 and later...
This has answered your qiestion?
Concerning
Surendra -
Hello
I intend to improve our WLC 4402 from 4.0.206 to 7.0.89, but I would like to know if the version 7 of the WLC is compatible with version 4.0 of Cisco ACS?
Thank you
Paul,
Yes WLC code version 7, is compatible with ACS 4.0. WLC will work with virtually any version of ACS, by using the parameter Radius Aironet.
See you soon,.
Steve
Please do not forget to messages useful rates
-
WLC... WCS... Rental App compatibility
Hello
I am installing a new unified wireless solution and I'm stuck trying to figure out what software is the best to use with all the different devices. I heard that 5.x is real buggy in the WLC unit, so I went with 4.2.176MD (I think) but I have not heard anything with the WCS and the location device. After reading some of the release notes, it seems that I have to go with a version of at least 5.1.64 WCS to be compatible with the version of the location of 5.1.30.0 but I don't know if they all happy well together.
Any help on this would be great.
Thanks in advance!
Yes... This combination will work.
-
LAP1131AG loop without end of join (5.2.130.0, WLC 5.2.178.0 WCS)
I have som Aironet LAP1131AG accesspoints, who, after an upgrade to 5.2 WCS (including the upgrade of WLC) will join not the controller.
I have attached a dump of the console. The accesspoints will improve the image, if they are hardreset (by pressing reset for a few seconds during the reboot), but they will be I have a never ending quest to join (last good message is changed CAPWAP State to CFG)...
We have 100 + accesspoints which are unaffected by the upgrade, but 2 accesspoints give me the same problem.
Any ideas as what to try?
-I would recommend that you use a browser to connect to your access point. The first page after logon has a good summary of the State of all interfaces.
-For the mistake of WCS: are you using the same strings of SNMP and versions on WCS and on the AP? They must match (but I have never tried to add a point to independent access to the WCS).
-
WCS couldn't handle WLC after software update WLC
Hi all
My version of WCS is 6.0.181.0 and my AIR-WLC4404-100-K9 2 running on a very old version of 4.2.61.0. I've decided to update the IOS on the WLCs. All the upgrade were made on the WLCs. First of all, I upgraded the to 5.1.151.0. After the level and restart, the WCS showed always accessible for the WLCs. Then, I upgraded the IOS at 5.2.157.0. After the upgrade and reboot, WCS is no longer sees the WLC and showed inaccessible for the WLCs. However, I could always directly log in the WLCs and updated successfully upgraded to the latest version 7.0.98.0.
Now the WCS, when I try to click on the WLCs, it always gives me this message "no response from the device, check communities SNMP, version or a network for questions." I checked the SNMP communities and the network with the only left version.
My question is, can WCS with version 6.0.181.0 manage WLC 4404 with version 5.2.157.0 and higher?
Any input will be appreciated? Thanks in advance.
Hi Robert,.
The recommendation is that the WCS is always a version equal or greater to the WLC
See table 1;
Table 1-WCS Versions
WCS versionController supported versionsRental Server Versions supportedVersions supported for MSERelease dateUpgrade took in charge ofOperating system requirement7.0.164.3
7.0.98.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
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.06.0.101.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.0Windows 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.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.06.0.101.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.0Windows 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 (taken from EAC)
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.06.0.102.0
6.0.105.0
July 15, 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.0Windows 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.06.0.101.0
6.0.103.0
February 17, 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.0Windows 2003 SP2 32-bit
RHEL 5.x
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_164_3.html#wp68364
See you soon!
Rob
-
I would like to know what is the difference between wireless Lan controller and controller wireless system.
I need WLC if I want to deploy WCS.
Can I use WCS without wireless LAN controllers?
What is the diference between WCS and WCS Navigator?
And just to add WCS navigator is used to group multiple instances of WCS. This would serve in a very large deployment (in thousands of controllers).
-Mike
-
Hi all
We have 3 WLC 4402 all with identical config and we use Lobby Admin to create guest accounts.
Problem with this is that the guest account must be created on 3 WLC.
I installation WCS and want to know how to extract the 3 existing wlc and their config in the WCS.
Can the admin of lobbay can create accounts on the WCS and grow them into all wlc
Hi RR,.
>I install WCS and want to know how to extract the 3 existing wlc and their config in the WCS.
It's pretty easy. You must add a new controller via the configuration-> page controllers. The option 'Add the new controller' is in the drop-down list at the top right of the screen. You can use a list separated by commas of IP addresses to add all three at the same time. WCS audit of the controller software and get to the bottom of the config.
>Also can the admin Hall can create accounts on the WCS and grow them into all wlc
I have not used the account Admin Hall (it is not really appropriate in the office where I work), but I know that you can create a guest account in the controller model launch pad. It is under Security in the sidebar. This model can then be applied to all three WLCs at the same time, that will simplify things. I guess you would need to make sure that your Hall administrator can access this particular part of the WCS.
Hope that helps.
-Jason
Maybe you are looking for
-
cant connet brower with slurl proxy how can I fix it?
-
How to create a color image optimized vectors R, G and B IMAQ?
Hello everyone, I have the R, G and B elements of an image RGB contained in three different vectors. I currently use the program as an attachment to get the color in IMAQ image. This program works perfectly, but I want a faster program without two ne
-
My hard drive is dead and I don't have a Vista Home premium, I have a stamp with the key of the operating system. I called Microsoft and they say that the only one who can provide me with this OS is the provider. What can I do to DOWNLOAD the OS for
-
Hello There is an option to whitelist for ICMP on EA6900? I want to check my Internet via ICMP (Smokeping) but cannot find the option to turn on the ICMP protocol. Maybe someone knows? Maybe there is a possibility to activate the option advanced on t
-
Brightness: f2 and f3 button do not work.
I tried everything I could but am not able to adjust the brightness of my laptop (i.e. laptop HP 250 G2). Please help me.