A single municipal border leaf terminates every DCI stitch for three sites and now shows high control-plane and forwarding load. What design lesson should the fabric team apply?
Select an answer to reveal the explanation.
Short Explanation
One border doing every stitch is like one bridge carrying every city bus route—it works until rush hour. Stitch gateways need horsepower and backup paths, not a lone hero leaf. Scale and redundancy belong in the DCI placement plan from day one.
Full Explanation
Stitch points concentrate overlay import/export and often re-encapsulation work. A solitary border leaf can become a control-plane and data-plane bottleneck as tenants and MAC/IP churn grow. Capacity planning, distributing stitch roles, and providing redundancy are required; offloading blindly to a provider CPE, dropping EVPN for flood-and-learn, or collapsing all tenants into one VNI are not sound scale answers.