Have an account?

  •   Personalized content
  •   Your products and support

Need an account?

Create an account

Cisco DNA Spaces Configuration Guide

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco DNA Spaces Configuration Guide

Chapter Title

Location Hierarchy in Cisco DNA Spaces

Results

Updated:
December 8, 2019

Chapter: Location Hierarchy in Cisco DNA Spaces

Location Hierarchy in Cisco DNA Spaces

This chapter describes the structure of the location hierarchy in Cisco Digital Network Architecture (DNA) Spaces, and how to define the location hierarchy in Cisco DNA Spaces.

Overview of Location Hierarchy

In Cisco DNA Spaces, you can import the locations in the same structure in which you have defined in your wireless network such as Cisco Unified Wireless Network (Cisco AireOS or Cisco Catalyst) or Cisco Meraki.

Each Cisco DNA Spaces customer is provided with a default customer name (root name), and this customer name acts as the root location of Cisco DNA Spaces location hierarchy. You can import the locations in the same structure in which they are defined in Cisco Unified Wireless Network or Cisco Meraki. For Cisco Unified Wireless Network, you can use Cisco DNA Spaces even without installing the Cisco CMX. However, this option will be having certain restrictions for the location hierarchy structure.

As Cisco DNA Spaces provides universal account, you can import and manage the locations of both Cisco Unified Wireless Network and Cisco Meraki. However, the wireless network specified when creating your customer account will be your base network. A proximity rule can include the locations of both Cisco Unified Wireless Network and Cisco Meraki.

You can create proximity rules such as captive portal rule, engagement rule, and profile rule, and view access points, BLE beacons, users, and child locations for any location in the location hierarchy. The number of access points, BLE beacons, proximity rules, child locations, and users for each location in the location hierarchy are displayed against that particular location. For example, the number of proximity rules, child locations, and users for a group are shown against that group in the location hierarchy. The count of these location parameters are shown in a cumulative manner.

Prerequisites for Defining the Location Hierarchy

To define the location hierarchy in the Cisco DNA Spaces dashboard, you must first define the required hierarchy structure in your wireless provider system such as Cisco Meraki or Cisco Unified Wireless Network. In addition, you must establish connection between Cisco DNA Spaces and your wireless network. When you try to add a wireless network in the location hierarchy, Cisco DNA Spaces asks you to provide the login credentials to connect to that wireless network. For the WLC Direct Connectoption, it is only required to ensure that the required access points are configured in the Cisco Wireless Controller.

Defining the Location Hierarchy

Cisco DNA Spaces supports the following wireless networks:

  • Cisco Meraki: If your wireless network is Cisco Meraki, you can define the location hierarchy using the Cisco Meraki option.

  • Cisco Unified Wireless Network with Cisco CMX Cisco (CMX On Prem): If your wireless Network is Cisco Unified Wireless Network and if you are having a Cisco CMX installed, you can define the location hierarchy using the CMX ON Prem option.

  • Cisco Unified Wireless Network with Cisco Wireless Controller : You can use Cisco DNA Spaces with Cisco Unified Wireless Network even if you don’t have installed the Cisco CMX. If your wireless Network is Cisco Unified Wireless Network, and if you are not having the Cisco CMX installed, you can define the location hierarchy using the WLC Direct Connect option.


Note
For the WLC Direct Connect option, you can ensure that appropriate data transfer happens between Cisco Wireless Controller and Cisco DNA Spaces using a Cisco DNA Spaces Connector.

Based on your wireless network, choose the required instructions from the following:

Defining the Location Hierarchy for Cisco Meraki

To import the Cisco Meraki locations, first you must add the Cisco Meraki Organization under the customer name. You can then import Meraki networks. When you import a Meraki network, its floors, and access points are also imported. You can group the access points and create zones at network or floor level. You can group the locations at customer name, or organization level. You can also rename the customer name.

Before creating the location hierarchy, ensure that all the prerequisites are met. To know the prerequisites for creating the location hierarchy, see the Prerequisites for Defining the Location Hierarchy.


Note

You must have Cisco Meraki credentials to import the locations. Thereafter, location hierarchy synchronizes with Cisco Meraki using a Meraki service account. So, you must configure the Cisco Meraki Service account in your Cisco Meraki Customer account for background network synchronization to keep the Location Hierarchy up-to-date. However, to connect Cisco DNA Spaces to Cisco Meraki, you must still use your Meraki customer account. For more information on configuring the Cisco Meraki service account, see Configuring Cisco Meraki Service Account

The location hierarchy for Cisco Meraki network is as follows:

Meraki > Organization > Network > Floor > Access Points.

The Location Hierarchy for Cisco Meraki is shown in the following figure.

Figure 1. Location Hierarchy for Meraki

If you do not have Meraki credentials you can import the locations using Meraki API keys. For more information on importing the locations from Meraki using the API keys, see Importing Meraki Locations Using the API Keys.

If you have the Meraki credentials, to import the Meraki locations to Cisco DNA Spaces, perform the following steps:


Note
After defining the location hierarchy, ensure that you define timezones for locations. The timezone defined affects the Cisco DNA Spaces rules and reports.

Adding a Cisco Meraki Organization

To create the location hierarchy in Cisco DNA Spaces, first you must add the Cisco Meraki Organization of which you want to import the locations to the location hierarchy.


Note
Cisco DNA Spaces enables you to add multiple Cisco Meraki Organizations to the location hierarchy so that you can connect to the multiple Meraki organizations simultaneously.

To add a Cisco Meraki Organization to the location hierarchy, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierrachy.

Step 2

In the Location Hierarchy window that appears, click More Actions for the customer name (root name).

Step 3

ChooseAdd a Wireless Network.

Step 4

From the Wireless Network drop-down list that appears, choose Meraki.

Step 5

Enter the user name and password for your Meraki account, and click Connect account.

Note 
You can also connect to Meraki using the Wi-Fi icon in the right pane of the dashboard. If you are already connected to Meraki, the fields to enter the login credentials will not appear.
Step 6

From the Organization drop-down list, choose the Cisco Meraki Organization from which you want to import the locations.

Step 7

Click Add.

The organization that is added gets listed in the location hierarchy.

Adding a Network to Cisco Meraki Organization

Cisco DNA Spaces enables you to maintain the network, and floor structure followed for the location hierarchy in Meraki. After adding a Cisco Meraki Organization to the location hierarchy, you can import its networks, and the associated floors.

To import a network and its associated floors to the location hierarchy, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, click Location Hierarchy.

Step 2

In the 'Location Hierarchy window, click the More Actions icon at the far right of the Cisco Meraki Organization for which you want to add the network.

Step 3

Choose Add Network.

Step 4

In the Add Network window, select the networks that you want to add to the location hierarchy.

The Add Network window appears with all the available networks for that Cisco Meraki Organization.

Step 5

Click Add.

The networks added gets listed in the location hierarchy along with its associated floors.

Note 
In Meraki, ensure that the network name is not duplicated.

Creating Zones and Adding Access Points

You can group the access points of a network or floor using zones. You can create the zones at network or floor level.


Note
You cannot modify the access points for a floor.

To create a zone for a network or floor, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

Step 2

In the Locations window, click the More Actions icon at the far right of the network or floor under which you want to create the zone.

Step 3

Choose Add Zone.

Step 4

In the Add Zone window that appears, perform the following steps:

  1. In the Enter Zone Name Here field, enter a name for the zone.

  2. In the Select Access Points area, check the check box for the access points that you want to add to the zone.

  3. Click Add.

What to do next

Tip

Before creating the zones, locate the access points that you want to include in the zone in the Meraki dashboard.

Note
When you add an access point of a network or floor to a zone, that access point will not be available for that network or floor. The access points added to a zone will not be available for other zones.
Importing Meraki Locations Using the API Keys

To import Meraki locations using the API keys, perform the following steps:

Procedure
Step 1

In the Location Hierarchy window, click the More Actions icon for the customer name (root name), and click Add a Wireless Network.

Step 2

In the window that appears, from the Add a Wireless Network drop-down list, choose Meraki.

Step 3

Click the Import Organization using API link that appears when you select Meraki.

Step 4

In the API Key field, enter the API Key for Meraki, and click Fetch Organizations.

The organizations for that API key gets listed.
Step 5

Select the organization that you want to import, and click Add.

The organization gets listed in the Locations window.

Step 6

Add the networks under the organization using theAdd Network in the More Actions menu for the organization.

When you import a network, the floors and access points under it also get imported.
Step 7

Create zones under the floors using the Add Zones in the More Actions menu for the floors.

Defining the Location Hierarchy for Cisco Unified Wireless Network with Cisco CMX

If you have the Cisco CMX installed, you can use theCMX on Prem option for defining the location hierarchy for Cisco Unified Wireless Network. The CMX on Prem option enables you to import the locations in the same hierarchy in which you have defined them in the Cisco CMX. Initially, you must add CMX nodes to the location hierarchy under the customer name. You can then import campuses. When you import a campus, its buildings, floors, and access points are also imported. You can create zones at building or floor level by grouping the access points. You can group the locations at customer name (root name), CMX node, or campus level. You can also rename the customer name.


Note
The Cisco Wireless Controller must be able to reach Cisco DNA Spaces cloud over HTTPS.

Before creating the location hierarchy, ensure that all the prerequisites are met. To know the prerequisites for creating the location hierarchy, see the Prerequisites for Defining the Location Hierarchy.

The location hierarchy for Cisco Unified Wireless Network with a Cisco CMX installation is a follows:

Cisco CMXOn Prem Node > Campus > Building(network) > Floor > Access Points

The location hierarchy of the Cisco Unified Wireless Network - CMX is shown in the following figure.

Figure 2. Location Hierarchy for Cisco Unified Wireless Network

If your Cisco CMX is not publicly accessible, you can manually import the locations. For more information on manually importing the locations, see the Creating the Location Hierarchy by Manually Uploading the Cisco CMX Details.


Note
After defining the location hierarchy, ensure that you define timezones for locations. The timezone defined affects the Cisco DNA Spaces rules and reports.

To create the location hierarchy for the CMX on Premoption, perform the following steps:

Adding a CMX Node


Note
Cisco DNA Spaces supports CMX 10.0 or later.

To add a CMX node to the location hierarchy, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

Step 2

In the Location Hierarchy window, click More Actions at the far right of the customer name (root name).

Step 3

Choose Add a Witeless Network.

Step 4

From the Add a Wireless Network drop-down list that appears, choose Cisco on Prem.

Step 5

In the Display field, enter the name that must display for the CMX node in the location hierarchy.

Step 6

In the URL field, enter the URL to connect to Cisco CMX.

Step 7

In the User Name field, enter the user name to connect to Cisco CMX.

Step 8

In the Password field, enter the password to connect to Cisco CMX.

Step 9

Click Add.

The CMX node appears in the location hierarchy under the customer name.
What to do next

Note
Cisco DNA Spaces will not allow you to add two CMX nodes with the same access point.

Adding a Campus to the Location Hierarchy

Cisco DNA Spaces enables you to maintain the campus, building, and floor structure followed for the location hierarchy in the Cisco CMX. After adding a CMX node to the location hierarchy, you can import its campuses, and the associated buildings, floors, and access points.

To import a campus and its associated buildings, floors, and access points to the location hierarchy, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

Step 2

In the Location Hierarchy window, click More Actions at the far right of the CMX node for which you want to add the campus.

Step 3

Click Add Campus.

Step 4

In the Add Campus window that appears, select the campuses that you want to add to the location hierarchy.

The Add Campus window appears with all the available campuses for that CMX node. If you select a campus, its buildings and floors appears to the right of the campus.

Note 
If you do not want to add a particular building or floor of a campus to the location hierarchy, you can remove it by unchecking the corresponding check box. If required, you can add it to the location hierarchy any time later. For more information on adding a building to a campus, see the Adding a Building to a Campus. For more information on adding a floor to a building, see the Adding a Floor to a Building.
Step 5

Click Add.

The campuses added gets listed in the location hierarchy along with its associated buildings and floors.

Note 
In the Cisco CMX, ensure that there is no duplicate for a building name under a campus.

Creating Zones and Adding Access Points

You can group the access points of a building or floor using zones. You can create the zones at building or floor level.


Note
You cannot modify the access points for a floor.

To create a zone for a building or floor, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

Step 2

In the Location Hierarchy window, click More Actionsat the far right of the building or floor under which you want to create the zone.

Step 3

Choose Add Zone.

Step 4

In the Add Zone window that appears, perform the following steps:

  1. In the Enter Zone Name Here field, enter a name for the zone.

  2. In the Select Access Points area, select the check box for the access points that you want to add to the zone.

  3. Click Add.

What to do next

Note
When you add an access point of a building or floor to a zone, that access point will not be available for that building or floor. The access points added to a zone will not be available for other zones.
Creating the Location Hierarchy by Manually Uploading the Cisco CMX Details

If you want to use the location hierarchy of a Cisco CMX that is not publicly accessible, you can import the location hierarchy to Cisco DNA Spaces by uploading the JSON file that contains the location hierarchy details.

For a location hierarchy created using the JSON file, you can rename and delete the locations such as building, floor, and so on, but you cannot edit the locations. You can create groups and zones in the location hierarchy.


Note
As this method has many limitations, we recommend you to use this option only if you cannot connect to the Cisco CMX from the Cisco DNA Spaces dashboard.

Note
As the wireless network information required for access point synchronization is not available, the access point synchronization will not happen if the locations are added to the location hierarchy using the JSON file. So after importing the JSON file if you make changes in the wireless network for the locations, those changes will not reflect in the location hierarchy.

To create a location hierarchy using a JSON file, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

Step 2

In the Locations window, click More Actions at the far right of the customer name.

Step 3

ClickAdd Wireless Network.

Step 4

From the Add Wireless Network drop-down list, choose CMX On Prem.

Step 5

Select Upload JSON.

Step 6

Enter the name that must be displayed for the CMX node in the location hierarchy.
Step 7

Select the JSON file to upload using the Browse button.

Step 8

Click Upload.

The JSON file is uploaded and the location hierarchy is created for the Cisco CMX in the Cisco DNA Spaces dashboard.
What to do next

Note
After uploading the JSON file, to update the location hierarchy, you must delete the location hierarchy manually, and then re-import the JSON file with new location details.
Creating the JSON File for Locations

Create the JSON file for locations with following curl command:

curl -u ‘<userName>:<Password>@123#’ https://<CMXPublicIP>/api/config/ v1/maps-- insecuremseoutput.json

Defining the Location Hierarchy for Cisco Unified Wireless Network with Wireless Controller (without Cisco CMX Installation)

You can use Cisco DNA Spaces with Cisco Wireless Controllers (Cisco Catalyst), even without installing Cisco CMX. In such cases, you must use the WLC Direct Connect option. If you are using Map Services, you can import the locations in the same Campus-Building-Floor structure in which they are defined in Cisco Prime. Otherwise, you can add only networks, groups, and zones in the location hierarchy.


Note
If you were using Cisco DNA Spaces earlier with Cisco CMX, and if you are moving to use Cisco DNA Spaces with Cisco Wireless Controller, the Reports and proximity rules will be affected. The Reports will be shown based on the new location configurations. You also have to re-configure the proximity rules to display captive portals or to send notifications.

If you are using the WLC Direct Connect option, you can import the wireless network locations to the Cisco DNA Spaces in any of the following methods:

  • Access Point Prefix: In this method, you must first connect the Cisco Wireless Controller to Cisco DNA Spaces to import the location hierrachy to the Cisco DNA Spaces dashboard. If you are using this option, you can add only networks, groups, and zones in the location hierarchy. For more information on connecting the Cisco Wireless Controller to Cisco DNA Spaces, and importing the location hierarchy to the Cisco DNA Spaces dashboard, see Connecting Cisco Wireless Controller to Cisco DNA Spaces (Using the "WLC Direct Connect" option). Alternatively, you can also refer to the configurations steps for Connect WLC/Catalyst 9800 Directly in Setup > Wireless Networks of Cisco DNA Spaces dashboard.

  • Importing from Maps: In this method, you must import the location map from Cisco Prime Infrastructure and upload the map to the Map Services option in the Cisco DNA Spaces dashboard. You can then import that locations to the location heirarchy. If you use this option, you can import the locations in the same hierarchial structure as in Cisco Prime, Campus-Building-Floor. For more information on importing the locations using Map Services, see Importing Locations to the Location Hierarchy Using Map Services.

Importing Locations to the Location Hierarchy Using Map Services

For Cisco AireOS without Cisco CMX (the WLC Direct Connect option), you can import the locations to the location hierarchy using the Map Services. If you are using this option, you can import the locations in the same hierarchial structure, Campus- Building-floor .

To import the to the location hierarchy using the Map Services , perform the following steps:

Procedure
Step 1

Log into Cisco Prime Infrastructure.

Step 2

In the Settings /Getting Started window, click the circle icon near the top right of the window (near Cisco logo).

Step 3

In the window that appears, click Maps on the left pane.
Step 4

In the Wireless Maps area, click Site Maps (Deprecated).

Note 

You can add new locations using the Site Maps (New) option.

Step 5

Click the drop-down list near Go, and choose Export Maps.

Step 6

Click Go.

Step 7

From the tree view of location maps, select the parent location (CMX node) that you want to export, and click Export.

Note 

Ensure that the Include Map Information check box is checked.

Step 8

Save the location map on your computer.

Note 

You must download the map in the gzip format and upload it in the Cisco DNA Spaces in the same format.

Step 9

In the Cisco DNA Spaces dashboard, choose Setup > Map Services.

Step 10

Click Upload at the top left of the window, and select the location map downloaded from Cisco Prime Infrastructure.

The location map grets uploaded to the Map Services.

Step 11

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

Step 12

In the Location Hierarchy window, click More Actions at the far right of the root location.

Step 13

Click Add a Wireless Network.

The Add a Wireless Network window appears.

Step 14

From the Add a Wireless Network drop-down list, choose WLC Direct Connect.

Step 15

Click the Import from Maps radio button.

The campuses and its associated buildings and floors that are available in the location map imported to Map Services are displayed.

Step 16

In the Display Namefield, enter a name for the parent location that must appear under the root location.

Step 17

Check the campuses that you want to import.

When you check a campus, its associated buildings and foors also get selected. If you do not want to import a particular building, uncheck that building's check box. However, you cannot uncheck a particular floor.

Step 18

ClickImport.

A message Locations imported Successfully is shown.

You can now view the imported locations in the location hierarchy

Note 

If you are adding new locations in the wireless network, you have to import them manually to the location hierarchy following the same procedure.

After defining the location hierarchy, ensure that you define timezones for locations. The timezone defined affects the Cisco DNA Spaces rules and reports.

Managing the Cisco Wireless Controller and Access Points

Managing the Location Hierarchy

Renaming a Customer

To rename a customer, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, click Location Hierarchy.

Step 2

In the Location Hierarchy window, click More Actions at the far right of the customer name.

Step 3

Click Rename <root name>.

Step 4

In the Rename root window that appears, enter the customer name you want.

Step 5

Click Rename.

Adding a Wireless Network

Cisco DNA Spaces supports both Cisco Unified Wireless Network and Meraki. You can add both CMX nodes and Cisco Meraki Organizations using the Add a Wireless network option.

The Add a Wireless Network drop-down list will be having the following three options:

  • Meraki—To define the location hierarchy for Meraki network.

  • CMX On Prem—To define the location hierarchy for the Cisco Unified Wireless Network, when the Cisco CMX is installed.

  • WLC Direct Connect—To define the location hierarchy for the Cisco Unified Wireless Network, when the Cisco CMX is not installed.

For more information on adding a Cisco CMX node, Cisco Meraki Organization, or Cisco Wireless Controller access points using the Add a Wireless Network option, see the respective topic from the following:

Searching for a Location

You can search for a location in the location hierarchy using its name. To search for a location in the location hierarchy, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears.

Step 2

In the Search field, enter the name of the location that you want to search.

The location gets highlighted in the location hierarchy.

Searching for an Access Point

You can search for an access point using its name or Mac address.

To search for an access point in the location hierarchy, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears.

Step 2

In the Search field, enter the name or Mac address of the access point that you want to search.

The access point gets highlighted.

Managing the Location Hierarchy for Cisco Unified Wireless Network

Adding a Building to a Campus

To add a building to a campus, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, click Location Hierrachy.

Step 2

In the Location Hierarchy window, click More Actions at the far right of the campus to which you want to add the building.

Step 3

Click Add Building.

Step 4

In the Add Building window that appears, select the building that you want to add under the campus.

Step 5

Click Add.

The building gets listed under the campus in the location hierarchy.

Adding a Floor to a Building

To add a floor to a building, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, click Location Hierarchy.

Step 2

In the Location Hierarchy window, click More Actions at the far right of the building to which you want to add the floor.

Step 3

ClickAdd Floor .

Step 4

In the Add Floorwindow that appears, select the floor that you want to add under the building.

Step 5

Click Add.

The floor gets listed under the building.

Renaming a CMX Node

To rename a CMX node, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the CMX node that you want to rename.

Step 3

Click Rename <Cisco CMX Node>.

Step 4

In the window that appears, enter the new name for the CMX node.
Step 5

Click Rename.

What to do next

Note
The renaming is not reflected in the Cisco CMX.

Editing a CMX Node

You can edit the Cisco CMX connection credentials.

To edit a CMX node, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the CMX node that you want to edit.

Step 3

Click the option to edit the CMX node.
Step 4

In the window that appears, provide the updated Cisco CMX log in credentials for the CMX node.
Step 5

Click Edit.

Deleting a CMX Node

To delete a CMX node from the location hierarchy, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the CMX node that you want to delete from the location hierarchy.

Step 3

Click the option to delete the CMX node.
What to do next

Note
To delete a CMX node, first you have to delete the locations and groups under that CMX node, if any.

Note
You cannot delete a CMX node that is associated with the proximity rules.

Renaming a Campus

To rename a campus, perform the following steps

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the campus that you want to rename.

Step 3

Click Rename <campus name>.

Step 4

In the Rename-campus window that appears, enter the new name for the campus.

Step 5

Click Rename.

Deleting a Campus

To delete a campus, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the campus that you want to delete.

Step 3

Click Delecte campus.

What to do next

Note
To delete a campus, first you have to delete the locations under that campus, if any.

Note
You cannot delete a campus that is associated with proximity rules.

Renaming a Building

To rename a building, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click Location Hierarchy for the building that you want to rename.

Step 3

Click Rename <building name>.

Step 4

In the Rename -network window that appears, enter the new name for the building.

Step 5

Click Rename.

Deleting a Building

To delete a building, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the building that you want to delete.

Step 3

Click Delete building.

What to do next

Note
To delete a building, first you have to delete the floor or zones under that building, if any.

Note
You cannot delete a building that is associated with a proximity rule.

Renaming a Floor

To rename a floor, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the floor that you want to rename.

Step 3

Click Rename "floor name".

Step 4

In the Rename-floor window that appears, enter the new name for the floor.

Step 5

ClickRename.

Deleting a Floor

To delete a floor, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the floor that you want to delete.

Step 3

Click Delete floor.

What to do next

Note
If the floor that you delete has any zone under it, that zone is moved under the building after the deletion of the floor.

Managing the Location Hierarchy for Meraki

You can rename, and delete the locations under Meraki.

Adding Floors to a Network

To add a floor to a network, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

Step 2

In the Location Hierarchy window, click More Actions at the far right of the network under which you want to create the floor.

Step 3

In the Add Floor window that appears, select the floor that you want to add under the network.

Step 4

Click Add.

The floor gets added to the network.

Renaming a Cisco Meraki Organization

To rename a Cisco Meraki Organization, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the organization that you want to rename.

Step 3

Click Rename "Organization Name".

Step 4

In the Rename-Meraki window that appears, enter the new name for the Cisco Meraki Organization.

Step 5

Click Rename.

Deleting a Cisco Meraki Organization

To delete a Cisco Meraki Organization, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the Cisco Meraki Organization that you want to delete.

Step 3

Click Delete Organization.

What to do next

Note
To delete an organization, first you have to delete the locations and groups under that organization, if any.

  • You cannot delete any organization that is associated with the proximity rules.

Renaming a Network

To rename a network, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the network that you want to rename.

Step 3

Click Rename "network name".

Step 4

In the Rename-location window that appears, enter the new name for the location.

Step 5

Click Rename.

Deleting a Network

To delete a network, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the network that you want to delete.

Step 3

Click Delete network.

What to do next

Note
To delete a network, first you have to delete the floors and access points under that network, if any.

  • You cannot delete any network that is associated with a proximity rule.

Renaming a Floor

To rename a floor, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the floor that you want to rename.

Step 3

Click Rename "floor name".

Step 4

In the Rename-floorwindow that appears, enter the new name for the floor.

Step 5

Click Rename.

Deleting a Floor

To delete a floor, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the floor that you want to delete.

Step 3

Click Delete floor.

What to do next

Note
If the floor that you delete has any zone under it, that zone is moved under the network after the deletion of the floor.

Note
You cannot delete any floor that is associated with a proximity rule.

Updating Metadata for a Location

To update the metadata for a location, perform the following steps:

Procedure

Step 1

In the Location Hierarchy window, click More Actions at the far right of the location for which you want to update the location metadata.

Step 2

Click Add/Edit Metadata.

Step 3

In the Add Metadat for <location> window that appears, click the metadata that you want to update.

Step 4

Make necessary changes, and click Update .

What to do next


Note
You can delete a location metadata by clicking the Delete button for that metadata.

Updating Metadata for a Location

To update the metadata for a location, perform the following steps:

Procedure

Step 1

In the Location Hierarchy window, click More Actions at the far right of the location for which you want to update the location metadata.

Step 2

Click Add/Edit Metadata.

Step 3

In the Add Metadat for <location> window that appears, click the metadata that you want to update.

Step 4

Make necessary changes, and click Update .

What to do next


Note
You can delete a location metadata by clicking the Delete button for that metadata.

Defining or Changing the Time Zone for Locations

You can define the time zone for various locations in the location hierarchy. To define the time zone for a location, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

Step 2

In the Location Hierarchy window, click More Actions for the location for which you want to define the time zone.

Step 3

Click Time Zone.

The Change TimeZone window appears. In the Current Time Zone field, the time zone configured for the location appears. For a location for which the time zone is not yet defined, No Time Zoneappears in the Current Time Zone field.

Step 4

From the Select Timezone drop-down list, choose the time zone that you want to configure for this location.

Step 5

Click Change.

The time zone is defined for the location.

What to do next


Note
The notifications are sent for the locations based on the configured time zones.

Wireless Network Synchronization

To know the synchronization status of the locations, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, click the Wi-Fi icon at the top-right.

Step 2

Click Wireless Network Status.

Step 3

Click the wireless network of which you want to see the synchronization status. For example, to view the synchronization status for Meraki, click Meraki.

The synchronization status is displayed.

Managing the Maps for a Location

The maps are displayed by default based on the map configuration in the wireless network.

To view the map for a location, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click the location for which you want to view the map.
Step 3

Click the Maps tab.

The map appears in the Maps tab.

Managing the Access Points

You can add or remove access points to a zone.

Adding an Access Point to a Zone

To add access points to a zone, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click the zone to which you want to add the access point.
Step 3

Click Modify Access Points
Step 4

Select the check box for the access point that you want to add.
Step 5

Click Add.

The access point gets added to the zone.

What to do next


Note
If there are no access points under that zone, the button name will beAdd Access Points.

Note
For Cisco Unified Wireless Network, to import the access points, the Cisco CMX must be publicly accessible. For a default Cisco Unified Wireless Network installation, the ports 80 and 443 must be open. For more information, see the “Bandwidth Requirements to Deploy Cisco DNA Spaces” section .

Removing an Access Point from a Zone

To remove an access point from a zone, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click the zone from which you want to delete the access point.
Step 3

Click Modify Access Points.

Step 4

Uncheck the check box for the access point that you want to delete.
Step 5

Click Add.

The access point gets deleted from the zone.

Viewing the Access Points for a Location

You can view the access points under each location. Ideally, the access points belong to a floor or zone.

To view the access points for a location, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click the location for which you want to view the access points.

Step 3

Click the Access Points tab.

The access points associated with that location are displayed.

What to do next


Note
The Access Points link for a location is enabled only if at least one access point exists for that location.

Managing the Groups

Cisco DNA Spaces enables you to rename a group name, edit a group, and delete an independent group.

Creating Groups

Grouping enables you to create proximity rules specific to a set of locations. You can create groups at the higher levels in the location hierarchy.

For Cisco Unified Wireless Network, you can group the CMX nodes or campuses in the location hierarchy. For example, you can group the Campus1 and Campus 2 under one group and Campus 3 and Campus 4 under another group. You can also create sub groups under these groups. For Meraki, you can group the Cisco Meraki Organizations or networks in the location hierarchy. For example, you can group the Network 1 and Network 2 under one group and Network 3 and Network 4 under another group. You can also create sub groups under these groups.

You can also create a group including the wireless network nodes of both Cisco Unified Wireless Network and Meraki. However, you cannot group the lower level locations of Cisco Unified Wireless Network and Meraki. For example, you cannot group a campus and a Meraki network.

To create a group for a location, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, click Location Hierarchy .

Step 2

In the Location Hierarchy window, click More Actions at the far right of the location under which you want to add the group.

Step 3

ClickCreate Group.

Step 4

In the window that appears, perform the following steps:

  1. Enter a name for the group.

  2. Select the locations that you want to add under this group.

    Note 
    The locations available for selection depends upon where you are adding the group in the location hierarchy. When you add a group under the customer name (root level), the first level locations (For example, CMX node, Cisco Meraki Organization) are available for selection. When you add a group under a CMX node, only the campuses under that CMX node are available for selection.

  3. Click Add.

What to do next


Tip

If you want to have a parent group without any location, and sub groups with location, then you first create the parent group with all the required locations that must become the part of its sub groups. Then you create a sub group under the parent group. The locations added to the parent group are available for selection. Select the locations that you want to add under the sub group. Similarly, you can create more sub groups under the parent group.


Note
You can add more locations to a group at any time.

Renaming a Group

To rename a group, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the group that you want to rename.

Step 3

Click Rename "group name".

Step 4

In the Rename group window that appears, enter the new name for the group.

Step 5

ClickRename .

Editing a Group

You can add or remove the locations from a group.

To edit a group, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions for the group that you want to edit.

Step 3

Click Edit group.

Step 4

In the Edit Group window that appears, check the check box for the locations that you want to be part of the group.

Step 5

Click Update.

Deleting a Group

To delete a group, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears with the location hierarchy.

Step 2

In the location hierarchy, click More Actions at the far-right of the group that you want to delete.

Step 3

Click Delete group.

What to do next


Note
To delete a group, first you have to delete the locations and sub groups under that group, if any.

Note
You cannot delete a group that is associated with the proximity rules.

Managing the Zones

You can rename and delete the zones created for Cisco Unified Wireless Network or Meraki.

Renaming a Zone

To rename a zone, perform the following steps

Procedure

Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears.

Step 2

In the location hierarchy, click More Actions for the zone that you want to rename.

Step 3

Click Rename "zone name".

Step 4

In the Rename-zone window that appears, enter the new name for the zone.

Step 5

Click Rename.

Deleting a Zone

To delete a zone, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

The Location Hierarchy window appears.

Step 2

In the location hierarchy, click More Actions for the zone that you want to delete.

Step 3

Click Delete zone.

What to do next


Note
You cannot delete any zone that is associated with the proximity rules.

Adding a CMX Zone

Cisco DNA Spaces dashboard supports to import the CMX Zones added to Cisco CMX and Map Service. CMX Zones can be added under floors. CMX Zones will just have X,Y cordinates, and will not have any access points associated with them.

Ideally, Cisco DNA Spaces will automatically add, update, and delete the CMX Zones in the location hierarchy based on the changes made in Cisco CMX or Map Service. However, for the existing locations in Cisco DNA Spaces, if any CMX Zone was created in Map Services before this CMX Zone support, that CMX Zone will not be imported automatically during synchronzation. You have to manually add it to the location hierarchy. Once added, all the updates done for this particular CMX Zone will be synchronized automatically.


Note

CMX Zone support is not applicable if the wireless network is Meraki.

To add a CMX Zone manually to the location hierarchy, perform the following steps:

Procedure

Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

Step 2

In the Location Hierarchy window, click the More Actions icon for the floor under which you want to add the CMX Zone

Step 3

Click Add CMX Zone.

Step 4

In the Add CMX Zone window that appears, select the CMX Zones that you want to add.

Note 

The CMX Zones added to Map Service or Cisco CMX are available for selection.
Step 5

Click Add.

The CMX Zone gets listed under the particular floor. Now all the updates done for this partucular CMX Zone will be synchronized automatically.

Note 

You can add a CMX Zone in Setup > Map service using the square icon (below the Expand Collapse icon) displayed in the map.

Displaying Cumulative Count in Location Hierarchy

In the location hierarchy, the count of APs, BLE Beacons, Proximity Rules, and child locations for the locations will be shown as cumulative. The count for a location will be the total of its count and the count of all its child locations. For example, the total count of APs for a floor will be the sum total of APs for the floor and the APs for each zone under that floor.

The locations with zero count will not have a link to view the details. You can view the APs, BLE beacons, Proximity Rules, Locations, and Users of a location by clicking that location. You can view the details of a location parameter only from the associated location.

For the proximity rules, only the unique rules are counted. For example, if two zones of a floor are included in an engagement rule, when counting the rule for the floor, that engagement rule will be counted only once.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

Related Cisco Community Discussions

About Us
Contact Us
Work with Us