Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Form LAG

Release: Juniper Apstra 4.1
{}
Change Release
date_range 30-May-23
It’s common to break a LAG towards a server into individual links, then reform the LAG from individual links, all while keeping the same VLAN allocation (when re-bootstrapping the server for example). When you form a LAG, it inherits any connectivity templates assigned on the individual links (as of Apstra version 4.1.0).
  1. From the blueprint, navigate to Staged > Physical > Topology and select the node to add as a member of a LAG.
  2. Select the interface check box to see the operations available for that interface (and that you have permissions for).
  3. Click Form LAG and 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.
  4. Click Update to stage your changes and return to the Topology view.
    The LAG is created, but LACP configuration won't be pushed to the device until connectivity templates are applied.

When you're ready to activate your changes, commit them from the Uncommitted tab.

footer-navigation