Remarkable Notes from the VMware Documentation

 

“When you add a host to a cluster, all virtual machines in the cluster default to the cluster’s default restart priority (Medium, if unspecified) and default isolation response (Power off, if unspecified).”

Resource Management Guide, page 116.

 

So avoid using per-vm settings for HA, because those are lost when adding a host to your cluster.

 

====

 

“As a result, if the network connection is restored in this window between 12 and 14 seconds after the host has lost connectivity, the virtual machines are powered off but not failed over.”

Resource Management Guide, page 80.

 

So it is theoretically possible that, in the case of an intermittent network problem, some of your virtual machines will be powered off but not restarted (not on the original server nor on any other server).

 

====

 

“In a cluster using DRS and HA with HA admission control turned on, virtual machines might not be evacuated from hosts entering maintenance mode. This is because of the resources reserved to maintain the failover level. In this case, you must manually migrate the virtual machines off the hosts using VMotion.”

Resource Management Guide, page 80

 

What will happen, is that the host will not enter maintenance mode until you have manually powered off or VMotioned the vm’s. Note that this will probably be an issue when trying to schedule ESX updates, as Update Manager will try to enter each ESX server into maintenance mode before installing the updates.

One thought on “Remarkable Notes from the VMware Documentation”

  1. Your first post on this topic about HA and the window for network isolation

    I’ve had it happen in production were I lost both the switches, gateway or something for 12 – 14 seconds. All 25 VMs went down because both servers were I changed the behavior of isolation mode NOT to power off. You can change the timeout in 3.5. But my feeling if you lose the main console port and the secondary failover console port on another switch…. you should just hang it up anyway go find something else to do while networking fixes there problem. Funny thing if the network is isolated on the VM, the VM will not failover to another server just another port.

Leave a Reply