Question 50
A spine-link migration changes a transit interface address and unexpectedly disrupts VXLAN reachability because the design never used a stable VTEP identity. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
The preventive practice is aligned with the diagnosed mechanism, not an unrelated protection. Document loopback allocation and verify its route advertisement during device replacement and uplink maintenance. Logical tunnel endpoint identity should be separated from individual physical transport paths.
Incorrect Answers
EVPN Type 5 routes can carry IP prefix reachability for routed overlays independently of individual MAC/IP Type 2 host advertisements. For the current prevention question, the evidence instead states: A spine-link migration changes a transit interface address and unexpectedly disrupts VXLAN reachability because the design never used a stable VTEP identity. Here, a VTEP endpoint requires an appropriate stable IP identity reachable in the underlay, commonly on a loopback interface.
VXLAN tunnel endpoints encapsulate tenant frames at ingress and decapsulate at egress using the overlay VNI context. However, the present prevention decision is grounded in: A spine-link migration changes a transit interface address and unexpectedly disrupts VXLAN reachability because the design never used a stable VTEP identity. For this issue, confirm the intended VTEP source address and advertise its loopback through the underlay so transport changes do not silently change endpoint identity.
Include endpoint move tests and MAC route convergence monitoring during host virtualization migrations. Here, a VTEP endpoint requires an appropriate stable IP identity reachable in the underlay, commonly on a loopback interface.