Configuring Location Settings

Finding Feature Information

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 device determines the location of client devices by gathering Received Signal Strength Indication (RSSI) measurements from access points all around the client of interest. The device 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.

How to Configure Location Settings

Configuring Location Settings (CLI)

Procedure

  Command or Action Purpose
Step 1

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 2

location plm {calibrating [multiband | uniband] | client burst_interval

Example:

Device(config)# location plm client 100

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 Device 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.

Step 3

location rssi-half-life {calibrating-client | client | rogue-aps | tags } seconds

Example:

Device(config)# location rssi-half-life calibrating-client 60

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.

Step 4

location expiry {calibrating-client | client | rogue-aps | tags } timeout

Example:

Device(config)# location expiry calibrating-client 50

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

location algorithm {rssi-average | simple}

Example:

Device(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

location admin-tag string

Example:

Device(config)# location admin-tag

Sets administrative tag or site information for the location of client devices.

Step 7

location civic-location identifier {identifier | host}

Example:

Device(config)# location civic-location identifier host

Specifies civic location information.

You can set the civic location identifier either as a string or host.

Step 8

location custom-location identifier {identifier | host}

Example:

Device(config)# location custom-location identifier host

Specifies custom location information.

You can set the custom location identifier either as a string or host.

Step 9

location geo-location identifier {identifier | host}

Example:

Device(config)# location geo-location identifier host

Specifies geographical location information of the client devices.

You can set the location identifier either as a string or host.

Step 10

location prefer {cdp | lldp-med | static} weight priority_value

Example:

Device(config)# location prefer weight cdp 50

Sets location information source priority.

You can enter the priority weight from zero through 255.

Step 11

location rfid {status | timeout | vendor-name}

Example:

Device(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:

Device(config)# end

Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode.

Example

Modifying the NMSP Notification Interval for Clients, RFID Tags, and Rogues

NMSP manages communication between the Cisco Mobility Services Engine (Cisco MSE) 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 Cisco MSE communicate over must be open (not blocked) on any firewall that exists between the controller and the Cisco MSE for NMSP to function.


Procedure

  Command or Action Purpose
Step 1

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 2

nmsp notification interval {attachment seconds | location seconds | rssi [clients interval | rfid interval | rogues [ap | client ] interval]}

Example:

Device(config)# nmsp notification interval rssi rfid 50

Sets the NMSP notification interval value for clients, RFID tags, and rogue clients and access points.

You can enter the NMSP notification interval value for RSSI measurement from 1 through 180 seconds.

Step 3

end

Example:

Device(config)# end

Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode.

Modifying the NMSP Notification Threshold for Clients, RFID Tags, and Rogues

Procedure

  Command or Action Purpose
Step 1

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 2

location notify-threshold {clients | rogues ap | tags } threshold

Example:

Device(config)# location notify-threshold clients 5

Configures the NMSP notification threshold for clients, RFID tags, rogue clients, and access points.

threshold- RSSI threshold value in db. Valid range is from 0 to 10.

Step 3

end

Example:

Device(config)# end

Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode.

Monitoring Location Settings and NMSP Settings

Monitoring Location Settings (CLI)

This section describes the new commands for location settings.

The following commands can be used to monitor location settings on the .
Table 1. Monitoring Location Settings Commands

Command

Purpose

show location summary

Displays the current location configuration values.

show location statistics rfid

Displays the location-based RFID statistics.

show location detail client_mac_addr

Displays the RSSI table for a particular client.

Monitoring NMSP Settings (CLI)

The following commands can be used to monitor NMSP settings on the .

Table 2. Monitoring NMSP Settings Commands

Command

Purpose

show nmsp attachment suppress interfaces

Displays the attachment suppress interfaces.

show nmsp capability

Displays the NMSP capabilities.

show nmsp notification interval

Displays the NMSP notification intervals.

show nmsp statistics connection

Displays the connection-specific NMSP counters.

show nmsp statistics summary

Displays the common NMSP counters.

show nmsp status

Displays the status of active NMSP connections.

show nmsp subscription detail

Displays all of the mobility services to which the is subscribed.

show nmsp subscription detail ip_addr

Displays details only for the mobility services subscribed to by a specific IP address.

show nmsp subscription summary

Displays details for all of the mobility services to which the is subscribed.

Examples: Location Settings Configuration

This example shows how to configure the path loss measurement (S60) request for calibrating client on the associated 802.11a or 802.11b/g radio:

Device# configure terminal
Device(config)# location plm calibrating uniband 
Device(config)# end
Device# show location summary
This example shows how to configure the RSSI half life for a rouge access point:

Device# configure terminal
Device(config)# location rssi-half-life rogue-aps 20
Device(config)# end
Device# show location summary

Examples: NMSP Settings Configuration

This example shows how to configure the NMSP notification interval for RFID tags:

Device# configure terminal
Device(config)# nmsp notification interval rssi rfid 50
Device(config)# end
Device# show nmsp notification interval
This example shows how to configure the NMSP notification interval for clients:

Device# configure terminal
Device(config)# nmsp notification interval rssi clients 180
Device(config)# end
Device# show nmsp notification interval

Additional References for Location Settings

Related Documents

Related Topic Document Title
System management commands

System Management Command Reference, Cisco IOS XE Release 3SE (Cisco WLC 5700 Series)

Standards and RFCs

Standard/RFC Title
None

MIBs

MIB MIBs Link
All the supported MIBs for this release.

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs

Technical Assistance

Description Link

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.

http://www.cisco.com/support

Feature History and Information For Performing Location Settings Configuration

Release Feature Information
Cisco IOS XE 3.2SE This feature was introduced.