6.0.1

Solution
When a Configure HA task fails, a reason for the failure is reported.
Reason for Failure Action
Host communication
errors
Resolve any communication problems with the host and retry the configuration operation.
Timeout errors Possible causes include that the host crashed during the configuration task, the agent failed to
start after being installed, or the agent was unable to initialize itself after starting up. Verify
that vCenter Server is able to communicate with the host. If so, see “vSphere HA Agent Is in
the Agent Unreachable State,” on page 23 or “vSphere HA Agent is in the Uninitialized State,”
on page 24 for possible solutions.
Lack of resources Free up approximately 75MB of disk space. If the failure is due to insufficient unreserved
memory, free up memory on the host by either relocating virtual machines to another host or
reducing their reservations. In either case, retry the vSphere HA configuration task after
resolving the problem.
Reboot pending If an installation for a 5.0 or later host fails because a reboot is pending, reboot the host and
retry the vSphere HA configuration task.
vSphere HA Agent is in the Uninitialization Error State
The vSphere HA agent on a host is in the Uninitialization Error state. User intervention is required to
resolve this situation.
Problem
vSphere HA reports that an agent is in the Uninitialization Error state when vCenter Server is unable to
unconfigure the agent on the host during the Unconfigure HA task. An agent left in this state can interfere
with the operation of the cluster. For example, the agent on the host might elect itself as master host and
lock a datastore. Locking a datastore prevents the valid cluster master host from managing the virtual
machines with configuration files on that datastore.
Cause
This condition usually indicates that vCenter Server lost the connection to the host while the agent was
being unconfigured.
Solution
Add the host back to vCenter Server (version 5.0 or later). The host can be added as a stand-alone host or
added to any cluster.
vSphere HA Agent is in the Host Failed State
The vSphere HA agent on a host is in the Host Failed state. User intervention is required to resolve the
situation.
Problem
Usually, such reports indicate that a host has actually failed, but failure reports can sometimes be incorrect.
A failed host reduces the available capacity in the cluster and, in the case of an incorrect report, prevents
vSphere HA from protecting the virtual machines running on the host.
Cause
This host state is reported when the vSphere HA master host to which vCenter Server is connected is unable
to communicate with the host and with the heartbeat datastores that are in use for the host. Any storage
failure that makes the datastores inaccessible to hosts can cause this condition if accompanied by a network
failure.
Chapter 3 Troubleshooting Hosts
VMware, Inc. 25