BGP

test test bla Spine config router bgp 65100 maximum-paths 2 ecmp 2 neighbor EVPN-OVERLAY peer-group neighbor EVPN-OVERLAY next-hop-unchanged neighbor EVPN-OVERLAY update-source Loopback0 neighbor EVPN-OVERLAY ebgp-multihop neighbor EVPN-OVERLAY send-community neighbor EVPN-OVERLAY maximum-routes 0 neighbor 10.0.1.11 peer-group EVPN-OVERLAY neighbor 10.0.1.11 remote-as 65001 next-hop-unchanged is only necesary in older EOS versions. in newer ones it’s the default value for EVPN peerings default behaviour of iBGP is next-hop-unchanged default behaviour of eBGP is next-hop-self

VXLAN/EVPN - BGP underlay Design Options using IGPs In case you need IGPs choose IBGP as an overlay and any IGP (ospf, is-is, etc.) for the underlay. using BGP in the underlay If your vendor offers a easy and robust implementetion of EVPN over eBGP go for an eBGP-only EVPN implementation. spine switches should not be involved in intra-fabric traffic forwarding the BGP-next hop in an EVPN update must not be changed (next-hop-unchaganged) on the path between egress and ingress switch.