Location Hierarchy feature enables you to organize your network view within Cisco Spaces based on your physical business location hierarchy and access point deployments. You can organize the hierarchy based specific
brands, regions and business taxonomy that is relevant for your business.
By translating your IT network view into a business view, you are automatically presented with a cleaner business relevant insights report. Any changes to your network topology are automatically reflected here thereby
making it easy to manage.
The Location Hierarchy module also makes it easy for you to manage role-based access, set tracking rules and drive varied outcomes based on the nature of the business location.
Location Hierarchy features as shown in the figure above:
Account Name: Each Cisco Spaces customer is provided with a default account name (root name), and this account name acts as the root location of Cisco Spaces location hierarchy.
Wireless Controller(s): Wireless controller(s) imported in Cisco Spaces. A single controller or multiple controllers added together as additional controllers under a Primary Controller
Groups: Multiple locations or zones grouped together based on geolocation, brand or any other type of grouping depending on the business
Location: All access points within a physical building consolidated as a Location.
This is the most important node in Location Hierarchy as business insights and location analytics calculations are generated from here
Zones: Collection of access points within a section of a building/location. It be defined based on the departments in a physical building of an organization
# of Locations: Number of locations in an Account, Controller, or Group
# of APs: Number of access points in an Account, Controller, Group, Location or Zone
# of BLE Beacons: Number of BLE beacons in an Account, Controller, Group, Location or Zone
# of Proximity Rules: Number of Proximity Rules defined in an Account, Controller, Group, Location or Zone
# of Users: Number of Users in an Account, Controller, Group, Location or Zone
More Actions: Various options to organize and setup Location Hierarchy
Recommended 5 Steps Process to Define Location Hierarchy
Choose primary and additional controllers before importing
Review the default (auto configuration) hierarchy suggested by platform
If the given hierarchy is in tune with physical business locations, then proceed to import as it is and create groups or zones if required
If the auto configuration hierarchy is incorrect, un-check the “Select All” option and import all APs under single location “Unconfigured”
Configure LH manually (Check How-To Section Below)