This section provides information related to upgrading a Cisco HyperFlexStretched Cluster. The procedure for performing a Stretched Cluster upgrade is similar to the regular HyperFlex cluster upgrade procedure.
Upgrade Guidelines for Stretched Cluster
Only split upgrade of the HX Data Platform is supported. Upgrade of UCS firmware 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.
When upgrading to any release from 3.0.x to 3.5.x or later releases:
If you manually bootstrap only one node, the ESXi checkbox will not appear under the Select Upgrade Type section of the Cluster Upgrade page. The ESXi upgrade option appears only after upgrading HX Data Platform to release 3.5.x or later releases.
If you manually bootstrap all the nodes to 3.5.x or later release, the ESXi checkbox will appear under the Select Upgrade Type section of the Cluster Upgrade page. However, you cannot perform an ESXi only upgrade at this point. You can do a combined upgrade of HX Data platform +
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.
HX Data Platform Software Versions for HyperFlex Witness Node
Witness Node Version
Upgrading HyperFlex Stretched Cluster Using HX Connect
Follow these steps when upgrading a HyperFlex Stretched Cluster from a current HX Data Platform version of 3.0(1x) or later releases.
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.
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.
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.
Log in to HX Connect.
Enter the HX Storage Cluster management IP address in a browser. Navigate to https://<storage-cluster-management-ip>.
Enter the administrative username and password.
In the Navigation pane, select Upgrade.
On the Select Upgrade Type page, select HX Data Platform and complete the following fields:
Log out from the Witness VM. Power off and rename the Witness VM to WitnessVM.old.
Confirm that the IP address of the old Witness VM is unreachable, using the ping
Deploy a new Witness VM and configure the same IP address as the old Witness VM.
If the IP address is not reachable, the Witness OVA deployment may contain stale entries in the /var/run/network directory. You must manually remove these entries and reboot the VM to have the assigned IP address become reachable on the
To reboot the VM, open the VM console in vCenter/vSphere and execute the following command:
rm -rf /var/run/network/*
Log in to the new witness VM using SSH and execute the following command to stop the service exhibitor.
root@WitnessVM:~# service exhibitor stop
Copy the exhibitor.properties file from the remote machine (copied in Step 2) to the /usr/share/exhibitor/ path of the new Witness VM.