WCS WLC support

Hi,
We are running version 4.2.62 of Cisco WCS.
I'd like to upgrade to 4.2.128.  We run version 4.2.209.0 on our WLCs.
The release notes for WCS version 4.2.128 does not list WLC version 4.2.209 as a supported version.
I would think it would be OK but can anyone confirm if this will actually work?
Also, is it worth upgrading the WCS to the more recent 7x versions?
thanks.

Hi,
The release notes mention with which version the WCS has been tested. So since 4.2.62 WCS came at the same time as 4.2.61 WLC it doesn't state it supports other 4.2 versions since it could not have been tested with those. However, since they are the same major release, all should be ok but you'll maybe face minor bugs here and there.
So just upgrade your WCS to the last 4.2 version of WCS and you'll be good to go :-)
Regards,
Nicolas
===
Don't forget to rate answers that you find useful

Similar Messages

  • Antenna type in WCS / WLC

    Hello, I am still somewhat new to the wireless side and I saw something today while trying to troubleshoot a wireless issue we were having that I have not heard or read about from my CCNA Wireless studies. I noticed that the antenna types our WCS is showing attached to my APs are wrong.
    My question is, do the APs / WCS / WLC know what type of antenna is connected to the APs automatically or is this a manual process that someone should assign them? The second question is, if it is a manual process (which I suspect it will be) can I change it without disrupting current connections or should I wait until a maintenance window to do this?
    We have 3502e AP with AIR-ANT-1728 and AIR-ANT-5150V-R antennas attached to them, but my WCS says they have the rubber duckies on them. Any insight would be greatly appreciated.
    Thank you in advance for any help you can provide!                    

    There is no way the WLC even knows what antennas you have. If your using antennas besides the rubber ducks then you need to define that on WCS. If you have Cisco antennas, there is a drop list of the antennas. You also have to make sure of the antenna orientation. This is all defined in the WCS user guide.
    Note
    If you have a ceiling-mounted AP with an integrated omni-directional antenna, the antenna orientation does not really need to be set in WCS. However, if you mount that same AP on the wall, you must set the antenna orientation to 90 degrees.
    Sent from Cisco Technical Support iPhone App

  • WCS annual support: what do I get for extra AP license packs?

    I am not trying to be snide here, but I am having a difficult time understanding what new value I get for an extra SAU annual support package that my Cisco Partner says I now need, since I added additional AP licenses to the WCS software. This add-on SAU will more than double my annual support costs for the WCS software. I've called and emailed my partner several times on this, and basically it came down to "that's how Cisco does it now." I've also done on-line chat and a couple hours of phone  time with Cisco's pre-sales support, and technical support, but neither of them was able to give me any answer, and after passing me back and forth between their two divisions, they passed the buck back to my Cisco partner.
    But, my question remains: What additional value do I get for this doubled price "Software Application support with Updates"? I can already download WCS software and WLC firmware. The only thing that has changed is my software's AP limit.
    We've had WCS 5.0, with the original Base 50 AP license. The WCS server runs two WLC 4402 units, one set for 25 APs, and one for 50. We actually have 46 APs deployed. We've paid annual support since we first purchased this system, SAU software and upgrade support for the WCS software, and SmartNet hardware support for the WLCs. We have not had support for our actual AP hardware, as our partner recommended just buying spares instead, as a cheaper option. But, AP firmware updates come automagically with the WLC firmware updates.
    We will soon be going beyond 50 APs, so we installed an 100 AP add-on license for the WCS. This changed the "About" box for the WCS software so it now says it is licensed for 150 permanent APs, instead of the original 50. (This add-on license cost more than $4,000, so I don't feel that I'm trying to get a bigger WCS system without paying for it.)
    Recently I upgraded my WCS software to v5.2 and then to v6, and am currently at 6.0.196.0. I also upgraded my WLC firmware, which updated my APs. Everything seems to be working well, and these updates were all included in my basic SAU for WCS, which runs about $720 per year.
    However, March is when our SmartNet renewals come due, and my partner says we now need to buy a second version of WCS SAU, supposedly a requirement with our additional 100 AP license. This add-on support ( part "CON-SAU-WLB100EX" ) goes for $1,080 per year, so my WCS annual support would now be $1,800 instead of $720.
    As I said, I really don't understand what I'm getting for this additional money. We are a small enough college that I can't spend $1000 without justifying the expense. Already, with my existing WLC SmartNet payment I get firmware updates for my WLC and AP hardware, and with my existing WCS SAU payment I get software updates on the server. None of this seems to have changed with the additional AP license count.
    (Note that although the WCS update package allows 100 more APs, my present WLC hardware really only allows an additional 25 APs.)
    If nothing else, for $1,000 a year, Cisco should be able to give me a pithy explanation of what I am buying :-)
    In summary:
    What does CON-SAU-WLB100EX actually support? Why do I need it?
    What happens if I keep paying my CON-SAU-WCS support and my WLC support, but do not add this new charge? Is my WCS software still upgradeable?
    Thanks for any insights you can provide,
    Steve Bohrer

    I'm not selling support contracts, I just work in TAC. But here's my 2 cents :
    If you have your license for your extra APs (which you said you already bought), your WCS will run just fine.
    With regards to software download, either you have download access or you don't. The system can't prevent you to download WCS because it saw you had purchased more AP license than your support contract mentions. So download should still work in the future.
    From a TAC perspective, if there is a support contract, we give support. We don't care at all how many APs people have.
    So all considered, I have no idea what this extra support contract will bring you :-)
    But since the Sales people in your region don't seem to gifted in explaining what they are selling, I would just go without that special contract unless they justify what it exactly adds and what you will lose if you don't take it. Probably if you don't say a word, they won't notice anything and will still support you nonetheless :-)

  • 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

  • Does a 2504 WLC support mobility group with WiSM1 on 6500 Series

    if a 2504 WLC support mobility group with WiSM1 on 6500 Series.
    Model: WLC 2504
    Software version: 7.3.101.0
    Model: WiSM1
    Software verion: 7.x.x.x

    Yes and no. 
    Yes, mobility is supported.  
    No because I personally won't recommend inter-controller roaming.  This is more true when you're dealing with 4400/WiSM-1.  This is even more true when you've got WLC running two (or more) different codes.  

  • Problem audit mismatch WCS/WLC for local net user

    HI,
    I have a problem in my WCS the audit status is mismatch for my two controllers. When I see the details of the mismatch, it is said that all my 400 users are "not present in controller".
    However, I checked directly on my web interface of my controllers and my users are there (Security--> AAA--> Local Net Users). I've also checked on the WCS (ConfigureàControllersà controlerà Security à AAA -> local net user).
    In both My users are present and are identical.
    When i refresh config from controllers on the WCS it disappears but a week after the mismatch comes back.
    If anyone can help, Thanks
    Alex

    Anyone able to answer this one?
    We are having the same issue.  We had WLC code 7.0.116.0 with WCS giving us mismatches on certain thresholds, despite the fact that the controller and the WCS configs were a match and no one made changes.  We would refresh confgi from controller and a week later, the mismatch was back.  It's as if there was something wrong with the WCS database.  We upgraded to NCS 1.1 and are now on WLC code 7.0.230.0 and it worked for a while, but we are now randomly experiencing the same issues and then some with NCS. 
    We have a multi-tenant campus that has several of another organizations access points configured as friendly in NCS, but the controllers still had them as rogue and were containing them.  We are also experiencing a max client count threshold that is set to 20 on the controller, but NCS is now reverting back to the default 12 value and giving off a mismatch.  I don't know if there is a SQL issue with the database or not, but we service roughly 3000 users on a 5 million sq. ft. campus and some of these mismatches and failure to identify critical mismatches is starting to become a problem.  Going to open a TAC case, but if anyone has any insight in the mean time, that would be helpful.  Thanks!

  • WCS/WLC Disabled WLAN still broadcasts! BUG?

    Versions 6.0.182.0 on controllers (4 WISMs) and 6.0.132.0 on WCS.
    Created a test WLAN which was used for a week or so, WPA2/PSK, broadcast ssid, standard stuff. I no longer wish to use it and set the enabled state in the template to disable and then saved and applied the template to the controllers. On various devices, I can still see it broadcasting! I have even checked on the individual controllers and the WLAN is set disabled, so no WCS sync issue. I also tried switching the broadcast ssid to off and reapplying it and this makes no difference.
    If I try to connect to the WLAN, this fails, which is obviously a good thing! I have not tried to delete it yet as there are situations where we need the ability to enable/disable wlans.
    Anybody else seen this issue before I report it to TAC?

    If the WCS and WLC has been synchronized, you should not see this issue. Since you have already verified and ruled out a sync issue, this looks like a bug.

  • WCS -- WLC "Device un reachable"

    Added WLC to WCS. Rebooted WLC from WLC and WCS cant reach WLC eventhough I can ping and access WLC. Verified SNMP and looks fine. Happened on two WLC's. I am waiting for almost 2 hours for WCS to talk WLC...

    Please update the following informations
    'show run-config' from the WLC and 'show run' from Switch connected to WLC while specifying the ports of Switch that connect to WLC in 2 separate text files.
    => Show msglog after the problem happens.
    => Check if there is crashes file available (WLC GUI ->Management ->Controller Crash)
    => 'show port summary' from the WLC when such problem happens.
    => 'show ip int br' from Switch connected to the WLC when such problem happens.
    => 'show arp switch' form WLC when such problem happens.
    => 'show arp' from Switch when such problem happens
    The following URL will help you:
    http://www.cisco.com/warp/public/707/cisco-amb-20070412-wlc.shtml

  • Wcs-wlc-ap

    hi! I've 2 controllers (5508) managed by Cisco WCS. What's the best and simpler way of pushing down the snmp config/string to the controllers and the wireless access points? How can this be done? The objective is to have these equipments (controllers and wireless access points) managed by cisco works. Thanks.

    WCS manages the Inventory and availability. CiscoWorks would only see the controller hardware. You could enable ssh on the ap's and have CiscoWorks login but I am not sure thats what your looking for. WAS manages the configs and all aspects of the AP and you can create automated reports about almost anything related to the pa's and forward alerts to CiscoWorks for tracking but WCS does a much better job.
    Stan
    Sent from Cisco Technical Support iPad App

  • WCS/WLC read-only access

    We use WCS and AAA in our wireless environment. Reading through the WCS user guide (http://www.cisco.com/en/US/docs/wireless/wcs/5.2/configuration/guide/5_2manag.html#wp1089936) , authorization seems awfully course grained. Is there a way to provide a security group with login and read-only rights to all aspects of all wireless components (or at least to WCS and all WLC)? Ideally, the security group would be able to login to any WLC at any time and verify settings, etc.

    Hi,
    We need to follow following document to ensure that user with which we are logging in has the appropriate attributes assigned,
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a0080851f7c.shtml
    What different roles means, please go through following document,
    http://www.cisco.com/en/US/docs/wireless/controller/4.1/configuration/guide/c41sol.html#wp1208657
    HTH
    Regards,
    JK
    Plz rate helpful posts-

  • Does the 2106 WLC support multiple interfaces?

    I am trying to lab something up and I believe I am doing something incorrectly.    My management VLAN works fine, the AP on port 7 finds the controller fine, but my VLAN 80 doesn't seem to be mapped to port 2.  I mapped a test WLAN to the VLAN, and setup a DHCP scope, and a client can get on the WLAN, acquire an IP address, etc.  I thought I coudl then map that VLAN (80) to port 2 and have it go out a cable modem.  Doesn't seem to be working that way, however.
    Anyone know if this is supported, or what am I doing wrong?
    Thanks in advance!

    You are getting FANCY Tim!
    For starters you should really use a switch because sometimes you may get odd behavior connecting right to the WLC. Also the WLC is like a layer 2 switch and doesnt route. Ive done something similar in fact. We call it offnet. We break out the ports and have 1 going external. We used a switch inbetween the ap and comcast line.
    "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."

  • WCS/WLC and Wii

    All,
    I am on a University campus where we allow students to plug in there game consoles into our network for online gaming. We recently purchased a WCS solution from Cisco and deployed it this summer. The students coming to campus have brought in their Wii consoles and are unable to connect to the network.
    I have attempted to use the Wii with an Access Point prior to joing the WCS system but once it is joined it will no longer connect. Is there a setting within the WCS system that needs to be tweaked to allow Wii connectivity?
    Best Regards.

    Rob,
    Thank You for the response. We spent several days troubleshooting this this week with Cisco and came to a resolution although not an ideal one.
    Problem Statement: Nintendo Wii Wireless consoles would not work with Cisco access points once they are added to the Wireless Lan Controller (WLC) solution. The Light Weight Access Point (LWAPP) would receive DHCP requests from the Wii and the DHCP server would send back an Offer but the Wii would not acknowledge the offer and would not accept a DHCP address. If the same model autonomous access point is used (not WCS/LWAPP) the Wii works as expected.
    Infrastructure background: Our DHCP server is a Unix platform which must DHCP Relay through a Cisco Clean Access (CCA) solution and then DHCP Relay through the WLC solution. Somewhere in all the relaying an address was changing that the Wii console could not understand and as a result never got the DHCP address. We are not using any encryption at this time.
    The solution: By creating a new DHCP scope and placing it directly on the WLC systems we were able to bypass any DHCP relaying and provide the address directly from the WLC to the Wii console. We are aware of at least one additional institution whose DHCP infrastructure is the same as ours who is also using CCA who had the exact same problem. They claim that a Nintendo Wii running firmware version 2.x will work with their system but once it is upgraded to 3.x it fails to connect. We haven't been able to validate that for ourselves but if this was the case, it would seem that Wii software version 3.0 handles DHCP a little differently than 2.0.
    Regards

  • Whether WLC support LDAP Secure ?..

    Hi ,
    We are using 5508 WLC with software version of 7.4.100.60 . Whether this code will support that ? When we tried LDAP on with port number 389 , we are able to authenticate the user . But with LDAPS on port number 636 we are not getting response from AD?
    Any clue on this...
    Thanks,
    Regards,
    Vijay.

    You can change the port, but you are not changing how it communicates by changing the port. If you search for WLC LDAP Configuration, you will not see any reference to supporting LDAPS. If there was a setting on the WLC to choose to use LDAP or LDAPS, then it would work. You have also tested it and you can see it doesn't work. Sniff the traffic and see if it is secure or not as that will also tell you.
    You can alway contact your local SE and put in for a feature request for that.
    Sent from Cisco Technical Support iPhone App

  • Does a 4402 WLC support ISL?

    Hey there,
    Does a wireless lan controller support isl encapsulation?
    I have an wlc with 8 active ap's, but their all using dot1q, but this gig fiber interface going to where i have the switch connected to the access point is isl and I can't get the ap to download the config.

    Does a wireless lan controller support isl encapsulation?
    No.
    but this gig fiber interface going to where i have the switch connected to the access point is isl and I can't get the ap to download the config.
    What switch is this?

  • WCS/WLC Alerts - Configuration

    I can't seem to find where I can make modifications to the alerts that I receive from either the WLC or WCS.  The alerts mainly being notifications of possible rogue access points.  Can someone direct me to where I can make changes as to what kind of alerts I can get from the WCS and/or WLC?

    I finally found this.  Administration > Settings > Mail Server Configuration > Configure  email notification for individual alarm categories.

Maybe you are looking for