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

Similar Messages

  • How to add antenna types to WCS

    I am running WCS 6.0.170.0 and don't have the option for an AIR-ANT5160V-R.  Is there a way to add additional antenna's to the WCS or do you have to upgrade your software?

    Depending on the version of your WCS ...
    Go to Configure > Access Point > choose the AP of your choice > under Radio Interface choose 802.11a/n > under Antenna is External Antenna drop down box.
    Please don't forget to rate our useful posts.  Thanks.

  • AIR-CAP1552H-M-K9 coverage area with AIR-ANT2547V-N antenna type.

    Hi,
    i just want to take information regarding access points coverage are of  AIR-CAP1552H-M-K9 while i am using ANT-ANT2547V-N antenna type. will these access points can join the WLC 2504 easily and can work on mesh mode.Second thing is these access points have the Ethernet port for connecting switch. 

    Hi Sandeep,
    I am using WLC 2504 and not able to getting the GUI interface. Kindly help me 
    Interface Name................................... management
    MAC Address...................................... 50:06:04:ca:85:40
    IP Address....................................... 192.168.1.1
    IP Netmask....................................... 255.255.255.0
    IP Gateway....................................... 192.168.1.2
    External NAT IP State............................ Disabled
    External NAT IP Address.......................... 0.0.0.0
    VLAN............................................. untagged
    Quarantine-vlan.................................. 0
    Active Physical Port............................. 1
    Primary Physical Port............................ 1
    Backup Physical Port............................. Unconfigured
    Primary DHCP Server.............................. 192.168.1.100
    Secondary DHCP Server............................ Unconfigured
    DHCP Option 82................................... Disabled
    ACL.............................................. Unconfigured
    AP Manager....................................... Yes
    Guest Interface.................................. No
    L2 Multicast..................................... Disabled

  • 1131 AP Shows as having "other" antenna in the WCS

    I just installed 5 lightweight 1131 ap's, two of them show up as having " other " as the antenna type in my WCS , the others show as having Ajax-Omni. They all have the same code and were installed at the same time. Also I can't get a het map profile from the " other " listed AP's. Can anyone help?
    Thanks
    Bill

    1. You can go to Monitor Map ---> Campus ---> Select Building ---> Select Floor ---> From the drop down menu select command, choose "Position AP" and Go .
    2. Click on the problematic AP's 1131 and select the correct Antenna type as being "AJAX-OMNI" which the image should match for AIR-LAP1131AG-A-K9.
    3. Click Save and the heat map should start to populate.
    4. From Floor Settings, select Access Points --> Protocol "802.11b/g/n" or 802.11a/n but not both. It's has to be one or the other else the heat maps will not display.
    5. From Floor Settings ---> AP Heatmaps --> Contributing APs, Select ALL the APs and OK.
    -nael

  • Antenna type on an AP

    Is there a way to figure out what type of antenna is connected to an AP either by logging on to the capwap AP or through the controller or thought the WCS?

    I agree with Leo. There is no way to know what type of antenna you use. Antenna is a dump device and it has no way to communicate with the AP. The AP will try to transmit the signal with or without an antenna so it does not even know if an antenna is really exist.
    Why you want to know the type of the antenna?
    Rating useful replies is more useful than saying "Thank you"

  • 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

  • WRT54G Ver.#6 Antenna Type Question

    Hi,
    I've tried my best to find the information I need concerning the actual type of connectors that are used on the factory installed antenna's that come on this router. I looked on the wrt54g specification page for this router, and it doesn't specify what they are. I'm really hoping that someone in here can tell me.
    Thanks,
    David

    I'm pretty sure it's a standard BNC connector.

  • Wireless Location AP Density and Antenna Type

    Does anyone have recomendations for the density for AP's for use with WCS location? If I use the 3 AP's required for location triangulation in an area (300x200 feet) (with omni antennas) I get great wireless coverage throughout the area, but I get lousy location tracking. If I choose inspect location readiness most everything is red with only a couple little specs of green. If I add 3 more ap's (for 6 total) I get about 20 % of the area only showing location readiness in the green with everything else red. Does anyone have any thoughts as to how dense AP's should be for tracking and what the best antennas to use would be.

    I had seen that document, but now reviewed it in further depth. I find it interesting (and somewhat expensive) to see that for acurate location information Cisco recomends AP's every 50 linear feet. Running the planning mode recomends 26 AP's rather than the 6 I now have in place, even though the 6 provide great RF coverage, they don't seem sufficiant for location.
    That being said if I do add 20 more AP's what would the best antennas for this application be? I'm assuming I should not use all 5 Db 1728 antennas as those are probably way overkill. What do you think?

  • 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