Edge transport node realization fails with the error "Failed to enable the datapath on the Edge node after three attempts" due to duplicate VTEP IP addresses.

Products

• VMware NSX Networking

Issue/Introduction

Symptoms:

• NSX-T versions: NSX 3.2.0, NSX 3.2.1, NSX 4.0.
• Transport nodes are assigned IP address from static pool in NSX-T.
• Edge TN realization fails with the error "Failed to enable the datapath on the Edge node after three attempts".
• Traffic will be impacted on the TN nodes which have the same VTEP IPs.
• Relevant log’s location: /var/log/hostd.log on the hosts show logs reporting duplicate IP addresses

2023-02-22T13:23:26.431Z info hostd[2101500] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 910 : A duplicate IP address was detected for 192.168.1.186 on the interface vmk10. The current owner is 00:50:56:60:50:0b.

2023-02-22T13:23:26.748Z info hostd[2101500] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 911 : A duplicate IP address was detected for 192.168.1.187 on the interface vmk11. The current owner is 00:50:56:69:11:e1.

Environment

VMware NSX-T Data Center

Cause

This is occurs when duplicate VTEP IP addresses are assigned to transport nodes (host or edge nodes).
This can occur during certain operations, where multiple transport nodes are being configured at the same time, 1 transport node has released the VTEP IP's addresses, but is still using them and the other host is then assigned these same IP addresses by the NSX manager.

Resolution

This is resolved in NSX 3.2.2, NSX 4.0.1 available at VMware downloads.

Workaround:

There are two possible workarounds:

• Option 1: 

Unprepare all transport node with the duplicate IPs identified or in failed state and prepare the transport node for NSX-T again.

• Option 2: 

Unprepare all transport nodes with the duplicate IPs identified, except one. i.e. one transport node can keep its VTEP IP address(es) and there will be no more duplicates, then prepare the other transport node for NSX-T again.