• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Update: HA Advanced Options

Duncan Epping · Oct 6, 2008 ·

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] = 0-9. 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 introducedwith Update 2. Default value is “false”, setting it to “true” disables the check.Virtual Machine Monitoring HA advanced options
  • 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.

Related

Server ESX, esxi, ha, networking, VirtualCenter, VMware

Reader Interactions

Comments

  1. David says

    7 October, 2008 at 00:31

    HI

    You mention ESX 3.5 update3 in the post, is this supposed to be Virtual centre 2.5 update 3? Or is ther a new release of ESX 3.5 on it’s way soon?

    Cheers

  2. Duncan Epping says

    7 October, 2008 at 07:22

    Sorry, I wasn’t awake yet when i wrote the article. should have said VirtualCenter instead of ESX.

  3. James Roth says

    8 October, 2008 at 09:54

    Hi Duncan, talking about advanced settings, is there one for the paste limit between VMs in the VI client? Currently it looks set to 64K.

  4. Duncan Epping says

    8 October, 2008 at 13:22

    i will have a look if i can find anything….

  5. Adam Baum says

    9 October, 2008 at 01:18

    is there a complete list of all the DAS settings? It looks like some of them may have changed or may be similar to existing settings. Example: You list das.failuredetectioninterval, but my VC U2 has das.failureInterval. Are these the same or different?

  6. Duncan Epping says

    9 October, 2008 at 11:31

    Okay, I see…. the das.failureInterval is related to VM Monitoring, so HA for the Guest OS. I will add the settings today.

  7. JOnas says

    5 January, 2012 at 18:04

    Hi Duncan

    Nice work! Thank you, it’s realy helpfully

Primary Sidebar

About the author

Duncan Epping is a Chief Technologist in the Office of CTO of the Cloud Platform BU at VMware. He is a VCDX (# 007), the author of the "vSAN Deep Dive", the “vSphere Clustering Technical Deep Dive” series, and the host of the "Unexplored Territory" podcast.

Upcoming Events

May 24th – VMUG Poland
June 1st – VMUG Belgium

Recommended Reads

Sponsors

Want to support Yellow-Bricks? Buy an advert!

Advertisements

Copyright Yellow-Bricks.com © 2023 · Log in