Upgrading Multi-Node Setup to Release 6.7

Upgrading Your Multi-Node Setup

Following is a summary of the process that you must follow to upgrade your current multi-node setup to the optimized multi-node setup introduced in Release 6.7:

  1. We recommend that you take snapshots of the VMs in the primary node, the inventory database node and monitoring database node.

  2. Stop all services on the primary and service nodes.

  3. Ensure that disk-1 has sufficient space in both database nodes for migrating data from the inventory database node. If there is not enough disk space, use the Clean-up patch files option in the Shell Admin console to create disk space in disk-1.

  4. Upgrade the monitoring database node to the current version of Cisco UCS Director and run the database migration script.

    For more information, see Upgrading the Monitoring Node to Release 6.7

  5. Upgrade the primary node to the Cisco UCS Director release 6.7.

    For more information, see Upgrading the Primary Node

  6. Power off the inventory database node and the service nodes.


Note

The time taken to upgrade your current multi-node configuration to the optimized multi-node configuration depends on the database size.

Upgrading the Monitoring Node to Release 6.7

When you upgrade the current monitoring node to release 6.7, the inventory and monitoring databases are merged, and the monitoring database node is converted to the new database node.

Before you begin

  1. We recommend that you take snapshots of the VMs in the primary node, the inventory database node and monitoring database node.

  2. Enable root access on the monitoring database node and the inventory database node.

  3. Ensure that the available disk size on the monitoring database node is equal to or more than the combined disk size of the inventory database node and monitoring database node.

Procedure

Step 1

Login to the monitoring database node.
Step 2

From the Shell Admin console, choose Apply Signed Patch to upgrade the node to Release 6.7.

Step 3

At the Do you want to take database backup before applying patch [y/n]? prompt, enter one of the following:

  • y to back up the Cisco UCS Director database.
  • n if you took a snapshot of the VM before you started.
Step 4

At the Specify the Transfer mode prompt, enter one of the following:

  • HTTP—Enter the URL for the location where you stored the upgrade file.
  • SFTP—Enter the SFTP server IP address, server login name and password, and the path to the location where you have stored the upgrade file.
  • SCP—Enter the SCP server IP address, server login name and password, and the path to the location where you have stored the upgrade file.
  • FILE—Enter the path to the local directory where you have stored the upgrade file.
  • FTP—Enter the FTP server IP address, server login name and password, and the path to the location where you have stored the upgrade file. For example, if you stored the patch file on an FTP server, enter ftp://username:password@hostname|IP_address/software_location_and_name
Step 5

When prompted for the Patch URL, type the location of the Release 6.7 patch and press Enter

For example, if you stored the software patch on an FTP server, enter ftp://username:password@hostname|IP_address/software_location_and_name

Step 6

Wait for the patch to download to the Cisco UCS Director VM.

Step 7

Wait for the patch upgrade to complete.

The upgrade process performs many steps including the following:

  • Unpacks the patch file.

  • Installs the Release 6.7 files

  • Initializes the database schema.

  • Reboots the Cisco UCS Director appliance. The Cisco UCS Director services start automatically.

Depending upon the size of the database, the upgrade process can take several minutes to complete.
Step 8

Log in as root.
Step 9

Navigate to the migration folder with the following command:

cd /opt/scalability/migration
Step 10

Run the upgradeMultiNodeDB.sh script.

Step 11

When prompted, enter y to confirm that you have taken a snapshot of the existing multi-node setup

Step 12

When prompted, enter y to confirm converting the monitoring database node to the database node.

Step 13

When prompted, enter the IP address of the inventory database node.
Step 14

When prompted, enter the root password for the inventory database node.

At this point, the process to migrate data from the inventory database node to the monitoring database node and to convert the monitoring database node into the database node is initiated.

Step 15

Wait for the upgradeMultiNodeDB.sh script to execute completely.

After the script executes completely, do not power off the inventory database node. This node must be powered on and running to upgrade the primary node successfully.

What to do next

Upgrade the primary node.

Upgrading the Primary Node

Before you begin

  • Take a snapshot of the VM in the primary node.

  • Upgrade the monitoring database node. See Upgrading the Monitoring Node to Release 6.7.

  • Ensure that the monitoring database node and the inventory database node is powered on.

Procedure

Step 1

Login to the primary node.

Step 2

From the Shell Admin console, choose Apply Signed Patch to upgrade the node to Release 6.7.

Step 3

When prompted, enter y to stop the services on the primary node.
Step 4

At the Do you want to take database backup before applying patch [y/n]? prompt, enter one of the following:

  • y to back up the Cisco UCS Director database.
  • n if you took a snapshot of the VM before you started.
Step 5

At the Specify the Transfer mode prompt, enter one of the following:

  • HTTP—Enter the URL for the location where you stored the upgrade file.
  • SFTP—Enter the SFTP server IP address, server login name and password, and the path to the location where you have stored the upgrade file.
  • SCP—Enter the SCP server IP address, server login name and password, and the path to the location where you have stored the upgrade file.
  • FILE—Enter the path to the local directory where you have stored the upgrade file.
  • FTP—Enter the FTP server IP address, server login name and password, and the path to the location where you have stored the upgrade file. For example, if you stored the patch file on an FTP server, enter ftp://username:password@hostname|IP_address/software_location_and_name
Step 6

When prompted for the Patch URL, type the location of the Release 6.7 patch and press Enter

For example, if you stored the software patch on an FTP server, enter ftp://username:password@hostname|IP_address/software_location_and_name

Step 7

Wait for the patch to download to the Cisco UCS Director VM.

Step 8

Wait for the patch upgrade to complete.

The upgrade process includes the following steps:

  • Unpacks the patch file.

  • Verifies that the database node upgrade is complete. If the database node upgrade is incomplete, the upgrade process is cancelled.

  • Installs the Release 6.7 files

  • Upgrades the primary node.

  • Initializes the database schema.

  • Reboots the Cisco UCS Director appliance. The Cisco UCS Director services start automatically.