Network connectivity fails on a new Distributed Port Group when VDS is configured with LACP

Products

• VMware vSphere ESXi
• VMware vCenter Server

Issue/Introduction

Virtual machines connected to a newly created Distributed Port Group cannot communicate with the network. This issue occurs on a vSphere Distributed Switch where a Link Aggregation Group (LAG) is configured. The problem persists even if the VLAN ID and guest OS IP settings are correct.

Environment

VMware vCenter Server 7.x
VMware vCenter Server 8.x

VMware ESXi 7.x
VMware ESXi 8.x

Cause

When a new Distributed Port Group is created using the default settings on a VDS with LACP, the Teaming and failover policy may automatically default to using individual uplinks (e.g., Uplink 1, Uplink 2) instead of the configured LAG interface (e.g., lag1). In a LACP configuration, port groups must utilize the LAG interface to handle traffic correctly. Because the default creation process does not always automatically select the LAG interface, the port group may be inadvertently configured with individual uplinks, which is an invalid configuration when those uplinks are part of a LAG.

Resolution

Configure the Distributed Port Group to use the LAG interface as the only active uplink.

1. Log in to the vSphere Client.

2. Navigate to the Networking inventory and select the affected Distributed Port Group.

3. Select Edit Settings and go to the Teaming and failover section.

4. Move the individual uplinks (e.g., Uplink 1, Uplink 2) down to the Unused uplinks category.

5. Move the LAG interface (e.g., lag1) up to the Active uplinks category.

6. Click OK to save the configuration.

Additional Information

Japanese version: LACP 構成済みの分散スイッチで新規ポートグループの通信ができない(428332)