--- title: "Configuring the vRack between the Public Cloud and a Dedicated Server" description: "Learn how to configure private networking between a Public Cloud instance and a Dedicated Server." url: https://docs.us.ovhcloud.com/en/bare-metal-cloud/dedicated-servers/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server lang: en --- > For AI agents: the complete documentation index is available at https://docs.us.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.us.ovhcloud.com/en/llms-full.txt. # Configuring the vRack between the Public Cloud and a Dedicated Server **Learn how to configure private networking between a Public Cloud instance and a Dedicated Server.** The OVHcloud [vRack](https://us.ovhcloud.com/network/vrack/) allows you to configure private network addressing between two or more OVHcloud [Dedicated Servers](https://us.ovhcloud.com/bare-metal/). But it also allows you to add [Public Cloud instances](https://us.ovhcloud.com/public-cloud/) to your private network so that you can create an infrastructure of both physical and virtual resources.   ## Requirements - An [OVHcloud Public Cloud instance](https://us.ovhcloud.com/public-cloud/) - A [vRack](https://us.ovhcloud.com/network/vrack/) service activated in your account - A [Dedicated Server](https://us.ovhcloud.com/bare-metal/) compatible with vRack - A private IP address range of your choice - Both services must be in the same vRack ### OVHcloud Control Panel Access - **Direct link:** [Public Cloud Project](https://manager.us.ovhcloud.com/#/public-cloud/pci/projects/) - **Navigation path:** `Public Cloud` > Select your project **Warning:** **NOTE:** This feature might be unavailable or limited on servers in the [Eco product line](https://eco.us.ovhcloud.com/about-us/). Please visit our [comparison page](https://eco.us.ovhcloud.com/compare/) for more information.   ## Instructions ### Add a Public Cloud project to the vRack **Note:** This does not apply to newly created projects, which are automatically delivered with a vRack. Once the project has been created, you can view the vRack by opening the `Network` menu in the left-hand sidebar and selecting `vRack Private Network`. You can also remove the project from its allocated vRack and attach it to another vRack if you wish, particularly if you already have an existing vRack with your dedicated server(s). From the [vRack section of OVHcloud Control Panel](https://manager.us.ovhcloud.com/#/dedicated/vrack), select the vRack you wish to use. From the list of eligible services, choose the Public Cloud project you want to add to the vRack and then click `Add`.   ## Integrating an instance into the vRack This guide focuses on a simple vRack configuration between a Public Cloud instance and a dedicated server. If you have set up your instance(s) with a local zones deployment mode, note that local zones do not support the vRack for now. Additionally, the **vRack** is a global L2 network and does not support "zone" or "region" level resilience. Two situations may arise: - The instance does not exist yet. - The instance already exists, and you must attach a private network to it. #### If using a new instance If you need assistance, follow our [Creating and Connecting a Public Cloud Instance](https://docs.us.ovhcloud.com/en/public-cloud/compute/getting-started.md) 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 Choose your [Public Cloud Project](https://manager.us.ovhcloud.com/#/public-cloud/pci/projects/), then navigate to the `Private Network` section. Create a new Private Network, taking note of the following settings: 1. The region for your Private Network must be the same as that of your instance. 2. For both services to communicate with each other, they have to be tagged with the same **VLAN ID**. **Note:** 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 to your private network. ##### If you do not intend to use VLAN ID 0... If you do not intend to use VLAN ID 0, you may select a different ID between 1 and 4000. In this case: - When configuring the vRack on the dedicated server, this VLAN ID must be included in the network configuration file(s). **Note:** It is possible to use the same VLAN ID for multiple private networks; however, this requires careful management of private IP addresses. Using non-overlapping DHCP pool allocations is one way to resolve this issue. **Note:** Unlike dedicated servers (when you use a VLAN ID other than 0), there is no need to include the VLAN ID directly in the Public Cloud instance's network configuration file once it has been defined in the OVHcloud Control Panel. Example: if the private network of the instance is tagged with VLAN 2, this VLAN ID must be included only in the network configuration of the dedicated server. For further information, please consult the following guide: [Create multiple VLANs in the vRack](https://docs.us.ovhcloud.com/en/bare-metal-cloud/dedicated-servers/creating-multiple-vlans-vrack.md). 3. You can keep the default private IP range or use a different one. Select "Enable DHCP for this private network" to automatically assign and configure the private IP address on the instance. You will then only need to configure the dedicated server’s network interfaces. When this option is not selected, manual configuration is required on both the Public cloud instance and the dedicated server. Make sure both **Network Gateway** options are unchecked. Once done, click on `Configure your private network`. This will take a few minutes. In the dashboard of the instance concerned, locate the "Networks" section and click the _more options_ `⋮` button next to "Private networks". Select `Attach a network`. In the pop-up window, select the private network(s) to attach to your instance and click on `Confirm`.   ### Configure your network interfaces **Note:** If you chose the option to configure the private network on your instance using DHCP, you only need to configure the network interfaces on the dedicated server. #### Configuration when using the default VLAN ID 0 Before you begin, connect to your server via SSH and list your network interfaces with the following command: ``` ip a ``` For dedicated servers, locate the line that begins with `link ether` and verify that this interface matches the **Private** interface listed in the `Network interfaces` tab of your server’s dashboard. Use this interface name to replace `NETWORK_INTERFACE` in the configurations below (example: `eth1`). For example purposes, we will use the IP address range of `192.168.0.0/16` (**Subnet mask**: `255.255.0.0`). From here, please refer to the [Configuration examples](https://docs.us.ovhcloud.com/en/bare-metal-cloud/dedicated-servers/vrack-configuring-on-dedicated-server.md#configuration-examples) section of our [Configuring the vRack on your dedicated servers](https://docs.us.ovhcloud.com/en/bare-metal-cloud/dedicated-servers/vrack-configuring-on-dedicated-server.md) guide.   #### Configuration when using a different VLAN ID In this example, we'll use **10** as the VLAN ID (tag), and **192.168.0.0/16** as the private IP address range. ##### Debian 11 The configuration below is based on Debian 11 (Bullseye). - Before you begin, establish an SSH connection to your server and run the following commands to install the VLAN package: ``` sudo apt update sudo apt install vlan ``` - Next, load the 8021q kernel module: ``` sudo modprobe 8021q ``` - To verify that the module is loaded: ``` user@server:~$ lsmod | grep 8021q 8021q 40960 0 garp 16384 1 8021q mrp 20480 1 8021q ``` - Run the following command to ensure the modules are permanently loaded at boot: ``` sudo su -c 'echo "8021q" >> /etc/modules' ``` - Retrieve the interface names and identify the private interface: ``` ip a ``` In this example, the private network interface is identified as `eno2`. - Next, create a VLAN subinterface for the network interface (non-persistent configuration) and assign (tag) it the VLAN ID. In this example, the VLAN ID is 10. Replace the values with your own. ``` sudo ip link add link eno2 name eno2.10 type vlan id 10 ``` - Next, assign a private IP address to the newly created VLAN subinterface: ``` sudo ip addr add 192.168.0.14/16 dev eno2.10 ``` - Next, activate the private interface and the VLAN subinterface: ``` sudo ip link set dev eno2 up sudo ip link set dev eno2.10 up ``` - To make the configuration persistent, add the following entries to the configuration file: ``` sudo nano /etc/network/interfaces.d/50-cloud-init ``` ``` auto eno2.10 iface eno2.10 inet static address 192.168.0.14 netmask 255.255.0.0 broadcast 192.168.255.255 vlan-raw-device eno2 ``` - Overview: - Restart the network to apply the changes: ``` sudo systemctl restart networking ``` ##### Ubuntu / Debian 12+ The configuration below is based on Ubuntu 24.04 (Noble Numbat). - Before you begin, establish an SSH connection to your server and run the following command to install the VLAN package: ``` sudo apt update sudo apt install vlan ``` - Next, load the 8021q kernel module: ``` sudo modprobe 8021q ``` - To verify that the module is loaded: ``` user@server:~$ lsmod | grep 8021q 8021q 40960 0 garp 16384 1 8021q mrp 20480 1 8021q ``` - Run the following command to ensure the modules are permanently loaded at boot: ``` sudo su -c 'echo "8021q" >> /etc/modules' ``` - Create or edit the `cloud.cfg` configuration file to prevent automatic changes to the network configuration: ``` sudo nano /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg ``` - Add this line: ``` network: {config: disabled} ``` Save and exit the file. - To obtain the network interface name and its MAC address: ``` ip a ``` - Here, the interface we want to configure is `eno2` with MAC address: `d0:50:99:d6:6b:14`. - Add the network configuration for this interface and the VLAN declaration to the configuration file, ensuring it is placed directly beneath the `version: 2` line. Replace the values with your own: ``` sudo nano /etc/netplan/50-cloud-init.yaml ``` ``` network: version: 2 ethernets: eno2: match: macaddress: d0:50:99:d6:6b:14 vlans: vlan10: id: 10 # VLAN ID link: eno2 # Interface name addresses: - 192.168.0.14/16 ``` - Overview: - Save and close the file, then run the following command: ``` sudo netplan apply ``` - If you receive the following message: ``` WARNING:root:Cannot call Open vSwitch: ovsdb-server.service is not running. ``` - You can resolve this by installing the following package: ``` sudo apt install openvswitch-switch ``` - Verify that the configuration has been properly applied: ``` ip a ``` ##### AlmaLinux and Rocky Linux (8 & 9) The configuration below is based on Almalinux 9. - Before you begin, establish an SSH connection to your server and run the following command to load the 8021q kernel module: ``` sudo modprobe 8021q ``` - To verify that the module is loaded: ``` user@server:~$ lsmod | grep 8021q 8021q 40960 0 garp 16384 1 8021q mrp 20480 1 8021q ``` - Run the following command to ensure the modules are permanently loaded at boot: ``` sudo su -c 'echo "8021q" >> /etc/modules' ``` - Retrieve the interface names and identify the private interface: ``` ip a ``` In this example, the private interface is `eno2`. - Next, create a subinterface configuration file for the VLAN in the main network configuration file. In this example, the file is named `ifcfg-eno2.10`, here eno2 refers to the private network interface and `10` the VLAN ID. ``` sudo nano /etc/sysconfig/network-scripts-ifcfg-eno2.10 ``` - Add the following entries to the configuration file. Replace the values with your own. ``` TYPE=Vlan PHYSDEV=eno2 VLAN_ID=10 BOOTPROTO=none IPADDR=192.168.0.14 PREFIX=16 NAME=eno2.10 DEVICE=eno2.10 ONBOOT=yes VLAN=yes ``` Save and exit the file. - Overview: - Restart the network interface: ``` sudo systemctl restart NetworkManager ``` ##### Fedora 42+ / AlmaLinux and Rocky Linux 10 The configuration below is based on Fedora 43. - Before you begin, establish an SSH connection to your server and run the following command to load the 8021q kernel module: ``` sudo modprobe 8021q ``` - To verify that the module is loaded: ``` user@server:~$ lsmod | grep 8021q 8021q 40960 0 garp 16384 1 8021q mrp 20480 1 8021q ``` - Run the following command to ensure the modules are permanently loaded at boot: ``` sudo su -c 'echo "8021q" >> /etc/modules' ``` - To obtain the network interface name: ``` ip a ``` In this example, the interface is called `eno2`. We will need to create a VLAN subinterface before assigning a private IP address to it. - Use the following command to create the VLAN interface: ``` sudo nmcli con add type vlan con-name dev id . ``` Replace `vlan-name` with the name of the VLAN subinterface, `parent-interface` with the name of the private interface and `vlan-id` with the VLAN ID. **In this example:** ``` sudo nmcli con add type vlan con-name eno2.10 dev eno2 id 10 Connection 'eno2.10' successfully added. ``` - Assign a private IP address to the VLAN subinterface: ``` sudo nmcli con mod ipv4.addresses ipv4.method manual ``` **In this example:** ``` sudo nmcli con mod eno2.10 ipv4.addresses 192.168.0.14/16 ipv4.method manual ``` - Next, bring the up the VLAN subinterface: ``` sudo nmcli con up . ``` **In this example:** ``` sudo nmcli con up eno2.10 # Connection successfully activated ``` The steps above create a configuration file for the VLAN interface. This file is located at `/etc/NetworkManager/system-connections/` and follows the naming format `vlan-name.nmconnection`. In this example, the file is called `eno2.10.nmconnection`. - Overview: ##### Windows Log on to your server via a remote desktop connection, and open the Server Manager app. Then select `Local Server`. Now click the `Disabled` link next to **NIC Teaming**: Next, right-click on the network interface and select `Add to New Team`. In the pop-up window, create a new team by typing a team name into the **Team name** field. When you have finished, click `OK`. Next, we need to define the VLAN tag. In the **ADAPTERS AND INTERFACES** pane of the **NIC Teaming** screen, go to the `Team Interfaces` tab and right-click the interface you have just added to the new team, then click `Properties`. Now click `Specific VLAN`, and define the tag: From here, continue by using the instructions for [Windows configuration](https://docs.us.ovhcloud.com/en/bare-metal-cloud/dedicated-servers/vrack-configuring-on-dedicated-server.md#configuration-examples) in our [Configuring the vRack on your dedicated servers](https://docs.us.ovhcloud.com/en/bare-metal-cloud/dedicated-servers/vrack-configuring-on-dedicated-server.md) guide.   ## Go further [Creating multiple VLANs in a vRack](https://docs.us.ovhcloud.com/en/bare-metal-cloud/dedicated-servers/creating-multiple-vlans-vrack.md) Browse all the [Dedicated Servers guides](https://docs.us.ovhcloud.com/en/bare-metal-cloud/dedicated-servers/landing-page-dedicated-servers.md). Browse the rest of the [OVHcloud US documentation](https://docs.us.ovhcloud.com/en/index.md) for guides on our other products and services. Learn more about [Dedicated Servers](https://us.ovhcloud.com/bare-metal/) on the OVHcloud US website.