---
# source: src/content/services/en/network.md
# route:  /en/services/network/
title: Network
group: infrastructure
audience: [enterprise, provider]
order: 11
tags: [network, security]
vendors: [vmware]
summary: From the classic campus network to network virtualization. We work with our partners' products and with yours.
photo: rack-fibre-fanout
photoNeed: "Cabling being done properly: a patch panel mid-work, labelled, with the person doing it"
stub: false
draft: false
---

## What we cover

Network infrastructure in the datacentre and on campus, segmentation, and the move to
network virtualization with NSX. Along with connecting branch sites and access from
outside.

Then there are the areas that tend to get lost in a data centre discussion: **edge
networking** for branch sites, and **wireless**, where the constraints are rarely
technical and almost always structural.

For branch sites there is SD-WAN with WAN optimisation, and for access there is network
access control: who connects with what is decided by role and location, not by the port.

## What we work with

Our partners' networking products, and equally with other vendors' kit on projects. A
network is rarely built on a green field, and a partner who only touches their own products
is not much use in an estate that grew.

## Where the work actually is

In segmentation, and there it is not technical. A distributed firewall is switched on in an
afternoon. Writing a rule set someone can still justify in three years takes months,
because first you have to answer which systems talk to each other today.

That is why we start in monitor mode and only enforce once the flows are documented.