Network & Infrastructure / EVPN, VXLAN & Data Center Fabrics
Route distinguisher versus route target in EVPN troubleshooting
An operator changes a route distinguisher to fix an import problem. The change churns advertisements while the receiving tenant still lacks the route because import policy remains wrong.
Environment and inputs: BGP EVPN overlays on a routed underlay; supported route types and multihoming behavior depend on the network OS. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Record the route key, RD, route targets, origin VTEP and import decision for a single endpoint. Compare uniqueness requirements separately from tenant membership policy.
Explain the result
The RD makes otherwise overlapping VPN routes distinguishable; route targets drive import/export membership. They have different roles even when deployment templates derive both from related numbers.
Plan the fix
Restore deliberate unique route identity and correct only the mismatched membership policy. Review auto-derived values carefully when changing ASNs, VNIs or per-device numbering conventions.
Check the result and rollback
Verify that redundant origins remain distinguishable and the intended VRF imports the route. Roll back if paths collapse unexpectedly or a tenant begins importing unrelated reachability.