Allocate addressing before configuring devices
A VLSM plan gives each VLAN a deliberate subnet size and reduces overlapping networks or wasteful address allocation.
ENGINEERING PROJECT / 04
An enterprise network design exercise focused on segmented VLANs, structured IPv4 addressing, dynamic routing, gateway redundancy and controlled inter-network access.
01 / CONTEXT
THE WHYEnterprise networks need clear segmentation, predictable addressing and resilient connectivity. This project applies core networking concepts to a multi-subnet design while considering how traffic should move between network zones.
02 / SYSTEM DESIGN
THE STRUCTUREA high-level view of the documented workflow and component boundaries.
VLSM divides the IPv4 address space into appropriately sized subnets.
VLANs separate user, server and management traffic into logical segments.
OSPF exchanges routes between network segments.
Access control lists express which inter-network traffic is permitted.
HSRP, DHCP, DNS and NAT support gateway availability and essential network services.
03 / ENGINEERING LOG
THE BUILD SEQUENCEA transparent sequence of engineering milestones. Status labels describe documented work—not a live completion percentage.
Use VLSM to divide the address range into appropriately sized subnets for the network segments.
Organize user, server and management networks into VLANs to establish logical boundaries.
Use OSPF as the planned dynamic routing protocol between the network segments.
Apply ACLs to express which inter-network traffic is permitted, then consider gateway redundancy with HSRP.
Add topology captures and relevant device configurations before presenting this academic design as a verified implementation.
04 / DESIGN JUDGMENT
TRADE-OFFS & REASONSThe engineering choices that shape the system—and the reason each boundary exists.
A VLSM plan gives each VLAN a deliberate subnet size and reduces overlapping networks or wasteful address allocation.
VLAN boundaries make the intended trust zones explicit; inter-VLAN communication should then pass through documented policy controls.
OSPF defines path exchange between routed segments, while HSRP addresses default-gateway availability. Each needs its own validation.
The available material describes an academic design, so the next step is topology and configuration evidence—not presenting the design as a verified deployment.
06 / IMPLEMENTATION
THE HOWThe work is broken into practical building blocks, from initial design through to validation.
Planned IPv4 subnets using VLSM to use address space efficiently.
Separated network functions with VLAN-based segmentation.
Configured OSPF for dynamic routing between network segments.
Applied access control lists to define permitted traffic flows.
Used HSRP to explore default-gateway redundancy.
Configured DHCP, DNS and NAT as supporting network services.
08 / RESULTS
THE VALUEA structured enterprise network design that combines addressing, segmentation and routing.
Hands-on practice with redundancy and access-control concepts.
A practical foundation for troubleshooting multi-subnet environments.
10 / ENGINEERING NOTES
TRANSPARENCYClear boundaries matter. These notes describe what the current project does—and what it does not claim to do.