Installation guide

67
Wi-Fi Location-Based Services—Design and Deployment Considerations
OL-11612-01
Deployment Best Practices
In this situation, one possible solution is to use WCS to create a campus location network design for the
buildings and floors that comprise the headquarters location. The 140 access points that are registered
to controller WiSM-1 are assigned to this network design, and an event notification group is created for
the headquarters location. The network design, the controller WiSM-1, and the headquarters event
notification group are all assigned to location appliance 2710-1 and synchronized. In a similar fashion,
the WCS is used to create a second network design and event notification group for the buildings and
floors that comprise the metropolitan locations using controller WiSM-2 and location appliance 2710-2.
You could have also used a single network design that views the entire citywide deployment as one
campus with multiple buildings, allowing the user to click on each individual building on a citywide
map. The design tenet to keep in mind is to synchronize only the controllers that comprise a location
domain to the location appliance servicing that domain. Failing to adhere to this rule can result in
unnecessarily consuming device support capacity and wasting network bandwidth because of controllers
being polled by the wrong location appliance. If there is any doubt whatsoever about which controllers
are assigned to which location appliances, unassign all questionable controllers from the location
appliance and re-assign them properly.
Using this approach, the entire enterprise is managed as a single management domain, with all
management polling and reporting emanating from a centralized WCS. Location appliance 2710-1
handles polling controller WiSM-1 for all information pertaining to tracked devices found within its
location domain, indicated by the red rectangle. Location server 2710-2 handles the polling of controller
WiSM-2 with regard to all tracked devices found in its location domain, shown by the green rectangle.
Except for the fact that the two location domains operate across a common Ethernet network, are
managed from a common management domain, and each possess a controller that shares a common
physical residence on a WiSM blade at headquarters, the two location domains exist entirely
independently of each other.
Multiple Management Domains, Each With a Single Location Domain
In this case, all the managed devices in the enterprise do not conveniently fit into a single management
domain (for example, this might occur because of pre-existing WCS server hardware that cannot scale
to high-end WCS server capacity). Three management domains are necessary, as shown in Figure 45.