# Multi-Pod EVPN Troubleshooting: Route Targets

DevFeed: [Multi-Pod EVPN Troubleshooting: Route Targets](<https://devfeed.tech/articles/multi-pod-evpn-troubleshooting-route-targets-11277.md>)

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

Published: 2025-11-25T05:49:00Z

Content type: article

Language: en

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

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

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

## AI overview

This fourth post in a Multi-Pod EVPN troubleshooting series explains why LA does not recognize LB as a remote VTEP after BGP next hops are corrected. The cause is a mismatch between the route target exported by LB and the route target imported by LA. The post presents adding remote import route targets or configuring consistent import and export route targets across autonomous systems as fixes.

## Source excerpt

Last week, we fixed the incorrect BGP next hops in our sample multi-pod EVPN fabric. With that fixed, every PE device should see every other PE device as a remote VTEP for ingress replication purposes. However, that's not the case; let's see why and fix it. Note: This is the fourth blog post in the Multi-Pod EVPN series. If you stumbled upon it, start with the design overview and troubleshooting overview posts. More importantly, familiarize yourself with the topology we'll be using; it's described in the Multi-Pod EVPN Troubleshooting: Fixing Next Hops. Ready? Let's go. Here's our network topology: Read more ...