# ARP Issues in EVPN Centralized Routing Design

DevFeed: [ARP Issues in EVPN Centralized Routing Design](<https://devfeed.tech/articles/arp-issues-in-evpn-centralized-routing-design-11377.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/05/arp-issues-evpn-central-routing/>)

Published: 2026-05-05T05:45:00Z

Content type: article

Language: en

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

Topics: [evpn](<https://devfeed.tech/topics/evpn.md>), [Network](<https://devfeed.tech/topics/network.md>), [IP routing](<https://devfeed.tech/topics/ip-routing.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>)

Tags: [arp](<https://devfeed.tech/tags/arp.md>), [ethernet](<https://devfeed.tech/tags/ethernet.md>), [evpn](<https://devfeed.tech/tags/evpn.md>), [ip-routing](<https://devfeed.tech/tags/ip-routing.md>), [routing](<https://devfeed.tech/tags/routing.md>)

## AI overview

This article examines ARP and traffic-flooding problems in a centralized routing design using EVPN MAC-VRFs. It explains the expected packet flow through a spine switch and describes how implementations that do not advertise VLAN IP/MAC addresses can prevent switches from locating the gateway MAC, causing inter-subnet traffic to be flooded.

## Source excerpt

Adding IRB to a EVPN MAC-VRFs (the fancy way of saying stretched VLANs) seems like a no-brainer: Add IP addresses to VLAN interfaces Optionally add a shared anycast gateway Declare "Mission Accomplished" (and try to ignore the inevitable phone call at 2 AM on a Sunday night) Making that work in a multi-vendor environment is even more fun1, as I sadly discovered when creating the EVPN lab exercises or trying to figure out why some EVPN implementations were failing netlab EVPN integration tests. Read more ...