Installation guide

39
Wi-Fi Location-Based Services—Design and Deployment Considerations
OL-11612-01
Cisco Location-Based Services Architecture
the channels for which they are configured (which is why it is important to ensure that they are
configured for the primary channels of all access points in your environment). Once again, these
multicasts are quickly detected by access points operating on these channels in the vicinity of the asset
tags. There is no guarantee, however, that rogue access points or rogue clients are operating on the
channels to which your access points are assigned (primary channels). Because of this, rogue access
points and rogue clients operating on channels other than the primary channel of your access point are
detected during periodic off-channel scans. For an LWAPP access point acting in local mode, this
typically takes place for about 500 milliseconds out of every 180 seconds of operation, or about 50
milliseconds per non-primary channel per 180 second interval.
Rogue Clients
Rogue clients are clients associated to rogue access points. Rogue clients are displayed on the WCS
location floor maps using a black rectangle icon with a skull-and-crossbones, as shown in Figure 24. To
display rogue clients on the WCS location floor map, ensure that the “Show Rogue Clients” view option
is selected at the top of the floor map display and click on “reload” in the left-hand column.
Figure 24 WCS Rogue Client Location Map
Note that beginning with release 4.0 of WCS it is possible to filter the location information displayed by
WCS based on the age of the information. Thus in Figure 24, WCS displays location server information
that has aged up to 15 minutes. Alternatively this value could be set to 2 or 5 minutes for more recent
location information or ½, 1, 3, 6, 12 or 24 hours for less recent information.
Several options are available by clicking on the black rectangular skull-and-crossbones icon under “View
Filters”.
• The total number of rogue clients detected on this floor.