Step 1

Download the upgrade tool.

1. Navigate to the Nexus Dashboard download page.

   https://software.cisco.com/download/home/286327743/type/286328258/

2. In the Latest Releases list, choose the target release.

3. Download the upgrade tool appropriate for your deployment type.

   DCNM 11.5(4) deployment type	Upgrade Tool File Name
   ISO/OVA	DCNM_To_NDFC_4.1.1_Upgrade_Tool_OVA_ISO.zip
   Linux or Windows	DCNM_To_NDFC_4.1.1_Upgrade_Tool_LIN_WIN.zip

4. Copy the upgrade tool image to your existing DCNM 11.5(4) server using the sysadmin account.

Step 2

Extract the archive and validate the signature for Linux/Windows deployments.

1. Ensure that you have Python 3 installed.

   $ python3 --version
   Python 3.9.6
   

2. Extract the downloaded archive.

   # unzip DCNM_To_NDFC_4.1.1_Upgrade_Tool_LIN_WIN.zip
   Archive: DCNM_To_NDFC_4.1.1_Upgrade_Tool_LIN_WIN.zip
   extracting: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN.zip
   extracting: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN.zip.signature
   inflating: ACI_4070389ff0d61fc7fbb8cdfdec0f38f30482c22e.PEM
   inflating: cisco_x509_verify_release.py3

3. Validate signature.

   Inside the ZIP archive, you will find the upgrade tool as well as the signature file. Use the following commands to validate the upgrade tool:

   
   # ./cisco_x509_verify_release.py3 -e ACI_4070389ff0d61fc7fbb8cdfdec0f38f30482c22e.PEM -i DCNM_To_NDFC_Upgrade_Tool_LIN_WIN.zip -s DCNM_To_NDFC_Upgrade_Tool_LIN_WIN.zip.signature -v dgst -sha512
   
   Retrieving CA certificate from https://www.cisco.com/security/pki/certs/crcam2.cer ...
   Successfully retrieved and verified crcam2.cer.
   Retrieving SubCA certificate from https://www.cisco.com/security/pki/certs/innerspace.cer ...
   Successfully retrieved and verified innerspace.cer.
   Successfully verified root, subca and end-entity certificate chain.
   Successfully fetched a public key from ACI_4070389ff0d61fc7fbb8cdfdec0f38f30482c22e.PEM.
   Successfully verified the signature of DCNM_To_NDFC_Upgrade_Tool_LIN_WIN.zip using ACI_4070389ff0d61fc7fbb8cdfdec0f38f30482c22e.PEM

4. Once the validation script signature is verified, extract the script itself.

   # unzip DCNM_To_NDFC_Upgrade_Tool_LIN_WIN.zip
   Archive: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN.zip
   creating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/log4j2.properties
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/DCNMBackup.sh
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/DCNMBackup.bat
   creating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/jar/
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/jar/jarchivelib-0.7.1-jar-with-dependencies.jar
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/jar/bcprov-jdk15on-1.68.jar
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/jar/not-going-to-be-commons-ssl-0.3.20.jar
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/jar/jnm.jar
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/jar/slf4j-simple-1.7.21.jar
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/jar/log4j.properties
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/jar/dcnmbackup.jar
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/jar/sequences.info.oracle
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/jar/tables.info.postgres
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/jar/sequences.info.postgres
   inflating: DCNM_To_NDFC_Upgrade_Tool_LIN_WIN/jar/tables.info.oracle

Step 3

Extract the archive and validate the signature for ISO/OVA deployments.

1. Extract the downloaded archive.

   # unzip DCNM_To_NDFC_4.1.1_Upgrade_Tool_OVA_ISO.zip
   Archive: DCNM_To_NDFC_4.1.1_Upgrade_Tool_OVA_ISO.zip
   inflating: DCNM_To_NDFC_Upgrade_Tool_OVA_ISO_4.1.1
   extracting: DCNM_To_NDFC_Upgrade_Tool_OVA_ISO_4.1.1.signature
   inflating: cisco_x509_verify_release.py3
   inflating: ACI_4070389ff0d61fc7fbb8cdfdec0f38f30482c22e.PEM

2. Validate signature.

   Inside the ZIP archive, you will find the upgrade tool as well as the signature file. Use the following commands to validate the upgrade tool:

   # ./cisco_x509_verify_release.py3 -e ACI_4070389ff0d61fc7fbb8cdfdec0f38f30482c22e.PEM -i DCNM_To_NDFC_Upgrade_Tool_OVA_ISO_4.1.1 -s DCNM_To_NDFC_Upgrade_Tool_OVA_ISO.signature -v dgst -sha512
   Retrieving CA certificate from https://www.cisco.com/security/pki/certs/crcam2.cer ...
   Successfully retrieved and verified crcam2.cer.
   Retrieving SubCA certificate from https://www.cisco.com/security/pki/certs/innerspace.cer ...
   Successfully retrieved and verified innerspace.cer.
   Successfully verified root, subca and end-entity certificate chain.
   Successfully fetched a public key from ACI_4070389ff0d61fc7fbb8cdfdec0f38f30482c22e.PEM.
   Successfully verified the signature of DCNM_To_NDFC_Upgrade_Tool_OVA_ISO using ACI_4070389ff0d61fc7fbb8cdfdec0f38f30482c22e.PEM

Step 4

Back up existing configuration.

1. Log in to your DCNM Release 11.5(4) appliance console.

2. Create a screen session.

   The following command creates a session which allows you to execute additional commands:

   dcnm# screen

   Note that the commands continue to run even when the window is not visible or if you get disconnected.

3. Gain super user (root) access.

   dcnm# su
   Enter password: <root-password>
   [root@dcnm]#

4. For OVA and ISO, enable execution permissions for the upgrade tool.

   [root@dcnm]# chmod +x ./DCNM_To_NDFC_Upgrade_Tool_OVA_ISO_4.1.1

5. Run the upgrade tool you downloaded in the previous step.

   • For example, for release 4.1.1 for Windows:

     C:\DCNM_To_NDFC_Upgrade_Tool_LIN_WIN>DCNMBackup.bat
     Enter DCNM root directory [C:\Program Files\Cisco Systems\dcm]:
     Initializing, please wait...
     *******************************************************************************
     Welcome to DCNM-to-NexusDashboard Upgrade Tool for Linux/Windows.
     This tool will analyze this system and determine whether you can move to Nexus Dashboard 4.1.1 or not.
     If upgrade to Nexus Dashboard 4.1.1 is possible, this tool will create files to be used for performing the upgrade.
     Thank you!
     *******************************************************************************
     This tool will backup config data. Exporting Operational data like Performance(PM) might take some time.
     Do you want to export operational data also? [y/N]: y
     *******************************************************************************
     Sensitive information will be encrypted using an encryption key.
     This encryption key will have to be provided when restoring
     the backup file generated by this tool.
     Please enter the encryption key:
     Enter it again for verification:
     …..
     2024-07-25 22:35:34,944 [main] DEBUG org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection [id: 0][route: {s}->https://127.0.0.1:9200] can be kept alive indefinitely
     2024-07-25 22:35:34,944 [main] DEBUG org.apache.http.impl.conn.DefaultManagedHttpClientConnection - http-outgoing-0: set socket timeout to 0
     2024-07-25 22:35:34,944 [main] DEBUG org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection released: [id: 0][route: {s}->https://127.0.0.1:9200][total kept alive: 1; route allocated: 1 of 20; total allocated: 1 of 20]
     2024-07-25 22:35:34,969 [main] INFO DCNMBackup - Total number of Json data entries in backup/es/pmdb_sanportratedata_daily.data ==> 145
     2024-07-25 22:35:35,036 [main] INFO DCNMBackup - ###### Total time to export Daily data: 7 seconds.
     2024-07-25 22:35:35,036 [main] INFO DCNMBackup - ###### Total time to export PM data: 36 seconds.
     2024-07-25 22:35:35,169 [main] INFO DCNMBackup - Creating data file...
     2024-07-25 22:35:38,083 [main] INFO DCNMBackup - Creating metadata file...
     2024-07-25 22:35:38,085 [main] INFO DCNMBackup - Creating final backup archive...
     2024-07-25 22:35:38,267 [main] INFO DCNMBackup - Done
     

   • For example, for release 4.1.1 for Linux:

     # ./DCNMBackup.sh
     Enter DCNM root directory [/usr/local/cisco/dcm]:
     Initializing, please wait...
     *******************************************************************************
     Welcome to DCNM-to-NexusDashboard Upgrade Tool for Linux/Windows.
     This tool will analyze this system and determine whether you can move to Nexus Dashboard 4.1.1 or not.
     If upgrade to Nexus Dashboard 4.1.1 is possible, this tool will create files to be used for performing the upgrade.
     Thank you!
     
     *******************************************************************************
     
     This tool will backup config data. Exporting Operational data like Performance(PM) might take some time.
     Do you want to export operational data also? [y/N]: y
     *******************************************************************************
     Sensitive information will be encrypted using an encryption key.
     This encryption key will have to be provided when restoring
     the backup file generated by this tool.
     
     Please enter the encryption key:
     Enter it again for verification:
     ……
     2024-07-26 04:04:46,540 [main] INFO DCNMBackup - Total number of Json data entries in backup/es/pmdb_sanportratedata_daily.data ==> 92
     2024-07-26 04:04:46,543 [main] INFO DCNMBackup - ###### Total time to export Daily data: 3 seconds.
     2024-07-26 04:04:46,543 [main] INFO DCNMBackup - ###### Total time to export PM data: 11 seconds.
     2024-07-26 04:04:46,958 [main] INFO DCNMBackup - Creating data file...
     2024-07-26 04:04:47,456 [main] INFO DCNMBackup - Creating metadata file...
     2024-07-26 04:04:47,467 [main] INFO DCNMBackup - Creating final backup archive...
     2024-07-26 04:04:47,478 [main] INFO DCNMBackup - Done.
     

   • For example, for release 4.1.1 for OVA:

     # ./DCNM_To_NDFC_Upgrade_Tool_OVA_ISO_4.1.1
     *******************************************************************************
     Welcome to DCNM-to-NexusDashboard Upgrade Tool for OVA/ISO.
     This tool will analyze this system and determine whether you can move to
     Nexus Dashboard 4.1.1 or not.
     If upgrade to Nexus Dashboard 4.1.1 is possible, this tool will create files
     to be used for performing the upgrade.
     NOTE:
     Only backup files created by this tool can be used for upgrading,
     older backup files created with 'appmgr backup' CAN NOT be used
     for upgrading to Nexus Dashboard 4.1.1
     Thank you!
     
     *******************************************************************************
     Continue? [y/n]: y
     Collect operational data (e.g. PM, EPL)? [y/n]: y
     Does this DCNM 11.5(4) have DCNM Tracker feature enabled on any switch on any fabric? [y/n]: n
     
     Sensitive information will be encrypted using an encryption key.
     This encryption key will have to be provided when restoring
     the backup file generated by this tool.
     
     Please enter the encryption key:
     Enter it again for verification:
     ……
     Adding backup header
     Collecting DB table data
     Collecting DB sequence data
     Collecting stored credentials
     Collecting Custom Templates
     Collecting CC files
     Collecting L4-7-service data
     Collecting CVisualizer data
     Collecting EPL data
     Collecting PM data - WARNING: this will take a while!
     Collecting AFW app info
     Decrypting stored credentials
     Adjusting DB tables
     Creating dcnm backup file
     Creating final backup file
     Done.
     Backup file: backup11_sandcnm_20240726-113054.tar.gz
     

Step 5

Deploy a brand new Nexus Dashboard cluster as described in one of the earlier chapters in this document.

Step 6

Restore the configuration backup in the new cluster.

1. Navigate to the unified backup and restore page in the Admin Console GUI: Admin > Backup and Restore.

   Backups that are already configured are listed in the Backups page.

2. Click Restore in the upper right corner of the main Backup and Restore page to access the Restore slider page.

   The Restore slide page appears.

3. In the Source field, determine where the backup is that you want to restore, if applicable.

   • Upload Configuration Backup Table: The Backup File area appears, where you can either drag and drop a local backup file to restore or you can navigate to the local area on your system to select a backup file to restore.

   • Remote Location:

     1. In the Remote Location field, select an already-configured remote location from the list, if available, or click Create Remote Location.

        If you click Create Remote Location, follow the procedures provided in "Create a remote storage location" in Backing Up and Restoring Your Nexus Dashboard, then return here. Even though you should have configured a remote location as part of the remote backup process, you might also have to configure a remote location as part of the restore process if you’re in a different cluster from the one where you configured the remote backup. In this case, you would be configuring the remote location again at this point so that the system can find the remote backup that you configured in the other cluster.

     2. In the Remote Path field, enter the remote path where the remote backup resides.

4. In the Encryption Key field, enter the encryption key that you used when you backed up the file.

5. In the Validation area, on the row with your backup, click Validate and Upload.

6. When the Progress bar shows 100% for the validation, the Next button becomes active. Click Next.

7. (Optional) Check the Ignore External Service IP Configuration check box, if necessary.

   If the Ignore External Service IP Configuration check box is selected, then the external service IP configuration is ignored. This selection allows you to take a backup on a system and restore it on a different system, with different management and/or data subnets.

   The following table provides more information on how IP addresses get honored if you leave the Ignore External Service IP Configuration box unchecked:

   Deployment Type in Release 11.5(4)	In 11.5(4), trap IP address is collected from	LAN Device Management Connectivity	Trap IP address after upgrade	Result
   LAN Fabric Media Controller	eth1 (or vip1 for HA systems)	Management	Belongs to Management subnet	Honored There is no configuration difference. No further action required.
   LAN Fabric Media Controller	eth0 (or vip0 for HA systems)	Management	Does not belong to Management subnet	Ignored, another IP from the Management pool will be used as trap IP. Configuration difference is created. On the Manage > Fabrics, double click on the fabric to view Fabric Overview. From the Actions drop-down list, select Recalculate and Deploy. Click Deploy Config.
   LAN Fabric Media Controller	eth0 (or vip0 for HA systems)	Data	Belongs to Data subnet	Honored There is no configuration difference. No further action required.
   LAN Fabric Media Controller	eth0 (or vip0 for HA systems)	Data	Does not belong to Data subnet	Ignored, another IP from the Data pool will be used as trap IP. Configuration difference is created. On the Manage > Fabrics, double click on the fabric to view Fabric Overview. From the Actions drop-down list, select Recalculate and Deploy. Click Deploy Config.
   SAN Management	OVA/ISO – trap.registaddress (if set) eth0 (if trap.registaddress is not set) Windows/Linux – trap.registaddress (if set) Interface based on event-manager algorithm (if trap.registaddress is not set	Not applicable	Belongs to Data subnet	Honored There is no configuration difference. No further action required.
   		Not applicable	Does not belong to Data subnet	Ignored, another IP from the Data pool will be used as trap IP.

8. Click Restore.

   A warning window appears to verify that you want to begin the restore process. Note that you will not be able to access any Nexus Dashboard functionality while the restore process runs, which could take several minutes.

9. Click Restore in the warning window to proceed with the restore process.

   Another window appears, showing the progress of the restore process. Click the arrow next to the entry in the Type column to get more details of the restore process.

10. If the restore process is successful, you will see 100% as the Progress, and the View History button becomes active.

    Click View History to navigate to the History area in the Backup and Restore window, with the restore process displayed and Success shown in the Status column.

Step 7

Complete the post-upgrade tasks.

1. If you have a SAN deployment in ND release 4.1.1:

   After restoring the data from backup, all the server-smart licenses are OutofCompliance.

   You can migrate to Smart Licensing using Policy from the Admin > Licensing > Smart page in the UI and establish trust with CCSM using SLP.

2. If you have a LAN deployment in ND release 4.1.1:

   Certain features might not carried over when you upgrade from DCNM 11.5(4). See Feature Compatibility Post Upgrade for more information.