Missing TEP IP Addresses After Domain Activation in VCF 9.1

Products

• VMware NSX

Issue/Introduction

ESXi hosts in an affected cluster fail to acquire TEP IP addresses from the configured TEP IP Pool after importing NSX in VCF 9.1.

Environment

• VMware Cloud Foundation (VCF) 9.1
• VMware NSX

Cause

Transport Node Profiles and Distributed Virtual Switches are bound to the specific vCenter Server instance in which they are configured. Because the affected cluster is managed by a separate vCenter Server, it lacks access to the DVS and TNP defined in the other vCenter. Without a valid, accessible TNP and DVS, NSX host preparation cannot complete, preventing the allocation of TEP IP addresses.

Resolution

Provision a dedicated DVS and corresponding Transport Node Profile within the target vCenter Server to resolve cross-vCenter object isolation.

1. Log into the vCenter Server managing the affected cluster.
2. Create a new Distributed Virtual Switch (DVS) with settings that match the DVS in the other environment.
3. Log into NSX Manager.
4. Create a new Transport Node Profile (TNP) associated with the newly created DVS.
5. Configure the TNP to use the target TEP IP Pool.
6. Apply the newly created Transport Node Profile to the affected cluster.
7. Confirm that NSX host preparation completes and that hosts successfully acquire TEP IP addresses from the pool.