Configuring the vRack between the Public Cloud and a Dedicated Server

Last updated 14th February 2023

Objective

The OVHcloud vRack allows you to configure private network addressing between two or more OVHcloud Dedicated Servers. But it also allows you to add Public Cloud instances to your private network so that you can create an infrastructure of both physical and virtual resources.

This guide will show you how to configure private networking between a Public Cloud instance and a Dedicated Server.

Requirements

• An OVHcloud Public Cloud instance
• A vRack service activated in your account
• A Dedicated Server compatible with the vRack
• Access to the OVHcloud Control Panel
• A private IP address range of your choice

Instructions

Add a Public Cloud project to the vRack

Once your Public Cloud project is set up, you will need to add it to the vRack. This can be done in two ways:

1. By ordering a vRack service if you do not have one yet, this service is free of charge.

Go to the Bare Metal Cloud menu and click on the Order button. Under this menu, click on vRack.

You will be redirected to another page to validate the order, it will take a few minutes for the vRack to be setup in your account.

Once the vRack service is delivered to your account, you can now add your project to it.

Go to the Bare Metal Cloud menu, click on Network, then on vRack. Select your vRack from the list.

From the list of eligible services, select the project you want to add to the vRack and then click on the Add button.

2. By creating or adding an existing vRack service in the Public Cloud section.

Add an Instance to the vRack

Two situations may arise:

• The instance does not exist yet.
• The instance already exists and you must add it to the vRack.

In case of a new instance

If you need assistance, follow this guide first: Creating your first Public Cloud instance. When creating an instance, you can specify, in Step 4, a private network to integrate your instance into. Choose your previously created vRack from the drop-down menu.

In case of an existing instance

You can attach an existing instance to a private network. For more information, please refer to this section of the corresponding guide.

Create a VLAN ID

For both services to communicate with each other, they have to be tagged with the same VLAN ID.

Using the default VLAN ID

By default, the VLAN ID for dedicated servers is 0. To use this VLAN ID, it will be necessary to tag the private network linked to your instance with VLAN 0. To do this, you will need to go through the OVHcloud APIv6.

Using a different VLAN ID

To use a different VLAN ID:

• The private network linked to the Public Cloud instance must be tagged with this VLAN ID.
• In the network configuration file on the dedicated server, the private network interface should be tagged with this VLAN ID.

In this case, if you tick the Set a VLAN ID box, you will need to choose a VLAN ID number between 2 and 4,000.

If you do not tick the box, the system will assign a random VLAN ID number to your private network.

An example: If your instance private network is tagged with VLAN 2, the private network interface on your dedicated server should be tagged with VLAN 2. For more information consult the following guide: Create multiple VLANs in the vRack.

Configure your network interfaces

Next, configure the network interfaces on your new Public Cloud instance and Dedicated Server using this guide: Configuring the vRack on your Dedicated Servers.

Go further

Join our community of users on https://community.ovh.com/en/.

---

---

These guides might also interest you...