The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!
VMware ESX 5.5 High Availability did not work when network failed, how to configure HA so VMs failover when network fails?
Hello all,
My customer has a VMware ESX 5.5 environment which consists of 5 hosts. One of the hosts lost network access to LAN and Management networks. None of the VMs failed over / migrated to the other hosts and became unavailable without network access until network access was restored. Checking the Cluster settings HA is enabled and Host Isolation is configured to Shut-Down. Now is this correct? How would I need to change the configuration so HA migrates VMs to another host in case this happens again?
Many Thanks,
Mark
My customer has a VMware ESX 5.5 environment which consists of 5 hosts. One of the hosts lost network access to LAN and Management networks. None of the VMs failed over / migrated to the other hosts and became unavailable without network access until network access was restored. Checking the Cluster settings HA is enabled and Host Isolation is configured to Shut-Down. Now is this correct? How would I need to change the configuration so HA migrates VMs to another host in case this happens again?
Many Thanks,
Mark
Asked:
-
3
2
1 Solution
I have included a screenshot of the log, thank you for explaining this. Just looking at the logs I can see that there may have not been enough time for the VMs to shut-down and restart on another host.
Am I correct by thinking that if a host cannot be contacted for 15 seconds, it will start shutting down all VMs. These VMs will then be restarted on another host?
ee-VM-HA.PNG
Am I correct by thinking that if a host cannot be contacted for 15 seconds, it will start shutting down all VMs. These VMs will then be restarted on another host?
ee-VM-HA.PNG
Well judging by the time between network errors in the log I can see that network connectivity has been restored in less than 15 seconds. This means that host would have not given the shut down command, so this is not necessary a config issue/fault. Thank you for clarifying this.
I've requested that this question be closed as follows:
Accepted answer: 250 points for Andrew Hancock's comment #a40618664
Assisted answer: 250 points for Andrew Hancock's comment #a40618628
Assisted answer: 0 points for MarkFogel's comment #a40618648
Assisted answer: 0 points for MarkFogel's comment #a40618768
for the following reason:
.
Accepted answer: 250 points for Andrew Hancock's comment #a40618664
Assisted answer: 250 points for Andrew Hancock's comment #a40618628
Assisted answer: 0 points for MarkFogel's comment #a40618648
Assisted answer: 0 points for MarkFogel's comment #a40618768
for the following reason:
.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
VMs are restarted automatically in a HA event when its uncontrolled.
So there will always be a few minutes of downtime.
Were there any errors?
Check DNS Reverse DNS and Default Gateway is contactable for ALL hosts.