Recommended Upgrade Method
For both combined upgrade and split upgrade, Cisco recommends upgrading the HyperFlex components in the following order for optimizing the upgrade time:
Upgrade Cisco UCS Infrastructure
Upgrade Cisco HX Data Platform
Upgrade Cisco customized VMware ESXi
Upgrade Cisco UCS firmware
Upgrading Cisco HX Data Platform
Before you begin
Complete pre-upgrade validation checks.
Download the latest Cisco HX Data Platform Upgrade Bundle for upgrading existing clusters from previous releases from Software Download .
Complete steps 1 to 6 in the Online Upgrade Process Work flow. See Online Upgrade Process Workflow for more details.
Upgrade Cisco UCS Infrastructure.
Bootstrap to upgrade Cisco HX Data Platform plug-in.
Disable snapshot schedule, on the bootstrapped storage controller VM.
Log in to the Cisco HX Data Platform plug-in with administrator credentials.
If DRS is Enabled, the VMs are automatically vMotioned to other hosts.
If DRS is Disabled, vMotion the VMs manually to continue the upgrade process. For more information, see VMware Documentation for Migration with vMotion.
From the vSphere Web Client Navigator, select vCenter Inventory Lists > Cisco HyperFlex Systems > Cisco HX Data Platform > HX-Cluster > Summary.
Select Upgrade Cluster.
Select only HX Data Platform.
Navigate to the .tgz package file on your local PC.
Upload the Cisco HX Data Platform upgrade bundle. This is the same .tgz package file that was used to upgrade the HX Data Platform Plug-in.
Enter administrator level vCenter credentials.
The Validation screen shows the progress of checks performed. Fix validation errors, if any.
The upgrade process proceeds as follows:
During cluster upgrade, if the orchestration node reboots or power cycles due to power issue, the cluster upgrade will be stuck. Once the node is up, restart the cluster upgrade process after cleaning the cluster system using the following command:
If the clean-up command fails, restart the stMgr service on all control VMs (ctrlVM) by running the following command:
Then, clean the cluster system by rerunning the following command:
Here is a sample code: