ESXi transport node is in 'Validation Error' state

Products

VMware NSX

Issue/Introduction

ESXi transport node preparation fails with Validation error in NSX.
Issue occurs after adding a new ESXi host to the vSphere cluster.
Trying to prepare the host manually with the same transport node profile fails with error suggesting the uplink teaming policy name/s is/are not specified in the Transport Node's attached uplink profile.

Error looks similar to the screenshot below:

Error: The uplink teaming policy name/s [[##-Uplink2, ##-Uplink1]] is/are not specified in the TranportNode's attached uplink profile [BaseHostSwitchProfile/#######-####-####-####-##########]. (Error code: 8516)

In the NSX Manager log location /var/log/proton/nsxapi.log, it reports the error similar as below

ERROR http-nio-127.0.0.1-7440-exec-24 SwitchingValidator 4316 SWITCHING [nsx@6876 comp="nsx-manager" errorCode="MP8516" level="ERROR" reqId="ffb####c-####-####9c56-########" subcomp="manager" username="admin"] The uplink teaming policy name/s [[##-Uplink2, ##-Uplink1]] is/are not specified in theTranportNode's attached uplink profile [BaseHostSwitchProfile/d1####b-####-####-####-bca05####801].

WARN http-nio-127.0.0.1-7440-exec-24 PolicyResourceChangeNotificationManager 4316 POLICY [nsx@6876 comp="nsx-manager" level="WARNING" reqId="ffb####c-####-####9c56-########" subcomp="manager" username="admin"] Failure received invoking listener TransportNodeListener for change CREATING on resource /infra/sites/default/enforcement-points/default/host-transport-nodes/esxi-host1.domain.com
com.vmware.nsx.management.switching.common.exceptions.SwitchingException: null
        at com.vmware.nsx.management.switching.common.SwitchingValidator.validateNamedTeamings(SwitchingValidator.java:2035) ~[?:?]
        at com.vmware.nsx.management.switching.infrastructure.service.TransportNodeServiceImpl.validateTransportNodeNamedTeamings(TransportNodeServiceImpl.java:2405) ~[?:?]
        at com.vmware.nsx.management.switching.infrastructure.service.TransportNodeServiceImpl.validateTNCreation(TransportNodeServiceImpl.java:463) ~[?:?]
        at com.vmware.nsx.management.switching.infrastructure.service.TransportNodeServiceImpl.validateTNCreationUfo(TransportNodeServiceImpl.java:6524) ~[?:?]
        at com.vmware.nsx.management.lcm.transportnode.service.TransportNodeLcmServiceImpl.validateHostTransportNodeCreateUfo(TransportNodeLcmServiceImpl.java:621) ~[?:?]
        at com.vmware.nsx.management.lcm.transportnode.service.TransportNodeListener.preCreate(TransportNodeListener.java:87) ~[?:?]
        at com.vmware.nsx.management.lcm.transportnode.service.TransportNodeListener.handleResourceChange(TransportNodeListener.java:139) ~[?:?]

Reinstalling NSX generates following error -
var/log/proton/nsxapi.log

INFO task-executor-1-21 TransportNodeProfileUtilImpl 76940 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Record validation error in TNC for discovered node ####-####-####-####:host-#### message : The uplink teaming policy name/s [[####-teaming-policy, ####-teaming-policy]] is/are not specified in the TranportNode's attached uplink profile [BaseHostSwitchProfile/####].


WARN task-executor-1-9 TransportNodeProfileUtilImpl 76940 FABRIC [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] Create or update TN failed for discovered node ####-####-####-####:host-#### with ErrorId NsxSwitching service:8516 AND message The uplink teaming policy name/s [[####-teaming-policy, ####-teaming-policy]] is/are not specified in the TranportNode's attached uplink profile [BaseHostSwitchProfile/####].

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware NSX

Cause

This issue occurs when the uplink profile assigned to the host switch does not include the named teaming policies referenced in the Transport Zones.
Check System > Fabric > Transport Zones for Uplink profile attached to transport zone.

Resolution

This is a condition that may occur in a VMware NSX environment.

To resolve the issue, ensure that the named teaming policies defined in the transport zone match with those configured in the transport node's uplink profile.

Additional Information

If the above steps do not resolve the issue, raise a support ticket with Broadcom support selecting NSX as the product.

Handling Log Bundles for offline review with Broadcom support.