Cisco DCNM Installation Guide, Release 10.4(2)

Upgrading Cisco DCNM

---

This section includes instructions for upgrading your Cisco DCNM Open Virtual Appliance installation in the following scenarios:

You can migrate Cisco DCNM with a local PostgreSQL database and an external Oracle database and Cisco DCNM in a High Availability (HA) environment.

Note Cisco DCNM Release 10.4(x) allows the HA setup for XMPP uses external oracle database. You must provide username and password for external oracle database. Create a new username and password for the XMPP application to use in the same remote Database instance, used by the Cisco DCNM.

Note Before upgrading Cisco DCNM, ensure that automatic failover is disabled. Otherwise, if one server within the federation is down, the devices discovered by the server will be moved to the other DCNM server which comes up first after upgrade. To prevent the automatic failover for DCNM upgrade, you need to disable the automatic failover on all DCNMs within the federation, and then upgrade the DCNM server one by one. Only after all the DCNMs upgrade successfully and run normally, then enable the automatic failover again. To enable / disable automatic failover, go to Administration > DCNM Server > Federation from DCNM web page, click the check box at top left for Enable Automatic Failover.

Note When upgrading to a newer DCNM version, you should use the same administrative password (as used in the existing setup) for the new DCNM setup. If you want to use a different password in the new setup, change the password in the existing DCNM setup before taking a backup and initiating the upgrade process.

Adhere to the following password requirements. If you do not comply with the requirements, the DCNM application might not function properly:

– It must be at least 8 characters long and contain at least one alphabet and one numeral.

– It can contain a combination of alphabets, numerals, and special characters.

– DO NOT use any of these special characters in the DCNM password for Linux, Windows, OVA, and ISO platforms: <SPACE> & $ % ‘ “ ^ = < > ; :

Note When upgrading to DCNM release 10.4(2), temperature data will not be automatically backed up as part of appmgr backup script on an OVA setup where EPL is not enabled.

This chapter contains the following:

• Retaining the CA Signed Certificate
• Upgrading Cisco DCNM Windows and Linux through GUI Installation
• Upgrading Cisco DCNM Windows and Linux through Silent Installation
• Upgrading Cisco DCNM Windows and Linux Federation through GUI Installation
• Upgrading Cisco DCNM Windows and Linux Federation through Silent Installation
• Upgrading Cisco DCNM Virtual Appliance with External Oracle Database
• Upgrading Cisco DCNM appliances with Enhanced Fabric Management in HA Environment
• Upgrading Cisco DCNM Virtual Appliance with Local PostgreSQL Database
• Upgrading Cisco DCNM appliances without Enhanced Fabric Management in HA Environment
• Upgrading Cisco DCNM Native HA appliances
• Database Utility Scripts
• Standalone Inline Upgrade for OVA/ISO
• DCNM Native HA Inline Upgrade for OVA/ISO

Retaining the CA Signed Certificate

Perform this procedure if you need to retain the CA signed SSL Certificate after upgrade.

DETAILED STEPS

---

Step 1 Backup the signed certificate from the location

<DCNM_install_root>\dcm\jboss-as-7.2.0.Final\standalone\configuration\fmserver.jks

Step 2 Upgrade to Cisco DCNM Release 10.4(2) based on the requirement.

Step 3 After upgrade, copy the certificate to the same location on the upgraded version of the Cisco DCNM.

---

Note You must load the certificates to the same location as mentioned in Step 1.

---

Step 4 Open the following files:

• <Install root>/dcm/JBoss- 7.2.0.Final/standalone/configuration/standalone-san.xml
• <Install root>/dcm/JBoss- 7.2.0.Final/standalone/configuration/ standalone-lan.xml

Step 5 Search for key-alias =“sme” and replace with key-alias=<key-alias used to create CA signed SSL Certificate>

Step 6 Restart the DCNM Services.

---

 

Upgrading Cisco DCNM Windows and Linux through GUI Installation

Before you begin, make sure that Cisco DCNM 10.3(1),10.3(2), or 10.4(1) is up and running.

Step 1 Stop the DCNM services.

Step 2 Run the Cisco DCNM software for Release 10.4(2) executable file.

Upgrade Notification window appears

Step 3 Click OK to begin the upgrade.

Step 4 Click Done after the upgrade is complete.

The Cisco DCNM Release 10.4(2) services will start automatically.

Upgrading Cisco DCNM Windows and Linux through Silent Installation

Before you begin, make sure that Cisco DCNM 10.3(1), 10.3(2), or 10.4(1) is up and running.

Note Cisco DCNM supports Silent installation and upgrade only on Local Authorization mode and not on Remote Authorization mode.

DETAILED STEPS

---

Step 1 Stop the DCNM services.

Step 2 Open the installer.properties file and update the following properties:

INSTALLATION_TYPE=UPGRADE

USE_EXISTING_DB=TRUE

 

Step 3 Go to the directory where you downloaded the Cisco DCNM software and run the appropriate installer by using the following command:

• For Windows installer—dcnm-release.exe -i silent -f <path_of_installer.properties>
• For Linux installer—dcnm-release.bin -i silent -f <path_of_installer.properties>

The Cisco DCNM Release 10.4(2) services will start after the upgrade is complete.

---

Note For Windows upgrade, you can check the status of the upgrade in the Task Manager process.

For Linux upgrade, you can check the status of the upgrade process by using the following command: ps -ef | grep ‘LAX’. The prompt will return after the silent install is complete.

---

 

Upgrading Cisco DCNM Windows and Linux Federation through GUI Installation

Before you begin, make sure that Cisco DCNM 10.3(1), 10.3(2), or 10.4(1) is up and running.

Note Ensure that both primary and secondary database properties are same.

Step 1 Stop both the primary and secondary DCNM services.

Step 2 On the primary server, run the Cisco DCNM Release 10.4(2) executable file.

Upgrade notification window appears.

Step 3 Click OK to begin the upgrade.

Step 4 On the secondary server, perform run the Cisco DCNM Release 10.4(2) executable file.

Upgrade notification window appears.

Step 5 Click OK to begin the upgrade.

Step 6 On the primary server, click Done after the upgrade is complete.

The Cisco DCNM Release 10.4(2) services will start automatically on the primary server.

Step 7 On the secondary server, click Done after the upgrade is complete.

The Cisco DCNM Release 10.4(2) services will start automatically on the secondary server.

Upgrading Cisco DCNM Windows and Linux Federation through Silent Installation

Before you begin, make sure that Cisco DCNM 10.3(1), 10.3(2), or 10.4(1) is up and running.

Note Cisco DCNM supports Silent installation and upgrade only on Local Authorization mode and not on Remote Authorization mode.

Note Ensure that both primary and secondary database properties are same.

Step 1 Stop both the primary and secondary DCNM services.

Step 2 On the primary server, open the installer.properties file and update the following properties:

Step 3 Go to the directory where you downloaded the Cisco DCNM software and run the appropriate installer by using the following command:

• For Windows installer—dcnm-release.exe -i silent -f <path_of_installer.properties>
• For Linux installer—dcnm-release.bin -i silent -f <path_of_installer.properties>

Note For Windows upgrade, you can check the status of the upgrade in the Task Manager process.

For Linux upgrade, you can check the status of the upgrade process by using the following command: ps -ef | grep ‘LAX’. The prompt will return after the silent install is complete.

Step 4 On the secondary server, open the installer.properties file and update the following properties:

Step 5 Go to the directory where you downloaded the Cisco DCNM software and run the appropriate installer by using the following command:

• For Windows installer—dcnm-release.exe -i silent -f <path_of_installer.properties>
• For Linux installer—dcnm-release.bin -i silent -f <path_of_installer.properties>

Step 6 On the primary server, click Done after the upgrade is complete.

The Cisco DCNM Release 10.4(x) services will start automatically on the primary server.

Step 7 On the secondary server, click Done after the upgrade is complete.

The Cisco DCNM Release 10.4(x) services will start automatically on the secondary server.

Upgrading Cisco DCNM Virtual Appliance with Local PostgreSQL Database

Before you begin, make sure that Cisco DCNM 10.3(1), 10.3(2) or 10.4(1) is up and running.

Step 1 Use the appmgr backup all command to backup all applications associated with the installation of Cisco DCNM 10.3(x) or 10.4(1).

A prompt appears to provide the DCNM DB password and XMPP DB password. By default, this password is the administrative password provided during the Open Virtual Appliance installation.

Step 2 On Cisco DCNM 10.4(2), ensure that the MAC addresses along with all network settings such as the IP address, default gateway, hostname, etc., are identical to the Cisco DCNM 10.3(x) or 10.4(1) installation.

Step 3 Transfer the backup file to an external file system.

Step 4 Power off Cisco DCNM 10.3(x) or 10.4(1).

Step 5 Deploy the Cisco DCNM Open Virtual Appliance file for version 10.4(2).

• Use the same network parameters (IP address/subnet/gateway/DNS).
• Use the same administrative password.
• Use the same vCenter port groups for both network interfaces.
• Disable auto-power-on. (The Power on Open Virtual Appliance after deployment check-box should not be selected).

Step 6 After Cisco DCNM 10.4(2) is deployed, right-click on VM > Edit Settings > Hardware.

For both Network Adapters, update the MAC address to be the same as Cisco DCNM 10.3(x) or 10.4(1). This ensures that the same MAC address is used for the new Virtual Machine (VM); licenses on Cisco DCNM will not need to be regenerated in the event of an upgrade.

Step 7 Power on DCNM 10.4(2) VM.

Step 8 Copy the Cisco DCNM 10.3(x) or 10.4(1) backup file from the external repository to Cisco DCNM 10.4(2).

Step 9 Use the appmgr status all status all command to make sure that all applications are up and running.

Step 10 Use the appmgr stop all to shut down all applications on Cisco DCNM 10.4(2).

Step 11 Use the appmgr upgrade <backup filename> command to run the upgrade script on Cisco DCNM 10.4(2).

The application displays the following message:

Step 12 Press Y to continue.

If you choose option [1] Standalone DCNM with Local PostgreSQL database, It will get upgraded successfully.

If you choose option [2] Standalone DCNM with External Oracle database, ensure that the external database is up and running. For more information, see Upgrading Cisco DCNM Virtual Appliance with External Oracle Database.

Upgrading Cisco DCNM Virtual Appliance with External Oracle Database

Perform the following procedure to upgrade Cisco DCNM Virtual Appliance with external Oracle database.

Note Ensure that you configure the timezone after installation or upgrade, before performing any other operations on the Cisco DCNM Appliance. For more information, see Setting the Timezone for Cisco DCNM Virtual Appliances.

When you select Option [2] in Step 12 of the procedure Upgrading Cisco DCNM Virtual Appliance with Local PostgreSQL Database, the following query appears:

Prior to upgrade, we strongly advise that you make a backup of your remote Oracle instance. Do you want to proceed with upgrade?

Press 'y' to continue [y/n] [n]

Step 1 Press Y to continue.

Step 2 Enter the DB URL.

Step 3 Enter the DB username

Step 4 Enter the DB password.

Enter it again for verification:

Step 5 Enter the administrative password provided during Virtual Appliance installation, when prompted for the root password.

The external DCNM database will be configured to access all the Fabric applications using the root password of this server.

Note You can change the password using the Cisco DCNM Web Client. To change the password, choose Administration > Management Users > Local.

Note Upgrading from Non-DFA to Cisco DCNM 10.4(2) with a Local PostgreSQL or External Oracle Database. Deploy the Cisco DCNM 10.4(2) with the Enhanced Fabric Management Network fields with default values (i.e., IP Address: 0.0.0.0, Subnet Mask: 0.0.0.0 and DNS IP: 1.1.1.1). Perform the procedure detailed in Upgrading Cisco DCNM Virtual Appliance with External Oracle Database.

Note Ensure that you configure the timezone after installation or upgrade, before performing any other operations on the Cisco DCNM Appliance. For more information, see Setting the Timezone for Cisco DCNM Virtual Appliances.

Upgrading Cisco DCNM appliances with Enhanced Fabric Management in HA Environment

Before you begin, ensure that:

• Both the Cisco DCNM 10.3(x) or 10.4(1) Active and Standby peers are up and running.
• Automatic failover is stopped manually. To disable automatic failover, go to Administration > DCNM Server > Federation in the DCNM web page, and clear the Enable Automatic Failover check box at the top left part of the screen.

Note For more information on Active and Standby peers in a High Availability environment, see “Managing Applications in a High-Availability Environment”.

Step 1 Verify if the appmgr backup all command was executed on both the Active and Standby peers. Check if separate tar archives are stored in an external file system.

Note If it is the non-DFA environment, please verify if the appmgr backup dcnm command was executed on both the Active and Standby peers.

Step 2 Power off the Cisco DCNM 10.3(x) or 10.4(1) Active peer.

Step 3 Power-on the Cisco DCNM 10.4(2) Active peer.

Step 4 Use the appmgr status all command to ensure that all the applications are up and running on the Cisco DCNM 10.4(2) Active peer.

Step 5 Stop all DCNM applications on the Cisco DCNM 10.4(2) Active peer, by using appmgr stop all command.

Step 6 Use the appmgr upgrade <active.tar.gz> command to run the upgrade script.

Step 7 Power off the Cisco DCNM 10.3(x) or 10.4(1) Standby peer.

Step 8 Power on the Cisco DCNM 10.4(2) Standby peer. Use the appmgr status all command to make sure that all applications are up and running.

Step 9 Stop all applications on the Cisco DCNM 10.4(2) Standby peer.

Step 10 Use the appmgr upgrade <standby.tar.gz> command to run the upgrade script on the Cisco DCNM 10.4(2) Standby peer.

a. Choose option [3] High Availability when prompted.

b. Select option [2] Standby when prompted.

To migrate the standby peer, perform the following:

a. Enter the active eth0 IP address.

Step 11 Invoke the following on the Active peer to establish SSH trust to the Standby peer:

Note Ensure that you configure the timezone after installation or upgrade, before performing any other operations on the Cisco DCNM Appliance. For more information, see Setting the Timezone for Cisco DCNM Virtual Appliances.

Upgrading Cisco DCNM appliances without Enhanced Fabric Management in HA Environment

Before you begin, ensure that:

• The virtual appliance is installed in Non Programmable Fabric mode.
• Automatic failover is stopped manually. To disable automatic failover, go to Administration > DCNM Server > Federation in the DCNM web page, and clear the Enable Automatic Failover check box at the top left part of the screen.

Note For instruction about installing these applications with the Cisco DCNM Open Virtual Appliance, see DCNM installation without Enhanced Fabric Management capabilities.
For more information on NON DFA High Availability environment, see Managing Applications in a High-Availability Environment.

Step 1 Make sure that both Cisco DCNM DCNM 10.3(x) servers are deployed, powered on and made it as a First and Federated node by using the below commands.

appmgr setup ha -type first-node

appmgr setup ha -type federated-node

Step 2 Verify if the appmgr backup dcnm command was executed on both the First Node and Federated Node using the below command. Check if separate tar archives are stored in an external file system.

Step 3 Bring up the DCNM 10.4(x) First and Federated node. Do not power on the DCNM yet.

Step 4 Power off the Cisco DCNM 10.3(x) First and Federated Node virtual appliance.

Step 5 Power-on the Cisco DCNM 10.4(x) First and Federated Node virtual appliance which should be deployed in the same eth0 IP of 10.3(x).

Note While deploying Cisco DCNM 10.4(x) First and Federated Node virtual appliance, the Enhanced Fabric Management Network fields must contain default values (i.e., IP Address:0.0.0.0, Subnet Mask:0.0.0.0 and DNS IP:1.1.1.1)

Step 6 Use the appmgr status all command to ensure that DCNM applications are up and running on the Cisco DCNM 10.4(x) First and Federated Nodes.

Step 7 Stop the applications on the Cisco DCNM 10.4(x) First node, by using appmgr stop dcnm command.

Step 8 Use the command appmgr upgrade <first_node.tar.gz> on the Cisco DCNM 10.4(x) First node to run the upgrade script. After issuing appmgr upgrade <first_node.tar.gz> on First Node, user will be prompted for various inputs. Provide the inputs as per the sample given below.

Step 9 Stop DCNM applications on the Cisco DCNM 10.4(x) Federated Node by using appmgr stop dcnm command.

Step 10 Run the below NTP command on standby to sync the time.

ntpdate -b -u clock.cisco.com

Step 11 Use the appmgr upgrade <federated_node.tar.gz> command to run the upgrade script on the Cisco DCNM 10.4(x) Federated Node. After issuing appmgr upgrade <first_node.tar.gz> on First Node, user will be prompted for various inputs. Provide the inputs as per the sample given below.

Upgrading Cisco DCNM Native HA appliances

Perform the following to upgrade the Cisco DCNM Native HA appliances to Release 10.4(2).

Before you begin, ensure that both the Cisco DCNM 10.3(x) or 10.4(1) Active and Standby peers are up and running.

Step 1 Verify if the appmgr backup all command was executed on both the Active and Standby peers. Check if separate .tar archives are stored in an external file system.

Step 2 Power off the Cisco DCNM 10.3(x) or 10.4(1) Standby host first and then power off the Active host.

Step 3 Power on the Cisco DCNM 10.4(2) Active host, and then power on the Standby host with the same IP and MAC address.

If both eth0 and eth1 interfaces are in the same subnet, edit the /etc/sysctl.conf file for DCNM ISO Virtual appliance Native HA installation on both active and standby nodes for both the appliances, as follows:

• Change the value of net.ipv4.conf.default.rp_filter from 1 to 2.
• Add net.ipv4.conf.all.rp_filter = 2 to the sysctl.conf file.

Save and close the file. On the SSH terminal, execute the sysctl --system command.

Step 4 Ensure that all the applications are up and running on the Cisco DCNM 10.4(2) Active host. Use the appmgr status all command to ensure that

Step 5 Stop all the DCNM applications on the Cisco DCNM 10.4(2) Active host, by using appmgr stop all command.

Step 6 Transfer the backup file from the external file system to the corresponding setup.

Step 7 Run the upgrade script on the Active host, by using the appmgr upgrade <active.tar.gz> command.

Step 8 Provide the inputs as per the sample given below.

Note You need to wait till all applications are up and running in the Active node. Use the appmgr status all command to ensure all applications are up and running.

Step 9 Stop all the DCNM applications on the Cisco DCNM 10.4(2) Standby host, by using appmgr stop all command.

Step 10 Run the upgrade script on the Standby host, by using the appmgr upgrade <standby.tar.gz> command.

Step 11 Provide the inputs as per the sample given below.

Database Utility Scripts

Remote Oracle Database Utility Scripts for Backup and Restore

Irrespective of the platform, Cisco DCNM is installed (Windows or Linux), the following scripts to backup and restore the remote Oracle database.

Utility scripts for Oracle database that is installed on Linux platform are;

1. backup-remote-oracledb.sh

2. restore-remote-oracledb.sh

Utility scripts for Oracle database that is installed on Windows platform are:

1. backup-remote-oracledb.bat

2. restore-remote-oracledb.bat

Cisco DCNM host is configured to run with a remote Oracle database. As part of housekeeping, you can copy DCNM utility scripts to a remote Oracle database and restore the DCNM database schema.

To run the utility scripts, you need the database administrator credentials. These scripts will prompt you for:

1. DCNM database password (the user name is already present)

2. Username/password of the admin user.

While entering the DBA user credentials, ensure that you do not to enter “sys” as sysdba" because in some versions of Oracle, the presence of space might cause the backup/restore to fail. Instead, user should provide valid user credentials that does not have a space in the user name, for example, system or sysdba. The admin credentials are not saved/cached and hence they do not leak sensitive credential information.

---

Note User scripts under dcnm/bin can be run only by administrator user.

---

Standalone Inline Upgrade for OVA/ISO

This upgrade method, introduced in the 10.4(2) release, is an alternative to the traditional upgrade method. After the inline upgrade, ensure that you clear your browser cache before launching the DCNM application.

Ensure that all the applications are up and running on the Cisco DCNM server by using the appmgr status all command.

Before you begin - Take a backup of the existing files. If an issue arises during the upgrade process, you will need to restore the backup and start the upgrade process afresh.

a. Use the appmgr backup all command to take a backup.

b. Transfer the backup file to an external server.

Step 1 Unzip the dcnm-va.10.4.2.iso.zip file and upload the DCNM 10.4(2) ISO file to the /root/ folder in the DCNM setup that you want to upgrade.

Step 2 Create folder named iso using the mkdir /mnt/iso command.

Step 3 Mount the DCNM 10.4(2) ISO file on the standalone setup in the /mnt/iso folder.

Step 4 Stop the DCNM application using the appmgr stop dcnm command.

Step 5 Navigate to /mnt/iso/packaged-files/scripts/ and run the ./inline-upgrade.sh script.

Note If some services are still running, you will receive a prompt that the services will be stopped. When prompted, press y and continue. An example is provided below.

Step 6 Ensure the DCNM application is functional with the appmgr status dcnm command.

DCNM Native HA Inline Upgrade for OVA/ISO

This upgrade method, introduced in the 10.4(2) release, is an alternative to the traditional Native HA upgrade method. After the inline upgrade, ensure that you clear your browser cache before launching the DCNM application.

Ensure that all the applications are up and running on the Cisco DCNM server active node by using the appmgr status all command. On the DCNM standby node, TFTP applications will not be running, as per expected behavior. You can check using the appmgr status all command.

To verify the role of a DCNM server (as an active or standby node), use the appmgr show ha-role command on both the nodes, as shown in the example.

Before you begin - Take a backup of the existing files. If an issue arises during the upgrade process, you will need to restore the backup and start the upgrade process afresh.

a. Take a backup of DCNM using the appmgr backup all command on the DCNM active and standby nodes.

b. Transfer the two backup files to an external server. For ease of use, name the files for appropriate recall.

Step 1 Unzip the dcnm-va.10.4.2.iso.zip file and upload the DCNM 10.4(2) ISO image to the /root/ folder on the active and standby nodes.

Step 2 Create a folder named iso using the mkdir /mnt/iso command, on the active and standby nodes.

Step 3 Mount the DCNM 10.4(2) ISO image in the /mnt/iso folder, on the active and standby nodes.

Step 4 Stop the DCNM application on the standby and active nodes, in that order, as noted below.

Note It is imperative that you execute the command on the standby node first, and only then on the active node. If not, the upgrade process will fail.

a. On the standby node, use the appmgr stop ha-apps command to stop the DCNM application.

b. On the active node, use the appmgr stop ha-apps command to stop the DCNM application.

Step 5 Verify that the DCNM application is stopped on the active and standby nodes using the appmgr show ha-role command, as show below.

Step 6 On the active node, navigate to /mnt/iso/packaged-files/scripts/ and run the ./inline-upgrade.sh script.

Note If some services are still running, you will receive a prompt that the services will be stopped. When prompted, press y and continue. An example is provided below.

Step 7 After the script is executed, ensure that all the applications (including DCNM) are functional on the active node by using the appmgr status all command.

Step 8 On the standby node, navigate to /mnt/iso/packaged-files/scripts/ and run the ./inline-upgrade.sh script.

Step 9 After the script is executed, ensure that all the applications (including DCNM) are functional on the standby node by using the appmgr status all command.

Note The DCNM and TFTP services will not be running on the standby node, as per expected behavior.