 Feedback
|
Table Of Contents
Release Notes for Cisco Wireless Control System 6.0.170.0 for Windows or Linux
Cisco Unified Wireless Network Solution Components
Hardware Requirements for Server
Operating Systems Requirements
Wireless LAN Controller Requirements
Location Server, Mesh, and MSE
Upgrading to a New Software Release
Using the Installer to Upgrade WCS for Windows
Using the Installer to Upgrade WCS for Linux
Restoring the WCS Database in a High Availability Environment
Cisco WCS Supported on Windows 2003 English and Japanese Operating Systems Only
Notifications in Junk E-mail Folder
Windows XP Cannot Load CAD Files
Deletion of TFTP Server Is Not Updated in the Configuration Backup
Conflicting Ports Interrupt WCS Start
Ability to Limit AP Transmit Power
Inter-Release Controller Mobility (IRCM)
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Wireless Control System 6.0.170.0 for Windows or Linux
Last Revised: November, 2009
These release notes describe open caveats for the Cisco Wireless Control System 6.0.170.0 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.
Contents
These release notes contain the following sections.
•
Cisco Unified Wireless Network Solution Components
•
Cisco Unified Wireless Network Solution Components
The following components are part of the Cisco UWN Solution and are compatible in this release:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Requirements for Cisco WCS
The following server hardware and software is required to support Cisco WCS for Windows or Linux.
Hardware Requirements for Server
Cisco WCS can be run on a workstation or server, and access points can be distributed unevenly across controllers.
•
–
–
–
•
–
–
–
–
–
•
–
–
–
–
Note
Note
Operating Systems Requirements
The following operating systems are supported:
•
Windows 2003/SP2 64-bit installations are not supported. A 32-bit operating system running on a 64-bit capable hardware is supported.
Windows 2003 32-bit installations provide support for up to 64 GB of RAM provided Physical Address Extension (PAE) is enabled. Refer to Windows documentation for instructions on enabling this mode.
•
Red Hat Linux Enterprise Server 5.X 64-bit operating system installations are not supported. A 32-bit operating system running on a 64-bit capable hardware is supported.
•
Individual operating systems running WCS in VmWare must follow the specifications for the size of WCS you intend to use.
Client Requirements
The Cisco WCS user interface requires Internet Explorer 7.0 with the Flash plugin or Mozilla Firefox 3.
Note
Note
Using a web browser running on Windows 2003 to access the WCS web GUI is not recommended because recommended Windows 2003 security settings may cause browsing problems.
The client running the browser must have a minimum of 1 GB of RAM and a 2-GHz processor. The client device should not be running any CPU or memory-intensive applications.
Note
Wireless LAN Controller Requirements
Cisco WCS 6.0.170.0 supports management of the following wireless LAN controllers:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Location Server, Mesh, and MSE
Cisco WCS 6.0.170.0 supports management for the following location server, mesh, and mobility service engine (MSE) software:
•
Note
•
Note
•
WCS on WLSE Appliance
Cisco WCS on a WLSE appliance supports up to 1,500 Cisco Aironet lightweight access points and 161 Cisco wireless LAN controllers. The required processor is a 3.16 GHz Intel Xeon processor (or AMD equivalent) with 3 GB of RAM and 38 GB of free hard drive space.
The Windows operating system is not supported with the WCS on the WLSE appliance.
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 connected, verify the software release by choosing Help > About the Software.
Upgrading to a New Software Release
The Cisco WCS release must be the same or more recent than the controller software release. Upgrade the Cisco WCS first to prevent any unexpected problems. Cisco WCS supports database upgrades only from the following official Cisco WCS releases:
•
•
•
•
•
•
•
•
•
•
•
•
Note
Upgrading WCS
This section provides instructions for upgrading WCS on either a Windows or Linux server. It handles the steps you would normally follow to accomplish a manual upgrade (shut down WCS, perform a backup, remove the old WCS version, install new version, restore the backup, and start WCS). If you choose to use the installer, it searches for any previous WCS versions.
Note
If you choose to use the easy upgrade process, it provides error checking at each step and gives an informative message if an error causing an exit occurs. An upgrade-version.log is also produced and provides corrective measures.
Note
Using the Installer to Upgrade WCS for Windows
Follow these steps to upgrade WCS (on a Windows platform) using the automated upgrade:
Step 1
Step 2
Step 3
Step 4
•
•
•
•
•
•
Step 5
Step 6
Step 7
Note
Note
Using the Installer to Upgrade WCS for Linux
Follow these steps to upgrade WCS (on a Linux platform) using the automated upgrade:
Step 1
a.
b.
Step 2
Step 3
Step 4
Step 5
Step 6
•
•
•
•
•
•
Step 7
Step 8
Step 9
Note
Note
Restoring the WCS Database in a High Availability Environment
During installation, you are prompted to determine if a secondary WCS server would be used for high availability support to the primary WCS server. If you opted for this high availability environment and enabled it in the Administration > High Availability window, the status appears as HA enabled. Before performing a database restore, you must convert the status to HA not configured.
Note
Follow one of these procedures to change the status from HA enabled to HA not configured:
•
•
–
The primary server is down and failover has not been executed, so the secondary server is in SecondaryLostPrimary state.
or
The primary server is down and failover is already executed, so the secondary server is in the SecondaryActive state.
The primary server will now be in HA Not Configured mode, and you can safely perform a database restore.
Important Notes
This section describes important information about Cisco WCS.
If you change the report repository path under Administration > Settings > Report, then the existing saved download report will no longer work. To fix this, manually move the files to the new directory by cutting and pasting the files.
Duplicate AP Name
If you see access points with the same name while applying controller templates or adding them to the map, perform a refresh config. The duplicates in the database will be eliminated.
High Availability
You must enter an e-mail address when configuring high availability. WCS tests the e-mail server configuration and if the test fails (because the mail server cannot connect), WCS does not allow the high availability configuration.
Note
Note
Client Session Report
The new client session report replaces the existing Client Association and Client Detail Report. If you perform an upgrade, Client Association no longer appears in the Reports menu. The data pertaining to these reports migrates successfully, and saved report entries for Client Association and Client Detail reports are migrated. However, the new ClientSessionInfo table is not populated with data from the previous reporting period; the table is populated with client-related data that occurred after upgrade. The new client detail report contains the details of association time, disassociation time, and session timeout along with details of VLAN, session length, client location, Megabit information used, SNR, RSSI, and throughput.
Cisco WCS Supported on Windows 2003 English and Japanese Operating Systems Only
Cisco WCS is supported only on English or Japanese versions of the Windows 2003 operating system. Display problems sometimes occur when you install and run Cisco WCS on operating systems translated to other languages or with locale settings other than English or Japanese.
Notifications in Junk E-mail Folder
If a domain name is not set in the e-mail settings, notifications may end up in the junk e-mail. When the primary device is down, no e-mail notifications are received, but the log message indicates that an e-mail was successfully sent.
Internet Explorer Error
When you click certain links that call Javascript code, you may get an Internet Explorer error as follows:
Problems with this web page might prevent it from being displayed properly or functioning properly. In the future, you can display this message by double clicking the warning icon displayed in the status bar.
This problem appears if another program has deregistered the DLLs below. Re-registering them corrects the problem.
Follow these steps to reregister the DLLs:
Step 1
Step 2
1.
2.
3.
4.
5.
6.
7.
Step 3
Notes about Google Earth
When you launch Google Earth, this message appears:
Google Earth could not write to the current cache or myplaces file location. The values will be set as follows:My Places Path:"C:\Document and Settings\userid\Application Data\Google\GoogleEarth"Cache Path: "C:\Documents and Settings\userid\Local Settings\Application Data\Google\GoogleEarth"This is expected behavior.
Also, if you visit the AP Details window a second time, you get an "invalid path / googleArthLradDetails was requested" HTTP status message. This Google Earth problem can be resolved by deleting the first AP Details occurrence.
Windows XP Cannot Load CAD Files
Internet Explorer 7 running on Windows XP cannot load CAD files because of missing DLLs (C:\Windows\system\DWMAPI.DLL). These DLLs are present only on Windows Vista.
Take one of the following actions:
•
•
Deletion of TFTP Server Is Not Updated in the Configuration Backup
To add a TFTP server, click Configure > Controller Templates, choose TFTP server from the left sidebar menu, and choose Add TFTP Server from the drop-down menu. To add the TFTP server, enter the name and IP address and click Save. If you later delete this TFTP server and back up the configuration (Administration > Background Task > Configuration Backup), the IP address of the TFTP server still appears in the TFTP Server window when only the default server appears.
Conflicting Ports Interrupt WCS Start
WCS fails to start if there is a conflicting port in use. You receive a "Failed to start WCS server" message, but you do not receive a list of conflicting ports. Go to WCS/webnms/logs/wcs-0-0.log and view the conflicting ports. Enter the following to get a list of the process IDs associated with each connection:
In Windows XP and Windows Server 2003, enter netstat -na0.
In Linux, enter netstat -nlp.
In the Task Manager, you see the respective PID and can stop the process using the port that WCS requires.
New Features
There are no new features in this software release. However, there are a few enhancements in this release that are listed in the next section.
Enhancements in This Release
The following section list the enhancements in this release. For your convenience in locating the enhancement bugs in Cisco's Bug Toolkit, the bug titles listed in this section are taken directly from the Bug Toolkit database. These enhancement bug titles are not intended to be read as complete sentences because the title field length is limited. In the bug titles, some truncation of wording or punctuation might be necessary to provide the most complete and concise description. The only modifications made to these titles are as follows:
•
•
•
Note
http://tools.cisco.com/Support/BugToolKit/.
To become a registered cisco.com user, go to the following website:
http://tools.cisco.com/RPF/register/register.do
Table 1 lists the enhancements in this release.
AP Image Predownload
This feature allows you to download the upgrade image to the controller, and then download the image to the access points while the network is still up. A new CLI and controller GUI allow you to specify the boot image for both devices and to reset the access points when the controller resets.
Ability to Limit AP Transmit Power
You use this feature to configure a maximum transmit power that access points cannot exceed. When you configure a maximum transmit power, RRM does not allow any access point attached to this controller to exceed this transmit power level (whether the power is set by RRM TPC or by Coverage Hole Detection). For example, if you configure a maximum transmit power of 11 dBm, then no access point would transmit above 11 dBm unless the access point is configured manually.
RRM Fixes for Medical Devices
This feature improves the way that QoS interacts with the RRM scan defer feature. In deployments with certain power-save clients, you sometimes need to defer RRM's normal off-channel scanning to avoid missing critical information from low-volume clients (for example, medical devices that use power-save mode and periodically send telemetry information).
You can use a client's WMM UP marking to tell the access point to defer off-channel scanning for a configurable period of time if it receives a packet marked UP.
Use this controller CLI command to configure this feature for a specific WLAN:
config wlan channel-scan defer-priority priority [enable | disable] WLAN-id
where priority = 0 through 7 for user priority (this value should be set for 6 on the client and on the WLAN).
Use this command to configure the amount of time that scanning will be deferred following an UP packet in the queue:
config wlan channel-scan defer-time msec WLAN-id
Enter the time value in milliseconds (ms); the valid range is 100 (default) to 60000 (60 seconds). This setting should match the requirements of the equipment on your wireless LAN.
You can also configure this feature on the controller GUI by selecting WLANs, and either editing an existing WLAN or creating a new one. On the WLANs > Edit page, click the Advanced tab. Under Off Channel Scanning Defer, select the scan defer priorities and enter the defer time in milliseconds.
Note
Assignment of a QoS policy (bronze, silver, gold, and platinum) to a WLAN affects how packets are marked on the downlink connection from the access point regardless of how they where received on the uplink from the client. UP=1,2 is the lowest priority, and UP=0,3 is the next higher priority. These are the marking results of each QoS policy:
•
•
•
•
Inter-Release Controller Mobility (IRCM)
This feature supports seamless mobility and Cisco Unified wireless network ( CUWN) services across controllers with different software versions.
Note
RRM is supported between controllers running different versions of code. However, different RF groups will form for the controllers running different code levels. Therefore, separate RF groups do not have the ability to interact with one another, resulting in two groups of radios calculating power and channel separately.
The effect on the network depends on how close the two RF groups are to one another. For example, if you have two controllers, one running software release 4.2.X.X and one running software release 6.0.X.X, and both controllers service access points that are on the same floor, there will be some impact at the boundary between the two groups of access points on channel and TX power decisions.
If you implement on neighboring floors, the result might be greater channel overlap (interference among access points), but TX power would likely not be affected. Non-neighboring floors would be fine. Implementing mixed controllers releases in a random deployment would likely result in significant issues with TX power assignments but would have a minor impact on channel assignments.
Caveats
The following sections list open and resolved caveats in Cisco WCS 6.0.170.0 for Windows and Linux. For your convenience in locating caveats in Cisco's Bug Toolkit, the caveat titles listed in this section are taken directly from the Bug Toolkit database. These caveat titles are not intended to be read as complete sentences because the title field length is limited. In the caveat titles, some truncation of wording or punctuation might be necessary to provide the most complete and concise description. The only modifications made to these titles are as follows:
•
•
•
Note
http://tools.cisco.com/Support/BugToolKit/.
To become a registered cisco.com user, go to the following website:
http://tools.cisco.com/RPF/register/register.do
Open Caveats
Major Open Caveats
There are no major open caveats in Version 6.0.170.0.
Moderate Open Caveats
Table 2 lists the moderate open caveats in Version 6.0.170.0.
Minor Open Caveats
Table 3 lists the minor open caveats in Version 6.0.170.0.
Table 3 Minor Open Caveats
CSCta77783
Backup and upload third party certificates installed on WLC
CSCta93780
Unable to upload customized web bundle from WLC via WCS
Resolved Caveats
Table 4 lists caveats resolved in Cisco WCS 6.0.170.0.
If You Need More Information
If you need information about a specific caveat that does not appear in these release notes, you can use the Cisco Bug Toolkit to find caveats of any severity. Click this URL to browse to the Bug Toolkit:
http://tools.cisco.com/Support/BugToolKit/
(If you request a defect that cannot be displayed, the defect number might not exist, the defect might not yet have a customer-visible description, or the defect might be marked Cisco Confidential.)
Troubleshooting
For the most up-to-date, detailed troubleshooting information, refer to the Cisco TAC website at the following location:
http://www.cisco.com/cisco/web/psa/troubleshoot.html
Click Wireless and Wireless LAN Management. Then choose Autonomous Wireless LAN and Unified Wireless LAN Management.
Related Documentation
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:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
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.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
