In my latest article at VirtualizationAdmin.com, I show you, step by step, how to configure VMware’s High Availability (VMHA). Make configuring VMHA easy by following the article at How to Configure VMware High Availability (VMHA)
In my latest article at VirtualizationAdmin.com, I show you, step by step, how to configure VMware’s High Availability (VMHA). Make configuring VMHA easy by following the article at How to Configure VMware High Availability (VMHA)
David Davis (CCIE #9369, vExpert, VCP, VCAP-DCA) has been in the IT industry for 20+ years. He has authored hundreds of articles, 10+ video training courses, and co-authored one book. Learn about David's certifications, video courses, and where you can find his content on our About Us page.
{ 4 comments… read them below or add one }
Hello,
Can you provide me on how enable the heartbeat monitoring, I tried a HA functionality using a one cluster with 2 host the primary and secondary, when I try to reboot the primary ESX server the VM went down too without a failover. I suspect that the two ESX server were not respond to the heartbeat bcoz of the reb indicator even do they are running.
note: the 2 ESX machine are not the same specs.
Hi Maiko,
Did you follow the instructions in the article above and put both ESX hosts in a resource pool and enable HA ?
Even if the other host doesn’t take the VM Guests when the first ESX host dies, the second ESX host should not also fail at the exact same time. Something doesn’t sound right there.
-David
Does anything need to be done to the hosts before moving them into the HA cluster? I’ve tried to move all three of my hosts, and they all give the status “The operation is not allowed in the current state”. I tried to find a solution to this, but the only one I found said to cancel the “Enter service mode task” in VIC… My hosts aren’t in maintenance mode.
Hi Clayton,
As long as they all have access to the same shared storage (where the VMs are) and as long as you are licensed for HA, then I don’t think there is much else that has to be done.
I would try what it suggests in this VMware KB article – maint mode & restarting the host mgmt agents – to see if it resolves your issue.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003829
Hope that helps! Thanks for reading!
-David