Chapter 1. Overview

Overview of the Upgrade to Cisco UCS Director, Release 6.0

Supported Upgrade Paths to Cisco UCS Director , Release 6.0

Upgrading a Single Node Setup to Release 6.0

Upgrading a Multi-Node Setup to Release 6.0

Upgrading Bare Metal Agent to Release 6.0

Downloading Cisco UCS Director PowerShell Agent

Installing Cisco UCS Director PowerShell Agent

Upgrading Cisco UCS Director REST API to Release 6.0

Cisco UCS Director Fails with Flex Error 1001: Digest Mismatch with RSL

Cisco UCS Director Upgrade Does Not Respond

Chapter 1. Overview

Cisco UCS Director Upgrade Guide, Release 6.0

First Published: September 16, 2016

Overview of the Upgrade to Cisco UCS Director, Release 6.0

The upgrade process to Release 6.0 depends on the current version of the software that is installed on your system. For information on supported upgrade paths, see Supported Upgrade Paths to Cisco UCS Director , Release 6.0.

If your system is running versions prior to Release 5.4, then you must first migrate to Release 5.4, and then upgrade to Release 5.5. Cisco UCS Director Release 5.4 uses a new version of Java and the CentOS operating system. Due to this, the upgrade procedure for Release 5.4 is different from previous upgrade processes. For more information on how to upgrade your system to Release 5.4, see the Cisco UCS Director Upgrade Guide, Release 5.4, available at:

Click Here

Supported Upgrade Paths to Cisco UCS Director , Release 6.0

The following are the supported upgrade paths for Cisco UCS Director, Release 6.0 .

Upgrade Paths from Release 5.5(x.x) Platform

- From Release 5.5 to Release 6.0

- From Release 5.5(0.1) to Release 6.0

Upgrade Paths from Prior Releases

Note

Direct upgrade to Release 6.0 from versions prior to Release 5.5 is not supported.

- Customers running Release 5.4.x version must first upgrade to Release 5.5 or Release 5.5(0.1), and then upgrade to Release 6.0 version.

- Customers running versions prior than 5.4 version must first migrate to Release 5.4, then upgrade to Release 5.5 or Release 5.5(0.1), and then upgrade to Release 6.0 version.

Upgrading a Single Node Setup to Release 6.0

Follow this procedure to upgrade from Cisco UCS Director, Release 5.5 . If you need to upgrade from a release prior to version 5.4, you must first migrate to release 5.4, followed by an upgrade to Release 5.5. For more information on migrating to Release 5.4, see the Cisco UCS Director Upgrade Guide, Release 5.4 available at: Click Here .

Before You Begin

- Download the Cisco UCS Director, Release 6.0 patch from Click Here .

- Place the software in the FTP or HTTP server that you plan to use to install the upgrade.

Note

We recommend that you take a snapshot of the VM before you begin the upgrade. If you do this, you do not need to back up the existing configuration database through an FTP server.

Procedure

Step 1

Start your current version of Cisco UCS Director, (Release 5.5) .

Step 2

In the ShellAdmin, choose Stop services to stop all services.

Step 3

To verify that all services are stopped, choose Display services status.

Step 4

(Optional)If desired, you can choose Backup database to back up the Cisco UCS Director database.
You do not need to back up the database if you took a snapshot of the VM before you started.

Step 5

To upgrade Cisco UCS Director, Release 6.0, choose Apply patch.

Step 6

When prompted, enter the location of the Release 6.0, patch.
ftp://username:password@hostname|IP_address/software_location_and_name

Step 7

Wait for the download and installation to complete.

Step 8

Re-login to the ShellAdmin, and choose Start services to complete the upgrade process.
Note:
After you apply the upgrade patch and complete that installation, choose the Start Services option of ShellAdmin to start/restart the Cisco UCS Director services and complete the patch process. The patch process is not complete or successful until the Cisco UCS Director services have started, Cisco UCS Director is available, the login screen is displayed, and the administrator can log in to Cisco UCS Director.

All Cisco UCS Director services must be started before you attempt to perform other shelladmin procedures, such as apply additional patches, take a database backup, or restore a database from a backup.

Step 9

When the upgrade is complete, choose Show Version in ShellAdmin to verify the current version of Cisco UCS Director.

Upgrading a Multi-Node Setup to Release 6.0

Perform these steps on the primary node and all service nodes, including the inventory database or monitoring database nodes.

Follow this procedure to upgrade from Cisco UCS Director, Release 5.5. If you need to upgrade from a release prior to version 5.4, you must first migrate to release 5.4, followed by an upgrade to Release 5.5. For more information on migrating to Release 5.4, see the Cisco UCS Director Upgrade Guide, Release 5.4 available at:

Click Here .

Before You Begin

- Download the Cisco UCS Director, Release 6.0 patch from Click Here .

- Place the software in the FTP or HTTP server that you plan to use to install the upgrade.

Note

We recommend that you take a snapshot of the VM before you begin the upgrade. If you do this, you do not need to back up the existing configuration database through an FTP server.

Procedure

Step 1

In the ShellAdmin, choose Stop services to stop all services for the primary and service nodes.

Step 2

To verify that all services are stopped on the primary and services nodes, choose Display services status.

Step 3

In the ShellAdmin, for the inventory database node, and the monitoring database node, choose Apply patch to upgrade the nodes to Release 6.0.

Step 4

When prompted, enter the location of the Release 6.0 patch.
ftp://username:password@hostname|IP_address/software_location_and_name

Step 5

Wait for the download and installation to complete.

Step 6

Using the ShellAdmin, determine that the monitoring database node and Inventory database node is running the database instance.

Step 7

Upgrade the services nodes sequentially using the Apply patch option.

Step 8

Upgrade the primary node using the Apply patch option.

Step 9

Start the services on the service nodes sequentially.
You must wait until all services are running on one service node before moving to another service node.

Step 10

Start the services on the primary node.
Note:
The patch process is not complete or successful until the Cisco UCS Director services have started, Cisco UCS Director is available, the login screen is displayed, and the admin user can log in to Cisco UCS Director.

All Cisco UCS Director services must be started before you attempt to perform other ShellAdmin procedures, such as apply additional patches, take a database backup, or restore a database from a backup.

Step 11

When the upgrade is complete, choose Show Version in ShellAdmin to verify the current version of Cisco UCS Director.

Upgrading Bare Metal Agent to Release 6.0

Before You Begin

- Upgrade Cisco UCS Director to Release 6.0.

If your system is running versions prior to release 5.4, then you must first migrate to Release 5.4, then upgrade to Release 5.5 and then upgrade to Release 6.0. For information on upgrading to release 5.4, see the Cisco UCS Director Release 5.4 Upgrade Guide available at: Click Here

Procedure

Step 1

Download the Bare Metal Agent, Release 6.0 patch to the existing Bare Metal Agent.

Step 2

Log in to the Bare Metal Agent console through PuTTY or another Secure Shell (SSH) client, using the default root credentials shown or the root credentials for your system.

Username: root
Password: pxeboot

Step 3

Navigate to the /opt/infra directory and run StopInfraAll.sh to stop the services.

Step 4

Unzip the patch.

Step 5

Navigate to the directory of the unzipped file.

cd ucsd_bma_patch_6_0_0_0

Step 6

Run ./applyPatch.sh to apply the patch to Bare Metal Agent.

Step 7

Wait for the installation to complete.

Step 8

Navigate to the /opt/infra directory.

Step 9

Run ./showBMAVersion.sh to verify that you have the correct version of Bare Metal Agent.

Step 10

Run startInfraAll.sh to start the BMA services.

Step 11

Run statusInfra.sh to check the status of the BMA services.

Step 12

Log in to Cisco UCS Director, Release 6.0, and choose Administration > Physical Accounts > Bare Metal Agents.

Step 13

Choose the account for the Bare Metal Agent that you have upgraded.
If your system has more than one instance of Bare Metal Agent, you can identify the correct account by the IP address.

Step 14

Confirm that the Bare Metal Agent account is reachable from Cisco UCS Director and then stop and start the services for that account.

Downloading Cisco UCS Director PowerShell Agent

You download the installer for PowerShell Agent from Cisco UCS Director.

Procedure

Step 1

In Cisco UCS Director, choose Administration > Virtual Accounts.

Step 2

Choose the PowerShell Agents tab.

Step 3

Click the Download Installer button.

Step 4

Review the list of installation requirements in the Download Agent Installer dialog box and ensure that you have them available on the target computer where you plan to install Powershell Agent.

Step 5

Click Submit.
The PSASetup.exe file is downloaded to the default download folder on the target computer.

What to Do Next

Install Cisco UCS Director PowerShell Agent on the target computer.

Installing Cisco UCS Director PowerShell Agent

Note

If you do not install the new version of PowerShell Agent for Cisco UCS Director, Release 5.5, the Execute Power Shell Task and the Execute Command options on the PowerShell Agents tab will not work correctly.

Before You Begin

You need system administrator privileges to complete this task.

Procedure

Step 1

If necessary, copy the PSASetup.exe that you downloaded from Cisco UCS Director to your target computer.

Step 2

Double-click the PSASetup.exe file.

Step 3

In the Preparing to Install screen, click Next.

Step 4

In the Ready to install the Program screen, click Install.
The Installing Cisco PSA Service screen displays during the installation. When the installation is complete, the InstallShield Wizard Completed screen displays.

Step 5

Click Finish.
The PowerShell Agent is installed to the C:\Program Files (x86)\Cisco Systems\Cisco PSA Service folder. This folder is referred to as %AGENT_INSTALL_FOLDER% in the remainder of the document.

Step 6

On your computer, choose Start, type services.msc in the text field, and press the Enter key.
A list of current services displays. Verify that the Cisco PSA Service is listed and is currently running.

Upgrading Cisco UCS Director REST API to Release 6.0

The following procedure assumes that you are using an Eclipse development environment. If you use a different development environment for your REST API projects, perform the appropriate steps for that environment.

Before You Begin

The currently installed version on your system should be release 5.5. For more information on upgrading to release 5.5, see the Cisco UCS Director Release 5.5 Upgrade Guide available at:

Click Here

Procedure

Step 1

Download the Cisco UCS Director SDK Bundle, Release 6.0 from Cisco.com.

Step 2

Import the project into Eclipse.

Step 3

Execute the examples available to understand the REST API execution. The examples are located at com.cisco.cuic.api.examples.

Cisco UCS Director Fails with Flex Error 1001: Digest Mismatch with RSL

Problem—After upgrading Cisco UCS Director, access to the GUI sometimes fails with the following error, immediately after logging in:

Flex Error #1001: Digest mismatch with RSL
http://10.5.40.10/app/cloudmgr/cloupia_common.swf. Redeploy the matching RSL or
relink your application with the matching library.

Possible Cause—This can happen after an upgrading the Cisco UCS Director appliance. Exact conditions are currently not known.

Recommended Solution—Cisco recommends the following workarounds:

Procedure

Step 1

Clear the browser cache.

Step 2

Restart the browser (or all open browsers).

Step 3

Use a different browser.

Step 4

Reset the browser as described in the following documents. This erases any previously configured browser settings.

- For Firefox, see Click Here .

- For Internet Explorer, see Click Here .

Cisco UCS Director Upgrade Does Not Respond

Problem—When applying a patch upgrade to the nodes of a Cisco UCS Director single-node or multi-node deployment, the upgrade does not respond.

Possible Cause—This can occur if the time on the nodes is not synchronized.

Recommended Solution—Resync the NTP time and time zone information on each node:

Procedure

Step 1

Stop the upgrade in process.

Step 2

Manually resync the NTP server settings using the Time Sync shell admin option in the standalone (single-node) node, primary node, service node, inventory node, and monitoring node.

Step 3

Restart the upgrade process.