Upgrading Cisco UCS Director to Release 6.8
Overview of the Upgrade to Cisco UCS Director, Release 6.8
The upgrade process to Cisco UCS Director, Release 6.8 depends on the current version of the software that is installed on your system. For information on supported upgrade paths, see Supported Migration Paths to Cisco UCS Director, Release 6.8.
Cisco UCS Director, Release 6.8 is installed on two disks in the virtual machine (VM). One disk hosts the operating system and the Cisco UCS Director application. The second disk hosts the Cisco UCS Director database. SeePrerequisites for Migrating to Cisco UCS Director, Release 6.8.
Note |
While deploying the OVA in a Customize template window, if no default passwords are populated for root and shelladmin, please enter the default password cisco123 for root and changeme for shelladmin. |
Supported Migration Paths to Cisco UCS Director, Release 6.8
The following are the supported migration paths for Cisco UCS Director, Release 6.8.
The following are the supported migrated paths for the Cisco UCS Director Release 6.8:
-
From Release 6.7(4.0) to Release 6.8
-
From Release 6.7(4.1) to Release 6.8
-
From Release 6.7(4.2) to Release 6.8
-
From Release 6.7(4.3) to Release 6.8
Note |
Before migrating from Release 6.7(4.x) to Release 6.8, in progress service requests (SRs) must be in completed state (no in progress service requests) because you cannot complete the service requests after migrating to Release 6.8. |
Supported Migration Paths for Bare Metal Agent Release 6.8
The following are the supported migration paths for the Bare Metal Agent Release 6.8:
-
From Release 6.7(4.0) to Release 6.8
-
From Release 6.7(4.2) to Release 6.8
Supported Migration Paths to Cisco UCS Director, Release 6.8(1.0)
The following are the supported migration paths for Cisco UCS Director, Release 6.8(1.0).
Important |
Cisco UCS Director Release 6.7, Release 6.7(1.0), Release 6.7(2.0), Release 6.7(3.0), and Release 6.7(4.0) are no longer available for download. We recommend that you upgrade immediately to Cisco UCS Director Release 6.8(1.0). For more information, contact the Cisco Support Team. |
Important |
Follow the migration process documented for Cisco UCSD 6.8, for migrating from Cisco UCSD Release 6.7(4.x) to Cisco UCSD 6.8(1.0). |
The following are the supported migrated paths for the Cisco UCS Director Release 6.8(1.0):
-
From Release 6.7(4.0) to Release 6.8(1.0)
-
From Release 6.7(4.1) to Release 6.8(1.0)
-
From Release 6.7(4.2) to Release 6.8(1.0)
-
From Release 6.7(4.3) to Release 6.8(1.0)
Note |
Before migrating from Release 6.7(4.x) to Release 6.8(1.0), in progress service requests (SRs) must be in completed state (no in progress service requests) because you cannot complete the service requests after migrating to Release 6.8(1.0). |
Supported Upgrade Paths to Cisco UCS Director, Release 6.8(1.0)
The following are the supported upgrade paths for Cisco UCS Director, Release 6.8(1.0).
Upgrade Paths from Release 6.8
-
From Release 6.8 to Release 6.8(1.0)
Upgrading from Versions Prior to Release 6.8
If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(1.0). You must first upgrade to Release 6.7(3.0) and Release 6.7(4.0) and then migrate to Release 6.8(1.0).
-
From Release 6.5(0.4) to Release 6.7(3.0) to Release 6.7(4.0)
-
From Release 6.6(2.0) to Release 6.7(3.0) to Release 6.7(4.0)
-
From Release 6.7(3.0) to Release 6.7(4.0)
Important |
Cisco UCS Director Release 6.7, Release 6.7(1.0), Release 6.7(2.0), Release 6.7(3.0), and Release 6.7(4.0) are no longer available for download. We recommend that you upgrade immediately to Cisco UCS Director Release 6.8(1.0). For more information, contact the Cisco Support Team. |
Supported Migration Paths for Bare Metal Agent Release 6.8(1.0)
The following are the supported migration paths for the Bare Metal Agent Release 6.8(1.0):
-
From Release 6.7(4.0) to Release 6.8(1.0)
-
From Release 6.7(4.2) to Release 6.8(1.0)
Supported Upgrade Paths for Bare Metal Agent Patch Release 6.8(1.0)
The following are the supported upgrade paths for the Bare Metal Agent Patch Release 6.8(1.0):
-
From Release 6.8 to Patch Release 6.8(1.0)
Supported Upgrade Paths to Cisco UCS Director, Release 6.8(2.0)
The following are the supported upgrade paths for Cisco UCS Director, Release 6.8(2.0).
Note |
Cisco UCS Director Release 6.8(2.0) includes fixes for security vulnerabilities reported in releases 6.7(4.1), 6.7(4.2), 6.7(4.3), 6.8, and 6.8(1.0). For information on the security vulnerabilities reported in releases 6.7(4.1), 6.7(4.2), 6.7(4.3), 6.8, and 6.8(1.0), see the security advisories for CVE-2021-44228 and and CVE-2021-45046 available at this link: https://tools.cisco.com/security/center/publicationListing.x |
Upgrade Paths from Release 6.8(x.x)
-
From Release 6.8(1.0) to Release 6.8(2.0)
-
From Release 6.8 to Release 6.8(1.0) to Release 6.8(2.0)
Migration from Versions Prior to Release 6.8
If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(2.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x) and then upgrade to Release 6.8(2.0).
Supported Upgrade Paths for Bare Metal Agent Patch Release 6.8(2.0)
The following are the supported upgrade paths for the Bare Metal Agent Patch Release 6.8(2.0):
-
From Release 6.8(1.0) to Patch Release 6.8(2.0)
-
From Release 6.8 to Patch Release 6.8(1.0) to Patch Release 6.8(2.0)
Migration from Versions Prior to Release 6.8
If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(2.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x) and then upgrade to Release 6.8(2.0).
Supported Upgrade Paths to Cisco UCS Director, Release 6.8(3.0)
The following are the supported upgrade paths for Cisco UCS Director, Release 6.8(3.0).
Upgrade Paths from Release 6.8(x.x)
-
From Release 6.8(2.0) to Release 6.8(3.0)
-
From Release 6.8(1.0) to Release 6.8(3.0)
-
From Release 6.8 to Release 6.8(1.0) to Release 6.8(3.0)
Migration from Versions Prior to Release 6.8
If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(3.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x) and then upgrade to Release 6.8(3.0).
Supported Upgrade Paths for Bare Metal Agent Patch Release 6.8(3.0)
The following are the supported upgrade paths for the Bare Metal Agent Patch Release 6.8(3.0):
-
From Release 6.8(2.0) to Release 6.8(3.0)
-
From Release 6.8(1.0) to Patch Release 6.8(3.0)
-
From Release 6.8 to Release 6.8(1.0) to Release 6.8(3.0)
Migration from Versions Prior to Release 6.8
If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(3.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x) and then upgrade to Release 6.8(3.0).
Supported Upgrade Paths to Cisco UCS Director, Release 6.8(4.0)
The following are the supported upgrade paths for Cisco UCS Director, Release 6.8(4.0).
Upgrade Paths from Release 6.8(x.x)
-
From Release 6.8(1.0) to Release 6.8(4.0)
-
From Release 6.8(2.0) to Release 6.8(4.0)
-
From Release 6.8(3.0) to Release 6.8(4.0)
Note |
If you have installed version 6.8, upgrade to Release 6.8(1.0), and then upgrade to Release 6.8(4.0). |
Migration from Versions Prior to Release 6.8
If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(4.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x), and then upgrade to Release 6.8(4.0).
Supported Upgrade Paths for Bare Metal Agent Patch Release 6.8(4.0)
The following are the supported upgrade paths for the Bare Metal Agent Patch Release 6.8(4.0):
-
From Release 6.8(1.0) to Release 6.8(4.0)
-
From Release 6.8(2.0) to Release 6.8(4.0)
-
From Release 6.8(3.0) to Release 6.8(4.0)
Note |
If you have installed version 6.8, upgrade to Release 6.8(1.0), and then upgrade to Release 6.8(4.0). |
Migration from Versions Prior to Release 6.8
If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(4.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x), and then upgrade to Release 6.8(4.0).
Supported Upgrade Paths to Cisco UCS Director, Release 6.8(5.0)
The following are the supported upgrade paths for Cisco UCS Director, Release 6.8(5.0).
Upgrade Paths from Release 6.8(x.x)
-
From Release 6.8(1.0) to Release 6.8(5.0)
-
From Release 6.8(2.0) to Release 6.8(5.0)
-
From Release 6.8(3.0) to Release 6.8(5.0)
-
From Release 6.8(4.0) to Release 6.8(5.0)
Note |
If you have installed version 6.8, upgrade to Release 6.8(1.0), and then upgrade to Release 6.8(5.0). |
Migration from Versions Prior to Release 6.8
If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(5.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x), and then upgrade to Release 6.8(5.0).
Supported Upgrade Paths for Bare Metal Agent Patch Release 6.8(5.0)
The following are the supported upgrade paths for the Bare Metal Agent Patch Release 6.8(5.0):
-
From Release 6.8(1.0) to Release 6.8(5.0)
-
From Release 6.8(2.0) to Release 6.8(5.0)
-
From Release 6.8(3.0) to Release 6.8(5.0)
-
From Release 6.8(4.0) to Release 6.8(5.0)
Note |
If you have installed version 6.8, upgrade to Release 6.8(1.0), and then upgrade to Release 6.8(5.0). |
Migration from Versions Prior to Release 6.8
If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(5.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x), and then upgrade to Release 6.8(5.0).
Supported Upgrade Paths to Cisco UCS Director, Release 6.8(6.0)
The following are the supported upgrade paths for Cisco UCS Director, Release 6.8(6.0).
Upgrade Paths from Release 6.8(x.x)
-
From Release 6.8(1.0) to Release 6.8(6.0)
-
From Release 6.8(2.0) to Release 6.8(6.0)
-
From Release 6.8(3.0) to Release 6.8(6.0)
-
From Release 6.8(4.0) to Release 6.8(6.0)
-
From Release 6.8(5.0) to Release 6.8(6.0)
Note |
If you have installed version 6.8, upgrade to Release 6.8(1.0), and then upgrade to Release 6.8(6.0). |
Migration from Versions Prior to Release 6.8
If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(6.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x), and then upgrade to Release 6.8(6.0).
Supported Upgrade Paths for Bare Metal Agent Patch Release 6.8(6.0)
The following are the supported upgrade paths for the Bare Metal Agent Patch Release 6.8(6.0):
-
From Release 6.8(1.0) to Release 6.8(6.0)
-
From Release 6.8(2.0) to Release 6.8(6.0)
-
From Release 6.8(3.0) to Release 6.8(6.0)
-
From Release 6.8(4.0) to Release 6.8(6.0)
-
From Release 6.8(5.0) to Release 6.8(6.0)
Note |
If you have installed version 6.8, upgrade to Release 6.8(1.0), and then upgrade to Release 6.8(6.0). |
Migration from Versions Prior to Release 6.8
If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(6.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x), and then upgrade to Release 6.8(6.0).
Supported Upgrade Paths to Cisco UCS Director, Release 6.8(7.0)
The following are the supported upgrade paths for Cisco UCS Director, Release 6.8(7.0).
Upgrade Paths from Release 6.8(x.x)
-
From Release 6.8(1.0) to Release 6.8(7.0)
-
From Release 6.8(2.0) to Release 6.8(7.0)
-
From Release 6.8(3.0) to Release 6.8(7.0)
-
From Release 6.8(4.0) to Release 6.8(7.0)
-
From Release 6.8(5.0) to Release 6.8(7.0)
-
From Release 6.8(6.0) to Release 6.8(7.0)
Note |
If you have installed version 6.8, upgrade to Release 6.8(1.0), and then upgrade to Release 6.8(7.0). |
Migration from Versions Prior to Release 6.8
If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(7.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x), and then upgrade to Release 6.8(7.0).
Supported Upgrade Paths for Bare Metal Agent Patch Release 6.8(7.0)
The following are the supported upgrade paths for the Bare Metal Agent Patch Release 6.8(7.0):
-
From Release 6.8(1.0) to Release 6.8(7.0)
-
From Release 6.8(2.0) to Release 6.8(7.0)
-
From Release 6.8(3.0) to Release 6.8(7.0)
-
From Release 6.8(4.0) to Release 6.8(7.0)
-
From Release 6.8(5.0) to Release 6.8(7.0)
-
From Release 6.8(6.0) to Release 6.8(7.0)
Note |
If you have installed version 6.8, upgrade to Release 6.8(1.0), and then upgrade to Release 6.8(7.0). |
Migration from Versions Prior to Release 6.8
If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(7.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x), and then upgrade to Release 6.8(7.0).
Supported Upgrade Paths to Cisco UCS Director, Release 6.8(8.0)
The following are the supported upgrade paths for Cisco UCS Director, Release 6.8(8.0).
Upgrade Paths from Release 6.8(x.x)
-
From Release 6.8(1.0) to Release 6.8(8.0)
-
From Release 6.8(2.0) to Release 6.8(8.0)
-
From Release 6.8(3.0) to Release 6.8(8.0)
-
From Release 6.8(4.0) to Release 6.8(8.0)
-
From Release 6.8(5.0) to Release 6.8(8.0)
-
From Release 6.8(6.0) to Release 6.8(8.0)
-
From Release 6.8(7.0) to Release 6.8(8.0)
Note |
If you have installed version 6.8, upgrade to Release 6.8(1.0), and then upgrade to Release 6.8(8.0). Migration from Versions Prior to Release 6.8 If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(8.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x), and then upgrade to Release 6.8(8.0). |
Supported Upgrade Paths for Bare Metal Agent Patch Release 6.8(8.0)
The following are the supported upgrade paths for the Bare Metal Agent Patch Release 6.8(8.0):
-
From Release 6.8(1.0) to Release 6.8(8.0)
-
From Release 6.8(2.0) to Release 6.8(8.0)
-
From Release 6.8(3.0) to Release 6.8(8.0)
-
From Release 6.8(4.0) to Release 6.8(8.0)
-
From Release 6.8(5.0) to Release 6.8(8.0)
-
From Release 6.8(6.0) to Release 6.8(8.0)
-
From Release 6.8(7.0) to Release 6.8(8.0)
Note |
If you have installed version 6.8, upgrade to Release 6.8(1.0), and then upgrade to Release 6.8(8.0). Migration from Versions Prior to Release 6.8 If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(8.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x), and then upgrade to Release 6.8(8.0). |
Supported Upgrade Paths to Cisco UCS Director, Release 6.8(9.0)
The following are the supported upgrade paths for Cisco UCS Director, Release 6.8(9.0).
Upgrade Paths from Release 6.8(x.x)
-
From Release 6.8(1.0) to Release 6.8(9.0)
-
From Release 6.8(2.0) to Release 6.8(9.0)
-
From Release 6.8(3.0) to Release 6.8(9.0)
-
From Release 6.8(4.0) to Release 6.8(9.0)
-
From Release 6.8(5.0) to Release 6.8(9.0)
-
From Release 6.8(6.0) to Release 6.8(9.0)
-
From Release 6.8(7.0) to Release 6.8(9.0)
-
From Release 6.8(8.0) to Release 6.8(9.0)
Note |
If you have installed version 6.8, upgrade to Release 6.8(1.0), and then upgrade to Release 6.8(9.0). Migration from Versions Prior to Release 6.8 If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(9.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x), and then upgrade to Release 6.8(9.0). |
Supported Upgrade Paths for Bare Metal Agent Patch Release 6.8(9.0)
The following are the supported upgrade paths for the Bare Metal Agent Patch Release 6.8(9.0):
-
From Release 6.8(1.0) to Release 6.8(9.0)
-
From Release 6.8(2.0) to Release 6.8(9.0)
-
From Release 6.8(3.0) to Release 6.8(9.0)
-
From Release 6.8(4.0) to Release 6.8(9.0)
-
From Release 6.8(5.0) to Release 6.8(9.0)
-
From Release 6.8(6.0) to Release 6.8(9.0)
-
From Release 6.8(7.0) to Release 6.8(9.0)
-
From Release 6.8(8.0) to Release 6.8(9.0)
Note |
If you have installed version 6.8, upgrade to Release 6.8(1.0), and then upgrade to Release 6.8(9.0). Migration from Versions Prior to Release 6.8 If you have a version prior to Release 6.8 installed, you cannot upgrade directly to Release 6.8(9.0). You must first migrate to Release 6.8(1.0) from Release 6.7(4.x), and then upgrade to Release 6.8(9.0). |
Digitally Signed Images
Cisco UCS Director images are delivered in digitally signed zip files. These signed zip files are wrapped in a container zip file that includes the following:
-
Digitally signed zip file—Contains the Cisco UCS Director installation image
-
Verification program—Verifies the certificate chain and signature. During certificate chain validation, the program verifies the authenticity of the end-entity certificate using Cisco's SubCA and root CA certificates. Then, the authenticated end-entity certificate is used to verify the signature.
-
Digital signature file—Contains the signature that you can verify before installation.
-
Certificate file—Enables you to verify the digital signature. This Cisco-signed x.509 end-entity certificate contains a public key that can be used to verify the signature. This certificate is chained to the Cisco root posted on http://www.cisco.com/security/pki/certs/crcam2.cer.
-
ReadMe file—Provides the information and instructions required to verify the digitally signed zip file.
Verify the image offline. Once the image is verified, you can begin the installation of Cisco UCS Director.
Note |
For migrating to Release 6.8, you can verify the digital signature of the patch manually and then use the Apply Patch option. See . Verifying a Digitally Signed Image |
Requirements for Verifying Digitally Signed Images
Before you verify a Cisco UCS Director digitally signed image, ensure that you have the following on your local machine:
-
Connectivity to https://www.cisco.com during the verification process
-
Python 3.4.0 or later
-
OpenSSL
Verifying a Digitally Signed Image
Before you begin
Download the Cisco UCS Director image from Cisco.com.
Procedure
Step 1 |
Unzip the file you downloaded from Cisco.com and verify that it contains the following files:
|
||
Step 2 |
Review the instructions in the ReadMe file.
|
||
Step 3 |
Run the signature verification program from the directory where you have unzipped the downloaded content. Example: Signature Verification for VMware OVA Installation
Example: Signature Verification for Hyper-V VHD Installation
|
||
Step 4 |
Review the output and ensure that the verification has succeeded. Example: Expected Output for VMware OVA Installation
Example: Expected Output for Hyper-V VHD Installation
|
What to do next
Install or upgrade Cisco UCS Director.
Migrating to Cisco UCS Director
Prerequisites for Migrating to Cisco UCS Director, Release 6.8
Important |
Follow the migration process documented for Cisco UCSD 6.8, for migrating from Cisco UCSD Release 6.7(4.x) to Cisco UCSD 6.8(1.0). |
Complete the following prerequisites before you upgrade your current Cisco UCS Director software to Release 6.8.
Plan a Maintenance Window
The upgrade to Release 6.8 requires that you stop all Cisco UCS Director services during the upgrade. We recommend that you plan a maintenance window of between 2 and 8 hours. Prior to upgrade, the length of the maintenance window depends on the size of your database. For example, if the infradb size is of 50GB, it would take approximately 5 hours to migrate (includes backup and restore), and if the infradb is 85GB, it would taker approximately 7 hours to migrate (backup and restore).
Note |
Backup and restore depends upon the read and write speed of the disk. |
Download Cisco UCS Director, Release 6.8 and Verify the Signed Image
Download the Cisco UCS Director, Release 6.8 software patch from http://www.cisco.com and then verify the digitally signed image. See Digitally Signed Images.
Verify that the Services and UI are Running
Ensure that the services and UI are up and running in Releases 6.7.4.x and Release 6.8.
If the report indicates any compatibility issues, resolve these issues in your Release 6.8 system after migration. See Upgrading Custom Tasks.
To resolve the incompatibilities, refer to Cisco UCS Director Troubleshooting Guide.
Checking the Disk Size Requirements
Offline Standalone Migration--Backup
Before performing an offline backup Release 6.7.4.x, validate that the root (/) disk size has 6% more than infra-DB size. The following table provides examples of disk size requirements.
Used Infra-DB size (GB) in Release 6.7.4.x |
Free space required in root disk size (GB) in Release 6.7.4.x |
---|---|
20 |
22 |
50 |
53 |
70 |
75 |
90 |
96 |
100 |
106 |
Offline Restore
Before performing an offline restore on UCSD 6.8.0.0, validate that the infra-DB (/infradb) disk size and root (/) disk size in UCSD 6.8.0.0 has 6% more than infra-DB size in UCSD 6.7.4.x. The following table provides examples of disk size requirements.
Used Infra-DB size (GB) in Release 6.7.4.x |
Free space required in Infra-DB disk size (GB) in Release 6.8.0.0 |
Free space required in root disk size (GB) in Release 6.8.0.0 |
---|---|---|
20 |
22 |
22 |
50 |
53 |
53 |
70 |
75 |
75 |
90 |
96 |
96 |
100 |
106 |
106 |
Online Standalone Migration
Before performing online migration on Release 6.8.0.0, validate that the root (/) disk size in UCSD 6.7.4.x has 6% more than infra-DB size in Release 6.7.4.x. It must also be validated that the infra-DB (/infradb) disk size and root (/) disk size in UCSD 6.8.0.0 has 6% more than DB size in Release 6.7.4.x. The following table provides examples of disk size requirements.
Used Infra-DB size (GB) in Release 6.7.4.x |
Free space required in root disk size (GB) in Release 6.7.4.x |
Free space required in Infra-DB disk size (GB) in Release 6.8.0.0 |
Free space required in root disk size (GB) in Release 6.8.0.0 |
---|---|---|---|
20 |
22 |
22 |
22 |
50 |
53 |
53 |
53 |
70 |
75 |
75 |
75 |
90 |
96 |
96 |
96 |
100 |
106 |
106 |
106 |
Offline Dual Node Migration--Offline Backup
Before performing an offline backup on primary node of UCSD 6.7.4.x, validate if the root (/) disk size in primary node of Release 6.7.4.x has 6% more than infra-DB size in DB Node of Release 6.7.4.x. The following table provides examples of disk size requirements.
Used Infra-DB size (GB) in Release 6.7.4.x |
Free space required in root disk size (GB) in Primary Node of Release 6.7.4.x |
---|---|
20 |
22 |
50 |
53 |
70 |
75 |
90 |
96 |
100 |
106 |
Dual Node Offline Restore
Before performing offline restore on primary node of Release 6.8.0.0, validate if the infra-DB (/infradb) disk size in DB node of Release 6.8.0.0 and root (/) disk size in primary node of UCSD 6.8.0.0 has 6% more than infra-DB size in DB Node of Release 6.7.4.x.
Used Infra-DB size (GB) in Release 6.7.4.x |
Free space required in Infra-DB disk size (GB) in Primary Node of Release 6.8.0.0 |
Free space required in root disk size (GB) in in DB Node of Release 6.8.0.0 |
---|---|---|
20 |
22 |
22 |
50 |
53 |
53 |
70 |
75 |
75 |
90 |
96 |
96 |
100 |
106 |
106 |
Online Dual Node Migration
Before performing an online migration on primary node of Release 6.8.0.0, validate if the root (/) disk size in DB and primary node of Release 6.7.4.x has 6% more than infra-DB size in DB node of UCSD 6.7.4.x. Validate that the infra-DB (/infradb) disk size in DB Node of Release 6.8.0.0 and root (/) disk size in primary node of Release 6.8.0.0 has 6% more than infra-DB size in DB node of Release 6.7.4.x.
Used Infra-DB size (GB) in Release 6.7.4.x |
Free space required in root disk size (GB) in DB Node of Release 6.7.4.x |
Free space required in root disk size (GB) in Primary Node of Release 6.7.4.x |
Free space required in Infra-DB disk size (GB) in Primary Node of Release 6.8.0.0 |
Free space required in root disk size (GB) in DB Node of Release 6.8.0.0 |
---|---|---|---|---|
20 |
22 |
22 |
22 |
22 |
50 |
53 |
53 |
53 |
53 |
70 |
75 |
75 |
75 |
75 |
90 |
96 |
96 |
96 |
96 |
100 |
106 |
106 |
106 |
106 |
Expanding the Disk Space
Refer to this link High Primary Disk Utilization to perform the steps for root volume expansion.
Refer to this link High Database Disk Utilization to perform steps to expand the database volume.
Important |
Changes made to vCPU Allocation, Memory Allocation, Memory Reservation in Release 6.7.4.x must be made in Release 6.8 instance also. Any Release 6.7.4.x configuration changes made to InfraMgr Memory Allocation in the /opt/infra/bin/inframgr.env file and MySQL Parameters in the /etc/my.cnf file must be reconfigured in Release 6.8 to achieve the same performance. |
Data Migration
Data Migration script is used to migrate the data from UCSD 6.7.4.x to UCSD 6.8. Migration is supported for both standalone and optimised multi-node.
The supported migration paths are 6.7.4.x (6.7.4.0, 6.7.4.1, 6.7.4.2 and 6.7.4.3 ) to 6.8.0.0.
Data Migration has two options
-
Online Migration : The backup and restore will happen at the same time during online migration from 6.7.4.x to 6.8.0.0. using the command
./performMigration.shNote
In case of optimized multi-node migration, execute command /performmigration.sh in the primary node.
-
Offline Migration : The backup taken from 6.7.4.x, can be copied to any remote location and restored to 6.8.0.0. This can be followed by three steps.
-
Command to copy migration script to 6.7.4.x UCSD from 6.8.0.0 UCSD for taking the backup is ./performMigration.sh offline copyMigrationScript
-
Command to copy to local or remote location and take the backup is ./performMigration.sh offline backup
-
Command to restore the backup taken, from local or remote anytime is ./performMigration.sh offline restore
-
Note |
If any configuration changes for enabling HTTP are made in shelladmin using the Enable/Disable HTTP option in Cisco UCS Director, Release 6.7.4.x, you must enable HTTP again after migrating to Cisco UCS Director, Release 6.8. |
Data Migration Scripts
Following operations are to be followed for Data Migration
-
DB backup from existing UCSD (6.7)
-
Import into UCSD 6.8.0.0
-
Backup and restore Open Automation and Script Modules, report builder
-
Migrate Property Files (Compare and merge old and new values based on key)
-
idaccessmgr/auth.properties
-
inframgr/vmware.properties
-
inframgr/ucsMaxSession.properties
-
idaccessmgr/service.properties
-
web_cloudmgr/apache-tomcat/bin/service.properties
-
controller/service.properties
-
eventmgr/service.properties
-
connectormgr/service.properties
-
networkServices/service.properties
-
usageMgr/service.properties
-
inframgr/service.properties
-
inframgr/apic.properties
-
inframgr/f5lb_tls_version.properties
-
inframgr/ucsCentralInventoryconfigurations.properties
-
inframgr/UcsCentralSessionPoolConfig.properties
-
inframgr/UCSFeatureTimeouts.properties
-
inframgr/ucsMaxSession.properties
-
inframgr/ucsServerAssociationTimeout.properties
-
inframgr/VMWareVNCKeyMap.properties
-
Backup and restore Open Automation and Script Modules, report builder.
-
-
Migrate configuration files
-
/opt/infra/inframgr/networkCollector/deviceprofile/cisco_asa_device.xml
-
/opt/infra/inframgr/networkCollector/deviceprofile/cisco_nexus_device.xml
-
/opt/infra/inframgr/resources/MSC/multisite_config.xml
-
Standalone Node Migration Process
Online Migration-Standalone Node
Steps for Online Migration
Procedure
Step 1 |
Deploy UCSD 6.8.0.0. |
Step 2 |
Login to UCSD 6.8.0.0 as root user. |
Step 3 |
Navigate to the folder /opt/infra/migration and run the migration script using the command ./performMigration.sh |
Step 4 |
Provide IP address and root password for the UCSD 6.7 application It will stop the services in UCSD 6.7.4.x & UCSD 6.8.0.0 application. It will take the DB backup form UCSD 6.7.4.x appliance and restore into UCSD 6.8.0.0 appliance. It will take the application configuration files, reports, open automation, script module from UCSD 6.7.4.X appliance to UCSD 6.8.0.0 appliance. The following information will be displayed
|
Step 5 |
Enter y and press Enter. The following information will be displayed
|
Step 6 |
Enter y and press Enter. The following information will be displayed
|
Step 7 |
Specify the IP address and press Enter.
|
Offline Migration-Standalone Node
Before you begin
Steps for Offline Migration
Procedure
Step 1 |
Deploy UCSD 6.8.0.0.. |
Step 2 |
Login to UCSD 6.8.0.0 as root user. |
Step 3 |
Navigate to the folder /opt/infra/migration and run the migration script using the ./performMigration.sh offline copyMigrationScript |
Step 4 |
Copy migration scripts to UCSD 6.7.4.x using the command. The following information will be displayed
|
Step 5 |
Enter y and press Enter. The following information will be displayed .
|
Step 6 |
Login as root user in UCSD 6.7.4.x appliance. |
Step 7 |
Run the script ./performMigration.sh offline backup from the location /opt/infra/migration. The script will stop the services, take the DB backup, application configuration files, reports, open automation, script module UCSD 6.7.4.x appliance and store in tar.gz format. The script provides an option to copy the backup.tar.gz in UCSD 6.8.0.0 or any remote location by SFTP/SCP/FTP. CLI Information for Offline Backup via SFTP
|
Step 8 |
Enter y and press Enter. The following information will be displayed
|
Step 9 |
Enter y and press Enter. The following information will be displayed
|
Step 10 |
Enter y and press Enter. The following information will be displayed
|
Step 11 |
Login as root user in UCSD 6.8.0.0 appliance. |
Step 12 |
Provide IP address and root password for the UCSD 6.8.0.0 application.
|
Step 13 |
Run the script “./performMigration.sh offline restore” from the location /opt/infra/migration in UCSD 6.8.0.0 pointing to the backup.tar.gz CLI Information for Offline Restore via SFTP
|
Step 14 |
Enter y and press Enter. The following information will be displayed
|
Step 15 |
Enter y and press Enter. The following information will be displayed
|
Step 16 |
Enter n and press Enter. The following information will be displayed
|
Optimized Multi-Node Migration Process
Online Migration-Optimized Multi-Node
Steps for Optimized Multi-Node Online Migration
Procedure
Step 1 |
Deploy optimized multi-node setup from UCSD 6.8.0.0 OVA. |
Step 2 |
Login to Primary Node of UCSD 6.8.0.0 as root user . |
Step 3 |
Navigate to the folder with the following command
|
Step 4 |
Run the script performMigration.sh or ./performMigration.sh |
Step 5 |
Provide IP address and root password for the UCSD 6.7.4.x application It will stop the services in UCSD 6.7.4.x & UCSD 6.8.0.0 application. It will take the DB backup form Database Node in UCSD 6.7.4.x appliance and restore it to the Database Node in UCSD 6.8.0.0 appliance. It will take the application configuration files, reports, open automation, script module from UCSD 6.7.4.x appliance to UCSD 6.8.0.0 appliance. The following information will be displayed
|
Step 6 |
Enter y and press Enter. The following information will be displayed
|
Step 7 |
Enter y and press Enter. The following information will be displayed
|
Step 8 |
Specify the UCSD 6.7.4.x Primary Node IP address, root password and press Enter.
|
Step 9 |
Specify the root password for UCSD 6.7.4.x Database Node and press Enter.
|
Step 10 |
Specify the root password for UCSD 6.8.0.0 Database Node and press Enter.
|
Offline Migration-Optimized Multi-Node
Before you begin
Steps for Offline Migration
Procedure
Step 1 |
Deploy Optimized Multi-Node from UCSD 6.8.0.0. |
Step 2 |
Login to Primary Node of UCSD 6.8.0.0 as root user. |
Step 3 |
Navigate to the folder using the command
|
Step 4 |
Copy migration scripts from Primary Node of UCSD 6.8.0.0 to Primary Node of UCSD 6.7.4.x using the command “./performMigration.sh offline copyMigrationScript”. The following information will be displayed
|
Step 5 |
Login to Primary Node of UCSD 6.7.4.x appliance as root user. |
Step 6 |
Run the script ./performMigration.sh offline backup from the location /opt/infra/migration. The script will stop the services, take the DB backup, application configuration files, reports, open automation, script module UCSD 6.7.4.x appliance and store in tar.gz format. The script provides an option to copy the backup.tar.gz in Primary Node of UCSD 6.8.0.0 or any remote location by SFTP/SCP/FTP options. CLI Information for Offline Backup via SFTP
|
Step 7 |
Enter y and press Enter. The following information will be displayed
|
Step 8 |
Enter y and press Enter. The following information will be displayed
|
Step 9 |
Enter y and press Enter. The following information will be displayed
|
Step 10 |
Enter root password for Database Node and press Enter. The following information will be displayed
|
Step 11 |
Enter y and press Enter. The following information will be displayed
|
Step 12 |
Login to Primary Node of UCSD 6.8.0.0 appliance as root user. |
Step 13 |
Run the script “./performMigration.sh offline restore” from the location /opt/infra/migration in UCSD 6.8.0.0 pointing to the backup.tar.gz CLI Information for Offline Restore via SFTP
|
Step 14 |
Enter y and press Enter. The following information will be displayed
|
Step 15 |
Enter y and press Enter. The following information will be displayed
|
Step 16 |
Enter y and press Enter. The following information will be displayed
|
Upgrading Cisco UCS Director to Release 6.8(1.0)
Prerequisites for Upgrading to Cisco UCS Director, Release 6.8(1.0)
Complete the following prerequisites before you upgrade your current Cisco UCS Director software to Release 6.8(1.0).
Plan a Maintenance Window
The upgrade to Release 6.8(1.0) requires that you stop all Cisco UCS Director services during the upgrade. We recommend that you plan a maintenance window of between 2 and 6 hours. Prior to upgrade, the length of the maintenance window depends on the size of your database
Download Cisco UCS Director, Release 6.8(1.0) and Verify the Signed Image
Download the Cisco UCS Director, Release 6.8(1.0) software patch from http://www.cisco.com and then verify the digitally signed image. See Digitally Signed Images.
Place the Verified Release 6.8(1.0) Software Patch on a Server
Place the Release 6.8(1.0) software patch on the FTP or HTTP server that you plan to use to install the upgrade.
Analyze Your Custom Scripts and Ensure Compatibility
If your existing Cisco UCS Director, Release 6.0(x.x) deployment includes custom tasks, download and run the Custom Task Script Analyzer. The analyzer evaluates all the custom scripts in the Cisco UCS Director database without executing any tasks and then outputs an analysis report on your custom tasks.
If the report indicates any compatibility issues, resolve these issues in your Release 6.0(x.x) system before completing the upgrade. See Upgrading Custom Tasks.
Take a Snapshot of the Current Cisco UCS Director VM
We recommend that you take a snapshot of the current Cisco UCS Director VM before you begin the upgrade. Before you take the VM snapshot, make sure the services and the OS are shutdown gracefully and the VM is in powered off state. If you do this, you do not need to back up the existing configuration database through an FTP server.
Upgrading a Single Node Setup to Release 6.8(1.0)
Procedure
Step 1 |
Log in to the Cisco UCS Director ShellAdmin. |
||
Step 2 |
To upgrade Cisco UCS Director to Release 6.8(1.0), choose Apply Signed Patch. |
||
Step 3 |
At the Services will be stopped before applying patch. Do you want to continue [y/n]?, enter y. When all services are stopped, the upgrade continues. |
||
Step 4 |
At the Do you want to take database backup before applying patch [y/n]? prompt, enter one of the following:
|
||
Step 5 |
At the Specify the Transfer mode prompt, enter one of the following:
|
||
Step 6 |
Wait for the patch file to download to the Cisco UCS Director VM. |
||
Step 7 |
Wait for the patch upgrade to complete. The upgrade process performs extra steps including the following:
Depending upon the size of your database, the upgrade process can take several minutes to complete.
|
||
Step 8 |
When the upgrade is complete, verify that the version and build in the Cisco UCS Director ShellAdmin match the version and build of the patch that you downloaded from Cisco.com. You can find the version and build in the following locations:
|
||
Step 9 |
After upgrading the software, you must delete all zip files and extracted files from the /opt/infra/install folder. Use the Clean-up Patch files option in the Shell Admin console to delete these files. For information on using this Shell Admin option, see Cisco UCS Director Shell Guide. |
Upgrading Optimized Multi-Node Setup
Before you begin
Login to the primary node and from the Shell Admin console, choose Stop Services to halt all services running on the primary node.
Procedure
Step 1 |
Login to the database node. |
Step 2 |
From the Shell Admin console, choose Apply Signed Patch to upgrade the node to Release 6.8(1.0). |
Step 3 |
Login to the primary node, and from the Shell Admin console, choose Apply Signed Patch to upgrade the node to Release 6.8(1.0). |
Step 4 |
Choose Start Services to start all the services on the primary node. |
Upgrading Cisco UCS Director Baremetal Agent
Upgrading Bare Metal Agent to Release 6.8(1.0) from Release 6.8
Before you begin
Upgrade Cisco UCS Director to Release 6.8(1,0).
-
Upgrade Cisco UCS Director to Release 6.8(1,0)
-
Delete the patch folder from the /tmp directory, if available
Procedure
Step 1 |
Download the Bare Metal Agent, Release 6.8(1,0) patch to the existing Bare Metal Agent VM. |
Step 2 |
Log on to the Bare Metal Agent VM using SSH client as 'shelladmin' user. |
Step 3 |
Choose Apply Signed Patch to apply the signed patch. For more information about how to apply signed patch, see the Cisco UCS Director Shell Guide. |
Upgrading Cisco UCS Director PowerShell Agent
Downloading PowerShell Agent from Cisco UCS Director
Download the installer for PowerShell Agent from Cisco UCS Director to your native Windows machine.
Procedure
Step 1 |
Choose . |
Step 2 |
Click PowerShell Agents. |
Step 3 |
Click Download Installer. |
Step 4 |
Review the list of installation requirements on the Download Agent Installer page. Ensure that you have them available on the Windows machine where you plan to install the PowerShell Agent. |
Step 5 |
Click Submit. The PSASetup.exe file is downloaded to your native Windows machine default download folder. |
What to do next
Install Cisco UCS Director PowerShell Agent on your Windows machine.
Installing Cisco UCS Director PowerShell Agent
Note |
If you get the Error 1001 error message while uninstalling the PowerShell agent, delete the PSA registry folders. To delete the PSA registry folders, do the following:
|
Note |
If you do not install the current version of PowerShell Agent for Cisco UCS Director on the Windows machine, some tasks or options on the PowerShell Agents tab are not available. |
Before you begin
-
You need system administrator privileges to complete this task.
-
Enable WinRM.
-
Configure Firewall.
Procedure
Step 1 |
If necessary, copy the PSASetup.exe file that you downloaded from Cisco UCS Director to your target Windows machine. |
Step 2 |
Double-click the PSASetup.exe file. |
Step 3 |
In the Cisco PSA Service - InstallShield Wizard 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 message is displayed. |
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 |
Verify that the Cisco PSA Service is running on the Windows machine by checking the Resource Monitor. |
Upgrading Cisco UCS Director SDKs
Upgrading Cisco UCS Director Open Automation to Release 6.8
The following procedure assumes that you are using an Eclipse development environment. If you use a different development environment for your Open Automation projects, perform the appropriate steps for that environment.
Procedure
Step 1 |
Download the Cisco UCS Director SDK Bundle, Release 6.7 from Cisco.com. |
Step 2 |
Import the project into Eclipse. |
Step 3 |
Execute the examples available to understand the Open Automation execution. The examples are located at com.cisco.cuic.api.examples. |
Upgrading Cisco UCS Director REST API to Release 6.8
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.
Procedure
Step 1 |
Download the Cisco UCS Director SDK Bundle, Release 6.8 from Cisco.com. |
Step 2 |
Import the project into Eclipse. |
Step 3 |
Execute the examples available to understand the REST API execution. You can download the OA zip file from the CCO link, unzip the file, and import the OA examples into eclipse. |
Upgrading Custom Tasks
Custom Task Script Analyzer
The Custom Task Script Analyzer analyses all the classes and methods in the CloupiaScripts that are embedded in a custom task, and provides complete signatures for the methods being used in the CloupiaScript. The analyzer evaluates all the custom scripts in the Cisco UCS Director database without executing any tasks, and then it outputs an analysis report.
The analysis report includes the custom task status (for example, Executed or Not executed), a list of methods used in the custom task, and a list of methods that are not compatible with the methods of the current version. You can use the analysis file to detect potential incompatibilities in the CloupiaScripts before you upgrade.
Configuring the Custom Task Script Analyzer
The Custom Task Script Analyzer is included with Cisco UCS Director as a zipped tar file named script-analyzer.tgz.
Procedure
Step 1 |
Download the script-analyzer.tgz tar file from the Cisco software download area. |
||||
Step 2 |
Copy the script-analyzer.tgz tar file to the /opt directory.
|
||||
Step 3 |
Create a folder (for example, csatool) under the /opt directory. |
||||
Step 4 |
Untar the script-analyzer.tgz tar file into the csatool folder using the following command:
The following files are unpacked into the csatool folder:
|
||||
Step 5 |
Edit the analyzer_config.properties file and configure the following properties:
|
||||
Step 6 |
Save and close the analyzer_config.properties file. |
Analyzing Custom Tasks with the Custom Task Script Analyzer
You can connect to Cisco UCS Director through a terminal and then run the Custom Task Script Analyzer from the terminal. To view the commands that are available to run the Custom Task Script Analyzer, run the following command:
[root@localhost csatool]# ./run-analyzer.sh --help
The following commands are available:
-
fetch-scripts—Fetches scripts from the database. By default, this option is set to True.
-
file—Specify the path of the JavaScript file to be processed.
-
help—Displays the command line menu options.
Procedure
Step 1 |
Open a terminal and connect to Cisco UCS Director. |
||
Step 2 |
To generate an analysis report for all custom tasks, execute the Custom Task Script Analyzer with the --fetch-scripts command as follows:
On execution of this command, you will get:
By default, these folders are created in /opt/csatool/, or whichever path you configured in the analyzer_config.properties file.
|
||
Step 3 |
To generate an analysis report for all JavaScript files in the javascripts folder, execute the Custom Task Script Analyzer with the --file command as follows:
This command generates an analysis report for all JavaScripts in the javascripts folder and saves the analysis report in the output folder as configured in the analyzer_config.properties file. |
||
Step 4 |
To generate an analysis report for a JavaScript file in the javascripts folder, execute the Custom Task Script Analyzer with the --file command as follows:
Where, the Change_VM_Max_Boot_Wait_Time.js is a javascript file in the javascripts folder. This command generates an analysis report for the Change_VM_Max_Boot_Wait_Time.js in the javascripts folder and saves the analysis report in the output folder as configured in the analyzer_config.properties file. |
The analysis report includes the following details:
-
taskLabel—Name of the custom task that was analyzed by the Custom Task Script Analyzer.
-
workflowList—List of workflows in which the custom task is used.
-
status—Executed or Not executed. If any of the workflows in the workflowList was executed at least once, the status is displayed as Executed.
-
usedMethodsList—List of methods that are used in the custom task.
-
incompatibleMethodsList—List of methods that are not compatible with the methods of the current version.
The following is a sample analysis report:
{
"taskLabel": "Change_VM_Max_Boot_Wait_Time",
"workflowList": [
"Provision_VM",
"UpdateVM"
],
"status": NotExecuted,
"usedMethodsList": [
"public static com.cloupia.service.cIM.inframgr.profiles.PrivateCloudSystemProfile com.cloupia.service.cIM.inframgr.InfraPersistenceUtil.getPrivateCloudSystemProfile(java.lang.String) throws java.lang.Exception",
"public int com.cloupia.service.cIM.inframgr.profiles.PrivateCloudSystemProfile.getLinuxVMMaxBootTime()",
"public void com.cloupia.service.cIM.inframgr.profiles.PrivateCloudSystemProfile.setWindowsVMMaxBootTime(int)",
"public static boolean com.cloupia.service.cIM.inframgr.InfraPersistenceUtil.modifyPrivateCloudSystemProfile (com.cloupia.service.cIM.inframgr.profiles.PrivateCloudSystemProfile) throws java.lang.Exception",
"public void com.cloupia.service.cIM.inframgr.profiles.PrivateCloudSystemProfile.setLinuxVMMaxBootTime(int)"
],
"incompatibleMethodsList": [
"public static com.cloupia.service.cIM.inframgr.profiles.PrivateCloudSystemProfile com.cloupia.service.cIM.inframgr.InfraPersistenceUtil.getPrivateCloudSystemProfile(java.lang.String) throws java.lang.Exception",
"public void com.cloupia.service.cIM.inframgr.profiles.PrivateCloudSystemProfile.setWindowsVMMaxBootTime(int)"
]
}
The following is a sample analysis report:
{
"taskLabel" : "ReadFromCSVFile",
"workflowList" : [ ],
"status" : "Notexecuted",
"usedMethods" : [
"public void com.cloupia.service.cIM.inframgr.customactions.CustomActionLogger.addError(java.lang.String)",
"public void com.cloupia.service.cIM.inframgr.customactions.CustomActionTriggerContext.setFailed(java.lang.String)",
"public void com.cloupia.service.cIM.inframgr.customactions.CustomActionLogger.addInfo(java.lang.String)",
"public void com.cloupia.service.cIM.inframgr.customactions.CustomActionTriggerContext.exit()"
],
"incompatibleMethods" : [
"Note:UCSD 6.8 Inframgr running as non-root user - This custom task might not succeed due to the recent security measures to disallow a custom task from performing operations that require root privileges.
For information about operations that require root privileges, please refer to the UCS Director Troubleshooting Guide."
],
"warningMethods" : { },
"fileOperationFlag" : true
},