Question 410
At Oakline Municipal Networks, while commissioning a routed spine uplink, the data center fabric team observes: Underlay BGP sessions appear stable but a wrong VLAN tag prevents one adjacency from exchanging routes. What observation should be required before this case is closed?
Explanation
Correct Answer
At Oakline Municipal Networks, while commissioning a routed spine uplink, the decisive validation is: The appropriate Layer 3 adjacency forms and exchanges required routes. It verifies that the change (Correct the tagged subinterface binding and validate neighbor-layer connectivity before BGP changes) resolved the mechanism: The control-plane frames do not reach the intended tagged subinterface.
Incorrect Answers
The referenced next-hop group has no reachable selected member, but here the case reports Underlay BGP sessions appear stable but a wrong VLAN tag prevents one adjacency from exchanging routes. Here, the control-plane frames do not reach the intended tagged subinterface.
A leaf's BGP session resets repeatedly after a minor interface disturbance. Here, the control-plane frames do not reach the intended tagged subinterface.
At Oakline Municipal Networks, while commissioning a routed spine uplink, this option proposes: A controlled single-link failure leaves remote VTEP loopbacks reachable. Although related to Underlay routing, BGP, BFD and ECMP, the proposed change fits another mechanism: The remaining path was omitted from routing adjacencies or next-hop eligibility. The evidence in the current case requires a different result: The appropriate Layer 3 adjacency forms and exchanges required routes.