A municipal leaf advertises EVPN routes for a VNI, but peer leaves have no matching route-target import. What is the likely learning result?
Select an answer to reveal the explanation.
Short Explanation
Route targets are the membership badges on EVPN routes—if the other leaves never import your badge, they politely ignore your MAC/IP ads. The routes can leave the speaker and still go nowhere useful. That is a control-plane policy miss, not a cosmetic SNMP issue.
Full Explanation
EVPN uses route targets (and related routing-instance policy) to define which MAC-VRF/IP-VRF members import which EVPN routes. Export without a matching import on peers means advertisements are not installed into the intended tenant tables, breaking remote learning for that VNI/VRF membership. VNIs do not bypass RT policy, and spines do not generally rewrite RTs to fix misaligned leaf policy. Troubleshooting EVPN-VXLAN “advertised but not learned” issues should include RT import/export verification.