HA error on one of the hosts in ESX4 cluster. Internal AAM error???

[ranj]

Hi

I have decided to turn HA availability on our ESX4 3 host cluster.

All Hosts are running ESX 4.0.0 294855 and all are identical hardware with same amount of CPU, memory etc.

The first 2 hosts successfully are now part of the HA but the 3rd host attempts to configure HA and then comes up with an error:

"cmd addnode failed for primary node: internal AAM error - agent could not start: unknown HA error"

It seems like it has to install a HA agent on each host but for some reason it doesnt want to install on the last host.

Does anyone know why I might be getting this error. Only today did we patch this host up to be the same version as the rest. I have been doing this gradually over the last few days.

Any assistance would be greatly appreciated.

[jamesreedersmith]

Sounds like a dns/hosts file issue.

Make sure all boxes can see each other.

[apaton]

Hi,

I agree with jamesreedersmith, most HA errors I find are usually down to DNS issues, either not correct, reverse look up is incorrect etc...

If your absolutely sure that DNS is correct, then try disabling HA Cluster then re-enable/reconfigure.

Hope that helps.

Andy