Private Network Overview

Private Network Overview

Private Network is a Layer 2 connectivity service that offers data center-wide (metro) connectivity between Leaseweb services.

Key Features:

  • Automatic VLAN ID: Each customer who adds Private Network to their Leaseweb services automatically receives a single VLAN ID.
  • Private IP Space Assignment: We offer automated Private IP space assignment via DHCP to simplify usage and prevent IP overlapping. DHCP can be enabled or disabled from the Customer Portal.

Connectivity: Private Network connects Leaseweb services and products within a single data center or across multiple data centers within a metro area. For example, a Leaseweb service in AMS-02 can connect with a service in AMS-01 using the same transport VLAN ID, remaining within the same Layer 2 domain.

Cost Efficiency: Traffic generated between Leaseweb services using Private Network is not measured and is free of charge within each metro area.

Private Network Availability and supported products Matrix

Private Network enabled productsAvailability
Dedicated Server 100Mbps/1Gbps/10GbpsYes
Dedicated Server 25GbpsYes, available in AMS-01, FRA-01, WDC-02, LON-01
Dedicated rackspaceYes
Colocation rackYes
Shared colocation
Public CloudYes
Elastic ComputeYes
VPS
VMware Single Tenant (vSphere/HCI)Yes
VMware vCloudYes
Dedicated Storage
Object Storage
Cloud Storage (SAN/NAS Storage)Yes

Multiple VLANs

QinQ Support in Private Network

Private Network supports QinQ (IEEE 802.1ad), an Ethernet networking standard that allows private network traffic to be segmented into an additional 4000 sub-VLANs within the single Private Network VLAN provided by Leaseweb.

Key Features:

  • Default Enablement: QinQ is enabled by default for all existing and new customers, free of charge.
  • Customer Control: Customers have full control over the sub-VLANs and IP subnet assignment.

Important Note: QinQ VLAN traffic within the private network is segmented, not isolated.

Supported Products:

ProductQinQ SupportNote
Dedicated ServersYesServers located in Shared racks
Dedicated RacksYesDedicated Servers located in Dedicated racks
Colocation RacksYes
Cloud ComputeNoPublic Cloud, Elastic Compute and vCloud (Multi-Tenant)
VPSNo 
Cloud ConnectNo 
VMware vSphere & HCINoVMware Single Tenant products

Please follow this article How to configure multiple vlans qinq in Private Network for more information how to activate this feature by configuring your operating system.

Dedicated Servers (Shared racks)

Private Network connects two or more servers and/or other Leaseweb services (See Product availability).

Private Network is available for dedicated servers in shared racks in all data centers.

It is offered in below port speeds and connects each server with a single link to Private Network:

  • 100 Mbps
  • 1 Gbps
  • 10 Gbps
  • 25 Gbps (available in AMS-01, FRA-01, LON-01 and WDC-02 Data Centers)

Redundancy options

For customers requiring more resiliency in their environment, Leaseweb offers redundant Private Network for the following port speeds:

  • 10 Gbps (2x 10Gbps in LACP, 802.3ad mode4)
    • This option provides 10 Gbps bandwidth with redundancy, using link aggregation and the LACP protocol for failover.
  • 25 Gbps (2x 25Gps in LACP, 802.3ad mode4)
    • This option offers 25 Gbps bandwidth with redundancy, also using link aggregation and LACP.

Servers are connected with 2 (bonded) links to a redundant set of Private Network switches.
This setup ensures high availability by eliminating single points of failure in the Private Network.

Configuring Server-Side Bonding for Redundant Private Network

To make use of the redundant Private Network setup, you need to configure bonding on your server. Bonding, also known as link aggregation, combines multiple network interfaces into a single logical interface, called a bond.

Think of it as teaming up two network cables for your server. Even though your server has two physical connections, without bonding, it would only use one at a time.

Why is Bonding Necessary for Redundant Private Network?

  • High availability: If one link or switch fails, the bond automatically switches to the other active link ensuring uninterrupted network connectivity. This is crucial for mission-critical applications and services that need to remain online.
  • Load balancing: Some bonding modes distribute traffic across both links, which can improve network performance.

Without bonding, having two network interfaces connected to redundant switches wouldn’t provide true redundancy. Your server would only use one link, and if that link or switch failed, your server would lose connectivity.

Bonding Configuration:

Different bonding modes are available, each with pros and cons. Leaseweb uses LACP (802.3ad) for redundant Private Network. LACP is a dynamic link aggregation protocol that actively manages the bond, negotiates with the switches, and provides failover and load balancing capabilities.

Configuring bonding involves setting up the bond on your server’s operating system. Specific steps vary depending on the OS:

  1. Create a bond interface.
  2. Assign the physical network interfaces to the bond.
  3. Select the bonding mode (LACP).
  4. Configure the IP address and other network settings for the bond.

Resources on configuring server-side bonding for various operating systems:

  1. Ubuntu
  2. Rocky Linux
  3. AlmaLinux
  4. FreeBSD
  5. Windows

Traffic generated between Dedicated Servers and/or other Leaseweb services using Private Network is not measured and is free of charge.

Ordering information

You can order Private Network for Dedicated Servers via the website (while ordering new servers), our Sales department, and from the Leaseweb Customer Portal (for existing servers).

In this article, there are instructions how to order Private Network for your Dedicated Servers and how to manage Private Network in the Customer Portal.

While ordering from the website, under the tab Network >Private Network, select Private Network port speed.

For Redundant Private Network per server, please contact our Sales department.

Tech specs Dedicated Servers (Shared racks):

  • Full layer-2 network connection (QinQ is supported)
  • 9k MTU, overlay tunnels support. See also Using Jumbo frames with Private Networking
  • Added DHCP services, offering a default /27 IP space. Can optionally be disabled.
  • Larger private subnets are available upon request.
  • Available in all data centers where shared rack Dedicated servers are offered.
    • 10 Gbps with redundancy option (available in AMS-01, FRA-01, LON-01, and WDC-02 Data Centers)
    • 25 Gbps with redundancy option (available in AMS-01, FRA-01, LON-01, and WDC-02 Data Centers)

Dedicated Racks (for dedicated servers)

Private Network connects Dedicated Servers in Dedicated Racks to other Leaseweb services (see Product availability).

Private Network is available for Dedicated Racks in all data centers. The service consists of a switch, 2 ports on Private Network routers (CIs), cabling, and 1/10/25 Gbps Private Network for all servers in the Dedicated Rack.

It is offered in the below router port speeds:

  • Entry level: 2x 10Gbps, providing 1Gbps per connected server.
  • Medium: 2x 40Gbps, providing 10Gbps per connected server (available in selected data centers, see in the data center list below).
  • Large: 2x 100Gbps, providing 10/25Gbps per connected server (available in selected data centers, see in the data center list below).

Redundancy options

For customers requiring more resiliency in their environment, Leaseweb offers redundant Private Network switches with the following port speeds per server:

  • 10 Gbps (2x 10Gbps in LACP, 802.3ad mode4), using 2x 100Gbps uplinks.
  • 25 Gbps (2x 25Gps in LACP, 802.3ad mode4), using 4x 100Gbps uplinks.

Servers are connected with 2 (bonded) links to a redundant set of Private Network switches.

Traffic generated between servers in Dedicated racks and other Leaseweb services using Private Network is not measured and is free of charge.

Traffic generated between Dedicated Servers and/or other Leaseweb services using Private Network is not measured and is free of charge.

Ordering information

You can order Private Network for Dedicated racks via our Sales department.

Private Network for Dedicated servers in Dedicated racks can be easily managed through our Customer Portal.

Tech specs Dedicated Servers (Dedicated racks):

  • Full layer-2 network connection (QinQ supported)
  • 9k MTU, overlay tunnels support. See also Using Jumbo frames with Private Networking
  • Added DHCP services, offering a default /27 IP space. Can optionally be disabled.
  • Larger private subnets are available upon request.
  • All data centers where Dedicated Racks are offered support 10Gbps.
  • The following data centers support 40Gbps and 100Gbps uplinks:
    • Amsterdam (AMS-01 and AMS-02)
    • London (LON-01)
    • Washington DC (WDC-02)
    • Singapore (SIN-01)

Cloud Compute (Public Cloud, Elastic Compute and VMware vCloud)

Private Network connects Public Cloud Instances, Elastic Compute and/or VMware vCloud Resource Pools to other Leaseweb services (see Product availability).

It is offered in the below virtual port speeds:

  • 100 Mbps and 1 Gbps for each Instance/VM, depending on location and vintage.

Traffic generated between Instances, VMs in a Resource pool and other Leaseweb services using Private Network is not measured and it is free of charge.
VM’s in a Resource Pool can connect to each other per default, therefore Private Network is not needed.

Ordering information

You can order Private Network for Public Cloud, Elastic Compute and/or vCloud VMware through our Sales department, and from the Leaseweb Customer Portal.

In this article, you can find instructions on how to set up Private Network in VMs in Elastic Compute.

Tech specs Cloud Compute

  • 100 Mbps / 1 Gbps per Private Cloud Virtual Server, for a full overview of Public Cloud instances and Private Network bandwidth, see here
  • Full layer-2 network connection (Untagged only, tagged / Dot1q not supported)
  • 9k MTU, overlay tunnels support.
  • Added DHCP services, offering a default /27 IP space.
  • Larger subnets are available upon request, at no additional cost.

Colocation

Private Network enables a customer with Colocation services to connect to other Leaseweb services. (see Product availability).

Private Network is available for Colocation racks (full and/or half) in all locations. The service consists of two ports on the Leaseweb Private Network routers and two fibre cables towards our redundant internal routers.

Colocation racks (half/full)
Network switches for Colocation racks are not bundled in the service. Customers can connect to Private Network with their own network switch(es) or lease a network switch from Leaseweb.

Colocation units
Private Network for Colocation Rack units is not available.

Customer’s own network switch:

  • Leaseweb provides instructions on how to configure the switch here.
  • A (separate) dedicated switch must be used for this connection. Using the same device for Public Connectivity via Leaseweb Network will cause issues and is not allowed.
    No interconnection between the Private switch and the Public switch in the rack is allowed.

Leaseweb provided network switch:

  • Leaseweb does the initial configuration and mounts the switch in the Colocation rack.
  • Leaseweb connects fibre cabling to switch
  • Leaseweb provides switch access to the customer
  • Customer manages the switch

It is offered in the below router port speeds:

  • Entry-level: 2x 10Gbps uplinks
  • Medium: 2x 40Gbps uplinks (available in selected data centers, see data center list below)
  • Large: 2x 100Gbps uplinks (available in selected data centers, see data center list below)

Traffic generated between Colocation and other Leaseweb services using Private Network is not measured and is free of charge.

Ordering information

You can order Private Network for your Colocation rack via our Sales department or the Customer portal.

In this article, you can find more information on how to order and manage Private Network for Colocation

Tech specs Colocation

  • Full layer-2 network connection (QinQ supported)
  • 9k MTU, overlay tunnels support. See also Using Jumbo frames with Private Networking
  • Added DHCP services, offering /27 IP space. Can optionally be disabled.
  • Larger private subnets are available upon request.
  • All data centers where Colocation racks are offered support 10Gbps.
  • The following data centers support 40Gbps and 100Gbps uplinks:
    • Amsterdam (AMS-01 and AMS-02)
    • London (LON-01)
    • Washington DC (WDC-02)
    • Singapore (SIN-01)

VMware Single Tenant vSphere and HCI

Private Network connects VMware vSphere and HCI platforms to other Leaseweb services (see Product availability). The service consists of a switch, two ports on the Leaseweb Private Network routers, two fibre cables towards our redundant internal routers and 1Gbps / 10 Gbps Private Network for all hypervisors in the VMware Single Tenant rack.

Tech specs VMware Single Tenant Private Networking

  • Full layer-2 network connection (QinQ is NOT supported)
  • 9k MTU, overlay tunnels support. See also Using Jumbo frames with Private Networking
  • Added DHCP services, offering /27 IP space. Can optionally be disabled.
  • Larger private subnets are available upon request.
  • All data centers where VMware Single Tenant products are offered support 10Gbps.
  • The following data centers support 40Gbps and 100Gbps:
    • Amsterdam (AMS-01 and AMS-02)
    • London (LON-01)
    • Washington DC (WDC-02)
    • Singapore (SIN-01)

It is offered in the below options:

  • Entry-level: 2x 10Gbps uplinks (providing up to 1Gbps per VM)
  • Medium: 2x 40Gbps uplinks (providing up to 10Gbps per VM, for up to 8 hypervisors)
  • Large: 2x 100Gbps providing (up to 25Gbps per VM, for large environments)

Traffic generated between VMware VMs and other Leaseweb services using Private Network is not measured and is free of charge.
VMs inside the VMware platform can connect to each other per default, therefore Private Network is not needed.

Ordering information

You can order Private Network for VMware Single Tenant vSphere and HCI products as add-on to your VMware Single tenant platform through our Sales department.

How to set up and use Private Network for Dedicated Servers

Using the Leaseweb API or the Leaseweb Customer Portal, you can create a private network which connects two or more dedicated servers within the same data center or between interconnected data centers (in the same metro-area). For details, see the specifications below. Traffic sent between servers across the private network will not count towards your bandwidth costs.
For instructions, please refer to Private Network.

Different scenarios of using Private Network

This section describes possible scenarios using Private Network with Dedicated Servers (and Private Cloud).

ScenarioGraphical Representation

Database traffic and webserver application traffic are routed via the private network to ensure the traffic generated between the servers will be free of charge. Meanwhile, all servers remain connected to the public network.


Information
It is important to configure your applications accordingly otherwise the traffic will still use the public network
1607785
In this setup, the public uplinks of the application and database servers are disabled from the Leaseweb Customer Portal (by disabling the public switch port). Both servers will not have internet access and will only serve their services using the internal network.1607786
In this setup, Public Cloud Instances or Private Cloud VM’s are connected to Dedicated servers through Private network. Both virtual and Dedicated servers have their public uplinks active. This setup ensures that database or backup traffic generated between Dedicated servers and VM’s is unmetered and free of charge.


Information
It is important to configure your applications accordingly otherwise the traffic will still use the public network.
1607784

Database traffic and webserver application traffic is routed via the private network to ensure the traffic generated between the servers will be free of charge. Meanwhile, all servers remain connected to the public network.


Information
It is important to configure your applications accordingly otherwise the traffic will still use the public network
In this setup, all the servers are disconnected from their primary public uplinks. A server is installed as a gateway. Such a scenario can be enlarged with software load balancers and firewalls.


Information
The public IPs of the different servers cannot be routed to this gateway box.

Private Network Overview - Manage