search

FRRouting / frr

The FRRouting Protocol Suite
https://frrouting.org/
Other
3.35k stars 1.25k forks source link

FRR as Route Reflector Server and L2VPN EVPN #2194

Closed javcasalc closed 5 years ago

javcasalc commented 6 years ago

Hi I have a FRR 4.0.1 configured as RR server with this config:

!
router bgp 65000
 bgp router-id 12.0.2.129
 bgp log-neighbor-changes
 no bgp default ipv4-unicast
 bgp cluster-id 12.0.2.129
 coalesce-time 1000
 bgp bestpath as-path multipath-relax
 neighbor fabric peer-group
 neighbor fabric remote-as 65000
 neighbor fabric update-source 12.0.2.129
 neighbor fabric capability extended-nexthop
 bgp listen range 12.0.0.0/16 peer-group fabric
 !
 address-family l2vpn evpn
  neighbor fabric activate
  neighbor fabric route-reflector-client
  neighbor fabric allowas-in
 exit-address-family
!

Then I have two BGP peers configured as RR-clients, running Nuage/Nokia SR-OS.

I have peer 1 announcing these prefixes:

### EVPN ROUTES SENT TO FRR

1 2018/05/09 11:18:30.52 CEST MINOR: DEBUG #2001 Base Peer 1: 12.0.2.129
"Peer 1: 12.0.2.129: UPDATE
Peer 1: 12.0.2.129 - Send BGP UPDATE:
    Withdrawn Length = 0
    Total Path Attr Length = 147
    Flag: 0x40 Type: 1 Len: 1 Origin: 0
    Flag: 0x40 Type: 2 Len: 0 AS Path:
    Flag: 0x80 Type: 4 Len: 4 MED: 0
    Flag: 0x40 Type: 5 Len: 4 Local Preference: 200
    Flag: 0xc0 Type: 16 Len: 24 Extended Community:
        target:65000:111
        virtual nexthop:33.53.23.149
        tunnel encap type:8
    Flag: 0x90 Type: 14 Len: 95 Multiprotocol Reachable NLRI:
        Address Family EVPN
        NextHop len 4 NextHop 34.246.2.81
        Type: EVPN-MAC Len: 49 RD: 65000:111 ESI: 00:00:00:00:00:00:00:00:00:00,
 tag: 0, mac len: 48 mac: 00:01:21:35:17:95, IP len: 16, IP: NULL, Label: 111
        Type: EVPN-MAC Len: 33 RD: 65000:111 ESI: 00:00:00:00:00:00:00:00:00:00,
 tag: 0, mac len: 48 mac: 00:01:21:35:17:95, IP len: 0, IP: NULL, Label: 111
"

2 2018/05/09 11:18:30.53 CEST MINOR: DEBUG #2001 Base Peer 1: 12.0.2.129
"Peer 1: 12.0.2.129: UPDATE
Peer 1: 12.0.2.129 - Send BGP UPDATE:
    Withdrawn Length = 0
    Total Path Attr Length = 104
    Flag: 0x40 Type: 1 Len: 1 Origin: 0
    Flag: 0x40 Type: 2 Len: 0 AS Path:
    Flag: 0x80 Type: 4 Len: 4 MED: 0
    Flag: 0x40 Type: 5 Len: 4 Local Preference: 200
    Flag: 0xc0 Type: 16 Len: 40 Extended Community:
        target:65000:111
        NAT Info:uplink id: 1 underlay id: 0
        NAT Binding Info:Public IP: 34.246.2.81
        NAT Info:Private IP: 12.0.3.10
        tunnel encap type:8
    Flag: 0x90 Type: 14 Len: 36 Multiprotocol Reachable NLRI:
        Address Family EVPN
        NextHop len 4 NextHop 33.53.23.149
        Type: EVPN-Nat Len: 25 RD: 65534:45176
        DataPathID: 33.53.23.149, Tunnel Encap: 0, Public IP: 0.0.0.0
        Public Port: 4789 Private IP 0.0.0.0, Site ID: 0
"

3 2018/05/09 11:18:30.60 CEST MINOR: DEBUG #2001 Base Peer 1: 12.0.2.129
"Peer 1: 12.0.2.129: UPDATE
Peer 1: 12.0.2.129 - Send BGP UPDATE:
    Withdrawn Length = 0
    Total Path Attr Length = 145
    Flag: 0x40 Type: 1 Len: 1 Origin: 0
    Flag: 0x40 Type: 2 Len: 0 AS Path:
    Flag: 0x80 Type: 4 Len: 4 MED: 0
    Flag: 0x40 Type: 5 Len: 4 Local Preference: 200
    Flag: 0xc0 Type: 16 Len: 72 Extended Community:
        target:65000:111
        virtual nexthop:33.53.23.149
        PG Id:1789310781
        PG Id:789925100
        pg to pg color:part3: 0x000000bcb1700000
        pg to pg color:part2: 0x0000020000000000
        pg to pg color:part1: 0x0000000000000000
        tunnel encap type:8
        origin:00:01:21:35:17:95
    Flag: 0x90 Type: 14 Len: 45 Multiprotocol Reachable NLRI:
        Address Family EVPN
        NextHop len 4 NextHop 34.246.2.81
        Type: EVPN-IP-prefix Len: 34 RD: 65534:35174
        ESI: 00:00:00:00:00:00:00:00:00:00, tag: 0, IP-Prefix: 100.64.1.0/24,
        GW-IP: 0.0.0.0, label: 111

8 2018/05/09 11:18:38.95 CEST MINOR: DEBUG #2001 Base Peer 1: 12.0.2.129
"Peer 1: 12.0.2.129: UPDATE
Peer 1: 12.0.2.129 - Send BGP UPDATE:
    Withdrawn Length = 0
    Total Path Attr Length = 104
    Flag: 0x40 Type: 1 Len: 1 Origin: 0
    Flag: 0x40 Type: 2 Len: 0 AS Path:
    Flag: 0x80 Type: 4 Len: 4 MED: 0
    Flag: 0x40 Type: 5 Len: 4 Local Preference: 200
    Flag: 0xc0 Type: 16 Len: 40 Extended Community:
        target:65000:111
        NAT Info:uplink id: 1 underlay id: 0
        NAT Binding Info:Public IP: 34.246.2.81
        NAT Info:Private IP: 12.0.3.10
        tunnel encap type:8
    Flag: 0x90 Type: 14 Len: 36 Multiprotocol Reachable NLRI:
        Address Family EVPN
        NextHop len 4 NextHop 33.53.23.149
        Type: EVPN-Nat Len: 25 RD: 65534:45176
        DataPathID: 33.53.23.149, Tunnel Encap: 1, Public IP: 0.0.0.0
        Public Port: 4500 Private IP 0.0.0.0, Site ID: 0

but peer-2 is getting only these prefixes:

### EVPN ROUTES REFLECTED BY frrouting.org

1 2018/05/09 11:18:29.14 CEST MINOR: DEBUG #2001 Base Peer 1: 12.0.2.129
"Peer 1: 12.0.2.129: UPDATE
Peer 1: 12.0.2.129 - Received BGP UPDATE:
    Withdrawn Length = 0
    Total Path Attr Length = 162
    Flag: 0x90 Type: 14 Len: 95 Multiprotocol Reachable NLRI:
        Address Family EVPN
        NextHop len 4 NextHop 34.246.2.81
        Type: EVPN-MAC Len: 49 RD: 65000:111 ESI: 00:00:00:00:00:00:00:00:00:00,
 tag: 0, mac len: 48 mac: 00:01:21:35:17:95, IP len: 16, IP: NULL, Label: 111
        Type: EVPN-MAC Len: 33 RD: 65000:111 ESI: 00:00:00:00:00:00:00:00:00:00,
 tag: 0, mac len: 48 mac: 00:01:21:35:17:95, IP len: 0, IP: NULL, Label: 111
    Flag: 0x40 Type: 1 Len: 1 Origin: 0
    Flag: 0x50 Type: 2 Len: 0 AS Path:
    Flag: 0x80 Type: 4 Len: 4 MED: 0
    Flag: 0x40 Type: 5 Len: 4 Local Preference: 200
    Flag: 0x80 Type: 9 Len: 4 Originator ID: 1.2.3.4
    Flag: 0x80 Type: 10 Len: 4 Cluster ID:
        12.0.2.129
    Flag: 0xc0 Type: 16 Len: 24 Extended Community:
        target:65000:111
        virtual nexthop:33.53.23.149
        tunnel encap type:8
"

2 2018/05/09 11:18:29.17 CEST MINOR: DEBUG #2001 Base Peer 1: 12.0.2.129
"Peer 1: 12.0.2.129: UPDATE
Peer 1: 12.0.2.129 - Received BGP UPDATE:
    Withdrawn Length = 0
    Total Path Attr Length = 160
    Flag: 0x90 Type: 14 Len: 45 Multiprotocol Reachable NLRI:
        Address Family EVPN
        NextHop len 4 NextHop 34.246.2.81
        Type: EVPN-IP-prefix Len: 34 RD: 65534:35174
        ESI: 00:00:00:00:00:00:00:00:00:00, tag: 0, IP-Prefix: 100.64.1.0/24,
        GW-IP: 0.0.0.0, label: 111
    Flag: 0x40 Type: 1 Len: 1 Origin: 0
    Flag: 0x50 Type: 2 Len: 0 AS Path:
    Flag: 0x80 Type: 4 Len: 4 MED: 0
    Flag: 0x40 Type: 5 Len: 4 Local Preference: 200
    Flag: 0x80 Type: 9 Len: 4 Originator ID: 1.2.3.4
    Flag: 0x80 Type: 10 Len: 4 Cluster ID:
        12.0.2.129
    Flag: 0xc0 Type: 16 Len: 72 Extended Community:
        target:65000:111
        pg to pg color:part1: 0x0000000000000000
        pg to pg color:part2: 0x0000020000000000
        virtual nexthop:33.53.23.149
        pg to pg color:part3: 0x000000bcb1700000
        PG Id:789925100
        PG Id:1789310781
        tunnel encap type:8
        origin:00:01:21:35:17:95

The question is: does FRR support this kind of config, RR-server for EVPN environments?

Thanks. J.

anithanarasimhamurthy commented 6 years ago

Issue seems to be specific to routes of Type: EVPN-Nat Can we please enable "debug bgp updates" on the FRR side and confirm?

javcasalc commented 6 years ago

Hi

I have enabled debug, but I got no debug logs.....¿?¿?

FRRbgpd# sh debugging 
BGP debugging status:
  BGP neighbor-events debugging is on
  BGP next-hop tracking debugging is on
  BGP updates debugging is on (inbound)
  BGP updates debugging is on (outbound)
  BGP zebra debugging is on

FRRbgpd# clear bgp *2018/05/16 11:21:05 BGP: : %NOTIFICATION: sent to neighbor 12.0.2.110 6/4 (Cease/Administratively Reset) 0 bytes 
2018/05/16 11:21:05 BGP: : %NOTIFICATION: sent to neighbor 12.0.2.111 6/4 (Cease/Administratively Reset) 0 bytes 
2018/05/16 11:21:05 BGP: : %ADJCHANGE: neighbor 12.0.2.110(Unknown) in vrf Default Down Neighbor deleted
2018/05/16 11:21:05 BGP: : %ADJCHANGE: neighbor 12.0.2.111(Unknown) in vrf Default Down Neighbor deleted

FRRbgpd# 2018/05/16 11:21:05 BGP: : %ADJCHANGE: neighbor 12.0.2.110(Unknown) in vrf Default Up
2018/05/16 11:21:05 BGP: : %ADJCHANGE: neighbor 12.0.2.111(Unknown) in vrf Default Up

FRRbgpd# show bgp l2vpn evpn all overlay 
Route Distinguisher: as2 65000:111

*>i[2]:[00:01:21:35:17:95]/224
                    34.246.2.81     00:00:00:00:00:00:00:00:00:00
*>i[2]:[00:01:21:35:17:95]:[fe80::201:21ff:fe35:1795]
                    34.246.2.81     00:00:00:00:00:00:00:00:00:00/::
Route Distinguisher: as2 65534:35174

*>i[5]:[0][100.64.1.0/24]/224
                    34.246.2.81     00:00:00:00:00:00:00:00:00:00/0.0.0.0/00:01:21:35:17:95

Displayed 3 out of 3 total prefixes

FRRbgpd# show bgp l2vpn evpn all tags 
Route Distinguisher: as2 65000:111

*>i[2]:[00:01:21:35:17:95]/224
                    34.246.2.81     *>i[2]:[00:01:21:35:17:95]:[fe80::201:21ff:fe35:1795]
                    34.246.2.81     Route Distinguisher: as2 65534:35174

*>i[5]:[0][100.64.1.0/24]/224
                    34.246.2.81     
Displayed 3 out of 3 total prefixes
donaldsharp commented 6 years ago

what does show log say where the log files are going?

javcasalc commented 6 years ago

ok, it was a log level issue. Now I have a complete debug:

FRRbgpd# clear bgp *
2018/05/16 13:30:21 BGP: : %NOTIFICATION: sent to neighbor 12.0.2.110 6/4 (Cease/Administratively Reset) 0 bytes 
2018/05/16 13:30:21 BGP: : %NOTIFICATION: sent to neighbor 12.0.2.111 6/4 (Cease/Administratively Reset) 0 bytes 
2018/05/16 13:30:21 BGP: : 12.0.2.110 [FSM] BGP_Stop (Established->Clearing), fd 20
2018/05/16 13:30:21 BGP: : 12.0.2.110 (dynamic neighbor) deleted
2018/05/16 13:30:21 BGP: : 12.0.2.110 dropped from group fabric, count 1
2018/05/16 13:30:21 BGP: : %ADJCHANGE: neighbor 12.0.2.110(Unknown) in vrf Default Down Neighbor deleted
2018/05/16 13:30:21 BGP: : 12.0.2.110 went from Established to Deleted
2018/05/16 13:30:21 BGP: : 12.0.2.111 [FSM] BGP_Stop (Established->Clearing), fd 22
2018/05/16 13:30:21 BGP: : 12.0.2.111 (dynamic neighbor) deleted
2018/05/16 13:30:21 BGP: : 12.0.2.111 dropped from group fabric, count 0
2018/05/16 13:30:21 BGP: : %ADJCHANGE: neighbor 12.0.2.111(Unknown) in vrf Default Down Neighbor deleted
2018/05/16 13:30:21 BGP: : 12.0.2.111 went from Established to Deleted

FRRbgpd# 2018/05/16 13:30:21 BGP: : Dynamic Neighbor 12.0.2.111/32 matches group fabric listen range 12.0.0.0/16
2018/05/16 13:30:21 BGP: : 12.0.2.111 Dynamic Neighbor added, group fabric count 1
2018/05/16 13:30:21 BGP: : 12.0.2.111 went from Idle to Active
2018/05/16 13:30:21 BGP: : 12.0.2.111 [FSM] TCP_connection_open (Active->OpenSent), fd 20
2018/05/16 13:30:21 BGP: : 12.0.2.111 open active, local address 12.0.2.129
2018/05/16 13:30:21 BGP: : 12.0.2.111 Sending hostname cap with hn = FRRbgpd, dn = (null)
2018/05/16 13:30:21 BGP: : 12.0.2.111 sending OPEN, version 4, my as 65000, holdtime 180, id 12.0.2.129
2018/05/16 13:30:21 BGP: : 12.0.2.111 went from Active to OpenSent
2018/05/16 13:30:21 BGP: : 12.0.2.111 rcv OPEN, version 4, remote-as (in open) 65000, holdtime 90, id 2.2.2.2
2018/05/16 13:30:21 BGP: : 12.0.2.111 rcv OPEN w/ OPTION parameter len: 16
2018/05/16 13:30:21 BGP: : 12.0.2.111 rcvd OPEN w/ optional parameter type 2 (Capability) len 14
2018/05/16 13:30:21 BGP: : 12.0.2.111 OPEN has MultiProtocol Extensions capability (1), length 4
2018/05/16 13:30:21 BGP: : 12.0.2.111 OPEN has MP_EXT CAP for afi/safi: 25/70
2018/05/16 13:30:21 BGP: : 12.0.2.111 OPEN has Route Refresh capability (2), length 0
2018/05/16 13:30:21 BGP: : 12.0.2.111 OPEN has 4-octet AS number capability (65), length 4
2018/05/16 13:30:21 BGP: : 12.0.2.111 [FSM] Receive_OPEN_message (OpenSent->OpenConfirm), fd 20
2018/05/16 13:30:21 BGP: : 12.0.2.111 went from OpenSent to OpenConfirm
2018/05/16 13:30:21 BGP: : 12.0.2.111 [FSM] Receive_KEEPALIVE_message (OpenConfirm->Established), fd 20
2018/05/16 13:30:21 BGP: : 12.0.2.111 went from OpenConfirm to Established
2018/05/16 13:30:21 BGP: : %ADJCHANGE: neighbor 12.0.2.111(Unknown) in vrf Default Up
2018/05/16 13:30:21 BGP: : 12.0.2.111 [FSM] Timer (routeadv timer expire)
2018/05/16 13:30:21 BGP: : Dynamic Neighbor 12.0.2.110/32 matches group fabric listen range 12.0.0.0/16
2018/05/16 13:30:21 BGP: : 12.0.2.110 Dynamic Neighbor added, group fabric count 2
2018/05/16 13:30:21 BGP: : 12.0.2.110 went from Idle to Active
2018/05/16 13:30:21 BGP: : 12.0.2.110 [FSM] TCP_connection_open (Active->OpenSent), fd 22
2018/05/16 13:30:21 BGP: : 12.0.2.110 open active, local address 12.0.2.129
2018/05/16 13:30:21 BGP: : 12.0.2.110 Sending hostname cap with hn = FRRbgpd, dn = (null)
2018/05/16 13:30:21 BGP: : 12.0.2.110 sending OPEN, version 4, my as 65000, holdtime 180, id 12.0.2.129
2018/05/16 13:30:21 BGP: : 12.0.2.110 went from Active to OpenSent
2018/05/16 13:30:21 BGP: : 12.0.2.110 rcv OPEN, version 4, remote-as (in open) 65000, holdtime 90, id 1.2.3.4
2018/05/16 13:30:21 BGP: : 12.0.2.110 rcv OPEN w/ OPTION parameter len: 16
2018/05/16 13:30:21 BGP: : 12.0.2.110 rcvd OPEN w/ optional parameter type 2 (Capability) len 14
2018/05/16 13:30:21 BGP: : 12.0.2.110 OPEN has MultiProtocol Extensions capability (1), length 4
2018/05/16 13:30:21 BGP: : 12.0.2.110 OPEN has MP_EXT CAP for afi/safi: 25/70
2018/05/16 13:30:21 BGP: : 12.0.2.110 OPEN has Route Refresh capability (2), length 0
2018/05/16 13:30:21 BGP: : 12.0.2.110 OPEN has 4-octet AS number capability (65), length 4
2018/05/16 13:30:21 BGP: : 12.0.2.110 [FSM] Receive_OPEN_message (OpenSent->OpenConfirm), fd 22
2018/05/16 13:30:21 BGP: : 12.0.2.110 went from OpenSent to OpenConfirm
2018/05/16 13:30:21 BGP: : 12.0.2.110 [FSM] Receive_KEEPALIVE_message (OpenConfirm->Established), fd 22
2018/05/16 13:30:21 BGP: : 12.0.2.110 went from OpenConfirm to Established
2018/05/16 13:30:21 BGP: : %ADJCHANGE: neighbor 12.0.2.110(Unknown) in vrf Default Up
2018/05/16 13:30:21 BGP: : 12.0.2.110 [FSM] Timer (routeadv timer expire)
2018/05/16 13:30:21 BGP: : 12.0.2.110 rcvd UPDATE w/ attr: nexthop 33.53.23.149, localpref 200, metric 0, extcommunity RT:65000:111 ? ? ? ET:8, path 
2018/05/16 13:30:21 BGP: : 12.0.2.110 rcvd UPDATE wlen 0 attrlen 131 alen 0
2018/05/16 13:30:21 BGP: : 12.0.2.110 rcvd UPDATE w/ attr: nexthop 34.246.2.81, localpref 200, metric 0, extcommunity RT:65000:111 ? ? ? ? ? ? ET:8 Rmac:00:01:21:35:17:95, path 
2018/05/16 13:30:21 BGP: : 12.0.2.110 rcvd UPDATE wlen 0 attrlen 145 alen 0
2018/05/16 13:30:21 BGP: : 12.0.2.110 rcvd RD 65534:35174 [5]:[0][100.64.1.0/24]/224 label 6 l2vpn evpn
2018/05/16 13:30:21 BGP: : 12.0.2.110 rcvd UPDATE w/ attr: nexthop 34.246.2.81, localpref 200, metric 0, extcommunity RT:65000:111 ? ET:8, path 
2018/05/16 13:30:21 BGP: : 12.0.2.110 rcvd UPDATE wlen 0 attrlen 147 alen 0
2018/05/16 13:30:21 BGP: : 12.0.2.110 rcvd RD 65000:111 [2]:[00:01:21:35:17:95]:[fe80::201:21ff:fe35:1795] label 6 l2vpn evpn
2018/05/16 13:30:21 BGP: : 12.0.2.110 rcvd RD 65000:111 [2]:[00:01:21:35:17:95]/224 label 6 l2vpn evpn
2018/05/16 13:30:22 BGP: : u5:s7 announcing routes upon coalesce timer expiry
2018/05/16 13:30:22 BGP: : u5:s7 send UPDATE w/ attr: nexthop 34.246.2.81, localpref 200, metric 0, extcommunity RT:65000:111 ? ET:8, path 
2018/05/16 13:30:22 BGP: : u5:s7 send MP_REACH for afi/safi 25/70
2018/05/16 13:30:22 BGP: : u5:s7 send UPDATE RD 65000:111 [2]:[00:01:21:35:17:95]/224 label 6 l2vpn evpn
2018/05/16 13:30:22 BGP: : u5:s7 send UPDATE RD 65000:111 [2]:[00:01:21:35:17:95]:[fe80::201:21ff:fe35:1795] label 6 l2vpn evpn
2018/05/16 13:30:22 BGP: : u5:s7 send UPDATE len 185 numpfx 2
2018/05/16 13:30:22 BGP: : u5:s7 12.0.2.110 send UPDATE w/ nexthop 34.246.2.81
2018/05/16 13:30:22 BGP: : u5:s7 send UPDATE w/ attr: nexthop 34.246.2.81, localpref 200, metric 0, extcommunity RT:65000:111 ? ? ? ? ? ? ET:8 Rmac:00:01:21:35:17:95, path 
2018/05/16 13:30:22 BGP: : u5:s7 send MP_REACH for afi/safi 25/70
2018/05/16 13:30:22 BGP: : u5:s7 send UPDATE RD 65534:35174 [5]:[0][100.64.1.0/24]/224 label 6 l2vpn evpn
2018/05/16 13:30:22 BGP: : u5:s7 send UPDATE len 183 numpfx 1
2018/05/16 13:30:22 BGP: : u5:s7 12.0.2.110 send UPDATE w/ nexthop 34.246.2.81
2018/05/16 13:30:22 BGP: : u5:s7 12.0.2.111 send UPDATE w/ nexthop 34.246.2.81
2018/05/16 13:30:22 BGP: : u5:s7 12.0.2.111 send UPDATE w/ nexthop 34.246.2.81
2018/05/16 13:30:22 BGP: : 12.0.2.110 [FSM] Timer (routeadv timer expire)
2018/05/16 13:30:22 BGP: : 12.0.2.111 [FSM] Timer (routeadv timer expire)
javcasalc commented 6 years ago

oops.....closed?

srimohans commented 6 years ago

I will be working on this bug

srimohans commented 6 years ago

@javcasalc

I have a similar setup with Router reflector configured. Tested for route types 2, 3, 5 and I don’t see any issues in my setup and route reflector does exchange all the routes as expected..

Trying to understand more on the issue & setup and I have the below questions.

  1. What does Type: EVPN-Nat mean ? which EVPN Route type it maps to ? I don’t see that this maps to any of Route Types 1 to 5. I also checked Route Types 6, 7, 8 but those are different.
  2. Only Routes of Type EVPN-Nat seems to have the issue. Also routes which has 33.53.23.149 seems to have issue in getting retransmitted via Router Server. Not sure if this has any relevance to the issue.
  3. I didn’t see any error log messages in the logs provided you. Could you confirm if you had attached full set of logs ?
  4. Any other inputs that you can provide which will help me to move forward with this bug analysis ?
javcasalc commented 6 years ago

EVPN-Nat routes include information about nat-ted openflow endpoints. I think is a non-standard implementation made by Nuage/Nokia SR-OS. Let me check it.

Thanks for your help. Javier.

netravnen commented 6 years ago

@javcasalc Would it be possible for you to capture (with fx. tcpdump) the BGP update messages relevant to EVPN route type 'EVPN-Nat' received on in incoming interface on the host running FRR-RR ?

And maybe also posting a snippet of relevant raw config lines from 'peer 1' device you have running SR OS regarding the configured EVPN-Nat route(s)? (Thinking I may be able to find references to information in the SR OS config manuals by Nokia (0),(1),(2))

Was looking at VPN Route Types and draft-ietf-bess-dci-evpn-overlay (co-authored by Nokia people and first edition published Jan 16, 2015). Thinking it is maybe (!) still an IETF draft document which Nokia has implemented in SR OS.

srimohans commented 6 years ago

@javcasalc Thanks for the quick reply. I still didn't find any relevant IETF draft on this. But as @netravnen suggested, may be the packet dumps can reveal on why FRR BGP is not processing these packets on the RR. Please provide this if possible. Let us know. Thanks.

netravnen commented 6 years ago

@ghankins: Would you perhaps have any input to this issue? (Thinking maybe a hint to what Type: EVPN-Nat is exactly)

qlyoung commented 5 years ago

No response from author.