The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The upgrade path to Cisco UCS Director Express for Big Data Baremetal Agent (Baremetal Agent), Release 5.4 depends upon your current version of Baremetal Agent.
From Release 5.3, you can upgrade directly to Release 5.4.
From Release 5.2, you can upgrade directly to Release 5.4.
From Release 5.0, you can upgrade directly to Release 5.4.
Cisco UCS Director Baremetal Agent (Baremetal Agent), 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 slightly different from previous upgrades. In previous releases, only the Baremetal Agent code was upgraded.
For Release 5.4, you are upgrading the following:
Baremetal Agent, Release 5.3 software and database schema to Release 5.4
Java version 1.6 to version 1.8
CentOS version 5.4 to version 6.6
Note | We recommend assigning your current Release 5.3 IP address to your new Release 5.4 VM, to minimize the impact to your production environment. |
Note | You must have Active Directory on your VM to integrate with LDAP. |
Upgrade Cisco UCS Director to Release 5.4, as described in Upgrading Cisco UCS Director.
Step 1 | In your
hypervisor, take a snapshot of the
Baremetal Agent,
Release 5.x VM.
| ||
Step 2 | Log in to your Baremetal Agent, Release 5.x. appliance. | ||
Step 3 | Stop all services through the Cisco UCS Director UI, or by running the /opt/infra/stopInfraAll.sh script: | ||
Step 4 | If your current
version of
Baremetal Agent
is not supported for upgrade, you must upgrade to one of Release 5.0, Release
5.2, or Release 5.3.
For information about how to upgrade from previous releases of Baremetal Agent, see the installation and upgrade guide for that release. | ||
Step 5 | Enable root access for that VM. | ||
Step 6 | If you want to
use the same IP address for your
Baremetal Agent,
Release 5.4 VM, reconfigure the Release 5.x VM with a temporary IP address.
|
Upgrade Cisco UCS Director to Release 5.4.
Complete the steps in Preparing a Baremetal Agent, Release 5.3 VM for Upgrade.
Step 1 | Download the Baremetal Agent, Release 5.4 software. |
Step 2 | Deploy a VM and
install
Baremetal Agent,
Release 5.4 as described in
Installing Cisco UCS Director Express Baremetal Agent for Big Data
If you want to use the IP address that was assigned to the Release 5.3 VM, /opt/scripts/configStaticIP.sh script to configure the Release 5.4 VM with that IP address. |
Step 3 | Log in to the Release 5.4 VM as root. |
Step 4 | On the Release
5.4 VM, run
/opt/infra/migration/performBMAMigration.sh to
migrate the images, templates, and configuration files from the
Baremetal Agent,
Release 5.3 VM to the Release 5.4 VM.
When prompted, provide the temporary IP address that you assigned to the Release 5.3 VM. |
Step 5 | In
Cisco UCS Director,
Release 5.4, do the following:
|
Step 6 | Log in toCisco UCS Director as an admin and verify that all the images from the Release 5.3 BMA has been migrated successfully |
The migration script cannot anticipate all operating system level customizations that you might have performed on the Baremetal Agent, Release 5.3 VM. You must, therefore, ensure that all customizations are duplicated in your Baremetal Agent, Release 5.4 VM.
Note | All of the following steps are optional. Complete them only if you customized or otherwise changed the defaults for the specified file. If you made any changes to file and folders that are not listed below, ensure that you also copy or merge those files from the Baremetal Agent, Release 5.3 VM to the Release 5.4 VM. |
Complete the steps in Upgrading to Baremetal Agent, Release 5.4.
Step 1 | Copy the following files from the Release 5.3 VM to the Release 5.4 VM: |
Step 2 | Evaluate and merge the following files from the Release 5.3 VM to the same files on the Release 5.4 VM: |
Step 3 | For any Windows
images migrated from the
Baremetal Agent,
Release 5.3 VM, update the
WinPE file with the new IP address of the
Baremetal Agent,
Release 5.4 VM.
You do not need to edit WinPE if the Baremetal Agent IP address was not changed. For more information, see Adding Windows Operating System Images. |