Overview
This chapter provides information to help you troubleshoot common problems that may occur during the Cisco HyperFlex upgrade process.
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.
This chapter provides information to help you troubleshoot common problems that may occur during the Cisco HyperFlex upgrade process.
Description
If the ESXi host is in lockdown mode, pre-upgrade validation will fail with the error message auth cancel.
Action: Disable Lockdown mode on the ESXi host and enable it after the upgrade is successful.
Using HX Connect
Log in to HX Connect.
On the Navigation pane, select System Overview.
On the System Overview tab, from the Actions drop-down list, you can enable or disable access to the controller VM using SSH as an administrator.
Using vSphere Web Client
Log in to vSphere Web Client.
Browse to the host in the vSphere Web Client inventory.
Click the Manage tab and click Settings.
Under System, select Security Profile.
In the Lockdown Mode panel, click Edit.
Click Lockdown Mode and select one of the Lockdown mode options.
Description
After an offline upgrade, due to a VMware EAM issue, sometimes all the controller VMs do not restart. The stcli start cluster
command returns an error: Node not available
.
Action: Manually power on the controller VMs, then start the storage cluster.
Step 1 |
Manually power on the controller VMs. |
Step 2 |
Restart the storage cluster. |
Description
Sometimes during an online upgrade the vCenter daemon crashes on a node. When this happens, the node cannot enter HX maintenance mode. Without entering HX maintenance mode, the node cannot complete the upgrade. All other nodes, with properly functioning vCenter, complete the upgrade.
Action: Re-run the Upgrade on the Affected Node
Correct the vCenter issue.
Re-run the upgrade on the affected node.
Description:
After a cluster upgrade to HXDP release 3.5, the vCenter Plugin continues to show the Upgrade button.
Action: If you see this issue, perform a vCenter cleanup.
Description
After upgrade of VCSA, cluster reregistration to the upgraded vCenter fails due to the controller IP not populating in vCenter. This is a known issue in a docker VM with multiple NICs where the IP does not populate in VC, causing upgrades to HX which immediately follow a VCSA upgrade, to fail because the IP can not be retrieved.
Action: Open a web console session to the controller VM to trigger it.
There are three suggested steps to workaround this issue. |
Description: Option to upgrade UCS does not appear in HX Connect.
Action: Verify that all backend services are up and running:
Verify that stNodeMgr is running on ESX clusters.
Verify that stMgr is running on ESX clusters.
If any of the services are stopped, start them by running start <service-name>, where <service-name> is stNodeMgr or stMgr or stUpgradeSvc.
Description: Connection to HX Connect lost after pre-upgrade step from HX 3.5(2g) to HX 4.0(2a). During the upgrade, if there is an expired certificate in the upgrade source version, the browser will log user out after pre-upgrade step. This is accepted secure behavior since the certificate of the server has changed after pre-upgrade.
Action: Refresh the browser and login again.