Problem
Batfish sets origin_type=incomplete for connected routes redistributed into EVPN Type 5, but Junos devices report origin_type=IGP for these routes.
Technical Details
When a Junos device redistributes a connected route into EVPN Type 5 (via ip-prefix-routes under protocols evpn), the resulting EVPN route has origin type IGP (I). Batfish models this redistribution with origin_type=incomplete, which is the standard for redistributed routes in conventional BGP but not correct for Junos EVPN Type 5 connected redistribution.
Observed In
junos_evpn_type5 lab -- route 10.99.0.0/31 in RD 172.16.0.100:10000 on node1-1, node2-1, and router1.
Symptoms
EVPN RIB validation fails with:
('172.16.0.100:10000', '10.99.0.0/31'): {
'origin_type': 'Batfish: incomplete, real: I'
}
Configuration Patterns
Junos EVPN Type 5 with connected routes in a VRF that has protocols evpn ip-prefix-routes configured. The connected route (e.g., from a directly-attached interface) is exported into EVPN and distributed to remote PEs.
Next Steps
Update Batfish's EVPN Type 5 export logic to use origin_type=igp when redistributing connected routes on Junos, matching the observed device behavior.
Problem
Batfish sets
origin_type=incompletefor connected routes redistributed into EVPN Type 5, but Junos devices reportorigin_type=IGPfor these routes.Technical Details
When a Junos device redistributes a connected route into EVPN Type 5 (via
ip-prefix-routesunderprotocols evpn), the resulting EVPN route has origin type IGP (I). Batfish models this redistribution withorigin_type=incomplete, which is the standard for redistributed routes in conventional BGP but not correct for Junos EVPN Type 5 connected redistribution.Observed In
junos_evpn_type5 lab -- route
10.99.0.0/31in RD172.16.0.100:10000on node1-1, node2-1, and router1.Symptoms
EVPN RIB validation fails with:
Configuration Patterns
Junos EVPN Type 5 with connected routes in a VRF that has
protocols evpn ip-prefix-routesconfigured. The connected route (e.g., from a directly-attached interface) is exported into EVPN and distributed to remote PEs.Next Steps
Update Batfish's EVPN Type 5 export logic to use
origin_type=igpwhen redistributing connected routes on Junos, matching the observed device behavior.