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)

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 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.


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

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:

Edit the network configuration file /etc/network/interfaces and add this by replacing XXXX with the tag of your vrack:

Then restart your network interface:

To check your configuration:

To test your configuration, you can ping the gateway or another server of your vrack where you have already performed the operations described above:

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:

Edit the network configuration file /etc/conf.d/net and add this by replacing XXXX with the tag of your vrack:

Then restart your network interface:

To check your configuration:

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:

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):

To install fping:

To install whatmask:

We copy the network configuration file and we add the tag of vrack:

We then edit the file:

Next, install your network interface:

To check your configuration:

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:





Guide on using vRack with Esxi ""ESXI""


In development.

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:


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



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:


Finally Vrack_num_vrack interface, you must configure the IP address you want to put on the Vrack with:

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:


Finally the interface Vrack_num_vrack, you must configure the IP address that you want the Vrack with:

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:

with


Saves the main configuration file:


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


Restart the network interfaces:


Check the configuration:



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:




In development.

• 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:

• For flow between your servers:

In the server to test :

In the other server :

• The gateway pings, but not the other servers:

( section in progress )

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

• Use an IP block in your vrack RIPE Click to consult the guide RipeVrack

• Cisco Loadbalancing with Cisco: click to view the guide Cisco ACE

Additional sections in progress