# Troubleshooting Multi-Pod EVPN: Overview

DevFeed: [Troubleshooting Multi-Pod EVPN: Overview](<https://devfeed.tech/articles/troubleshooting-multi-pod-evpn-overview-11270.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2025/10/troubleshoot-multi-pod-evpn/>)

Published: 2025-10-09T06:27:00Z

Content type: tutorial

Language: en

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

Topics: [evpn](<https://devfeed.tech/topics/evpn.md>), [VXLAN](<https://devfeed.tech/topics/vxlan.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [evpn](<https://devfeed.tech/tags/evpn.md>), [network](<https://devfeed.tech/tags/network.md>), [overview](<https://devfeed.tech/tags/overview.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>), [vxlan](<https://devfeed.tech/tags/vxlan.md>)

## AI overview

This troubleshooting guide explains how to isolate multi-pod EVPN connectivity problems by first testing IP reachability between VTEPs, including packet sizes needed for VXLAN encapsulation. It then separates underlay, firewall, EVPN route propagation, next-hop processing, and implementation or compatibility issues.

## Source excerpt

An engineer reading my multi-pod EVPN article asked an interesting question: How do you handle troubleshooting when VTEPs cannot reach each other across pods? The ancient Romans already knew the rough answer: divide and conquer. In this particular case, the "divide" part starts with a simple realization: VXLAN/EVPN is just another application running on top of IP. Read more ...