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

My Subscriptions

Loading

Knowledge Base

Incompatible HA Networks appearing when attempting to configure HA (High Availability) (1006541)

Last Updated: 3/20/2024Categories: How toTotal Views: 29726Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

VMware High Availability (HA) does not work.

Configuration of VMware HA fails with VirtualCenter 2.5 Update 2.

Errors similar to these appears in the Tasks and Events tab:

HA agent on <esxhostname> in cluster <clustername> in <datacenter> has an error Incompatible HA Networks:
Cluster has network(s) missing on host: x.x.x.x
Consider using the Advanced Cluster Settings das.allowNetwork to control network usage.

Currently has no available networks for HA communication. The following networks are currently used by HA:Service console

Resolution

As of VirtualCenter 2.5 Update 2, two advanced options have been added to allow greater control over the networks used for cluster communication. These two advanced settings enable greater flexibility in the control and usage of VMware HA networks, while still preserving the VMware HA requirement that all cluster nodes have identical, compatible networks.

Note: This new network compatibility check is implemented to increase cluster reliability and only impacts existing clusters after VirtualCenter is upgraded to Update 2 if they were previously configured with incompatible networks.

The parameters are:

das.allowVmotionNetworks - Allows for a NIC that is used for VMotion networks to be considered for VMware HA usage. This parameter enables a host that has only one NIC configured for management and VMotion combined to be used in VMware High Availability communication. By default, any VMotion network is ignored. To use the VMotion network, add das.allowVmotionNetworks with a value of true to the HA advanced options.

das.allowNetwork[...]- Allows the use of port group names to control the networks used for VMware HA. The value is set as the name of the portgroup, for example, Service Console or Management Network. When configured, the VMware HA cluster only uses the specified networks for VMware HA communication.

This error is often experienced after an upgrade when the cluster has both ESX hosts and ESXi hosts in the configuration, if they previously had incompatible networks and were successfully configured. The reason is that the ESX standard hosts have a service console portgroup for the service console IP address and one VMkernel port group for VMotion IP address, whereas in ESXi, both the Management IP address (similar to the service console in standard ESX 3.x) and the VMotion IP address are on the VMkernel port group. Therefore, standard ESX hosts only use the service console network, whereas the ESXi Server hosts use both, or whichever was picked up first, causing the incompatible network error to be displayed.

To configure VMware HA to use the new settings:

Log in to VirtualCenter with VMware Infrastructure (VI) Client as an administrator.

Edit the settings of the cluster and deselect Enable VMware HA.

Click OK, and wait for the servers to unconfigure for VMware HA.

Click ESX Server > Configuration > Networking on each of the ESX hosts in the cluster and note the portgroups that are common between the servers.

Note: The portgroup names should all be identical, and must have network connectivity with each other. For more information about testing network connectivity using ping, see Testing network connectivity with the Ping command (1003486).

Edit the settings of the cluster, and select Enable VMware HA.

Click VMware HA.

Click Advanced Options.

Add the das.allowNetworkX option with a value of the portgroup name, where X is a number between 0 and 9, as shown in the following image:

Note: You can add more than one portgroup, if required (to a maximum of 10), as shown in the following image:

When all network portgroups have been added, click OK to exit out of the advanced options.

Click OK to exit out of the Cluster configuration, and start the reconfiguration of VMware HA with the modified network settings.

Related Information

HA (High Availability) を構成しようとすると「Incompatible HA Networks」エラーが表示される
尝试配置 HA (High Availability) 时出现不兼容的 HA 网络

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
VMware Update Manager 插件安装失败 (1003468)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware VirtualCenter

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

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