Overview
This section provides information related to upgrading a Cisco HyperFlex Stretched Cluster. The procedure for performing a Stretched Cluster upgrade is similar to the regular HyperFlex cluster upgrade procedure.
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.
This section provides information related to upgrading a Cisco HyperFlex Stretched Cluster. The procedure for performing a Stretched Cluster upgrade is similar to the regular HyperFlex cluster upgrade procedure.
Review the Cisco HyperFlex Upgrade Guidelines in the Recommended Cisco HyperFlex HX Data Platform Software Releases - for Cisco HyperFlex HX-Series Systems.
Combined HXDP and UCS FW is not supported.
UCS FW upgrade from HX-Connect is not supported.
Manual cluster bootstrap is required for upgrade from a pre-3.5 release to 3.5(1a).
Auto bootstrap is supported for upgrade from 3.5(1a) to later releases.
HyperFlex Witness node version 1.0.2 is supported from 3.5(1a) or later releases. An upgrade of the HyperFlex Witness node is not required when upgrading stretched clusters to 3.5(1a) or later releases.
Hypercheck Health Check Utility— Cisco recommends running this proactive health check utility on your HyperFlex cluster prior to upgrade. These checks provide early visibility into any areas that may need attention and will help ensure a seamless upgrade experience. For more information see the Hyperflex Health & Pre-Upgrade Check Tool TechNote for full instructions on how to install and run Hypercheck.
HyperFlex Release |
Witness Node Version |
---|---|
3.5(2i) |
1.0.9 |
3.5(2h) |
1.0.8 |
3.5(2g) |
1.0.6 |
3.5(2f) |
1.0.6 |
3.5(2e) |
1.0.4 |
3.5(2d) |
1.0.3 |
3.5(2c) |
Release Deferred |
3.5(2b) |
1.0.3 |
3.5(2a) |
1.0.3 |
3.5(1a) - Unsupported |
1.0.2 |
![]() Note |
Cisco HyperFlex Release 3.5(2f) requires that stretch clusters upgrade the Witness VM to version 1.0.6. For details on how to upgrade the Witness VM, see Upgrading a Witness VM. |
![]() Note |
Older versions of witness VMs are supported when the cluster is upgraded to the latest HXDP version. |
Follow these steps when upgrading a HyperFlex Stretched Cluster from a current Cisco HX Data Platform version of 3.0(1x) or later releases.
![]() Warning |
Do NOT use Cisco HyperFlex Release 3.5(2c) with Stretched Clusters. Please wait for Cisco HyperFlex Release 3.5(2d). For more information, refer to the Software Advisory for CSCvp90129: Stretched cluster nodes that experience failures may become unavailable. |
![]() Note |
If the HyperFlex package update is interrupted due to power failure or reboot of the node that is being upgraded, the controller VM must be re-imaged or manual intervention is required to fix the issue depending on the state of the system. For more details, contact Cisco TAC. |
Complete pre-upgrade validation checks. See for more details.
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 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.
If DRS is Enabled, the VMs are automatically migrated to other hosts with vMotion.
![]() Note |
If DRS is not enabled and the VMs of the node are not migrated with vMotion, all the VMs on the node will be automatically shutdown. For more information, see VMware Documentation for Migration with vMotion. |
Step 1 |
Log in to HX Connect.
|
||||||||||||
Step 2 |
In the Navigation pane, select Upgrade. |
||||||||||||
Step 3 |
On the Select Upgrade Type page, select HX Data Platform and complete the following fields:
|
||||||||||||
Step 4 |
Enter the vCenter credentials.
|
||||||||||||
Step 5 |
Click Upgrade to begin the cluster upgrade process. |
||||||||||||
Step 6 |
The Validation Screen on the Upgrade Progress page displays the progress of the checks performed. Fix validation errors, if any. Confirm that the upgrade is complete. |
Select the Witness VM version that supports the HXDP version you are upgrading to. For supported versions see the HX Data Platform Software Versions for HyperFlex Witness Node for Stretched Cluster section of the Cisco HyperFlex Recommended Software Release and Requirements Guide.
For supported versions see the HX Data Platform Software Versions for HyperFlex Witness Node for Stretched Cluster section of the Cisco HyperFlex Recommended Software Release and Requirements Guide
Upgrade HyperFlex Stretched Cluster.
root@StCtlVM:~# stcli cluster info | grep healthy
Step 1 |
Log in to the witness VM using SSH and execute the following command to stop the service exhibitor.
|
||||||
Step 2 |
Copy the exhibitor.properties file available in the /usr/share/exhibitor/ path to a remote machine from where you can retrieve the exhibitor.properties file.
|
||||||
Step 3 |
Log out from the Witness VM. Power off and rename the Witness VM to WitnessVM.old.
|
||||||
Step 4 |
Deploy a new Witness VM and configure the same IP address as the old Witness VM.
|
||||||
Step 5 |
Log in to the new witness VM using SSH and execute the following command to stop the service exhibitor.
|
||||||
Step 6 |
Copy the exhibitor.properties file from the remote machine (copied in Step 2) to the /usr/share/exhibitor/ path of the new Witness VM.
|
||||||
Step 7 |
Verify if the following symlinks are preserved in the new Witness VM:
If the symlinks are not available, execute the following command:
|
||||||
Step 8 |
Run the /usr/share/springpath/storfs-misc/setexhibitorconfig.sh command to upgrade the Witness exhibitor configuration.
|
||||||
Step 9 |
Start the service exhibitor by executing the following command:
|
Step 1 |
Select one of the hosts and put it in HX maintenance mode using the vSphere Web Client. After the host enters maintenance mode, complete the following steps. |
||
Step 2 |
Copy files using SCP, start the SSH service in the destination ESXi hosts as well.
|
||
Step 3 |
Log in to ESXi, and execute the following command to query the list of available image profiles and for profile name verification.
Example:
|
||
Step 4 |
Run the following command to perform the upgrade.
Example:
|
||
Step 5 |
After the ESXi host comes up, verify that the host has booted up with the correct version.
|
||
Step 6 |
Exit maintenance mode using the vSphere Web Client. |
||
Step 7 |
Ensure that the cluster becomes healthy between each ESXi upgrade.
|
||
Step 8 |
Repeat this process for all hosts in the cluster in a sequence.
|