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
How it works
Unite sites through a routed private network with shared policies.
Site · local routes
Private Layer 3 WAN
Sites / cloudA 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
Sites / cloudPriority 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
Sites / cloudRecovering 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
What challenge would you like to solve?
Tell us what is happening and what needs to change. You do not need to know the catalogue.
What happens next?
- Understand the context
What’s changing, where your teams work and what cannot fail. Still defining the brief? We can help structure it.
- Design the options
Bring needs, Colt capabilities and technical criteria together. Compare alternatives and explain dependencies and limits.
- Validate before committing
Coverage, feasibility, responsibilities and terms. A commercial proposal is developed with the relevant specialists.
ColtPlatinum guides the project and coordinates commercial discussions and follow-up. Colt validates feasibility, enters into the service contract, and provisions, installs and delivers the services.
Availability, coverage, capabilities, SLAs and timelines are subject to technical validation and contract. No diagram is a service guarantee.