Example Configuration of LACP on VMware, Cisco, HP, Dell switches
book
Article ID: 324490
calendar_today
Updated On:
Products
VMware vSphere ESXi
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.
Configuring LACP within the vSphere/VMware Infrastructure Client
To configure vSwitch properties for load balancing:
Select the Networking tab in the vCenter Server.
Select the vSphere distributed switch and click LACP.
Note: LACP is only supported in vSphere on Distributed Switches (vDS).
Click +NEW to add a new LAG group.
Select the number of uplinks that will be in the LAG per host.
From the Load Balancing dropdown, select the correct load balancing policy. This will be determined by the physical switch. However, see note below.
Click OK.
Verify that there are adapters listed under Assigned Adapters in the LAG for each host.
Click Actions on the distributed switch.
Follow the wizard until the Manage Physical Adapters section.
Choose the appropriate adapters and ensure that under Uplink they have the LAG listed.
If the LAG is not listed, select Assign Adapter and assign it to the LAG. Select OK and repeat until finished, then finish the wizard.
Note: If the adapters being chosen to move to the LAG are currently in use for a vmkernel such as the management vmkernel, the adapter must be moved over to the LAG in steps- they cannot be moved all at once. See Configuring LACP on an Uplink Port Group for more information. As with any configuration change, this should be done during a maintenance window.
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).
interface Port-channel1 switchport switchport access vlan 100 switchport mode access no ip address ! interface GigabitEthernet1/1 switchport switchport access vlan 100 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)
Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.