VMware ESXi 4.1 HA Warning Message
Posted by jlchannel - on September 9th, 2010 in ESXi, Tips, vSphere | 11 Comments »
I was playing around with VMware vSphere ESXi 4.1 recently and I found the warning message “HA initiated a failover action in cluster your-cluster-name in datacenter your-datacenter-name” keep show on my vCenter. Nothing has been changed, HA working like a charm, no VMs have been reboot and the warning message just annoying.
The solution are pretty simple.
Option 1:
1. Turn OFF VMware HA on Cluster Feature setting.
2. Enable VMware HA setting again.
Option 2:
1. Enter maintenance mode
2. Remove ESXi hosts from cluster
3. Add ESXi hosts back to cluster
4. Exit maintenance mode
Done! The annoying warning message will go away.
11 Responses
For Option-1, sometime you need to wait for about 30-minutes or more between action 1 and 2.
If you disable and then enable it again in less than 2 minutes, sometime the problem persist.
I really like VMware, and especially ESXi 4.1.
However, I find it rather annoying that I have to look in like 10 different places in order to determine what a warning sign means.
There should have been a consolidated error panel!
And I think it’s extremely bad having to break my HA for HALF AN HOUR while performing this trick. What happens if a node fails for some reason for that period? Downtime!
Come again, VMware. You can make that better!
You may want to recheck all the connectivity and consistency especially on the DNS server you are pointing to, from the ESX hosts. FQDN is important for each ESX hosts to communicate in the HA scenario. Always have redundant DNS configuration in place to prevent HA failure. Beside that, you can also edit the host file to hard code the IP for each ESX hosts, but I will not recommend to do this as the environment scale out, you will face challenges to keep this updated.
Nothing is perfect but VMware had done a great job in term of the HA architecture compare to others hyper-visor in the market today.
Just my 2 cents
Option 1 work for me…I got rid of the error. Thanks a lot
Hi. Option 1 worked for me too. I waitet 3 minutes between step 1 and step 2.
Thanks for your help and kind regards
option one worked great!!
thank you
Option 1 did the business for me, thanks!
Option 1 worked for me.
option 1
Option 1 worked gr8 for me..Thanks a lot
Option 1 worked for me.