Problem when adding a ESXi 4.1 server to an existing HA cluster

[da01661]

Dear all,

I have an existing HA cluster working with two ESX 4.0 servers. Both ESX server configured to use its default Service console port for management traffic and i have defined a separated vSwitch with vKernel port specified for vMotion. Now we want to add a newly installed ESXi 4.1 server to the HA cluster, while adding, it prompts error "Cannot complete the configuration of the HA agent on the host. Other HA configuration error". The detail event is "cmd addnode failed for primary node: Internal AAM Error - agent count not start: Unknown HA error"

I have tried to "Reconfigure for VMware HA", but the same outcome.

Do anybody know what cause this problem? Is that related to networking?

Thank you!

[Josh26]

Hi,

Please check your vCenter version - I have a suspicion you are due for an upgrade.

[RHari · Accepted solution]

Hi,

I have faced a similar issue before..

You can try the following

1)     Disable HA and DRS on the cluster first, wait for it to apply on all the hosts,

2)     Make sure that you have Default Gateway set and correct on your new host

3)     Enable HA, then then apply

4)     If that works then enable DRS again.

In case if you are getting the same error – check and update “\etc\hosts” file on esx hosts with ip address of all 3 hosts, example below -

10.1.1.1 ESXHOST1.XXX.COM ESXHOST1

10.1.1.2 ESXHOST2.XXX.COM ESXHOST2

10.1.1.3 ESXHOST1.XXX.COM ESXHOST3

You can test this and let me know -

[11satya]

Hi if got any solution please share with us .

_________________________________
Good luck!

[da01661]

i added the host names into my dns servers and also tried to disable and re-enable the HA cluster

The alert disappears now.

Thank you.

[sharifmahmood]

Pls check the version of vCenter Server u r using to manage existing ESX/ESXi Servers. If it is version 4.0. then u will not be able to add ESXi 4.1 host in your existing HA cluster. you need to upgrade your vCenter server first.

[da01661]

i'm using vCenter 4.1.0.

Thanks for your advice.