Back to portfolioPROJECT CASE STUDY / 04
ENTERPRISE NETWORK DESIGN

ENGINEERING PROJECT / 04

Secure Enterprise Network.

CASE STUDY
2026

An enterprise network design exercise focused on segmented VLANs, structured IPv4 addressing, dynamic routing, gateway redundancy and controlled inter-network access.

PROJECTSecure Enterprise Network
TYPEENTERPRISE NETWORK DESIGN
TECHNOLOGIES8 core tools
VLANsVLSMOSPFACLsHSRPDHCPDNSNAT

01 / CONTEXT

THE WHY

The challenge

Enterprise 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 STRUCTURE

How the pieces fit together

A high-level view of the documented workflow and component boundaries.

01

Addressing plan

VLSM divides the IPv4 address space into appropriately sized subnets.

02

Access layer

VLANs separate user, server and management traffic into logical segments.

03

Routing layer

OSPF exchanges routes between network segments.

04

Policy boundary

Access control lists express which inter-network traffic is permitted.

05

Resilient services

HSRP, DHCP, DNS and NAT support gateway availability and essential network services.

03 / ENGINEERING LOG

THE BUILD SEQUENCE

How the work took shape

A transparent sequence of engineering milestones. Status labels describe documented work—not a live completion percentage.

  1. 01
    01 · ADDRESSINGDesign

    Plan the IPv4 space

    Use VLSM to divide the address range into appropriately sized subnets for the network segments.

  2. 02
    02 · SEGMENTATIONDesign

    Separate traffic by function

    Organize user, server and management networks into VLANs to establish logical boundaries.

  3. 03
    03 · ROUTINGDesign

    Define inter-network paths

    Use OSPF as the planned dynamic routing protocol between the network segments.

  4. 04
    04 · POLICYDesign

    Specify traffic controls

    Apply ACLs to express which inter-network traffic is permitted, then consider gateway redundancy with HSRP.

  5. 05
    05 · EVIDENCENext

    Publish reproducible lab proof

    Add topology captures and relevant device configurations before presenting this academic design as a verified implementation.

04 / DESIGN JUDGMENT

TRADE-OFFS & REASONS

Decisions behind the design

The engineering choices that shape the system—and the reason each boundary exists.

01

Allocate addressing before configuring devices

A VLSM plan gives each VLAN a deliberate subnet size and reduces overlapping networks or wasteful address allocation.

02

Separate user, server and management traffic

VLAN boundaries make the intended trust zones explicit; inter-VLAN communication should then pass through documented policy controls.

03

Treat routing and gateway redundancy as separate concerns

OSPF defines path exchange between routed segments, while HSRP addresses default-gateway availability. Each needs its own validation.

04

Keep the current page honest about implementation

The available material describes an academic design, so the next step is topology and configuration evidence—not presenting the design as a verified deployment.

05 / NEXT INVESTIGATION

THE NEXT USEFUL TEST

What I would test next

Turn the design into a reproducible GNS3 lab: publish the topology, addressing table, device configurations and a small validation matrix covering VLAN isolation, OSPF adjacency, ACL allow/deny cases, HSRP failover, DHCP leases and NAT translation.

06 / IMPLEMENTATION

THE HOW

Engineering approach

The work is broken into practical building blocks, from initial design through to validation.

  1. 01

    Planned IPv4 subnets using VLSM to use address space efficiently.

  2. 02

    Separated network functions with VLAN-based segmentation.

  3. 03

    Configured OSPF for dynamic routing between network segments.

  4. 04

    Applied access control lists to define permitted traffic flows.

  5. 05

    Used HSRP to explore default-gateway redundancy.

  6. 06

    Configured DHCP, DNS and NAT as supporting network services.

08 / RESULTS

THE VALUE

What this project demonstrates

01

A structured enterprise network design that combines addressing, segmentation and routing.

02

Hands-on practice with redundancy and access-control concepts.

03

A practical foundation for troubleshooting multi-subnet environments.

10 / ENGINEERING NOTES

TRANSPARENCY

Scope, assumptions & limitations

Clear boundaries matter. These notes describe what the current project does—and what it does not claim to do.

  • This is an academic and lab-based design exercise, not a claim of a production enterprise deployment.
  • The architecture diagram on this page is a conceptual summary of the documented design elements, not a packet-level topology capture.
  • The security of a real deployment depends on validated configurations, device hardening, monitoring and ongoing operational controls.