Selecting a teaming policy with prepared VMware NSX for vSphere 6.x clusters
search cancel

Selecting a teaming policy with prepared VMware NSX for vSphere 6.x clusters

book

Article ID: 339047

calendar_today

Updated On:

Products

VMware NSX Networking

Issue/Introduction

Virtual machine traffic is being sent out of a dvUplink which does not have a VTEP (VXLAN Tunnel Endpoint) assigned to it. The teaming policy of the VTEP vmknic port-group and all logical switch port-groups must match to ensure they use the same set of uplinks, including failover order. In addition, for teaming policies other than Etherchannel/LACP, the number of VTEP interfaces on each host must equal the number of active dvUplinks in the teaming policy to ensure that there is a VTEP assigned to and available for encapsulating traffic on each dvUplink.


Symptoms:
  • Intermittent and random network connection failures are seen between virtual machines across logical switches
  • If the VTEP vmknic port-group is configured to use a single vNIC, connections succeed


Environment

VMware NSX for vSphere 6.1.x
VMware NSX for vSphere 6.0.x

Cause

Resolution

This is by design. The teaming policy cannot be changed after the NSX cluster is prepared.

Note: vCenter Server accepts a new value for the teaming policy in the UI, but the policy is not validated by NSX and new hosts/logical switch portgroups does not use the new values.

For more information on teaming mode descriptions, see NIC teaming in ESXi and ESX (1004088) and the Teaming Policy for Virtual Distributed Switches section in the NSX for vSphere Installation and Upgrade Guide.