Transport Nodes with TNP (Transport Node Profile) shows the following Validation errors: "The uplink teaming policy names are not specified in the TransportNode's attached uplink profile"

Products

• VMware NSX

Issue/Introduction

• We can see the validation error on the Transport Node Cluster: 

ERROR 8516: The uplink teaming policy name/s [[####, #####, #####]] is/are not specified in the TransportNode's attached uplink profile [BaseHostSwitchProfile/####-######--######-######]

• If we remove the TNP from the cluster, the transport node status is in success state, but with TNP all the transport nodes status shows Validation errors with the same above error. This will confirm that TNP (and its configuration) is causing the issue
• Named Teaming Profile has been added to TZ  and it does not exist in the Uplink Profile which is using this TZ.

Environment

VMware NSX

Cause

 

• Named Teaming Policy is only applicable to VLAN segments/logical switches.  Uplink Profile only supports the Failover Teaming Policy
• This issue can occur if Uplink Profile does not have the Named Teaming Policies that are defined in VLAN Transport Zone which is attached to Transport Node Profile. 

Resolution

Steps to resolve:

1. Define the uplink Named Teaming Policies in the Uplink Profile  which are selected in the Transport Zone attached to the TNP
2. Make sure to have active uplinks selected for any Teaming Policies that are defined

Additional Information

VM connected to a VLAN segment intermittently starts choosing wrong uplink to send the traffic despite the named teaming policy configured

VMware Doc - TN failed as named teaming defined with no active uplinks

 Configure Named Teaming Policy