Cisco CMX allows you to import maps from Catalyst Center. When you import a map from Catalyst Center to Cisco CMX, all elements of map data is imported to Cisco CMX in the same manner when you import maps from Cisco Prime
Infrastructure, such as access points information, floor images, calibration model/antenna patterns, inclusion/exclusion region,
GPS markers, zones and so on.
After you add Cisco CMX in Catalyst Center and perform a map synchronization, Catalyst Center pushes the maps to Cisco CMX and overwrites the existing maps in Cisco CMX. For more information, refer to About Cisco Connected Mobile Experiences Integration, Create Cisco CMX Settings.
Catalyst Center sends regular API queries to Cisco CMX to get client information and map files. To troubleshoot client and map synchronization
issues, you can use Catalyst Center API calls. Refer to Devnet for details on the APIs.
In Catalyst Center, the Network Hierarchy tab under Design helps you to create network hierarchy and apply them to different areas of the organization. When you add maps using Network Hierarchy, map data can have nested campus/site structure. For example, under Global map, you can add U.S.A as a site and can add San
Jose and RTP as sub-sites.
When you import maps in Cisco CMX, the map utility imports map data following a simple three element structure: "Campus > Building(s) > Floor(s)”. However, when you import maps from Catalyst Center, map data pushed to Cisco CMX can include nested campus/site structure. For example, "US>CA>SJC>Milpitas>CiscoBuilding24>FirstFloor" which is different from the typical three element structure "Milpitas>CiscoBuilding10>FirstFloor" as in Cisco CMX.
When you import maps from Catalyst Center to Cisco CMX, Cisco CMX will only import the sites/campuses with a building element. For an imported map, if the Network Hierarchy on Catalyst Center is US>CA>SJC>Milpitas>CiscoBuilding24>FirstFloor, Cisco CMX will only show partial Network Hierarchy that is Milpitas>CiscoBuilding24>FirstFloor. However, Cisco CMX maintains a list of the parent elements in the database as US>CA>SJC and this information is only displayed in the API response and Northbound Notification messages, but not on the Cisco CMX
GUI.
In Cisco CMX, you can view the Network Hierarchy using the following three options:
-
REST API version 1 (HTTP GET /api/location/v1/<element-type>/)
-
REST API version 3 (HTTP GET /api/location/v3/clients/)
-
Northbound Notification messages
Following are the limitations when you import maps from Catalyst Center
Network Hierarachy:
-
Cisco CMX does not import the address and latitude/longitude of the sites from the Catalyst Center.
-
No limitation for the number of nested sites. Catalyst Center allows you to create a maximum of four nested sites. As the number of nested sites increase, the locationMapHierarchy or mapHierarchyString attribute value will also increase accordingly.
-
It is not recommended to have duplicate site names. When map data is imported from Catalyst Center with the Network Hierarchy: US>CA>SJC>Campus-One>CiscoBuilding24>FirstFloor and US>CA>RTP>Campus-One>CiscoBuilding24>FirstFloor, Cisco CMXwill overwrite the parent list of Campus-One from US>CA>SJC to US>CA>RTP which is the last incoming parent list for that campus.