In such case where keepalive packets are not received the slave shuts down its MLAG interfaces and the master becomes a standalone switch in order to avoid misalignment in MLAG configuration. To avoid a scenario where failure on the IPL causes both MLAG peers to assume that their peer has failed, a safety mechanism is maintained based on UDP packets running via the management plane which alerts both MLAG switches that its peer is alive. In such a case, the remaining active switch begins to act as a standalone switch and assumes that its previously peering MLAG switch has failed. If the keepalive message fails to arrive for three consecutive intervals the switches break into two standalone switches.

The MLAG pair of switches periodically exchanges a keepalive message on a user configurable interval.

MLAG master/slave roles take effect in fault scenarios such as split-brain, peer faults, and during software upgrades. Layer-3 failure – serves redundancy in case of a failed connection between the MLAG switches and the rest of the 元 network should there be one.MLAG port failure – serves redundancy in case of a fallen link on one of the MLAG switches.MLAG protocol control – keepalive messages, MAC sync, MLAG port sync, etc.The figure in section ”Configuring MLAG” illustrates this. In such a case, PFC must be configured on this IPL. The IPL itself can be a LAG and may be constructed of links of any supported speed. Thus, the bandwidth of the IPL should be defined accordingly.

The MLAG switches share an inter-peer link (IPL) between them for carrying control messages in a steady state or data packages in failure scenarios. MLAG port-channel VLAN membership, static MAC, ACL, etc).Ī peered device (host or switch) connecting to switches running an MLAG runs a standard LAG and is unaware of the fact that the LAG connects to two separate switches. Each switch configuration is independent and it is user responsibility to make sure to configure both switches similarly pertaining MLAG (e.g.

Software lag switch rack