A metro EBGP Clos design assigns a private ASN per leaf. What concept does that ASN allocation illustrate?
Select an answer to reveal the explanation.
Short Explanation
Giving each leaf its own private ASN is a familiar EBGP Clos phonebook trick—external BGP hop by hop without inventing public ASN paperwork. It is a pattern family, not a law that forbids other designs. Spines get ASNs in the plan too.
Full Explanation
Per-leaf private ASN allocation is a common EBGP Clos approach that makes each leaf-spine session external and supports multipath-friendly designs. It is a conceptual pattern, not the only valid template, and it does not mandate IBGP route reflection. Leaves do not inherit server ASNs, and private ASNs are not reserved only for border routers. Document the ASN plan alongside multipath and policy choices.