Search


print PDF Ireland
Virtual Rack

Requirements


To use the functions explained in this guide you must have a Virtual Rack.
You can order it here.

Therefore, you must:
  • Have a Virtual Rack (vRack)
  • Have a dedicated servers which us SP, EG, MG or HG (1Gb/s) (Gigabit and Fast Ethernet) with the option for professional use.
  • Be able to connect via SSH (for Linux servers)

General

The virtual rack is compatible with all 1 Gbit/s and 10 Gbit/s servers EG, MG, HG series in the data centers RBX 1-5 (is the only option to set up a separate virtual rack, the other OVH datacentres currently in preparation).

The Virtual Rack allows to connect several serversto a virtual switch. Your servers can communicate with each other privately and securely (in a dedicated VLAN).

Order a Vrack


Order professional use on the servers:

  • If you do not have a professional server, visit the OVH Manager and click on the server that requires it to order it: Professional servers offers

Order Virtual Rack:

  • To order your virtual rack visit the manager v3. On the homepage, select one of your servers.
    Go to the section "Services" and click "Order a Virtual Rack".
    Simply select the servers you want to add to your infrastructure and validate your order.

Once your virtual rack is installed you will receive a confirmation email containing the number of your vrack and some useful information.

Vlan Configuration


Above all we recommend you install the following packages as it will be useful for configuration and diagnostics in case of problems:

  • vlan or vconfig Mandatory to configure your vrack
  • tcpdump To listen NICs
  • netcat or nc For testing transfers between two servers for example
  • fping Will be useful to ping a range of IPs
  • netmask Which will allow to see the number of available IPs

Info !
Throughout this guide, eth0.XXXX corresponds to tag your vrack Example for vrack 2009 eth0.XXXX = eth0.2009. In all the examples below where we configure our vrack with IP 172.16.0.1 and this on two machines: testvrack1 (172.16.0.1) and testvrack2 (172.16.0.2).

IMPORTANT !!
You can set 172.16.0.0/12 with the exception of IP listed below, you must not add IN ANY CASE the following IPs as the interface on your machine:
  • 172.16.0.0 => IP Network
  • 172.31.0.252 => IP reserved for internal use OVH
  • 172.31.0.253 => IP reserved for internal use OVH
  • 172.31.0.254 => IP Gateway your vrack


Info!
But how many IPs are in a /16? Netmask can help you see the number of IPs. In ssh, connected to your server type:
netmask -r 172.16.0.0/12
and you'll get:
172.16.0.0-172.31.255.255 (8192)
You can use IP 8192 IP except those listed above. As a good administrator is 172.16.0.1 and we begin to stop at 172.31.255.250


Linux Basic

Debian & Ubuntu

IMPORTANT !!
You can set 172.16.0.0/12 with the exception of IPs listed below, you must not add IN ANY CASE following IP as the interface on your machine:
  • 172.16.0.0 => IP Network
  • 172.31.255.252 => IP reserved for internal use OVH
  • 172.31.255.253 => IP reserved for internal use OVH
  • 172.31.255.254 => IP Gateway your vrack

Install the packages mentioned above:
testvrack1:~# apt-get install vlan netcat fping tcpdump netmask

Edit the network configuration file /etc/network/interfaces and add this by replacing XXXX with the tag of your vrack:
auto eth0.XXXX
iface eth0.XXXX inet static # replace XXXX for the tag of your virtual rack
address 172.16.0.1
netmask 255.240.0.0
post-up ip r a 172.16.0.0/12 via 172.31.255.254 dev eth0.XXXX ; true # replace XXXX with the tag of your vrack.


Then restart your network interface:
/etc/init.d/networking restart

To check your configuration:
testvrack1:~#ifconfig
eth0 Link encap:Ethernet HWaddr 00:1c:c0:b9:98:f3
inet adr:94.23.196.195 Bcast:94.23.196.255 Masque:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:48325 errors:0 dropped:0 overruns:0 frame:0
TX packets:28121 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:4033662 (3.8 MiB) TX bytes:3680376 (3.5 MiB)
M�moire:e0200000-e0220000

eth0.2009 Link encap:Ethernet HWaddr 00:1c:c0:b9:98:f3
inet adr:172.16.0.1 Bcast:172.31.255.255 Masque:255.240.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3726 errors:0 dropped:0 overruns:0 frame:0
TX packets:2775 errors:0 dropped:4 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:174402 (170.3 KiB) TX bytes:181332 (177.0 KiB)

lo Link encap:Boucle locale
inet adr:127.0.0.1 Masque:255.240.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1291 errors:0 dropped:0 overruns:0 frame:0
TX packets:1291 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:146137 (142.7 KiB) TX bytes:146137 (142.7 KiB)

testvrack1:~# route -n
IP routing table
Destination Gateway Genmask Flgs Metric Ref Use Iface
94.23.196.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
172.16.0.0 0.0.0.0 255.240.0.0 U 0 0 0 eth0.2009
0.0.0.0 172.31.255.254 0.0.0.0 UG 0 0 0 eth0.2009
0.0.0.0 94.23.196.254 0.0.0.0 UG 0 0 0 eth0

To test your configuration, you can ping the gateway or another server of your vrack where you have already performed the operations described above:
testvrack1:~# ping 172.31.255.254
PING 172.16.0.2 (172.16.0.2) 56(84) bytes of data.
64 bytes from 172.31.255.254: icmp_seq=1 ttl=63 time=9.46 ms
64 bytes from 172.31.255.254: icmp_seq=2 ttl=63 time=0.219 ms

testvrack1:~# ping 172.16.0.2
PING 172.16.0.2 (172.16.0.2) 56(84) bytes of data.
64 bytes from 172.16.0.2: icmp_seq=1 ttl=63 time=8.83 ms
64 bytes from 172.16.0.2: icmp_seq=2 ttl=63 time=0.220 ms


Gentoo

IMPORTANT !!
You can set 172.16.0.0/12 with the exception of IPs listed below, you must not add IN ANY CASE following IP as the interface on your machine:
  • 172.16.0.0 => IP Network
  • 172.31.255.252 => IP reserved for internal use OVH
  • 172.31.255.253 => IP reserved for internal use OVH
  • 172.31.255.254 => IP Gateway your vrack

Install the packages mentioned above:
testvrack1:~# emerge install vlan netcat fping tcpdump whatmask

Edit the network configuration file /etc/conf.d/net and add this by replacing XXXX with the tag of your vrack:
vlans_eth0="XXXX" # replace XXXX for the tag of your Virtual Rack

vconfig_eth0=( "set_name_type VLAN_PLUS_VID_NO_PAD" ) # do not modify this line

config_vlanXXXX=( "172.16.0.1 netmask 255.0.0.0" ) # replace XXXX for the tag of your Virtual Rack

Then restart your network interface:
/etc/init.d/net.eth0 restart

To check your configuration:
testvrack1 ~ # ifconfig
eth0 Lien encap:Ethernet HWaddr 00:1c:c0:b9:98:f3
inet adr:94.23.196.195 Bcast:94.23.196.255 Masque:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11260 errors:0 dropped:0 overruns:0 frame:0
TX packets:5307 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:3738636 (3.5 MiB) TX bytes:701067 (684.6 KiB)
M�moire:e0200000-e0220000

lo Lien encap:Boucle locale
inet adr:127.0.0.1 Masque:255.240.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vlan2009 Lien encap:Ethernet HWaddr 00:1c:c0:b9:98:f3
inet adr:172.16.0.1 Bcast:172.31.255.255 Masque:255.240.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:730 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:34852 (34.0 KiB) TX bytes:3556 (3.4 KiB)

testvrack1 ~ # route -n
IP routing table
Destination gateway Genmask Indic Metric Ref Use Iface
94.23.196.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
172.16.0.0 0.0.0.0 255.240.0.0 U 0 0 0 vlan2009
127.0.0.0 0.0.0.0 255.240.0.0 U 0 0 0 lo
0.0.0.0 94.23.196.254 0.0.0.0 UG 0 0 0 eth0

To test your configuration, you can ping the gateway or another server of your virtual bay where you have already performed the operations described above:
testvrack1:~# ping 172.31.255.254
PING 172.16.0.2 (172.16.0.2) 56(84) bytes of data.
64 bytes from 172.31.255.254: icmp_seq=1 ttl=63 time=9.46 ms
64 bytes from 172.31.255.254: icmp_seq=2 ttl=63 time=0.219 ms

testvrack1:~# ping 172.16.0.2
PING 172.16.0.2 (172.16.0.2) 56(84) bytes of data.
64 bytes from 172.16.0.2: icmp_seq=1 ttl=63 time=8.83 ms
64 bytes from 172.16.0.2: icmp_seq=2 ttl=63 time=0.220 ms


Red Hat & CentOS & Fedora

IMPORTANT !!
You can set 172.16.0.0/12 with the exception of IPs listed below, you must not add IN ANY CASE following IP as the interface on your machine:
  • 172.16.0.0 => IP Network
  • 172.31.255.252 => IP reserved for internal use OVH
  • 172.31.255.253 => IP reserved for internal use OVH
  • 172.31.255.254 => IP Gateway your vrack

Install the packages mentioned above, netcat is already installed(nc):
testvrack1:~# yum install vconfig tcpdump

To install fping:
wget http://fping.sourceforge.net/download/fping.tar.gz
tar zxvf fping.tar.gz
cd fping-2.4b2_to/
./configure
make
make install

To install whatmask:
Waiting rpm compile

We copy the network configuration file and we add the tag of vrack:
cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth0.XXXX

We then edit the file:
DEVICE=eth0.XXXX # replace XXXX for the tag of your Virtual Rack
VLAN=yes
BOOTPROTO=static
IPADDR=172.16.0.2
NETMASK=255.240.0.0
ONBOOT=yes
BROADCAST=172.31.255.255

Next, install your network interface:
ifup eth0.XXXX # replace XXXX for the tag of your Virtual Rack

To check your configuration:
root@testvrack2 ~# ifconfig

eth0 Link encap:Ethernet HWaddr 00:1C:C0:BA:D4:54
inet addr:94.23.196.217 Bcast:94.23.196.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:319842 errors:0 dropped:0 overruns:0 frame:0
TX packets:267546 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:366903141 (349.9 MiB) TX bytes:228654217 (218.0 MiB)
Memory:e0200000-e0220000

eth0.2009 Link encap:Ethernet HWaddr 00:1C:C0:BA:D4:54
inet addr:172.16.0.2 Bcast:172.31.255.255 Mask:255.240.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:110446 errors:0 dropped:0 overruns:0 frame:0
TX packets:45326 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:110613350 (105.4 MiB) TX bytes:108015196 (103.0 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.240.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:140 errors:0 dropped:0 overruns:0 frame:0
TX packets:140 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19479 (19.0 KiB) TX bytes:19479 (19.0 KiB)

root@testvrack2 ~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
94.23.196.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0.2009
172.16.0.0 0.0.0.0 255.240.0.0 U 0 0 0 eth0.2009
0.0.0.0 94.23.196.254 0.0.0.0 UG 0 0 0 eth0

To test your configuration, you can ping the gateway or another server of your virtual bay where you have already performed the operations described above:
root@testvrack2 ~# ping 172.31.255.254
PING 172.31.255.254 (172.31.255.254) 56(84) bytes of data.
64 bytes from 172.31.255.254: icmp_seq=1 ttl=255 time=8.36 ms
64 bytes from 172.31.255.254: icmp_seq=2 ttl=255 time=0.407 ms
64 bytes from 172.31.255.254: icmp_seq=3 ttl=255 time=0.388 ms

root@testvrack2 ~# ping 172.16.0.1
PING 172.16.0.1 (172.16.0.1) 56(84) bytes of data.
64 bytes from 172.16.0.1: icmp_seq=1 ttl=63 time=11.4 ms
64 bytes from 172.16.0.1: icmp_seq=2 ttl=63 time=0.218 ms
64 bytes from 172.16.0.1: icmp_seq=3 ttl=63 time=0.213 ms



Virtualisation

Esxi


Guide on using vRack with Esxi ""ESXI""

Proxmox


In development.

Other Distributions

Windows Server 2008

IMPORTANT !!
You can set 172.16.0.0/12 with the exception of IPs listed below, you must not add IN ANY CASE following IP as the interface on your machine:
  • 172.16.0.0 => IP Network
  • 172.31.255.252 => IP reserved for internal use OVH
  • 172.31.255.253 => IP reserved for internal use OVH
  • 172.31.255.254 => IP Gateway your vrack


Update first the network card driver by downloading the driver at this address:

http://downloadcenter.intel.com/detail_desc.aspx?agr=Y&DwnldID=18725

You have to get the reference number of the NIC with the following command from the command line:
C:\Program Files\Intel\DMIX\CL\PROSetCL.exe Adapter_Enumerate


Then you must create a script .bat in C:\Program Files\Intel\DMIX\CL\ to configure VLANs:

PROSetCL.exe Adapter_CreateVlan? num_carte XXX vrackXXX
ping -n 5 127.0.0.1 >NUL 2>&1
PROSetCL.exe Adapter_CreateVlan? num_carte 0 vrack0
ping -n 5 127.0.0.1 >NUL 2>&1


num_carte: corresponds to the number of the NIC
XXX : is the number of your Vrack

Then you will have two new interface in the network management server.
For the interface Vrack0 you must provide the IP configuration on your server's informatons:
IP : xx.xx.xx.xx
Netmask : 255.255.255.0
Gateway : xx.xx.xx.254
DNS Server : 213.186.33.99


Finally Vrack_num_vrack interface, you must configure the IP address you want to put on the Vrack with:
Gateway : 172.31.255.254
DNS Server : 213.186.33.99


Windows Server 2012

IMPORTANT !!
You can set 172.16.0.0/12 with the exception of IPs listed below, you must not add IN ANY CASE following IP as the interface on your machine:
  • 172.16.0.0 => IP Network
  • 172.31.255.252 => IP reserved for internal use OVH
  • 172.31.255.253 => IP reserved for internal use OVH
  • 172.31.255.254 => IP Gateway your vrack


It is strongly recommended to perform the vrack configuration BEFORE any configuration for HyperV, which bind the physical interface with a virtual interface therefore preventing the creation of vlan tagged interfaces. The presence of KVM (ipmi or USB) to the server is also highly recommended to regain control if necessary.


Go to in the Server Manager and click on Local Server:


Then click on Nic Teaming, Tasks and then click New Team:


You will lose at this stage your connection, you can simply restart your connection to continue setup.

Now indicate the name of the team here, and select the network card to use:



Once the team is created and selected in the left Cards and Interfaces, click Tasks and then click Add Interface:



Now specify the name of the interface for your Vrack here Vrack2222, replace 2222 with the number of your Vrack:





Then you will have two new interface in Network and Sharing Center.
Interface for Vrack you must provide the IP configuration information on your server:
The IP : xx.xx.xx.xx
The Netmask: 255.255.255.0
The Gateway: xx.xx.xx.254
The DNS: 213.186.33.99


Finally the interface Vrack_num_vrack, you must configure the IP address that you want the Vrack with:
The Gateway: 172.31.255.254
The DNS: 213.186.33.99



Free BSD

IMPORTANT !!
You can set 172.16.0.0/12 with the exception of IPs listed below, you must not add IN ANY CASE following IP as the interface on your machine:
  • 172.16.0.0 => IP Network
  • 172.31.255.252 => IP reserved for internal use OVH
  • 172.31.255.253 => IP reserved for internal use OVH
  • 172.31.255.254 => IP Gateway your vrack


To enable support vlans start your server, you edit the file /boot/defaults/loader.conf, and we replace:

if_vlan_load="NO"

with

if_vlan_load="YES"


Saves the main configuration file:

cp /etc/rc.conf /etc/rc.conf.bak


We then edit the file /etc/rc.conf, and we add to the file the following lines:

replace XXXX with the tag of your virtual rack
cloned_interfaces="em0.vlanXXXX"
ifconfig_em0_vlanXXXX="inet 172.16.0.2 netmask 255.240.0.0 broadcast 172.31.255.255"


Restart the network interfaces:
/etc/rc.d/netif restart && /etc/rc.d/routing restart


Check the configuration:


testvrack1# netstat -nr
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 94.23.196.254 UGS 2 64 em0
172.16.0.0/12 link#3 U 0 0 em0.vl
172.16.0.2 link#3 UHS 0 0 lo0
94.23.196.0/24 link#1 U 3 777 em0
94.23.196.195 link#1 UHS 0 0 lo0
127.0.0.1 link#2 UH 0 0 lo0


To test your configuration, you can ping the gateway or another server in your virtual rack where you have already performed the steps described above:

testvrack1# ping 172.31.255.254
PING 172.31.255.254 (172.31.255.254): 56 data bytes
64 bytes from 172.31.255.254: icmp_seq=0 ttl=255 time=1.957 ms
64 bytes from 172.31.255.254: icmp_seq=1 ttl=255 time=0.551 ms
64 bytes from 172.31.255.254: icmp_seq=2 ttl=255 time=0.525 ms

3 packets transmitted, 3 packets received, 0.0% packet loss



testvrack1# ping 172.16.0.1
PING 172.16.0.38 (172.16.0.1): 56 data bytes
64 bytes from 172.16.0.1: icmp_seq=0 ttl=63 time=6.721 ms
64 bytes from 172.16.0.1: icmp_seq=1 ttl=63 time=0.300 ms
64 bytes from 172.16.0.1: icmp_seq=2 ttl=63 time=0.306 ms

3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.300/2.442/6.721/3.025 ms


Open Solaris


In development.

Tests, Diagnostics


  • Your IP is private in "ifconfig" or in "ip addr show" ? If not, check your network configuration file and restart the interface
  • The IP is private but not on the vrack:Have you configured the tag of vrack in the network configuration file?
  • The gateway does not ping:Is the server really in the vrack? Have you configured the right gateway? Do you have configured a firewall blocking the requests?
  • To verify what IPs are addable in your block:
root@testvrack1 fping-2.4b2_to# fping -g 178.33.8.64/28 # replace this for your block
178.33.8.64 error while sending ping: Permission denied

178.33.8.71 is alive
178.33.8.78 is alive

  • For flow between your servers:
In the server to test :
# nc -l 7777 > /dev/null

In the other server :
# dd if=/dev/zero bs=100M count=1 | nc 178.33.8.71 7777
1+0 records in
1+0 records out
104857600 bytes (105 MB) copied, 9,08299 s, 61,5 MB/s

  • The gateway pings, but not the other servers:

( section in progress )

Additional Options

In addition to the standard use of your virtual rack you can also:

Bloc IP RIPE




Additional sections in progress