Routing

Expand all | Collapse all

EVPN - no remote route of type EVPN in the L3VPN

Jump to Best Answer
  • 1.  EVPN - no remote route of type EVPN in the L3VPN

    Posted 07-03-2019 06:02
    Hi guys,
     
    I have a lab set up on EVE-NG to test EVPN. I am running version 14.1R1.10.
     
    When my local PE router learns a new MAC/IP binding it installs a host route in the IP VPN VRF with protocol type EVPN and a next hop of the VLAN’s IRB interface. This triggers the PE to transmit this host route to remote PEs that are members of the IP VPN via a VPN route advertisement. The remote PEs add this route to their VRF with protocol type BGP.
     
    The PE also advertises the MAC/IP binding via a MAC/IP Advertisement route to remote PEs. I see this type 2 route on the remote PEs. So far so good.
     
    From hereon things start to divert from expectation. I expected the remote PE  to install a corresponding host route in its IP VPN VRF with protocol type EVPN. I only see the BGP route via IP VPN VRF in the VRF.inet.0 table. The MAC/IP route is supposed to be the preferred on but I don't even have it. Where could things be going wrong.
     


  • 2.  RE: EVPN - no remote route of type EVPN in the L3VPN

     
    Posted 07-03-2019 07:46

    Hi enyatoti,

     

    Please check the "vrf-target" for vrf-export and vrf-import policies on each side.

     

    The type 2 route is used to advertise MAC addresses and somtimes also an IP address that is bound to that MAC address.  So one leaf as an EVPN PE, will learn MAC addresses in data plane from Ethernet frames received from CEs.  Once the leaf learns CE’s MAC address, it will automatically advertise it to remote PEs and attaches a target community.  The remote end leaf, which is another EVPN PE, upon receiving the route must decide on whether it should keep the route. It makes this decision based on the received route target community.  The remote PE, in order to accept and use this advertisement, must be configured with an import policy that accepts routes tagged with the target community.  Without a configured policy that matches on the specified route target , the remote leaf/PE would just discard the advertisement.  So, at a minimum, each EVI on each participating PE for a given EVPN must be configured with an export policy that attaches a unique target community to MAC advertisements and also configured with an import policy that matches and accepts advertisements based on that unique target community.

     

    Example:

    https://www.juniper.net/documentation/en_US/release-independent/nce/topics/example/nce156-example-evpn-vxlan-virtual-gateway-address.html
    https://www.juniper.net/documentation/en_US/junos/topics/example/vrf-target-auto-manual.html

     

    Hope this helps.

    Regards,
    -r.

    --------------------------------------------------

    If this solves your problem, please mark this post as "Accepted Solution."
    Kudos are always appreciated :).



  • 3.  RE: EVPN - no remote route of type EVPN in the L3VPN
    Best Answer

    Posted 07-05-2019 01:54

    I got the solution. One of EVPN's prerequisites is that Chained composite next hops should be enabled. Starting in Junos Release 14.1R4, the load balancing and chained composite next hop features required for EVPN are automatically configured.

     

    I had to enable chained composite next hops as follows:

     

     routing-options
         forwarding-table {
            chained-composite-next-hop ingress evpn;
       }

    }

     

    Only then I started getting the remote type 2 MAC/IP route.



  • 4.  RE: EVPN - no remote route of type EVPN in the L3VPN

    Posted 05-03-2020 16:40

    I'm facing the same issue, but the solution mentioned above didnt work for me.

     

    Config snip:


    lab@vMX4> show configuration routing-options | display set
    set routing-options forwarding-table chained-composite-next-hop ingress evpn

     

    lab@vMX4> show route table inet.0 192.168.1.0/24 terse

    inet.0: 27 destinations, 27 routes (27 active, 0 holddown, 0 hidden)
    @ = Routing Use Only, # = Forwarding Use Only
    + = Active Route, - = Last Active, * = Both

    A V Destination P Prf Metric 1 Metric 2 Next hop AS path
    * ? 192.168.1.0/24 D 0 >irb.110
    * ? 192.168.1.4/32 E 7 >irb.110
    * ? 192.168.1.254/32 L 0 Local

     

    Bold face routes are MAC/IP routes(type 2) learnt from remote PEs which i need to be installed in inet.0 as local learnt route got installed:

     

    lab@vMX4> show route table iNET-BLUE-EVPN.evpn.0 terse | match 192.168.1.
    2:172.16.1.1:8::110::2c:6b:f5:6a:74:f0::192.168.1.254/304 MAC/IP
    2:172.16.1.1:8::110::50:00:00:13:00:03::192.168.1.1/304 MAC/IP
    2:172.16.1.2:8::110::2c:6b:f5:7a:c4:f0::192.168.1.254/304 MAC/IP
    2:172.16.1.2:8::110::50:00:00:13:00:04::192.168.1.2/304 MAC/IP
    2:172.16.1.3:5::110::2c:6b:f5:ef:11:f0::192.168.1.254/304 MAC/IP
    2:172.16.1.3:5::110::50:00:00:13:00:05::192.168.1.3/304 MAC/IP
    2:172.16.1.4:11::110::2c:6b:f5:7d:ea:f0::192.168.1.254/304 MAC/IP
    2:172.16.1.4:11::110::50:00:00:13:00:06::192.168.1.4/304 MAC/IP

     

    But i have ARP entries for all remote learnt MAC/IP type2 routes:

     

    lab@vMX4> show arp
    MAC Address Address Name Interface Flags

    50:00:00:13:00:06 10.0.10.14 10.0.10.14 xe-0/0/5.10 none
    50:00:00:13:00:06 10.0.30.14 10.0.30.14 xe-0/0/5.30 none
    50:00:00:07:00:01 128.0.0.16 fpc0 em1.0 none
    50:00:00:06:00:02 172.16.0.9 172.16.0.9 xe-0/0/0.0 none
    50:00:00:13:00:06 172.16.0.26 172.16.0.26 xe-0/0/5.2 none
    50:00:00:13:00:03 192.168.1.1 192.168.1.1 irb.110 [.local..11] permanent remote
    50:00:00:13:00:04 192.168.1.2 192.168.1.2 irb.110 [.local..11] permanent remote
    50:00:00:13:00:05 192.168.1.3 192.168.1.3 irb.110 [.local..11] permanent remote
    50:00:00:13:00:06 192.168.1.4 192.168.1.4 irb.110 [xe-0/0/5.110] permanent remote

     

    Is anyone aware of the possible fix?