Duplicate TEP IP Address Conflict During VCF ESXi Host Commissioning

Products

• VMware NSX

Issue/Introduction

During the commissioning of new ESXi hosts within VMware Cloud Foundation (VCF), duplicate Tunnel Endpoint (TEP) IP addresses are assigned to the new hosts, creating conflicts on the Geneve overlay network.

• The NSX Manager UI (System > Fabric > Hosts > Clusters > Node > IP Addressses) displays assigned TEP IP addresses for newly commissioned hosts that match IPs currently in use by a separate NSX host cluster.

• Transport nodes status reports as Degraded.

Environment

• VMware Cloud Foundation (VCF) 4.x/5.x

• VMware NSX

• VMware vSphere (ESXi)

Cause

An address pool with a similar name to the production pool was created containing overlapping IP addresses. Because the cluster was not configured to use a Transport Node Profile (TNP) and each host was configured individually, the incorrect overlapping IP pool was selected by mistake when configuring NSX on the new hosts.

Resolution

1. Log in to the NSX Manager UI.

2. Navigate to System > Fabric > Hosts > Clusters.

3. Expand the clusters to show the affected Nodes.

4. Select the individually configured ESXi hosts and reconfigure NSX to use the correct, non-overlapping IP pool.

5. If a cluster does not use a Transport Node Profile (TNP), create and apply a new TNP to the cluster to standardize the configuration.

6. If a cluster already uses a TNP, edit the existing TNP to use the correct pool. You do not need to create a new TNP.

7. Navigate to Networking > IP Management > IP Address Pools.

8. Delete or modify the incorrect IP pool containing the overlapping address range to prevent duplicate IP assignment during future host commissioning operations.

Additional Information

For more information on configuring Transport Nodes and IP Pools, refer to the VMware NSX Documentation.

Create an IP Pool for Tunnel Endpoint IP Addresses

Adding a Transport Node Profile