Search


print PDF
Using a RIPE IP block in a Virtual Rack

Requirements


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!


General


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

Order a RIPE Block


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.

Move an existing RIPE Block


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.

RIPE VRACK Configuration

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


Debian & Ubuntu


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:
testvrack1:~# apt-get install vlan netcat fping tcpdump netmask

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.XXXX:1, for a third eth0.XXXX:2 etc.)

auto eth0.XXXX:0 # replace XXXX with your virtual rack tag
iface eth0.XXXX:0 inet static # replace XXXX with your virtual rack tag
address 178.33.8.72 # put the ip FailOver? here? RIPE you want to assign to this server
network 178.33.8.64 # here put the first ip of your RIPE block
broadcast 178.33.8.79 # here put the last ip of your RIPE block
netmask 255.255.255.240 # to get the mask of your network, run the command: netmask -s your_block (example : 178.33.8.64/28)


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

up /sbin/ip route add default via 178.33.8.78 dev eth0.2009 table 125 # 178.33.8.78 = gateway.du.bloc.ripe # vlanXXXX # table number.of.your.choice
up /sbin/ip rule add from 178.33.8.64/28 table 125 # votre.bloc.ripe.vrack # table number same as above
post-down /sbin/ip route del default via 1178.33.8.78 dev eth0.2009 table 125 # table number same as above with "del" instead of "add"
post-down /sbin/ip rule del from 178.33.8.64/28 table 125 # table number same as above with "del" instead of "add"


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:10.0.0.1 Bcast:10.255.255.255 Masque:255.0.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)

eth0.2009:0 Link encap:Ethernet HWaddr 00:1c:c0:b9:98:f3
inet adr:178.33.8.71 Bcast:178.33.8.79 Masque:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

lo Link encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.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 Indic Metric Ref Use Iface
178.33.8.64 0.0.0.0 255.255.255.240 U 0 0 0 eth0.2009
94.23.196.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth0.2009
0.0.0.0 10.255.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:
testvrack1:~# ping 178.33.8.79
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.255.255.254: icmp_seq=1 ttl=63 time=9.46 ms
64 bytes from 10.255.255.254: icmp_seq=2 ttl=63 time=0.219 ms

Or yet another virtual server on your rack that you have already performed the operations described above:
testvrack1:~# ping 178.33.8.72
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_seq=1 ttl=63 time=8.83 ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=63 time=0.220 ms


And finally ping from outside the vrack:
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


Gentoo


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:
testvrack1:~# emerge vconfig netcat fping tcpdump whatmask

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

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

config_vlanXXXX=( "10.0.0.1 netmask 255.0.0.0" # replace XXXX for the tag in your vrack
"IP.FAIL.OVER.RIPE netmask MASK.OF.YOUR?NETWORK brd IP.OF.BROADCAST.RIPE")

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:
vlans_eth0="2009"

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

config_vlan2009=( "10.0.0.1 netmask 255.0.0.0"
"178.33.8.71 netmask 255.255.255.240 brd 178.33.8.79")

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

postup()
{
/sbin/ip route add default via 178.33.8.78 dev vlan2009 table 125 # 178.33.8.78 = gateway.du.bloc.ripe # vlanXXXX # table number.of.your.choice # replace XXXX for the tag of your vrack
/sbin/ip rule add from 178.33.8.64/28 table 125 # your.block.ripe.vrack # table the.same.as.above
}

postdown()
{
/sbin/ip route del default via 178.33.8.78 dev vlan2009 table 125 # same line as above "up" but with "del"
/sbin/ip rule del from 178.33.8.64/28 table 125 # lsame line as above "up" but with "del"
}


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

To check your configuration:
testvrack1 ~ # ip addr show
1: lo: mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:1c:c0:b9:98:f3 brd ff:ff:ff:ff:ff:ff
inet 94.23.196.195/24 brd 94.23.196.255 scope global eth0
inet 213.186.37.47/32 brd 213.186.37.47 scope global eth0
3: dummy0: mtu 1500 qdisc noop state DOWN
link/ether 66:cf:9f:b3:f7:69 brd ff:ff:ff:ff:ff:ff
4: tunl0: mtu 1480 qdisc noop state DOWN
link/ipip 0.0.0.0 brd 0.0.0.0
5: gre0: mtu 1476 qdisc noop state DOWN
link/gre 0.0.0.0 brd 0.0.0.0
11: vlan2009@eth0: mtu 1500 qdisc noqueue state UP
link/ether 00:1c:c0:b9:98:f3 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.1/8 brd 10.255.255.255 scope global vlan2009
inet 178.33.8.71/28 brd 178.33.8.79 scope global vlan2009


testvrack1 ~ # route -n
IP Routing Tables
Destination Gateway Genmask Indic Metric Ref Use Iface
178.33.8.64 0.0.0.0 255.255.255.240 U 0 0 0 vlan2009
94.23.196.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 vlan2009
127.0.0.0 0.0.0.0 255.0.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:
testvrack1:~# ping 178.33.8.79
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.255.255.254: icmp_seq=1 ttl=63 time=9.46 ms
64 bytes from 10.255.255.254: icmp_seq=2 ttl=63 time=0.219 ms

Or yet another virtual server on your rack that you have already performed the operations described above:
testvrack1:~# ping 178.33.8.72
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_seq=1 ttl=63 time=8.83 ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=63 time=0.220 ms


And finally ping from outside the vrack:
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


CentOS & RedHat? & Fedora


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):
testvrack2:~# 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 installer whatmask:
Waiting compiled rpm

We copy the configuration file vrack and we add the number of our virtual interface:
cp /etc/sysconfig/network-scripts/ifcfg-eth0.XXXX /etc/sysconfig/network-scripts/ifcfg-eth0.XXXX:0

We then edit the file:
DEVICE=eth0.XXXX:0 # Put in place of XXX tag your vlan
VLAN=yes
BOOTPROTO=static
IPADDR=178.33.8.72 # Put here RIPE IP FailOver? you want to assign to this server
NETMASK=255.255.255.240 # Put here the first IP of your RIPE block
ONBOOT=yes
BROADCAST=178.33.8.79 # Put here the last IP your RIPE block


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):
default via 178.33.8.78 dev eth0.2009 table 125 # put here the gateeway of your RIPE block eth0.XXXX (with the tag of your vrack) and the table of your choice

And create a file /etc/sysconfig/network-scripts/rule-eth0.XXXX (replace XXX for your vrack):
from 178.33.8.64/28 table 125 # put your RIPE IP block and the table chosen in the file


Next, install your network interface:
ifup eth0.2009:0

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:10.0.0.2 Bcast:10.255.255.255 Mask:255.0.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)

eth0.2009:0 Link encap:Ethernet HWaddr 00:1C:C0:BA:D4:54
inet addr:178.33.8.72 Bcast:178.33.8.79 Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.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
178.33.8.64 0.0.0.0 255.255.255.240 U 0 0 0 eth0.2009
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
10.0.0.0 0.0.0.0 255.0.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 rack where you have already performed the operations described above:
root@testvrack2 ~# ping 178.33.8.71
PING 10.255.255.254 (10.255.255.254) 56(84) bytes of data.
64 bytes from 10.255.255.254: icmp_seq=1 ttl=255 time=8.36 ms
64 bytes from 10.255.255.254: icmp_seq=2 ttl=255 time=0.407 ms
64 bytes from 10.255.255.254: icmp_seq=3 ttl=255 time=0.388 ms

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

And finally, ping from outside the vrack:
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
^

Procedure of migration without downtime

Currently being edited