Page MenuHomeVyOS Platform

Allow BGP to use address-family l2vpn evpn
Open, WishlistPublicFEATURE REQUEST

Description

hi,

please make it possible to configure bgp address-family l2vpn evpn.
frr has support for it. See bgp documentation

Details

Difficulty level
Unknown (require assessment)
Version
-
Why the issue appeared?
Will be filled on close

Event Timeline

rherold created this task.Mar 25 2019, 8:40 PM
pasik added a subscriber: pasik.Apr 10 2019, 2:45 PM
syncer triaged this task as Wishlist priority.Apr 17 2019, 7:40 PM
syncer edited projects, added VyOS 1.3 Equuleus; removed VyOS 1.2 Crux.
adestis added a subscriber: adestis.Oct 9 2019, 9:19 AM
Viacheslav added a comment.EditedSun, Mar 29, 1:44 PM

I created a network diagram for "l2vpn evpn" implementation.
I used this instruction vxlan-bgp-vpn

Each VTEP opens a BGP session with central Route-Reflector (RR), sends its information (MACs and VNIs) and receives others.
On RR we use the feature "bgp listen range 22.22.22.0/24 peer-group fabric". Therefore, we don't need to configure each neighbor, they have connected via BGP automatically.

Because At this stage, the VyOS doesn't support all the necessary commands, some of them are loaded from the "/config/scripts/vyos-postconfig-bootup.script".
These are mainly such commands:

sudo ip link add vxlan14 type vxlan id 14 dstport 8472 local 22.22.22.5 nolearning

vtysh -c "conf t" -c "router bgp 65001" -c " address-family l2vpn evpn" -c " neighbor fabric activate" -c " advertise-all-vni "

In the configuration, I don't use default routes.

Router configurations below.






So we can ping from VPC11 = > VPC12

l-11> ping 10.11.11.102 -c 3

84 bytes from 10.11.11.102 icmp_seq=1 ttl=64 time=3.777 ms
84 bytes from 10.11.11.102 icmp_seq=2 ttl=64 time=3.134 ms
84 bytes from 10.11.11.102 icmp_seq=3 ttl=64 time=3.109 ms

l-11>

Show routes from "left-r1":

left-r1# show ip bgp l2vpn evpn neighbors 22.22.22.254 routes 
BGP table version is 5, local router ID is 22.22.22.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
Route Distinguisher: ip 22.22.22.2:2

*>i[3]:[0]:[32]:[22.22.22.2]
                    22.22.22.2               0    100      0 i
                    RT:65001:14 ET:8
*>i[2]:[0]:[48]:[00:50:79:66:68:0c]
                    22.22.22.3               0    100      0 i
                    RT:65001:11 ET:8
*>i[3]:[0]:[32]:[22.22.22.3]
                    22.22.22.3               0    100      0 i
                    RT:65001:11 ET:8
Route Distinguisher: ip 22.22.22.4:2

*>i[3]:[0]:[32]:[22.22.22.4]
                    22.22.22.4               0    100      0 i
                    RT:65001:12 ET:8
Route Distinguisher: ip 22.22.22.5:2

*>i[3]:[0]:[32]:[22.22.22.5]
                    22.22.22.5               0    100      0 i
                    RT:65001:14 ET:8

Displayed 5 out of 8 total prefixes
left-r1#
left-r1# show evpn vni 
VNI        Type VxLAN IF              # MACs   # ARPs   # Remote VTEPs  Tenant VRF                           
12         L2   vxlan12               1        1        1               default                              
11         L2   vxlan11               1        1        1               default 

left-r1# show evpn vni 11
VNI: 11
 Type: L2
 Tenant VRF: default
 VxLAN interface: vxlan11
 VxLAN ifIndex: 8
 Local VTEP IP: 22.22.22.1
 Mcast group: 0.0.0.0
 Remote VTEPs for this VNI:
  22.22.22.3 flood: HER
 Number of MACs (local and remote) known for this VNI: 1
 Number of ARPs (IPv4 and IPv6, local and remote) known for this VNI: 1
 Advertise-gw-macip: No

If someone has experience in this or uses a different scheme, please contact.