Switching on HA causes error on 1 host. Internal A...

queensbridgeitt · ‎10-22-2010

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.

piaroa · ‎10-22-2010

You need to check that DNS resolution works well for all hosts to each other and to vCenter and viceversa. Also, I ran into an issue where the / partition (ram disk) got full after a vCenter agent update. The only way to fix the issue was by rebooting the host.

Check this KB: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100864...

You could try uninstalling the vpxa agent from within the host console.

Is this ESXi ?

If this post has been helpful/solved your issue, please mark the thread and award points as you see fit. Thanks!