Question 330
At Meadowridge Municipal Networks, while verifying multiple equal-cost paths, the data center fabric team observes: A leaf can reach its directly connected spine but not the loopback used for BGP sessions. What observation should be required before this case is closed?
Explanation
Correct Answer
At Meadowridge Municipal Networks, while verifying multiple equal-cost paths, the decisive validation is: The loopback addresses ping in the underlay and the corresponding BGP transport succeeds. It verifies that the change (Provide correct loopback reachability through the intended routing design) resolved the mechanism: The underlay lacks a route to the remote loopback or its advertised prefix.
Incorrect Answers
At Meadowridge Municipal Networks, while verifying multiple equal-cost paths, this option proposes: The forwarding table matches the approved spine preference and still has required backup paths. Using that approach would investigate Traffic follows an unexpected spine after a route-policy update instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The underlay lacks a route to the remote loopback or its advertised prefix.
At Meadowridge Municipal Networks, while verifying multiple equal-cost paths, this option proposes: The remote route resolves to a usable forwarding next hop without fallback leakage. The alternative focuses on The received route's next hop cannot be resolved in the relevant routing instance, not on the stated defect. For this scenario the expected acceptance result would be: The loopback addresses ping in the underlay and the corresponding BGP transport succeeds.
At Meadowridge Municipal Networks, while verifying multiple equal-cost paths, this option proposes: A policy test exports required fabric routes but denies representative tenant prefixes. It tests a different symptom: A route policy intended to permit fabric loopbacks inadvertently permits all tenant prefixes. For the observed case, the relevant distinction is The underlay lacks a route to the remote loopback or its advertised prefix, with verification: The loopback addresses ping in the underlay and the corresponding BGP transport succeeds.