<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/more-arista-eos-bgp-route-reflector-woes-ipspace-net-blog-uaebo69fr" -->

---
title: More Arista EOS BGP Route Reflector Woes « ipSpace.net blog
description: Arista EOS has a quirk where the global `neighbor next-hop-self` command affects EVPN address family processing, causing route reflectors to silently drop EVPN...
canonical: https://daily.dev/posts/more-arista-eos-bgp-route-reflector-woes-ipspace-net-blog-uaebo69fr
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: More Arista EOS BGP Route Reflector Woes « ipSpace.net blog | daily.dev
og:description: Arista EOS has a quirk where the global `neighbor next-hop-self` command affects EVPN address family processing, causing route reflectors to silently drop EVPN...
og:url: https://daily.dev/posts/more-arista-eos-bgp-route-reflector-woes-ipspace-net-blog-uaebo69fr
og:image: https://api.daily.dev/og/posts/uAEBO69fR.png
og:image:alt: More Arista EOS BGP Route Reflector Woes « 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.

# More Arista EOS BGP Route Reflector Woes « ipSpace.net blog

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

## Summary

Arista EOS has a quirk where the global `neighbor next-hop-self` command affects EVPN address family processing, causing route reflectors to silently drop EVPN updates because the next hop is changed to the spine switch (which lacks VXLAN interfaces). The `bgp route-reflector preserve-attributes` command does not fix this for EVPN. The workaround is removing `next-hop-self` globally and using a route map that sets the next hop only for EBGP-learned routes. A follow-up note confirms that Arista EOS 4.29.0F added per-address-family `next-hop-self` support for IPv4 and IPv6 unicast, partially resolving the issue.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blog.ipspace.net/2022/10/arista-route-reflector-woes>

## Questions this post answers

### Why is my Arista EOS BGP route reflector not sending EVPN routes between leaf switches when next-hop-self is configured?

When `neighbor next-hop-self` is configured globally in Arista EOS, it also applies to the EVPN address family, changing the next hop to the spine/route-reflector. Because the spine lacks VXLAN interfaces to handle that traffic, it suppresses the reflected EVPN updates entirely. The `bgp route-reflector preserve-attributes` command does not override this for EVPN. Removing `next-hop-self` globally restores EVPN route reflection.

_Engineers debugging EVPN fabric issues on Arista track fixes like the 4.29.0F per-AF next-hop-self support on daily.dev._

### How do I fix next-hop-self breaking EVPN on an Arista EOS route reflector while still changing next hops for IBGP+EBGP IPv4 routes?

Use a route map instead of the global `next-hop-self` command. Configure a route map that matches external (EBGP) routes and sets the next hop to the peer address, with a second permit entry to pass all other routes unchanged. Apply this route map as an outbound policy on IBGP neighbors in the IPv4 address family. This avoids the global next-hop-self affecting EVPN.

_Networking engineers solving Arista BGP edge cases share workarounds like this on daily.dev._

### Does Arista EOS support per-address-family next-hop-self configuration for BGP?

Yes, starting with EOS release 4.29.0F, `neighbor next-hop-self` can be configured within IPv4 and IPv6 unicast address families. Prior to this release, next-hop-self was only configurable at the global BGP neighbor level, causing it to unintentionally affect EVPN address family processing on route reflectors.

_Arista EOS release notes and their impact on BGP fabric designs surface regularly for networking engineers on daily.dev._

## Similar posts on daily.dev

- [Arista cEOS Does Not Apply ACLs to Control-Plane Traffic « ipSpace.net blog](https://daily.dev/posts/arista-ceos-does-not-apply-acls-to-control-plane-traffic-ipspace-net-blog-ieh2uzhm7) · ipSpace.net Blog · 0 upvotes · 0 comments
- [The Never-Ending IPv6 Loopback Prefix Saga « ipSpace.net blog](https://daily.dev/posts/the-never-ending-ipv6-loopback-prefix-saga-ipspace-net-blog-4nlhgh10l) · ipSpace.net Blog · 0 upvotes · 0 comments

---

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

[View this post on daily.dev](https://daily.dev/posts/more-arista-eos-bgp-route-reflector-woes-ipspace-net-blog-uaebo69fr)

```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":"More Arista EOS BGP Route Reflector Woes « ipSpace.net blog","url":"https://daily.dev/posts/more-arista-eos-bgp-route-reflector-woes-ipspace-net-blog-uaebo69fr","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/more-arista-eos-bgp-route-reflector-woes-ipspace-net-blog-uaebo69fr"},"datePublished":"2026-08-11T08:52:36.609Z","dateModified":"2026-10-14T02:35:50.865Z","description":"Arista EOS has a quirk where the global `neighbor next-hop-self` command affects EVPN address family processing, causing route reflectors to silently drop EVPN...","image":"https://media.daily.dev/image/upload/s--P4t4XyoV--/f_auto/v1722860399/public/Placeholder%2001","thumbnailUrl":"https://media.daily.dev/image/upload/s--P4t4XyoV--/f_auto/v1722860399/public/Placeholder%2001","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/more-arista-eos-bgp-route-reflector-woes-ipspace-net-blog-uaebo69fr","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp,evpn","timeRequired":"PT4M"}
{"@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":"More Arista EOS BGP Route Reflector Woes « ipSpace.net blog"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/more-arista-eos-bgp-route-reflector-woes-ipspace-net-blog-uaebo69fr#faq","mainEntity":[{"@type":"Question","name":"Why is my Arista EOS BGP route reflector not sending EVPN routes between leaf switches when next-hop-self is configured?","acceptedAnswer":{"@type":"Answer","text":"When `neighbor next-hop-self` is configured globally in Arista EOS, it also applies to the EVPN address family, changing the next hop to the spine/route-reflector. Because the spine lacks VXLAN interfaces to handle that traffic, it suppresses the reflected EVPN updates entirely. The `bgp route-reflector preserve-attributes` command does not override this for EVPN. Removing `next-hop-self` globally restores EVPN route reflection. Engineers debugging EVPN fabric issues on Arista track fixes like the 4.29.0F per-AF next-hop-self support on daily.dev."}},{"@type":"Question","name":"How do I fix next-hop-self breaking EVPN on an Arista EOS route reflector while still changing next hops for IBGP+EBGP IPv4 routes?","acceptedAnswer":{"@type":"Answer","text":"Use a route map instead of the global `next-hop-self` command. Configure a route map that matches external (EBGP) routes and sets the next hop to the peer address, with a second permit entry to pass all other routes unchanged. Apply this route map as an outbound policy on IBGP neighbors in the IPv4 address family. This avoids the global next-hop-self affecting EVPN. Networking engineers solving Arista BGP edge cases share workarounds like this on daily.dev."}},{"@type":"Question","name":"Does Arista EOS support per-address-family next-hop-self configuration for BGP?","acceptedAnswer":{"@type":"Answer","text":"Yes, starting with EOS release 4.29.0F, `neighbor next-hop-self` can be configured within IPv4 and IPv6 unicast address families. Prior to this release, next-hop-self was only configurable at the global BGP neighbor level, causing it to unintentionally affect EVPN address family processing on route reflectors. Arista EOS release notes and their impact on BGP fabric designs surface regularly for networking engineers on daily.dev."}}]}
```

