Ensure that the operating systems on all servers have the right driver levels for the release of Cisco UCS to which you plan
to upgrade. See Cisco UCS Driver Installation Guide for identifying the server hardware.
Before you perform firmware updates, use the Cisco UCS Manager image management interfaces to download relevant images to the fabric interconnect. Images are stored in bootflash partition
in the fabric interconnect. See Downloading Software for more details.
An ESXi upgrade is required from ESX 5.5 U3b and ESXi 6.0 U1. Only VMware vSphere versions ESXi 6.0 U1b, 6.0U2, and 6.0U2 patch 3 are supported. For ESXi upgrade, refer Upgrading ESXi.
Keep SSH enabled on all ESXi Hosts.
Enable vMotion so that the VMs can be moved automatically during the upgrade and MTUs are set as Jumbo. See Configuring vMotion Interfaces for details on adding VMkernel interface.
Verify that the cluster is in lenient mode. If not, set the cluster to lenient mode, refer Configure Lenient Mode.
Cautions and Guidelines
Before you begin upgrade of a Cisco HyperFlex System, consider the following cautions, guidelines, and limitations.
Optimizations in Capacity Tier—Backend access is optimized to significantly reduce the magnitude and frequency of high latency
Important Upgrade Guidelines
This upgrade is recommended for only those customers who have been identified having this problem.
For hybrid clusters—The default upgrade process will not enable this optimization. Contact Cisco TAC to enable this performance
enhancement during the upgrade process. Enabling this optimization will require a longer maintenance window.
For All Flash clusters—The upgrade times will not be significantly affected and the default upgrade path will enable this
Upgrade VMware ESXi before starting the upgrade process.
If you have to upgrade from VMware ESXi version 5.5 U3, contact Cisco TAC for assistance.
For a split upgrade, Cisco HX Data Platform must be updated first, before updating the Cisco UCS firmware to avoid no connection error message.
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.
All endpoints in a Cisco HyperFlex domain must be fully functional and all processes must be complete before you begin a firmware upgrade on those endpoints.
For example, the firmware on a server that has not been discovered cannot be upgraded or downgraded. Each endpoint is a component
in the Cisco HyperFlex domain that requires firmware to function.
In a three node cluster, if you shut down one node or put into maintenance mode it makes the cluster unhealthy, but the cluster
is still online. During the upgrade process, put the host in maintenance mode one at a time and move to the next host, after
the cluster becomes healthy.
You cannot remove a node from 3 node cluster by doing stcli node remove operation. To replace a node on a 3 node cluster, please contact Cisco TAC for assistance with the node replacement procedure.
Firefox browser is not supported due to an outdated version of flash that is bundled with the browser. Manual update of flash
within Firefox is possible, but the recommendation is to use either Chrome or Internet Explorer with a modern version of flash.
Pre-Upgrade Validation Checks
HyperFlex Node Upgrade Validations
Perform the following validations on each HyperFlex node before moving on to upgrade the next node in the cluster.
Verify that the HyperFlex cluster is healthy and online. Verify all HyperFlex cluster nodes are connected to the vCenter and are online.
SSH into each controller VM in the HX cluster and make sure that there is space in /var/stv for the upgrade using the command df -h /var/stv.
/dev/sdb1 63G 2.7G 58G 5% /var/stv
If there is not enough space (usage is over 50%), contact Cisco TAC for assistance.
Verify that no major Alarms are reported for the HyperFlex cluster in the vSphere Web Client.
Verify that DRS is enabled and set to fully automated.
Verify that vSphere services are running and ESXi Agent Manager (EAM) health is normal.
Verify the health of the cluster in Cisco UCS Manager.
Viewing HyperFlex Cluster Health
From the vSphere Web Client Navigator, select vCenter Inventory Lists > Cisco HyperFlex Systems > Cisco HX Data Platform > cluster > Summary. View the cluster widget to verify if the HyperFlex cluster is healthy and online.
From the vSphere Web Client Navigator, select vCenter Inventory Lists > Clusters > cluster > Summary. Verify if all HX Cluster nodes are connected to the vCenter and they are online.
Log in to any controller VM in the storage cluster. Run the command stcli cluster storage-summary –-detail.
Sample response that indicates the HyperFlex storage cluster is online and healthy.
uptime: 0 days 12 hours 16 minutes 44 seconds
activeNodes: 5 of 5
current ensemble size:5
# of ssd failures before cluster shuts down:3
minimum cache copies remaining:3
minimum data copies available for some user data:3
minimum metadata copies available for cluster metadata:3
# of unavailable nodes:0
# of nodes failure tolerable for cluster to be available:2
health state reason:storage cluster is healthy.
# of node failures before cluster shuts down:3
# of node failures before cluster goes into readonly:3
# of hdd failures tolerable for cluster to be available:2
# of node failures before cluster goes to enospace warn trying to move the existing data:na
# of hdd failures before cluster shuts down:3
# of hdd failures before cluster goes into readonly:3
# of ssd failures before cluster goes into readonly:na
# of ssd failures tolerable for cluster to be available:2
Storage cluster is healthy.
Verifying If DRS Is Enabled
From the vSphere Web Client Navigator, select vCenter Inventory Lists > Clusters > cluster > Summary.
Verify that DRS is Enabled.
Click the vSphere DRS tab.
Check if Migration Automation Level is set to Fully Automated.
Viewing ESX Agent Manager
From the vSphere Web Client Navigator, select Administration > vCenter Server Extensions > vSphere ESX Agent Manager > Summary.
Verify that vSphere services are running and ESX Agent Manager (EAM) health is normal.
Verify Health of HyperFlex Cluster In Cisco UCS Manager
Verify if the high availability status of the fabric interconnects shows that both the fabric interconnects are up and running.