This article provides information on enabling and disabling link aggregation, NIC Teaming, Link Aggregation Control Protocol (LACP), and EtherChannel connectivity between ESXi/ESX and Physical Network Switches.
Note: There are a number of requirements which need to be considered before implementing any form of link aggregation.
For more information on these requirements, see Host requirements for link aggregation (etherchannel, port channel, or LACP) in ESXi (324555).
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x
To remove EtherChannel, there must only be one active network adapter on the vSwitch/dvSwitch. Ensure that the other host NICs in the EtherChannel configuration are disconnected (Link Down). Perform one of these options:
With only a single network card online, remove the portchannel configuration from the physical network switch and change the network teaming settings on the vSwitch/dvSwitch from IP HASH to portID.
For more information about teaming, see NIC teaming in ESXi and ESX and process to configure (315432).
Note: Both adding and removing a host from an LACP configuration can be complicated process, especially if the management vmkernel is using the LACP uplink group. There is a chance for network disruption due to this complication.
Configuring LACP on a vSphere Distributed Switch Port Group (312554)
Host requirements for link aggregation (etherchannel or port channel) for ESXi and ESX (324555)
Converting to Enhanced LACP Support on a vSphere Distributed Switch- "Source vCenter Server has instance(s) of Distributed Virtual Switch at unsupported lacpApiVersion" (318706)
Link aggregation concepts:
VMware Skyline Health Diagnostics for vSphere - FAQ (345059)
Host requirements for link aggregation for ESXi and ESX (324555)
VLAN configuration on virtual switches, physical switches, and virtual machines (311764)
NIC teaming in ESXi and ESX (315432)
Forcing a link state up or down for a vmnic interface on ESXi (324496)
Configuring LACP on an Uplink Port Group using the vSphere Web Client (312544)
Impact/Risks:
As with any networking change, there is a chance for network disruption so a maintenance period is recommended for changes. This is especially true on a vSphere Distributed Switch (vDS) because the Distributed Switch is owned by vCenter and the hosts alone cannot make changes to the vDS if connection to vCenter is lost. Enabling LACP can greatly complicate vCenter or host management recovery in production down scenarios, because the LACP connection may need to be broken to move back to a Standard Switch if necessary (since LACP is not supported on a Standard Switch).