Overview
Over the course of my career, I've been involved in deploying, configuring, and maintaining network infrastructure across 69+ office sites. Each deployment presented unique challenges — from differing building layouts to varying bandwidth needs — but patterns emerged that shaped a reliable, repeatable process.
This article shares the key lessons and best practices I've learned through hands-on experience in real-world enterprise environments.
What You'll Learn
- How to plan network infrastructure for multi-site deployments
- Standard equipment and configurations that work at scale
- Common pitfalls and how to avoid them
- Best practices for documentation and handover
Step 1: Site Survey & Requirements Gathering
Before any equipment arrives, a thorough site survey is essential. This includes:
- Physical layout assessment — Floor plans, cable run distances, environmental conditions
- User count & device inventory — Number of workstations, printers, IP phones, CCTV cameras
- Bandwidth requirements — Internet speed, internal traffic patterns, VoIP needs
- Existing infrastructure — What can be reused vs. what needs replacing
Step 2: Standard Equipment Stack
Consistency across sites reduces troubleshooting time and simplifies spare parts management. Here's the standard stack I use:
| Component | Purpose | Notes |
|---|---|---|
| MikroTik Router | Core routing, firewall, VPN | RouterOS provides granular control |
| Managed L2+ Switch | VLAN, QoS, port security | 24/48 port PoE for cameras & APs |
| Wireless AP | Wi-Fi coverage | Ceiling-mount, PoE powered |
| UPS | Power protection | Minimum 30-minute runtime |
| Patch Panel | Cable management | Cat6 for all new runs |
Step 3: Network Design & VLAN Segmentation
Every site follows a standard VLAN scheme to keep traffic isolated and manageable:
- VLAN 10 — Management (switches, routers, APs)
- VLAN 20 — Staff devices (workstations, laptops)
- VLAN 30 — CCTV & security devices
- VLAN 40 — Guest Wi-Fi (isolated, rate-limited)
- VLAN 50 — VoIP phones (QoS priority)
Common Pitfall
Never put CCTV cameras on the same VLAN as user devices. Camera traffic (especially during motion events) can saturate the network and cause slowdowns for staff. VLAN 30 isolation is mandatory.
Step 4: Configuration & Testing
Before deploying to site, I pre-configure all equipment in the office. This saves hours of on-site work:
- Flash router firmware to latest stable version
- Apply standard configuration template (DHCP, DNS, firewall rules, VPN)
- Configure switch VLANs and port assignments
- Set up Wi-Fi SSIDs with WPA3 authentication
- Test inter-VLAN routing and internet connectivity
- Label all cables and ports before packing
Step 5: On-Site Deployment
With pre-configured equipment, on-site work focuses on physical installation:
- Mount rack, patch panel, and equipment
- Terminate and test all cable runs
- Connect ISP uplink and verify WAN connectivity
- Verify each VLAN has proper connectivity and isolation
- Speed test from multiple points in the office
- Walk through the setup with the site contact
Step 6: Documentation & Handover
Every site gets a standardized documentation package:
- Network diagram (physical and logical)
- IP address allocation table
- VLAN assignments and port mapping
- Wi-Fi credentials and guest network info
- Emergency escalation contacts
Key Takeaways
Best Practices Summary
- Standardize everything — Same equipment, same VLANs, same procedures
- Pre-configure before deployment — Reduces on-site time by 60%+
- Always segment traffic — VLANs are non-negotiable
- Document religiously — Future-you will thank present-you
- Test before leaving — Verify from the user's perspective, not just the switch