Working in the integrations and service provider space has provided exposure to a wide variety of platforms. Over the past few years we have seen the shift from clients running traditional 3-tier architecture to more adopting a hyper-converged platform. I have worked with a few different hyper-converged platforms but I have always been a huge fan of Cisco UCS, so when the two came together for me it was a perfect match. Being able to provide both hyper-converged and 3-tier in my eyes is a huge plus!
I have been working with Cisco Hyperflex for a while now and I thought its about time I put together an upgrade walk through. The following multi-part post will step through upgrading from Hyperflex 3.0(1d) to 3.5(1a)
As always we need to run through and check compatibility and upgrade paths for the each of the versions of hardware and software we are running. The following tables are referenced from cisco.com.
Hyperflex and VMware Interoperability Matrix
Review the Interoperability Matrix for Hyperflex and VMware and qualify the versions you are running and their upgrade path
HyperFlex Version |
vSphere Versions |
vCenter Versions |
vSphere Editions |
3.5(1a) |
6.0 U3, 6.5 U1, 6.5 U2 |
6.0U3, 6.5U1, 6.5U2, 6.7U1 |
Enterprise, Enterprise Plus, Standard, Essentials Plus |
3.0(1e) |
6.0 U3, 6.5 U1, 6.5 U2 |
6.0U3, 6.5U1, 6.5U2 |
Enterprise, Enterprise Plus, Standard, Essentials Plus |
3.0(1d) |
6.0 U3, 6.5 U1, 6.5 U2 |
6.0U3, 6.5U1, 6.5U2 |
Enterprise, Enterprise Plus, Standard, Essentials Plus |
3.0(1c) |
6.0 U3, 6.5 U1, 6.5 U2 |
6.0U3, 6.5U1, 6.5U2 |
Enterprise, Enterprise Plus, Standard, Essentials Plus |
3.0(1b) |
6.0 U3, 6.5 U1, 6.5 U2 |
6.0U3, 6.5U1, 6.5U2 |
Enterprise, Enterprise Plus, Standard, Essentials Plus |
3.0(1a) |
6.0 U3, 6.5 U1 |
6.0 U3, 6.5 U1 |
Enterprise, Enterprise Plus, Standard, Essentials Plus |
2.6(1e) |
6.0 U1b, 6.0 U2, 6.0 U2 Patch 3, 6.0 U2 Patch 4, 6.0 U3, 6.5 U1 |
6.0U1/U2/U3, 6.5U1 |
Enterprise, Enterprise Plus, Standard, Essentials Plus |
2.6(1d) |
6.0 U1b, 6.0 U2, 6.0 U2 Patch 3, 6.0 U2 Patch 4, 6.0 U3, 6.5 U1 |
6.0U1/U2/U3, 6.5U1 |
Enterprise, Enterprise Plus, Standard, Essentials Plu |
2.6(1b) |
6.0 U1b, 6.0 U2, 6.0 U2 Patch 3, 6.0 U2 Patch 4, 6.0 U3, 6.5 U1 |
6.0U1/U2/U3, 6.5U1 |
Enterprise, Enterprise Plus, Standard, Essentials Plus |
2.6(1a) |
6.0 U1b, 6.0 U2, 6.0 U2 Patch 3, 6.0 U2 Patch 4, 6.0 U3, 6.5 U1 |
6.0U1/U2/U3, 6.5U1 |
Enterprise, Enterprise Plus, Standard, Essentials Plus |
Use of vCenter 6.7U1 is supported only with the ESXi 6.0 and 6.5 versions listed. Support for ESXi 6.7U1 will come in a future release.
Cisco HX Data Platform Matrix
The following table outlines the supported upgrade paths. Here we can confirm upgrading Hyperflex 3.0 to 3.5 is supported.
Cisco HX Data Platform Current Version |
Supported Upgrade Paths Desired version |
|
|
|
|
|
|
|
3.5(x) |
3.0(1x) |
2.6(1x) |
2.5(1x) |
2.1(1x) |
2.0(1x) |
1.8(1x) |
3.0(1x) |
Yes |
— |
— |
— |
— |
— |
— |
2.6(1x) |
Yes |
Yes |
— |
— |
— |
— |
— |
2.5(1x) |
Yes |
Yes |
Yes |
— |
— |
— |
— |
2.1(1x) |
Yes |
Yes |
Yes |
Yes |
— |
— |
— |
2.0(1x) |
— |
Yes |
Yes |
Yes |
Yes |
— |
— |
1.8(1f) |
— |
Yes |
Yes |
Yes |
Yes |
Yes |
— |
1.8(1a) to 1.8(1e) |
— |
— |
Yes |
Yes |
Yes |
Yes |
— |
1.7.x |
— |
— |
— |
— |
Yes |
Yes |
Yes |
Cisco UCS Manager Matrix
Currently with Hyperflex 3.0 the required firmware version is 3.2(3g) so checking below we can confirm that upgrading to 4.0(1a) is supported.
Cisco UCS Manager Current Version |
Supported Upgrade Paths Desired Version |
|
|
|
|
|
|
|
|
|
|
|
4.0(1a) |
3.2(3g) |
3.2(3d) |
3.2(2d) |
3.1(3j) |
3.1(3h) |
3.1(3f) |
3.1(3c) |
3.1(2g) |
3.1(2f) |
3.1(2b) |
3.2(3g) |
Yes |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
3.2(3d) |
Yes |
Yes |
— |
— |
— |
— |
— |
— |
— |
— |
— |
3.2(2d) |
Yes |
Yes |
Yes |
— |
— |
— |
— |
— |
— |
— |
— |
3.1(3j) |
Yes |
Yes |
Yes |
Yes |
— |
— |
— |
— |
— |
— |
— |
3.1(3h) |
Yes |
Yes |
Yes |
Yes |
Yes |
— |
— |
— |
— |
— |
— |
3.1(3f) |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
— |
— |
— |
— |
— |
3.1(3c) |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
— |
— |
— |
— |
3.1(2g) |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
— |
— |
— |
3.1(2f) |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
— |
— |
3.1(2b) |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
— |
VMware ESXi Matrix
Please review the table below to ensure your hosts meet the requirements.
VMware ESXi Current Version |
Supported Upgrade Paths Desired Version |
|
|
|
|
6.5 U1 |
6.0 U3 |
6.0 U2 (All Patch Levels) |
6.0 U1b |
6.0 U3 |
Yes |
— |
— |
— |
6.0 U2 (All Patch Levels) |
Yes |
Yes |
— |
— |
6.0 U1b |
Yes |
Yes |
Yes |
— |
5.5 U3 (Only on HX240c) |
Yes |
Yes |
Yes |
Yes |
Cisco HX Data Platform Versions Supported by Cisco UCS Manager
Review the below table to ensure the nodes you have in use will be supported.
Cisco UCS Manager Version |
Cisco HX Data Platform |
|
|
|
|
|
|
|
|
3.5(x) |
3.0(1x) |
2.6(1x) |
2.5(1x) |
2.1(1x) |
2.0(1x) |
1.8(1x) |
1.7.x |
4.0(1a) |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, M4 and M5 servers |
— |
— |
— |
— |
— |
3.2(3g) |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, M4 and M5 servers |
— |
— |
— |
— |
— |
3.2(3g) |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, M4 and M5 servers |
— |
— |
— |
— |
— |
3.2(3d) |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, M4 and M5 servers |
— |
— |
— |
— |
— |
3.2(2d) |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash and M4 servers |
Yes Supports hybrid, All Flash, and M4 servers |
Yes Supports hybrid, All Flash and M4 servers |
Yes |
— |
3.1(3j) |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, and M4 servers |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes |
— |
3.1(3h) |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, and M4 servers |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes |
— |
3.1(3f) |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, and M4 servers |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes |
— |
3.1(3c) |
Yes Supports hybrid, All Flash, M4 and M5 servers |
Yes Supports hybrid, All Flash, and M4 servers |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes |
— |
3.1(2g) |
— |
— |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes Supports hybrid and All Flash |
Yes |
— |
3.1(2f) |
— |
— |
— |
— |
— |
Yes Supports hybrid and All Flash |
Yes |
— |
3.1(2b) |
— |
— |
— |
— |
— |
Yes Supports hybrid |
Yes |
— |
Pre-Upgrade Validation Checks
- Check that the HyperFlex cluster is healthy and online. Verify all HyperFlex cluster nodes are connected to the vCenter and are online.
- Check that no major Alarms are reported for the HyperFlex cluster in HyperFlex Connect.
- Check that DRS is enabled and set to fully automated.
- Check that vSphere services are running and ESXi Agent Manager (EAM) health is normal.
- Check the health of the cluster in Cisco UCS Manager.
- Cisco recommends using GUI upgrade over CLI for ease of use and better reporting
- During online upgrade, as one node is being upgraded (put into maintenance mode), the number of tolerated node failures is reduced based on the Data Replication Factor and Access Policy settings.
Time to Download the Software
The Hyperflex software can be accessed using the following link
Since we will be performing an upgrade of the existing data platform installer we will need the Upgrade Bundle highlighted below.
I will not be upgrading the ESXi version as I am already at 6.5 Upgrade 2b. I will put together a separate post detailing this process and will list out the steps when required.
If you will be upgrading your hosts during the process please make sure you download the required ESXi Custom Image.
Check the model of fabric interconnect you have as it will determine which UCS Infrastructure Bundle you require. You will need to download the following packages,
- Software for the UCS B-Series blade server products
- Software for the UCS C-Series rack-mounted servers
- The UCS Infrastructure Software Bundle
Uploading the UCS Software to UCS Manager
Next we need to login to UCS Manager
Select the Equipment tab and then click on Firmware Management
Under Firmware Management click on Download Firmware
Click Local File System and Choose File should be selected by default. Select each of the following software bundles one at a time and select Open then click Ok to upload them to UCS Manager.
- Software for the UCS B-Series blade server products
- Software for the UCS C-Series rack-mounted servers
- The UCS Infrastructure Software Bundle
UCS Manager GUI now begins downloading the firmware bundle to the fabric interconnect.
You can monitor the progress on the Download Tasks tab.
Once you have uploaded all 3 firmware bundles you are ready to move to Part 2.