Form LAG

You can form a LAG using the GUI.

When you form a LAG, it inherits any connectivity templates assigned on the individual links. The LAG is created, but LACP configuration won't be pushed to the device until connectivity templates are applied. When you form a LAG, it inherits any connectivity templates assigned on the individual links.

To form a LAG using the GUI:

  1. From the blueprint, navigate to Staged > Physical > Topology and select the node to add as a member of a LAG. In our example, we've selected leaf3.
    Network management interface screenshot displaying a topology view of nodes, links, racks, and pods with options for physical and virtual management. Tabs include Dashboard, Analytics, Staged, Uncommitted, and Active. The diagram shows spine and leaf switches with connected devices.
    The Topology selection view appears.
  2. From the Neighbors view (default view), select the interface check box to see the operations available for that link (and that you have permissions for).
    Network topology interface showing tabs like Topology, Nodes, Links, and Interfaces. Neighbors tab is selected. Selected rack is evpn_single_001 and node is leaf3 Leaf. Interface xe-0/0/2 is selected, connected to spine1, spine2, and switch3-server1. Operations menu displays options like Form LAG and Update link speed. Red annotation highlights checkbox and operations menu.
  3. Click Form LAG
    The Form LAG dialog opens.
  4. Select the LAG mode:
    • LACP (Active) - actively advertises LACP BPDU even when neighbors do not.
    • LACP (Passive) - doesn't generate LACP BPDU until it sees one from a neighbor.
    • Static LAG (no LACP) - Static LAGs don't participate in LACP and will conditionally operate in forwarding mode.
    User interface for configuring a Link Aggregation Group with options for LAG mode selection including LACP Active, LACP Passive, and Static LAG. Displays link details between leaf3 xe-0/0/2 and switch3-server1, speed 10G, PC ID not available, no tags. Lists applied configuration templates including vn_endpoints_red_vxlan_32_v4_1_vlan_tagged and vn_endpoints_blue_vxlan_31_v4_1_vlan_tagged. Create button available to finalize configuration.
  5. Click Update.

The changes are staged and you're returned to the Topology selection view

When you're ready to activate your changes, go to the Uncommitted tab to review and commit (or discard) your changes.