ESX 3.5 U4 - HA Agent error

[davidhaase]

Hi there,

maybe sombody can help me with the following issue in my VI (vCenter 2.5 U4, ESX 3.5 U4 - latest Patches installed)

I have an HA Cluster containing 10 hosts (same hardware, same configuration)

One ESX host (it's always the same server) periodically reports "HA Agent has an error... cmd addnode failed for primary node: Internal AAM Error - agent could not start.". I can fix this using "Reconfigure for HA" via VI-Client. Sometimes I have to try it up to 3 times before the error message is gone. After a short period of time the host reports the same error. Rebooting didn't fix this issue. Any ideas?

Thanks in advance,

David

-- Pedo mellon a minno --

[AndreTheGiant]

The error could appens.

Be sure that name resolution works well and the network is good.

Andre

[LarsLiljeroth]

Hi

I see this alot. When i have had a server in Maintenance mode and bring it into the cluster i see it.

As mentioned. Make sure you network is good. No lost ping..

// Lars Liljeroth

-

---

*If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

[Rockapot]

As Andre said check the network is good and DNS resolution is working fine.

Instead of doing a "Reconfigure for HA" have you tried editing the cluster and removing the HA option. Then once all the hosts have been reconfigured edit the cluster and recheck the HA feature?

Carl

[davidhaase]

Hi *, thanks for your responses.

I can't figure out any network problems - DNS works like a charme.

Yes, I already disabled the HA cluster and enabled it again - but no healing at all.

Currently the host keeps still, but I'm afraid it won't take a long time till I will see the error msg. again.

Any more recommendations? Thx.

David

-- Pedo mellon a minno --

[harunsahiner]

Hi,

I have the same problem.

ESX on the /var/log/vmware/aam/agent directory in the following error messaginig. I researched it but could

not find any solutions.

"FATAL: 0x88e97d8 (09/11/09 14:22:02) Agent already running on this node."

Failed to Modify Rule "VMWareClusterManager": Rule must first be disabled

Error : Rule must first be disabled

[harunsahiner]

Hi,
I've solved this problem. When I use the following link to solve. FYI,

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100371...

:smileyblush: