[VMC on AWS] vSphere HA has gone into an uninitialized state on one or more ESXi hosts
search cancel

[VMC on AWS] vSphere HA has gone into an uninitialized state on one or more ESXi hosts

book

Article ID: 323666

calendar_today

Updated On:

Products

VMware Cloud on AWS VMware Cloud on Dell EMC

Issue/Introduction

To provide the reasoning for why vSphere HA goes into an uninitialized state after a cert refresh and the resolution.

Symptoms:
Customers may see one or more of their ESXi hosts vSphere HA status go into an uninitialized state after a certificate refresh from SHA1 to SHA256.

Cause

As part of the certificate refresh, vCenter will place the host into a disconnected state momentarily. If a host is in a disconnected state longer than expected, the FDM service is restarted, causing vSphere HA to reset on all ESXi hosts in the cluster.

Resolution

In order to re-initialize vSphere HA for the host(s), VMC GS will need to reconfigure vSphere HA for the impacted host(s). To reconfigure vSphere HA, please create an SR with VMC GS (How to file a Support Request in Customer Connect and via Cloud Services Portal (2006985)).
 
When engaging VMC GS, please provide the Host IP that is running into the issue and a screenshot of the alert/issue.
 
Note: Reconfiguring vSphere HA will not impact any workloads or other ESXi hosts within the Cluster/vCenter.

Additional Information

Impact/Risks:
The host that has vSphere HA uninitialized will be unusable until the resolution is performed.