• 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

vSphere HA in 5.0 constantly pinging my gateway?

Duncan Epping · Jun 26, 2012 ·

I had this question today and noticed someone also dropped it on the community forums. The question was if vSphere HA is constantly pinging the default gateway or not. I knew HA would ping the gateway on a regular basis as of vSphere 5.0, and on a more frequently basis if a ping would fail but I wasn’t sure about the timing. I pointed Marc Sevigny from the HA engineering team to the thread on the community forums and he added added some nice juicy details to the it. I figured I would share them with you.

First of all, each ESXi host in a 5.x cluster will ping the isolation address every 5 minutes (300 seconds). Could this flood the isolation device?

There should be no “flood” of ICMP messages, and it should have little impact on network performance. The ICMP packet is 53 bytes long and sent once every 5 seconds from each of the HA hosts until the address(es) become pingable once again, at which point it returns to pinging once per hour.

If your default gateway is never pingable because of your firewall, you should open up the ports needed by HA. It is also possible to or disable the isolation address monitoring on the default gateway by using an advanced option (das.useDefaultIsolationAddress = false). It is recommended to specify a different isolation address (das.isolationaddress0) when the default gateway is a non-pingable device. Note that it is highly recommend to use a device as the default gateway which is as few hops removed from your hosts as possible!

Related

BC-DR 5, 5.0, ha, high availability, vSphere

Reader Interactions

Comments

  1. sanderdaems says

    26 June, 2012 at 16:11

    Nice, good to know, thanks!

  2. Martin says

    26 June, 2012 at 16:34

    Thank you, this is very useful practical knowledge

  3. Sven says

    27 June, 2012 at 16:27

    Hi Duncan,
    apologies this ahs nothing to do with the above post but i could not find any other way to get this to you.
    Just reading your Vsphere 5 Clustering Technical deepdive and it looks on page 43 Table2:Host states there is an error in the isolated state…surely you meant the Storage heartbeat should be set to NO to fullfill the isolated state?

    Cheers
    Sven

  4. smooter says

    20 August, 2012 at 23:32

    Something to remember:

    If you DO enable a different isolation address “das.isolationaddress0”, it will NOT stop utilizing the default unless you DO make the “das.useDefaultIsolationAddress = false” change as well!

    Just a simple gotcha I have seen too many times to ignore!

    smooter

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