 Feedback
|
Table Of Contents
Release Notes for Cisco 3300 Series Mobility Services Engine, Release 7.4.100.0
Cisco 3300 Series Mobility Services Engine and Services
Upgrading the MSE to 7.4.100.0 from Older Releases Without Data Migration
Upgrading the MSE to 7.4.100.0 from Older Releases with Data Migration
Upgrading the MSE to 7.4.100.0 from 7.0.201.204 or Later Releases
Restoring an Old Database from to 7.4.100.0
Updated Software Version Shown in the Prime Infrastructure After Polling
CAS and wIPS License Requirements
Cisco MSE Location Services and Advanced Location Services Software
Cisco Adaptive Wireless IPS Software
Cisco Mobility Services Licenses for High Availability
Operational Notes for a Mobility Services Engine
Automatic Installation Script for Initial Setup
Parameter Changes During Upgrade from 6.0.x to 7.0.x
Mandatory Default Root Password Change
Configuring the Prime Infrastructure Communication Username and Password Using MSE setup.sh
Configuration Changes for Greater Location Accuracy
Synchronization Required When Upgrading to Release 7.4.100.0 or Importing CAD Floor Images
Floor Change or Minimum Distance Required for Location Transitions to Post to the History Log
AeroScout MobileView Release 4.1 Required for Northbound Notifications
Separate Partner Engine Software Install Not Required for Tag Contextual Information
Non-Cisco Compatible Extensions Tags Not Supported
Cisco Compatible Extensions Version 1 Tags Required at a Minimum
Monitoring Information Varies for Clients and Tags
Location History Time stamps Match Browser Location
PDAs and Smartphone with Limited Probe Requests Might Affect Location
Prime Infrastructure Screen and Navigation Changes
Operational Notes for Location Analytics Service
Adaptive wIPS Signature Enhancement
Wireless Security and Spectrum Intelligence Module for AP 3600
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco 3300 Series Mobility Services Engine, Release 7.4.100.0
First Published: February, 2013OL-28564-01These release notes describe the requirements, features, limitations, restrictions (caveats), and related information for release 7.4.100.0 of the Cisco 3300 and 3355 mobility services engines and its services:
•
Context Aware Service (CAS)
•
Note
Note
Note
Contents
These release notes contain the following sections:
•
•
Introduction
This section introduces the Cisco 3300 series mobility services engine (MSE) and the 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 7.4.100.0:
•
CAS relies on two engines for processing the contextual information it receives. The Context Aware Engine for clients and tags ("KC" licenses) processes data for Wi-Fi clients and tags using the RSSI information. The Context Aware Engine for tags ("KT" licenses) processes data for Wi-Fi tags using RSSI and TDoA information. Both these engines can be deployed together or separately depending on the business needs.
Note
•
Note
Note
Note
http://www.cisco.com/en/US/products/ps9806/products_installation_and_configuration_guides_list.html
Note
http://www.cisco.com/en/US/products/ps9817/products_installation_and_configuration_guides_list.html
Note
http://www.cisco.com/en/US/products/ps9742/prod_installation_guides_list.html
Note
Software Compatibility Matrix
Table 1 lists the compatibility matrix for the various releases of the Cisco mobility services engine, Cisco Wireless Control System, Cisco Prime Network Control System, and Cisco Wireless LAN controller.
Upgrading the MSE
For instructions on automatically downloading the software using the Prime Infrastructure 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 3355 Mobility Services Engine Getting Started Guide.
You can find these documents at the following URL:
http://www.cisco.com/en/US/products/ps9742/prod_installation_guides_list.html
This section contains the following topics:
•
•
•
Upgrade Scenarios
There are four scenarios available to upgrade MSE to 7.4.100.0 from 6.0, 7.0.105.0, and 7.0.112.0:
•
•
•
•
Upgrading the MSE to 7.4.100.0 from Older Releases Without Data Migration
To upgrade from older releases to 7.4.100.0 without data migration, follow these steps:
Step 1
All data existing on the system will be lost and a fresh blank database will be created.
Step 2
CISCO-MSE-L-K9-7-4-100-0-64bit.db.tar
Step 3
Note
Step 4
This gives you the following:•
•
–
–
–
–
•
Step 5
Step 6
chmod +x CISCO-MSE-L-K9-7-4-100-0-64bit.bin
Step 7
service msed stop
Step 8
Step 9
Doing so installs the new database using the four .zip files for the database along with the MSE software.
Initial database installation can take a long time (20 minutes at least -or- approximately). Do not cancel the installer midway through the installation process.
Once installed, follow the regular procedure to start, stop, or add an MSE to the Prime Infrastructure.
Upgrading the MSE to 7.4.100.0 from Older Releases with Data Migration
To upgrade the MSE to 7.4.100.0 from older releases with data migration, follow these steps:
Step 1
All data existing on the system will be lost and a fresh blank database will be created.
Step 2
CISCO-MSE-L-K9-7-4-100-0-64bit.db.tar
Step 3
Note
Note
Note
Step 4
This gives you the following:•
•
–
–
–
–
•
Step 5
Step 6
Step 7
service msed stop
Step 8
The installer automatically detects if there is an old database present and asks the relevant questions.
Sample Upgrade Questions
Installation Check
---------------------
The system appears to have a Cisco Mobility Services Engine already installed. If you choose Continue", all the currently installed components will be removed permanently (Only database and license files will be preserved
->1 - Exit
2 - Continue
ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT: 2
-------------------------------------------------
-------------------------------------------------
Data Migration Check
-------------------------------------------------
The currently installed version of the MSE database is not directly compatible with the new version. The system will now migrate the database from existing database to the new system. Choose an appropriate option below -
->1 - Proceed to migrate data from previous release
2 - Abort Installation
ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT: 1
--------------------------------------------------
--------------------------------------------------
Do you wish to migrate history data too? It can take a long time if history data is large in size (Y/N): y
Exporting data from currently installed database.
This may take a while .....
Data migration successfully completed. Will now proceed with installation of new image.
Installing...
----------------------
-------------------------------------------------
-------------------------------------------------
-------------------------------------------------
-------------------------------------------------
Database Installation
-----------------------
The installer will now install the database. This may take a long time (- 15 minutes). Do not cancel the installer.
PRESS <ENTER> TO CONTINUE:
---------------------------------------------------
---------------------------------------------------
!!!!!! IMPORTANT NOTE !!!! :
---------------------------------
The system is minimally configured right now. It is strongly recommended that you run the setup script under /opt/mse/setup/setup.sh to configure all appliance related parameters immediately after installation is complete. The hostname must be set correctly on the system. The Cisco MSE platform will NOT start if it is configured incorrectly or not configured at all. Additionally, it is strongly recommended that the Cisco MSE is configured to use the same NTP servers as the controllers with which it will be synchronized. This is essential to the correct operation of the Cisco Mobility Services Engine. Both these parameters may be configured as part of the setup script.
PRESS <ENTER> TO CONTINUE:
-------------------------------------------------
-------------------------------------------------
Importing Data
-------------------------------------------------
Loading data into newly installed database. This may take a while ......
PRESS <ENTER> TO CONTINUE:
Upgrading the MSE to 7.4.100.0 from 7.0.201.204 or Later Releases
To upgrade the MSE to 7.4.100.0 from 7.0.201.204 or later releases, follow these steps:
Note
Step 1
Step 2
cd /opt/installers
./CISCO-MSE-L-K9-7-4-100-0-64.bit.bin
Step 3
The installer automatically detects if there is an old database present and asks the relevant questions.
Restoring an Old Database from to 7.4.100.0
To restore an old database, follow these steps:
Note
Step 1
Step 2
Step 3
Table 2 Release Matrix
5.2.0
5.2, 6.0, 7.0
6.0
6.0, 7.0
Step 4
Step 5
Compressed Software Image
If you download the mobility services engine image *.gz file using the Prime Infrastructure, 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 chmod +x filename.bin command.
The MSE virtual appliance software is distributed as an Open Virtualization Archive (OVA) file. You can install the MSE virtual appliance using any of the methods for deploying an OVF. For more information on deploying the MSE virtual appliance, see Chapter 5: "MSE Delivery Modes" in the Cisco Context-Aware Service Configuration Guide, Release 7.4.100.0, and Cisco Adaptive Wireless Intrusion Prevention System, Release 7.4.100.0, respectively.
Updated Software Version Shown in the Prime Infrastructure After Polling
After a software update, the new mobility services engine software version does not immediately appear in mobility services engine queries on the Prime Infrastructure. Up to 5 minutes is required for the new version to appear. Prime Infrastructure, by default, queries the mobility services engine for status every 5 minutes.
CAS and wIPS License Requirements
Client and wIPS licenses are installed from the Prime Infrastructure (Administration > License Center). See, Chapter 2: "Adding and Deleting Mobility Services Engines and Licenses" in the Cisco Context-Aware Service Configuration Guide, Release 7.4.100.0, and Cisco Adaptive Wireless Intrusion Prevention System, Release 7.4.100.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.4.100.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.4.100.0, at the following URL:
http://www.cisco.com/en/US/prod/collateral/wireless/ps9733/ps9742/data_sheet_c07-473865.html
Licensing Information for MSE
Cisco MSE Location Services and Advanced Location Services Software
•
•
Note
•
•
SKUs for Cisco MSE Location Services
Following are the Cisco MSE Location Services software licenses.
Note
SKU to upgrade from a Location Services to Advanced Location Services:
L-UPG-LS-1AP
License to upgrade to Advanced Location Services for 1 access point.
Cisco Adaptive Wireless IPS Software
Licenses are available for Monitor Mode and Enhanced Local Mode for Cisco Adaptive wIPS.
SKUs for Cisco Adaptive wIPS in Monitor Mode
Cisco Adaptive wIPS Monitor Mode licenses are based on the number of Monitor Mode access points. Cisco MSE 3355 supports up to 5,000 Monitor Mode access points. The Cisco MSE virtual appliance supports up to 10,000 Monitor Mode access points, depending on server resources. All licenses are additive.
Note
L-WIPS-MM-1AP
Supports 1 Monitor Mode access point.
L-WIPS-MM-100AP
Supports 100 Monitor Mode access points.
L-WIPS-MM-1000AP
Supports 1000 Monitor Mode access points.
SKUs for Cisco Adaptive wIPS in Enhanced Local Mode
Cisco Adaptive wIPS Enhanced Local Mode software licenses are based on the number of local mode (data serving) access points. Cisco MSE supports up to 5,000 local mode access points. The Cisco MSE virtual appliance can track up to 10,000 local mode access points, depending on the server resources. All licenses are additive.
Note
Cisco Mobility Services Licenses for High Availability
No separate license is required for high availability. To enable high availability, you need to deploy a primary Cisco MSE appliance with Cisco CAS and Adaptive wIPS licenses, and a secondary Cisco MSE appliance without any Cisco CAS or Adaptive wIPS license.
Important Notes
This section describes the operational notes and navigation changes for CAS, wIPS, and the mobility services engine for Release 6.0.103.0 and later releases.
Features and operational notes are summarized separately for the mobility services engine, CAS, and wIPS.
This section contains the following topics:
•
•
•
Operational Notes for a Mobility Services Engine
This section lists the operational notes for the mobility services engine and contains 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 3355 Mobility Services Engine Getting Started Guide.
You can find these documents at the following URL:
http://www.cisco.com/en/US/products/ps9742/prod_installation_guides_list.html
Parameter Changes During Upgrade from 6.0.x to 7.0.x
You will notice a change in the tracking limits when you do the following:
1.
2.
If limits are greater than licensed counts, limits are removed and licensed counts are enforced instead (CSCtd57386).
Controller and Associated Mobility Services Engine Must be Mapped to the Same NTP and Prime Infrastructure Server
Communication between the mobility services engine, the Prime Infrastructure, and the controller are in Coordinated Universal Time (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, Prime Infrastructure, and the mobility services engine.
The mobility services engine and its associated controllers must be mapped to the same NTP server and the same Prime Infrastructure server.
Local time zones can be configured on a mobility services engine to assist network operations center personnel in locating events within logs.
Note
http://www.cisco.com/en/US/products/ps9742/prod_installation_guides_list.html
Mandatory Default Root Password Change
You must change the default root password of the mobility services engine while running the automatic installation script to ensure optimum network security.
You can also change the password using the Linux passwd command.
Note
Configuring the Prime Infrastructure Communication Username and Password Using MSE setup.sh
You can configure the Prime Infrastructure Communication username and password using the MSE setup.sh script file.
Scenarios which you might encounter while configuring the Prime Infrastructure username and password are as follows:
•
•
•
•
Note
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 Context Aware Service > Advanced > Location Parameters page on the Prime Infrastructure.
The following RSSI parameters might require modification:
•
•
•
•
Caution
Operational Notes for CAS
This section lists the operational notes for a mobility services engine and contains the following topics:
•
•
•
•
•
•
•
•
Synchronization Required When Upgrading to Release 7.4.100.0 or Importing CAD Floor Images
When upgrading to Release 7.4.100.0 from Release 6.x (and earlier), you must synchronize after the software upgrade and also when CAD-generated floor images are imported into the Prime Infrastructure.
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 new location of the element is at least 30 feet (10 meters) from its original location.
Note
•
•
•
See Services > Mobility Services > Device Name > Context Aware Service > Administration > History Parameters.
Logs can be viewed at Services > Mobility Services > Device Name > Systems > Log.
AeroScout MobileView Release 4.1 Required for Northbound Notifications
If AeroScout MobileView Release 4.1 and earlier is in use, incorrect responses are sent to those northbound notifications received from the mobility services engine. Northbound notifications are then sent again by the mobility services engine, overloading the notification queue and resulting in reports of dropped notifications.
The workaround for this is to upgrade to AeroScout MobileView Version 4.1 (CSCsx56618).
Separate Partner Engine Software Install Not Required for Tag Contextual Information
In Release 5.2 and later, the partner software that supports tag contextual information (temperature, availability, and location calculations) is bundled into the mobility services engine software. No separate download of partner engine software is required as in Release 5.1.
Non-Cisco Compatible Extensions Tags Not Supported
The mobility services engine does not support non-Cisco CX Wi-Fi tags. Additionally, these non-compliant tags are not used in location calculations or shown on the Prime Infrastructure maps.
Cisco Compatible Extensions Version 1 Tags Required at a Minimum
Only Cisco CX Version 1 (or later) tags are used in location calculations and mapped in the Prime Infrastructure.
Monitoring Information Varies for Clients and Tags
Note
In 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 Indicator (RSSI) reading.
Calibration Models and Data
If AeroScout engine is used for calculation, then calibration models that are done through the Prime Infrastructure do not apply to tags. If Cisco tag engine is used, everything done on the Prime Infrastructure calibration models and data uses tag calculation.
Calibration models and data do not apply only to tags if AeroScout engine is used for tag calculation. It always applies to Wireless clients, Interferers, Rogue APs, and Rogue Clients.
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 URL:
Advanced Location Parameters
Advanced location parameters does not apply to tags if AeroScout engine is used and otherwise it works always. 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.
See Services > Mobility Services > Device Name > Context Aware Service > Advanced > Location Parameters.
Location History Time stamps Match Browser Location
The Prime Infrastructure time stamp is based on the browser location and not on the mobility services engine settings. Changing the time zone on the Prime Infrastructure or on the mobility services engine does not change the time stamp for the location history.
PDAs and Smartphone with Limited Probe Requests Might Affect Location
Many PDAs like smartphones and other Wi-Fi devices with power save mode 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.
Prime Infrastructure Screen and Navigation Changes
•
•
•
Operational Notes for Location Analytics Service
This section lists the operational notes for Location Analytics service.
WebGL Compatibility
•
•
•
•
Note
Jboss Issue
Sometimes Location Analytics service does not start up because of a stray Jboss process that runs as a root user. If Analytics engine does not start and if you notice a stray Jboss process with root permissions running, then you must to do the following:
•
•
•
•
New Feature Support
This section provides a brief description of what is new in this release. For more information about these features, see the Cisco MSE CAS Configuration guide and MSE wIPS configuration guide.
MSE Licensing Changes
The following are the licensing changes done in Release 7.4
•
•
–
–
•
Note
Note
Advanced Location Services
The following are the two advanced location services:
•
•
Location Analytics Service
The Advanced Location services includes the recently acquired ThinkSmart technoloies Software, which has been integrated into the Cisco Mobility Services Engine. The Location Analytics is a system that provides a set of tools packaged for analyzing Wi-Fi device location data that is coming from the MSE.
The Location Analytics analyzes wireless device location data and provides analytic information for historical trends and patterns. This enables greater visibility into customer movements and behavior throughout the building and throughout the day. The Location Analytics can determine device parameters such as dwell times, crowding, path choice, and aggregate these for common understanding. Business can better understand how their customers interact with different parts of their building or environment such as, where the customers enter from, what are the most popular areas during the day, how long it takes to get around, etc. This allows for better facility planning, measurement of changes to the environment, and business interaction with customers.
Mobile Concierge Service
It includes the Mobile Concierge SDK, a developer's kit that provides an easy to use approach to developing applications and services that leverage the Mobility Services Engine and provide content that is highly personalized for the individual and the context. The Application Partner Ecosystem can use these APIs to provide access to applications and services developed by third-parties for use with the Mobility Services Engine. Mobile Concierge SDK allows end users to receive push notifications, be seamlessly on-boarded to the Wi-Fi network and receive personalized services.
It is a support for L2 MSAP. This allows service discovery without associating to the Network and without requiring a native application on the smartphone. This capability is available only on Android phones shipping in CY13 which have the Snapdragon silicon from Qualcomm Atheros. It also delivers precise indoor location capabilities on mobile devices, by interoperating with Cisco Wi-Fi infrastructure. This collaboration provides a better indoor location capability in venues with Cisco Wi-Fi infrastructure, as well as enhances service discovery, provides greater context, and delivers a better mobile user experience.
New wIPS Signature Support
The following are the new wIPS signatures introduced in Release 7.4.100.0:
•
•
•
Adaptive wIPS Signature Enhancement
In Release 7.4, new signature support in Enhanced Local Mode (ELM) is introduced.
Rogue Scaling
Rogue client per rogue AP has been increased from 16 to 256 for all Controllers and 64 for WLC 2504.
Wireless Security and Spectrum Intelligence Module for AP 3600
The wireless security and spectrum intelligence module for AP 3600 does the following:
•
•
•
•
•
MSE Meridian Integration
Prior to Release 7.4, Meridian integration with MSE was a manual process and from Release 7.4 onwards, it is a single step process to enable the Meridian integration.
Meridian uses the location update and containment events from the MSE to display the location of a mobile device in the mobile application. In addition, Meridian provides an online content management system to create placemarks, mobile application content, and routing for indoor navigation.
MSE-Qualcomm Solution
The Map Extraction Tool (MET) accepts an indoor map (DXF File) of a venue and after some user input generates QC Map XML and PNG Image that capture the geometric features for walls and doors and POIs such as room numbers. Apart from it, it also generates span xml containing horizontal and vertical span of indoor map. The MET supports following features:
•
•
•
•
•
Caveats
This section lists the open caveats in 7.4.100.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:
•
•
•
If you are a registered cisco.com user, view Bug Toolkit on cisco.com at the following website:
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.doThis section contains of the following topics:
Open Caveats
Table 3 lists the open caveats in Release 7.4.100.0.
Resolved Caveats
Table 4 lists the open caveats in Release 7.4.100.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 URL:
http://www.cisco.com/cisco/web/support/index.html
Click Troubleshooting, choose your product, and then click the Troubleshoot and Alerts heading on the product page to find information on the problem you are experiencing and other service advisories.
Related Documentation
The following documents are related to the mobility services engine:
•
http://www.cisco.com/en/US/products/ps9742/tsd_products_support_series_home.html
•
http://www.cisco.com/en/US/products/ps9817/products_installation_and_configuration_guides_list.html
•
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.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section. 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. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2013 Cisco Systems, Inc. All rights reserved.
