Ten-Site Network Rebuild for a Public School District

The district's HP networking environment had reached end of life. It still worked, in the sense that packets moved — but it couldn't deliver the performance, reliability, or management visibility that a modern school district needs, and the demands on it were growing every year.

School networks have changed shape. A district that once needed wired connectivity in computer labs now supports one-to-one devices in every classroom, security cameras at every entrance, VoIP handsets in every office, and guest access in public areas. Each of those is a different traffic pattern with a different security posture, and the old flat network treated them all the same.

The scope

Ten sites: five primary campuses and five remote branch locations. The network had to be rebuilt across all of them while classes continued, administration ran, and technology services stayed available.

The objectives:

• Replace end-of-life HP equipment with modern enterprise infrastructure
• Improve wired and wireless performance
• Establish consistent architecture across every location instead of ten variations
• Segment the network properly
• Add redundant connectivity so a single circuit failure isn't a district-wide outage
• Give the district's team centralized visibility instead of per-site guesswork
• Absorb the growing load from wireless devices, cameras, and classroom technology

What we built

A Cisco and Cisco Meraki architecture, deployed in phases and coordinated with the district's ISP:

• Approximately 100 Cisco enterprise switches installed and configured
• Approximately 250 Cisco Meraki wireless access points
• Approximately 250 Cisco Meraki security cameras
• Layer 3 networking at each primary campus, so inter-VLAN routing happens locally rather than hauling traffic back to headquarters
• Centralized core infrastructure at district headquarters
• Dual 10 Gbps internet connections with vPC-based failover
• Layer 2 deployments at remote branches, coordinated with the ISP on circuit delivery
• Migration off the legacy HP estate

Segmentation

This is the part that matters most for a school district, and it's where the old flat network was riskiest. We built dedicated segments for:

• Staff devices
• Student devices
• Voice and VoIP
• Security cameras
• Guest and BYOD access in public areas

Each segment carries its own access controls and isolation. A compromised student laptop can't reach the camera network. A guest on the public Wi-Fi can't see administrative systems. Cameras — which are notoriously weak endpoints — sit where they can't be used as a foothold.

For a district holding student records, that separation isn't just good practice; it's the structure an auditor expects to see, and the thing that makes an incident containable instead of district-wide.

The outcome

• 10 locations modernized, supporting roughly 350 staff and 1,500 students
• Approximately 100 switches, 250 access points, and 250 cameras deployed
• Redundant 10 Gbps internet connectivity with automatic failover
• Layer 3 routing at every primary campus
• Segmentation across staff, students, voice, cameras, and guest
• Centralized visibility through the Meraki dashboard, replacing per-site troubleshooting
• Approximately 4 months from equipment delivery to production-ready

Technologies

Cisco Catalyst switching · Cisco Meraki wireless · Cisco Meraki smart cameras · Cisco Meraki dashboard · Cisco Layer 3 routing · Virtual Port Channel (vPC) failover · Dual 10 Gbps WAN · VLAN design and segmentation · Enterprise campus architecture · ISP circuit coordination

Why it worked

Ten sites, three equipment categories, an ISP dependency, and a building full of people who need the network to work during the school day. Projects like this fail on sequencing rather than on technology.

Phasing it site by site, coordinating circuit delivery with the ISP rather than hoping it aligned, and keeping consistent architecture across all ten locations meant each site was a repeat of a proven pattern instead of a fresh problem. The district ended up with a network its own team can actually operate — which, four months after handover, is the outcome that matters.