ESXi transport node is in Validation error in NSX

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 the same error
Error: The uplink teaming policy name/s [[##-Uplink2, ##-Uplink1]] is/are not specified in the TranportNode's attached uplink profile [BaseHostSwitchProfile/#######-####-####-####-##########]. (Error code: 8516)
Error looks similar to the screenshot below
nsxapi.log in the nsx manager log reports the error similar to the below

2025-07-30T05:37:40.616Z 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" user
name="admin"] The uplink teaming policy name/s [[##-Uplink2, ##-Uplink1]] is/are not specified in theTranportNode's attached uplink profile [BaseHostSwitchProfile/d1####b-####-####-####-bca05####801].
2025-07-30T05:37:40.616Z 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" use
rname="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) ~[?:?]

Environment

NSX 3.2.2.0

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.

Resolution

To resolve the issue, ensure that the named teaming policies defined in the transport zone match 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.