Subnetting for Real-World Network Designs

There's a difference between subnetting an exam question and designing an addressing scheme for a real network. The exam gives you exact host counts. Real life gives you vague estimates, growth projections, and someone in finance asking why the network costs so much.

#The Principles of Realistic Address Planning#link

• ▪Reserve from the top down — assign each site a large block, then subdivide inside it
• ▪Leave room to grow — a site using 200 hosts today may need 400 in three years
• ▪Summarize hierarchically — /16 for a region, /20 for a site, /24 for a VLAN
• ▪Keep functional roles on their own blocks — user VLANs separate from servers, separate from management
• ▪Document everything — the network engineer who inherits your scheme should not have to reverse-engineer it

Real address plans live in spreadsheets and IPAM tools. The exam will hand you a paragraph and expect a plan. The thinking is the same — allocate big blocks per site, subdivide within, and always leave the last block or two reserved.

#Worked Design: Three-Site Enterprise#link

Company has a HQ and two branches. Planning to grow for five years. Allocated block: `10.0.0.0/8` (large, plenty of room).

Notice the structure. Each site gets a clean /16 that summarizes to a single route. WAN links are grouped together for easy ACL management. Future regions are reserved as a block, not scattered — so when expansion comes, it's a clean allocation, not a scavenged set of leftover fragments.

Inside HQ — 10.1.0.0/16

#Summarization — the Payoff of Good Planning#link

Because HQ is one /16, the WAN edge router advertises one route to reach every HQ subnet: `10.1.0.0/16`. That's one line in every routing table across the network, not dozens. When you add a VLAN inside HQ, no other router needs to know — the summary route already covers it.

This is why hierarchical addressing matters. Random allocation forces you to advertise dozens of routes and clutter every routing table. Structured allocation collapses them into a handful of summaries.

#Scenario: Address Plan for a New Acquisition#link

#Quick Check#link