| title | excerpt | updated |
|---|---|---|
Configuring the vRack between the Public Cloud and a Dedicated Server |
Find out how to configure private networking between a Public Cloud instance and a Dedicated Server |
2024-11-08 |
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.
- 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
Warning
This feature might be unavailable or limited on servers of the Eco product line.
Please visit our comparison page for more information.
[!primary] This does not apply to newly created projects, which are automatically delivered with a vRack. To view the vRack once the project has been created, go the
Bare Metal Cloud{.action} menu and click onNetwork{.action} in the left tab. Click onvRack private network{.action} to view the vRack(s).You can also remove the project from its allocated vRack and attach it to another vRack if you wish, particularly if you already had an existing vRack with your dedicated server(s).
For older projects, once you have ordered your vRack, go to the Bare Metal Cloud{.action} menu, click on Network{.action} in the left tab, then on vRack private network{.action}. Select your vRack from the list.
From the list of eligible services, select the project you want to add to the vRack and click the Add{.action} button.
{.thumbnail}
Two situations may arise:
- The instance does not exist yet.
- The instance already exists and you must attach a private network to it.
If you need assistance, follow this guide first: Creating your first Public Cloud instance. When creating an instance, you can choose, in Step 5, a network mode, followed by a private network to integrate your instance into.
You can attach a private network to an existing instance.
With your project linked to the vRack, you are ready to create private networks.
In the Public cloud tab, click on Private Network{.action} in the left-hand menu under Network.
Click on the button Add Private Network{.action}.
{.thumbnail}
The following page allows you to customise multiple settings.
In step 1, select the region in which you want the private network to be located.
{.thumbnail}
For both services to communicate with each other, they have to be tagged with the same VLAN ID.
This can be configured in step 2.
{.thumbnail}
This step offers several configuration options. For the purpose of this guide, we will focus on the necessary ones. Click on the tabs below to view the details:
[!tabs] Private Network Name
Enter a name for your private network.
Layer 2 network options
By default, the VLAN ID for dedicated servers is 0. To use this VLAN ID for an instance, it will be necessary to tag the private network with VLAN 0 as well. Tick the Set a VLAN ID box and select VLAN ID 0.
If you do not tick the box, the system will assign a random VLAN ID number to your private network.
Using a different VLAN ID
If you do not intend use the VLAN ID 0, you can select a different ID between 1 to 4000. The following rules apply:
- The private network linked to the Public Cloud instance must be tagged with this VLAN ID.
- When configuring the vRack on the dedicated server, this VLAN ID should be included in the network configuration file.
[!primary] 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.
[!primary] Unlike dedicated servers (when using a VLAN ID other than 0), there is no need to include the VLAN ID directly in the network configuration file of the Public Cloud instance once it is set in the OVHcloud Control Panel.
An example: If your instance private network is tagged with VLAN 2, this VLAN ID should be included in the network configuration of the dedicated server only. For more information consult the following guide: Create multiple VLANs in the vRack.
DHCP address distribution options
You can keep the default private IP range or use a different one.
Once done, click on Create{.action}. This will take a few minutes.
In the corresponding instance dashboard, click on the ...{.action} button in the box "Networks", next to "Private networks", and select Attach a network{.action}.
{.thumbnail}
In the popup window that appears, select the private network(s) to attach to your instance and click on Attach{.action}.
{.thumbnail}
Next, configure the network interfaces on your new public cloud instance and Dedicated Server using this guide: Configuring the vRack on your Dedicated Servers.
Join our community of users.