Ha error

[tdubb123]

i have a 3 node cluster

1 host is esxi 4.1 u1

the 2 others are 4.0 esx

Ha is getting an error when i enable it on both esx 4,0 hosts.

Ha agent in cluster has an error: cannot complete Ha configuration

task and events:

/opt/vmware/aam/bin/ft_startup failed to complete within 3 minutes: Unknown Ha error

[idle-jam]

check this out: http://communities.vmware.com/thread/291099

[tdubb123]

i tried removing the hosts and adding them back. when i add the 2 esx4 hosts. ha is fine. no errors. when i add the 3rd esxi 4.1 u1 host, ha fails on both esx4 hosts

[athlon_crazy]

Please try this here

[AndreTheGiant]

DNS resolution, FQDN, netmask are fine?

Andre

[tdubb123]

Yes all good

Sent from my iPhone

[Dave_Mac]

Can you try the following:

(i) Disable HA and DRS.

(ii) Enable HA on the Cluster
(iii) Let HA finish being configured
(iv) Enable DRS

If the above doesn't work, can you confirm the following:

(a) Hosts are added to the cluster using FQDN and not IP

(b) Confirm IP address of the hosts are the same in DNS as they are in /etc/hosts and /etc/vmware/esx.conf

If so can you post your logs up here from one of the ESX hosts

[bulletprooffool]

Are portgroups and storage consistent across all hosts in the cluster?

[tdubb123]

3 host cluster

2. esx4 hosts

1 esxi4.1 u1 host

the 2 esx4 hosts works fine in a cluster.

whenever i try to add the esxi 4.1u1 host into that cluster, ha fails.

[tdubb123]

there is no issue with dns. all hosts can be ping via fqdn. all vmotion and iscsi interfaces have ip addresses and can be pinged via fqdn and ip

[tdubb123]

i am not sure I have found the issue yet but I fouund out that my vsphere version was older than the esxi host that I was trying to put into a cluster. since I upgraded to vsphere u1 345043. but even after i upgraded I was still having HA problems. kind of a hit and miss thing. I would disconnect a host, remove it, put it back in a cluster. sometimes it would work sometimes it wouldnt. I tried disabling HA in the cluster level most of the times it fails. vmotion also timed out.

Also I noticed that everytime I remove a host and put it back into a cluster, It loses all vds configuration. I had to manually add a host back into the dvswitch.

since upgrading all hosts to esxi 4.1 u1, its been working ok.