IP VPN

Connect sites with private routes and shared traffic priorities.

An IP Virtual Private Network (IP VPN) links sites and data centres. It suits multisite networks; separate internal traffic from Internet breakout before choosing the design.

It is less agile than an Internet-first model for some SaaS applications and does not remove the need for diverse access.

Let’s talk
Business sites connected by a fibre network.

How it works

Unite sites through a routed private network with shared policies.

Site · local routes
Private Layer 3 WAN
Routes and service classes
Sites / cloud

A WAN that knows the destinations

Sites exchange routes with the managed network at the agreed demarcation. The routed WAN connects subnets without requiring a single LAN stretched across offices.

Define which networks can communicate, which reach cloud and where Internet traffic exits. Network isolation and firewall controls are separate decisions.

Site · local routes
Private Layer 3 WAN
Prioritise critical traffic
Sites / cloud

Priority when applications compete

Classification and service classes allow different traffic to receive agreed priorities. Marking and access capacity must match the actual traffic profile.

Broken voice requires checking loss, delay, queues and the LAN. Priority protects a class under contention; it does not create bandwidth.

Site · local routes
Private Layer 3 WAN
Recovery routes
Sites / cloud

Recovering access and routes

A redundant path needs routing that detects failure and a working second access. Convergence and return routes determine what remains reachable.

Test loss and restoration of a site, device or access. WAN availability does not replace server high availability.

Illustrative case: from situation to decision

Situation
Offices use a central application alongside public cloud tools.
Option
Define which flows use the private network and where each reaches the Internet.
Check
Check return routes, isolation and priorities when voice and data compete.

Private does not inherently mean encrypted: confirm encryption, segmentation and Internet breakout in the design.

Decisions for your project

Routes and segmentation
Prefixes, possible overlaps and permissions between segments.
Quality and breakout
Classes, marking, cloud and central or distributed Internet breakout.
Operations and failures
CPE, routing, monitoring, diverse paths and restoration tests.

From design to operation

Define the route map; pilot reachability and quality before adding sites in phases.

Complements, alternatives and variants

Product sources

Back to top