Example Configuration of LACP on VMware, Cisco, HP, Dell switches

Products

• VMware vSphere ESXi
• VMware vCenter Server

Issue/Introduction

This article provides information on the concepts, limitations, and some sample configurations of link aggregation, NIC Teaming, Link Aggregation Control Protocol (LACP), and EtherChannel connectivity between ESXi and Physical Network Switches, particularly for Cisco and HP.

Note: There are a number of requirements which need to be considered before implementing any form of link aggregation. For more/related information on these requirements, see Host requirements for link aggregation (etherchannel, port channel, or LACP) in ESXi.

Resolution

Configuring LACP within the vSphere/VMware Infrastructure Client

To be able to utilize NICs that are in/going to be in an LACP configuration on the physical switch there are two main requirements:

1. The environment must use a vDS as a Standard Switches do not support LACP
2. A LAG must be created on the vDS

Please refer to the step by step guide Configuring a LAG on a vSphere Distributed Switch Port Group when using LACP

VMware by Broadcom recommends that the above process be completed during a maintenance window and ensuring both a VMware by Broadcom Network engineer and someone who has access to modify/implement changes to the physical switch settings are present during the above process. 

For more information on LACP in vSphere, see:

• LACP Support on a vSphere Distributed Switch
• Converting to Enhanced LACP Support on a vSphere Distributed Switch

EtherChannel/LACP supported scenarios

• One IP to many IP connections. (Host A making two connection sessions to Host B and C).
• Many IP to many IP connections. (Host A and B multiple connection sessions to Host C, D, etc)
  
  Note: One IP to one IP connections over multiple NICs is not supported. (Host A one connection session to Host B uses only one NIC).
   
• Compatible with all ESXi VLAN configuration modes: VST, EST, and VGT.
• Supported Cisco configuration: EtherChannel Mode ON – ( Enable EtherChannel only).
• Supported HP configuration: Trunk Mode.
• Supported switch Aggregation algorithm: IP-SRC-DST, for example (short for IP-Source-Destination).
• Supported Virtual Switch NIC Teaming mode to match the physical switch load balancing algorithm.
  • For information on the load balancing algorithm the physical switch uses, please refer to the physical switch vendor.
• Lower model Cisco switches may have MAC-SRC-DST set by default, and may require additional configuration. For more information, see the Understanding EtherChannel Load Balancing and Redundancy on Catalyst Switches article from Cisco.

Configuring Virtual Switches with an EtherChannel (port channel)

To utilize NICs that are in an EtherChannel configuration on the physical switch please refer to the following articles for more detailed information:

• Configure Virtual Switch with an EtherChannel (or port channel)
• Route Based on IP Hash
  • vSwitch (Standard Switches) teaming Load balancing change to port id after ESXi 7.0.3l update

Cisco EtherChannel sample configuration

interface Port-channe##
switchport
switchport access vlan ###
switchport mode access
no ip address
!
interface GigabitEthernet1/1
switchport
switchport access vlan ###
switchport mode access
no ip address
channel-group 1 mode on
!

Run this command to verify EtherChannel load balancing mode configuration:

show etherchannel load-balance
EtherChannel Load-Balancing Configuration:
src-dst-ip
mpls label-ip
EtherChannel Load-Balancing Addresses Used Per-Protocol:
Non-IP: Source XOR Destination MAC address
IPv4: Source XOR Destination IP address
IPv6: Source XOR Destination IP address
MPLS: Label or IP

show etherchannel summary
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
M - not in use, minimum links not met
u - unsuitable for bundling
w - waiting to be aggregated
Number of channel-groups in use: 2
Number of aggregators: 2
Group Port-channel Protocol Ports
------+-------------+-----------+--------------------------
1 Po1(SU) - Gi1/15(P) Gi1/16(P)
2 Po2(SU) - Gi1/1(P) Gi1/2(P)

Switch# show etherchannel protocol
Channel-group listing:
-----------------------
Group: 1
----------
Protocol: - (Mode ON)
Group: 2
----------
Protocol: - (Mode ON)

HP EtherChannel sample configuration

This configuration is specific to HP switches:

• HP switches support only two modes of LACP:
  • ACTIVE
  • PASSIVE
    
    Note: LACP is only supported in vSphere with vSphere Distributed Switches.
     
• Set the HP switch port mode to TRUNK to accomplish static link aggregation with ESXi.
• TRUNK Mode of HP switch ports is the only supported aggregation method compatible with ESXi NIC teaming mode IP hash.

To configure a static port channel in an HP switch using ports 10, 11, 12, and 13, run this command:

conf
trunk 10-13 Trk1 Trunk

To verify the port channel, run this command:

show trunk
Load Balancing
Port | Name Type | Group Type
---- + --------- + ----- -----
10 | 100/1000T | Trk1 Trunk
11 | 100/1000T | Trk1 Trunk
12 | 100/1000T | Trk1 Trunk
13 | 100/1000T | Trk1 Trunk
 

Dell EtherChannel sample configuration:

How to create Link Aggregation Groups (LAGs) on Dell Networking PowerConnect Switches

Additional Information

• If using vSAN then it would be advised to consult the vSAN design guide before implementing LAG or LACP. In particular it would be advised to check the section on 'Advanced NIC Teaming', which includes some example configurations:

https://techdocs.broadcom.com/us/en/vmware-cis/vsan/vsan/8-0/vsan-network-design/advanced-nic-teaming.html