County IT sees intermittent overlay drops for fabric clients while underlay pings between edges succeed at small sizes. Which Assurance-driven conclusion best links those symptoms?
Select an answer to reveal the explanation.
Short Explanation
Little pings are like shipping postcards—they squeeze through a too-small chute that packages cannot. VXLAN adds header bulk, so an undersized underlay MTU drops real overlay frames while 64-byte pings still smile. Assurance helps connect those underlay MTU clues to the overlay pain you are chasing.
Full Explanation
County IT seeing intermittent overlay drops while small underlay pings between edges succeed is a classic VXLAN MTU symptom. Tiny ICMP can pass while larger encapsulated overlay frames exceed underlay MTU and drop. Assurance insights help correlate client/overlay loss with underlay path MTU problems across civic fabric hops.
Overlay drops always meaning the control-plane node lost its AAA RADIUS key invents a single root cause; authentication key loss is a different failure class and is not implied by successful small pings with overlay loss.
Small underlay pings proving VXLAN MTU is adequate end-to-end is false by concept—small probes do not exercise inner-frame-plus-VXLAN overhead.
Overlay drops indicating SGTs must be removed from all VN route targets confuses policy tagging with MTU/encapsulation failures.
Exam caveat: measure underlay MTU with oversized pings/DF bit or platform MTU tools hop-by-hop, including spines and borders, not only edge-to-edge wishful thinking.
Operational check: run DF-bit pings sized for VXLAN overhead between locators, raise underlay MTU where short, and confirm overlay transfers succeed. Capture MTU values in the county fabric underlay standard before declaring the site healthy.