Problem
Batfish does not model remote IMET (Type 3) routes under the local VNI's Route Distinguisher. NX-OS duplicates received IMET routes into each local VNI RD context, but Batfish only stores them under the originator's RD.
Observed In
nxos_evpn_l2vni
Symptoms
EVPN RIB validation reports extra routes on the NX-OS device that Batfish does not have. For example, NX-1 sees 2.2.2.2/32 (remote IMET) under RD 1.1.1.1:32777 (local VNI 5010), but Batfish only has that route under 2.2.2.2:32777.
Configuration Patterns
NX-OS L2VNI EVPN with iBGP peering between VTEPs
Next Steps
Investigate whether Batfish should replicate remote IMET routes under the local VNI RD to match NX-OS behavior, or whether the validation should filter these duplicates.
Problem
Batfish does not model remote IMET (Type 3) routes under the local VNI's Route Distinguisher. NX-OS duplicates received IMET routes into each local VNI RD context, but Batfish only stores them under the originator's RD.
Observed In
nxos_evpn_l2vni
Symptoms
EVPN RIB validation reports extra routes on the NX-OS device that Batfish does not have. For example, NX-1 sees
2.2.2.2/32(remote IMET) under RD1.1.1.1:32777(local VNI 5010), but Batfish only has that route under2.2.2.2:32777.Configuration Patterns
NX-OS L2VNI EVPN with iBGP peering between VTEPs
Next Steps
Investigate whether Batfish should replicate remote IMET routes under the local VNI RD to match NX-OS behavior, or whether the validation should filter these duplicates.