Cisco Cisco 3365 Mobility Services Engine Release Notes
18
Release Notes for Cisco Mobility Services Engine, Release 7.4.121.0
OL-28564-03
Upgrading the MSE
•
Tags: Tag Emergency button.
•
Interferers: Interferer severity change, cluster center change, or merge.
See Services > Mobility Services > Device Name > Context Aware Service > Administration > History
Parameters.
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.
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.
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.
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.
Infrastructure.
Monitoring Information Varies for Clients and Tags
Note
This information is missing if the AeroScout Tag Engine is used.
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.
heard access point and its corresponding Received Signal Strength Indicator (RSSI) reading.
Calibration Models and Data
Calibration models that are applied through the Prime Infrastructure do not apply to tags if AeroScout
engine is used for calculation. If the Cisco tag engine is used, then everything applied on the Prime
Infrastructure calibration models and data uses tag calculation.
engine is used for calculation. If the Cisco tag engine is used, then everything applied 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.
always applies to wireless clients, interferers, rogue APs, and rogue clients.