network·Cisco hierarchical internetworking model (core/distribution/access)·enterprise, it·complexity 3/3·since v0.6.0
Three-tier enterprise campus network
Classic Cisco hierarchical campus — Internet/WAN edge, redundant core switches with a LAG uplink, a distribution layer, and an access layer feeding a server farm. The canonical core/distribution/access model.
For the network engineer
network·§ —
↘ preview
100%
UTF-8 · LF · 23 lines · 565 chars✓ parsed·13.3 ms·12.8 KB SVG
Scenario
A network engineer is drawing the as-built for a campus that follows Cisco's three-tier hierarchical model. The tier: attribute on each device drives the banding, so the diagram lands in the canonical edge → core → distribution → access rows automatically — no manual placement.
What the diagram shows
tier:banding —edge,core,distribution,accessplace devices in fixed rows top-to-bottom. Endpoints (the server farm) hang below their switch.- The redundant core —
cs1 == cs2 : lag 40Gis the EtherChannel uplink, drawn as a double line with a 40G label (==is shorthand for a LAG link). - Shorthand —
a1 a2 a3 : switch tier: accessdeclares three identical access switches on one line. - The server farm —
serverfarm ... count: 4draws a stacked icon labelled ×4.
Annotation key
| Element | Meaning |
|---|---|
Double line + 40G | Aggregated link (LAG / EtherChannel) |
tier: core etc. | Hierarchical band assignment |
Trunk · VLAN 100 | Server-farm uplink trunk |
For a two-tier "collapsed core" just drop the distribution devices; for a data-center fabric use layout: spine-leaf instead.