To use the functions in this guide, you must have a Virtual Rack. You can click Viutal Rack to see the package and consult this guide: Configuration Vrack

You will need to have:

• Have a Virtual Bay (vrack)
• Have at least one dedicated server in the range EG, MG or HG (Ethernet 1Gb/s) with the professional use option.
• About to connect via SSH (for Linux servers)
• A RIPE IP block

Info ! You are not obliged to order a RIPE block through the section provided for this purpose in Part VRACK of your manager. You can move an existing RIPE block to your vrack. For more information, see the Order & RIPE IP Failover!

Virtual Rack brings together several virtual servers (whatever their number and physical location in our Datcenters) and connect to a virtual switch within the same 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 virtual rack "vrackXXXX" at home in "Dedicated Server"> "Infrastructure". Click
"RIPE block" and
"Order a RIPE block" and validate your order.


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

IMPORTANT !! This procedure will change the blocks split 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 with the block, or have your migration done (see below).

Log in to your manager V3 and select the server with the block in question.
Go to the section "Services" then "RIPE IP Failover", 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 RIPE block or having Virtual MAC, it will validate the warning.

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

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

• vlan and 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 and whatmask which will allow to see the number of available IPs

IMPORTANT !! Attention in the activation email or switching your block email has important information! It contains the IP that you do not have to configure, ie IP network and IP broadcast and netmask of your block! Please carefully observe the information provided. Before following this guide, you must have necessarily followed the vrack guide.

Install the packages mentioned above:

Edit the network configuration file /etc/network/interfaces and add the following to replace XXXX with the tag of your vrack (For a second it will therefore eth0.XXXX2 etc.)



Fpr the RIPE IPs to be accessible from the outside, it is necessary to configure a specific route. So add the following interfaces file :


Then restart your network interface:

To check your configuration:

To test your configuration, you can ping the gateway:

Or yet another virtual server on your rack that you have already performed the operations described above:


And finally ping from outside the vrack:

IMPORTANT !! Attention in the activation email or switching your block email has important information! It contains the IP that you do not have to configure, ie IP network and IP broadcast and netmask of your block! Please carefully observe the information provided. Before following this guide, you must have necessarily followed the vrack guide.

Install the packages mentioned above:

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

To get the mask of your network, run the command: whatmask 178.33.8.64/28
Configuration example IP 178.33.8.71 block 178.33.8.64/28:

For the RIPE IPs are accessible from the outside, it is necessary to configure a specific route. So add the following interfaces file:


Then restart your network interface:

To check your configuration:

To test your configuration, you can ping the gateway:

Or yet another virtual server on your rack that you have already performed the operations described above:


And finally ping from outside the vrack:

IMPORTANT !! Attention in the activation email or switching your block email has important information! It contains the IP that you do not have to configure, ie IP network and IP broadcast and netmask of your block! Please carefully observe the information provided. Before following this guide, you must have necessarily followed the vrack guide.

Install the packages mentioned above, is already installed netcat (nc):

To install fping:

To installer whatmask:

We copy the configuration file vrack and we add the number of our virtual interface:

We then edit the file:


For the RIPE IPs to be accessible from the outside, it is necessary to configure a specific route. To do this, create a file /etc/sysconfig/network-scripts/route-eth0.XXXX (replacing XXXX with the tag of your VLANs):

And create a file /etc/sysconfig/network-scripts/rule-eth0.XXXX (replace XXX for your vrack):


Next, install your network interface:

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:

root@ns20172 ~# ping 178.33.8.72
PING 178.33.8.71 (178.33.8.71) 56(84) bytes of data.
64 bytes from 178.33.8.71: icmp_seq=1 ttl=59 time=4.11 ms
64 bytes from 178.33.8.71: icmp_seq=2 ttl=59 time=4.07 ms
64 bytes from 178.33.8.71: icmp_seq=3 ttl=59 time=4.06 ms
^

Currently being edited