fix(ins): crosslink routed ip docs (scaleway#4158)

* fix(ins): crosslink routed ip docs

* fix(ins): wording

* Update faq/instances.mdx

Co-authored-by: Rowena Jones <[email protected]>

* Apply suggestions from code review

Co-authored-by: Jessica <[email protected]>

* Apply suggestions from code review

Co-authored-by: Jessica <[email protected]>

---------

Co-authored-by: Rowena Jones <[email protected]>
Co-authored-by: Jessica <[email protected]>

Author: 3 people

compute/instances/how-to/migrate-routed-ips.mdx

@@ -24,6 +24,7 @@ In addition to the benefits explained above, routed IPs allow precise control ov
   * Ensure no static network configuration is in use for your public network interface (usually `ens2` or `eth0`)
   * Ensure that you are not using the internal private IP of the Instance for internal communications. Instead, [attach your Instances to a VPC](/network/vpc/how-to/attach-resources-to-pn/).
   * You must update the `scaleway-ecosystem` and `cloud-init` packages before starting transition.
+  * Before proceeding with the migration, please review the [FAQ on IP autoconfiguration limitations](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature) and the [guide to fix unreachable Ubuntu Focal Instances with multiple public IPs](/compute/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips/). These resources provide important information to ensure a seamless migration process.
 </Message>
 
 <Macro id="requirements" />

compute/instances/troubleshooting/fix-broken-vpn-when-switching-openvpn-vm-to-routed-ip.mdx

@@ -19,6 +19,11 @@ This can now be fixed by installing a new version of the OpenVPN scripts, which
 
 You can also avoid this situation altogether by installing the package prior to moving to a routed IP.
 
+<Message type="note">
+  This guide addresses specific issues related to OpenVPN Instances. For general information on routed IPs and migration procedures, refer to our [main migration guide](/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
+</Message>
+
+
 ## Your Instance has not been rebooted
 
 1. Add Scaleway's stable PPA

compute/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster.mdx

@@ -15,6 +15,10 @@ categories:
 
 On older Debian Buster images, the installed custom version of `cloud-init` may interfere with IPv6 connectivity when the instance transitions to using routed IP. To avoid this, you should install a newer version of `cloud-init` before the migration to routed IP. This procedure also recovers connectivity for an instance already using routed IP.
 
+<Message type="note">
+  This guide addresses specific issues related to older Debian Buster Instances transitioned to routed IP. For general information on routed IPs and migration procedures, refer to our [main migration guide](/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
+</Message>
+
 1. Install the new `debian-stable` PPA.
    The URL of the PPA may be configured to use the `noble` series. Replace `noble` with `bionic` in the URL.
    ```bash

compute/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx

@@ -19,6 +19,10 @@ The version of `systemd-networkd` used in Ubuntu Focal does not support the defi
 
 A modified `cloud-init` package named `cloud-init_24.2-0ubuntu1~20.04.1+scaleway` has been added to Scaleway's stable PPA to work around this situation.
 
+<Message type="note">
+  This guide addresses specific issues related to Ubuntu Focal Instances with multiple public IPs. For general information on routed IPs and migration procedures, refer to our [main migration guide](/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
+</Message>
+
 ## Your Instance has not been rebooted
 
 1. Add Scaleway's stable PPA

compute/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance.mdx

@@ -26,6 +26,10 @@ The affected O/S distributions are:
   CentOS 7.9 is not concerned by this issue as it does not support routed IP.
 </Message>
 
+<Message type="note">
+  This guide addresses specific issues related to RHEL-based Instances after transitioning to routed IP. For general information on routed IPs and migration procedures, refer to our [main migration guide](/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
+</Message>
+
 ## Your Instance has not been migrated to routed IP yet
 
 Connect to your Instance and execute the following command as `root` user to add the required NetworkManager option:

faq/instances.mdx

@@ -322,4 +322,5 @@ Yes, they can communicate with each other using their public IPs.
 ### Are there any limitations on IP autoconfiguration with the routed IP feature?
 
 Currently, additional routed IPv6 addresses do not autoconfigure on CentOS 7, 8, 9, Alma 8, 9, Rocky 8, 9 after migration.
-Additionally, both additional routed IPv4 and IPv6 addresses are not autoconfigured post-migration on Ubuntu 20.04 focal. However, the primary IPv6 continues to be configured via SLAAC. These limitations are currently being addressed.
+Additional routed IPv4 and IPv6 addresses are not autoconfigured post-migration on Ubuntu 20.04 Focal. However, the primary IPv6 continues to be configured via SLAAC. These limitations are currently being addressed.
+For detailed migration steps, refer to our [migration guide](/compute/instances/how-to/migrate-routed-ips/). If you encounter connectivity issues with Ubuntu Focal Instances having multiple public IPs, consult our [troubleshooting guide](/compute/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips/).