Virtual Rack 1.0

Deprecated since version 1.5: Use vRack 1.5 instead.

Warning

Since vRack 1.5 is available, this service is obsolete. However, you may need to use this version of the vRack if you want to put a Cisco ASA or Cisco ACE in front of your vRack 1.5.


Introduction

To use the functions explained in this guide you must have a Virtual Rack.

Therefore, you must:

  • Have a Virtual Rack (vRack)
  • Have an OVH Infrastructure dedicated servers (although it is preferable to have at least two Infrastructure server to fully use the vRack functionnality).
  • Be able to connect via SSH (for Linux servers)

Important

For 2013 server range and older, you need to have servers with extended features in order to be able to order the vRack.

Note

Not available for SP server from the 2013 series and not advised on older series because the servers only have one private connection. So the support and maintenance are more tricky.

Variables

In this guide we will use the following variable, you have to change it for your own information in the examples.

VRACK_TAG:The tag (VLAN) of your vRack

General

The Virtual Rack is compatible with all OVH Infrastrure server range.

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

Order a vRack 1.0

Please contact the support if you need to order a vRack 1.0. Since this service is deprecated since vRack 1.5, the only way to acquire a vRack 1.0 is through manual order.

Note

While ordering the vRack 1.0, you will also need an IP Block in order to route it through your vRack 1.5. This IP block will be used to link the vRack 1.0 to the vRack 1.5 as well as the service you need to be routed through vRack 1.5 (ex: Cisco ASA Firewall, Cisco ACE Loadbalancer)

VLAN Configuration

Linux Basic

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 diagnose network interfaces
  • netcat: For testing transfers between two servers for example
  • fping: Will be useful to ping a range of IPs
  • netmask: A tool to calculate the number of available IPs within a given netmask

Note

Throughout this guide, eth0.VRACK_TAG corresponds to your vRack tag . For example, for the vRack 2009 eth0.VRACK_TAG -> 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).

Debian & Ubuntu

Install the packages mentioned above:

apt-get install vlan netcat fping tcpdump netmask

Edit the network configuration file /etc/network/interfaces and add this:

auto eth0.VRACK_TAG
iface eth0.VRACK_TAG inet static
    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.VRACK_TAG ; true

Then restart your network interface:

/etc/init.d/networking restart

To check your configuration:

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

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
testvrack2:~#
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

Install the packages mentioned above:

emerge install vlan netcat fping tcpdump whatmask

Edit the network configuration file /etc/conf.d/net and add this:

# IMPORTANT: replace every "VRACK_TAG" with the tag of your vRack
vlans_eth0="VRACK_TAG"

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

config_vlanVRACK_TAG=( "172.16.0.1 netmask 255.0.0.0" )

Then restart your network interface:

/etc/init.d/net.eth0 restart

To check your configuration:

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)
Memoire: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)
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 rack where you have already performed the operations described above:

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=63 time=9.46 ms
64 bytes from 172.31.255.254: icmp_seq=2 ttl=63 time=0.219 ms
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

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

yum install vconfig tcpdump whatmask

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

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

We then edit the file:

DEVICE=eth0.VRACK_TAG
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.VRACK_TAG

To check your configuration:

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)
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 Rack where you have already performed the operations described above:

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