I turned this blog into a Page because I think it’s useful enough to keep this on the front page.
A while back I wrote down all the HA advanced options. With VirtualCenter 2.5 Update 3(and the ESX patch that came with it) VMware added another extra advanced options, this is the complete list:
- das.failuredetectiontime - Amount of milliseconds, timeout time for isolation response action(with a default of 15000 milliseconds).
- das.isolationaddress[x] - IP adres the ESX hosts uses for it’s heartbeat, where [x] = 1‐10. It will use the default gateway by default.
- das.usedefaultisolationaddress - Value can be true or false and needs to be set in case the default gateway, which is the default isolation address shouldn’t be used for this purpose.
- das.poweroffonisolation - Values are False or True, this is for setting the isolation response. Default a VM will be powered off.
- das.vmMemoryMinMB - Higher values will reserve more space for failovers.
- das.vmCpuMinMHz - Higher values will reserve more space for failovers.
- das.defaultfailoverhost - Value is a hostname, this host will be the primary failover host.
- das.failuredetectioninterval - Changes the heartbeat interval among HA hosts. By default, this occurs every second (1000 milliseconds).
- das.allowVmotionNetworks - Allows a NIC that is used for VMotion networks to be
- considered for VMware HA usage. This permits a host to have only one NIC configured for management and VMotion combined.
- das.allowNetwork[x] - Enables the use of port group names to control the networks used for VMware HA, where [x] = 0 - ?. You can set the value to be ʺService Console 2ʺ or ʺManagement Networkʺ to use (only) the networks associated with those port group names in the networking configuration.
- das.isolationShutdownTimeout - Shutdown time out for the isolation response “Shutdown VM”, default is 300 seconds. In other words, if a VM isn’t shutdown clean when isolation response occured it’s being powered off after 300 seconds.
- das.bypassNetCompatCheck - Disable the “compatible network” check for HA that was introduced with Update 2. Default value is “false”, setting it to “true” disables the check.
- das.failureInterval = The polling interval for failures. Default value is 30.
- das.maxFailureWindows = Minimum amount of seconds between failure. Default value is 3600 seconds, if VM fails within 3600 seconds VM HA doesn’t restart the machine.
- das.maxFailures = Maximum amount of VM failures, if the amount is reached VM HA doesn’t restart the machine automatically. Default value is 3.
- das.minUptime = The minimum uptime in seconds before VM HA starts polling. The default value is 120 seconds.
Virtual Machine Monitoring HA advanced options



Hello — i have a problem where an ESX server in a farm seems to send lots of reservations - i believe this could be HA issue - where in the HA is trying to poweron a running VM due to isolation etc - is there any way to check any logs as to how the aent is acting - checked tasks and events in VC - nothing much found
Thanks in advance for any advise u may render