Cisco Cisco 3310 Mobility Services Engine Release Notes
18
Release Notes for Cisco 3300 Series Mobility Services Engine, Release 7.3.101.0
OL-24938-06
Important Notes
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
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.
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.
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.
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.
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.
Software Configuration Guide, Release 7.0.
See Services > Mobility Services > Device Name > Context Aware Service > Advanced > Location
Parameters.
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.
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.
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.
Operational Notes for wIPS
This section lists the operational notes for a mobility services engine.
Prime Infrastructure Screen and Navigation Changes
•
Services replaces Mobility in the Prime Infrastructure navigation bar.