Question 420
A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Which controlled change best addresses the described requirement?
Explanation
Correct Answer
This action addresses the stated defect: advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability. The underlying constraint is that overlay tunnel endpoint reachability depends on the underlay carrying the VTEP loopback routes. Verify rather than assume success: confirm remote VTEP loopbacks resolve to healthy fabric routes and VXLAN tunnel traffic succeeds.
Incorrect Answers
The option “Correct underlay failure detection and routing convergence within the approved topology and timer policy” is useful in a different setting: A fabric uses two equal-cost underlay next hops yet packets continue toward a failed path following a port outage. The case being tested is: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability. The most relevant correction is “Advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability”.
That choice—“Repair the routed underlay addressing or protocol configuration and then validate overlay sessions”—addresses this other problem: An additional rack joins a Clos fabric with healthy physical interfaces but fails to form underlay neighbor sessions. Here the scenario is: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability. The most relevant correction is “Advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability”.
“Use validated spine-leaf cabling and routing relationships rather than ad hoc lateral transit links” is associated with a distinct issue: A migration plan connects every rack leaf laterally and treats spine devices as only optional edge routers. By contrast, the actual problem is: A newly installed rack can exchange underlay packets but VTEP loopback routes are missing from the remote leaf routing tables. Advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability. The most relevant correction is “Advertise the approved VTEP loopbacks through the fabric underlay and check next-hop reachability”.