NSX can't configure static LAG

Products

• VMware NSX

Issue/Introduction

• A static LAG is configured on the physical switch.
• The teaming policy on the vSphere Distributed Switch (VDS) is set to "Route based on IP hash" in vCenter.
• Distributed port groups operate as expected with this configuration.
• When configuring NSX to use the same static LAG, the NSX uplink profile does not provide "Route based on IP hash" as an available teaming policy.
• Selecting any of the other available teaming policies in the NSX uplink profile results in communication issues for NSX segments.

Environment

VMware NSX-T

VMware NSX

Cause

NSX does not support static LAG.

Resolution

• Configure a dynamic LAG (LACP) on both, physical switches and the vSphere Distributed Switch (VDS).
• NSX uplink profile can utilize LAG created on DVS.
• If using dynamic LAG (LACP) is not feasible, it is recommended to avoid using static LAG, as it is not supported by NSX.