In Cisco Application Policy Infrastructure
Controller (APIC) Release 3.2(7), you can improve uplink load balancing by applying different Link Aggregation Control Protocol (LACP)
policies to different distributed virtual switch (DVS) uplink port groups.
Cisco APIC now supports VMware's Enhanced LACP feature, which is available for DVS 5.5 and later. Previously, the same LACP policy applied
to all DVS uplink port groups. Before Cisco APIC Release 3.2(7), it was not possible to manage VMware link aggregation groups (LAGs) with Cisco APIC.
When you enable Enhanced LACP policy on the ACI side, it will push the configuration to DVS. Later, even if you remove the
policy on the ACI side, enhanced LACP is still available on the DVS side, because after an enhanced LACP policy is enabled,
it can not be reverted.
Enhanced LACP policy can be enabled either on the ACI or DVS side.
You can choose from up to 20 different load-balancing algorithms when you create a VMware vCenter virtual machine manager
(VMM) domain for Cisco Application Centric Infrastructure
(ACI) Virtual Edge or VMware VDS. You apply different policies to different uplink portgroups.
You have eight DVS uplink portgroups, and you must configure at least two uplinks in the same policy. So you can have up to
four different LACP policies for each DVS. Enhanced LACP supports only active and passive LACP modes.
For Cisco ACI Virtual Edge VXLAN mode, it is mandatory to use a load-balancing algorithm having a UDP port. We recommend the algorithm Source and Destination TCP/UDP Port. In VLXAN mode, traffic is always sent between VTEP to the FTEP IP. So communication is always between one pair of IP address.
So for VXLAN traffic, the only way to distinguish traffic is using the UDP port number.
The following sections provide instructions for configuring multiple LACP policies for DVS uplinks using the Cisco APIC GUI, NX-OS style CLI, or REST API.