Two municipal tenant hosts are mapped to the same VNI number on different leaves, but each leaf mistakenly binds that VNI into a different VRF. What is the data-plane consequence?
Select an answer to reveal the explanation.
Short Explanation
Same hallway number painted on two doors that open into different locked offices—chaos. The VNI has to land in the same VRF/bridge-domain story on every leaf or isolation and routing go sideways. Match the bindings, don’t just match the integer.
Full Explanation
A VNI is only meaningful when consistently bound to the intended bridge domain and, for L3, the correct routing instance/VRF. Identical VNI IDs with divergent VRF bindings produce inconsistent classification after decap and break the isolation model operators expected. Underlay ECMP and DSCP behavior do not reconcile tenant routing-instance mistakes. Verification of VNI-to-VRF/bridge-domain maps on each municipal leaf is a core data-plane correctness check.