Capstone: Designing Office Subnets

Congratulations on reaching the capstone lab of the Subnetting and Network Segmentation module! Up to this point, you have explored the mathematics of subnet masks, partitioned class C networks into halves, conserved WAN links with slash 30 blocks, and planned variable length subnetting schemes.

Now, you will put all these skills together in a complete enterprise scenario. You are hired as the network administrator for a regional engineering consultancy. The company has been assigned the parent network block 172.16.0.0/22 and requires a robust three-tier segmentation architecture: Operations Workstations, Corporate Management, and Central File Storage.

The Business Requirements and Architecture Plan

A senior IT director has outlined the following technical requirements for the new office facility:

1. Tier 1 - Operations Department: Needs capacity for up to 100 client workstations. We assign 172.16.1.0/25 (mask 255.255.255.128), providing 126 usable host addresses.
2. Tier 2 - Executive Management: Needs capacity for 25 secure office laptops. We assign 172.16.2.0/27 (mask 255.255.255.224), providing 30 usable host addresses.
3. Tier 3 - Server Infrastructure: Needs capacity for 10 high-availability storage servers. We assign 172.16.3.0/28 (mask 255.255.255.240), providing 14 usable host addresses.

Each tier has been carefully aligned to avoid any address collisions. Operations occupies the entire lower half of the 172.16.1 space. Management sits on a small 32-address block within 172.16.2. The server farm sits on a compact 16-address block in 172.16.3. This structure provides generous room for future expansion across each department.

Verification Methodology: From Edge to Core

When completing a multi-subnet deployment, follow a disciplined verification sequence:

Step 1: Local Loopback and Interface Health. Confirm that every workstation has correctly applied its IP address and subnet mask using ipconfig.

Step 2: Default Gateway Reachability. Ping the local gateway interface on the central router from each department. If a host cannot reach its immediate gateway, it can never reach other tiers.

Step 3: Inter-Subnet Cross-Routing. Ping across departmental boundaries—from Operations to Management, and from Management to the Central Storage Server. Confirm 0% packet loss and verify that TTL decrements by 1 hop.

Following this bottom-up troubleshooting methodology ensures that you detect wiring faults or address typos immediately, rather than spending hours trying to figure out why a remote server is unreachable when the local gateway was never configured.

Real-World Verification Commands for System Administrators

On enterprise routers, verification is not just about pinging. Experienced system administrators inspect routing tables with show ip route to verify that each subnet appears as a directly connected network with the expected mask length.

If a subnet is missing from the routing table, check the physical interface status with show ip interface brief. An interface that is administratively down or disconnected will prevent the router from advertising that subnet to other connected devices.

Field Best Practices for IP Documentation

In production enterprise environments, maintaining an accurate IP Address Management (IPAM) spreadsheet or database is mandatory. Whenever you deploy a new subnet, document the network ID, CIDR mask, gateway IP, DHCP scope range, and broadcast address.

Without up-to-date documentation, another engineer might accidentally assign the same subnet to a new floor six months later, causing severe IP conflicts and routing loops. Clear documentation turns complex subnet architectures into manageable, scalable assets for the entire team.

Final Wrap-Up and Next Steps

By completing this capstone lab, you have proven that you understand how IPv4 addressing, custom subnet masks, and default gateways work together to build scalable enterprise network topologies. In our next module, we will explore Static Routing and Internetwork Path Selection, taking your routing knowledge across multi-router wide area networks.

Celebrate your mastery of subnetting! What once seemed like intimidating binary math is now a natural tool in your engineering toolkit. You are now fully prepared to connect separate corporate networks across the wider world.