 Feedback
|
Table Of Contents
Release Notes for Cisco Wireless Control System for Windows or Linux, Release 6.0.202.0
Cisco Unified Wireless Network Solution Components
Operating Systems Requirements
Using the Installer to Upgrade Cisco WCS for Windows
Using the Installer to Upgrade Cisco WCS for Linux
Restoring the Cisco 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 Cisco WCS Start
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Wireless Control System for Windows or Linux, Release 6.0.202.0
April 2011
These release notes describe open caveats for the Cisco Wireless Control System 6.0.202.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.
Server Hardware Requirements
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 if Physical Address Extension (PAE) is enabled. See the 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 Cisco WCS in VMware must follow the specifications for the size of Cisco WCS that you intend to use.
Client Requirements
The Cisco WCS user interface requires Internet Explorer 7.0 or later releases with the Flash plugin or Mozilla Firefox 3 or later releases.
Using a web browser running on Windows 2003 to access the Cisco WCS web GUI is not recommended because 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
Table 1 lists the WCS supported versions of controller, location, and mobility services engine (MSE),
Table 1 WCS Versions
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.06.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.0Windows 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.06.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.0Windows 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.06.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.0Windows 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.06.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.0Windows 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.06.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.0Windows 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.05.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.0Windows 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.05.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.0Windows 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.05.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.0Windows 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.05.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.0Windows 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.05.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.0Windows 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.05.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.0Windows 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.04.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.0Windows 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.x4.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.0Windows 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.x4.0.32.0
Not Applicable
16 Feb 2008
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0Windows 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.03.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.0Windows 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.03.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.0Windows 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.03.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.0Windows 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.03.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.0Windows 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.03.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.0Windows 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.03.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.0Windows 2003 SP2 32-bit
RHEL 4.0 Update 5
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
1 All 5.2.x releases posted after 5.2.148.0 will not be eligible for upgrade to Release 6.0.202.0.
Cisco WCS on WLSE Appliance
Cisco WCS on a WLSE appliance supports up to 1500 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 Cisco WCS on the WLSE appliance.
Finding the Software Release
To find the software release that Cisco WCS is running, see the Cisco Wireless Control System Configuration Guide. If Cisco WCS is already installed and connected, verify the software release by choosing Help > About the Software.
Upgrading Cisco WCS
This section provides instructions for upgrading Cisco WCS on either a Windows or Linux server. It handles the steps you would normally follow to accomplish a manual upgrade (shut down Cisco WCS, perform a backup, remove the old Cisco WCS version, install the new version, restore the backup, and start Cisco WCS). If you choose to use the installer, it searches for any previous Cisco 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 that causes an exit occurs. An upgrade-version.log is also produced and provides corrective measures.
Note
Using the Installer to Upgrade Cisco WCS for Windows
To upgrade Cisco WCS (on a Windows platform) using the automated upgrade, follow these steps:
Step 1
Step 2
Step 3
Several of the values from the previous installation are retained as part of the upgrade. These include the following:
•
•
•
•
•
•
Step 4
Step 5
Note
Step 6
Note
Note
Using the Installer to Upgrade Cisco WCS for Linux
To upgrade Cisco WCS (on a Linux platform) using the automated upgrade, follow these steps:
Step 1
a.
b.
Step 2
Step 3
At this point, the install wizard detects whether a previous version of Cisco WCS is installed and specifies whether the current version is eligible for an automated upgrade. You receive a notification whether or not your most recent Cisco WCS version is eligible for the automated upgrade.
Step 4
Several of the values from the previous installation are retained and carried over as part of the upgrade. These include the following:
•
•
•
•
•
•
Step 5
Step 6
Step 7
Note
Note
Restoring the Cisco WCS Database in a High Availability Environment
During installation, you are prompted to determine if a secondary Cisco WCS server would be used for high availability support to the primary Cisco WCS server. If you opted for this high availability environment and enabled it in the Administration > High Availability page, the status appears as HA enabled. Before performing a database restore, you must convert the status to HA not configured.
Note
Choose the desired option from the following choices to change the status from HA enabled to HA not configured:
•
•
This procedure is used when one of the following instances has occurred:
–
–
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 problem, manually move the files to the new directory by cutting and pasting the files.
If you are upgrading between different releases of the WCS and Controller, check the SNMP MIBs or OID structures on running controller versions for affected changes of features. Controller should be applying commands based on right MIB versions.
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
An e-mail address is now optional when you configure high availability. However, if you enter a properly formatted e-mail address, you must also configure a Cisco WCS e-mail server.
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 on 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 the upgrade. The new client detail report contains the details of association time, disassociation time, and session timeout 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 dynamic-link library (DLLs). Reregistering them corrects the problem.
To reregister the DLLs, follow these steps:
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 behavior is expected.
Also, if you visit the AP Details page 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, choose Configure > Controller Templates, choose TFTP server from the left sidebar menu, and choose Add TFTP Server from the drop-down list. 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 page when only the default server appears.
Conflicting Ports Interrupt Cisco WCS Start
Cisco 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 Cisco WCS requires.
System Error After Upgrade
After upgrading WCS from 4.2.128.0 to 6.0.202.0, the message, "System Error : Wrong Alarm Type rougueUnclassifiedMinor", appears in the UI.
If you see this error, clear your browser cache.
New Features
There are no new features in this maintenance release.
Caveats
The following sections list open and resolved caveats in Cisco WCS 6.0.202.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
Table 2 lists the open caveats in Cisco WCS Release 6.0.202.0.
Resolved Caveats
Table 3 lists caveats resolved in Cisco WCS Release 6.0.202.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, see the Cisco TAC website at the following location:
http://www.cisco.com/cisco/web/psa/troubleshoot.html
Click Wireless and Wireless LAN Management, and 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, see 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.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
