ESX host preparation fails with error "Host configuration: Failed to send the HostConfig message.[TN=TransportNode/<Tn UUID>]. Reason:Failed to get a valid IP from IpPoolIpPool/<IP Pool UUDI> with cidr###."

Products

• VMware NSX

Issue/Introduction

• The ESXi host transport nodes are reporting the error below.
  
  'Failed' : "Host configuration: Failed to send the HostConfig message.[TN=TransportNode/<Tn UUID>]. Reason:Failed to get a valid IP from IpPoolIpPool/<IP Pool UUDI> with cidr###."

 

Environment

VMware NSX

Cause

• This Issue triggers when the Transport Node Uplink Profile is configured with the default Teaming policy that uses uplinks 1 and 2, while the Named Teaming Policy (defined under the default teaming policy) uses the uplink 3 and 4.
• Hence the Transport Node Profile detects 4 uplinks associated with the Uplink Profile and therefore it allocates 4 TEPs to the ESXi hosts. If there is an exhaustion in the TEP IP pool, it will fail to allocate the required TEP IPs.
  • For example, TEP pool with 10 free IP's can be fully utilized on 5 ESXi hosts with 2 TEPS. If any of the ESXi host is configured with 4 TEP Uplinks, the ESXi host will not get the IPs on the extra 2 TEP interfaces.
• Path: NSX UI --> System --> Profiles --> Uplink profiles--> Select the uplink profile of the host configured as part of Transport Node Profile (TNP).

Resolution

• Correct the name teaming policy with required uplinks to match with the same uplinks across both Default Teaming and Named Teaming Policy.

(Or)

• If there is a requirement for multiple TEP interface on the ESXi host, then add additional free IPs to TEP Pool.