edge datapath configuration failure with the error "Failed to enable the datapath on the Edge node after three attempts"

Products

• VMware NSX

Issue/Introduction

• Edge tunnel went down or it stuck at not available state, tier1 gateways were in down state.
• North-south and east-west traffic will be impacted.

     

   

NSX Manager var/log/syslog

2026-02-01T02:28:07.548Z  NSX 5020 MONITORING [nsx@6876 alarmId="ID" alarmState="OPEN" comp="nsx-manager" entId="ID" errorCode="MP701099" eventFeatureName="edge_health" eventSev="HIGH" eventState="On" eventType="edge_datapath_configuration_failure" level="ERROR" nodeId="ID" subcomp="monitoring"] Failed to enable the datapath on the Edge node after three attempts.
var/log/syslog:2026-02-01T02:28:21.546Z  NSX 5020 MONITORING [nsx@6876 alarmId="ID" alarmState="OPEN" comp="nsx-manager" entId="ID" errorCode="MP701099" eventFeatureName="edge_health" eventSev="HIGH" eventState="On" eventType="edge_datapath_configuration_failure" level="ERROR" nodeId="ID" subcomp="monitoring"] Failed to enable the datapath on the Edge node after three attempts.

NSX edge syslog.log

2026-01-31T16:24:31.541Z <edge name> NSX 17107 SWITCHING [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="lswitch" tname="dp-ipc23" level="WARN"] lswitch 17###-#####2f is also using VLAN 311 on device fp-eth0
2026-01-31T16:24:31.541Z <edge name> NSX 17107 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="dpc-pb" tname="dp-ipc23" level="ERROR" errorCode="EDG0400171"] dpc_create_vlan_lswitch failed to create lswitch ca##-#####-#####bb7
2026-01-31T16:24:31.363Z <edge name> - -  2026-01-31T16:24:31Z datapathd 17107 dpc-pb tname="dp-ipc23" [ERROR] dpc_create_vlan_lswitch failed to create lswitch ca##-#####-#####bb7  errorCode="EDG0400171"
2026-01-31T16:24:31.489Z <edge name> datapath-systemd-helper 16960 - -  2026-01-31T16:24:31Z datapathd 17107 dpc-pb tname="dp-ipc23" [ERROR] dpc_create_vlan_lswitch failed to create lswitch ca##-#####-#####bb7  errorCode="EDG0400171"

Cause

Multiple Tier-1 Service Routers were moved to the same edge cluster, causing VLAN-backed segments with identical VLAN IDs to be pushed to the same edge node.
Specifically:

• VLAN 311: Segments 17###-#####2f  and ca##-#####-#####bb7 (both using VLAN 311 on the same Transport Zone) ended up on edge after their associated T1 routers were assigned to the same edge cluster.

Resolution

When configuring VLAN-backed segments, ensure that segments using the same VLAN ID on the same Transport Zone are not connected to Tier-1 routers that may be hosted on the same edge cluster.