MLAG-LACP
Beginning in EXOS 15.3, the EXOS MLAG feature supports Link Aggregation
Control Protocol (LACP) over MLAG ports. To do this, all MLAG peer switches use a common MAC
in the System Identifier portion of the LACPDU transmitted over the MLAG ports. The following
options and requirements are provided:
- The MLAG peer that has the highest IP address for the ISC control
VLAN is considered the MLAG LACP master. The switch MAC of the MLAG LACP master is used as
the System Identifier by all the MLAG peer switches in the LACPDUs transmitted over the
MLAG ports. This is the default option.
- You can configure a common unicast MAC address for use on all the
MLAG peer switches. This MAC address is used as the System Identifier by all the MLAG peer
switches in the LACPDUs transmitted over the MLAG ports. This configuration is not
checkpointed to the MLAG peers, and you must make sure that the same MAC address is
configured on all the MLAG switches. Additionally, you must ensure that this address does
not conflict with the switch MAC of the server node that teams with the MLAG peer
switches.
All the peer MLAG ports have to use the same Actor Key in the LACPDU. As explained above,
the MLAG peer that has the highest IP address for the ISC control VLAN is considered the MLAG
LACP master. The MLAG port will use the Actor Key of the peer MLAG port on the MLAG LACP
master as the Actor Key in the transmitted LACPDUs. The MLAG LACP master has to checkpoint
LACP LAG related information to the other MLAG peer so that the peer knows the Actor Key
information of the MLAG LACP master.

Note
When LACP shared ports are configured as MLAG
ports, a LAG ID change after MLAG peer reboot may result in MLAG ports being removed and
re-added to the aggregator. To avoid the MLAG port flap, it is recommended to configure a
common LACP MAC in both the MLAG peers using the
configure mlag peer
peer_name lacp-maclacp_mac_address command.