Migrate Cisco Prime Infrastructure Data to Cisco DNA Center Using Prime Data Migration Tool Update 01

This chapter provides information on migrating data and important points related to migrating Cisco Prime Infrastructure to Cicso DNA Center using the Prime Data Migration Tool Update 01.

Prerequisites for Using Prime Data Migration Tool Update 01

This section lists the prerequisites for using the Prime Data Migration Tool Update 01 in 3.9.1 and for PI 3.8.x Prime Data Migration Tool Update 01 Hotfix, PI 3.7.x Prime Data Migration Tool Update 01, PI 3.6.x Prime Data Migration Tool Update 01, and PI 3.5.x Prime Data Migration Tool Update 01.

Before you use the Prime Data Migration Tool, you must ensure that you run the Cisco DNA Center AURA command line tool. The AURA tool performs a variety of health, scale and upgrade readiness checks for the Cisco DNA Center and the rest of the Fabric network. AURA ensures that Cisco DNA Center and its component services are all healthy and available before you start a migration.

For more information on using Cisco DNA Center AURA tool, see Enhanced Visibility into the Cisco DNA Center using AURA.

Prerequisites for Using Prime Data Migration Tool in 3.9.1

Ensure that:

  • You install Cisco Prime Infrastructure PI 3.9 or PI 39 + PI 3.9 Oracle Patch on Upgrade or PI 3.9 Update01. If you need support for Catalyst 9800 16.12.x version, you will need to install PI_3_9_Oct_Oracle_patch-1.0.8.ubf patch before you install PI 3.9.1. For instructions to install the Oracle Patch,see Installing CiscoPrime InfrastructureSystem Patch 3.9 section in the Cisco Prime Infrastructure 3.9 Administrator Guide.

  • You have Root or Super Users access privileges of Cisco Prime Infrastructure.

  • You have access credentials of Cisco DNA Center.

  • Refer the Cisco Prime Infrastructure and Cisco Catalyst Center Compatibility Matrix.

Prerequisites for Using PI 3.8.x Prime Data Migration Tool Update 01 Hotfix

Ensure that:

Prerequisites for Using PI 3.6.x Prime Data Migration Tool Update 01

Ensure that:

Migrating Data from Cisco Prime Infrastructure to Cisco DNA Center using Prime Data Migration Tool Update 01

This section helps you to migrate your Cisco Prime Infrastructure data from:

  • 3.9.1 to Cisco DNA Center.

  • 3.8.1 update 01 to Cisco DNA Center using PI 3.8.x Prime Data Migration Tool Update 01 Hotfix.

  • 3.7.1 update 05 to Cisco DNA Center using PI 3.7.x Prime Data Migration Tool Update 01.

  • 3.5.1 update 03 to Cisco DNA Center using PI 3.5.x Prime Data Migration Tool Update 01.

  • 3.6, 3.6 update 01, 3.6 update 02, 3.6 update 03, or 3.6 update 04 to Cisco DNA Center using PI 3.6.x Prime Data Migration Tool Update 01.

Follow this procedure to access the Cisco Prime Infrastructure to Cisco DNA Center migration by logging in to Cisco Prime Infrastructure:

Procedure

Step 1

Choose Administration > Settings > System Settings > General > Cisco DNA Center coexistence, and then click Launch Cisco DNA Center coexistence to open Prime Infrastructure - Cisco DNA Center Coexistence page.

For 3.9.1, you can either:

Click Cisco DNA Center coexistence in the Mega Menu page.

Or

Launch Cisco DNA Center coexistence from the Getting Started page. Choose Settings > Getting Started > Cisco DNA Center coexistence, and then click Launch Cisco DNA Center coexistence to open Prime Infrastructure - Cisco DNA Center Coexistence page.

Step 2

Click Add Cisco DNA Center Server.

Step 3

Enter the following Cisco DNA Center server details:

  1. Server IP Address or Hostname.

  2. Username

  3. Password

  4. Confirm Password

Note

 

You can integrate only one Cisco DNA Center server at a time.

Step 4

Click Save, to check server reachability.

Step 5

Click Next to go to Sync Settings.

Step 6

In the Sync Settings window:

  1. You can check for the Supported/Available Limits of the Cisco DNA Center server for the Site Groups/Site Maps and Devices. Supported/Available Limits of Cisco DNA Center will vary based on the Cisco DNA Center server core(s) count.

    The Supported/Available limits are specified in the below table:

    Table 1. Supported/Available Limits

    DNAC Core

    Site Groups/Site Maps

    Devices

    44-Core

    500

    1000

    56-Core

    1000

    4000

    112-Core

    2000

    5000

  2. Select the Enables automatic synchronization of data integrated with Cisco DNA Center check box to synchronize already migrated data set for the groups and devices from Prime Infrastructure to Cisco DNA Center automatically post modification.

  3. Select the Include newly added data during dynamic synchronization checkbox to move newly created groups and newly added devices during dynamic synchronization if any, from Prime Infrastructure to Cisco DNA Center automatically post addition.

    Note

     

    Dynamic Synchronization does not support add, update or delete operations for the already migrated data and will not synchronize the data automatically for the following components:

    • Maps

    • CLI Templates

    • ISE Server

    Maps, CLI templates, and ISE server migration is achieved only by Force Sync.

    • This check box is enabled only if you select the Enables automatic synchronization of data integrated with Cisco DNA Center check box.

    • During force synchronization, if the Enables automatic synchronization of data integrated with Cisco DNA Center check box is enabled, any modifications that are made through force synchronization to the Location Group and Devices entities are dynamically synced in Cisco DNA Center.

    • If the Enables automatic synchronization of data integrated with Cisco DNA Center check box is selected, CMX is dynamically assigned to Cisco DNA Center floor groups, when Cisco Prime Infrastructure imports maps to CMX. (Pre Req.: CMX dynamic sync works only on already migrated floor groups and CMX should exist in Cisco DNA Center server for CMX dynamic sync.)

  4. If the Enable CMX settings check box is selected, CMX will be pushed with floor groups. If the Enable CMX settings check is not selected, CMX data will not be pushed to the Cisco DNA Center server.

  5. Select the Migrate User Defined CLI Templates check box to migrate the user defined CLI and/or Composite Templates to Cisco DNA Center.

Step 7

Click Next to go to the Select Groups page.

Step 8

In the Select Groups window:

  1. If you want to move an entire group hierarchy to Cisco DNA Center, check the Replicate Parent Hierarchy check box and select the location groups from the Prime Infrastructure Location Groups pane.

    By default, when you select Site Groups, the buildings, floors, and associated maps are also selected.

    Select Global from the Cisco DNA Center Site Groups pane and click Move.

  2. If you want to move only a building or a floor to Cisco DNA Center under a different campus or area, select the required building or floor from the Prime Infrastructure Location Groups pane.

    Select a campus or an area from Cisco DNA Center Site Groups under which you need to move the building or floor and click Move.

After you move the groups from Cisco Prime Infrastructure to Cisco DNA Center, a Moved label appears on the moved groups.

The Prime Infrastructure Location Groups pane lists all the Cisco Prime Infrastructure groups irrespective of any virtual domain.

Note

 

Cisco Prime Infrastructure does not migrate devices assigned in a "Campus" to the Cisco DNA Center, when the co-existence tool is used.

As a workaround, you can assign your devices to a "Building" or "Floor" type location group before using the co-existence tool.

Note

 

Devices assigned in the Location groups with 'Default' Group type will not be migrated to Cisco DNA Center.

Step 9

Click Next.

Step 10

In the CMX Credentials window:

  1. You can view the list of associated CMX for selected groups with the following details:

    • Credential Status

    • Server IP address

    • Device Name

    • Username

    • Password

    • SSH Username

    • SSH Password

  2. You must update the SSH Username and SSH Password, if it is not available for the respective CMX.

  3. If the associated CMX is not found, then click Next.

Note

 

When the Cisco Prime Infrastructure – Cisco DNA Center migration tool is active and auto sync is enabled, then CMX will be dynamically pushed to Cisco DNA Center floor groups. Cisco DNA Center will there by track the location data for assigned groups.

Step 11

If you check the Migrate User Defined CLI Templates check box in the Sync Settings page, then a new page Select CLI Templates appears after the CMX page.

Step 12

In the Select CLI Templates window:

  1. Non-Migrated Templates will list all the applicable user defined CLI and/or Composite templates for the device types in the selected groups for migration to Cisco DNA Center.

  2. Migrated templates will list all the migrated templates available in Cisco DNA Center. You can either update or delete these templates.

    Note

     

    By default all the rows will be selected. Selected templates from the list will be updated and the deselected templates will be deleted from Cisco DNA Center.

Step 13

Click Next.

Step 14

In the Summary window:

  1. You can view the overall summary of selected location groups, devices, associated maps, user defined templates and CMX before migrating to the Cisco DNA Center.

  2. You can also view the groups, devices, maps and CMX which is added, updated and deleted under each respective tab.

  3. You can view the selected CLI templates listed here. Based on the device selection in the groups you can Add/Update or Delete the CLI/Composite user defined Templates in Cisco DNA Center.

  4. You can also view the status of last synced date and time.

Step 15

Click Submit, to migrate all the Location groups, Devices, Maps, CMX and user defined CLI/Composite templates from Prime Infrastructure to Cisco DNA Center.

Step 16

Click Force Sync to push data to the Cisco DNA Center server after the first migration.

You will be asked for a confirmation DNAC data will be overwritten by PI data by the Force Sync. Click Yes to proceed or No to stop Force Sync.

What to do next

If you want to revert the site hierarchy in Cisco DNA Center, uncheck the migrated groups in the Prime Data Migration tool and click Force Sync. This step deletes the migrated groups in Cisco DNA Center.

If you want to revert the device assignment (devices will be unassigned from Cisco DNA Center sites and assigned to migrated groups if the same devices are present both in Cisco Prime Infrastructure groups and Cisco DNA Center sites), perform the following steps:

  • Uncheck the migrated groups in the Prime Data Migration tool and click Force Sync. This step deletes the migrated groups and devices in Cisco DNA Center.

  • Add and assign or provision the devices in Cisco DNA Center in the required sites.

The pre-migration site hierarchy appears in Cisco DNA Center.

To migrate your Cisco Prime Infrastructure data again using the Prime Data Migration Tool, unassign the devices in Cisco Prime Infrastructure for the required groups and migrate the data.

Important Notes

This section contains important notes about Cisco Prime Infrastructure - Cisco DNA Center migration:

  • You can integrate only one Cisco DNA Center server at a time.

  • When you remove the existing DNAC server and add it again, the Migrated label for all the DNAC migrated groups/sites is removed and the groups appear as non-migrated groups/sites, even though the groups/sites are migrated.

  • Only CMX version 10.6.2 or above is supported for migration.

  • Before you start the next migration, you must refresh the Prime Data Migration tool to display the accurate groups and site maps.

  • For the first time ISE migration, ISE can be migrated only along with Sites and Groups, from the next migration onwards, you can migrate ISE alone.

  • You use a single session of the migration at a time for the same Cisco Prime Infrastructure server and Cisco DNA Center server pair.

  • Once the CMX is migrated to Cisco DNA Center, it will not be managed by Cisco Prime Infrastructure.

  • Cisco DNA Center will not migrate the location and civic data of any building which has no floor.

  • Any legacy devices that are not supported by Cisco DNA Center chosen for migration will be added to Cisco DNA Center inventory under Device Type column “Unsupported Cisco Device”.

  • Any devices managed only with SNMP V1 credentials in Cisco Prime Infrastructure cannot be migrated to Cisco DNA Center, whereas SNMP V2 and V3 can be migrated to Cisco DNA Center.

  • Only the basic information of the groups will be migrated, but not the rules and profiles assigned to group.

  • After integration, while upgrading Cisco DNA Center to an unsupported version, an Unsupported Version error appears and migration will stop.

  • Access Points positioned in the maps in Cisco Prime Infrastructure will migrate to Cisco DNA Center, only if we manage its WLC devices with CLI Credentials.

  • For Composite template Migration - The associated template should not be System template. If any composite template with system template will not get migrated.

  • During composite template migration all the associated template in composite template should be having the same device type. Otherwise migration will fail.

  • Specific composite templates migration is not recommended till Cisco DNA Center 1.3.3.8 and 2.1.1.3. However it works in later DNAC versions.

  • DNAC Version 2.2.1.0 specific update:

    • Civic location is mandatory for Location Groups / Site groups migration especially for Cisco DNA Center 2.2.1.0 version.

    • If any one selected group does not have civic location configured, then all the selected Location Groups/Site groups migration will fail.

Open Caveats for Prime Data Migration Tool Update 01

The following table lists the open caveats in Prime Data Migration Tool Update 01.

Table 2. Open Caveats

Identifier

Description

CSCvx55562

Selected CLI templates are not retained in the Select CLI template section for one scenario.

CSCvx58263

Resync of the migrated hierarchy has an issue.

CSCvx58265

Check box is not applied if a group has more than 3 levels.

CSCvx58267

Wrong error message appears when there is no error.

CSCvx99927

Reparenting does not work in some scenarios.

CSCvx88631

Unrelated devices appear in the Update tab in one scenario.