[j-nsp] BGP EVPN, VXLAN and ECMP

Vincent Bernat bernat at luffy.cx
Thu Mar 29 05:21:31 EDT 2018


So, after trying 17.3R2 and 14.1X53-D63, I have the same behavior with
17.3 and rpd is crashing with 14.1X53.

I have also looked at what the FPC thinks, but I am unsure how the
lookup is done:

TFXPC0(net-connect001.gv2 vty)# show l2 manager mac-table detail

[...]
route table name   : default-switch.4

  mac counters
    maximum   count
    0           3

 mac address          0a:e3:40:00:00:d9
 bd_index             3
 learn vlan           0
 FwdEntry Addr        0x297ee932
 entry flags          0x14
 need sync flag       False
 retry count          0
 In ifl list, In RTT Table
 entry ifl            vtep.32769
 entry hw ifl         vtep.32769
 entry seq number     0
 entry epoch          0
 stp_index            0
 hardware information
 --------------------
    pfe id  0
[...]

TFXPC0(net-connect001.gv2 vty)# show interfaces vtep.32769
    <carriage return>     Completes command
    statistics            Interface statistics
    targeting             Show ae link targeting

TFXPC0(net-connect001.gv2 vty)# show interfaces vtep.32769

Logical interface vtep.32769 (Index 570, Alias-Index 0 Peer-Index 0 ifl address 0x297ee478)
Channel Mode DISABLED (channel1 6  channel2 0)
  Flags: (0x0000000000008000) Up SNMP-Traps
  GEN Flags: (0x0000)
Addresses:
  Media address: Family: Unspecified (0), Chan: 0, Length: 0
IRB ifl BD index 65535
VTEP IP address 10.16.39.3
VTEP L2 RTT index 4
VTEP L3 RTT index 0
VTEP interface type (remote)
Vxlan encapsulation NH id 0
VTEP flags 0x0x0
Reroute Ref: 0, Restore Ref: 0, LRID: 0
Residue Stats in:         0 out:         0
Protocols:
  Protocol: BRIDGE, MTU: 65535 bytes, TCP MSS 0 bytes, Flags: 0x000001400c000000, Route table: 4
    Maximum labels: 0
    Mesh-group index: 0
    Input filter: 0, Output filter: 0, Interface class: 0, Dialer Filter: 0
    Input Simple Filter: 0, Output Simple Filter: 0
    Input implicit filters: None
    Output implicit filters: None
    L2 Input policer: 0, L2 Output policer: 0
    Input policer: 0, Output policer: 0
    RPF fail-filter: 0, Reroute Ref: 0, Restore Ref: 0
    STP Index: 0, Unicast nh_id: 0, Unicast Token: 98
    L2 IFF multi BD : 1, Forwarding Nexthop : 0, Flags 0x0
Media:
  Type: VxLAN End Point, Encapsulation: Ethernet (0x0000000E)
  MTU: 4294967295 bytes, Flags: 0x0000
Dependencies:
  Parent ifl index:     570
Storm control:
  BC: 0, UC: 0, Flags: 0x1
Creation time: Mar 29 08:40:19 2018

So, from here, I don't know where to go.

TFXPC0(net-connect001.gv2 vty)# show route ip prefix 10.16.39.3

IPv4 Route Table 0, default.0, 0x80000:
Destination                       NH IP Addr      Type     NH ID Interface
--------------------------------- --------------- -------- ----- ---------
10.16.39.3                                         Unilist 131332 RT-ifl 0

[...]

IPv4 Route Table 7, :vxlan.7, 0x0:
Destination                       NH IP Addr      Type     NH ID Interface
--------------------------------- --------------- -------- ----- ---------
10.16.39.3                        10.64.128.23    Indirect 131457 RT-ifl 0 xe-1/0/47.183 ifl 566


So, if it uses the table 7, there is only one next-hop. If it uses the
table 0, there are two hops.

TFXPC0(net-connect001.gv2 vty)# show nhdb id 131457 extensive
   ID      Type      Interface    Next Hop Addr    Protocol       Encap     MTU               Flags  PFE internal Flags
-----  --------  -------------  ---------------  ----------  ------------  ----  ------------------  ------------------
131457  Indirect  xe-1/0/47.183  -                      IPv4      Ethernet     0  0x0000000000000000  0x0000000000000000

BFD Session Id: 0
Indirect Target:
 (no-jtree)
   ID      Type      Interface    Next Hop Addr    Protocol       Encap     MTU               Flags  PFE internal Flags
-----  --------  -------------  ---------------  ----------  ------------  ----  ------------------  ------------------
 1767   Unicast  xe-1/0/47.183  10.64.128.23           IPv4      Ethernet     0  0x0000000000000000  0x0000000000000000

  Routing-table id: 0

-- 
Watch out for off-by-one errors.
            - The Elements of Programming Style (Kernighan & Plauger)

 ――――――― Original Message ―――――――
 From: Nitzan Tzelniker <nitzan.tzelniker at gmail.com>
 Sent: 28 mars 2018 19:44 GMT
 Subject: Re: [j-nsp] BGP EVPN, VXLAN and ECMP
 To: bernat at luffy.cx
 Cc: juniper-nsp at puck.nether.net

> Not sure I understand you but both can run 17.3R2 (just time of
> installation )
>
>
> On Wed, Mar 28, 2018 at 10:16 PM Vincent Bernat <bernat at luffy.cx> wrote:
>
>>  ❦ 28 mars 2018 19:06 GMT, Nitzan Tzelniker <nitzan.tzelniker at gmail.com> :
>>
>> > The 5100 run 15.1X53-D63 and the 5110 17.3R2
>>
>> Do you mean the other way around? No 15.1X53 for the 5100.
>> --
>> Use statement labels that mean something.
>>             - The Elements of Programming Style (Kernighan & Plauger)
>>


More information about the juniper-nsp mailing list