Cisco Cisco 2700 Series Wireless Location Appliance Release Notes

CSCsc64772—When aggressive polling or historical parameters are configured in the location 
server, such as polling for all element categories every 10 seconds and saving history points every 
minute, the database operations can take longer to complete, and the server can momentarily take 
longer to respond to requests. 

CSCsd29958—If you modify the SNMP access for a controller in WCS and push the changes to the 
location server, the changes do not take effect until you either restart the location server or 
unassign/reassign the controller to the location server in the synchronization page.

CSCsd36689—Access points in monitor mode do not detect probing clients. These access points do 
not track the clients’ RSSI values and do not contribute location information to the Location 
Appliance.

Workaround: Configure the access points for local mode.

If you need information about a specific caveat that does not appear in these release notes, you can use 
the Cisco Bug Toolkit to find caveats of any severity. Click this URL to browse to the Bug Toolkit:

(If you request a defect that cannot be displayed, the defect number might not exist, the defect might not 
yet have a customer-visible description, or the defect might be marked Cisco Confidential.) 

For the most up-to-date, detailed troubleshooting information, refer to the Cisco TAC website at 

. Click Technology Support, choose Wireless 

from the menu on the left, and click Wireless LAN.

The Quick Start Guide: Cisco 2700 Series Location Appliance should include the following information 
for location appliances. 

When you have a non-default port or HTTPS turned on, you must pass the correct information along with 
the command. For example, getserverinfo must include -port <<port>> -protocol <<HTTP/HTTPS>>. 
Similarly, for stopping the server, stoplocserver - port <<port>> -protocol <HTTP/HTTPS>>.

You can configure NTP servers to set up the time and date of the 2700 location appliance.