Table Of Contents
Release Notes for Cisco Wireless Control System 188.8.131.52 for Windows or Linux
These release notes describe open caveats for the Cisco Wireless Control System 184.108.40.206 for Windows or Linux, which comprises part of the Cisco Unified Wireless Network Solution (Cisco UWN).
The Cisco Wireless Control System is hereafter referred to as Cisco WCS.
These release notes contain the following sections.
The following components are part of the Cisco UWN:
•Operating system (Wireless LAN Controller and Cisco Aironet Lightweight Access Points)
•Cisco 2700 Series Location Appliances
•Cisco 2000 Series Wireless LAN Controllers
•Cisco 4100 Series Wireless LAN Controllers
•Cisco 4400 Series Wireless LAN Controllers
•Cisco Wireless Services Module (WiSMs) for Cisco Catalyst 6500 Series Switch
•Cisco WLAN Controller Network Modules for Cisco Integrated Services Router
•Cisco Aironet 1000 Series Lightweight Access Points
•Cisco Aironet 1130 Series Lightweight Access Points
•Cisco Aironet 1200 Series Lightweight Access Points
•Cisco Aironet 1230 Series Lightweight Access Points
•Cisco Aironet 1240 Series Lightweight Access Points
•Cisco Aironet 1500 Series Lightweight Access Points
Requirements for Cisco WCS
The following server hardware and software is required to support Cisco WCS for Windows or Linux:
•Requirements for Cisco WCS Server - Cisco WCS can be run on a workstation/server class system:
–For up to 500 Cisco Aironet lightweight access points: 2.4 GHz Pentium processor with 1 GB RAM.
–For over 500 Cisco Aironet lightweight access points: dual processors (at least 2.4 GHz each) with minimum 2 GB RAM.
–20 GB of free space on your hard drive.
The following operating systems are supported:
–Windows 2000/SP4 or later, or Windows 2003/SP1 or later with all critical and security Windows updates installed.
–Red Hat Enterprise Linux ES 3.0.
•Requirements for Cisco WCS User Interface - The Cisco WCS user interface requires Internet Explorer 6.0/SP1 or later, with the Flash plugin. The Cisco WCS user interface has been tested and verified using Internet Explorer 6.0 on a Windows workstation.
Cisco WCS 220.127.116.11 is now available. As new releases become available for Cisco WCS, consider upgrading.
Finding the Software Release
To find the software release Cisco WCS is running, refer to the Cisco Wireless Control System Configuration Guide. If WCS is already installed and you are connected, verify the software release version in the Help > About the Software option.
Upgrading to New Software
For instructions on installing a new Cisco WCS software release, refer to the instructions in the Cisco Wireless Control System Configuration Guide.
New Software Features in Release
Multiple WLANs can use the same WEP key index (referenced as resolved bug CSCsd46973).
This section describes important information about Cisco WCS.
Changing Default Password
To ensure security of the application, you should immediately change the default WCS password.
Cisco WCS Upgrade
Cisco WCS for Linux supports database upgrades only from the following official Cisco WCS releases: 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, and 18.104.22.168.
This release of Cisco WCS for Windows or Linux is compatible with wireless LAN controller and Cisco Aironet lightweight access point operating system 3.0 or later.
Single Cisco WCS per Wireless LAN Controller
The UWN is designed so that one instance of Cisco WCS can be used to configure, monitor, and operate each set of wireless LAN controllers. This design ensures that the wireless LAN controllers are properly represented in Cisco WCS (CSCsc42249).
Cisco MCS7800 servers are not supported as Cisco WCS servers.
Cisco WCS Physical Location and IP Addresses
Cisco WCS should be run on a robust desktop or rack-mount machine in a server room, but the Cisco WCS user interface can be run on any Windows workstation.
Workaround: If you need to change the IP parameters on the Cisco WCS workstation, such as the IP address or the default gateway, shut down Cisco WCS before making the change, and start Cisco WCS after your IP configuration changes are complete.
When you have more than 200 tags, clients, or rogues on a maps page, map-page rendering can be slow. The browser may temporarily freeze during the first rendering and when it renders at every refresh interval.
Workaround: Cisco recommends that the user limit the number of visible entries to 200 for each asset type (client, tag, rogue access point, rogue client) and then save that as the default view if more than 200 of any asset type are expected on a map.
Background Policies Time Intervals
The default time intervals for scheduled policies give optimal performance when Cisco WCS is monitoring up to 500 Cisco Aironet lightweight access points.
Workaround: When Cisco WCS is monitoring more than 500 Cisco lightweight access points, increase the time intervals to the following values:
•Device Status Policy—12 minutes
•Client Statistics—30 minutes
•Rogue AP—120 minutes
Manually Executing Scheduled Tasks
Manually executed scheduled tasks (device status, client statistics, rogue access point, and statistics) do not run immediately if any of the other tasks are already running. Instead, Cisco WCS queues and executes them as soon as the running tasks are completed.
Workaround: Wait for the manually executed scheduled tasks to complete.
The poll interval for Cisco 2700 series location appliances is the time between polls (CSCar15324). When the poll interval is set to 1 second, and the actual poll takes 20 seconds, the start of each poll is 21 seconds apart.
Workaround: Wait for the polling interval to complete.
Slow Imports of FPE Files with More Than 200 Walls
Importing a floor plan editor (FPE) file with more than 200 walls can be slow, and the browser may not report any status or redirect you to any other page.
Workaround: Do not click anywhere on the map page for at least 5 minutes before you try to verify that the file is imported.
Calibrating the Location Model Using Cisco Aironet 802.11a/b/g Wireless Cardbus Adapter Clients
Cisco Aironet 802.11a/b/g Wireless Cardbus Adapter (AIR-CB21AG) clients are not ideal for calibrating the location model (CSCsb52149). The AIR-CB21AG clients do not send the SSID in the probe request when the Broadcast SSID is disabled on the wireless LAN controller.
Workaround: Use an approved wireless client, such as Netgear WAG511.
Restoring an Upgraded Cisco 2700 Series Location Appliance to an Earlier Release
A backup from the latest release of Cisco 2700 series location appliance software cannot be restored on a location appliance running an earlier release (CSCsb54606).
Workaround: Before you upgrade a location appliance to the latest release, Cisco recommends that you create a backup for the earlier release and archive it in case you need to return an upgraded location appliance to an earlier release.
Managing Cisco Wireless Services Modules using Cisco WCS
Unlike other wireless LAN controllers, Cisco Wireless Services Modules (WiSMs) use their service ports to communicate with the Cisco Catalyst 6500 series switch supervisor. The Cisco WCS server uses the WiSM data port to connect to and control the WiSM and its associated Cisco lightweight access points (CSCsb49178).
Using the Cisco WCS Map Editor Tool
Creating a map directly by using a file image from the floor plan editor (FPE) tool is no longer allowed in Cisco WCS. The option to import this type of file is not present in the user interface and attempting to import the file causes Cisco WCS to generate a message indicating that the user needs to enter a valid JPG or PNG image (CSCsb04081). The workaround is to create a map with a regular image and later use the option to edit the floor and reimport the map image with an FPE file. The FPE tool is no longer supported in Cisco WCS. Users are encouraged to use the new Map Editor tool provided within Cisco WCS to draw obstacles, etc.
Using Microsoft Windows 2003 Browsers with Cisco WCS
Browsing on Windows 2003 Cisco WCS servers is not recommended because recommended Windows 2003 security settings cause browsing problems.
This section lists resolved caveats in Cisco WCS 22.214.171.124 for Windows and Linux.
These caveats are resolved in Cisco WCS 126.96.36.199:
•CSCsd93784—RRM Commands on WCS do not work. When the Channel/power Update command is selected, channel or power are not changed automatically on WLC.
•CSCsk91931—When a known Rogue entry is made by an uppercase MAC address on WCS's template, WLC and WCS display it in lowercase which causes an audit error.
•CSCsm75640—WCS overwrites WLC's "snmp syslocation" when an access point joins to the WLC.
These caveats have been closed in Cisco WCS 188.8.131.52:
•CSCsl11236—The configuration change on an individual controller's 802.11b/g parameter (Configure > Controllers > 802.11b/g > Parameters) throws the following exception: [ServletException in:/pages/configure/global/dot11bConfigDetail.jsp] No bean found under attribute key switchingForm.
•CSCsl11361—The roaming candidate AP list sometimes contains incorrect parameters.
For the most up-to-date, detailed troubleshooting information, refer to the Cisco TAC website at the following location:
Click Technology Support, select Wireless from the menu on the left, and click Wireless LAN.
For information on the Cisco Unified Wireless Network Solution and for instructions on how to configure and use the Cisco UWN, refer to the Cisco Wireless Control System Configuration Guide and the Cisco Wireless LAN Controller Configuration Guide.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Copyright © 2006 Cisco Systems, Inc. All rights reserved.