Reconfiguring HA (FDM) on a cluster fails with the error: Operation timed out (2008609) | VMware KB Language :

Reconfiguring HA (FDM) on a cluster fails with the error: Operation timed out (2008609)

 Click here to view full document
  • Cannot reconfigure HA on a cluster
  • Reconfiguring HA on a cluster fails
  • You see the error:

    Operation timed out

  • Removing the ESX host from the cluster and then adding it again to the cluster does not resolve the issue
  • You see this error in the Task Details pane in vCenter Server:

    Status: Operation timed out.

  • You may see these related events:
    • vSphere HA agent on <<Host's Name>> in cluster <<Cluster's Name>> in <<Datacenter's Name>> is disabled
    • The vSphere HA availability state of the host <<Host's Name>> in cluster <<Cluster's Name>> in <<Datacenter's Name>> has changed to Uninitialized
    • The vSphere HA availability state of the host <<Host's Name>> in cluster <<Cluster's Name>> in <<Datacenter's Name>> has changed to Initialization Error
    • vSphere HA agent for host <<Host's Name>> has an error in <<Cluster's Name>> in <<Datacenter's Name>>: vSphere HA agent cannot be correctly installed or configured
The purpose of this article is to resolve Error - operation time out while configuring HA.
This issue occurs if the vSphere High Availability Agent service on the ESXi host is stopped.
To resolve this issue:

  1. Disable HA on the cluster.
  2. Select the host and click the Configuration tab.
  3. Click Security Profile.
  4. Click Properties and check the status of vSphere High Availability.
  5. Start the service if it is stopped.
  6. Enable HA on the cluster. You should now be able to reconfigure HA.

Note: If jumbo frames are configured then make sure you are able to ping the vmkernel with a minimum of 9000 packet size. For more information see,

Data Conversion
3/20/2017 8:00 AM
Santalyne Lyngdoh