Merge pull request #7646 from ovh/sa-ipv6-vrack-guides

IPv6 in vRack - Minor edits + French translation

Author: Y0Coss

pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.de-de.md

@@ -1,7 +1,7 @@
 ---
 title: Configuring an IPv6 block in a vRack (EN)
 excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack
-updated: 2024-07-18
+updated: 2025-03-17
 ---
 
 <style>
@@ -18,17 +18,12 @@ details[open]>summary::before {
 }
 </style>
 
-> [!warning]
-> Usage of this feature is currently in Beta phase.
-> This guide may be incomplete and will be extended during this Beta phase. Our team remains available on our dedicated Discord Channel, do not hesitate to join and reach us: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our Network services.
-
 ## Objective
 
 The vRack network serves as a global private network bridging various OVHcloud products, enabling the creation of sophisticated network solutions. Beyond facilitating private connections, it also supports routing public IP addresses.
 
 **This guide focuses on Additional IPv6 address block configuration within a vRack network.**
 
-
 ## Introduction
 
 IPv6 revolutionizes networking within OVHcloud's vRack by addressing IPv4's limitations and introducing features for the modern internet. Its rollout is a direct response to the need for more extensive, secure, and sophisticated internet architectures. Here are the key benefits of integrating IPv6 with vRack:
@@ -44,14 +39,14 @@ By leveraging IPv6 within vRack, OVHcloud users can enjoy a more secure, efficie
 
 ## Requirements
 
-- A [vRack](https://www.ovhcloud.com/de/network/vrack/){.external} service activated in your account
-- A [vRack compatible server](https://www.ovhcloud.com/de/network/vrack/){.external} attached to your vRack network
+- A [vRack](/links/network/vrack) service activated in your account
+- A [vRack compatible server](/links/network/vrack) attached to your vRack network
 - Access to the [OVHcloud Control Panel](/links/manager)
 
 > [!warning]
-> This feature might be unavailable or limited on servers of the [**Eco** product line](https://eco.ovhcloud.com/en-gb/about/).
+> This feature might be unavailable or limited on servers of the [**Eco** product line](/links/bare-metal/eco-about).
 >
-> Please visit our [comparison page](https://eco.ovhcloud.com/en-gb/compare/) for more information.
+> Please visit our [comparison page](/links/bare-metal/eco-compare) for more information.
 
 ## Instructions
 
@@ -83,15 +78,15 @@ The example above shows two hosts with their vRack-side interfaces configured wi
 
 Go to `Network`{.action} and click the `vRack private network`{.action} section. Then select the vRack you want to manage:
 
-![vrack management](images/700.png){.thumbnail}
+![vRack management](images/700.png){.thumbnail}
 
 On the left side, the possible options (eligible services to be configured) are listed.
 
 On the right you see what is already configured with your vRack.
 
 Select your new Additional IPv6 and add it to your vRack.
 
-![vrack selection](images/701.png){.thumbnail}
+![vRack selection](images/701.png){.thumbnail}
 
 You now have your new Additional IPv6 added to your vRack.
 
@@ -155,7 +150,7 @@ Let's check exactly which subnet is bridged:
 
 As in the example below:
 
-![GET subrange bridged into your vrack](images/20240418-05.png){.thumbnail}
+![GET subrange bridged into your vRack](images/20240418-05.png){.thumbnail}
 
 To get more details, use this call:
 
@@ -166,7 +161,7 @@ To get more details, use this call:
 
 As in the example below:
 
-![GET subrange bridged into your vrack](images/20240418-06.png){.thumbnail}
+![GET subrange bridged into your vRack](images/20240418-06.png){.thumbnail}
 
 Notice that IP autoconfiguration (SLAAC) is turned off by default.
 
@@ -193,7 +188,7 @@ Don't forget to configure SLAAC on your host machine.
 
 In a basic configuration, you may want to setup an IP address and routing manually. This is also the suggested way when your machine acts as a router (see the [configuring routed subnet](#routedmode) section) and has ipv6.forwarding mode enabled.
 
-First, let's add an IP address on the vrack interface (in our example "eth1"):
+First, let's add an IP address on the vRack interface (in our example "eth1"):
 
 ```bash
 $ sudo ip address add 2001:41d0:abcd:ef00::2/64 dev eth1
@@ -224,15 +219,15 @@ To use automatic configuration, please ensure you have configured your interface
 
 First, let's allow our host to accept Router Advertisements (for autoconfiguration) on the vRack interface (in our example "eth1"):
 
-``` bash
+```bash
 $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1
 ```
 
 Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to <a href="#host-side-configuration">[Automatic IP configuration for routed subnet](#host-side) for more details.
 
 Then, simply bring up the interface:
 
-``` bash
+```bash
 $ sudo ip link set up dev eth1
 $ ip -6 addr list dev eth1
 4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
@@ -250,7 +245,7 @@ After a moment (the configuration must propagate), specific IPv6 address (with t
 
 The most basic test is to ping a local IP address on a host:
 
-``` bash
+```bash
 debian@host:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166
 PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c166) 56 data bytes
 64 bytes from 2001:41d0:900:2100:fe34:97ff:feb0:c166: icmp_seq=1 ttl=64 time=0.043 ms
@@ -263,7 +258,7 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1
 
 Next, let's verify the connectivity from remote:
 
-``` bash
+```bash
 ubuntu@remote-test:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166
 PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c166) 56 data bytes
 64 bytes from 2001:41d0:900:2100:fe34:97ff:feb0:c166: icmp_seq=1 ttl=55 time=7.23 ms
@@ -290,7 +285,7 @@ For routed subnet definition any prefix size can be used between /57 and /64.
 
 After adding Additional IP to your vRack you can manage routed subnet by clicking `Add subnet`{.action} button.
 
-![vrack select](images/600.png){.thumbnail}
+![vRack select](images/600.png){.thumbnail}
 
 To create a routed subnet, we must first define:
 
@@ -418,7 +413,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes
 
 Check the route to our /60 subnet on a host:
 
-``` bash
+```bash
 debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1
 2001:41d0:abcd:ef10::1 from :: via fd00::2 dev veth1a src fd00::1 metric 1024 pref medium
 ```
@@ -525,7 +520,6 @@ Please note that in such setups (with Additional IPv6 from more than single regi
 
 - **No SLAAC support in multi-location setups:** When there is more than one location acting in routing public IP traffic (both IPv4 and IPv6) into the same vRack, Stateless Address Autoconfiguration (SLAAC) **should not be used**. As an example of such situation, let's consider existing hosts using IPv4 addresses. Such hosts are becoming reconfigured automatically by SLAAC with IPv6 gateway set up from other region. Together with IPv6 prioritization over IPv4 by some Operating Systems this situation can lead to suboptimal routing or even total loss of connectivity for such hosts.
 
-
 ## Known Limitations
 
 Understanding the constraints of using **Additional IPv6** within the **vRack** environment is crucial for effective network planning. Here are the key limitations to consider:
@@ -537,8 +531,8 @@ Understanding the constraints of using **Additional IPv6** within the **vRack**
 - **Public bandwidth cap**: Outbound traffic from OVHcloud to the internet is capped at 5Gbps per region location.
 - **IPv6 block allocation limits**: Single Additional IPv6 block per vRack in a region location. Maximum of 3 blocks (/56) per region location.
 - **Mobility of Additional IPv6 blocks**: Due to the hierarchical design of the IPv6 address space, Additional IPv6 blocks are region-specific. This means blocks cannot be transferred between regions, although they can be reassigned within any vRack-connected backend.
-- **No direct VLAN 802.1Q support in vRack by Additional IPv6**: Configuration can only be done with native vlan of your vRack network. For packet forwarding inside specific vlan (of a vRack) a dedicated host on customer side will be needed.
-- **APAC, TOR and 3AZ regions are not supported for the moment.**
+- **No direct VLAN 802.1Q support in vRack by Additional IPv6**: Configuration can only be done with native VLAN of your vRack network. For packet forwarding inside specific VLAN (of a vRack) a dedicated host on customer side will be needed.
+- **At the moment, routing Additional IPv6 into vRack is not supported in APAC (Asia-Pacific) regions.**
 
 ## Go further
 

pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-asia.md

@@ -1,7 +1,7 @@
 ---
 title: Configuring an IPv6 block in a vRack
 excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack
-updated: 2024-07-18
+updated: 2025-03-17
 ---
 
 <style>
@@ -18,17 +18,12 @@ details[open]>summary::before {
 }
 </style>
 
-> [!warning]
-> Usage of this feature is currently in Beta phase.
-> This guide may be incomplete and will be extended during this Beta phase. Our team remains available on our dedicated Discord Channel, do not hesitate to join and reach us: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our Network services.
-
 ## Objective
 
 The vRack network serves as a global private network bridging various OVHcloud products, enabling the creation of sophisticated network solutions. Beyond facilitating private connections, it also supports routing public IP addresses.
 
 **This guide focuses on Additional IPv6 address block configuration within a vRack network.**
 
-
 ## Introduction
 
 IPv6 revolutionizes networking within OVHcloud's vRack by addressing IPv4's limitations and introducing features for the modern internet. Its rollout is a direct response to the need for more extensive, secure, and sophisticated internet architectures. Here are the key benefits of integrating IPv6 with vRack:
@@ -44,14 +39,14 @@ By leveraging IPv6 within vRack, OVHcloud users can enjoy a more secure, efficie
 
 ## Requirements
 
-- A [vRack](/links/network/vrack){.external} service activated in your account
-- A [vRack compatible server](/links/network/vrack){.external} attached to your vRack network
+- A [vRack](/links/network/vrack) service activated in your account
+- A [vRack compatible server](/links/network/vrack) attached to your vRack network
 - Access to the [OVHcloud Control Panel](/links/manager)
 
 > [!warning]
-> This feature might be unavailable or limited on servers of the [**Eco** product line](https://eco.ovhcloud.com/en-gb/about/).
+> This feature might be unavailable or limited on servers of the [**Eco** product line](/links/bare-metal/eco-about).
 >
-> Please visit our [comparison page](https://eco.ovhcloud.com/en-gb/compare/) for more information.
+> Please visit our [comparison page](/links/bare-metal/eco-compare) for more information.
 
 ## Instructions
 
@@ -61,7 +56,7 @@ While requesting a new Additional IPv6 block, it's important to note that the al
 
 /// details | Request a new Additional IPv6 block
 
-You can order your new additional IPv6 block [here](https://www.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip).
+You can order your new additional IPv6 block [here](https://ca.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip).
 
 ![configuration page](images/500.png){.thumbnail}
 
@@ -83,15 +78,15 @@ The example above shows two hosts with their vRack-side interfaces configured wi
 
 Go to `Network`{.action} and click the `vRack private network`{.action} section. Then select the vRack you want to manage:
 
-![vrack management](images/700.png){.thumbnail}
+![vRack management](images/700.png){.thumbnail}
 
 On the left side, the possible options (eligible services to be configured) are listed.
 
 On the right you see what is already configured with your vRack.
 
 Select your new Additional IPv6 and add it to your vRack.
 
-![vrack selection](images/701.png){.thumbnail}
+![vRack selection](images/701.png){.thumbnail}
 
 You now have your new Additional IPv6 added to your vRack.
 
@@ -155,7 +150,7 @@ Let's check exactly which subnet is bridged:
 
 As in the example below:
 
-![GET subrange bridged into your vrack](images/20240418-05.png){.thumbnail}
+![GET subrange bridged into your vRack](images/20240418-05.png){.thumbnail}
 
 To get more details, use this call:
 
@@ -166,7 +161,7 @@ To get more details, use this call:
 
 As in the example below:
 
-![GET subrange bridged into your vrack](images/20240418-06.png){.thumbnail}
+![GET subrange bridged into your vRack](images/20240418-06.png){.thumbnail}
 
 Notice that IP autoconfiguration (SLAAC) is turned off by default.
 
@@ -193,7 +188,7 @@ Don't forget to configure SLAAC on your host machine.
 
 In a basic configuration, you may want to setup an IP address and routing manually. This is also the suggested way when your machine acts as a router (see the [configuring routed subnet](#routedmode) section) and has ipv6.forwarding mode enabled.
 
-First, let's add an IP address on the vrack interface (in our example "eth1"):
+First, let's add an IP address on the vRack interface (in our example "eth1"):
 
 ```bash
 $ sudo ip address add 2001:41d0:abcd:ef00::2/64 dev eth1
@@ -224,15 +219,15 @@ To use automatic configuration, please ensure you have configured your interface
 
 First, let's allow our host to accept Router Advertisements (for autoconfiguration) on the vRack interface (in our example "eth1"):
 
-``` bash
+```bash
 $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1
 ```
 
 Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to <a href="#host-side-configuration">[Automatic IP configuration for routed subnet](#host-side) for more details.
 
 Then, simply bring up the interface:
 
-``` bash
+```bash
 $ sudo ip link set up dev eth1
 $ ip -6 addr list dev eth1
 4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
@@ -250,7 +245,7 @@ After a moment (the configuration must propagate), specific IPv6 address (with t
 
 The most basic test is to ping a local IP address on a host:
 
-``` bash
+```bash
 debian@host:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166
 PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c166) 56 data bytes
 64 bytes from 2001:41d0:900:2100:fe34:97ff:feb0:c166: icmp_seq=1 ttl=64 time=0.043 ms
@@ -263,7 +258,7 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1
 
 Next, let's verify the connectivity from remote:
 
-``` bash
+```bash
 ubuntu@remote-test:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166
 PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c166) 56 data bytes
 64 bytes from 2001:41d0:900:2100:fe34:97ff:feb0:c166: icmp_seq=1 ttl=55 time=7.23 ms
@@ -290,7 +285,7 @@ For routed subnet definition any prefix size can be used between /57 and /64.
 
 After adding Additional IP to your vRack you can manage routed subnet by clicking `Add subnet`{.action} button.
 
-![vrack select](images/600.png){.thumbnail}
+![vRack select](images/600.png){.thumbnail}
 
 To create a routed subnet, we must first define:
 
@@ -418,7 +413,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes
 
 Check the route to our /60 subnet on a host:
 
-``` bash
+```bash
 debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1
 2001:41d0:abcd:ef10::1 from :: via fd00::2 dev veth1a src fd00::1 metric 1024 pref medium
 ```
@@ -525,7 +520,6 @@ Please note that in such setups (with Additional IPv6 from more than single regi
 
 - **No SLAAC support in multi-location setups:** When there is more than one location acting in routing public IP traffic (both IPv4 and IPv6) into the same vRack, Stateless Address Autoconfiguration (SLAAC) **should not be used**. As an example of such situation, let's consider existing hosts using IPv4 addresses. Such hosts are becoming reconfigured automatically by SLAAC with IPv6 gateway set up from other region. Together with IPv6 prioritization over IPv4 by some Operating Systems this situation can lead to suboptimal routing or even total loss of connectivity for such hosts.
 
-
 ## Known Limitations
 
 Understanding the constraints of using **Additional IPv6** within the **vRack** environment is crucial for effective network planning. Here are the key limitations to consider:
@@ -537,8 +531,8 @@ Understanding the constraints of using **Additional IPv6** within the **vRack**
 - **Public bandwidth cap**: Outbound traffic from OVHcloud to the internet is capped at 5Gbps per region location.
 - **IPv6 block allocation limits**: Single Additional IPv6 block per vRack in a region location. Maximum of 3 blocks (/56) per region location.
 - **Mobility of Additional IPv6 blocks**: Due to the hierarchical design of the IPv6 address space, Additional IPv6 blocks are region-specific. This means blocks cannot be transferred between regions, although they can be reassigned within any vRack-connected backend.
-- **No direct VLAN 802.1Q support in vRack by Additional IPv6**: Configuration can only be done with native vlan of your vRack network. For packet forwarding inside specific vlan (of a vRack) a dedicated host on customer side will be needed.
-- **APAC, TOR and 3AZ regions are not supported for the moment.**
+- **No direct VLAN 802.1Q support in vRack by Additional IPv6**: Configuration can only be done with native VLAN of your vRack network. For packet forwarding inside specific VLAN (of a vRack) a dedicated host on customer side will be needed.
+- **At the moment, routing Additional IPv6 into vRack is not supported in APAC (Asia-Pacific) regions.**
 
 ## Go further