<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/troubleshooting-multi-pod-evpn-overview-ipspace-net-blog-3ogyydhi2" -->

---
title: Troubleshooting Multi-Pod EVPN: Overview « ipSpace.net blog
description: A structured troubleshooting approach for multi-pod EVPN environments where VTEPs cannot reach each other across pods. The divide-and-conquer strategy starts...
canonical: https://daily.dev/posts/troubleshooting-multi-pod-evpn-overview-ipspace-net-blog-3ogyydhi2
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Troubleshooting Multi-Pod EVPN: Overview « ipSpace.net blog | daily.dev
og:description: A structured troubleshooting approach for multi-pod EVPN environments where VTEPs cannot reach each other across pods. The divide-and-conquer strategy starts...
og:url: https://daily.dev/posts/troubleshooting-multi-pod-evpn-overview-ipspace-net-blog-3ogyydhi2
og:image: https://api.daily.dev/og/posts/3OgYYDhi2.png
og:image:alt: Troubleshooting Multi-Pod EVPN: Overview « ipSpace.net blog
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting Multi-Pod EVPN: Overview « ipSpace.net blog

**[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 3 min read · 0 upvotes · 0 comments

## Summary

A structured troubleshooting approach for multi-pod EVPN environments where VTEPs cannot reach each other across pods. The divide-and-conquer strategy starts by treating VXLAN/EVPN as an application over IP: first verify underlay connectivity using VTEP-to-VTEP pings with correct VXLAN packet sizes, then check for firewalls blocking UDP. If the underlay is healthy, move to the overlay: verify EVPN route propagation (type-2 and type-3 routes), check BGP sessions and address families, validate next-hop processing on EBGP sessions, and compare working vs. problematic routes to identify missing configuration knobs, vendor compatibility issues, or bugs.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blog.ipspace.net/2025/10/troubleshoot-multi-pod-evpn>

## Questions this post answers

### How do I troubleshoot EVPN when VTEPs cannot reach each other across pods in a multi-pod fabric?

Start by separating underlay from overlay problems. Ping remote VTEPs from the local VTEP IP using the packet size needed for VXLAN-encapsulated Ethernet frames — a failure points to an IP underlay issue. If pings succeed, move to the overlay: check whether expected EVPN type-2 and type-3 routes are propagated between PE-devices, verify BGP sessions and activated address families, and confirm next-hop processing on EBGP sessions is correct.

_Engineers debugging multi-pod EVPN fabrics track related issues and fixes on daily.dev._

### How can I tell if a firewall is blocking VXLAN UDP traffic but passing ICMP in an EVPN underlay?

Use UDP-based pings to detect firewalls that pass ICMP but silently drop UDP. On Linux, netcat can send UDP probes. Checking the actual VXLAN UDP port is harder unless the device supports a dedicated VXLAN ping command, which is uncommon on most network OS platforms outside of Linux-based ones.

_Network engineers dealing with subtle VXLAN underlay issues share findings like these on daily.dev._

## Similar posts on daily.dev

- [EVPN with SR-MPLS Core « ipSpace.net blog](https://daily.dev/posts/evpn-with-sr-mpls-core-ipspace-net-blog-taobtibzc) · ipSpace.net Blog · 0 upvotes · 0 comments

---

Tags: [#bgp](https://daily.dev/tags/bgp)

[View this post on daily.dev](https://daily.dev/posts/troubleshooting-multi-pod-evpn-overview-ipspace-net-blog-3ogyydhi2)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Troubleshooting Multi-Pod EVPN: Overview « ipSpace.net blog","url":"https://daily.dev/posts/troubleshooting-multi-pod-evpn-overview-ipspace-net-blog-3ogyydhi2","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/troubleshooting-multi-pod-evpn-overview-ipspace-net-blog-3ogyydhi2"},"datePublished":"2026-08-11T08:56:01.200Z","dateModified":"2026-08-11T09:34:11.004Z","description":"A structured troubleshooting approach for multi-pod EVPN environments where VTEPs cannot reach each other across pods. The divide-and-conquer strategy starts...","image":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","thumbnailUrl":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","isAccessibleForFree":true,"articleSection":"ipSpace.net Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ipSpace.net Blog","logo":"https://media.daily.dev/image/upload/s--xS7E82MT--/f_auto,q_auto/v1786438303/logos/ipspace?_a=BAMAMicg0","url":"https://daily.dev/sources/ipspace"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/troubleshooting-multi-pod-evpn-overview-ipspace-net-blog-3ogyydhi2","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp","timeRequired":"PT3M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ipSpace.net Blog","item":"https://daily.dev/sources/ipspace"},{"@type":"ListItem","position":3,"name":"Troubleshooting Multi-Pod EVPN: Overview « ipSpace.net blog"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/troubleshooting-multi-pod-evpn-overview-ipspace-net-blog-3ogyydhi2#faq","mainEntity":[{"@type":"Question","name":"How do I troubleshoot EVPN when VTEPs cannot reach each other across pods in a multi-pod fabric?","acceptedAnswer":{"@type":"Answer","text":"Start by separating underlay from overlay problems. Ping remote VTEPs from the local VTEP IP using the packet size needed for VXLAN-encapsulated Ethernet frames — a failure points to an IP underlay issue. If pings succeed, move to the overlay: check whether expected EVPN type-2 and type-3 routes are propagated between PE-devices, verify BGP sessions and activated address families, and confirm next-hop processing on EBGP sessions is correct. Engineers debugging multi-pod EVPN fabrics track related issues and fixes on daily.dev."}},{"@type":"Question","name":"How can I tell if a firewall is blocking VXLAN UDP traffic but passing ICMP in an EVPN underlay?","acceptedAnswer":{"@type":"Answer","text":"Use UDP-based pings to detect firewalls that pass ICMP but silently drop UDP. On Linux, netcat can send UDP probes. Checking the actual VXLAN UDP port is harder unless the device supports a dedicated VXLAN ping command, which is uncommon on most network OS platforms outside of Linux-based ones. Network engineers dealing with subtle VXLAN underlay issues share findings like these on daily.dev."}}]}
```

