Cisco Nexus LAG supportability with "no lacp suspend-individual"

Products

• VMware vSphere ESXi

Issue/Introduction

This KB addresses the supportability of using the "no lacp suspend-individual" option with DVS LAG:

• Default Behavior (suspend-individual): If a physical port in a Link Aggregation Group (LAG) does not receive Link Aggregation Control Protocol (LACP) Protocol Data Units (PDUs) from the opposite side, the switch places that port into a suspended state, effectively shutting it down from the LAG.

• "no lacp suspend-individual" (or equivalent): This command forces the port to remain active and operate as a standalone link, even if it is not fully bundled in the LAG.

• Common Use Case: A frequent scenario for using the no suspend-individual command is during Server Provisioning. Issuing this command allows servers to obtain an IP address via DHCP/PXE before their operating system fully loads and starts sending LACP packets, which ensures initial connectivity.

Environment

VMware vSphere ESXi

VMware Cloud Foundation

Resolution

VMware vSphere DVS LAGs support the "no lacp suspend-individual"  behavior.

Additional Information

If additional assistance is needed with troubleshooting, reach out to Broadcom support by creating a support case using the instructions at Creating and managing Broadcom support cases.

ESXi Uplinks in "Stand-alone" State Due to LACP Negotiation Failure.

ESXi Host lost Network Connectivity After 7.x to 8.0 Upgrade Due to Legacy vDS LACP Mismatch.