The enterprise network: what you will learn and the big picture
What you will learn in this module. By the end of these chapters you will be able to look at any enterprise network drawing and explain why it is built the way it is: why there are two of every box, where Layer 2 ends and Layer 3 begins, why the spanning-tree root and the default gateway must live on the same switch, how a supervisor can fail without users noticing, which wireless deployment model fits a campus or a branch, when a workload belongs in the cloud, and how a switch actually forwards a frame in hardware. You will also build a redundant collapsed-core block in the lab and review a broken design until traffic stops taking the long way.
Prerequisites. You should be comfortable with CCNA-level VLANs and trunks, spanning tree (root bridge, root port, blocking), EtherChannel with LACP, HSRP basics and single-area OSPF. If any of these feel shaky, revisit the CCNA modules on STP, EtherChannel and FHRP first. This module does not re-teach them; it uses them as building blocks for design.
An analogy: a network is a city's road system
Picture a well-planned city. Every house sits on a quiet local lane. Lanes feed into arterial roads where the traffic lights, speed checks and turn restrictions live. Arterial roads join a fast highway with no traffic lights at all, because its only job is to move a lot of cars quickly between districts. Every district is planned as a copy of the same template, so a new district can be added without redesigning the city. If a lane is dug up for repairs, only that street is affected, and there is always a second road into every district.
An enterprise network works the same way. Local lanes are the access layer where users plug in. Arterial roads are the distribution layer where policy and routing decisions happen. The highway is the core. Districts are modules (a building, a data centre, a WAN edge). The second road is redundancy. The rule that a dug-up lane only affects one street is the idea of a failure domain.
An enterprise is a set of modules joined by a core. Each module is designed on its own and can fail on its own.
Where this module sits in the exam
The ENCOR 350-401 Architecture domain opens with design. This module covers the design-level items; later modules go deep on the technologies they mention.
| Blueprint item | What you must be able to do | Chapters |
|---|---|---|
| 1.1 Design principles | Explain 2-tier, 3-tier, fabric and cloud designs; high availability with redundancy, FHRP and SSO | 2 to 7 |
| 1.2 WLAN deployment models | Compare centralised, distributed, controller-less, controller-based, cloud and remote-branch designs | 9 |
| 1.3 On-premises vs cloud | Choose where infrastructure should live and how it connects | 8 |
| 1.7 Hardware vs software switching | Explain process switching, CEF, RIB, FIB, adjacency table, CAM and TCAM | 10 |
SD-WAN and SD-Access, LISP and VXLAN, HSRP object tracking and deep wireless configuration each get their own modules later. Here you learn why they exist and where they fit.
The lab network you will use
Both labs use the same small collapsed-core block. Two distribution/core switches, DS1 and DS2, are joined by two links (Gi0/6 and Gi0/7). One access switch, AS1, has an uplink to each: Gi0/0 to DS1 and Gi0/1 to DS2. PC1 sits in VLAN 10 (10.1.10.0/24) and PC2 in VLAN 20 (10.1.20.0/24). DS1 owns .2 and DS2 owns .3 in each VLAN, and HSRP provides the virtual gateway .1. A WAN router R1 connects to DS1 over 10.0.1.0/30 and to DS2 over 10.0.2.0/30, and reaches the data-centre server SRV (172.16.0.10). OSPF area 0 runs between R1 and the distribution switches.
Worked example. PC1 (10.1.10.11) opens a file on SRV (172.16.0.10). The frame leaves AS1 on the uplink towards the HSRP active gateway, DS1 routes it onto 10.0.1.0/30, R1 routes it to the data-centre LAN. If DS1 dies, HSRP moves 10.1.10.1 to DS2, spanning tree unblocks the DS2 uplink if needed, and OSPF on R1 already has a second equal-cost path through DS2. Three independent mechanisms, each covering a different failure. That is design.
Common mistake. Treating design as drawing boxes. Every design choice has a protocol consequence. "Two distribution switches" immediately means you must decide the STP root, the HSRP active router, the EtherChannel mode between them and how routing sees both paths. Most outages in well-funded networks are caused by redundancy that was bought but never aligned.
Exam trap. ENCOR design questions rarely ask for commands. They describe a situation (many buildings, a small branch, heavy east-west traffic, a supervisor failure) and ask which design or feature fits. Learn the reason behind each option, not just its name.
The campus that grew one switch at a time
A college started with one core switch and added access switches whenever a lab opened, daisy-chaining some of them. After five years a single faulty NIC in one hostel caused a broadcast storm that took down every building, because all 40 switches shared one flat VLAN and one spanning tree. The redesign split the campus into building modules, each with a distribution pair, routed links to a core pair and VLANs that never leave the building.
Lesson: hierarchy and modularity are not paperwork. They are what keeps one bad cable from becoming a campus-wide outage.
"Walk me through how you would design a new enterprise campus."
Start with requirements: number of users and buildings, applications, growth, availability target. Then describe the hierarchy (access, distribution, core, or collapsed core if small), the Layer 2/3 boundary, redundancy at every layer, how STP and FHRP are aligned, how the campus connects to the data centre, WAN and cloud, and how wireless is deployed. Mentioning failure domains and oversubscription shows you think like a designer, not just a configurator.
Key takeaways
- Enterprise networks are built from modules joined by a core, like districts joined by a highway.
- Access connects users, distribution applies policy and is the L2/L3 boundary, core moves traffic fast.
- Redundancy only works when protocols such as STP, FHRP and routing are aligned with it.
- This module covers ENCOR 1.1, 1.2, 1.3 and 1.7 at a design level; later modules go deep.
- The labs use DS1, DS2, AS1, R1, SRV, PC1 and PC2 in a collapsed-core block.