Migrate Cisco Prime Infrastructure 3.10.1 data to Cisco DNA Center

This chapter provides helpful information on the compatibility matrix, migrating data and important points related to migrating Cicso Prime Infrastructure 3.10.1 to Cicso DNA Center.

Migrating Data from Cisco Prime Infrastructure 3.10.1 to Cisco Digital Network Architecture Center

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

Before you begin

Ensure that:

Procedure

Step 1

Click Prime Data Migration Tool in the Mega Menu page.

You can also launch Prime Data Migration Tool from the Getting Started page. Choose Settings > Getting Started > Prime Data Migration Tool, and then click Launch Prime Data Migration Tool to open Prime Infrastructure - Prime Data Migration Tool page.

Step 2

Click Job history, in the top right corner of the Prime Data Migration Tool to view Job Id, Cisco DNA Center IP, Start Time, End Time, and Status in the Prime Data Migration Job History window. The job summary will display only the latest 100 jobs.

Step 3

Click Add Cisco DNA Center Server.

Step 4

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 5

Click Save, to check server reachability.

Step 6

(Optional) Click Multi Server Settings, to archive, and restore the data migrated from Prime Infrastructure to DNA Center. It is recommended to use this option after Force Sync.

You can use the following options to archive the migrated data:

  • List of Cisco DNA Center Archive Available - Displays the list of available archives.

  • Back-up Current Cisco DNA Center Pairing - Back up migrated data of currently paired Cisco DNA Center server details in the migration tool.

  • Back-up Current & Load Cisco DNA Center Archive - Current Cisco DNA Center server and its migrated data are backed up and you can load the required archive from the list of available archives.

  • Delete Cisco DNA Center Archive - Deletes the selected DNA Center archives.

Step 7

Click Next to go to Sync Settings.

Step 8

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 , Devices, and Templates. 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

    Templates

    44-Core

    500

    1000

    1000

    56-Core

    1000

    4000

    1000

    112-Core

    2000

    5000

    1000

  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 you select the Enable CMX settings check box, CMX will be pushed with floor groups. If you do not select the Enable CMX settings check box, CMX data will not be pushed to the Cisco DNA Center server.

  5. If you select the Enable ISE settings check box, ISE server details will be pushed. If you do not select the Enable ISE settings check box, ISE data will not be pushed to the Cisco DNA Center server.

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

Step 9

Click Next to go to the Select Groups page.

Step 10

In the Select Groups window:

Expand the Usage Details section to view a summary of the site and device count details such as Recommended, Selected for Migration, and Available.

  1. If you want to delete only the mapping from Prime Infrastructure to Cisco DNA Center and retain the instances of migrated sites in the DNA Center for the current force sync, uncheck the Delete sites in Cisco DNA Center for the current Force Sync checkbox.

  2. Check the Delete sites in Cisco DNA Center for the current Force Sync check box to delete the sites from Cisco DNA Center and remove mapping from Prime Infrastructure to Cisco DNA Center for the current force sync.

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

    Click Select Parent below the Prime Infrastructure Location Groups pane to open the Cisco DNA Center Site Groups window.

    Marked for Deletion label appears when you unselect an already migrated group.

    Select Global from the Cisco DNA Center Site Groups pane under which you want to move the PI groups and click OK. The selected groups will be added in the Group Movement Log pane with the label as Marked for Migration.

  4. If you want to move only a building or a floor to Cisco DNA Center under a different campus or area, click Select Parent below the Prime Infrastructure Location Groups pane to open the Cisco DNA Center Site Groups window.

    Select a campus or an area from Cisco DNA Center Site Groups under which you need to move the building and select a building from Cisco DNA Center Site Groups under which you need to move the floor and click OK. The selected groups will be added in the Group Movement Log pane with the label as Marked for Migration.

If you click the Close or Cancel buttons in the Cisco DNA Center Site Groups window, the window closes without selecting any groups for migration and the Group Movement Log pane is not updated with the selected groups.

After you move the groups from Prime Infrastructure to Cisco DNA Center, Marked for Migration label appears on the moved groups.

Already migrated groups from Prime Infrastructure to Cisco DNA Center appear with the label as Migrated in the Prime Infrastructure Location Groups pane as well as the Group Movement Log pane.

The count of selected groups for migration appears as Selected for Migration under Sites. The count of selected devices for migration appears as Selected for Migration under Devices in Usage details.

Available groups count in Cisco DNA Center appears in the Available section under Sites and available devices count in Cisco DNA Center appears in the Available section under Devices in Usage details.

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 are not migrated to Cisco DNA Center.

To create sites directly in Cisco DNA Center so that you can move your sites from Prime Infrastructure to Cisco DNA Center, click Site Builder.

In the Site Builder window, if you select the Area radio button, enter the following information:

  • Site Name: Site name that you can create in Cisco DNA Center.

  • Parent Site: Cisco DNA Center parent under which you can create the site.

In the Site Builder window, if you select the Building radio button to create a building in the Cisco DNA Center Area, enter the following information:

  • Site Name: Building name that you can create in Cisco DNA Center.

  • Parent Site: Cisco DNA Center parent under which you can create the building.

  • Civic Location: Enter the civic location details under which you want to create the building.

  • GPS (Latitude/Longitude): These co-ordinates are auto-populated.

Click Add to create a site or building in Cisco DNA Center.

Step 11

Click Next.

Step 12

In the ISE & CMX Credentials window:

  1. Click the ISE tab to view the ISE server details that are present in Prime Infrastructure such as:

    • Server Status

    • Server IP

    • Port

    • FQDN: Ensure FQDN field is not empty and should match the ISE admin certificate otherwise the integration will fail in DNA Center.

    • Shared Secret: You must ensure that this shared secret field is not empty.

    • Timeout: This value must not exceed 20.

    • Retries

    If no ISE server is present in Prime Infrastructure, a No data available message appears.

    Note

     

    You can migrate only one ISE server to Cisco DNA Center. If ISE is already configured in DNA Center, the following warning is displayed:

    Cisco DNA Center is already configured with ISE server, do you want to delete the existing and migrate the ISE from PI. Do you want to continue?

  2. Click the CMX tab to can view the list of associated CMX servers for selected groups with the following details:

    • Credential Status

    • Server IP address

    • Device Name

    • Username

    • Password

    • SSH Username

    • SSH Password

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

    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 13

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 14

In the Select CLI Templates window:

  1. Non-Migrated templates list all the available CLI or Composite User Defined Templates available in Prime Infrastructure. You can select the templates need to be migrated to Cisco DNA Center.

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

    Note

     

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

Step 15

Click Next.

Step 16

In the Summary window:

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

  2. Click the CLI Templates tab to view the Add/Update of CLI/Composite user defined Templates based on the devices available in the Prime Infrastructure and click Delete section to view the templates marked for deletion.

  3. In the Sync Settings tab, you can view the summary of the sync status.

Step 17

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

A confirmation message appears DNAC data will be overwritten by PI data by the Force Sync. Click Yes to proceed or No to stop Force Sync.

A success message appears after the successful completion of the Force Sync operation.

What to do next

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

  2. Multi-DNAC is supported from Prime Data Migration Tool Update 02.0. This feature allows you to migrate to multiple DNAC clusters (one DNAC server at a time) and retain the migration data for each DNAC server. For more information, see Multi-DNAC Support.

  3. Refer the important notes about Cisco Prime Infrastructure - Cisco DNA Center migration, see Important Notes .

  4. For the open bugs specific to the Cisco Prime Infrastructure - Cisco DNA Center migration in Prime Infrastructure 3.10.1, see Open Caveats of Cisco Prime Infrastructure 3.10.1 Release Notes.

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.

  • Groups with empty/0/null civic location values will be ignored for migration.

  • When migrating ISE from Prime to DNA Center, ISE gets added to DNA Center in the failed state. To avoid this make sure to do the following:

    • Activate PXGrid on ISE

    • Enable ERS on ISE

    • ISE's CLI and GUI password must be the same

  • 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 which 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”.

  • Devices managed with SNMP v2 and v3 can be migrated to Cisco DNA Center.

  • Any devices managed only with SNMP v1 or SNMP v3 with DES protocol of AuthPriv credentials in Cisco Prime Infrastructure cannot be migrated to Cisco DNA Center.

  • Also, bulk migration fails if any one of the devices managed by SNMP v1 or v3 with DES protocol of AuthPriv credentials.

  • 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, error will be thrown as “Unsupported Version” 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 DNA Center versions.

  • DNA Center Version 2.2.1.0 specific update.

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