HA:cmd addnode failed for secondary node: /opt/vmware/aam/bin/ft_startup failed to complete within three minutes

[doubin2]

when i enable HA on the cluster,  the error occurs.

"cmd addnode failed for secondary node: /opt/vmware/aam/bin/ft_startup failed to complete within three minutes"

I have searched for a long time, i have tried a lot of methods but don't work for me.

For example : the linke(http://www.virtualizationteam.com/virtualization-vmware/vmware-esxi/esxi-cmd-addnode-failed-for-seco...) does not work for me.

version:

ESX 4.1 update 1

vCenter 4.1 update1

/etc/hosts : include all the hosts's shortname and full domain name and ip in the cluster.

ip/shortname/full domain name: ping OK.

/etc/hosts;/etc/vmware/resolv.con;/etc/sysconfig/network;:the host name is lowcase.

please help me.

thank you.

[FranckRookie]

Hi Doubin,

You can start by reading the following KB and make the recommended checks:

• http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1001596

Good luck!

Regards

Franck

[AndreTheGiant]

IMHO, do not use manually hosts entry... is no needed anymore.

You issue could be typical when you have renamed the nodes or the vCenter, if so, be sure that the node has been rebooted.

Andre

[doubin2]

I didn't try the steps 9/10/14, because those steps is not for my errors information.

Steps 9/10/14:

9.If configured with Advanced Settings, confirm that the configuration is valid. For more information, see Advanced Configuration options for VMware High Availability (1006421).

10.Verify that the correct version of the VirtualCenter agent service is installed. For more information on determining agent versions and how to manually uninstall and reinstall the HA agents on an ESX host, see Verifying and reinstalling the correct version of VMware VirtualCenter Server agent (1003714).

14.Verify that that UDP 8043 packets used for the HA backbone communications are not dropped between the ESX hosts.  For more information see HA fails to configure after task passes 90% "Internal AAM Error - agent could not start" (1018217).

[doubin2]

I remember i didn't midify the host or vcenter name any more. how can i confirm it.

abour the HOSTS file , i just add the hosts and vcenter's shortname and full domain name into it.

[AndreTheGiant]

hosts file now are handle in a correct way.

I suggest to clear them (an error in this file may block HA configuration) and use only DNS Server entries.

Andre