Cisco Cisco 2700 Series Wireless Location Appliance
4
Release Notes for Cisco 2700 and 2710 Location Appliances for Software Release 2.0.48.0
OL-10315-02
Caveats
Location History Timestamps Match Browser’s Locale
The WCS timestamp is based on the browser’s location and not on the location appliance settings.
Changing the time zone of the WCS or on the location appliance does not change the timestamp for the
location history.
Changing the time zone of the WCS or on the location appliance does not change the timestamp for the
location history.
Assign a Controller/Network Design/Event Group to a Location Appliance Before Using Auto-Synch
With auto-synchronization, controllers, network designs, and event groups that are detected as
unsynchronized are synchronized automatically. Before this automatic synchronization can be enabled,
you must assign a controller, event group, or network design to a location appliance.
unsynchronized are synchronized automatically. Before this automatic synchronization can be enabled,
you must assign a controller, event group, or network design to a location appliance.
Controller Name Must be Unique Before Synchronization
The assigned controller names must be unique. If the controller names are duplicated, the
synchronization process occurs only on one controller.
synchronization process occurs only on one controller.
Caveats
This section lists open caveats in location appliance release 2.0.48.0.
Open Caveats
The following caveats are open (unresolved) in this release.
•
CSCsc09186—When you perform the location calibration, the process of taking data points can take
up to one minute per point if a single controller is unreachable.
up to one minute per point if a single controller is unreachable.
Workaround: Verify that controllers are reachable during calibration or remove the controllers that
are not accessible.
are not accessible.
•
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.
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.
Workaround: No known workaround.
•
CSCsd05107—Conducting a client search using the 802.11b/g protocol filter will return the 802.11b
users but not the 802.11g users.
users but not the 802.11g users.
Workaround: Do not filter by the 802.11b/g protocol option. Select the all option.
•
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
or reassign the controller to the location server on the synchronization page.
location server, the changes do not take effect until you either restart the location server or unassign
or reassign the controller to the location server on the synchronization page.
Workaround: Restart the location server or reassign to or unassign the controller from the location
server on the synchronization page.
server on the synchronization page.
•
CSCsd36689—Access points in monitor mode do not detect probing clients as efficiently as when
configured for local mode. These access points do not track the clients’ RSSI values and do not
contribute location information to the location appliance.
configured for local mode. 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.