Installation guide

69
Wi-Fi Location-Based Services—Design and Deployment Considerations
OL-11612-01
Deployment Best Practices
handles polling of controller WiSM-3 with regard to all tracked devices found in its location domain,
which is shown by the green rectangle. Other than the fact that the three management/location domain
pairs operate across a common Ethernet network and possess controllers that share a common physical
residence with a Cat6500 chassis at headquarters, the three exist independently of each other. This is
very similar conceptually to multiple iterations of the standard deployment model of one WCS and one
location appliance.
Antenna Considerations
Third-Party Antennas
Gain for third-party antennas can be defined via the “Other” option that is available via Monitor > Maps
> Position APs, as shown in Figure 46. Because only the antenna gain and not the propagation pattern
of the antenna is defined for “other” antennas, access points using third-party antennas are not included
in coverage heat maps and client, tag, or rogue location tracking. Note the loss of the antenna orientation
compass when the “Other” option is selected.
Figure 46 Specifying Third-Party Antennas on WCS Floor Maps
In some cases, it may be tempting to substitute a third-party antenna of similar construction with the
same or less gain than an antenna sold by Cisco. Although this may be acceptable from the perspective
of FCC compliance, such actions may yield results that are far less than optimal when attempting to
perform location tracking. Although the antenna gain may in fact be identical to or below that of an
antenna already pre-defined in WCS, the propagation patterns associated with the third-party antenna
may not be identical to that of the Cisco-supplied antenna, as shown in Figure 47.