Grid5000:Network
Note | |
---|---|
This page provides an overview of Grid'5000 network infrastructure. Other useful pages:
|
Grid'5000 Network Infrastructure
Backbone Network
Grid'5000 backbone network infrastructure is provided by RENATER. RENATER is the French National Telecommunication Network for Technology, Education and Research. More information can be found on renater.fr.
The actual phase of the network is RENATER-5, the deployment has been completed by January 2009. Renater provides Grid'5000 a dedicated 10Gbit/s switching network (using dedicated lambdas on Renater network infrastructure) and every Grid'5000 router devices is connected to the closest Renater's Point of Presence.
From Grid'5000 point of view, this backbone network interconnecting its sites is a single layer-2 Ethernet network. To forward communication between two sites, IP routing is performed through the backbone network.
The IP addresses of sites' router in the backbone network are:
Network address:192.168.4.0/24
Sophia:192.168.4.12
Lyon:192.168.4.13
Nancy:192.168.4.14
Grenoble:192.168.4.15
Toulouse:192.168.4.16
Lille:192.168.4.18
Rennes:192.168.4.19
Luxembourg:192.168.4.21
Nantes:192.168.4.22
Strasbourg:192.168.4.23
Louvain:192.168.4.24
Grid'5000 sites networks
Grid'5000 sites provide access to a variety of network technologies (both Ethernet and high-performance networks such as InfiniBand). More information is available on the following pages:
The list of high performance networks is available on this page.
Network MTU
- A MTU (Maximum Transmission Unit) of up to 9000 is guaranteed to work on Grid'5000: within a site, between sites, and in a Kavlan
- Values of MTU above 9000 may work locally between nodes on the same site, but there is no guarantee. Contact Support if your experiment needs a MTU above 9000.
- The default MTU configured on nodes is 1500, but you can easily change the MTU during your experiments:
sudo-g5k ip link set INTERFACE mtu 9000
Address space for virtual machines
Grid'5000 has two different mechanisms to provide IP addresses to virtual machines: subnet reservation and KaVLAN.
- Subnet reservation provides a mean to allocate IP addresses in the production (= default) network. This provides a way to avoid conflicts between users, but does not provide isolation: all machines are still in the same L2 network. Subnet reservation is documented in the Virtualization on the standard environment tutorial, and on the Subnet reservation page.
- KaVLAN provides network isolation through dynamic switches and routers reconfiguration, for the duration of an experiment. Inside a KaVLAN network, users are free to allocate IP addresses as needed. However, some IP ranges are routed to/from the KaVLAN network. KaVLAN is documented in the Network reconfiguration tutorial (which provides an introduction to KaVLAN), in the Network isolation on Grid'5000 tutorial (which is a more advanced KaVLAN tutorial), and on the KaVLAN page.
Tables of available IP networks
Production network and subnet reservation
Here are the private IPv4 networks allocated to every site:
Here are the IPv6 networks allocated to every site (these are global scope networks, thus routable on the internet):
Virtual subnets configuration
Site | Block | Gateway | DHCP server |
10.128.0.0/14 |
10.131.255.254 | 10.131.255.253 | |
Grenoble | 10.132.0.0/14 |
10.135.255.254 | 10.135.255.253 |
Lille | 10.136.0.0/14 |
10.139.255.254 | 10.139.255.253 |
Lyon | 10.140.0.0/14 |
10.143.255.254 | 10.143.255.253 |
Nancy | 10.144.0.0/14 |
10.147.255.254 | 10.147.255.253 |
10.148.0.0/14 |
10.151.255.254 | 10.151.255.253 | |
10.152.0.0/14 |
10.155.255.254 | 10.155.255.253 | |
Rennes | 10.156.0.0/14 |
10.159.255.254 | 10.159.255.253 |
10.160.0.0/14 |
10.163.255.254 | 10.163.255.253 | |
Sophia | 10.164.0.0/14 |
10.167.255.254 | 10.167.255.253 |
Strasbourg |
10.168.0.0/14 |
10.171.255.254 | 10.171.255.253 |
Luxembourg | 10.172.0.0/14 |
10.175.255.254 | 10.175.255.253 |
Nantes | 10.176.0.0/14 |
10.179.255.254 | 10.179.255.253 |
Louvain | 10.180.0.0/14 |
10.181.255.254 | 10.181.255.253 |
VPN nets |
|
n/a | n/a |
10.252.0.0/14 |
10.255.255.254 | 10.255.255.253 |
KaVLAN
KaVLAN deployment status
Sites | Version | Status |
---|---|---|
Grenoble | 1.2.7-1 | |
Lille | 1.2.7-1 | |
Luxembourg | 1.2.7-1 | |
Lyon | 1.2.7-1 | |
Nancy | 1.2.7-1 | |
Nantes | 1.2.7-1 | |
Rennes | 1.2.7-1 | |
Sophia | 1.2.7-1 | |
Toulouse | 1.2.7-1 | |
Strasbourg | 1.2.7-1 | |
Louvain | 1.2.7-1 |
KaVLAN networks
- Local VLANs (non-routed)
Site | KAVLAN-1 | KAVLAN-2 | KAVLAN-3 |
---|---|---|---|
All | 192.168.192.0/20 |
192.168.208.0/20 |
192.168.224.0/20
|
- Routed VLANs
Site | KAVLAN-4 | KAVLAN-5 | KAVLAN-6 | KAVLAN-7 | KAVLAN-8 | KAVLAN-9 |
---|---|---|---|---|---|---|
10.0.0.0/18 |
10.0.64.0/18 |
10.0.128.0/18 |
10.0.192.0/18 |
10.1.0.0/18 |
10.1.64.0/18
| |
Grenoble | 10.4.0.0/18 |
10.4.64.0/18 |
10.4.128.0/18 |
10.4.192.0/18 |
10.5.0.0/18 |
10.5.64.0/18
|
Lille | 10.8.0.0/18 |
10.8.64.0/18 |
10.8.128.0/18 |
10.8.192.0/18 |
10.9.0.0/18 |
10.9.64.0/18
|
Lyon | 10.12.0.0/18 |
10.12.64.0/18 |
10.12.128.0/18 |
10.12.192.0/18 |
10.13.0.0/18 |
10.13.64.0/18
|
Nancy | 10.16.0.0/18 |
10.16.64.0/18 |
10.16.128.0/18 |
10.16.192.0/18 |
10.17.0.0/18 |
10.17.64.0/18
|
10.20.0.0/18 |
10.20.64.0/18 |
10.20.128.0/18 |
10.20.192.0/18 |
10.21.0.0/18 |
10.21.64.0/18
| |
Rennes | 10.24.0.0/18 |
10.24.64.0/18 |
10.24.128.0/18 |
10.24.192.0/18 |
10.25.0.0/18 |
10.25.64.0/18
|
Toulouse | 10.28.0.0/18 |
10.28.64.0/18 |
10.28.128.0/18 |
10.28.192.0/18 |
10.29.0.0/18 |
10.29.64.0/18
|
Sophia | 10.32.0.0/18 |
10.32.64.0/18 |
10.32.128.0/18 |
10.32.192.0/18 |
10.33.0.0/18 |
10.33.64.0/18
|
Strasbourg |
10.36.0.0/18 |
10.36.64.0/18 |
10.36.128.0/18 |
10.36.192.0/18 |
10.37.0.0/18 |
10.37.64.0/18
|
Luxembourg | 10.40.0.0/18 |
10.40.64.0/18 |
10.40.128.0/18 |
10.40.192.0/18 |
10.41.0.0/18 |
10.41.64.0/18
|
Nantes | 10.44.0.0/18 |
10.44.64.0/18 |
10.44.128.0/18 |
10.44.192.0/18 |
10.45.0.0/18 |
10.45.64.0/18
|
Louvain | 10.48.0.0/18 |
10.48.64.0/18 |
10.48.128.0/18 |
10.48.192.0/18 |
10.49.0.0/18 |
10.49.64.0/18
|
- Global VLANs
Site | Global Vlan | Subnet | Router IP |
---|---|---|---|
KAVLAN-10 |
10.3.192.0/18 |
10.3.255.254
| |
Grenoble | KAVLAN-11 |
10.7.192.0/18 |
10.7.255.254
|
Lille | KAVLAN-12 |
10.11.192.0/18 |
10.11.255.254
|
Lyon | KAVLAN-13 |
10.15.192.0/18 |
10.15.255.254
|
Nancy | KAVLAN-14 |
10.19.192.0/18 |
10.19.255.254
|
KAVLAN-15 |
10.23.192.0/18 |
10.23.255.254
| |
Rennes | KAVLAN-16 |
10.27.192.0/18 |
10.27.255.254
|
Toulouse | KAVLAN-17 |
10.31.192.0/18 |
10.31.255.254
|
Sophia | KAVLAN-18 |
10.35.192.0/18 |
10.35.255.254
|
Strasbourg |
KAVLAN-19 |
10.39.192.0/18 |
10.39.255.254
|
Luxembourg | KAVLAN-20 |
10.43.192.0/18 |
10.43.255.254
|
Nantes | KAVLAN-21 |
10.47.192.0/18 |
10.47.255.254
|
Louvain | KAVLAN-22 |
10.51.192.0/18 |
10.51.255.254
|
- IP subnet assignments for the sites within a global VLANs
A global VLAN is a /18 subnet (16382 IP addresses). It is split so that every site gets one /23 (510 ip) in the global VLAN address space.
Example for the global VLAN of Lille, KAVLAN-12, whose address space is 10.11.192.0/18:
Bordeaux:10.11.192.1
→10.11.193.254
- Grenoble:
10.11.194.1
→10.11.195.254
- Lille:
10.11.196.1
→10.11.197.254
- Lyon:
10.11.198.1
→10.11.199.254
- Nancy:
10.11.200.1
→10.11.201.254
Orsay:10.11.202.1
→10.11.203.254
- Rennes:
10.11.204.1
→10.11.205.254
- Toulouse:
10.11.206.1
→10.11.207.254
- Sophia:
10.11.208.1
→10.11.209.254
- Strasbourg
Reims:10.11.210.1
→10.11.211.254
- Luxembourg:
10.11.212.1
→10.11.213.254
- Nantes:
10.11.214.1
→10.11.215.254
KaVLAN-NG networks
Large IPv4 / IPv6 networks are allocated for Kavlan-NG, which automatically takes care of handling address allocation and routing inside them:
- IPv4:
10.240.0.0/12
(4096 simultaneous possible/24
kavlans) - IPv6:
2001:660:4406:e000::/52
(4096 simultaneous possible kavlans)