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

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

  • 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 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

  • 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 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

  • 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-

  • 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

  • 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.

  • Can't find WCS/WLC log files

    i'm using a WCS to manage two 4404 controllers, i tried to sync the two controllers with the WCS. the first one worked fine the second failed with the message to view the logs. but i can't find any mention of a failure on eiter the WCS or the controller.
    any ideas where i can find the detail of the error message so that i can look at sorting the failure out.
    Many thanks,
    Adam

    IP Address Status
    192.168.168.1 Success
    192.168.168.2 Failed (see logs)
    this is all i see, hence the question where can i find the logs so i can see the error message

  • WCS WLC Config Files

    I am finding it difficult to locate the backup config files for my controllers on the WCS server.  Can someone tell me the file extension and the file folder where these files are saved so I can verify they are getting saved?  This seems to be more complicated to find than it needs to be.                  

    When WCS was installed it asked you for a folder name where to store these files. Go to Admin--Settings--Server Settings and you will see the drive and folder name. Look in these .. Should be under TFTP folder
    "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 upgrade options

    Hi,
    I'm currently running both a WCS appliance and a windows server WCS on version 4.2.62.11
    They are managing around 1000 AP's that are in a Hospital environment. They are using Vocera badges.
    The controllers are all running v4.2.61.0
    What are my best upgrade options for both WCS and the controllers? I'm looking for stability, improvements and fixes.

    We ran a pretty stable 4.0.217 for about a year with no big issues that I can remember. We started getting 1252s and needed to upgrade. We finally jumped in with 4.2.130 and had some pain. We started having issues with Vocera roaming, and Dell 1470/90 adapters had issues also. We've seen the following issues (CSCsm65043, CSCsi26248, CSCsi72578, CSCsq57697, CSCsu44970, CSCsr40109, CSCsv21441, and CSCsv21464). Some have been fixed in 4.2.173/176, but with the latest security advisory, it makes sense to run 4.2.176.
    With 19 pages of open caveats in 4.2.176, it's a crap shoot for sure, but probably the best you can do as it's a MD release. Also we have depreciated the Spectralink and only run 7921 and Vocera.

  • WCS:- WLC Alarm not getting cleared automatically on WCS

    ALarm TAB:-
    ==========
    Severity: Message:
    Critical ------------------------------Port 2 is down on Controller.
    This Alarm is not getting cleared automatically, Where as the alarms generated for AP's are getting cleared, I would like to know is this the default behaviour or we need to look into some thing here. To clear this i need to manually delete the alarm.
    Any help would be greatly appriciated.

    Alarms are automatically cleared after 7 days. Clear the alarms manually if you want to clear the alarms before 7 days. For more information refer http://www.cisco.com/en/US/products/ps6305/products_qanda_item09186a00807a60f0.shtml#qa11.

  • WPA-PSK on multiple WLANs (WCS/WLC 4400)

    Greetings,
    If I have two different WLANs, both configured for WPA-PSK, are the pre-shared keys different per WLAN?
    I ask because when I change the PSK on one WLAN, it seems that this may be affecting the other WLAN.
    I'm not on-site to test this out, unfortunately.
    It almost appears that setting the pre-shared key is a global setting, and not an individual setting per WLAN.
    Any assistance would be appreciated!

    The setting of the WPA-PSK should be per WLAN. Changing one shouldn't affect the other WLAN that is configured.

Maybe you are looking for

  • Coldfusion Socket Gateway in web application help

    I've created a Java Socket Gateway in ColdFusion to talk to a 3rd party API.     User requests their credit balance by clicking a button.     On clicking the button, a socket is opened with the 3rd party server in CFML, it sends a gateway message (re

  • Seems to be continuously indexing. Why i my iMac so slow?

    I just loaded OS X Lion on my iMac, as well as Messenger beta. I can't see why these would affect the machine by indexing since it ran fine before. I have installed the same on both of my other macs with no problem. It seems this one is indexing almo

  • Group function is not allowed here - where statement

    I have a select that is basically: select a,b, sum(c),sum(d), sum(c) - sum(d) from A group by a, b I would like to add: where sum(c) - sum(d) <> 0 I know that I can't use the sum function in the where statement. Any ideas how I can get around it? Tha

  • Code inspection warnings in Function Group

    Hello, Help appreciated. I have created a Function Group. When code inspection is done it is giving following warnings : Warnings: 1. Message code Len The parameter "I_INHDR" is transferred as value. Use reference transfer 2. Message Code MESSAGEGM1

  • Sony Alpha 6000 RAW support is missing

    Hi, I just bought a SONY Alpha 6000. I like to shoot in RAW, however, neither Aperture or iPhoto support my SONY RAW format. I like to know where can I send in request to get it updated?