Cisco Cisco 3365 Mobility Services Engine Release Notes

Page of 40
32
Release Notes for Cisco Mobility Services Engine, Release 8.0.110.0
OL-32458-01
  Operational Notes for Mobility Services Engine
MSE Location REST APIs
The MSE Location REST APIs always show the last known state of clients. When it shows the last 
known state as Probing, it does not mean that the client is probing currently. This is the same with other 
fields such as x, y, floorid. Networkstatus is the only field that shows whether the client is active or 
inactive, and all other fields show the last known values.
Operational Notes for Context Aware Service
This section lists the operational notes for a Mobility Services Engine and contains the following topics:
Synchronization Required When Upgrading to Release 8.0.110.0 or Importing CAD Floor Images
When upgrading to Release 8.0.110.0 from Release 7.x, 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
The other conditions for history logging are as follows:
Clients: Association, authentication, re-association, re-authentication, or disassociation.
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.
Logs can be viewed at Services > Mobility Services > Device Name > Systems > Log.