A leaf redistributes connected routes into BGP with a loose policy and leaks tenant networks into the underlay. What routing-hygiene principle did the fabric violate?
Select an answer to reveal the explanation.
Short Explanation
The underlay phone book should list fabric infrastructure—not every tenant hallway. Loose redistribution spills department nets into the Clos and makes troubleshooting miserable. Keep tenant reachability in the overlay/tenant control plane where it belongs.
Full Explanation
IP fabric underlays are meant to carry infrastructure reachability such as loopbacks, fabric links, and other prefixes needed for fabric operation. Redistributing arbitrary tenant connected networks pollutes the underlay and blurs overlay boundaries. That leak is not required for ECMP or spine bridging. Apply export policy discipline so only intended infrastructure prefixes enter underlay BGP or IGP.