Network & Infrastructure / EVPN, VXLAN & Data Center Fabrics
EVPN Type-5 prefix routes and overlay next-hop resolution
An external prefix is visible as an EVPN Type-5 route but is not usable in the tenant VRF. Its overlay resolution model may depend on additional gateway or router information.
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
Inspect Type-5 attributes, route targets, next-hop resolution and the platform's selected IRB model. Compare any required supporting MAC/IP or router-MAC state against a working prefix.
Explain the result
A received prefix advertisement is only one part of forwarding installation. Overlay next-hop dependencies differ by implementation and route model, so generic Type-5 visibility is not sufficient evidence.
Plan the fix
Correct the specific supporting route or VRF/VNI association identified by the platform documentation. Avoid adding static host routes that hide a recurring control-plane dependency failure.
Check the result and rollback
Verify installed forwarding, bidirectional application traffic and withdrawal when the external origin fails. Revert if a static or leaked fallback keeps a failed external prefix falsely reachable.