Hello Everyone,
Is there are any plans add l2vpn-evpn family in BGP advertisement, that for VXLAN or router reflector for EVPN.
There are 3 things I think would round out the routing stack for MikroTik after they get ROSv7 stable and look at new features
- IS-IS
- EVPN
- SR-MPLS w/ TI-LFA
I would like to add vpnv6 address family to the list.
.+1
+2500 site routers. Let’s do it!
1.IS-IS
2. EVPN
3. SR-MPLS w/ TI-LFA
+1
1.IS-IS
2. EVPN
3. SR-MPLS w/ TI-LFA
+1
1.IS-IS
2. EVPN
3. SR-MPLS w/ TI-LFA
+1
- EVPN
- IS-IS
- SR-MPLS w/ TI-LFA
+1
- EVPN
+1
EVPN
+1 for EVPN here as well.
There is an RFC for this: https://datatracker.ietf.org/doc/html/rfc9136
/Martin
So there is now EVPN still?
Not yet…
Maybe soon 
Damn and I was migrating from RouterOS v6 to v7 because I thought that where VXLAN there should also be control plane EVPN to connect my proxmox SDN using its evpn controller setting peer to MikroTik 
I had to use BGP instead. How working without knowledge can be irritating
As side note I added in lab ISIS to the mix from cli. So far so good.
Step 1 DONE.
Thank you.
I would like to see the implementation of vxlan/evpn already in 2025y
+1
…but are there MT devices with ASICs that can handle VXLAN TEPs in hardware?
There is, the high-end ones has the hardware. But no support implemented yet.
Seems to be baking in the oven.
Documentation revealed at this page (now behind login/private, as of May 15):
Conversation at r/mikrotik:
2. https://www.reddit.com/r/mikrotik/comments/1ig3pj9/evpn_support_is_coming_for_rosv7/
3. https://www.reddit.com/r/mikrotik/comments/1kmkf23/evpn_documentation_added/
Public documentation available at a sub-section added under Routing > BGP page:
4. https://help.mikrotik.com/docs/spaces/ROS/pages/328220/BGP#BGP-EVPN
From the 7.19rc topic:
5. http://forum.mikrotik.com/t/v7-19rc-testing-is-released/183473/188
And the wayback machine from May 14:
6. https://web.archive.org/web/20250514194805/https://help.mikrotik.com/docs/spaces/ROS/pages/315883568/EVPN
Copy-paste from the wayback machines snapshot taken on May 14.
Overview
Ethernet Virtual Private Network (EVPN) is a technology to extend Layer 2 and 3 connectivity between different network segments. MPLS or VXLAN encapsulations can be used to transfer ethernet frames over MPLS or IP-based networks.
BGP EVPN is used as a control plane for multiple data-planes encapsulations (for both Layer2 and Layer3 VPN services). MP-BGP carries MAC addresses, MAC/IP bindings and IP prefixes.
RFC7432 is initial EVPN standard thad defines BGP as control plane for MPLS data plane. RFC8365 extends the use of additional data planes, VXLAN, NVGRE and MPLS over GRE and defines the use of EVPN as Network Virtualization Overlay (NVO).
Terminology
- NVO: Network Virtualization Overlay used to deliver Layer2 and Layer 3 VPN services.
- NVE: Network Virtualization Endpoint is Provider Edge (PE) node within the NVO environment. It is responsible for encapsulation/decapsulation of VPN traffic. In case of VXLAN this defines VTEP (Virtual Tunnel End Point).
- VNI: Virtual Network Identifier
- EVI: EVPN Instance
- RD: Route Distinguisher is a 64-bit prefix appended to IP prefix to make it unique, multiple tenants can use overlapping IP range.
- RT: Route Target is BGP extended community used to control import and export of routes. Typically, RT is based on the AS number and the VNI of the MAC-VRF
- MAC-VRF: VRF table for MAC addresses on a PE (VTEP). Requires RD and RT.
For MP-BGP to carry EVPN, new AFI/SAFI was defined 25(L2 VPN)/70(EVPN). Next-hop address within the NLRI is an IP address of the VTEP advertising the EVPN route.
There are five EVPN route types:
- Type-1: (Ethernet A-D) announces reachability of multi-homed ethernet segment
- Type-2:( MAC advertisement) advertises MAC address of MAC/IP binding learned by specific EVI
- Type-3: (Inclusive multicast) advertises membership of a Layer 2 domain, allowing to auto discover VTEPs
- Type-4: (Ethernet segment) is used to discover VTEPs attached to the same shared Ethernet Segment for EVPN multi-homing model (active-active, active-standby forwarding)
- Type-5: (IP prefix) Advertising IP prefix into the EVPN domain allows to create classic Layer 3 VPN.
Data plane encapsulation is defined with encapsulation extended community value:
- 8 - VXLAN
- 9 - NVGRE
- 10 - MPLS
- 11 - MPLSoGRE
There are two methods for supporting inter-subnet routing with EVPN: symmetric and asymmetric integrated routing and bridging (IRB). The main difference between the two methods is that the symmetric method supports both routing and bridged on both the ingress and egress VTEPs, where the asymmetric method supports routing on the ingress, but only bridging on the egress.
Basic Configuration Example
Basic Layer2 EVPN Vxlan configuration:
/interface bridge
add name=bridge1 vlan-filtering=yes
/interface bridge port
add bridge=bridge1 interface=sfp-sfpplus3 pvid=40
/ip address
add address=203.0.113.1 interface=lo
/interface vxlan
add bridge=bridge1 bridge-pvid=40
local-address=203.0.113.1 name=vxlan1 vni=100040
/routing bgp instance
add as=65000 name=evpn-inst
/routing bgp connection
add afi=evpn instance=evpn-inst local.address=203.0.113.1 .role=ebgp
multihop=yes name=to-leaf-lo remote.address=203.0.113.2 .as=65001
/routing bgp evpn
add export.route-targets=65000:100040 import.route-targets=65001:100040
instance=evpn-inst name=bgp-evpn-1o vni=100040
>
> For simple setups with only one vlan (broadcast domain) there is no need to set route distinguisher.