Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

Unable to configure VMware High Availability because the Default Gateway cannot be reached (1002478)

Last Updated: 3/29/2012Categories: Total Views: 8756Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Details

The configuration of VMware High Availability (HA) on ESX hosts fails because the default gateway is not pingable. The error message from the logs appears similar to:

An error occurred during configuration of the HA Agent on the host. Error detected on host.domain.com in hostname: isolationipunreachable: isolation address ping failed: <default gateway IP>

Inability to configure the default gateway may occur because there is no default gateway or that ICMP echoes have been disabled on the network.

Solution

A different isolation address can be configured by setting the das.isolationaddress parameter. This parameter is the address to ping to determine if a host is isolated from the network.

If you choose to change this address ensure that you choose a reliable address that is known to be available, so that the ESX host can determine if it is isolated from the network.

Note: This must be an address that is highly available because if it goes down, it causes a VMware HA isolation failover to occur. A HA isolation occurs on a given ESX if the HA agent on that ESX stops receiving heartbeats from HA agents on all other ESX hosts in the cluster and if it cannot ping the isolation address.

To change the isolation address:

Log in to VMware Infrastructure Client as an administrator.

Right-click the cluster in the Inventory.

Click Edit Settings.

Click the VMware HA item.

Click Advanced Options.

Under Option add das.isolationaddress, then under Value add the IP Address to be used for isolation failover detection.

Note: If you are using VirtualCenter 2.0.2 or later under Option add das.usedefaultisolationaddress and set the Value to false. This disables the use of the default gateway as an isolation address.

Note: As of VirtualCenter 2.0.2 multiple isolation addresses can be set. For more information, see Setting Multiple Isolation Response Addresses for VMware High Availability (1002117).

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

Related Versions:

VMware VirtualCenter 2.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant