This section provides information related to upgrading a Cisco HyperFlex Edge system.
For upgrading a HyperFlex Edge system, use split upgrade only. Do not use combined upgrade.
Automated ESXi upgrade should be performed via
HX Connect or Intersight. In the event a manual
ESXi upgrade is required, see the procedure Upgrading ESXi.
When upgrading a
HyperFlex Edge system, only HyperFlex Data
Platform can be upgraded from the HX Connect UI.
Do not select the UCS Server firmware option.
Instead, perform the firmware upgrade separately
using the Host Upgrade Utility (HUU) tool or the
Integrated Management Controller (IMC) Supervisor.
On the same controller VM, to enable snapshot schedule, run the command stcli snapshot-schedule -–enable.
Upgrading HyperFlex Edge Using HX Connect from 2.5(1a) or Later Releases
When upgrading a HyperFlex Edge system not managed by Cisco Intersight or prior to a HX release 4.0(2a) use the HX Connect
HX Edge clusters deployed via Intersight do not have upgrade capability from Hyperflex Connect. The upgrade is only supported
For upgrading a HyperFlex Edge system managed using Cisco Intersight or for systems running HX release 4.0(2a), follow the
steps listed here.
Only Cisco HyperFlex Edge clusters that are deployed through Cisco Intersight can be upgraded.
Additionally, upgrade can be initiated only from the Organization to which the HyperFlex Cluster Profile belongs to. For example,
if a cluster is shared between Org A and Org B and the Cluster Profile belongs to Org A, upgrade can be performed only from
All clusters that are selected for the upgrade must be HyperFlex Edge clusters.
Ensure that the cluster is at HyperFlex Data Platform version 4.0(1a) or later.
Upgrading Server Firmware on a Cisco UCS C-Series Server Using the Cisco IMC Supervisor
If you are upgrading to Cisco IMC version 2.0(x), you must change the default Cisco IMC password.
Before upgrading Cisco IMC Supervisor and if a firmware profile was already set up, ensure that the Cisco.com credentials
and proxy details are configured.
Choose Systems > Firmware Management.
On the Firmware Management page, click Firmware Upgrades.
Click Run Upgrade. A warning message appears, advising you that running the upgrade on the selected servers will cause the host to reboot into
the firmware update tool. On completion of the firmware update, the servers will reboot back to the host OS.
Click OK to confirm.
On the Upgrade Firmware screen, complete the following:
Select Profile drop-down list
Choose a profile from the drop-down list.
Click Select and choose the servers from the list. The list displays only those servers whose platforms match the one configured in the
Image Version field
Image Path field
Schedule later check box
Check this check box and select an existing schedule to run an upgrade. You can also click the + icon to create a new schedule.
Post Upgrade Tasks for HyperFlex Edge
After the upgrade is complete and the HyperFlex Edge cluster has been upgraded, log
out and log back in to vCenter to see the upgrade changes.
Confirm that the HX nodes match the expected firmware version.
Check the firmware version in the IMC supervisor GUI to verify for the correct firmware version.
Verify that the datastores are up and are mounted properly on the ESXi host.
From HX controller VMs run the command:
# stcli datastore list
From the ESXi host run:
# esxcfg-nas -l
For each browser interface you use, empty the cache and reload the browser page
to refresh the HX Connect content.
Replace Static Self-signed Certificate with Dynamic Self-signed Certificate
When upgrading your Edge cluster to HyperFlex release 4.0(2a), the static self-signed
certificates on the controller VMs are replaced with dynamically generated
self-signed certificates and VC re-registration takes place during upgrade. However,
if your cluster is upgraded to HX 4.0(2x) via Intersight, the static self-signed
certificates do not get replaced.
To manually replace the static self-signed certificates for dynamic self-signed
certificates perform the following actions:
SSH to the cluster management IP.
Upload the contents from
/etc/springpath/secure/root_file.pub which is used as
the X-RootSessionID in the next step.
Run the following command to generate and install dynamic certificate on all
the controller VMs.