A county IP fabric’s leaf RIBs keep filling with host and external prefixes that servers never need for east-west reachability. What scaling practice should the fabric team apply first?
Select an answer to reveal the explanation.
Short Explanation
Picture each leaf’s route table like a filing cabinet that somebody stuffed with every flyer from the mailroom. Summarize and filter so leaves only keep what the Clos actually needs for reachability—otherwise the drawers jam as the county grows.
Full Explanation
IP fabric scale depends on prefix discipline: leaves should carry infrastructure and necessary tenant reachability, not unnecessary host or Internet-scale tables. Summarization at appropriate boundaries and export/import filtering keep RIB/FIB growth bounded. Dumping full external tables into the fabric, removing ECMP, or swapping BGP for dense static meshes worsens operations and does not solve prefix bloat.