Collapsed core

Why it exists

Cisco Campus LAN/WLAN CVDs describe collapsing distribution and core for smaller sites (often one building or a few adjacent buildings with adequate fiber). The separate core tier is omitted so distribution becomes the Layer-3 aggregation point for access and often for WAN/Internet-edge/services connectivity.

Visual walkthrough

Scaling & math

Without a distinct distribution↔core hop, oversubscription planning collapses to the access↔aggregation relationship. Cisco CVDs treat ratios as business-driven and note that historical implementations have used access↔aggregation oversubscription up to 20:1 — an observed range, not a mandate. Exact maximum access switches per collapsed-core platform is platform-specific (unknown here).

When it breaks

• One collapsed-core member is down or drained; dual-homed closets should stay up with reduced HA capacity.

  Cause. Single CC chassis/stack member failure or maintenance.

  Mitigation. Confirm access dual-homing and FHRP/routing adjacency on the surviving member before maintenance; size the pair for acceptable capacity loss.

• Site-wide L3 aggregation and typically WAN attachment fail together.

  Cause. Both collapsed-core members unavailable, or a shared control-plane fault spanning the pair.

  Mitigation. Treat the pair as a single change/fault domain for major work; prefer designs with stronger isolation when that blast radius is unacceptable.

• A maintenance window on aggregation also risks WAN/services co-located on the same pair.

  Cause. Weaker change isolation than a dedicated core that separates user aggregation from edge services.

  Mitigation. Schedule dual impacts deliberately, or keep WAN/services on a more isolated attachment when the CVD recommends a dedicated core.

• Large STP/broadcast domain; slow convergence or instability across many access closets.

  Cause. Layer-2 stretched from many access switches into the collapsed core without segmentation.

  Mitigation. Limit L2 domains; prefer L3 at the collapsed core with smaller access VLANs where the design allows.

• Loss or latency under load even though the topology is “up”.

  Cause. Access↔aggregation uplink capacity oversubscribed relative to demand — a planning choice called out in CVD language (including historical examples up to 20:1).

  Mitigation. Recalculate access↔aggregation oversubscription against business requirements; add uplinks or reduce contention.

Misconceptions

• “Collapsed core means a single non-redundant switch.” — CVD language describes a redundant collapsed-core / distribution pair (or logical pair), not a lone box.
• “Always prefer three-tier; collapsed core is outdated.” — Cisco documents collapsed core as appropriate for smaller sites and calls out geographic dispersion / fiber cost as reasons to keep a dedicated core.
• “Access↔aggregation oversubscription is fixed at 20:1.” — CVDs treat ratios as business-driven; “up to 20:1” is an implemented historical range, not a universal default.

Reference expression

Primary teaching sources are Cisco Campus LAN and Wireless LAN CVD language, Enterprise Campus 3.0 architecture overview (when not to stay collapsed), and the Aug 2013 Campus Wired LAN configuration files guide for two-tier collapsed-core wording. Short excerpts only — follow the linked sources for full validated designs. review: draft.

Standards & sources

• ●cisco-campus-lan-wlan-cvd · Two-tier / collapsed core campus patternPrimary source, retrieved 2026-09-20. Campus LAN and Wireless LAN Solution Design Guide (CVD)Campus LAN and Wireless LAN Solution Design Guide (CVD) — Two-tier / collapsed core campus pattern
• ●cisco-campus-lan-wlan-cvd-pdf · CVD PDF companionPrimary source, retrieved 2026-09-20. Campus LAN and Wireless LAN Design Guide (October 2016 PDF)Campus LAN and Wireless LAN Design Guide (October 2016 PDF) — CVD PDF companion
• ●cisco-enterprise-campus-3 · When not to collapse; change domainsPrimary source, retrieved 2026-09-20. Enterprise Campus 3.0 Architecture: Overview and FrameworkEnterprise Campus 3.0 Architecture: Overview and Framework — When not to collapse; change domains
• ●cisco-campus-wired-cfg-2013 · Two-tier collapsed-core configuration languagePrimary source, retrieved 2026-09-20. Campus Wired LAN Configuration Files Guide (August 2013)Campus Wired LAN Configuration Files Guide (August 2013) — Two-tier collapsed-core configuration language
• ●cisco-campus-wired-2014 · Campus wired LAN design lineagePrimary source, retrieved 2026-09-20. Campus Wired LAN Technology Design Guide (August 2014)Campus Wired LAN Technology Design Guide (August 2014) — Campus wired LAN design lineage

Known unknowns

• Exact maximum access switches or ports per collapsed-core platform are platform-specific and not tabulated here.
• FHRP timers, STP mode defaults, and WAN peering details vary by vendor OS and site policy — not asserted as universal defaults.

Check yourself

1. What does “collapsed core” omit compared with classic three-tier campus?

   • The access tier
   • A separate dedicated core tier
   • All Layer-3 routing
   • WAN attachment

   Answer: A separate dedicated core tier. Distribution takes on core aggregation roles so a separate core pair is not required for that site size.

2. Where do access switches typically dual-home in this pattern?

   • Only to the WAN firewall
   • To both members of the collapsed-core pair
   • Only to other access switches
   • Directly to the Internet

   Answer: To both members of the collapsed-core pair. Dual-homing into the CC pair is how a single uplink/CC member failure is survived.

3. Why can maintenance on the collapsed core be riskier than on a dedicated core?

   • Because STP cannot run at access
   • Because user aggregation and often WAN/services share the same pair’s change domain
   • Because dual-homing is forbidden
   • Because oversubscription is always 1:1

   Answer: Because user aggregation and often WAN/services share the same pair’s change domain. Enterprise Campus guidance highlights weaker change isolation when edge and aggregation share the collapsed pair.

4. Cisco CVD language on access↔aggregation oversubscription treats 20:1 as…

   • A mandatory default for every campus
   • A business-driven ratio, with historical implementations up to 20:1 noted
   • Impossible on copper
   • Only valid for wireless

   Answer: A business-driven ratio, with historical implementations up to 20:1 noted. Ratios are business-driven; “up to 20:1” is documented as implemented, not mandated.

5. When does Cisco guidance push away from staying collapsed?

   • Any site with more than one VLAN
   • Geographic dispersion with many buildings and long fiber runs raising aggregation cost
   • Whenever OSPF is used
   • Whenever hosts are dual-homed

   Answer: Geographic dispersion with many buildings and long fiber runs raising aggregation cost. Fiber cost and aggregation fan-in across dispersed buildings are cited reasons for a dedicated core.

6. Inter-VLAN east-west in this teaching topology typically…

   • Stays only on the access switch with no gateway
   • Climbs to the collapsed core for routing, then returns to access
   • Requires a spine tier
   • Must hairpin through the public Internet

   Answer: Climbs to the collapsed core for routing, then returns to access. L3 gateways concentrate on the collapsed core in the two-tier pattern.

7. Is collapsed core the right class for a large east-west DC fabric?

   • Yes — it replaces Clos
   • No — DC east-west scale is a different architecture class (e.g. spine-leaf)
   • Yes — if you add more VLANs
   • Only with VXLAN

   Answer: No — DC east-west scale is a different architecture class (e.g. spine-leaf). Campus collapsed core is not a substitute for DC Clos fabrics.

8. Primary sources used on this page include…

   • Anonymous forum posts only
   • Cisco Campus LAN/WLAN CVD and Enterprise Campus 3.0 overview materials
   • Invented show-command captures
   • Unlabeled AI summaries

   Answer: Cisco Campus LAN/WLAN CVD and Enterprise Campus 3.0 overview materials. Claims are tied to CVD / campus architecture primary docs with provenance.