Enable
Calculation time
|
Select the
Enable check box to
initiate the calculation of the time required to compute location.
Note
|
This
parameter applies only to clients, rogue access points, rogue clients, and
interferers.
|
Caution
|
Enable
this parameter only under Cisco TAC personnel guidance because it slows down
the overall location calculations.
|
|
Enabled OW Location
|
Select the
Enable check box to
include Outer Wall (OW) calculation as part of location calculation.
Note
|
This parameter is ignored by
the mobility services engine.
|
|
Enable
Data Accuracy Tool
|
Select
the
Enable check box to enable the Data Accuracy Tool.
This parameter is disabled by default.
Note
|
The
Data Accuracy Tool is a web application that displays in the MSE admin UI. Use
this tool to filter the devices outside the venue using location tuning,
maximum RSSI threshold, and based on stationary devices and MAC addresses.
To
use the Data Accuracy tool, enable the
Beta Features from the MSE admin UI. After the beta
features are enabled, scroll down to the bottom of the MSE admin UI and run the
tool. For more information about the Data Accuracy Tool, see
Using Data Accuracy Tool.
|
|
Relative discard RSSI time
|
Enter the number of minutes
since the most recent RSSI sample after which RSSI measurement should be
considered discarded. For example, if you set this parameter to 3 minutes and
the mobility services engine receives two samples at 10 and 12 minutes, it
keeps both samples. An additional sample received at 15 minutes is discarded.
The default value is 3. Allowed values range from 0 to 99999. A value of less
than 3 is not recommended.
Note
|
This parameter applies only
to clients, rogue access points, rogue clients, and interferers.
|
|
Absolute discard RSSI time
|
Enter the number of minutes
after which RSSI measurement should be considered stale and discarded,
regardless of the most recent sample. The default value is 60. Allowed values
range from 0 to 99999. A value of less than 60 is not recommended.
Note
|
This parameter applies only
to clients.
|
|
RSSI Cutoff
|
Enter the RSSI cutoff value,
in decibels (dBs) with respect to one (1) mW (dBm), above which the mobility
services engine will always use the access point measurement. The default value
is –75.
Note
|
When 3 or more measurements
are available above the RSSI cutoff value, the mobility services engine
discards any weaker values (lower than the RSSI cutoff value) and uses the 3
(or more) strongest measurements for calculation; however, when only weak
measurements below the RSSI cutoff value are available, those values are used
for calculation.
|
Note
|
This parameter applies only
to clients.
|
Caution
|
Modify
only under Cisco TAC personnel guidance. Modifying this value can reduce the
accuracy of location calculation.
|
|
Enable Location Filtering
|
Location filtering is used to
smooth out the jitters in the calculated location. This prevents the located
device from jumping between two discrete points on the floor map.
|
Chokepoint Usage
|
Select
the
Enable check box to enable chokepoints to track
Cisco-compatible tags.
|
Use
Chokepoints for Interfloor conflicts
|
Perimeter chokepoints or weighted location readings can be used
to locate Cisco-compatible tags.
Options:
-
Never: When selected, perimeter chokepoints are not used to
locate Cisco-compatible tags.
-
Always: When selected, perimeter points are used to locate
Cisco-compatible tags.
-
Floor Ambiguity: When selected, both weighted location readings
and perimeter chokepoints are used to locate Cisco-compatible tags. If similar
locations are calculated by the two methods, the perimeter chokepoint value is
used by default.
|
Chokepoint Out of Range timeout
|
When a
Cisco-compatible tag leaves a chokepoint range, the timeout period entered is
the period that passes before RSSI values are again used for determining
location.
|
Absent
Data cleanup interval
|
Enter
the number of minutes that data for
absent mobile stations is kept. An
absent mobile station is one that was discovered but does
not appear in the network. The default value is 1440.
|
Use
Default Heatmaps for Non Cisco Antennas
|
Select
this check box to enable the usage of default heatmaps for non-Cisco antennas
during the Location Calculation. This option is disabled by default.
|
Movement Detection
Parameters
|
Individual RSSI change threshold
|
This
parameter specifies the Individual RSSI movement recalculation trigger
threshold.
Enter
a threshold value between 0-127 dBm.
Modify
only under Cisco TAC personnel guidance.
|
Aggregated RSSI change threshold
|
This
parameter specifies the Aggregated RSSI movement recalculation trigger
threshold.
Enter
a threshold value between 0-127 dBm.
Modify
only under Cisco TAC personnel guidance.
Note
|
When
tags do not move and are being tracked, the telemetry information such as
temperature will not get forwarded to the tag engine. If you do not want the
tags to move but still want the notification to get forwarded, you must set the
Aggregated RSSI change threshold value to zero.
|
|
Many
new RSSI change percentage threshold
|
This
parameter specifies Many new RSSI movement recalculation trigger threshold in
percentage.
Modify
only under Cisco TAC personnel guidance.
|
Notification Parameters
|
Rate Limit
|
Enter the rate, in
milliseconds, at which the mobility services engine generates notifications. A
value of 0 (default) means that the mobility services engine generates
notifications as fast as possible (Northbound notifications only).
|
Queue Limit
|
Enter the event queue limit
for sending notifications. The mobility services engine drops any event above
this limit. Default values: Cisco 3350 (30000), Cisco 3310 (5,000), and Cisco
2710 (10,000).
|
Retry Count
|
Enter the number of times
to generate an event notification before the refresh time expires. This
parameter can be used for asynchronous transport types which do not acknowledge
the receipt of the notification and there is a possibility that the
notification may be lost in transit. The default value is 1.
Note
|
The
mobility services engine does not store events in its database.
|
|
Refresh Time
|
Enter the wait time, in
minutes, that must pass before a notification is resent. For example, if a
device is configured for In Coverage Area notification and it is constantly
being detected within the Coverage Area. The notification is sent once every
refresh time. Default value is 0 minutes.
|
Drop Oldest Entry on Queue
Overflow
|
(Read-only). The number of
event notifications dropped from the queue since startup.
|
Serialize Events per Mac
address per Destination
|
Select this option if you
want the successive events for the same MAC address to be sent to a single
destination in a serial manner.
|