Your software release may not support all of the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Information About
Configuring Location Settings
The
switch determines the location of client
devices by gathering Received Signal Strength Indication (RSSI) measurements
from access points all around the client of interest. The
switch can obtain location reports from up to
16 access points for clients, RFID tags, and rogue access points.
You can configure the
path loss measurement (S60) request for normal clients or calibrating clients
to improve location accuracy.
Configures the path loss measurement (S60) request for calibrating clients or non-calibrating.
The path loss measurement request improves the location accuracy. You can configure the burst_interval parameter for the normal, noncalibrating client from zero through 3600 seconds, and the default value is 60 seconds.
You can configure the path loss measurement request for calibrating clients on the associated 802.11a or 802.11b/g radio or on the associated 802.11a/b/g radio.
If a client does not send probes often or sends them only on a few channels, its location cannot be updated or cannot be updated accurately. The location plm command forces clients to send more packets on all channels. When a CCXv4 (or higher) client associates, the Switch sends it a path loss measurement request, which instructs the client to transmit on the bands and channels that the access points are on (typically, channels 1, 6, and 11 for 2.4-GHz-only access points) at a configurable interval (such as 60 seconds) indefinitely.
Configures the RSSI half life for the clients, calibrating clients, RFID tags, and rogue access points.
You can enter the location rssi-half-life parameter value for the clients, calibrating clients, RFID tags, and rogue access points as 0, 1, 2, 5, 10, 20, 30, 60, 90, 120, 180, or 300 seconds, and the default value is 0 seconds.
Some client devices transmit at reduced power immediately after changing channels, and RF is variable, so RSSI values might vary considerably from packet to packet. The location rssi-half-life command increases accuracy by averaging nonuniformly arriving data using a configurable forget period (or half life).
Note
We recommend that you do not use or modify the location rssi-half-life command.
Configures the RSSI timeout value for the clients, calibrating clients, RFID tags, and rogue access points.
You can enter the RSSI timeout value for the clients, RFID tags, and rogue access points from 5 through 3600 seconds, and the default value is 5 seconds.
For the calibrating clients, you can enter the RSSI timeout value from 0 through 3600 seconds, and the default value is 5 seconds.
Ensuring that recent, strong RSSIs are retained by the CPU is critical to location accuracy. The location expiry command enables you to specify the length of time after which old RSSI averages expire.
Note
We recommend that you do not use or modify the location expiry command.
Step 5
locationalgorithm {rssi-average | simple}
Example:
Switch(config)# location algorithm rssi-average
Configures the algorithm used to average RSSI and signal-to-noise ratio (SNR) values.
You can enter the location algorithm rssi-average command to specify a more accurate algorithm but requires more CPU overhead or the location algorithm simple command to specify a faster algorithm that requires low CPU overhead but provides less accuracy.
Note
We recommend that you do not use or modify the location algorithm command.
Step 6
locationadmin-tagstring
Example:
Switch(config)# location admin-tag
Sets administrative tag or site information for the location of client devices.
You can enter the priority weight from zero through 255.
Step 11
locationrfid {status | timeout | vendor-name}
Example:
Switch(config)# location rfid timeout 100
Configures RFID tag tracking options such as RFID tag status, RFID timeout value, and RFID tag vendor name.
You can enter the RFID timeout value in a range from 60 and 7200 seconds.
Step 12
end
Example:
Switch(config)# end
Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode.
Modifying the NMSP Notification Interval for Clients, RFID Tags, and Rogues (CLI)
The Network Mobility Services Protocol (NMSP) manages communication between the mobility services engine and the controller for incoming and outgoing traffic. If your application requires more frequent location updates, you can modify the NMSP notification interval (to a value between 1 and 180 seconds) for clients, active RFID tags, and rogue access points and clients.
Note
The TCP port (16113) that the controller and mobility services engine communicate over must be open (not blocked) on any firewall that exists between the controller and the mobility services engine for NMSP to function.
The Cisco Support website provides extensive online resources,
including documentation and tools for troubleshooting and
resolving technical issues with Cisco products and technologies.
To receive security and technical information about your
products, you can subscribe to various services, such as the
Product Alert Tool (accessed from Field Notices), the Cisco
Technical Services Newsletter, and Really Simple Syndication
(RSS) Feeds.
Access to most tools on the Cisco Support website requires a
Cisco.com user ID and password.