Last updated 21st June 2018
Objective
The vRack or virtual rack allows multiple servers to be grouped together (regardless of number and physical location in our datacentre) and connects them to a virtual switch within the same private network. Your servers can communicate privately and securely between each other (within a dedicated VLAN).
This guide will help you to configure the vRack on two or more dedicated servers.
Requirements
- a vRack service activated in your account
- two or more vRack compatible servers
- administrative (root) access to the server via SSH
- access to the OVH Control Panel
- your chosen private IP address range
Instructions
Step 1: Add your servers to the vRack
Once the vRack is in your account go to the Cloud section of your control panel and select the vRack menu on the left.
Select your vRack from the list and then, from the list of eligible services, select the servers you want to add to the vRack and then click the Add button.
Step 2: Configure your network interfaces
For example purposes, we’ll use an internal IP address range of 192.168.0.0/16.
Also, we’ve used the names of eth1 and eno4 for the secondary network interface. Your servers may use a different naming convention. To be sure, please check with the following commands.
List your network interfaces with the following command:
ifconfig -a | grep eth | awk '{print $ 1}'
The first interface in the list is your primary network connection. you can check which one is active with the following command:
ifconfig eth1 up
ethtool eth1 | grep "Link detected"
If the command returns Link detected: no then this is the network interface you should use for your vRack configuration after running this command:
ifconfig eth1 down
CentOS 6 and 7
Open the network interface configuration file with the following command:
vi /etc/sysconfig/network-scripts/ifcfg-eth1
Press the I key on your keyboard to enter Insert Mode.
Configure the secondary network interface as follows:
DEVICE=eth1
BOOTPROTO=static
IPADDR=192.168.0.1
NETMASK=255.255.0.0
ONBOOT=yes
TYPE=Ethernet
In the example above, you can use any private IP range of your choice and any address within that range.
Save your changes to the network config file and exit the editor. Then repeat the process for your other server(s) and assign a unique IP address from your internal range. Once you have done this, your servers will be able to communicate with each other on the private network.
Linux (Debian 7, 8)
Open the network interface configuration file with the following command:
nano /etc/network/interfaces
Configure the secondary network interface as follows:
auto eth1
iface eth1 inet static
address 192.168.0.1
netmask 255.255.0.0
In the example above you can use any private IP range of your choice and any address within that range.
Save your changes to the network config file and exit the editor. Then repeat the process for your other server(s) and assign a unique IP address from your internal range. Once you have done this, your servers will be able to communicate with each other on the private network.
Linux (Debian 9)
Open the network interface configuration file with the following command:
nano /etc/network/interfaces
Configure the secondary network interface as follows:
auto eno4
iface eno4 inet static
address 192.168.0.1
netmask 255.255.0.0
In the example above you can use any private IP range of your choice and any address within that range.
Save your changes to the network config file and exit the editor. Then repeat the process for your other server(s) and assign a unique IP address from your internal range. After doing this, your servers will be able to communicate with each other on the private network.
Repeat this process for your other server(s) and assign a unique IP address from your internal range. After doing this, your servers will be able to communicate with each other on the private network.
Ubuntu Server 16
Open the network interface configuration file with the following command:
vi /etc/network/interfaces
Press the I key on your keyboard to enter Insert Mode and then configure the secondary network interface as follows:
auto eth1
iface eth1 inet static
address 192.168.0.1
netmask 255.255.0.0
In the example above you can use any private IP range of your choice and any address within that range.
Save your changes to the network config file and exit the editor. Then repeat the process for your other server(s) and assign a unique IP address from your internal range. Once you have done this, your servers will be able to communicate with each other on the private network.
Ubuntu Server 17
Open the network interface configuration file with the following command:
nano /etc/network/interfaces
Configure the secondary network interface as follows:
auto eno4
iface eno4 inet static
address 192.168.0.1
netmask 255.255.0.0
In the example above, you can use any private IP range of your choice and any address within that range.
Save your changes to the network config file and exit the editor. Then repeat the process for your other server(s) and assign a unique IP address from your internal range. Once you have done this, your servers will be able to communicate with each other on the private network.
Windows
For example purposes, we’ll use an internal IP address range of 192.168.0.0/16.
Log on to your Windows server by remote desktop and go to the Control Panel.
Click Network and Internet
Click Network and Sharing Centre
Change Adapter Settings
Right-click the secondary network interface and then click Properties
Double-click Internet Protocol Version 4 (TCP/IP/IPv4)
Click Use the following IP address. For IP address, type in an IP from your internal range. For Subnet mask, type in 255.255.0.0.
Click the OK button to save the changes and the reboot your server.
Repeat this process for your other server(s) and assign a unique IP address from your internal range. Once you have done this, your servers will be able to communicate with each other on the private network.
Go further
Join our community of users on https://community.ovh.com/en/.
Did you find this guide useful?
Please feel free to give any suggestions in order to improve this documentation.
Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.
Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.
Thank you. Your feedback has been received.