Hey all!
I believe the issue I'm having is DNS related, but I just wanted to post this and confirm.
I have 3 hosts, all on a private lan (192.168..). My vServer (which is a VM) is on a public lan, and is managing the hosts just fine when it's online... however when I upgraded VMware Tools on it and rebooted, I noticed before it shutdown that the hosts started having problems (Alarm triggered with an HA problem) and it started vMotioning a few of my VM's around. When the vServer came back up and I connected back to the cluster, it was still vMotioning a VM.
I know that in 3.5, private hosts needed to have the /etc/hosts file updated with the IP/Names, as well as the VC (for HA to work). I know that vCenter now takes care of the HA part, in regards to DNS... however would inputting the IP/names onto each host in /etc/hosts resolve this issue when the vCenter server is being rebooted/or offline?
Side note... I cannot console to the VM's through a workstation running the client, only through the vCenter server. I'm assuming that DNS entires on the host itself would also resolve this?
Thanks
-Chris