Explore Cisco
How to Buy

Have an account?

  •   Personalized content
  •   Your products and support

Need an account?

Create an account

Cisco DNA Spaces Configuration Guide

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

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:
November 18, 2020

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 AireOS Wireless Controller, Cisco Catalyst 9800 Series Wireless Controller, 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.

As Cisco DNA Spaces provides universal account, you can import and manage the locations of multiple wireless networks. A proximity rule can include the locations of multiple wireless networks.

You can create proximity rules such as Captive Portal rule, Engagement rule, and Location Personas rule, and view access points, users, and child locations for any location in the location hierarchy. The number of access points, 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 network such as Cisco Meraki, Cisco AireOS Wireless Controller or Cisco Catalyst 9800 Series Wireless Controller. In addition, you must establish connection between Cisco DNA Spaces and your wireless network.

Defining the Location Hierarchy

Cisco DNA Spaces supports the following wireless networks:

  • Cisco Meraki

  • Cisco Wireless Controller with or with out Cisco CMX

  • Cisco Catalyst 9800 Series Wireless Controller


Note
For Cisco Wireless Controller without Cisco CMX and Cisco Catalyst 9800 Series Wireless Controller, you can ensure that appropriate data transfer happens between the 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 Cisco 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

Choose Add a Wireless Network.

Step 4

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

Step 5

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

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 Cisco 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 Cisco Meraki application, 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 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 Zone Name 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 Cisco 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 Cisco Meraki Locations Using the API Keys

To import Cisco 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 Cisco Meraki.

Step 3

Click the Import Organization using API link that appears when you select Cisco 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 the Add 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 AireOS/ Cisco Catalyst

You can connect CiscoAireOS (Cisco Wireless Controller) and Cisco Catalyst (Cisco Catalyst 9800 Series Wireless Controller) to Cisco DNA Spaces and import the location hierarchy using any of the following connectors: Cisco CMX, Cisco WLC Direct Connect, or Cisco DNA Spaces Connector.

Defining the Location Hierarchy for Cisco AireOS/ Cisco Catalyst Wireless Controller with Cisco CMX

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.

Cisco DNA Spaces supports only Cisco CMX 10.6 or later.


Note
The CMX on Prem option in Add a Wireless window will not function any more. When connecting Cisco DNA Spaces to Cisco AireOS/ Catalyst with Cisco CMX, for importing the location to location hierarchy, you can import the locations using CMX Tethering. CMX Tethering can be done by uploading map to Map Services or by configuring Token in Cisco CMX. After importing maps, the map data will reflect in the Location Hierarchy automatically.

The location hierarchy for Cisco AireOS Wireless Controller with a Cisco CMX installation is as following:

Cisco CMX Node > Campus > Building(network) > Floor > CMX Zone (if defined)


Note

  • Due to the update in Map services, the location hierarchies imported newly after October 2020 will have only Campus > Building > Floor > CMX Zone (if defined) in the hierarchy.However, any updates made to the existing location hierarchy through map upload will maintain CMX Node

  • For an existing location hierarchy, if you reimport the locations using Map Services, the overlapping APs (APs already existed in location hierarchy and is available in the map imported as well) will be moved to the map-based hierarchy.Therefore, the reports and proximity rules will be affected. . You also have to re-configure the proximity rules to display captive portals or to send notifications

The location hierarchy for Cisco AireOS/Catalyst Wireless Controller with Cisco CMX is shown in the following figure.

Figure 2. Location Hierarchy with Cisco CMX

Note
After defining the location hierarchy, ensure that you define timezones for locations. The timezone defined affects the Cisco DNA Spaces rules and reports.
Connecting Cisco DNA Spaces to Cisco Wireless Controller or Cisco Catalyst 9800 Series Wireless Controller Using CMX Tethering

If you are having Cisco CMX 10. 6 or later, you can use the CMX tethering feature to connect Cisco DNA Spaces to the controller, import locations and to configure the location updates for notifications and reports.

Cisco DNA Spaces Network Sync Server supports AP synchronization for CMX Tethering. For CMX Tethering, the changes made to APs in Cisco Prime get updated in Cisco DNA Spaces location hierarchy. To synchronize the AP changes, do any of the following:

  • In Cisco CMX, click SYSTEM. In the dashboard that appears, choose Settings > Controllers and Maps Setup > Import. In the window that appears, provide Cisco Prime Username, Password and IP Address. Then click Import Controllers and Maps to get latest map changes. Click Save.

  • Download updated map from Cisco Prime and upload it to Cisco CMX.

  • Download updated map from Cisco Prime and upload it to Map Services in Cisco DNA Spaces.

You can do CMX Tethering in the following ways:

CMX Tethering by Configuring Token in Cisco CMX

To configure CMX Tethering through token, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Setup > Wireless Networks.

Step 2

In the Connect your wireless network window, click Add New.

Step 3

Click Select for Cisco AireOS/Catalyst.

Step 4

Click Select for Connect Via CMX Tethering.

The prerequisites for using this option are displayed.
Step 5

Click Continue Setup.

The Connect Via CMX Tethering widget appears in the Connect your wireless network window.

Step 6

Expand the widget Connect Via CMX Tethering .

Step 7

Click Create New Token displayed at Step 2.

Step 8

In the Create a new token window, enter a name and description for the Cisco CMX Tethering.

Step 9

Click Save.

Step 10

Click View Tokens displayed at Step 2.

The Cisco CMX Tethering instance added gets listed.
Step 11

To generate token for connecting the Cisco DNA Spaces with Cisco CMX, in the CMX Tethering Tokens window, click the Key icon for the Cisco CMX Tethering instance for which you want to generate token.

Step 12

Click Copy.

Step 13

Log into Cisco CMX.
Step 14

Choose Manage > Cloud Apps.

Step 15

In the Cloud Applications window that appears, click Enable in the Actions column for Cisco DNA Spaces.

Step 16

In the window that appears, configure the token copied from Cisco DNA Spaces dashboard.

When you configure CMX tethering using token, the location map for the particular CMX node appears in the Map Service window and the locations appear automatically under Location Hierarchy of the Cisco DNA Spaces dashboard.

Note 

If you delete a location from Location Hierarchy, it will also be removed from Map Service.

Note 

  • To enable the Cisco DNA Spaces service in Cisco CMX, you must have a Cisco DNA Spaces account.

  • For Cisco CMX, you cannot add campus, building, and other child locations using More Actions in the location hierarchy. You must update the locations in Setup > Map Service.However, you cannot add zones (AP Zones). You can group or delete the locations from the location hierarchy. When you delete a location from the location hierarchy, that location gets removed from the Map Service also. For more information, see Managing the Location Hierarchy for Cisco Wireless Controller with Cisco CMX.

  • If you want the location updates in Cisco Prime to get automatically synchronized in Cisco DNA Spaces, you must click the Map Sync button in Cisco CMX.

CMX Tethering by Uploading the Location Map to Map Services

Note
The configurations done in the external applications that are not a part of Cisco DNA Spaces, and the menu path and names specified for the tabs, windows, options, and so on in this documentation are subject to change.

Note
You can export the maps from Cisco Prime or Cisco DNA Center. Maps exported from Cisco Prime Infrastructure or Cisco DNA Center, and imported into Cisco DNA Spaces using Map Service will appear automatically under Location Hierarchy.

To import the locations to the location hierarchy by exporting the maps from Cisco Prime, 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 left 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.

Save the location map on your computer.

Note 
You must download the map in the zip format and upload it in the Cisco DNA Spaces in the same format.
Step 8

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

Step 9

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

The location map gets uploaded to the Map Service.

Note 

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

Step 10

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

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

  • Maps exported from Cisco Prime Infrastructure and imported into Cisco DNA Spaces using Map Service now appears automatically under Location Hierarchy.

  • If you delete a location from Location Hierarchy, it will also be removed from Map Service.

Note 

  • For Cisco CMX, you cannot add campus, building, and other child locations using More Actions in the location hierarchy. You must update the locations in Setup > Map Service. However, you cannot add zones (AP Zones). You can group or delete the locations from the location hierarchy. When you delete a location from the location hierarchy, that location gets removed from the Map Service also. For more information, see Managing the Location Hierarchy for Cisco Wireless Controller with Cisco CMX.

  • If you want the location updates in Cisco Prime to get synchronized in Cisco DNA Spaces, you must upload the latest map to Map Service.

Defining the Location Hierarchy for Cisco Catalyst 9800 Series Wireless Controllers or Cisco Wireless Controller (without Cisco CMX)

You can connect a Cisco AireOS Wireless Controller (without CMX) or Cisco Catalyst 9800 Series Wireless Controller to Cisco DNA Spaces using any of the following connectors:

  • Cisco WLC Direct Connect

  • Cisco DNA Spaces Connector

For more information on features supported by these connectors, see Features Supported by Various Connectors.

When you have connected the controller to Cisco DNA Spaces using Cisco WLC Direct Connect or Cisco DNA Spaces Connector, you can import the locations to the location hierarchy using any of the following methods:

  • Access Point Prefix: 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 Importing the Locations using Access Point Prefix. 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: This radio button is disabled now. Importing the locations through maps must be done now through Setup > Map Service. Using maps, you can import the locations in the same hierarchial structure as in Cisco Prime, Campus-Building-Floor. You must export the location map from Cisco Prime Infrastructure and upload the map to the Map Service option in the Cisco DNA Spaces dashboard to view the locations in the location heirarchy. After importing maps to Cisco DNA Spaces, the map data will reflect in the Location Hierarchy automatically. For more information on importing the locations using Map Services, see Importing Locations to the Location Hierarchy Using Map Services.


Note

  • If you were using Cisco DNA Spaces earlier with Cisco CMX, and if you are moving to use Cisco DNA Spaces directly 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

  • For an existing location hierarchy, if you reimport the locations using Map Services, the overlapping APs (APs already existed in location hierarchy and is available in the newly imported map as well) will be moved to the map-based hierarchy.Therefore, the reports and proximity rules will be affected. You also have to re-configure the proximity rules to display captive portals or to send notifications.

.
Importing the Locations using Access Point Prefix
Procedure
Step 1

To import the locations to the Cisco DNA Spaces, click the three-line menu icon at the top-left of the Cisco DNA Spaces dashboard,

Step 2

Choose Location Hierarchy.

Step 3

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

Step 4

Click Add a Wireless Network.

Step 5

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

Step 6

Click the Access Point Prefix radio button.

The imported Cisco Wireless Controllers get listed.

Note 
The Cisco Wireless Controllers get listed only if you configure the Cisco Wireless Controller for importing them to Cisco DNA Spaces.
Step 7

Select the Cisco Wireless Controller, and click Next.

This Cisco Wireless Controller will act as the primary Cisco Wireless Controller.

Step 8

Select another Cisco Wireless Controller as secondary controller, and click Next.

Note 
This feature helps you manage Cisco DNA Spaces with a secondary Cisco Wireless Controller with the same APs if the primary controller is down.

The secondary controller is optional. You can move to the next screen without selecting a secondary controller by clicking the Skip button.

Step 9

Select the networks that you want to add.

Note 
Cisco DNA Spaces will automatically group the APs based on the prefix of their names, and creates networks. The APs that are not grouped under a network will be listed under the name “Unconfigured”.
Note 
If you are not selecting a network, the APs in that network will be added to the location hierarchy under the name “Unconfigured”.
Step 10

Click Done.

The APs of the primary and secondary controllers selected will get listed in the location hierarchy.

Step 11

In the location hierarchy, click the More Actions icon at the far right of the network, and click Add Zone.

Step 12

In the window that appears, enter a name for the zone, and select the APs to be included in the zone.
Step 13

Similarly, create all the required zones.
Step 14

If you have created the location hierarchy earlier using the Cisco CMX, delete that location hierarchy, and re-configure the rules such as captive portal rules, engagement rules and location personas rules.

Note 

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

  • When adding the APs in the Cisco Wireless Controller, follow proper naming conventions (with appropriate prefix) to ease auto-network creation in Cisco DNA Spaces.

  • In the Cisco Wireless Controller, if new APs are added to the Cisco Wireless Controller, those APs get automatically imported during the next Cisco Wireless Controller synchronization. If an imported AP is deleted from the Cisco Wireless Controller, the changes will be reflected in Cisco DNA Spaces only after 48 hours.

What to do next

You can change the primary controller, and add more secondary controllers. You can also add APs of multiple prefixes to a single network. For more information, see the Managing the Location Hierarchy for Cisco Wireles Controller or Cisco Catalyst 9800 Series Controller(with WLC Direct Connect or Cisco DNA Spaces Connector).

Importing Locations to the Location Hierarchy Using Map Services

If a Cisco Wireless Controller or Cisco Catalyst 9800 Series Wireless Controller is connected to Cisco DNA Spaces through WLC Direct Connect or Cisco DNA Spaces Connector, 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 .


Note

You can export the maps from Cisco Prime or Cisco DNA Center. Maps exported from Cisco Prime Infrastructure or Cisco DNA Center and imported into Cisco DNA Spaces using Map Service appears automatically under Location Hierarchy.

To import the locations to the location hierarchy by exporting the maps from Cisco Prime, 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-left 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 Service.

Step 10

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

The location map gets uploaded to the Map Service.

Step 11

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

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

  • Maps exported from Cisco Prime Infrastructure and imported into Cisco DNA Spaces using Map Service now appears automatically under Location Hierarchy.

  • If you delete a location from Location Hierarchy, it will also be removed from Map Service.

Note 

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

  • If the locations are imported using Map Service, you cannot add campus, building, and other child locations using More Actions in the location hierarchy. You must update the locations in Setup > Map Service. However, you cannot add zones (AP Zones). You can group or delete the locations from the location hierarchy. When you delete a location from the location hierarchy, that location gets removed from the Map Service also. For more information, see Managing the Location Hierarchy for Cisco Wireless Controller with Cisco CMX.

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 Cisco AireOS Wireless Controller (Cisco Wireless Controller), Cisco Catalyst 9800 Series Wireless Controller and Cisco Meraki. You can add multiple wireless networks to the loaction hierarchy using the Add a Wireless Network option.

In the Add a Wireless Network window, 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—This option will not function any more.Importing of locations to location hierarchy will be managed by Setup > Map Service.

  • WLC Direct Connect—To define the location hierarchy for Cisco Catalyst 9800 Series Wireless Controller or Cisco Wireless Controller without Cisco CMX.

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 Defining the Location Hierarchy.

Adding Metadata for a Location

You can group the locations using metadata. You can use this metadata when defining the proximity rules. You can also use this metadata also for defining the brands for the Behavior Metrics app.

To add a metadata 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 the More Actions icon for the location for which you want to add metadata.

Step 3

Click Add/Edit Metadata.

Step 4

In the Add Metadata for <location>window that appears, perform the following steps:

  1. In the Key field, enter a metadata key.

  2. In the value field, enter a value for the key.

  3. Click Save.

What to do next


Note
Similarly, add the metadata for other locations that must have this 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.

Adding the Information of a Location

You can specify the information such as address of each separately location in the location hierarchy.

To add the location information for a location, perform the following steps:

Procedure

Step 1

Click the three-line menu icon at the top-left of the Cisco DNA Spaces dashboard.
Step 2

Choose Location Hierrachy.

Step 3

In the Location Hierarchy window, click the location for which you want to add the information.

Step 4

On the Location Info tab, click Edit for Location Data.

Step 5

In the Location Information window that appears, enter the information for the particular location.

You can add the following information about the location:

  • Brand

  • Country

  • State

  • City

  • Zip /Postal Code

  • Address

  • Time Zone

  • Area in Square Feet or Square Meter

  • Occupancy Limit (Max Capacity)
Step 6

Click Update.

The location information added will now gets listed in the Location Data area on the Location Info tab.

Note 

If you are not specifying the location information for a location, that location will inherit the information of its parent location. Location information inherited from the parent location will appear in Orange. However, we recommend you to update the location information for each location.

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 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.

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.

Managing the Location Hierarchy for Cisco Wireless Controller with Cisco CMX

For Cisco Wireless Controller with Cisco CMX, you cannot add campuses, building, and other child locations using More Actions in the location hierarchy. You must update the locations in Setup > Map Service. However, you can rename, group, or delete the locations from the location hierarchy.

When you delete a location from the location hierarchy, that location gets removed from Map Service also. When you delete a location from Map Service, only the APs will be removed from the location hiearchy leaving the hierarchy structure as it is.

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.

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 Cisco Wireles Controller or Cisco Catalyst 9800 Series Controller(with WLC Direct Connect or Cisco DNA Spaces Connector)

Adding Networks Automatically for a Primary Controller

If you have skipped to select the networks when importing the Cisco Wireless Controller, you can add the networks automatically at any time later.

To add network automatically for a Cisco Wireless Controller or Cisco Catalyst 9800 Series Wireless Controller, 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 wireless controller for which you want to add networks.

Step 3

Click Edit.

Step 4

In the Edit Controller window that appears, select the Auto Network Creation check box.

Step 5

Click Done.

The APs with similar prefix are grouped, and networks are formed automatically. The APs that are not added to the auto-created networks are listed under the network name “unconfigured”.

What to do next

Note
Only the APs added to the wireless controller after configuring the auto network are grouped. Existing APs under the “unconfigured” network name will not be grouped automatically based on this configuration. However, if any new AP gets added to the wireless controller with the same prefix of an existing AP in the “unconfigured” network, then the existing AP gets grouped with the new AP added.

Manually Adding Networks for a Primary Controller

To manually add network for a Cisco Wireless Controller or Cisco Catalyst 9800 Series Wireless Controller, 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 cisco wireless controller for which you want to define the network.

Step 3

Click Add Network.

The Add Networkwindow that appears.

Step 4

In the Network Name field that appears, enter a name for the network.

Step 5

In the Access Point Prefix field that appears, enter the prefix the APs must have to group under the network, and click Fetch.

The network get listed in the location hierarchy.

Note 

Multiple prefixes are supported for a wireless network. However, when you are adding a network, you can add the APs of only one prefix. If you want to add access points with another prefix to this network, you must edit the network after adding it. For more information on adding APs of multiple prefixes, see Adding APs of Multiple Prefixes to a Network.

Step 6

Click Done.

The network will be created with the APs having the prefix mentioned.

Adding APs of Multiple Prefixes to a Network

You can add APs of multiple prefixes to a network. For example, if you have APs with prefixes, AB, BC, and CA, and if you want to group the APs with AB and BC under one wireless network, you can do so.

To add APs of multiple prefixes to a network of a Cisco Wireless Controller or Cisco Catalyst 9800 Series Wireless Controller, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, click the three-line menu icon at the top-left of the window.
Step 2

Choose Location Hierarchy.

Step 3

In the Location Hierarchy window, click the network to which you want to add APs of multiple prefixes.

Step 4

In the Location Info tab, click Edit for Access Points Prefix Used.

Step 5

In the Edit Prefix window that appears, in the Prefix field, enter the prefix.

The APs with the prefix entered get listed.
Step 6

Click Add Prefix.

Now the newly added prefix gets listed under Added Prefixes in the right pane of the window. Add Prefix will be enabled only if there are APs with the Prefix entered.

Step 7

Click Save.

After adding the prefix, the APs under the unconfigured network with this prefix will be moved to this network.

To delete a prefix, hover over that prefix under Added Prefixes, and click the Delete icon that appears.

Note 

The Access Points Prefix Used option will be available in the Location Info tab only for the network locations. However, the Access Points Prefix Used option will not be available for the Unconfigured network.

Adding Additional Secondary Controller

If you have skipped to add a secondary controller when importing the Cisco Wireless Controller, you can add it any time later. Even if you have configured a secondary controller, you can add more than one secondary controllers.

To add a secondary controller for a Cisco Wireless Controller, 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 Cisco Wireless Controller for which you want to add secondary controller.

Step 3

Click Edit.

Step 4

In the Edit Controller window that appears, click Add Morefor Additional Controllers.

Step 5

In the Add additional controller window that appears, select the Cisco Wireless Controller that you want to configure as secondary controller.

Note 
The Cisco Wireless Controllers similar to the primary controller (having same APs) will be top in the list.
Step 6

Click Add.

Now the newly configured Cisco Wireless Controller has become the secondary controller.

Note 
You can add more than one Cisco Wireless Controller as secondary controller. However, you can add only one at a time.

Deleting a Secondary Controller

To delete a secondary controller, perform the following steps:

Procedure
Step 1

Click the three-line menu icon displayed at the top-left of the Cisco DNA Spaces dashboard.
Step 2

Choose Location Hierarchy.

Step 3

In the location hierarchy, click the More Actions icon for the Primary Controller of which you want to delete the secondary Cisco Wireless Controller.

Step 4

Click Edit.

In the Edit Controller window that appears, the secondary controllers added for that PrimaryController will be listed under Additional Controllers.

Step 5

Click the Delete icon for the secondary controller that you want to delete.

Step 6

In the window that appears, confirm the deletion.

Now, the secondary controller is deleted.
What to do next

Note
When you delete a secondary controller, the APs that are unique for this secondary controller (APs not in the primary controller or its other secondary controllers) also will be deleted.

Renaming the Primary Controller

To rename the primary controller, perform the following steps:

Procedure
Step 1

In the Cisco DNA Spaces dashboard, choose Location Hierarchy.

Step 2

In the location hierarchy, click the More Actions icon for the Cisco Wireless Controller that you want to rename.

Step 3

Click Rename <cisco wireless controller>.

Step 4

In the Rename WLC window that appears, enter the name required, and click Rename.

Now the name of the Cisco Wireless Controller is changed to the new name specified.

Note 
The name change is not reflected in the Cisco Wireless Controller.

Displaying Cumulative Count in Location Hierarchy

In the location hierarchy, the count of APs, 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, 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