Service
Network
Cisco, Aruba, Ruckus, Extreme, Alcatel-Lucent, MikroTik.
Scope of work
- 01Site survey and enterprise network architecture design
- 02VLAN and IP addressing plan by role and function
- 03Core / Distribution / Access switch deployment
- 04STP/RSTP, LACP, inter-VLAN routing and link redundancy configuration
- 05Enterprise Wi-Fi deployment, coverage optimisation and roaming
- 06QoS and IGMP snooping configuration for AV/Dante systems
- 07Management VLAN and remote access setup
- 08Documentation: network diagrams, VLAN table, IP table, configuration backups
A small-office Wi-Fi router is enough for ten people browsing the web. But when a building has hundreds of devices, including IP cameras, AV controllers, Dante equipment, IP telephony, BMS, user computers and phones, all on one infrastructure, the problem is entirely different. I tend to see two kinds of failure: a network that works but is unstable for no obvious reason, or a network that works fine until the day a new system is added and it collapses. Both have the same root cause: the network was never designed as a platform.
What is enterprise network infrastructure — and why does it decide how every other system performs?
The network is the foundation layer every modern system depends on. Cameras need stable bandwidth, Dante audio needs very low latency, IP telephony needs voice packet priority, user computers need secure access. When the network is designed correctly, these systems share one infrastructure without affecting each other. When it is designed incorrectly, no end device is good enough to compensate.
VLANs — segmentation for control and security
A VLAN (Virtual LAN) divides one physical network into multiple independent logical networks. It is the most fundamental tool for managing complex infrastructure. An integrated building typically needs separate VLANs for: internal users, infrastructure management, AV and Dante, IP cameras, IP telephony, IoT and guests.
Correct segmentation means cameras cannot "see" staff computers, Dante audio gets bandwidth priority, and an infected device cannot spread across the system. Alongside it comes a systematic IP addressing plan: from the address alone, an engineer knows which zone a device belongs to, which makes operations and troubleshooting much faster.
Switching — the backbone
Switching infrastructure is usually organised in three tiers. The Access tier connects end devices directly and supplies PoE to cameras, IP phones and access points. The Distribution tier aggregates Access switches and applies policy. The Core tier is the high-speed backbone, built for stability. In small and medium projects, Core and Distribution may be collapsed into one.
Configuration covers VLAN trunking, STP/RSTP to prevent loops (a network loop can bring down an entire system within seconds), LACP link aggregation for both bandwidth and redundancy, and inter-VLAN routing so zones communicate under control. Cisco Catalyst, Aruba CX, Ruckus ICX and Extreme are stable platforms for continuous-operation environments.
Network configuration for AV and Dante systems
Professional audio over the network is more demanding than office data. Switches need QoS so Dante packets are prioritised, IGMP snooping so multicast does not flood the whole network, and stable clock synchronisation. A standard office switch left at defaults can cause crackling or dropped audio packets. This is the area I check most carefully when AV and network share one project.
Enterprise Wi-Fi — more than broadcasting a signal
Home Wi-Fi and enterprise Wi-Fi are different things. An enterprise system is designed for hundreds of simultaneous devices, seamless roaming between access points, SSID separation by role (staff, guests, devices) and centralised management. The most important step is the coverage survey and AP placement, because wrong AP density causes co-channel interference that makes Wi-Fi slower even with more access points installed.
Aruba, Ruckus and Cisco Meraki support both on-site controller and cloud-managed models, with the choice depending on project scale and operating model. In hotels and multi-storey buildings, seamless roaming is mandatory: calls and meetings must not drop when users change floors.
Management network and documentation
A good network has a dedicated management entry point (management VLAN), separate from user traffic, so engineers can reach switches and APs even when the user network has a problem. At project end I hand over complete network diagrams, VLAN tables, IP tables and configuration backups. A system without documentation depends on one person's memory.
When does network infrastructure need to be redesigned?
When the network is frequently slow or unstable for unclear reasons, when cameras, AV, telephony or new systems are about to be added, when the building expands to new floors or branches, or when the network has grown organically over years and nobody holds the full picture any more.