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.
 Warning |
This chapter contains a list of procedures required by various upgrade workflows. Follow only the procedures that are required for the specific upgrade workflow you intend to use. For step-by-step guidance on online and offline upgrades, refer to the Upgrade Procedures chapter. |
For a successful HyperFlex upgrade, the Cisco HyperFlex System component bundles can be downloaded from the Cisco HyperFlex Download website:
HX Data Platform upgrade bundle (.tgz file)
VMware ESXi Offline Zip bundle
Cisco UCS infrastructure bundle, blade firmware bundle, and rack firmware bundle.
After the Cisco UCS bundles and firmware are downloaded, they need to be copied to Cisco UCS Manager.
To copy UCS software bundles to CIsco UCS Manager
| Step 1 |
Log in to the Cisco UCS Manager GUI. |
||
| Step 2 |
Enter the username and password. |
||
| Step 3 |
In the Navigation pane, click the Equipment tab. |
||
| Step 4 |
On the Equipment tab, click the Equipment node. |
||
| Step 5 |
In the Work pane, click . |
||
| Step 6 |
In the Download Firmware dialog box, click the Local File System radio button in the Location of the Image File field and fill in the required fields. |
||
| Step 7 |
In the Filename field, enter the full path and name of the image file. If you do not know the exact path to the folder where the firmware image file is located, click Browse and navigate to the file. |
||
| Step 8 |
Click OK. The Cisco UCS Manager GUI begins downloading the firmware bundle to the fabric interconnect. |
||
| Step 9 |
Monitor the status of the download on the Download Tasks tab.
|
||
| Step 10 |
Repeat this task until all the required firmware and bundles are downloaded to the fabric interconnect. |
Ensure that the hx-storage-data and vMotion upstream switches are configured for Jumbo Frames. Skipping this step could lead to input/output interruption during Cisco UCS infrastructure upgrade.
| Step 1 |
Put a node in Cisco HX Maintenance mode (see Entering Cisco HyperFlex Maintenance Mode). |
||
| Step 2 |
SSH to the ESXi host in step 1. |
||
| Step 3 |
Verify that the ping is working by pinging the corresponding vmk1 IP interface of another host. If using Jumbo Frames:
If not using Jumbo Frames:
|
||
| Step 4 |
Swap the active interfaces in vswitch-hx-storage-data to force traffic upstream.
|
||
| Step 5 |
Again, verify that the ping is working by pinging the corresponding vmk1 IP interface of another host. If using Jumbo Frames:
If the ping fails, try again with:
If not using Jumbo Frames:
|
||
| Step 6 |
Swap interface back to defaults even if ping fails.
|
||
| Step 7 |
Exit the node from Cisco HX Maintenance mode (see Exiting Cisco HyperFlex Maintenance Mode). |
Warning |
This chapter contains a list of procedures required by various upgrade workflows. Follow only the procedures that are required for the specific upgrade workflow you intend to use. For step-by-step guidance on online and offline upgrades, refer to the Upgrade Procedures chapter. |
| Step 1 |
SSH to any controller VM in the cluster. |
| Step 2 |
Check cluster health |
| Step 3 |
If healthy, shutdown the cluster |
| Step 4 |
Shutdown takes a few minutes, wait for the prompt to return. |
Host Firmware Package is set automatically, during CIsco UCS infrastructure upgrade. To manually stage the correct firmware version before starting the upgrade process use the following procedure.
| Step 1 |
Sign in to Cisco UCS Manager. |
| Step 2 |
In the Navigation pane, click Servers. |
| Step 3 |
Expand . |
| Step 4 |
Expand Host Firmware Packages and choose the policy you want to update. |
| Step 5 |
In the Work pane, click the General tab. |
| Step 6 |
To modify the components in the host firmware package, click Modify Package Versions. |
| Step 7 |
Modify value for Blade Package and Rack Package, to the latest firmware version. See Recommended FI/Server Firmware - 4.0(x) Releases for the list of recommended UCS FI firmware. |
| Step 8 |
In the Excluded Components area, check the boxes corresponding to the components that you want to exclude from this host firmware package. |
| Step 9 |
Click OK. Click yes for all the warnings. |
User acknowledgement of each server is performed automatically during upgrade. Optionally, you can manually acknowledge pending activities on the HyperFlex node.
On the Cisco UCS Manager toolbar, click Pending Activities.
The User Acknowledged Activities tab lists the HyperFlex nodes that require user acknowledgment within the selected sub-org. They are in Pending Reboot status.
 Note |
Do not acknowledge service profiles. |
If you are running HyperFlex release 3.5(1a) or later, you can upgrade the Cisco HX Data Platform by performing the auto-bootstrap process from the HX Connect UI. However, if you are running a HyperFlex release that is earlier than release 3.5(1a) you must run the manual bootstrap process to upgrade the Cisco HX Data Platform as outlined in Manual Bootstrap Upgrade Process.
| Step 1 |
Log in to HX Connect.
|
||
| Step 2 |
In the Navigation pane, select Upgrade. The Select Upgrade Type page appears. 
|
||
| Step 3 |
Upload the new Cisco HX Data Platform upgrade package, specify vCenter credentials, and then click Upgrade. 
|
||
| Step 4 |
Click Confirm in the Initiating Pre-Upgrade message box. The Pre-Upgrade process begins and will be performed on all nodes. 
|
||
| Step 5 |
When the Pre-Upgrade upgrade (management packages upgrade) process is completed, the HX Connect UI prompts you so with an onscreen message. The software will again ask you which component you want to upgrade. Click Upgrade again the complete the HX data platform part of the upgrade.
|
The manual bootstrap process enables you to upgrade the Cisco HX Data Platform and the Cisco HX Data Platform Plug-in.
Note |
Perform this procedure on the node that has the Cluster Management IP address. |
| Step 1 |
From the vSphere Web Client Navigator, select . |
||
| Step 2 |
Navigate to and note the Cluster Management IP address. |
||
| Step 3 |
SSH to the cluster management IP address with root privileges. |
||
| Step 4 |
Transfer the latest HX Data Platform upgrade bundle to the controller VM's /tmp directory. Depending on your operating system, use you can either use SCP directly or download third-party tools, such as WinSCP or MobaXterm. |
||
| Step 5 |
From the controller VM shell, change to the
|
||
| Step 6 |
Un-compress the package using Example:This un-compresses and extracts all files to the root of the |
||
| Step 7 |
Invoke the cluster-bootstrap.sh script to bootstrap packages for upgrade. Execute the command Enter the vCenter FQDN or IP address and administrator level username and password. Wait for the system management service to restart and the bootstrap process to complete. Verify if the HX Data Platform Plug-in is now updated. |
Before you perform maintenance operations on the Cisco HyperFlex (HX) cluster, verify all nodes in the HX cluster are configured for vMotion. Confirm the following from your vSphere Web Client:
Verify that the vMotion port group is configured with vmnic3 and vmnic7 in an active/standby configuration across all of the ESXi hosts in the cluster.
Verify that a port group is configured for vMotion, and that the naming convention is EXACTLY the same across all ESXi hosts in the cluster.
Note |
The name is case-sensitive. |
Verify that you have assigned a static IP to each vMotion port group, and that the static IPs for each vMotion port group are in the same subnet.
Note |
The static IP address is defined as a VMKernel interface. |
Verify that the vMotion port group has the vMotion option checked in the properties, and that no other port groups (such as management) have this option checked, on each ESXi host in the cluster.
Verify in the settings that the vMotion port group is set to 9000 MTU, (if you are using jumbo frames), and the VLAN ID matches the network configuration for the vMotion subnet.
Verify you can ping from the vMotion port group on one ESXi host to the vMotion IP on the other host.
Type vmkping -I vmk2 -d -s 8972 <vMotion IP address of neighboring server>
Note |
Maintenance Mode was introduced in Cisco HyperFlex Release 2.5(1a) and 2.5(1b). |
Log in to Cisco HX Connect: https://<cluster management ip>.
In the menu, click System Information.
Click Nodes, and then click the row of the node you want to put in to maintenance mode.
Click Enter HX Maintenance Mode.
In the Confirm HX Maintenance Mode dialog box, click Enter HX Maintenance Mode.
Note |
After you complete any maintenance tasks, you must manually exit HX maintenance mode. |
Log in to the vSphere web client.
Go to Home > Hosts and Clusters.
Expand the Datacenter that contains the HX Cluster.
Expand the HX Cluster and select the node.
Right-click the node and select Cisco HX Maintenance Mode > Enter HX Maintenance Mode.
Log in to the storage controller cluster command line as a user with root privileges.
Move the node into HX Maintenance Mode.
Identify the node ID and IP address.
# stcli node list --summary
Enter the node into HX Maintenance Mode.
# stcli node maintenanceMode (--id ID | --ip IP Address) --mode enter
(see also stcli node maintenanceMode --help)
Log in to the ESXi command line of this node as a user with root privileges.
Verify that the node has entered HX Maintenance Mode.
# esxcli system maintenanceMode get
You can monitor the progress of the Enter Maintenance Mode task in vSphere Web Client, under the tab.
If the operation fails, an error message displays. Try to fix the underlying problem and attempt to enter maintenance mode again.
Note |
Maintenance Mode was introduced in Cisco HyperFlex Release 2.5(1a) and 2.5(1b). |
Log in to HX Connect: https://<cluster management ip>.
In the menu, click System Information.
Click Nodes, and then click the row of the node you want to remove from maintenance mode.
Click Exit HX Maintenance Mode.
Log in to the vSphere web client.
Go to Home > Hosts and Clusters.
Expand the Datacenter that contains the HX Cluster.
Expand the HX Cluster and select the node.
Right-click the node and select Cisco HX Maintenance Mode > Exit HX Maintenance Mode.
Log in to the storage controller cluster command line as a user with root privileges.
Exit the node out of HX Maintenance Mode.
Identify the node ID and IP address.
# stcli node list --summary
Exit the node out of HX Maintenance Mode.
# stcli node maintenanceMode (--id ID | --ip IP Address) --mode exit
(see also stcli node maintenanceMode --help)
Log in to the ESXi command line of this node as a user with root privileges.
Verify that the node has exited HX Maintenance Mode.
# esxcli system maintenanceMode get
You can monitor the progress of the Exit Maintenance Mode task in vSphere Web Client, under the tab.
If the operation fails, an error message displays. Try to fix the underlying problem and attempt to exit maintenance mode again.
Feedback