Arista EOS: evpn rib routes not in route table

[rmcmilli]

Routes present in EVPN table on fabric switches aren't redistributing into main routing table. bf.q.traceroute() fails as well.

In this example the route 115.103.155.156/32 is received from a non-EVPN router attached to ny5-tor3-1

Current behavior

Route Exists in EVPN RIB:

bf.q.evpnRib(nodes="ny5-tor4-1", network="115.103.155.156/32").answer().frame().head(5)

Route does not exist in route table:

bf.q.routes(nodes="ny5-tor4-1", network="115.103.155.156/32").answer().frame().head(5)

Expected Behavior

Route Exists in EVPN RIB:

bf.q.evpnRib(nodes="ny5-tor3-1", network="115.103.155.156/32").answer().frame().head(5)

Route exists in route table:

bf.q.routes(nodes="ny5-tor3-1", network="115.103.155.156/32").answer().frame().head(5)

Snapshot:
snapshot.tar.gz

[dhalperi]

Thanks! The Arista EVPN code was largely authored by @jeffkala so I'm looping him in.

[jeffkala]

I had done most of the juniper evpn code, don't recall adding much on the Arista front but can still try to take a look.