Configuring a Hierarchical Tree

Tree Setup is unique because it is not a policy (which is reused in other objects), but rather a global configuration that represents the tree displayed for Dashboard, Operations, and Statistics. However since it is set as a configuration, it follows the standard configuration methods, and requires a Commit before it taking effect and a Save to become persistent across reboots.

ADSP can run as a virtual machine on NX9500 and NX9510 model service platforms. WiNG communicates with ADSP using a single sign-on (SSO) authentication mechanism. Once the user is logged in, WiNG gains access to ADSP without being prompted to login again at ADSP. There is no synchronization between the WiNG and ADSP databases. ADSP has its own user database stored locally within its virtual machine. This local database is accessed if a user logs directly into ADSP.

WiNG and ADSP must be consistent in the manner events are reported up through a network hierarchy to ensure optimal interoperability and event reporting. To provide such consistency, WiNG has added support for an ADSPlike hierarchal tree. The tree resides within WiNG, and ADSP reads it from WiNG and displays the network hierarchy in its own ADSP interface. The hierarchal tree can also be used to launch ADSP modules (like Spectrum Analyzer) directly from WiNG.

Note

The hierarchical tree is available on both controllers and service platforms, but not access points.

WiNG uses the following containers within the tree to be consistent with ADSP's hierarchy conventions:

• Country
• Region
• City
• Campus

Hierarchy rules are enforced in the containers. For example, a city can be created under a country or region, but not vice versa. An RF Domain can be placed in any container. However, there cannot be any additional containers under the RF Domain. WiNG‘s RF Domain‘s already use areas and floors, and these will continue to work as they currently do. Floors are also numbered to be consistent with ADSP‘s usage.

To configure a hierarchical tree to use with ADSP:

1. Select Configuration > Management.
2. Click Tree Setup on the top left-hand corner of the UI.
   The Tree Setup screen displays with a System node that requires population with the containers to represent the deployment shared between WiNG and ADSP. The Country, Region, City and Campus containers can be defined in any order, but at least one of these containers is required within the hierarchy before the RF Domain can be added and the hierarchy defined as valid.
3. To add a Country, Region, City or Campus to the tree, select System from the upper, left-hand, portion of the Tree Setup screen.
   

   Note

   If a complete tree configuration has been saved and exported for archive to remote location, it can be imported back into the Tree Setup screen and utilized without having to re-configure the containers and RF Domain of that tree. Select Import to utilize and existing tree configuration.

   

   Note

   If a tree container (country, region, city or campus) has a red box around it, it either has invalid attributes or a RF Domain requires addition.
   An Add Child link displays on the right-hand side of the display.
4. If adding a country, go to Type > Name to scroll to the country of deployment where the RF Domain resides.
   Adding a country first is a good idea since regions, city and campus can all be added as child items in the tree structure. However, the selected country is an invalid tree node until a RF Domain is applied.
5. If adding a region, select Region from the Type drop-down menu and use the Name parameter to enter its name. Select Add to display the region.
   A city and campus can be added as child items in the tree structure under a region. An RF Domain can be mapped anywhere down the hierarchy for a region and not just directly under a Country. For example, a region can have city and campus and one RF Domain mapped.
6. If adding a city, select City from the Type drop-down menu and use the Name parameter to enter its name. Select Add to display the city.
   Only a campus can be added as a child item under a city. The city is an invalid tree node until a RF Domain is applied somewhere within the directory tree.
7. If adding a campus, select Campus from the Type drop-down menu and use the Name parameter to enter its name. Select Add to display the campus.
   A Campus is the last node in the hierarchy before A RF Domain, and it cannot be valid unless it has a RF Domain mapped to it.
8. Select the add RF Domain link at the right-hand side of any container to display an Unmapped RF Domain screen.
9. Provide the default RF Domain name whose deployment area and floor is mapped graphically, and whose events are shared between WiNG and ADSP. Select Add to display the RF Domain within its respective place in the tree hierarchy. A default RF Domain can also be dragged into the tree from the right-hand side of the screen.
10. Once the RF Domain is in the tree, select the add child link at the right-hand side of the RF Domain to display a screen where the RF Domain deployment Area and Floor are defined. Once defined, select Add to populate the tree with the Area and Floor.
11. Provide the Map URL to upload the floor plan created under an Area. Each area can have multiple floors
    

    Note

    While the MAP URL graphic file represents the RF Domain‘s physical device deployment area, devices cannot be dragged into topology or manipulated. To define a network topology that allows an administrator to add devices and manipulate locations, refer to Network View
12. Edit a tree node at any time by selecting it from amongst the Tree Setup screen, and referring to the right-hand side of the screen where a field displays to modify the container.
13. Optionally, select Tree Import Export Template to upload a template.csv file if one is needed for container configuration.
    A sample of the tree template is provided here for reference:

    Row Description

    record type (folder),server,Name,Description,Type,Floor Number,Path(slash delimited),Command(add|delete)

    Actual Row is CSV file

    folder,localhost,US,Country Description,Country,,
    folder,localhost,Southeast,Region Description,Region,,US
    folder,localhost,Alpharetta,City Description,City,,US/Southeast
    folder,localhost,Sanctuary Park,Campus Description,Campus,,US/Southeast/Alpharetta
    folder,localhost,The Falls 1125,Domain Description,RFDomain,,US/Southeast/Alpharetta/Sanctuary Park
    folder,localhost,Queens,,Area,,US/Southeast/Alpharetta/Sanctuary Park/The Falls 1125
    folder,localhost,FloorQLab,,Floor,1,US/Southeast/Alpharetta/Sanctuary Park/The Falls 1125/Queens
    folder,localhost,FloorSLab,,Floor,2,US/Southeast/Alpharetta/Sanctuary Park/The Falls 1125/Queens
    folder,localhost,FloorTLab,,Floor,3,US/Southeast/Alpharetta/Sanctuary Park/The Falls 1125/Queens

    In the CSV file, configure specifc tree node properties:

    Index 1:	Record Type. This value is always 'folder'. Import/export allows the configuration of folder nodes only. Leaf nodes cannot be configured like devices.
    Index 2:	Server Name. This value is always 'localhost' as we are supporting the import/export from localhost only.
    Index 3:	Name. This configures the name/label of the tree node. This is the value which is visible to the user in Tree node.
    Index 4:	Description. This configures the additional information in form, which user wants to store with the Tree node.
    Index 5:	Type. This configures the type of the Tree node. Type can take one of the value "country, region, city, campus, rfdomain, area, floor".
    Index 6:	Floor Number. This is configures the floor number. This is applicable only for the floor node.
    Index 7:	Path. This is /'(slash delimited) from the 'root'.
    Index 8:	add|delete. Allows manipulation of the node. If no value is specified, the default is 'add' . If value is 'delete' then reference node is removed.

14. Select Import Tree Structure to optionally import a .csv file with pre-defined the containers and RF Domain. Importing an existing tree saves an administrator from creating a new one from the beginning.
15. Once the tree topology is defined to your satisfaction, select Export Tree Structure to archive the tree topology (in .csv file format) to a defined location.
    The exported tree topology can be re-imported and automatically displayed within the Tree Setup screen at any time.
16. Select OK to update the tree setup configuration. Select Reset to revert to the last saved configuration.
    

    Note

    Since the tree is set as a configuration, it follows standard configuration methods, and requires a Commit before it taking effect and A Save to become persistent across reboots.