# MLAG Deep Dive: Dealing with LAG Member Failures

DevFeed: [MLAG Deep Dive: Dealing with LAG Member Failures](<https://devfeed.tech/articles/mlag-deep-dive-dealing-with-lag-member-failures-11004.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2024/05/mlag-lag-member-rerouting/>)

Published: 2024-05-09T06:12:00Z

Content type: tutorial

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [networking](<https://devfeed.tech/topics/networking.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>)

Tags: [blog-post](<https://devfeed.tech/tags/blog-post.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [deep-dive](<https://devfeed.tech/tags/deep-dive.md>), [failover](<https://devfeed.tech/tags/failover.md>), [switching](<https://devfeed.tech/tags/switching.md>)

## AI overview

This article explains how traditional MLAG clusters using a peer link reroute traffic after an MLAG member link fails. It describes forwarding changes on the surviving switches, handling of unicast and BUM traffic, and the localized nature of the failure.

## Source excerpt

Craig Weinhold pointed me to a complex topic I managed to ignore in my MLAG Deep Dive series: how does an MLAG cluster reroute around a failure of a LAG member link? In this blog post, we'll focus on traditional MLAG cluster implementations using a peer link; another blog post will explore the implications of using VXLAN and EVPN to implement MLAG clusters. We'll also ignore the interesting question of "how is the LAG member link failure detected?"1 and focus on "what happens next?" using the sample MLAG topology: Read more ...