A change window adds a new VNI on a municipal leaf but omits flood-list or EVPN membership for that VNI. What incomplete-enablement failure should be expected?
Select an answer to reveal the explanation.
Short Explanation
Painting a new hallway number on one door doesn’t invite the other buildings to the party. The VNI needs membership in EVPN or the flood/replication list, not just a local definition. Incomplete enablement is how ARP goes quiet after a ‘successful’ change.
Full Explanation
Defining a VNI locally is insufficient unless the leaf also participates in the fabric’s distribution mechanism for that segment—EVPN route exchange and/or BUM flood lists / ingress-replication lists. Without membership, remote VTEPs will not receive multi-destination traffic or appropriate learning for that VNI. Operators should validate both local mapping and fabric membership after changes. Civic change checklists should include this second step explicitly.