Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

"vSphere HA agent on this host could not reach isolation address '6.0.0.0'" reported on ESXi host (76737)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 44935Language:
English

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

1. In the vCenter user interface,in the Hosts and Clusters view, with the ESXi host selected, you see the message "vsphere ha agent on this host could not reach isolation address '6.0.0.0'".
2. 6.0.0.0 is configured as gateway of DefaultTcpIpStack.as below:

To check this:
1. Connect to the vCenter Server through the vSphere Client
2. Select Hosts and Clusters, select the ESXi host object
3. Select Configure > Networking > TCP/IP configuration
Note the default TCP/IP stack gateway is set to '6.0.0.0'

Purpose

This article provides information on how this issue is produced and how to work around it.

Cause

A new vSwitch and vmk port is created automatically when Integrated Management Module (IMM) is connected.
If 0.0.0.1/24 is configured as IP address by IMM, an ESXi bug will be triggered and 6.0.0.0 will be set as gateway of DefaultTcpIpStack,
You will see an error because this is not a valid gateway address.

Impact / Risks

vSphere HA agent cannot be implemented on affected ESXi host.

Changing network settings using these commands may make the host unusable and can necessitate a reboot to recover.

Resolution

This issue is resolved in VMware ESXi 7.0 Update 1 (build number 16850804).

Workaround

1. Modify the IMM configuration to make sure a legal IPv4 address is set, but not 0.0.0.1/24

For information about modifying the IMM configuration, consult your ESXi server hardware vendor or documentation.

2. Modify ESXi configuration to clear the notification "vsphere ha agent on this host could not reach isolation address '6.0.0.0'":
a. Connect to the vCenter Server through the vSphere Client

b. Select Hosts and Clusters, select the ESXi host object

c. Select Configure > Networking > VMkernel adapters

d. Select each vmk to check if the gateway is set to 6.0.0.0.

e. With a vmk selected, In the pane below the adapter list select the All tab

If the display below under IPv4 settings shows the Default gateway is '6.0.0.0':

Either select the 'X' icon to delete the vmk, or

Select the pencil (edit) icon to edit the settings:

Select IPv4 settings

Select Use static IPv4 settings

Enable Override default gateway for this adapter

Set the gateway to a valid address

If deleting the vmk:

If modifying the vmk gateway to a valid IP address:

Check the management network gateway setting in the ESXi host Direct Console User Interface (DCUI)
a. Access to the ESXi host DCUI.
Note: This can be done by direct connection to the server hardware, back-end management system such as iDRAC, iLO, UCS, or from an SSH session per KB 2039638 .
b. Select IPv4 Configuration. If the gatway is set to '6.0.0.0' and use the Enter key to change settings
c. Set the default gateway to a valid IP address.

d. Restart management agents. Refer to Restarting the Management agents in ESXi (1003490)

Related Information

This issue can be reproduced by setting up ESXi with default network configuration, vmk0 and vSwitch0:
a. esxcli network vswitch standard portgroup add --portgroup-name="test-pg" --vswitch-name=vSwitch0
b. esxcli network vswitch standard portgroup list
c. esxcli network ip interface add --interface-name=vmk1 --portgroup-name=test-pg
d. esxcli network ip interface ipv4 set --interface-name=vmk1 --type=static --ipv4=0.0.0.1 --netmask=255.255.255.0

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant