I had to reboot one of the two ESX 3.0.2 server that I have here.
Now the I get a HA Error ‘An error occurred during configuration of the HA Agent on the host' when try to reconfigure HA.
I also notice that within the console of the same host if type "hostname -a" I get "Host name lookup failure"
I appear to still be able migrate VMs but clearly something is wrong somewhere, is there DNS config file I can check, I have allready check ed the hosts file and I can ping everything using both long DNS name and short hostname.
Or maybe there is dns service I can restart?
Thanks
If you are running ESX 3.0.x check /etc/FT_HOSTS
you can also check http://kb.vmware.com/kb/1003691
check your /etc/hosts file
Also, you can check /etc/opt/vmware/aam/FT_HOSTS
You can also confirm your DNS settings through the VI Client -
If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
I have allready but maybe you could check it for me.
127.0.0.1 localhost.localdomain localhost
127.0.0.1 mcsesx2.mcs.local mcsesx2
172.16.1.25 mcsesx1.mcs.local mcsesx1
172.16.1.26 mcsesx2.mcs.local mcsesx2
172.16.1.3 mcsdc02.mcs.local mcsdc02
MY
/etc/opt/
folder is empty? I that ok?
If you are running ESX 3.0.x check /etc/FT_HOSTS
you can also check http://kb.vmware.com/kb/1003691
Sorry
There doesn't appear to be any /etc/FT_HOSTS on the ESX host that has the problems.
My other server looks like-
Auto-generated FT_HOSTS file. Timestamp: Tue Feb 10 14:14:10 2009
I'm not running 3.0.x, but in my FT_HOSTS file I have the IP and shortname of all the ESX hosts participating in HA Cluster.
That intresting, can you tell me what it looks like please?
added the FT_HOSTS file ,sadly I am still "getting hostname lookup failure" and ‘An error occurred during configuration of the HA Agent on the host'
?:|
can you restart hostd?
At the service console type:
service mgmt-vmware restart
Just make a note of this KB if you are running 3.0.1
service mgmt-vmware restart - still the same
Have also rebooted the vmware VC server and recreated the cluster but still no joy.
have you check the Configuration Tab and DNS and Routing to ensure the hostname is listed properly there? Hopefully this is it, because you have me stumped right now.
Finally, you may consider a rebuild as the last resort.
Yes DNS and gateway settings are the same as they''ve allways been and are the same as the OK server.
yes, you very well could be experiencing the problems outlined in KB http://kb.vmware.com/kb/1003789
Could I just remove the Service Console with IP 172.31.2.121 or do I need that?
you don't necessarily need it. It appears it was setup for HA as a isolation address. I would also think about moving your iSCSI VMkerel port up to vSwitch0, adding and additional NIC and moving your LAN onto it's on vSwitch.
But try removing the secondary COS first, that may fix your problem. Are all you ESX Hosts configured this way?
I removed the secondary COS but I still a have the same problem.
