• 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

HA enhancements, exploring the next version of ESX/vCenter

Duncan Epping · Mar 23, 2009 ·

Let’s start with a screenshot:

These are the properties of an HA cluster, as you can see there are two sections that changed:

  1. “Enable Host Monitoring” is a brand new feature. Anyone who did network maintenance while HA was enabled knows why this feature will come in handy. Those that didn’t: Isolation response! If ESX is unable to send or receive it’s heartbeat and can’t ping it’s default isolation response address it will shutdown all VM’s. To avoid this behavior you can switch of HA for a specific host with this new feature. In just four words: Maintenance mode for HA.
  2. Besides the amount of host failures a cluster can tolerate you can also specify a percentage. With the “host failures” option VMware uses the highest values of CPU and Memory reservations to calculate the amount of slots. (For more on slot / slot size read the Resource Management Guide for ESX 3.5) With the new option “Percentage of cluster resources” this isn’t the case. This new option uses the actual reservation of the VM and calculates the total percentage of resources used based on these calculations. If no reservation have been made it uses the default 256Mhz / 256MB reservation. In other words, you will be more flexible and will get a higher consolidation ratio. If the default reservation values are to low you can always use the advanced options to increase it. Another new option is “specify a failover host”. This option can be compared to “das.defaultfailoverhost”. The good thing about this option is that the designated host will be used for fail-over only. DRS will not migrate VM’s to this host, and it’s not possible to start VM’s on this host.

Share it:

  • Tweet

Related

BC-DR, Server BC-DR, ESX, esxi, ha, vcenter, vSphere

Reader Interactions

Comments

  1. javellan says

    24 March, 2009 at 15:26

    “Enable Host Monitoring”
    Now what happens if say some of your guests don’t have VMware tools installed and running, do guests still give a hearbeat?

  2. Duncan says

    24 March, 2009 at 21:44

    it’s “Host” monitoring, not VM monitoring. This feature is for disabling the normal HA temporarily, isn’t about VM HA.

  3. Dan Malcor says

    17 September, 2009 at 20:15

    I have not seen anything that anything that says “This works for both ESX3.5 and vSphere”.

    :-Dan

  4. michael says

    1 October, 2009 at 11:17

    regarding “enable host monitoring”, does unchecking the box disable HA functionality completely?
    will it detect host failures and restart VMs or not?

  5. kopper says

    28 July, 2013 at 05:04

    michael hi did you get an answer? I am having the same doubt Disabling Host Monitoring will avoid VMs restarting when a physical hosts fails

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

Feb 9th – Irish VMUG
Feb 23rd – Swiss VMUG
March 7th – Dutch VMUG
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