When attempting to configure vCenter High Availability (vCenter HA/VCHA) for a vCenter Server that is part of a VMware Cloud Foundation (VCF) environment, the vCenter HA wizard may fail during validation of the management vCenter or SSO credentials.
Example UI Errors:
Not able to validate management vCenterFailed to add to alien vCenter server - AlienVcDescriptor [ssoDomain=null], url=<redacted>, message: Required argument not passed: passwordAlthough vCenter HA remains a documented vSphere feature, it is not supported for vCenter Server instances that are part of a VCF stack.
VMware Cloud Foundation 9.x
The issue occurs because vCenter HA is being configured against a vCenter Server that is managed by VMware Cloud Foundation. If
vCenter HA is supported as a vSphere feature in applicable standalone/general vSphere environments. For VCF-managed vCenter Server instances, the supported availability model is vSphere HA, not vCenter HA.
Broadcom’s vCenter HA FAQ states that vCenter HA cannot be configured for a vCenter Server that is part of VCF.
vCenter HA FAQ
Do not configure vCenter HA/VCHA for a vCenter Server that is part of a VMware Cloud Foundation environment.
If vCenter HA has already been configured on a VCF-managed vCenter Server, return the vCenter Server to a compliant single-node architecture:
Use vSphere HA at the cluster level to protect the vCenter Server VM.
| Feature | Support status |
|---|---|
| vCenter HA in standalone/general vSphere 9.x environments | Supported where applicable (Stand alone deployments, see VVF) |
| vCenter HA for VCF-managed vCenter Server | Not supported |
| vSphere HA for VCF-managed vCenter Server VM | Supported/recommended |