An administrator logs into the vSphere client to check the health of a cluster. An alert appears on the cluster stating, "vSphere HA host status". The administrator toggles vSphere HA off and on and…

Question

Options

• AThe vmware-fdm service is disabled on the ESX host.
• BThe vmware-fdm vib is missing from the ESX host.
• CvSphere HA Admission Control settings are not configured correctly.
• DvSphere HA startup policy is not configured correctly.

• A
  9% (4)
• B
  73% (33)
• C
  16% (7)
• D
  2% (1)

Explanation

vSphere High Availability (HA) depends on the FDM agent (Fault Domain Manager) that runs on every ESXi host in the cluster. When an administrator enables HA on a cluster, vCenter automatically installs or updates the vmware-fdm VIB on each participating ESXi host. This VIB contains the HA agent binaries and is mandatory for HA services to start. The error encountered: "A general system error occurred: Failed to start fdm service on host" is a classic and well-documented symptom of a missing or corrupted vmware-fdm VIB. When vSphere HA is toggled off and on, vCenter attempts to reinstall or restart the FDM agent; if the VIB is not present, HA cannot deploy successfully, and the FDM service fails to start.

No community discussion yet for this question.