VMware Cloud Community
thieslei
Contributor
Contributor
Jump to solution

Vsphere HA automatic Vmotion not working

Hi Guys.

We’re building a new HA Vmware environment, and we’re getting some issues about “HA-VMOTION, Migrating” and I need some help.

Probably something’s wrong in my cluster configuration, cause when I turn my Host Server off all virtual machines are migrated to the other Host Server automatically, but when just my network fails (took the cable off) the virtual machines appear like “disconnected” and stop responding ping requests, and it are not migrated to Host Server available.

Have someone had this problem? Can you help me to solve it?

Thanks.

Reply
0 Kudos
1 Solution

Accepted Solutions
tomtom901
Commander
Commander
Jump to solution

Because there are 2 levels of heartbeating integrated with vSphere HA.

1) Network heartbeat, which basically uses some basic connectivity tests to check if the host is still connected to the network.

2) Datastore heartbeat, which checkes if some files on the storage array can still be written to.

Because your network heartbeat fails, but the storage doesn't (assuming the storage and the network use different nics, and you didn't pull both cables) the host becomes isolated. This means that it isn't available on the network, but still has a connection to the storage array. Because the host is isolated, this triggers the host isolation response.

Screen Shot 2013-12-06 at 18.49.22.png

The default host isolation response is Leave powered on, which leaves the VM's powered on, in case of a host isolation.

Hope this helps you understanding the behaviour (by design) you're seeing.

View solution in original post

Reply
0 Kudos
3 Replies
tomtom901
Commander
Commander
Jump to solution

Because there are 2 levels of heartbeating integrated with vSphere HA.

1) Network heartbeat, which basically uses some basic connectivity tests to check if the host is still connected to the network.

2) Datastore heartbeat, which checkes if some files on the storage array can still be written to.

Because your network heartbeat fails, but the storage doesn't (assuming the storage and the network use different nics, and you didn't pull both cables) the host becomes isolated. This means that it isn't available on the network, but still has a connection to the storage array. Because the host is isolated, this triggers the host isolation response.

Screen Shot 2013-12-06 at 18.49.22.png

The default host isolation response is Leave powered on, which leaves the VM's powered on, in case of a host isolation.

Hope this helps you understanding the behaviour (by design) you're seeing.

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

Hello,

The vSphere is actually working as per design.HA does not trigger a vMotion at any time .only DRS does a vmotion. HA always restarts or reboots the VM on a Different Host when

one of the Host fails. Now when you remove the network cable of the host the VM's will not migrate because the host enters a Network isolation.

Please refer to the below KB that explains the situation better.

VMware KB: Understanding High Availability Host Isolation Response with Network Attached Storage

Thank you,

Avinash

thieslei
Contributor
Contributor
Jump to solution

Thank you guys

That was exactly what I was looking for. Thanks a lot.

Reply
0 Kudos