Question 60
A new spine switch uses an ordinary Ethernet MTU while adjacent leaf paths assume extra VXLAN header overhead, so large tenant frames fail intermittently. 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 adds outer transport headers, making the required underlay packet size greater than the original tenant Ethernet payload. Apply the recurring practice: Include encapsulated MTU and every ECMP path in fabric acceptance and upgrade testing. The previous example was: A new spine switch uses an ordinary Ethernet MTU while adjacent leaf paths assume extra VXLAN header overhead, so large tenant frames fail intermittently.
Incorrect Answers
Document loopback allocation and verify its route advertisement during device replacement and uplink maintenance. That concerns VTEP loopback source identity stability, while the issue here is underlay MTU for VXLAN encapsulation. Measure encapsulation overhead and configure a consistent supported underlay MTU, or constrain overlay payload sizes according to the design.
Physical link state does not guarantee underlay routes if the intended BGP neighbors or address-family configuration fail. However, the present prevention decision is grounded in: A new spine switch uses an ordinary Ethernet MTU while adjacent leaf paths assume extra VXLAN header overhead, so large tenant frames fail intermittently. For this issue, measure encapsulation overhead and configure a consistent supported underlay MTU, or constrain overlay payload sizes according to the design.
Include route type and tenant VRF checks in intersubnet rollout procedures. Here, vXLAN adds outer transport headers, making the required underlay packet size greater than the original tenant Ethernet payload.