BGP EVPN sessions are Established, yet a leaf installs no remote tenant routes. Investigation shows the route-target import is missing on the routing instance. What is the right fix focus?
Select an answer to reveal the explanation.
Short Explanation
Session up but empty tenant tables usually means the RT membership badge is wrong or missing — fix import/export on the EVPN instance. Twiddling OSPF hellos or cloning RDs will not subscribe you to the right routes.
Full Explanation
When BGP EVPN sessions are Established yet a leaf installs no remote tenant routes, a missing route-target import on the routing instance is a classic cause. The fix focus is correcting EVPN instance route-target import/export so membership matches the tenant VRF/VNI design. Increasing OSPF hello timers does not install Type-5 into an EVPN VRF. Assigning the same RD to every VRF collapses uniqueness and is harmful, not a fix. Removing VXLAN for pure Q-in-Q abandons the architecture. Exam caveat: export-only configuration on one side with no import on the other yields empty tables despite green BGP—verify both directions of RT policy. Operational check: compare RT export on advertisers with import on the municipal leaf, add the missing import, confirm Type-2/Type-5 appear in the tenant instance, and ensure other tenants remain isolated. Prefer RT fix evidence (before/after EVPN table counts) in change records over simply noting that BGP was Established. Prefer RT fix evidence (before/after EVPN table counts) in change records over simply noting that BGP was Established. Prefer RT fix evidence (before/after EVPN table counts) in change records over simply noting that BGP was Established.