LACP support

  • a VMware plugin must be running
  • a deployment mapping to the participating vCenter must exist
You can integrate the functionality of LACP LAGs in vCenter by configuring the underlying fabric in response to changes in vCenter.
  1. Create an LACP LAG on the DVS in vCenter. Specify parameters for the LAG, including:
    • LAG name
    • number of LAG members
    • LAG mode and load balancing mode
    Note: This does not trigger any action in the VMware plugin.
  2. Ensure that the LAG exists on the Fabric Services System fabric and that its members map to the correct SubHostPorts in Connect.
  3. Attach the preferred host NICs to the preferred LAG members.
    The VMware plugin will use this information to determine the correct SRL Leaf ports for when the LACP LAG is used as an uplink for a Port Group.
  4. Create one or more Port Groups on the distributed vSwitch and use the LACP LAG as the Active uplink.
    The VMware plugin will use the Connect service to provision the Leaf switches with the appropriate network connectivity for the Port Groups.
Sub-Interfaces corresponding to the LAG members are automatically created in the appropriate Subnets in the Fabric Services System.
Note:
  • To get LLDP information from vCenter, ensure that the discovery protocol in the distributed vSwitch advanced settings is set to Link Layer Discovery Protocol, and the operation is either advertise or both.
  • The total number of LAG members and individual uplinks per distributed vSwitch cannot exceed 32.