EVPN L2 setup with bridge vxlan - MAC-IPv4 not exchanged

[pguibert6WIND]

Version 6.0 MAC-IPv4 RT2 messages are not visible in the BGP EVPN exchanged packets. There are MAC-IPv6 RT2, and MAC-NULL RT2, but not MAC-IPv4 RT2, whereas the interface used has an IPv4 address.

[pguibert6WIND]

https://gist.github.com/pguibert6WIND/fad44a7a15842d743a642ed371ad26c0

[pguibert6WIND]

this is more a newbie quesiton, since it seems that only local ipv6 address is exchanged, and neither ipv4 nor ipv6 configured addresses on veth are passed through evpn

[pguibert6WIND]

north-vm# show evpn mac vni all

VNI 100 #MACs (local and remote) 1

MAC               Type   Intf/Remote VTEP      VLAN
c2:11:8d:1c:d2:09 local  vrf11_evpn
92:52:17:a0:9e:e3 local  br100                 1
north-vm#

what is the meaning of VLAN, here ?

[AnuradhaKaruppiah]

Hi Phillipe

1. What are you setting up? asymmetric IRB or symmetric IRB?
2. "this is more a newbie quesiton, since it seems that only local ipv6 address is exchanged, and neither ipv4 nor ipv6 configured addresses on veth are passed through evpn" - local neighbors/ARP both v4/v6 are advertised as type-2 routes. If you have advertise-default-gw config configured for a vni like this -

   !
   address-family l2vpn evpn
   vni 1004
   advertise-default-gw
   exit-vni

   you should see the interface addresses advertised as type-2 routes -

   root@TORC11:~# net show  interface vlan1004-v0 |grep inet
   inet 45.0.4.1/24
   inet6 2001:fee1:0:4::1/64
   inet6 fe80::200:5eff:fe00:101/64
   root@TORC11:~# net show bgp l2vpn evpn route vni 1004 |grep "45.0.4.1\|2001:fee1:0:4::1\|fe80::200:5eff:fe00:101"
   *> [2]:[0]:[0]:[48]:[00:00:5e:00:01:01]:[32]:[45.0.4.1]
   *> [2]:[0]:[0]:[48]:[00:00:5e:00:01:01]:[128]:[2001:fee1:0:4::1]
   *> [2]:[0]:[0]:[48]:[00:00:5e:00:01:01]:[128]:[fe80::200:5eff:fe00:101]
   root@TORC11:~# 

   Is that what you are trying to do? Advertise interface address as a GW to the other VTEPs?

3. "what is the meaning of VLAN, here" The VLAN in the "show evpn mac vni" is the VLAN associated with the local-mac (it is not applicable for remote-macs). I assume vlan-1 is mapped to vni-100 in your config? Also VLAN id is NOT advertised in the type-2 route (ethernet-tag is only needed for vlan aware bundles which is not supported i.e. ethernet-tag=0).

Does that answer your qs? cheers, Anuradha.

[qlyoung]

@pguibert6WIND closing this, reopen if your issue is not addressed.

[pguibert6WIND]

Hi @AnuradhaKaruppiah ,

I picked up again the confiugraiton, and managed to go a bir further.

• about your suggestion to use advertise-default-gw, I did not see the interfaces addresses in RT2 messages
• I am using only one bridge interface without vlan filtering, because I only have one subnetwork behind.
• the remote IP I tried to ping has been resolved through ARP ( I could see ARP resolution inside the vxlan tunnel). However, when the ping goes out and reaches the bridge ports, the incoming ICMP echo packet goes out of br100, instead of using vxlan100 interface.

  3a:c4:5d:83:40:7e dev vxlan100 extern_learn master br100 
  3a:c4:5d:83:40:7e dev vxlan100 vlan 1 extern_learn master br100 
  3a:c4:5d:83:40:7e dev vxlan100 dst 10.125.0.2 self extern_learn 

  any inputs from that ?

[pguibert6WIND]

closing the ticket as I managed to solve the issue.

[qlyoung]

If you want - it might help someone in the future to put a brief summary of what the problem was and how it was solved.

On Tue, Jul 23, 2019, 11:57 AM Philippe Guibert notifications@github.com wrote:

Closed #3445 https://github.com/FRRouting/frr/issues/3445.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/FRRouting/frr/issues/3445?email_source=notifications&email_token=ABUCX62GUYKCDOCUVGUB4RTQA4S6JA5CNFSM4GJCMB52YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSU44GJQ#event-2503590694, or mute the thread https://github.com/notifications/unsubscribe-auth/ABUCX6ZMFPV4C77SR5M5YJLQA4S6JANCNFSM4GJCMB5Q .