Municipal ops wants dashboards for BGP underlay session state across spines. Why is that monitoring focus fabric-critical?
Select an answer to reveal the explanation.
Short Explanation
The underlay BGP sessions are the steel beams holding up the building—if a beam drops, the overlay apartment tenants feel it next. Dashboarding peer state across spines is how the NOC sees a crack before the floor sags. Guest Wi-Fi captive portals are a totally different movie.
Full Explanation
In a leaf-spine IP fabric, BGP (or another underlay IGP/EGP design) establishes the reachability that VTEPs and overlays rely on. Monitoring underlay BGP session state across spines therefore directly reflects fabric health. Treating those sessions as irrelevant, assuming spines only bridge, or tying the requirement only to wireless captive portals misstates the role of underlay routing in Juniper DC fabrics.