# EVPN Rerouting After LAG Member Failures

DevFeed: [EVPN Rerouting After LAG Member Failures](<https://devfeed.tech/articles/evpn-rerouting-after-lag-member-failures-11003.md>)

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

Published: 2024-05-22T06:51:00Z

Content type: opinion

Language: en

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

Topics: [evpn](<https://devfeed.tech/topics/evpn.md>), [networking](<https://devfeed.tech/topics/networking.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [Ethernet](<https://devfeed.tech/topics/ethernet.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [ethernet](<https://devfeed.tech/tags/ethernet.md>), [evpn](<https://devfeed.tech/tags/evpn.md>), [routing](<https://devfeed.tech/tags/routing.md>), [switching](<https://devfeed.tech/tags/switching.md>)

## AI overview

This article examines failover after a LAG member failure in an ESI-based MLAG deployment using EVPN without a peer link. It argues that EVPN changes a local data-plane switchover into a control-plane process involving BGP updates, potentially making convergence much slower.

## Source excerpt

In the previous two blog posts (Dealing with LAG Member Failures, LAG Member Failures in VXLAN Fabrics) we discovered that it's almost trivial to deal with a LAG member failure in an MLAG cluster if we have a peer link between MLAG members. What about the holy grail of EVPN pundits: ESI-based MLAG with no peer link between MLAG members? Read more ...