To use this guide, you must have a Virtual Rack offers.

You will need :

• A Virtual Rack (vrack)
• Have at least one dedicated server from EG, MG or HG (Ethernet 1Gb/s) range with the option for professional use.
• Able to connect via SSH: SSH on a Dedicated Server (Linux Servers)
• A RIPE IP Block (only if you want the machines to have access vlan network service)

Information You do not have to order a new RIPE IP block. You can switch an existing block to your virtual rack. For more information, see the Checkout & Switch!

Virtual Rack brings together several virtual servers (whatever their number and physical location in our Datacentres) and connect to a virtual switch within a single private network. Your servers can communicate privately and securely between them (in a dedicated VLAN).


You can order one directly for your virtual rack.
Log in to your manager and select your "vrackXXXX" at home in "Dedicated Server> "Infrastructures".
Click on "RIPE Block" and then "Order a RIPE Block" and then confirm your order.


Already have a RIPE IP block assigned to a server? In this case you can switch this block directly to your VLAN. No matter if the original server is part of it or not.

IMPORTANT!! This procedure will reform blocks divided and all will be re-routed to the IP VLAN. All virtual macs associated with the block will be deleted. Make sure to either stop using the IPs in the block, and have your migration set in advance (see below).

Log in to your manager V3 and select the server with the block in question.
Go to the section "Services" then "IP FailOver? RIPE", select the block in question and then click
In the drop down "Change routing to" select the virtual destination VrackXXXX Bay. In the case of a split block or havomg virtual mac it will display a warning.

A confirmation email with the configuration settings to use will be sent shortly thereafter.

Info ! In all the examples here we will configure our vrack with the virtual IP 172.16.0.1 and this on two machines: testvrack1 (172.16.0.1) and testvrack2 (172.16.0.2). You will need the following examples replace XXXX with the number assigned by OVH vrack.

IMPORTANT !! You can set 172.31.0.0/8 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 OVH internal use 172.31.255.253 => IP reserved for OVH internal use 172.31.255.254 => IP Gateway of your virtual vrack The introduction of Virtual Machine (VM) within a virtual rack, you save the free virtual mac It is forbidden that more than one VM to have the same mac

We will create a Virtual Machine Port Group to our new vlan:

Via the vSphere Interface, go to the Configuration tab, click on Networking, then click Add Networking... :



We will create a connection type Virtual Machine:



It connects the Port Group in vSwitch associated with the network card by selecting Use vSwitch0:



We modify Network Label to VLANXXX to make it easier to manage, and it changes the VLAN ID with that assigned by OVH:




We then create a new machine that we associate with the virtual bay.

At the last stage before finalization, we click Edit the virtual machine settings before completion and Continue :



It will change the value of Network Connection by selecting VLANXXX. We suggest you put an end to the custom mac, in fact it should never two virtual machines the same virtual vrack. We can follow a standard 00:50:56:0ma_esxi_n 1:00 ma_première_interface. For example, if I configure the first network interface of my first ESXi:

00:50:56:01:00:01

IMPORTANT !! You can set 172.16.0.0/8 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 OVH internal use 172.31.255.253 => IP reserved for OVH internal use 172.31.255.254 => IP Gateway of your virtual vrack The introduction of Virtual Machine (VM) within a virtual rack, you save the free virtual mac It is forbidden that more than one VM to have the same mac

Info ! A Virtual Machine (VM) with this type of setup can not access from outside or be accessed only from a virtual machine from the vrack. To add enable outside access, you must either set up a VM which will have an upstream gateway or add it with a public ip.

We edit the file : /etc/sysconfig/network-scripts/ifcfg-eth0


We add /etc/resolv.conf


Next, enable your network interface :


To check your configuration:


To test your configuration, you can ping the gateway or another server in your virtual 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 OVH internal use 172.31.255.253 => IP reserved for OVH internal use 172.31.255.254 => IP Gateway of your virtual vrack The introduction of Virtual Machine (VM) within a virtual rack, you save the free virtual mac It is forbidden that more than one VM to have the same mac

Info ! A Virtual Machine (VM) with this type of setup can not access from outside or be accessed only from a virtual machine from the vrack. To add enable outside access, you must either set up a VM which will have an upstream gateway or add it with a public ip.

We edit the file : /etc/network/interfaces



Relaunch your network interface:



To check your configuration:



To test your configuration, you can ping the gateway or another server in your virtual rack 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 OVH internal use 172.31.255.253 => IP reserved for OVH internal use 172.31.255.254 => IP Gateway of your virtual vrack The introduction of Virtual Machine (VM) within a virtual rack, you save the free virtual mac It is forbidden that more than one VM to have the same mac

Info ! A Virtual Machine (VM) with this type of setup can not access from outside or be accessed only from a virtual machine from the vrack. To add enable outside access, you must either set up a VM which will have an upstream gateway or add it with a public ip.

We edit the file: /etc/conf.d/net


We add: /etc/resolv.conf


Restart your network interfaces :



To check your configuration :



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

IMPORTANT !! The activation email contains important information! It contains the IP that you do not have to configure, ie IP network and IP broadcast, the IP of the gateway, and netmask of your block! Please carefully read the information provided. The introduction of Virtual Machine (VM) within a virtual rack, you save the free virtual mac. It is forbidden that more than one VM has the same mac

We edit the file: /etc/sysconfig/network-scripts/ifcfg-eth0


We add /etc/resolv.conf


Next, install your network interface:



To check your configuration:


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

IMPORTANT !! The activation email contains important information! It contains the IP that you do not have to configure, ie IP network and IP broadcast, the IP of the gateway, and netmask of your block! Please carefully read the information provided. The introduction of Virtual Machine (VM) within a virtual rack, you save the free virtual mac. It is forbidden that more than one VM has the same mac

We edit the file: /etc/network/interfaces



Restart your network interfaces:



To check your configuration:



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

IMPORTANT !! The activation email contains important information! It contains the IP that you do not have to configure, ie IP network and IP broadcast, the IP of the gateway, and netmask of your block! Please carefully read the information provided. The introduction of Virtual Machine (VM) within a virtual rack, you save the free virtual mac. It is forbidden that more than one VM has the same mac

We edit the file: /etc/conf.d/net



Restart your network interface:



To check your configuration:



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





VMware ESXi enables a large number of network interface for VM management by ip failovers. Therefore, to alleviate the configuration and routing rules, we will add additional network interface to our VM.

Either add it when creating the machine, or editing a VM existing in selecting, click on Edit virtual machine settings, then click Add...

We choose Ethernet Adapter :



It retains an interface type e1000, and forget not to choose VLANXXXX:



You click on Finish:



Then you just post a custom virtual mac:

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 OVH internal use 172.31.255.253 => IP reserved for OVH internal use 172.31.255.254 => IP Gateway of your virtual vrack The activation email contains important information! It contains the IP that you do not have to configure, ie IP network and IP broadcast, the IP of the gateway, and netmask of your block! Please carefully read the information provided. The introduction of Virtual Machine (VM) within a virtual rack, you save the free virtual mac. It is forbidden that more than one VM has the same mac

Info ! For the remainder of this guide, you must add an additional network interface.

We edit the file that will have eth0 private ip:

/etc/sysconfig/network-scripts/ifcfg-eth0



We edit the file that will eth1 public ip:
/etc/sysconfig/network-scripts/ifcfg-eth1



It adds a rule of routing rules for what goes out through eth0 to eth0, and what comes out in through eth1 to eth1:

/etc/sysconfig/network-scripts/rule-eth0



/etc/sysconfig/network-scripts/route-eth0



It will replace below 178.33.8.64/28 by the block provided by OVH, and 178.33.8.78 the gateway of your block:

/etc/sysconfig/network-scripts/rule-eth1



/etc/sysconfig/network-scripts/route-eth1



We edit /etc/resolv.conf



Then mount the network interfaces:



To check your configuration:



To test your configuration, you can ping the gateway, the ip of a dns server or another virtual server on your rack that 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 OVH internal use 172.31.255.253 => IP reserved for OVH internal use 172.31.255.254 => IP Gateway of your virtual vrack The activation email contains important information! It contains the IP that you do not have to configure, ie IP network and IP broadcast, the IP of the gateway, and netmask of your block! Please carefully read the information provided. The introduction of Virtual Machine (VM) within a virtual rack, you save the free virtual mac. It is forbidden that more than one VM has the same mac

Info ! For the remainder of this guide, you must add an additional network interface.

We edit the file /etc/network/interfaces :



Restart your network interfaces:


To check your configuration:



To test your configuration, you can ping the gateway or another server of your virtual rack 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 OVH internal use 172.31.255.253 => IP reserved for OVH internal use 172.31.255.254 => IP Gateway of your virtual vrack The activation email contains important information! It contains the IP that you do not have to configure, ie IP network and IP broadcast, the IP of the gateway, and netmask of your block! Please carefully read the information provided. The introduction of Virtual Machine (VM) within a virtual rack, you save the free virtual mac. It is forbidden that more than one VM has the same mac

Info ! For the remainder of this guide, you must add an additional network interface.

We create the files necessary for starting the new network interface:




We edit the file /etc/conf.d/net



We edit /etc/resolv.conf


Relaunch your network interface:


To check your configuration:



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