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

Stretching a cluster fails with "Validate interzone host connectivity failed due to unknown error" (78342)

Last Updated: 4/14/2020Categories: TroubleshootingTotal Views: 3232Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article provides a workaround for VMware Cloud Foundation deployments that encounter the error "Validate interzone host connectivity failed due to unknown error".

Environments that do not allow routing between the Management Network and the vSAN Network between Availability Zones will encounter this issue.

Cause

Up to vSphere 6.7u3 vSAN does not have a dedicated TCP/IP stack, instead it uses the Management TCP/IP stack to route traffic out of the ESXi host.

To force the vSAN interface to be used to route traffic, static routes must be added.  Although the Cloud Foundation adds static routes during the Stretched Cluster workflow to ensure that vSAN traffic doesn't egress the Management interface, it does not add them prior to the validation.

Because the static routes do not exist before the interzone host connectivity task, the ping test sends traffic out the Management (vmk0), if the vSAN network is not reachable via the Management network the validation will fail with the error, "Validate interzone host connectivity failed due to unknown error'.

Resolution

This is a known issue for environments that do not allow routing between the Management Network and the vSAN Network.

Prior to executing the Cloud Foundation Stretched Cluster Workflow, static routes will need to added to all hosts in AZ1 and AZ2 that will participate in the stretched cluster.

Example:
The vSAN network in AZ2 is 172.16.33.0/24.

SSH to each ESXi host in AZ1 and view the routing table.  In the example below the 172.16.33.0/24 network does not exist. Run the following command:

esxcfg-route -l

VMkernel Routes:
Network          Netmask          Gateway          Interface
172.16.11.0      255.255.255.0    Local Subnet     vmk0
172.16.13.0      255.255.255.0    Local Subnet     vmk2
default          0.0.0.0          172.16.11.253    vmk0

Manually add the static route to each ESXi host in AZ1 using the command below:

esxcli network ip route ipv4 add -n 172.16.33.0/24 -g 172.16.13.253

Verify that the static route was created successfully. Run the following command:

esxcfg-route -l

VMkernel Routes:
Network          Netmask          Gateway          Interface
172.16.11.0      255.255.255.0    Local Subnet     vmk0
172.16.13.0      255.255.255.0    Local Subnet     vmk2
172.16.33.0      255.255.255.0    172.16.13.253    vmk2
default          0.0.0.0          172.16.11.253    vmk0

Note: Be sure to complete the process for each ESXi host in AZ1 that is participating in the stretched cluster.

The vSAN network in AZ1 is 172.16.13.0/24

SSH to each ESXi host in AZ1 and view the routing table.  In the example below the 172.16.33.0/24 network does not exist. Run the following command:

esxcfg-route -l

VMkernel Routes:
Network          Netmask          Gateway          Interface
172.16.31.0      255.255.255.0    Local Subnet     vmk0
172.16.33.0      255.255.255.0    Local Subnet     vmk2
default          0.0.0.0          172.16.31.253    vmk0

Manually add the static route to each ESXi host in AZ1 using the command below:

esxcli network ip route ipv4 add -n 172.16.13.0/24 -g 172.16.13.253

Verify that the static route was created successfully. Run the following command:

esxcfg-route -l

VMkernel Routes:
Network          Netmask          Gateway          Interface
172.16.31.0      255.255.255.0    Local Subnet     vmk0
172.16.33.0      255.255.255.0    Local Subnet     vmk2
172.16.13.0      255.255.255.0    172.16.33.253    vmk2
default          0.0.0.0          172.16.11.253    vmk0

Once the static routes have been added retry the workflow.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vRealize Operations Manager 8.1 でアップグレード プロセスの再起動フェーズを実行した後、ノードにアクセスできない (78302)

KB
•
SR-IOV シナリオで Intel NIC 82599/X520 を使用している場合の VLAN トランク モードの VLAN インターフェイス間の問題 (78245)

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

KB
•
よくあるご質問：VMware Workspace ONE SaaS 環境の月次メンテナンス (2960626)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 3.9.x

Take Our Survey

Support Assistant