Cisco DCNM Installation and Licensing Guide, Release 6.x
Upgrading Cisco DCNM Servers
Downloads: This chapterpdf (PDF - 158.0KB) The complete bookPDF (PDF - 1.8MB) | Feedback

Table of Contents

Upgrading Cisco DCNM Servers

Information About Cisco DCNM Server Upgrades

Upgrading Cisco DCNM

Upgrading Cisco DCNM Using the Silent Installer

Primary Server Upgrades

Secondary Server Upgrades

Upgrading Cisco DCNM Servers

Upgrading from a Previous Version of Cisco DCNM-SAN

Single-node

Federation

Upgrading from a Previous Version of Cisco DCNM-LAN

Single-node

Cluster

Upgrade using the VSB

Upgrading from a Previous Version of Cisco DCNM-SAN and Cisco DCNM-LAN

Single Node Federation or Cluster

Multiple Nodes Cluster or Federation

Upgrading from DCNM 6.1.x/6.2.x on RHEL 5.4/5.9 to DCNM 6.3.x on RHEL 6.3

Upgrading Cisco DCNM Servers

This chapter describes how to upgrade Cisco Data Center Network Manager (DCNM) on a server system where a previous installation of an earlier Cisco DCNM release is present.

This chapter includes the following sections:

Information About Cisco DCNM Server Upgrades

Y ou can upgrade from a previous version of Cisco DCNM-SAN, Cisco DCNM-LAN, and Cisco DCNM-SAN and DCNM-LAN.


Note Cisco DCNM upgrade is not supported on releases previous to Release 5.2. You must upgrade to Release 5.2.1 and then upgrade to the latest version of Cisco DCNM.


Upgrading Cisco DCNM

BEFORE YOU BEGIN

Ensure the Cisco DCNM version installed is under the following supported upgrade versions:

Cisco DCNM LAN 5.2.1

Cisco DCNM SAN 5.2.1

Cisco DCNM LAN and SAN 5.2.1

Cisco DCNM LAN 5.2.2

Cisco DCNM SAN 5.2.2

Cisco DCNM LAN and SAN 5.2.2

Cisco DCNM LAN 5.2.2a

Cisco DCNM SAN 5.2.2a

Cisco DCNM LAN and SAN 5.2.2a

Cisco DCNM LAN 5.2.2c

Cisco DCNM SAN 5.2.2c

Cisco DCNM LAN and SAN 5.2.2c

  • Check if the Cisco DCNM version on your machine is under the supported upgrade version.
  • Stop all the Cisco DCNM servers.
  • Close all running instances of Cisco DCNM-SAN, Cisco DCNM-LAN, and Device Manager.

DETAILED STEPS

You may change the default credentials after the upgrade is complete.


Step 1 Go to the directory where you downloaded the Cisco DCNM software and run the dcnm-release.exe/dcnm-release.bin file.

After the installer prepares the installation, the Introduction step appears in the Cisco DCNM installer window.

Step 2 Click Next when the Introduction step appears in the Cisco DCNM installer window after the installer prepares the installation.

Step 3 Click Next when the Please Read Before Continuing information appears in the Cisco DCNM installer window.

As part of the Cisco DCNM upgrade, the following options will be displayed according to your system requirements.

  • Upgrade Cisco DCNM-LAN and DCNM-SAN—The installer discovered a previous version of Cisco DCNM-LAN and DCNM-SAN. The installer upgrades to the latest version of Cisco DCNM-LAN and DCNM-SAN and installs the SMI-S agent.
  • Upgrade Cisco DCNM-LAN—The installer discovered a previous version of Cisco DCNM-LAN. The installer upgrades to the latest version of Cisco DCNM-LAN, DCNM-SAN and the SMI-S agent.
  • Upgrade Cisco DCNM-SAN—The installer discovered a previous version of Cisco DCNM-SAN. The installer upgrades to the latest version of Cisco DCNM-SAN, and SMI-S agent. As part of this upgrade process, DCNM-LAN is also installed.
  • Skip installation—The latest version of Cisco DCNM-LAN and DCNM-SAN already exists, so the installer skips the installation.

Click Ok to upgrade.

Step 4 The Database Options step appears in the Cisco DCNM installer window. Use the existing PostgreSQL installation or an existing Oracle installation.


Note Cisco DCNM installation with existing postgres requires an existing schema with the same name as the dcnm username, owned by the same username. When there are no schemas existing with the DCNM username or if you do not have the ownership of the schema with the same dcnmuser name, then the tables get created in the default schema called public.


Step 5 Click Next .

Step 6 In the Configuration Options dialog box, the properties are prepopulated with the values from the earlier Cisco DCNM (DCNM-LAN, DCNM-SAN or DCNM-LAN and DCNM-SAN) installation. If your earlier installation was only a Cisco DCNM-LAN or Cisco DCNM-SAN installation, then during the upgrade process, the other component is installed. For example, if you have an earlier version of Cisco DCNM-LAN, the default port configuration for Cisco DCNM-SAN is displayed. Also, if you had chosen HTTPS for Cisco DCNM-SAN, then after the upgrade, Cisco DCNM-LAN, Cisco DCNM-SAN, and the web client will be HTTPS.

a. From the Server IP Address list, choose the IP address that you want to use for the Cisco DCNM server. The list shows only the IP addresses currently assigned to network interfaces on the server system.

b. If you want to change the port that the Cisco DCNM-LAN web server listens to, enter the new port number in the LAN Web Server Port field. By default, the Cisco DCNM-LAN web server listens to TCP port 8080.

c. If you want to change the port that the Cisco DCNM-SAN web server listens to, enter the new port number in the SAN Web Server Port field. By default, the Cisco DCNM-SAN web server listens to TCP port 80.


Note If you change the web server port number, it affects the URL that Cisco DCNM-LAN users use to download the Cisco DCNM-LAN client.


Table 8-1 displays the HTTPs behavior during a Cisco DCNM upgrade.

Table 8-1 HTTPs Behavior

Existing Cisco DCNM Installation
Current Installation
HTTPs State

5.2.x Cisco DCNM-LAN

Cisco DCNM 6.1.1

Disabled

5.2.x Cisco DCNM-SAN without HTTPS

Cisco DCNM 6.1.1

Disabled

5.2.x Cisco DCNM-SAN with HTTPS

Cisco DCNM 6.1.1

Disabled and Checked

5.2.x Cisco DCNM-LAN+ DCNM-SAN without HTTP

Cisco DCNM 6.1.1

Disabled

5.2.x Cisco DCNM-LAN+ DCNM-SAN with HTTPs

Cisco DCNM 6.1.1

Disabled and Checked

Step 7 If you want to change the port that the Cisco DCNM server accepts Cisco DCNM client connections on, under Advanced Settings, enter the new port number in the Naming Service Port fields for DCNM-LAN and DCNM-SAN.

Step 8 (Optional) For the remaining service ports listed on the Configuration Options step, if you want to specify a different port number, follow these steps in Advanced Settings :

a. For each service port number that you want to change, enter the new port number in the field.

b. Click Resolve Port Conflicts .

If the Cisco DCNM installer detects that a port that you specified is already in use, it automatically assigns an unused port number to the service.

c. Click OK to save the Advanced Settings.

Step 9 Click Next to save the Configuration Options and the IP Multicast Addresses Configuration step appears in the Cisco DCNM installer window.

Step 10 (Optional) If you are installing the primary server for a Cisco DCNM server cluster, follow these steps:

a. In the Partition Name field, enter a unique name for a Cisco DCNM server cluster. The default partition name is the Cisco DCNM host instance ID. The name can contain alphabets and numbers only.

b. (Optional) As needed, change the multicast IP addresses. You may need to change the multicast IP addresses if the addresses provided by the installer are already in use in the routing environment of the Cisco DCNM server cluster.

c. (Optional) As needed, change the multicast ports. You may need to change the multicast ports if the port numbers provided by the installer are already in use on the server system that you are installing Cisco DCNM on.

Step 11 Click Next .

The Choose Archive Folder step appears in the Cisco DCNM installer window.

Step 12 Do one of the following:

    • If you are deploying a clustered-server Cisco DCNM environment, enter or choose the archive folder that you prepared for use by all the servers in the cluster.
    • If you are deploying a single-server Cisco DCNM environment, you can accept the default archive folder or choose the desired archive folder.

Step 13 Click Next .

The Local User Credentials step appears in the Cisco DCNM installer window.

Step 14 In the Local Admin Username field, enter a name for a Cisco DCNM server user. The installer creates the Cisco DCNM server user and assign the Administrator role to it.

Step 15 In the Password field, enter a password for the user, and then in the Confirm Password field, reenter the password.


Note We recommend that you use a strong password. Common guidelines for strong passwords include a minimum password length of eight characters and at least one letter, one number, and one symbol. For example, the password Re1Ax@h0m3 has ten characters and contains uppercase and lowercase letters in addition to one symbol and three numbers.


Step 16 If you want to create a LAN admin user, do the following:

a. Check the Create LAN Admin User check box.

a. In the Local Admin Username field, enter a name for a Cisco DCNM-LAN server user. The installer creates the Cisco DCNM-LAN server user and assign the Administrator role to it.

b. In the Password field, enter a password for the user, and then in the Confirm Password field, reenter the password.

Step 17 If you want to create a SAN admin user, do the following:

a. Check the Create SAN Admin User check box.

a. In the Local Admin Username field, enter a name for a Cisco DCNM-SAN server user. The installer creates the Cisco DCNM-SAN server user and assign the Administrator role to it.

b. In the Password field, enter a password for the user, and then in the Confirm Password field, reenter the password.

Step 18 Click Next .

The Authentication Settings step appears in the Cisco DCNM installer window.

Choose the authentication method that the Cisco DCNM server should use to authenticate users who log into the Cisco DCNM client. You can choose one of the following:

    • Local —Cisco DCNM client users are authenticated by the Cisco DCNM server user accounts only.
    • RADIUS —Cisco DCNM client users are authenticated by a RADIUS server.
    • TACACS+ —Cisco DCNM client users are authenticated by a TACACS+ server.

Step 19 If you chose RADIUS or TACACS+, do the following:

a. In the primary server address field, enter the IPv4 address of the server in dotted-decimal format.

b. In the primary server key field, enter the shared secret of the server.

c. (Optional) If you want to ensure that Cisco DCNM can communicate with the server, click Verify .

d. In the secondary server address field, enter the IPv4 address of the server in dotted-decimal format.

e. In the secondary server key field, enter the shared secret of the server.

f. (Optional) If you want to ensure that Cisco DCNM can communicate with the server, click Verify .

g. In the tertiary server address field, enter the address of the server in the dotted-decimal format.

h. In the tertirary servery key field, enter the shared secret of the server.

i. (Optional) If you want to ensure that Cisco DCNM can communicate with the server, click Verify .

Step 20 Click Next .

The Pre-Installation Summary step appears in the Cisco DCNM installer window.

Step 21 Carefully review the summary of your choices. If you need to change anything, click Previous until the Cisco DCNM installer window displays the step that you need to change, and then return to the applicable preceding step.

Step 22 Click Next when you are ready to install the Cisco DCNM server software.

The installer installs the Cisco DCNM server software.

The Installing Cisco DCNM installer window appears.

Step 23 Choose whether you want to start the Cisco DCNM server now. If you start the Cisco DCNM server now, a splash screen appears while the server starts.

The Install Complete step appears in the Cisco DCNM installer window. The Cisco DCNM instance ID number is displayed.

Step 24 (Optional) If you plan to order licenses for Cisco DCNM, record the Cisco DCNM instance ID number. The licensing process requires that you enter that number.


Note You can begin using Cisco DCNM without a license but some features are not available unless you purchase and install a license and apply the license to managed devices that you want to use licensed features with.


Step 25 Click Done .

Step 26 (Optional) If you want to install a Cisco DCNM license, see Chapter7, “Installing and Managing Licenses for Cisco Data Center Network Manager”


 

Upgrading Cisco DCNM Using the Silent Installer

This section describes how to upgrade the Cisco DCNM server software of a clustered-server environment using the silent installer.

BEFORE YOU BEGIN

Determine the IP address of the secondary server.

Disable antivirus and instruction detection software on the server system. In general, disable any security software or feature that may interfere with the installation of the Cisco DCNM server software. After you complete the installation, reenable the software or features.

DETAILED STEPS


Step 1 From the primary server system, get a copy of the installer.properties file from the following location:

INSTALL_DIR /dcm/dcnm/config

On a Microsoft Windows server system, the default INSTALL_DIR value is C:\Program Files\Cisco Systems. On a RHEL server system, the default INSTALL_DIR value is /usr/local/cisco.

Step 2 Log into server with a user account that has the required privileges, as follows:

    • For Microsoft Windows, the user account must be a member of the local administrators group.
    • For RHEL, the user account must be root.

If you are installing Cisco DCNM on Microsoft Windows and using a remote desktop connection (RDC) to access the Cisco DCNM server system, start RDC from a command prompt and use the /console option, as follows:

C:\>mstsc /console /v:server
 

where server is the DNS name or IP address of the Cisco DCNM server system.

Step 3 Choose a directory and copy the following files to that directory:

    • Copy the installer.properties file that you copied from the primary Cisco DCNM server system.
    • The Cisco DCNM server software that you downloaded.

Step 4 At a command prompt, change directories as needed to ensure that the working directory is the directory that contains the installer.properties file and the Cisco DCNM server software. On Microsoft Windows, use the chdir command without arguments to display the working directory. On RHEL, use the pwd command.

Step 5 Run the applicable command as follows:

    • For Microsoft Windows:
      dcnm-k9. release .exe -i silent -f installer.properties
    • For RHEL:
      sh dcnm-k9. release .bin -i silent -f installer.properties
 

Step 6 Monitor the dcnm_installer.log file to determine the status of the upgrade installation. The Cisco DCNM installer writes the log file to the home directory of the current user account.

Step 7 (Optional) If you want to install a Cisco DCNM license, see Chapter7, “Installing and Managing Licenses for Cisco Data Center Network Manager”


 

Primary Server Upgrades

You perform a primary server upgrade when you upgrade to a newer release of the Cisco DCNM server software for either of the following two purposes:

  • You are upgrading a single-server Cisco DCNM environment.
  • You are upgrading the primary Cisco DCNM server in a clustered or federation environment.

Note All servers in a Cisco DCNM server cluster or federation must run an identical release of Cisco DCNM, such as Cisco DCNM Release 5.2(2c). If you upgrade the primary server, you must upgrade all secondary servers in the cluster or federation.


A primary server upgrades use the Cisco DCNM installer wizard to collect information about how the upgraded Cisco DCNM server should be configured. After you have provided the installer the information that it needs, it upgrades the server software. You can also upgrade the primary server using the silent installer.

A primary server upgrades also create the upgrade-installation.properties file in the INSTALL_DIR /dcm/dcnm/config directory. This file is for use during the upgrade of each secondary server in the server cluster that the primary server belongs to. On a Microsoft Windows server system, the default INSTALL_DIR value is C:\Program Files\Cisco Systems. On a RHEL server system, the default INSTALL_DIR value is /usr/local/cisco. The common property file provided as part of the installer can be used for both fresh and upgrade mode of installations.

Secondary Server Upgrades

You perform a secondary server upgrade when you upgrade secondary Cisco DCNM servers in a clustered or federation server environment. This upgrade can be performed only after you upgrade the primary server in the cluster.

A secondary server upgrade is a silent installation. After you run the installer from a command prompt, the installer does not prompt you for information. Instead, a secondary server upgrade uses the information from the installer.properties file that was created when you upgraded the primary server in the cluster that the secondary server belongs to.

Using the installer.properties file from the primary server ensures that each secondary server is configured identically, as required by Cisco DCNM clustered-server deployments.

Upgrading Cisco DCNM Servers

This section includes the following topics:

Upgrading from a Previous Version of Cisco DCNM-SAN

You can upgrade from an earlier version of Cisco DCNM-SAN using the following options:

Single-node

For information on upgrading a single-node, see the “Upgrading Cisco DCNM” section.

Federation

For information on upgrading a federation server, see the “Upgrading Cisco DCNM” section.

Upgrading from a Previous Version of Cisco DCNM-LAN

You can upgrade from an earlier version of Cisco DCNM-LAN using the following options:

Single-node

For information on upgrading a single-node, see “Upgrading Cisco DCNM” section.

Cluster

For information on upgrading a cluster server, see “Upgrading Cisco DCNM” section.

Upgrade using the VSB

For information on upgrading the DCNM server using the VSB, see the “Installing and Administering Cisco DCNM VSB on a Cisco Nexus 1010 Switch” section.

Upgrading from a Previous Version of Cisco DCNM-SAN and Cisco DCNM-LAN

You can upgrade from an earlier version of Cisco DCNM-LAN or Cisco DCNM-SAN using the following options:

Single Node Federation or Cluster

For information on upgrading a single-node federation or cluster, see the “Upgrading Cisco DCNM” section.


Note If the nodes in the Cisco DCNM federation are in different subnets, do not start the Cisco DCNM-LAN services because Cisco DCNM-LAN does not support nodes in different subnets to point to the same database with the same database user credentials (Cisco DCNM-LAN cluster).


Multiple Nodes Cluster or Federation

For information on upgrading a multiple nodes federation or cluster, see the “Upgrading Cisco DCNM” section.

Upgrading from DCNM 6.1.x/6.2.x on RHEL 5.4/5.9 to DCNM 6.3.x on RHEL 6.3

DETAILED STEPS

Follow the steps to upgrade DCNM 6.1.x/6.2.x on RHEL 5.4/5.9 to DCNM 6.3.x on RHEL 6.3


Step 1 Install DCNM 6.1.x/6.2.x on RHEL 5.4/5.9 with dbuser “user 1” using local postgres or remote postgres, Oracle 10g, Oracle 11g or Oracle RAC.

Step 2 Make a note of the MAC and IP address of the DCNM server.

Step 3 Follow the steps to create the database backup:

    • Local postgres database - Run the backup script locally and collect the database dump.
    • Remote postgres/Oracle/Oracle RAC database - Copy the backup script file available at “dcm/dcnm/bin folder to the remote postgres/oracle server.
    • Oracle 10g/Oracle 11g - Set the ORACLE_SID value in the backup script file to the instance name used while installing the Oracle database.
Example: If the instance name used during the installation was ORCL, then mention ORACLE_SID=ORCL.
    • Oracle RAC - Mention the following backup script for ORACLE_SID

ORACLE_SID=@(description=(address_list=(load_balance=on)(failover=on)(address=(protocol=tcp)(host=10.106.177.89)(port=1521))(address=(protocol=tcp)(host=10.106.177.88)(port=1521))(address=(protocol=tcp)(host=10.106.177.90)(port=1521)))(connect_data=(SERVER=DEDICATED)(service_name=ORCL1)(failover_mode=(type=select)(method=basic

Modify the above script with the Oracle Instance used for installing the Oracle RAC.

Example: If you are using Server 1 to run the backup script file and the Server 1 Oracle instance is ORCL1, the you need to set the ORACLE_SID to the server 1 instance name in the backup script file. ORACLE_SID=ORCL1.
    • Save and Run the backup script file to collect the database dump. You may use one word file name in lower case without any special characters to save the database backup.

Step 4 Take a backup of the rrd files available at dcm/fm/pm/db/

Step 5 If you need reference to old server logs, we recommend that you take a backup of old server logs, as these logs may be lost during migration from old to new RHEL.

Step 6 Re-image the virtual machine or standalone server with RHEL 6.3 or use the MAC ID and IP address you have made a note of in step 2, to configure another virtual machine with RHEL 6.3.

Step 7 Install DCNM 6.1.x or 6.2.x on RHEL 6.3 using the following command:

<dcnm installer bin> Dforce=true

Database User Name - user1

If you are using 64-bit local postgres, then you must specify the DLINUX_OS_BITS

<dcnm installer bin> Dforce=true-DLINK_os_bits=64


Note Move to step 8 without starting the server.


Step 8 Copy the license file manually to the following path /usr/local/cisco/dcm.licenses/ folder.

Step 9 Follow the steps to restore the backup taken in step 3:

    • Local postgres database - Run the restore backup script locally.
    • Remote postgres/Oracle/Oracle RAC database - Copy the restore backup script file available at dcm/dnm/bin folder to the remote postgres/Oracle server.
    • Oracle Database - You must create an Oracle database admin user manually and specify the same in th erestore backupscript as follows:

ORALOGINUSER

ORALOGINPASSWORD


Note By default, user1 is the default parameters for the ORALOGINUSER AND ORALOGINPASSWORD fields.


    • Ensure that the database dump filename is in lower case and run the restore backup script file.

Step 10 Copy the rrd file back to the same directory /dcm/fm/pm/db/.

Step 11 Restart the DCNM servers.

Now the system is ready for the DCNM 6.3.x upgrade.


Note For DCNM versions 6.2.3 or below using Oracle RAC as the underlying database before starting DCNM server, You must navigate to <DCNM install root>/dcm/jboss-4.2.2.GA/server/dcnm/lib and delete the file ojdbc6dms.jar