• Tag : BGP EVPN


Extending EVPN and VXLAN to the Host

Overview VxLAN provides a highly scalable, standards based approach for constructing L2 overlays on top of routed networks. It is defined in RFC7348, and encapsulates the original host Ethernet frame in a UDP + IP + Ethernet frame. BGP EVPN (RFC 7432 and RFC 8365 for its application to VXLAN) is a standards based control protocol to efficiently discover other endpoints (VTEPs) and distribute reachability information (MAC addresses). This post assumes the reader is already familiar with configuration and operations of EVPN and VXLAN for Arista. Goals The use case here is the extension of a L2 overlay south of the TOR/Leaf...
Continue reading →

bgp evpn neighbors not establishing

Hello, I got stuck at the BGP eVPN setup; neighbors will not come up: BGP state is Idle, Missing local addresses for activated AFI/SAFIs Logging messahe spine1#Sep 3 03:07:41 spine1 Bgp: %BGP-3-NOTIFICATION: received from neighbor (VRF default AS 65001) 6/5 (Cease/connection rejected) 0 bytes Please see attached bgp output and config. Thanks,

EVPN with MPLS over GRE encapsulation

Hello folks, I follow this guild to configure EVPN with VXLAN data plane encapsulation, it worked fine to me as the flowing link. https://www.arista.com/assets/data/pdf/user-manual/um-eos/Chapters/EVPN.pdf. However, I want to know that does Arista support EVPN with MPLS over GRE encapsulation? I appreciate your help. Thank you so much.

EVPN with MPLS over GRE

Hello folks, I follow this guild to configure EVPN with VXLAN data plane encapsulation, it worked fine to me. However, I want to know that does Arista support EVPN with MPLS over GRE encapsulation? I appreciate your help. Thank you so much.

What is the meaning of this command?

In EVPN configuration guide, I read the following command has been used: ip address virtual source-nat vrf A address But I could not find any documentation to explain this command. What is used for? and How to use it? Please give some hint about this command. Thanks.


G’day, I am looking for some guidance as well as real life experience, gotchas, etc (if someone has done something similar it will be great to hear some thoughts). I am working on a design of 50+ DCs, meaning I’ll have 50+ fabrics across the globe. The requirement is to support multi-tenancy across all the sites and the only “relief” here is I only need to support layer3! That being said, I am considering multi-site, multi-pod architecture running route-servers within and between all sites. My current idea is to have three major sites (regions) – US, EMEA & APAC. In...
Continue reading →

Problem with EVPN type-5 packet forwarding on vEOS

Hello, I am testing a solution based on VXLAN EVPN, with Type-5 routes, with vEOS, but I am having some issues in packet forwarding. The routes are correctly propagated, but when I try to ping from a device connected to one node, on a device connected to another node, the ping does not work. I also tried a ping, with a forced source IP, from the vEOS machine itself, but it has problems too. LEAF-2 LEAF-2#sh ip route vrf gold VRF: gold Codes: C – connected, S – static, K – kernel, O – OSPF, IA – OSPF inter...
Continue reading →

VLAN Aware Bundle Service

Description A VLAN-Aware bundle MAC-VRF allows multiple L2 domains to be advertised by a single MAC-VRF. The Ethernet Tag ID (ETID) as described in RFC7432 identifies the L2 domain within an EVPN instance corresponding to each route. VLAN-Aware mode can be configured by using the vlan-aware-bundle BGP submode.   Each vlan-aware-bundle MAC-VRF will require a unique name. The user will need to specify the VLANs to be included in the MAC-VRF. By default, the Ethernet Tag ID for a given VLAN is the VNI associated locally to that VLAN, unless the Ethernet Tag ID is explicitly set with the etid...
Continue reading →

BGP Crashing with VXLAN EVPN

I have a network setup with 6 Arista 7050QX running VXLAN-EVPN. All nodes are doing eBGP. I can establish eBGP sessions and configure EVPN as well but the moment I start sending traffic via VXLAN then BGP stops working saying “BGP agent not running”. I have tried 4.21.5F, 4.21.3F and currently using 4.20.5F but same result. Config looks like this at one end. Router bgp 65001 vlan 101 rd route-target both 101:10000002 redistribute learned interface Vxlan1 description VXLAN Interface vxlan source-interface Loopback0 vxlan udp-port 4789 vxlan vlan 100 vni 10000001 vxlan vlan 101 vni 10000002 Arista DCS-7050QX-32-R Hardware version:...
Continue reading →

MAC Address flapping – VXLAN with MLAG

As per the attached diagram, its a VXLAN EVPN setup. Everything was working fine on that side. Both switches in city A and City B have MLAG configured with the TOR Stack switches. After creating MLAG with the TOR Stack switches, all MAC addresses have started flapping. For example MAC address ab-bc-cd is coming from the server connected to TOR Stack switch in City B. On B-SW01 it is learning from Port-channel10 (MLAG) but on B-SW02 it is learning from VX1 interface (vxlan) which is coming from the RR via B-SW01 and then it hands it back to the TOR...
Continue reading →

Spine-Leaf BGP EVPN Best Practice

Hello I’m seeking for a white paper\best practice document that can cover deploying a topology of spine-leaf data center. The points i’m seeking clarifications are 1. underlay L3 connectivity – is IGP required to be configured between spine and leafs. 2. is multicast a must between spine and leaf for control plan operation? (forwarding BUM packets?) 3. with vxlan, are there any problems using mlags? how can i advertise a certain MAC address is available from two different VTEPs and encapsulate into vxlan from both connections? 4. in terms of configuration, how can i deploy such a scenario? 5. unconventional as it...
Continue reading →

Multicast in VXLAN with BGP EVPN control-plane

 Hello, We are trying to run multicast in data center overlay network. In our data centers we are using L3 leaf-spine topology with VXLAN. For the control plane BGP EVPN is used.  Leaf switches are deployed in an MLAG configuration. We want to run multicast between hosts that are on same vlan across switches in different MLAG domains. Multiple multicast receivers, as well as multiple senders are connected to different MLAG domains and are all in the same VLAN. Multicast receiver can receive m-c stream from the sender if both of them are in the same MLAG domain. But if receiver is connected to...
Continue reading →


Get every new post on this blog delivered to your Inbox.

Join other followers: