Table Of Contents
Release Notes for Cisco 3300 Series Mobility Services Engine, Release 18.104.22.168
These release notes describe open and resolved caveats for Release 22.214.171.124 of the Cisco 3300, 3350, and 3355 Mobility Services Engines and its two services:
•Context Aware Service (CAS)
•Adaptive Wireless Intrusion Protection Service (wIPS).
Note Before installing this software, see the "System Requirements" section for details on compatibility with Cisco wireless LAN controllers and Cisco Wireless Control Systems (WCS).
Note You must purchase licenses from Cisco to retrieve information on tags and clients from access points. See the "Ordering CAS Client and Tag Licenses for the Mobility Services Engine" section for more information. You must purchase licenses from Cisco to support wIPS monitor mode access points. See the "Ordering Adaptive wIPS Licenses for the Mobility Services Engine" section.
These release notes contain the following sections:
This section introduces the Cisco 3300 series Mobility Services Engine (MSE) andthe various services that it supports.
Cisco 3300 Series Mobility Services Engine and Services
The Cisco 3300 Series Mobility Services Engine supports various services within the overall Cisco Unified Wireless Network (CUWN).
The Cisco 3300 Series Mobility Services Engine currently supports the following services in release 126.96.36.199:
•Context Aware Service (CAS)—Allows a mobility services engine to simultaneously track thousands of mobile assets and clients by retrieving contextual information such as location, temperature, and availability.
CAS relies on two engines for processing the contextual information it receives. The Context Aware Engine for Clients processes data received from Wi-Fi clients and the Context Aware Engine for Tags processes data received from Wi-Fi tags. Both of these engines can be deployed together or separately depending on the business need. This service was introduced in release 5.1.
Note You must purchase licenses from Cisco to retrieve contextual information on tags and clients. See the "Ordering CAS Client and Tag Licenses for the Mobility Services Engine" section.
•Wireless Intrusion Protection Service (wIPS)—Provides wireless-specific network threat detection and mitigation against malicious attacks, security vulnerabilities, and sources of performance disruption within the CUWN infrastructure. wIPS visualizes, analyzes, and identifies wireless threats, and centrally manages mitigation and resolution of security and performance issues using Cisco monitor mode access points. Proactive threat prevention is also supported to create a hardened wireless network core that is impenetrable by most wireless attacks.
Note You must purchase licenses from Cisco to support wIPS. See the "Ordering Adaptive wIPS Licenses for the Mobility Services Engine" section.
Note Evaluation licenses for 100 clients,100 tags, and 20 access points (wIPS) come standard on each mobility services engine installed with release 6.0 and later. Evaluation licenses are good for 60 days.
Note CAS and wIPS can operate simultaneously on the Cisco 3350, 3355, and 3310 mobility services engines.
Note See the online version of the Cisco Context-Aware Software Configuration Guide, Release 7.0, for details on configuring and monitoring CAS on the mobility services engine at the following URL:
Note See the online version of the Cisco Wireless Intrusion Prevention System Configuration Guide, Release 7.0 for details on configuring and monitoring wIPS on the mobility services engine at the following URL:
Note See the online versions of the Cisco 3350 and 3310 Mobility Services Engine Getting Started Guides for details on the physical installation and initial configuration of the mobility services engines at the following URL:
Software and Aeroscout CLE Compatibility Matrix
Table 1 lists the compatibility matrix for the various releases of WCS, Controllers, 2710 Location Based Services, MSE 3300 Series, and Aeroscout CLE.
The following minimum releases are required to configure and monitor CAS on the Cisco 3300 Series Mobility Services Engine, WCS, and Wireless LAN Controller. (See Table 2).
Table 2 Minimum Software Requirements
Service System Minimum Software Release
Context-Aware Software and Wireless Intrusion Prevention System1
Mobility Services Engine
188.8.131.52 (or later)
184.108.40.206 (or later)
220.127.116.11 and 18.104.22.168
22.214.171.124 and 126.96.36.199
4.2.130 (or later)
Note Release 5.0.x is not supported with release 6.0.
188.8.131.52 (or later)
Cisco WCS Navigator
184.108.40.206 (or later)
1 Release 5.2 is the minimum software requirement for the controller, WCS, and mobility services engine to support the Cisco Adaptive Wireless Intrusion Prevention System.
Upgrading to This Release
For instructions for automatically downloading the software using WCS or for manually downloading the software using a local or remote connection, see the "Updating Mobility Services Engine Software" section in Chapter 2 of the Cisco 3350 Mobility Services Engine Getting Started Guide and Cisco 3310 Mobility Services Engine Getting Started Guide.
You can find these documents at the following URL:
This section consists of the following topics:
Upgrading from Release 5.x to 6.0.x or 7.0.x
Caution The number of supported clients, tags, and access points (wIPS) is reset to 100 clients, 100 tags, and 20 access points when you upgrade to release 6.0. All tracking beyond these limits is lost. These limits correspond to the 60-day evaluation licenses that are standard on mobility services engines.
Caution When upgrading mobility services engine from 6.0 to 7.0.x, if any limits have been set on wireless clients or rogues, they will get reset because of the wired client limit change in 7.0.x.
Caution You must back up the mobility services engine database before upgrading from release 5.x to 6.0 to preserve client, tag, and access point configurations. You can restore the database after the software upgrade.
Caution In order to prevent the configuration loss in the AeroScout Engine due to the MAP ID change caused by the WCS upgrade from 5.0 to 7.0, the CLEv.220.127.116.11 must be installed before restoring the MSE database.
To upgrade to release 6.0.x, follow these steps:
Step 1 Register the Product Authorization Key (PAK).
Note You receive a PAK when you order a license. If you have lost your PAK, you can use your sales order or the UDI number of the mobility services engine to register.
•Client and wIPS licenses are registered at the following URL:
•Tag licenses are registered at the following URL:
Step 2 Back up the mobility services engine database and the AeroScout database:
a. To back up the mobility services database (network designs controller configurations, clients, and access points), follow these steps:
1. Choose Services > Mobility Services.
2. Click the name of the mobility services engine for which you want to back up the database.
3. Choose Maintenance > Backup from System left sidebar menu.
4. Enter a name for the backup file.
5. Click Submit (see Figure 1).
b. To back up the AeroScout database (tag licenses, chokepoints, and TDOA receivers) see the AeroScout Context-Aware Engine for Tags for Cisco Mobility Services Engine User's Guide at:
Figure 1 System > Maintenance Window
Step 3 Download release 18.104.22.168:
a. Choose Services > Mobility Services.
b. Click the name of the mobility services engine on which you want to upgrade the software.
c. Choose Maintenance > Download Software from under the System menu.
d. Choose either an uploaded image or browse and upload an image.
e. Click Download.
Step 4 Install release 22.214.171.124 using the MSE CLI:
a. To overwrite existing software, enter:
./mse software file name
b. To do a fresh install, enter:
Note enter this once in the directory. Enter no when prompted to keep the old database.
cd /opt/installers./mse software file name
Step 5 Restore the mobility services engine and AeroScout database:
a. To restore the mobility services database, follow these steps:
1. Choose Services > Mobility Services.
2. Click the name of the mobility services engine on which you upgraded the software.
3. Choose Maintenance > Restore from the System sidebar menu.
4. Choose the file to restore from the drop-down list.
5. Click Submit.
b. To restore the AeroScout database see the AeroScout Context-Aware Engine for Tags for Cisco Mobility Services Engine User's Guide at the following URL
Step 6 Install licenses:
See Chapter 2 of the Context-Aware Services Configuration Guide, Release 7.0 at the following URL:
Compressed Software Image
If you download the mobility services engine image *.gz file using WCS, the mobility services engine automatically decompresses (unzips) it, and you can proceed with the installation as before.
If you manually download the compressed *.gz file using FTP, you must decompress the files before running the installer. These files are compressed under the LINUX operating system and must be decompressed using the gunzip utility program. The unzip method you use is defined by the filename you are trying to unzip.
To make the bin file executable, use the following command:
chmod +x filename.bin
Updated Software Version Shown in WCS After Polling
After a software update, the new mobility services engine software version does not immediately appear in mobility services engine queries on WCS. Up to 5 minutes is required for the new version to appear. WCS, by default, queries the mobility services engine for status every 5 minutes.
CAS and wIPS License Requirements
Client and wIPS licenses are installed from WCS (Administration > License Center). See, Chapter 2: "Adding and Deleting Mobility Services Engines and Licenses" in the Cisco Context-Aware Service Configuration Guide, Release 7.0, and Cisco Adaptive Wireless Intrusion Prevention System, Release 7.0, respectively.
Tag licenses are installed using the AeroScout System Manager. See the "Installing Tag Licenses" section in Chapter 2: "Adding and Deleting Mobility Services Engines and Licenses in the Cisco Context-Aware Service Configuration Guide, Release 7.0.
For complete details on ordering and downloading licenses, see the Cisco 3300 Series Mobility Services Engine Licensing and Ordering Guide for Context-Aware Mobility Software, and Adaptive wIPS, Release 7.0, at the following URL:
Ordering CAS Client and Tag Licenses for the Mobility Services Engine
CAS software licenses are based on the number of Wi-Fi client and Wi-Fi tag devices tracked. The Cisco 3350 Mobility Services Engine allows for the tracking of up to 18,000 devices (combined count of Wi-Fi clients and Wi-Fi tags) and the 3310 Mobility Services Engine allows for the tracking of up to 2000 devices (combined count of Wi-Fi clients and Wi-Fi tags).
Licenses for Cisco Compatible Extensions (CX) tags (version 1 or later) and clients are offered independently. The client license also includes tracking of rogue clients and rogue access points.
Licenses for tags and clients are offered in quantities ranging from 1000 to 12,000 units and can be combined to meet the location tracking requirements of a CAS deployment. For example, combining the AIR-CAS-3KC-K9, AIR-CAS-12KC-K9, and AIR-CAS-1KT-K9 licenses provide, tracking of 15,000 Wi-Fi clients and 1000 Wi-Fi tags on a Cisco 3350 mobility services engine (see Table 3).
CAS License Ordering Summary
Order numbers for client and tag licenses are summarized in Table 3.
Table 3 Order Numbers for Client and Tag Licenses
Order Number Licenses Client Licenses 1
License for tracking 1000 client devices.
License for tracking 3000 client devices.
License for tracking 6000 client devices.
License for tracking 12,000 client devices.
License for tracking 1000 tag devices.
License for tracking 3000 tag devices.
License for tracking 6000 tag devices.
License for tracking 12,000 tag devices.
1 All client licenses include tracking of rogue clients and rogue access points.
Ordering Adaptive wIPS Licenses for the Mobility Services Engine
Adaptive wIPS software licenses are based on the number of full-time monitoring access points (often referred to as monitor mode access points) that are deployed in the network. The licenses may be combined to arrive at the number of monitor mode access points required to run the Adaptive wIPS deployment. For example, combining AIR-WIPS-AP-5, AIR-WIPS-AP-25, and AIR-WIPS-AP-500 licenses provides support for 530 monitor mode access points.
Adaptive wIPS License Ordering Summary
Order numbers for Adaptive wIPS licenses are summarized in Table 4.
Note From the 126.96.36.199 Release onwards, the evaluation license for wIPS monitor mode access points is 10.
This section describes important information about the operational notes and navigation changes for CAS, wIPS, and the mobility services engine for release 188.8.131.52 and later releases.
Features and operational notes are summarized separately for the mobility services engine, CAS, and wIPS.
This section consists of the following topics:
Operational Notes for a Mobility Services Engine
This section lists the operational notes for an mobility services engine and consists of the following topics:
Automatic Installation Script for Initial Setup
An automatic setup wizard is available to help you initially set up the mobility services engine.
An example of the complete automatic setup script is provided in the Cisco 3350 Mobility Services Engine Getting Started Guide and Cisco 3310 Mobility Services Engine Getting Started Guide.
You can find these documents online at the following URL:
Parameter Changes During Upgrade from 5.0.x to 6.0.x or 7.0.x
You will notice a change in the tracking limits when you:
1. Configure tracking limits in 5.0.x.
2. Upgrade to 6.0.x or 7.0.x.
If limits are greater than licensed counts, limits are removed and licensed counts are enforced instead.
Controller and Associated Mobility Services Engine Must be Mapped to the Same NTP and WCS Server
Communications between the mobility services engine, WCS, and the controller are in universal time code (UTC). Configuring the network time protocol (NTP) on each system provides devices with the UTC time. An NTP server is required to automatically synchronize time between the controller, WCS, and the mobility services engine.
The mobility services engine and its associated controllers must be mapped to the same NTP server and the same WCS server.
Local time zones can be configured on a mobility services engine to assist network operations center personnel in locating events within logs.
Note You can configure NTP server settings during the automatic installation script. See the Cisco 3350 Mobility Services Engine Getting Started Guide or Cisco 3310 Mobility Services Engine Getting Started Guide for details on the automatic installation script. You can find these documents online at the following URL:
Mandatory Default Root Password Change
You must change the default root password of the mobility services engine during the automatic installation script to ensure optimum network security.
You can also change the password using the Linux command, passwd.
Note During first time login, even if you choose Skip (S), you will be prompted to enter the password. This is because it is mandatory to change root password during first time login.
Root Password Configuration
During the first time MSE setup script run, the Skip option provided for configuring root password is not honored even if it is specified. This is because the first time login and setup script invocation enforces the default credential change. So this prompts you to change the password (CSCsz44105).
Configuring WCS Communication Username and password using MSE setup.sh
You can configure the WCS Communication username and password using the MSE setup.sh script file.
Scenarios which you might encounter while configuring the WCS Username and password:
•If you configure a new WCS username and password, the password provided is applicable for the new WCS username created.
•If you only configure WCS username without configuring WCS password, then the default password admin is applied to the configured username.
•If you only configure WCS password without configuring the WCS username, then the password for the admin user is changed.
•If you configure an existing user name for the WCS username and also configure the password, then the password for that existing user is changed.
Note These users are API users, and they do not have corresponding OS users on MSE appliance.
Revoking MSE License Using MSE CLI
You can also revoke an MSE license from MSE CLI manually without using WCS.
To revoke an MSE license:
Step 1 Login to an MSE using CLI.
Step 2 Navigate to /opt/mse/licensing/
Step 3 Delete the license file by running this command:
rm /opt/mse/licensing/license file name.lic
where license file name is the name of the license file.
Step 4 Restart the MSE process.
The MSE license is revoked.
Networks with Large Access Point Deployments Might Experience Slower Location Updates
In networks with a large number of access points (approximately 2000 or more), mobility services engines might experience a slowdown in location calculation and heatmap updates for clients, tags, and access points (CSCsk18810).
Large Burst of Notifications Might Cause Drop of Notifications
A mobility services engine might fail to send notifications if it receives a large burst of notifications. The dropped notification count appears on the Services > Context Aware Notifications window.
See CSCsu43201 in the Open Caveats section for workaround.
Configuration Changes for Greater Location Accuracy
In some RF environments, where location accuracy is around 60 to 70% or where incorrect client or tag floor location map placements occur, you might need to modify the moment RSSI thresholds in the aes-config.xml file in the opt/locserver/conf/ directory of the mobility services engine (CSCsw17583).
The RSSI parameters that might need modification are:
Caution Please contact TAC for assistance in modifying these parameters.
Operational Notes for CAS
This section lists the operational notes for a mobility services engine and consists of the following topics:
Synchronization Required When Upgrading to Release 184.108.40.206 or Importing CAD Floor Images
When upgrading to release 220.127.116.11 from release 6.x (and earlier) you must synchronize after the software upgrade and also when CAD-generated floor images are imported into WCS.
Floor Change or Minimum Distance Required for Location Transitions to Post to the History Log
When history logging is enabled for any or all elements (client stations, asset tags, rogue clients, and access points), a location transition for an element is posted only if it changes floors or the element's new location is at least 30 feet (10 meters) from its original location.
Navigation Path: Services > Mobility Services > Device Name > Context Aware Service > Administration > History Parameters.
Logs can be viewed at Services > Mobility Services > Device Name > Systems > Log.
Release 4.1 of AeroScout MobileView Required for Northbound Notifications
If a release of AeroScout MobileView earlier than 4.1 is in use, incorrect responses are sent to those northbound notifications received from the mobility services engine. Northbound notifications are then resent by the mobility services engine, overloading the notification queue and resulting in reports of dropped notifications.
The workaround for this is to upgrade to Mobile View version 4.1(CSCsx56618).
Non-Cisco Compatible Extensions Tags Not Supported
The mobility services engine does not support non-Cisco CX Wi-Fi tags. Additionally, these noncompliant tags are not used in location calculations or shown on WCS maps.
Cisco Compatible Extensions, Version 1 Tags Required at a Minimum
Only Cisco CX version 1 tags (or later) are used in location calculations and mapped in WCS.
Monitoring Information Varies for Clients and Tags
On the Monitor > Clients page (when Location Debug is enabled), you can view information on the last heard access point and its corresponding (Received Signal Strength Indication) RSSI reading. This information is not available on the Monitor > Tags page.
Calibration Models and Data Apply Only to Clients
Calibration models and data apply only to clients. Calibration for tags is done using the AeroScout System Manager.
See Chapter 7, "Context-Aware Planning and Verification" in the Cisco Context-Aware Software Configuration Guide, Release 7.0 for more details on client calibration.
See the AeroScout Context-Aware Engine for Tags for Cisco Mobility Services Engine User's Guide at the following link:
Advanced Location Parameters Apply Only to Clients
Settings for advanced location parameters related to RSSI, chokepoint usage, location smoothing, and assignment of outside walls on floors, are not applicable to tags.
See the "Editing Advanced Location Parameters" section in Chapter 7 of the Cisco Context-Aware Software Configuration Guide, Release 7.0.
WCS Navigation Path: Services > Mobility Services > Device Name > Context Aware Service > Advanced > Location Parameters.
Location History Time stamps Match Browser's Location
The WCS time stamp is based on the browser's location and not on the mobility services engine settings. Changing the time zone on WCS or on the mobility services engine does not change the time stamp for the location history.
PDAs with Limited Probe Requests Might Affect Location
Many PDAs do not continuously send out probe requests after an initial association to the CUWN. Therefore, calculating the location accuracy of such PDAs using RSSI readings is not always optimal.
Mandatory Setting Required on Intel 802.11n and 802.11 b/g/n Client Cards for Accurate Calibration
The Cisco CX RM option within Intel's Enterprise Security Profile must be enabled to ensure adequate calibration data points are collected for Intel 802.11n and 802.11 b/g/n client cards. You can use the Intel Client Software PROSET package to enable the Cisco CX RM option in the Enterprise Security Profile (CSCsl40623).
Operational Notes for wIPS
This section lists the operational notes for a mobility services engine.
Mobility Services Engine with wIPS Service Enabled Mistakenly Allows a Controller to Be Assigned to Multiple MSEs
When wIPS is configured on the mobility services engine, a controller can be assigned to more than one mobility services engine in error. By design, a controller can only be assigned to one mobility services engine and an error appears in the WCS page when you synchronize a mobility services engine and a controller (CSCsx38955).
WCS Screen and Navigation Changes
•Services replaces Mobility in the navigation bar of WCS.
•A centralized license center to install and view license status is available (Administration > License Center).
•A Switches tab is a new synchronize option to support the new wired Catalyst switch and wired client feature (Services > Synchronize Services).
New Feature Support
The new features for the mobility services engine, CAS, and wIPS are summarized under separate headings.
This section consists of the following topics:
Cisco 3355 Mobility Services Engine Support
The 18.104.22.168 release supports the new Cisco 3355 Mobility Services Engine.
Common CAS and wIPS Features
Both the CAS and wIPS services can operate on the Cisco 3350 and 3310 mobility services engines simultaneously. CAS and wIPS can now be deployed with the Cisco 3350, or the 3310 platforms.
Both platforms support services separately or concurrently as needed.
For information about the coexistence and scalability of services, see the Cisco 3300 Series Mobility Services Engine Licensing and Ordering Guide.
The MSE 3300 Series platform offers the advantage of centralizing support of mobility services within the Cisco WLAN infrastructure and enables third-party application integration through a common API.
Context-Aware Software Features
This section summarizes the features for Context-Aware Software and consists of the following topics:
Troubleshooting and Notification Enhancements
The following new troubleshooting and configuration enhancements have been implemented in Release 22.214.171.124:
•Mobility Services Engine support of up to 300 notifications per second per destination
•Enhanced network mobility services protocol (NMSP) troubleshooting GUI
•Improved error logging
•Better visibility into northbound notifications
•Enhanced synchronization history
The enhanced notification capabilities allow you to receive a great number of real-time notifications in a timely manner.
The improved error logging and enhanced troubleshooting provides information when data is not being updated properly, It helps you to troubleshoot the problems and provide a way to trace the path of data and drill down to the exact problem.
This feature enables location tracking of all Wi-Fi and interference devices across the WLAN with synchronization on a per-floor and per-building level. It also increases the efficiency of tracking Wi-Fi devices or interference devices on a per-floor or per-building basis across large campus or distributed deployments.
Performance and Accuracy Enhancements
The following Performance and Accuracy features have been implemented in this release:
•Post calculation enhancements
•Detailed view of the number of destinations configured with status
•Type of each destination
With these performance improvements, the accuracy is now improved to the average of 5m and CFD of 7m 90% of the time.
Context-Aware Software with Cisco CleanAir Features
This section summarizes the features for the Context-Aware Software with CleanAir and consists of the following sections:
Reporting Capability for Interferers
This reporting option provides reporting capabilities for the top 10 worst interference devices. By default it displays all interferers which have severity greater than or equal to 5 and further filtering can be done by band, severity and options. These report tables provide instant visibility into the 10 worst interference incidents currently being reported to the system. Interferers are classified by band (802.11b/g/n or 802.11a/n).
You can use workflow links to efficiently view interference reports in the context of location or drill down to the radio level to perform troubleshooting and analysis.
This feature allows you to perform very granular analysis and to get a better understanding of the impact that devices causing interference have on the network.
Correlation of Interference Devices Across Multiple Wireless LAN Controllers
This feature enables multiple access points to hear the same interference event. The MSE correlates and aggregates interference events that span more than one WLC. It will identify and clarify that a source of interference is coming from a single interference device.
This feature not only provides visibility into the source of interference but identifies that it is the same interference that might be causing problems across larger network coverage areas. This feature indicates when to resolve a single source of interference, so that time is not wasted looking for multiple sources.
Interference History Tracking and Playback
The MSE collects and stores location tracking information on reported interference devices and provides details for forensics and analysis. The visual playback capability shows the exact movement and impact as the interferer moves within the network for the selected time of playback.
Historical interference tracking information and detailed playback allows you to correlate problems and quickly troubleshoot network issues.
This information also allows regular long- term tracking of organizational trends and provides visibility for monitoring non-Wi-Fi device usage and for policy enforcement.
The report launch pad interface allows highly customizable views of all reported interference devices so that you can get the required information and the visibility.
Location of Interferers Including Zone of Impact
This feature provides detailed location and information about the visibility of an interference device, including the zone impacted, from a Wireless Control System floor map. By default, interferers on b/g band are displayed on the map.
You can also see the zone of impact based on the interferer status, severity, and interferer type from the Interferer Filter page.
This feature saves valuable time in finding an interference source so that it can be permanently mitigated or policy can be changed.
The level of detailed visibility also provides valuable information on the impact not only to networks but to specific clients within the zone of impact, saving time in troubleshooting and reducing the cost for IT support.
For details on all the features discussed in this section, see the Cisco Context-Aware Configuration Guide, Release 7.0, at the following link:
Adaptive Wireless Intrusion Prevention Software Features
This section summarizes the features for the wIPS (Adaptive Wireless Intrusion Prevention Software) and consists of the following topics:
Supported on Cisco 3350 and 3310 Series Mobility Service Engine
wIPS is supported on 3350 and 3310 series mobility services engines in release 6.0 and 7.0.x. Previously, wIPS was supported only on the 3310 mobility services engine in release 5.2.
For details on all the features discussed in this section, see the Cisco Adaptive Wireless Intrusion Prevention System Configuration Guide, Release 7.0 at the following link:
The following sections list Open Caveats and Resolved Caveats in Release 126.96.36.199 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:
•Commands are in boldface type.
•Product names and acronyms may be standardized.
•Spelling errors and typos may be corrected.
Note If you are a registered cisco.com user, view Bug Toolkit on cisco.com at the following website:
To become a registered cisco.com user, go to the following website:
This section consists of the following topics:
Table 5 lists the open caveats in Version 188.8.131.52.
Table 6 lists the Release 6.0.x caveats resolved in Release 184.108.40.206.
Table 7 lists the Customer found defects that were fixed in 220.127.116.11
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:
(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.)
For the most up-to-date, detailed troubleshooting information, see the Cisco TAC website at the following URL:
Click Troubleshooting, choose your product, and then select the Troubleshoot and Alerts heading on the product page to find information on the problem you are experiencing and other service advisories.
The following documents are related to the mobility services engine:
•Cisco Context-Aware Software Configuration Guide, Release 7.0
•Cisco Adaptive Wireless Intrusion Prevention System Configuration Guide, Release 7.0
•The WCS Online Help available with the WCS product.
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.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)