Question 40
A new rack comes online with correct cabling, yet mismatched BGP neighbor ASNs prevent underlay prefix exchange and overlay traffic cannot form usable paths. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
A lasting control should detect the original error before release. Check interface state, BGP session state and learned prefix coverage as separate fabric health criteria. That is important in this case because physical link state does not guarantee underlay routes if the intended BGP neighbors or address-family configuration fail. The scenario was: A new rack comes online with correct cabling, yet mismatched BGP neighbor ASNs prevent underlay prefix exchange and overlay traffic cannot form usable paths.
Incorrect Answers
Correlate MAC learning, EVPN advertisement and remote route import during server moves. That concerns EVPN control-plane MAC location advertisement, while the issue here is BGP underlay adjacency versus established overlay. Compare the peer addressing and ASNs on leaf and spine, establish the supported BGP underlay sessions, and verify route installation.
A distributed anycast gateway design requires a consistent logical gateway identity across participating VTEPs for the same tenant segment. For this issue, compare the peer addressing and ASNs on leaf and spine, establish the supported BGP underlay sessions, and verify route installation.
Include endpoint move tests and MAC route convergence monitoring during host virtualization migrations. Here, physical link state does not guarantee underlay routes if the intended BGP neighbors or address-family configuration fail.