Every campus network is some answer to the same question: how do you connect thousands of users to each other and the outside world, reliably, at a cost you can justify, in a way you can grow? The classic answers are the two-tier and three-tier hierarchical designs, and the modern answer is the spine-leaf fabric. Knowing which to reach for, and why, is a CCNP-level design skill that shows up throughout the ENCOR blueprint.
This article covers enterprise campus design at CCNP depth. It extends the QoS cluster guide (design and QoS are the two architecture-domain topics) and connects to the Network Virtualization cluster for the fabric direction.
The Three-Tier Model and Its Layers
The classic hierarchical design has three layers, each with a distinct job. The whole point of the model is that separating these roles makes the network scalable, predictable, and easy to troubleshoot:
The design discipline that matters: the core does nothing but forward fast. You do not put access lists, policy, or anything that adds latency or complexity in the core, because everything depends on it and it must never be the bottleneck or the thing that breaks. Policy and intelligence live at the distribution layer; the access layer connects users; the core just moves packets. Keeping those roles clean is what makes the network operable.
Two-Tier: The Collapsed Core
Not every network needs three tiers. In a smaller campus, a full dedicated core is expensive overkill, so you collapse the core and distribution into one layer. This is the two-tier (collapsed core) design: access switches connect to a pair of collapsed core/distribution switches that do both jobs.
The decision rule is about scale and the number of distribution blocks. If you have one or two buildings and a handful of distribution switches, a dedicated core adds cost and hops for no benefit, so collapse it. When you have many distribution blocks (multiple buildings, thousands of users), a dedicated core is worth it: it gives every distribution block a single, simple, high-speed point to reach every other block, without a full mesh of distribution-to-distribution links. The core exists to avoid that mesh.
The Layer 2 / Layer 3 Boundary
The most consequential design decision in a campus is where Layer 2 ends and Layer 3 begins, because it determines your failure domains, your spanning-tree footprint, and your convergence behaviour.
Pushing Layer 3 down to the access layer (routed access) shrinks the spanning-tree domain to a single switch and lets routing (which converges faster and more predictably than STP) handle failures. The trade-off is that VLANs can no longer span multiple access switches, which some applications and wireless designs assume. The traditional Layer-2-access model keeps VLANs flexible but pays for it with spanning tree and FHRP complexity and slower convergence. The trend is toward routed access; the exam expects you to know both and their trade-offs.
Designing for Failure
A campus design is only as good as its behaviour when something breaks. The principles:
- No single points of failure at the aggregation and core. Distribution and core switches come in pairs, with redundant links, so any single device or link failure is survivable. The access layer is often single-homed per user (a user's own switch failing only affects that user), but the layers above must be redundant.
- Redundant links, not just redundant devices. Two core switches with a single link between the distribution and each is not truly redundant. Design the link topology so any single link loss has a path around it.
- Fast convergence. Whatever fails, the network must reroute quickly. This is where routed access (fast IGP convergence), BFD for sub-second detection, and the high-availability techniques (SSO, NSF, graceful restart) all contribute.
- Consistent, predictable structure. The reason hierarchy matters is not aesthetics; a predictable structure means you can reason about failure, capacity, and change. An ad-hoc topology cannot be reasoned about.
The Modern Direction: Spine-Leaf and Fabric
The three-tier model was designed for a traffic pattern that has changed. It assumes most traffic is north-south (users to the internet or data centre), which is why the core is a small fast backbone. Modern data centres and increasingly campuses see huge east-west traffic (server to server, service to service), and the three-tier model handles that poorly, because east-west traffic has to go up to the core and back down.
The answer is spine-leaf: every leaf (access) connects to every spine (aggregation), so any leaf is exactly two hops from any other leaf, and east-west bandwidth scales by adding spines. Combined with a VXLAN overlay and BGP EVPN control plane, this is the modern data-centre fabric, and in the campus it becomes Cisco SD-Access. The hierarchical model has not disappeared, most campuses still run it, but the fabric direction is where new large-scale designs are heading, and the CCNP expects you to understand both and when each fits.
FAQ
Two-tier or three-tier?
Two-tier (collapsed core) for small-to-medium campuses with few distribution blocks, where a dedicated core is overkill. Three-tier when you have many distribution blocks and need the core to avoid a distribution-to-distribution mesh.
What should the core layer do?
Only forward packets, as fast and reliably as possible. No ACLs, no policy, no complexity. Everything depends on the core, so it must never be the bottleneck or the fragile part.
Where should the Layer 2 / Layer 3 boundary be?
The modern preference is routed access (L3 at the access switch), which shrinks the STP domain and converges fast, at the cost of VLANs not spanning switches. The traditional model puts L3 at distribution, keeping VLANs flexible but needing STP and FHRP.
Is spine-leaf replacing three-tier?
For large-scale and east-west-heavy designs, increasingly yes, especially in the data centre and as SD-Access in the campus. But most campuses still run hierarchical designs, and the CCNP expects you to know both.
How many core switches should I have?
At least two, with redundant links, so no single device or link failure isolates a distribution block. Redundancy at the core and distribution is non-negotiable; the access layer is often single-homed per user.
Key Takeaways
- The three-tier model separates access (users connect), distribution (aggregation, L2/L3 boundary, policy), and core (fast backbone only).
- The core does nothing but forward fast. No policy or complexity in the core; intelligence lives at distribution.
- Two-tier (collapsed core) merges core and distribution for smaller campuses; three-tier scales to many distribution blocks.
- The Layer 2 / Layer 3 boundary is the key decision: routed access (fast, small STP domain, VLANs do not span) vs L2-access/L3-distribution (flexible VLANs, needs STP and FHRP).
- Design for failure: redundant devices and links at aggregation/core, fast convergence (routed access, BFD, SSO/NSF), and predictable structure.
- Spine-leaf is the modern direction for east-west-heavy and large-scale designs (data-centre fabric, campus SD-Access), but hierarchical designs still dominate. Know both.
Next: High availability techniques (SSO, NSF, GR), or the QoS cluster guide.
