Access
Edge switches, PoE for access points and handsets, documented ports. When it is done, you know which cable leaves which wall socket and lands on which port.
A written addressing plan, VLANs that mean something, Wi-Fi measured before it is bought. The rest is hardware, and hardware has never once rescued a poor design.
The scope
The three layers, and what sits around them.
Distribution and core
Aggregation, link redundancy, inter-VLAN routing. The point where a single failure must not stop the building — that is where availability is decided.
Wi-Fi
A coverage survey before the purchase, not after. Access points placed according to the real walls, racking and machinery, not an architect's drawing.
Firewalls and segmentation
Keeping guests, office work, production, voice and management apart. Every firewall rule carries a comment saying why it exists.
Remote access
Site-to-site VPN, home working, two-factor. The same level of access as at the office, without opening more than is needed.
Monitoring
Metrics, thresholds, alerts, logs. Being warned by the probe at six in the morning rather than by the user at nine.
The sequence
How a network project runs.
Five steps. The first two cost the least and settle everything that follows.
The audit
What exists, surveyed on site: racks, cabling, switches, firmware, carrier contracts. Photographs, a diagram, and the list of what the manufacturer no longer supports.
The plan
Addressing plan, VLAN table, segmentation rules, proposed hardware with the reasons behind each choice. You read it and approve it before a single cable moves.
The roll-out
In batches, each with a way back. Cut-overs that interrupt anything happen outside production hours, on a date you set.
The acceptance
We show you: every VLAN, every rule, every access point, the failover of a redundant link, the VPN from outside. What has not been tested has not been delivered.
The monitoring
Probes in place, thresholds set, alert recipients agreed. Then the documentation comes to you: addressing plan, VLAN table, current diagram.
The vocabulary
This vocabulary is not here to impress anyone. It is here because a network has to be documented, and documentation is read in the words of the trade.
At the end of a project you are handed three documents: the addressing plan, the VLAN table and the current diagram. They are yours and they follow you — including on the day you might change provider. A network nobody can take over without us is not a good network, it is a dependency.
Do you already have a network, built by someone else, and nobody left who knows how it is put together? That is the most common situation of all. The audit exists precisely for it, and it commits you to no project at all.
What we work with.
VLAN 802.1Q802.1XRADIUS/24 · /26PoE+ 802.3atWi-Fi 6 · 6 GHzIPsecWireGuardOSPFBGPLACPRSTPSNMPNetFlowDHCP · DNSCat 6aOM4 fibreSD-WAN
The Wi-Fi drops, the VPN crawls, nobody knows why.
Three symptoms, almost always the same cause: a network that grew without a plan. That can be measured, and then corrected.