Migrate from NDB to ND

Migrate from NDB to ND

If you are currently using the NDB centralized version 3.10.4 (or 3.10.5.x) and intend to upgrade, you can upgrade to the NDB version which is available as part of ND 4.2.

Use this procedure for migrating from the centralized deployment of Nexus Data Broker (NDB) to Nexus Dashboard (ND).

The supported paths for migrating to ND 4.2 are:

  • Migration from NDB 3.10.4 or 3.10.5.x to ND 4.2.

  • For NDB versions prior to release 3.10.4, migration to ND 4.2 is a two-step process. NDB versions prior to 3.10.4 must first be upgraded to 3.10.4 (or 3.10.5.x). The supported NDB versions for this upgrade are: 3.8.x, 3.9.x, 3.10.1, 3.10.2, 3.10.3.

    Refer to the respective Nexus Data Broker Deployment Guide for the detailed procedure for upgrading to NDB release 3.10.4 or 3.10.5.x.

    Example: For upgrading NDB 3.8.1 to ND 4.2, first upgrade to NDB 3.10.4 (or 3.10.5.x), and then migrate to ND 4.2.

Before you begin

  1. Log in to the Nexus Data Broker GUI, and download the configuration file using the standard procedure.

    On the NDB GUI, navigate to Administration > Backup Restore > Actions. You can back up the configuration to your local machine or to a server.

  2. Convert the NDB configuration file (which you have downloaded using step 1) to an ND-compatible file using the backup_converter.sh file located on Github.

  3. (optional) Create an encryption key using ./backup_converter.sh -f {zip_file} -v {ND_version} -k {password}. See Run the Script step (Github). This encryption key cannot be changed later. Ensure to save the encryption key as you will need to enter the same key while restoring the backup.

  4. Follow the steps detailed in the steps_to_generate_ND_format_backup.txt file (available on Github). The file includes a detailed procedure for converting the NDB configuration file to an ND-compatible file. The ND compatible file is named as cisco-nddb-backup.tar.gz.

Procedure

Step 1

Log in to the Nexus Dashboard GUI.

Step 2

Navigate to Admin > Backup and Restore.

Step 3

On the Backup and Restore screen, click the Restore button.

Step 4

On the Restore screen, enter:

  1. Source: the location of the backup file.

  2. Backup file: the converted ND compatible file.

  3. Encryption key: enter the custom encryption key which you had earlier created. If you have not set an encryption key, the default value, cisco123, is assigned.

  4. Click Validate and upload. The Filename field is automatically populated with the ND compatible file (cisco-nddb-backup.tar.gz).

  5. Click Next after the validation is complete.

    The progress of the validation is indicated by the green bar, wait till 100% is displayed.

Step 5

(on the next page of the Restore screen) Check the Do not restore persistent IP configs from this backup check box to override the persistent IP configuration.

Ensure to check the check box, else the restore process will fail.

Step 6

Click Restore.

Step 7

Click Restore (again) on the Begin Restore confirmation screen.

After the confirmation, the migration process is initiated. You can monitor the progress; the various stages are indicated by the progress bar.

Step 8

Click Close.

What to do next

After the migration process, perform these steps:

  1. On the ND GUI, navigate to Manage > Fabrics.

  2. Select the required NDB fabric (NDB_default or if you have created a slice, the slice name is the fabric name).

  3. Click Actions (on the top right) > Recalculate and deploy.

    This updates the configuration on the NDB devices.

  4. Check the device mode (Manage > Inventory). The mode is now displayed as Normal (during the migration process, the device mode is indicated as Migration).