Migrating NSX Transport Node TEPs from DHCP to Static IP Pools
search cancel

Migrating NSX Transport Node TEPs from DHCP to Static IP Pools

book

Article ID: 425283

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

In VMware NSX environments, Transport Nodes (ESXi hosts and Edge Nodes) require Tunnel End Point (TEP) IP addresses to facilitate overlay (Geneve) traffic.
While DHCP can be used for initial deployment, many organizations transition to Static IP Pools to gain better control over IP management, reduce dependency on external DHCP servers.
This article provides the procedure to migrate existing Transport Nodes from DHCP to an NSX Static IP 

Environment

VMware NSX 4.x

Resolution

Prerequisites

  1. NSX Backup: Perform a fresh backup of the NSX Manager before making configuration changes.
  2. IP Pool Creation: Ensure a Static IP Pool has been created in NSX with sufficient addresses and the correct Gateway/Subnet mask details. (Inventory > IP Address Pools).
    Reference: https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-2/installation-guide/transport-zones-and-transport-nodes/create-an-ip-pool-for-tunnel-endpoint-ip-addresses.html
  3. Make sure that the IP Range that does not conflict with the addresses administered by the DHCP server.

Step 1: Create or Update the Uplink Profile

  1. If your current Uplink Profile is specifically tied to DHCP, you may need to ensure your profile is compatible with an IP Pool.
  2. Navigate to System > Fabric > Profiles > Uplink Profiles. Verify the profile used by your Transport Nodes. No specific change is usually needed here, as the IP assignment method is defined at the Transport Node Profile or Host level.

Step 2: Update the Transport Node Profile (TNP)

  1. To ensure all hosts in a cluster move to the Static Pool, update the cluster-wide profile.
  2. Navigate to System > Fabric > Nodes > Host Transport Nodes.
  3. Select the Clusters tab.
  4. Select your cluster and click Configure NSX (or Edit if already configured).
  5. Under the IPv4 Assignment section, change the setting from DHCP to Use IP Pool.
  6. Select the Static IP Pool you created in the prerequisites.
  7. Click Save.

Step 3: Monitor the Migration.

  1. Once the TNP is saved, NSX will push the configuration change to the hosts.

Note on Impact: It is recommended to perform this activity in Maintenance Mode. If performed on an active cluster, a brief TEP flap may occur as the vmk interface releases the DHCP lease and acquires the Static IP.

  1. Navigate to System > Fabric > Nodes > Host Transport Nodes.
  2. Verify the new IP assignment by checking the Node Status or running the following command on the ESXi host: localcli network ip interface ipv4 get (Look for the vmk associated with the TEP).

Step 4: Verify Overlay Connectivity

  1. After the migration, ensure the TEPs can communicate across the fabric.
  2. From the NSX Manager UI, go to Plan & Troubleshoot > Traceflow. Perform a test between two VMs on different hosts to ensure overlay traffic is flowing.
  3. Alternatively, use the specialized ping command from one ESXi host to another's TEP IP: vmkping -I vmkX <Remote_TEP_IP> (where vmkX is the TEP interface).

 

Additional Information

Create an IP Pool for Tunnel Endpoint IP Addresses

Powered by Wolken Software