Configuration of Link Aggregation Control Protocol (LACP) with Vmware ESXi/ESX and Dell Switches

12/06/2018

Description:

This article provides information on the concepts, limitations, and a sample configuration of link aggregation between ESXi host and a Dell switch which supports VLT (Virtual Link Trunk), i.e. setting up NIC Teaming on the ESXi host and Link Aggregation Control Protocol (LACP) on the Physical Network Dell Switches

LACP or IEEE 802.3ad: The Link Aggregation Control Protocol (LACP) is included in IEEE specification as a method to control the bundling of several physical ports together to form a single logical channel.

ESXi/ESX host only supports NIC teaming when connected to a single physical switch, stacked switches, or switches combined via VLT (Virtual Link Trunk). This means that the links on the ESXi host are teamed and appear as one from switch perspective. Switches combined into a stack or VLT appear as one switch to the ESXi host. Link aggregation is never supported between separate trunked switches.

Note: LACP is only supported in vSphere 5.1 and 5.5 or later with vSphere Distributed Switches

Configuring load balancing within the vSphere/VMware Client

To configure vSwitch properties for load balancing:

Click the ESXi/ESX host.
Click the Configuration tab.
Click the Networking link.
Click Properties.
Click the virtual switch in the Ports tab and click Edit.
Click the NIC Teaming tab.
From the Load Balancing dropdown, choose Route based on ip hash.
Verify that there are two or more network adapters listed under Active Adapters.

Do not configure standby or unused uplinks with IP HASH load balancing.

2. Configuration for LACP port channel on the switch side, where the two switches A and B are configured in a VLT.

In the below example vmnic2 is connected to port 0/41 on Switch A and vmnic 3 is connected to port 0/41 on Switch B. Switch A and switch B have exactly the same configuration as below.

Vlt-peer-lag refers to the port channel number on the peer switch.