Skip to main content

Configuring the vRack between the Public Cloud and a Dedicated Server

Stephanie R.
Updated

Learn how to configure private networking between a Public Cloud instance and a Dedicated Server.

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.

 

Requirements

NOTE: This feature might be unavailable or limited on servers in the Eco product line.
             Please visit our comparison page for more information.

 

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.

    From the OVHcloud Control Panel, click Bare Metal Cloud in the top navigation bar.

    Select the Order button, and then click vRack.

    DS_vRack-with-PCI01.png

    You will be redirected to another page to validate the order, it will take a few minutes for the vRack to be set up 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 Network, and 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.

    DS_vRack-with-PCI02**.png

  1. By adding an existing vRack service in the Public Cloud section.

 

Add an Instance to the vRack

In case of a new instance

If you need assistance, follow our Creating and Connecting a Public Cloud Instance guide. When creating an instance, you can choose to connect your instance to a specific private network. 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 our 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.

For Public Cloud, you set a unique vLAN ID per private network.

It is not possible to set the same vLAN ID on two different private networks.

 

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.

Unlike dedicated servers, there is no need to tag a vLAN directly in the network configuration file of the Public Cloud instance, once the vLAN ID is set in the OVHcloud Control Panel.

An example: if your instance private network is tagged vLAN 2, the private network interface on your dedicated server should be tagged with vLAN 2. For more information, consult the following guide: Creating Multiple vLANs in a vRack.

 

Configure your network interfaces

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

 

Go further

For more information and tutorials, please see our other Dedicated Server support guides, and our Public Cloud guides, or explore the guides for other OVHcloud products and services.

Related articles