Edge TEP gateway not reachable from Host TEP. Ensure that Edge TEP VLAN and Host TEP VLAN networks are routed error in SDDC for Edge cluster deployment.
search cancel

Edge TEP gateway not reachable from Host TEP. Ensure that Edge TEP VLAN and Host TEP VLAN networks are routed error in SDDC for Edge cluster deployment.

book

Article ID: 397158

calendar_today

Updated On:

Products

VMware SDDC Manager VMware NSX

Issue/Introduction

  • When attempting to deploy an Edge Cluster or to verify an edge cluster configuration within SDDC a failure is observed with the error:

Edge TEP gateway <Edge TEP Gateway> not reachable from Host TEP . Ensure that Edge TEP VLAN and Host TEP VLAN networks are routed

  • Log lines similar to the below are encountered in /var/log/vmware/vcf/domainmanager/domainmanager.log  (192.168.0.1 would be the Edge TEP Gateway IP in this log snippet) : 

    2025-05-07T12:12:53.246+0000 DEBUG [vcf_dm,681b########################9b9e,12ee] [c.v.e.s.c.c.v.esx.EsxCommandExecutor,dm-exec-8]  <ESXI Hostname>: esxcli response:

    <obj xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:vim25" versionId="6.0" xsi:type="ArrayOfDataObject"><DataObject xsi:type="VimEsxCLInetworkdiagpingVMKPing"><Summary><Duplicated>0</Duplicated><HostAddr>192.168.0.1</HostAddr><PacketLost>100</PacketLost><Received>0</Received><Recieved>0</Recieved><Roun
    dtripAvg>-2147483648</RoundtripAvg><RoundtripAvgMS>-2147483648</RoundtripAvgMS><RoundtripMax>0</RoundtripMax><RoundtripMaxMS>0</RoundtripMaxMS><RoundtripMin>999999000</RoundtripMin><RoundtripMinMS>999999</RoundtripMinMS><Transmitted>3</Transmitted></Summary></DataObject></obj>

    2025-05-07T12:12:53.267+0000 ERROR [vcf_dm,681b########################9b9e,12ee] [c.v.v.n.h.NsxtEdgeClusterValidationUtil,dm-exec-8]  Ping to 192.168.0.1 from <ESXI Hostname> is unsuccessful

    2025-05-07T12:12:53.267+0000 DEBUG [vcf_dm,681b########################9b9e,12ee] [c.v.v.n.h.NsxtEdgeClusterValidationUtil,dm-exec-8]  Checking routing on the following gateways: 192.168.0.1

    2025-05-07T12:13:06.356+0000 ERROR [vcf_dm,681b########################9b9e,12ee] [c.v.v.n.c.v.v.NsxTEdgeClusterValidator,dm-exec-8]  Validation errors for routing between Edge TEP VLAN and Host TEP VLAN : 192.168.0.1

    2025-05-07T12:13:06.357+0000 INFO  [vcf_dm,681b########################9b9e,12ee] [c.v.v.n.c.v.v.NsxTEdgeClusterValidator,dm-exec-8]  updateValidationCheck: {"errorCode":"EC_TEP_VLAN_ROUTING_VALIDATION_FAILURE","arguments":["192.168.0.1"],"stringArgs":["192.168.0.1"]}


    Note:
     The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware Cloud Foundation
VMware NSX

Cause

As part of the pre-checks within SDDC it checks whether all existing host TEPs can reach the configured gateway of the deploying edges. If these pings to the gateway fail the above error can occur.

Resolution

This is a condition that may occur in a VMware Cloud Foundation environment.

Ensure this gateway IP configured on the edge nodes is reachable and pingable from all ESXI nodes currently present in the environment. This can be validated by following the KB Testing VMkernel network connectivity with the vmkping command .

Once ping is fully working, re-deploy/re-verify the configuration for the edge nodes.

Additional Information

While validating and checking the edge config / deployments. The logs can be checked live on the SDDC manager to find the ESXI host that is problematic by running the below via SSH on the SDDC Manager:

tail -f /var/log/vmware/vcf/domainmanager/domainmanager.log  | grep -i 'Ping to.*from.*is unsuccessful'