After a cabling change, one municipal spine carries no production traffic while peers are busy. What should engineers verify first on the leaf-spine fabric links?
Select an answer to reveal the explanation.
Short Explanation
If one spine is a ghost town after a recable, start with the boring stuff: is the L3 link up and is BGP (or the underlay IGP) actually adjacent? Dark optics and dead sessions move zero packets.
Full Explanation
Uneven spine load after cabling often traces to down interfaces, wrong L3 config, or missing underlay adjacency/BGP on specific leaf-spine links. Operators should verify interface admin/link state and routing-session health before blaming overlay route types or unrelated tools. Console baud rate and documentation search are not primary fabric-traffic checks.