Question 180
A remote VTEP receives encapsulated traffic for a configured VNI but does not deliver it locally because its service mapping fails at decapsulation. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
This control reduces recurrence of the same class of failure: VXLAN tunnel endpoints encapsulate tenant frames at ingress and decapsulate at egress using the overlay VNI context. Apply the recurring practice: Include encapsulation/decapsulation and VNI validation in packet-level overlay fault isolation. The previous example was: A remote VTEP receives encapsulated traffic for a configured VNI but does not deliver it locally because its service mapping fails at decapsulation.
Incorrect Answers
Maintain automated checks for VNI service identity during VLAN renumbering and rack expansion. That concerns VXLAN VNI-to-VLAN mapping, while the issue here is ingress VTEP encapsulation and egress decapsulation. Trace VTEP source/destination, outer transport and VNI at ingress and egress, then align the receiving bridge-domain attachment.
Edge-routed bridging places an appropriate distributed Layer 3 gateway function at fabric edges for attached virtual networks. However, the present prevention decision is grounded in: A remote VTEP receives encapsulated traffic for a configured VNI but does not deliver it locally because its service mapping fails at decapsulation. For this issue, trace VTEP source/destination, outer transport and VNI at ingress and egress, then align the receiving bridge-domain attachment.
Check BUM membership whenever adding VNIs or extending a bridge domain to a new rack. Here, vXLAN tunnel endpoints encapsulate tenant frames at ingress and decapsulate at egress using the overlay VNI context.