Tunnel End Point (TEP) not getting created after making changes on uplink profile.

Products

• VMware NSX

Issue/Introduction

• After adding a new uplink to an existing uplink profile that is currently applied to a transport node (ESXi) cluster, the corresponding Tunnel Endpoint (TEP) is not being created on the transport nodes.
• It appears that the configuration change made to the uplink profile is not being reflected or pushed onto the corresponding transport nodes in the cluster.

Environment

VMware NSX

VMware vSphere ESXi

Cause

• The TEP IP Pool used in the Transport Node profile (attached with the concerned Uplink profile) does not have any free IP address which can be assigned to the newly created vmkernels(TEP).
• In this case, there were two uplinks set to active-active mode but the load balancing policy is set to "failover order", there is no standby uplink available for failover, leading to a configuration conflict.

Resolution

• Add additional IP addresses to the TEP IP pool.
• Configure a load balancing policy that is compatible with the teaming and failover settings.

Additional Information

• For more information on the load balancing policy refer: Create an Uplink Profile
• To add IP address in the IP pool refer: Add an NSX IP Address Pool