diff --git a/.gitignore b/.gitignore index 2d3a1a8b614..8bf5cf82f28 100644 --- a/.gitignore +++ b/.gitignore @@ -14,4 +14,4 @@ llm-config/ cp-extraction CLAUDE.md CLAUDE.local.md -.mcp.json \ No newline at end of file +.mcp.json diff --git a/pages/index.md b/pages/index.md index 9bfc4abe47a..75f14631ce0 100644 --- a/pages/index.md +++ b/pages/index.md @@ -2514,21 +2514,37 @@ + [Monitoring DDoS attacks with the Network Security Dashboard](bare_metal_cloud/dedicated_servers/network_security_dashboard) + [OVHcloud Connect](products/network-ovhcloud-connect) + [Key Concepts](network-ovhcloud-connect-concepts) - + [Concepts overview](network/ovhcloud_connect/occ-concepts-overview) - + [Layer 2 mode](network/ovhcloud_connect/occ-layer2) - + [Layer 3 mode](network/ovhcloud_connect/occ-layer3) + + [Introduction to OVHcloud Connect](network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect) + + [OVHcloud Connect - Glossary](network/ovhcloud_connect/1.2_glossary) + + [OVHcloud Connect - Providers](network/ovhcloud_connect/1.3_providers) + + [OVHcloud Connect - PoPs and Regions](network/ovhcloud_connect/1.4_pop_locations_regions) + + [Multi-AZ architectures for OVHcloud Connect](network/ovhcloud_connect/1.5_multi_az) + + [Automate OVHcloud Connect with API, CLI, and Terraform](network/ovhcloud_connect/1.6_automation) + + [OVHcloud Connect - SLAs](network/ovhcloud_connect/1.7_slas) + + [OVHcloud Connect - Prerequisites & Limitations](network/ovhcloud_connect/1.8_prerequisites_limitations) + [Getting started](network-ovhcloud-connect-getting-started) - + [Installation of OVHcloud Connect Direct from the OVHcloud Control Panel](network/ovhcloud_connect/occ-direct-control-panel) - + [Installation of OVHcloud Connect Provider from the OVHcloud Control Panel](network/ovhcloud_connect/occ-provider-control-panel) - + [How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel](network/ovhcloud_connect/occ-diagnostics) - + [OVHcloud Connect Logs Forwarding](network/ovhcloud_connect/occ-logs-2-customers) - + [FAQ](network/ovhcloud_connect/occdedicated-faq) + + [Quick Start: Direct Connection to OVHcloud](network/ovhcloud_connect/2.1_quick_start_direct) + + [Quick Start: Connection to OVHcloud with a Provider](network/ovhcloud_connect/2.2_quick_start_provider) + [Configuration](network-ovhcloud-connect-configuration) - + [Configuration of OVHcloud Connect using OVHcloud APIv6](network/ovhcloud_connect/occ-howto-api) + + [Order OVHcloud Connect Direct](network/ovhcloud_connect/3.1_order_direct) + + [Order OVHcloud Connect Provider](network/ovhcloud_connect/3.2_order_provider) + + [Cancel OVHcloud Connect Direct](network/ovhcloud_connect/3.3_cancel_direct) + + [Cancel OVHcloud Connect Provider](network/ovhcloud_connect/3.4_cancel_provider) + + [Associate an OVHcloud Connect to Your vRack](network/ovhcloud_connect/3.5_associate_vrack) + + [Set up the vRack network for OVHcloud Connect](network/ovhcloud_connect/3.6_vrack_network_setup) + + [Configure OVHcloud Connect L3 with BGP](network/ovhcloud_connect/3.7_occ_l3_bgp) + + [Configure OVHcloud Connect L3 with static routes](network/ovhcloud_connect/3.8_occ_l3_static) + + [Monitor Your OVHcloud Connect](network/ovhcloud_connect/3.9_monitor) + + [Order or cancel a Cross Connect with an LOA](network/ovhcloud_connect/3.11_cross_connect_loa) + + [Set up logs forwarding for OVHcloud Connect](network/ovhcloud_connect/3.12_log_forwarding) + + [Tutorials](network-ovhcloud-connect-tutorials) + + [Set up a simple OVHcloud Connect architecture](network/ovhcloud_connect/4.1_simple) + + [Set up a resilient OVHcloud Connect architecture](network/ovhcloud_connect/4.2_resilient) + [Troubleshooting](network-ovhcloud-connect-troubleshooting) - + [Troubleshooting common errors setting up OVHcloud Connect](network/ovhcloud_connect/occ-setup-diagnostics) + + [Troubleshoot OVHcloud Connect](network/ovhcloud_connect/1.9_troubleshooting) + + [Declare and Follow Up Upon an Incident](network/ovhcloud_connect/3.10_incident_followup) + [Additional resources](network-ovhcloud-connect-technical-resources) - + [Technical capabilities and limitations](network/ovhcloud_connect/occ-limits) + + [OVHcloud Connect - Frequently Asked Questions (FAQ)](network/ovhcloud_connect/5_faq) + [SecNumCloud](network-secnumcloud-connectivity) + [Concepts overview](hosted_private_cloud/hosted_private_cloud_powered_by_vmware/snc-connectivity-concepts-overview) + [SPN Concept](hosted_private_cloud/hosted_private_cloud_powered_by_vmware/snc-connectivity-concepts-spn) @@ -2636,7 +2652,7 @@ + [Web Cloud Databases - How to manage logs](web_cloud/web_cloud_databases/retrieve-logs) + [Managed Kubernetes Service Audit Logs Forwarding](public_cloud/containers_orchestration/managed_kubernetes/forwarding-audit-logs-to-logs-data-platform) + [Pushing logs from OVHcloud KMS to Logs Data Platform](manage_and_operate/kms/kms-troubleshooting) - + [OVHcloud Connect Logs Forwarding](network/ovhcloud_connect/occ-logs-2-customers) + + [OVHcloud Connect Logs Forwarding](network/ovhcloud_connect/3.12_log_forwarding) + [IAM](observability-logs-data-platform-iam) + [IAM for Logs Data Platform - Migration and Breaking Changes](manage_and_operate/observability/logs_data_platform/iam_migration_to_iam) + [IAM for Logs Data Platform - Presentation and FAQ](manage_and_operate/observability/logs_data_platform/iam_presentation_faq) diff --git a/pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/guide.en-gb.md b/pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/guide.en-gb.md new file mode 100644 index 00000000000..74fe42d582c --- /dev/null +++ b/pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/guide.en-gb.md @@ -0,0 +1,73 @@ +--- +title: Introduction to OVHcloud Connect +excerpt: Overview of the concepts required to understand the OVHcloud Connect offer +updated: 2026-02-18 +--- + +## What is OVHcloud Connect? + +OVHcloud Connect is a **dedicated, private network connection** between your infrastructure and OVHcloud. Instead of routing traffic over the public internet, OVHcloud Connect establishes a direct link that offers better security, lower latency, and guaranteed bandwidth. + +## Who is it for? + +OVHcloud Connect is designed for organisations that need: + +- **Reliable connectivity** for business-critical applications (ERP, databases, backups). +- **Enhanced security** by keeping traffic off the public internet. +- **Predictable performance** with dedicated bandwidth (no shared bottlenecks). +- **Multi-cloud or hybrid-cloud** architectures connecting on-premises data centres, different cloud infrastructures, or WAN networks to OVHcloud. + +## How does it work? + +OVHcloud Connect links your network to OVHcloud through a **Point of Presence (PoP)** — a physical location where OVHcloud has networking equipment. You can establish this link in two ways: + +| Connection type | How it works | Best for | +|---|---|---| +| **OVHcloud Connect Direct** | You manage a physical cable (cross-connect) between your equipment and OVHcloud's equipment in a common Point of Presence. | Organisations already present in an OVHcloud PoP. | +| **OVHcloud Connect Provider** | A third-party network provider among our [partners](https://www.ovhcloud.com/en/network/ovhcloud-connect/#partenaires) handles the physical connection on your behalf. | Organisations that are not co-located with OVHcloud or prefer a managed connectivity service. | + +### Layer 2 (L2) service - OVHcloud Connect Direct only + +OVHcloud Connect L2 links your infrastructure to OVHcloud services at the data link layer (Layer 2). It allows you to extend your private network to OVHcloud datacenters, creating a seamless bridge between your local network and cloud resources, no routing involved. As opposed to Layer 3 service, it is transparent to VLANs (802.1q). + +**Key points:** +- It is a strict point-to-point link (**one PoP** and **one AZ** only). +- Redundancy is possible via link aggregation (LACP) on the same PoP. + +**Potential use cases:** +- Simple hybrid topologies +- "Lift & Shift" migrations without IP changes +- Applications requiring L2 adjacency or VLAN transparency + +### Layer 3 (L3) service + +OVHcloud Connect L3 links your infrastructure to OVHcloud services at the network layer (Layer 3). It allows routing and requires routes exchange. + +Once the physical link is established, routing is configured using **BGP (Border Gateway Protocol)**, and the connection is associated with your **vRack** — OVHcloud's virtual private network — so your OVHcloud resources can communicate privately with your external infrastructure. + +**Key points:** +- It is supported by a Full Mesh architecture allowing multiple PoPs and availability zones (AZ) to be interconnected within a region. +- Network resilience can be created via BGP sessions (multi-peers) and ECMP, with the possibility of automatic failover between multiple PoPs. + +**Potential use cases:** +- Enterprise WAN integration (Cloud as a Branch) +- Critical multi-PoP architectures +- Large-scale complex deployments. + +## Architecture overview + +![Global design](image.png) + +## What's next? + +- Review the [Glossary](../1.2_glossary) to understand key terms. +- See the list of [Providers](../1.3_providers) available for managed connectivity. +- Read the [prerequisites and limitations](../1.8_prerequisites_limitations) to verify whether OVHcloud Connect meets your use case. +- Jump to the [Quick Start guides: Direct](../2.1_quick_start_direct) to get connected. +- Jump to the [Quick Start guides: Provider](../2.2_quick_start_provider) to get connected. + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/guide.fr-fr.md b/pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/guide.fr-fr.md new file mode 100644 index 00000000000..d7dd07176bc --- /dev/null +++ b/pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/guide.fr-fr.md @@ -0,0 +1,73 @@ +--- +title: Introduction à OVHcloud Connect +excerpt: Vue d'ensemble des concepts nécessaires à la compréhension de l'offre OVHcloud Connect +updated: 2026-02-18 +--- + +## Qu'est-ce qu'OVHcloud Connect ? + +OVHcloud Connect est une **connexion réseau privée et dédiée** entre votre infrastructure et OVHcloud. Au lieu d'acheminer le trafic via l'internet public, OVHcloud Connect établit un lien direct qui offre une meilleure sécurité, une latence réduite et une bande passante garantie. + +## À qui s'adresse-t-elle ? + +OVHcloud Connect s'adresse aux organisations qui ont besoin de : + +- **Connectivité fiable** pour les applications critiques pour l'activité (ERP, bases de données, sauvegardes). +- **Sécurité renforcée** en maintenant le trafic hors de l'internet public. +- **Performances prévisibles** grâce à une bande passante dédiée (sans goulets d'étranglement partagés). +- Architectures **multi-cloud ou hybrides** reliant des datacenters sur site, différentes infrastructures cloud ou des réseaux WAN à OVHcloud. + +## Comment cela fonctionne-t-il ? + +OVHcloud Connect relie votre réseau à OVHcloud via un **Point de présence (PoP)** — un emplacement physique où OVHcloud dispose d'équipements réseau. Vous pouvez établir cette liaison de deux manières : + +| Type de connexion | Fonctionnement | Idéal pour | +|---|---|---| +| **OVHcloud Connect Direct** | Vous gérez un câble physique (cross-connect) entre votre équipement et celui d'OVHcloud dans un Point de présence commun. | Les organisations déjà présentes dans un PoP OVHcloud. | +| **OVHcloud Connect Provider** | Un opérateur réseau tiers parmi nos [partenaires](https://www.ovhcloud.com/en/network/ovhcloud-connect/#partenaires) prend en charge la connexion physique pour vous. | Les organisations qui ne sont pas colocalisées avec OVHcloud ou qui préfèrent un service de connectivité managé. | + +### Service Layer 2 (L2) - OVHcloud Connect Direct uniquement + +OVHcloud Connect L2 relie votre infrastructure aux services OVHcloud au niveau de la couche liaison de données (Layer 2). Il vous permet d'étendre votre réseau privé aux datacenters OVHcloud, créant un pont transparent entre votre réseau local et vos ressources cloud, sans routage. Contrairement au service Layer 3, il est transparent aux VLAN (802.1q). + +**Points clés :** +- Il s'agit d'un lien strictement point à point (**un seul PoP** et **une seule AZ**). +- La redondance est possible via l'agrégation de liens (LACP) sur le même PoP. + +**Cas d'usage potentiels :** +- Topologies hybrides simples +- Migrations « Lift & Shift » sans changement d'adressage IP +- Applications nécessitant l'adjacence L2 ou la transparence VLAN + +### Service Layer 3 (L3) + +OVHcloud Connect L3 relie votre infrastructure aux services OVHcloud au niveau de la couche réseau (Layer 3). Il permet le routage et nécessite l'échange de routes. + +Une fois le lien physique établi, le routage est configuré via **BGP (Border Gateway Protocol)**, et la connexion est associée à votre **vRack** — le réseau privé virtuel d'OVHcloud — afin que vos ressources OVHcloud puissent communiquer en privé avec votre infrastructure externe. + +**Points clés :** +- Il repose sur une architecture Full Mesh permettant d'interconnecter plusieurs PoPs et availability zones (AZ) au sein d'une région. +- La résilience réseau peut être obtenue via des sessions BGP (multi-peers) et ECMP, avec la possibilité d'un basculement automatique entre plusieurs PoPs. + +**Cas d'usage potentiels :** +- Intégration WAN d'entreprise (Cloud as a Branch) +- Architectures multi-PoP critiques +- Déploiements complexes à grande échelle. + +## Vue d'ensemble de l'architecture + +![Conception globale](image.png) + +## Et ensuite ? + +- Consultez le [Glossaire](../1.2_glossary) pour comprendre les termes clés. +- Découvrez la liste des [Providers](../1.3_providers) disponibles pour la connectivité managée. +- Lisez les [prérequis et limitations](../1.8_prerequisites_limitations) pour vérifier si OVHcloud Connect répond à votre cas d'usage. +- Accédez aux [guides Quick Start : Direct](../2.1_quick_start_direct) pour vous connecter. +- Accédez aux [guides Quick Start : Provider](../2.2_quick_start_provider) pour vous connecter. + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/image.png b/pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/image.png new file mode 100644 index 00000000000..c9bf7898e0b Binary files /dev/null and b/pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/image.png differ diff --git a/pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/images/OCC_architecture_overview.png b/pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/images/OCC_architecture_overview.png new file mode 100644 index 00000000000..c9bf7898e0b Binary files /dev/null and b/pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/images/OCC_architecture_overview.png differ diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/meta.yaml b/pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/meta.yaml old mode 100755 new mode 100644 similarity index 100% rename from pages/network/ovhcloud_connect/occ-concepts-overview/meta.yaml rename to pages/network/ovhcloud_connect/1.1_introduction_to_ovhcloud_connect/meta.yaml diff --git a/pages/network/ovhcloud_connect/1.2_glossary/guide.en-gb.md b/pages/network/ovhcloud_connect/1.2_glossary/guide.en-gb.md new file mode 100644 index 00000000000..6b1a23dd409 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.2_glossary/guide.en-gb.md @@ -0,0 +1,101 @@ +--- +title: 'OVHcloud Connect - Glossary' +excerpt: 'Discover the vocabulary related to the technologies used by OVHcloud Connect' +updated: 2026-01-12 +--- + +## OVHcloud Connect Glossary + +This page defines the key terms you will encounter throughout the OVHcloud Connect documentation. Terms are listed alphabetically. + +### A + +**ASN (Autonomous System Number)** +A unique number that identifies a network on the internet for the purpose of exchanging routing information via BGP. Your network has its own ASN, and OVHcloud has its own ASN. These numbers are used when configuring BGP sessions. + +**AZ (Availability Zone)** +A physically separate datacenter within a region, containing the one or more datacenters hosting your services. AZs are both sufficiently geographically distant from each other to be isolated in the event of a disaster, and sufficiently close to ensure low latency. + +### B + +**Bandwidth** +The subscribed throughput capacity for your link (from 50 Mbps to 10 Gbps). Unlike a connection established over the Internet, this throughput is guaranteed and ensures consistent performance. + +**BGP (Border Gateway Protocol)** +The standard routing protocol used to exchange network routes between different networks. In the context of OVHcloud Connect, BGP is used in L3 mode to tell each side (your network and OVHcloud) which IP address ranges are reachable through the connection. + +**BGP-ECMP (Equal-Cost Multi-Path)** +Routing technique that distributes traffic across multiple active physical links simultaneously, thus optimising load and redundancy. + +**BGP Session** +An active connection between two BGP routers (called "peers") that allows them to share routing information. You will configure at least one BGP session between your router and OVHcloud's router at the PoP. + +### C + +**Cross-connect** +A physical cable that connects your equipment (or your provider's equipment) to OVHcloud's equipment inside a Point of Presence. Cross-connects are typically fibre-optic cables. + +### D + +**Direct Connection (OVHcloud Connect Direct)** +A connection type where you manage the physical link yourself, typically through a cross-connect in a co-location facility where OVHcloud has a PoP. + +### I + +**Isolation** +Physical or logical separation of your data, protecting it from external threats (DDoS, interceptions) related to the public web. + +### L + +**LACP (Link Aggregation Control Protocol)** +Protocol that allows multiple physical interfaces to be grouped into a single logical link, useful for redundancy and increasing throughput. + +**Layer 2 (L2) Connectivity** +A connection mode where OVHcloud Connect acts as a transparent bridge. You manage your own routing and IP addressing on top of the link. This gives maximum flexibility. + +**Layer 3 (L3) Connectivity** +A connection mode where routing is handled at the network layer. BGP sessions are established to exchange routes between your network and OVHcloud. + +**LOA (Letter of Authorization)** +An official document provided by OVHcloud that authorises a data centre operator to set up or remove a cross-connect on your behalf. You hand the LOA to the facility operator to complete the physical patching. + +### M + +**Multi-AZ** +A deployment strategy that spreads your resources and connections across multiple Availability Zones. This protects against the failure of a single data centre or network path. + +### P + +**PoP (Point of Presence)** +A physical location (third-party data center) where the OVHcloud network is available for connection. It is also the entry point of your data into OVHcloud's private network. The accessible PoPs are listed on [this link on our website](/links/network/ovhcloud-connect). + +**Provider (OVHcloud Connect Provider)** +A third-party network operator that facilitates the physical connectivity between your network and OVHcloud's network. Using a provider means you do not need to be physically present in the same data centre as OVHcloud. + +### R + +**Region** +A geographical area where OVHcloud operates one or more data centres and Availability Zones. OVHcloud regions are deployed around the world, including in Europe, North America, and Asia-Pacific. Find out more on OVHcloud regions on [this link to our website](https://www.ovhcloud.com/en/about-us/global-infrastructure/expansion-regions-az/). + +### S + +**Service Key** +A unique activation key you need to provide to your partner operator to establish the connection. + +**SLA (Service Level Agreement)** +A contractual commitment from OVHcloud that defines the guaranteed level of service — typically expressed as a percentage of uptime (e.g. 99.9%) along with support response times. + + +### V + +**VLAN (Virtual Local Area Network)** +Independent logical network created on a shared physical infrastructure, allowing a local network to be segmented into several isolated groups to improve security and performance. + +**vRack** +Isolated virtual private network provided by OVHcloud that allows you to interconnect your other OVHcloud services (Bare Metal servers, Public Cloud instances, Hosted Private Cloud, etc) in an isolated private network, regardless of their location. OVHcloud Connect is associated with a vRack to extend your private network into OVHcloud. For more information, please consult the [product page on our website](/links/network/vrack). + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/1.2_glossary/guide.fr-fr.md b/pages/network/ovhcloud_connect/1.2_glossary/guide.fr-fr.md new file mode 100644 index 00000000000..b7342ef197e --- /dev/null +++ b/pages/network/ovhcloud_connect/1.2_glossary/guide.fr-fr.md @@ -0,0 +1,101 @@ +--- +title: 'OVHcloud Connect - Glossaire' +excerpt: 'Découvrez le vocabulaire lié aux technologies utilisées par OVHcloud Connect' +updated: 2026-01-12 +--- + +## Glossaire OVHcloud Connect + +Cette page définit les termes clés que vous rencontrerez tout au long de la documentation OVHcloud Connect. Les termes sont listés par ordre alphabétique. + +### A + +**ASN (Autonomous System Number)** +Numéro unique qui identifie un réseau sur internet, utilisé pour échanger des informations de routage via BGP. Votre réseau dispose de son propre ASN, et OVHcloud dispose de son propre ASN. Ces numéros sont utilisés lors de la configuration des sessions BGP. + +**AZ (Availability Zone)** +Datacenter physiquement séparé au sein d'une région, contenant un ou plusieurs datacenters hébergeant vos services. Les AZ sont à la fois suffisamment éloignées géographiquement les unes des autres pour être isolées en cas de sinistre, et suffisamment proches pour garantir une faible latence. + +### B + +**Bande passante** +Capacité de débit souscrite pour votre lien (de 50 Mbps à 10 Gbps). Contrairement à une connexion établie via internet, ce débit est garanti et assure des performances constantes. + +**BGP (Border Gateway Protocol)** +Protocole de routage standard utilisé pour échanger des routes réseau entre différents réseaux. Dans le cadre d'OVHcloud Connect, BGP est utilisé en mode L3 pour indiquer à chaque côté (votre réseau et OVHcloud) quelles plages d'adresses IP sont accessibles via la connexion. + +**BGP-ECMP (Equal-Cost Multi-Path)** +Technique de routage qui répartit le trafic sur plusieurs liens physiques actifs simultanément, optimisant ainsi la charge et la redondance. + +**Session BGP** +Connexion active entre deux routeurs BGP (appelés « peers ») qui leur permet de partager des informations de routage. Vous configurerez au moins une session BGP entre votre routeur et celui d'OVHcloud au PoP. + +### C + +**Clé de service** +Clé d'activation unique que vous devez fournir à votre opérateur partenaire pour établir la connexion. + +**Cross-connect** +Câble physique qui relie votre équipement (ou celui de votre provider) à celui d'OVHcloud à l'intérieur d'un Point de présence. Les cross-connects sont généralement des câbles à fibre optique. + +### D + +**Connexion directe (OVHcloud Connect Direct)** +Type de connexion où vous gérez vous-même le lien physique, généralement via un cross-connect dans une installation de colocation où OVHcloud dispose d'un PoP. + +### I + +**Isolation** +Séparation physique ou logique de vos données, les protégeant des menaces externes (DDoS, interceptions) liées au web public. + +### L + +**LACP (Link Aggregation Control Protocol)** +Protocole qui permet de regrouper plusieurs interfaces physiques en un seul lien logique, utile pour la redondance et l'augmentation du débit. + +**Connectivité Layer 2 (L2)** +Mode de connexion où OVHcloud Connect agit comme un pont transparent. Vous gérez votre propre routage et adressage IP par-dessus le lien. Cela offre une flexibilité maximale. + +**Connectivité Layer 3 (L3)** +Mode de connexion où le routage est géré au niveau de la couche réseau. Des sessions BGP sont établies pour échanger des routes entre votre réseau et OVHcloud. + +**LOA (Letter of Authorization)** +Document officiel fourni par OVHcloud qui autorise un opérateur de datacenter à mettre en place ou à supprimer un cross-connect pour votre compte. Vous remettez la LOA à l'opérateur de l'installation pour finaliser le brassage physique. + +### M + +**Multi-AZ** +Stratégie de déploiement qui répartit vos ressources et connexions sur plusieurs Availability Zones. Cela protège contre la défaillance d'un datacenter ou d'un chemin réseau unique. + +### P + +**PoP (Point de présence)** +Emplacement physique (datacenter tiers) où le réseau OVHcloud est disponible pour la connexion. C'est également le point d'entrée de vos données dans le réseau privé d'OVHcloud. Les PoPs accessibles sont listés sur [ce lien de notre site web](/links/network/ovhcloud-connect). + +**Provider (OVHcloud Connect Provider)** +Opérateur réseau tiers qui facilite la connectivité physique entre votre réseau et celui d'OVHcloud. Recourir à un provider signifie que vous n'avez pas besoin d'être physiquement présent dans le même datacenter qu'OVHcloud. + +### R + +**Région** +Zone géographique où OVHcloud exploite un ou plusieurs datacenters et Availability Zones. Les régions OVHcloud sont déployées dans le monde entier, notamment en Europe, en Amérique du Nord et en Asie-Pacifique. Pour en savoir plus sur les régions OVHcloud, consultez [ce lien vers notre site web](https://www.ovhcloud.com/en/about-us/global-infrastructure/expansion-regions-az/). + +### S + +**SLA (Service Level Agreement)** +Engagement contractuel d'OVHcloud qui définit le niveau de service garanti — généralement exprimé en pourcentage de disponibilité (par exemple 99,9 %) ainsi qu'en délais de réponse du support. + + +### V + +**VLAN (Virtual Local Area Network)** +Réseau logique indépendant créé sur une infrastructure physique partagée, permettant de segmenter un réseau local en plusieurs groupes isolés afin d'améliorer la sécurité et les performances. + +**vRack** +Réseau privé virtuel isolé fourni par OVHcloud, qui vous permet d'interconnecter vos autres services OVHcloud (serveurs Bare Metal, instances Public Cloud, Hosted Private Cloud, etc.) au sein d'un réseau privé isolé, indépendamment de leur emplacement. OVHcloud Connect est associé à un vRack pour étendre votre réseau privé jusque dans OVHcloud. Pour plus d'informations, veuillez consulter la [page produit sur notre site web](/links/network/vrack). + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/1.2_glossary/meta.yaml b/pages/network/ovhcloud_connect/1.2_glossary/meta.yaml new file mode 100644 index 00000000000..2e85a49dcef --- /dev/null +++ b/pages/network/ovhcloud_connect/1.2_glossary/meta.yaml @@ -0,0 +1,2 @@ +id: 888c4638-6672-4f1e-9f64-b92d1e7c066e +full_slug: network-ovhcloud-connect-glossary diff --git a/pages/network/ovhcloud_connect/1.3_providers/guide.en-gb.md b/pages/network/ovhcloud_connect/1.3_providers/guide.en-gb.md new file mode 100644 index 00000000000..ea7f3e22683 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.3_providers/guide.en-gb.md @@ -0,0 +1,147 @@ +--- +title: 'OVHcloud Connect - Providers' +excerpt: 'Discover the third-party network providers that partner with OVHcloud to offer managed connectivity' +updated: 2026-02-18 +--- + +## Objective + +Providers are third-party network operators that partner with OVHcloud to offer managed connectivity in OVHcloud's Points of Presence (PoPs). Using a provider is an alternative to managing your own physical cross-connect (Direct connection). + +## Why use a provider? + +| Benefit | Description | +|---|---| +| **No co-location required** | You don't need equipment in the same data centre as OVHcloud. The provider bridges the gap. | +| **Simplified ordering** | The provider handles the physical connection, cross-connects, and often provides a portal to manage everything. | +| **Dynamic provisioning** | Many providers offer on-demand connections that can be set up in minutes through their platform. | +| **Multi-cloud connectivity** | Many providers also connect to AWS, Azure, GCP, and others — ideal for multi-cloud architectures. | +| **Managed services** | Providers may offer additional support, monitoring, and SLAs on top of OVHcloud's own guarantees. | + +## Choosing the right provider + +Consider the following: + +- **Geography** — Is the provider present at your location and at the OVHcloud PoP you want to use? +- **Existing relationship** — Do you already use a provider for other cloud connections? Consolidating simplifies management. +- **Connection speed** — Confirm the bandwidth options available (typically from 50 Mbps to 50 Gbps). +- **Provisioning model** — Some providers offer instant, portal-based provisioning; others require manual coordination. +- **Additional services** — Look for monitoring, SLA guarantees, and multi-cloud features. + +## Supported providers + +OVHcloud partners with the global network providers listed below. + +> **Note:** The list of supported providers may evolve over time. Check the [OVHcloud Connect Webpage](https://www.ovhcloud.com/en/network/ovhcloud-connect/) for the most current list. + +### BSO (formerly Intercloud) +--- +#### Description + +BSO is a global financial network and technology provider specializing in ultra-low latency connectivity and cloud access for capital markets, enterprises, and trading firms. Following the acquisition of Intercloud, BSO expanded its cloud connectivity portfolio to offer direct, private connections to major cloud providers including OVHcloud. + +BSO's network is optimised for performance-critical applications, with a focus on financial services, media, and data-intensive industries. Their solutions combine high-performance networking with cloud on-ramps and managed services. + +#### Useful links + +- **Website:** [bso.co/network/cloud-connectivity](https://www.bso.co/network/cloud-connectivity) +- **Documentation:** [bso.co/resources](https://www.bso.co/resources) + +### Console Connect +--- +#### Description + +Console Connect is an on-demand Software-Defined Interconnection platform that simplifies connectivity to clouds, data centres, and networks. The platform allows enterprises to establish private Layer 2 connections, deploy a CloudRouter or last-mile connectivity through a user-friendly web portal without the need for physical hardware or long lead times. + +Console Connect leverages PCCW Global's extensive subsea and terrestrial fibre network, providing reliable global reach with strong presence in Asia-Pacific, Europe, and the Americas. + +#### Useful links + +- **Website:** [consoleconnect.com](https://www.consoleconnect.com/clouds/connect-to-ovhcloud/) +- **Documentation:** [docs.consoleconnect.com](https://docs.consoleconnect.com/) +- **API Documentation:** [api.consoleconnect.com](https://api.consoleconnect.com/docs/) + +### Digital Realty +--- +#### Description + +Digital Realty is a global provider of data centre, colocation, and interconnection solutions, serving enterprises, cloud providers, and network operators. Through their ServiceFabric platform, Digital Realty offers direct, secure connectivity to major cloud and network service providers, including OVHcloud. + +With over 300 data centres across six continents, Digital Realty provides high-density colocation combined with scalable interconnection options for hybrid and multi-cloud deployments. + +#### Useful links + +- **Website:** [digitalrealty.com/data-center-solutions/servicefabric](https://www.digitalrealty.com/platform-digital/connectivity/service-fabric/connect) + +### Equinix Fabric +--- +#### Description + +Equinix Fabric is a global interconnection platform that provides software-defined networking to connect distributed infrastructure and digital ecosystems. Part of Equinix's Platform Equinix offering, Fabric enables secure, direct, and dynamic connections between enterprises, network service providers, and cloud providers. + +With presence in over 70 metros worldwide and direct access to more than 2,900 clouds and networks, Equinix Fabric is a powerful solution for enterprises requiring low-latency, high-performance interconnection at scale. + +#### Useful links + +- **Website:** [equinix.com/interconnection-services/fabric](https://www.equinix.com/products/digital-infrastructure-services/equinix-fabric) +- **Documentation:** [docs.equinix.com/en-us/Content/Interconnection/Fabric/Fabric-landing-main.htm](https://docs.equinix.com/fabric/) +- **API Documentation:** [developer.equinix.com/catalog/fabricv4](https://developer.equinix.com/catalog/fabricv4) + +### Megaport +--- +#### Description + +Megaport is a leading global Network-as-a-Service (NaaS) platform that enables businesses to rapidly connect their network to cloud service providers and data centres through software-defined networking. Their solutions include: +- Virtual Cross Connects (VXC) for point-to-point connectivity, +- Megaport Cloud Router (MCR) for advanced multi-cloud routing without physical hardware, +- Megaport Virtual Edge (MVE) for deploying network virtualized functions (NFV). + +Megaport's network spans over 700 enabled data centres across North America, Europe, and Asia-Pacific, providing extensive reach for hybrid and multi-cloud architectures. + +#### Useful links + +- **Website:** [megaport.com/ovhcloud](https://www.megaport.com/ecosystem/ovhcloud/) +- **Documentation:** [docs.megaport.com](https://docs.megaport.com/) +- **API Documentation:** [dev.megaport.com](https://dev.megaport.com/) + +### Orange Business Services +--- +#### Description + +Orange Business Services is the enterprise division of Orange, one of Europe's leading telecommunications operators. They provide managed network solutions including SD-WAN, MPLS, Internet, and cloud connectivity services tailored for large enterprises and multinational corporations. + +Orange Business Services operates a global network reaching 166 countries and territories, with strong presence in Europe, Africa, and the Middle East. Their solutions integrate traditional WAN services with modern cloud connectivity, enabling seamless hybrid architectures. + +#### Useful links + +- **Website:** [orange-business.com/en/products/galerie](https://www.orange-business.com/en/solutions/cloud/galerie) + +### Risq +--- +#### Description + +Risq is a Quebec-based network service provider offering secure, high-performance connectivity solutions for enterprises, financial institutions, and cloud service providers. Risq operates a carrier-grade network with a strong presence in Quebec and Canada, providing direct cloud on-ramps, MPLS, Internet, and dark fibre services. + +Risq positions itself as a premium connectivity partner for businesses requiring dedicated bandwidth, low latency, and stringent security and compliance standards, particularly in regulated industries and the Canadian market. + +#### Useful links + +- **Website:** [risq.quebec](https://www.risq.quebec/) + +## How it works + +1. **You order** a connection to OVHcloud through the provider's portal or with OVHcloud (who gives you a **pairing key**). +2. **The provider provisions** the link between your location and the OVHcloud PoP. +3. **You configure** BGP and VLAN settings on your side (or the provider handles Layer 3 routing for you). +4. **Traffic flows privately** between your network and OVHcloud through the provider's backbone. + +## What's next? + +- Check [PoP Locations & Regions](../1.4_pop_locations_regions/guide.en-gb.md) to find where you can connect +- Follow the [Quick Start with a Provider](../2.2_quick_start_provider/guide.en-gb.md) to get started + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/1.3_providers/guide.fr-fr.md b/pages/network/ovhcloud_connect/1.3_providers/guide.fr-fr.md new file mode 100644 index 00000000000..b7348b36e36 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.3_providers/guide.fr-fr.md @@ -0,0 +1,147 @@ +--- +title: 'OVHcloud Connect - Providers' +excerpt: 'Découvrez les opérateurs réseau tiers partenaires d''OVHcloud qui proposent une connectivité managée' +updated: 2026-02-18 +--- + +## Objectif + +Les providers sont des opérateurs réseau tiers partenaires d'OVHcloud qui proposent une connectivité managée dans les Points de présence (PoP) d'OVHcloud. Recourir à un provider est une alternative à la gestion de votre propre cross-connect physique (connexion Direct). + +## Pourquoi recourir à un provider ? + +| Avantage | Description | +|---|---| +| **Pas de colocation requise** | Vous n'avez pas besoin d'avoir des équipements dans le même datacenter qu'OVHcloud. Le provider fait le lien. | +| **Commande simplifiée** | Le provider gère la connexion physique, les cross-connects, et propose souvent un portail pour tout administrer. | +| **Provisionnement dynamique** | De nombreux providers proposent des connexions à la demande qui peuvent être mises en place en quelques minutes via leur plateforme. | +| **Connectivité multi-cloud** | De nombreux providers se connectent également à AWS, Azure, GCP et d'autres — idéal pour les architectures multi-cloud. | +| **Services managés** | Les providers peuvent proposer un support, une supervision et des SLAs supplémentaires en plus des garanties propres à OVHcloud. | + +## Choisir le bon provider + +Considérez les éléments suivants : + +- **Géographie** — Le provider est-il présent à votre emplacement et au PoP OVHcloud que vous souhaitez utiliser ? +- **Relation existante** — Utilisez-vous déjà un provider pour d'autres connexions cloud ? La consolidation simplifie la gestion. +- **Vitesse de connexion** — Vérifiez les options de bande passante disponibles (généralement de 50 Mbps à 50 Gbps). +- **Modèle de provisionnement** — Certains providers proposent un provisionnement instantané via portail ; d'autres nécessitent une coordination manuelle. +- **Services additionnels** — Recherchez la supervision, les garanties SLA et les fonctionnalités multi-cloud. + +## Providers pris en charge + +OVHcloud est partenaire des opérateurs réseau mondiaux listés ci-dessous. + +> **Remarque :** la liste des providers pris en charge peut évoluer. Consultez la [page web OVHcloud Connect](https://www.ovhcloud.com/en/network/ovhcloud-connect/) pour la liste la plus à jour. + +### BSO (anciennement Intercloud) +--- +#### Description + +BSO est un fournisseur mondial de réseau financier et de technologie spécialisé dans la connectivité à très faible latence et l'accès au cloud pour les marchés des capitaux, les entreprises et les sociétés de trading. À la suite de l'acquisition d'Intercloud, BSO a élargi son portefeuille de connectivité cloud pour proposer des connexions privées directes vers les principaux fournisseurs cloud, dont OVHcloud. + +Le réseau de BSO est optimisé pour les applications critiques en termes de performances, avec un focus sur les services financiers, les médias et les industries fortement consommatrices de données. Leurs solutions combinent un réseau haute performance avec des on-ramps cloud et des services managés. + +#### Liens utiles + +- **Site web :** [bso.co/network/cloud-connectivity](https://www.bso.co/network/cloud-connectivity) +- **Documentation :** [bso.co/resources](https://www.bso.co/resources) + +### Console Connect +--- +#### Description + +Console Connect est une plateforme d'interconnexion à la demande définie par logiciel (Software-Defined Interconnection) qui simplifie la connectivité aux clouds, datacenters et réseaux. La plateforme permet aux entreprises d'établir des connexions privées Layer 2, de déployer un CloudRouter ou d'obtenir une connectivité de dernier kilomètre via un portail web convivial, sans matériel physique ni longs délais. + +Console Connect s'appuie sur le vaste réseau de fibre sous-marine et terrestre de PCCW Global, offrant une portée mondiale fiable avec une forte présence en Asie-Pacifique, en Europe et dans les Amériques. + +#### Liens utiles + +- **Site web :** [consoleconnect.com](https://www.consoleconnect.com/clouds/connect-to-ovhcloud/) +- **Documentation :** [docs.consoleconnect.com](https://docs.consoleconnect.com/) +- **Documentation API :** [api.consoleconnect.com](https://api.consoleconnect.com/docs/) + +### Digital Realty +--- +#### Description + +Digital Realty est un fournisseur mondial de solutions de datacenter, de colocation et d'interconnexion, au service des entreprises, des fournisseurs cloud et des opérateurs réseau. Via leur plateforme ServiceFabric, Digital Realty propose une connectivité directe et sécurisée vers les principaux fournisseurs cloud et de services réseau, dont OVHcloud. + +Avec plus de 300 datacenters répartis sur six continents, Digital Realty offre une colocation à haute densité combinée à des options d'interconnexion évolutives pour les déploiements hybrides et multi-cloud. + +#### Liens utiles + +- **Site web :** [digitalrealty.com/data-center-solutions/servicefabric](https://www.digitalrealty.com/platform-digital/connectivity/service-fabric/connect) + +### Equinix Fabric +--- +#### Description + +Equinix Fabric est une plateforme d'interconnexion mondiale qui fournit un réseau défini par logiciel pour connecter des infrastructures distribuées et des écosystèmes numériques. Composante de l'offre Platform Equinix, Fabric permet des connexions sécurisées, directes et dynamiques entre les entreprises, les fournisseurs de services réseau et les fournisseurs cloud. + +Avec une présence dans plus de 70 métropoles dans le monde et un accès direct à plus de 2 900 clouds et réseaux, Equinix Fabric est une solution puissante pour les entreprises ayant besoin d'une interconnexion à faible latence et haute performance à grande échelle. + +#### Liens utiles + +- **Site web :** [equinix.com/interconnection-services/fabric](https://www.equinix.com/products/digital-infrastructure-services/equinix-fabric) +- **Documentation :** [docs.equinix.com/en-us/Content/Interconnection/Fabric/Fabric-landing-main.htm](https://docs.equinix.com/fabric/) +- **Documentation API :** [developer.equinix.com/catalog/fabricv4](https://developer.equinix.com/catalog/fabricv4) + +### Megaport +--- +#### Description + +Megaport est une plateforme mondiale leader de Network-as-a-Service (NaaS) qui permet aux entreprises de connecter rapidement leur réseau aux fournisseurs de services cloud et aux datacenters via un réseau défini par logiciel. Leurs solutions incluent : +- les Virtual Cross Connects (VXC) pour la connectivité point à point, +- le Megaport Cloud Router (MCR) pour le routage multi-cloud avancé sans matériel physique, +- le Megaport Virtual Edge (MVE) pour le déploiement de fonctions réseau virtualisées (NFV). + +Le réseau de Megaport couvre plus de 700 datacenters compatibles en Amérique du Nord, en Europe et en Asie-Pacifique, offrant une portée étendue pour les architectures hybrides et multi-cloud. + +#### Liens utiles + +- **Site web :** [megaport.com/ovhcloud](https://www.megaport.com/ecosystem/ovhcloud/) +- **Documentation :** [docs.megaport.com](https://docs.megaport.com/) +- **Documentation API :** [dev.megaport.com](https://dev.megaport.com/) + +### Orange Business Services +--- +#### Description + +Orange Business Services est la division entreprise d'Orange, l'un des principaux opérateurs de télécommunications européens. Ils fournissent des solutions réseau managées incluant SD-WAN, MPLS, internet et des services de connectivité cloud adaptés aux grandes entreprises et aux multinationales. + +Orange Business Services exploite un réseau mondial couvrant 166 pays et territoires, avec une forte présence en Europe, en Afrique et au Moyen-Orient. Leurs solutions intègrent les services WAN traditionnels avec la connectivité cloud moderne, permettant des architectures hybrides fluides. + +#### Liens utiles + +- **Site web :** [orange-business.com/en/products/galerie](https://www.orange-business.com/en/solutions/cloud/galerie) + +### Risq +--- +#### Description + +Risq est un fournisseur de services réseau basé au Québec qui propose des solutions de connectivité sécurisées et hautes performances pour les entreprises, les institutions financières et les fournisseurs de services cloud. Risq exploite un réseau de classe opérateur avec une forte présence au Québec et au Canada, proposant des on-ramps cloud directs, MPLS, internet et des services de fibre noire. + +Risq se positionne comme un partenaire de connectivité premium pour les entreprises ayant besoin d'une bande passante dédiée, d'une faible latence et de standards de sécurité et de conformité stricts, en particulier dans les secteurs réglementés et le marché canadien. + +#### Liens utiles + +- **Site web :** [risq.quebec](https://www.risq.quebec/) + +## Fonctionnement + +1. **Vous commandez** une connexion à OVHcloud via le portail du provider ou auprès d'OVHcloud (qui vous fournit une **clé d'appairage**). +2. **Le provider provisionne** le lien entre votre site et le PoP OVHcloud. +3. **Vous configurez** les paramètres BGP et VLAN de votre côté (ou le provider gère le routage Layer 3 pour vous). +4. **Le trafic circule en privé** entre votre réseau et OVHcloud via le backbone du provider. + +## Et ensuite ? + +- Consultez [Emplacements des PoPs et régions](../1.4_pop_locations_regions/guide.fr-fr.md) pour identifier où vous pouvez vous connecter +- Suivez le [Quick Start avec un Provider](../2.2_quick_start_provider/guide.fr-fr.md) pour démarrer + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/1.3_providers/meta.yaml b/pages/network/ovhcloud_connect/1.3_providers/meta.yaml new file mode 100644 index 00000000000..4d5b0dcd094 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.3_providers/meta.yaml @@ -0,0 +1,2 @@ +id: 677e01d5-f0fa-4030-a771-f74ea6be0fe8 +full_slug: network-ovhcloud-connect-providers diff --git a/pages/network/ovhcloud_connect/1.4_pop_locations_regions/guide.en-gb.md b/pages/network/ovhcloud_connect/1.4_pop_locations_regions/guide.en-gb.md new file mode 100644 index 00000000000..922fd2b2098 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.4_pop_locations_regions/guide.en-gb.md @@ -0,0 +1,126 @@ +--- +title: 'OVHcloud Connect - PoPs and Regions' +excerpt: 'Understand how OCC works with PoPs and Regions, and find out which ones are the most suitable for your infrastructure' +updated: 2026-02-18 +--- + +## Introduction + +When setting up OVHcloud Connect, you choose one or more **Points of Presence (PoP)** as the hand-off point between your network or your provider's network, and OVHcloud. Each PoP is tied to a specific geographic zone; consequently, it can only access OVHcloud regions within that same zone. + +This guide explains how OVHcloud PoPs and regions interact with OVHcloud Connect, and provides a framework for selecting the most suitable PoP for your specific infrastructure needs. + +## Understanding Regions and PoPs + +### Regions + +OVHcloud organises its infrastructure into **regions** — geographical areas where data centres and services are hosted. Each region may contain one or more PoPs where OVHcloud Connect is available. + +### Points of Presence (PoP) + +OVHcloud PoPs are located inside major carrier-neutral datacenters managed by our partners. If you are ordering a **Direct** connection, you need to be present (or arrange a circuit) in the same datacenter to install a cross-connect. + +If you are using a **Provider**, the provider handles the physical connectivity and may reach the PoP from a different facility. + +> [!primary] +> OVHcloud regularly adds new locations. Always check the [OVHcloud Connect webpage](https://www.ovhcloud.com/en-gb/network/ovhcloud-connect/) for the most up-to-date list. +> + +## How to choose a PoP + +When selecting a PoP for your OVHcloud Connect service, please consider the following: + +### 1. Proximity (latency) + +Choose the PoP that is geographically closest to your infrastructure to minimise network delay. For example, if your data centre is in Paris, a French PoP will provide the lowest latency. + +### 2. Provider availability + +If you are using OVHcloud Connect Provider, verify that your chosen provider has a presence at the PoP. Not all providers are available at every PoP. + +### 3. Redundancy + +For high-availability architectures, select **two PoPs in different locations** so that a single site failure does not take down your connection. Follow one of the resilient architecture tutorials for details: +- [On-prem](../4.2_resilient/4.1.2_onprem_resilient/guide.en-gb.md) +- [WAN](../4.2_resilient/4.2.2_wan_resilient/guide.en-gb.md) +- [AWS](../4.2_resilient/4.3.2_aws_resilient/guide.en-gb.md) +- [Azure](../4.2_resilient/4.4.2_azure_resilient/guide.en-gb.md) +- [GCP](../4.2_resilient/4.5.2_gcp_resilient/guide.en-gb.md) + +### 4. Regulatory / data residency requirements + +Some industries or countries require data to stay within a specific geography. Choose a PoP and region that comply with your data residency obligations. + +### 5. Target OVHcloud region + +To ensure the best performance, your OVHcloud Connect service should terminate in the region where your OVHcloud workloads are running (or will run). Verify that the PoP serves the region you need. + +## PoP and Region Mapping Tables + +The following tables list the regions accessible from each PoP, the corresponding low-latency OVHcloud region, and the available OCC Direct bandwidth, by geographic zone: + +> [!tabs] +> Europe +>> +>> | List of accessible regions | +>> | :--- | +>> | Germany - Limburg (`eu-west-lim`) | +>> | England - Erith (`eu-west-eri`) | +>> | France - Gravelines (`eu-west-gra`) | +>> | France - Paris (`eu-west-par`) | +>> | France - Roubaix (`eu-west-rbx`) | +>> | France - Strasbourg (`eu-west-sbg`) | +>> | Poland - Warsaw (`eu-central-waw`) | +>> +>> PoP / Low-latency Region Mapping Table +>> +>> | City | PoP | Low-latency OVHcloud Region | 1 Gbps | 10 Gbps | 100 Gbps | +>> | :--- | :--- | :--- | :--- | :--- | :--- | +>> | **Frankfurt** | Equinix - FR5 | Limburg (`eu-west-lim`) | X | X | X | +>> | **Lille** | ETIX - ETX2 | Roubaix (`eu-west-rbx`) | X | X | | +>> | **London** | Equinix - LD5 | Erith (`eu-west-eri`) | X | X | | +>> | **London** | Telehouse - West | Erith (`eu-west-eri`) | X | X | | +>> | **Madrid** | Digital Realty - MAD2 | - | X | X | | +>> | **Paris** | Equinix - PA3 | Paris (`eu-west-par`) | X | X | X | +>> | **Paris** | GlobalSwitch | Paris (`eu-west-par`) | X | X | | +>> | **Paris** | Telehouse - TH2 | Paris (`eu-west-par`) | X | X | X | +>> | **Warsaw** | Equinix - WA2 | Warsaw (`eu-central-waw`) | X | X | | +>> +> North America +>> +>> | List of accessible regions | +>> | :--- | +>> | Canada - Beauharnois (`ca-east-bhs`) | +>> | Canada - Toronto (`ca-east-tor`) | +>> +>> PoP / Low-latency Region Mapping Table +>> +>> | City | PoP | Low-latency OVHcloud Region | OCC Direct Bandwidth (Gbps) | +>> | :--- | :--- | :--- | :--- | :--- | :--- | +>> | **Montreal** | Cologix - MTL3 | Beauharnois (`ca-east-bhs`) | X | X | | +>> | **Toronto** | Equinix - TR1 | Toronto (`ca-east-tor`) | X | X | | +>> +> Asia-Pacific +>> +>> | List of accessible regions | +>> | :--- | +>> | Singapore - Singapore (`ap-southeast-sgp`) | +>> | India - Mumbai (`ap-south-mum`) | +>> +>> PoP / Low-latency Region Mapping Table +>> +>> | City | PoP | Low-latency OVHcloud Region | OCC Direct Bandwidth (Gbps) | +>> | :--- | :--- | :--- | :--- | :--- | :--- | +>> | **Mumbai** | Equinix - MB2 | Mumbai (`ap-south-mum`) | X | X | | +>> | **Singapore** | Equinix - SG1 | Singapore (`ap-southeast-sgp`) | X | X | | + +## What's next? + +- Understand [Multi-AZ](../1.5_multi_az/guide.en-gb.md) for resilient architectures +- Review [Configure OCC L3 with BGP](../3.7_occ_l3_bgp/guide.en-gb.md) for technical setup + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/1.4_pop_locations_regions/guide.fr-fr.md b/pages/network/ovhcloud_connect/1.4_pop_locations_regions/guide.fr-fr.md new file mode 100644 index 00000000000..f401aea809f --- /dev/null +++ b/pages/network/ovhcloud_connect/1.4_pop_locations_regions/guide.fr-fr.md @@ -0,0 +1,126 @@ +--- +title: 'OVHcloud Connect - PoPs et régions' +excerpt: 'Comprenez le fonctionnement d''OCC avec les PoPs et les régions, et identifiez ceux qui correspondent le mieux à votre infrastructure' +updated: 2026-02-18 +--- + +## Introduction + +Lorsque vous mettez en place OVHcloud Connect, vous choisissez un ou plusieurs **Points de présence (PoP)** comme point de raccordement entre votre réseau (ou celui de votre provider) et OVHcloud. Chaque PoP est rattaché à une zone géographique spécifique ; par conséquent, il ne peut accéder qu'aux régions OVHcloud situées dans cette même zone. + +Ce guide explique comment les PoPs et les régions OVHcloud interagissent avec OVHcloud Connect, et fournit un cadre pour sélectionner le PoP le plus adapté aux besoins spécifiques de votre infrastructure. + +## Comprendre les régions et les PoPs + +### Régions + +OVHcloud organise son infrastructure en **régions** — des zones géographiques où sont hébergés les datacenters et les services. Chaque région peut contenir un ou plusieurs PoPs où OVHcloud Connect est disponible. + +### Points de présence (PoP) + +Les PoPs OVHcloud sont situés dans des datacenters majeurs, neutres vis-à-vis des opérateurs, gérés par nos partenaires. Si vous commandez une connexion **Direct**, vous devez être présent (ou organiser un circuit) dans le même datacenter pour installer un cross-connect. + +Si vous utilisez un **Provider**, ce dernier prend en charge la connectivité physique et peut atteindre le PoP depuis un autre site. + +> [!primary] +> OVHcloud ajoute régulièrement de nouveaux emplacements. Consultez toujours la [page web OVHcloud Connect](https://www.ovhcloud.com/en-gb/network/ovhcloud-connect/) pour disposer de la liste la plus à jour. +> + +## Comment choisir un PoP + +Lors de la sélection d'un PoP pour votre service OVHcloud Connect, prenez en compte les éléments suivants : + +### 1. Proximité (latence) + +Choisissez le PoP géographiquement le plus proche de votre infrastructure pour minimiser le délai réseau. Par exemple, si votre datacenter est à Paris, un PoP français offrira la latence la plus faible. + +### 2. Disponibilité du provider + +Si vous utilisez OVHcloud Connect Provider, vérifiez que le provider choisi est présent au PoP. Tous les providers ne sont pas disponibles dans chaque PoP. + +### 3. Redondance + +Pour les architectures à haute disponibilité, sélectionnez **deux PoPs situés à des emplacements distincts** afin qu'une défaillance d'un site unique ne mette pas votre connexion hors service. Suivez l'un des tutoriels d'architecture résiliente pour plus de détails : +- [On-prem](../4.2_resilient/4.1.2_onprem_resilient/guide.fr-fr.md) +- [WAN](../4.2_resilient/4.2.2_wan_resilient/guide.fr-fr.md) +- [AWS](../4.2_resilient/4.3.2_aws_resilient/guide.fr-fr.md) +- [Azure](../4.2_resilient/4.4.2_azure_resilient/guide.fr-fr.md) +- [GCP](../4.2_resilient/4.5.2_gcp_resilient/guide.fr-fr.md) + +### 4. Exigences réglementaires / résidence des données + +Certains secteurs ou pays exigent que les données restent dans une zone géographique spécifique. Choisissez un PoP et une région conformes à vos obligations de résidence des données. + +### 5. Région OVHcloud cible + +Pour garantir les meilleures performances, votre service OVHcloud Connect doit aboutir dans la région où s'exécutent (ou s'exécuteront) vos workloads OVHcloud. Vérifiez que le PoP dessert la région dont vous avez besoin. + +## Tableaux de correspondance PoP / région + +Les tableaux suivants listent les régions accessibles depuis chaque PoP, la région OVHcloud à faible latence correspondante, ainsi que la bande passante OCC Direct disponible, par zone géographique : + +> [!tabs] +> Europe +>> +>> | Liste des régions accessibles | +>> | :--- | +>> | Allemagne - Limburg (`eu-west-lim`) | +>> | Angleterre - Erith (`eu-west-eri`) | +>> | France - Gravelines (`eu-west-gra`) | +>> | France - Paris (`eu-west-par`) | +>> | France - Roubaix (`eu-west-rbx`) | +>> | France - Strasbourg (`eu-west-sbg`) | +>> | Pologne - Varsovie (`eu-central-waw`) | +>> +>> Tableau de correspondance PoP / région à faible latence +>> +>> | Ville | PoP | Région OVHcloud à faible latence | 1 Gbps | 10 Gbps | 100 Gbps | +>> | :--- | :--- | :--- | :--- | :--- | :--- | +>> | **Francfort** | Equinix - FR5 | Limburg (`eu-west-lim`) | X | X | X | +>> | **Lille** | ETIX - ETX2 | Roubaix (`eu-west-rbx`) | X | X | | +>> | **Londres** | Equinix - LD5 | Erith (`eu-west-eri`) | X | X | | +>> | **Londres** | Telehouse - West | Erith (`eu-west-eri`) | X | X | | +>> | **Madrid** | Digital Realty - MAD2 | - | X | X | | +>> | **Paris** | Equinix - PA3 | Paris (`eu-west-par`) | X | X | X | +>> | **Paris** | GlobalSwitch | Paris (`eu-west-par`) | X | X | | +>> | **Paris** | Telehouse - TH2 | Paris (`eu-west-par`) | X | X | X | +>> | **Varsovie** | Equinix - WA2 | Varsovie (`eu-central-waw`) | X | X | | +>> +> Amérique du Nord +>> +>> | Liste des régions accessibles | +>> | :--- | +>> | Canada - Beauharnois (`ca-east-bhs`) | +>> | Canada - Toronto (`ca-east-tor`) | +>> +>> Tableau de correspondance PoP / région à faible latence +>> +>> | Ville | PoP | Région OVHcloud à faible latence | Bande passante OCC Direct (Gbps) | +>> | :--- | :--- | :--- | :--- | :--- | :--- | +>> | **Montréal** | Cologix - MTL3 | Beauharnois (`ca-east-bhs`) | X | X | | +>> | **Toronto** | Equinix - TR1 | Toronto (`ca-east-tor`) | X | X | | +>> +> Asie-Pacifique +>> +>> | Liste des régions accessibles | +>> | :--- | +>> | Singapour - Singapour (`ap-southeast-sgp`) | +>> | Inde - Mumbai (`ap-south-mum`) | +>> +>> Tableau de correspondance PoP / région à faible latence +>> +>> | Ville | PoP | Région OVHcloud à faible latence | Bande passante OCC Direct (Gbps) | +>> | :--- | :--- | :--- | :--- | :--- | :--- | +>> | **Mumbai** | Equinix - MB2 | Mumbai (`ap-south-mum`) | X | X | | +>> | **Singapour** | Equinix - SG1 | Singapour (`ap-southeast-sgp`) | X | X | | + +## Et ensuite ? + +- Comprenez le [Multi-AZ](../1.5_multi_az/guide.fr-fr.md) pour les architectures résilientes +- Consultez [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp/guide.fr-fr.md) pour la mise en place technique + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/1.4_pop_locations_regions/meta.yaml b/pages/network/ovhcloud_connect/1.4_pop_locations_regions/meta.yaml new file mode 100644 index 00000000000..aff77f684d8 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.4_pop_locations_regions/meta.yaml @@ -0,0 +1,2 @@ +id: f09a2b66-b42c-46f3-b291-46cb3e4a05f1 +full_slug: network-ovhcloud-connect-pop-locations-regions diff --git a/pages/network/ovhcloud_connect/1.5_multi_az/guide.en-gb.md b/pages/network/ovhcloud_connect/1.5_multi_az/guide.en-gb.md new file mode 100644 index 00000000000..0b01b5034e6 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.5_multi_az/guide.en-gb.md @@ -0,0 +1,57 @@ +--- +title: 'Multi-AZ architectures for OVHcloud Connect' +excerpt: 'Understand how Multi-AZ architectures enhance resilience for OVHcloud Connect' +updated: 2026-02-18 +--- + +## Objective + +**Multi-AZ (Multiple Availability Zones)** is an architecture strategy where your resources and network connections are distributed across two or more physically separated data centres (Availability Zones) within a region. This protects against the failure of a single site. + +## Why Multi-AZ matters for OVHcloud Connect + +A single OVHcloud Connect link through a single PoP is a **single point of failure**. If that PoP, the cross-connect, or the physical link experiences an outage, your private connectivity is lost. + +Multi-AZ designs address this by establishing **redundant connections through different PoPs or Availability Zones**, so that traffic can automatically reroute if one path fails. + +## Architecture Overview + +![Multi AZ architecture](image.png) + +## How Multi-AZ works with OVHcloud Connect + +1. **Order two OVHcloud Connect services** in two **different PoPs**. +2. **Configure BGP on both links** with appropriate route priorities (using BGP attributes like Local Preference, MED, or AS-path prepending) so that traffic prefers one path but can fall back to the other. +3. **Distribute your OVHcloud resources** across multiple Availability Zones within the same region. +4. **Test failover** by simulating a link outage and verifying that traffic switches to the backup path. + +## Multi-AZ and BGP configuration + +For automatic failover, your BGP configuration must distinguish between the primary and backup paths. Common approaches: + +- **Local Preference** — Set a higher Local Preference on routes learned from the primary link. +- **AS-path prepending** — Make the backup path's AS-path longer so it is less preferred. +- **MED (Multi-Exit Discriminator)** — Use MED values to influence inbound routing from OVHcloud. + +See [Configure OCC L3 with BGP](../3.7_occ_l3_bgp/guide.en-gb.md) for detailed configuration guidance. + +## When to use Multi-AZ + +| Scenario | Recommendation | +|---|---| +| Test / development workloads | Single connection is usually sufficient | +| Non-critical production | Single connection with monitoring | +| Business-critical production | **Multi-AZ recommended** | +| Regulated / compliance workloads | **Multi-AZ required** | + +## What's next? + +- Learn about [SLAs](../1.7_slas/guide.en-gb.md) and how Multi-AZ affects your uptime guarantees +- See the [AZ configuration guide](../3.6_vrack_network_setup/guide.en-gb.md) to set up subnets across zones +- Explore [resilient architecture tutorials](../4.2_resilient/4.1.2_onprem_resilient/guide.en-gb.md) for step-by-step examples + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/1.5_multi_az/guide.fr-fr.md b/pages/network/ovhcloud_connect/1.5_multi_az/guide.fr-fr.md new file mode 100644 index 00000000000..5612f0df483 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.5_multi_az/guide.fr-fr.md @@ -0,0 +1,57 @@ +--- +title: 'Architectures Multi-AZ pour OVHcloud Connect' +excerpt: 'Comprenez comment les architectures Multi-AZ renforcent la résilience d''OVHcloud Connect' +updated: 2026-02-18 +--- + +## Objectif + +Le **Multi-AZ (Multiple Availability Zones)** est une stratégie d'architecture où vos ressources et connexions réseau sont réparties sur deux datacenters physiquement séparés ou plus (Availability Zones) au sein d'une région. Cela protège contre la défaillance d'un site unique. + +## Pourquoi le Multi-AZ est important pour OVHcloud Connect + +Un lien OVHcloud Connect unique passant par un seul PoP constitue un **point unique de défaillance**. Si ce PoP, le cross-connect ou le lien physique subit une panne, votre connectivité privée est perdue. + +Les architectures Multi-AZ répondent à cela en établissant des **connexions redondantes via différents PoPs ou Availability Zones**, afin que le trafic puisse être automatiquement réacheminé en cas de défaillance d'un chemin. + +## Vue d'ensemble de l'architecture + +![Architecture Multi-AZ](image.png) + +## Comment fonctionne le Multi-AZ avec OVHcloud Connect + +1. **Commandez deux services OVHcloud Connect** dans deux **PoPs différents**. +2. **Configurez BGP sur les deux liens** avec les priorités de routes appropriées (en utilisant des attributs BGP comme la Local Preference, le MED ou l'AS-path prepending) afin que le trafic privilégie un chemin tout en pouvant basculer sur l'autre. +3. **Répartissez vos ressources OVHcloud** sur plusieurs Availability Zones au sein de la même région. +4. **Testez le basculement** en simulant une coupure de lien et en vérifiant que le trafic bascule sur le chemin de secours. + +## Multi-AZ et configuration BGP + +Pour un basculement automatique, votre configuration BGP doit distinguer le chemin principal du chemin de secours. Approches courantes : + +- **Local Preference** — Définissez une Local Preference plus élevée sur les routes apprises depuis le lien principal. +- **AS-path prepending** — Allongez l'AS-path du chemin de secours pour qu'il soit moins privilégié. +- **MED (Multi-Exit Discriminator)** — Utilisez les valeurs MED pour influencer le routage entrant depuis OVHcloud. + +Consultez [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp/guide.fr-fr.md) pour des instructions de configuration détaillées. + +## Quand utiliser le Multi-AZ + +| Scénario | Recommandation | +|---|---| +| Workloads de test / développement | Une connexion unique est généralement suffisante | +| Production non critique | Connexion unique avec supervision | +| Production critique pour l'activité | **Multi-AZ recommandé** | +| Workloads réglementés / soumis à conformité | **Multi-AZ requis** | + +## Et ensuite ? + +- Découvrez les [SLAs](../1.7_slas/guide.fr-fr.md) et l'impact du Multi-AZ sur vos garanties de disponibilité +- Consultez le [guide de configuration des AZ](../3.6_vrack_network_setup/guide.fr-fr.md) pour mettre en place des sous-réseaux entre zones +- Explorez les [tutoriels d'architectures résilientes](../4.2_resilient/4.1.2_onprem_resilient/guide.fr-fr.md) pour des exemples pas à pas + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/1.5_multi_az/image.png b/pages/network/ovhcloud_connect/1.5_multi_az/image.png new file mode 100644 index 00000000000..f087aae8768 Binary files /dev/null and b/pages/network/ovhcloud_connect/1.5_multi_az/image.png differ diff --git a/pages/network/ovhcloud_connect/1.5_multi_az/meta.yaml b/pages/network/ovhcloud_connect/1.5_multi_az/meta.yaml new file mode 100644 index 00000000000..19a1fb4a55c --- /dev/null +++ b/pages/network/ovhcloud_connect/1.5_multi_az/meta.yaml @@ -0,0 +1,2 @@ +id: 88c8c515-e98a-4cd7-9ec5-ae3ae5e89cdc +full_slug: network-ovhcloud-connect-multi-az diff --git a/pages/network/ovhcloud_connect/1.6_automation/guide.en-gb.md b/pages/network/ovhcloud_connect/1.6_automation/guide.en-gb.md new file mode 100644 index 00000000000..f1f3e4f745d --- /dev/null +++ b/pages/network/ovhcloud_connect/1.6_automation/guide.en-gb.md @@ -0,0 +1,113 @@ +--- +title: 'Automate OVHcloud Connect with API, CLI, and Terraform' +excerpt: 'Discover how to manage OVHcloud Connect programmatically using the API, CLI, and Terraform' +updated: 2026-02-18 +--- + +## Objective + +OVHcloud Connect can be managed programmatically using the OVHcloud API, command-line tools, and Terraform. Automation reduces manual errors, speeds up provisioning, and makes your infrastructure repeatable and version-controlled. + +## OVHcloud API + +The OVHcloud API provides RESTful endpoints for all OVHcloud Connect operations: ordering, configuring, monitoring, and cancelling connections. + +**API Console:** [https://eu.api.ovh.com/console/?section=%2FovhCloudConnect&branch=v1](https://eu.api.ovh.com/console/?section=%2FovhCloudConnect&branch=v1) + +### Key API endpoints + +| Endpoint | Description | +|---|---| +| `GET /ovhCloudConnect` | List all your OVHcloud Connect services | +| `GET /ovhCloudConnect/{serviceName}` | Get details of a specific service | +| `GET /ovhCloudConnect/{serviceName}/config/pop` | List PoP configurations | +| `POST /ovhCloudConnect/{serviceName}/config/pop` | Create a new PoP configuration | +| `GET /ovhCloudConnect/{serviceName}/serviceInfos` | Get service metadata and billing info | + +### Getting started with the API + +1. **Create API credentials** — Go to [https://eu.api.ovh.com/createToken/](https://eu.api.ovh.com/createToken/) and generate an Application Key, Application Secret, and Consumer Key. +2. **Choose an SDK** — OVHcloud provides official API wrappers in multiple languages: + - **Python:** [github.com/ovh/python-ovh](https://github.com/ovh/python-ovh) + - **Node.js:** [github.com/ovh/node-ovh](https://github.com/ovh/node-ovh) + - **Go:** [github.com/ovh/go-ovh](https://github.com/ovh/go-ovh) + - **PHP:** [github.com/ovh/php-ovh](https://github.com/ovh/php-ovh) + - **C#:** [github.com/ovh/csharp-ovh](https://github.com/ovh/csharp-ovh) +3. **Make your first call** — Example in Python: + +```python +import ovh + +client = ovh.Client( + endpoint='ovh-eu', + # Configure via environment variables or ovh.conf file: + # OVH_APPLICATION_KEY, OVH_APPLICATION_SECRET, OVH_CONSUMER_KEY +) + +# List all OVHcloud Connect services +services = client.get('/ovhCloudConnect') +print(services) +``` + +> **Security tip:** Never hard-code your API credentials. Use environment variables, a configuration file (`ovh.conf`), or a secrets manager (e.g. HashiCorp Vault, CI/CD secrets). + +## Command-Line Interface (CLI) + +While there is no dedicated OVHcloud CLI binary for OVHcloud Connect, you can use the API wrappers in a scripting context or build lightweight CLI scripts using the SDKs above. + +Example: a quick bash script using `curl` and the OVHcloud API signing mechanism: + +```bash +# Simplified example — use an SDK for proper signature handling +curl -X GET \ + -H "X-Ovh-Application: YOUR_APP_KEY" \ + -H "X-Ovh-Consumer: YOUR_CONSUMER_KEY" \ + -H "X-Ovh-Timestamp: $(date +%s)" \ + -H "X-Ovh-Signature: \$1\$..." \ + "https://eu.api.ovh.com/1.0/ovhCloudConnect" +``` + +> In practice, using the Python or Node.js SDK is much simpler than manual signing. + +## Terraform + +Terraform allows you to define your OVHcloud Connect infrastructure as code. This is ideal for repeatable deployments, version control, and collaboration. + +### OVH Terraform Provider + +- **Terraform Registry:** [registry.terraform.io/providers/ovh/ovh](https://registry.terraform.io/providers/ovh/ovh/latest) +- **GitHub:** [github.com/ovh/terraform-provider-ovh](https://github.com/ovh/terraform-provider-ovh) + +### Example Terraform configuration + +```hcl +terraform { + required_providers { + ovh = { + source = "ovh/ovh" + version = ">= 2.7.0" + } + } +} + +provider "ovh" { + endpoint = "ovh-eu" + # Credentials from environment variables: + # OVH_APPLICATION_KEY, OVH_APPLICATION_SECRET, OVH_CONSUMER_KEY +} + +# Example: Associate an OVHcloud Connect service with a vRack +# Check the Terraform Registry for exact resource names and attributes +resource "ovh_vrack_ovhcloudconnect" "my_connect" { + service_name = "vrack-abc123" + ovh_cloud_connect = "ovhcloudconnect-xyz789" +} +``` + +> **Note:** Resource names and attributes may change between provider versions. Always refer to the [Terraform Registry documentation](https://registry.terraform.io/providers/ovh/ovh/latest/docs) for the latest resource definitions. + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/1.6_automation/guide.fr-fr.md b/pages/network/ovhcloud_connect/1.6_automation/guide.fr-fr.md new file mode 100644 index 00000000000..d2ee8ecd45f --- /dev/null +++ b/pages/network/ovhcloud_connect/1.6_automation/guide.fr-fr.md @@ -0,0 +1,113 @@ +--- +title: 'Automatiser OVHcloud Connect avec l''API, la CLI et Terraform' +excerpt: 'Découvrez comment administrer OVHcloud Connect de manière programmatique via l''API, la CLI et Terraform' +updated: 2026-02-18 +--- + +## Objectif + +OVHcloud Connect peut être administré de manière programmatique via l'API OVHcloud, des outils en ligne de commande et Terraform. L'automatisation réduit les erreurs manuelles, accélère le provisionnement et rend votre infrastructure reproductible et versionnée. + +## API OVHcloud + +L'API OVHcloud fournit des endpoints RESTful pour toutes les opérations OVHcloud Connect : commande, configuration, supervision et résiliation des connexions. + +**Console API :** [https://eu.api.ovh.com/console/?section=%2FovhCloudConnect&branch=v1](https://eu.api.ovh.com/console/?section=%2FovhCloudConnect&branch=v1) + +### Principaux endpoints API + +| Endpoint | Description | +|---|---| +| `GET /ovhCloudConnect` | Lister tous vos services OVHcloud Connect | +| `GET /ovhCloudConnect/{serviceName}` | Obtenir les détails d'un service spécifique | +| `GET /ovhCloudConnect/{serviceName}/config/pop` | Lister les configurations de PoPs | +| `POST /ovhCloudConnect/{serviceName}/config/pop` | Créer une nouvelle configuration de PoP | +| `GET /ovhCloudConnect/{serviceName}/serviceInfos` | Obtenir les métadonnées du service et les informations de facturation | + +### Premiers pas avec l'API + +1. **Créez des identifiants API** — Rendez-vous sur [https://eu.api.ovh.com/createToken/](https://eu.api.ovh.com/createToken/) et générez une Application Key, une Application Secret et une Consumer Key. +2. **Choisissez un SDK** — OVHcloud propose des wrappers d'API officiels dans plusieurs langages : + - **Python :** [github.com/ovh/python-ovh](https://github.com/ovh/python-ovh) + - **Node.js :** [github.com/ovh/node-ovh](https://github.com/ovh/node-ovh) + - **Go :** [github.com/ovh/go-ovh](https://github.com/ovh/go-ovh) + - **PHP :** [github.com/ovh/php-ovh](https://github.com/ovh/php-ovh) + - **C# :** [github.com/ovh/csharp-ovh](https://github.com/ovh/csharp-ovh) +3. **Effectuez votre premier appel** — Exemple en Python : + +```python +import ovh + +client = ovh.Client( + endpoint='ovh-eu', + # Configure via environment variables or ovh.conf file: + # OVH_APPLICATION_KEY, OVH_APPLICATION_SECRET, OVH_CONSUMER_KEY +) + +# List all OVHcloud Connect services +services = client.get('/ovhCloudConnect') +print(services) +``` + +> **Conseil de sécurité :** ne codez jamais en dur vos identifiants API. Utilisez des variables d'environnement, un fichier de configuration (`ovh.conf`) ou un gestionnaire de secrets (par exemple HashiCorp Vault, secrets CI/CD). + +## Interface en ligne de commande (CLI) + +Bien qu'il n'existe pas de binaire CLI OVHcloud dédié à OVHcloud Connect, vous pouvez utiliser les wrappers d'API dans un contexte de scripting ou créer des scripts CLI légers à l'aide des SDKs ci-dessus. + +Exemple : un rapide script bash utilisant `curl` et le mécanisme de signature de l'API OVHcloud : + +```bash +# Simplified example — use an SDK for proper signature handling +curl -X GET \ + -H "X-Ovh-Application: YOUR_APP_KEY" \ + -H "X-Ovh-Consumer: YOUR_CONSUMER_KEY" \ + -H "X-Ovh-Timestamp: $(date +%s)" \ + -H "X-Ovh-Signature: \$1\$..." \ + "https://eu.api.ovh.com/1.0/ovhCloudConnect" +``` + +> En pratique, utiliser le SDK Python ou Node.js est bien plus simple que de gérer la signature manuellement. + +## Terraform + +Terraform vous permet de définir votre infrastructure OVHcloud Connect en tant que code. C'est idéal pour des déploiements reproductibles, le versioning et la collaboration. + +### Provider Terraform OVH + +- **Terraform Registry :** [registry.terraform.io/providers/ovh/ovh](https://registry.terraform.io/providers/ovh/ovh/latest) +- **GitHub :** [github.com/ovh/terraform-provider-ovh](https://github.com/ovh/terraform-provider-ovh) + +### Exemple de configuration Terraform + +```hcl +terraform { + required_providers { + ovh = { + source = "ovh/ovh" + version = ">= 2.7.0" + } + } +} + +provider "ovh" { + endpoint = "ovh-eu" + # Credentials from environment variables: + # OVH_APPLICATION_KEY, OVH_APPLICATION_SECRET, OVH_CONSUMER_KEY +} + +# Example: Associate an OVHcloud Connect service with a vRack +# Check the Terraform Registry for exact resource names and attributes +resource "ovh_vrack_ovhcloudconnect" "my_connect" { + service_name = "vrack-abc123" + ovh_cloud_connect = "ovhcloudconnect-xyz789" +} +``` + +> **Remarque :** les noms de ressources et attributs peuvent évoluer entre les versions du provider. Référez-vous toujours à la [documentation du Terraform Registry](https://registry.terraform.io/providers/ovh/ovh/latest/docs) pour les définitions de ressources les plus récentes. + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/1.6_automation/meta.yaml b/pages/network/ovhcloud_connect/1.6_automation/meta.yaml new file mode 100644 index 00000000000..688b10bd92b --- /dev/null +++ b/pages/network/ovhcloud_connect/1.6_automation/meta.yaml @@ -0,0 +1,2 @@ +id: 049270ed-dc6a-434a-9c92-db96880639b3 +full_slug: network-ovhcloud-connect-automation diff --git a/pages/network/ovhcloud_connect/1.7_slas/guide.en-gb.md b/pages/network/ovhcloud_connect/1.7_slas/guide.en-gb.md new file mode 100644 index 00000000000..2de6995de81 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.7_slas/guide.en-gb.md @@ -0,0 +1,72 @@ +--- +title: 'OVHcloud Connect - SLAs' +excerpt: 'Learn about the Service Level Agreements for OVHcloud Connect and how to achieve higher availability' +updated: 2026-02-18 +--- + +## Objective + +A **Service Level Agreement (SLA)** is a contractual commitment from OVHcloud that defines the guaranteed level of service for OVHcloud Connect. SLAs give you confidence that your connection will meet specific performance and availability targets. + +## What the SLA covers + +OVHcloud Connect SLAs typically address the following areas: + +| Area | What it means | +|---|---| +| **Availability (uptime)** | The percentage of time the service is operational over a given period (e.g. 99.9% monthly uptime). | +| **Latency** | The maximum acceptable delay for traffic traversing the OVHcloud Connect link. | +| **Support response time** | How quickly OVHcloud acknowledges and begins working on a reported issue. | +| **Resolution time** | The target timeframe for restoring service after an incident. | + +## SLA levels and connection type + +The level of SLA you can achieve depends on your architecture: + +| Architecture | Typical availability | Notes | +|---|---|---| +| **Single connection** (one PoP, one link) | Up to 99.9% | Covers the OVHcloud-managed portion of the link. A single physical path remains a point of failure. | +| **Redundant connections** (Multi-AZ, two PoPs) | Up to 99.99% | Multiple independent paths protect against single-link and single-site failures. Higher SLA tiers may apply. | +| **Provider connection** | Varies | The end-to-end SLA depends on both OVHcloud's SLA and your provider's SLA. Check both. | + +> **Important:** SLA guarantees apply to the OVHcloud-managed portion of the service. Third-party elements (your router, provider links, cross-connects managed by data centre operators) are not covered under OVHcloud's SLA. + +## SLA prerequisites + +For the SLA to be valid, you must: + +1. **Follow OVHcloud's configuration guidelines** — Incorrect BGP configuration or unsupported setups may void the SLA. +2. **Report incidents promptly** — Use the official support channels (see [Declare and follow up upon an incident](../3.10_incident_followup/guide.en-gb.md)). +3. **Accept scheduled maintenance** — OVHcloud may perform maintenance windows. Downtime during announced maintenance is typically excluded from SLA calculations. +4. **Use a supported architecture** — Higher SLA tiers require redundant connections. A single connection cannot claim the 99.99% SLA. + +## Remedies and service credits + +If OVHcloud fails to meet the SLA targets, you may be entitled to: + +- **Service credits** — A percentage of your monthly fee credited back to your account, proportional to the downtime experienced. +- **Priority support** — Accelerated handling for unresolved issues. + +The exact credit calculation and claim process are described in the OVHcloud Connect specific conditions, available in your contract or on the OVHcloud website. + +## Monitoring SLA compliance + +To track whether your connection meets the SLA: + +- Use the **OVHcloud Control Panel** to view connection status, uptime, and historical metrics. +- Set up **alerts** for link-down events, BGP session drops, and latency spikes. +- Use the **OVHcloud API** to query status programmatically and integrate with your monitoring tools. + +See [Monitor your OVHcloud Connect](../3.9_monitor/guide.en-gb.md) for detailed monitoring guidance. + +## What's next? + +- Review [Prerequisites & Limitations](../1.8_prerequisites_limitations/guide.en-gb.md) +- Set up [monitoring](../3.9_monitor/guide.en-gb.md) for your connection +- Learn how to [declare and follow up on incidents](../3.10_incident_followup/guide.en-gb.md) + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/1.7_slas/guide.fr-fr.md b/pages/network/ovhcloud_connect/1.7_slas/guide.fr-fr.md new file mode 100644 index 00000000000..a70259cfeec --- /dev/null +++ b/pages/network/ovhcloud_connect/1.7_slas/guide.fr-fr.md @@ -0,0 +1,72 @@ +--- +title: 'OVHcloud Connect - SLAs' +excerpt: 'Découvrez les Service Level Agreements d''OVHcloud Connect et comment atteindre une plus haute disponibilité' +updated: 2026-02-18 +--- + +## Objectif + +Un **Service Level Agreement (SLA)** est un engagement contractuel d'OVHcloud qui définit le niveau de service garanti pour OVHcloud Connect. Les SLAs vous donnent l'assurance que votre connexion atteindra des objectifs de performance et de disponibilité spécifiques. + +## Ce que couvre le SLA + +Les SLAs OVHcloud Connect portent généralement sur les domaines suivants : + +| Domaine | Signification | +|---|---| +| **Disponibilité (uptime)** | Le pourcentage de temps pendant lequel le service est opérationnel sur une période donnée (par exemple 99,9 % de disponibilité mensuelle). | +| **Latence** | Le délai maximal acceptable pour le trafic traversant le lien OVHcloud Connect. | +| **Délai de réponse du support** | La rapidité avec laquelle OVHcloud accuse réception d'un incident signalé et commence à le traiter. | +| **Temps de résolution** | L'objectif de délai pour rétablir le service après un incident. | + +## Niveaux de SLA et type de connexion + +Le niveau de SLA que vous pouvez atteindre dépend de votre architecture : + +| Architecture | Disponibilité typique | Remarques | +|---|---|---| +| **Connexion unique** (un PoP, un lien) | Jusqu'à 99,9 % | Couvre la portion du lien gérée par OVHcloud. Un chemin physique unique reste un point de défaillance. | +| **Connexions redondantes** (Multi-AZ, deux PoPs) | Jusqu'à 99,99 % | Plusieurs chemins indépendants protègent contre les défaillances d'un lien unique et d'un site unique. Des paliers SLA supérieurs peuvent s'appliquer. | +| **Connexion via Provider** | Variable | Le SLA de bout en bout dépend à la fois du SLA d'OVHcloud et de celui de votre provider. Vérifiez les deux. | + +> **Important :** les garanties SLA s'appliquent à la portion du service gérée par OVHcloud. Les éléments tiers (votre routeur, les liens du provider, les cross-connects gérés par les opérateurs de datacenters) ne sont pas couverts par le SLA d'OVHcloud. + +## Prérequis du SLA + +Pour que le SLA soit valide, vous devez : + +1. **Suivre les recommandations de configuration d'OVHcloud** — Une configuration BGP incorrecte ou un montage non pris en charge peut invalider le SLA. +2. **Signaler les incidents rapidement** — Utilisez les canaux de support officiels (consultez [Déclarer un incident et en assurer le suivi](../3.10_incident_followup/guide.fr-fr.md)). +3. **Accepter les maintenances planifiées** — OVHcloud peut effectuer des fenêtres de maintenance. L'indisponibilité durant les maintenances annoncées est généralement exclue du calcul du SLA. +4. **Utiliser une architecture prise en charge** — Les paliers SLA supérieurs nécessitent des connexions redondantes. Une connexion unique ne peut prétendre au SLA de 99,99 %. + +## Recours et avoirs de service + +Si OVHcloud ne respecte pas les objectifs SLA, vous pouvez avoir droit à : + +- **Des avoirs de service** — Un pourcentage de votre redevance mensuelle crédité sur votre compte, proportionnel à l'indisponibilité constatée. +- **Un support prioritaire** — Un traitement accéléré pour les incidents non résolus. + +Le calcul exact des avoirs et la procédure de réclamation sont décrits dans les conditions particulières OVHcloud Connect, disponibles dans votre contrat ou sur le site web d'OVHcloud. + +## Suivi de la conformité au SLA + +Pour suivre le respect du SLA par votre connexion : + +- Utilisez l'**espace client OVHcloud** pour consulter le statut de la connexion, la disponibilité et les métriques historiques. +- Mettez en place des **alertes** pour les événements de coupure de lien, les chutes de session BGP et les pics de latence. +- Utilisez l'**API OVHcloud** pour interroger le statut de manière programmatique et l'intégrer à vos outils de supervision. + +Consultez [Superviser votre OVHcloud Connect](../3.9_monitor/guide.fr-fr.md) pour des conseils détaillés sur la supervision. + +## Et ensuite ? + +- Consultez [Prérequis et limitations](../1.8_prerequisites_limitations/guide.fr-fr.md) +- Mettez en place la [supervision](../3.9_monitor/guide.fr-fr.md) de votre connexion +- Apprenez à [déclarer un incident et en assurer le suivi](../3.10_incident_followup/guide.fr-fr.md) + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/1.7_slas/meta.yaml b/pages/network/ovhcloud_connect/1.7_slas/meta.yaml new file mode 100644 index 00000000000..c174ef683a3 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.7_slas/meta.yaml @@ -0,0 +1,2 @@ +id: 52a47331-b444-4c21-8d82-ff11073bfad4 +full_slug: network-ovhcloud-connect-slas diff --git a/pages/network/ovhcloud_connect/1.8_prerequisites_limitations/guide.en-gb.md b/pages/network/ovhcloud_connect/1.8_prerequisites_limitations/guide.en-gb.md new file mode 100644 index 00000000000..00ec20c7ef0 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.8_prerequisites_limitations/guide.en-gb.md @@ -0,0 +1,110 @@ +--- +title: 'OVHcloud Connect - Prerequisites & Limitations' +excerpt: 'Review the requirements and current limitations before ordering OVHcloud Connect' +updated: 2026-02-18 +--- + +## Objective + +Before ordering OVHcloud Connect, review the requirements below to ensure your environment is ready. Also be aware of the current limitations to plan your implementation effectively. + +## General + +### Requirements + +- A valid **OVHcloud account** with billing set up. +- Sufficient permissions to manage network services (Network / vRack). +- A **vRack** service provisioned (or ready to be created) to associate with OVHcloud Connect. +- You (or your network team) should be familiar with basic IP networking (subnets, routing), BGP concepts, VLAN configuration + +> **Tip:** If you are not comfortable with BGP or network configuration, consider working with a managed service provider or engaging OVHcloud Professional Services. + +### Limits + +- An OVHcloud Connect service can be associated to one vRack only. +- Maximum number of OVHcloud Connect services per PoP and per vRack: 16. +- Maximum MTU (Jumbo frame): up to 9000 bytes + +## OVHcloud Connect Direct + +### Requirements + +#### Administrative requirements + +- Access to a **co-location facility** where OVHcloud has a PoP (see [PoP Locations & Regions](../1.4_pop_locations_regions/guide.en-gb.md)). +- Ability to order a **cross-connect** inside the data centre (or arrange one through the facility operator). + +#### Technical requirements + +- Your equipment interface should be supported (refer to below table). + +| Bandwidth | Interface Type | +|---|---| +| 1 Gb | 1000Base-LX/LH | +| 10 Gb | 10GBase-LR | +| 100 Gb | 100GBase-LR4 | + +- Auto-negotiation shall be disabled (not supported). + +### Limits + +#### Layer 2 mode + +- The number of client-side MAC addresses is limited to 512 per port. +- The maximum bandwidth is 10Gb per port. +- Only one OVHcloud Connect Direct Layer 2 can be attached per vRack. + - This mode does not allow to deploy redundant PoP architectures. + - You may deploy redundant links in the same PoP by enabling LACP. + +- The following features are not supported: + - 802.1p CoS-based + - DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) + - TRILL, SPF and FabricPath + - FCoE + - Spanning Tree + - IGMP and Multicast + - EtherChannel, PaGP for aggregation + +#### Layer 3 mode + +If you chose an OVHcloud Connect Direct Layer 3, please read the [Layer 3 section](#id-l3) below. + +## OVHcloud Connect Provider + +### Requirements + +- A contract with a **supported provider** (see [Providers](../1.3_providers/guide.en-gb.md)). +- The provider must have a presence at your chosen OVHcloud PoP. + +### Limits + +#### Layer 3 mode + +OVHcloud Connect Provider is always a Layer 3 network service: please read the [Layer 3 section](#id-l3) below. + +## Layer 3 mode + +### Limits + +- Maximum one BGP session between your equipment and the OVHcloud Point of Presence router (no eBGP Multihop). More details in the [Configure OCC L3 with BGP](../3.7_occ_l3_bgp/guide.en-gb.md). +- Each Availability Zone supports up to 4 BGP peers. More details in the [Set up your vRack network](../3.6_vrack_network_setup/guide.en-gb.md). +- Up to 100 prefixes can be announced per BGP session. + +- The following features are not supported: + - IPv6 + - Any QoS mechanism + - 802.1q tag + - Multi-VRF + - eBGP Multi-Hop + - iBGP + - Static routing in PoP configuration + +## What's next? + +- Jump to the [Quick Start: Direct Connection](../2.1_quick_start_direct/guide.en-gb.md) or [Quick Start: Provider Connection](../2.2_quick_start_provider/guide.en-gb.md) + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/1.8_prerequisites_limitations/guide.fr-fr.md b/pages/network/ovhcloud_connect/1.8_prerequisites_limitations/guide.fr-fr.md new file mode 100644 index 00000000000..d398a82e606 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.8_prerequisites_limitations/guide.fr-fr.md @@ -0,0 +1,110 @@ +--- +title: 'OVHcloud Connect - Prérequis et limitations' +excerpt: 'Vérifiez les exigences et les limitations actuelles avant de commander OVHcloud Connect' +updated: 2026-02-18 +--- + +## Objectif + +Avant de commander OVHcloud Connect, passez en revue les exigences ci-dessous pour vous assurer que votre environnement est prêt. Tenez également compte des limitations actuelles afin de planifier efficacement votre mise en œuvre. + +## Général + +### Prérequis + +- Un **compte OVHcloud** valide avec une facturation configurée. +- Des permissions suffisantes pour gérer les services réseau (Network / vRack). +- Un service **vRack** provisionné (ou prêt à être créé) à associer à OVHcloud Connect. +- Vous (ou votre équipe réseau) devez maîtriser les bases du réseau IP (sous-réseaux, routage), les concepts BGP, la configuration VLAN. + +> **Astuce :** si vous n'êtes pas à l'aise avec BGP ou la configuration réseau, envisagez de travailler avec un fournisseur de services managés ou de solliciter l'équipe Professional Services d'OVHcloud. + +### Limites + +- Un service OVHcloud Connect ne peut être associé qu'à un seul vRack. +- Nombre maximum de services OVHcloud Connect par PoP et par vRack : 16. +- MTU maximum (Jumbo frame) : jusqu'à 9000 octets. + +## OVHcloud Connect Direct + +### Prérequis + +#### Prérequis administratifs + +- Accès à une **installation de colocation** où OVHcloud dispose d'un PoP (consultez [Emplacements des PoPs et régions](../1.4_pop_locations_regions/guide.fr-fr.md)). +- Capacité à commander un **cross-connect** dans le datacenter (ou à en organiser un via l'opérateur de l'installation). + +#### Prérequis techniques + +- L'interface de votre équipement doit être prise en charge (référez-vous au tableau ci-dessous). + +| Bande passante | Type d'interface | +|---|---| +| 1 Gb | 1000Base-LX/LH | +| 10 Gb | 10GBase-LR | +| 100 Gb | 100GBase-LR4 | + +- L'auto-négociation doit être désactivée (non prise en charge). + +### Limites + +#### Mode Layer 2 + +- Le nombre d'adresses MAC côté client est limité à 512 par port. +- La bande passante maximale est de 10 Gb par port. +- Un seul OVHcloud Connect Direct Layer 2 peut être attaché par vRack. + - Ce mode ne permet pas de déployer des architectures à PoPs redondants. + - Vous pouvez déployer des liens redondants au sein du même PoP en activant LACP. + +- Les fonctionnalités suivantes ne sont pas prises en charge : + - 802.1p CoS-based + - DCBX et protocoles associés (802.1Qbb, 802.1Qaz, 802.1Qau) + - TRILL, SPF et FabricPath + - FCoE + - Spanning Tree + - IGMP et Multicast + - EtherChannel, PaGP pour l'agrégation + +#### Mode Layer 3 + +Si vous avez choisi un OVHcloud Connect Direct Layer 3, veuillez consulter la [section Layer 3](#id-l3) ci-dessous. + +## OVHcloud Connect Provider + +### Prérequis + +- Un contrat avec un **provider pris en charge** (consultez [Providers](../1.3_providers/guide.fr-fr.md)). +- Le provider doit être présent au PoP OVHcloud que vous avez choisi. + +### Limites + +#### Mode Layer 3 + +OVHcloud Connect Provider est toujours un service réseau Layer 3 : veuillez consulter la [section Layer 3](#id-l3) ci-dessous. + +## Mode Layer 3 + +### Limites + +- Une seule session BGP entre votre équipement et le routeur du Point de présence OVHcloud (pas d'eBGP Multihop). Plus de détails dans [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp/guide.fr-fr.md). +- Chaque Availability Zone supporte jusqu'à 4 peers BGP. Plus de détails dans [Configurer votre réseau vRack](../3.6_vrack_network_setup/guide.fr-fr.md). +- Jusqu'à 100 préfixes peuvent être annoncés par session BGP. + +- Les fonctionnalités suivantes ne sont pas prises en charge : + - IPv6 + - Tout mécanisme de QoS + - Tag 802.1q + - Multi-VRF + - eBGP Multi-Hop + - iBGP + - Routage statique dans la configuration de PoP + +## Et ensuite ? + +- Accédez au [Quick Start : connexion Direct](../2.1_quick_start_direct/guide.fr-fr.md) ou au [Quick Start : connexion via Provider](../2.2_quick_start_provider/guide.fr-fr.md) + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-limits/meta.yaml b/pages/network/ovhcloud_connect/1.8_prerequisites_limitations/meta.yaml old mode 100755 new mode 100644 similarity index 100% rename from pages/network/ovhcloud_connect/occ-limits/meta.yaml rename to pages/network/ovhcloud_connect/1.8_prerequisites_limitations/meta.yaml diff --git a/pages/network/ovhcloud_connect/1.9_troubleshooting/guide.en-gb.md b/pages/network/ovhcloud_connect/1.9_troubleshooting/guide.en-gb.md new file mode 100644 index 00000000000..74bdce2d2e2 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.9_troubleshooting/guide.en-gb.md @@ -0,0 +1,596 @@ +--- +title: 'Troubleshoot OVHcloud Connect' +excerpt: 'Diagnose and resolve the most common issues encountered with OVHcloud Connect' +updated: 2026-02-18 +--- + +## Objective + +This guide helps you diagnose and resolve the most common issues encountered with OVHcloud Connect. Each section describes a known issue, its possible causes, and the steps to fix it. + +## Before you begin + +### General considerations + +- **Always check both sides** — Most OVHcloud Connect issues involve configuration or physical elements on both your side and OVHcloud's side. Verify your router, cross-connect (or provider virtual circuit), and the OVHcloud Control Panel before opening a ticket. +- **Collect diagnostics first** — Before making changes, gather interface status, BGP state, traceroute, and optical values. This information speeds up resolution whether you solve the issue yourself or need to contact support. +- **Check for scheduled maintenance** — Some issues may be caused by planned work on OVHcloud infrastructure or at your provider. Always check the status page before deep-diving into troubleshooting. + +### Useful resources + +| Resource | Link | +|---|---| +| **FAQ** | [Frequently Asked Questions](../5_faq/guide.en-gb.md) | +| **Glossary** | [Glossary of OVHcloud Connect terms](../1.2_glossary/guide.en-gb.md) | +| **OVHcloud services status** | [status.ovhcloud.com](https://www.status-ovhcloud.com/) | +| **Prerequisites & Limitations** | [Prerequisites & Limitations](../1.8_prerequisites_limitations/guide.en-gb.md) | +| **Monitoring guide** | [Monitor Your OVHcloud Connect](../3.9_monitor/guide.en-gb.md) | +| **Incident follow-up** | [Declare and Follow Up Upon an Incident](../3.10_incident_followup/guide.en-gb.md) | + +--- + +## Issue 1 — No light on the physical link (OVHcloud Connect Direct) + +After ordering OVHcloud Connect Direct, the physical link shows no optical signal on one or both sides. + +### Possible causes and solutions + +| # | Possible cause | Solution | +|---|---|---| +| 1 | **Cross-connect not yet installed** | Contact your data centre operator and provide the LOA. See [Ordering a Cross Connect with an LOA](../3.11_cross_connect_loa/guide.en-gb.md). | +| 2 | **LOA misinterpreted by the data centre** | Verify the LOA details with the PoP operator: cabinet, cage, patch panel, port, fibre termination. See [How to read LOA information](#how-to-read-loa-information) below. | +| 3 | **Tx/Rx fibre inversion** | The transmit and receive fibres may be swapped, causing light to arrive on the wrong port. Ask the data centre operator to check for a Tx/Rx inversion on the cross-connect. | +| 4 | **SFP module issue** | Ensure the SFP matches the ordered bandwidth: 1000Base-LX/LH for 1 Gbps, 10GBase-LR for 10 Gbps, 100GBase-LR4 for 100 Gbps. Replace the SFP if faulty. See [Prerequisites & Limitations](../1.8_prerequisites_limitations/guide.en-gb.md). | +| 5 | **Port disabled or locked** | Check the OVHcloud Control Panel — the port may be administratively locked. If the OUT optical value is DOWN, the port may also be in the process of being cancelled. | +| 6 | **Faulty cross-connect cable** | Ask the data centre operator to test the cable or provision a new one. | + +### How to read LOA information + +A typical LOA contains information formatted like this: + +``` +Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 +Port: P16/FO31-32/BCK Fiber Termination: SC/PC +``` + +Interpretation: + +| Field | Value | Meaning | +|---|---|---| +| Cabinet | 103 | Position of the bay where the rack is located | +| Cage | PA3:OG:00GMC3:OVH | Rack reference | +| Patch Panel (Z-side) | PP:0103:1132697 | Switch position on OVHcloud side | +| Port | 16 | Position on the switch | +| FibreOptic Port A | 31 | Fibre A identifier | +| FibreOptic Port B | 32 | Fibre B identifier | +| Side | BCK (Back) | Front or back of the equipment | +| Fibre Termination | SC/PC | Connector type | + +### Checking optical values + +In the OVHcloud Control Panel, navigate to **Network** → **OVHcloud Connect** → select your service, and check the IN/OUT optical values: + +- **OUT is DOWN** — The OVHcloud-side port is not emitting light. Possible reasons: port issue, service being cancelled, port locked, SFP failure. +- **IN is DOWN** — OVHcloud is not receiving light from your side. Possible reasons: cross-connect not installed, your equipment not connected, your port disabled, Tx/Rx fibre inversion. + +### Diagnostic flowchart + +```svg + + + + + + No light on the link + + + + Is OUT (OVHcloud → You) UP? + + + + + OUT is DOWN + Check: port locked? Cancellation? SFP issue? + + No + + + + Is IN (You → OVHcloud) UP? + + Yes + + + + IN is DOWN + Check: cross-connect, Tx/Rx swap, your port + + No + + + + Light OK on both sides ✓ + + Yes + + + + Contact OVHcloud support + + + + + + + + + +``` + +--- + +## Issue 2 — Ethernet link down (no peering) despite light being UP + +Optical values show UP on both sides, but the Ethernet interface remains DOWN and no peering can be established. + +### Possible causes and solutions + +| # | Possible cause | Solution | +|---|---|---| +| 1 | **SFP type mismatch** | The SFP must match the ordered bandwidth. Use **1000Base-LX/LH** for 1 Gbps, **10GBase-LR** for 10 Gbps, **100GBase-LR4** for 100 Gbps. | +| 2 | **Auto-negotiation enabled** | Auto-negotiation is **not supported** on OVHcloud Connect. Disable it on your router (see commands below). | +| 3 | **Speed mismatch** | Your interface speed must match the ordered link speed. Configure it explicitly. | +| 4 | **Faulty SFP or transceiver** | Try replacing the SFP module on your side. | + +### Disabling auto-negotiation + +**Cisco IOS:** + +``` +interface GigabitEthernet0/0 + no negotiate auto +``` + +or: + +``` +interface GigabitEthernet0/0 + speed nonegotiate +``` + +**Cisco NX-OS:** + +``` +interface Ethernet1/1 + speed 1000 + no negotiate auto +``` + +**Juniper JunOS:** + +``` +set interfaces ge-0/0/0 ether-options no-auto-negotiation +``` + +--- + +## Issue 3 — BGP session stuck in Active or Idle state + +The physical link is up, but the BGP session does not reach the `Established` state. + +### Possible causes and solutions + +| # | Possible cause | Solution | +|---|---|---| +| 1 | **Incorrect peer IP address** | Verify that the peer IP configured on your router matches exactly the IP assigned by OVHcloud in the Control Panel. The PoP peering subnet is a /30: OVHcloud takes the first IP, you take the second. See [Configure OCC L3 with BGP](../3.7_occ_l3_bgp/guide.en-gb.md). | +| 2 | **Incorrect ASN** | Check that you are peering with OVHcloud ASN **35540** and that your own ASN is correctly configured (private ASN range 64512–65534 recommended). Avoid reserved ASNs: **65501** (EU PoP), **65502** (CA PoP), **65519** (Asia PoP). | +| 3 | **VLAN ID mismatch** | The VLAN tag on your interface must match the VLAN ID configured in the OVHcloud Control Panel PoP configuration. Verify with `show interfaces` or `show vlans`. | +| 4 | **Firewall blocking TCP port 179** | BGP uses TCP port 179. Ensure no firewall or ACL is blocking this port between the two peers. | +| 5 | **Interface not configured with correct encapsulation** | For L3 connections, the interface must use 802.1Q encapsulation with the correct VLAN ID. See configuration examples in the [Configure OCC L3 with BGP](../3.7_occ_l3_bgp/guide.en-gb.md). | +| 6 | **PoP configuration not created in OVHcloud** | Verify in the OVHcloud Control Panel that a PoP configuration has been created for your service. Without it, OVHcloud's router will not peer. | +| 7 | **MD5 authentication mismatch** | If MD5 is configured, the password must match on both sides. Check with your OVHcloud Connect service details. | + +### Verification commands + +**Cisco IOS:** + +``` +show ip bgp summary +show bgp ipv4 unicast neighbors 192.0.2.1 +show interfaces GigabitEthernet0/0 +show ip interface brief +``` + +**Juniper JunOS:** + +``` +show bgp summary +show bgp neighbor 192.0.2.1 +show interfaces terse +``` + +### Diagnostic flowchart + +```svg + + + + + + BGP stuck in Active / Idle + + + + Is the physical interface UP? + + + + + Fix physical link first + See Issue 1 & Issue 2 + + No + + + + Do peer IP and ASN match? + + Yes + + + + Fix IP/ASN/VLAN configuration + + No + + + + Is TCP 179 allowed (no FW block)? + + Yes + + + + Open TCP 179 on both sides + + No + + + + Is PoP configuration created in OVHcloud? + + Yes + + + + Create PoP config in Control Panel + + No + + + + Contact OVHcloud support + + Yes + + + + + + + +``` + +--- + +## Issue 4 — BGP session established but no routes received + +The BGP session shows `Established`, but no prefixes are being received from OVHcloud (or from your network). + +### Possible causes and solutions + +| # | Possible cause | Solution | +|---|---|---| +| 1 | **Missing `network` statement or export policy** | On your router, ensure you are advertising the correct prefixes using `network` commands (Cisco) or export policies (Juniper). See [Configure OCC L3 with BGP](../3.7_occ_l3_bgp/guide.en-gb.md). | +| 2 | **Prefix filter blocking routes** | Your import prefix-list may be too restrictive, filtering out OVHcloud routes. Check your prefix-lists and route policies. | +| 3 | **vRack not associated** | OVHcloud routes are only exchanged if the OVHcloud Connect service is associated with a vRack. Verify the association in the Control Panel. See [Associate with vRack](../3.5_associate_vrack/guide.en-gb.md). | +| 4 | **AZ subnets not configured** | If no subnets are defined in the Availability Zone configuration, there will be no routes to exchange. See [Set up your vRack network](../3.6_vrack_network_setup/guide.en-gb.md). | +| 5 | **Maximum prefix limit reached** | OVHcloud supports up to **100 prefixes** per BGP session. If you exceed this limit, the session may stop accepting new routes. Aggregate your prefixes. | +| 6 | **Route not in the routing table** | The prefix you are trying to advertise must exist in your router's routing table (via a connected network, static route, or IGP). | + +### Verification commands + +**Cisco IOS:** + +``` +show ip bgp summary +show ip bgp neighbors 192.0.2.1 received-routes +show ip bgp neighbors 192.0.2.1 advertised-routes +show ip route bgp +``` + +**Juniper JunOS:** + +``` +show bgp summary +show route receive-protocol bgp 192.0.2.1 +show route advertising-protocol bgp 192.0.2.1 +show route protocol bgp +``` + +--- + +## Issue 5 — BGP session keeps flapping (repeatedly going up and down) + +The BGP session oscillates between `Established` and `Active`/`Idle` states, causing intermittent connectivity. + +### Possible causes and solutions + +| # | Possible cause | Solution | +|---|---|---| +| 1 | **Unstable physical link** | Check interface error counters (`show interfaces`) for CRC errors, input errors, or output drops. Inspect the SFP, cross-connect cable, and patch panel. | +| 2 | **MTU mismatch** | An MTU mismatch between your equipment and OVHcloud can cause large BGP update packets to be dropped. The default MTU is **1500 bytes**. Confirm MTU settings on both sides. | +| 3 | **BGP hold timer expiry** | Default BGP hold time is 90 seconds. If keepalives are lost due to link instability, the session drops. Consider adjusting BGP timers, but fix the root cause first. | +| 4 | **CPU or memory overload on your router** | BGP processing may be delayed if the router is under high load. Check CPU and memory usage. | +| 5 | **Aggressive prefix changes** | Rapidly withdrawing and re-advertising routes can trigger flap dampening. Stabilise your routing announcements. | + +### Verification commands + +**Cisco IOS:** + +``` +show interfaces GigabitEthernet0/0 +show ip bgp summary +show ip bgp flap-statistics +show log | include BGP +``` + +**Juniper JunOS:** + +``` +show interfaces ge-0/0/0 extensive +show bgp summary +show log messages | match BGP +``` + +--- + +## Issue 6 — Traffic not flowing despite BGP session established and routes exchanged + +BGP is up, routes appear in the routing table on both sides, but actual traffic (ping, application data) does not flow. + +### Possible causes and solutions + +| # | Possible cause | Solution | +|---|---|---| +| 1 | **Firewall or ACL blocking traffic** | Check firewall rules and access control lists on your router, your OVHcloud resources (security groups, iptables), and any intermediate devices. | +| 2 | **VLAN tagging mismatch** | The VLAN ID on your interface must match the VLAN configured in OVHcloud. A mismatch results in tagged traffic being silently dropped. | +| 3 | **Incorrect subnet configuration** | Verify that source and destination IPs belong to the correct subnets and that there are no overlapping ranges. See [Set up your vRack network](../3.6_vrack_network_setup/guide.en-gb.md). | +| 4 | **Asymmetric routing** | If you have multiple paths (e.g. internet + OVHcloud Connect), return traffic may take a different path. Ensure symmetric routing using BGP attributes (Local Preference, AS-path prepending). | +| 5 | **vRack resource not attached** | The target OVHcloud resource (Bare Metal server, Public Cloud instance, Hosted Private Cloud) must be attached to the same vRack as OVHcloud Connect. Verify in the Control Panel. | +| 6 | **MTU mismatch causing fragmentation** | Large packets may be silently dropped if MTU differs between segments. Test with varying packet sizes: `ping -s 1472 -M do ` (Linux) to check for fragmentation issues. | + +### Verification commands + +**From your side:** + +``` +ping 172.16.1.1 +traceroute 172.16.1.1 +``` + +**From a Linux host in OVHcloud:** + +```bash +ping -c 10 10.0.0.1 +traceroute 10.0.0.1 +mtr -r -c 50 10.0.0.1 +``` + +--- + +## Issue 7 — Slow performance or high latency + +The connection is working, but throughput is lower than expected or latency is higher than normal. + +### Possible causes and solutions + +| # | Possible cause | Solution | +|---|---|---| +| 1 | **Bandwidth saturation** | Check interface utilisation in the OVHcloud Control Panel and on your router. If you consistently exceed 80% of the provisioned bandwidth, plan an upgrade. | +| 2 | **MTU mismatch causing fragmentation** | Fragmented packets reduce effective throughput. Verify MTU end-to-end and run path MTU discovery: `ping -s 1472 -M do `. | +| 3 | **Interface errors (CRC, FCS, drops)** | Check `show interfaces` for error counters. Physical issues (dirty fibre, bad SFP, loose connector) cause retransmissions and degrade performance. | +| 4 | **Sub-optimal routing** | Traffic may be taking a longer path than expected. Check `traceroute` and BGP attributes (Local Preference, AS-path) to ensure optimal path selection. | +| 5 | **Congestion at the provider** | If using OVHcloud Connect Provider, check the provider's portal (Megaport, Equinix Fabric, Console Connect) for utilisation and alerts on the virtual circuit. | +| 6 | **TCP window size misconfiguration** | For high-bandwidth, high-latency links, ensure TCP window scaling is enabled on hosts to maximise throughput. | + +### Verification commands + +**Cisco IOS:** + +``` +show interfaces GigabitEthernet0/0 | include rate|error|drop|CRC +show ip route 172.16.1.0 +``` + +**From a Linux host:** + +```bash +iperf3 -c -t 30 +mtr -r -c 100 +``` + +--- + +## Issue 8 — Provider virtual circuit not connecting (OVHcloud Connect Provider) + +You have ordered an OVHcloud Connect Provider service, but the connection through your provider (Megaport, Equinix Fabric, or Console Connect) is not coming up. + +### Possible causes and solutions + +| # | Possible cause | Solution | +|---|---|---| +| 1 | **Incorrect pairing key / service key** | Verify that the pairing key (or service key) entered in your provider's portal exactly matches the key from the OVHcloud Control Panel. | +| 2 | **Provider virtual circuit not provisioned** | Check the status of the VXC (Megaport), virtual connection (Equinix), or connection (Console Connect) in the provider's portal. It should show as "Active" or "Provisioned". | +| 3 | **Provider does not have presence at the PoP** | The provider must be available at the OVHcloud PoP you selected. Verify PoP availability in [Providers](../1.3_providers/guide.en-gb.md) and [PoP Locations](../1.4_pop_locations_regions/guide.en-gb.md). | +| 4 | **Bandwidth mismatch** | The bandwidth ordered on the provider side must match or be compatible with the OVHcloud Connect service bandwidth. | +| 5 | **Provider-side maintenance or outage** | Check your provider's status page for ongoing incidents or planned maintenance. | + +> **Tip:** If the provider portal shows the connection as "Active" but OVHcloud still shows it as "Pending", wait a few minutes for the provisioning to complete. If it persists beyond 30 minutes, contact OVHcloud support. + +--- + +## Issue 9 — Service ordered but not delivered / not configurable + +Your OVHcloud Connect service appears in the Control Panel but cannot be configured. + +### Possible causes and solutions + +| # | Possible cause | Solution | +|---|---|---| +| 1 | **Cross-connect not yet installed (Direct)** | The service becomes configurable once OVHcloud detects light on the port. Order the cross-connect from your data centre operator using the LOA and ensure your equipment is connected. | +| 2 | **60-day interconnection window (Direct)** | After the order, you have **60 days** to finalize the interconnection (order the cross-connect and interconnect your equipment). Beyond 60 days — even without detected light — the service is considered operational and billing starts. | +| 3 | **Provider circuit not yet linked (Provider)** | Ensure the provider virtual circuit is provisioned and linked to the OVHcloud service using the correct pairing key. | +| 4 | **Provisioning in progress** | New services may take a few minutes to become configurable after ordering. Wait and refresh the Control Panel. | +| 5 | **Order issue** | If the service remains in "Pending" state for an extended period, contact OVHcloud support with your order reference. | + +--- + +## Issue 10 — Failover not working in Multi-AZ setup + +You have two OVHcloud Connect links for redundancy, but traffic does not failover when one link goes down. + +### Possible causes and solutions + +| # | Possible cause | Solution | +|---|---|---| +| 1 | **Both links in the same PoP** | For true Multi-AZ resilience, the two links must terminate at **different PoPs** and **different Availability Zones**. See [Multi-AZ](../1.5_multi_az/guide.en-gb.md). | +| 2 | **BGP failover not configured** | Configure BGP attributes to control path selection: use **Local Preference** to prefer the primary path and **AS-path prepending** on the backup. See [Configure OCC L3 with BGP](../3.7_occ_l3_bgp/guide.en-gb.md). | +| 3 | **BFD not enabled** | Without BFD, BGP failover relies on hold timers (default 90 seconds). Enable **BFD (Bidirectional Forwarding Detection)** to reduce failover time to under 1 second. Contact OVHcloud support to confirm BFD availability for your service. | +| 4 | **vRack not shared between both services** | Both OVHcloud Connect services must be associated with the **same vRack** for failover to work. Verify in the Control Panel. See [Associate with vRack](../3.5_associate_vrack/guide.en-gb.md). | +| 5 | **Prefix-list filtering backup routes** | Ensure your import/export prefix filters allow the same prefixes on both links. | + +### Verification commands + +**Cisco IOS:** + +``` +show ip bgp +show ip bgp summary +show ip route bgp +show ip bgp neighbors 192.0.2.1 +show ip bgp neighbors 198.51.100.1 +``` + +Check that both BGP sessions are `Established` and that routes are received from both peers with different attributes (Local Preference, AS-path length). + +--- + +## Issue 11 — IP address conflict in PoP or DC configuration + +BGP session may not establish, or traffic may be routed incorrectly due to IP address conflicts. + +### Possible causes and solutions + +| # | Possible cause | Solution | +|---|---|---| +| 1 | **Using OVHcloud reserved IPs** | In the PoP /30 subnet, the **first IP** is reserved for OVHcloud. In the DC /28 (minimum) subnet, the **first three IPs** are reserved for OVHcloud. Ensure you are using the correct IPs. | +| 2 | **Overlapping subnets** | Your on-premises subnets must not overlap with subnets used in the OVHcloud vRack. Plan your IP addressing carefully. See [Set up your vRack network](../3.6_vrack_network_setup/guide.en-gb.md). | +| 3 | **Duplicate ASN** | Your BGP ASN must differ from OVHcloud's ASN (35540) and from the reserved ASNs (65501, 65502, 65519). | + +--- + +## Issue 12 — Unsupported features or unexpected behaviour + +Certain features may not work as expected due to current platform limitations. + +### Known limitations + +| Feature | Status | Notes | +|---|---|---| +| **IPv6** | Not supported | OVHcloud Connect currently supports IPv4 only. | +| **QoS / CoS** | Not supported | No quality of service or 802.1p class of service mechanisms. | +| **802.1q VLAN tagging (L2 mode)** | Supported | But L2 mode is available on OVHcloud Connect Direct only. | +| **Multi-VRF** | Not supported | Only a single routing instance per OVHcloud Connect service. | +| **eBGP Multi-Hop** | Not supported | BGP peering must be directly connected (single hop). | +| **iBGP** | Not supported | Only eBGP is supported. | +| **Static routing at PoP** | Not supported | All routing is done via BGP. | +| **Spanning Tree (L2)** | Not supported | L2 mode does not pass BPDUs. | +| **Multicast / IGMP (L2)** | Not supported | Only unicast traffic is supported in L2 mode. | +| **FCoE (L2)** | Not supported | Fibre Channel over Ethernet is not supported. | +| **LACP (L2)** | Supported | Can be used for link aggregation in L2 mode within a single PoP. | + +For the full list of prerequisites and limitations, see [Prerequisites & Limitations](../1.8_prerequisites_limitations/guide.en-gb.md). + +--- + +## Quick reference: diagnostic commands + +### Cisco IOS / IOS-XE + +| Purpose | Command | +|---|---| +| Interface status | `show interfaces GigabitEthernet0/0` | +| Interface brief | `show ip interface brief` | +| BGP session summary | `show ip bgp summary` | +| BGP neighbour details | `show bgp ipv4 unicast neighbors ` | +| Routes received from peer | `show ip bgp neighbors received-routes` | +| Routes advertised to peer | `show ip bgp neighbors advertised-routes` | +| BGP routing table | `show ip route bgp` | +| BGP flap statistics | `show ip bgp flap-statistics` | +| Logs | `show log \| include BGP` | + +### Juniper JunOS + +| Purpose | Command | +|---|---| +| Interface status | `show interfaces ge-0/0/0 extensive` | +| Interface summary | `show interfaces terse` | +| BGP session summary | `show bgp summary` | +| BGP neighbour details | `show bgp neighbor ` | +| Routes received from peer | `show route receive-protocol bgp ` | +| Routes advertised to peer | `show route advertising-protocol bgp ` | +| BGP routing table | `show route protocol bgp` | +| Logs | `show log messages \| match BGP` | + +### Linux host + +| Purpose | Command | +|---|---| +| Connectivity test | `ping -c 10 ` | +| Path trace | `traceroute ` | +| Combined ping + trace | `mtr -r -c 50 ` | +| MTU test (no fragmentation) | `ping -s 1472 -M do ` | +| Throughput test | `iperf3 -c -t 30` | + +--- + +## When to contact support + +If you have followed the troubleshooting steps above and the issue persists, open a support ticket: + +1. From the [OVHcloud Control Panel](/links/manager), go to **Support** → **Create a ticket**. +2. Select **Network** → **OVHcloud Connect**. +3. Include: + - Your OVHcloud Connect **service name/ID** + - **Timestamp** of the issue (UTC) + - **Symptoms** observed + - **Diagnostic outputs** (BGP summary, interface status, traceroute, optical values) + - **Steps already taken** to troubleshoot +4. See [Declare and Follow Up Upon an Incident](../3.10_incident_followup/guide.en-gb.md) for the full incident management process. + +--- + +## What's next? + +- Set up proactive [monitoring](../3.9_monitor/guide.en-gb.md) to detect issues before they impact your users +- Review [Prerequisites & Limitations](../1.8_prerequisites_limitations/guide.en-gb.md) to avoid known pitfalls +- Consult the [FAQ](../5_faq/guide.en-gb.md) for answers to common questions +- Check [SLAs](../1.7_slas/guide.en-gb.md) for uptime guarantees and service credits + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/1.9_troubleshooting/guide.fr-fr.md b/pages/network/ovhcloud_connect/1.9_troubleshooting/guide.fr-fr.md new file mode 100644 index 00000000000..a745d604726 --- /dev/null +++ b/pages/network/ovhcloud_connect/1.9_troubleshooting/guide.fr-fr.md @@ -0,0 +1,596 @@ +--- +title: 'Dépannage d''OVHcloud Connect' +excerpt: 'Diagnostiquez et résolvez les problèmes les plus courants rencontrés avec OVHcloud Connect' +updated: 2026-02-18 +--- + +## Objectif + +Ce guide vous aide à diagnostiquer et à résoudre les problèmes les plus courants rencontrés avec OVHcloud Connect. Chaque section décrit un problème connu, ses causes possibles ainsi que les étapes pour le corriger. + +## Avant de commencer + +### Considérations générales + +- **Vérifiez toujours les deux côtés** — La plupart des problèmes liés à OVHcloud Connect impliquent des éléments de configuration ou physiques de votre côté comme du côté OVHcloud. Vérifiez votre routeur, le cross-connect (ou le circuit virtuel du fournisseur) ainsi que l'espace client OVHcloud avant d'ouvrir un ticket. +- **Collectez les diagnostics au préalable** — Avant toute modification, recueillez l'état des interfaces, l'état BGP, un traceroute et les valeurs optiques. Ces informations accélèrent la résolution, que vous régliez le problème vous-même ou que vous deviez contacter le support. +- **Vérifiez les maintenances planifiées** — Certains problèmes peuvent être causés par des travaux planifiés sur l'infrastructure OVHcloud ou chez votre fournisseur. Consultez toujours la page de statut avant d'approfondir le dépannage. + +### Ressources utiles + +| Ressource | Lien | +|---|---| +| **FAQ** | [Foire aux questions](../5_faq/guide.fr-fr.md) | +| **Glossaire** | [Glossaire des termes OVHcloud Connect](../1.2_glossary/guide.fr-fr.md) | +| **Statut des services OVHcloud** | [status.ovhcloud.com](https://www.status-ovhcloud.com/) | +| **Prérequis et limitations** | [Prérequis et limitations](../1.8_prerequisites_limitations/guide.fr-fr.md) | +| **Guide de monitoring** | [Superviser votre OVHcloud Connect](../3.9_monitor/guide.fr-fr.md) | +| **Suivi d'incident** | [Déclarer et suivre un incident](../3.10_incident_followup/guide.fr-fr.md) | + +--- + +## Problème 1 — Aucune lumière sur le lien physique (OVHcloud Connect Direct) + +Après la commande d'OVHcloud Connect Direct, le lien physique n'affiche aucun signal optique d'un côté ou des deux. + +### Causes possibles et solutions + +| # | Cause possible | Solution | +|---|---|---| +| 1 | **Cross-connect non encore installé** | Contactez l'opérateur de votre datacenter et fournissez-lui la LOA. Consultez [Commander un cross-connect avec une LOA](../3.11_cross_connect_loa/guide.fr-fr.md). | +| 2 | **LOA mal interprétée par le datacenter** | Vérifiez les détails de la LOA avec l'opérateur du PoP : baie, cage, panneau de brassage, port, terminaison de la fibre. Consultez [Comment lire les informations d'une LOA](#comment-lire-les-informations-dune-loa) ci-dessous. | +| 3 | **Inversion des fibres Tx/Rx** | Les fibres d'émission et de réception peuvent être inversées, ce qui fait arriver la lumière sur le mauvais port. Demandez à l'opérateur du datacenter de vérifier l'absence d'inversion Tx/Rx sur le cross-connect. | +| 4 | **Problème de module SFP** | Assurez-vous que le SFP correspond à la bande passante commandée : 1000Base-LX/LH pour 1 Gbps, 10GBase-LR pour 10 Gbps, 100GBase-LR4 pour 100 Gbps. Remplacez le SFP s'il est défectueux. Consultez [Prérequis et limitations](../1.8_prerequisites_limitations/guide.fr-fr.md). | +| 5 | **Port désactivé ou verrouillé** | Vérifiez l'espace client OVHcloud — le port peut être verrouillé administrativement. Si la valeur optique OUT est DOWN, le port peut également être en cours de résiliation. | +| 6 | **Câble cross-connect défectueux** | Demandez à l'opérateur du datacenter de tester le câble ou de provisionner un nouveau câble. | + +### Comment lire les informations d'une LOA + +Une LOA classique contient des informations formatées ainsi : + +``` +Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 +Port: P16/FO31-32/BCK Fiber Termination: SC/PC +``` + +Interprétation : + +| Champ | Valeur | Signification | +|---|---|---| +| Baie | 103 | Position de la baie où se trouve le rack | +| Cage | PA3:OG:00GMC3:OVH | Référence du rack | +| Panneau de brassage (côté Z) | PP:0103:1132697 | Position du switch côté OVHcloud | +| Port | 16 | Position sur le switch | +| Port fibre optique A | 31 | Identifiant de la fibre A | +| Port fibre optique B | 32 | Identifiant de la fibre B | +| Côté | BCK (Back) | Avant ou arrière de l'équipement | +| Terminaison de fibre | SC/PC | Type de connecteur | + +### Vérifier les valeurs optiques + +Dans l'espace client OVHcloud, accédez à **Network** → **OVHcloud Connect** → sélectionnez votre service, puis vérifiez les valeurs optiques IN/OUT : + +- **OUT est DOWN** — Le port côté OVHcloud n'émet pas de lumière. Causes possibles : problème de port, service en cours de résiliation, port verrouillé, panne de SFP. +- **IN est DOWN** — OVHcloud ne reçoit pas de lumière de votre côté. Causes possibles : cross-connect non installé, votre équipement non connecté, votre port désactivé, inversion des fibres Tx/Rx. + +### Logigramme de diagnostic + +```svg + + + + + + Pas de lumière sur le lien + + + + OUT (OVHcloud → Vous) UP ? + + + + + OUT est DOWN + Vérifier : port verrouillé ? résiliation ? SFP ? + + Non + + + + IN (Vous → OVHcloud) UP ? + + Oui + + + + IN est DOWN + Vérifier : cross-connect, inversion Tx/Rx, votre port + + Non + + + + Lumière OK des deux côtés ✓ + + Oui + + + + Contacter le support OVHcloud + + + + + + + + + +``` + +--- + +## Problème 2 — Lien Ethernet down (pas de peering) malgré une lumière UP + +Les valeurs optiques sont UP des deux côtés, mais l'interface Ethernet reste DOWN et aucun peering ne peut être établi. + +### Causes possibles et solutions + +| # | Cause possible | Solution | +|---|---|---| +| 1 | **Type de SFP incompatible** | Le SFP doit correspondre à la bande passante commandée. Utilisez **1000Base-LX/LH** pour 1 Gbps, **10GBase-LR** pour 10 Gbps, **100GBase-LR4** pour 100 Gbps. | +| 2 | **Auto-négociation activée** | L'auto-négociation **n'est pas prise en charge** sur OVHcloud Connect. Désactivez-la sur votre routeur (voir les commandes ci-dessous). | +| 3 | **Vitesse incompatible** | La vitesse de votre interface doit correspondre à celle du lien commandé. Configurez-la explicitement. | +| 4 | **SFP ou transceiver défectueux** | Essayez de remplacer le module SFP de votre côté. | + +### Désactiver l'auto-négociation + +**Cisco IOS :** + +``` +interface GigabitEthernet0/0 + no negotiate auto +``` + +ou : + +``` +interface GigabitEthernet0/0 + speed nonegotiate +``` + +**Cisco NX-OS :** + +``` +interface Ethernet1/1 + speed 1000 + no negotiate auto +``` + +**Juniper JunOS :** + +``` +set interfaces ge-0/0/0 ether-options no-auto-negotiation +``` + +--- + +## Problème 3 — Session BGP bloquée à l'état Active ou Idle + +Le lien physique est up, mais la session BGP n'atteint pas l'état `Established`. + +### Causes possibles et solutions + +| # | Cause possible | Solution | +|---|---|---| +| 1 | **Adresse IP du pair incorrecte** | Vérifiez que l'IP du pair configurée sur votre routeur correspond exactement à l'IP attribuée par OVHcloud dans l'espace client. Le sous-réseau de peering du PoP est un /30 : OVHcloud prend la première IP, vous prenez la seconde. Consultez [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp/guide.fr-fr.md). | +| 2 | **ASN incorrect** | Vérifiez que vous établissez le peering avec l'ASN OVHcloud **35540** et que votre propre ASN est correctement configuré (plage d'ASN privés 64512-65534 recommandée). Évitez les ASN réservés : **65501** (PoP UE), **65502** (PoP CA), **65519** (PoP Asie). | +| 3 | **ID de VLAN incompatible** | Le tag VLAN sur votre interface doit correspondre à l'ID de VLAN configuré dans la configuration du PoP de l'espace client OVHcloud. Vérifiez avec `show interfaces` ou `show vlans`. | +| 4 | **Pare-feu bloquant le port TCP 179** | BGP utilise le port TCP 179. Assurez-vous qu'aucun pare-feu ou ACL ne bloque ce port entre les deux pairs. | +| 5 | **Interface non configurée avec l'encapsulation correcte** | Pour les connexions L3, l'interface doit utiliser l'encapsulation 802.1Q avec l'ID de VLAN correct. Consultez les exemples de configuration dans [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp/guide.fr-fr.md). | +| 6 | **Configuration du PoP non créée chez OVHcloud** | Vérifiez dans l'espace client OVHcloud qu'une configuration de PoP a bien été créée pour votre service. Sans cela, le routeur OVHcloud n'établira pas le peering. | +| 7 | **Authentification MD5 incompatible** | Si MD5 est configuré, le mot de passe doit correspondre des deux côtés. Vérifiez avec les détails de votre service OVHcloud Connect. | + +### Commandes de vérification + +**Cisco IOS :** + +``` +show ip bgp summary +show bgp ipv4 unicast neighbors 192.0.2.1 +show interfaces GigabitEthernet0/0 +show ip interface brief +``` + +**Juniper JunOS :** + +``` +show bgp summary +show bgp neighbor 192.0.2.1 +show interfaces terse +``` + +### Logigramme de diagnostic + +```svg + + + + + + BGP bloqué en Active / Idle + + + + L'interface physique est-elle UP ? + + + + + Corriger le lien physique d'abord + Voir Problème 1 & Problème 2 + + Non + + + + IP du pair et ASN concordent ? + + Oui + + + + Corriger la configuration IP/ASN/VLAN + + Non + + + + TCP 179 autorisé (pas de blocage FW) ? + + Oui + + + + Ouvrir TCP 179 des deux côtés + + Non + + + + Config du PoP créée chez OVHcloud ? + + Oui + + + + Créer la config PoP dans l'espace client + + Non + + + + Contacter le support OVHcloud + + Oui + + + + + + + +``` + +--- + +## Problème 4 — Session BGP établie mais aucune route reçue + +La session BGP affiche `Established`, mais aucun préfixe n'est reçu d'OVHcloud (ou de votre réseau). + +### Causes possibles et solutions + +| # | Cause possible | Solution | +|---|---|---| +| 1 | **Instruction `network` ou politique d'export manquante** | Sur votre routeur, assurez-vous d'annoncer les bons préfixes via les commandes `network` (Cisco) ou les politiques d'export (Juniper). Consultez [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp/guide.fr-fr.md). | +| 2 | **Filtre de préfixes bloquant les routes** | Votre prefix-list d'import peut être trop restrictive et filtrer les routes OVHcloud. Vérifiez vos prefix-lists et vos politiques de routage. | +| 3 | **vRack non associé** | Les routes OVHcloud ne sont échangées que si le service OVHcloud Connect est associé à un vRack. Vérifiez l'association dans l'espace client. Consultez [Associer à un vRack](../3.5_associate_vrack/guide.fr-fr.md). | +| 4 | **Sous-réseaux d'AZ non configurés** | Si aucun sous-réseau n'est défini dans la configuration de l'Availability Zone, aucune route ne pourra être échangée. Consultez [Configurer votre réseau vRack](../3.6_vrack_network_setup/guide.fr-fr.md). | +| 5 | **Limite maximale de préfixes atteinte** | OVHcloud prend en charge jusqu'à **100 préfixes** par session BGP. Si vous dépassez cette limite, la session peut cesser d'accepter de nouvelles routes. Agrégez vos préfixes. | +| 6 | **Route absente de la table de routage** | Le préfixe que vous tentez d'annoncer doit exister dans la table de routage de votre routeur (via un réseau connecté, une route statique ou un IGP). | + +### Commandes de vérification + +**Cisco IOS :** + +``` +show ip bgp summary +show ip bgp neighbors 192.0.2.1 received-routes +show ip bgp neighbors 192.0.2.1 advertised-routes +show ip route bgp +``` + +**Juniper JunOS :** + +``` +show bgp summary +show route receive-protocol bgp 192.0.2.1 +show route advertising-protocol bgp 192.0.2.1 +show route protocol bgp +``` + +--- + +## Problème 5 — Session BGP qui flappe en permanence (montées et descentes répétées) + +La session BGP oscille entre les états `Established` et `Active`/`Idle`, provoquant une connectivité intermittente. + +### Causes possibles et solutions + +| # | Cause possible | Solution | +|---|---|---| +| 1 | **Lien physique instable** | Vérifiez les compteurs d'erreurs des interfaces (`show interfaces`) pour les erreurs CRC, les erreurs d'entrée ou les drops de sortie. Inspectez le SFP, le câble cross-connect et le panneau de brassage. | +| 2 | **MTU incompatible** | Une incompatibilité de MTU entre votre équipement et OVHcloud peut entraîner la perte des grands paquets de mise à jour BGP. Le MTU par défaut est de **1500 octets**. Confirmez les paramètres de MTU des deux côtés. | +| 3 | **Expiration du hold timer BGP** | Le hold timer BGP par défaut est de 90 secondes. Si des keepalives sont perdus à cause de l'instabilité du lien, la session tombe. Envisagez d'ajuster les timers BGP, mais corrigez d'abord la cause racine. | +| 4 | **Surcharge CPU ou mémoire de votre routeur** | Le traitement BGP peut être retardé si le routeur est en forte charge. Vérifiez l'utilisation CPU et mémoire. | +| 5 | **Changements agressifs de préfixes** | Le retrait et l'annonce rapides de routes peuvent déclencher du flap dampening. Stabilisez vos annonces de routage. | + +### Commandes de vérification + +**Cisco IOS :** + +``` +show interfaces GigabitEthernet0/0 +show ip bgp summary +show ip bgp flap-statistics +show log | include BGP +``` + +**Juniper JunOS :** + +``` +show interfaces ge-0/0/0 extensive +show bgp summary +show log messages | match BGP +``` + +--- + +## Problème 6 — Le trafic ne circule pas malgré une session BGP établie et des routes échangées + +BGP est up, les routes apparaissent dans la table de routage des deux côtés, mais le trafic réel (ping, données applicatives) ne passe pas. + +### Causes possibles et solutions + +| # | Cause possible | Solution | +|---|---|---| +| 1 | **Pare-feu ou ACL bloquant le trafic** | Vérifiez les règles de pare-feu et les listes de contrôle d'accès sur votre routeur, sur vos ressources OVHcloud (security groups, iptables) et sur tout équipement intermédiaire. | +| 2 | **Tag VLAN incompatible** | L'ID de VLAN sur votre interface doit correspondre au VLAN configuré chez OVHcloud. Une incompatibilité entraîne un drop silencieux du trafic taggé. | +| 3 | **Configuration de sous-réseau incorrecte** | Vérifiez que les IPs source et destination appartiennent aux bons sous-réseaux et qu'aucune plage ne se chevauche. Consultez [Configurer votre réseau vRack](../3.6_vrack_network_setup/guide.fr-fr.md). | +| 4 | **Routage asymétrique** | Si vous avez plusieurs chemins (par exemple internet + OVHcloud Connect), le trafic retour peut emprunter un chemin différent. Garantissez un routage symétrique grâce aux attributs BGP (Local Preference, AS-path prepending). | +| 5 | **Ressource vRack non rattachée** | La ressource OVHcloud cible (serveur Bare Metal, instance Public Cloud, Hosted Private Cloud) doit être rattachée au même vRack qu'OVHcloud Connect. Vérifiez dans l'espace client. | +| 6 | **MTU incompatible entraînant de la fragmentation** | Les grands paquets peuvent être perdus silencieusement si le MTU diffère entre les segments. Testez avec différentes tailles de paquets : `ping -s 1472 -M do ` (Linux) pour vérifier les problèmes de fragmentation. | + +### Commandes de vérification + +**De votre côté :** + +``` +ping 172.16.1.1 +traceroute 172.16.1.1 +``` + +**Depuis un hôte Linux dans OVHcloud :** + +```bash +ping -c 10 10.0.0.1 +traceroute 10.0.0.1 +mtr -r -c 50 10.0.0.1 +``` + +--- + +## Problème 7 — Performances lentes ou latence élevée + +La connexion fonctionne, mais le débit est inférieur aux attentes ou la latence est plus élevée que la normale. + +### Causes possibles et solutions + +| # | Cause possible | Solution | +|---|---|---| +| 1 | **Saturation de la bande passante** | Vérifiez l'utilisation des interfaces dans l'espace client OVHcloud et sur votre routeur. Si vous dépassez régulièrement 80 % de la bande passante provisionnée, planifiez une montée en gamme. | +| 2 | **MTU incompatible entraînant de la fragmentation** | Les paquets fragmentés réduisent le débit effectif. Vérifiez le MTU de bout en bout et exécutez une découverte de path MTU : `ping -s 1472 -M do `. | +| 3 | **Erreurs d'interface (CRC, FCS, drops)** | Vérifiez les compteurs d'erreurs avec `show interfaces`. Les problèmes physiques (fibre encrassée, SFP défectueux, connecteur mal serré) provoquent des retransmissions et dégradent les performances. | +| 4 | **Routage sous-optimal** | Le trafic peut emprunter un chemin plus long qu'attendu. Vérifiez le `traceroute` et les attributs BGP (Local Preference, AS-path) pour garantir une sélection optimale du chemin. | +| 5 | **Congestion chez le fournisseur** | Si vous utilisez OVHcloud Connect Provider, vérifiez le portail du fournisseur (Megaport, Equinix Fabric, Console Connect) pour l'utilisation et les alertes sur le circuit virtuel. | +| 6 | **Mauvaise configuration de la taille de fenêtre TCP** | Pour les liens à haute bande passante et latence élevée, assurez-vous que le TCP window scaling est activé sur les hôtes afin de maximiser le débit. | + +### Commandes de vérification + +**Cisco IOS :** + +``` +show interfaces GigabitEthernet0/0 | include rate|error|drop|CRC +show ip route 172.16.1.0 +``` + +**Depuis un hôte Linux :** + +```bash +iperf3 -c -t 30 +mtr -r -c 100 +``` + +--- + +## Problème 8 — Circuit virtuel du fournisseur ne s'établit pas (OVHcloud Connect Provider) + +Vous avez commandé un service OVHcloud Connect Provider, mais la connexion via votre fournisseur (Megaport, Equinix Fabric ou Console Connect) ne monte pas. + +### Causes possibles et solutions + +| # | Cause possible | Solution | +|---|---|---| +| 1 | **Pairing key / clé de service incorrecte** | Vérifiez que la pairing key (ou clé de service) saisie dans le portail de votre fournisseur correspond exactement à la clé issue de l'espace client OVHcloud. | +| 2 | **Circuit virtuel du fournisseur non provisionné** | Vérifiez le statut du VXC (Megaport), de la connexion virtuelle (Equinix) ou de la connexion (Console Connect) dans le portail du fournisseur. Il doit être affiché « Active » ou « Provisioned ». | +| 3 | **Le fournisseur n'est pas présent au PoP** | Le fournisseur doit être disponible au PoP OVHcloud que vous avez sélectionné. Vérifiez la disponibilité du PoP dans [Fournisseurs](../1.3_providers/guide.fr-fr.md) et [Localisations des PoP](../1.4_pop_locations_regions/guide.fr-fr.md). | +| 4 | **Bande passante incompatible** | La bande passante commandée côté fournisseur doit correspondre, ou être compatible, avec la bande passante du service OVHcloud Connect. | +| 5 | **Maintenance ou incident côté fournisseur** | Consultez la page de statut de votre fournisseur pour vérifier les incidents en cours ou les maintenances planifiées. | + +> **Astuce :** si le portail du fournisseur affiche la connexion comme « Active » mais qu'OVHcloud l'affiche encore comme « Pending », attendez quelques minutes que le provisionnement se termine. Si cela persiste au-delà de 30 minutes, contactez le support OVHcloud. + +--- + +## Problème 9 — Service commandé mais non livré / non configurable + +Votre service OVHcloud Connect apparaît dans l'espace client mais ne peut pas être configuré. + +### Causes possibles et solutions + +| # | Cause possible | Solution | +|---|---|---| +| 1 | **Cross-connect non encore installé (Direct)** | Le service devient configurable une fois qu'OVHcloud détecte de la lumière sur le port. Commandez le cross-connect auprès de l'opérateur de votre datacenter à l'aide de la LOA et assurez-vous que votre équipement est connecté. | +| 2 | **Fenêtre d'interconnexion de 60 jours (Direct)** | Après la commande, vous disposez de **60 jours** pour finaliser l'interconnexion (commander le cross-connect et interconnecter votre équipement). Au-delà de 60 jours — même sans détection de lumière — le service est considéré comme opérationnel et la facturation démarre. | +| 3 | **Circuit du fournisseur non encore relié (Provider)** | Assurez-vous que le circuit virtuel du fournisseur est provisionné et relié au service OVHcloud à l'aide de la pairing key correcte. | +| 4 | **Provisionnement en cours** | Les nouveaux services peuvent mettre quelques minutes à devenir configurables après la commande. Patientez et rafraîchissez l'espace client. | +| 5 | **Problème de commande** | Si le service reste à l'état « Pending » pendant une période prolongée, contactez le support OVHcloud avec la référence de votre commande. | + +--- + +## Problème 10 — Bascule inopérante en configuration Multi-AZ + +Vous disposez de deux liens OVHcloud Connect pour la redondance, mais le trafic ne bascule pas lorsque l'un des liens tombe. + +### Causes possibles et solutions + +| # | Cause possible | Solution | +|---|---|---| +| 1 | **Les deux liens dans le même PoP** | Pour une véritable résilience Multi-AZ, les deux liens doivent se terminer sur des **PoP différents** et des **Availability Zones différentes**. Consultez [Multi-AZ](../1.5_multi_az/guide.fr-fr.md). | +| 2 | **Bascule BGP non configurée** | Configurez les attributs BGP pour contrôler la sélection du chemin : utilisez la **Local Preference** pour privilégier le chemin principal et l'**AS-path prepending** sur le secours. Consultez [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp/guide.fr-fr.md). | +| 3 | **BFD non activé** | Sans BFD, la bascule BGP repose sur les hold timers (90 secondes par défaut). Activez **BFD (Bidirectional Forwarding Detection)** pour réduire le temps de bascule à moins d'une seconde. Contactez le support OVHcloud pour confirmer la disponibilité de BFD pour votre service. | +| 4 | **vRack non partagé entre les deux services** | Les deux services OVHcloud Connect doivent être associés au **même vRack** pour que la bascule fonctionne. Vérifiez dans l'espace client. Consultez [Associer à un vRack](../3.5_associate_vrack/guide.fr-fr.md). | +| 5 | **Prefix-list filtrant les routes de secours** | Assurez-vous que vos filtres de préfixes en import/export autorisent les mêmes préfixes sur les deux liens. | + +### Commandes de vérification + +**Cisco IOS :** + +``` +show ip bgp +show ip bgp summary +show ip route bgp +show ip bgp neighbors 192.0.2.1 +show ip bgp neighbors 198.51.100.1 +``` + +Vérifiez que les deux sessions BGP sont à l'état `Established` et que les routes sont reçues des deux pairs avec des attributs différents (Local Preference, longueur de l'AS-path). + +--- + +## Problème 11 — Conflit d'adresses IP dans la configuration PoP ou DC + +La session BGP peut ne pas s'établir, ou le trafic peut être mal routé en raison de conflits d'adresses IP. + +### Causes possibles et solutions + +| # | Cause possible | Solution | +|---|---|---| +| 1 | **Utilisation d'IPs réservées par OVHcloud** | Dans le sous-réseau /30 du PoP, la **première IP** est réservée à OVHcloud. Dans le sous-réseau /28 (minimum) du DC, les **trois premières IPs** sont réservées à OVHcloud. Assurez-vous d'utiliser les bonnes IPs. | +| 2 | **Sous-réseaux qui se chevauchent** | Vos sous-réseaux on-premises ne doivent pas se chevaucher avec les sous-réseaux utilisés dans le vRack OVHcloud. Planifiez soigneusement votre adressage IP. Consultez [Configurer votre réseau vRack](../3.6_vrack_network_setup/guide.fr-fr.md). | +| 3 | **ASN en doublon** | Votre ASN BGP doit être différent de celui d'OVHcloud (35540) et des ASN réservés (65501, 65502, 65519). | + +--- + +## Problème 12 — Fonctionnalités non prises en charge ou comportement inattendu + +Certaines fonctionnalités peuvent ne pas se comporter comme attendu en raison des limitations actuelles de la plateforme. + +### Limitations connues + +| Fonctionnalité | Statut | Notes | +|---|---|---| +| **IPv6** | Non pris en charge | OVHcloud Connect ne prend en charge qu'IPv4 actuellement. | +| **QoS / CoS** | Non pris en charge | Aucun mécanisme de qualité de service ou de classe de service 802.1p. | +| **Tag VLAN 802.1q (mode L2)** | Pris en charge | Le mode L2 n'est toutefois disponible que sur OVHcloud Connect Direct. | +| **Multi-VRF** | Non pris en charge | Une seule instance de routage par service OVHcloud Connect. | +| **eBGP Multi-Hop** | Non pris en charge | Le peering BGP doit être directement connecté (single hop). | +| **iBGP** | Non pris en charge | Seul l'eBGP est pris en charge. | +| **Routage statique au PoP** | Non pris en charge | Tout le routage se fait via BGP. | +| **Spanning Tree (L2)** | Non pris en charge | Le mode L2 ne transmet pas les BPDU. | +| **Multicast / IGMP (L2)** | Non pris en charge | Seul le trafic unicast est pris en charge en mode L2. | +| **FCoE (L2)** | Non pris en charge | Fibre Channel over Ethernet n'est pas pris en charge. | +| **LACP (L2)** | Pris en charge | Peut être utilisé pour l'agrégation de liens en mode L2 au sein d'un même PoP. | + +Pour la liste complète des prérequis et limitations, consultez [Prérequis et limitations](../1.8_prerequisites_limitations/guide.fr-fr.md). + +--- + +## Référence rapide : commandes de diagnostic + +### Cisco IOS / IOS-XE + +| Objectif | Commande | +|---|---| +| État de l'interface | `show interfaces GigabitEthernet0/0` | +| Résumé des interfaces | `show ip interface brief` | +| Résumé de la session BGP | `show ip bgp summary` | +| Détails du voisin BGP | `show bgp ipv4 unicast neighbors ` | +| Routes reçues du pair | `show ip bgp neighbors received-routes` | +| Routes annoncées au pair | `show ip bgp neighbors advertised-routes` | +| Table de routage BGP | `show ip route bgp` | +| Statistiques de flap BGP | `show ip bgp flap-statistics` | +| Logs | `show log \| include BGP` | + +### Juniper JunOS + +| Objectif | Commande | +|---|---| +| État de l'interface | `show interfaces ge-0/0/0 extensive` | +| Résumé des interfaces | `show interfaces terse` | +| Résumé de la session BGP | `show bgp summary` | +| Détails du voisin BGP | `show bgp neighbor ` | +| Routes reçues du pair | `show route receive-protocol bgp ` | +| Routes annoncées au pair | `show route advertising-protocol bgp ` | +| Table de routage BGP | `show route protocol bgp` | +| Logs | `show log messages \| match BGP` | + +### Hôte Linux + +| Objectif | Commande | +|---|---| +| Test de connectivité | `ping -c 10 ` | +| Trace de chemin | `traceroute ` | +| Ping + trace combinés | `mtr -r -c 50 ` | +| Test de MTU (sans fragmentation) | `ping -s 1472 -M do ` | +| Test de débit | `iperf3 -c -t 30` | + +--- + +## Quand contacter le support + +Si vous avez suivi les étapes de dépannage ci-dessus et que le problème persiste, ouvrez un ticket de support : + +1. Depuis l'[espace client OVHcloud](/links/manager), allez dans **Support** → **Créer un ticket**. +2. Sélectionnez **Network** → **OVHcloud Connect**. +3. Incluez : + - Le **nom/ID de service** de votre OVHcloud Connect + - L'**horodatage** du problème (UTC) + - Les **symptômes** observés + - Les **sorties de diagnostic** (résumé BGP, état des interfaces, traceroute, valeurs optiques) + - Les **étapes déjà entreprises** pour le dépannage +4. Consultez [Déclarer et suivre un incident](../3.10_incident_followup/guide.fr-fr.md) pour le processus complet de gestion des incidents. + +--- + +## Et ensuite ? + +- Mettez en place un [monitoring](../3.9_monitor/guide.fr-fr.md) proactif pour détecter les problèmes avant qu'ils n'impactent vos utilisateurs +- Consultez [Prérequis et limitations](../1.8_prerequisites_limitations/guide.fr-fr.md) pour éviter les écueils connus +- Consultez la [FAQ](../5_faq/guide.fr-fr.md) pour les réponses aux questions courantes +- Vérifiez les [SLA](../1.7_slas/guide.fr-fr.md) pour les garanties de disponibilité et les avoirs de service + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/meta.yaml b/pages/network/ovhcloud_connect/1.9_troubleshooting/meta.yaml old mode 100755 new mode 100644 similarity index 100% rename from pages/network/ovhcloud_connect/occ-setup-diagnostics/meta.yaml rename to pages/network/ovhcloud_connect/1.9_troubleshooting/meta.yaml diff --git a/pages/network/ovhcloud_connect/2.1_quick_start_direct/guide.en-gb.md b/pages/network/ovhcloud_connect/2.1_quick_start_direct/guide.en-gb.md new file mode 100644 index 00000000000..3913ffc5018 --- /dev/null +++ b/pages/network/ovhcloud_connect/2.1_quick_start_direct/guide.en-gb.md @@ -0,0 +1,149 @@ +--- +title: 'Quick Start: Direct Connection to OVHcloud' +excerpt: 'Walk through the essential steps to establish a direct, private connection to OVHcloud' +updated: 2026-02-18 +--- + +## Objective + +This guide walks you through the essential steps to establish a **direct, private connection** between your infrastructure and OVHcloud — without using a third-party provider. + +## Before you begin + +Make sure you have: + +- ✅ An **OVHcloud account** with billing configured +- ✅ Equipment (or a circuit) in a **data centre where OVHcloud has a PoP** (see [PoP Locations](../1.4_pop_locations_regions/guide.en-gb.md)) +- ✅ A **router** that supports BGP and single-mode fibre optic interfaces +- ✅ A planned **IP addressing scheme** (peering IPs and prefixes to advertise) +- ✅ A private or public **ASN** (Autonomous System Number) + + +--- + +### OVHcloud Control Panel Access + +- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Steps overview + +```svg + + + + + + 1 + Order OVHcloud Connect Direct + + + + 2 + Receive the LOA (Letter of Authorization) + + + + 3 + Install the physical cross-connect + + + + 4 + Configure your PoP (BGP session) + + + + 5 + Associate with your vRack + + + + 6 + Test and verify connectivity + + + + + + + + +``` + +### Step 1 — Order OVHcloud Connect Direct + +1. Select **Direct Connection**. +2. Choose your **PoP location** and **bandwidth** (e.g. 1 Gbps or 10 Gbps). +3. Fill in technical details: your ASN, contact information, and any special instructions for the data centre. +4. Review pricing and confirm the order. + +For detailed ordering steps, see [Order OVHcloud Connect Direct](../3.1_order_direct/guide.en-gb.md). + +### Step 2 — Receive the LOA + +After your order is validated, OVHcloud sends you a **Letter of Authorization (LOA)** by email. This document contains: + +- The data centre and rack/cage reference for OVHcloud's equipment +- The port designation on OVHcloud's side +- Instructions for the data centre operator + +### Step 3 — Install the physical cross-connect + +Give the LOA to your **data centre operator** (or handle it yourself if you manage your own cage). They will install a fibre-optic patch cable between your router port and OVHcloud's designated port. + +This step may take a few days depending on the data centre's processes. + +### Step 4 — Associate with your vRack + +Link your OVHcloud Connect service to your **vRack** so that your OVHcloud resources (servers, VMs, etc.) can communicate over the private connection. + +See [Associate an OVHcloud Connect to your vRack](../3.5_associate_vrack/guide.en-gb.md). + +### Step 5 — Configure BGP + +Once the physical link is up: + +1. In the OVHcloud Control Panel, go to your OVHcloud Connect service and **create a PoP configuration** with the BGP session parameters. +2. On **your router**, configure a BGP neighbour using the peering IP and OVHcloud's ASN provided in the configuration details. +3. Advertise the IP prefixes you want to reach from OVHcloud. + +For detailed BGP configuration, see [Configure OCC L3 with BGP](../3.7_occ_l3_bgp/guide.en-gb.md). + +### Step 6 — Test and verify + +Run these checks to confirm everything is working: + +| Check | How | +|---|---| +| **Physical link** | Confirm the port shows as "up" in the OVHcloud Control Panel and on your router (`show interfaces`). | +| **BGP session** | Verify the session is **Established**: `show ip bgp summary` (Cisco) or `show bgp summary` (Juniper). | +| **Route exchange** | Confirm routes from OVHcloud appear in your routing table and vice versa. | +| **Connectivity** | Ping a known OVHcloud resource (e.g. a VM in your vRack) from your on-premises network. | +| **Traceroute** | Run `traceroute` to confirm traffic takes the private path (not the internet). | + +## Troubleshooting + +| Issue | What to check | +|---|---| +| Port shows "down" | Physical cable, SFP/transceiver compatibility, data centre cross-connect status | +| BGP session stuck in "Active" or "Idle" | Peer IP addresses, ASN configuration, firewall rules (TCP port 179) | +| No routes exchanged | BGP prefix filters, route-map configuration, maximum-prefix limits | +| Cannot ping OVHcloud resources | vRack association, VLAN ID, subnet configuration in AZ | + +If you cannot resolve the issue, [open a support ticket](../3.10_incident_followup/guide.en-gb.md) with your BGP output, interface status, and traceroute results. + +## What's next? + +- For a managed connection, see [Quick Start: Provider Connection](../2.2_quick_start_provider/guide.en-gb.md) +- For resilient setups, see [Resilient On-Prem tutorial](../4.2_resilient/4.1.2_onprem_resilient/guide.en-gb.md) +- Set up [monitoring](../3.9_monitor/guide.en-gb.md) for your connection + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/2.1_quick_start_direct/guide.fr-fr.md b/pages/network/ovhcloud_connect/2.1_quick_start_direct/guide.fr-fr.md new file mode 100644 index 00000000000..0d50cc04cc9 --- /dev/null +++ b/pages/network/ovhcloud_connect/2.1_quick_start_direct/guide.fr-fr.md @@ -0,0 +1,149 @@ +--- +title: 'Quick Start : connexion Direct vers OVHcloud' +excerpt: 'Suivez les étapes essentielles pour établir une connexion privée et directe vers OVHcloud' +updated: 2026-02-18 +--- + +## Objectif + +Ce guide vous accompagne dans les étapes essentielles pour établir une **connexion privée et directe** entre votre infrastructure et OVHcloud — sans passer par un provider tiers. + +## Avant de commencer + +Assurez-vous de disposer de : + +- Un **compte OVHcloud** avec une facturation configurée +- D'un équipement (ou d'un circuit) dans un **datacenter où OVHcloud dispose d'un PoP** (consultez [Emplacements des PoPs](../1.4_pop_locations_regions/guide.fr-fr.md)) +- D'un **routeur** prenant en charge BGP et les interfaces fibre optique monomode +- D'un **plan d'adressage IP** prévu (IPs de peering et préfixes à annoncer) +- D'un **ASN** (Autonomous System Number) privé ou public + + +--- + +### Accès à l'espace client OVHcloud + +- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Vue d'ensemble des étapes + +```svg + + + + + + 1 + Commander OVHcloud Connect Direct + + + + 2 + Recevoir la LOA (Lettre d'autorisation) + + + + 3 + Installer le cross-connect physique + + + + 4 + Configurer votre PoP (session BGP) + + + + 5 + Associer à votre vRack + + + + 6 + Tester et vérifier la connectivité + + + + + + + + +``` + +### Étape 1 — Commander OVHcloud Connect Direct + +1. Sélectionnez **Connexion Direct**. +2. Choisissez votre **emplacement de PoP** et la **bande passante** (par exemple 1 Gbps ou 10 Gbps). +3. Renseignez les détails techniques : votre ASN, vos coordonnées et toute instruction particulière pour le datacenter. +4. Vérifiez la tarification et confirmez la commande. + +Pour les étapes de commande détaillées, consultez [Commander OVHcloud Connect Direct](../3.1_order_direct/guide.fr-fr.md). + +### Étape 2 — Recevoir la LOA + +Une fois votre commande validée, OVHcloud vous envoie une **Lettre d'autorisation (LOA)** par e-mail. Ce document contient : + +- La référence du datacenter et du rack/cage de l'équipement OVHcloud +- La désignation du port côté OVHcloud +- Les instructions pour l'opérateur du datacenter + +### Étape 3 — Installer le cross-connect physique + +Remettez la LOA à votre **opérateur de datacenter** (ou prenez-la en charge vous-même si vous gérez votre propre cage). Il installera un câble de brassage en fibre optique entre le port de votre routeur et le port désigné d'OVHcloud. + +Cette étape peut prendre quelques jours selon les processus du datacenter. + +### Étape 4 — Associer à votre vRack + +Reliez votre service OVHcloud Connect à votre **vRack** afin que vos ressources OVHcloud (serveurs, VMs, etc.) puissent communiquer via la connexion privée. + +Consultez [Associer un OVHcloud Connect à votre vRack](../3.5_associate_vrack/guide.fr-fr.md). + +### Étape 5 — Configurer BGP + +Une fois le lien physique opérationnel : + +1. Dans l'espace client OVHcloud, accédez à votre service OVHcloud Connect et **créez une configuration de PoP** avec les paramètres de session BGP. +2. Sur **votre routeur**, configurez un voisin BGP en utilisant l'IP de peering et l'ASN d'OVHcloud fournis dans les détails de configuration. +3. Annoncez les préfixes IP que vous souhaitez atteindre depuis OVHcloud. + +Pour la configuration BGP détaillée, consultez [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp/guide.fr-fr.md). + +### Étape 6 — Tester et vérifier + +Effectuez ces vérifications pour confirmer que tout fonctionne : + +| Vérification | Comment | +|---|---| +| **Lien physique** | Vérifiez que le port apparaît comme « up » dans l'espace client OVHcloud et sur votre routeur (`show interfaces`). | +| **Session BGP** | Vérifiez que la session est **Established** : `show ip bgp summary` (Cisco) ou `show bgp summary` (Juniper). | +| **Échange de routes** | Vérifiez que les routes d'OVHcloud apparaissent dans votre table de routage et inversement. | +| **Connectivité** | Effectuez un ping vers une ressource OVHcloud connue (par exemple une VM dans votre vRack) depuis votre réseau on-premises. | +| **Traceroute** | Exécutez un `traceroute` pour vérifier que le trafic emprunte bien le chemin privé (et non internet). | + +## Dépannage + +| Problème | Que vérifier | +|---|---| +| Le port apparaît « down » | Câble physique, compatibilité SFP/transceiver, statut du cross-connect côté datacenter | +| Session BGP bloquée en « Active » ou « Idle » | IPs de peering, configuration ASN, règles de pare-feu (port TCP 179) | +| Aucune route échangée | Filtres de préfixes BGP, configuration des route-maps, limites maximum-prefix | +| Impossible de pinguer les ressources OVHcloud | Association au vRack, ID VLAN, configuration des sous-réseaux dans l'AZ | + +Si vous ne parvenez pas à résoudre le problème, [ouvrez un ticket de support](../3.10_incident_followup/guide.fr-fr.md) en joignant la sortie BGP, le statut des interfaces et les résultats du traceroute. + +## Et ensuite ? + +- Pour une connexion managée, consultez [Quick Start : connexion via Provider](../2.2_quick_start_provider/guide.fr-fr.md) +- Pour des montages résilients, consultez le [tutoriel On-Prem résilient](../4.2_resilient/4.1.2_onprem_resilient/guide.fr-fr.md) +- Mettez en place la [supervision](../3.9_monitor/guide.fr-fr.md) de votre connexion + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/meta.yaml b/pages/network/ovhcloud_connect/2.1_quick_start_direct/meta.yaml old mode 100755 new mode 100644 similarity index 100% rename from pages/network/ovhcloud_connect/occ-direct-control-panel/meta.yaml rename to pages/network/ovhcloud_connect/2.1_quick_start_direct/meta.yaml diff --git a/pages/network/ovhcloud_connect/2.2_quick_start_provider/guide.en-gb.md b/pages/network/ovhcloud_connect/2.2_quick_start_provider/guide.en-gb.md new file mode 100644 index 00000000000..63a9acb626e --- /dev/null +++ b/pages/network/ovhcloud_connect/2.2_quick_start_provider/guide.en-gb.md @@ -0,0 +1,144 @@ +--- +title: 'Quick Start: Connection to OVHcloud with a Provider' +excerpt: 'Walk through the steps to connect to OVHcloud using a third-party network provider' +updated: 2026-02-18 +--- + +## Objective + +This guide walks you through connecting to OVHcloud using a **third-party network provider** (such as Megaport, Equinix Fabric, or Console Connect). A provider handles the physical connectivity on your behalf, so you don't need to be present in the same data centre as OVHcloud. + +## Before you begin + +Make sure you have: + +- ✅ An **OVHcloud account** with billing configured +- ✅ A contract or account with a **supported provider** (see [Providers](../1.3_providers)) +- ✅ A **router** that supports BGP peering (OVHcloud Connect Provider is always a Layer 3 service) +- ✅ A planned **IP addressing scheme** and **ASN** + + +--- + +### OVHcloud Control Panel Access + +- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Steps overview + +```svg + + + + + + 1 + Order OVHcloud Connect Provider + + + + 2 + Share the pairing key with your provider + + + + 3 + Provider provisions the connection + + + + 4 + Verify BGP session and routing + + + + 5 + Associate with your vRack + + + + 6 + Test and verify connectivity + + + + + + + + +``` + +### Step 1 — Order OVHcloud Connect Provider + +1. Select **Provider Connection**. +2. Choose your **provider**, **PoP location**, and **bandwidth**. +3. Review pricing and submit the order. +4. OVHcloud generates a **pairing key** (also called a service key) for your provider. + +For detailed steps, see [Order OVHcloud Connect Provider](../3.2_order_provider). + +### Step 2 — Share the pairing key + +Give the **pairing key** to your provider. This key allows the provider to identify and activate the connection to OVHcloud on your behalf. + +- On **Megaport**: create a VXC (Virtual Cross Connect) to OVHcloud and enter the pairing key. +- On **Equinix Fabric**: create a connection to OVHcloud and provide the service key. +- On **Console Connect**: initiate a connection to OVHcloud and use the pairing key. + +### Step 3 — Provider provisions the connection + +The provider sets up the physical and logical link between their infrastructure and OVHcloud's PoP. This is usually fast (minutes to hours for on-demand providers like Megaport), but timing varies. + +You can track the connection status in both the **OVHcloud Control Panel** and your **provider's portal**. + +### Step 4 — Associate with your vRack + +Link the OVHcloud Connect service to your **vRack**: + +1. In the OVHcloud Control Panel, go to **vRack**. +2. Add your OVHcloud Connect service. +3. Configure the required VLANs and subnets. + +See [Associate an OVHcloud Connect to your vRack](../3.5_associate_vrack). + +### Step 5 — Verify BGP session and routing + +OVHcloud Connect Provider is always a Layer 3 service — BGP peering is established between your router (or your provider's router, depending on your provider offering) and the OVHcloud PoP. Verify in the OVHcloud Control Panel and in your provider's portal that the session is established and routes are being exchanged. + +See [Configure OCC L3 with BGP](../3.7_occ_l3_bgp) for detailed guidance. + +### Step 6 — Test and verify + +| Check | How | +|---|---| +| **Connection status** | Shows "Active" in OVHcloud Control Panel and provider portal | +| **BGP session** | Established — check on your router and in the OVHcloud Control Panel | +| **Routes** | Your prefixes visible on OVHcloud side; OVHcloud routes visible on your side | +| **Ping** | Ping an OVHcloud resource from your network | +| **Traceroute** | Verify traffic goes through the private link, not the internet | + +## Troubleshooting + +| Issue | What to check | +|---|---| +| Connection stuck in "Pending" | Verify the pairing key was entered correctly on the provider's side | +| Provider shows "Active" but OVHcloud shows "Down" | Contact OVHcloud support — there may be a provisioning delay | +| BGP session not establishing | Check peering IPs, ASN, and VLAN ID on both your router and the OVHcloud PoP configuration | +| High latency or packet loss | Check provider's network status page; run traceroute to identify where delays occur | + +## What's next? + +- For a self-managed connection, see [Quick Start: Direct Connection](../2.1_quick_start_direct) +- Set up [monitoring](../3.9_monitor) +- Explore [resilient architectures](../4.2_resilient/4.1.2_onprem_resilient) + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/2.2_quick_start_provider/guide.fr-fr.md b/pages/network/ovhcloud_connect/2.2_quick_start_provider/guide.fr-fr.md new file mode 100644 index 00000000000..b7578066d02 --- /dev/null +++ b/pages/network/ovhcloud_connect/2.2_quick_start_provider/guide.fr-fr.md @@ -0,0 +1,144 @@ +--- +title: 'Quick Start : connexion à OVHcloud avec un Provider' +excerpt: 'Suivez les étapes pour vous connecter à OVHcloud via un opérateur réseau tiers' +updated: 2026-02-18 +--- + +## Objectif + +Ce guide vous accompagne dans la connexion à OVHcloud via un **opérateur réseau tiers** (par exemple Megaport, Equinix Fabric ou Console Connect). Un provider prend en charge la connectivité physique pour votre compte, ce qui vous évite d'avoir à être présent dans le même datacenter qu'OVHcloud. + +## Avant de commencer + +Assurez-vous de disposer de : + +- Un **compte OVHcloud** avec une facturation configurée +- D'un contrat ou d'un compte chez un **provider pris en charge** (consultez [Providers](../1.3_providers)) +- D'un **routeur** prenant en charge le peering BGP (OVHcloud Connect Provider est toujours un service Layer 3) +- D'un **plan d'adressage IP** prévu et d'un **ASN** + + +--- + +### Accès à l'espace client OVHcloud + +- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Vue d'ensemble des étapes + +```svg + + + + + + 1 + Commander OVHcloud Connect Provider + + + + 2 + Partager la clé d'appairage avec votre provider + + + + 3 + Le provider provisionne la connexion + + + + 4 + Vérifier la session BGP et le routage + + + + 5 + Associer à votre vRack + + + + 6 + Tester et vérifier la connectivité + + + + + + + + +``` + +### Étape 1 — Commander OVHcloud Connect Provider + +1. Sélectionnez **Connexion via Provider**. +2. Choisissez votre **provider**, votre **emplacement de PoP** et la **bande passante**. +3. Vérifiez la tarification et soumettez la commande. +4. OVHcloud génère une **clé d'appairage** (également appelée clé de service) destinée à votre provider. + +Pour les étapes détaillées, consultez [Commander OVHcloud Connect Provider](../3.2_order_provider). + +### Étape 2 — Partager la clé d'appairage + +Communiquez la **clé d'appairage** à votre provider. Cette clé permet au provider d'identifier et d'activer la connexion vers OVHcloud pour votre compte. + +- Sur **Megaport** : créez un VXC (Virtual Cross Connect) vers OVHcloud et saisissez la clé d'appairage. +- Sur **Equinix Fabric** : créez une connexion vers OVHcloud et fournissez la clé de service. +- Sur **Console Connect** : initiez une connexion vers OVHcloud et utilisez la clé d'appairage. + +### Étape 3 — Le provider provisionne la connexion + +Le provider met en place le lien physique et logique entre son infrastructure et le PoP OVHcloud. Cela est généralement rapide (de quelques minutes à quelques heures pour les providers à la demande comme Megaport), mais les délais peuvent varier. + +Vous pouvez suivre le statut de la connexion à la fois dans l'**espace client OVHcloud** et dans le **portail de votre provider**. + +### Étape 4 — Associer à votre vRack + +Reliez le service OVHcloud Connect à votre **vRack** : + +1. Dans l'espace client OVHcloud, rendez-vous sur **vRack**. +2. Ajoutez votre service OVHcloud Connect. +3. Configurez les VLANs et sous-réseaux requis. + +Consultez [Associer un OVHcloud Connect à votre vRack](../3.5_associate_vrack). + +### Étape 5 — Vérifier la session BGP et le routage + +OVHcloud Connect Provider est toujours un service Layer 3 — un peering BGP est établi entre votre routeur (ou celui de votre provider, selon l'offre du provider) et le PoP OVHcloud. Vérifiez dans l'espace client OVHcloud et dans le portail de votre provider que la session est établie et que les routes sont bien échangées. + +Consultez [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp) pour des instructions détaillées. + +### Étape 6 — Tester et vérifier + +| Vérification | Comment | +|---|---| +| **Statut de la connexion** | Affiche « Active » dans l'espace client OVHcloud et dans le portail du provider | +| **Session BGP** | Établie — vérifiez sur votre routeur et dans l'espace client OVHcloud | +| **Routes** | Vos préfixes sont visibles côté OVHcloud ; les routes OVHcloud sont visibles de votre côté | +| **Ping** | Effectuez un ping vers une ressource OVHcloud depuis votre réseau | +| **Traceroute** | Vérifiez que le trafic emprunte le lien privé et non internet | + +## Dépannage + +| Problème | Que vérifier | +|---|---| +| Connexion bloquée en « Pending » | Vérifiez que la clé d'appairage a été correctement saisie côté provider | +| Le provider affiche « Active » mais OVHcloud affiche « Down » | Contactez le support OVHcloud — il peut s'agir d'un délai de provisionnement | +| La session BGP ne s'établit pas | Vérifiez les IPs de peering, l'ASN et l'ID VLAN à la fois sur votre routeur et dans la configuration de PoP OVHcloud | +| Latence élevée ou perte de paquets | Consultez la page de statut réseau du provider ; exécutez un traceroute pour identifier où se produisent les délais | + +## Et ensuite ? + +- Pour une connexion auto-gérée, consultez [Quick Start : connexion Direct](../2.1_quick_start_direct) +- Mettez en place la [supervision](../3.9_monitor) +- Explorez les [architectures résilientes](../4.2_resilient/4.1.2_onprem_resilient) + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/meta.yaml b/pages/network/ovhcloud_connect/2.2_quick_start_provider/meta.yaml old mode 100755 new mode 100644 similarity index 100% rename from pages/network/ovhcloud_connect/occ-provider-control-panel/meta.yaml rename to pages/network/ovhcloud_connect/2.2_quick_start_provider/meta.yaml diff --git a/pages/network/ovhcloud_connect/3.10_incident_followup/guide.en-gb.md b/pages/network/ovhcloud_connect/3.10_incident_followup/guide.en-gb.md new file mode 100644 index 00000000000..098e95e9604 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.10_incident_followup/guide.en-gb.md @@ -0,0 +1,162 @@ +--- +title: 'Declare and Follow Up Upon an Incident' +excerpt: 'Learn how to report an OVHcloud Connect incident, provide diagnostic information, and track resolution' +updated: 2026-02-18 +--- + +## Objective + +If you experience a service degradation or outage on your OVHcloud Connect link, follow this guide to report the incident, provide the right diagnostic information, and track resolution. + +## Step 1 — Gather diagnostic information + +Before contacting support, collect the following information to speed up diagnosis: + +### Incident triage checklist + +| Information | How to collect it | +|---|---| +| **Timestamp (UTC)** | Note exactly when the issue started and its duration | +| **Affected service** | OVHcloud Connect service name/ID, PoP, VLAN ID | +| **Symptoms** | Link down, BGP session drop, packet loss, high latency, etc. | +| **Interface status** | `show interfaces` (Cisco) or `show interfaces terse` (Juniper) | +| **BGP status** | `show ip bgp summary` (Cisco) or `show bgp summary` (Juniper) | +| **Traceroute** | Run from your side to an OVHcloud resource, and vice versa | +| **MTR output** | If available, run `mtr` for a combined ping + traceroute with loss % | +| **Recent changes** | Any configuration changes, maintenance, or updates before the incident | + +### Example diagnostic commands + +**Cisco IOS:** +``` +show ip bgp summary +show interfaces GigabitEthernet0/0 +show ip route +traceroute 172.16.1.10 +``` + +**Juniper JunOS:** +``` +show bgp summary +show interfaces terse +show route +traceroute 172.16.1.10 +``` + +**From a Linux host in OVHcloud:** +```bash +ping -c 10 10.0.0.1 +traceroute 10.0.0.1 +mtr -r -c 50 10.0.0.1 +``` + +## Step 2 — Check for known issues + +Before opening a ticket, verify whether the issue is already known: + +- **OVHcloud status page** — Check the OVHcloud status and scheduled maintenance pages (accessible from the Control Panel). +- **Provider status page** — If using a provider (Megaport, Equinix, Console Connect), check their status/maintenance pages. +- **Your own monitoring** — Confirm the issue is not on your side (local router failure, ISP outage, etc.). + + +--- + +### OVHcloud Control Panel Access + +- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Step 3 — Open a support ticket + +1. Go to **Support** → **Create a ticket** (or navigate to the support section). +2. Select the category related to **Network** / **OVHcloud Connect**. +3. Provide a clear **subject line** (e.g. "OVHcloud Connect — BGP session down since 14:30 UTC"). +4. In the description, include: + - Your OVHcloud Connect **service name/ID** + - **Timestamp** of the issue (UTC) + - **Symptoms** observed + - **Diagnostic outputs** (paste BGP summary, interface status, traceroute) + - **Impact** on your business (number of users affected, critical services down) +5. Attach any **screenshots** or log files. +6. Submit the ticket and note the **ticket number**. + +> **Tip:** The more detailed your initial report, the faster the support team can diagnose the issue. + +## Step 4 — Follow up + +| Action | When | +|---|---| +| **Check ticket status** | Regularly, through the OVHcloud Control Panel | +| **Respond to requests** | If support asks for additional information, provide it promptly | +| **Escalate if needed** | For critical business impact, request priority handling or escalation | +| **Keep a chronology** | Maintain a timeline of events, communications, and status changes | + +### Escalation + +If the issue is **business-critical** and you are not getting a timely response: + +1. Reference the SLA terms in your contract (see [SLAs](../1.7_slas/guide.en-gb.md)). +2. Request an escalation through the support portal. +3. Contact your OVHcloud account manager for priority handling. + +## Step 5 — Post-incident + +After the incident is resolved: + +1. **Request a Root Cause Analysis (RCA)** — Ask OVHcloud support for a post-incident report explaining what happened and what measures are being taken to prevent recurrence. +2. **Update your runbooks** — Document the incident, resolution steps, and lessons learned. +3. **Implement mitigations** — If the incident revealed a gap (e.g. missing redundancy, inadequate monitoring), plan improvements. +4. **Verify SLA compliance** — If the incident caused downtime beyond the SLA commitment, you may be eligible for service credits (see [SLAs](../1.7_slas/guide.en-gb.md)). + +## Summary: incident response flow + +```svg + + + + + Detect + Alert or user report + + + Diagnose + Collect logs & data + + + Report + Open support ticket + + + Resolve + Fix & verify + + + Post-incident + RCA & improvements + + + + + + + + + + + + +``` + +## What's next? + +- Set up proactive [monitoring](../3.9_monitor/guide.en-gb.md) to detect issues before they impact your users +- Review your [SLA](../1.7_slas/guide.en-gb.md) commitments + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/3.10_incident_followup/guide.fr-fr.md b/pages/network/ovhcloud_connect/3.10_incident_followup/guide.fr-fr.md new file mode 100644 index 00000000000..60f0dbfae29 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.10_incident_followup/guide.fr-fr.md @@ -0,0 +1,162 @@ +--- +title: 'Déclarer et suivre un incident' +excerpt: 'Découvrez comment signaler un incident OVHcloud Connect, fournir les informations de diagnostic et suivre la résolution' +updated: 2026-02-18 +--- + +## Objectif + +Si vous constatez une dégradation de service ou une interruption sur votre lien OVHcloud Connect, suivez ce guide pour signaler l'incident, fournir les bonnes informations de diagnostic et suivre la résolution. + +## Étape 1 — Recueillir les informations de diagnostic + +Avant de contacter le support, collectez les informations suivantes pour accélérer le diagnostic : + +### Liste de contrôle pour le tri d'incident + +| Information | Comment la collecter | +|---|---| +| **Horodatage (UTC)** | Notez précisément le début du problème et sa durée | +| **Service concerné** | Nom/ID du service OVHcloud Connect, PoP, ID de VLAN | +| **Symptômes** | Lien down, chute de session BGP, perte de paquets, latence élevée, etc. | +| **État de l'interface** | `show interfaces` (Cisco) ou `show interfaces terse` (Juniper) | +| **État BGP** | `show ip bgp summary` (Cisco) ou `show bgp summary` (Juniper) | +| **Traceroute** | À exécuter de votre côté vers une ressource OVHcloud, et inversement | +| **Sortie MTR** | Si disponible, exécutez `mtr` pour combiner ping et traceroute avec le pourcentage de pertes | +| **Changements récents** | Toute modification de configuration, maintenance ou mise à jour avant l'incident | + +### Exemples de commandes de diagnostic + +**Cisco IOS :** +``` +show ip bgp summary +show interfaces GigabitEthernet0/0 +show ip route +traceroute 172.16.1.10 +``` + +**Juniper JunOS :** +``` +show bgp summary +show interfaces terse +show route +traceroute 172.16.1.10 +``` + +**Depuis un hôte Linux dans OVHcloud :** +```bash +ping -c 10 10.0.0.1 +traceroute 10.0.0.1 +mtr -r -c 50 10.0.0.1 +``` + +## Étape 2 — Vérifier les incidents connus + +Avant d'ouvrir un ticket, vérifiez si le problème est déjà connu : + +- **Page de statut OVHcloud** — Consultez les pages de statut OVHcloud et de maintenances planifiées (accessibles depuis l'espace client). +- **Page de statut du fournisseur** — Si vous utilisez un fournisseur (Megaport, Equinix, Console Connect), consultez ses pages de statut/maintenance. +- **Votre propre supervision** — Confirmez que le problème ne se situe pas de votre côté (panne du routeur local, panne du FAI, etc.). + + +--- + +### Accès à l'espace client OVHcloud + +- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Étape 3 — Ouvrir un ticket de support + +1. Allez dans **Support** puis **Créer un ticket** (ou rendez-vous dans la section support). +2. Sélectionnez la catégorie liée à **Réseau** / **OVHcloud Connect**. +3. Indiquez un **objet** clair (par exemple : « OVHcloud Connect — session BGP down depuis 14h30 UTC »). +4. Dans la description, incluez : + - Le **nom/ID du service** OVHcloud Connect + - L'**horodatage** du problème (UTC) + - Les **symptômes** observés + - Les **sorties de diagnostic** (collez le résumé BGP, l'état d'interface, le traceroute) + - L'**impact** sur votre activité (nombre d'utilisateurs concernés, services critiques indisponibles) +5. Joignez toutes les **captures d'écran** ou fichiers de logs. +6. Soumettez le ticket et notez le **numéro de ticket**. + +> **Astuce :** plus votre rapport initial est détaillé, plus l'équipe de support pourra diagnostiquer le problème rapidement. + +## Étape 4 — Suivre + +| Action | Quand | +|---|---| +| **Vérifier le statut du ticket** | Régulièrement, depuis l'espace client OVHcloud | +| **Répondre aux demandes** | Si le support demande des informations complémentaires, fournissez-les rapidement | +| **Escalader si nécessaire** | En cas d'impact métier critique, demandez un traitement prioritaire ou une escalade | +| **Tenir une chronologie** | Conservez une chronologie des événements, communications et changements de statut | + +### Escalade + +Si le problème est **critique pour votre activité** et que vous n'obtenez pas de réponse dans les délais : + +1. Référez-vous aux conditions de SLA de votre contrat (voir [SLA](../1.7_slas/guide.fr-fr.md)). +2. Demandez une escalade via le portail de support. +3. Contactez votre interlocuteur commercial OVHcloud pour un traitement prioritaire. + +## Étape 5 — Post-incident + +Une fois l'incident résolu : + +1. **Demandez une analyse de cause racine (RCA)** — Demandez au support OVHcloud un rapport post-incident expliquant ce qu'il s'est passé et les mesures prises pour éviter une récidive. +2. **Mettez à jour vos runbooks** — Documentez l'incident, les étapes de résolution et les enseignements tirés. +3. **Mettez en place des mesures correctives** — Si l'incident a révélé une faiblesse (par exemple un manque de redondance, une supervision insuffisante), planifiez les améliorations. +4. **Vérifiez la conformité au SLA** — Si l'incident a entraîné une indisponibilité supérieure à l'engagement SLA, vous pouvez être éligible à des avoirs (voir [SLA](../1.7_slas/guide.fr-fr.md)). + +## Synthèse : flux de réponse à incident + +```svg + + + + + Détecter + Alerte ou signalement + + + Diagnostiquer + Collecter logs et données + + + Signaler + Ouvrir un ticket de support + + + Résoudre + Corriger et vérifier + + + Post-incident + RCA et améliorations + + + + + + + + + + + + +``` + +## Et ensuite ? + +- Mettez en place une [supervision](../3.9_monitor/guide.fr-fr.md) proactive afin de détecter les problèmes avant qu'ils n'impactent vos utilisateurs +- Passez en revue vos engagements [SLA](../1.7_slas/guide.fr-fr.md) + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/3.10_incident_followup/meta.yaml b/pages/network/ovhcloud_connect/3.10_incident_followup/meta.yaml new file mode 100644 index 00000000000..783ebbf91f9 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.10_incident_followup/meta.yaml @@ -0,0 +1,2 @@ +id: c908eeeb-35eb-48b5-815f-06a1c948fa2f +full_slug: network-ovhcloud-connect-incident-followup diff --git a/pages/network/ovhcloud_connect/3.11_cross_connect_loa/guide.en-gb.md b/pages/network/ovhcloud_connect/3.11_cross_connect_loa/guide.en-gb.md new file mode 100644 index 00000000000..4038772ed14 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.11_cross_connect_loa/guide.en-gb.md @@ -0,0 +1,114 @@ +--- +title: 'Order or cancel a Cross Connect with an LOA' +excerpt: 'Learn how to order or cancel a physical cross-connect using a Letter of Authorization' +updated: 2026-02-18 +--- + +## Objective + +A **cross-connect** is a physical fibre-optic cable that links your equipment (or your provider's equipment) to OVHcloud's equipment inside a data centre. A **Letter of Authorization (LOA)** is the document that authorises the data centre operator to install or remove this cable. + +## What is an LOA? + +An LOA is a formal document that contains: + +- **Data centre name and address** — The facility where the cross-connect will be installed or removed. +- **OVHcloud's rack/cage reference** — The exact location of OVHcloud's equipment. +- **Port designation** — The specific port on OVHcloud's patch panel or router. +- **Authorised party** — Who is allowed to perform the work (you, your provider, or the facility operator). +- **Cable specifications** — Type of fibre (single-mode), connector type (LC/SC), and length. + +```svg + + + + + + Your Equipment + Cage / Cabinet A + + + + Cross-Connect + (fibre patch cable) + + + + OVHcloud Equipment + Cage / Cabinet B + + + + LOA + DC: Equinix PA3 + Rack: OVH-FR-01 + Port: Gi0/0/1 + Type: SM LC + +``` + +## Ordering a cross-connect + +### Step 1 — Obtain the LOA from OVHcloud + +After you order **OVHcloud Connect Direct**, OVHcloud will provide the LOA: + +- **Automatically by email** after your order is confirmed. +- **Through the OVHcloud Control Panel** — in your OVHcloud Connect service details, look for a "Download LOA" option. +- **Via support** — If you haven't received it, contact OVHcloud support with your service reference. + +### Step 2 — Submit the LOA to the data centre operator + +1. Contact the **data centre operator** (e.g. Equinix, Interxion/Digital Realty, Telehouse) and submit a cross-connect order. +2. Attach the **LOA from OVHcloud**. +3. Specify: + - **Your cage/cabinet reference** (A-end) + - **OVHcloud's cage/cabinet reference** (Z-end, from the LOA) + - **Cable type** — Typically single-mode fibre with LC connectors + - **Requested completion date** +4. The data centre operator may charge a **cross-connect installation fee** and a **monthly recurring fee**. + +### Step 3 — Confirm installation + +1. The data centre operator installs the physical cable (typically within a few business days). +2. Verify in the **OVHcloud Control Panel** that the port status changes to "Up". +3. Proceed with [BGP configuration](../3.7_occ_l3_bgp/guide.en-gb.md). + +## Cancelling a cross-connect + +### Step 1 — Cancel the OVHcloud Connect service first + +Before removing the physical cable, cancel the OVHcloud Connect service (see [Cancel Direct](../3.3_cancel_direct/guide.en-gb.md) or [Cancel Provider](../3.4_cancel_provider/guide.en-gb.md)). + +### Step 2 — Request cross-connect removal + +1. Contact the **data centre operator**. +2. Submit a **de-installation order** for the cross-connect. +3. Some data centres require an **LOA for removal** — check with the operator. If needed, request one from OVHcloud support. +4. Confirm the physical cable has been removed. + +### Step 3 — Verify billing + +- Confirm with the data centre operator that the **monthly cross-connect fee** has been stopped. +- Verify on the OVHcloud side that the service is no longer billed. + +## Important tips + +| Tip | Details | +|---|---| +| **Keep copies of all LOAs** | Store them in your documentation for future reference and audits. | +| **Track lead times** | Cross-connect installation timelines vary by data centre (1–10 business days is typical). | +| **Coordinate with your provider** | If using OVHcloud Connect Provider, the provider typically handles the cross-connect for you. | +| **Match cable types** | Ensure your side uses the same fibre type (single-mode) and connector (LC) as specified in the LOA. | +| **Test after installation** | Once the cable is patched, verify optical light levels and port status before configuring BGP. | + +## What's next? + +- [Configure OCC L3 with BGP](../3.7_occ_l3_bgp/guide.en-gb.md) after the cross-connect is installed +- [Order OVHcloud Connect Direct](../3.1_order_direct/guide.en-gb.md) if you haven't started the process yet + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/3.11_cross_connect_loa/guide.fr-fr.md b/pages/network/ovhcloud_connect/3.11_cross_connect_loa/guide.fr-fr.md new file mode 100644 index 00000000000..cbf08f3b164 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.11_cross_connect_loa/guide.fr-fr.md @@ -0,0 +1,114 @@ +--- +title: 'Commander ou résilier un cross-connect avec une LOA' +excerpt: 'Découvrez comment commander ou résilier un cross-connect physique à l''aide d''une lettre d''autorisation' +updated: 2026-02-18 +--- + +## Objectif + +Un **cross-connect** est un câble fibre optique physique qui relie votre équipement (ou celui de votre fournisseur) à l'équipement OVHcloud à l'intérieur d'un datacenter. Une **lettre d'autorisation (LOA)** est le document qui autorise l'opérateur du datacenter à installer ou retirer ce câble. + +## Qu'est-ce qu'une LOA ? + +Une LOA est un document formel qui contient : + +- **Nom et adresse du datacenter** — Le site où le cross-connect sera installé ou retiré. +- **Référence de la baie/cage OVHcloud** — L'emplacement exact de l'équipement OVHcloud. +- **Désignation du port** — Le port spécifique sur le panneau de brassage ou le routeur OVHcloud. +- **Partie autorisée** — Qui est autorisé à effectuer l'intervention (vous, votre fournisseur ou l'opérateur du site). +- **Spécifications du câble** — Type de fibre (monomode), type de connecteur (LC/SC) et longueur. + +```svg + + + + + + Votre équipement + Cage / Baie A + + + + Cross-Connect + (jarretière fibre) + + + + Équipement OVHcloud + Cage / Baie B + + + + LOA + DC : Equinix PA3 + Baie : OVH-FR-01 + Port : Gi0/0/1 + Type : SM LC + +``` + +## Commander un cross-connect + +### Étape 1 — Obtenir la LOA auprès d'OVHcloud + +Après avoir commandé **OVHcloud Connect Direct**, OVHcloud vous fournit la LOA : + +- **Automatiquement par e-mail** après la confirmation de votre commande. +- **Via l'espace client OVHcloud** — dans les détails de votre service OVHcloud Connect, recherchez l'option « Télécharger la LOA ». +- **Via le support** — Si vous ne l'avez pas reçue, contactez le support OVHcloud avec la référence de votre service. + +### Étape 2 — Soumettre la LOA à l'opérateur du datacenter + +1. Contactez l'**opérateur du datacenter** (par exemple Equinix, Interxion/Digital Realty, Telehouse) et soumettez une commande de cross-connect. +2. Joignez la **LOA fournie par OVHcloud**. +3. Précisez : + - La **référence de votre cage/baie** (côté A) + - La **référence de la cage/baie OVHcloud** (côté Z, indiquée dans la LOA) + - Le **type de câble** — Typiquement de la fibre monomode avec connecteurs LC + - La **date de réalisation souhaitée** +4. L'opérateur du datacenter peut facturer des **frais d'installation du cross-connect** ainsi qu'une **redevance mensuelle**. + +### Étape 3 — Confirmer l'installation + +1. L'opérateur du datacenter installe le câble physique (généralement sous quelques jours ouvrés). +2. Vérifiez dans l'**espace client OVHcloud** que le statut du port passe à « Up ». +3. Procédez à la [configuration BGP](../3.7_occ_l3_bgp/guide.fr-fr.md). + +## Résilier un cross-connect + +### Étape 1 — Résilier d'abord le service OVHcloud Connect + +Avant de retirer le câble physique, résiliez le service OVHcloud Connect (voir [Résilier Direct](../3.3_cancel_direct/guide.fr-fr.md) ou [Résilier Provider](../3.4_cancel_provider/guide.fr-fr.md)). + +### Étape 2 — Demander le retrait du cross-connect + +1. Contactez l'**opérateur du datacenter**. +2. Soumettez une **commande de désinstallation** du cross-connect. +3. Certains datacenters exigent une **LOA pour le retrait** — vérifiez auprès de l'opérateur. Si nécessaire, demandez-en une au support OVHcloud. +4. Confirmez que le câble physique a bien été retiré. + +### Étape 3 — Vérifier la facturation + +- Confirmez auprès de l'opérateur du datacenter que la **redevance mensuelle de cross-connect** a bien été stoppée. +- Vérifiez côté OVHcloud que le service n'est plus facturé. + +## Conseils importants + +| Conseil | Détails | +|---|---| +| **Conservez les copies de toutes les LOA** | Stockez-les dans votre documentation pour référence et audits ultérieurs. | +| **Suivez les délais** | Les délais d'installation d'un cross-connect varient selon le datacenter (de 1 à 10 jours ouvrés en général). | +| **Coordonnez avec votre fournisseur** | Si vous utilisez OVHcloud Connect Provider, le fournisseur prend généralement en charge le cross-connect pour vous. | +| **Faites correspondre les types de câbles** | Veillez à utiliser de votre côté le même type de fibre (monomode) et le même connecteur (LC) que ceux indiqués dans la LOA. | +| **Testez après installation** | Une fois le câble brassé, vérifiez les niveaux optiques et le statut du port avant de configurer BGP. | + +## Et ensuite ? + +- [Configurez OCC L3 avec BGP](../3.7_occ_l3_bgp/guide.fr-fr.md) une fois le cross-connect installé +- [Commandez OVHcloud Connect Direct](../3.1_order_direct/guide.fr-fr.md) si vous n'avez pas encore débuté la procédure + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/3.11_cross_connect_loa/meta.yaml b/pages/network/ovhcloud_connect/3.11_cross_connect_loa/meta.yaml new file mode 100644 index 00000000000..d246e4f7d21 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.11_cross_connect_loa/meta.yaml @@ -0,0 +1,2 @@ +id: c9b9132b-d44f-465c-b0b3-6fef6e36706a +full_slug: network-ovhcloud-connect-cross-connect-loa diff --git a/pages/network/ovhcloud_connect/occ-logs-2-customers/guide.en-gb.md b/pages/network/ovhcloud_connect/3.12_log_forwarding/guide.en-gb.md similarity index 74% rename from pages/network/ovhcloud_connect/occ-logs-2-customers/guide.en-gb.md rename to pages/network/ovhcloud_connect/3.12_log_forwarding/guide.en-gb.md index 585abd567fb..75d04510839 100644 --- a/pages/network/ovhcloud_connect/occ-logs-2-customers/guide.en-gb.md +++ b/pages/network/ovhcloud_connect/3.12_log_forwarding/guide.en-gb.md @@ -1,13 +1,14 @@ --- -title: OVHcloud Connect Logs Forwarding -excerpt: Find out how to forward your logs from an OCC service to Logs Data Platform -updated: 2025-08-28 +title: 'Set up logs forwarding for OVHcloud Connect' +excerpt: 'Forward your OVHcloud Connect event logs to Logs Data Platform for storage, querying, and visualisation' +updated: 2026-04-22 --- -  + ## Objective -The purpose of this guide is to show you how to enable the forwarding of logs from your OVHcloud Connect to Logs Data Platform (LDP), a platform that helps you store, archive, query and visualize your logs. -If you would like to find out more about Logs Data Platform before reading this guide, please refer to the [Logs Data Platform introduction guide](/pages/manage_and_operate/observability/logs_data_platform/getting_started_introduction_to_LDP). +The purpose of this guide is to show you how to enable the forwarding of logs from your OVHcloud Connect to Logs Data Platform (LDP), a platform that helps you store, archive, query and visualise your logs. + +If you would like to find out more about Logs Data Platform before reading this guide, refer to the [Logs Data Platform introduction guide](/pages/manage_and_operate/observability/logs_data_platform/getting_started_introduction_to_LDP). ## Glossary @@ -19,10 +20,30 @@ If you would like to find out more about Logs Data Platform before reading this ## Requirements - A Logs Data Platform (LDP) account with at least one active *Stream* configured. This guide will walk you through all the necessary steps: [Quick start for Logs Data Platform](/pages/manage_and_operate/observability/logs_data_platform/getting_started_quick_start). - - If you are not familiar with all the LDP *Stream* configuration possibilities, simply create a new one with the default options (indexing & websocket enabled, long-term storage disabled) for the purpose of this guide. -- An up-and-running [OVHcloud Connect service](/pages/network/ovhcloud_connect/occ-concepts-overview). + - If you are not familiar with all the LDP *Stream* configuration possibilities, create a new one with the default options (indexing and websocket enabled, long-term storage disabled) for the purpose of this guide. +- An up-and-running [OVHcloud Connect service](../1.1_introduction_to_ovhcloud_connect/guide.en-gb.md). - Both the LDP account and the OVHcloud Connect account must belong to the same OVHcloud account. + + +--- + +### OVHcloud Control Panel Access + +**OVHcloud Connect:** + +- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} + +**Logs Data Platform:** + +- **Direct link:** [Logs Data Platform](/links/control-panel/logs-data-platform) +- **Navigation path:** `Identity, Security & Operations`{.action} > `Logs Data Platform`{.action} > Select the platform concerned + +--- + + + ## Concepts & limits **What are the logs of an OVHcloud Connect?** @@ -31,10 +52,10 @@ If you would like to find out more about Logs Data Platform before reading this There are four different kinds of logs which can be forwarded: -- **service** : Events related to the service's lifecycle (suspended, delivered, etc). -- **service_configuration** : Events related to the service configuration, including adding or deleting DC/POP configurations. -- **bgp** : Status of the BGP session. -- **interface** : Events related to the optic fiber interface, including incoming and outgoing light. +- **service**: Events related to the service's lifecycle (suspended, delivered, etc). +- **service_configuration**: Events related to the service configuration, including adding or deleting DC/POP configurations. +- **bgp**: Status of the BGP session. +- **interface**: Events related to the optic fibre interface, including incoming and outgoing light. ### Log contents @@ -46,12 +67,10 @@ There are four different kinds of logs which can be forwarded: | service_uuid | The UUID of the OVHcloud Connect service concerned by the event | String | | timestamp | The timestamp at which the event was logged | datetime (with millisecond resolution) e.g. 25/Mar/2024:14:07:19.536 | -## Instructions +## Enabling OVHcloud Connect log forwarding using APIs Note that the forwarding activation is free of charge, but you will be charged for the usage of the Logs Data Platform service as per the standard price plan. For LDP pricing, refer to this [page](/links/manage-operate/ldp). -### Enabling OVHcloud Connect Log Forwarding using APIs - You will have to define the targeted *Stream* of one of your LDP accounts to which you want your logs forwarded. The enablement of the forwarding will create a subscription for this stream id. You can retrieve the API specifications in the [OVHcloud API Portal](/links/api): @@ -61,7 +80,7 @@ You can retrieve the API specifications in the [OVHcloud API Portal](/links/api) > @api {v1} /dbaas/logs POST /dbaas/logs/{serviceName}/output/graylog/stream > -#### Step 1 - Retrieve your target Stream (and ID) +### Step 1 - Retrieve your target Stream (and ID) List data streams of your Logs Data Platform account (enter your LDP ID in the form ldp-xx-xxxx into the field "serviceName"): @@ -77,7 +96,7 @@ Get the details of a data stream: > @api {v1} /dbaas/logs GET /dbaas/logs/{serviceName}/output/graylog/stream/{streamId} > -#### Step 2 - Create your subscription +### Step 2 - Create your subscription Use the following API call to create a subscription: @@ -111,7 +130,6 @@ The POST request has a payload that requires: > > > - ```shell POST /ovhCloudConnect/{serviceName}/log/subscription { @@ -167,24 +185,24 @@ GET /ovhCloudConnect/{serviceName}/log/subscription/{subscriptionId} } ``` -### How to use OVHcloud Connect logs? +## How to use OVHcloud Connect logs Now that your logs are ingested and stored in your Logs Data Platform data stream, you can query your logs and build dashboards to have a graphical representation of your logs using the web-based UI of Graylog. - In the OVHcloud Control Panel, retrieve the LDP username (ex: logs-xxxx) and its password in your Logs Data Platform account home page. You can refer to the [Quick start guide for Logs Data Platform](/pages/manage_and_operate/observability/logs_data_platform/getting_started_quick_start). - Open the Graylog web-ui. You can retrieve the link in your account home page or using your Access point depending on your account region (for example: Gravelines region is https://gra1.logs.ovh.com/). - Log into Graylog using your Logs Data Platform Username and Password. -- Search through your logs across the data stream of your Logs Data Platform account. You can refer to [Graylog writing search queries](https://go2docs.graylog.org/current/making_sense_of_your_log_data/writing_search_queries.html)documentation for details on search syntax. +- Search through your logs across the data stream of your Logs Data Platform account. You can refer to [Graylog writing search queries](https://go2docs.graylog.org/current/making_sense_of_your_log_data/writing_search_queries.html) documentation for details on search syntax. -Refer to the following documentation: [Logs Data Platform - Visualizing, querying and exploiting your logs](/products/observability-logs-data-platform-visualizing-querying-exploiting) for more details about how to use your logs with Logs Data Platform, including how to: +Refer to the following documentation: [Logs Data Platform - Visualising, querying and exploiting your logs](/products/observability-logs-data-platform-visualizing-querying-exploiting) for more details about how to use your logs with Logs Data Platform, including how to: -- setup alerts +- set up alerts - view the logs in real time through a WebSocket -- build visualization with OpenSearch Dashboards +- build visualisations with OpenSearch Dashboards - integrate with OpenSearch API - connect with Grafana -  -### How to manage your subscriptions? + +## How to manage your subscriptions At any time, you can retrieve the subscriptions attached to your Logs Data Platform data stream and choose to disable the forwarding by cancelling your subscription on your stream, so that your Logs Data Platform stream no longer receives your audit logs. @@ -197,8 +215,14 @@ To delete your subscription you can use the following API call: > @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/log/subscription/{subscriptionId} > +## What's next? + +- [Monitor your OVHcloud Connect](../3.9_monitor/guide.en-gb.md) +- [Troubleshooting OVHcloud Connect](../1.9_troubleshooting/guide.en-gb.md) +- [Declare and follow up on an incident](../3.10_incident_followup/guide.en-gb.md) + ## Go further -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/3.12_log_forwarding/guide.fr-fr.md b/pages/network/ovhcloud_connect/3.12_log_forwarding/guide.fr-fr.md new file mode 100644 index 00000000000..b9ef0203176 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.12_log_forwarding/guide.fr-fr.md @@ -0,0 +1,228 @@ +--- +title: 'Mettre en place la transmission des logs pour OVHcloud Connect' +excerpt: 'Transmettez vos logs d''événements OVHcloud Connect vers Logs Data Platform pour les stocker, les interroger et les visualiser' +updated: 2026-04-22 +--- + +## Objectif + +Ce guide a pour but de vous montrer comment activer la transmission des logs de votre OVHcloud Connect vers Logs Data Platform (LDP), une plateforme qui vous permet de stocker, archiver, interroger et visualiser vos logs. + +Si vous souhaitez en savoir plus sur Logs Data Platform avant de lire ce guide, consultez le [guide d'introduction à Logs Data Platform](/pages/manage_and_operate/observability/logs_data_platform/getting_started_introduction_to_LDP). + +## Glossaire + +- **Logs Data Platform :** une plateforme de gestion de logs entièrement managée et sécurisée par OVHcloud. Pour plus d'informations, consultez la page produit [Logs Data Platform](/links/manage-operate/ldp). +- **Data Stream :** une partition logique de logs que vous créez dans un compte LDP et que vous utilisez lors de l'ingestion, de la consultation ou de l'interrogation de vos logs. Plusieurs sources peuvent être stockées dans un même data stream, et c'est l'unité qui permet de définir un pipeline de logs (politique de rétention, archivage, diffusion en direct, etc.), des droits d'accès et des politiques d'alerte. +- **Transmission de logs :** une fonctionnalité intégrée à un produit OVHcloud pour ingérer les logs de ses services dans un *Data Stream* d'un compte LDP appartenant au même compte OVHcloud. Cette fonctionnalité doit être activée par le client et par service. +- **Abonnement de transmission de logs :** lorsque vous activez la transmission de logs d'un service OVHcloud donné vers un *Data Stream* LDP donné, un *Abonnement* est créé et rattaché au *Data Stream* pour permettre une gestion ultérieure par le client. + +## Prérequis + +- Un compte Logs Data Platform (LDP) avec au moins un *Stream* actif configuré. Ce guide vous accompagne dans toutes les étapes nécessaires : [Démarrage rapide pour Logs Data Platform](/pages/manage_and_operate/observability/logs_data_platform/getting_started_quick_start). + - Si vous n'êtes pas familier avec toutes les possibilités de configuration d'un *Stream* LDP, créez-en un nouveau avec les options par défaut (indexation et websocket activés, stockage long terme désactivé) pour les besoins de ce guide. +- Un [service OVHcloud Connect](../1.1_introduction_to_ovhcloud_connect/guide.fr-fr.md) opérationnel. +- Le compte LDP et le compte OVHcloud Connect doivent appartenir au même compte OVHcloud. + + + +--- + +### Accès à l'espace client OVHcloud + +**OVHcloud Connect :** + +- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} + +**Logs Data Platform :** + +- **Lien direct :** [Logs Data Platform](/links/control-panel/logs-data-platform) +- **Pour accéder à vos services :** `Identité, Sécurité & Opérations`{.action} > `Logs Data Platform`{.action} > Sélectionnez la plateforme concernée + +--- + + + +## Concepts et limites + +**Quels sont les logs d'un OVHcloud Connect ?** + +### Types de logs + +Quatre types de logs différents peuvent être transmis : + +- **service** : événements liés au cycle de vie du service (suspendu, livré, etc.). +- **service_configuration** : événements liés à la configuration du service, dont l'ajout ou la suppression de configurations DC/POP. +- **bgp** : statut de la session BGP. +- **interface** : événements liés à l'interface fibre optique, dont la lumière entrante et sortante. + +### Contenu des logs + +| Nom du champ | Description | Type | +|------------|-------------|---------| +| kind | Le type de log transmis | String | +| message | Une description explicite de l'événement journalisé | String | +| neighbor | L'adresse distante dans le sous-réseau établi entre le service OVHcloud Connect et le PoP | IP | +| service_uuid | L'UUID du service OVHcloud Connect concerné par l'événement | String | +| timestamp | L'horodatage auquel l'événement a été journalisé | datetime (avec une résolution à la milliseconde) ex. 25/Mar/2024:14:07:19.536 | + +## Activer la transmission de logs OVHcloud Connect via les API + +Notez que l'activation de la transmission est gratuite, mais l'utilisation du service Logs Data Platform vous sera facturée selon la grille tarifaire standard. Pour la tarification de LDP, consultez cette [page](/links/manage-operate/ldp). + +Vous devez définir le *Stream* cible de l'un de vos comptes LDP vers lequel vous souhaitez transmettre vos logs. L'activation de la transmission crée un abonnement pour cet identifiant de stream. + +Vous pouvez retrouver les spécifications de l'API dans le [portail API OVHcloud](/links/api) : + +> [!api] +> +> @api {v1} /dbaas/logs POST /dbaas/logs/{serviceName}/output/graylog/stream +> + +### Étape 1 - Récupérer votre Stream cible (et son ID) + +Listez les data streams de votre compte Logs Data Platform (saisissez votre identifiant LDP au format ldp-xx-xxxx dans le champ « serviceName ») : + +> [!api] +> +> @api {v1} /dbaas/logs GET /dbaas/logs/{serviceName}/output/graylog/stream +> + +Récupérez les détails d'un data stream : + +> [!api] +> +> @api {v1} /dbaas/logs GET /dbaas/logs/{serviceName}/output/graylog/stream/{streamId} +> + +### Étape 2 - Créer votre abonnement + +Utilisez l'appel API suivant pour créer un abonnement : + +> [!api] +> +> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/log/subscription +> + +> [!primary] +> Vous devrez remplacer : +> +> - **serviceName** : il s'agit du nom interne de votre service OVHcloud Connect, vous le trouverez dans la page de gestion d'OVHcloud Connect dans l'espace client OVHcloud ou en utilisant l'appel API suivant : +> +> > [!api] +> > +> > @api {v1} /ovhCloudConnect GET /ovhCloudConnect +> > +> + +La requête POST attend un payload qui requiert : + +- `kind` : le type de log que vous souhaitez transmettre, parmi « service », « service_configuration », « bgp » et « interface ». +- `streamId` : le data stream cible de votre compte LDP vers lequel vous souhaitez transmettre vos logs OVHcloud Connect. + +> [!primary] +> Vous pouvez retrouver les types disponibles à l'aide de l'appel API suivant : +> +> > [!api] +> > +> > @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/log/kind +> > +> + +```shell +POST /ovhCloudConnect/{serviceName}/log/subscription +{ + "kind": "string", // "service", "service_configuration", "bgp" or "interface" + "streamId": "198ef9d5-c320-4000-8bee-236623da5b80" // The streamID of the targeted Stream. +} +``` + +Vous obtiendrez en réponse un `operationId` : + +```shell +{ + "operationId": "f550aa1c-89ab-4b1a-81ae-4fba4959966f", + "serviceName": "occ-xxxxx" +} +``` + +Vous pouvez utiliser l'`operationId` pour récupérer le `subscriptionId` à des fins de gestion ultérieure à l'aide de l'appel API suivant : + +> [!api] +> +> @api {v1} /dbaas/logs GET /dbaas/logs/{serviceName}/operation/{operationId} +> + +Alternativement, une fois l'opération terminée, les abonnements peuvent être récupérés à l'aide de l'appel API suivant : + +> [!api] +> +> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/log/subscription +> + +Une fois que vous disposez du `subscriptionId`, vous pouvez en obtenir les détails à l'aide de l'appel API suivant : + +> [!api] +> +> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/log/subscription/{subscriptionId} +> + +```shell +GET /ovhCloudConnect/{serviceName}/log/subscription/{subscriptionId} + +{ +"createdAt": "2025-08-28T07:42:50.645Z", +"kind": "string", +"resource": { + "name": "string", + "type": "string" +}, +"serviceName": "string", +"streamId": "string", +"subscriptionId": "198efa11-f150-4000-8e8d-871b1e482b80", +"updatedAt": "2025-08-28T07:42:50.645Z" +} +``` + +## Comment utiliser les logs OVHcloud Connect + +Maintenant que vos logs sont ingérés et stockés dans le data stream de votre Logs Data Platform, vous pouvez interroger vos logs et créer des tableaux de bord afin d'obtenir une représentation graphique de vos logs grâce à l'interface web de Graylog. + +- Dans l'espace client OVHcloud, récupérez le nom d'utilisateur LDP (par exemple : logs-xxxx) et son mot de passe sur la page d'accueil de votre compte Logs Data Platform. Vous pouvez vous référer au [guide de démarrage rapide pour Logs Data Platform](/pages/manage_and_operate/observability/logs_data_platform/getting_started_quick_start). +- Ouvrez l'interface web Graylog. Vous pouvez retrouver le lien sur la page d'accueil de votre compte ou via votre point d'accès en fonction de la région de votre compte (par exemple : la région Gravelines est https://gra1.logs.ovh.com/). +- Connectez-vous à Graylog avec votre nom d'utilisateur et votre mot de passe Logs Data Platform. +- Effectuez des recherches dans vos logs sur le data stream de votre compte Logs Data Platform. Vous pouvez vous référer à la documentation [Graylog writing search queries](https://go2docs.graylog.org/current/making_sense_of_your_log_data/writing_search_queries.html) pour des détails sur la syntaxe de recherche. + +Référez-vous à la documentation suivante : [Logs Data Platform - Visualiser, interroger et exploiter vos logs](/products/observability-logs-data-platform-visualizing-querying-exploiting) pour plus de détails sur l'utilisation de vos logs avec Logs Data Platform, notamment comment : + +- configurer des alertes +- visualiser les logs en temps réel via un WebSocket +- créer des visualisations avec OpenSearch Dashboards +- s'intégrer avec l'API OpenSearch +- se connecter à Grafana + +## Comment gérer vos abonnements + +À tout moment, vous pouvez récupérer les abonnements rattachés au data stream de votre Logs Data Platform et choisir de désactiver la transmission en annulant votre abonnement sur votre stream, afin que votre stream Logs Data Platform ne reçoive plus vos logs d'audit. + +Notez que cela ne supprime pas les logs stockés avant l'annulation de l'abonnement, car les données stockées dans un stream de logs sont immuables sauf si vous supprimez l'intégralité du stream. + +Pour supprimer votre abonnement, vous pouvez utiliser l'appel API suivant : + +> [!api] +> +> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/log/subscription/{subscriptionId} +> + +## Et ensuite ? + +- [Superviser votre OVHcloud Connect](../3.9_monitor/guide.fr-fr.md) +- [Résolution des problèmes OVHcloud Connect](../1.9_troubleshooting/guide.fr-fr.md) +- [Déclarer et suivre un incident](../3.10_incident_followup/guide.fr-fr.md) + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-logs-2-customers/meta.yaml b/pages/network/ovhcloud_connect/3.12_log_forwarding/meta.yaml similarity index 100% rename from pages/network/ovhcloud_connect/occ-logs-2-customers/meta.yaml rename to pages/network/ovhcloud_connect/3.12_log_forwarding/meta.yaml diff --git a/pages/network/ovhcloud_connect/3.1_order_direct/guide.en-gb.md b/pages/network/ovhcloud_connect/3.1_order_direct/guide.en-gb.md new file mode 100644 index 00000000000..156f15387c6 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.1_order_direct/guide.en-gb.md @@ -0,0 +1,129 @@ +--- +title: 'Order OVHcloud Connect Direct' +excerpt: 'Learn how to order a direct physical connection to OVHcloud through the Control Panel or the API' +updated: 2026-02-18 +--- + +## Objective + +This guide explains how to order a **direct physical connection** to OVHcloud through the OVHcloud Control Panel or the API. + +## What you will need + +Before starting the order, prepare the following: + +| Information | Description | +|---|---| +| **PoP location** | The data centre where you want to connect (see [PoP Locations](../1.4_pop_locations_regions/guide.en-gb.md)) | +| **Bandwidth** | The speed of the connection (e.g. 1 Gbps or 10 Gbps) | +| **Your ASN** | Your Autonomous System Number (public or private) for BGP peering | +| **IP plan** | The prefixes you intend to advertise and the peering subnet | +| **Contact details** | Technical and billing contacts for the order | +| **Cross-connect instructions** | Cage/cabinet references if you have your own space in the data centre | + + +--- + +### OVHcloud Control Panel Access + +- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Order via the OVHcloud Control Panel + +1. Click **Order a new connection**. +2. Select **Direct Connection**. +3. Choose your **PoP location** from the list of available sites. +4. Select the desired **bandwidth** (1 Gbps or 10 Gbps). +5. Fill in the **technical details**: + - Your ASN + - Preferred VLAN ID (if applicable) + - Contact information for LOA delivery + - Any special instructions for the data centre cross-connect +6. Review the **pricing and contract terms** (minimum commitment period, monthly fee). +7. **Confirm** the order. + +You will receive an email confirmation with your order reference and estimated delivery timeline. + +## Order via the API + +You can also order programmatically using the [OVHcloud API](https://eu.api.ovh.com/console/?section=%2FovhCloudConnect&branch=v1). + +```python +import ovh + +client = ovh.Client(endpoint='ovh-eu') + +# Example: list your existing OVHcloud Connect services +# Check the API console for the exact endpoint and parameters +result = client.get('/ovhCloudConnect') +print(result) +``` + +> Refer to the [Automation guide](../1.6_automation/guide.en-gb.md) for API setup instructions. + +## What happens after ordering + +```svg + + + + + Order confirmed + Email received + + + LOA sent + Within minutes + + + Cross-connect + Installed by DC operator + + + Port active + Ready to configure + + + + + + + + + + + +``` + +1. **Order confirmed** — You receive an email with your order reference. +2. **LOA delivered** — OVHcloud issues the Letter of Authorization **within minutes** of the order. The LOA contains the data centre details needed to install the cross-connect. +3. **Cross-connect installed** — Give the LOA to your data centre operator. They install the fibre patch cable. Timing depends on the facility (a few days to 2 weeks). +4. **Port becomes active** — Once the cross-connect is in place and OVHcloud detects light, the port becomes active and the service is delivered. You can now configure BGP and associate with your vRack. + +> [!warning] +> +> After the order, you have **60 days** to finalize the interconnection (order the cross-connect and connect your equipment). Beyond 60 days — even without detected light — the service is considered operational and **billing starts**. +> + +## Pricing and billing + +- OVHcloud Connect Direct is billed **monthly**. +- Pricing depends on the PoP location and bandwidth tier. +- A **minimum commitment period** may apply (check during ordering). +- Cross-connect fees from the data centre operator are separate and billed by the operator. + +## What's next? + +- [Receive and use your LOA](../3.11_cross_connect_loa/guide.en-gb.md) +- [Configure OCC L3 with BGP](../3.7_occ_l3_bgp/guide.en-gb.md) +- [Associate with your vRack](../3.5_associate_vrack/guide.en-gb.md) + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/3.1_order_direct/guide.fr-fr.md b/pages/network/ovhcloud_connect/3.1_order_direct/guide.fr-fr.md new file mode 100644 index 00000000000..89b5068b7f7 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.1_order_direct/guide.fr-fr.md @@ -0,0 +1,129 @@ +--- +title: 'Commander OVHcloud Connect Direct' +excerpt: 'Découvrez comment commander une connexion physique directe vers OVHcloud depuis l''espace client ou via l''API' +updated: 2026-02-18 +--- + +## Objectif + +Ce guide explique comment commander une **connexion physique directe** vers OVHcloud depuis l'espace client OVHcloud ou via l'API. + +## Prérequis + +Avant de passer commande, préparez les informations suivantes : + +| Information | Description | +|---|---| +| **Localisation du PoP** | Le datacenter dans lequel vous souhaitez vous connecter (consultez [Localisations des PoP](../1.4_pop_locations_regions/guide.fr-fr.md)) | +| **Bande passante** | Le débit de la connexion (par exemple 1 Gbps ou 10 Gbps) | +| **Votre ASN** | Votre numéro de système autonome (public ou privé) pour le peering BGP | +| **Plan d'adressage IP** | Les préfixes que vous comptez annoncer ainsi que le sous-réseau de peering | +| **Coordonnées** | Contacts techniques et de facturation pour la commande | +| **Instructions de cross-connect** | Références de cage/baie si vous disposez de votre propre espace dans le datacenter | + + +--- + +### Accès à l'espace client OVHcloud + +- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Commander depuis l'espace client OVHcloud + +1. Cliquez sur **Commander une nouvelle connexion**. +2. Sélectionnez **Connexion directe**. +3. Choisissez la **localisation du PoP** dans la liste des sites disponibles. +4. Sélectionnez la **bande passante** souhaitée (1 Gbps ou 10 Gbps). +5. Renseignez les **détails techniques** : + - Votre ASN + - VLAN ID préféré (le cas échéant) + - Coordonnées pour la livraison de la LOA + - Toute instruction particulière pour le cross-connect en datacenter +6. Vérifiez les **conditions tarifaires et contractuelles** (durée d'engagement minimale, redevance mensuelle). +7. **Confirmez** la commande. + +Vous recevrez un e-mail de confirmation contenant la référence de votre commande ainsi que le délai de livraison estimé. + +## Commander via l'API + +Vous pouvez également passer commande de manière programmatique en utilisant l'[API OVHcloud](https://eu.api.ovh.com/console/?section=%2FovhCloudConnect&branch=v1). + +```python +import ovh + +client = ovh.Client(endpoint='ovh-eu') + +# Exemple : lister vos services OVHcloud Connect existants +# Consultez la console API pour connaître l'endpoint et les paramètres exacts +result = client.get('/ovhCloudConnect') +print(result) +``` + +> Reportez-vous au [guide d'automatisation](../1.6_automation/guide.fr-fr.md) pour les instructions de configuration de l'API. + +## Et ensuite ? + +```svg + + + + + Commande confirmée + E-mail reçu + + + LOA envoyée + En quelques minutes + + + Cross-connect + Installé par l'opérateur DC + + + Port actif + Prêt à configurer + + + + + + + + + + + +``` + +1. **Commande confirmée** — Vous recevez un e-mail contenant la référence de votre commande. +2. **LOA livrée** — OVHcloud émet la Lettre d'autorisation (LOA) **en quelques minutes** après la commande. La LOA contient les informations relatives au datacenter nécessaires à l'installation du cross-connect. +3. **Cross-connect installé** — Transmettez la LOA à l'opérateur de votre datacenter. Il procède à l'installation du jarretière en fibre. Le délai dépend du site (de quelques jours à 2 semaines). +4. **Activation du port** — Une fois le cross-connect en place et la lumière détectée par OVHcloud, le port devient actif et le service est livré. Vous pouvez alors configurer BGP et associer le service à votre vRack. + +> [!warning] +> +> Après la commande, vous disposez de **60 jours** pour finaliser l'interconnexion (commander le cross-connect et raccorder votre équipement). Au-delà de 60 jours, même sans détection de lumière, le service est considéré comme opérationnel et **la facturation démarre**. +> + +## Tarification et facturation + +- OVHcloud Connect Direct est facturé **mensuellement**. +- Le tarif dépend de la localisation du PoP et du palier de bande passante. +- Une **durée d'engagement minimale** peut s'appliquer (à vérifier lors de la commande). +- Les frais de cross-connect facturés par l'opérateur du datacenter sont distincts et facturés par cet opérateur. + +## Et ensuite ? + +- [Recevoir et utiliser votre LOA](../3.11_cross_connect_loa/guide.fr-fr.md) +- [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp/guide.fr-fr.md) +- [Associer le service à votre vRack](../3.5_associate_vrack/guide.fr-fr.md) + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/3.1_order_direct/meta.yaml b/pages/network/ovhcloud_connect/3.1_order_direct/meta.yaml new file mode 100644 index 00000000000..92b290886db --- /dev/null +++ b/pages/network/ovhcloud_connect/3.1_order_direct/meta.yaml @@ -0,0 +1,2 @@ +id: 17c1c8fa-d094-404d-87a0-1a810ca84a3e +full_slug: network-ovhcloud-connect-order-direct diff --git a/pages/network/ovhcloud_connect/3.2_order_provider/guide.en-gb.md b/pages/network/ovhcloud_connect/3.2_order_provider/guide.en-gb.md new file mode 100644 index 00000000000..1d788061327 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.2_order_provider/guide.en-gb.md @@ -0,0 +1,121 @@ +--- +title: 'Order OVHcloud Connect Provider' +excerpt: 'Learn how to order an OVHcloud Connect service through a third-party network provider' +updated: 2026-02-18 +--- + +## Objective + +This guide explains how to order an OVHcloud Connect service through a **third-party network provider** (e.g. Megaport, Equinix Fabric, Console Connect). + +## What you will need + +| Information | Description | +|---|---| +| **Provider** | The third-party provider you want to use (see [Providers](../1.3_providers/guide.en-gb.md)) | +| **PoP location** | The OVHcloud PoP where the provider will connect | +| **Bandwidth** | The desired speed (e.g. 100 Mbps, 1 Gbps, 10 Gbps — options vary by provider) | +| **Your ASN & IP plan** | OVHcloud Connect Provider is always a Layer 3 service; you need an ASN and peering IPs for BGP | + +## Order via the OVHcloud Control Panel + +1. **Log in** to the [OVHcloud Control Panel](https://www.ovh.com/manager/). +2. Navigate to **Network** → **OVHcloud Connect**. +3. Click **Order a new connection**. +4. Select **Provider Connection**. +5. Choose your **provider** from the list. +6. Select the **PoP location** and **bandwidth**. +7. OVHcloud generates a **pairing key** (service key). +8. Review pricing and **confirm** the order. + +> **Important:** Copy the pairing key — you will need it in the next step. + +## Share the pairing key with your provider + +The pairing key identifies your OVHcloud Connect order and allows the provider to provision the connection. + +### On Megaport + +1. Log in to the [Megaport portal](https://portal.megaport.com/). +2. Create a new **VXC (Virtual Cross Connect)**. +3. Select **OVHcloud** as the destination. +4. Enter the **pairing key** provided by OVHcloud. +5. Choose bandwidth and confirm. + +> Megaport documentation: [docs.megaport.com](https://docs.megaport.com/) + +### On Equinix Fabric + +1. Log in to [Equinix Fabric](https://fabric.equinix.com/). +2. Create a new **connection**. +3. Select **OVHcloud** from the service provider catalogue. +4. Enter the **service key** (pairing key). +5. Choose speed and confirm. + +> Equinix Fabric documentation: [docs.equinix.com/fabric](https://docs.equinix.com/fabric/) + +### On Console Connect + +1. Log in to [Console Connect](https://app.consoleconnect.com/). +2. Search for **OVHcloud** in the marketplace. +3. Create a new connection and enter the **pairing key**. +4. Choose bandwidth and confirm. + +> Console Connect documentation: [consoleconnect.com/help](https://www.consoleconnect.com/help/) + +## What happens after ordering + +```svg + + + + + Pairing key + Generated by OVHcloud + + + Provider setup + Minutes to hours + + + Link active + OVHcloud confirms + + + Configure & test + BGP + vRack + + + + + + + + + + + +``` + +1. **Pairing key generated** — OVHcloud provides the key after you place the order. +2. **Provider provisions** — The provider uses the key to set up the virtual or physical link. On-demand providers (Megaport, Equinix) typically complete this in minutes. +3. **Link becomes active** — OVHcloud activates the connection and the status changes to "Active" in the Control Panel. +4. **Configure and test** — Verify BGP peering, associate with your vRack, and test connectivity. + +## Pricing and billing + +- **OVHcloud** bills you for the OVHcloud Connect Provider service (monthly). +- **Your provider** bills you separately for their circuit/VXC (pricing varies by provider, bandwidth, and contract). +- Ensure you understand both billing structures before ordering. + +## What's next? + +- [Configure OCC L3 with BGP](../3.7_occ_l3_bgp/guide.en-gb.md) +- [Associate with your vRack](../3.5_associate_vrack/guide.en-gb.md) +- [Monitor your connection](../3.9_monitor/guide.en-gb.md) + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/3.2_order_provider/guide.fr-fr.md b/pages/network/ovhcloud_connect/3.2_order_provider/guide.fr-fr.md new file mode 100644 index 00000000000..33913f304b8 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.2_order_provider/guide.fr-fr.md @@ -0,0 +1,121 @@ +--- +title: 'Commander OVHcloud Connect Provider' +excerpt: 'Découvrez comment commander un service OVHcloud Connect via un opérateur réseau tiers' +updated: 2026-02-18 +--- + +## Objectif + +Ce guide explique comment commander un service OVHcloud Connect via un **opérateur réseau tiers** (par exemple Megaport, Equinix Fabric, Console Connect). + +## Prérequis + +| Information | Description | +|---|---| +| **Opérateur** | L'opérateur tiers que vous souhaitez utiliser (consultez [Opérateurs](../1.3_providers/guide.fr-fr.md)) | +| **Localisation du PoP** | Le PoP OVHcloud auquel l'opérateur va se raccorder | +| **Bande passante** | Le débit souhaité (par exemple 100 Mbps, 1 Gbps, 10 Gbps — les options varient selon l'opérateur) | +| **Votre ASN et plan IP** | OVHcloud Connect Provider est toujours un service Layer 3 ; vous avez besoin d'un ASN et d'IP de peering pour BGP | + +## Commander depuis l'espace client OVHcloud + +1. **Connectez-vous** à l'[espace client OVHcloud](https://www.ovh.com/manager/). +2. Rendez-vous dans **Network** → **OVHcloud Connect**. +3. Cliquez sur **Commander une nouvelle connexion**. +4. Sélectionnez **Connexion via un opérateur**. +5. Choisissez votre **opérateur** dans la liste. +6. Sélectionnez la **localisation du PoP** et la **bande passante**. +7. OVHcloud génère une **clé de pairing** (clé de service). +8. Vérifiez le tarif et **confirmez** la commande. + +> **Important :** copiez la clé de pairing — vous en aurez besoin à l'étape suivante. + +## Partager la clé de pairing avec votre opérateur + +La clé de pairing identifie votre commande OVHcloud Connect et permet à l'opérateur de provisionner la connexion. + +### Sur Megaport + +1. Connectez-vous au [portail Megaport](https://portal.megaport.com/). +2. Créez un nouveau **VXC (Virtual Cross Connect)**. +3. Sélectionnez **OVHcloud** comme destination. +4. Saisissez la **clé de pairing** fournie par OVHcloud. +5. Choisissez la bande passante puis confirmez. + +> Documentation Megaport : [docs.megaport.com](https://docs.megaport.com/) + +### Sur Equinix Fabric + +1. Connectez-vous à [Equinix Fabric](https://fabric.equinix.com/). +2. Créez une nouvelle **connexion**. +3. Sélectionnez **OVHcloud** dans le catalogue des fournisseurs de services. +4. Saisissez la **clé de service** (clé de pairing). +5. Choisissez le débit puis confirmez. + +> Documentation Equinix Fabric : [docs.equinix.com/fabric](https://docs.equinix.com/fabric/) + +### Sur Console Connect + +1. Connectez-vous à [Console Connect](https://app.consoleconnect.com/). +2. Recherchez **OVHcloud** dans la marketplace. +3. Créez une nouvelle connexion et saisissez la **clé de pairing**. +4. Choisissez la bande passante puis confirmez. + +> Documentation Console Connect : [consoleconnect.com/help](https://www.consoleconnect.com/help/) + +## Et ensuite ? + +```svg + + + + + Clé de pairing + Générée par OVHcloud + + + Mise en place opérateur + Minutes à heures + + + Lien actif + OVHcloud confirme + + + Configurer et tester + BGP + vRack + + + + + + + + + + + +``` + +1. **Clé de pairing générée** — OVHcloud fournit la clé après la passation de votre commande. +2. **Provisionnement par l'opérateur** — L'opérateur utilise la clé pour mettre en place le lien virtuel ou physique. Les opérateurs à la demande (Megaport, Equinix) le réalisent généralement en quelques minutes. +3. **Activation du lien** — OVHcloud active la connexion et le statut passe à « Actif » dans l'espace client. +4. **Configurer et tester** — Vérifiez le peering BGP, associez le service à votre vRack et testez la connectivité. + +## Tarification et facturation + +- **OVHcloud** vous facture le service OVHcloud Connect Provider (mensuellement). +- **Votre opérateur** vous facture séparément son circuit/VXC (les tarifs varient selon l'opérateur, la bande passante et le contrat). +- Assurez-vous de bien comprendre les deux structures de facturation avant de passer commande. + +## Et ensuite ? + +- [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp/guide.fr-fr.md) +- [Associer le service à votre vRack](../3.5_associate_vrack/guide.fr-fr.md) +- [Superviser votre connexion](../3.9_monitor/guide.fr-fr.md) + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/3.2_order_provider/meta.yaml b/pages/network/ovhcloud_connect/3.2_order_provider/meta.yaml new file mode 100644 index 00000000000..20d092d9568 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.2_order_provider/meta.yaml @@ -0,0 +1,2 @@ +id: fefcaf17-c918-4cf9-98ae-a0eb997c7eca +full_slug: network-ovhcloud-connect-order-provider diff --git a/pages/network/ovhcloud_connect/3.3_cancel_direct/guide.en-gb.md b/pages/network/ovhcloud_connect/3.3_cancel_direct/guide.en-gb.md new file mode 100644 index 00000000000..0e53f2e0e35 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.3_cancel_direct/guide.en-gb.md @@ -0,0 +1,90 @@ +--- +title: 'Cancel OVHcloud Connect Direct' +excerpt: 'Learn how to cancel an OVHcloud Connect Direct service and decommission the physical connection' +updated: 2026-02-18 +--- + +## Objective + +This guide explains how to cancel an OVHcloud Connect Direct service and decommission the physical connection. + +## Before you cancel + +Consider the following before proceeding: + +- **Traffic disruption** — Cancelling the service will permanently interrupt all traffic flowing through this connection. Ensure you have migrated workloads or set up alternative connectivity. +- **Minimum contract term** — Check whether your contract has a minimum commitment period. Early cancellation may incur fees. +- **Cross-connect removal** — The physical cross-connect in the data centre needs to be decommissioned separately. +- **Billing** — Understand the billing cycle. Cancellation typically takes effect at the end of the current billing period. + + +--- + +### OVHcloud Control Panel Access + +- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Steps to cancel + +### 1. Remove dependent configurations + +Before cancelling the OVHcloud Connect service: + +1. **Remove the vRack association** — Dissociate the OVHcloud Connect service from your vRack in the OVHcloud Control Panel. +2. **Remove PoP/BGP configuration** — Delete the PoP configuration and BGP sessions associated with the service. +3. **Update your routing** — Ensure your network no longer relies on routes learned through this connection. + +### 2. Request cancellation in the OVHcloud Control Panel + +1. Select the **Direct connection** you want to cancel. +2. Click **Cancel** (or **Terminate service**). +3. Confirm the cancellation. You may be asked to provide a reason. +4. You will receive a **confirmation email** with the effective cancellation date. + +### 3. Decommission the cross-connect + +After OVHcloud confirms the cancellation: + +1. Contact your **data centre operator** and request the removal of the cross-connect. +2. Provide any required documentation (some facilities require an LOA for removal — see [Cross Connect LOA](../3.11_cross_connect_loa/guide.en-gb.md)). +3. Confirm with the data centre that the physical cable has been removed. + +> **Tip:** Keep a copy of all cancellation confirmations and LOAs for your records. + +### 4. Verify clean-up + +- Confirm the service no longer appears as active in the OVHcloud Control Panel. +- Verify that billing has stopped (check your next invoice). +- Ensure your network routing has been updated to remove references to the cancelled connection. + +## Cancellation via the API + +You can also manage cancellation programmatically: + +```python +import ovh + +client = ovh.Client(endpoint='ovh-eu') + +service_name = "your-occ-service-uuid" + +# Terminate the service +client.post(f"/ovhCloudConnect/{service_name}/terminate") +``` + +> Refer to the [OVHcloud API Console](https://eu.api.ovh.com/console/?section=%2FovhCloudConnect&branch=v1) for available cancellation endpoints. + +## What's next? + +- [Cancel OVHcloud Connect Provider](../3.4_cancel_provider/guide.en-gb.md) (if you also have a provider connection) +- [Order a new connection](../3.1_order_direct/guide.en-gb.md) if you need to replace the service + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/3.3_cancel_direct/guide.fr-fr.md b/pages/network/ovhcloud_connect/3.3_cancel_direct/guide.fr-fr.md new file mode 100644 index 00000000000..5b3a414e682 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.3_cancel_direct/guide.fr-fr.md @@ -0,0 +1,90 @@ +--- +title: 'Résilier OVHcloud Connect Direct' +excerpt: 'Découvrez comment résilier un service OVHcloud Connect Direct et démanteler la connexion physique' +updated: 2026-02-18 +--- + +## Objectif + +Ce guide explique comment résilier un service OVHcloud Connect Direct et démanteler la connexion physique. + +## Avant de commencer + +Tenez compte des points suivants avant de poursuivre : + +- **Interruption de trafic** — La résiliation du service interrompt définitivement l'ensemble du trafic transitant par cette connexion. Assurez-vous d'avoir migré vos charges de travail ou mis en place une connectivité alternative. +- **Durée d'engagement minimale** — Vérifiez si votre contrat comporte une durée d'engagement minimale. Une résiliation anticipée peut entraîner des frais. +- **Démantèlement du cross-connect** — Le cross-connect physique en datacenter doit être démantelé séparément. +- **Facturation** — Comprenez le cycle de facturation. La résiliation prend généralement effet à la fin de la période de facturation en cours. + + +--- + +### Accès à l'espace client OVHcloud + +- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Étapes de résiliation + +### 1. Supprimer les configurations dépendantes + +Avant de résilier le service OVHcloud Connect : + +1. **Supprimez l'association vRack** — Dissociez le service OVHcloud Connect de votre vRack dans l'espace client OVHcloud. +2. **Supprimez la configuration PoP/BGP** — Supprimez la configuration PoP et les sessions BGP associées au service. +3. **Mettez à jour votre routage** — Assurez-vous que votre réseau ne dépend plus des routes apprises via cette connexion. + +### 2. Demander la résiliation depuis l'espace client OVHcloud + +1. Sélectionnez la **connexion directe** que vous souhaitez résilier. +2. Cliquez sur **Annuler** (ou **Résilier le service**). +3. Confirmez la résiliation. Un motif peut vous être demandé. +4. Vous recevrez un **e-mail de confirmation** indiquant la date effective de résiliation. + +### 3. Démanteler le cross-connect + +Une fois la résiliation confirmée par OVHcloud : + +1. Contactez l'**opérateur de votre datacenter** et demandez la dépose du cross-connect. +2. Fournissez la documentation requise (certains sites exigent une LOA pour la dépose — consultez [LOA Cross-connect](../3.11_cross_connect_loa/guide.fr-fr.md)). +3. Confirmez auprès du datacenter que le câble physique a bien été retiré. + +> **Conseil :** conservez une copie de toutes les confirmations de résiliation et des LOA pour vos archives. + +### 4. Vérifier le nettoyage + +- Confirmez que le service n'apparaît plus comme actif dans l'espace client OVHcloud. +- Vérifiez que la facturation s'est arrêtée (consultez votre prochaine facture). +- Assurez-vous que votre routage réseau a été mis à jour pour supprimer les références à la connexion résiliée. + +## Résiliation via l'API + +Vous pouvez également gérer la résiliation de manière programmatique : + +```python +import ovh + +client = ovh.Client(endpoint='ovh-eu') + +service_name = "your-occ-service-uuid" + +# Résilier le service +client.post(f"/ovhCloudConnect/{service_name}/terminate") +``` + +> Reportez-vous à la [console API OVHcloud](https://eu.api.ovh.com/console/?section=%2FovhCloudConnect&branch=v1) pour connaître les endpoints de résiliation disponibles. + +## Et ensuite ? + +- [Résilier OVHcloud Connect Provider](../3.4_cancel_provider/guide.fr-fr.md) (si vous disposez également d'une connexion via un opérateur) +- [Commander une nouvelle connexion](../3.1_order_direct/guide.fr-fr.md) si vous avez besoin de remplacer le service + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/3.3_cancel_direct/meta.yaml b/pages/network/ovhcloud_connect/3.3_cancel_direct/meta.yaml new file mode 100644 index 00000000000..ce0c3545a87 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.3_cancel_direct/meta.yaml @@ -0,0 +1,2 @@ +id: 241cdec1-5c0a-419a-a0c5-5112dcf8fba8 +full_slug: network-ovhcloud-connect-cancel-direct diff --git a/pages/network/ovhcloud_connect/3.4_cancel_provider/guide.en-gb.md b/pages/network/ovhcloud_connect/3.4_cancel_provider/guide.en-gb.md new file mode 100644 index 00000000000..80b2211550f --- /dev/null +++ b/pages/network/ovhcloud_connect/3.4_cancel_provider/guide.en-gb.md @@ -0,0 +1,77 @@ +--- +title: 'Cancel OVHcloud Connect Provider' +excerpt: 'Learn how to cancel an OVHcloud Connect Provider service and coordinate with your provider' +updated: 2026-02-18 +--- + +## Objective + +This guide explains how to cancel an OVHcloud Connect Provider service. Since a provider connection involves both OVHcloud and a third-party network operator, you need to coordinate the cancellation with both parties. + +## Before you cancel + +- **Traffic disruption** — All traffic over this connection will be permanently interrupted. +- **Provider contract** — Check your provider's terms for minimum commitment, notice periods, and early termination fees. +- **OVHcloud contract** — Check your OVHcloud commitment period and billing cycle. +- **Alternative connectivity** — Ensure workloads are migrated or an alternative path is available. + + +--- + +### OVHcloud Control Panel Access + +- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Steps to cancel + +### 1. Remove dependent configurations on OVHcloud + +1. **Remove the vRack association** — Dissociate the OVHcloud Connect service from your vRack in the Control Panel. +2. **Remove PoP/BGP configuration** — Delete BGP sessions and PoP configuration for this service. +3. **Update routing** — Ensure your network no longer depends on routes from this connection. + +### 2. Cancel on the OVHcloud side + +1. Select the **Provider connection** you want to cancel. +2. Click **Cancel** (or **Terminate service**). +3. Confirm and note the effective cancellation date. + +### 3. Cancel on the provider side + +**This is essential.** If you only cancel on OVHcloud but not with your provider, the provider may continue billing you. + +| Provider | How to cancel | +|---|---| +| **Megaport** | Delete the VXC in the [Megaport Portal](https://portal.megaport.com/). | +| **Equinix Fabric** | Delete the connection in [Equinix Fabric](https://fabric.equinix.com/). | +| **Console Connect** | Cancel the connection in [Console Connect](https://app.consoleconnect.com/). | + +> Contact your provider's support if you have questions about their cancellation process or timelines. + +### 4. Verify clean-up + +- Confirm the OVHcloud Connect service shows as cancelled in the OVHcloud Control Panel. +- Confirm the VXC/connection is deleted in your provider's portal. +- Verify that billing has stopped on both OVHcloud and the provider side. +- Update your network configuration to remove any stale routes or BGP peers. + +## Important reminders + +- **Cancel on both sides** — OVHcloud and the provider are separate services with separate billing. Cancelling one does not automatically cancel the other. +- **Keep records** — Save cancellation confirmation emails from both OVHcloud and the provider. +- **Cross-connect clean-up** — If the provider installed a physical cross-connect on your behalf, coordinate with them to ensure it is removed from the data centre. + +## What's next? + +- [Cancel OVHcloud Connect Direct](../3.3_cancel_direct/guide.en-gb.md) (if you also have a direct connection) +- [Order a new connection](../3.2_order_provider/guide.en-gb.md) if you need a replacement + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/3.4_cancel_provider/guide.fr-fr.md b/pages/network/ovhcloud_connect/3.4_cancel_provider/guide.fr-fr.md new file mode 100644 index 00000000000..ed124670122 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.4_cancel_provider/guide.fr-fr.md @@ -0,0 +1,77 @@ +--- +title: 'Résilier OVHcloud Connect Provider' +excerpt: 'Découvrez comment résilier un service OVHcloud Connect Provider et coordonner la résiliation avec votre opérateur' +updated: 2026-02-18 +--- + +## Objectif + +Ce guide explique comment résilier un service OVHcloud Connect Provider. Une connexion via un opérateur impliquant à la fois OVHcloud et un opérateur réseau tiers, vous devez coordonner la résiliation avec les deux parties. + +## Avant de commencer + +- **Interruption de trafic** — Tout le trafic transitant par cette connexion sera définitivement interrompu. +- **Contrat avec l'opérateur** — Vérifiez les conditions de votre opérateur concernant la durée d'engagement minimale, les délais de préavis et les frais de résiliation anticipée. +- **Contrat OVHcloud** — Vérifiez votre durée d'engagement OVHcloud et votre cycle de facturation. +- **Connectivité alternative** — Assurez-vous que vos charges de travail sont migrées ou qu'un chemin alternatif est disponible. + + +--- + +### Accès à l'espace client OVHcloud + +- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Étapes de résiliation + +### 1. Supprimer les configurations dépendantes côté OVHcloud + +1. **Supprimez l'association vRack** — Dissociez le service OVHcloud Connect de votre vRack dans l'espace client. +2. **Supprimez la configuration PoP/BGP** — Supprimez les sessions BGP et la configuration PoP de ce service. +3. **Mettez à jour le routage** — Assurez-vous que votre réseau ne dépend plus des routes issues de cette connexion. + +### 2. Résilier côté OVHcloud + +1. Sélectionnez la **connexion via un opérateur** que vous souhaitez résilier. +2. Cliquez sur **Annuler** (ou **Résilier le service**). +3. Confirmez et notez la date effective de résiliation. + +### 3. Résilier côté opérateur + +**Cette étape est essentielle.** Si vous résiliez uniquement chez OVHcloud sans le faire chez votre opérateur, ce dernier peut continuer à vous facturer. + +| Opérateur | Comment résilier | +|---|---| +| **Megaport** | Supprimez le VXC dans le [portail Megaport](https://portal.megaport.com/). | +| **Equinix Fabric** | Supprimez la connexion dans [Equinix Fabric](https://fabric.equinix.com/). | +| **Console Connect** | Annulez la connexion dans [Console Connect](https://app.consoleconnect.com/). | + +> Contactez le support de votre opérateur si vous avez des questions sur la procédure ou les délais de résiliation. + +### 4. Vérifier le nettoyage + +- Confirmez que le service OVHcloud Connect apparaît bien comme résilié dans l'espace client OVHcloud. +- Confirmez que le VXC/la connexion est supprimée dans le portail de votre opérateur. +- Vérifiez que la facturation s'est arrêtée à la fois côté OVHcloud et côté opérateur. +- Mettez à jour la configuration de votre réseau pour supprimer toute route obsolète ou pair BGP résiduel. + +## Rappels importants + +- **Résiliez des deux côtés** — OVHcloud et l'opérateur sont des services distincts avec des facturations distinctes. Résilier l'un ne résilie pas automatiquement l'autre. +- **Conservez les preuves** — Sauvegardez les e-mails de confirmation de résiliation envoyés par OVHcloud et par votre opérateur. +- **Démantèlement du cross-connect** — Si l'opérateur a installé un cross-connect physique pour votre compte, coordonnez-vous avec lui pour vous assurer qu'il est bien retiré du datacenter. + +## Et ensuite ? + +- [Résilier OVHcloud Connect Direct](../3.3_cancel_direct/guide.fr-fr.md) (si vous disposez également d'une connexion directe) +- [Commander une nouvelle connexion](../3.2_order_provider/guide.fr-fr.md) si vous souhaitez la remplacer + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/3.4_cancel_provider/meta.yaml b/pages/network/ovhcloud_connect/3.4_cancel_provider/meta.yaml new file mode 100644 index 00000000000..1348e3a9a4c --- /dev/null +++ b/pages/network/ovhcloud_connect/3.4_cancel_provider/meta.yaml @@ -0,0 +1,2 @@ +id: a647b874-4aee-446a-815b-90d05f863336 +full_slug: network-ovhcloud-connect-cancel-provider diff --git a/pages/network/ovhcloud_connect/3.5_associate_vrack/guide.en-gb.md b/pages/network/ovhcloud_connect/3.5_associate_vrack/guide.en-gb.md new file mode 100644 index 00000000000..ba9c0edc8d6 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.5_associate_vrack/guide.en-gb.md @@ -0,0 +1,145 @@ +--- +title: 'Associate an OVHcloud Connect to Your vRack' +excerpt: 'Learn how to associate your OVHcloud Connect service with a vRack for private connectivity' +updated: 2026-02-18 +--- + +## Objective + +The **vRack** is OVHcloud's private networking service. To allow your OVHcloud resources (servers, VMs, etc.) to communicate through your OVHcloud Connect link, you must associate the OVHcloud Connect service with a vRack. + +## What the association does + +```svg + + + + + + OVHcloud Connect + Private link to your network + + + + vRack + Private network fabric + + VLANs & Subnets + + + + OVHcloud Services + Bare Metal Servers + Public Cloud VMs + Hosted Private Cloud + Managed Kubernetes + + + + + + + + + + + +``` + +When you associate OVHcloud Connect with a vRack: + +- Traffic from your external network (on-premises, cloud, WAN) can reach OVHcloud services attached to the same vRack. +- OVHcloud services in the vRack can send traffic back through OVHcloud Connect to your network. +- All communication stays **private** — it never touches the public internet. + +## Prerequisites + +- An **OVHcloud Connect** service that is active (physical link up or provider connection active). +- A **vRack** service provisioned on your OVHcloud account. If you don't have one, you can create it from the Control Panel (it's free). +- At least one OVHcloud service (server, VM, etc.) attached to the vRack. + + +--- + +### OVHcloud Control Panel Access + +- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Steps to associate + +### Via the OVHcloud Control Panel + +1. Navigate to **Network** → **vRack**. +2. Select your vRack. +3. Click **Add a service**. +4. From the list of eligible services, find your **OVHcloud Connect** service and select it. +5. Click **Add** to confirm. + +The association is typically effective within a few minutes. + +### Via the API + +> [!api] +> +> @api {v1} GET /vrack/{serviceName}/ovhCloudConnect +> + +```python +import ovh + +client = ovh.Client(endpoint='ovh-eu') + +vrack_service_name = "pn-12345" +occ_service_id = "your-occ-service-uuid" + +# Associate OVHcloud Connect with a vRack +client.post(f"/vrack/{vrack_service_name}/ovhCloudConnect", + ovhCloudConnect=occ_service_id) +``` + +> See the [OVHcloud API Console](https://eu.api.ovh.com/console/?section=%2FovhCloudConnect&branch=v1) for the complete list of vRack-related endpoints. + +### Via Terraform + +```hcl +resource "ovh_vrack_ovhcloudconnect" "association" { + service_name = "pn-abc123" # Your vRack service name + ovh_cloud_connect = "ovhcc-xyz789" # Your OVHcloud Connect service ID +} +``` + +> Check the [OVH Terraform provider documentation](https://registry.terraform.io/providers/ovh/ovh/latest/docs) for the exact resource name and attributes. + +## Verify the association + +After associating: + +1. In the **vRack** section of the Control Panel, confirm that OVHcloud Connect appears in the list of associated services. +2. Check that the **VLAN configuration** is consistent: the VLAN ID used in your OVHcloud Connect PoP configuration should match the VLAN used by your OVHcloud resources in the vRack. +3. **Test connectivity**: ping an OVHcloud resource from your external network to confirm end-to-end private communication. + +## Removing the association + +If you need to dissociate OVHcloud Connect from a vRack: + +1. Go to **Network** → **vRack** in the Control Panel. +2. Select your vRack. +3. Find the OVHcloud Connect service and click **Remove**. +4. Confirm the removal. + +> **Warning:** Removing the association will immediately interrupt private traffic between your external network and OVHcloud resources in that vRack. + +## What's next? + +- [Monitor your OVHcloud Connect](../3.9_monitor/guide.en-gb.md) +- [Set up your vRack network](../3.6_vrack_network_setup/guide.en-gb.md) to set up subnets properly + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/3.5_associate_vrack/guide.fr-fr.md b/pages/network/ovhcloud_connect/3.5_associate_vrack/guide.fr-fr.md new file mode 100644 index 00000000000..ff3c9a02cf2 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.5_associate_vrack/guide.fr-fr.md @@ -0,0 +1,145 @@ +--- +title: 'Associer un OVHcloud Connect à votre vRack' +excerpt: 'Découvrez comment associer votre service OVHcloud Connect à un vRack pour bénéficier d''une connectivité privée' +updated: 2026-02-18 +--- + +## Objectif + +Le **vRack** est le service de réseau privé d'OVHcloud. Pour permettre à vos ressources OVHcloud (serveurs, VM, etc.) de communiquer via votre lien OVHcloud Connect, vous devez associer le service OVHcloud Connect à un vRack. + +## Rôle de l'association + +```svg + + + + + + OVHcloud Connect + Lien privé vers votre réseau + + + + vRack + Fabric réseau privé + + VLAN et sous-réseaux + + + + Services OVHcloud + Bare Metal Servers + VM Public Cloud + Hosted Private Cloud + Managed Kubernetes + + + + + + + + + + + +``` + +Lorsque vous associez OVHcloud Connect à un vRack : + +- Le trafic provenant de votre réseau externe (on-premises, cloud, WAN) peut atteindre les services OVHcloud rattachés au même vRack. +- Les services OVHcloud présents dans le vRack peuvent renvoyer du trafic via OVHcloud Connect vers votre réseau. +- Toutes les communications restent **privées** — elles n'empruntent jamais l'internet public. + +## Prérequis + +- Un service **OVHcloud Connect** actif (lien physique up ou connexion opérateur active). +- Un service **vRack** provisionné sur votre compte OVHcloud. Si vous n'en disposez pas, vous pouvez le créer depuis l'espace client (gratuit). +- Au moins un service OVHcloud (serveur, VM, etc.) rattaché au vRack. + + +--- + +### Accès à l'espace client OVHcloud + +- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Étapes d'association + +### Depuis l'espace client OVHcloud + +1. Rendez-vous dans **Network** → **vRack**. +2. Sélectionnez votre vRack. +3. Cliquez sur **Ajouter un service**. +4. Dans la liste des services éligibles, sélectionnez votre service **OVHcloud Connect**. +5. Cliquez sur **Ajouter** pour confirmer. + +L'association est généralement effective en quelques minutes. + +### Via l'API + +> [!api] +> +> @api {v1} GET /vrack/{serviceName}/ovhCloudConnect +> + +```python +import ovh + +client = ovh.Client(endpoint='ovh-eu') + +vrack_service_name = "pn-12345" +occ_service_id = "your-occ-service-uuid" + +# Associer OVHcloud Connect à un vRack +client.post(f"/vrack/{vrack_service_name}/ovhCloudConnect", + ovhCloudConnect=occ_service_id) +``` + +> Consultez la [console API OVHcloud](https://eu.api.ovh.com/console/?section=%2FovhCloudConnect&branch=v1) pour la liste complète des endpoints liés au vRack. + +### Via Terraform + +```hcl +resource "ovh_vrack_ovhcloudconnect" "association" { + service_name = "pn-abc123" # Nom de votre service vRack + ovh_cloud_connect = "ovhcc-xyz789" # ID de votre service OVHcloud Connect +} +``` + +> Consultez la [documentation du provider Terraform OVH](https://registry.terraform.io/providers/ovh/ovh/latest/docs) pour connaître le nom exact de la ressource et ses attributs. + +## Vérifier l'association + +Après avoir effectué l'association : + +1. Dans la rubrique **vRack** de l'espace client, vérifiez que le service OVHcloud Connect apparaît bien dans la liste des services associés. +2. Vérifiez la cohérence de la **configuration VLAN** : le VLAN ID utilisé dans la configuration de votre PoP OVHcloud Connect doit correspondre au VLAN utilisé par vos ressources OVHcloud dans le vRack. +3. **Testez la connectivité** : envoyez un ping vers une ressource OVHcloud depuis votre réseau externe afin de confirmer la communication privée de bout en bout. + +## Supprimer l'association + +Si vous devez dissocier OVHcloud Connect d'un vRack : + +1. Rendez-vous dans **Network** → **vRack** dans l'espace client. +2. Sélectionnez votre vRack. +3. Repérez le service OVHcloud Connect et cliquez sur **Supprimer**. +4. Confirmez la suppression. + +> **Avertissement :** la suppression de l'association interrompt immédiatement le trafic privé entre votre réseau externe et les ressources OVHcloud présentes dans ce vRack. + +## Et ensuite ? + +- [Superviser votre OVHcloud Connect](../3.9_monitor/guide.fr-fr.md) +- [Configurer le réseau de votre vRack](../3.6_vrack_network_setup/guide.fr-fr.md) pour mettre en place correctement les sous-réseaux + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/3.5_associate_vrack/meta.yaml b/pages/network/ovhcloud_connect/3.5_associate_vrack/meta.yaml new file mode 100644 index 00000000000..e3dfe53ecac --- /dev/null +++ b/pages/network/ovhcloud_connect/3.5_associate_vrack/meta.yaml @@ -0,0 +1,2 @@ +id: 6884cd5f-3dd0-41d7-b19a-e08bdf3da542 +full_slug: network-ovhcloud-connect-associate-vrack diff --git a/pages/network/ovhcloud_connect/3.6_vrack_network_setup/guide.en-gb.md b/pages/network/ovhcloud_connect/3.6_vrack_network_setup/guide.en-gb.md new file mode 100644 index 00000000000..bb736445108 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.6_vrack_network_setup/guide.en-gb.md @@ -0,0 +1,241 @@ +--- +title: 'Set up the vRack network for OVHcloud Connect' +excerpt: 'Create an AZ configuration for OVHcloud Connect L3 and understand IP addressing and VRRP' +updated: 2026-04-15 +--- + +## Objective + +Before configuring OVHcloud Connect L3 routing (BGP or static), you must prepare the **AZ configuration** that creates a virtual router inside the vRack, connecting your OVHcloud Connect link to the OVHcloud AZ(s) where your services run. + +**This guide explains how to:** + +- Create an **AZ configuration** (virtual router) inside your vRack +- Understand the **IP addressing rules** for the AZ subnet (reserved addresses, VRRP) +- Understand the **limitations** of this router (no VLAN, no trunk) + +> [!primary] +> This guide covers the **basic vRack configuration for OVHcloud Connect compatibility**. For advanced vRack networking configuration, see: +> +> - [Configure OVHcloud Connect L3 with BGP](/pages/network/ovhcloud_connect_revamp/3.7_occ_l3_bgp) +> - [Configure OVHcloud Connect L3 with static routing](/pages/network/ovhcloud_connect_revamp/3.8_occ_l3_static) +> +> For general vRack networking, see the [vRack service presentation](/pages/network/vrack/global). +> + + + +## Requirements + +You need to have cleared steps 1 through 3 of one of the following guides: + +- [Quick Start: Direct Connection to OVHcloud](/pages/network/ovhcloud_connect_revamp/2.1_quick_start_direct) +- [Quick Start: Connection to OVHcloud with a Provider](/pages/network/ovhcloud_connect_revamp/2.2_quick_start_provider) + + +--- + +### OVHcloud Control Panel Access + +- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Instructions + +### Overview + +When you use OVHcloud Connect in L3 mode, traffic flows through three stages: + +``` +Your Network ──── [ PoP BGP/Static ] ──── [ vRack Router ] ──── OVHcloud AZ(s) + (OCC-specific) (this guide) +``` + +The **AZ configuration** creates an L3 routing instance inside the vRack. This routing instance is composed of two physical OVHcloud devices (labelled "A" and "B") for redundancy. You must create one AZ configuration per AZ you want to reach. + +### AZ subnet — IP addressing rules + +When you create an AZ configuration, you assign a **private subnet** to it. Within this subnet, several IP addresses are reserved by OVHcloud: + +| IP address | Role | +|---|---| +| First address (e.g. `.0`) | Network address | +| Second address (e.g. `.1`) | OVHcloud virtual router (VRRP gateway) | +| Third address (e.g. `.2`) | OVHcloud router A | +| Fourth address (e.g. `.3`) | OVHcloud router B | +| Remaining addresses | Available for your services | + +**Subnet planning guidelines:** + +| Guideline | Why | +|---|---| +| **Minimum /28 per AZ** | The API enforces this minimum. | +| **Avoid IP overlaps** | Subnets must not overlap with your on-premises network, WAN, or other cloud providers. | +| **Use private (RFC 1918) addresses** | Use `10.0.0.0/8`, `172.16.0.0/12`, or `192.168.0.0/16` ranges. | +| **Use different subnets per AZ** | One subnet cannot be stretched between two AZs. | + +### VRRP — Gateway redundancy + +The OVHcloud AZ routing instance uses **VRRP (Virtual Router Redundancy Protocol)** to provide gateway redundancy between devices A and B. + +| Property | Detail | +|---|---| +| **Virtual IP** | The second address of the AZ subnet (e.g. `172.16.1.1`) | +| **VRID** | Assigned by OVHcloud (not configurable) | +| **Master device** | Device A by default | +| **Instances per AZ** | One VRRP instance per AZ configuration | +| **Interaction with BGP** | Enabling BGP on the AZ endpoint **disables** VRRP | + +> [!primary] +> When you use **static routing** at the AZ level (extra configuration type `static`), VRRP is active and provides automatic failover between devices A and B. Your services should point their default gateway to the VRRP virtual IP. +> +> When you use **BGP** at the AZ level (extra configuration type `bgp`), VRRP is disabled. BGP handles failover instead. You must establish a BGP session with **both** device A and device B (up to 4 BGP peers per AZ). + +### vRack router limitations + +> [!warning] +> The virtual router created by the AZ configuration has the following limitations: +> +> - **No VLAN support** — The router does not handle 802.1Q VLAN tagging. All traffic is untagged. +> - **No trunk support** — The router cannot carry multiple VLANs over a single trunk interface. +> +> Plan your subnet architecture accordingly. Use separate AZ configurations if you need to isolate different traffic types across AZs. + +### Step 1 — Identify available AZs + +Before creating an AZ configuration, check which AZs are available for your OVHcloud Connect service. + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/datacenter +> + +**Example response:** + +```json +{ + "id": 1234, + "name": "GRA-DC1", + "region": "eu-west-gra", + "regionType": "3-AZ", + "available": true +} +``` + +Only AZs where `available` is `true` can receive a new configuration. + +### Step 2 — Create the AZ configuration + +The AZ configuration creates a virtual router in the vRack for the specified AZ. You need the `popId` from your existing PoP configuration. + +List your existing PoP configurations to get the `popId`: + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop +> + +Create the AZ configuration: + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter +> + +**Request parameters:** + +| Parameter | Type | Required | Description | +|---|---|---|---| +| `datacenterId` | long | Yes | ID of the AZ (from Step 1) | +| `ovhBgpArea` | long | No | OVHcloud private AS number for the AZ BGP session (assigned automatically if omitted) | +| `subnet` | ipv4Block | No | Private subnet for the AZ (/28 minimum). Example: `172.16.1.0/28` | + + +**Example response:** + +```json +{ + "id": 9012, + "function": "addDatacenterConfiguration", + "resourceId": 3456, + "status": "todo" +} +``` + +The `resourceId` is the ID of the new AZ configuration. The task progresses through `todo` → `doing` → `done`. + +### Step 3 — Verify the configuration + +Once the task completes, verify the AZ configuration: + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} +> + +**Example response:** + +```json +{ + "id": 3456, + "datacenterId": 1234, + "subnet": "172.16.1.0/28", + "ovhBgpArea": 65501, + "status": "active" +} +``` + +Monitor task progress with: + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/task/{taskId} +> + +### Step 4 — Repeat for additional AZs (optional) + +For a **multi-AZ resilient setup**, create an AZ configuration for each AZ: + +```python +# AZ 1 +client.post( + f"/ovhCloudConnect/{service_name}/config/pop/{pop_id}/datacenter", + datacenterId=1234, + subnet="172.16.1.0/28" +) + +# AZ 2 +client.post( + f"/ovhCloudConnect/{service_name}/config/pop/{pop_id}/datacenter", + datacenterId=1235, + subnet="172.16.2.0/28" +) +``` + +> [!primary] +> One subnet cannot be stretched between two AZs. Each AZ configuration must use a distinct subnet. + +For more information, refer to our guide on [Multi-AZ](/pages/network/ovhcloud_connect_revamp/1.5_multi_az). + +### Delete an AZ configuration + +> [!api] +> +> @api {v1} DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} +> + +> [!warning] +> Deleting an AZ configuration immediately stops private traffic to and from that AZ. Remove any dependent extra configurations (BGP or static) first. + +## Go further + +Now that your AZ configuration is ready, configure the OVHcloud Connect L3 routing: + +- [Configure OVHcloud Connect L3 with BGP](/pages/network/ovhcloud_connect_revamp/3.7_occ_l3_bgp) +- [Configure OVHcloud Connect L3 with static routing](/pages/network/ovhcloud_connect_revamp/3.8_occ_l3_static) +- [Monitor your connection](/pages/network/ovhcloud_connect_revamp/3.9_monitor) + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/3.6_vrack_network_setup/guide.fr-fr.md b/pages/network/ovhcloud_connect/3.6_vrack_network_setup/guide.fr-fr.md new file mode 100644 index 00000000000..0b5bf0dc260 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.6_vrack_network_setup/guide.fr-fr.md @@ -0,0 +1,241 @@ +--- +title: 'Configurer le réseau vRack pour OVHcloud Connect' +excerpt: 'Créez une configuration AZ pour OVHcloud Connect L3 et comprenez l''adressage IP ainsi que VRRP' +updated: 2026-04-15 +--- + +## Objectif + +Avant de configurer le routage L3 d'OVHcloud Connect (BGP ou statique), vous devez préparer la **configuration AZ** qui crée un routeur virtuel à l'intérieur du vRack, reliant votre lien OVHcloud Connect aux Availability Zones (AZ) OVHcloud où s'exécutent vos services. + +**Ce guide explique comment :** + +- Créer une **configuration AZ** (routeur virtuel) à l'intérieur de votre vRack +- Comprendre les **règles d'adressage IP** du sous-réseau AZ (adresses réservées, VRRP) +- Comprendre les **limitations** de ce routeur (pas de VLAN, pas de trunk) + +> [!primary] +> Ce guide couvre la **configuration vRack basique pour la compatibilité avec OVHcloud Connect**. Pour une configuration vRack avancée, consultez : +> +> - [Configurer OVHcloud Connect L3 avec BGP](/pages/network/ovhcloud_connect_revamp/3.7_occ_l3_bgp) +> - [Configurer OVHcloud Connect L3 avec du routage statique](/pages/network/ovhcloud_connect_revamp/3.8_occ_l3_static) +> +> Pour une vue générale du réseau vRack, consultez la [présentation du service vRack](/pages/network/vrack/global). +> + + + +## Prérequis + +Vous devez avoir réalisé les étapes 1 à 3 de l'un des guides suivants : + +- [Démarrage rapide : connexion directe à OVHcloud](/pages/network/ovhcloud_connect_revamp/2.1_quick_start_direct) +- [Démarrage rapide : connexion à OVHcloud via un opérateur](/pages/network/ovhcloud_connect_revamp/2.2_quick_start_provider) + + +--- + +### Accès à l'espace client OVHcloud + +- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## En pratique + +### Vue d'ensemble + +Lorsque vous utilisez OVHcloud Connect en mode L3, le trafic transite par trois étages : + +``` +Votre réseau ──── [ PoP BGP/Statique ] ──── [ Routeur vRack ] ──── AZ OVHcloud + (spécifique OCC) (ce guide) +``` + +La **configuration AZ** crée une instance de routage L3 à l'intérieur du vRack. Cette instance est composée de deux équipements physiques OVHcloud (étiquetés « A » et « B ») pour assurer la redondance. Vous devez créer une configuration AZ par AZ que vous souhaitez atteindre. + +### Sous-réseau AZ — règles d'adressage IP + +Lorsque vous créez une configuration AZ, vous lui attribuez un **sous-réseau privé**. À l'intérieur de ce sous-réseau, plusieurs adresses IP sont réservées par OVHcloud : + +| Adresse IP | Rôle | +|---|---| +| Première adresse (par exemple `.0`) | Adresse réseau | +| Deuxième adresse (par exemple `.1`) | Routeur virtuel OVHcloud (passerelle VRRP) | +| Troisième adresse (par exemple `.2`) | Routeur OVHcloud A | +| Quatrième adresse (par exemple `.3`) | Routeur OVHcloud B | +| Adresses restantes | Disponibles pour vos services | + +**Recommandations de planification du sous-réseau :** + +| Recommandation | Pourquoi | +|---|---| +| **Minimum /28 par AZ** | L'API impose ce minimum. | +| **Éviter les recouvrements d'IP** | Les sous-réseaux ne doivent pas se chevaucher avec votre réseau on-premises, votre WAN ou d'autres fournisseurs cloud. | +| **Utiliser des adresses privées (RFC 1918)** | Utilisez les plages `10.0.0.0/8`, `172.16.0.0/12` ou `192.168.0.0/16`. | +| **Utiliser des sous-réseaux différents par AZ** | Un même sous-réseau ne peut pas être étendu sur deux AZ. | + +### VRRP — redondance de la passerelle + +L'instance de routage AZ d'OVHcloud utilise **VRRP (Virtual Router Redundancy Protocol)** pour assurer la redondance de la passerelle entre les équipements A et B. + +| Propriété | Détail | +|---|---| +| **IP virtuelle** | La deuxième adresse du sous-réseau AZ (par exemple `172.16.1.1`) | +| **VRID** | Attribué par OVHcloud (non configurable) | +| **Équipement maître** | Équipement A par défaut | +| **Instances par AZ** | Une instance VRRP par configuration AZ | +| **Interaction avec BGP** | Activer BGP sur l'extrémité AZ **désactive** VRRP | + +> [!primary] +> Lorsque vous utilisez le **routage statique** au niveau de l'AZ (type de configuration extra `static`), VRRP est actif et assure le basculement automatique entre les équipements A et B. Vos services doivent pointer leur passerelle par défaut vers l'IP virtuelle VRRP. +> +> Lorsque vous utilisez **BGP** au niveau de l'AZ (type de configuration extra `bgp`), VRRP est désactivé. C'est BGP qui prend en charge le basculement. Vous devez établir une session BGP avec **les deux** équipements A et B (jusqu'à 4 pairs BGP par AZ). + +### Limitations du routeur vRack + +> [!warning] +> Le routeur virtuel créé par la configuration AZ présente les limitations suivantes : +> +> - **Pas de support VLAN** — Le routeur ne gère pas le tagging VLAN 802.1Q. Tout le trafic est non taggé. +> - **Pas de support trunk** — Le routeur ne peut pas transporter plusieurs VLAN sur une même interface trunk. +> +> Planifiez l'architecture de vos sous-réseaux en conséquence. Utilisez des configurations AZ distinctes si vous devez isoler différents types de trafic entre les AZ. + +### Étape 1 — Identifier les AZ disponibles + +Avant de créer une configuration AZ, vérifiez les AZ disponibles pour votre service OVHcloud Connect. + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/datacenter +> + +**Exemple de réponse :** + +```json +{ + "id": 1234, + "name": "GRA-DC1", + "region": "eu-west-gra", + "regionType": "3-AZ", + "available": true +} +``` + +Seules les AZ pour lesquelles `available` vaut `true` peuvent recevoir une nouvelle configuration. + +### Étape 2 — Créer la configuration AZ + +La configuration AZ crée un routeur virtuel dans le vRack pour l'AZ indiquée. Vous avez besoin de l'identifiant `popId` issu de votre configuration PoP existante. + +Listez vos configurations PoP existantes pour récupérer le `popId` : + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop +> + +Créez la configuration AZ : + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter +> + +**Paramètres de la requête :** + +| Paramètre | Type | Obligatoire | Description | +|---|---|---|---| +| `datacenterId` | long | Oui | Identifiant de l'AZ (issu de l'étape 1) | +| `ovhBgpArea` | long | Non | Numéro AS privé OVHcloud pour la session BGP de l'AZ (attribué automatiquement si omis) | +| `subnet` | ipv4Block | Non | Sous-réseau privé pour l'AZ (/28 minimum). Exemple : `172.16.1.0/28` | + + +**Exemple de réponse :** + +```json +{ + "id": 9012, + "function": "addDatacenterConfiguration", + "resourceId": 3456, + "status": "todo" +} +``` + +Le `resourceId` correspond à l'identifiant de la nouvelle configuration AZ. La tâche progresse selon les états `todo` → `doing` → `done`. + +### Étape 3 — Vérifier la configuration + +Une fois la tâche terminée, vérifiez la configuration AZ : + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} +> + +**Exemple de réponse :** + +```json +{ + "id": 3456, + "datacenterId": 1234, + "subnet": "172.16.1.0/28", + "ovhBgpArea": 65501, + "status": "active" +} +``` + +Suivez l'avancement de la tâche avec : + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/task/{taskId} +> + +### Étape 4 — Répéter pour les AZ supplémentaires (facultatif) + +Pour une **architecture résiliente multi-AZ**, créez une configuration AZ pour chaque AZ : + +```python +# AZ 1 +client.post( + f"/ovhCloudConnect/{service_name}/config/pop/{pop_id}/datacenter", + datacenterId=1234, + subnet="172.16.1.0/28" +) + +# AZ 2 +client.post( + f"/ovhCloudConnect/{service_name}/config/pop/{pop_id}/datacenter", + datacenterId=1235, + subnet="172.16.2.0/28" +) +``` + +> [!primary] +> Un même sous-réseau ne peut pas être étendu sur deux AZ. Chaque configuration AZ doit utiliser un sous-réseau distinct. + +Pour plus d'informations, reportez-vous à notre guide sur le [Multi-AZ](/pages/network/ovhcloud_connect_revamp/1.5_multi_az). + +### Supprimer une configuration AZ + +> [!api] +> +> @api {v1} DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} +> + +> [!warning] +> La suppression d'une configuration AZ stoppe immédiatement le trafic privé à destination et en provenance de cette AZ. Supprimez d'abord toute configuration extra dépendante (BGP ou statique). + +## Aller plus loin + +Maintenant que votre configuration AZ est prête, configurez le routage L3 d'OVHcloud Connect : + +- [Configurer OVHcloud Connect L3 avec BGP](/pages/network/ovhcloud_connect_revamp/3.7_occ_l3_bgp) +- [Configurer OVHcloud Connect L3 avec du routage statique](/pages/network/ovhcloud_connect_revamp/3.8_occ_l3_static) +- [Superviser votre connexion](/pages/network/ovhcloud_connect_revamp/3.9_monitor) + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/3.6_vrack_network_setup/meta.yaml b/pages/network/ovhcloud_connect/3.6_vrack_network_setup/meta.yaml new file mode 100644 index 00000000000..5903f19f61c --- /dev/null +++ b/pages/network/ovhcloud_connect/3.6_vrack_network_setup/meta.yaml @@ -0,0 +1,2 @@ +id: 8a1f484f-b554-4e3e-9429-9c27a77ead30 +full_slug: network-ovhcloud-connect-vrack-network-setup diff --git a/pages/network/ovhcloud_connect/3.7_occ_l3_bgp/guide.en-gb.md b/pages/network/ovhcloud_connect/3.7_occ_l3_bgp/guide.en-gb.md new file mode 100644 index 00000000000..1d863a9fa75 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.7_occ_l3_bgp/guide.en-gb.md @@ -0,0 +1,345 @@ +--- +title: 'Configure OVHcloud Connect L3 with BGP' +excerpt: 'Configure OVHcloud Connect L3 using BGP for dynamic route exchange between your network and OVHcloud' +updated: 2026-04-14 +--- + +## Objective + +**This guide explains how to** configure OVHcloud Connect in L3 mode with BGP. This involves two levels of configuration: + +1. **PoP configuration** — The eBGP session between your router and OVHcloud at the Point of Presence. +2. **AZ extra configuration (BGP)** — BGP peering within the OVHcloud AZ for route distribution. + +> [!primary] +> If you prefer static routing instead of BGP, see [Configure OVHcloud Connect L3 with static routing](/pages/network/ovhcloud_connect_revamp/3.8_occ_l3_static). + +## Requirements + +- An active OVHcloud Connect service (status `active`) +- OVHcloud Connect associated with a vRack — see [Associate OVHcloud Connect with your vRack](/pages/network/ovhcloud_connect_revamp/3.5_associate_vrack) +- An AZ configuration created — see [Set up vRack networking](/pages/network/ovhcloud_connect_revamp/3.6_vrack_network_setup) +- Your ASN (a public ASN or a private ASN in the range 64512–65534) +- A /30 peering subnet (e.g. `192.0.2.0/30`) +- OVHcloud API credentials (Application Key, Application Secret, Consumer Key). Refer to the [First steps with the OVHcloud API](/pages/manage-and-operate/api/first-steps) guide. + + +--- + +### OVHcloud Control Panel Access + +- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Instructions + +### Overview + +``` +Your Router ── [ eBGP at PoP ] ── OVHcloud PoP Router ── [ iBGP at DC ] ── vRack Router ── Services + ASN 65001 /30 peering ASN 35540 AZ (172.16.x.x) + extra config +``` + +- **PoP level**: An eBGP session between your router (your ASN) and OVHcloud (ASN 35540) over a /30 peering subnet. +- **AZ level**: A BGP neighbour configured inside the AZ to distribute routes to your OVHcloud services. + +### Step 1 — Identify your interface ID + +Retrieve the interface ID for your OVHcloud Connect service: + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/interface +> + + +### Step 2 — Create the PoP configuration (L3) + +The PoP configuration establishes the L3 BGP session at the Point of Presence. + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/config/pop +> + +**Request parameters:** + +| Parameter | Type | Required | Description | +|---|---|---|---| +| `interfaceId` | long | Yes | ID of the OVHcloud Connect interface | +| `type` | string | Yes | `l3` for Layer 3 mode | +| `customerBgpArea` | long | No | Your private AS number (e.g. `65001`) | +| `ovhBgpArea` | long | No | OVHcloud private AS (usually left empty — assigned automatically) | +| `subnet` | ipv4Block | No | /30 peering subnet (e.g. `192.0.2.0/30`). First IP is OVHcloud, second is yours. | + +**Example request:** + + +The `resourceId` in the response is your new `popId`. + +### Step 3 — Verify the PoP configuration + +Once the task completes: + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId} +> + + +**Example response:** + +```json +{ + "id": 5678, + "interfaceId": 101, + "type": "l3", + "customerBgpArea": 65001, + "ovhBgpArea": 35540, + "subnet": "192.0.2.0/30", + "status": "active" +} +``` + +From this response, note: + +| Parameter | Value | Meaning | +|---|---|---| +| **OVHcloud peer IP** | `192.0.2.1` | First IP of the /30 — OVHcloud side | +| **Your peer IP** | `192.0.2.2` | Second IP of the /30 — your router | +| **OVHcloud ASN** | `35540` | The `ovhBgpArea` value | +| **Your ASN** | `65001` | The `customerBgpArea` value | + +Check the BGP session state: + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/status +> + + +### Step 4 — Create AZ extra configuration (BGP) + +After the PoP configuration and the [AZ configuration](/pages/network/ovhcloud_connect_revamp/3.6_vrack_network_setup), create a **BGP extra configuration** to enable BGP route distribution within the AZ. + +> [!warning] +> Enabling BGP at the AZ level **disables VRRP** on that AZ configuration. BGP handles failover instead. You must establish a BGP session with **both** OVHcloud device A and device B (up to 4 BGP peers per AZ). By default, BFD (Bidirectional Forwarding Detection) is activated on all AZ BGP sessions — enabling BFD on your side as well is strongly recommended for faster convergence. + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra +> + +**Request parameters:** + +| Parameter | Type | Required | Description | +|---|---|---|---| +| `type` | string | Yes | `bgp` for BGP routing | +| `bgpNeighborArea` | long | No | BGP AS number for the AZ neighbour | +| `bgpNeighborIp` | ipv4 | No | Router IP for the BGP session within the AZ | + +**Example request:** + + +Verify the extra configuration: + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} +> + +**Example response:** + +```json +{ + "id": 4567, + "type": "bgp", + "bgpNeighborArea": 65501, + "bgpNeighborIp": "172.16.1.1", + "nextHop": null, + "subnet": null, + "status": "active" +} +``` + +### Step 5 — Configure BGP on your router + +Configure your physical router to establish the eBGP session with OVHcloud at the PoP. **Replace the example values** with your actual parameters from Step 3. + +#### Cisco IOS / IOS-XE + +``` +! Interface facing OVHcloud +interface GigabitEthernet0/0 + description OVHcloud Connect + ip address 192.0.2.2 255.255.255.252 + no shutdown + +! BGP configuration +router bgp 65001 + bgp log-neighbor-changes + neighbor 192.0.2.1 remote-as 35540 + neighbor 192.0.2.1 description OVHcloud-Peer + ! + address-family ipv4 unicast + neighbor 192.0.2.1 activate + network 10.0.0.0 mask 255.255.0.0 + ! Only advertise your own prefixes + neighbor 192.0.2.1 prefix-list MY-PREFIXES out + neighbor 192.0.2.1 prefix-list OVH-PREFIXES in + neighbor 192.0.2.1 maximum-prefix 100 + +ip prefix-list MY-PREFIXES seq 10 permit 10.0.0.0/16 +ip prefix-list OVH-PREFIXES seq 10 permit 172.16.0.0/12 le 24 +``` + +#### Juniper JunOS + +``` +interfaces { + ge-0/0/0 { + description "OVHcloud Connect"; + unit 0 { + family inet { + address 192.0.2.2/30; + } + } + } +} + +protocols { + bgp { + group OVHcloud { + type external; + peer-as 35540; + local-address 192.0.2.2; + neighbor 192.0.2.1 { + description "OVHcloud Peer"; + import OVH-IMPORT; + export MY-EXPORT; + } + } + } +} + +policy-options { + policy-statement MY-EXPORT { + term allow { + from { + route-filter 10.0.0.0/16 exact; + } + then accept; + } + term reject { + then reject; + } + } + policy-statement OVH-IMPORT { + term accept-ovh { + from { + route-filter 172.16.0.0/12 orlonger; + } + then accept; + } + term reject { + then reject; + } + } +} +``` + +### Step 6 — Verify the BGP session + +#### From your router + +**Cisco:** + +``` +show ip bgp summary +show bgp ipv4 unicast neighbors 192.0.2.1 +show ip route bgp +``` + +**Juniper:** + +``` +show bgp summary +show bgp neighbor 192.0.2.1 +show route protocol bgp +``` + +**Expected results:** + +| Check | Expected output | +|---|---| +| **BGP state** | `Established` | +| **Prefixes received** | At least 1 route from OVHcloud (your AZ subnets) | +| **Prefixes sent** | Your advertised prefixes visible | + +#### From the OVHcloud API + +Check PoP statistics (accepted prefixes): + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/statistics +> + + +#### Run a diagnostic + +If the session does not come up, run a peering diagnostic: + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/diagnostic +> + + +Available diagnostic names: `diagPeering`, `diagPeeringExtra`, `diagRoutes`, `diagMacs`. + +### Best practices + +- **Only advertise prefixes you own.** Do not leak third-party routes through OVHcloud Connect. +- **Apply prefix filters.** Use prefix-lists on both import and export to prevent accidental route leaks. +- **Set maximum-prefix limits.** Protect your router from receiving an unexpected number of routes. +- **Use MD5 authentication.** If required, configure MD5 on the BGP session for added security. +- **Monitor the session.** Set up alerts for BGP flaps and session drops — see [Monitor your connection](/pages/network/ovhcloud_connect_revamp/3.9_monitor). +- **For redundant setups.** Use Local Preference or AS-path prepending to control primary/backup path selection — see [Multi-AZ](/pages/network/ovhcloud_connect_revamp/1.5_multi_az). + +### Troubleshooting + +| Issue | Possible cause | Solution | +|---|---|---| +| BGP stuck in `Active` | Incorrect peer IP or ASN | Verify IP addresses and ASN on both sides. Use `GET .../config/pop/{popId}` to check OVHcloud-side values. | +| BGP stuck in `Idle` | Interface down or firewall blocking TCP 179 | Check physical link and firewall rules. Use `GET .../interface/{id}/status` to check link status. | +| No routes received | Missing `network` statement or prefix filter too restrictive | Verify export policy and `network` commands. Run `diagRoutes` diagnostic. | +| Session drops frequently (flapping) | Unstable physical link or MTU mismatch | Check interface errors and MTU settings. Use `GET .../interface/{id}/statistics` to check error counters. | +| PoP config stuck in `init` status | Task still in progress or failed | Check `GET .../task` for pending tasks. | + +### Delete configurations + +To remove the BGP configuration, delete in reverse order: + +> [!api] +> +> @api {v1} DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} +> + +> [!api] +> +> @api {v1} DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} +> + + +## Go further + +- [Set up vRack networking](/pages/network/ovhcloud_connect_revamp/3.6_vrack_network_setup) — If you have not configured AZ subnets yet +- [Associate OVHcloud Connect with your vRack](/pages/network/ovhcloud_connect_revamp/3.5_associate_vrack) +- [Monitor your connection](/pages/network/ovhcloud_connect_revamp/3.9_monitor) + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/3.7_occ_l3_bgp/guide.fr-fr.md b/pages/network/ovhcloud_connect/3.7_occ_l3_bgp/guide.fr-fr.md new file mode 100644 index 00000000000..d1cd05cff6f --- /dev/null +++ b/pages/network/ovhcloud_connect/3.7_occ_l3_bgp/guide.fr-fr.md @@ -0,0 +1,345 @@ +--- +title: 'Configurer OVHcloud Connect L3 avec BGP' +excerpt: 'Configurez OVHcloud Connect L3 avec BGP pour l’échange dynamique de routes entre votre réseau et OVHcloud' +updated: 2026-04-14 +--- + +## Objectif + +**Ce guide explique comment** configurer OVHcloud Connect en mode L3 avec BGP. Cela implique deux niveaux de configuration : + +1. **Configuration PoP** — La session eBGP entre votre routeur et OVHcloud au niveau du Point de présence. +2. **Configuration supplémentaire AZ (BGP)** — Le peering BGP au sein de l’Availability Zone OVHcloud pour la distribution des routes. + +> [!primary] +> Si vous préférez le routage statique au lieu de BGP, consultez [Configurer OVHcloud Connect L3 avec routage statique](/pages/network/ovhcloud_connect_revamp/3.8_occ_l3_static). + +## Prérequis + +- Un service OVHcloud Connect actif (statut `active`) +- OVHcloud Connect associé à un vRack — voir [Associer OVHcloud Connect à votre vRack](/pages/network/ovhcloud_connect_revamp/3.5_associate_vrack) +- Une configuration AZ créée — voir [Configurer le réseau vRack](/pages/network/ovhcloud_connect_revamp/3.6_vrack_network_setup) +- Votre ASN (un ASN public ou un ASN privé compris dans la plage 64512–65534) +- Un sous-réseau de peering /30 (par exemple `192.0.2.0/30`) +- Des identifiants de l’API OVHcloud (Application Key, Application Secret, Consumer Key). Consultez le guide [Premiers pas avec l’API OVHcloud](/pages/manage-and-operate/api/first-steps). + + +--- + +### Accès à l'espace client OVHcloud + +- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## En pratique + +### Vue d’ensemble + +``` +Votre routeur ── [ eBGP au PoP ] ── Routeur PoP OVHcloud ── [ iBGP au DC ] ── Routeur vRack ── Services + ASN 65001 peering /30 ASN 35540 AZ (172.16.x.x) + config supp. +``` + +- **Niveau PoP** : une session eBGP entre votre routeur (votre ASN) et OVHcloud (ASN 35540) sur un sous-réseau de peering /30. +- **Niveau AZ** : un voisin BGP configuré au sein de l’AZ pour distribuer les routes vers vos services OVHcloud. + +### Étape 1 — Identifier l’ID de votre interface + +Récupérez l’ID de l’interface pour votre service OVHcloud Connect : + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/interface +> + + +### Étape 2 — Créer la configuration PoP (L3) + +La configuration PoP établit la session BGP L3 au niveau du Point de présence. + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/config/pop +> + +**Paramètres de la requête :** + +| Paramètre | Type | Requis | Description | +|---|---|---|---| +| `interfaceId` | long | Oui | ID de l’interface OVHcloud Connect | +| `type` | string | Oui | `l3` pour le mode Layer 3 | +| `customerBgpArea` | long | Non | Votre numéro d’AS privé (par exemple `65001`) | +| `ovhBgpArea` | long | Non | AS privé OVHcloud (généralement laissé vide — attribué automatiquement) | +| `subnet` | ipv4Block | Non | Sous-réseau de peering /30 (par exemple `192.0.2.0/30`). La première IP est OVHcloud, la seconde est la vôtre. | + +**Exemple de requête :** + + +Le `resourceId` dans la réponse correspond à votre nouveau `popId`. + +### Étape 3 — Vérifier la configuration PoP + +Une fois la tâche terminée : + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId} +> + + +**Exemple de réponse :** + +```json +{ + "id": 5678, + "interfaceId": 101, + "type": "l3", + "customerBgpArea": 65001, + "ovhBgpArea": 35540, + "subnet": "192.0.2.0/30", + "status": "active" +} +``` + +À partir de cette réponse, notez : + +| Paramètre | Valeur | Signification | +|---|---|---| +| **IP du pair OVHcloud** | `192.0.2.1` | Première IP du /30 — côté OVHcloud | +| **Votre IP de pair** | `192.0.2.2` | Deuxième IP du /30 — votre routeur | +| **ASN OVHcloud** | `35540` | La valeur `ovhBgpArea` | +| **Votre ASN** | `65001` | La valeur `customerBgpArea` | + +Vérifiez l’état de la session BGP : + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/status +> + + +### Étape 4 — Créer la configuration supplémentaire AZ (BGP) + +Après la configuration PoP et la [configuration AZ](/pages/network/ovhcloud_connect_revamp/3.6_vrack_network_setup), créez une **configuration supplémentaire BGP** pour activer la distribution des routes BGP au sein de l’AZ. + +> [!warning] +> L’activation de BGP au niveau de l’AZ **désactive VRRP** sur cette configuration AZ. BGP gère la bascule à la place. Vous devez établir une session BGP avec **les deux** équipements OVHcloud A et B (jusqu’à 4 pairs BGP par AZ). Par défaut, BFD (Bidirectional Forwarding Detection) est activé sur toutes les sessions BGP de l’AZ — il est fortement recommandé d’activer également BFD de votre côté pour une convergence plus rapide. + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra +> + +**Paramètres de la requête :** + +| Paramètre | Type | Requis | Description | +|---|---|---|---| +| `type` | string | Oui | `bgp` pour le routage BGP | +| `bgpNeighborArea` | long | Non | Numéro d’AS BGP du voisin de l’AZ | +| `bgpNeighborIp` | ipv4 | Non | IP du routeur pour la session BGP au sein de l’AZ | + +**Exemple de requête :** + + +Vérifiez la configuration supplémentaire : + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} +> + +**Exemple de réponse :** + +```json +{ + "id": 4567, + "type": "bgp", + "bgpNeighborArea": 65501, + "bgpNeighborIp": "172.16.1.1", + "nextHop": null, + "subnet": null, + "status": "active" +} +``` + +### Étape 5 — Configurer BGP sur votre routeur + +Configurez votre routeur physique pour établir la session eBGP avec OVHcloud au niveau du PoP. **Remplacez les valeurs d’exemple** par vos paramètres réels issus de l’étape 3. + +#### Cisco IOS / IOS-XE + +``` +! Interface facing OVHcloud +interface GigabitEthernet0/0 + description OVHcloud Connect + ip address 192.0.2.2 255.255.255.252 + no shutdown + +! BGP configuration +router bgp 65001 + bgp log-neighbor-changes + neighbor 192.0.2.1 remote-as 35540 + neighbor 192.0.2.1 description OVHcloud-Peer + ! + address-family ipv4 unicast + neighbor 192.0.2.1 activate + network 10.0.0.0 mask 255.255.0.0 + ! Only advertise your own prefixes + neighbor 192.0.2.1 prefix-list MY-PREFIXES out + neighbor 192.0.2.1 prefix-list OVH-PREFIXES in + neighbor 192.0.2.1 maximum-prefix 100 + +ip prefix-list MY-PREFIXES seq 10 permit 10.0.0.0/16 +ip prefix-list OVH-PREFIXES seq 10 permit 172.16.0.0/12 le 24 +``` + +#### Juniper JunOS + +``` +interfaces { + ge-0/0/0 { + description "OVHcloud Connect"; + unit 0 { + family inet { + address 192.0.2.2/30; + } + } + } +} + +protocols { + bgp { + group OVHcloud { + type external; + peer-as 35540; + local-address 192.0.2.2; + neighbor 192.0.2.1 { + description "OVHcloud Peer"; + import OVH-IMPORT; + export MY-EXPORT; + } + } + } +} + +policy-options { + policy-statement MY-EXPORT { + term allow { + from { + route-filter 10.0.0.0/16 exact; + } + then accept; + } + term reject { + then reject; + } + } + policy-statement OVH-IMPORT { + term accept-ovh { + from { + route-filter 172.16.0.0/12 orlonger; + } + then accept; + } + term reject { + then reject; + } + } +} +``` + +### Étape 6 — Vérifier la session BGP + +#### Depuis votre routeur + +**Cisco :** + +``` +show ip bgp summary +show bgp ipv4 unicast neighbors 192.0.2.1 +show ip route bgp +``` + +**Juniper :** + +``` +show bgp summary +show bgp neighbor 192.0.2.1 +show route protocol bgp +``` + +**Résultats attendus :** + +| Vérification | Sortie attendue | +|---|---| +| **État BGP** | `Established` | +| **Préfixes reçus** | Au moins 1 route depuis OVHcloud (vos sous-réseaux d’AZ) | +| **Préfixes envoyés** | Vos préfixes annoncés visibles | + +#### Depuis l’API OVHcloud + +Vérifiez les statistiques du PoP (préfixes acceptés) : + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/statistics +> + + +#### Lancer un diagnostic + +Si la session ne s’établit pas, lancez un diagnostic de peering : + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/diagnostic +> + + +Noms de diagnostics disponibles : `diagPeering`, `diagPeeringExtra`, `diagRoutes`, `diagMacs`. + +### Bonnes pratiques + +- **Annoncez uniquement les préfixes que vous possédez.** Ne laissez pas fuiter des routes tierces via OVHcloud Connect. +- **Appliquez des filtres de préfixes.** Utilisez des prefix-lists à l’import et à l’export pour éviter les fuites de routes accidentelles. +- **Définissez des limites maximum-prefix.** Protégez votre routeur de la réception d’un nombre inattendu de routes. +- **Utilisez l’authentification MD5.** Si nécessaire, configurez MD5 sur la session BGP pour renforcer la sécurité. +- **Surveillez la session.** Configurez des alertes pour les flaps BGP et les coupures de session — voir [Surveiller votre connexion](/pages/network/ovhcloud_connect_revamp/3.9_monitor). +- **Pour les configurations redondantes.** Utilisez la Local Preference ou l’AS-path prepending pour contrôler la sélection du chemin principal/secondaire — voir [Multi-AZ](/pages/network/ovhcloud_connect_revamp/1.5_multi_az). + +### Dépannage + +| Problème | Cause possible | Solution | +|---|---|---| +| BGP bloqué en `Active` | IP de pair ou ASN incorrect | Vérifiez les adresses IP et l’ASN des deux côtés. Utilisez `GET .../config/pop/{popId}` pour vérifier les valeurs côté OVHcloud. | +| BGP bloqué en `Idle` | Interface inactive ou pare-feu bloquant le TCP 179 | Vérifiez le lien physique et les règles de pare-feu. Utilisez `GET .../interface/{id}/status` pour vérifier l’état du lien. | +| Aucune route reçue | Instruction `network` manquante ou filtre de préfixes trop restrictif | Vérifiez la politique d’export et les commandes `network`. Lancez le diagnostic `diagRoutes`. | +| La session tombe fréquemment (flapping) | Lien physique instable ou MTU non cohérent | Vérifiez les erreurs d’interface et les paramètres MTU. Utilisez `GET .../interface/{id}/statistics` pour consulter les compteurs d’erreurs. | +| Configuration PoP bloquée en statut `init` | Tâche encore en cours ou échouée | Vérifiez `GET .../task` pour les tâches en attente. | + +### Supprimer les configurations + +Pour supprimer la configuration BGP, supprimez dans l’ordre inverse : + +> [!api] +> +> @api {v1} DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} +> + +> [!api] +> +> @api {v1} DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} +> + + +## Aller plus loin + +- [Configurer le réseau vRack](/pages/network/ovhcloud_connect_revamp/3.6_vrack_network_setup) — Si vous n’avez pas encore configuré les sous-réseaux d’AZ +- [Associer OVHcloud Connect à votre vRack](/pages/network/ovhcloud_connect_revamp/3.5_associate_vrack) +- [Surveiller votre connexion](/pages/network/ovhcloud_connect_revamp/3.9_monitor) + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/3.7_occ_l3_bgp/meta.yaml b/pages/network/ovhcloud_connect/3.7_occ_l3_bgp/meta.yaml new file mode 100644 index 00000000000..7c5ebf65ce8 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.7_occ_l3_bgp/meta.yaml @@ -0,0 +1,2 @@ +id: 6ab803f1-da9c-44bd-bcad-a84cf57e35f9 +full_slug: network-ovhcloud-connect-l3-bgp diff --git a/pages/network/ovhcloud_connect/3.8_occ_l3_static/guide.en-gb.md b/pages/network/ovhcloud_connect/3.8_occ_l3_static/guide.en-gb.md new file mode 100644 index 00000000000..a9ab8e77c81 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.8_occ_l3_static/guide.en-gb.md @@ -0,0 +1,302 @@ +--- +title: 'Configure OVHcloud Connect L3 with static routes' +excerpt: 'Configure OVHcloud Connect L3 using static IP routes for predictable routing between your network and OVHcloud' +updated: 2026-04-14 +--- + +## Objective + +**This guide explains how to** configure OVHcloud Connect in L3 mode with static routing. This involves two levels of configuration: + +1. **PoP configuration** — The L3 session between your router and OVHcloud at the Point of Presence. +2. **AZ extra configuration (network)** — Static routes within the OVHcloud AZ for route distribution. + +> [!primary] +> If you prefer dynamic routing with BGP, see [Configure OVHcloud Connect L3 with BGP](/pages/network/ovhcloud_connect_revamp/3.7_occ_l3_bgp). + +### When to use static routing vs BGP + +| Criteria | Static routing | BGP | +|---|---|---| +| **Number of prefixes** | Small (1–5 routes) | Large or growing | +| **Network topology** | Simple, single-path | Complex, multi-path, multi-AZ | +| **Failover** | Manual — you must update routes yourself | Automatic — BGP reconverges | +| **Maintenance** | Routes must be updated manually when subnets change | Routes update dynamically | +| **Complexity** | Low — no routing protocol to manage | Higher — requires BGP configuration | + +Use static routing when you have a simple setup with a small number of stable prefixes and do not require automatic failover. + +## Requirements + +- An active OVHcloud Connect service (status `active`) +- OVHcloud Connect associated with a vRack — see [Associate OVHcloud Connect with your vRack](/pages/network/ovhcloud_connect_revamp/3.5_associate_vrack) +- An AZ configuration created — see [Set up vRack networking](/pages/network/ovhcloud_connect_revamp/3.6_vrack_network_setup) +- A /30 peering subnet (e.g. `192.0.2.0/30`) +- OVHcloud API credentials (Application Key, Application Secret, Consumer Key). Refer to the [First steps with the OVHcloud API](/pages/manage-and-operate/api/first-steps) guide. + + +--- + +### OVHcloud Control Panel Access + +- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Instructions + +### Overview + +``` +Your Router ── [ L3 at PoP ] ── OVHcloud PoP Router ── [ Static routes at DC ] ── vRack Router ── Services + /30 peering next-hop + subnet (172.16.x.x) +``` + +- **PoP level**: An L3 session with a /30 peering subnet between your router and OVHcloud. +- **AZ level**: Static routes defined with a next-hop IP and destination subnet. + +### Step 1 — Identify your interface ID + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/interface +> + + +### Step 2 — Create the PoP configuration (L3) + +The PoP configuration establishes the L3 session at the Point of Presence. This step is the same whether you use BGP or static routing at the AZ level. + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/config/pop +> + +**Request parameters:** + +| Parameter | Type | Required | Description | +|---|---|---|---| +| `interfaceId` | long | Yes | ID of the OVHcloud Connect interface | +| `type` | string | Yes | `l3` for Layer 3 mode | +| `customerBgpArea` | long | No | Your AS number (still required for L3 — used for PoP-level peering) | +| `subnet` | ipv4Block | No | /30 peering subnet. First IP is OVHcloud, second is yours. | + +**Example request:** + + +### Step 3 — Verify the PoP configuration + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId} +> + + +**Example response:** + +```json +{ + "id": 5678, + "interfaceId": 101, + "type": "l3", + "customerBgpArea": 65001, + "ovhBgpArea": 35540, + "subnet": "192.0.2.0/30", + "status": "active" +} +``` + +From this response: + +| Parameter | Value | Meaning | +|---|---|---| +| **OVHcloud peer IP** | `192.0.2.1` | First IP of the /30 | +| **Your peer IP** | `192.0.2.2` | Second IP of the /30 | + +### Step 4 — Create AZ extra configuration (static) + +After the PoP configuration and a [AZ configuration](/pages/network/ovhcloud_connect_revamp/3.6_vrack_network_setup), create a **network extra configuration** to define static routes within the AZ. + +> [!primary] +> With static routing, **VRRP remains active** on the AZ endpoint. OVHcloud devices A and B share a virtual IP (the second address of the AZ subnet, e.g. `172.16.1.1`). Point your services' default gateway to this VRRP virtual IP for automatic failover between devices. + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra +> + +**Request parameters:** + +| Parameter | Type | Required | Description | +|---|---|---|---| +| `type` | string | Yes | `network` for static routing | +| `nextHop` | ipv4 | No | Next-hop IP address for the static route | +| `subnet` | ipv4Block | No | Destination subnet for the static route | + +**Example request — route your on-premises subnet through the OVHcloud Connect link:** + + +#### Add multiple static routes + +Create one extra configuration per destination subnet: + + +#### Verify the extra configuration + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} +> + +**Example response:** + +```json +{ + "id": 4568, + "type": "network", + "bgpNeighborArea": null, + "bgpNeighborIp": null, + "nextHop": "172.16.1.1", + "subnet": "10.0.0.0/16", + "status": "active" +} +``` + +#### List all extra configurations for an AZ + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra +> + + +### Step 5 — Configure static routes on your router + +Configure your physical router with static routes pointing OVHcloud AZ subnets towards the OVHcloud Connect peering IP. + +#### Cisco IOS / IOS-XE + +``` +! Interface facing OVHcloud +interface GigabitEthernet0/0 + description OVHcloud Connect + ip address 192.0.2.2 255.255.255.252 + no shutdown + +! Static routes to OVHcloud AZ subnets +ip route 172.16.1.0 255.255.255.0 192.0.2.1 name OVH-DC1-Production +ip route 172.16.2.0 255.255.255.0 192.0.2.1 name OVH-DC2-Production +ip route 172.16.10.0 255.255.255.0 192.0.2.1 name OVH-DC1-Management +``` + +#### Juniper JunOS + +``` +interfaces { + ge-0/0/0 { + description "OVHcloud Connect"; + unit 0 { + family inet { + address 192.0.2.2/30; + } + } + } +} + +routing-options { + static { + route 172.16.1.0/24 next-hop 192.0.2.1; + route 172.16.2.0/24 next-hop 192.0.2.1; + route 172.16.10.0/24 next-hop 192.0.2.1; + } +} +``` + +### Step 6 — Verify connectivity + +#### From your router + +**Cisco:** + +``` +show ip route static +ping 172.16.1.1 source 192.0.2.2 +traceroute 172.16.1.1 source 192.0.2.2 +``` + +**Juniper:** + +``` +show route protocol static +ping 172.16.1.1 source 192.0.2.2 +traceroute 172.16.1.1 source 192.0.2.2 +``` + +**Expected results:** + +| Check | Expected output | +|---|---| +| **Static routes present** | Routes to 172.16.x.x via 192.0.2.1 in routing table | +| **Ping succeeds** | Reply from OVHcloud AZ subnet gateway | +| **Traceroute** | Traffic goes through 192.0.2.1 (OVHcloud PoP) | + +#### From the OVHcloud API + +Check interface status: + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/interface/{id}/status +> + +Check PoP configuration status: + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/status +> + +#### Run a diagnostic + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/diagnostic +> + + +Available diagnostic names: `diagPeering`, `diagPeeringExtra`, `diagRoutes`, `diagMacs`. + +### Limitations of static routing + +> [!warning] +> Static routing has significant limitations compared to BGP: +> +> - **No automatic failover.** If a link goes down, traffic is blackholed until you manually update routes. For automatic failover, use [BGP](/pages/network/ovhcloud_connect_revamp/3.7_occ_l3_bgp). +> - **Manual updates required.** When you add or change subnets, you must update both the OVHcloud extra configuration and your router configuration. +> - **No load balancing.** Static routes do not support ECMP or traffic engineering. Traffic follows a single path. +> - **Not recommended for multi-AZ.** For resilient multi-AZ setups, BGP is strongly recommended — see [Multi-AZ](/pages/network/ovhcloud_connect_revamp/1.5_multi_az). + +### Delete configurations + +Delete in reverse order: + +> [!api] +> +> @api {v1} DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} +> + +> [!api] +> +> @api {v1} DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} +> + + +## Go further + +- [Set up vRack networking](/pages/network/ovhcloud_connect_revamp/3.6_vrack_network_setup) — If you have not configured AZ subnets yet +- [Associate OVHcloud Connect with your vRack](/pages/network/ovhcloud_connect_revamp/3.5_associate_vrack) +- [Monitor your connection](/pages/network/ovhcloud_connect_revamp/3.9_monitor) + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/3.8_occ_l3_static/guide.fr-fr.md b/pages/network/ovhcloud_connect/3.8_occ_l3_static/guide.fr-fr.md new file mode 100644 index 00000000000..b7de8bf459f --- /dev/null +++ b/pages/network/ovhcloud_connect/3.8_occ_l3_static/guide.fr-fr.md @@ -0,0 +1,302 @@ +--- +title: 'Configurer OVHcloud Connect L3 avec des routes statiques' +excerpt: 'Configurez OVHcloud Connect L3 avec des routes IP statiques pour un routage prévisible entre votre réseau et OVHcloud' +updated: 2026-04-14 +--- + +## Objectif + +**Ce guide explique comment** configurer OVHcloud Connect en mode L3 avec routage statique. Cela implique deux niveaux de configuration : + +1. **Configuration PoP** — La session L3 entre votre routeur et OVHcloud au niveau du Point de présence. +2. **Configuration supplémentaire AZ (network)** — Des routes statiques au sein de l’Availability Zone OVHcloud pour la distribution des routes. + +> [!primary] +> Si vous préférez le routage dynamique avec BGP, consultez [Configurer OVHcloud Connect L3 avec BGP](/pages/network/ovhcloud_connect_revamp/3.7_occ_l3_bgp). + +### Quand utiliser le routage statique plutôt que BGP + +| Critère | Routage statique | BGP | +|---|---|---| +| **Nombre de préfixes** | Faible (1 à 5 routes) | Élevé ou en croissance | +| **Topologie réseau** | Simple, chemin unique | Complexe, multi-chemins, multi-AZ | +| **Bascule** | Manuelle — vous devez mettre à jour les routes vous-même | Automatique — BGP reconverge | +| **Maintenance** | Les routes doivent être mises à jour manuellement lorsque les sous-réseaux changent | Les routes sont mises à jour dynamiquement | +| **Complexité** | Faible — aucun protocole de routage à gérer | Plus élevée — nécessite la configuration de BGP | + +Utilisez le routage statique lorsque vous disposez d’une configuration simple avec un faible nombre de préfixes stables et que vous n’avez pas besoin d’une bascule automatique. + +## Prérequis + +- Un service OVHcloud Connect actif (statut `active`) +- OVHcloud Connect associé à un vRack — voir [Associer OVHcloud Connect à votre vRack](/pages/network/ovhcloud_connect_revamp/3.5_associate_vrack) +- Une configuration AZ créée — voir [Configurer le réseau vRack](/pages/network/ovhcloud_connect_revamp/3.6_vrack_network_setup) +- Un sous-réseau de peering /30 (par exemple `192.0.2.0/30`) +- Des identifiants de l’API OVHcloud (Application Key, Application Secret, Consumer Key). Consultez le guide [Premiers pas avec l’API OVHcloud](/pages/manage-and-operate/api/first-steps). + + +--- + +### Accès à l'espace client OVHcloud + +- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## En pratique + +### Vue d’ensemble + +``` +Votre routeur ── [ L3 au PoP ] ── Routeur PoP OVHcloud ── [ Routes statiques au DC ] ── Routeur vRack ── Services + peering /30 next-hop + sous-réseau (172.16.x.x) +``` + +- **Niveau PoP** : une session L3 avec un sous-réseau de peering /30 entre votre routeur et OVHcloud. +- **Niveau AZ** : des routes statiques définies par une IP next-hop et un sous-réseau de destination. + +### Étape 1 — Identifier l’ID de votre interface + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/interface +> + + +### Étape 2 — Créer la configuration PoP (L3) + +La configuration PoP établit la session L3 au niveau du Point de présence. Cette étape est identique que vous utilisiez BGP ou le routage statique au niveau de l’AZ. + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/config/pop +> + +**Paramètres de la requête :** + +| Paramètre | Type | Requis | Description | +|---|---|---|---| +| `interfaceId` | long | Oui | ID de l’interface OVHcloud Connect | +| `type` | string | Oui | `l3` pour le mode Layer 3 | +| `customerBgpArea` | long | Non | Votre numéro d’AS (toujours requis pour le L3 — utilisé pour le peering au niveau du PoP) | +| `subnet` | ipv4Block | Non | Sous-réseau de peering /30. La première IP est OVHcloud, la seconde est la vôtre. | + +**Exemple de requête :** + + +### Étape 3 — Vérifier la configuration PoP + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId} +> + + +**Exemple de réponse :** + +```json +{ + "id": 5678, + "interfaceId": 101, + "type": "l3", + "customerBgpArea": 65001, + "ovhBgpArea": 35540, + "subnet": "192.0.2.0/30", + "status": "active" +} +``` + +À partir de cette réponse : + +| Paramètre | Valeur | Signification | +|---|---|---| +| **IP du pair OVHcloud** | `192.0.2.1` | Première IP du /30 | +| **Votre IP de pair** | `192.0.2.2` | Deuxième IP du /30 | + +### Étape 4 — Créer la configuration supplémentaire AZ (statique) + +Après la configuration PoP et une [configuration AZ](/pages/network/ovhcloud_connect_revamp/3.6_vrack_network_setup), créez une **configuration supplémentaire network** pour définir des routes statiques au sein de l’AZ. + +> [!primary] +> Avec le routage statique, **VRRP reste actif** sur le point de terminaison de l’AZ. Les équipements OVHcloud A et B partagent une IP virtuelle (la deuxième adresse du sous-réseau de l’AZ, par exemple `172.16.1.1`). Pointez la passerelle par défaut de vos services vers cette IP virtuelle VRRP pour une bascule automatique entre les équipements. + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra +> + +**Paramètres de la requête :** + +| Paramètre | Type | Requis | Description | +|---|---|---|---| +| `type` | string | Oui | `network` pour le routage statique | +| `nextHop` | ipv4 | Non | Adresse IP next-hop pour la route statique | +| `subnet` | ipv4Block | Non | Sous-réseau de destination pour la route statique | + +**Exemple de requête — router votre sous-réseau on-premises via le lien OVHcloud Connect :** + + +#### Ajouter plusieurs routes statiques + +Créez une configuration supplémentaire par sous-réseau de destination : + + +#### Vérifier la configuration supplémentaire + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} +> + +**Exemple de réponse :** + +```json +{ + "id": 4568, + "type": "network", + "bgpNeighborArea": null, + "bgpNeighborIp": null, + "nextHop": "172.16.1.1", + "subnet": "10.0.0.0/16", + "status": "active" +} +``` + +#### Lister toutes les configurations supplémentaires d’une AZ + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra +> + + +### Étape 5 — Configurer les routes statiques sur votre routeur + +Configurez votre routeur physique avec des routes statiques pointant les sous-réseaux d’AZ OVHcloud vers l’IP de peering OVHcloud Connect. + +#### Cisco IOS / IOS-XE + +``` +! Interface facing OVHcloud +interface GigabitEthernet0/0 + description OVHcloud Connect + ip address 192.0.2.2 255.255.255.252 + no shutdown + +! Static routes to OVHcloud AZ subnets +ip route 172.16.1.0 255.255.255.0 192.0.2.1 name OVH-DC1-Production +ip route 172.16.2.0 255.255.255.0 192.0.2.1 name OVH-DC2-Production +ip route 172.16.10.0 255.255.255.0 192.0.2.1 name OVH-DC1-Management +``` + +#### Juniper JunOS + +``` +interfaces { + ge-0/0/0 { + description "OVHcloud Connect"; + unit 0 { + family inet { + address 192.0.2.2/30; + } + } + } +} + +routing-options { + static { + route 172.16.1.0/24 next-hop 192.0.2.1; + route 172.16.2.0/24 next-hop 192.0.2.1; + route 172.16.10.0/24 next-hop 192.0.2.1; + } +} +``` + +### Étape 6 — Vérifier la connectivité + +#### Depuis votre routeur + +**Cisco :** + +``` +show ip route static +ping 172.16.1.1 source 192.0.2.2 +traceroute 172.16.1.1 source 192.0.2.2 +``` + +**Juniper :** + +``` +show route protocol static +ping 172.16.1.1 source 192.0.2.2 +traceroute 172.16.1.1 source 192.0.2.2 +``` + +**Résultats attendus :** + +| Vérification | Sortie attendue | +|---|---| +| **Routes statiques présentes** | Routes vers 172.16.x.x via 192.0.2.1 dans la table de routage | +| **Le ping aboutit** | Réponse depuis la passerelle du sous-réseau d’AZ OVHcloud | +| **Traceroute** | Le trafic passe par 192.0.2.1 (PoP OVHcloud) | + +#### Depuis l’API OVHcloud + +Vérifiez l’état de l’interface : + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/interface/{id}/status +> + +Vérifiez le statut de la configuration PoP : + +> [!api] +> +> @api {v1} GET /ovhCloudConnect/{serviceName}/config/pop/{popId}/status +> + +#### Lancer un diagnostic + +> [!api] +> +> @api {v1} POST /ovhCloudConnect/{serviceName}/diagnostic +> + + +Noms de diagnostics disponibles : `diagPeering`, `diagPeeringExtra`, `diagRoutes`, `diagMacs`. + +### Limites du routage statique + +> [!warning] +> Le routage statique présente des limites importantes par rapport à BGP : +> +> - **Pas de bascule automatique.** Si un lien tombe, le trafic est blackholé jusqu’à ce que vous mettiez manuellement à jour les routes. Pour une bascule automatique, utilisez [BGP](/pages/network/ovhcloud_connect_revamp/3.7_occ_l3_bgp). +> - **Mises à jour manuelles requises.** Lorsque vous ajoutez ou modifiez des sous-réseaux, vous devez mettre à jour à la fois la configuration supplémentaire OVHcloud et la configuration de votre routeur. +> - **Pas de répartition de charge.** Les routes statiques ne prennent pas en charge ECMP ni le traffic engineering. Le trafic suit un chemin unique. +> - **Non recommandé pour le multi-AZ.** Pour les configurations multi-AZ résilientes, BGP est fortement recommandé — voir [Multi-AZ](/pages/network/ovhcloud_connect_revamp/1.5_multi_az). + +### Supprimer les configurations + +Supprimez dans l’ordre inverse : + +> [!api] +> +> @api {v1} DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} +> + +> [!api] +> +> @api {v1} DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} +> + + +## Aller plus loin + +- [Configurer le réseau vRack](/pages/network/ovhcloud_connect_revamp/3.6_vrack_network_setup) — Si vous n’avez pas encore configuré les sous-réseaux d’AZ +- [Associer OVHcloud Connect à votre vRack](/pages/network/ovhcloud_connect_revamp/3.5_associate_vrack) +- [Surveiller votre connexion](/pages/network/ovhcloud_connect_revamp/3.9_monitor) + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/3.8_occ_l3_static/meta.yaml b/pages/network/ovhcloud_connect/3.8_occ_l3_static/meta.yaml new file mode 100644 index 00000000000..fd9bdf27c7a --- /dev/null +++ b/pages/network/ovhcloud_connect/3.8_occ_l3_static/meta.yaml @@ -0,0 +1,2 @@ +id: d5edb71b-03fa-4f0f-a7b8-83827b67384e +full_slug: network-ovhcloud-connect-l3-static diff --git a/pages/network/ovhcloud_connect/3.9_monitor/guide.en-gb.md b/pages/network/ovhcloud_connect/3.9_monitor/guide.en-gb.md new file mode 100644 index 00000000000..914e07154cf --- /dev/null +++ b/pages/network/ovhcloud_connect/3.9_monitor/guide.en-gb.md @@ -0,0 +1,195 @@ +--- +title: 'Monitor Your OVHcloud Connect' +excerpt: 'Discover the tools and metrics available to monitor your OVHcloud Connect service' +updated: 2026-02-18 +--- + +## Objective + +Monitoring your OVHcloud Connect service ensures that the connection is healthy, performant, and meeting your expectations. This guide covers the tools and metrics available. + + +--- + +### OVHcloud Control Panel Access + +- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Monitoring tools + +### OVHcloud Control Panel + +The primary interface for monitoring your connection provides visibility into the following metrics: + +| Metric | Description | +|---|---| +| **Connection status** | Whether the physical link is up or down | +| **BGP session status** | Whether BGP peering is Established, Active, or Idle | +| **Bandwidth usage** | Current and historical throughput (inbound/outbound) | +| **Port status** | Physical interface state and error counters | +| **Service details** | PoP, bandwidth tier, vRack association, configuration | + +### OVHcloud API + +For programmatic monitoring and integration with your own tools: + +```python +import ovh + +client = ovh.Client(endpoint='ovh-eu') + +service_name = "your-occ-service-uuid" + +# Get service status +service = client.get(f"/ovhCloudConnect/{service_name}") +print(f"Status: {service['status']}") + +# Get PoP configuration and BGP state +pop_config = client.get(f"/ovhCloudConnect/{service_name}/config/pop") +print(pop_config) +``` + +> Full API reference: [eu.api.ovh.com/console](https://eu.api.ovh.com/console/?section=%2FovhCloudConnect&branch=v1) + +### Your own monitoring tools + +Complement OVHcloud's monitoring with your own infrastructure: + +- **SNMP** — Poll your router's interfaces for traffic counters, error rates, and interface status. +- **BGP monitoring** — Use tools like `bgpstream`, `exabgp`, or your router's built-in monitoring to track BGP session stability and prefix changes. +- **Ping / latency probes** — Set up regular pings or latency measurements between your on-premises network and OVHcloud resources. +- **Third-party platforms** — Tools like Datadog, Zabbix, PRTG, or Grafana can aggregate metrics from both your infrastructure and OVHcloud's API. + +## On-demand diagnostics + +You can launch on-demand diagnostics from the OVHcloud Control Panel to get a point-in-time status report of your OVHcloud Connect service. Each diagnostic runs in real time against the OVHcloud-side equipment and returns a result you can view or download. + +### Available diagnostics + +**Layer 3 mode:** + +| Diagnostic | Description | +|---|---| +| **BGP Peering Test** | Fetches the BGP session state and related information. | +| **Routes** | Fetches the routing table learned by OVHcloud via BGP (routes received from your side). | +| **Advertised-Routes** | Fetches the routing table advertised by OVHcloud to your side. | + +**Layer 2 mode:** + +| Diagnostic | Description | +|---|---| +| **MAC Address** | Fetches the list of MAC addresses seen on the Layer 2 segment between your network devices and the vRack. | + +### Launch a diagnostic + +1. Open the OVHcloud Connect service you want to diagnose. +2. At the bottom of the "POP Configuration" panel, in the "Diagnostic POP" segment, click the ellipsis button `...`{.action}. +3. Select the diagnostic to run — for example `BGP Peering Test`{.action} in Layer 3 mode, or `Get the list of my MAC addresses`{.action} in Layer 2 mode. +4. Confirm by clicking `Launch diagnostic`{.action}. + +### Retrieve a result + +1. Open the `Diagnostics`{.action} tab of the service. Each diagnostic is listed with its ID and timestamp. +2. Click the ellipsis button `...`{.action} next to the entry. +3. Select `See result`{.action} to open the output in a new window, or `Download result`{.action} to save a `.txt` file. + +### Limits + +| Limit | Value | +|---|---| +| **Retention** | Only diagnostics initiated **within the last seven days** are accessible. Download and archive the ones you need to keep. | +| **Rate limit** | **10 diagnostics per type, per service, per 24 hours.** This applies independently to each diagnostic type (BGP Peering Test, Routes, Advertised-Routes, MAC Address). | + +> [!primary] +> +> Diagnostics are also available programmatically through the OVHcloud API under the `/ovhCloudConnect/{serviceName}/diagnostic/...` endpoints. Refer to the [API console](/links/api) for the full list. +> + +## Key metrics to watch + +```svg + + + + + Link Status + Up / Down + Error counters + + + BGP State + Session status + Prefix count + + + Throughput + Bandwidth in/out + Peak vs. average + + + Latency + Round-trip time + Jitter + + + Alerts to configure + Link down · BGP flap · Bandwidth > 80% · Latency spike · Prefix change + Notify by email, SMS, or integration with your incident system + +``` + +### Critical alerts (set these up immediately) + +| Alert | Trigger | Action | +|---|---|---| +| **Link down** | Physical port state changes to "down" | Check cross-connect, SFP, and contact data centre or provider | +| **BGP session down** | BGP session state changes from "Established" | Check router configuration, peer reachability, and firewall rules | +| **High bandwidth usage** | Throughput exceeds 80% of provisioned capacity | Plan a bandwidth upgrade or optimise traffic | +| **Latency spike** | RTT increases significantly above baseline | Run traceroute and check for congestion or routing changes | +| **Prefix count change** | Unexpected increase or decrease in received/sent prefixes | Investigate route leaks or configuration changes | + +## Monitoring commands on your router + +### Cisco IOS + +``` +show interfaces GigabitEthernet0/0 +show ip bgp summary +show ip bgp neighbors 192.0.2.1 received-routes +show ip bgp neighbors 192.0.2.1 advertised-routes +show ip route bgp +``` + +### Juniper JunOS + +``` +show interfaces terse +show bgp summary +show route receive-protocol bgp 192.0.2.1 +show route advertising-protocol bgp 192.0.2.1 +show route protocol bgp +``` + +## Best practices + +- **Monitor from both sides** — Check metrics on your router and in the OVHcloud Control Panel. +- **Baseline your metrics** — Record normal bandwidth, latency, and prefix counts so you can detect anomalies. +- **Automate alerting** — Don't rely on manual checks. Set up automated notifications for critical events. +- **Review regularly** — Check monitoring dashboards weekly to spot trends (growing bandwidth, increasing latency). +- **Test failover** — If you have a Multi-AZ setup, periodically test failover and verify that monitoring detects the switch. + +## What's next? + +- [Forward your OVHcloud Connect logs](../3.12_log_forwarding/guide.en-gb.md) to Logs Data Platform for long-term storage and analysis +- [Declare and follow up on an incident](../3.10_incident_followup/guide.en-gb.md) if you detect a problem +- Review [SLAs](../1.7_slas/guide.en-gb.md) to understand uptime guarantees + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/3.9_monitor/guide.fr-fr.md b/pages/network/ovhcloud_connect/3.9_monitor/guide.fr-fr.md new file mode 100644 index 00000000000..57ec9060392 --- /dev/null +++ b/pages/network/ovhcloud_connect/3.9_monitor/guide.fr-fr.md @@ -0,0 +1,195 @@ +--- +title: 'Surveiller votre OVHcloud Connect' +excerpt: 'Découvrez les outils et les métriques disponibles pour surveiller votre service OVHcloud Connect' +updated: 2026-02-18 +--- + +## Objectif + +La surveillance de votre service OVHcloud Connect garantit que la connexion est saine, performante et conforme à vos attentes. Ce guide présente les outils et les métriques disponibles. + + +--- + +### Accès à l'espace client OVHcloud + +- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) +- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} + +--- + + +## Outils de surveillance + +### Espace client OVHcloud + +L'interface principale de surveillance de votre connexion donne accès aux métriques suivantes : + +| Métrique | Description | +|---|---| +| **État de la connexion** | Indique si le lien physique est actif ou inactif | +| **État de la session BGP** | Indique si le peering BGP est Established, Active ou Idle | +| **Utilisation de la bande passante** | Débit actuel et historique (entrant/sortant) | +| **État du port** | État de l’interface physique et compteurs d’erreurs | +| **Détails du service** | PoP, niveau de bande passante, association vRack, configuration | + +### API OVHcloud + +Pour une surveillance programmatique et une intégration avec vos propres outils : + +```python +import ovh + +client = ovh.Client(endpoint='ovh-eu') + +service_name = "your-occ-service-uuid" + +# Get service status +service = client.get(f"/ovhCloudConnect/{service_name}") +print(f"Status: {service['status']}") + +# Get PoP configuration and BGP state +pop_config = client.get(f"/ovhCloudConnect/{service_name}/config/pop") +print(pop_config) +``` + +> Référence complète de l’API : [eu.api.ovh.com/console](https://eu.api.ovh.com/console/?section=%2FovhCloudConnect&branch=v1) + +### Vos propres outils de surveillance + +Complétez la surveillance d’OVHcloud avec votre propre infrastructure : + +- **SNMP** — Interrogez les interfaces de votre routeur pour obtenir les compteurs de trafic, les taux d’erreur et l’état des interfaces. +- **Surveillance BGP** — Utilisez des outils tels que `bgpstream`, `exabgp` ou la surveillance intégrée de votre routeur pour suivre la stabilité des sessions BGP et les changements de préfixes. +- **Sondes ping / latence** — Mettez en place des pings réguliers ou des mesures de latence entre votre réseau on-premises et les ressources OVHcloud. +- **Plateformes tierces** — Des outils comme Datadog, Zabbix, PRTG ou Grafana peuvent agréger les métriques provenant à la fois de votre infrastructure et de l’API OVHcloud. + +## Diagnostics à la demande + +Vous pouvez lancer des diagnostics à la demande depuis l’espace client OVHcloud afin d’obtenir un rapport d’état ponctuel de votre service OVHcloud Connect. Chaque diagnostic s’exécute en temps réel sur les équipements côté OVHcloud et renvoie un résultat que vous pouvez consulter ou télécharger. + +### Diagnostics disponibles + +**Mode Layer 3 :** + +| Diagnostic | Description | +|---|---| +| **BGP Peering Test** | Récupère l’état de la session BGP et les informations associées. | +| **Routes** | Récupère la table de routage apprise par OVHcloud via BGP (routes reçues de votre côté). | +| **Advertised-Routes** | Récupère la table de routage annoncée par OVHcloud à votre côté. | + +**Mode Layer 2 :** + +| Diagnostic | Description | +|---|---| +| **MAC Address** | Récupère la liste des adresses MAC vues sur le segment Layer 2 entre vos équipements réseau et le vRack. | + +### Lancer un diagnostic + +1. Ouvrez le service OVHcloud Connect que vous souhaitez diagnostiquer. +2. En bas du panneau « POP Configuration », dans la section « Diagnostic POP », cliquez sur le bouton points de suspension `...`{.action}. +3. Sélectionnez le diagnostic à exécuter — par exemple `BGP Peering Test`{.action} en mode Layer 3, ou `Obtenir la liste de mes adresses MAC`{.action} en mode Layer 2. +4. Confirmez en cliquant sur `Lancer le diagnostic`{.action}. + +### Récupérer un résultat + +1. Ouvrez l’onglet `Diagnostics`{.action} du service. Chaque diagnostic est listé avec son ID et son horodatage. +2. Cliquez sur le bouton points de suspension `...`{.action} en regard de l’entrée. +3. Sélectionnez `Voir le résultat`{.action} pour ouvrir la sortie dans une nouvelle fenêtre, ou `Télécharger le résultat`{.action} pour enregistrer un fichier `.txt`. + +### Limites + +| Limite | Valeur | +|---|---| +| **Rétention** | Seuls les diagnostics initiés **au cours des sept derniers jours** sont accessibles. Téléchargez et archivez ceux que vous souhaitez conserver. | +| **Limite de débit** | **10 diagnostics par type, par service et par période de 24 heures.** Cela s’applique indépendamment à chaque type de diagnostic (BGP Peering Test, Routes, Advertised-Routes, MAC Address). | + +> [!primary] +> +> Les diagnostics sont également disponibles de manière programmatique via l’API OVHcloud sous les endpoints `/ovhCloudConnect/{serviceName}/diagnostic/...`. Consultez la [console API](/links/api) pour la liste complète. +> + +## Métriques clés à surveiller + +```svg + + + + + État du lien + Up / Down + Compteurs d’erreurs + + + État BGP + État de la session + Nombre de préfixes + + + Débit + Bande passante in/out + Pic vs moyenne + + + Latence + Temps aller-retour + Gigue + + + Alertes à configurer + Lien down · Flap BGP · Bande passante > 80 % · Pic de latence · Changement de préfixes + Notification par e-mail, SMS ou intégration avec votre système d’incidents + +``` + +### Alertes critiques (à mettre en place immédiatement) + +| Alerte | Déclencheur | Action | +|---|---|---| +| **Lien down** | L’état du port physique passe à « down » | Vérifiez le cross-connect, le SFP et contactez le datacenter ou le fournisseur | +| **Session BGP down** | L’état de la session BGP n’est plus « Established » | Vérifiez la configuration du routeur, l’accessibilité du pair et les règles de pare-feu | +| **Utilisation élevée de la bande passante** | Le débit dépasse 80 % de la capacité provisionnée | Planifiez une montée en bande passante ou optimisez le trafic | +| **Pic de latence** | Le RTT augmente significativement au-dessus de la référence | Lancez un traceroute et vérifiez la présence de congestion ou de changements de routage | +| **Changement du nombre de préfixes** | Augmentation ou diminution inattendue des préfixes reçus/envoyés | Investiguez d’éventuelles fuites de routes ou modifications de configuration | + +## Commandes de surveillance sur votre routeur + +### Cisco IOS + +``` +show interfaces GigabitEthernet0/0 +show ip bgp summary +show ip bgp neighbors 192.0.2.1 received-routes +show ip bgp neighbors 192.0.2.1 advertised-routes +show ip route bgp +``` + +### Juniper JunOS + +``` +show interfaces terse +show bgp summary +show route receive-protocol bgp 192.0.2.1 +show route advertising-protocol bgp 192.0.2.1 +show route protocol bgp +``` + +## Bonnes pratiques + +- **Surveillez des deux côtés** — Vérifiez les métriques sur votre routeur et dans l’espace client OVHcloud. +- **Établissez une référence pour vos métriques** — Enregistrez la bande passante, la latence et le nombre de préfixes en conditions normales afin de pouvoir détecter les anomalies. +- **Automatisez les alertes** — Ne vous fiez pas aux contrôles manuels. Configurez des notifications automatiques pour les événements critiques. +- **Faites des revues régulières** — Consultez les tableaux de bord de surveillance chaque semaine afin de repérer les tendances (croissance de la bande passante, augmentation de la latence). +- **Testez la bascule** — Si vous disposez d’une configuration Multi-AZ, testez périodiquement la bascule et vérifiez que la surveillance détecte le basculement. + +## Et ensuite ? + +- [Transférer les logs de votre OVHcloud Connect](../3.12_log_forwarding/guide.fr-fr.md) vers Logs Data Platform pour un stockage et une analyse à long terme +- [Déclarer et suivre un incident](../3.10_incident_followup/guide.fr-fr.md) si vous détectez un problème +- Consultez les [SLA](../1.7_slas/guide.fr-fr.md) pour comprendre les garanties de disponibilité + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/meta.yaml b/pages/network/ovhcloud_connect/3.9_monitor/meta.yaml similarity index 100% rename from pages/network/ovhcloud_connect/occ-diagnostics/meta.yaml rename to pages/network/ovhcloud_connect/3.9_monitor/meta.yaml diff --git a/pages/network/ovhcloud_connect/4.1_simple/guide.en-gb.md b/pages/network/ovhcloud_connect/4.1_simple/guide.en-gb.md new file mode 100644 index 00000000000..a4166f4821c --- /dev/null +++ b/pages/network/ovhcloud_connect/4.1_simple/guide.en-gb.md @@ -0,0 +1,708 @@ +--- +title: Set up a simple OVHcloud Connect architecture +excerpt: Connect a single on-premises site, branch WAN, or public cloud (AWS, Azure, GCP) environment to OVHcloud through one OVHcloud Connect link. +updated: 2026-02-18 +--- + +## Objective + +This tutorial guides you through connecting a single on-premises site to OVHcloud using **one OVHcloud Connect link**. This is the simplest architecture, suitable when you need private connectivity but can accept a single path (no built-in redundancy). + +## Instructions + +Below, you will find prerequisites and instructions for five separate use-cases, which you may choose depending on desired architecture. + +> [!tabs] +> On-Premises +>>### Prerequisites +>> +>>- An OVHcloud account with a vRack +>>- A router in a data centre with OVHcloud PoP presence (for Direct) or a provider account (for Provider) +>>- BGP-capable network equipment +>>- An IP addressing plan with no overlaps between your network and OVHcloud subnets +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> On-Premises +>> Your data centre +>> Router + BGP +>> 10.0.0.0/16 +>> +>> +>> +>> PoP +>> Cross-connect +>> BGP peering +>> +>> +>> +>> OVHcloud +>> vRack +>> Servers / VMs +>> 172.16.0.0/16 +>> +>> +>> +>> +>> 1 Gbps or +>> 10 Gbps +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### When to use this architecture +>> +>>| ✅ Good for | ❌ Not recommended for | +>>|---|---| +>>| Development and test environments | Business-critical production workloads | +>>| Non-critical production workloads | Regulated / compliance-heavy environments | +>>| Proof of concept or pilot projects | Applications requiring 99.99% uptime | +>>| Small offices with a single site | Multi-site organisations needing failover | +>> +>>#### 1. Order OVHcloud Connect +>> +>>Choose **Direct** or **Provider** depending on your situation: +>> +>>- **Direct** — You have equipment in the same data centre as an OVHcloud PoP. See [Order Direct](../3.1_order_direct). +>>- **Provider** — You prefer a managed connection. See [Order Provider](../3.2_order_provider). +>> +>>#### 2. Install the physical connection +>> +>>- **Direct:** Provide the LOA to the data centre operator to install a cross-connect. See [Cross Connect LOA](../3.11_cross_connect_loa). +>>- **Provider:** Share the service key with your provider and wait for activation. +>> +>>#### 3. Configure BGP +>> +>>Set up a single BGP session between your on-premises router and OVHcloud: +>> +>>- Advertise your on-premises prefixes (e.g. `10.0.0.0/16`) to OVHcloud. +>>- Accept OVHcloud prefixes (e.g. `172.16.0.0/16`) from OVHcloud. +>> +>>See [Configure OCC L3 with BGP](../3.7_occ_l3_bgp) for detailed instructions and configuration examples. +>> +>>#### 4. Associate with vRack +>> +>>Link your OVHcloud Connect service to your vRack. See [Associate with vRack](../3.5_associate_vrack). +>> +>>#### 5. Configure AZ subnets +>> +>>Define the private subnets in OVHcloud that your on-premises network should reach. See [Set up your vRack network](../3.6_vrack_network_setup). +>> +>>#### 6. Test connectivity +>> +>>| Test | Command | +>>|---|---| +>>| Ping from on-prem to OVHcloud VM | `ping 172.16.1.10` | +>>| Ping from OVHcloud VM to on-prem | `ping 10.0.0.1` | +>>| Traceroute | `traceroute 172.16.1.10` (should not go via internet) | +>>| BGP verification | `show ip bgp summary` | +>> +>>#### 7. Set up monitoring +>> +>>Configure monitoring alerts for link status, BGP session, and bandwidth. See [Monitor](../3.9_monitor). +>> +>>### Limitations of a simple connection +>> +>>- **Single point of failure** — If the link, PoP, or cross-connect fails, connectivity is lost. +>>- **No automatic failover** — You need to manually intervene or rely on internet-based backup. +>>- **Lower SLA** — A single connection typically supports up to 99.9% SLA (see [SLAs](../1.7_slas)). +>> +>>**Recommendation:** For production workloads, consider upgrading to a [resilient architecture](../4.2_resilient). +>> +> WAN +>>### Prerequisites +>> +>>- An OVHcloud account with a vRack +>>- A router in a data centre with OVHcloud PoP presence (for Direct) or a provider account (for Provider) +>>- BGP-capable network equipment +>>- An IP addressing plan with no overlaps between your network and OVHcloud subnets +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> Branch Offices +>> Office A +>> Office B +>> Office C +>> 10.x.x.x/16 +>> +>> +>> +>> WAN / SD-WAN +>> MPLS backbone +>> or SD-WAN fabric +>> +>> +>> +>> PoP +>> BGP session +>> VLAN +>> +>> +>> +>> OVHcloud +>> vRack · Servers · VMs +>> 172.16.0.0/16 +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### How it differs from on-premises +>> +>>In a WAN scenario, your traffic typically originates from **multiple branch offices** or sites and is aggregated through a WAN backbone (MPLS or SD-WAN) before reaching the OVHcloud PoP. The WAN edge device (router or SD-WAN gateway) is the equipment that peers with OVHcloud via BGP. +>> +>>### When to use this architecture +>> +>>| ✅ Good for | ❌ Not recommended for | +>>|---|---| +>>| Connecting multiple branch offices to OVHcloud through a single WAN exit | Critical workloads needing 99.99% uptime | +>>| Branch consolidation to a cloud environment | Multi-cloud setups requiring diverse paths | +>>| Hybrid SD-WAN deployments | Highly regulated environments | +>> +>>### Step-by-step +>> +>>#### 1. Coordinate with your WAN provider +>> +>>Contact your WAN/MPLS/SD-WAN provider and request: +>> +>>- A **circuit** or **virtual connection** from your WAN backbone to the OVHcloud PoP. +>>- The circuit should terminate at a facility where OVHcloud has a PoP (see [PoP Locations](../1.4_pop_locations_regions)). +>> +>>If your WAN provider is also an OVHcloud Connect provider (e.g. Megaport, Equinix), they can handle both the WAN handoff and the OVHcloud Connect provisioning. +>> +>>#### 2. Order OVHcloud Connect +>> +>>- **Direct:** If your WAN edge router is co-located at the OVHcloud PoP. See [Order Direct](../3.1_order_direct). +>>- **Provider:** If the connection is managed by a provider. See [Order Provider](../3.2_order_provider). +>> +>>#### 3. Configure BGP on the WAN edge +>> +>>Set up a BGP session between your **WAN edge device** and OVHcloud: +>> +>>- Advertise aggregated branch prefixes (e.g. `10.0.0.0/8` or more specific per-branch subnets). +>>- Accept OVHcloud routes. +>>- Ensure your WAN routing propagates the OVHcloud routes back to all branch offices. +>> +>>See [Configure OCC L3 with BGP](../3.7_occ_l3_bgp). +>> +>>#### 4. Associate with vRack and configure subnets +>> +>>Link to your vRack and set up the required subnets. See [Associate with vRack](../3.5_associate_vrack) and [Set up your vRack network](../3.6_vrack_network_setup). +>> +>>#### 5. Test end-to-end connectivity +>> +>>From a branch office, verify you can reach OVHcloud resources: +>> +>>``` +>>ping 172.16.1.10 ## Ping an OVHcloud VM +>>traceroute 172.16.1.10 ## Should go: branch → WAN → PoP → OVHcloud (private) +>>``` +>> +>>Verify from OVHcloud back to a branch: +>> +>>```bash +>>ping 10.1.0.1 ## Ping a branch IP from an OVHcloud VM +>>``` +>> +>>#### 6. Set up monitoring +>> +>>Monitor the WAN edge BGP session and OVHcloud Connect link. See [Monitor](../3.9_monitor). +>> +> AWS +>>### Prerequisites +>> +>>- An **AWS account** with a VPC configured +>>- An **OVHcloud account** with a vRack +>>- An account with a **shared provider** that supports both AWS Direct Connect and OVHcloud Connect +>>- Non-overlapping IP ranges between AWS VPC and OVHcloud subnets +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> AWS +>> VPC: 10.1.0.0/16 +>> Direct Connect +>> Virtual Interface (VIF) +>> +>> +>> +>> Interconnection Provider +>> Megaport / Equinix Fabric +>> Bridging AWS ↔ OVHcloud +>> +>> +>> +>> OVHcloud +>> vRack: 172.16.0.0/16 +>> OVHcloud Connect +>> Servers / VMs +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### How it works +>> +>>The connection between AWS and OVHcloud is typically routed through a **shared provider** (such as Megaport or Equinix Fabric) that has physical presence at both AWS Direct Connect locations and OVHcloud PoPs. +>> +>>1. **On the AWS side**, you create a Direct Connect connection (or hosted connection) and a Virtual Interface (VIF) that connects your AWS VPC. +>>2. **On the provider side**, you create a virtual cross-connect (VXC) that bridges the AWS VIF to the OVHcloud Connect service. +>>3. **On the OVHcloud side**, you configure BGP and associate the connection with your vRack. +>> +>>### Step-by-step +>> +>>#### 1. Set up AWS Direct Connect +>> +>>1. In the **AWS Console**, go to **Direct Connect** → **Connections**. +>>2. Create a new connection (or use a hosted connection via your provider). +>>3. Select the **AWS Direct Connect location** closest to your OVHcloud PoP. +>>4. Create a **Private Virtual Interface (VIF)** associated with your VPC or Virtual Private Gateway. +>>5. Note the BGP ASN, peer IPs, and VLAN ID. +>> +>> For more information, please consult [AWS Direct Connect documentation](https://docs.aws.amazon.com/directconnect/) +>> +>>#### 2. Order OVHcloud Connect Provider +>> +>>1. In the **OVHcloud Control Panel**, order OVHcloud Connect Provider. +>>2. Select the same provider you're using for AWS (e.g. Megaport). +>>3. Choose the PoP location. +>>4. Copy the **service key**. +>> +>>See [Order OVHcloud Connect Provider](../3.2_order_provider). +>> +>>#### 3. Create the bridge on the provider +>> +>>In your provider's portal, create connections that bridge AWS and OVHcloud: +>> +>>**Example with Megaport:** +>> +>>1. Create a **Megaport port** or use an existing one. +>>2. Create a **VXC to AWS** using the AWS Direct Connect hosted connection details. +>>3. Create a **VXC to OVHcloud** using the OVHcloud service key. +>>4. Optionally, use a **Megaport MCR (Cloud Router)** to route between the two VXCs if you need Layer 3 routing at the provider level. +>> +>>#### 4. Configure BGP +>> +>>You need BGP sessions on three segments: +>> +>>| Segment | Your side | Remote side | +>>|---|---|---| +>>| **AWS VIF** | AWS VPC (via VGW/TGW) | Provider or your router | +>>| **Provider bridge** | Handled by provider (if using MCR) | — | +>>| **OVHcloud Connect** | OVHcloud router | Your router or provider MCR | +>> +>>If using a provider MCR: +>>- The MCR peers with AWS via the VIF. +>>- The MCR peers with OVHcloud via OVHcloud Connect. +>>- Routes are exchanged automatically between the two peers. +>> +>>If **not** using a provider MCR: +>>- You need your own router (physical or virtual) co-located with the provider to handle BGP routing between AWS and OVHcloud. +>> +>>#### 5. Associate OVHcloud Connect with vRack +>> +>>See [Associate with vRack](../3.5_associate_vrack). +>> +>>#### 6. Test connectivity +>> +>>| Test | Details | +>>|---|---| +>>| **From AWS EC2 to OVHcloud** | `ping 172.16.1.10` from an EC2 instance | +>>| **From OVHcloud to AWS** | `ping 10.1.0.10` from an OVHcloud VM | +>>| **Traceroute** | Verify traffic stays on private paths (no internet hops) | +>>| **BGP routes** | Check that AWS VPC routes and OVHcloud routes appear in each other's routing tables | +>> +>>### Important considerations +>> +>>- **Routing domains:** Ensure there are no overlapping IP ranges between AWS VPCs and OVHcloud subnets. +>>- **Costs:** You will be billed by AWS (Direct Connect), the provider (VXC/MCR), and OVHcloud (Connect). Review all three pricing models. +>>- **Latency:** The total latency depends on the distance between the AWS region and OVHcloud region, plus any intermediate provider hops. +>> +> Azure +>>### Prerequisites +>> +>>- An **Azure subscription** with permissions to create ExpressRoute circuits +>>- An **OVHcloud account** with a vRack +>>- An account with a **shared provider** that supports both Azure ExpressRoute and OVHcloud Connect +>>- Non-overlapping IP ranges between Azure VNet and OVHcloud vRack +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> Azure +>> +>> ExpressRoute Circuit +>> VNet: 10.2.0.0/16 +>> Private Peering +>> +>> +>> +>> Provider +>> Megaport / Equinix +>> VXC or Fabric +>> Service Key ↔ Service Key +>> +>> +>> +>> OVHcloud PoP +>> OCC Provider +>> BGP peering +>> ASN varies by PoP +>> +>> +>> +>> vRack +>> 172.16.0.0/16 +>> Bare Metal +>> Hosted Private Cloud +>> Public Cloud +>> +>> +>> +>> +>> +>> +>> VXC +>> VXC +>> vRack +>> +>> +>> Azure ↔ Provider ↔ OVHcloud Connect ↔ vRack +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### When to use +>> +>>| Scenario | Recommendation | +>>|---|---| +>>| Migrate VMs from Azure to OVHcloud | ✅ Simple connection | +>>| Burst compute from Azure to OVHcloud | ✅ Simple connection | +>>| Production multi-cloud (high availability) | Use the [resilient tutorial](../4.2_resilient/4.4.2_azure_resilient) | +>>| DR between Azure and OVHcloud | Use the [resilient tutorial](../4.2_resilient/4.4.2_azure_resilient) | +>> +>>### Step-by-step +>> +>>#### 1. Create an Azure ExpressRoute circuit +>> +>>1. In the **Azure Portal** → **Create a resource** → **ExpressRoute**. +>>2. Select: +>> - **Provider**: Megaport or Equinix +>> - **Peering location**: Choose a location shared with your OVHcloud PoP +>> - **Bandwidth**: Match your OVHcloud Connect bandwidth (1 Gbps / 10 Gbps) +>>3. Complete the creation. Note the **Service Key** (a GUID). +>> +>>#### 2. Order your OVHcloud Connect Provider +>> +>>If not already done, [order an OVHcloud Connect Provider](../3.2_order_provider) at a PoP served by the same provider. +>> +>>Retrieve your **service key** from the OVHcloud Control Panel or API. +>> +>>#### 3. Create the provider bridge +>> +>>On the provider platform, create **two VXCs** (or equivalent connections): +>> +>>| VXC | Source | Destination | +>>|---|---|---| +>>| VXC 1 | Azure ExpressRoute (Service Key) | Provider MCR / Port | +>>| VXC 2 | Provider MCR / Port | OVHcloud Connect (Service Key) | +>> +>>If the provider supports it, an MCR (Cloud Router) acts as a transit point between Azure and OVHcloud. +>> +>>**Megaport example:** +>> +>>1. Create a **Megaport Cloud Router (MCR)** in the same metro. +>>2. Add VXC from MCR → Azure ExpressRoute using the Azure Service Key. +>>3. Add VXC from MCR → OVHcloud Connect using the OVHcloud service key. +>> +>>**Equinix Fabric example:** +>> +>>1. Create a connection from your Fabric port → Azure ExpressRoute using the Service Key. +>>2. Create a connection from your Fabric port → OVHcloud Connect using the service key. +>> +>>#### 4. Configure Azure Private Peering +>> +>>On the Azure ExpressRoute circuit: +>> +>>1. Go to **Peerings** → **Azure private**. +>>2. Configure: +>> - **Peer ASN**: Your MCR or provider ASN +>> - **Primary subnet**: A /30 for BGP (e.g., `169.254.100.0/30`) +>> - **Secondary subnet**: A /30 for BGP (e.g., `169.254.100.4/30`) +>> - **VLAN ID**: Provided by the provider +>> +>>#### 5. Configure OVHcloud BGP peering +>> +>>[Configure OCC L3 with BGP](../3.7_occ_l3_bgp) for the OVHcloud Connect service. +>> +>>Ensure the MCR or provider router advertises Azure prefixes (`10.2.0.0/16`) toward OVHcloud, and OVHcloud prefixes (`172.16.0.0/16`) toward Azure. +>> +>>#### 6. Associate your vRack +>> +>>[Associate the OVHcloud Connect service with your vRack](../3.5_associate_vrack). +>> +>>#### 7. Verify connectivity +>> +>>| Check | Command / Action | +>>|---|---| +>>| Azure circuit status | Azure Portal → ExpressRoute → Overview → **Provider status: Provisioned** | +>>| Azure BGP peering | Azure Portal → ExpressRoute → Peerings → **State: Enabled** | +>>| OVHcloud BGP status | OVHcloud API: `GET /ovhCloudConnect/{serviceName}` → `status: active` | +>>| Provider VXC status | Provider portal → VXC → **Active / Up** | +>>| End-to-end ping | From Azure VM → OVHcloud server private IP | +>> +>>### BGP route flow +>> +>>There are **three BGP segments** in this architecture: +>> +>>| Segment | Endpoints | ASNs | +>>|---|---|---| +>>| Azure ↔ Provider | Azure (ASN 12076) ↔ MCR/Provider ASN | 12076 ↔ Provider | +>>| Provider ↔ OVHcloud | MCR/Provider ASN ↔ OVHcloud BGP AS [TODO: per-PoP — 65501 EU / 65502 CA / 65519 Asia] | Provider ↔ [TODO: per-PoP] | +>>| OVHcloud ↔ vRack | Internal routing within OVHcloud | N/A | +>> +>> **Note:** Azure uses ASN **12076** for ExpressRoute Private Peering. +>> +>>### Troubleshooting +>> +>>| Symptom | Likely cause | Action | +>>|---|---|---| +>>| ExpressRoute circuit stuck in "Enabling" | Provider has not completed provisioning | Check provider portal; contact provider support | +>>| Azure private peering not established | Subnet or ASN mismatch | Verify /30 subnets and peer ASN match provider settings | +>>| OVHcloud BGP session down | Service key not activated or VLAN mismatch | Check OVHcloud API and provider VXC configuration | +>>| No route to Azure VNet | Missing route advertisement | Verify MCR forwards Azure prefixes toward OVHcloud | +>>| Asymmetric routing | Different paths for outbound/inbound | Ensure both sides prefer the same path; check BGP attributes | +>> +> GCP +>>### Prerequisites +>> +>>- A **GCP project** with the Compute Network Admin role +>>- A **GCP Cloud Router** created in the region nearest to the provider location +>>- An **OVHcloud account** with a vRack +>>- An account with a **shared provider** that supports both GCP Cross-Cloud Interconnect and OVHcloud Connect +>>- **Non-overlapping IP ranges** between GCP VPC and OVHcloud vRack +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> Google Cloud +>> +>> Interconnect +>> VPC: 10.3.0.0/16 +>> Cloud Router +>> +>> +>> +>> Provider +>> Megaport / Equinix +>> VXC or Fabric +>> Service Key bridge +>> +>> +>> +>> OVHcloud PoP +>> OCC Provider +>> BGP peering +>> ASN varies by PoP +>> +>> +>> +>> vRack +>> 172.16.0.0/16 +>> Bare Metal +>> Hosted Private Cloud +>> Public Cloud +>> +>> +>> +>> +>> +>> +>> VXC +>> VXC +>> vRack +>> +>> +>> GCP ↔ Provider ↔ OVHcloud Connect ↔ vRack +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### When to use +>> +>>| Scenario | Recommendation | +>>|---|---| +>>| Data transfer from GCP to OVHcloud | ✅ Simple connection | +>>| Hybrid AI/ML pipeline (GCP compute + OVHcloud storage) | ✅ Simple connection | +>>| Production multi-cloud with SLA requirements | Use the [resilient tutorial](../4.2_resilient) | +>>| Disaster recovery | Use the [resilient tutorial](../4.2_resilient) | +>> +>>### GCP Interconnect types +>> +>>GCP offers two main interconnect options: +>> +>>| Type | Description | Use when | +>>|---|---|---| +>>| **Dedicated Interconnect** | Direct physical connection to Google's network | You have a presence in a GCP colocation facility | +>>| **Partner Interconnect** | Connection through a supported service provider | You use Megaport, Equinix, or another GCP partner | +>> +>> **For this tutorial**, we use **Partner Interconnect** since the shared provider (Megaport or Equinix) acts as a bridge between GCP and OVHcloud. +>> +>>### Step-by-step +>> +>>#### 1. Create a GCP Cloud Router +>> +>>In the **GCP Console** → **Hybrid Connectivity** → **Cloud Routers** → **Create**: +>> +>>- **Name**: `router-ovhcloud` +>>- **Network**: Your VPC +>>- **Region**: Region closest to the provider PoP (e.g., `europe-west1` for Paris) +>>- **ASN**: Use a private ASN (e.g., `65001`) or Google's default (`16550`) +>> +>>#### 2. Create a Partner Interconnect VLAN attachment +>> +>>Go to **Hybrid Connectivity** → **Interconnect** → **VLAN attachments** → **Create**: +>> +>>1. Select **Partner Interconnect connection**. +>>2. Choose your Cloud Router. +>>3. Select the appropriate region and edge availability domain. +>>4. Set the **MTU** to 1500 (standard) or 1440 for VPN interworking. +>>5. Note the **pairing key** generated by GCP. +>> +>> **GCP pairing key format**: A string like `//` +>> +>>#### 3. Create the provider bridge +>> +>>On the provider platform, create connections to bridge GCP and OVHcloud: +>> +>>**Megaport example:** +>> +>>1. Create an **MCR** (Megaport Cloud Router) in a metro with both GCP and OVHcloud presence. +>>2. **VXC 1**: MCR → Google Cloud Partner Interconnect (use GCP pairing key). +>>3. **VXC 2**: MCR → OVHcloud Connect (use OVHcloud service key). +>> +>>**Equinix Fabric example:** +>> +>>1. Create a connection from your Fabric port → GCP Partner Interconnect (use GCP pairing key). +>>2. Create a connection from your Fabric port → OVHcloud Connect (use OVHcloud service key). +>> +>>#### 4. Activate the GCP VLAN attachment +>> +>>After the provider provisions the connection: +>> +>>1. Return to **GCP Console** → **VLAN attachments**. +>>2. The attachment should show **"Waiting for provider"** → then **"Pending customer"**. +>>3. Click **Activate** to enable the attachment. +>>4. GCP will automatically configure BGP between the Cloud Router and the provider. +>> +>>#### 5. Configure OVHcloud BGP peering +>> +>>[Configure OCC L3 with BGP](../3.7_occ_l3_bgp). +>> +>>Ensure the provider MCR: +>>- Advertises GCP VPC prefixes (`10.3.0.0/16`) toward OVHcloud (BGP AS [TODO: per-PoP — 65501 EU / 65502 CA / 65519 Asia]). +>>- Advertises OVHcloud prefixes (`172.16.0.0/16`) toward GCP Cloud Router. +>> +>>#### 6. Associate your vRack +>> +>>[Associate the OVHcloud Connect service with your vRack](../3.5_associate_vrack). +>> +>>#### 7. Verify connectivity +>> +>>| Check | How to verify | +>>|---|---| +>>| GCP VLAN attachment | GCP Console → VLAN attachments → **Status: Active** | +>>| GCP Cloud Router BGP | GCP Console → Cloud Routers → BGP peers → **Status: Established** | +>>| Provider VXC | Provider portal → VXC → **Active / Up** | +>>| OVHcloud BGP | OVHcloud API → service status = **active** | +>>| End-to-end | Ping from GCP VM → OVHcloud server private IP | +>> +>>### BGP route flow +>> +>>| Segment | Endpoints | ASNs | +>>|---|---|---| +>>| GCP ↔ Provider | Cloud Router (ASN 16550) ↔ MCR (Provider ASN) | 16550 ↔ Provider | +>>| Provider ↔ OVHcloud | MCR (Provider ASN) ↔ OVHcloud BGP AS [TODO: per-PoP — 65501 EU / 65502 CA / 65519 Asia] | Provider ↔ [TODO: per-PoP] | +>>| OVHcloud ↔ vRack | Internal OVHcloud routing | N/A | +>> +>> **Note:** GCP Cloud Router uses ASN **16550** by default. You can configure a custom ASN during Cloud Router creation. +>> +>>### Troubleshooting +>> +>>| Symptom | Likely cause | Action | +>>|---|---|---| +>>| VLAN attachment stuck in "Waiting for provider" | Provider VXC not yet provisioned | Check provider portal; ensure the GCP pairing key is correct | +>>| VLAN attachment in "Pending customer" | Not yet activated in GCP Console | Click **Activate** on the VLAN attachment | +>>| Cloud Router BGP not established | ASN mismatch or incorrect peering IPs | Verify Cloud Router ASN matches what the provider expects | +>>| No routes to GCP VPC | Missing route advertisement | Ensure Cloud Router advertises VPC subnets and MCR forwards them | +>>| OVHcloud BGP down | Service key not consumed or VLAN mismatch | Check OVHcloud service status and provider VXC config | + +### What's next? + +- [Resilient On-Prem architecture](../4.2_resilient) for high availability +- [Monitor your connection](../3.9_monitor) + +### Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/4.1_simple/guide.fr-fr.md b/pages/network/ovhcloud_connect/4.1_simple/guide.fr-fr.md new file mode 100644 index 00000000000..5ccc003b150 --- /dev/null +++ b/pages/network/ovhcloud_connect/4.1_simple/guide.fr-fr.md @@ -0,0 +1,708 @@ +--- +title: Mettre en place une architecture OVHcloud Connect simple +excerpt: Connectez un site on-premises unique, un WAN d'agences ou un environnement de cloud public (AWS, Azure, GCP) à OVHcloud via un seul lien OVHcloud Connect. +updated: 2026-02-18 +--- + +## Objectif + +Ce tutoriel vous guide dans la connexion d'un site on-premises unique à OVHcloud à l'aide d'**un seul lien OVHcloud Connect**. Il s'agit de l'architecture la plus simple, adaptée lorsque vous avez besoin d'une connectivité privée mais que vous pouvez accepter un chemin unique (sans redondance intégrée). + +## En pratique + +Vous trouverez ci-dessous les prérequis et les instructions pour cinq cas d'usage distincts, que vous pouvez choisir en fonction de l'architecture souhaitée. + +> [!tabs] +> On-Premises +>>### Prérequis +>> +>>- Un compte OVHcloud avec un vRack +>>- Un routeur dans un datacenter avec présence d'un PoP OVHcloud (pour Direct) ou un compte chez un fournisseur (pour Provider) +>>- Un équipement réseau compatible BGP +>>- Un plan d'adressage IP sans chevauchement entre votre réseau et les sous-réseaux OVHcloud +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> On-Premises +>> Votre datacenter +>> Routeur + BGP +>> 10.0.0.0/16 +>> +>> +>> +>> PoP +>> Cross-connect +>> Peering BGP +>> +>> +>> +>> OVHcloud +>> vRack +>> Serveurs / VM +>> 172.16.0.0/16 +>> +>> +>> +>> +>> 1 Gbps ou +>> 10 Gbps +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### Quand utiliser cette architecture +>> +>>| ✅ Idéal pour | ❌ Non recommandé pour | +>>|---|---| +>>| Environnements de développement et de test | Charges de production critiques pour l'activité | +>>| Charges de production non critiques | Environnements régulés ou à fortes exigences de conformité | +>>| Preuves de concept ou projets pilotes | Applications nécessitant une disponibilité de 99,99 % | +>>| Petites entreprises avec un site unique | Organisations multisites nécessitant une bascule | +>> +>>#### 1. Commander OVHcloud Connect +>> +>>Choisissez **Direct** ou **Provider** selon votre situation : +>> +>>- **Direct** — Vous disposez d'équipements dans le même datacenter qu'un PoP OVHcloud. Consultez [Commander Direct](../3.1_order_direct). +>>- **Provider** — Vous préférez une connexion managée. Consultez [Commander Provider](../3.2_order_provider). +>> +>>#### 2. Installer la connexion physique +>> +>>- **Direct :** fournissez la LOA à l'opérateur du datacenter pour installer un cross-connect. Consultez [LOA Cross-Connect](../3.11_cross_connect_loa). +>>- **Provider :** partagez la clé de service avec votre fournisseur et attendez l'activation. +>> +>>#### 3. Configurer BGP +>> +>>Mettez en place une session BGP unique entre votre routeur on-premises et OVHcloud : +>> +>>- Annoncez vos préfixes on-premises (par exemple `10.0.0.0/16`) à OVHcloud. +>>- Acceptez les préfixes OVHcloud (par exemple `172.16.0.0/16`) provenant d'OVHcloud. +>> +>>Consultez [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp) pour obtenir des instructions détaillées et des exemples de configuration. +>> +>>#### 4. Associer au vRack +>> +>>Reliez votre service OVHcloud Connect à votre vRack. Consultez [Associer au vRack](../3.5_associate_vrack). +>> +>>#### 5. Configurer les sous-réseaux d'AZ +>> +>>Définissez les sous-réseaux privés dans OVHcloud que votre réseau on-premises doit atteindre. Consultez [Configurer votre réseau vRack](../3.6_vrack_network_setup). +>> +>>#### 6. Tester la connectivité +>> +>>| Test | Commande | +>>|---|---| +>>| Ping depuis l'on-prem vers une VM OVHcloud | `ping 172.16.1.10` | +>>| Ping depuis une VM OVHcloud vers l'on-prem | `ping 10.0.0.1` | +>>| Traceroute | `traceroute 172.16.1.10` (ne doit pas passer par Internet) | +>>| Vérification BGP | `show ip bgp summary` | +>> +>>#### 7. Mettre en place la supervision +>> +>>Configurez des alertes de supervision pour le statut du lien, la session BGP et la bande passante. Consultez [Superviser](../3.9_monitor). +>> +>>### Limites d'une connexion simple +>> +>>- **Point unique de défaillance** — Si le lien, le PoP ou le cross-connect tombe en panne, la connectivité est perdue. +>>- **Pas de bascule automatique** — Vous devez intervenir manuellement ou compter sur un secours via Internet. +>>- **SLA plus faible** — Une connexion unique prend généralement en charge un SLA jusqu'à 99,9 % (consultez [SLA](../1.7_slas)). +>> +>>**Recommandation :** pour les charges de production, envisagez de passer à une [architecture résiliente](../4.2_resilient). +>> +> WAN +>>### Prérequis +>> +>>- Un compte OVHcloud avec un vRack +>>- Un routeur dans un datacenter avec présence d'un PoP OVHcloud (pour Direct) ou un compte chez un fournisseur (pour Provider) +>>- Un équipement réseau compatible BGP +>>- Un plan d'adressage IP sans chevauchement entre votre réseau et les sous-réseaux OVHcloud +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> Agences +>> Agence A +>> Agence B +>> Agence C +>> 10.x.x.x/16 +>> +>> +>> +>> WAN / SD-WAN +>> Backbone MPLS +>> ou fabric SD-WAN +>> +>> +>> +>> PoP +>> Session BGP +>> VLAN +>> +>> +>> +>> OVHcloud +>> vRack · Serveurs · VM +>> 172.16.0.0/16 +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### Différences par rapport à l'on-premises +>> +>>Dans un scénario WAN, votre trafic provient généralement de **plusieurs agences** ou sites et est agrégé via un backbone WAN (MPLS ou SD-WAN) avant d'atteindre le PoP OVHcloud. L'équipement de bordure WAN (routeur ou passerelle SD-WAN) est l'équipement qui établit le peering avec OVHcloud via BGP. +>> +>>### Quand utiliser cette architecture +>> +>>| ✅ Idéal pour | ❌ Non recommandé pour | +>>|---|---| +>>| Connecter plusieurs agences à OVHcloud via une sortie WAN unique | Charges critiques nécessitant une disponibilité de 99,99 % | +>>| Consolidation d'agences vers un environnement cloud | Configurations multicloud nécessitant des chemins diversifiés | +>>| Déploiements SD-WAN hybrides | Environnements fortement régulés | +>> +>>### Étape par étape +>> +>>#### 1. Coordonner avec votre fournisseur WAN +>> +>>Contactez votre fournisseur WAN/MPLS/SD-WAN et demandez : +>> +>>- Un **circuit** ou une **connexion virtuelle** depuis votre backbone WAN vers le PoP OVHcloud. +>>- Le circuit doit se terminer dans un site où OVHcloud dispose d'un PoP (consultez [Emplacements des PoP](../1.4_pop_locations_regions)). +>> +>>Si votre fournisseur WAN est également un fournisseur OVHcloud Connect (par exemple Megaport, Equinix), il peut gérer à la fois la livraison WAN et le provisionnement OVHcloud Connect. +>> +>>#### 2. Commander OVHcloud Connect +>> +>>- **Direct :** si votre routeur de bordure WAN est colocalisé avec le PoP OVHcloud. Consultez [Commander Direct](../3.1_order_direct). +>>- **Provider :** si la connexion est gérée par un fournisseur. Consultez [Commander Provider](../3.2_order_provider). +>> +>>#### 3. Configurer BGP sur la bordure WAN +>> +>>Mettez en place une session BGP entre votre **équipement de bordure WAN** et OVHcloud : +>> +>>- Annoncez les préfixes agrégés des agences (par exemple `10.0.0.0/8` ou des sous-réseaux plus spécifiques par agence). +>>- Acceptez les routes OVHcloud. +>>- Assurez-vous que votre routage WAN propage les routes OVHcloud vers toutes les agences. +>> +>>Consultez [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp). +>> +>>#### 4. Associer au vRack et configurer les sous-réseaux +>> +>>Reliez la connexion à votre vRack et configurez les sous-réseaux requis. Consultez [Associer au vRack](../3.5_associate_vrack) et [Configurer votre réseau vRack](../3.6_vrack_network_setup). +>> +>>#### 5. Tester la connectivité de bout en bout +>> +>>Depuis une agence, vérifiez que vous pouvez atteindre les ressources OVHcloud : +>> +>>``` +>>ping 172.16.1.10 ## Ping d'une VM OVHcloud +>>traceroute 172.16.1.10 ## Doit passer : agence → WAN → PoP → OVHcloud (privé) +>>``` +>> +>>Vérifiez depuis OVHcloud vers une agence : +>> +>>```bash +>>ping 10.1.0.1 ## Ping d'une IP d'agence depuis une VM OVHcloud +>>``` +>> +>>#### 6. Mettre en place la supervision +>> +>>Supervisez la session BGP de bordure WAN et le lien OVHcloud Connect. Consultez [Superviser](../3.9_monitor). +>> +> AWS +>>### Prérequis +>> +>>- Un **compte AWS** avec un VPC configuré +>>- Un **compte OVHcloud** avec un vRack +>>- Un compte chez un **fournisseur partagé** prenant en charge à la fois AWS Direct Connect et OVHcloud Connect +>>- Des plages IP non chevauchantes entre le VPC AWS et les sous-réseaux OVHcloud +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> AWS +>> VPC : 10.1.0.0/16 +>> Direct Connect +>> Virtual Interface (VIF) +>> +>> +>> +>> Fournisseur d'interconnexion +>> Megaport / Equinix Fabric +>> Pont AWS ↔ OVHcloud +>> +>> +>> +>> OVHcloud +>> vRack : 172.16.0.0/16 +>> OVHcloud Connect +>> Serveurs / VM +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### Fonctionnement +>> +>>La connexion entre AWS et OVHcloud est généralement routée via un **fournisseur partagé** (tel que Megaport ou Equinix Fabric) qui dispose d'une présence physique à la fois sur les sites AWS Direct Connect et sur les PoP OVHcloud. +>> +>>1. **Côté AWS**, vous créez une connexion Direct Connect (ou une connexion hébergée) et une Virtual Interface (VIF) qui relie votre VPC AWS. +>>2. **Côté fournisseur**, vous créez un cross-connect virtuel (VXC) qui ponte la VIF AWS vers le service OVHcloud Connect. +>>3. **Côté OVHcloud**, vous configurez BGP et associez la connexion à votre vRack. +>> +>>### Étape par étape +>> +>>#### 1. Configurer AWS Direct Connect +>> +>>1. Dans la **console AWS**, accédez à **Direct Connect** → **Connections**. +>>2. Créez une nouvelle connexion (ou utilisez une connexion hébergée via votre fournisseur). +>>3. Sélectionnez l'**emplacement AWS Direct Connect** le plus proche de votre PoP OVHcloud. +>>4. Créez une **Private Virtual Interface (VIF)** associée à votre VPC ou à votre Virtual Private Gateway. +>>5. Notez l'ASN BGP, les IP de peer et l'identifiant VLAN. +>> +>> Pour plus d'informations, consultez la [documentation AWS Direct Connect](https://docs.aws.amazon.com/directconnect/). +>> +>>#### 2. Commander OVHcloud Connect Provider +>> +>>1. Dans l'**espace client OVHcloud**, commandez OVHcloud Connect Provider. +>>2. Sélectionnez le même fournisseur que celui que vous utilisez pour AWS (par exemple Megaport). +>>3. Choisissez l'emplacement du PoP. +>>4. Copiez la **clé de service**. +>> +>>Consultez [Commander OVHcloud Connect Provider](../3.2_order_provider). +>> +>>#### 3. Créer le pont chez le fournisseur +>> +>>Dans le portail de votre fournisseur, créez les connexions qui pontent AWS et OVHcloud : +>> +>>**Exemple avec Megaport :** +>> +>>1. Créez un **port Megaport** ou utilisez-en un existant. +>>2. Créez une **VXC vers AWS** en utilisant les détails de la connexion hébergée AWS Direct Connect. +>>3. Créez une **VXC vers OVHcloud** en utilisant la clé de service OVHcloud. +>>4. En option, utilisez un **Megaport MCR (Cloud Router)** pour router entre les deux VXC si vous avez besoin de routage de couche 3 au niveau du fournisseur. +>> +>>#### 4. Configurer BGP +>> +>>Vous avez besoin de sessions BGP sur trois segments : +>> +>>| Segment | Votre côté | Côté distant | +>>|---|---|---| +>>| **VIF AWS** | VPC AWS (via VGW/TGW) | Fournisseur ou votre routeur | +>>| **Pont fournisseur** | Géré par le fournisseur (avec MCR) | — | +>>| **OVHcloud Connect** | Routeur OVHcloud | Votre routeur ou MCR du fournisseur | +>> +>>Avec un MCR du fournisseur : +>>- Le MCR établit le peering avec AWS via la VIF. +>>- Le MCR établit le peering avec OVHcloud via OVHcloud Connect. +>>- Les routes sont échangées automatiquement entre les deux peers. +>> +>>**Sans** MCR du fournisseur : +>>- Vous avez besoin de votre propre routeur (physique ou virtuel) colocalisé avec le fournisseur pour gérer le routage BGP entre AWS et OVHcloud. +>> +>>#### 5. Associer OVHcloud Connect au vRack +>> +>>Consultez [Associer au vRack](../3.5_associate_vrack). +>> +>>#### 6. Tester la connectivité +>> +>>| Test | Détails | +>>|---|---| +>>| **Depuis AWS EC2 vers OVHcloud** | `ping 172.16.1.10` depuis une instance EC2 | +>>| **Depuis OVHcloud vers AWS** | `ping 10.1.0.10` depuis une VM OVHcloud | +>>| **Traceroute** | Vérifiez que le trafic reste sur des chemins privés (pas de sauts Internet) | +>>| **Routes BGP** | Vérifiez que les routes du VPC AWS et les routes OVHcloud apparaissent dans les tables de routage de chacun | +>> +>>### Considérations importantes +>> +>>- **Domaines de routage :** assurez-vous qu'il n'y a pas de chevauchement de plages IP entre les VPC AWS et les sous-réseaux OVHcloud. +>>- **Coûts :** vous serez facturé par AWS (Direct Connect), par le fournisseur (VXC/MCR) et par OVHcloud (Connect). Consultez les trois modèles tarifaires. +>>- **Latence :** la latence totale dépend de la distance entre la région AWS et la région OVHcloud, ainsi que des sauts intermédiaires éventuels chez le fournisseur. +>> +> Azure +>>### Prérequis +>> +>>- Un **abonnement Azure** avec les autorisations nécessaires pour créer des circuits ExpressRoute +>>- Un **compte OVHcloud** avec un vRack +>>- Un compte chez un **fournisseur partagé** prenant en charge à la fois Azure ExpressRoute et OVHcloud Connect +>>- Des plages IP non chevauchantes entre le VNet Azure et le vRack OVHcloud +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> Azure +>> +>> Circuit ExpressRoute +>> VNet : 10.2.0.0/16 +>> Private Peering +>> +>> +>> +>> Fournisseur +>> Megaport / Equinix +>> VXC ou Fabric +>> Clé de service ↔ Clé de service +>> +>> +>> +>> PoP OVHcloud +>> OCC Provider +>> Peering BGP +>> ASN variable selon le PoP +>> +>> +>> +>> vRack +>> 172.16.0.0/16 +>> Bare Metal +>> Hosted Private Cloud +>> Public Cloud +>> +>> +>> +>> +>> +>> +>> VXC +>> VXC +>> vRack +>> +>> +>> Azure ↔ Fournisseur ↔ OVHcloud Connect ↔ vRack +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### Quand l'utiliser +>> +>>| Scénario | Recommandation | +>>|---|---| +>>| Migrer des VM depuis Azure vers OVHcloud | ✅ Connexion simple | +>>| Burst de calcul depuis Azure vers OVHcloud | ✅ Connexion simple | +>>| Multicloud de production (haute disponibilité) | Utilisez le [tutoriel résilient](../4.2_resilient/4.4.2_azure_resilient) | +>>| PRA entre Azure et OVHcloud | Utilisez le [tutoriel résilient](../4.2_resilient/4.4.2_azure_resilient) | +>> +>>### Étape par étape +>> +>>#### 1. Créer un circuit Azure ExpressRoute +>> +>>1. Dans le **portail Azure** → **Créer une ressource** → **ExpressRoute**. +>>2. Sélectionnez : +>> - **Provider** : Megaport ou Equinix +>> - **Peering location** : choisissez un emplacement partagé avec votre PoP OVHcloud +>> - **Bandwidth** : faites correspondre la bande passante de votre OVHcloud Connect (1 Gbps / 10 Gbps) +>>3. Finalisez la création. Notez la **clé de service** (un GUID). +>> +>>#### 2. Commander votre OVHcloud Connect Provider +>> +>>Si ce n'est pas déjà fait, [commandez un OVHcloud Connect Provider](../3.2_order_provider) sur un PoP desservi par le même fournisseur. +>> +>>Récupérez votre **clé de service** depuis l'espace client OVHcloud ou via l'API. +>> +>>#### 3. Créer le pont chez le fournisseur +>> +>>Sur la plateforme du fournisseur, créez **deux VXC** (ou connexions équivalentes) : +>> +>>| VXC | Source | Destination | +>>|---|---|---| +>>| VXC 1 | Azure ExpressRoute (clé de service) | MCR / Port du fournisseur | +>>| VXC 2 | MCR / Port du fournisseur | OVHcloud Connect (clé de service) | +>> +>>Si le fournisseur le prend en charge, un MCR (Cloud Router) joue le rôle de point de transit entre Azure et OVHcloud. +>> +>>**Exemple Megaport :** +>> +>>1. Créez un **Megaport Cloud Router (MCR)** dans la même métropole. +>>2. Ajoutez une VXC depuis le MCR → Azure ExpressRoute en utilisant la clé de service Azure. +>>3. Ajoutez une VXC depuis le MCR → OVHcloud Connect en utilisant la clé de service OVHcloud. +>> +>>**Exemple Equinix Fabric :** +>> +>>1. Créez une connexion depuis votre port Fabric → Azure ExpressRoute en utilisant la clé de service. +>>2. Créez une connexion depuis votre port Fabric → OVHcloud Connect en utilisant la clé de service. +>> +>>#### 4. Configurer Azure Private Peering +>> +>>Sur le circuit Azure ExpressRoute : +>> +>>1. Allez dans **Peerings** → **Azure private**. +>>2. Configurez : +>> - **Peer ASN** : l'ASN de votre MCR ou de votre fournisseur +>> - **Primary subnet** : un /30 pour BGP (par exemple `169.254.100.0/30`) +>> - **Secondary subnet** : un /30 pour BGP (par exemple `169.254.100.4/30`) +>> - **VLAN ID** : fourni par le fournisseur +>> +>>#### 5. Configurer le peering BGP OVHcloud +>> +>>[Configurez OCC L3 avec BGP](../3.7_occ_l3_bgp) pour le service OVHcloud Connect. +>> +>>Assurez-vous que le MCR ou le routeur du fournisseur annonce les préfixes Azure (`10.2.0.0/16`) vers OVHcloud, et les préfixes OVHcloud (`172.16.0.0/16`) vers Azure. +>> +>>#### 6. Associer votre vRack +>> +>>[Associez le service OVHcloud Connect à votre vRack](../3.5_associate_vrack). +>> +>>#### 7. Vérifier la connectivité +>> +>>| Vérification | Commande / Action | +>>|---|---| +>>| Statut du circuit Azure | Portail Azure → ExpressRoute → Overview → **Provider status: Provisioned** | +>>| Peering BGP Azure | Portail Azure → ExpressRoute → Peerings → **State: Enabled** | +>>| Statut BGP OVHcloud | API OVHcloud : `GET /ovhCloudConnect/{serviceName}` → `status: active` | +>>| Statut VXC fournisseur | Portail fournisseur → VXC → **Active / Up** | +>>| Ping de bout en bout | Depuis une VM Azure → IP privée d'un serveur OVHcloud | +>> +>>### Flux de routage BGP +>> +>>Cette architecture comporte **trois segments BGP** : +>> +>>| Segment | Extrémités | ASN | +>>|---|---|---| +>>| Azure ↔ Fournisseur | Azure (ASN 12076) ↔ ASN du MCR/fournisseur | 12076 ↔ Fournisseur | +>>| Fournisseur ↔ OVHcloud | ASN du MCR/fournisseur ↔ AS BGP OVHcloud [TODO: par PoP — 65501 EU / 65502 CA / 65519 Asia] | Fournisseur ↔ [TODO: par PoP] | +>>| OVHcloud ↔ vRack | Routage interne au sein d'OVHcloud | N/A | +>> +>> **Note :** Azure utilise l'ASN **12076** pour le Private Peering ExpressRoute. +>> +>>### Dépannage +>> +>>| Symptôme | Cause probable | Action | +>>|---|---|---| +>>| Circuit ExpressRoute bloqué dans « Enabling » | Le fournisseur n'a pas finalisé le provisionnement | Consultez le portail du fournisseur ; contactez son support | +>>| Le peering privé Azure n'est pas établi | Discordance de sous-réseau ou d'ASN | Vérifiez que les sous-réseaux /30 et l'ASN du peer correspondent aux paramètres du fournisseur | +>>| Session BGP OVHcloud en panne | Clé de service non activée ou discordance de VLAN | Vérifiez l'API OVHcloud et la configuration VXC du fournisseur | +>>| Pas de route vers le VNet Azure | Annonce de route manquante | Vérifiez que le MCR transmet les préfixes Azure vers OVHcloud | +>>| Routage asymétrique | Chemins différents pour le sortant/entrant | Assurez-vous que les deux côtés préfèrent le même chemin ; vérifiez les attributs BGP | +>> +> GCP +>>### Prérequis +>> +>>- Un **projet GCP** avec le rôle Compute Network Admin +>>- Un **GCP Cloud Router** créé dans la région la plus proche de l'emplacement du fournisseur +>>- Un **compte OVHcloud** avec un vRack +>>- Un compte chez un **fournisseur partagé** prenant en charge à la fois GCP Cross-Cloud Interconnect et OVHcloud Connect +>>- Des **plages IP non chevauchantes** entre le VPC GCP et le vRack OVHcloud +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> Google Cloud +>> +>> Interconnect +>> VPC : 10.3.0.0/16 +>> Cloud Router +>> +>> +>> +>> Fournisseur +>> Megaport / Equinix +>> VXC ou Fabric +>> Pont par clé de service +>> +>> +>> +>> PoP OVHcloud +>> OCC Provider +>> Peering BGP +>> ASN variable selon le PoP +>> +>> +>> +>> vRack +>> 172.16.0.0/16 +>> Bare Metal +>> Hosted Private Cloud +>> Public Cloud +>> +>> +>> +>> +>> +>> +>> VXC +>> VXC +>> vRack +>> +>> +>> GCP ↔ Fournisseur ↔ OVHcloud Connect ↔ vRack +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### Quand l'utiliser +>> +>>| Scénario | Recommandation | +>>|---|---| +>>| Transfert de données depuis GCP vers OVHcloud | ✅ Connexion simple | +>>| Pipeline IA/ML hybride (compute GCP + stockage OVHcloud) | ✅ Connexion simple | +>>| Multicloud de production avec exigences de SLA | Utilisez le [tutoriel résilient](../4.2_resilient) | +>>| Reprise d'activité après sinistre | Utilisez le [tutoriel résilient](../4.2_resilient) | +>> +>>### Types d'Interconnect GCP +>> +>>GCP propose deux principales options d'interconnect : +>> +>>| Type | Description | À utiliser quand | +>>|---|---|---| +>>| **Dedicated Interconnect** | Connexion physique directe au réseau de Google | Vous disposez d'une présence dans un site de colocation GCP | +>>| **Partner Interconnect** | Connexion via un fournisseur de services pris en charge | Vous utilisez Megaport, Equinix ou un autre partenaire GCP | +>> +>> **Pour ce tutoriel**, nous utilisons **Partner Interconnect** car le fournisseur partagé (Megaport ou Equinix) joue le rôle de pont entre GCP et OVHcloud. +>> +>>### Étape par étape +>> +>>#### 1. Créer un GCP Cloud Router +>> +>>Dans la **console GCP** → **Hybrid Connectivity** → **Cloud Routers** → **Create** : +>> +>>- **Name** : `router-ovhcloud` +>>- **Network** : votre VPC +>>- **Region** : la région la plus proche du PoP du fournisseur (par exemple `europe-west1` pour Paris) +>>- **ASN** : utilisez un ASN privé (par exemple `65001`) ou la valeur par défaut de Google (`16550`) +>> +>>#### 2. Créer une VLAN attachment Partner Interconnect +>> +>>Allez dans **Hybrid Connectivity** → **Interconnect** → **VLAN attachments** → **Create** : +>> +>>1. Sélectionnez **Partner Interconnect connection**. +>>2. Choisissez votre Cloud Router. +>>3. Sélectionnez la région et le edge availability domain appropriés. +>>4. Définissez la **MTU** à 1500 (standard) ou à 1440 pour l'interopérabilité VPN. +>>5. Notez la **pairing key** générée par GCP. +>> +>> **Format de la pairing key GCP** : une chaîne de la forme `//` +>> +>>#### 3. Créer le pont chez le fournisseur +>> +>>Sur la plateforme du fournisseur, créez les connexions qui pontent GCP et OVHcloud : +>> +>>**Exemple Megaport :** +>> +>>1. Créez un **MCR** (Megaport Cloud Router) dans une métropole avec présence GCP et OVHcloud. +>>2. **VXC 1** : MCR → Google Cloud Partner Interconnect (utilisez la pairing key GCP). +>>3. **VXC 2** : MCR → OVHcloud Connect (utilisez la clé de service OVHcloud). +>> +>>**Exemple Equinix Fabric :** +>> +>>1. Créez une connexion depuis votre port Fabric → GCP Partner Interconnect (utilisez la pairing key GCP). +>>2. Créez une connexion depuis votre port Fabric → OVHcloud Connect (utilisez la clé de service OVHcloud). +>> +>>#### 4. Activer la VLAN attachment GCP +>> +>>Une fois que le fournisseur a provisionné la connexion : +>> +>>1. Retournez dans la **console GCP** → **VLAN attachments**. +>>2. L'attachement doit afficher **« Waiting for provider »** puis **« Pending customer »**. +>>3. Cliquez sur **Activate** pour activer l'attachement. +>>4. GCP configurera automatiquement BGP entre le Cloud Router et le fournisseur. +>> +>>#### 5. Configurer le peering BGP OVHcloud +>> +>>[Configurez OCC L3 avec BGP](../3.7_occ_l3_bgp). +>> +>>Assurez-vous que le MCR du fournisseur : +>>- Annonce les préfixes du VPC GCP (`10.3.0.0/16`) vers OVHcloud (AS BGP [TODO: par PoP — 65501 EU / 65502 CA / 65519 Asia]). +>>- Annonce les préfixes OVHcloud (`172.16.0.0/16`) vers le GCP Cloud Router. +>> +>>#### 6. Associer votre vRack +>> +>>[Associez le service OVHcloud Connect à votre vRack](../3.5_associate_vrack). +>> +>>#### 7. Vérifier la connectivité +>> +>>| Vérification | Comment vérifier | +>>|---|---| +>>| VLAN attachment GCP | Console GCP → VLAN attachments → **Status: Active** | +>>| BGP du Cloud Router GCP | Console GCP → Cloud Routers → BGP peers → **Status: Established** | +>>| VXC fournisseur | Portail fournisseur → VXC → **Active / Up** | +>>| BGP OVHcloud | API OVHcloud → statut du service = **active** | +>>| De bout en bout | Ping depuis une VM GCP → IP privée d'un serveur OVHcloud | +>> +>>### Flux de routage BGP +>> +>>| Segment | Extrémités | ASN | +>>|---|---|---| +>>| GCP ↔ Fournisseur | Cloud Router (ASN 16550) ↔ MCR (ASN du fournisseur) | 16550 ↔ Fournisseur | +>>| Fournisseur ↔ OVHcloud | MCR (ASN du fournisseur) ↔ AS BGP OVHcloud [TODO: par PoP — 65501 EU / 65502 CA / 65519 Asia] | Fournisseur ↔ [TODO: par PoP] | +>>| OVHcloud ↔ vRack | Routage interne OVHcloud | N/A | +>> +>> **Note :** le GCP Cloud Router utilise l'ASN **16550** par défaut. Vous pouvez configurer un ASN personnalisé lors de la création du Cloud Router. +>> +>>### Dépannage +>> +>>| Symptôme | Cause probable | Action | +>>|---|---|---| +>>| VLAN attachment bloqué dans « Waiting for provider » | VXC du fournisseur pas encore provisionnée | Consultez le portail du fournisseur ; vérifiez que la pairing key GCP est correcte | +>>| VLAN attachment dans « Pending customer » | Pas encore activé dans la console GCP | Cliquez sur **Activate** sur la VLAN attachment | +>>| BGP du Cloud Router non établi | Discordance d'ASN ou d'IP de peering | Vérifiez que l'ASN du Cloud Router correspond à ce que le fournisseur attend | +>>| Pas de routes vers le VPC GCP | Annonce de route manquante | Assurez-vous que le Cloud Router annonce les sous-réseaux du VPC et que le MCR les transmet | +>>| BGP OVHcloud en panne | Clé de service non consommée ou discordance de VLAN | Vérifiez le statut du service OVHcloud et la configuration de la VXC du fournisseur | + +### Et ensuite ? + +- [Architecture On-Prem résiliente](../4.2_resilient) pour la haute disponibilité +- [Superviser votre connexion](../3.9_monitor) + +### Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/4.1_simple/meta.yaml b/pages/network/ovhcloud_connect/4.1_simple/meta.yaml new file mode 100644 index 00000000000..fb523d73fc6 --- /dev/null +++ b/pages/network/ovhcloud_connect/4.1_simple/meta.yaml @@ -0,0 +1,2 @@ +id: 1999b15e-28f2-4719-a256-6a142515b85c +full_slug: network-ovhcloud-connect-simple-architecture diff --git a/pages/network/ovhcloud_connect/4.2_resilient/guide.en-gb.md b/pages/network/ovhcloud_connect/4.2_resilient/guide.en-gb.md new file mode 100644 index 00000000000..a5376d02675 --- /dev/null +++ b/pages/network/ovhcloud_connect/4.2_resilient/guide.en-gb.md @@ -0,0 +1,816 @@ +--- +title: Set up a resilient OVHcloud Connect architecture +excerpt: Connect your infrastructure to OVHcloud through two redundant OVHcloud Connect links for high availability and automatic failover. +updated: 2026-02-18 +--- + +## Objective + +This tutorial guides you through connecting your infrastructure to OVHcloud using **two independent OVHcloud Connect links** for high availability. If one link fails, traffic automatically switches to the other. + +## Instructions + +Below, you will find prerequisites and instructions for five separate use-cases, which you may choose depending on desired architecture. + +> [!tabs] +> On-Premises +>>### Prerequisites +>> +>>- Two OVHcloud Connect services (Direct, Provider, or a mix) terminating at **different PoPs** +>>- A router (or two routers) capable of running **multiple BGP sessions** with failover +>>- An IP plan covering **two AZs** in OVHcloud +>>- A vRack with resources in both AZs +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> On-Premises +>> Router 1 +>> (or dual-homed router) +>> ASN: 65001 +>> 10.0.0.0/16 +>> +>> +>> +>> PoP A +>> Primary link +>> +>> +>> +>> PoP B +>> Backup link +>> +>> +>> +>> OVHcloud AZ 1 +>> vRack · Servers · VMs +>> 172.16.1.0/24 +>> +>> +>> +>> OVHcloud AZ 2 +>> vRack · Servers · VMs +>> 172.16.2.0/24 +>> +>> +>> +>> +>> +>> +>> +>> +>> Primary +>> Backup +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### When to use this architecture +>> +>>| ✅ Recommended for | Details | +>>|---|---| +>>| Business-critical production | Workloads that cannot tolerate downtime | +>>| Regulated environments | Compliance frameworks requiring high availability | +>>| SLA requirements ≥ 99.99% | Multi-path architecture needed for premium SLA | +>>| Disaster recovery | Automatic failover without manual intervention | +>> +>>#### 1. Order two OVHcloud Connect links +>> +>>Order two separate OVHcloud Connect services at **different PoPs** for physical diversity: +>> +>>- **Link 1 (Primary):** Order at PoP A — See [Order Direct](../3.1_order_direct) or [Order Provider](../3.2_order_provider). +>>- **Link 2 (Backup):** Order at PoP B — Same process, different PoP. +>> +>>> **Diversity tip:** Use different data centres or at minimum different physical paths to avoid a shared failure point. +>> +>>#### 2. Install both physical connections +>> +>>For each link: +>>- **Direct:** Install cross-connects at each PoP. See [Cross Connect LOA](../3.11_cross_connect_loa). +>>- **Provider:** Share the respective pairing keys with your provider(s). +>> +>>#### 3. Configure BGP with failover +>> +>>Set up **two BGP sessions** — one per link — with routing policies that define which path is preferred. +>> +>>##### Active/Standby example (Cisco IOS) +>> +>>``` +>>router bgp 65001 +>> ! Primary link via PoP A +>> neighbor 192.0.2.1 remote-as 35540 +>> neighbor 192.0.2.1 description OVHcloud-Primary +>> neighbor 192.0.2.1 route-map PRIMARY-IN in +>> neighbor 192.0.2.1 route-map PRIMARY-OUT out +>> +>> ! Backup link via PoP B +>> neighbor 198.51.100.1 remote-as 35540 +>> neighbor 198.51.100.1 description OVHcloud-Backup +>> neighbor 198.51.100.1 route-map BACKUP-IN in +>> neighbor 198.51.100.1 route-map BACKUP-OUT out +>> +>>! Prefer primary path using Local Preference +>>route-map PRIMARY-IN permit 10 +>> set local-preference 200 +>> +>>route-map BACKUP-IN permit 10 +>> set local-preference 100 +>> +>>! Influence OVHcloud's return traffic using AS-path prepending on backup +>>route-map PRIMARY-OUT permit 10 +>> +>>route-map BACKUP-OUT permit 10 +>> set as-path prepend 65001 65001 +>>``` +>> +>>##### Key BGP attributes for failover +>> +>>| Attribute | Effect | Use case | +>>|---|---|---| +>>| **Local Preference** | Controls outbound path preference (higher = preferred) | Make primary path preferred for traffic leaving your network | +>>| **AS-path prepending** | Makes a path look longer (less preferred) | Influence OVHcloud's choice of return path | +>>| **MED** | Suggests preference to the remote side | May not be honoured in all OVHcloud configurations | +>> +>>#### 4. Associate both links with your vRack +>> +>>Associate both OVHcloud Connect services with the **same vRack**. See [Associate with vRack](../3.5_associate_vrack). +>> +>>#### 5. Configure subnets in both AZs +>> +>>Set up private subnets in both Availability Zones. See [Set up your vRack network](../3.6_vrack_network_setup). +>> +>>#### 6. Test failover +>> +>>**This is critical.** Do not skip failover testing. +>> +>>1. **Verify normal operation:** +>> - Both BGP sessions are Established. +>> - Traffic flows through the primary link. +>> +>>2. **Simulate primary failure:** +>> - Shut down the primary BGP session or physically disconnect the primary link. +>> - Verify traffic switches to the backup link within the BGP convergence time (typically 30–90 seconds; can be faster with BFD). +>> - Confirm no packet loss beyond the convergence window. +>> +>>3. **Restore primary:** +>> - Bring the primary link back up. +>> - Verify traffic returns to the primary path. +>> +>>4. **Test the reverse:** +>> - Simulate failure of the backup link while the primary is up. This confirms both links work independently. +>> +>>#### 7. Set up monitoring +>> +>>Monitor **both links** independently. Set alerts for: +>>- BGP session drops on either link +>>- Traffic imbalance (all traffic on one link may indicate a failure on the other) +>>- Bandwidth approaching capacity on either link +>> +>>See [Monitor](../3.9_monitor). +>> +>>### Advanced: Active/Active configuration +>> +>>For maximum throughput and faster failover, you can run both links in **Active/Active** mode: +>> +>>- Set **equal Local Preference** on both paths. +>>- Use **ECMP (Equal-Cost Multi-Path)** if supported. +>>- Traffic is load-balanced across both links. +>>- If one link fails, all traffic immediately flows through the surviving link. +>> +>>> Active/Active provides higher aggregate bandwidth but requires careful capacity planning — each link must be able to handle the full traffic load alone during a failure. +>> +> WAN +>>### Prerequisites +>> +>>- An OVHcloud account with a vRack +>>- Two OVHcloud Connect services (Direct, Provider, or a mix) terminating at **different PoPs** +>>- A WAN backbone (MPLS or SD-WAN) with circuits reaching both PoPs +>>- BGP-capable WAN edge devices +>>- An IP addressing plan with no overlaps between your WAN and OVHcloud subnets +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> Branches +>> Office A +>> Office B +>> Office C +>> +>> +>> +>> WAN +>> SD-WAN / +>> MPLS +>> +>> +>> +>> PoP A +>> Primary +>> +>> +>> +>> PoP B +>> Backup +>> +>> +>> +>> OVHcloud AZ 1 +>> vRack · Servers · 172.16.1.0/24 +>> +>> +>> +>> OVHcloud AZ 2 +>> vRack · Servers · 172.16.2.0/24 +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### When to use this architecture +>> +>>- **Business-critical WAN connectivity** — Multiple branches depend on OVHcloud access. +>>- **SLA requirements ≥ 99.99%** — Dual links needed for premium uptime guarantees. +>>- **SD-WAN with diverse paths** — SD-WAN platforms can automatically route over the best available path. +>> +>>### Step-by-step +>> +>>#### 1. Order two OVHcloud Connect links +>> +>>Order at **different PoPs** for physical diversity. You can mix Direct and Provider connections. +>> +>>#### 2. Provision both WAN circuits +>> +>>Coordinate with your WAN provider to deliver circuits to both PoPs. If using an SD-WAN platform, configure both paths as underlay connections. +>> +>>#### 3. Configure BGP with failover +>> +>>Set up two BGP sessions with appropriate routing policies: +>> +>>- **Active/Standby:** Use Local Preference and AS-path prepending (see the On-Premises tab for detailed BGP examples). +>>- **Active/Active:** Use ECMP for load balancing across both links. +>>- **SD-WAN integration:** Many SD-WAN platforms can detect link quality and switch traffic automatically, supplementing BGP failover. +>> +>>#### 4. Associate both links with your vRack +>> +>>Both OVHcloud Connect services should be associated with the same vRack. +>> +>>#### 5. Configure subnets across AZs +>> +>>Distribute subnets across both AZs for full redundancy. See [Set up your vRack network](../3.6_vrack_network_setup). +>> +>>#### 6. Test failover +>> +>>1. Verify both BGP sessions are Established. +>>2. Shut down the primary link and confirm traffic switches to the backup. +>>3. Restore the primary and verify traffic returns. +>>4. Repeat for the backup link. +>> +>>#### 7. Monitor both paths +>> +>>Set up independent monitoring for each link, each BGP session, and each WAN circuit. See [Monitor](../3.9_monitor). +>> +>>### SD-WAN considerations +>> +>>If you use an SD-WAN overlay: +>> +>>- Configure OVHcloud Connect links as **underlay transports** in your SD-WAN controller. +>>- The SD-WAN platform can perform **path selection** based on latency, jitter, and packet loss — faster than BGP convergence. +>>- Ensure BGP and SD-WAN policies are **aligned** (avoid conflicting routing decisions). +>> +> AWS +>>### Prerequisites +>> +>>- An **AWS account** with a VPC configured +>>- An **OVHcloud account** with a vRack +>>- Two AWS Direct Connect connections at **different locations** +>>- Two OVHcloud Connect Provider services at **different PoPs** +>>- A shared provider (Megaport or Equinix) present at both locations +>>- Non-overlapping IP ranges between AWS VPC and OVHcloud subnets +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> AWS +>> +>> Direct Connect 1 +>> +>> Direct Connect 2 +>> VPC: 10.1.0.0/16 +>> +>> +>> +>> Provider A +>> VXC / MCR +>> +>> +>> Provider B +>> VXC / MCR +>> +>> +>> +>> OVHcloud +>> PoP A / AZ 1 +>> +>> +>> OVHcloud +>> PoP B / AZ 2 +>> +>> +>> +>> vRack +>> 172.16.0.0/16 +>> Servers / VMs +>> Multi-AZ +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> Primary path ─── +>> Backup path - - - +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### Resilience strategy +>> +>>For maximum availability between AWS and OVHcloud: +>> +>>1. **Two AWS Direct Connect connections** in different AWS Direct Connect locations. +>>2. **Two provider VXCs** (or separate providers) bridging to two OVHcloud PoPs. +>>3. **Two OVHcloud Connect services** at different PoPs, both associated with your vRack. +>>4. **BGP failover** configured across both paths. +>> +>>### Step-by-step +>> +>>#### 1. Order redundant AWS Direct Connect connections +>> +>>In the **AWS Console**, create two Direct Connect connections at **different locations**: +>> +>>- Connection 1: AWS Direct Connect location A +>>- Connection 2: AWS Direct Connect location B +>> +>>Create a **Private VIF** on each connection pointing to your VPC (via Virtual Private Gateway or Transit Gateway). +>> +>>> AWS recommends using **Transit Gateway** with multiple Direct Connect Gateways for resilient multi-region architectures. +>> +>>#### 2. Order two OVHcloud Connect Provider services +>> +>>Order at **two different OVHcloud PoPs**. Get two separate pairing keys. See [Order Provider](../3.2_order_provider). +>> +>>#### 3. Create redundant provider bridges +>> +>>On your provider platform: +>> +>>- **Bridge 1:** AWS Direct Connect 1 ↔ OVHcloud PoP A +>>- **Bridge 2:** AWS Direct Connect 2 ↔ OVHcloud PoP B +>> +>>If using MCR (Cloud Router), create separate MCR instances or peering sessions for each path. +>> +>>#### 4. Configure BGP failover +>> +>>Ensure BGP routing preferences are set so traffic prefers the primary path and falls back to the backup: +>> +>>- Use **Local Preference** on the OVHcloud side. +>>- Use **AS-path prepending** on the backup path. +>>- On AWS, use **Direct Connect Gateway** with appropriate route priorities. +>> +>>See [Configure OCC L3 with BGP](../3.7_occ_l3_bgp) for detailed instructions. +>> +>>#### 5. Associate both links with your vRack +>> +>>Associate both OVHcloud Connect services with the same vRack. See [Associate with vRack](../3.5_associate_vrack). +>> +>>#### 6. Test failover +>> +>>1. Verify both paths are active and passing traffic. +>>2. Disable the primary AWS Direct Connect VIF — confirm traffic flows via the backup. +>>3. Disable the primary OVHcloud Connect — confirm traffic flows via the backup. +>>4. Restore both and verify traffic returns to the preferred path. +>> +>>### Cost considerations +>> +>>Resilient AWS-to-OVHcloud requires: +>>- 2× AWS Direct Connect connections (AWS billing) +>>- 2× Provider VXCs or MCR sessions (provider billing) +>>- 2× OVHcloud Connect services (OVHcloud billing) +>> +>>Plan your budget accordingly. The cost of redundancy is typically justified by the risk reduction for production workloads. +>> +>> For more information, please consult [AWS Direct Connect documentation](https://docs.aws.amazon.com/directconnect/) +>> +> Azure +>>### Prerequisites +>> +>>- An **Azure subscription** with permissions to create ExpressRoute circuits +>>- An **OVHcloud account** with a vRack +>>- Two Azure ExpressRoute circuits at **different peering locations** +>>- Two OVHcloud Connect Provider services at **different PoPs** +>>- A shared provider (Megaport or Equinix) present at both locations +>>- A vRack with Multi-AZ enabled ([Multi-AZ guide](../1.5_multi_az)) +>>- Non-overlapping IP ranges between Azure VNet and OVHcloud vRack +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> Azure +>> +>> ExpressRoute 1 +>> +>> ExpressRoute 2 +>> VNet: 10.2.0.0/16 +>> +>> +>> +>> Provider A +>> Location 1 +>> +>> +>> +>> Provider B +>> Location 2 +>> +>> +>> +>> OVHcloud +>> PoP A / AZ 1 +>> +>> +>> +>> OVHcloud +>> PoP B / AZ 2 +>> +>> +>> +>> vRack +>> 172.16.0.0/16 +>> Multi-AZ Servers +>> Hosted Private Cloud +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> Primary ─── +>> Backup - - - +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### Resilience strategy +>> +>>Microsoft recommends **two ExpressRoute circuits in different peering locations** for maximum availability. Combined with two OVHcloud Connect Provider services at different PoPs, this provides end-to-end redundancy: +>> +>>| Component | Primary | Backup | +>>|---|---|---| +>>| Azure ExpressRoute | Circuit 1 (Location A) | Circuit 2 (Location B) | +>>| Provider VXC | VXC set 1 | VXC set 2 | +>>| OVHcloud Connect | Service 1 (PoP A) | Service 2 (PoP B) | +>>| OVHcloud AZ | AZ 1 | AZ 2 | +>> +>>### Step-by-step +>> +>>#### 1. Create two ExpressRoute circuits +>> +>>In the **Azure Portal** → **Create ExpressRoute** (repeat for each circuit): +>> +>>| Setting | Circuit 1 | Circuit 2 | +>>|---|---|---| +>>| Provider | Megaport (or Equinix) | Megaport (or Equinix) | +>>| Peering location | Location A (e.g., Paris) | Location B (e.g., Frankfurt) | +>>| Bandwidth | 1 Gbps | 1 Gbps | +>>| SKU | Standard or Premium | Standard or Premium | +>> +>>Note each circuit's **Service Key**. +>> +>>> **Tip:** Use **ExpressRoute Premium** if your VNets are in different Azure regions than the peering locations. +>> +>>#### 2. Order two OVHcloud Connect Provider services +>> +>>[Order two OVHcloud Connect Provider services](../3.2_order_provider) at different PoPs that correspond to the ExpressRoute peering locations: +>> +>>- OVHcloud Connect 1 → PoP A +>>- OVHcloud Connect 2 → PoP B +>> +>>Retrieve both **pairing keys**. +>> +>>#### 3. Create provider bridges for each path +>> +>>**Path 1 (Primary):** +>> +>>1. Create MCR or port at Location A. +>>2. VXC: Azure ExpressRoute 1 (Service Key 1) → MCR A. +>>3. VXC: MCR A → OVHcloud Connect 1 (Pairing Key 1). +>> +>>**Path 2 (Backup):** +>> +>>1. Create MCR or port at Location B. +>>2. VXC: Azure ExpressRoute 2 (Service Key 2) → MCR B. +>>3. VXC: MCR B → OVHcloud Connect 2 (Pairing Key 2). +>> +>>#### 4. Configure Azure Private Peering on both circuits +>> +>>For each ExpressRoute circuit, configure **Azure Private Peering**: +>> +>>| Parameter | Circuit 1 | Circuit 2 | +>>|---|---|---| +>>| Peer ASN | Provider ASN | Provider ASN | +>>| Primary /30 | 169.254.100.0/30 | 169.254.101.0/30 | +>>| Secondary /30 | 169.254.100.4/30 | 169.254.101.4/30 | +>>| VLAN ID | Assigned by provider | Assigned by provider | +>> +>>#### 5. Link both circuits to your VNet +>> +>>In Azure: +>> +>>1. Go to **Virtual Network Gateways** → **Connections**. +>>2. Add Connection 1 → ExpressRoute Circuit 1 (weight: **100**). +>>3. Add Connection 2 → ExpressRoute Circuit 2 (weight: **50** — lower = backup). +>> +>>Azure uses **connection weight** to prefer one path over the other. +>> +>>#### 6. Configure OVHcloud BGP with failover +>> +>>On the OVHcloud side, use [Configure OCC L3 with BGP](../3.7_occ_l3_bgp) to prefer the primary path: +>> +>>| Path | Local Preference | AS-path prepend | +>>|---|---|---| +>>| OVHcloud Connect 1 (primary) | 200 | None | +>>| OVHcloud Connect 2 (backup) | 100 | 1× prepend | +>> +>>#### 7. Associate both services with your vRack +>> +>>[Associate both OVHcloud Connect services](../3.5_associate_vrack) with the same vRack. Both will inject routes; the vRack will use the higher Local Preference path. +>> +>>#### 8. Test failover +>> +>>| Test | Action | Expected result | +>>|---|---|---| +>>| Primary link failure | Disable ExpressRoute 1 VIF in Azure | Traffic shifts to ExpressRoute 2 within BGP convergence time | +>>| Primary OCC failure | Disable OVHcloud Connect 1 | Traffic shifts to OVHcloud Connect 2 | +>>| Provider failure | Take down MCR A VXCs | Traffic shifts to MCR B path | +>>| Full recovery | Re-enable all links | Traffic returns to primary path | +>> +>>> **Convergence time:** BGP failover typically completes in **30–90 seconds** depending on hold timers and BFD configuration. +>> +>>### Azure-specific considerations +>> +>>- **ExpressRoute Global Reach**: If both OVHcloud PoPs are in different Azure regions, consider enabling [Global Reach](https://learn.microsoft.com/en-us/azure/expressroute/expressroute-global-reach) for direct circuit-to-circuit communication. +>>- **FastPath**: For Ultra Performance or ErGw3AZ gateways, enable [FastPath](https://learn.microsoft.com/en-us/azure/expressroute/about-fastpath) for improved network performance. +>>- **Route limits**: Azure Private Peering supports up to **4,000 routes** per circuit. Aggregate OVHcloud prefixes to stay within limits. +>> +>> For more information, please consult [Azure ExpressRoute documentation](https://learn.microsoft.com/en-us/azure/expressroute/) +>> +> GCP +>>### Prerequisites +>> +>>- A **GCP project** with the Compute Network Admin role +>>- Two Cloud Routers (one per region or availability domain) +>>- An **OVHcloud account** with a vRack +>>- Two OVHcloud Connect Provider services at **different PoPs** +>>- A shared provider (Megaport or Equinix) at both locations +>>- A vRack with Multi-AZ enabled +>>- **Non-overlapping IP ranges** between GCP VPC and OVHcloud vRack +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> Google Cloud +>> +>> Interconnect 1 +>> +>> Interconnect 2 +>> VPC: 10.3.0.0/16 +>> +>> +>> +>> Provider A +>> Edge domain 1 +>> +>> +>> +>> Provider B +>> Edge domain 2 +>> +>> +>> +>> OVHcloud +>> PoP A / AZ 1 +>> +>> +>> +>> OVHcloud +>> PoP B / AZ 2 +>> +>> +>> +>> vRack +>> 172.16.0.0/16 +>> Multi-AZ Servers +>> Cloud Instances +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> Primary ─── +>> Backup - - - +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### Resilience strategy +>> +>>Google Cloud recommends using VLAN attachments in **different edge availability domains** to achieve 99.9%–99.99% SLA. Combined with dual OVHcloud Connect links, you get full end-to-end resilience: +>> +>>| Component | Primary | Backup | +>>|---|---|---| +>>| GCP VLAN attachment | Edge domain zone1 | Edge domain zone2 | +>>| Provider VXC | VXC set 1 | VXC set 2 | +>>| OVHcloud Connect | Service 1 (PoP A) | Service 2 (PoP B) | +>>| OVHcloud AZ | AZ 1 | AZ 2 | +>> +>>##### GCP SLA tiers +>> +>>| Configuration | GCP SLA | +>>|---|---| +>>| Single VLAN attachment | No SLA | +>>| Two attachments in different edge domains, same metro | 99.9% | +>>| Four attachments in two different metros | 99.99% | +>> +>>### Step-by-step +>> +>>#### 1. Create two Cloud Routers +>> +>>Create a Cloud Router in each region or for each edge availability domain: +>> +>>| Router | Region | ASN | +>>|---|---|---| +>>| `router-ovhcloud-1` | `europe-west1` | 16550 (default) | +>>| `router-ovhcloud-2` | `europe-west3` | 16550 (default) | +>> +>>#### 2. Create two VLAN attachments +>> +>>For each Cloud Router, create a **Partner Interconnect VLAN attachment**: +>> +>>| Attachment | Cloud Router | Edge availability domain | +>>|---|---|---| +>>| `attachment-1` | `router-ovhcloud-1` | `zone1` | +>>| `attachment-2` | `router-ovhcloud-2` | `zone2` | +>> +>>Note both **GCP pairing keys**. +>> +>>#### 3. Order two OVHcloud Connect Provider services +>> +>>[Order two OVHcloud Connect Provider services](../3.2_order_provider) at different PoPs: +>> +>>- OVHcloud Connect 1 → PoP A +>>- OVHcloud Connect 2 → PoP B +>> +>>Retrieve both **OVHcloud pairing keys**. +>> +>>#### 4. Create provider bridges for each path +>> +>>**Path 1 (Primary):** +>> +>>1. MCR or port at Location A. +>>2. VXC: GCP Partner Interconnect (GCP pairing key 1) → MCR A. +>>3. VXC: MCR A → OVHcloud Connect 1 (OVHcloud pairing key 1). +>> +>>**Path 2 (Backup):** +>> +>>1. MCR or port at Location B. +>>2. VXC: GCP Partner Interconnect (GCP pairing key 2) → MCR B. +>>3. VXC: MCR B → OVHcloud Connect 2 (OVHcloud pairing key 2). +>> +>>#### 5. Activate both GCP VLAN attachments +>> +>>In the GCP Console: +>> +>>1. Go to **Hybrid Connectivity** → **VLAN attachments**. +>>2. For each attachment: click **Activate** once it shows "Pending customer". +>>3. Verify BGP sessions are established in both Cloud Routers. +>> +>>#### 6. Configure BGP failover +>> +>>**GCP side:** +>> +>>GCP Cloud Router uses **MED (Multi-Exit Discriminator)** to influence path selection. Set different MED values: +>> +>>| Attachment | Advertised MED | +>>|---|---| +>>| `attachment-1` (primary) | 100 (lower = preferred) | +>>| `attachment-2` (backup) | 200 | +>> +>>You can configure MED via custom route advertisements in the Cloud Router BGP peer settings. +>> +>>**OVHcloud side:** +>> +>>Use [Configure OCC L3 with BGP](../3.7_occ_l3_bgp): +>> +>>| Path | Local Preference | AS-path prepend | +>>|---|---|---| +>>| OVHcloud Connect 1 (primary) | 200 | None | +>>| OVHcloud Connect 2 (backup) | 100 | 1× prepend | +>> +>>#### 7. Associate both services with your vRack +>> +>>[Associate both OVHcloud Connect services](../3.5_associate_vrack) with the same vRack. +>> +>>#### 8. Test failover +>> +>>| Test | Action | Expected result | +>>|---|---|---| +>>| GCP link failure | Disable VLAN attachment 1 | Traffic shifts to attachment 2 | +>>| OCC link failure | Disable OVHcloud Connect 1 | Traffic shifts to OVHcloud Connect 2 | +>>| Provider failure | Take down MCR A | Traffic shifts to MCR B path | +>>| Full recovery | Re-enable all | Traffic returns to primary | +>> +>>### GCP-specific considerations +>> +>>- **Custom route advertisements**: Use Cloud Router custom route advertisements to control which subnets are announced to OVHcloud. Avoid advertising the entire VPC if only specific subnets are needed. +>>- **Dataplane v2**: If using GKE with Dataplane v2, ensure Pod CIDR ranges are included in route advertisements if GKE pods need to communicate with OVHcloud. +>>- **Shared VPC**: If using Shared VPC, create the Interconnect in the host project and share with service projects. +>>- **MTU**: GCP Interconnect supports **1440 MTU** for Partner Interconnect. Ensure OVHcloud Connect and provider VXCs use matching MTU settings. +>> +>> For more information, please consult [GCP Interconnect documentation](https://cloud.google.com/network-connectivity/docs/interconnect) and [GCP Cloud Router documentation](https://cloud.google.com/network-connectivity/docs/router) + +### What's next? + +- [Simple architecture](../4.1_simple) for non-critical use cases +- [Monitor your connections](../3.9_monitor) +- [Multi-AZ configuration](../1.5_multi_az) for OVHcloud side resilience + +### Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/4.2_resilient/guide.fr-fr.md b/pages/network/ovhcloud_connect/4.2_resilient/guide.fr-fr.md new file mode 100644 index 00000000000..388ff58ed00 --- /dev/null +++ b/pages/network/ovhcloud_connect/4.2_resilient/guide.fr-fr.md @@ -0,0 +1,816 @@ +--- +title: Mettre en place une architecture OVHcloud Connect résiliente +excerpt: Connectez votre infrastructure à OVHcloud via deux liens OVHcloud Connect redondants pour assurer la haute disponibilité et la bascule automatique. +updated: 2026-02-18 +--- + +## Objectif + +Ce tutoriel vous guide pour connecter votre infrastructure à OVHcloud à l'aide de **deux liens OVHcloud Connect indépendants** afin d'obtenir la haute disponibilité. Si un lien tombe en panne, le trafic bascule automatiquement vers l'autre. + +## En pratique + +Vous trouverez ci-dessous les prérequis et les instructions pour cinq cas d'usage distincts, que vous pouvez choisir selon l'architecture souhaitée. + +> [!tabs] +> On-Premises +>>### Prérequis +>> +>>- Deux services OVHcloud Connect (Direct, Provider ou un mix) se terminant sur **des PoPs différents** +>>- Un routeur (ou deux routeurs) capable de gérer **plusieurs sessions BGP** avec bascule +>>- Un plan d'adressage IP couvrant **deux AZ** chez OVHcloud +>>- Un vRack avec des ressources dans les deux AZ +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> On-Premises +>> Router 1 +>> (or dual-homed router) +>> ASN: 65001 +>> 10.0.0.0/16 +>> +>> +>> +>> PoP A +>> Primary link +>> +>> +>> +>> PoP B +>> Backup link +>> +>> +>> +>> OVHcloud AZ 1 +>> vRack · Servers · VMs +>> 172.16.1.0/24 +>> +>> +>> +>> OVHcloud AZ 2 +>> vRack · Servers · VMs +>> 172.16.2.0/24 +>> +>> +>> +>> +>> +>> +>> +>> +>> Primary +>> Backup +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### Quand utiliser cette architecture +>> +>>| ✅ Recommandée pour | Détails | +>>|---|---| +>>| Production critique pour l'activité | Workloads ne tolérant aucune indisponibilité | +>>| Environnements réglementés | Cadres de conformité exigeant la haute disponibilité | +>>| Exigences de SLA ≥ 99,99 % | Architecture multi-chemins nécessaire pour un SLA premium | +>>| Reprise après sinistre | Bascule automatique sans intervention manuelle | +>> +>>#### 1. Commander deux liens OVHcloud Connect +>> +>>Commandez deux services OVHcloud Connect distincts sur **des PoPs différents** pour assurer la diversité physique : +>> +>>- **Lien 1 (principal) :** commandez sur le PoP A — voir [Commander Direct](../3.1_order_direct) ou [Commander Provider](../3.2_order_provider). +>>- **Lien 2 (secours) :** commandez sur le PoP B — même processus, PoP différent. +>> +>>> **Conseil de diversité :** utilisez des datacenters différents ou, à défaut, des chemins physiques distincts pour éviter un point de défaillance partagé. +>> +>>#### 2. Installer les deux connexions physiques +>> +>>Pour chaque lien : +>>- **Direct :** installez les cross-connects sur chaque PoP. Voir [LOA Cross Connect](../3.11_cross_connect_loa). +>>- **Provider :** partagez les clés d'appairage respectives avec votre ou vos opérateurs. +>> +>>#### 3. Configurer BGP avec bascule +>> +>>Mettez en place **deux sessions BGP** — une par lien — avec des politiques de routage qui définissent le chemin préféré. +>> +>>##### Exemple actif/passif (Cisco IOS) +>> +>>``` +>>router bgp 65001 +>> ! Primary link via PoP A +>> neighbor 192.0.2.1 remote-as 35540 +>> neighbor 192.0.2.1 description OVHcloud-Primary +>> neighbor 192.0.2.1 route-map PRIMARY-IN in +>> neighbor 192.0.2.1 route-map PRIMARY-OUT out +>> +>> ! Backup link via PoP B +>> neighbor 198.51.100.1 remote-as 35540 +>> neighbor 198.51.100.1 description OVHcloud-Backup +>> neighbor 198.51.100.1 route-map BACKUP-IN in +>> neighbor 198.51.100.1 route-map BACKUP-OUT out +>> +>>! Prefer primary path using Local Preference +>>route-map PRIMARY-IN permit 10 +>> set local-preference 200 +>> +>>route-map BACKUP-IN permit 10 +>> set local-preference 100 +>> +>>! Influence OVHcloud's return traffic using AS-path prepending on backup +>>route-map PRIMARY-OUT permit 10 +>> +>>route-map BACKUP-OUT permit 10 +>> set as-path prepend 65001 65001 +>>``` +>> +>>##### Attributs BGP clés pour la bascule +>> +>>| Attribut | Effet | Cas d'usage | +>>|---|---|---| +>>| **Local Preference** | Contrôle la préférence du chemin sortant (plus élevé = préféré) | Rendre le chemin principal préféré pour le trafic sortant de votre réseau | +>>| **AS-path prepending** | Fait paraître un chemin plus long (moins préféré) | Influencer le choix du chemin de retour par OVHcloud | +>>| **MED** | Suggère une préférence au côté distant | Peut ne pas être pris en compte dans toutes les configurations OVHcloud | +>> +>>#### 4. Associer les deux liens à votre vRack +>> +>>Associez les deux services OVHcloud Connect au **même vRack**. Voir [Associer à un vRack](../3.5_associate_vrack). +>> +>>#### 5. Configurer les sous-réseaux dans les deux AZ +>> +>>Configurez des sous-réseaux privés dans les deux Availability Zones. Voir [Configurer votre réseau vRack](../3.6_vrack_network_setup). +>> +>>#### 6. Tester la bascule +>> +>>**Cette étape est critique.** Ne sautez pas les tests de bascule. +>> +>>1. **Vérifiez le fonctionnement normal :** +>> - Les deux sessions BGP sont à l'état Established. +>> - Le trafic transite par le lien principal. +>> +>>2. **Simulez la défaillance du lien principal :** +>> - Arrêtez la session BGP principale ou déconnectez physiquement le lien principal. +>> - Vérifiez que le trafic bascule vers le lien de secours dans le délai de convergence BGP (généralement 30 à 90 secondes ; cela peut être plus rapide avec BFD). +>> - Confirmez l'absence de perte de paquets au-delà de la fenêtre de convergence. +>> +>>3. **Restaurez le lien principal :** +>> - Remettez le lien principal en service. +>> - Vérifiez que le trafic revient sur le chemin principal. +>> +>>4. **Testez l'inverse :** +>> - Simulez une défaillance du lien de secours pendant que le principal est actif. Cela confirme que les deux liens fonctionnent indépendamment. +>> +>>#### 7. Mettre en place la supervision +>> +>>Supervisez les **deux liens** indépendamment. Configurez des alertes pour : +>>- Les chutes de session BGP sur l'un ou l'autre lien +>>- Le déséquilibre de trafic (tout le trafic sur un seul lien peut indiquer une défaillance de l'autre) +>>- La bande passante approchant la capacité maximale sur l'un ou l'autre lien +>> +>>Voir [Superviser](../3.9_monitor). +>> +>>### Avancé : configuration actif/actif +>> +>>Pour un débit maximal et une bascule plus rapide, vous pouvez exploiter les deux liens en mode **actif/actif** : +>> +>>- Définissez une **Local Preference égale** sur les deux chemins. +>>- Utilisez **ECMP (Equal-Cost Multi-Path)** s'il est pris en charge. +>>- Le trafic est réparti sur les deux liens. +>>- Si un lien tombe en panne, l'intégralité du trafic transite immédiatement par le lien restant. +>> +>>> Le mode actif/actif offre une bande passante agrégée plus élevée mais nécessite une planification de capacité rigoureuse — chaque lien doit être en mesure d'absorber seul la totalité de la charge en cas de défaillance. +>> +> WAN +>>### Prérequis +>> +>>- Un compte OVHcloud avec un vRack +>>- Deux services OVHcloud Connect (Direct, Provider ou un mix) se terminant sur **des PoPs différents** +>>- Un backbone WAN (MPLS ou SD-WAN) avec des circuits atteignant les deux PoPs +>>- Des équipements de bordure WAN compatibles BGP +>>- Un plan d'adressage IP sans recouvrement entre vos sous-réseaux WAN et OVHcloud +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> Branches +>> Office A +>> Office B +>> Office C +>> +>> +>> +>> WAN +>> SD-WAN / +>> MPLS +>> +>> +>> +>> PoP A +>> Primary +>> +>> +>> +>> PoP B +>> Backup +>> +>> +>> +>> OVHcloud AZ 1 +>> vRack · Servers · 172.16.1.0/24 +>> +>> +>> +>> OVHcloud AZ 2 +>> vRack · Servers · 172.16.2.0/24 +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### Quand utiliser cette architecture +>> +>>- **Connectivité WAN critique pour l'activité** — plusieurs sites dépendent de l'accès à OVHcloud. +>>- **Exigences de SLA ≥ 99,99 %** — des liens redondants sont nécessaires pour des garanties de disponibilité premium. +>>- **SD-WAN avec chemins diversifiés** — les plateformes SD-WAN peuvent router automatiquement sur le meilleur chemin disponible. +>> +>>### Étape par étape +>> +>>#### 1. Commander deux liens OVHcloud Connect +>> +>>Commandez sur **des PoPs différents** pour assurer la diversité physique. Vous pouvez combiner connexions Direct et Provider. +>> +>>#### 2. Provisionner les deux circuits WAN +>> +>>Coordonnez-vous avec votre opérateur WAN pour livrer des circuits sur les deux PoPs. Si vous utilisez une plateforme SD-WAN, configurez les deux chemins comme connexions de transport (underlay). +>> +>>#### 3. Configurer BGP avec bascule +>> +>>Mettez en place deux sessions BGP avec des politiques de routage adaptées : +>> +>>- **Actif/passif :** utilisez la Local Preference et l'AS-path prepending (voir l'onglet On-Premises pour des exemples BGP détaillés). +>>- **Actif/actif :** utilisez ECMP pour répartir la charge sur les deux liens. +>>- **Intégration SD-WAN :** de nombreuses plateformes SD-WAN détectent la qualité des liens et redirigent le trafic automatiquement, en complément de la bascule BGP. +>> +>>#### 4. Associer les deux liens à votre vRack +>> +>>Les deux services OVHcloud Connect doivent être associés au même vRack. +>> +>>#### 5. Configurer les sous-réseaux dans les AZ +>> +>>Répartissez les sous-réseaux entre les deux AZ pour une redondance complète. Voir [Configurer votre réseau vRack](../3.6_vrack_network_setup). +>> +>>#### 6. Tester la bascule +>> +>>1. Vérifiez que les deux sessions BGP sont à l'état Established. +>>2. Arrêtez le lien principal et confirmez que le trafic bascule vers le lien de secours. +>>3. Restaurez le lien principal et vérifiez que le trafic revient. +>>4. Répétez pour le lien de secours. +>> +>>#### 7. Superviser les deux chemins +>> +>>Mettez en place une supervision indépendante pour chaque lien, chaque session BGP et chaque circuit WAN. Voir [Superviser](../3.9_monitor). +>> +>>### Considérations SD-WAN +>> +>>Si vous utilisez un overlay SD-WAN : +>> +>>- Configurez les liens OVHcloud Connect comme **transports underlay** dans votre contrôleur SD-WAN. +>>- La plateforme SD-WAN peut effectuer une **sélection de chemin** basée sur la latence, la gigue et la perte de paquets — plus rapidement que la convergence BGP. +>>- Assurez-vous que les politiques BGP et SD-WAN sont **alignées** (évitez les décisions de routage contradictoires). +>> +> AWS +>>### Prérequis +>> +>>- Un **compte AWS** avec un VPC configuré +>>- Un **compte OVHcloud** avec un vRack +>>- Deux connexions AWS Direct Connect sur **des emplacements différents** +>>- Deux services OVHcloud Connect Provider sur **des PoPs différents** +>>- Un opérateur partagé (Megaport ou Equinix) présent sur les deux emplacements +>>- Des plages IP non chevauchantes entre le VPC AWS et les sous-réseaux OVHcloud +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> AWS +>> +>> Direct Connect 1 +>> +>> Direct Connect 2 +>> VPC: 10.1.0.0/16 +>> +>> +>> +>> Provider A +>> VXC / MCR +>> +>> +>> Provider B +>> VXC / MCR +>> +>> +>> +>> OVHcloud +>> PoP A / AZ 1 +>> +>> +>> OVHcloud +>> PoP B / AZ 2 +>> +>> +>> +>> vRack +>> 172.16.0.0/16 +>> Servers / VMs +>> Multi-AZ +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> Primary path ─── +>> Backup path - - - +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### Stratégie de résilience +>> +>>Pour une disponibilité maximale entre AWS et OVHcloud : +>> +>>1. **Deux connexions AWS Direct Connect** sur des emplacements AWS Direct Connect différents. +>>2. **Deux VXC opérateur** (ou opérateurs distincts) reliant deux PoPs OVHcloud. +>>3. **Deux services OVHcloud Connect** sur des PoPs différents, tous deux associés à votre vRack. +>>4. **Bascule BGP** configurée sur les deux chemins. +>> +>>### Étape par étape +>> +>>#### 1. Commander des connexions AWS Direct Connect redondantes +>> +>>Dans la **console AWS**, créez deux connexions Direct Connect sur **des emplacements différents** : +>> +>>- Connexion 1 : emplacement AWS Direct Connect A +>>- Connexion 2 : emplacement AWS Direct Connect B +>> +>>Créez une **Private VIF** sur chaque connexion pointant vers votre VPC (via Virtual Private Gateway ou Transit Gateway). +>> +>>> AWS recommande d'utiliser **Transit Gateway** avec plusieurs Direct Connect Gateways pour des architectures multi-régions résilientes. +>> +>>#### 2. Commander deux services OVHcloud Connect Provider +>> +>>Commandez sur **deux PoPs OVHcloud différents**. Récupérez deux clés d'appairage distinctes. Voir [Commander Provider](../3.2_order_provider). +>> +>>#### 3. Créer des ponts opérateur redondants +>> +>>Sur la plateforme de votre opérateur : +>> +>>- **Pont 1 :** AWS Direct Connect 1 ↔ OVHcloud PoP A +>>- **Pont 2 :** AWS Direct Connect 2 ↔ OVHcloud PoP B +>> +>>Si vous utilisez un MCR (Cloud Router), créez des instances MCR séparées ou des sessions de peering pour chaque chemin. +>> +>>#### 4. Configurer la bascule BGP +>> +>>Assurez-vous que les préférences de routage BGP sont définies de telle sorte que le trafic privilégie le chemin principal et bascule sur le chemin de secours : +>> +>>- Utilisez la **Local Preference** côté OVHcloud. +>>- Utilisez l'**AS-path prepending** sur le chemin de secours. +>>- Sur AWS, utilisez **Direct Connect Gateway** avec des priorités de routes adaptées. +>> +>>Consultez [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp) pour les instructions détaillées. +>> +>>#### 5. Associer les deux liens à votre vRack +>> +>>Associez les deux services OVHcloud Connect au même vRack. Voir [Associer à un vRack](../3.5_associate_vrack). +>> +>>#### 6. Tester la bascule +>> +>>1. Vérifiez que les deux chemins sont actifs et acheminent du trafic. +>>2. Désactivez la VIF AWS Direct Connect principale — confirmez que le trafic transite par le chemin de secours. +>>3. Désactivez le service OVHcloud Connect principal — confirmez que le trafic transite par le chemin de secours. +>>4. Restaurez les deux et vérifiez que le trafic revient sur le chemin préféré. +>> +>>### Considérations de coût +>> +>>Une connectivité résiliente entre AWS et OVHcloud nécessite : +>>- 2× connexions AWS Direct Connect (facturation AWS) +>>- 2× VXC opérateur ou sessions MCR (facturation opérateur) +>>- 2× services OVHcloud Connect (facturation OVHcloud) +>> +>>Planifiez votre budget en conséquence. Le coût de la redondance est généralement justifié par la réduction du risque pour les workloads de production. +>> +>> Pour plus d'informations, veuillez consulter la [documentation AWS Direct Connect](https://docs.aws.amazon.com/directconnect/) +>> +> Azure +>>### Prérequis +>> +>>- Un **abonnement Azure** avec les autorisations nécessaires pour créer des circuits ExpressRoute +>>- Un **compte OVHcloud** avec un vRack +>>- Deux circuits Azure ExpressRoute sur **des emplacements de peering différents** +>>- Deux services OVHcloud Connect Provider sur **des PoPs différents** +>>- Un opérateur partagé (Megaport ou Equinix) présent sur les deux emplacements +>>- Un vRack avec Multi-AZ activé ([guide Multi-AZ](../1.5_multi_az)) +>>- Des plages IP non chevauchantes entre le VNet Azure et le vRack OVHcloud +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> Azure +>> +>> ExpressRoute 1 +>> +>> ExpressRoute 2 +>> VNet: 10.2.0.0/16 +>> +>> +>> +>> Provider A +>> Location 1 +>> +>> +>> +>> Provider B +>> Location 2 +>> +>> +>> +>> OVHcloud +>> PoP A / AZ 1 +>> +>> +>> +>> OVHcloud +>> PoP B / AZ 2 +>> +>> +>> +>> vRack +>> 172.16.0.0/16 +>> Multi-AZ Servers +>> Hosted Private Cloud +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> Primary ─── +>> Backup - - - +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### Stratégie de résilience +>> +>>Microsoft recommande **deux circuits ExpressRoute sur des emplacements de peering différents** pour une disponibilité maximale. Combinés à deux services OVHcloud Connect Provider sur des PoPs différents, cela offre une redondance de bout en bout : +>> +>>| Composant | Principal | Secours | +>>|---|---|---| +>>| Azure ExpressRoute | Circuit 1 (emplacement A) | Circuit 2 (emplacement B) | +>>| VXC opérateur | Set VXC 1 | Set VXC 2 | +>>| OVHcloud Connect | Service 1 (PoP A) | Service 2 (PoP B) | +>>| AZ OVHcloud | AZ 1 | AZ 2 | +>> +>>### Étape par étape +>> +>>#### 1. Créer deux circuits ExpressRoute +>> +>>Dans le **portail Azure** → **Créer ExpressRoute** (à répéter pour chaque circuit) : +>> +>>| Paramètre | Circuit 1 | Circuit 2 | +>>|---|---|---| +>>| Provider | Megaport (ou Equinix) | Megaport (ou Equinix) | +>>| Emplacement de peering | Emplacement A (par exemple, Paris) | Emplacement B (par exemple, Francfort) | +>>| Bande passante | 1 Gbps | 1 Gbps | +>>| SKU | Standard ou Premium | Standard ou Premium | +>> +>>Notez la **clé de service** de chaque circuit. +>> +>>> **Astuce :** utilisez **ExpressRoute Premium** si vos VNets se trouvent dans des régions Azure différentes des emplacements de peering. +>> +>>#### 2. Commander deux services OVHcloud Connect Provider +>> +>>[Commandez deux services OVHcloud Connect Provider](../3.2_order_provider) sur des PoPs différents correspondant aux emplacements de peering ExpressRoute : +>> +>>- OVHcloud Connect 1 → PoP A +>>- OVHcloud Connect 2 → PoP B +>> +>>Récupérez les deux **clés d'appairage**. +>> +>>#### 3. Créer les ponts opérateur pour chaque chemin +>> +>>**Chemin 1 (principal) :** +>> +>>1. Créez un MCR ou un port à l'emplacement A. +>>2. VXC : Azure ExpressRoute 1 (clé de service 1) → MCR A. +>>3. VXC : MCR A → OVHcloud Connect 1 (clé d'appairage 1). +>> +>>**Chemin 2 (secours) :** +>> +>>1. Créez un MCR ou un port à l'emplacement B. +>>2. VXC : Azure ExpressRoute 2 (clé de service 2) → MCR B. +>>3. VXC : MCR B → OVHcloud Connect 2 (clé d'appairage 2). +>> +>>#### 4. Configurer le peering privé Azure sur les deux circuits +>> +>>Pour chaque circuit ExpressRoute, configurez l'**Azure Private Peering** : +>> +>>| Paramètre | Circuit 1 | Circuit 2 | +>>|---|---|---| +>>| ASN du peer | ASN du provider | ASN du provider | +>>| /30 principal | 169.254.100.0/30 | 169.254.101.0/30 | +>>| /30 secondaire | 169.254.100.4/30 | 169.254.101.4/30 | +>>| ID VLAN | Attribué par le provider | Attribué par le provider | +>> +>>#### 5. Lier les deux circuits à votre VNet +>> +>>Dans Azure : +>> +>>1. Accédez à **Virtual Network Gateways** → **Connections**. +>>2. Ajoutez Connection 1 → ExpressRoute Circuit 1 (poids : **100**). +>>3. Ajoutez Connection 2 → ExpressRoute Circuit 2 (poids : **50** — plus bas = secours). +>> +>>Azure utilise le **poids de connexion** pour privilégier un chemin par rapport à l'autre. +>> +>>#### 6. Configurer BGP côté OVHcloud avec bascule +>> +>>Côté OVHcloud, utilisez [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp) pour privilégier le chemin principal : +>> +>>| Chemin | Local Preference | AS-path prepend | +>>|---|---|---| +>>| OVHcloud Connect 1 (principal) | 200 | Aucun | +>>| OVHcloud Connect 2 (secours) | 100 | 1× prepend | +>> +>>#### 7. Associer les deux services à votre vRack +>> +>>[Associez les deux services OVHcloud Connect](../3.5_associate_vrack) au même vRack. Les deux injecteront des routes ; le vRack utilisera le chemin avec la Local Preference la plus élevée. +>> +>>#### 8. Tester la bascule +>> +>>| Test | Action | Résultat attendu | +>>|---|---|---| +>>| Défaillance du lien principal | Désactiver la VIF ExpressRoute 1 dans Azure | Le trafic bascule vers ExpressRoute 2 dans le délai de convergence BGP | +>>| Défaillance OCC principal | Désactiver OVHcloud Connect 1 | Le trafic bascule vers OVHcloud Connect 2 | +>>| Défaillance opérateur | Mettre hors service les VXC du MCR A | Le trafic bascule sur le chemin via MCR B | +>>| Récupération complète | Réactiver tous les liens | Le trafic revient sur le chemin principal | +>> +>>> **Temps de convergence :** la bascule BGP s'effectue généralement en **30 à 90 secondes** selon les hold timers et la configuration BFD. +>> +>>### Considérations spécifiques à Azure +>> +>>- **ExpressRoute Global Reach :** si les deux PoPs OVHcloud sont dans des régions Azure différentes, envisagez d'activer [Global Reach](https://learn.microsoft.com/en-us/azure/expressroute/expressroute-global-reach) pour permettre la communication directe entre circuits. +>>- **FastPath :** pour les passerelles Ultra Performance ou ErGw3AZ, activez [FastPath](https://learn.microsoft.com/en-us/azure/expressroute/about-fastpath) afin d'améliorer les performances réseau. +>>- **Limites de routes :** Azure Private Peering prend en charge jusqu'à **4 000 routes** par circuit. Agrégez les préfixes OVHcloud pour rester dans la limite. +>> +>> Pour plus d'informations, veuillez consulter la [documentation Azure ExpressRoute](https://learn.microsoft.com/en-us/azure/expressroute/) +>> +> GCP +>>### Prérequis +>> +>>- Un **projet GCP** avec le rôle Compute Network Admin +>>- Deux Cloud Routers (un par région ou domaine de disponibilité) +>>- Un **compte OVHcloud** avec un vRack +>>- Deux services OVHcloud Connect Provider sur **des PoPs différents** +>>- Un opérateur partagé (Megaport ou Equinix) présent sur les deux emplacements +>>- Un vRack avec Multi-AZ activé +>>- Des **plages IP non chevauchantes** entre le VPC GCP et le vRack OVHcloud +>> +>>### Architecture +>> +>>```svg +>> +>> +>> +>> +>> +>> Google Cloud +>> +>> Interconnect 1 +>> +>> Interconnect 2 +>> VPC: 10.3.0.0/16 +>> +>> +>> +>> Provider A +>> Edge domain 1 +>> +>> +>> +>> Provider B +>> Edge domain 2 +>> +>> +>> +>> OVHcloud +>> PoP A / AZ 1 +>> +>> +>> +>> OVHcloud +>> PoP B / AZ 2 +>> +>> +>> +>> vRack +>> 172.16.0.0/16 +>> Multi-AZ Servers +>> Cloud Instances +>> +>> +>> +>> +>> +>> +>> +>> +>> +>> Primary ─── +>> Backup - - - +>> +>> +>> +>> +>> +>> +>> +>>``` +>> +>>### Stratégie de résilience +>> +>>Google Cloud recommande d'utiliser des VLAN attachments dans **des edge availability domains différents** pour atteindre un SLA de 99,9 % à 99,99 %. Combiné à des liens OVHcloud Connect en double, vous obtenez une résilience complète de bout en bout : +>> +>>| Composant | Principal | Secours | +>>|---|---|---| +>>| GCP VLAN attachment | Edge domain zone1 | Edge domain zone2 | +>>| VXC opérateur | Set VXC 1 | Set VXC 2 | +>>| OVHcloud Connect | Service 1 (PoP A) | Service 2 (PoP B) | +>>| AZ OVHcloud | AZ 1 | AZ 2 | +>> +>>##### Niveaux de SLA GCP +>> +>>| Configuration | SLA GCP | +>>|---|---| +>>| Un seul VLAN attachment | Aucun SLA | +>>| Deux attachments dans des edge domains différents, même metro | 99,9 % | +>>| Quatre attachments dans deux metros différents | 99,99 % | +>> +>>### Étape par étape +>> +>>#### 1. Créer deux Cloud Routers +>> +>>Créez un Cloud Router dans chaque région ou pour chaque edge availability domain : +>> +>>| Router | Région | ASN | +>>|---|---|---| +>>| `router-ovhcloud-1` | `europe-west1` | 16550 (par défaut) | +>>| `router-ovhcloud-2` | `europe-west3` | 16550 (par défaut) | +>> +>>#### 2. Créer deux VLAN attachments +>> +>>Pour chaque Cloud Router, créez un **VLAN attachment Partner Interconnect** : +>> +>>| Attachment | Cloud Router | Edge availability domain | +>>|---|---|---| +>>| `attachment-1` | `router-ovhcloud-1` | `zone1` | +>>| `attachment-2` | `router-ovhcloud-2` | `zone2` | +>> +>>Notez les deux **clés d'appairage GCP**. +>> +>>#### 3. Commander deux services OVHcloud Connect Provider +>> +>>[Commandez deux services OVHcloud Connect Provider](../3.2_order_provider) sur des PoPs différents : +>> +>>- OVHcloud Connect 1 → PoP A +>>- OVHcloud Connect 2 → PoP B +>> +>>Récupérez les deux **clés d'appairage OVHcloud**. +>> +>>#### 4. Créer les ponts opérateur pour chaque chemin +>> +>>**Chemin 1 (principal) :** +>> +>>1. MCR ou port à l'emplacement A. +>>2. VXC : GCP Partner Interconnect (clé d'appairage GCP 1) → MCR A. +>>3. VXC : MCR A → OVHcloud Connect 1 (clé d'appairage OVHcloud 1). +>> +>>**Chemin 2 (secours) :** +>> +>>1. MCR ou port à l'emplacement B. +>>2. VXC : GCP Partner Interconnect (clé d'appairage GCP 2) → MCR B. +>>3. VXC : MCR B → OVHcloud Connect 2 (clé d'appairage OVHcloud 2). +>> +>>#### 5. Activer les deux VLAN attachments GCP +>> +>>Dans la console GCP : +>> +>>1. Accédez à **Hybrid Connectivity** → **VLAN attachments**. +>>2. Pour chaque attachment : cliquez sur **Activate** dès qu'il affiche « Pending customer ». +>>3. Vérifiez que les sessions BGP sont établies dans les deux Cloud Routers. +>> +>>#### 6. Configurer la bascule BGP +>> +>>**Côté GCP :** +>> +>>Le Cloud Router de GCP utilise le **MED (Multi-Exit Discriminator)** pour influencer la sélection du chemin. Définissez des valeurs MED différentes : +>> +>>| Attachment | MED annoncé | +>>|---|---| +>>| `attachment-1` (principal) | 100 (plus bas = préféré) | +>>| `attachment-2` (secours) | 200 | +>> +>>Vous pouvez configurer le MED via les annonces de routes personnalisées dans les paramètres du peer BGP du Cloud Router. +>> +>>**Côté OVHcloud :** +>> +>>Utilisez [Configurer OCC L3 avec BGP](../3.7_occ_l3_bgp) : +>> +>>| Chemin | Local Preference | AS-path prepend | +>>|---|---|---| +>>| OVHcloud Connect 1 (principal) | 200 | Aucun | +>>| OVHcloud Connect 2 (secours) | 100 | 1× prepend | +>> +>>#### 7. Associer les deux services à votre vRack +>> +>>[Associez les deux services OVHcloud Connect](../3.5_associate_vrack) au même vRack. +>> +>>#### 8. Tester la bascule +>> +>>| Test | Action | Résultat attendu | +>>|---|---|---| +>>| Défaillance du lien GCP | Désactiver le VLAN attachment 1 | Le trafic bascule vers l'attachment 2 | +>>| Défaillance du lien OCC | Désactiver OVHcloud Connect 1 | Le trafic bascule vers OVHcloud Connect 2 | +>>| Défaillance opérateur | Mettre hors service le MCR A | Le trafic bascule sur le chemin via MCR B | +>>| Récupération complète | Tout réactiver | Le trafic revient sur le chemin principal | +>> +>>### Considérations spécifiques à GCP +>> +>>- **Annonces de routes personnalisées :** utilisez les annonces de routes personnalisées du Cloud Router pour contrôler les sous-réseaux annoncés à OVHcloud. Évitez d'annoncer le VPC entier si seuls certains sous-réseaux sont nécessaires. +>>- **Dataplane v2 :** si vous utilisez GKE avec Dataplane v2, veillez à inclure les plages CIDR des Pods dans les annonces de routes si les pods GKE doivent communiquer avec OVHcloud. +>>- **Shared VPC :** si vous utilisez un Shared VPC, créez l'Interconnect dans le projet hôte et partagez-le avec les projets de service. +>>- **MTU :** GCP Interconnect prend en charge un **MTU de 1440** pour Partner Interconnect. Assurez-vous qu'OVHcloud Connect et les VXC opérateur utilisent des paramètres MTU correspondants. +>> +>> Pour plus d'informations, veuillez consulter la [documentation GCP Interconnect](https://cloud.google.com/network-connectivity/docs/interconnect) et la [documentation GCP Cloud Router](https://cloud.google.com/network-connectivity/docs/router) + +### Et ensuite ? + +- [Architecture simple](../4.1_simple) pour les cas d'usage non critiques +- [Superviser vos connexions](../3.9_monitor) +- [Configuration Multi-AZ](../1.5_multi_az) pour la résilience côté OVHcloud + +### Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/4.2_resilient/meta.yaml b/pages/network/ovhcloud_connect/4.2_resilient/meta.yaml new file mode 100644 index 00000000000..2b81fa18d90 --- /dev/null +++ b/pages/network/ovhcloud_connect/4.2_resilient/meta.yaml @@ -0,0 +1,2 @@ +id: e5f58472-d268-4e45-b6c8-d17f4041add1 +full_slug: network-ovhcloud-connect-resilient-architecture diff --git a/pages/network/ovhcloud_connect/5_faq/guide.en-gb.md b/pages/network/ovhcloud_connect/5_faq/guide.en-gb.md new file mode 100644 index 00000000000..32c5cb365c9 --- /dev/null +++ b/pages/network/ovhcloud_connect/5_faq/guide.en-gb.md @@ -0,0 +1,244 @@ +--- +title: 'OVHcloud Connect - Frequently Asked Questions (FAQ)' +excerpt: 'Find answers to the most common questions about OVHcloud Connect' +updated: 2026-02-18 +--- + +## General + +### What is OVHcloud Connect? + +OVHcloud Connect (OCC) is a dedicated, private network connection between your infrastructure and OVHcloud. It bypasses the public internet, providing **lower latency, higher bandwidth, and improved security** compared to VPN or internet-based connections. + +See [What is OVHcloud Connect?](../1.1_introduction_to_ovhcloud_connect/guide.en-gb.md) for a full overview. + +### What is the difference between Direct and Provider? + +| | OVHcloud Connect Direct | OVHcloud Connect Provider | +|---|---|---| +| Physical connection | You manage the cross-connect at the PoP | Provider manages the last-mile connection | +| Speed | 1 Gbps or 10 Gbps | 1 Gbps or 10 Gbps | +| Lead time | Days–weeks (cross-connect provisioning) | Minutes–hours (provider virtual circuit) | +| Best for | Organisations with colocation presence | Multi-cloud, remote sites, faster deployment | + +### Which providers are supported? + +OVHcloud Connect Provider works with: + +- **Megaport** — VXC and MCR (Cloud Router) +- **Equinix Fabric** — Virtual connections +- **Console Connect** (PCCW Global) — On-demand connections + +See [Providers](../1.3_providers/guide.en-gb.md) for details. + +### Where is OVHcloud Connect available? + +OVHcloud Connect is available in major PoP locations across Europe, North America, and Asia-Pacific. See [PoP locations and regions](../1.4_pop_locations_regions/guide.en-gb.md) for the full list. + +### Can OVHcloud host my router? + +No. OVHcloud does not host customer networking equipment. To use OVHcloud Connect Direct, you must have your **own rack space (a bay)** in a data centre where OVHcloud has a point of presence, with your router installed and operated by you. You can then order an OVHcloud Connect Direct service and a cross-connect between your bay and the OVHcloud PoP within that facility. + +If you do not have a presence in an OVHcloud PoP, use [OVHcloud Connect Provider](../3.2_order_provider/guide.en-gb.md) instead — your provider handles the last-mile connectivity on your behalf. + +--- + +## Ordering & billing + +### How do I order OVHcloud Connect? + +- **Direct**: [Order a Direct connection](../3.1_order_direct/guide.en-gb.md) +- **Provider**: [Order a Provider connection](../3.2_order_provider/guide.en-gb.md) + +You can order through the OVHcloud Control Panel, the API, or Terraform. + +### How long before my OVHcloud Connect service is delivered? + +**Direct:** + +- The **Letter of Authorization (LOA)** is issued **within minutes** of the order. +- You then have **60 days** to finalize the interconnection: order the cross-connect from your data centre operator, and physically connect your equipment to the OVHcloud patch panel. +- The service is delivered as soon as OVHcloud detects light on the port. If no light is detected within 60 days, the service is nevertheless considered operational and **billing starts**. + +**Provider:** + +- OVHcloud generates a **pairing key** (service key) immediately after the order. +- The service is delivered as soon as your provider consumes the pairing key and provisions the virtual circuit — typically within **minutes to hours** for on-demand providers such as Megaport, Equinix Fabric, or Console Connect. + +### How is OVHcloud Connect billed? + +OVHcloud Connect is billed monthly based on: + +- **Connection type** (Direct or Provider) +- **Bandwidth** (1 Gbps or 10 Gbps) +- **Number of services** + +Provider connections may also incur charges from the provider (Megaport, Equinix, etc.). Check the [OVHcloud pricing page](https://www.ovhcloud.com/en/network/ovhcloud-connect/) for current rates. + +### Can I upgrade bandwidth without downtime? + +No. Bandwidth changes require ordering a new service at the desired speed and migrating traffic. Plan the migration during a maintenance window. + +### How do I cancel a service? + +- **Direct**: [Cancel a Direct connection](../3.3_cancel_direct/guide.en-gb.md) +- **Provider**: [Cancel a Provider connection](../3.4_cancel_provider/guide.en-gb.md) + +> **Important:** Always remove the provider virtual circuit and BGP configuration before cancelling the OVHcloud service to avoid routing issues. + +--- + +## Technical + +### What BGP ASN does OVHcloud use? + +OVHcloud uses ASN **35540** for OVHcloud Connect BGP peering. You must configure your side with a different ASN (typically a private ASN in the 64512–65534 range). + +### What is the maximum number of BGP prefixes? + +OVHcloud supports a maximum of **100 prefixes** per BGP session. Aggregate your routes to stay within this limit. If you need more, contact OVHcloud support. + +### Does OVHcloud Connect support IPv6? + +Currently, OVHcloud Connect primarily supports **IPv4**. Check with OVHcloud support for the latest IPv6 availability. + +### What MTU is supported? + +The default MTU is **1500 bytes**. Jumbo frames (9000 bytes) may be supported on Direct connections depending on the PoP — confirm with OVHcloud support before configuring. + +### Can I use OVHcloud Connect with Hosted Private Cloud (VMware)? + +Yes. Associate your OVHcloud Connect service with a vRack, then add your Hosted Private Cloud service to the same vRack. VMware VMs can use the private connection via vRack-attached port groups. + +### Can I use OVHcloud Connect with Public Cloud instances? + +Yes. Attach your Public Cloud project to the same vRack as your OVHcloud Connect service. Assign a vRack private network to your instances to route traffic through the OCC link. + +### What happens if my BGP session goes down? + +If you have a single OVHcloud Connect link, traffic between your network and OVHcloud will stop flowing until BGP is re-established. For production workloads, always use a [resilient architecture](../1.5_multi_az/guide.en-gb.md) with two links and BGP failover. + +### Can I use BFD (Bidirectional Forwarding Detection)? + +BFD support depends on the OVHcloud Connect type and PoP. Contact OVHcloud support to confirm BFD availability for your service. BFD can significantly reduce failover times from ~90 seconds to under 1 second. + +--- + +## Multi-cloud + +### Can I connect AWS, Azure, and GCP to OVHcloud simultaneously? + +Yes. Order separate OVHcloud Connect Provider services and bridge each to the respective cloud: + +- [AWS via Direct Connect](../4.1_simple/4.3.1_aws_simple/guide.en-gb.md) +- [Azure via ExpressRoute](../4.1_simple/4.4.1_azure_simple/guide.en-gb.md) +- [GCP via Interconnect](../4.1_simple/4.5.1_gcp_simple/guide.en-gb.md) + +All can be associated with the same vRack, allowing traffic to flow between all clouds through OVHcloud. + +### Can cloud-to-cloud traffic transit through OVHcloud? + +Technically, if all cloud connections share the same vRack and BGP prefixes are exchanged, traffic could transit through OVHcloud. However, this is **not recommended** for production — use dedicated cloud-to-cloud interconnects (e.g., AWS ↔ Azure) for direct inter-cloud traffic. + +### Do I need a separate vRack for each cloud connection? + +No. You can associate multiple OVHcloud Connect services with the **same vRack**. This allows all connected networks (on-premises, AWS, Azure, GCP) to communicate through the shared vRack. + +--- + +## Resilience & SLA + +### What SLA does OVHcloud Connect offer? + +SLA levels depend on your architecture: + +| Architecture | Typical SLA | +|---|---| +| Single link, single AZ | ~99.9% | +| Dual links, Multi-AZ | ~99.95%–99.99% | + +See [SLAs](../1.7_slas/guide.en-gb.md) for full details and conditions. + +### How do I set up a resilient connection? + +Order two OVHcloud Connect services at **different PoPs**, associate both with the same vRack, and configure BGP failover with Local Preference and AS-path prepending. + +Tutorials: +- [On-premises resilient](../4.2_resilient/4.1.2_onprem_resilient/guide.en-gb.md) +- [WAN resilient](../4.2_resilient/4.2.2_wan_resilient/guide.en-gb.md) +- [AWS resilient](../4.2_resilient/4.3.2_aws_resilient/guide.en-gb.md) +- [Azure resilient](../4.2_resilient/4.4.2_azure_resilient/guide.en-gb.md) +- [GCP resilient](../4.2_resilient/4.5.2_gcp_resilient/guide.en-gb.md) + +### How long does BGP failover take? + +With default BGP timers (hold time = 90 seconds), failover can take **30–90 seconds**. With aggressive timers or BFD enabled, failover can be **under 1 second**. + +--- + +## Troubleshooting + +### My connection is ordered but not active + +| Possible cause | Action | +|---|---| +| Cross-connect not completed (Direct) | Contact your colocation provider; check LOA status | +| Provider VXC not provisioned (Provider) | Check provider portal; ensure pairing key is correct | +| BGP not configured | [Configure BGP](../3.7_occ_l3_bgp/guide.en-gb.md) | +| vRack not associated | [Associate vRack](../3.5_associate_vrack/guide.en-gb.md) | + +### I can see the BGP session but have no reachability + +- Verify that **routes are being exchanged** (check `show ip bgp summary` or the OVHcloud API). +- Ensure **subnets are correct** and non-overlapping. +- Check for **firewall rules** blocking traffic on either side. +- Verify **VLAN tagging** matches between your equipment and OVHcloud. + +### Traffic is slow or experiencing packet loss + +- Check interface errors and CRC counts on your router. +- Verify the **bandwidth** of your OVHcloud Connect matches your traffic load. +- Look for **MTU mismatches** causing fragmentation. +- Use the [monitoring guide](../3.9_monitor/guide.en-gb.md) to check link health. + +### How do I open a support ticket? + +1. Go to the [OVHcloud Control Panel](https://www.ovh.com/manager/). +2. Click **Support** → **Create a ticket**. +3. Select **Network** → **OVHcloud Connect**. +4. Include your service name, error details, and any diagnostic output. + +See [Incident follow-up](../3.10_incident_followup/guide.en-gb.md) for detailed escalation procedures. + +--- + +## Automation + +### Can I manage OVHcloud Connect with Terraform? + +Yes. Use the [OVHcloud Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest) (version ≥ 2.7.0) to manage OVHcloud Connect resources. See [Automation](../1.6_automation/guide.en-gb.md) for examples. + +### Is there an API for OVHcloud Connect? + +Yes. The OVHcloud API provides full lifecycle management: + +- **EU endpoint**: `https://eu.api.ovh.com/v1/ovhCloudConnect/` +- **CA endpoint**: `https://ca.api.ovh.com/v1/ovhCloudConnect/` + +Explore the API at [api.ovh.com/console](https://api.ovh.com/console/#/ovhCloudConnect). + +See [Automation](../1.6_automation/guide.en-gb.md) for SDK and API examples. + +--- + +## Still have questions? + +- Browse the [full documentation](../1.1_introduction_to_ovhcloud_connect/guide.en-gb.md) +- Check the [OVHcloud Community](https://community.ovh.com/) +- Contact [OVHcloud Support](https://www.ovh.com/manager/) via the Control Panel + +## Go further + +If you would like training or technical assistance for the implementation of our solutions, contact your sales representative or click [this link](/links/professional-services) to get a quote and request a personalized analysis of your project from our Professional Services team experts. + +Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/5_faq/guide.fr-fr.md b/pages/network/ovhcloud_connect/5_faq/guide.fr-fr.md new file mode 100644 index 00000000000..0151af5f0aa --- /dev/null +++ b/pages/network/ovhcloud_connect/5_faq/guide.fr-fr.md @@ -0,0 +1,244 @@ +--- +title: 'OVHcloud Connect - Foire aux questions (FAQ)' +excerpt: 'Trouvez des réponses aux questions les plus fréquentes sur OVHcloud Connect' +updated: 2026-02-18 +--- + +## Général + +### Qu'est-ce qu'OVHcloud Connect ? + +OVHcloud Connect (OCC) est une connexion réseau privée et dédiée entre votre infrastructure et OVHcloud. Elle contourne l'internet public et offre une **latence plus faible, une bande passante plus élevée et une sécurité renforcée** par rapport aux connexions VPN ou via internet. + +Consultez [Qu'est-ce qu'OVHcloud Connect ?](../1.1_introduction_to_ovhcloud_connect/guide.fr-fr.md) pour une présentation complète. + +### Quelle est la différence entre Direct et Provider ? + +| | OVHcloud Connect Direct | OVHcloud Connect Provider | +|---|---|---| +| Connexion physique | Vous gérez le cross-connect au PoP | Le fournisseur gère la connexion du dernier kilomètre | +| Débit | 1 Gbps ou 10 Gbps | 1 Gbps ou 10 Gbps | +| Délai de mise en service | Jours à semaines (provisionnement du cross-connect) | Minutes à heures (circuit virtuel du fournisseur) | +| Idéal pour | Organisations disposant d'une présence en colocation | Multi-cloud, sites distants, déploiement plus rapide | + +### Quels fournisseurs sont pris en charge ? + +OVHcloud Connect Provider fonctionne avec : + +- **Megaport** — VXC et MCR (Cloud Router) +- **Equinix Fabric** — Connexions virtuelles +- **Console Connect** (PCCW Global) — Connexions à la demande + +Consultez [Fournisseurs](../1.3_providers/guide.fr-fr.md) pour plus de détails. + +### Où OVHcloud Connect est-il disponible ? + +OVHcloud Connect est disponible dans les principaux Points de présence (PoP) en Europe, en Amérique du Nord et en Asie-Pacifique. Consultez [Localisations des PoP et régions](../1.4_pop_locations_regions/guide.fr-fr.md) pour la liste complète. + +### OVHcloud peut-il héberger mon routeur ? + +Non. OVHcloud n'héberge pas l'équipement réseau des clients. Pour utiliser OVHcloud Connect Direct, vous devez disposer de **votre propre espace en baie** dans un datacenter où OVHcloud dispose d'un point de présence, avec votre routeur installé et exploité par vos soins. Vous pouvez ensuite commander un service OVHcloud Connect Direct ainsi qu'un cross-connect entre votre baie et le PoP OVHcloud à l'intérieur de ce site. + +Si vous n'avez pas de présence dans un PoP OVHcloud, utilisez plutôt [OVHcloud Connect Provider](../3.2_order_provider/guide.fr-fr.md) — votre fournisseur gérera la connectivité du dernier kilomètre pour vous. + +--- + +## Commande et facturation + +### Comment commander OVHcloud Connect ? + +- **Direct** : [Commander une connexion Direct](../3.1_order_direct/guide.fr-fr.md) +- **Provider** : [Commander une connexion Provider](../3.2_order_provider/guide.fr-fr.md) + +Vous pouvez commander via l'espace client OVHcloud, l'API ou Terraform. + +### Combien de temps faut-il pour que mon service OVHcloud Connect soit livré ? + +**Direct :** + +- La **lettre d'autorisation (LOA)** est émise **en quelques minutes** après la commande. +- Vous disposez ensuite de **60 jours** pour finaliser l'interconnexion : commander le cross-connect auprès de l'opérateur de votre datacenter et raccorder physiquement votre équipement au panneau de brassage OVHcloud. +- Le service est livré dès qu'OVHcloud détecte de la lumière sur le port. Si aucune lumière n'est détectée dans les 60 jours, le service est néanmoins considéré comme opérationnel et **la facturation démarre**. + +**Provider :** + +- OVHcloud génère une **clé d'appairage** (clé de service) immédiatement après la commande. +- Le service est livré dès que votre fournisseur consomme la clé d'appairage et provisionne le circuit virtuel — généralement en **quelques minutes à quelques heures** chez les fournisseurs à la demande tels que Megaport, Equinix Fabric ou Console Connect. + +### Comment OVHcloud Connect est-il facturé ? + +OVHcloud Connect est facturé mensuellement en fonction de : + +- **Type de connexion** (Direct ou Provider) +- **Bande passante** (1 Gbps ou 10 Gbps) +- **Nombre de services** + +Les connexions Provider peuvent également entraîner des frais de la part du fournisseur (Megaport, Equinix, etc.). Consultez la [page de tarification OVHcloud](https://www.ovhcloud.com/fr/network/ovhcloud-connect/) pour les tarifs en vigueur. + +### Puis-je augmenter la bande passante sans interruption ? + +Non. Les changements de bande passante nécessitent la commande d'un nouveau service au débit souhaité ainsi que la migration du trafic. Planifiez la migration pendant une fenêtre de maintenance. + +### Comment résilier un service ? + +- **Direct** : [Résilier une connexion Direct](../3.3_cancel_direct/guide.fr-fr.md) +- **Provider** : [Résilier une connexion Provider](../3.4_cancel_provider/guide.fr-fr.md) + +> **Important :** retirez toujours le circuit virtuel du fournisseur et la configuration BGP avant de résilier le service OVHcloud, afin d'éviter des problèmes de routage. + +--- + +## Technique + +### Quel ASN BGP OVHcloud utilise-t-il ? + +OVHcloud utilise l'ASN **35540** pour le peering BGP d'OVHcloud Connect. Vous devez configurer votre côté avec un ASN différent (généralement un ASN privé dans la plage 64512–65534). + +### Quel est le nombre maximal de préfixes BGP ? + +OVHcloud prend en charge un maximum de **100 préfixes** par session BGP. Agrégez vos routes pour rester dans cette limite. Si vous avez besoin de plus, contactez le support OVHcloud. + +### OVHcloud Connect prend-il en charge IPv6 ? + +Actuellement, OVHcloud Connect prend en charge principalement **IPv4**. Vérifiez auprès du support OVHcloud la disponibilité d'IPv6 la plus récente. + +### Quel MTU est pris en charge ? + +Le MTU par défaut est de **1500 octets**. Les jumbo frames (9000 octets) peuvent être pris en charge sur les connexions Direct selon le PoP — confirmez-le avec le support OVHcloud avant configuration. + +### Puis-je utiliser OVHcloud Connect avec Hosted Private Cloud (VMware) ? + +Oui. Associez votre service OVHcloud Connect à un vRack, puis ajoutez votre service Hosted Private Cloud au même vRack. Les VM VMware peuvent utiliser la connexion privée via les port groups attachés au vRack. + +### Puis-je utiliser OVHcloud Connect avec des instances Public Cloud ? + +Oui. Attachez votre projet Public Cloud au même vRack que votre service OVHcloud Connect. Affectez un réseau privé vRack à vos instances pour faire transiter le trafic via le lien OCC. + +### Que se passe-t-il si ma session BGP tombe ? + +Si vous disposez d'un seul lien OVHcloud Connect, le trafic entre votre réseau et OVHcloud cessera de circuler tant que la session BGP n'est pas rétablie. Pour les charges de production, utilisez toujours une [architecture résiliente](../1.5_multi_az/guide.fr-fr.md) avec deux liens et un basculement BGP. + +### Puis-je utiliser BFD (Bidirectional Forwarding Detection) ? + +La prise en charge de BFD dépend du type d'OVHcloud Connect et du PoP. Contactez le support OVHcloud pour confirmer la disponibilité de BFD pour votre service. BFD peut réduire significativement les délais de basculement, d'environ 90 secondes à moins d'une seconde. + +--- + +## Multi-cloud + +### Puis-je connecter AWS, Azure et GCP à OVHcloud simultanément ? + +Oui. Commandez des services OVHcloud Connect Provider distincts et reliez chacun au cloud correspondant : + +- [AWS via Direct Connect](../4.1_simple/4.3.1_aws_simple/guide.fr-fr.md) +- [Azure via ExpressRoute](../4.1_simple/4.4.1_azure_simple/guide.fr-fr.md) +- [GCP via Interconnect](../4.1_simple/4.5.1_gcp_simple/guide.fr-fr.md) + +Tous peuvent être associés au même vRack, ce qui permet au trafic de circuler entre l'ensemble des clouds via OVHcloud. + +### Le trafic cloud-à-cloud peut-il transiter par OVHcloud ? + +Techniquement, si toutes les connexions cloud partagent le même vRack et que les préfixes BGP sont échangés, le trafic peut transiter par OVHcloud. Cependant, cela n'est **pas recommandé** en production — utilisez des interconnexions cloud-à-cloud dédiées (par exemple AWS ↔ Azure) pour le trafic direct entre clouds. + +### Ai-je besoin d'un vRack distinct pour chaque connexion cloud ? + +Non. Vous pouvez associer plusieurs services OVHcloud Connect au **même vRack**. Cela permet à tous les réseaux connectés (on-premises, AWS, Azure, GCP) de communiquer via le vRack partagé. + +--- + +## Résilience et SLA + +### Quel SLA propose OVHcloud Connect ? + +Les niveaux de SLA dépendent de votre architecture : + +| Architecture | SLA typique | +|---|---| +| Lien unique, AZ unique | ~99,9 % | +| Doubles liens, Multi-AZ | ~99,95 %–99,99 % | + +Consultez [SLA](../1.7_slas/guide.fr-fr.md) pour les détails complets et les conditions. + +### Comment mettre en place une connexion résiliente ? + +Commandez deux services OVHcloud Connect dans des **PoP différents**, associez les deux au même vRack et configurez le basculement BGP avec Local Preference et AS-path prepending. + +Tutoriels : +- [On-premises résilient](../4.2_resilient/4.1.2_onprem_resilient/guide.fr-fr.md) +- [WAN résilient](../4.2_resilient/4.2.2_wan_resilient/guide.fr-fr.md) +- [AWS résilient](../4.2_resilient/4.3.2_aws_resilient/guide.fr-fr.md) +- [Azure résilient](../4.2_resilient/4.4.2_azure_resilient/guide.fr-fr.md) +- [GCP résilient](../4.2_resilient/4.5.2_gcp_resilient/guide.fr-fr.md) + +### Combien de temps prend un basculement BGP ? + +Avec les timers BGP par défaut (hold time = 90 secondes), le basculement peut prendre **30 à 90 secondes**. Avec des timers agressifs ou BFD activé, le basculement peut s'effectuer en **moins d'une seconde**. + +--- + +## Résolution des problèmes + +### Ma connexion est commandée mais n'est pas active + +| Cause possible | Action | +|---|---| +| Cross-connect non finalisé (Direct) | Contactez votre prestataire de colocation ; vérifiez le statut de la LOA | +| VXC du fournisseur non provisionné (Provider) | Vérifiez le portail du fournisseur ; assurez-vous que la clé d'appairage est correcte | +| BGP non configuré | [Configurer BGP](../3.7_occ_l3_bgp/guide.fr-fr.md) | +| vRack non associé | [Associer un vRack](../3.5_associate_vrack/guide.fr-fr.md) | + +### Je vois la session BGP mais je n'ai pas de joignabilité + +- Vérifiez que **les routes sont bien échangées** (consultez `show ip bgp summary` ou l'API OVHcloud). +- Assurez-vous que **les sous-réseaux sont corrects** et non chevauchants. +- Vérifiez l'absence de **règles de pare-feu** bloquant le trafic d'un côté ou de l'autre. +- Vérifiez que le **marquage VLAN** correspond entre votre équipement et OVHcloud. + +### Le trafic est lent ou subit des pertes de paquets + +- Vérifiez les erreurs d'interface et les compteurs CRC sur votre routeur. +- Vérifiez que la **bande passante** de votre OVHcloud Connect correspond à votre charge de trafic. +- Recherchez les **incompatibilités de MTU** susceptibles de provoquer de la fragmentation. +- Utilisez le [guide de supervision](../3.9_monitor/guide.fr-fr.md) pour vérifier la santé du lien. + +### Comment ouvrir un ticket de support ? + +1. Rendez-vous sur l'[espace client OVHcloud](https://www.ovh.com/manager/). +2. Cliquez sur **Support** puis **Créer un ticket**. +3. Sélectionnez **Réseau** puis **OVHcloud Connect**. +4. Indiquez le nom de votre service, les détails de l'erreur et toute sortie de diagnostic. + +Consultez [Suivi d'incident](../3.10_incident_followup/guide.fr-fr.md) pour les procédures d'escalade détaillées. + +--- + +## Automatisation + +### Puis-je gérer OVHcloud Connect avec Terraform ? + +Oui. Utilisez le [provider Terraform OVHcloud](https://registry.terraform.io/providers/ovh/ovh/latest) (version ≥ 2.7.0) pour gérer les ressources OVHcloud Connect. Consultez [Automatisation](../1.6_automation/guide.fr-fr.md) pour des exemples. + +### Existe-t-il une API pour OVHcloud Connect ? + +Oui. L'API OVHcloud offre une gestion complète du cycle de vie : + +- **Endpoint EU** : `https://eu.api.ovh.com/v1/ovhCloudConnect/` +- **Endpoint CA** : `https://ca.api.ovh.com/v1/ovhCloudConnect/` + +Explorez l'API sur [api.ovh.com/console](https://api.ovh.com/console/#/ovhCloudConnect). + +Consultez [Automatisation](../1.6_automation/guide.fr-fr.md) pour des exemples de SDK et d'API. + +--- + +## Vous avez encore des questions ? + +- Parcourez la [documentation complète](../1.1_introduction_to_ovhcloud_connect/guide.fr-fr.md) +- Consultez la [communauté OVHcloud](https://community.ovh.com/) +- Contactez le [support OVHcloud](https://www.ovh.com/manager/) via l'espace client + +## Aller plus loin + +Pour bénéficier d'une formation ou d'une assistance technique dans la mise en œuvre de nos solutions, contactez votre conseiller commercial ou cliquez sur [ce lien](/links/professional-services) afin d'obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l'équipe Professional Services. + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/meta.yaml b/pages/network/ovhcloud_connect/5_faq/meta.yaml old mode 100755 new mode 100644 similarity index 100% rename from pages/network/ovhcloud_connect/occdedicated-faq/meta.yaml rename to pages/network/ovhcloud_connect/5_faq/meta.yaml diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.de-de.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.de-de.md deleted file mode 100644 index 2246a998b43..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.de-de.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Concepts overview -excerpt: 'Concepts overview - OVHcloud Connect' -updated: 2025-10-29 ---- - -## What is OVHcloud Connect? - -OVHcloud Connect is a private, dedicated connection between your on-premises network and your OVHcloud vRack. It is designed to extend your network and securely connect to your cloud resources, bypassing the public internet. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Benefits of OVHcloud Connect - -### Dedicated service - -Dedicated Mode is a direct connection with OVHcloud devices. You can manage different configurations, from a single connection to a multiple one using LACP (Layer 2) or BGP-ECMP (Layer 3) with port speed at 1Gb or 10Gb. Interface and bandwidth are not shared with other customers. - -### Private connection - -Your traffic is isolated from the Internet. You manage your own VLANs (Layer 2) and/or your own IP addresses (Layer 3). BGP instances are private, and you can configure the ASN you want. - -OVHcloud Connect is connected to your vRack with all compatible services. - -### Network extension - -OVHcloud Connect can be connected either to your WAN or your data centre network, allowing seamless extension to the cloud. This eases hybrid cloud strategies and migrations by keeping your existing VLAN topology or IP addresses. - -### High availability - -Using BGP, you can interconnect your network through multiple Points-of-Presence (PoPs) and reach several OVHcloud data centres. From your vRack, you can configure BGP to enable maximum resiliency with distributed services. - -## Components of OVHcloud Connect - -### PoP - EntryPoint - -Points of Presence are facilities like Equinix, InterXion, Telehouse or Global Switch. The OVHcloud Connect service entry PoP is called *EntryPoint*. - -### DC - EndPoint - -The OVHcloud data centre is the service *EndPoint* of OVHcloud Connect. - -### Cross-connect - -A cross-connection is a physical link (monomode fiber) managed by the local facility team in the PoP. The cross-connection is established in the MMR (Meet-Me Room) between the position given by OVHcloud and the position owned by the customer. The customer must order and manage the cross-connect for OVHcloud Connect Direct. - -### vRack - -The OVHcloud Private Network, available on compute resources between all OVHcloud data centres. It allows you to connect compatible services into a single private network. - -### BGP - -BGP (Border Gateway Protocol) is the routing protocol used in Layer 3 mode to manage routes between your network and the OVHcloud vRack. - -## Principles of OVHcloud Connect - -OVHcloud Connect is based on a virtual link between an *EntryPoint* and an *EndPoint*. The *EntryPoint* is where you want to make the interconnection with OVHcloud. The *EndPoint* is the OVHcloud data centre with your services. You can choose any data centre in the same region as the PoP. - -### Layer 2 Mode (L2) - -The virtual link is a L2 tunnel for OVHcloud Connect L2. Only one PoP/*EntryPoint* with one DC/*EndPoint* can be configured. - -### Layer 3 Mode (L3) - -The virtual link is a full mesh IP network between any PoP/*EntryPoint* and any DC/*EndPoint* of the same region. - -## Accessible PoPs per provider - -The OVHcloud Points of Presence (PoPs) available through each of our cloud service provider partners are outlined in the list present at [this link on our website](/links/network/ovhcloud-connect). - -## Accessible Regions per PoP - -When you establish a connection to OVHcloud Connect, your traffic enters the OVHcloud network through a specific PoP. Each PoP is associated with a geographic zone, and the OVHcloud regions that can be reached from that PoP are limited to the zone in which it is located. Depending on the PoP you select, only a defined set of regions will be available for interconnection. - -The following table lists regions that can be accessed from each PoP location: - -| Zone | OVHcloud Connect PoPs | Accessible OVHcloud Regions | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-asia.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-asia.md deleted file mode 100644 index 2246a998b43..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-asia.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Concepts overview -excerpt: 'Concepts overview - OVHcloud Connect' -updated: 2025-10-29 ---- - -## What is OVHcloud Connect? - -OVHcloud Connect is a private, dedicated connection between your on-premises network and your OVHcloud vRack. It is designed to extend your network and securely connect to your cloud resources, bypassing the public internet. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Benefits of OVHcloud Connect - -### Dedicated service - -Dedicated Mode is a direct connection with OVHcloud devices. You can manage different configurations, from a single connection to a multiple one using LACP (Layer 2) or BGP-ECMP (Layer 3) with port speed at 1Gb or 10Gb. Interface and bandwidth are not shared with other customers. - -### Private connection - -Your traffic is isolated from the Internet. You manage your own VLANs (Layer 2) and/or your own IP addresses (Layer 3). BGP instances are private, and you can configure the ASN you want. - -OVHcloud Connect is connected to your vRack with all compatible services. - -### Network extension - -OVHcloud Connect can be connected either to your WAN or your data centre network, allowing seamless extension to the cloud. This eases hybrid cloud strategies and migrations by keeping your existing VLAN topology or IP addresses. - -### High availability - -Using BGP, you can interconnect your network through multiple Points-of-Presence (PoPs) and reach several OVHcloud data centres. From your vRack, you can configure BGP to enable maximum resiliency with distributed services. - -## Components of OVHcloud Connect - -### PoP - EntryPoint - -Points of Presence are facilities like Equinix, InterXion, Telehouse or Global Switch. The OVHcloud Connect service entry PoP is called *EntryPoint*. - -### DC - EndPoint - -The OVHcloud data centre is the service *EndPoint* of OVHcloud Connect. - -### Cross-connect - -A cross-connection is a physical link (monomode fiber) managed by the local facility team in the PoP. The cross-connection is established in the MMR (Meet-Me Room) between the position given by OVHcloud and the position owned by the customer. The customer must order and manage the cross-connect for OVHcloud Connect Direct. - -### vRack - -The OVHcloud Private Network, available on compute resources between all OVHcloud data centres. It allows you to connect compatible services into a single private network. - -### BGP - -BGP (Border Gateway Protocol) is the routing protocol used in Layer 3 mode to manage routes between your network and the OVHcloud vRack. - -## Principles of OVHcloud Connect - -OVHcloud Connect is based on a virtual link between an *EntryPoint* and an *EndPoint*. The *EntryPoint* is where you want to make the interconnection with OVHcloud. The *EndPoint* is the OVHcloud data centre with your services. You can choose any data centre in the same region as the PoP. - -### Layer 2 Mode (L2) - -The virtual link is a L2 tunnel for OVHcloud Connect L2. Only one PoP/*EntryPoint* with one DC/*EndPoint* can be configured. - -### Layer 3 Mode (L3) - -The virtual link is a full mesh IP network between any PoP/*EntryPoint* and any DC/*EndPoint* of the same region. - -## Accessible PoPs per provider - -The OVHcloud Points of Presence (PoPs) available through each of our cloud service provider partners are outlined in the list present at [this link on our website](/links/network/ovhcloud-connect). - -## Accessible Regions per PoP - -When you establish a connection to OVHcloud Connect, your traffic enters the OVHcloud network through a specific PoP. Each PoP is associated with a geographic zone, and the OVHcloud regions that can be reached from that PoP are limited to the zone in which it is located. Depending on the PoP you select, only a defined set of regions will be available for interconnection. - -The following table lists regions that can be accessed from each PoP location: - -| Zone | OVHcloud Connect PoPs | Accessible OVHcloud Regions | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-au.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-au.md deleted file mode 100644 index 2246a998b43..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-au.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Concepts overview -excerpt: 'Concepts overview - OVHcloud Connect' -updated: 2025-10-29 ---- - -## What is OVHcloud Connect? - -OVHcloud Connect is a private, dedicated connection between your on-premises network and your OVHcloud vRack. It is designed to extend your network and securely connect to your cloud resources, bypassing the public internet. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Benefits of OVHcloud Connect - -### Dedicated service - -Dedicated Mode is a direct connection with OVHcloud devices. You can manage different configurations, from a single connection to a multiple one using LACP (Layer 2) or BGP-ECMP (Layer 3) with port speed at 1Gb or 10Gb. Interface and bandwidth are not shared with other customers. - -### Private connection - -Your traffic is isolated from the Internet. You manage your own VLANs (Layer 2) and/or your own IP addresses (Layer 3). BGP instances are private, and you can configure the ASN you want. - -OVHcloud Connect is connected to your vRack with all compatible services. - -### Network extension - -OVHcloud Connect can be connected either to your WAN or your data centre network, allowing seamless extension to the cloud. This eases hybrid cloud strategies and migrations by keeping your existing VLAN topology or IP addresses. - -### High availability - -Using BGP, you can interconnect your network through multiple Points-of-Presence (PoPs) and reach several OVHcloud data centres. From your vRack, you can configure BGP to enable maximum resiliency with distributed services. - -## Components of OVHcloud Connect - -### PoP - EntryPoint - -Points of Presence are facilities like Equinix, InterXion, Telehouse or Global Switch. The OVHcloud Connect service entry PoP is called *EntryPoint*. - -### DC - EndPoint - -The OVHcloud data centre is the service *EndPoint* of OVHcloud Connect. - -### Cross-connect - -A cross-connection is a physical link (monomode fiber) managed by the local facility team in the PoP. The cross-connection is established in the MMR (Meet-Me Room) between the position given by OVHcloud and the position owned by the customer. The customer must order and manage the cross-connect for OVHcloud Connect Direct. - -### vRack - -The OVHcloud Private Network, available on compute resources between all OVHcloud data centres. It allows you to connect compatible services into a single private network. - -### BGP - -BGP (Border Gateway Protocol) is the routing protocol used in Layer 3 mode to manage routes between your network and the OVHcloud vRack. - -## Principles of OVHcloud Connect - -OVHcloud Connect is based on a virtual link between an *EntryPoint* and an *EndPoint*. The *EntryPoint* is where you want to make the interconnection with OVHcloud. The *EndPoint* is the OVHcloud data centre with your services. You can choose any data centre in the same region as the PoP. - -### Layer 2 Mode (L2) - -The virtual link is a L2 tunnel for OVHcloud Connect L2. Only one PoP/*EntryPoint* with one DC/*EndPoint* can be configured. - -### Layer 3 Mode (L3) - -The virtual link is a full mesh IP network between any PoP/*EntryPoint* and any DC/*EndPoint* of the same region. - -## Accessible PoPs per provider - -The OVHcloud Points of Presence (PoPs) available through each of our cloud service provider partners are outlined in the list present at [this link on our website](/links/network/ovhcloud-connect). - -## Accessible Regions per PoP - -When you establish a connection to OVHcloud Connect, your traffic enters the OVHcloud network through a specific PoP. Each PoP is associated with a geographic zone, and the OVHcloud regions that can be reached from that PoP are limited to the zone in which it is located. Depending on the PoP you select, only a defined set of regions will be available for interconnection. - -The following table lists regions that can be accessed from each PoP location: - -| Zone | OVHcloud Connect PoPs | Accessible OVHcloud Regions | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-ca.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-ca.md deleted file mode 100644 index 2246a998b43..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-ca.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Concepts overview -excerpt: 'Concepts overview - OVHcloud Connect' -updated: 2025-10-29 ---- - -## What is OVHcloud Connect? - -OVHcloud Connect is a private, dedicated connection between your on-premises network and your OVHcloud vRack. It is designed to extend your network and securely connect to your cloud resources, bypassing the public internet. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Benefits of OVHcloud Connect - -### Dedicated service - -Dedicated Mode is a direct connection with OVHcloud devices. You can manage different configurations, from a single connection to a multiple one using LACP (Layer 2) or BGP-ECMP (Layer 3) with port speed at 1Gb or 10Gb. Interface and bandwidth are not shared with other customers. - -### Private connection - -Your traffic is isolated from the Internet. You manage your own VLANs (Layer 2) and/or your own IP addresses (Layer 3). BGP instances are private, and you can configure the ASN you want. - -OVHcloud Connect is connected to your vRack with all compatible services. - -### Network extension - -OVHcloud Connect can be connected either to your WAN or your data centre network, allowing seamless extension to the cloud. This eases hybrid cloud strategies and migrations by keeping your existing VLAN topology or IP addresses. - -### High availability - -Using BGP, you can interconnect your network through multiple Points-of-Presence (PoPs) and reach several OVHcloud data centres. From your vRack, you can configure BGP to enable maximum resiliency with distributed services. - -## Components of OVHcloud Connect - -### PoP - EntryPoint - -Points of Presence are facilities like Equinix, InterXion, Telehouse or Global Switch. The OVHcloud Connect service entry PoP is called *EntryPoint*. - -### DC - EndPoint - -The OVHcloud data centre is the service *EndPoint* of OVHcloud Connect. - -### Cross-connect - -A cross-connection is a physical link (monomode fiber) managed by the local facility team in the PoP. The cross-connection is established in the MMR (Meet-Me Room) between the position given by OVHcloud and the position owned by the customer. The customer must order and manage the cross-connect for OVHcloud Connect Direct. - -### vRack - -The OVHcloud Private Network, available on compute resources between all OVHcloud data centres. It allows you to connect compatible services into a single private network. - -### BGP - -BGP (Border Gateway Protocol) is the routing protocol used in Layer 3 mode to manage routes between your network and the OVHcloud vRack. - -## Principles of OVHcloud Connect - -OVHcloud Connect is based on a virtual link between an *EntryPoint* and an *EndPoint*. The *EntryPoint* is where you want to make the interconnection with OVHcloud. The *EndPoint* is the OVHcloud data centre with your services. You can choose any data centre in the same region as the PoP. - -### Layer 2 Mode (L2) - -The virtual link is a L2 tunnel for OVHcloud Connect L2. Only one PoP/*EntryPoint* with one DC/*EndPoint* can be configured. - -### Layer 3 Mode (L3) - -The virtual link is a full mesh IP network between any PoP/*EntryPoint* and any DC/*EndPoint* of the same region. - -## Accessible PoPs per provider - -The OVHcloud Points of Presence (PoPs) available through each of our cloud service provider partners are outlined in the list present at [this link on our website](/links/network/ovhcloud-connect). - -## Accessible Regions per PoP - -When you establish a connection to OVHcloud Connect, your traffic enters the OVHcloud network through a specific PoP. Each PoP is associated with a geographic zone, and the OVHcloud regions that can be reached from that PoP are limited to the zone in which it is located. Depending on the PoP you select, only a defined set of regions will be available for interconnection. - -The following table lists regions that can be accessed from each PoP location: - -| Zone | OVHcloud Connect PoPs | Accessible OVHcloud Regions | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-gb.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-gb.md deleted file mode 100644 index 2246a998b43..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-gb.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Concepts overview -excerpt: 'Concepts overview - OVHcloud Connect' -updated: 2025-10-29 ---- - -## What is OVHcloud Connect? - -OVHcloud Connect is a private, dedicated connection between your on-premises network and your OVHcloud vRack. It is designed to extend your network and securely connect to your cloud resources, bypassing the public internet. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Benefits of OVHcloud Connect - -### Dedicated service - -Dedicated Mode is a direct connection with OVHcloud devices. You can manage different configurations, from a single connection to a multiple one using LACP (Layer 2) or BGP-ECMP (Layer 3) with port speed at 1Gb or 10Gb. Interface and bandwidth are not shared with other customers. - -### Private connection - -Your traffic is isolated from the Internet. You manage your own VLANs (Layer 2) and/or your own IP addresses (Layer 3). BGP instances are private, and you can configure the ASN you want. - -OVHcloud Connect is connected to your vRack with all compatible services. - -### Network extension - -OVHcloud Connect can be connected either to your WAN or your data centre network, allowing seamless extension to the cloud. This eases hybrid cloud strategies and migrations by keeping your existing VLAN topology or IP addresses. - -### High availability - -Using BGP, you can interconnect your network through multiple Points-of-Presence (PoPs) and reach several OVHcloud data centres. From your vRack, you can configure BGP to enable maximum resiliency with distributed services. - -## Components of OVHcloud Connect - -### PoP - EntryPoint - -Points of Presence are facilities like Equinix, InterXion, Telehouse or Global Switch. The OVHcloud Connect service entry PoP is called *EntryPoint*. - -### DC - EndPoint - -The OVHcloud data centre is the service *EndPoint* of OVHcloud Connect. - -### Cross-connect - -A cross-connection is a physical link (monomode fiber) managed by the local facility team in the PoP. The cross-connection is established in the MMR (Meet-Me Room) between the position given by OVHcloud and the position owned by the customer. The customer must order and manage the cross-connect for OVHcloud Connect Direct. - -### vRack - -The OVHcloud Private Network, available on compute resources between all OVHcloud data centres. It allows you to connect compatible services into a single private network. - -### BGP - -BGP (Border Gateway Protocol) is the routing protocol used in Layer 3 mode to manage routes between your network and the OVHcloud vRack. - -## Principles of OVHcloud Connect - -OVHcloud Connect is based on a virtual link between an *EntryPoint* and an *EndPoint*. The *EntryPoint* is where you want to make the interconnection with OVHcloud. The *EndPoint* is the OVHcloud data centre with your services. You can choose any data centre in the same region as the PoP. - -### Layer 2 Mode (L2) - -The virtual link is a L2 tunnel for OVHcloud Connect L2. Only one PoP/*EntryPoint* with one DC/*EndPoint* can be configured. - -### Layer 3 Mode (L3) - -The virtual link is a full mesh IP network between any PoP/*EntryPoint* and any DC/*EndPoint* of the same region. - -## Accessible PoPs per provider - -The OVHcloud Points of Presence (PoPs) available through each of our cloud service provider partners are outlined in the list present at [this link on our website](/links/network/ovhcloud-connect). - -## Accessible Regions per PoP - -When you establish a connection to OVHcloud Connect, your traffic enters the OVHcloud network through a specific PoP. Each PoP is associated with a geographic zone, and the OVHcloud regions that can be reached from that PoP are limited to the zone in which it is located. Depending on the PoP you select, only a defined set of regions will be available for interconnection. - -The following table lists regions that can be accessed from each PoP location: - -| Zone | OVHcloud Connect PoPs | Accessible OVHcloud Regions | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-ie.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-ie.md deleted file mode 100644 index 2246a998b43..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-ie.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Concepts overview -excerpt: 'Concepts overview - OVHcloud Connect' -updated: 2025-10-29 ---- - -## What is OVHcloud Connect? - -OVHcloud Connect is a private, dedicated connection between your on-premises network and your OVHcloud vRack. It is designed to extend your network and securely connect to your cloud resources, bypassing the public internet. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Benefits of OVHcloud Connect - -### Dedicated service - -Dedicated Mode is a direct connection with OVHcloud devices. You can manage different configurations, from a single connection to a multiple one using LACP (Layer 2) or BGP-ECMP (Layer 3) with port speed at 1Gb or 10Gb. Interface and bandwidth are not shared with other customers. - -### Private connection - -Your traffic is isolated from the Internet. You manage your own VLANs (Layer 2) and/or your own IP addresses (Layer 3). BGP instances are private, and you can configure the ASN you want. - -OVHcloud Connect is connected to your vRack with all compatible services. - -### Network extension - -OVHcloud Connect can be connected either to your WAN or your data centre network, allowing seamless extension to the cloud. This eases hybrid cloud strategies and migrations by keeping your existing VLAN topology or IP addresses. - -### High availability - -Using BGP, you can interconnect your network through multiple Points-of-Presence (PoPs) and reach several OVHcloud data centres. From your vRack, you can configure BGP to enable maximum resiliency with distributed services. - -## Components of OVHcloud Connect - -### PoP - EntryPoint - -Points of Presence are facilities like Equinix, InterXion, Telehouse or Global Switch. The OVHcloud Connect service entry PoP is called *EntryPoint*. - -### DC - EndPoint - -The OVHcloud data centre is the service *EndPoint* of OVHcloud Connect. - -### Cross-connect - -A cross-connection is a physical link (monomode fiber) managed by the local facility team in the PoP. The cross-connection is established in the MMR (Meet-Me Room) between the position given by OVHcloud and the position owned by the customer. The customer must order and manage the cross-connect for OVHcloud Connect Direct. - -### vRack - -The OVHcloud Private Network, available on compute resources between all OVHcloud data centres. It allows you to connect compatible services into a single private network. - -### BGP - -BGP (Border Gateway Protocol) is the routing protocol used in Layer 3 mode to manage routes between your network and the OVHcloud vRack. - -## Principles of OVHcloud Connect - -OVHcloud Connect is based on a virtual link between an *EntryPoint* and an *EndPoint*. The *EntryPoint* is where you want to make the interconnection with OVHcloud. The *EndPoint* is the OVHcloud data centre with your services. You can choose any data centre in the same region as the PoP. - -### Layer 2 Mode (L2) - -The virtual link is a L2 tunnel for OVHcloud Connect L2. Only one PoP/*EntryPoint* with one DC/*EndPoint* can be configured. - -### Layer 3 Mode (L3) - -The virtual link is a full mesh IP network between any PoP/*EntryPoint* and any DC/*EndPoint* of the same region. - -## Accessible PoPs per provider - -The OVHcloud Points of Presence (PoPs) available through each of our cloud service provider partners are outlined in the list present at [this link on our website](/links/network/ovhcloud-connect). - -## Accessible Regions per PoP - -When you establish a connection to OVHcloud Connect, your traffic enters the OVHcloud network through a specific PoP. Each PoP is associated with a geographic zone, and the OVHcloud regions that can be reached from that PoP are limited to the zone in which it is located. Depending on the PoP you select, only a defined set of regions will be available for interconnection. - -The following table lists regions that can be accessed from each PoP location: - -| Zone | OVHcloud Connect PoPs | Accessible OVHcloud Regions | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-sg.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-sg.md deleted file mode 100644 index 2246a998b43..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-sg.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Concepts overview -excerpt: 'Concepts overview - OVHcloud Connect' -updated: 2025-10-29 ---- - -## What is OVHcloud Connect? - -OVHcloud Connect is a private, dedicated connection between your on-premises network and your OVHcloud vRack. It is designed to extend your network and securely connect to your cloud resources, bypassing the public internet. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Benefits of OVHcloud Connect - -### Dedicated service - -Dedicated Mode is a direct connection with OVHcloud devices. You can manage different configurations, from a single connection to a multiple one using LACP (Layer 2) or BGP-ECMP (Layer 3) with port speed at 1Gb or 10Gb. Interface and bandwidth are not shared with other customers. - -### Private connection - -Your traffic is isolated from the Internet. You manage your own VLANs (Layer 2) and/or your own IP addresses (Layer 3). BGP instances are private, and you can configure the ASN you want. - -OVHcloud Connect is connected to your vRack with all compatible services. - -### Network extension - -OVHcloud Connect can be connected either to your WAN or your data centre network, allowing seamless extension to the cloud. This eases hybrid cloud strategies and migrations by keeping your existing VLAN topology or IP addresses. - -### High availability - -Using BGP, you can interconnect your network through multiple Points-of-Presence (PoPs) and reach several OVHcloud data centres. From your vRack, you can configure BGP to enable maximum resiliency with distributed services. - -## Components of OVHcloud Connect - -### PoP - EntryPoint - -Points of Presence are facilities like Equinix, InterXion, Telehouse or Global Switch. The OVHcloud Connect service entry PoP is called *EntryPoint*. - -### DC - EndPoint - -The OVHcloud data centre is the service *EndPoint* of OVHcloud Connect. - -### Cross-connect - -A cross-connection is a physical link (monomode fiber) managed by the local facility team in the PoP. The cross-connection is established in the MMR (Meet-Me Room) between the position given by OVHcloud and the position owned by the customer. The customer must order and manage the cross-connect for OVHcloud Connect Direct. - -### vRack - -The OVHcloud Private Network, available on compute resources between all OVHcloud data centres. It allows you to connect compatible services into a single private network. - -### BGP - -BGP (Border Gateway Protocol) is the routing protocol used in Layer 3 mode to manage routes between your network and the OVHcloud vRack. - -## Principles of OVHcloud Connect - -OVHcloud Connect is based on a virtual link between an *EntryPoint* and an *EndPoint*. The *EntryPoint* is where you want to make the interconnection with OVHcloud. The *EndPoint* is the OVHcloud data centre with your services. You can choose any data centre in the same region as the PoP. - -### Layer 2 Mode (L2) - -The virtual link is a L2 tunnel for OVHcloud Connect L2. Only one PoP/*EntryPoint* with one DC/*EndPoint* can be configured. - -### Layer 3 Mode (L3) - -The virtual link is a full mesh IP network between any PoP/*EntryPoint* and any DC/*EndPoint* of the same region. - -## Accessible PoPs per provider - -The OVHcloud Points of Presence (PoPs) available through each of our cloud service provider partners are outlined in the list present at [this link on our website](/links/network/ovhcloud-connect). - -## Accessible Regions per PoP - -When you establish a connection to OVHcloud Connect, your traffic enters the OVHcloud network through a specific PoP. Each PoP is associated with a geographic zone, and the OVHcloud regions that can be reached from that PoP are limited to the zone in which it is located. Depending on the PoP you select, only a defined set of regions will be available for interconnection. - -The following table lists regions that can be accessed from each PoP location: - -| Zone | OVHcloud Connect PoPs | Accessible OVHcloud Regions | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-us.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-us.md deleted file mode 100644 index 2246a998b43..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.en-us.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Concepts overview -excerpt: 'Concepts overview - OVHcloud Connect' -updated: 2025-10-29 ---- - -## What is OVHcloud Connect? - -OVHcloud Connect is a private, dedicated connection between your on-premises network and your OVHcloud vRack. It is designed to extend your network and securely connect to your cloud resources, bypassing the public internet. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Benefits of OVHcloud Connect - -### Dedicated service - -Dedicated Mode is a direct connection with OVHcloud devices. You can manage different configurations, from a single connection to a multiple one using LACP (Layer 2) or BGP-ECMP (Layer 3) with port speed at 1Gb or 10Gb. Interface and bandwidth are not shared with other customers. - -### Private connection - -Your traffic is isolated from the Internet. You manage your own VLANs (Layer 2) and/or your own IP addresses (Layer 3). BGP instances are private, and you can configure the ASN you want. - -OVHcloud Connect is connected to your vRack with all compatible services. - -### Network extension - -OVHcloud Connect can be connected either to your WAN or your data centre network, allowing seamless extension to the cloud. This eases hybrid cloud strategies and migrations by keeping your existing VLAN topology or IP addresses. - -### High availability - -Using BGP, you can interconnect your network through multiple Points-of-Presence (PoPs) and reach several OVHcloud data centres. From your vRack, you can configure BGP to enable maximum resiliency with distributed services. - -## Components of OVHcloud Connect - -### PoP - EntryPoint - -Points of Presence are facilities like Equinix, InterXion, Telehouse or Global Switch. The OVHcloud Connect service entry PoP is called *EntryPoint*. - -### DC - EndPoint - -The OVHcloud data centre is the service *EndPoint* of OVHcloud Connect. - -### Cross-connect - -A cross-connection is a physical link (monomode fiber) managed by the local facility team in the PoP. The cross-connection is established in the MMR (Meet-Me Room) between the position given by OVHcloud and the position owned by the customer. The customer must order and manage the cross-connect for OVHcloud Connect Direct. - -### vRack - -The OVHcloud Private Network, available on compute resources between all OVHcloud data centres. It allows you to connect compatible services into a single private network. - -### BGP - -BGP (Border Gateway Protocol) is the routing protocol used in Layer 3 mode to manage routes between your network and the OVHcloud vRack. - -## Principles of OVHcloud Connect - -OVHcloud Connect is based on a virtual link between an *EntryPoint* and an *EndPoint*. The *EntryPoint* is where you want to make the interconnection with OVHcloud. The *EndPoint* is the OVHcloud data centre with your services. You can choose any data centre in the same region as the PoP. - -### Layer 2 Mode (L2) - -The virtual link is a L2 tunnel for OVHcloud Connect L2. Only one PoP/*EntryPoint* with one DC/*EndPoint* can be configured. - -### Layer 3 Mode (L3) - -The virtual link is a full mesh IP network between any PoP/*EntryPoint* and any DC/*EndPoint* of the same region. - -## Accessible PoPs per provider - -The OVHcloud Points of Presence (PoPs) available through each of our cloud service provider partners are outlined in the list present at [this link on our website](/links/network/ovhcloud-connect). - -## Accessible Regions per PoP - -When you establish a connection to OVHcloud Connect, your traffic enters the OVHcloud network through a specific PoP. Each PoP is associated with a geographic zone, and the OVHcloud regions that can be reached from that PoP are limited to the zone in which it is located. Depending on the PoP you select, only a defined set of regions will be available for interconnection. - -The following table lists regions that can be accessed from each PoP location: - -| Zone | OVHcloud Connect PoPs | Accessible OVHcloud Regions | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.es-es.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.es-es.md deleted file mode 100644 index 2246a998b43..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.es-es.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Concepts overview -excerpt: 'Concepts overview - OVHcloud Connect' -updated: 2025-10-29 ---- - -## What is OVHcloud Connect? - -OVHcloud Connect is a private, dedicated connection between your on-premises network and your OVHcloud vRack. It is designed to extend your network and securely connect to your cloud resources, bypassing the public internet. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Benefits of OVHcloud Connect - -### Dedicated service - -Dedicated Mode is a direct connection with OVHcloud devices. You can manage different configurations, from a single connection to a multiple one using LACP (Layer 2) or BGP-ECMP (Layer 3) with port speed at 1Gb or 10Gb. Interface and bandwidth are not shared with other customers. - -### Private connection - -Your traffic is isolated from the Internet. You manage your own VLANs (Layer 2) and/or your own IP addresses (Layer 3). BGP instances are private, and you can configure the ASN you want. - -OVHcloud Connect is connected to your vRack with all compatible services. - -### Network extension - -OVHcloud Connect can be connected either to your WAN or your data centre network, allowing seamless extension to the cloud. This eases hybrid cloud strategies and migrations by keeping your existing VLAN topology or IP addresses. - -### High availability - -Using BGP, you can interconnect your network through multiple Points-of-Presence (PoPs) and reach several OVHcloud data centres. From your vRack, you can configure BGP to enable maximum resiliency with distributed services. - -## Components of OVHcloud Connect - -### PoP - EntryPoint - -Points of Presence are facilities like Equinix, InterXion, Telehouse or Global Switch. The OVHcloud Connect service entry PoP is called *EntryPoint*. - -### DC - EndPoint - -The OVHcloud data centre is the service *EndPoint* of OVHcloud Connect. - -### Cross-connect - -A cross-connection is a physical link (monomode fiber) managed by the local facility team in the PoP. The cross-connection is established in the MMR (Meet-Me Room) between the position given by OVHcloud and the position owned by the customer. The customer must order and manage the cross-connect for OVHcloud Connect Direct. - -### vRack - -The OVHcloud Private Network, available on compute resources between all OVHcloud data centres. It allows you to connect compatible services into a single private network. - -### BGP - -BGP (Border Gateway Protocol) is the routing protocol used in Layer 3 mode to manage routes between your network and the OVHcloud vRack. - -## Principles of OVHcloud Connect - -OVHcloud Connect is based on a virtual link between an *EntryPoint* and an *EndPoint*. The *EntryPoint* is where you want to make the interconnection with OVHcloud. The *EndPoint* is the OVHcloud data centre with your services. You can choose any data centre in the same region as the PoP. - -### Layer 2 Mode (L2) - -The virtual link is a L2 tunnel for OVHcloud Connect L2. Only one PoP/*EntryPoint* with one DC/*EndPoint* can be configured. - -### Layer 3 Mode (L3) - -The virtual link is a full mesh IP network between any PoP/*EntryPoint* and any DC/*EndPoint* of the same region. - -## Accessible PoPs per provider - -The OVHcloud Points of Presence (PoPs) available through each of our cloud service provider partners are outlined in the list present at [this link on our website](/links/network/ovhcloud-connect). - -## Accessible Regions per PoP - -When you establish a connection to OVHcloud Connect, your traffic enters the OVHcloud network through a specific PoP. Each PoP is associated with a geographic zone, and the OVHcloud regions that can be reached from that PoP are limited to the zone in which it is located. Depending on the PoP you select, only a defined set of regions will be available for interconnection. - -The following table lists regions that can be accessed from each PoP location: - -| Zone | OVHcloud Connect PoPs | Accessible OVHcloud Regions | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.es-us.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.es-us.md deleted file mode 100644 index 2246a998b43..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.es-us.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Concepts overview -excerpt: 'Concepts overview - OVHcloud Connect' -updated: 2025-10-29 ---- - -## What is OVHcloud Connect? - -OVHcloud Connect is a private, dedicated connection between your on-premises network and your OVHcloud vRack. It is designed to extend your network and securely connect to your cloud resources, bypassing the public internet. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Benefits of OVHcloud Connect - -### Dedicated service - -Dedicated Mode is a direct connection with OVHcloud devices. You can manage different configurations, from a single connection to a multiple one using LACP (Layer 2) or BGP-ECMP (Layer 3) with port speed at 1Gb or 10Gb. Interface and bandwidth are not shared with other customers. - -### Private connection - -Your traffic is isolated from the Internet. You manage your own VLANs (Layer 2) and/or your own IP addresses (Layer 3). BGP instances are private, and you can configure the ASN you want. - -OVHcloud Connect is connected to your vRack with all compatible services. - -### Network extension - -OVHcloud Connect can be connected either to your WAN or your data centre network, allowing seamless extension to the cloud. This eases hybrid cloud strategies and migrations by keeping your existing VLAN topology or IP addresses. - -### High availability - -Using BGP, you can interconnect your network through multiple Points-of-Presence (PoPs) and reach several OVHcloud data centres. From your vRack, you can configure BGP to enable maximum resiliency with distributed services. - -## Components of OVHcloud Connect - -### PoP - EntryPoint - -Points of Presence are facilities like Equinix, InterXion, Telehouse or Global Switch. The OVHcloud Connect service entry PoP is called *EntryPoint*. - -### DC - EndPoint - -The OVHcloud data centre is the service *EndPoint* of OVHcloud Connect. - -### Cross-connect - -A cross-connection is a physical link (monomode fiber) managed by the local facility team in the PoP. The cross-connection is established in the MMR (Meet-Me Room) between the position given by OVHcloud and the position owned by the customer. The customer must order and manage the cross-connect for OVHcloud Connect Direct. - -### vRack - -The OVHcloud Private Network, available on compute resources between all OVHcloud data centres. It allows you to connect compatible services into a single private network. - -### BGP - -BGP (Border Gateway Protocol) is the routing protocol used in Layer 3 mode to manage routes between your network and the OVHcloud vRack. - -## Principles of OVHcloud Connect - -OVHcloud Connect is based on a virtual link between an *EntryPoint* and an *EndPoint*. The *EntryPoint* is where you want to make the interconnection with OVHcloud. The *EndPoint* is the OVHcloud data centre with your services. You can choose any data centre in the same region as the PoP. - -### Layer 2 Mode (L2) - -The virtual link is a L2 tunnel for OVHcloud Connect L2. Only one PoP/*EntryPoint* with one DC/*EndPoint* can be configured. - -### Layer 3 Mode (L3) - -The virtual link is a full mesh IP network between any PoP/*EntryPoint* and any DC/*EndPoint* of the same region. - -## Accessible PoPs per provider - -The OVHcloud Points of Presence (PoPs) available through each of our cloud service provider partners are outlined in the list present at [this link on our website](/links/network/ovhcloud-connect). - -## Accessible Regions per PoP - -When you establish a connection to OVHcloud Connect, your traffic enters the OVHcloud network through a specific PoP. Each PoP is associated with a geographic zone, and the OVHcloud regions that can be reached from that PoP are limited to the zone in which it is located. Depending on the PoP you select, only a defined set of regions will be available for interconnection. - -The following table lists regions that can be accessed from each PoP location: - -| Zone | OVHcloud Connect PoPs | Accessible OVHcloud Regions | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.fr-ca.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.fr-ca.md deleted file mode 100644 index f1d77f4838b..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.fr-ca.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -title: Présentation des concepts -excerpt: Présentation des concepts nécessaires à la compréhension de l’offre OVHcloud Connect -updated: 2025-10-29 ---- - -## Qu'est-ce que OVHcloud Connect ? - -OVHcloud Connect est une connexion privée et dédiée entre votre réseau sur site et votre vRack OVHcloud. Il est conçu pour étendre votre réseau et vous connecter de manière sécurisée à vos ressources cloud, en contournant l'internet public. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Avantages de l'offre - -### Dédié - -Le mode dédié est une connexion directe avec les services OVHcloud. Vous pouvez gérer différentes configurations, d'une connexion unique à une connexion multiple à l'aide de LACP (L2) ou BGP-ECMP (L3) avec une vitesse de port de 1 Gbps ou 10 Gbps. L'interface et la bande-passante ne sont pas partagées avec d'autres clients. - -### Privé - -Votre trafic est isolé d'Internet, vous gérez vos propres VLAN (L2) et/ou vos propres adresses IP (L3). Même les instances BGP sont privées et vous pouvez configurer l'ASN de votre choix. -OVHcloud Connect est connecté à votre vRack avec tous les services compatibles. - -### Extension réseau - -OVHcloud Connect peut être connecté à votre réseau WAN ou à votre réseau de Datacentres. permettant une extension transparente vers le cloud. Ceci facilite les stratégies de cloud hybride et les migrations en conservant la topologie de vos VLAN existants ou vos adresses IP. - -### Haute disponibilité - -Grâce à BGP, vous pouvez interconnecter votre réseau via plusieurs PoP et atteindre plusieurs Datacentres OVHcloud. À partir du vRack, configurez BGP pour permettre une résilience maximale avec les services distribués. - -## Composants - -### PoP - EntryPoint - -Les points de présence (PoP) sont des installations comme Equinix, InterXion, Telehouse ou Global Switch. Le PoP est l'entrée de service d'OVHcloud Connect: nous l'appelons EntryPoint. - -### DC - EndPoint - -Le Datacentre (DC) OVHcloud est la terminaison du service, le EndPoint. - -### Interconnexion - -Une interconnexion (Cross-connect) est une liaison physique (fibre monomode) gérée par les équipes d'installation dans le PoP. L'interconnexion est établie dans la MMR (Meet-Me-Room) entre la position donnée par OVHcloud et la position détenue par le client. Dans le cas d'une offre OVHcloud Connect Direct, le client doit commander et gérer l'interconnexion. - -### vRack - -Réseau privé OVHcloud, disponible sur les ressources Cloud entre tous les Datacentres OVHcloud. - -### BGP - -Protocole de routage à utiliser lors de l'utilisation du mode de L3. - -## Principes - -OVHcloud Connect est basé sur une liaison virtuelle entre un EntryPoint et un EndPoint. Le EntryPoint est là où vous voulez établir l'interconnexion avec OVHcloud. Le EndPoint est le Datacentre OVHcloud où sont situés vos services. Vous pouvez choisir n'importe quel Datacentre de la même région que le PoP. - -### Layer 2 (L2) - -La liaison virtuelle est un tunnel L2 pour OVHcloud Connect L2. Seul un PoP/EntryPoint avec 1 DC/EndPoint peut être configuré. - -### Layer 3 (L3) - -La liaison virtuelle est un réseau IP à maillage complet entre tout PoP/EntryPoint et tout DC/EndPoint de la même région. - -## PoPs accessibles par fournisseur de service - -La liste disponible sur [ce lien de notre site web](/links/network/ovhcloud-connect) présente les PoPs d'OVHcloud accessibles via chacun de nos partenaires fournisseurs de services cloud. - -## Régions accessibles par PoP - -Lorsque vous établissez une connexion à OVHcloud Connect, votre trafic entre dans le réseau OVHcloud via un PoP spécifique. Chaque PoP est associé à une zone géographique, et les régions OVHcloud qui peuvent être atteintes depuis ce PoP sont limitées à la zone dans laquelle il se trouve. Selon le PoP que vous choisissez, seul un ensemble de régions prédéfini sera disponible pour l'interconnexion. - -Le tableau suivant répertorie les régions accessibles depuis chaque PoP : - -| Zone | PoPs OVHcloud Connect | Régions OVHcloud accessibles | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.fr-fr.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.fr-fr.md deleted file mode 100644 index f1d77f4838b..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.fr-fr.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -title: Présentation des concepts -excerpt: Présentation des concepts nécessaires à la compréhension de l’offre OVHcloud Connect -updated: 2025-10-29 ---- - -## Qu'est-ce que OVHcloud Connect ? - -OVHcloud Connect est une connexion privée et dédiée entre votre réseau sur site et votre vRack OVHcloud. Il est conçu pour étendre votre réseau et vous connecter de manière sécurisée à vos ressources cloud, en contournant l'internet public. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Avantages de l'offre - -### Dédié - -Le mode dédié est une connexion directe avec les services OVHcloud. Vous pouvez gérer différentes configurations, d'une connexion unique à une connexion multiple à l'aide de LACP (L2) ou BGP-ECMP (L3) avec une vitesse de port de 1 Gbps ou 10 Gbps. L'interface et la bande-passante ne sont pas partagées avec d'autres clients. - -### Privé - -Votre trafic est isolé d'Internet, vous gérez vos propres VLAN (L2) et/ou vos propres adresses IP (L3). Même les instances BGP sont privées et vous pouvez configurer l'ASN de votre choix. -OVHcloud Connect est connecté à votre vRack avec tous les services compatibles. - -### Extension réseau - -OVHcloud Connect peut être connecté à votre réseau WAN ou à votre réseau de Datacentres. permettant une extension transparente vers le cloud. Ceci facilite les stratégies de cloud hybride et les migrations en conservant la topologie de vos VLAN existants ou vos adresses IP. - -### Haute disponibilité - -Grâce à BGP, vous pouvez interconnecter votre réseau via plusieurs PoP et atteindre plusieurs Datacentres OVHcloud. À partir du vRack, configurez BGP pour permettre une résilience maximale avec les services distribués. - -## Composants - -### PoP - EntryPoint - -Les points de présence (PoP) sont des installations comme Equinix, InterXion, Telehouse ou Global Switch. Le PoP est l'entrée de service d'OVHcloud Connect: nous l'appelons EntryPoint. - -### DC - EndPoint - -Le Datacentre (DC) OVHcloud est la terminaison du service, le EndPoint. - -### Interconnexion - -Une interconnexion (Cross-connect) est une liaison physique (fibre monomode) gérée par les équipes d'installation dans le PoP. L'interconnexion est établie dans la MMR (Meet-Me-Room) entre la position donnée par OVHcloud et la position détenue par le client. Dans le cas d'une offre OVHcloud Connect Direct, le client doit commander et gérer l'interconnexion. - -### vRack - -Réseau privé OVHcloud, disponible sur les ressources Cloud entre tous les Datacentres OVHcloud. - -### BGP - -Protocole de routage à utiliser lors de l'utilisation du mode de L3. - -## Principes - -OVHcloud Connect est basé sur une liaison virtuelle entre un EntryPoint et un EndPoint. Le EntryPoint est là où vous voulez établir l'interconnexion avec OVHcloud. Le EndPoint est le Datacentre OVHcloud où sont situés vos services. Vous pouvez choisir n'importe quel Datacentre de la même région que le PoP. - -### Layer 2 (L2) - -La liaison virtuelle est un tunnel L2 pour OVHcloud Connect L2. Seul un PoP/EntryPoint avec 1 DC/EndPoint peut être configuré. - -### Layer 3 (L3) - -La liaison virtuelle est un réseau IP à maillage complet entre tout PoP/EntryPoint et tout DC/EndPoint de la même région. - -## PoPs accessibles par fournisseur de service - -La liste disponible sur [ce lien de notre site web](/links/network/ovhcloud-connect) présente les PoPs d'OVHcloud accessibles via chacun de nos partenaires fournisseurs de services cloud. - -## Régions accessibles par PoP - -Lorsque vous établissez une connexion à OVHcloud Connect, votre trafic entre dans le réseau OVHcloud via un PoP spécifique. Chaque PoP est associé à une zone géographique, et les régions OVHcloud qui peuvent être atteintes depuis ce PoP sont limitées à la zone dans laquelle il se trouve. Selon le PoP que vous choisissez, seul un ensemble de régions prédéfini sera disponible pour l'interconnexion. - -Le tableau suivant répertorie les régions accessibles depuis chaque PoP : - -| Zone | PoPs OVHcloud Connect | Régions OVHcloud accessibles | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.it-it.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.it-it.md deleted file mode 100644 index 2246a998b43..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.it-it.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Concepts overview -excerpt: 'Concepts overview - OVHcloud Connect' -updated: 2025-10-29 ---- - -## What is OVHcloud Connect? - -OVHcloud Connect is a private, dedicated connection between your on-premises network and your OVHcloud vRack. It is designed to extend your network and securely connect to your cloud resources, bypassing the public internet. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Benefits of OVHcloud Connect - -### Dedicated service - -Dedicated Mode is a direct connection with OVHcloud devices. You can manage different configurations, from a single connection to a multiple one using LACP (Layer 2) or BGP-ECMP (Layer 3) with port speed at 1Gb or 10Gb. Interface and bandwidth are not shared with other customers. - -### Private connection - -Your traffic is isolated from the Internet. You manage your own VLANs (Layer 2) and/or your own IP addresses (Layer 3). BGP instances are private, and you can configure the ASN you want. - -OVHcloud Connect is connected to your vRack with all compatible services. - -### Network extension - -OVHcloud Connect can be connected either to your WAN or your data centre network, allowing seamless extension to the cloud. This eases hybrid cloud strategies and migrations by keeping your existing VLAN topology or IP addresses. - -### High availability - -Using BGP, you can interconnect your network through multiple Points-of-Presence (PoPs) and reach several OVHcloud data centres. From your vRack, you can configure BGP to enable maximum resiliency with distributed services. - -## Components of OVHcloud Connect - -### PoP - EntryPoint - -Points of Presence are facilities like Equinix, InterXion, Telehouse or Global Switch. The OVHcloud Connect service entry PoP is called *EntryPoint*. - -### DC - EndPoint - -The OVHcloud data centre is the service *EndPoint* of OVHcloud Connect. - -### Cross-connect - -A cross-connection is a physical link (monomode fiber) managed by the local facility team in the PoP. The cross-connection is established in the MMR (Meet-Me Room) between the position given by OVHcloud and the position owned by the customer. The customer must order and manage the cross-connect for OVHcloud Connect Direct. - -### vRack - -The OVHcloud Private Network, available on compute resources between all OVHcloud data centres. It allows you to connect compatible services into a single private network. - -### BGP - -BGP (Border Gateway Protocol) is the routing protocol used in Layer 3 mode to manage routes between your network and the OVHcloud vRack. - -## Principles of OVHcloud Connect - -OVHcloud Connect is based on a virtual link between an *EntryPoint* and an *EndPoint*. The *EntryPoint* is where you want to make the interconnection with OVHcloud. The *EndPoint* is the OVHcloud data centre with your services. You can choose any data centre in the same region as the PoP. - -### Layer 2 Mode (L2) - -The virtual link is a L2 tunnel for OVHcloud Connect L2. Only one PoP/*EntryPoint* with one DC/*EndPoint* can be configured. - -### Layer 3 Mode (L3) - -The virtual link is a full mesh IP network between any PoP/*EntryPoint* and any DC/*EndPoint* of the same region. - -## Accessible PoPs per provider - -The OVHcloud Points of Presence (PoPs) available through each of our cloud service provider partners are outlined in the list present at [this link on our website](/links/network/ovhcloud-connect). - -## Accessible Regions per PoP - -When you establish a connection to OVHcloud Connect, your traffic enters the OVHcloud network through a specific PoP. Each PoP is associated with a geographic zone, and the OVHcloud regions that can be reached from that PoP are limited to the zone in which it is located. Depending on the PoP you select, only a defined set of regions will be available for interconnection. - -The following table lists regions that can be accessed from each PoP location: - -| Zone | OVHcloud Connect PoPs | Accessible OVHcloud Regions | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.pl-pl.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.pl-pl.md deleted file mode 100644 index 2246a998b43..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.pl-pl.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Concepts overview -excerpt: 'Concepts overview - OVHcloud Connect' -updated: 2025-10-29 ---- - -## What is OVHcloud Connect? - -OVHcloud Connect is a private, dedicated connection between your on-premises network and your OVHcloud vRack. It is designed to extend your network and securely connect to your cloud resources, bypassing the public internet. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Benefits of OVHcloud Connect - -### Dedicated service - -Dedicated Mode is a direct connection with OVHcloud devices. You can manage different configurations, from a single connection to a multiple one using LACP (Layer 2) or BGP-ECMP (Layer 3) with port speed at 1Gb or 10Gb. Interface and bandwidth are not shared with other customers. - -### Private connection - -Your traffic is isolated from the Internet. You manage your own VLANs (Layer 2) and/or your own IP addresses (Layer 3). BGP instances are private, and you can configure the ASN you want. - -OVHcloud Connect is connected to your vRack with all compatible services. - -### Network extension - -OVHcloud Connect can be connected either to your WAN or your data centre network, allowing seamless extension to the cloud. This eases hybrid cloud strategies and migrations by keeping your existing VLAN topology or IP addresses. - -### High availability - -Using BGP, you can interconnect your network through multiple Points-of-Presence (PoPs) and reach several OVHcloud data centres. From your vRack, you can configure BGP to enable maximum resiliency with distributed services. - -## Components of OVHcloud Connect - -### PoP - EntryPoint - -Points of Presence are facilities like Equinix, InterXion, Telehouse or Global Switch. The OVHcloud Connect service entry PoP is called *EntryPoint*. - -### DC - EndPoint - -The OVHcloud data centre is the service *EndPoint* of OVHcloud Connect. - -### Cross-connect - -A cross-connection is a physical link (monomode fiber) managed by the local facility team in the PoP. The cross-connection is established in the MMR (Meet-Me Room) between the position given by OVHcloud and the position owned by the customer. The customer must order and manage the cross-connect for OVHcloud Connect Direct. - -### vRack - -The OVHcloud Private Network, available on compute resources between all OVHcloud data centres. It allows you to connect compatible services into a single private network. - -### BGP - -BGP (Border Gateway Protocol) is the routing protocol used in Layer 3 mode to manage routes between your network and the OVHcloud vRack. - -## Principles of OVHcloud Connect - -OVHcloud Connect is based on a virtual link between an *EntryPoint* and an *EndPoint*. The *EntryPoint* is where you want to make the interconnection with OVHcloud. The *EndPoint* is the OVHcloud data centre with your services. You can choose any data centre in the same region as the PoP. - -### Layer 2 Mode (L2) - -The virtual link is a L2 tunnel for OVHcloud Connect L2. Only one PoP/*EntryPoint* with one DC/*EndPoint* can be configured. - -### Layer 3 Mode (L3) - -The virtual link is a full mesh IP network between any PoP/*EntryPoint* and any DC/*EndPoint* of the same region. - -## Accessible PoPs per provider - -The OVHcloud Points of Presence (PoPs) available through each of our cloud service provider partners are outlined in the list present at [this link on our website](/links/network/ovhcloud-connect). - -## Accessible Regions per PoP - -When you establish a connection to OVHcloud Connect, your traffic enters the OVHcloud network through a specific PoP. Each PoP is associated with a geographic zone, and the OVHcloud regions that can be reached from that PoP are limited to the zone in which it is located. Depending on the PoP you select, only a defined set of regions will be available for interconnection. - -The following table lists regions that can be accessed from each PoP location: - -| Zone | OVHcloud Connect PoPs | Accessible OVHcloud Regions | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.pt-pt.md b/pages/network/ovhcloud_connect/occ-concepts-overview/guide.pt-pt.md deleted file mode 100644 index 2246a998b43..00000000000 --- a/pages/network/ovhcloud_connect/occ-concepts-overview/guide.pt-pt.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: Concepts overview -excerpt: 'Concepts overview - OVHcloud Connect' -updated: 2025-10-29 ---- - -## What is OVHcloud Connect? - -OVHcloud Connect is a private, dedicated connection between your on-premises network and your OVHcloud vRack. It is designed to extend your network and securely connect to your cloud resources, bypassing the public internet. - -![OVHcloud Connect](images/VrackConnectDedicated2025.png){.thumbnail} - -## Benefits of OVHcloud Connect - -### Dedicated service - -Dedicated Mode is a direct connection with OVHcloud devices. You can manage different configurations, from a single connection to a multiple one using LACP (Layer 2) or BGP-ECMP (Layer 3) with port speed at 1Gb or 10Gb. Interface and bandwidth are not shared with other customers. - -### Private connection - -Your traffic is isolated from the Internet. You manage your own VLANs (Layer 2) and/or your own IP addresses (Layer 3). BGP instances are private, and you can configure the ASN you want. - -OVHcloud Connect is connected to your vRack with all compatible services. - -### Network extension - -OVHcloud Connect can be connected either to your WAN or your data centre network, allowing seamless extension to the cloud. This eases hybrid cloud strategies and migrations by keeping your existing VLAN topology or IP addresses. - -### High availability - -Using BGP, you can interconnect your network through multiple Points-of-Presence (PoPs) and reach several OVHcloud data centres. From your vRack, you can configure BGP to enable maximum resiliency with distributed services. - -## Components of OVHcloud Connect - -### PoP - EntryPoint - -Points of Presence are facilities like Equinix, InterXion, Telehouse or Global Switch. The OVHcloud Connect service entry PoP is called *EntryPoint*. - -### DC - EndPoint - -The OVHcloud data centre is the service *EndPoint* of OVHcloud Connect. - -### Cross-connect - -A cross-connection is a physical link (monomode fiber) managed by the local facility team in the PoP. The cross-connection is established in the MMR (Meet-Me Room) between the position given by OVHcloud and the position owned by the customer. The customer must order and manage the cross-connect for OVHcloud Connect Direct. - -### vRack - -The OVHcloud Private Network, available on compute resources between all OVHcloud data centres. It allows you to connect compatible services into a single private network. - -### BGP - -BGP (Border Gateway Protocol) is the routing protocol used in Layer 3 mode to manage routes between your network and the OVHcloud vRack. - -## Principles of OVHcloud Connect - -OVHcloud Connect is based on a virtual link between an *EntryPoint* and an *EndPoint*. The *EntryPoint* is where you want to make the interconnection with OVHcloud. The *EndPoint* is the OVHcloud data centre with your services. You can choose any data centre in the same region as the PoP. - -### Layer 2 Mode (L2) - -The virtual link is a L2 tunnel for OVHcloud Connect L2. Only one PoP/*EntryPoint* with one DC/*EndPoint* can be configured. - -### Layer 3 Mode (L3) - -The virtual link is a full mesh IP network between any PoP/*EntryPoint* and any DC/*EndPoint* of the same region. - -## Accessible PoPs per provider - -The OVHcloud Points of Presence (PoPs) available through each of our cloud service provider partners are outlined in the list present at [this link on our website](/links/network/ovhcloud-connect). - -## Accessible Regions per PoP - -When you establish a connection to OVHcloud Connect, your traffic enters the OVHcloud network through a specific PoP. Each PoP is associated with a geographic zone, and the OVHcloud regions that can be reached from that PoP are limited to the zone in which it is located. Depending on the PoP you select, only a defined set of regions will be available for interconnection. - -The following table lists regions that can be accessed from each PoP location: - -| Zone | OVHcloud Connect PoPs | Accessible OVHcloud Regions | -| :--- | :--- | :--- | -| **Europe** | •Paris: Equinix - PA3, GlobalSwitch, Telehouse - TH2
•Frankfurt: Equinix - FR5
•London: Equinix - LD5, Telehouse - West
•Madrid: Digital Realty - MAD2
•Warsaw: Equinix - WA2
•Lille: ETIX - ETX2 | •Strasbourg (`eu-west-sbg`),
•Gravelines (`eu-west-gra`),
•Roubaix (`eu-west-rbx`),
•Paris (`eu-west-par`),
•Limburg (`eu-west-lim`),
•Warsaw (`eu-central-waw`),
•Erith (`eu-west-eri`) | -| **North America** | •Montreal: Cologix - MTL3
•Toronto: Equinix - TR1 | •Beauharnois (`ca-east-bhs`),
•Toronto (`ca-east-tor`) | -| **Asia-Pacific** | •Singapore: Equinix - SG1
•Mumbai: Equinix - MB2 | •Singapore (`ap-southeast-sgp`),
•Mumbai (`ap-south-mum`) | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-concepts-overview/images/VrackConnectDedicated2025.png b/pages/network/ovhcloud_connect/occ-concepts-overview/images/VrackConnectDedicated2025.png deleted file mode 100644 index fe81a8786e4..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-concepts-overview/images/VrackConnectDedicated2025.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.de-de.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.de-de.md deleted file mode 100644 index 5ad3e79471a..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.de-de.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel -excerpt: Find out how to get a status report of your OVHcloud Connect services -updated: 2025-04-28 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** - -## Requirements - -- An [OVHcloud Connect solution](/links/network/ovhcloud-connect) with a valid POP configuration. - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## List of available diagnostics - -### Layer 3 mode - -- **Default**: Fetches the BGP session states and all related information. -- **Routes**: Fetches the routing table learned by OVHcloud via BGP. -- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP. - -### Layer 2 mode - -- **MAC Address**: Fetches the list of MAC addresses of network devices and vRack. - -## Instructions - -### Layer 3 mode - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_BGP.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "BGP Peering Test": - -![OCC Service Test Button](images/OCC_service_test_button_BGP.png){.thumbnail} - -A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Layer 2 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_MAC.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "Get the list of my MAC addresses": - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limits - -- **Retention time of diagnostics**: Only diagnostics initiated **within the last seven days** are accessible. We recommend you download them and properly archive them, in case you need future access. - -- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60.
-This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-asia.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-asia.md deleted file mode 100644 index 5ad3e79471a..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-asia.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel -excerpt: Find out how to get a status report of your OVHcloud Connect services -updated: 2025-04-28 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** - -## Requirements - -- An [OVHcloud Connect solution](/links/network/ovhcloud-connect) with a valid POP configuration. - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## List of available diagnostics - -### Layer 3 mode - -- **Default**: Fetches the BGP session states and all related information. -- **Routes**: Fetches the routing table learned by OVHcloud via BGP. -- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP. - -### Layer 2 mode - -- **MAC Address**: Fetches the list of MAC addresses of network devices and vRack. - -## Instructions - -### Layer 3 mode - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_BGP.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "BGP Peering Test": - -![OCC Service Test Button](images/OCC_service_test_button_BGP.png){.thumbnail} - -A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Layer 2 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_MAC.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "Get the list of my MAC addresses": - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limits - -- **Retention time of diagnostics**: Only diagnostics initiated **within the last seven days** are accessible. We recommend you download them and properly archive them, in case you need future access. - -- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60.
-This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-au.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-au.md deleted file mode 100644 index 5ad3e79471a..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-au.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel -excerpt: Find out how to get a status report of your OVHcloud Connect services -updated: 2025-04-28 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** - -## Requirements - -- An [OVHcloud Connect solution](/links/network/ovhcloud-connect) with a valid POP configuration. - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## List of available diagnostics - -### Layer 3 mode - -- **Default**: Fetches the BGP session states and all related information. -- **Routes**: Fetches the routing table learned by OVHcloud via BGP. -- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP. - -### Layer 2 mode - -- **MAC Address**: Fetches the list of MAC addresses of network devices and vRack. - -## Instructions - -### Layer 3 mode - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_BGP.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "BGP Peering Test": - -![OCC Service Test Button](images/OCC_service_test_button_BGP.png){.thumbnail} - -A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Layer 2 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_MAC.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "Get the list of my MAC addresses": - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limits - -- **Retention time of diagnostics**: Only diagnostics initiated **within the last seven days** are accessible. We recommend you download them and properly archive them, in case you need future access. - -- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60.
-This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-ca.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-ca.md deleted file mode 100644 index 5ad3e79471a..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-ca.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel -excerpt: Find out how to get a status report of your OVHcloud Connect services -updated: 2025-04-28 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** - -## Requirements - -- An [OVHcloud Connect solution](/links/network/ovhcloud-connect) with a valid POP configuration. - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## List of available diagnostics - -### Layer 3 mode - -- **Default**: Fetches the BGP session states and all related information. -- **Routes**: Fetches the routing table learned by OVHcloud via BGP. -- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP. - -### Layer 2 mode - -- **MAC Address**: Fetches the list of MAC addresses of network devices and vRack. - -## Instructions - -### Layer 3 mode - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_BGP.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "BGP Peering Test": - -![OCC Service Test Button](images/OCC_service_test_button_BGP.png){.thumbnail} - -A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Layer 2 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_MAC.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "Get the list of my MAC addresses": - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limits - -- **Retention time of diagnostics**: Only diagnostics initiated **within the last seven days** are accessible. We recommend you download them and properly archive them, in case you need future access. - -- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60.
-This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-gb.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-gb.md deleted file mode 100644 index 5ad3e79471a..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-gb.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel -excerpt: Find out how to get a status report of your OVHcloud Connect services -updated: 2025-04-28 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** - -## Requirements - -- An [OVHcloud Connect solution](/links/network/ovhcloud-connect) with a valid POP configuration. - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## List of available diagnostics - -### Layer 3 mode - -- **Default**: Fetches the BGP session states and all related information. -- **Routes**: Fetches the routing table learned by OVHcloud via BGP. -- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP. - -### Layer 2 mode - -- **MAC Address**: Fetches the list of MAC addresses of network devices and vRack. - -## Instructions - -### Layer 3 mode - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_BGP.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "BGP Peering Test": - -![OCC Service Test Button](images/OCC_service_test_button_BGP.png){.thumbnail} - -A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Layer 2 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_MAC.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "Get the list of my MAC addresses": - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limits - -- **Retention time of diagnostics**: Only diagnostics initiated **within the last seven days** are accessible. We recommend you download them and properly archive them, in case you need future access. - -- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60.
-This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-ie.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-ie.md deleted file mode 100644 index 5ad3e79471a..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-ie.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel -excerpt: Find out how to get a status report of your OVHcloud Connect services -updated: 2025-04-28 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** - -## Requirements - -- An [OVHcloud Connect solution](/links/network/ovhcloud-connect) with a valid POP configuration. - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## List of available diagnostics - -### Layer 3 mode - -- **Default**: Fetches the BGP session states and all related information. -- **Routes**: Fetches the routing table learned by OVHcloud via BGP. -- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP. - -### Layer 2 mode - -- **MAC Address**: Fetches the list of MAC addresses of network devices and vRack. - -## Instructions - -### Layer 3 mode - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_BGP.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "BGP Peering Test": - -![OCC Service Test Button](images/OCC_service_test_button_BGP.png){.thumbnail} - -A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Layer 2 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_MAC.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "Get the list of my MAC addresses": - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limits - -- **Retention time of diagnostics**: Only diagnostics initiated **within the last seven days** are accessible. We recommend you download them and properly archive them, in case you need future access. - -- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60.
-This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-sg.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-sg.md deleted file mode 100644 index 5ad3e79471a..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-sg.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel -excerpt: Find out how to get a status report of your OVHcloud Connect services -updated: 2025-04-28 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** - -## Requirements - -- An [OVHcloud Connect solution](/links/network/ovhcloud-connect) with a valid POP configuration. - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## List of available diagnostics - -### Layer 3 mode - -- **Default**: Fetches the BGP session states and all related information. -- **Routes**: Fetches the routing table learned by OVHcloud via BGP. -- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP. - -### Layer 2 mode - -- **MAC Address**: Fetches the list of MAC addresses of network devices and vRack. - -## Instructions - -### Layer 3 mode - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_BGP.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "BGP Peering Test": - -![OCC Service Test Button](images/OCC_service_test_button_BGP.png){.thumbnail} - -A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Layer 2 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_MAC.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "Get the list of my MAC addresses": - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limits - -- **Retention time of diagnostics**: Only diagnostics initiated **within the last seven days** are accessible. We recommend you download them and properly archive them, in case you need future access. - -- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60.
-This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-us.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-us.md deleted file mode 100644 index 5ad3e79471a..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.en-us.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel -excerpt: Find out how to get a status report of your OVHcloud Connect services -updated: 2025-04-28 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** - -## Requirements - -- An [OVHcloud Connect solution](/links/network/ovhcloud-connect) with a valid POP configuration. - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## List of available diagnostics - -### Layer 3 mode - -- **Default**: Fetches the BGP session states and all related information. -- **Routes**: Fetches the routing table learned by OVHcloud via BGP. -- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP. - -### Layer 2 mode - -- **MAC Address**: Fetches the list of MAC addresses of network devices and vRack. - -## Instructions - -### Layer 3 mode - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_BGP.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "BGP Peering Test": - -![OCC Service Test Button](images/OCC_service_test_button_BGP.png){.thumbnail} - -A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Layer 2 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_MAC.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "Get the list of my MAC addresses": - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limits - -- **Retention time of diagnostics**: Only diagnostics initiated **within the last seven days** are accessible. We recommend you download them and properly archive them, in case you need future access. - -- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60.
-This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.es-es.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.es-es.md deleted file mode 100644 index 5ad3e79471a..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.es-es.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel -excerpt: Find out how to get a status report of your OVHcloud Connect services -updated: 2025-04-28 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** - -## Requirements - -- An [OVHcloud Connect solution](/links/network/ovhcloud-connect) with a valid POP configuration. - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## List of available diagnostics - -### Layer 3 mode - -- **Default**: Fetches the BGP session states and all related information. -- **Routes**: Fetches the routing table learned by OVHcloud via BGP. -- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP. - -### Layer 2 mode - -- **MAC Address**: Fetches the list of MAC addresses of network devices and vRack. - -## Instructions - -### Layer 3 mode - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_BGP.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "BGP Peering Test": - -![OCC Service Test Button](images/OCC_service_test_button_BGP.png){.thumbnail} - -A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Layer 2 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_MAC.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "Get the list of my MAC addresses": - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limits - -- **Retention time of diagnostics**: Only diagnostics initiated **within the last seven days** are accessible. We recommend you download them and properly archive them, in case you need future access. - -- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60.
-This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.es-us.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.es-us.md deleted file mode 100644 index 86569f0c40b..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.es-us.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel -excerpt: Find out how to get a status report of your OVHcloud Connect services -updated: 2025-04-28 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** - -## Requirements - -- An [OVHcloud Connect solution](/links/network/ovhcloud-connect) with a valid POP configuration. -- Access to the [OVHcloud Control Panel](/links/manager). - -## List of available diagnostics - -### Layer 3 mode - -- **Default**: Fetches the BGP session states and all related information. -- **Routes**: Fetches the routing table learned by OVHcloud via BGP. -- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP. - -### Layer 2 mode - -- **MAC Address**: Fetches the list of MAC addresses of network devices and vRack. - -## Instructions - -### Layer 3 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_BGP.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "BGP Peering Test": - -![OCC Service Test Button](images/OCC_service_test_button_BGP.png){.thumbnail} - -A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Layer 2 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_MAC.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "Get the list of my MAC addresses": - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limits - -- **Retention time of diagnostics**: Only diagnostics initiated **within the last seven days** are accessible. We recommend you download them and properly archive them, in case you need future access. - -- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60.
-This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.fr-ca.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.fr-ca.md deleted file mode 100644 index 44d087731e2..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.fr-ca.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: "Comment lancer un diagnostic OVHcloud Connect depuis votre espace client" -excerpt: "Découvrez comment obtenir un rapport sur l'état de vos services OVHcloud Connect" -updated: 2025-04-28 ---- - -## Objectif - -Avec OVHcloud Connect, vous pouvez relier votre réseau d'entreprise à votre réseau privé OVHcloud vRack, sans créer de tunnel VPN à travers Internet. Vous bénéficiez ainsi d’une connexion plus rapide et plus stable, avec une bande passante garantie. - -**Ce guide vous explique comment obtenir un rapport sur l'état de vos services OVHcloud Connect depuis votre espace client.** - -## Prérequis - -- Détenir une solution [OVHcloud Connect](/links/network/ovhcloud-connect) avec une configuration POP valide. - - ---- - -### Accès à l'espace client OVHcloud - -- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Liste des diagnostics disponibles - -### Mode L3 - -- **Par défaut** : Extrait les états de session BGP et toutes les informations associées. -- **Routes** : Récupère la table de routage apprise par OVHcloud via BGP. -- **Advertised-Routes** : Récupère la table de routage annoncée par OVHcloud via BGP. - -### Mode L2 - -- **Adresse MAC** : Extrait la liste des adresses MAC des périphériques réseau et du vRack. - -## En pratique - -### Mode L3 - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Ouvrez le service pour lequel vous souhaitez obtenir un diagnostic : - -![Service OCC](images/OCC_service_BGP.png){.thumbnail} - -En bas du panneau « Configuration POP », vous trouverez un segment nommé « POP Diagnostic » et un bouton de sélection `...`{.action}. Cliquez dessus, puis sélectionnez « Test BGP Peering » : - -![Bouton de test du service OCC](images/OCC_service_test_button_BGP.png){.thumbnail} - -Une fenêtre s'ouvrira. Sélectionnez le type de diagnostic que vous souhaitez utiliser, puis cliquez sur « Lancer le diagnostic » : - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -Vous pouvez maintenant accéder à la liste de vos diagnostics en ouvrant l'onglet « Diagnostics ». - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Chaque diagnostic est référencé à l'aide d'un ID et d'un horodatage. -Pour accéder au contenu des diagnostics, cliquez sur le bouton de sélection `...`{.action} situé à droite de chacun d'entre eux. Vous pouvez sélectionner « Voir le résultat » pour ouvrir une fenêtre avec le contenu du diagnostic souhaité, ou « Télécharger le résultat » pour obtenir un fichier *.txt* avec le même contenu. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Mode L2 - -Vous retrouverez la liste de vos services `OVHcloud Connect`{.action} dans la section `Network`{.action} de votre [espace client OVHcloud](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Ouvrez le service pour lequel vous souhaitez obtenir un diagnostic : - -![Service OCC](images/OCC_service_MAC.png){.thumbnail} - -En bas du panneau « Configuration POP », vous trouverez un segment nommé « POP Diagnostic » et un bouton de sélection `...`{.action}. Cliquez dessus, puis sélectionnez « Voir la liste de mes adresses MAC » : - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -Vous pouvez maintenant accéder à la liste de vos diagnostics en ouvrant l'onglet « Diagnostics ». - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Chaque diagnostic est référencé à l'aide d'un ID et d'un horodatage. -Pour accéder au contenu des diagnostics, cliquez sur le bouton de sélection `...`{.action} situé à droite de chacun d'entre eux. Vous pouvez sélectionner « Voir le résultat » pour ouvrir une fenêtre avec le contenu du diagnostic souhaité, ou « Télécharger le résultat » pour obtenir un fichier *.txt* avec le même contenu. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limites - -- **Durée de rétention des diagnostics** : Seuls les diagnostics initiés **au cours des sept derniers jours** sont accessibles. Nous vous recommandons de les télécharger et de les archiver correctement, au cas où vous auriez besoin d'un accès ultérieur. - -- **Nombre maximum de diagnostics** : Sur une période de 24 heures, vous pouvez lancer un maximum de 10 diagnostics par type de diagnostic et par service. Par exemple, si vous détenez deux services OVHcloud Connect sur votre espace client OVHcloud, tous deux configurés en mode Layer 3, vous pouvez théoriquement lancer 10 diagnostics de chaque type par service, pour un total de 60.
-Cette limite a été fixée afin de limiter la quantité de ressources utilisées par l’infrastructure OVHcloud, les diagnostics étant lancés en temps réel. - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.fr-fr.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.fr-fr.md deleted file mode 100644 index 44d087731e2..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.fr-fr.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: "Comment lancer un diagnostic OVHcloud Connect depuis votre espace client" -excerpt: "Découvrez comment obtenir un rapport sur l'état de vos services OVHcloud Connect" -updated: 2025-04-28 ---- - -## Objectif - -Avec OVHcloud Connect, vous pouvez relier votre réseau d'entreprise à votre réseau privé OVHcloud vRack, sans créer de tunnel VPN à travers Internet. Vous bénéficiez ainsi d’une connexion plus rapide et plus stable, avec une bande passante garantie. - -**Ce guide vous explique comment obtenir un rapport sur l'état de vos services OVHcloud Connect depuis votre espace client.** - -## Prérequis - -- Détenir une solution [OVHcloud Connect](/links/network/ovhcloud-connect) avec une configuration POP valide. - - ---- - -### Accès à l'espace client OVHcloud - -- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Liste des diagnostics disponibles - -### Mode L3 - -- **Par défaut** : Extrait les états de session BGP et toutes les informations associées. -- **Routes** : Récupère la table de routage apprise par OVHcloud via BGP. -- **Advertised-Routes** : Récupère la table de routage annoncée par OVHcloud via BGP. - -### Mode L2 - -- **Adresse MAC** : Extrait la liste des adresses MAC des périphériques réseau et du vRack. - -## En pratique - -### Mode L3 - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Ouvrez le service pour lequel vous souhaitez obtenir un diagnostic : - -![Service OCC](images/OCC_service_BGP.png){.thumbnail} - -En bas du panneau « Configuration POP », vous trouverez un segment nommé « POP Diagnostic » et un bouton de sélection `...`{.action}. Cliquez dessus, puis sélectionnez « Test BGP Peering » : - -![Bouton de test du service OCC](images/OCC_service_test_button_BGP.png){.thumbnail} - -Une fenêtre s'ouvrira. Sélectionnez le type de diagnostic que vous souhaitez utiliser, puis cliquez sur « Lancer le diagnostic » : - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -Vous pouvez maintenant accéder à la liste de vos diagnostics en ouvrant l'onglet « Diagnostics ». - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Chaque diagnostic est référencé à l'aide d'un ID et d'un horodatage. -Pour accéder au contenu des diagnostics, cliquez sur le bouton de sélection `...`{.action} situé à droite de chacun d'entre eux. Vous pouvez sélectionner « Voir le résultat » pour ouvrir une fenêtre avec le contenu du diagnostic souhaité, ou « Télécharger le résultat » pour obtenir un fichier *.txt* avec le même contenu. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Mode L2 - -Vous retrouverez la liste de vos services `OVHcloud Connect`{.action} dans la section `Network`{.action} de votre [espace client OVHcloud](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Ouvrez le service pour lequel vous souhaitez obtenir un diagnostic : - -![Service OCC](images/OCC_service_MAC.png){.thumbnail} - -En bas du panneau « Configuration POP », vous trouverez un segment nommé « POP Diagnostic » et un bouton de sélection `...`{.action}. Cliquez dessus, puis sélectionnez « Voir la liste de mes adresses MAC » : - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -Vous pouvez maintenant accéder à la liste de vos diagnostics en ouvrant l'onglet « Diagnostics ». - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Chaque diagnostic est référencé à l'aide d'un ID et d'un horodatage. -Pour accéder au contenu des diagnostics, cliquez sur le bouton de sélection `...`{.action} situé à droite de chacun d'entre eux. Vous pouvez sélectionner « Voir le résultat » pour ouvrir une fenêtre avec le contenu du diagnostic souhaité, ou « Télécharger le résultat » pour obtenir un fichier *.txt* avec le même contenu. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limites - -- **Durée de rétention des diagnostics** : Seuls les diagnostics initiés **au cours des sept derniers jours** sont accessibles. Nous vous recommandons de les télécharger et de les archiver correctement, au cas où vous auriez besoin d'un accès ultérieur. - -- **Nombre maximum de diagnostics** : Sur une période de 24 heures, vous pouvez lancer un maximum de 10 diagnostics par type de diagnostic et par service. Par exemple, si vous détenez deux services OVHcloud Connect sur votre espace client OVHcloud, tous deux configurés en mode Layer 3, vous pouvez théoriquement lancer 10 diagnostics de chaque type par service, pour un total de 60.
-Cette limite a été fixée afin de limiter la quantité de ressources utilisées par l’infrastructure OVHcloud, les diagnostics étant lancés en temps réel. - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.it-it.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.it-it.md deleted file mode 100644 index 5ad3e79471a..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.it-it.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel -excerpt: Find out how to get a status report of your OVHcloud Connect services -updated: 2025-04-28 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** - -## Requirements - -- An [OVHcloud Connect solution](/links/network/ovhcloud-connect) with a valid POP configuration. - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## List of available diagnostics - -### Layer 3 mode - -- **Default**: Fetches the BGP session states and all related information. -- **Routes**: Fetches the routing table learned by OVHcloud via BGP. -- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP. - -### Layer 2 mode - -- **MAC Address**: Fetches the list of MAC addresses of network devices and vRack. - -## Instructions - -### Layer 3 mode - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_BGP.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "BGP Peering Test": - -![OCC Service Test Button](images/OCC_service_test_button_BGP.png){.thumbnail} - -A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Layer 2 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_MAC.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "Get the list of my MAC addresses": - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limits - -- **Retention time of diagnostics**: Only diagnostics initiated **within the last seven days** are accessible. We recommend you download them and properly archive them, in case you need future access. - -- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60.
-This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.pl-pl.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.pl-pl.md deleted file mode 100644 index 5ad3e79471a..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.pl-pl.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel -excerpt: Find out how to get a status report of your OVHcloud Connect services -updated: 2025-04-28 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** - -## Requirements - -- An [OVHcloud Connect solution](/links/network/ovhcloud-connect) with a valid POP configuration. - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## List of available diagnostics - -### Layer 3 mode - -- **Default**: Fetches the BGP session states and all related information. -- **Routes**: Fetches the routing table learned by OVHcloud via BGP. -- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP. - -### Layer 2 mode - -- **MAC Address**: Fetches the list of MAC addresses of network devices and vRack. - -## Instructions - -### Layer 3 mode - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_BGP.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "BGP Peering Test": - -![OCC Service Test Button](images/OCC_service_test_button_BGP.png){.thumbnail} - -A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Layer 2 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_MAC.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "Get the list of my MAC addresses": - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limits - -- **Retention time of diagnostics**: Only diagnostics initiated **within the last seven days** are accessible. We recommend you download them and properly archive them, in case you need future access. - -- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60.
-This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/guide.pt-pt.md b/pages/network/ovhcloud_connect/occ-diagnostics/guide.pt-pt.md deleted file mode 100644 index 5ad3e79471a..00000000000 --- a/pages/network/ovhcloud_connect/occ-diagnostics/guide.pt-pt.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel -excerpt: Find out how to get a status report of your OVHcloud Connect services -updated: 2025-04-28 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** - -## Requirements - -- An [OVHcloud Connect solution](/links/network/ovhcloud-connect) with a valid POP configuration. - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## List of available diagnostics - -### Layer 3 mode - -- **Default**: Fetches the BGP session states and all related information. -- **Routes**: Fetches the routing table learned by OVHcloud via BGP. -- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP. - -### Layer 2 mode - -- **MAC Address**: Fetches the list of MAC addresses of network devices and vRack. - -## Instructions - -### Layer 3 mode - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_BGP.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "BGP Peering Test": - -![OCC Service Test Button](images/OCC_service_test_button_BGP.png){.thumbnail} - -A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": - -![OCC Diagnostics Choice](images/OCC_diag_choice.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_BGP.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -### Layer 2 mode - -You can find the list of your `OVHcloud Connect`{.action} services in the `Network`{.action} section of your [OVHcloud Control Panel](/links/manager). - -![OCC Control Panel](images/OCC_cpanel.png){.thumbnail} - -Open the service for which you want to get a diagnosis: - -![OCC Service](images/OCC_service_MAC.png){.thumbnail} - -At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis button `...`{.action}. Click it, and then select "Get the list of my MAC addresses": - -![OCC Service Test Button](images/OCC_service_test_button_MAC.png){.thumbnail} - -You can now access the list of your diagnostics by opening the "Diagnostics" tab. - -![OCC Diagnostics Tab](images/OCC_diag_tab_MAC.png){.thumbnail} - -Each diagnostic is referred to using an ID and a timestamp. -To access the diagnostics content, click the ellipsis button `...`{.action} located to the right of each one listed. You can select either "See result" to have a window open with the content of the desired diagnostic, or "Download result" to get a *.txt* file with the same content. - -![OCC Diagnostic view button](images/OCC_diag_view_button.png){.thumbnail} - -## Limits - -- **Retention time of diagnostics**: Only diagnostics initiated **within the last seven days** are accessible. We recommend you download them and properly archive them, in case you need future access. - -- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60.
-This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_cpanel.png b/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_cpanel.png deleted file mode 100644 index aa3a5aa485b..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_cpanel.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_diag_choice.png b/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_diag_choice.png deleted file mode 100644 index c448eff11af..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_diag_choice.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_diag_tab_BGP.png b/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_diag_tab_BGP.png deleted file mode 100644 index d3a1e4d9727..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_diag_tab_BGP.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_diag_tab_MAC.png b/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_diag_tab_MAC.png deleted file mode 100644 index 213be5bacdc..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_diag_tab_MAC.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_diag_view_button.png b/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_diag_view_button.png deleted file mode 100644 index f2ce60ca9f4..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_diag_view_button.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_service_BGP.png b/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_service_BGP.png deleted file mode 100644 index 7c1ec7f64e7..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_service_BGP.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_service_MAC.png b/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_service_MAC.png deleted file mode 100644 index 6336499540f..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_service_MAC.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_service_test_button_BGP.png b/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_service_test_button_BGP.png deleted file mode 100644 index b991dce916b..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_service_test_button_BGP.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_service_test_button_MAC.png b/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_service_test_button_MAC.png deleted file mode 100644 index 4217187c397..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-diagnostics/images/OCC_service_test_button_MAC.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.de-de.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.de-de.md deleted file mode 100644 index e5e16420034..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.de-de.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: Installation of OVHcloud Connect Direct from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Direct solution via the OVHcloud Control Panel.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Direct solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Step 1: Associating a vRack - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 2: Adding a PoP configuration - -> [!warning] -> Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further. -> - -> [!primary] -> For more details on the differences between levels L2 and L3, see our [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration - -Once you have linked your vRack, two `PoP configuration` menus will appear. Click the `Add a PoP configuration`{.action} button in the first menu, select L2 from the drop-down menu, then confirm. - -![adding PoP L2](images/pop2.png){.thumbnail} - -The L2 configuration will then be enabled in the `PoP configuration` menu. - -![adding PoP L2](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Once you have connected your vRack, click `Add a PoP configuration`{.action} and select the L3 configuration from the drop-down menu. - -![adding PoP L3](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![adding PoP L3](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![ajout PoP](images/l3pop2.png){.thumbnail} - -You can also add a second PoP L3 configuration via the second `PoP configuration` menu. - -### Step 3: Adding an availability zone configuration - -#### Configuration - -When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm. - -![add AZ](images/l2dc1.png){.thumbnail} - -![add AZ](images/l2dc1-1.png){.thumbnail} - -The AZ configuration will then begin. - -![add AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![add AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the drop-down menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![add AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![add AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add routing configuration](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add routing configuration](images/l3dc3.png){.thumbnail} - -If you choose the type BGP, then enter the required information. - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section | - -![add routing configuration](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Network Focus | A prefix using CIDR notation | -| Next hop | An IP address acting as gateway in the subnetwork range | - -![add routing configuration](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone. - -![add routing configuration](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting a AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration to delete, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepop.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the related AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-asia.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-asia.md deleted file mode 100644 index e5e16420034..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-asia.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: Installation of OVHcloud Connect Direct from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Direct solution via the OVHcloud Control Panel.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Direct solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Step 1: Associating a vRack - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 2: Adding a PoP configuration - -> [!warning] -> Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further. -> - -> [!primary] -> For more details on the differences between levels L2 and L3, see our [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration - -Once you have linked your vRack, two `PoP configuration` menus will appear. Click the `Add a PoP configuration`{.action} button in the first menu, select L2 from the drop-down menu, then confirm. - -![adding PoP L2](images/pop2.png){.thumbnail} - -The L2 configuration will then be enabled in the `PoP configuration` menu. - -![adding PoP L2](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Once you have connected your vRack, click `Add a PoP configuration`{.action} and select the L3 configuration from the drop-down menu. - -![adding PoP L3](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![adding PoP L3](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![ajout PoP](images/l3pop2.png){.thumbnail} - -You can also add a second PoP L3 configuration via the second `PoP configuration` menu. - -### Step 3: Adding an availability zone configuration - -#### Configuration - -When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm. - -![add AZ](images/l2dc1.png){.thumbnail} - -![add AZ](images/l2dc1-1.png){.thumbnail} - -The AZ configuration will then begin. - -![add AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![add AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the drop-down menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![add AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![add AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add routing configuration](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add routing configuration](images/l3dc3.png){.thumbnail} - -If you choose the type BGP, then enter the required information. - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section | - -![add routing configuration](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Network Focus | A prefix using CIDR notation | -| Next hop | An IP address acting as gateway in the subnetwork range | - -![add routing configuration](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone. - -![add routing configuration](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting a AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration to delete, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepop.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the related AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-au.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-au.md deleted file mode 100644 index e5e16420034..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-au.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: Installation of OVHcloud Connect Direct from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Direct solution via the OVHcloud Control Panel.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Direct solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Step 1: Associating a vRack - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 2: Adding a PoP configuration - -> [!warning] -> Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further. -> - -> [!primary] -> For more details on the differences between levels L2 and L3, see our [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration - -Once you have linked your vRack, two `PoP configuration` menus will appear. Click the `Add a PoP configuration`{.action} button in the first menu, select L2 from the drop-down menu, then confirm. - -![adding PoP L2](images/pop2.png){.thumbnail} - -The L2 configuration will then be enabled in the `PoP configuration` menu. - -![adding PoP L2](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Once you have connected your vRack, click `Add a PoP configuration`{.action} and select the L3 configuration from the drop-down menu. - -![adding PoP L3](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![adding PoP L3](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![ajout PoP](images/l3pop2.png){.thumbnail} - -You can also add a second PoP L3 configuration via the second `PoP configuration` menu. - -### Step 3: Adding an availability zone configuration - -#### Configuration - -When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm. - -![add AZ](images/l2dc1.png){.thumbnail} - -![add AZ](images/l2dc1-1.png){.thumbnail} - -The AZ configuration will then begin. - -![add AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![add AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the drop-down menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![add AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![add AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add routing configuration](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add routing configuration](images/l3dc3.png){.thumbnail} - -If you choose the type BGP, then enter the required information. - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section | - -![add routing configuration](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Network Focus | A prefix using CIDR notation | -| Next hop | An IP address acting as gateway in the subnetwork range | - -![add routing configuration](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone. - -![add routing configuration](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting a AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration to delete, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepop.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the related AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-ca.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-ca.md deleted file mode 100644 index e5e16420034..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-ca.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: Installation of OVHcloud Connect Direct from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Direct solution via the OVHcloud Control Panel.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Direct solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Step 1: Associating a vRack - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 2: Adding a PoP configuration - -> [!warning] -> Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further. -> - -> [!primary] -> For more details on the differences between levels L2 and L3, see our [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration - -Once you have linked your vRack, two `PoP configuration` menus will appear. Click the `Add a PoP configuration`{.action} button in the first menu, select L2 from the drop-down menu, then confirm. - -![adding PoP L2](images/pop2.png){.thumbnail} - -The L2 configuration will then be enabled in the `PoP configuration` menu. - -![adding PoP L2](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Once you have connected your vRack, click `Add a PoP configuration`{.action} and select the L3 configuration from the drop-down menu. - -![adding PoP L3](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![adding PoP L3](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![ajout PoP](images/l3pop2.png){.thumbnail} - -You can also add a second PoP L3 configuration via the second `PoP configuration` menu. - -### Step 3: Adding an availability zone configuration - -#### Configuration - -When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm. - -![add AZ](images/l2dc1.png){.thumbnail} - -![add AZ](images/l2dc1-1.png){.thumbnail} - -The AZ configuration will then begin. - -![add AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![add AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the drop-down menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![add AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![add AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add routing configuration](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add routing configuration](images/l3dc3.png){.thumbnail} - -If you choose the type BGP, then enter the required information. - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section | - -![add routing configuration](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Network Focus | A prefix using CIDR notation | -| Next hop | An IP address acting as gateway in the subnetwork range | - -![add routing configuration](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone. - -![add routing configuration](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting a AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration to delete, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepop.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the related AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-gb.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-gb.md deleted file mode 100644 index e5e16420034..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-gb.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: Installation of OVHcloud Connect Direct from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Direct solution via the OVHcloud Control Panel.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Direct solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Step 1: Associating a vRack - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 2: Adding a PoP configuration - -> [!warning] -> Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further. -> - -> [!primary] -> For more details on the differences between levels L2 and L3, see our [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration - -Once you have linked your vRack, two `PoP configuration` menus will appear. Click the `Add a PoP configuration`{.action} button in the first menu, select L2 from the drop-down menu, then confirm. - -![adding PoP L2](images/pop2.png){.thumbnail} - -The L2 configuration will then be enabled in the `PoP configuration` menu. - -![adding PoP L2](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Once you have connected your vRack, click `Add a PoP configuration`{.action} and select the L3 configuration from the drop-down menu. - -![adding PoP L3](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![adding PoP L3](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![ajout PoP](images/l3pop2.png){.thumbnail} - -You can also add a second PoP L3 configuration via the second `PoP configuration` menu. - -### Step 3: Adding an availability zone configuration - -#### Configuration - -When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm. - -![add AZ](images/l2dc1.png){.thumbnail} - -![add AZ](images/l2dc1-1.png){.thumbnail} - -The AZ configuration will then begin. - -![add AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![add AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the drop-down menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![add AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![add AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add routing configuration](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add routing configuration](images/l3dc3.png){.thumbnail} - -If you choose the type BGP, then enter the required information. - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section | - -![add routing configuration](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Network Focus | A prefix using CIDR notation | -| Next hop | An IP address acting as gateway in the subnetwork range | - -![add routing configuration](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone. - -![add routing configuration](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting a AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration to delete, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepop.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the related AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-ie.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-ie.md deleted file mode 100644 index e5e16420034..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-ie.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: Installation of OVHcloud Connect Direct from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Direct solution via the OVHcloud Control Panel.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Direct solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Step 1: Associating a vRack - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 2: Adding a PoP configuration - -> [!warning] -> Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further. -> - -> [!primary] -> For more details on the differences between levels L2 and L3, see our [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration - -Once you have linked your vRack, two `PoP configuration` menus will appear. Click the `Add a PoP configuration`{.action} button in the first menu, select L2 from the drop-down menu, then confirm. - -![adding PoP L2](images/pop2.png){.thumbnail} - -The L2 configuration will then be enabled in the `PoP configuration` menu. - -![adding PoP L2](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Once you have connected your vRack, click `Add a PoP configuration`{.action} and select the L3 configuration from the drop-down menu. - -![adding PoP L3](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![adding PoP L3](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![ajout PoP](images/l3pop2.png){.thumbnail} - -You can also add a second PoP L3 configuration via the second `PoP configuration` menu. - -### Step 3: Adding an availability zone configuration - -#### Configuration - -When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm. - -![add AZ](images/l2dc1.png){.thumbnail} - -![add AZ](images/l2dc1-1.png){.thumbnail} - -The AZ configuration will then begin. - -![add AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![add AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the drop-down menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![add AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![add AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add routing configuration](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add routing configuration](images/l3dc3.png){.thumbnail} - -If you choose the type BGP, then enter the required information. - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section | - -![add routing configuration](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Network Focus | A prefix using CIDR notation | -| Next hop | An IP address acting as gateway in the subnetwork range | - -![add routing configuration](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone. - -![add routing configuration](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting a AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration to delete, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepop.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the related AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-sg.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-sg.md deleted file mode 100644 index e5e16420034..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-sg.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: Installation of OVHcloud Connect Direct from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Direct solution via the OVHcloud Control Panel.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Direct solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Step 1: Associating a vRack - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 2: Adding a PoP configuration - -> [!warning] -> Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further. -> - -> [!primary] -> For more details on the differences between levels L2 and L3, see our [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration - -Once you have linked your vRack, two `PoP configuration` menus will appear. Click the `Add a PoP configuration`{.action} button in the first menu, select L2 from the drop-down menu, then confirm. - -![adding PoP L2](images/pop2.png){.thumbnail} - -The L2 configuration will then be enabled in the `PoP configuration` menu. - -![adding PoP L2](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Once you have connected your vRack, click `Add a PoP configuration`{.action} and select the L3 configuration from the drop-down menu. - -![adding PoP L3](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![adding PoP L3](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![ajout PoP](images/l3pop2.png){.thumbnail} - -You can also add a second PoP L3 configuration via the second `PoP configuration` menu. - -### Step 3: Adding an availability zone configuration - -#### Configuration - -When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm. - -![add AZ](images/l2dc1.png){.thumbnail} - -![add AZ](images/l2dc1-1.png){.thumbnail} - -The AZ configuration will then begin. - -![add AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![add AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the drop-down menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![add AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![add AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add routing configuration](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add routing configuration](images/l3dc3.png){.thumbnail} - -If you choose the type BGP, then enter the required information. - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section | - -![add routing configuration](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Network Focus | A prefix using CIDR notation | -| Next hop | An IP address acting as gateway in the subnetwork range | - -![add routing configuration](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone. - -![add routing configuration](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting a AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration to delete, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepop.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the related AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-us.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-us.md deleted file mode 100644 index e5e16420034..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.en-us.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: Installation of OVHcloud Connect Direct from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Direct solution via the OVHcloud Control Panel.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Direct solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Step 1: Associating a vRack - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 2: Adding a PoP configuration - -> [!warning] -> Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further. -> - -> [!primary] -> For more details on the differences between levels L2 and L3, see our [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration - -Once you have linked your vRack, two `PoP configuration` menus will appear. Click the `Add a PoP configuration`{.action} button in the first menu, select L2 from the drop-down menu, then confirm. - -![adding PoP L2](images/pop2.png){.thumbnail} - -The L2 configuration will then be enabled in the `PoP configuration` menu. - -![adding PoP L2](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Once you have connected your vRack, click `Add a PoP configuration`{.action} and select the L3 configuration from the drop-down menu. - -![adding PoP L3](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![adding PoP L3](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![ajout PoP](images/l3pop2.png){.thumbnail} - -You can also add a second PoP L3 configuration via the second `PoP configuration` menu. - -### Step 3: Adding an availability zone configuration - -#### Configuration - -When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm. - -![add AZ](images/l2dc1.png){.thumbnail} - -![add AZ](images/l2dc1-1.png){.thumbnail} - -The AZ configuration will then begin. - -![add AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![add AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the drop-down menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![add AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![add AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add routing configuration](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add routing configuration](images/l3dc3.png){.thumbnail} - -If you choose the type BGP, then enter the required information. - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section | - -![add routing configuration](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Network Focus | A prefix using CIDR notation | -| Next hop | An IP address acting as gateway in the subnetwork range | - -![add routing configuration](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone. - -![add routing configuration](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting a AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration to delete, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepop.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the related AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.es-es.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.es-es.md deleted file mode 100644 index e5e16420034..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.es-es.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: Installation of OVHcloud Connect Direct from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Direct solution via the OVHcloud Control Panel.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Direct solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Step 1: Associating a vRack - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 2: Adding a PoP configuration - -> [!warning] -> Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further. -> - -> [!primary] -> For more details on the differences between levels L2 and L3, see our [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration - -Once you have linked your vRack, two `PoP configuration` menus will appear. Click the `Add a PoP configuration`{.action} button in the first menu, select L2 from the drop-down menu, then confirm. - -![adding PoP L2](images/pop2.png){.thumbnail} - -The L2 configuration will then be enabled in the `PoP configuration` menu. - -![adding PoP L2](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Once you have connected your vRack, click `Add a PoP configuration`{.action} and select the L3 configuration from the drop-down menu. - -![adding PoP L3](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![adding PoP L3](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![ajout PoP](images/l3pop2.png){.thumbnail} - -You can also add a second PoP L3 configuration via the second `PoP configuration` menu. - -### Step 3: Adding an availability zone configuration - -#### Configuration - -When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm. - -![add AZ](images/l2dc1.png){.thumbnail} - -![add AZ](images/l2dc1-1.png){.thumbnail} - -The AZ configuration will then begin. - -![add AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![add AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the drop-down menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![add AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![add AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add routing configuration](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add routing configuration](images/l3dc3.png){.thumbnail} - -If you choose the type BGP, then enter the required information. - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section | - -![add routing configuration](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Network Focus | A prefix using CIDR notation | -| Next hop | An IP address acting as gateway in the subnetwork range | - -![add routing configuration](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone. - -![add routing configuration](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting a AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration to delete, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepop.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the related AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.es-us.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.es-us.md deleted file mode 100644 index 5bd4bfc7cb5..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.es-us.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -title: Installation of OVHcloud Connect Direct from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Direct solution via the OVHcloud Control Panel.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Direct solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) -- Access to the [OVHcloud Control Panel](/links/manager) - -## Instructions - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and click on `Network`{.action}. Next, open `OVHcloud Connect`{.action} and click on your solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Step 1: Associating a vRack - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 2: Adding a PoP configuration - -> [!warning] -> Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further. -> - -> [!primary] -> For more details on the differences between levels L2 and L3, see our [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration - -Once you have linked your vRack, two `PoP configuration` menus will appear. Click the `Add a PoP configuration`{.action} button in the first menu, select L2 from the drop-down menu, then confirm. - -![adding PoP L2](images/pop2.png){.thumbnail} - -The L2 configuration will then be enabled in the `PoP configuration` menu. - -![adding PoP L2](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Once you have connected your vRack, click `Add a PoP configuration`{.action} and select the L3 configuration from the drop-down menu. - -![adding PoP L3](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![adding PoP L3](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![ajout PoP](images/l3pop2.png){.thumbnail} - -You can also add a second PoP L3 configuration via the second `PoP configuration` menu. - -### Step 3: Adding an availability zone configuration - -#### Configuration - -When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm. - -![add AZ](images/l2dc1.png){.thumbnail} - -![add AZ](images/l2dc1-1.png){.thumbnail} - -The AZ configuration will then begin. - -![add AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![add AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the drop-down menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![add AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![add AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add routing configuration](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add routing configuration](images/l3dc3.png){.thumbnail} - -If you choose the type BGP, then enter the required information. - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section | - -![add routing configuration](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Network Focus | A prefix using CIDR notation | -| Next hop | An IP address acting as gateway in the subnetwork range | - -![add routing configuration](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone. - -![add routing configuration](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting a AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration to delete, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepop.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the related AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.fr-ca.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.fr-ca.md deleted file mode 100644 index b9cefc22f1a..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.fr-ca.md +++ /dev/null @@ -1,196 +0,0 @@ ---- -title: Mise en service de OVHcloud Connect Direct depuis l’espace client OVHcloud -excerpt: Découvrez comment mettre en service votre offre OVHcloud Connect Direct depuis votre espace client OVHcloud -updated: 2025-07-15 ---- - -## Objectif - -OVHcloud Connect permet d’étendre votre réseau d’entreprise avec votre réseau privé OVHcloud vRack sans passer par la création d’un tunnel VPN à travers Internet. Cette connexion sera ainsi plus rapide, plus fiable et avec une bande passante garantie. - -**Ce guide vous présente la mise en service de l'offre OVHcloud Connect Direct depuis l'espace client OVHcloud** - -## Prérequis - -> [!warning] -> Pour assurer un fonctionnement correct de ce service, vous devez prendre connaissance des [capacités et limites techniques de l'offre OVHcloud Connect](/pages/network/ovhcloud_connect/occ-limits) et configurer vos équipements réseau en accord avec celles-ci. -> - -- Posséder une [offre OVHcloud Connect Direct](/links/network/ovhcloud-connect) -- Disposer d'un [vRack OVHcloud](/links/network/vrack) - - ---- - -### Accès à l'espace client OVHcloud - -- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## En pratique - -Cliquez sur votre offre OVHcloud Connect. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Étape 1: associer un vRack - -Vous devez commencer par associer un vRack à votre offre. Cliquez sur le bouton `Associer un vRack`{.action} et sélectionnez un vRack existant dans le menu déroulant. - -![associate vRack](images/vrack01.png){.thumbnail} - -Un message vous confirmera l'association du vRack. - -![associate vRack](images/vrack2.png){.thumbnail} - -### Étape 2: ajouter une configuration PoP - -> [!warning] -> Un changement de configuration PoP de L2 à L3, ou inversement, nécessiterait de supprimer toute la configuration. Nous vous conseillons donc de bien réfléchir à votre choix de configuration avant d'aller plus loin. -> - -> [!primary] -> Pour plus de détails sur les différences entre les niveaux L2 et L3, consultez notre [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration L2 - -Une fois votre vRack associé, deux menus `Configuration PoP` apparaîtront. Cliquez sur `Ajouter une configuration PoP`{.action} dans le premier menu, sélectionnez L2 dans le menu déroulant puis validez. - -![ajout Pop](images/pop2.png){.thumbnail} - -La configuration L2 sera alors activée dans les deux menus `Configuration PoP`. - -![ajout Pop](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Une fois votre vRack associé, cliquez sur `Ajouter une configuration PoP`{.action} et sélectionnez la configuration L3 dans le menu déroulant. - -![ajout Pop](images/pop1.png){.thumbnail} - -Vous devrez alors saisir les éléments suivants : - -| Information | Description | -|:-------:|:------:| -| ASN client | Votre numéro d'AS BGP, qui est configuré sur votre routeur situé dans le PoP | -| ASN OVHcloud | Le numéro d'AS OVHcloud qui sera configuré sur les routeurs de OVHcloud Connect situés dans le PoP | -| Sous-réseau en /30 | Un bloc IPv4 de taille /30, utilisé pour le lien entre votre routeur et le routeur OVHcloud Connect situé dans le PoP | - -![ajout Pop](images/l3pop1-1.png){.thumbnail} - -Le menu `Configuration PoP` apparaîtra alors. - -![ajout Pop](images/l3pop2.png){.thumbnail} - -Vous pouvez également ajouter une seconde configuration PoP L3 via le deuxième menu `Configuration PoP` qui vous sera présenté. - -### Étape 3: ajout d'une configuration Zone de disponibilité - -#### Configuration L2 - -Lorsque votre configuration PoP est active, cliquez sur `Ajouter une configuration`{.action} sous le menu `Configuration AZ`. Sélectionnez une zone de disponibilité dans le menu déroulant et validez. - -![ajout AZ](images/l2dc1.png){.thumbnail} - -![ajout AZ](images/l2dc1-1.png){.thumbnail} - -La configuration de la zone de disponibilité débutera alors. - -![ajout AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -Lorsque votre configuration PoP a été définie, cliquez sur `Ajouter une configuration`{.action} sous le menu `Configuration AZ`. - -![ajout AZ](images/l3dc0.png){.thumbnail} - -Sélectionnez une zone de disponibilité dans le menu déroulant puis renseignez les informations requises. - -| Information | Description | -|:-------:|:------:| -| ASN OVHcloud | Le numéro d'AS OVHcloud qui sera configuré sur les routeurs OVHcloud Connect situés dans l'AZ. Ce numéro peut être différent de l'ASN choisi pour le PoP | -| Sous-réseau en /28 | Un sous-réseau privé configuré dans votre vRack dans l'AZ sélectionnée. Cela peut être un bloc IPv4 de taille /28 ou supérieur | - -![ajout AZ](images/l3dc1.png){.thumbnail} - -Vous pouvez ajouter des configurations Zone de disponibilité supplémentaires en cliquant sur le bouton `+ Ajouter une configuration`{.action}. - -![ajout AZ](images/l3dc1-1.png){.thumbnail} - -Vous devez également ajouter une configuration de routage. - -##### **Ajout d'une configuration de routage** - -Cliquez sur le bouton `(...)`{.action} sur la zone de disponibilité voulue puis sur `Ajouter configuration de routage`{.action}. - -![ajout AZ](images/l3dc2.png){.thumbnail} - -Choisissez alors le type de routage entre « Static » et « BGP ». - -![ajout AZ](images/l3dc3.png){.thumbnail} - -Si vous choisissez le type « BGP », saisissez alors les informations requises. - -| Information | Description | -|:-------:|:------:| -| ASN client | Votre numéro d'AS BGP, qui est configuré sur votre routeur situé dans l'AZ | -| IP Neighbor | Adresse IP du neighbor BGP de votre routeur dans l'AZ. Cette adresse doit faire partie du sous-réseau renseigné dans la `Configuration AZ` | - -![ajout AZ](images/l3dc5.png){.thumbnail} - -Si vous choisissez le type « Static », saisissez les informations requises : - -| Information | Description | -|:-------:|:------:| -| Sous-réseau | Un préfixe utilisant la notation CIDR | -| Nexthop | Adresse IP agissant comme passerelle dans la plage de sous-réseau | - -![ajout AZ](images/l3dc4.png){.thumbnail} - -Vous pouvez ajouter plusieurs configurations de routage au sein d'une même zone de disponibilité. Le type de configuration (BGP ou Static) choisi sur votre première configuration de routage s'appliquera alors aux suivantes sur la même zone de disponibilité. - -![ajout AZ](images/l3dc6.png){.thumbnail} - -### Suppression des ressources - -Chaque ressource (PoP ou AZ) peut être supprimée individuellement, mais la suppression d’une ressource parente telle que AZ ou POP supprimera automatiquement toutes les sous-ressources. - -La suppression récursive est plus lente que la suppression séquentielle de chaque ressource. - -> [!primary] -> Si une configuration AZ est partagée entre au moins deux services OVHcloud Connect, la suppression de la configuration PoP d’un seul service OVHcloud Connect n’affectera pas la ressource AZ. -> -#### Suppression d'une configuration de routage - -Pour supprimer une configuration de routage, cliquez sur le bouton `(...)`{.action} sur la configuration de routage à supprimer puis sur `Supprimer`{.action}. - -![suppression configuration routage](images/deleterouting.png){.thumbnail} - -#### Suppression d'une configuration AZ - -Pour supprimer une configuration AZ, cliquez sur le bouton `(...)`{.action} sur la configuration AZ à supprimer puis sur `Supprimer`{.action}. - -![suppression configuration DC](images/deletedc.png){.thumbnail} - -> [!primary] -> La suppression d'une configuration AZ entraînera la suppression des configurations de routage liées. -> - -#### Suppression d'une configuration PoP - -Pour supprimer une configuration PoP, cliquez sur le bouton `(...)`{.action} sur la configuration PoP à supprimer puis sur `Supprimer la configuration`{.action}. - -![suppression configuration PoP](images/deletepop.png){.thumbnail} - -> [!primary] -> La suppression d'une configuration PoP entraînera la suppression des configurations AZ et de routage liées. -> - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.fr-fr.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.fr-fr.md deleted file mode 100644 index b9cefc22f1a..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.fr-fr.md +++ /dev/null @@ -1,196 +0,0 @@ ---- -title: Mise en service de OVHcloud Connect Direct depuis l’espace client OVHcloud -excerpt: Découvrez comment mettre en service votre offre OVHcloud Connect Direct depuis votre espace client OVHcloud -updated: 2025-07-15 ---- - -## Objectif - -OVHcloud Connect permet d’étendre votre réseau d’entreprise avec votre réseau privé OVHcloud vRack sans passer par la création d’un tunnel VPN à travers Internet. Cette connexion sera ainsi plus rapide, plus fiable et avec une bande passante garantie. - -**Ce guide vous présente la mise en service de l'offre OVHcloud Connect Direct depuis l'espace client OVHcloud** - -## Prérequis - -> [!warning] -> Pour assurer un fonctionnement correct de ce service, vous devez prendre connaissance des [capacités et limites techniques de l'offre OVHcloud Connect](/pages/network/ovhcloud_connect/occ-limits) et configurer vos équipements réseau en accord avec celles-ci. -> - -- Posséder une [offre OVHcloud Connect Direct](/links/network/ovhcloud-connect) -- Disposer d'un [vRack OVHcloud](/links/network/vrack) - - ---- - -### Accès à l'espace client OVHcloud - -- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## En pratique - -Cliquez sur votre offre OVHcloud Connect. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Étape 1: associer un vRack - -Vous devez commencer par associer un vRack à votre offre. Cliquez sur le bouton `Associer un vRack`{.action} et sélectionnez un vRack existant dans le menu déroulant. - -![associate vRack](images/vrack01.png){.thumbnail} - -Un message vous confirmera l'association du vRack. - -![associate vRack](images/vrack2.png){.thumbnail} - -### Étape 2: ajouter une configuration PoP - -> [!warning] -> Un changement de configuration PoP de L2 à L3, ou inversement, nécessiterait de supprimer toute la configuration. Nous vous conseillons donc de bien réfléchir à votre choix de configuration avant d'aller plus loin. -> - -> [!primary] -> Pour plus de détails sur les différences entre les niveaux L2 et L3, consultez notre [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration L2 - -Une fois votre vRack associé, deux menus `Configuration PoP` apparaîtront. Cliquez sur `Ajouter une configuration PoP`{.action} dans le premier menu, sélectionnez L2 dans le menu déroulant puis validez. - -![ajout Pop](images/pop2.png){.thumbnail} - -La configuration L2 sera alors activée dans les deux menus `Configuration PoP`. - -![ajout Pop](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Une fois votre vRack associé, cliquez sur `Ajouter une configuration PoP`{.action} et sélectionnez la configuration L3 dans le menu déroulant. - -![ajout Pop](images/pop1.png){.thumbnail} - -Vous devrez alors saisir les éléments suivants : - -| Information | Description | -|:-------:|:------:| -| ASN client | Votre numéro d'AS BGP, qui est configuré sur votre routeur situé dans le PoP | -| ASN OVHcloud | Le numéro d'AS OVHcloud qui sera configuré sur les routeurs de OVHcloud Connect situés dans le PoP | -| Sous-réseau en /30 | Un bloc IPv4 de taille /30, utilisé pour le lien entre votre routeur et le routeur OVHcloud Connect situé dans le PoP | - -![ajout Pop](images/l3pop1-1.png){.thumbnail} - -Le menu `Configuration PoP` apparaîtra alors. - -![ajout Pop](images/l3pop2.png){.thumbnail} - -Vous pouvez également ajouter une seconde configuration PoP L3 via le deuxième menu `Configuration PoP` qui vous sera présenté. - -### Étape 3: ajout d'une configuration Zone de disponibilité - -#### Configuration L2 - -Lorsque votre configuration PoP est active, cliquez sur `Ajouter une configuration`{.action} sous le menu `Configuration AZ`. Sélectionnez une zone de disponibilité dans le menu déroulant et validez. - -![ajout AZ](images/l2dc1.png){.thumbnail} - -![ajout AZ](images/l2dc1-1.png){.thumbnail} - -La configuration de la zone de disponibilité débutera alors. - -![ajout AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -Lorsque votre configuration PoP a été définie, cliquez sur `Ajouter une configuration`{.action} sous le menu `Configuration AZ`. - -![ajout AZ](images/l3dc0.png){.thumbnail} - -Sélectionnez une zone de disponibilité dans le menu déroulant puis renseignez les informations requises. - -| Information | Description | -|:-------:|:------:| -| ASN OVHcloud | Le numéro d'AS OVHcloud qui sera configuré sur les routeurs OVHcloud Connect situés dans l'AZ. Ce numéro peut être différent de l'ASN choisi pour le PoP | -| Sous-réseau en /28 | Un sous-réseau privé configuré dans votre vRack dans l'AZ sélectionnée. Cela peut être un bloc IPv4 de taille /28 ou supérieur | - -![ajout AZ](images/l3dc1.png){.thumbnail} - -Vous pouvez ajouter des configurations Zone de disponibilité supplémentaires en cliquant sur le bouton `+ Ajouter une configuration`{.action}. - -![ajout AZ](images/l3dc1-1.png){.thumbnail} - -Vous devez également ajouter une configuration de routage. - -##### **Ajout d'une configuration de routage** - -Cliquez sur le bouton `(...)`{.action} sur la zone de disponibilité voulue puis sur `Ajouter configuration de routage`{.action}. - -![ajout AZ](images/l3dc2.png){.thumbnail} - -Choisissez alors le type de routage entre « Static » et « BGP ». - -![ajout AZ](images/l3dc3.png){.thumbnail} - -Si vous choisissez le type « BGP », saisissez alors les informations requises. - -| Information | Description | -|:-------:|:------:| -| ASN client | Votre numéro d'AS BGP, qui est configuré sur votre routeur situé dans l'AZ | -| IP Neighbor | Adresse IP du neighbor BGP de votre routeur dans l'AZ. Cette adresse doit faire partie du sous-réseau renseigné dans la `Configuration AZ` | - -![ajout AZ](images/l3dc5.png){.thumbnail} - -Si vous choisissez le type « Static », saisissez les informations requises : - -| Information | Description | -|:-------:|:------:| -| Sous-réseau | Un préfixe utilisant la notation CIDR | -| Nexthop | Adresse IP agissant comme passerelle dans la plage de sous-réseau | - -![ajout AZ](images/l3dc4.png){.thumbnail} - -Vous pouvez ajouter plusieurs configurations de routage au sein d'une même zone de disponibilité. Le type de configuration (BGP ou Static) choisi sur votre première configuration de routage s'appliquera alors aux suivantes sur la même zone de disponibilité. - -![ajout AZ](images/l3dc6.png){.thumbnail} - -### Suppression des ressources - -Chaque ressource (PoP ou AZ) peut être supprimée individuellement, mais la suppression d’une ressource parente telle que AZ ou POP supprimera automatiquement toutes les sous-ressources. - -La suppression récursive est plus lente que la suppression séquentielle de chaque ressource. - -> [!primary] -> Si une configuration AZ est partagée entre au moins deux services OVHcloud Connect, la suppression de la configuration PoP d’un seul service OVHcloud Connect n’affectera pas la ressource AZ. -> -#### Suppression d'une configuration de routage - -Pour supprimer une configuration de routage, cliquez sur le bouton `(...)`{.action} sur la configuration de routage à supprimer puis sur `Supprimer`{.action}. - -![suppression configuration routage](images/deleterouting.png){.thumbnail} - -#### Suppression d'une configuration AZ - -Pour supprimer une configuration AZ, cliquez sur le bouton `(...)`{.action} sur la configuration AZ à supprimer puis sur `Supprimer`{.action}. - -![suppression configuration DC](images/deletedc.png){.thumbnail} - -> [!primary] -> La suppression d'une configuration AZ entraînera la suppression des configurations de routage liées. -> - -#### Suppression d'une configuration PoP - -Pour supprimer une configuration PoP, cliquez sur le bouton `(...)`{.action} sur la configuration PoP à supprimer puis sur `Supprimer la configuration`{.action}. - -![suppression configuration PoP](images/deletepop.png){.thumbnail} - -> [!primary] -> La suppression d'une configuration PoP entraînera la suppression des configurations AZ et de routage liées. -> - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.it-it.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.it-it.md deleted file mode 100644 index e5e16420034..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.it-it.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: Installation of OVHcloud Connect Direct from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Direct solution via the OVHcloud Control Panel.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Direct solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Step 1: Associating a vRack - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 2: Adding a PoP configuration - -> [!warning] -> Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further. -> - -> [!primary] -> For more details on the differences between levels L2 and L3, see our [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration - -Once you have linked your vRack, two `PoP configuration` menus will appear. Click the `Add a PoP configuration`{.action} button in the first menu, select L2 from the drop-down menu, then confirm. - -![adding PoP L2](images/pop2.png){.thumbnail} - -The L2 configuration will then be enabled in the `PoP configuration` menu. - -![adding PoP L2](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Once you have connected your vRack, click `Add a PoP configuration`{.action} and select the L3 configuration from the drop-down menu. - -![adding PoP L3](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![adding PoP L3](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![ajout PoP](images/l3pop2.png){.thumbnail} - -You can also add a second PoP L3 configuration via the second `PoP configuration` menu. - -### Step 3: Adding an availability zone configuration - -#### Configuration - -When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm. - -![add AZ](images/l2dc1.png){.thumbnail} - -![add AZ](images/l2dc1-1.png){.thumbnail} - -The AZ configuration will then begin. - -![add AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![add AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the drop-down menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![add AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![add AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add routing configuration](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add routing configuration](images/l3dc3.png){.thumbnail} - -If you choose the type BGP, then enter the required information. - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section | - -![add routing configuration](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Network Focus | A prefix using CIDR notation | -| Next hop | An IP address acting as gateway in the subnetwork range | - -![add routing configuration](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone. - -![add routing configuration](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting a AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration to delete, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepop.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the related AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.pl-pl.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.pl-pl.md deleted file mode 100644 index e5e16420034..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.pl-pl.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: Installation of OVHcloud Connect Direct from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Direct solution via the OVHcloud Control Panel.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Direct solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Step 1: Associating a vRack - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 2: Adding a PoP configuration - -> [!warning] -> Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further. -> - -> [!primary] -> For more details on the differences between levels L2 and L3, see our [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration - -Once you have linked your vRack, two `PoP configuration` menus will appear. Click the `Add a PoP configuration`{.action} button in the first menu, select L2 from the drop-down menu, then confirm. - -![adding PoP L2](images/pop2.png){.thumbnail} - -The L2 configuration will then be enabled in the `PoP configuration` menu. - -![adding PoP L2](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Once you have connected your vRack, click `Add a PoP configuration`{.action} and select the L3 configuration from the drop-down menu. - -![adding PoP L3](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![adding PoP L3](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![ajout PoP](images/l3pop2.png){.thumbnail} - -You can also add a second PoP L3 configuration via the second `PoP configuration` menu. - -### Step 3: Adding an availability zone configuration - -#### Configuration - -When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm. - -![add AZ](images/l2dc1.png){.thumbnail} - -![add AZ](images/l2dc1-1.png){.thumbnail} - -The AZ configuration will then begin. - -![add AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![add AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the drop-down menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![add AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![add AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add routing configuration](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add routing configuration](images/l3dc3.png){.thumbnail} - -If you choose the type BGP, then enter the required information. - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section | - -![add routing configuration](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Network Focus | A prefix using CIDR notation | -| Next hop | An IP address acting as gateway in the subnetwork range | - -![add routing configuration](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone. - -![add routing configuration](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting a AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration to delete, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepop.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the related AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.pt-pt.md b/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.pt-pt.md deleted file mode 100644 index e5e16420034..00000000000 --- a/pages/network/ovhcloud_connect/occ-direct-control-panel/guide.pt-pt.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: Installation of OVHcloud Connect Direct from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Direct solution via the OVHcloud Control Panel.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Direct solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -### Step 1: Associating a vRack - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 2: Adding a PoP configuration - -> [!warning] -> Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further. -> - -> [!primary] -> For more details on the differences between levels L2 and L3, see our [FAQ](/pages/network/ovhcloud_connect/occdedicated-faq). -> - -#### Configuration - -Once you have linked your vRack, two `PoP configuration` menus will appear. Click the `Add a PoP configuration`{.action} button in the first menu, select L2 from the drop-down menu, then confirm. - -![adding PoP L2](images/pop2.png){.thumbnail} - -The L2 configuration will then be enabled in the `PoP configuration` menu. - -![adding PoP L2](images/l2pop2.png){.thumbnail} - -#### Configuration L3 - -Once you have connected your vRack, click `Add a PoP configuration`{.action} and select the L3 configuration from the drop-down menu. - -![adding PoP L3](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![adding PoP L3](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![ajout PoP](images/l3pop2.png){.thumbnail} - -You can also add a second PoP L3 configuration via the second `PoP configuration` menu. - -### Step 3: Adding an availability zone configuration - -#### Configuration - -When your PoP configuration is active, click `Add a configuration`{.action} under the `AZ configuration` menu. Select an availability zone from the drop-down menu and confirm. - -![add AZ](images/l2dc1.png){.thumbnail} - -![add AZ](images/l2dc1-1.png){.thumbnail} - -The AZ configuration will then begin. - -![add AZ](images/l2dc1-2.png){.thumbnail} - -#### Configuration L3 - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![add AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the drop-down menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![add AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![add AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `(...)`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add routing configuration](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add routing configuration](images/l3dc3.png){.thumbnail} - -If you choose the type BGP, then enter the required information. - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnetwork specified in the `AZ Configuration` section | - -![add routing configuration](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Network Focus | A prefix using CIDR notation | -| Next hop | An IP address acting as gateway in the subnetwork range | - -![add routing configuration](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same availability zone. - -![add routing configuration](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or PoP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting a AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration to delete, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepop.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the related AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/deletedc.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/deletedc.png deleted file mode 100644 index a67ef16533f..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/deletedc.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/deletepop.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/deletepop.png deleted file mode 100644 index f72091af051..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/deletepop.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/deleterouting.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/deleterouting.png deleted file mode 100644 index e81ce8472b8..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/deleterouting.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l2dc1-1.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l2dc1-1.png deleted file mode 100644 index c7d419cda6e..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l2dc1-1.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l2dc1-2.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l2dc1-2.png deleted file mode 100644 index 1aac72432c8..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l2dc1-2.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l2dc1.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l2dc1.png deleted file mode 100644 index 0f41d687669..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l2dc1.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l2pop2.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l2pop2.png deleted file mode 100644 index b85a4ec2eb7..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l2pop2.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc0.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc0.png deleted file mode 100644 index 0f41d687669..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc0.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc1-1.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc1-1.png deleted file mode 100644 index 39c3a93d016..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc1-1.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc1.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc1.png deleted file mode 100644 index a339eb59a37..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc1.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc2.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc2.png deleted file mode 100644 index 344db725880..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc2.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc3.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc3.png deleted file mode 100644 index 52eb63d5b5e..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc3.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc4.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc4.png deleted file mode 100644 index 0889754d659..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc4.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc5.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc5.png deleted file mode 100644 index 71dcb9cf158..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc5.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc6.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc6.png deleted file mode 100644 index 467788ced39..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3dc6.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3pop1-1.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3pop1-1.png deleted file mode 100644 index 34b8c4ab655..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3pop1-1.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3pop2.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3pop2.png deleted file mode 100644 index dcbf5565784..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/l3pop2.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/occ_01.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/occ_01.png deleted file mode 100644 index 2465d4aeaee..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/occ_01.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/pop1.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/pop1.png deleted file mode 100644 index 3a039fa0dca..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/pop1.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/pop2.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/pop2.png deleted file mode 100644 index d2c6ee81c7a..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/pop2.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/vrack01.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/vrack01.png deleted file mode 100644 index 78c56edf1dc..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/vrack01.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/vrack2.png b/pages/network/ovhcloud_connect/occ-direct-control-panel/images/vrack2.png deleted file mode 100644 index 2ed3acd7aee..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-direct-control-panel/images/vrack2.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.de-de.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.de-de.md deleted file mode 100644 index a9207b2a78b..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.de-de.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Configuration of OVHcloud Connect using OVHcloud APIv6 -excerpt: 'Find out how to set up OVHcloud Connect using OVHcloud APIv6' -updated: 2020-09-14 ---- - -## Objective - -Configuring the OVHcloud Connect solution can be done via API. - -**Find out how to set up OVHcloud Connect using OVHcloud APIv6.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) - -## Instructions - -### Step 1: Configuring vRack - -As a mandatory first step, the service must be interconnected with a vRack to enable the configuration. - -Verify that the service is available with the following call: - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -It will return UUIDs of eligible services. Then you can link OVHcloud Connect with the vRack: - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Enter the vRack name as well as the UUID of OVHcloud Connect. - -### Step 2: Configuring the PoP - -This step is important because you have to choose between L2 and L3. - -> [!warning] -> Please be aware of the ramifications of this decision. To switch between L2 and L3 later, you will have to delete the whole configuration. -> - -#### Obtaining the interface ID - -Your service is attached to an interface with an ID. Use this call to obtain the ID: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -It will return the ID of the interface dedicated to your service. - -The following call provides more service details: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -The LightStatus parameter is refreshed every 5 minutes for monitoring purposes. - -#### Configuration with Layer 2 (L2) - -This is the simplest configuration. Use this call: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L2. - -#### Configuration with Layer 3 (L3) - -This configuration is more complex because of the required BGP settings: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L3. -- customerBgpArea: your BGP ASN, configured on your device which will be used for peering. -- ovhBgpArea: BGP ASN to be configured on the OVHcloud routing instance, pertaining to BGP session and AS path. -- subnet: a /30 IPv4 block. - -### Step 3: Data centre (DC) configuration - -> [!primary] -> If an OVHcloud Connect service is already configured in the vRack, the second service will inherit the data centre configuration. -> - -#### Obtaining available data centres - -You can list available data centres for configuration using the following calls: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration with Layer 2 (L2) - -Only the ID of the data centre is needed for the L2 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. - -#### Configuration with Layer 3 (L3) - -More parameters have to be provided for the L3 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. -- ovhBgpArea: as with the PoP, you need to assign an ASN for the OVHcloud routing instance. It will appear in AS path. (It can be different from the PoP ASN.) -- subnet: an IPv4 block, any size is accepted from /28. - -By default, the data centre will be configured with a VRRP instance. You have to proceed with the next steps for static routing or dynamic routing using BGP. - -#### Layer 3 option: static route - -A static route is needed when you have one or more subnets behind a gateway. This may be Linux gateway (with IP forwarding enabled), a NSX edge or any instance capable of routing. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- nextHop: IP address in the subnet range acting as gateway. -- subnet: a prefix using the CIDR notation. -- type: 'network' - -#### Layer 3 option: BGP session - -A BGP session enables dynamic routing from your routing instance with OVHcloud Connect. Announcements are dynamically managed using the BGP protocol. Enabling a BGP session disables the VRRP configuration. You cannot have a BGP session and a static route in the same DC configuration. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- bgpNeighborArea: your BGP ASN. -- bgpNeighborIp: your IP address in the subnet range. -- type: 'bgp' - -### Removing resources - -Each resource can be deleted individually, but deleting a parent resource like DC or PoP will automatically delete all sub-resources. However, recursive deletion is slower than a sequential deletion of each resource. - -#### Global deletion - -The following call recursively deletes the entire configuration of an OVHcloud Connect service: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -Each sub-resource's status will change from 'active' to 'toDelete' but it takes some time to see the status change. - -Only one task ID is created. - -#### Deleting by resource - -Each resource can be deleted individually using the following call that will delete the smallest resource (extra): - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -The following call removes the DC configuration and recursively deletes any additional sub-resources: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -When all sub-resources have been deleted, the PoP configuration can be safely removed: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -> [!primary] -> If a DC configuration is shared between two or more OVHcloud Connect services, deleting the PoP configuration of only one will not affect the DC ressource. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-asia.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-asia.md deleted file mode 100644 index a9207b2a78b..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-asia.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Configuration of OVHcloud Connect using OVHcloud APIv6 -excerpt: 'Find out how to set up OVHcloud Connect using OVHcloud APIv6' -updated: 2020-09-14 ---- - -## Objective - -Configuring the OVHcloud Connect solution can be done via API. - -**Find out how to set up OVHcloud Connect using OVHcloud APIv6.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) - -## Instructions - -### Step 1: Configuring vRack - -As a mandatory first step, the service must be interconnected with a vRack to enable the configuration. - -Verify that the service is available with the following call: - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -It will return UUIDs of eligible services. Then you can link OVHcloud Connect with the vRack: - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Enter the vRack name as well as the UUID of OVHcloud Connect. - -### Step 2: Configuring the PoP - -This step is important because you have to choose between L2 and L3. - -> [!warning] -> Please be aware of the ramifications of this decision. To switch between L2 and L3 later, you will have to delete the whole configuration. -> - -#### Obtaining the interface ID - -Your service is attached to an interface with an ID. Use this call to obtain the ID: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -It will return the ID of the interface dedicated to your service. - -The following call provides more service details: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -The LightStatus parameter is refreshed every 5 minutes for monitoring purposes. - -#### Configuration with Layer 2 (L2) - -This is the simplest configuration. Use this call: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L2. - -#### Configuration with Layer 3 (L3) - -This configuration is more complex because of the required BGP settings: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L3. -- customerBgpArea: your BGP ASN, configured on your device which will be used for peering. -- ovhBgpArea: BGP ASN to be configured on the OVHcloud routing instance, pertaining to BGP session and AS path. -- subnet: a /30 IPv4 block. - -### Step 3: Data centre (DC) configuration - -> [!primary] -> If an OVHcloud Connect service is already configured in the vRack, the second service will inherit the data centre configuration. -> - -#### Obtaining available data centres - -You can list available data centres for configuration using the following calls: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration with Layer 2 (L2) - -Only the ID of the data centre is needed for the L2 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. - -#### Configuration with Layer 3 (L3) - -More parameters have to be provided for the L3 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. -- ovhBgpArea: as with the PoP, you need to assign an ASN for the OVHcloud routing instance. It will appear in AS path. (It can be different from the PoP ASN.) -- subnet: an IPv4 block, any size is accepted from /28. - -By default, the data centre will be configured with a VRRP instance. You have to proceed with the next steps for static routing or dynamic routing using BGP. - -#### Layer 3 option: static route - -A static route is needed when you have one or more subnets behind a gateway. This may be Linux gateway (with IP forwarding enabled), a NSX edge or any instance capable of routing. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- nextHop: IP address in the subnet range acting as gateway. -- subnet: a prefix using the CIDR notation. -- type: 'network' - -#### Layer 3 option: BGP session - -A BGP session enables dynamic routing from your routing instance with OVHcloud Connect. Announcements are dynamically managed using the BGP protocol. Enabling a BGP session disables the VRRP configuration. You cannot have a BGP session and a static route in the same DC configuration. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- bgpNeighborArea: your BGP ASN. -- bgpNeighborIp: your IP address in the subnet range. -- type: 'bgp' - -### Removing resources - -Each resource can be deleted individually, but deleting a parent resource like DC or PoP will automatically delete all sub-resources. However, recursive deletion is slower than a sequential deletion of each resource. - -#### Global deletion - -The following call recursively deletes the entire configuration of an OVHcloud Connect service: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -Each sub-resource's status will change from 'active' to 'toDelete' but it takes some time to see the status change. - -Only one task ID is created. - -#### Deleting by resource - -Each resource can be deleted individually using the following call that will delete the smallest resource (extra): - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -The following call removes the DC configuration and recursively deletes any additional sub-resources: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -When all sub-resources have been deleted, the PoP configuration can be safely removed: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -> [!primary] -> If a DC configuration is shared between two or more OVHcloud Connect services, deleting the PoP configuration of only one will not affect the DC ressource. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-au.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-au.md deleted file mode 100644 index a9207b2a78b..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-au.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Configuration of OVHcloud Connect using OVHcloud APIv6 -excerpt: 'Find out how to set up OVHcloud Connect using OVHcloud APIv6' -updated: 2020-09-14 ---- - -## Objective - -Configuring the OVHcloud Connect solution can be done via API. - -**Find out how to set up OVHcloud Connect using OVHcloud APIv6.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) - -## Instructions - -### Step 1: Configuring vRack - -As a mandatory first step, the service must be interconnected with a vRack to enable the configuration. - -Verify that the service is available with the following call: - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -It will return UUIDs of eligible services. Then you can link OVHcloud Connect with the vRack: - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Enter the vRack name as well as the UUID of OVHcloud Connect. - -### Step 2: Configuring the PoP - -This step is important because you have to choose between L2 and L3. - -> [!warning] -> Please be aware of the ramifications of this decision. To switch between L2 and L3 later, you will have to delete the whole configuration. -> - -#### Obtaining the interface ID - -Your service is attached to an interface with an ID. Use this call to obtain the ID: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -It will return the ID of the interface dedicated to your service. - -The following call provides more service details: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -The LightStatus parameter is refreshed every 5 minutes for monitoring purposes. - -#### Configuration with Layer 2 (L2) - -This is the simplest configuration. Use this call: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L2. - -#### Configuration with Layer 3 (L3) - -This configuration is more complex because of the required BGP settings: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L3. -- customerBgpArea: your BGP ASN, configured on your device which will be used for peering. -- ovhBgpArea: BGP ASN to be configured on the OVHcloud routing instance, pertaining to BGP session and AS path. -- subnet: a /30 IPv4 block. - -### Step 3: Data centre (DC) configuration - -> [!primary] -> If an OVHcloud Connect service is already configured in the vRack, the second service will inherit the data centre configuration. -> - -#### Obtaining available data centres - -You can list available data centres for configuration using the following calls: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration with Layer 2 (L2) - -Only the ID of the data centre is needed for the L2 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. - -#### Configuration with Layer 3 (L3) - -More parameters have to be provided for the L3 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. -- ovhBgpArea: as with the PoP, you need to assign an ASN for the OVHcloud routing instance. It will appear in AS path. (It can be different from the PoP ASN.) -- subnet: an IPv4 block, any size is accepted from /28. - -By default, the data centre will be configured with a VRRP instance. You have to proceed with the next steps for static routing or dynamic routing using BGP. - -#### Layer 3 option: static route - -A static route is needed when you have one or more subnets behind a gateway. This may be Linux gateway (with IP forwarding enabled), a NSX edge or any instance capable of routing. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- nextHop: IP address in the subnet range acting as gateway. -- subnet: a prefix using the CIDR notation. -- type: 'network' - -#### Layer 3 option: BGP session - -A BGP session enables dynamic routing from your routing instance with OVHcloud Connect. Announcements are dynamically managed using the BGP protocol. Enabling a BGP session disables the VRRP configuration. You cannot have a BGP session and a static route in the same DC configuration. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- bgpNeighborArea: your BGP ASN. -- bgpNeighborIp: your IP address in the subnet range. -- type: 'bgp' - -### Removing resources - -Each resource can be deleted individually, but deleting a parent resource like DC or PoP will automatically delete all sub-resources. However, recursive deletion is slower than a sequential deletion of each resource. - -#### Global deletion - -The following call recursively deletes the entire configuration of an OVHcloud Connect service: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -Each sub-resource's status will change from 'active' to 'toDelete' but it takes some time to see the status change. - -Only one task ID is created. - -#### Deleting by resource - -Each resource can be deleted individually using the following call that will delete the smallest resource (extra): - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -The following call removes the DC configuration and recursively deletes any additional sub-resources: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -When all sub-resources have been deleted, the PoP configuration can be safely removed: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -> [!primary] -> If a DC configuration is shared between two or more OVHcloud Connect services, deleting the PoP configuration of only one will not affect the DC ressource. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ca.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ca.md deleted file mode 100644 index a9207b2a78b..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ca.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Configuration of OVHcloud Connect using OVHcloud APIv6 -excerpt: 'Find out how to set up OVHcloud Connect using OVHcloud APIv6' -updated: 2020-09-14 ---- - -## Objective - -Configuring the OVHcloud Connect solution can be done via API. - -**Find out how to set up OVHcloud Connect using OVHcloud APIv6.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) - -## Instructions - -### Step 1: Configuring vRack - -As a mandatory first step, the service must be interconnected with a vRack to enable the configuration. - -Verify that the service is available with the following call: - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -It will return UUIDs of eligible services. Then you can link OVHcloud Connect with the vRack: - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Enter the vRack name as well as the UUID of OVHcloud Connect. - -### Step 2: Configuring the PoP - -This step is important because you have to choose between L2 and L3. - -> [!warning] -> Please be aware of the ramifications of this decision. To switch between L2 and L3 later, you will have to delete the whole configuration. -> - -#### Obtaining the interface ID - -Your service is attached to an interface with an ID. Use this call to obtain the ID: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -It will return the ID of the interface dedicated to your service. - -The following call provides more service details: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -The LightStatus parameter is refreshed every 5 minutes for monitoring purposes. - -#### Configuration with Layer 2 (L2) - -This is the simplest configuration. Use this call: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L2. - -#### Configuration with Layer 3 (L3) - -This configuration is more complex because of the required BGP settings: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L3. -- customerBgpArea: your BGP ASN, configured on your device which will be used for peering. -- ovhBgpArea: BGP ASN to be configured on the OVHcloud routing instance, pertaining to BGP session and AS path. -- subnet: a /30 IPv4 block. - -### Step 3: Data centre (DC) configuration - -> [!primary] -> If an OVHcloud Connect service is already configured in the vRack, the second service will inherit the data centre configuration. -> - -#### Obtaining available data centres - -You can list available data centres for configuration using the following calls: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration with Layer 2 (L2) - -Only the ID of the data centre is needed for the L2 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. - -#### Configuration with Layer 3 (L3) - -More parameters have to be provided for the L3 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. -- ovhBgpArea: as with the PoP, you need to assign an ASN for the OVHcloud routing instance. It will appear in AS path. (It can be different from the PoP ASN.) -- subnet: an IPv4 block, any size is accepted from /28. - -By default, the data centre will be configured with a VRRP instance. You have to proceed with the next steps for static routing or dynamic routing using BGP. - -#### Layer 3 option: static route - -A static route is needed when you have one or more subnets behind a gateway. This may be Linux gateway (with IP forwarding enabled), a NSX edge or any instance capable of routing. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- nextHop: IP address in the subnet range acting as gateway. -- subnet: a prefix using the CIDR notation. -- type: 'network' - -#### Layer 3 option: BGP session - -A BGP session enables dynamic routing from your routing instance with OVHcloud Connect. Announcements are dynamically managed using the BGP protocol. Enabling a BGP session disables the VRRP configuration. You cannot have a BGP session and a static route in the same DC configuration. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- bgpNeighborArea: your BGP ASN. -- bgpNeighborIp: your IP address in the subnet range. -- type: 'bgp' - -### Removing resources - -Each resource can be deleted individually, but deleting a parent resource like DC or PoP will automatically delete all sub-resources. However, recursive deletion is slower than a sequential deletion of each resource. - -#### Global deletion - -The following call recursively deletes the entire configuration of an OVHcloud Connect service: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -Each sub-resource's status will change from 'active' to 'toDelete' but it takes some time to see the status change. - -Only one task ID is created. - -#### Deleting by resource - -Each resource can be deleted individually using the following call that will delete the smallest resource (extra): - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -The following call removes the DC configuration and recursively deletes any additional sub-resources: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -When all sub-resources have been deleted, the PoP configuration can be safely removed: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -> [!primary] -> If a DC configuration is shared between two or more OVHcloud Connect services, deleting the PoP configuration of only one will not affect the DC ressource. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-gb.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-gb.md deleted file mode 100644 index a9207b2a78b..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-gb.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Configuration of OVHcloud Connect using OVHcloud APIv6 -excerpt: 'Find out how to set up OVHcloud Connect using OVHcloud APIv6' -updated: 2020-09-14 ---- - -## Objective - -Configuring the OVHcloud Connect solution can be done via API. - -**Find out how to set up OVHcloud Connect using OVHcloud APIv6.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) - -## Instructions - -### Step 1: Configuring vRack - -As a mandatory first step, the service must be interconnected with a vRack to enable the configuration. - -Verify that the service is available with the following call: - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -It will return UUIDs of eligible services. Then you can link OVHcloud Connect with the vRack: - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Enter the vRack name as well as the UUID of OVHcloud Connect. - -### Step 2: Configuring the PoP - -This step is important because you have to choose between L2 and L3. - -> [!warning] -> Please be aware of the ramifications of this decision. To switch between L2 and L3 later, you will have to delete the whole configuration. -> - -#### Obtaining the interface ID - -Your service is attached to an interface with an ID. Use this call to obtain the ID: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -It will return the ID of the interface dedicated to your service. - -The following call provides more service details: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -The LightStatus parameter is refreshed every 5 minutes for monitoring purposes. - -#### Configuration with Layer 2 (L2) - -This is the simplest configuration. Use this call: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L2. - -#### Configuration with Layer 3 (L3) - -This configuration is more complex because of the required BGP settings: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L3. -- customerBgpArea: your BGP ASN, configured on your device which will be used for peering. -- ovhBgpArea: BGP ASN to be configured on the OVHcloud routing instance, pertaining to BGP session and AS path. -- subnet: a /30 IPv4 block. - -### Step 3: Data centre (DC) configuration - -> [!primary] -> If an OVHcloud Connect service is already configured in the vRack, the second service will inherit the data centre configuration. -> - -#### Obtaining available data centres - -You can list available data centres for configuration using the following calls: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration with Layer 2 (L2) - -Only the ID of the data centre is needed for the L2 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. - -#### Configuration with Layer 3 (L3) - -More parameters have to be provided for the L3 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. -- ovhBgpArea: as with the PoP, you need to assign an ASN for the OVHcloud routing instance. It will appear in AS path. (It can be different from the PoP ASN.) -- subnet: an IPv4 block, any size is accepted from /28. - -By default, the data centre will be configured with a VRRP instance. You have to proceed with the next steps for static routing or dynamic routing using BGP. - -#### Layer 3 option: static route - -A static route is needed when you have one or more subnets behind a gateway. This may be Linux gateway (with IP forwarding enabled), a NSX edge or any instance capable of routing. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- nextHop: IP address in the subnet range acting as gateway. -- subnet: a prefix using the CIDR notation. -- type: 'network' - -#### Layer 3 option: BGP session - -A BGP session enables dynamic routing from your routing instance with OVHcloud Connect. Announcements are dynamically managed using the BGP protocol. Enabling a BGP session disables the VRRP configuration. You cannot have a BGP session and a static route in the same DC configuration. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- bgpNeighborArea: your BGP ASN. -- bgpNeighborIp: your IP address in the subnet range. -- type: 'bgp' - -### Removing resources - -Each resource can be deleted individually, but deleting a parent resource like DC or PoP will automatically delete all sub-resources. However, recursive deletion is slower than a sequential deletion of each resource. - -#### Global deletion - -The following call recursively deletes the entire configuration of an OVHcloud Connect service: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -Each sub-resource's status will change from 'active' to 'toDelete' but it takes some time to see the status change. - -Only one task ID is created. - -#### Deleting by resource - -Each resource can be deleted individually using the following call that will delete the smallest resource (extra): - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -The following call removes the DC configuration and recursively deletes any additional sub-resources: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -When all sub-resources have been deleted, the PoP configuration can be safely removed: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -> [!primary] -> If a DC configuration is shared between two or more OVHcloud Connect services, deleting the PoP configuration of only one will not affect the DC ressource. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ie.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ie.md deleted file mode 100644 index a9207b2a78b..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-ie.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Configuration of OVHcloud Connect using OVHcloud APIv6 -excerpt: 'Find out how to set up OVHcloud Connect using OVHcloud APIv6' -updated: 2020-09-14 ---- - -## Objective - -Configuring the OVHcloud Connect solution can be done via API. - -**Find out how to set up OVHcloud Connect using OVHcloud APIv6.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) - -## Instructions - -### Step 1: Configuring vRack - -As a mandatory first step, the service must be interconnected with a vRack to enable the configuration. - -Verify that the service is available with the following call: - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -It will return UUIDs of eligible services. Then you can link OVHcloud Connect with the vRack: - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Enter the vRack name as well as the UUID of OVHcloud Connect. - -### Step 2: Configuring the PoP - -This step is important because you have to choose between L2 and L3. - -> [!warning] -> Please be aware of the ramifications of this decision. To switch between L2 and L3 later, you will have to delete the whole configuration. -> - -#### Obtaining the interface ID - -Your service is attached to an interface with an ID. Use this call to obtain the ID: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -It will return the ID of the interface dedicated to your service. - -The following call provides more service details: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -The LightStatus parameter is refreshed every 5 minutes for monitoring purposes. - -#### Configuration with Layer 2 (L2) - -This is the simplest configuration. Use this call: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L2. - -#### Configuration with Layer 3 (L3) - -This configuration is more complex because of the required BGP settings: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L3. -- customerBgpArea: your BGP ASN, configured on your device which will be used for peering. -- ovhBgpArea: BGP ASN to be configured on the OVHcloud routing instance, pertaining to BGP session and AS path. -- subnet: a /30 IPv4 block. - -### Step 3: Data centre (DC) configuration - -> [!primary] -> If an OVHcloud Connect service is already configured in the vRack, the second service will inherit the data centre configuration. -> - -#### Obtaining available data centres - -You can list available data centres for configuration using the following calls: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration with Layer 2 (L2) - -Only the ID of the data centre is needed for the L2 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. - -#### Configuration with Layer 3 (L3) - -More parameters have to be provided for the L3 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. -- ovhBgpArea: as with the PoP, you need to assign an ASN for the OVHcloud routing instance. It will appear in AS path. (It can be different from the PoP ASN.) -- subnet: an IPv4 block, any size is accepted from /28. - -By default, the data centre will be configured with a VRRP instance. You have to proceed with the next steps for static routing or dynamic routing using BGP. - -#### Layer 3 option: static route - -A static route is needed when you have one or more subnets behind a gateway. This may be Linux gateway (with IP forwarding enabled), a NSX edge or any instance capable of routing. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- nextHop: IP address in the subnet range acting as gateway. -- subnet: a prefix using the CIDR notation. -- type: 'network' - -#### Layer 3 option: BGP session - -A BGP session enables dynamic routing from your routing instance with OVHcloud Connect. Announcements are dynamically managed using the BGP protocol. Enabling a BGP session disables the VRRP configuration. You cannot have a BGP session and a static route in the same DC configuration. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- bgpNeighborArea: your BGP ASN. -- bgpNeighborIp: your IP address in the subnet range. -- type: 'bgp' - -### Removing resources - -Each resource can be deleted individually, but deleting a parent resource like DC or PoP will automatically delete all sub-resources. However, recursive deletion is slower than a sequential deletion of each resource. - -#### Global deletion - -The following call recursively deletes the entire configuration of an OVHcloud Connect service: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -Each sub-resource's status will change from 'active' to 'toDelete' but it takes some time to see the status change. - -Only one task ID is created. - -#### Deleting by resource - -Each resource can be deleted individually using the following call that will delete the smallest resource (extra): - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -The following call removes the DC configuration and recursively deletes any additional sub-resources: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -When all sub-resources have been deleted, the PoP configuration can be safely removed: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -> [!primary] -> If a DC configuration is shared between two or more OVHcloud Connect services, deleting the PoP configuration of only one will not affect the DC ressource. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-sg.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-sg.md deleted file mode 100644 index a9207b2a78b..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-sg.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Configuration of OVHcloud Connect using OVHcloud APIv6 -excerpt: 'Find out how to set up OVHcloud Connect using OVHcloud APIv6' -updated: 2020-09-14 ---- - -## Objective - -Configuring the OVHcloud Connect solution can be done via API. - -**Find out how to set up OVHcloud Connect using OVHcloud APIv6.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) - -## Instructions - -### Step 1: Configuring vRack - -As a mandatory first step, the service must be interconnected with a vRack to enable the configuration. - -Verify that the service is available with the following call: - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -It will return UUIDs of eligible services. Then you can link OVHcloud Connect with the vRack: - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Enter the vRack name as well as the UUID of OVHcloud Connect. - -### Step 2: Configuring the PoP - -This step is important because you have to choose between L2 and L3. - -> [!warning] -> Please be aware of the ramifications of this decision. To switch between L2 and L3 later, you will have to delete the whole configuration. -> - -#### Obtaining the interface ID - -Your service is attached to an interface with an ID. Use this call to obtain the ID: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -It will return the ID of the interface dedicated to your service. - -The following call provides more service details: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -The LightStatus parameter is refreshed every 5 minutes for monitoring purposes. - -#### Configuration with Layer 2 (L2) - -This is the simplest configuration. Use this call: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L2. - -#### Configuration with Layer 3 (L3) - -This configuration is more complex because of the required BGP settings: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L3. -- customerBgpArea: your BGP ASN, configured on your device which will be used for peering. -- ovhBgpArea: BGP ASN to be configured on the OVHcloud routing instance, pertaining to BGP session and AS path. -- subnet: a /30 IPv4 block. - -### Step 3: Data centre (DC) configuration - -> [!primary] -> If an OVHcloud Connect service is already configured in the vRack, the second service will inherit the data centre configuration. -> - -#### Obtaining available data centres - -You can list available data centres for configuration using the following calls: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration with Layer 2 (L2) - -Only the ID of the data centre is needed for the L2 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. - -#### Configuration with Layer 3 (L3) - -More parameters have to be provided for the L3 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. -- ovhBgpArea: as with the PoP, you need to assign an ASN for the OVHcloud routing instance. It will appear in AS path. (It can be different from the PoP ASN.) -- subnet: an IPv4 block, any size is accepted from /28. - -By default, the data centre will be configured with a VRRP instance. You have to proceed with the next steps for static routing or dynamic routing using BGP. - -#### Layer 3 option: static route - -A static route is needed when you have one or more subnets behind a gateway. This may be Linux gateway (with IP forwarding enabled), a NSX edge or any instance capable of routing. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- nextHop: IP address in the subnet range acting as gateway. -- subnet: a prefix using the CIDR notation. -- type: 'network' - -#### Layer 3 option: BGP session - -A BGP session enables dynamic routing from your routing instance with OVHcloud Connect. Announcements are dynamically managed using the BGP protocol. Enabling a BGP session disables the VRRP configuration. You cannot have a BGP session and a static route in the same DC configuration. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- bgpNeighborArea: your BGP ASN. -- bgpNeighborIp: your IP address in the subnet range. -- type: 'bgp' - -### Removing resources - -Each resource can be deleted individually, but deleting a parent resource like DC or PoP will automatically delete all sub-resources. However, recursive deletion is slower than a sequential deletion of each resource. - -#### Global deletion - -The following call recursively deletes the entire configuration of an OVHcloud Connect service: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -Each sub-resource's status will change from 'active' to 'toDelete' but it takes some time to see the status change. - -Only one task ID is created. - -#### Deleting by resource - -Each resource can be deleted individually using the following call that will delete the smallest resource (extra): - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -The following call removes the DC configuration and recursively deletes any additional sub-resources: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -When all sub-resources have been deleted, the PoP configuration can be safely removed: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -> [!primary] -> If a DC configuration is shared between two or more OVHcloud Connect services, deleting the PoP configuration of only one will not affect the DC ressource. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-us.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.en-us.md deleted file mode 100644 index a9207b2a78b..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.en-us.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Configuration of OVHcloud Connect using OVHcloud APIv6 -excerpt: 'Find out how to set up OVHcloud Connect using OVHcloud APIv6' -updated: 2020-09-14 ---- - -## Objective - -Configuring the OVHcloud Connect solution can be done via API. - -**Find out how to set up OVHcloud Connect using OVHcloud APIv6.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) - -## Instructions - -### Step 1: Configuring vRack - -As a mandatory first step, the service must be interconnected with a vRack to enable the configuration. - -Verify that the service is available with the following call: - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -It will return UUIDs of eligible services. Then you can link OVHcloud Connect with the vRack: - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Enter the vRack name as well as the UUID of OVHcloud Connect. - -### Step 2: Configuring the PoP - -This step is important because you have to choose between L2 and L3. - -> [!warning] -> Please be aware of the ramifications of this decision. To switch between L2 and L3 later, you will have to delete the whole configuration. -> - -#### Obtaining the interface ID - -Your service is attached to an interface with an ID. Use this call to obtain the ID: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -It will return the ID of the interface dedicated to your service. - -The following call provides more service details: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -The LightStatus parameter is refreshed every 5 minutes for monitoring purposes. - -#### Configuration with Layer 2 (L2) - -This is the simplest configuration. Use this call: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L2. - -#### Configuration with Layer 3 (L3) - -This configuration is more complex because of the required BGP settings: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L3. -- customerBgpArea: your BGP ASN, configured on your device which will be used for peering. -- ovhBgpArea: BGP ASN to be configured on the OVHcloud routing instance, pertaining to BGP session and AS path. -- subnet: a /30 IPv4 block. - -### Step 3: Data centre (DC) configuration - -> [!primary] -> If an OVHcloud Connect service is already configured in the vRack, the second service will inherit the data centre configuration. -> - -#### Obtaining available data centres - -You can list available data centres for configuration using the following calls: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration with Layer 2 (L2) - -Only the ID of the data centre is needed for the L2 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. - -#### Configuration with Layer 3 (L3) - -More parameters have to be provided for the L3 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. -- ovhBgpArea: as with the PoP, you need to assign an ASN for the OVHcloud routing instance. It will appear in AS path. (It can be different from the PoP ASN.) -- subnet: an IPv4 block, any size is accepted from /28. - -By default, the data centre will be configured with a VRRP instance. You have to proceed with the next steps for static routing or dynamic routing using BGP. - -#### Layer 3 option: static route - -A static route is needed when you have one or more subnets behind a gateway. This may be Linux gateway (with IP forwarding enabled), a NSX edge or any instance capable of routing. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- nextHop: IP address in the subnet range acting as gateway. -- subnet: a prefix using the CIDR notation. -- type: 'network' - -#### Layer 3 option: BGP session - -A BGP session enables dynamic routing from your routing instance with OVHcloud Connect. Announcements are dynamically managed using the BGP protocol. Enabling a BGP session disables the VRRP configuration. You cannot have a BGP session and a static route in the same DC configuration. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- bgpNeighborArea: your BGP ASN. -- bgpNeighborIp: your IP address in the subnet range. -- type: 'bgp' - -### Removing resources - -Each resource can be deleted individually, but deleting a parent resource like DC or PoP will automatically delete all sub-resources. However, recursive deletion is slower than a sequential deletion of each resource. - -#### Global deletion - -The following call recursively deletes the entire configuration of an OVHcloud Connect service: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -Each sub-resource's status will change from 'active' to 'toDelete' but it takes some time to see the status change. - -Only one task ID is created. - -#### Deleting by resource - -Each resource can be deleted individually using the following call that will delete the smallest resource (extra): - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -The following call removes the DC configuration and recursively deletes any additional sub-resources: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -When all sub-resources have been deleted, the PoP configuration can be safely removed: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -> [!primary] -> If a DC configuration is shared between two or more OVHcloud Connect services, deleting the PoP configuration of only one will not affect the DC ressource. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.es-es.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.es-es.md deleted file mode 100644 index a9207b2a78b..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.es-es.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Configuration of OVHcloud Connect using OVHcloud APIv6 -excerpt: 'Find out how to set up OVHcloud Connect using OVHcloud APIv6' -updated: 2020-09-14 ---- - -## Objective - -Configuring the OVHcloud Connect solution can be done via API. - -**Find out how to set up OVHcloud Connect using OVHcloud APIv6.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) - -## Instructions - -### Step 1: Configuring vRack - -As a mandatory first step, the service must be interconnected with a vRack to enable the configuration. - -Verify that the service is available with the following call: - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -It will return UUIDs of eligible services. Then you can link OVHcloud Connect with the vRack: - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Enter the vRack name as well as the UUID of OVHcloud Connect. - -### Step 2: Configuring the PoP - -This step is important because you have to choose between L2 and L3. - -> [!warning] -> Please be aware of the ramifications of this decision. To switch between L2 and L3 later, you will have to delete the whole configuration. -> - -#### Obtaining the interface ID - -Your service is attached to an interface with an ID. Use this call to obtain the ID: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -It will return the ID of the interface dedicated to your service. - -The following call provides more service details: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -The LightStatus parameter is refreshed every 5 minutes for monitoring purposes. - -#### Configuration with Layer 2 (L2) - -This is the simplest configuration. Use this call: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L2. - -#### Configuration with Layer 3 (L3) - -This configuration is more complex because of the required BGP settings: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L3. -- customerBgpArea: your BGP ASN, configured on your device which will be used for peering. -- ovhBgpArea: BGP ASN to be configured on the OVHcloud routing instance, pertaining to BGP session and AS path. -- subnet: a /30 IPv4 block. - -### Step 3: Data centre (DC) configuration - -> [!primary] -> If an OVHcloud Connect service is already configured in the vRack, the second service will inherit the data centre configuration. -> - -#### Obtaining available data centres - -You can list available data centres for configuration using the following calls: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration with Layer 2 (L2) - -Only the ID of the data centre is needed for the L2 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. - -#### Configuration with Layer 3 (L3) - -More parameters have to be provided for the L3 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. -- ovhBgpArea: as with the PoP, you need to assign an ASN for the OVHcloud routing instance. It will appear in AS path. (It can be different from the PoP ASN.) -- subnet: an IPv4 block, any size is accepted from /28. - -By default, the data centre will be configured with a VRRP instance. You have to proceed with the next steps for static routing or dynamic routing using BGP. - -#### Layer 3 option: static route - -A static route is needed when you have one or more subnets behind a gateway. This may be Linux gateway (with IP forwarding enabled), a NSX edge or any instance capable of routing. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- nextHop: IP address in the subnet range acting as gateway. -- subnet: a prefix using the CIDR notation. -- type: 'network' - -#### Layer 3 option: BGP session - -A BGP session enables dynamic routing from your routing instance with OVHcloud Connect. Announcements are dynamically managed using the BGP protocol. Enabling a BGP session disables the VRRP configuration. You cannot have a BGP session and a static route in the same DC configuration. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- bgpNeighborArea: your BGP ASN. -- bgpNeighborIp: your IP address in the subnet range. -- type: 'bgp' - -### Removing resources - -Each resource can be deleted individually, but deleting a parent resource like DC or PoP will automatically delete all sub-resources. However, recursive deletion is slower than a sequential deletion of each resource. - -#### Global deletion - -The following call recursively deletes the entire configuration of an OVHcloud Connect service: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -Each sub-resource's status will change from 'active' to 'toDelete' but it takes some time to see the status change. - -Only one task ID is created. - -#### Deleting by resource - -Each resource can be deleted individually using the following call that will delete the smallest resource (extra): - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -The following call removes the DC configuration and recursively deletes any additional sub-resources: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -When all sub-resources have been deleted, the PoP configuration can be safely removed: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -> [!primary] -> If a DC configuration is shared between two or more OVHcloud Connect services, deleting the PoP configuration of only one will not affect the DC ressource. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.es-us.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.es-us.md deleted file mode 100644 index a9207b2a78b..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.es-us.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Configuration of OVHcloud Connect using OVHcloud APIv6 -excerpt: 'Find out how to set up OVHcloud Connect using OVHcloud APIv6' -updated: 2020-09-14 ---- - -## Objective - -Configuring the OVHcloud Connect solution can be done via API. - -**Find out how to set up OVHcloud Connect using OVHcloud APIv6.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) - -## Instructions - -### Step 1: Configuring vRack - -As a mandatory first step, the service must be interconnected with a vRack to enable the configuration. - -Verify that the service is available with the following call: - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -It will return UUIDs of eligible services. Then you can link OVHcloud Connect with the vRack: - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Enter the vRack name as well as the UUID of OVHcloud Connect. - -### Step 2: Configuring the PoP - -This step is important because you have to choose between L2 and L3. - -> [!warning] -> Please be aware of the ramifications of this decision. To switch between L2 and L3 later, you will have to delete the whole configuration. -> - -#### Obtaining the interface ID - -Your service is attached to an interface with an ID. Use this call to obtain the ID: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -It will return the ID of the interface dedicated to your service. - -The following call provides more service details: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -The LightStatus parameter is refreshed every 5 minutes for monitoring purposes. - -#### Configuration with Layer 2 (L2) - -This is the simplest configuration. Use this call: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L2. - -#### Configuration with Layer 3 (L3) - -This configuration is more complex because of the required BGP settings: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L3. -- customerBgpArea: your BGP ASN, configured on your device which will be used for peering. -- ovhBgpArea: BGP ASN to be configured on the OVHcloud routing instance, pertaining to BGP session and AS path. -- subnet: a /30 IPv4 block. - -### Step 3: Data centre (DC) configuration - -> [!primary] -> If an OVHcloud Connect service is already configured in the vRack, the second service will inherit the data centre configuration. -> - -#### Obtaining available data centres - -You can list available data centres for configuration using the following calls: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration with Layer 2 (L2) - -Only the ID of the data centre is needed for the L2 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. - -#### Configuration with Layer 3 (L3) - -More parameters have to be provided for the L3 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. -- ovhBgpArea: as with the PoP, you need to assign an ASN for the OVHcloud routing instance. It will appear in AS path. (It can be different from the PoP ASN.) -- subnet: an IPv4 block, any size is accepted from /28. - -By default, the data centre will be configured with a VRRP instance. You have to proceed with the next steps for static routing or dynamic routing using BGP. - -#### Layer 3 option: static route - -A static route is needed when you have one or more subnets behind a gateway. This may be Linux gateway (with IP forwarding enabled), a NSX edge or any instance capable of routing. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- nextHop: IP address in the subnet range acting as gateway. -- subnet: a prefix using the CIDR notation. -- type: 'network' - -#### Layer 3 option: BGP session - -A BGP session enables dynamic routing from your routing instance with OVHcloud Connect. Announcements are dynamically managed using the BGP protocol. Enabling a BGP session disables the VRRP configuration. You cannot have a BGP session and a static route in the same DC configuration. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- bgpNeighborArea: your BGP ASN. -- bgpNeighborIp: your IP address in the subnet range. -- type: 'bgp' - -### Removing resources - -Each resource can be deleted individually, but deleting a parent resource like DC or PoP will automatically delete all sub-resources. However, recursive deletion is slower than a sequential deletion of each resource. - -#### Global deletion - -The following call recursively deletes the entire configuration of an OVHcloud Connect service: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -Each sub-resource's status will change from 'active' to 'toDelete' but it takes some time to see the status change. - -Only one task ID is created. - -#### Deleting by resource - -Each resource can be deleted individually using the following call that will delete the smallest resource (extra): - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -The following call removes the DC configuration and recursively deletes any additional sub-resources: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -When all sub-resources have been deleted, the PoP configuration can be safely removed: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -> [!primary] -> If a DC configuration is shared between two or more OVHcloud Connect services, deleting the PoP configuration of only one will not affect the DC ressource. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-ca.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-ca.md deleted file mode 100644 index e53222d8c0a..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-ca.md +++ /dev/null @@ -1,232 +0,0 @@ ---- -title: Configuration de OVHcloud Connect depuis les APIv6 OVHcloud -excerpt: Découvrez comment déployer OVHcloud Connect via les API OVHcloud -updated: 2020-09-14 ---- - -## Objectif - -La mise en place de l'offre OVHcloud Connect peut se faire directement depuis les API OVhcloud. - -**Découvrez comment configurer le service OVHcloud Connect via les API OVHcloud**. - -## Prérequis - -> [!warning] -> Pour assurer un fonctionnement correct de ce service, vous devez prendre connaissance des [capacités et limites techniques de l'offre OVHcloud Connect](/pages/network/ovhcloud_connect/occ-limits) et configurer vos équipements réseau en accord avec celles-ci. -> - -* Posséder une offre [OVHcloud Connect](/links/network/ovhcloud-connect) dans votre compte OVHcloud. -* Être connecté aux [API OVHcloud](/links/api). -* Avoir [créé vos credentials pour l'utilisation des API OVHcloud](/pages/manage_and_operate/api/first-steps). - -## En pratique - -### Étape 1 : Association du vRack - -Cette première étape est obligatoire, le service OVHcloud Connect devant être associé à un vRack pour activer la configuration. - -L'appel suivant vérifie que votre vRack peut être associé à un service OVHcloud Connect : - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -Il retournera l'uuid des services OVHcloud Connect admissibles. - -Vous pouvez ensuite associer le service OVHcloud Connect à un vRack admissible via l'appel suivant : - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Renseignez le nom de votre vRack ainsi que l'uuid de votre service OVHcloud Connect. - -### Étape 2 : Configurer le POP - -C'est une étape importante car vous devez choisir entre L2 et L3. - -> [!warning] -> Pour basculer entre L2 et L3, il serait nécessaire de supprimer toute la configuration. Bien définir le choix de votre modèle est donc important à cette étape. -> - -#### Obtenir l'ID de l'interface - -Votre service est connecté à une interface avec un ID. Utilisez l'appel suivant pour obtenir cet ID : - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -Une fois l'ID obtenu, vous pouvez utiliser l'appel suivant pour obtenir plus de détails : - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -Le paramètre LightStatus est actualisé toutes les 5 minutes à des fins de surveillance du port. - -#### Configuration en Layer 2 (L2) - -Il s'agit de la configuration la plus simple. Utilisez l'appel suivant : - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -Renseignez uniquement les informations suivantes : - -* ID interface : renseignez l'ID obtenu précédemment. -* Type : sélectionnez `l2`. - -#### Configuration en Layer 3 (L3) - -Cette configuration est plus complexe en raison des paramètres BGP à renseigner : - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -Renseignez les informations suivantes : - -* ID interface : renseignez l'ID obtenu précédemment. -* Type : sélectionnez `l3`. -* customerBgpArea : votre ASN BGP, celui configuré sur votre routeur. -* ovhBgpArea : l'ASN BGP à configurer sur l'instance de routage OVHcloud. Un tel ASN apparaîtra dans la session BGP et en tant que chemin. -* sous-réseau : un bloc IPv4 /30 - -### Étape 3 : Configuration du Datacentre (DC) - -> [!primary] -> Si un premier service OVHcloud Connect est déjà configuré dans le même vRack, la configuration existante du Datacentre sera appliquée au deuxième service OVHcloud Connect. -> - -#### Obtenir le Datacentre disponible - -Vous pouvez répertorier les Datacentres disponibles pour la configuration à l'aide de l'appel suivant : - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -L'appel suivant vous retourne le nom du Datacentre : - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration en Layer 2 (L2) - -La configuration en L2 reste la plus simple car seul l'ID du centre de données est nécessaire : - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -* datacenterId : Renseignez l'ID du Datacentre - -#### Configuration en Layer 3 (L3) - -La configuration en L3 nécessite là aussi d'autres informations à renseigner : - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -* datacenterId : Renseignez l'ID du Datacentre -* ovhBgpArea : comme pour la configuration POP, vous devez affecter un ASN pour l'instance de routage OVHcloud. Il apparaîtra dans as-path. Il peut être différent de l'ASN POP. -* sous-réseau : un bloc IPv4. Toute taille est acceptée à partir de /28. - -Par défaut, le Datacentre est configuré avec une instance VRRP. Vous devez passer aux étapes suivantes pour le routage statique ou dynamique à l'aide de BGP. - -##### **Option L3 : route statique** - -Une route statique est nécessaire lorsque vous avez un ou plusieurs sous-réseaux derrière une passerelle. Une telle passerelle peut être un Linux (avec IP forward activé), un NSX edge ou toute instance de routage compatible. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -* nextHop : Adresse IP agissant comme passerelle dans la plage de sous-réseau -* sous-réseau : un préfixe utilisant la notation CIDR. -* type : `network` - -##### **Option L3 : Session BGP** - -Une session BGP active le routage dynamique à partir de votre instance de routage avec OVHcloud Connect. Les annonces sont gérées de manière dynamique à l'aide du protocole BGP. L'activation d'une session BGP désactive la configuration VRRP. - -> [!primary] -> Vous ne pouvez pas combiner une session BGP et un itinéraire statique dans la même configuration de Datacentre. -> - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -* bgpNeighborArea : votre ASN BGP -* bgpNeighborIp : votre adresse IP dans la plage de sous-réseau -* type : `bgp` - -### Suppression des ressources - -Chaque ressource peut être supprimée individuellement, mais la suppression d'une ressource parente telle que DC ou POP supprimera automatiquement toutes les sous-ressources. - -La suppression récursive est plus lente que la suppression séquentielle de chaque ressource. - -#### Suppression globale - -L'appel suivant supprime récursivement toute la configuration d'un service OVHcloud Connect. - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -L'état de chaque sous-ressource passe de `active` à `toDelete`. Le changement d'état peut nécessiter un certain temps. - -Un seul identifiant de tâche est créé. - -#### Supprimer par ressource - -Chaque ressource peut être supprimée individuellement à l'aide de l'appel suivant qui va supprimer la plus petite ressource (extra) : - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -L'appel suivant supprime la configuration DC ainsi que toute sous-ressource supplémentaire éventuelle. Celles-ci seront alors supprimées de manière récursive : - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -Lorsque toutes les sous-ressources ont été supprimées, la configuration POP peut être supprimée en toute sécurité. - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -#### Adhérences - -Si une configuration DC est partagée entre au moins deux services OVHcloud Connect, la suppression de la configuration POP d'un seul service OVHcloud Connect n'affectera pas la ressource DC. - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-fr.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-fr.md deleted file mode 100644 index e53222d8c0a..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.fr-fr.md +++ /dev/null @@ -1,232 +0,0 @@ ---- -title: Configuration de OVHcloud Connect depuis les APIv6 OVHcloud -excerpt: Découvrez comment déployer OVHcloud Connect via les API OVHcloud -updated: 2020-09-14 ---- - -## Objectif - -La mise en place de l'offre OVHcloud Connect peut se faire directement depuis les API OVhcloud. - -**Découvrez comment configurer le service OVHcloud Connect via les API OVHcloud**. - -## Prérequis - -> [!warning] -> Pour assurer un fonctionnement correct de ce service, vous devez prendre connaissance des [capacités et limites techniques de l'offre OVHcloud Connect](/pages/network/ovhcloud_connect/occ-limits) et configurer vos équipements réseau en accord avec celles-ci. -> - -* Posséder une offre [OVHcloud Connect](/links/network/ovhcloud-connect) dans votre compte OVHcloud. -* Être connecté aux [API OVHcloud](/links/api). -* Avoir [créé vos credentials pour l'utilisation des API OVHcloud](/pages/manage_and_operate/api/first-steps). - -## En pratique - -### Étape 1 : Association du vRack - -Cette première étape est obligatoire, le service OVHcloud Connect devant être associé à un vRack pour activer la configuration. - -L'appel suivant vérifie que votre vRack peut être associé à un service OVHcloud Connect : - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -Il retournera l'uuid des services OVHcloud Connect admissibles. - -Vous pouvez ensuite associer le service OVHcloud Connect à un vRack admissible via l'appel suivant : - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Renseignez le nom de votre vRack ainsi que l'uuid de votre service OVHcloud Connect. - -### Étape 2 : Configurer le POP - -C'est une étape importante car vous devez choisir entre L2 et L3. - -> [!warning] -> Pour basculer entre L2 et L3, il serait nécessaire de supprimer toute la configuration. Bien définir le choix de votre modèle est donc important à cette étape. -> - -#### Obtenir l'ID de l'interface - -Votre service est connecté à une interface avec un ID. Utilisez l'appel suivant pour obtenir cet ID : - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -Une fois l'ID obtenu, vous pouvez utiliser l'appel suivant pour obtenir plus de détails : - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -Le paramètre LightStatus est actualisé toutes les 5 minutes à des fins de surveillance du port. - -#### Configuration en Layer 2 (L2) - -Il s'agit de la configuration la plus simple. Utilisez l'appel suivant : - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -Renseignez uniquement les informations suivantes : - -* ID interface : renseignez l'ID obtenu précédemment. -* Type : sélectionnez `l2`. - -#### Configuration en Layer 3 (L3) - -Cette configuration est plus complexe en raison des paramètres BGP à renseigner : - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -Renseignez les informations suivantes : - -* ID interface : renseignez l'ID obtenu précédemment. -* Type : sélectionnez `l3`. -* customerBgpArea : votre ASN BGP, celui configuré sur votre routeur. -* ovhBgpArea : l'ASN BGP à configurer sur l'instance de routage OVHcloud. Un tel ASN apparaîtra dans la session BGP et en tant que chemin. -* sous-réseau : un bloc IPv4 /30 - -### Étape 3 : Configuration du Datacentre (DC) - -> [!primary] -> Si un premier service OVHcloud Connect est déjà configuré dans le même vRack, la configuration existante du Datacentre sera appliquée au deuxième service OVHcloud Connect. -> - -#### Obtenir le Datacentre disponible - -Vous pouvez répertorier les Datacentres disponibles pour la configuration à l'aide de l'appel suivant : - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -L'appel suivant vous retourne le nom du Datacentre : - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration en Layer 2 (L2) - -La configuration en L2 reste la plus simple car seul l'ID du centre de données est nécessaire : - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -* datacenterId : Renseignez l'ID du Datacentre - -#### Configuration en Layer 3 (L3) - -La configuration en L3 nécessite là aussi d'autres informations à renseigner : - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -* datacenterId : Renseignez l'ID du Datacentre -* ovhBgpArea : comme pour la configuration POP, vous devez affecter un ASN pour l'instance de routage OVHcloud. Il apparaîtra dans as-path. Il peut être différent de l'ASN POP. -* sous-réseau : un bloc IPv4. Toute taille est acceptée à partir de /28. - -Par défaut, le Datacentre est configuré avec une instance VRRP. Vous devez passer aux étapes suivantes pour le routage statique ou dynamique à l'aide de BGP. - -##### **Option L3 : route statique** - -Une route statique est nécessaire lorsque vous avez un ou plusieurs sous-réseaux derrière une passerelle. Une telle passerelle peut être un Linux (avec IP forward activé), un NSX edge ou toute instance de routage compatible. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -* nextHop : Adresse IP agissant comme passerelle dans la plage de sous-réseau -* sous-réseau : un préfixe utilisant la notation CIDR. -* type : `network` - -##### **Option L3 : Session BGP** - -Une session BGP active le routage dynamique à partir de votre instance de routage avec OVHcloud Connect. Les annonces sont gérées de manière dynamique à l'aide du protocole BGP. L'activation d'une session BGP désactive la configuration VRRP. - -> [!primary] -> Vous ne pouvez pas combiner une session BGP et un itinéraire statique dans la même configuration de Datacentre. -> - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -* bgpNeighborArea : votre ASN BGP -* bgpNeighborIp : votre adresse IP dans la plage de sous-réseau -* type : `bgp` - -### Suppression des ressources - -Chaque ressource peut être supprimée individuellement, mais la suppression d'une ressource parente telle que DC ou POP supprimera automatiquement toutes les sous-ressources. - -La suppression récursive est plus lente que la suppression séquentielle de chaque ressource. - -#### Suppression globale - -L'appel suivant supprime récursivement toute la configuration d'un service OVHcloud Connect. - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -L'état de chaque sous-ressource passe de `active` à `toDelete`. Le changement d'état peut nécessiter un certain temps. - -Un seul identifiant de tâche est créé. - -#### Supprimer par ressource - -Chaque ressource peut être supprimée individuellement à l'aide de l'appel suivant qui va supprimer la plus petite ressource (extra) : - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -L'appel suivant supprime la configuration DC ainsi que toute sous-ressource supplémentaire éventuelle. Celles-ci seront alors supprimées de manière récursive : - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -Lorsque toutes les sous-ressources ont été supprimées, la configuration POP peut être supprimée en toute sécurité. - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -#### Adhérences - -Si une configuration DC est partagée entre au moins deux services OVHcloud Connect, la suppression de la configuration POP d'un seul service OVHcloud Connect n'affectera pas la ressource DC. - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.it-it.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.it-it.md deleted file mode 100644 index a9207b2a78b..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.it-it.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Configuration of OVHcloud Connect using OVHcloud APIv6 -excerpt: 'Find out how to set up OVHcloud Connect using OVHcloud APIv6' -updated: 2020-09-14 ---- - -## Objective - -Configuring the OVHcloud Connect solution can be done via API. - -**Find out how to set up OVHcloud Connect using OVHcloud APIv6.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) - -## Instructions - -### Step 1: Configuring vRack - -As a mandatory first step, the service must be interconnected with a vRack to enable the configuration. - -Verify that the service is available with the following call: - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -It will return UUIDs of eligible services. Then you can link OVHcloud Connect with the vRack: - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Enter the vRack name as well as the UUID of OVHcloud Connect. - -### Step 2: Configuring the PoP - -This step is important because you have to choose between L2 and L3. - -> [!warning] -> Please be aware of the ramifications of this decision. To switch between L2 and L3 later, you will have to delete the whole configuration. -> - -#### Obtaining the interface ID - -Your service is attached to an interface with an ID. Use this call to obtain the ID: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -It will return the ID of the interface dedicated to your service. - -The following call provides more service details: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -The LightStatus parameter is refreshed every 5 minutes for monitoring purposes. - -#### Configuration with Layer 2 (L2) - -This is the simplest configuration. Use this call: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L2. - -#### Configuration with Layer 3 (L3) - -This configuration is more complex because of the required BGP settings: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L3. -- customerBgpArea: your BGP ASN, configured on your device which will be used for peering. -- ovhBgpArea: BGP ASN to be configured on the OVHcloud routing instance, pertaining to BGP session and AS path. -- subnet: a /30 IPv4 block. - -### Step 3: Data centre (DC) configuration - -> [!primary] -> If an OVHcloud Connect service is already configured in the vRack, the second service will inherit the data centre configuration. -> - -#### Obtaining available data centres - -You can list available data centres for configuration using the following calls: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration with Layer 2 (L2) - -Only the ID of the data centre is needed for the L2 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. - -#### Configuration with Layer 3 (L3) - -More parameters have to be provided for the L3 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. -- ovhBgpArea: as with the PoP, you need to assign an ASN for the OVHcloud routing instance. It will appear in AS path. (It can be different from the PoP ASN.) -- subnet: an IPv4 block, any size is accepted from /28. - -By default, the data centre will be configured with a VRRP instance. You have to proceed with the next steps for static routing or dynamic routing using BGP. - -#### Layer 3 option: static route - -A static route is needed when you have one or more subnets behind a gateway. This may be Linux gateway (with IP forwarding enabled), a NSX edge or any instance capable of routing. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- nextHop: IP address in the subnet range acting as gateway. -- subnet: a prefix using the CIDR notation. -- type: 'network' - -#### Layer 3 option: BGP session - -A BGP session enables dynamic routing from your routing instance with OVHcloud Connect. Announcements are dynamically managed using the BGP protocol. Enabling a BGP session disables the VRRP configuration. You cannot have a BGP session and a static route in the same DC configuration. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- bgpNeighborArea: your BGP ASN. -- bgpNeighborIp: your IP address in the subnet range. -- type: 'bgp' - -### Removing resources - -Each resource can be deleted individually, but deleting a parent resource like DC or PoP will automatically delete all sub-resources. However, recursive deletion is slower than a sequential deletion of each resource. - -#### Global deletion - -The following call recursively deletes the entire configuration of an OVHcloud Connect service: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -Each sub-resource's status will change from 'active' to 'toDelete' but it takes some time to see the status change. - -Only one task ID is created. - -#### Deleting by resource - -Each resource can be deleted individually using the following call that will delete the smallest resource (extra): - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -The following call removes the DC configuration and recursively deletes any additional sub-resources: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -When all sub-resources have been deleted, the PoP configuration can be safely removed: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -> [!primary] -> If a DC configuration is shared between two or more OVHcloud Connect services, deleting the PoP configuration of only one will not affect the DC ressource. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.pl-pl.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.pl-pl.md deleted file mode 100644 index a9207b2a78b..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.pl-pl.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Configuration of OVHcloud Connect using OVHcloud APIv6 -excerpt: 'Find out how to set up OVHcloud Connect using OVHcloud APIv6' -updated: 2020-09-14 ---- - -## Objective - -Configuring the OVHcloud Connect solution can be done via API. - -**Find out how to set up OVHcloud Connect using OVHcloud APIv6.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) - -## Instructions - -### Step 1: Configuring vRack - -As a mandatory first step, the service must be interconnected with a vRack to enable the configuration. - -Verify that the service is available with the following call: - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -It will return UUIDs of eligible services. Then you can link OVHcloud Connect with the vRack: - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Enter the vRack name as well as the UUID of OVHcloud Connect. - -### Step 2: Configuring the PoP - -This step is important because you have to choose between L2 and L3. - -> [!warning] -> Please be aware of the ramifications of this decision. To switch between L2 and L3 later, you will have to delete the whole configuration. -> - -#### Obtaining the interface ID - -Your service is attached to an interface with an ID. Use this call to obtain the ID: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -It will return the ID of the interface dedicated to your service. - -The following call provides more service details: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -The LightStatus parameter is refreshed every 5 minutes for monitoring purposes. - -#### Configuration with Layer 2 (L2) - -This is the simplest configuration. Use this call: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L2. - -#### Configuration with Layer 3 (L3) - -This configuration is more complex because of the required BGP settings: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L3. -- customerBgpArea: your BGP ASN, configured on your device which will be used for peering. -- ovhBgpArea: BGP ASN to be configured on the OVHcloud routing instance, pertaining to BGP session and AS path. -- subnet: a /30 IPv4 block. - -### Step 3: Data centre (DC) configuration - -> [!primary] -> If an OVHcloud Connect service is already configured in the vRack, the second service will inherit the data centre configuration. -> - -#### Obtaining available data centres - -You can list available data centres for configuration using the following calls: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration with Layer 2 (L2) - -Only the ID of the data centre is needed for the L2 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. - -#### Configuration with Layer 3 (L3) - -More parameters have to be provided for the L3 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. -- ovhBgpArea: as with the PoP, you need to assign an ASN for the OVHcloud routing instance. It will appear in AS path. (It can be different from the PoP ASN.) -- subnet: an IPv4 block, any size is accepted from /28. - -By default, the data centre will be configured with a VRRP instance. You have to proceed with the next steps for static routing or dynamic routing using BGP. - -#### Layer 3 option: static route - -A static route is needed when you have one or more subnets behind a gateway. This may be Linux gateway (with IP forwarding enabled), a NSX edge or any instance capable of routing. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- nextHop: IP address in the subnet range acting as gateway. -- subnet: a prefix using the CIDR notation. -- type: 'network' - -#### Layer 3 option: BGP session - -A BGP session enables dynamic routing from your routing instance with OVHcloud Connect. Announcements are dynamically managed using the BGP protocol. Enabling a BGP session disables the VRRP configuration. You cannot have a BGP session and a static route in the same DC configuration. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- bgpNeighborArea: your BGP ASN. -- bgpNeighborIp: your IP address in the subnet range. -- type: 'bgp' - -### Removing resources - -Each resource can be deleted individually, but deleting a parent resource like DC or PoP will automatically delete all sub-resources. However, recursive deletion is slower than a sequential deletion of each resource. - -#### Global deletion - -The following call recursively deletes the entire configuration of an OVHcloud Connect service: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -Each sub-resource's status will change from 'active' to 'toDelete' but it takes some time to see the status change. - -Only one task ID is created. - -#### Deleting by resource - -Each resource can be deleted individually using the following call that will delete the smallest resource (extra): - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -The following call removes the DC configuration and recursively deletes any additional sub-resources: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -When all sub-resources have been deleted, the PoP configuration can be safely removed: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -> [!primary] -> If a DC configuration is shared between two or more OVHcloud Connect services, deleting the PoP configuration of only one will not affect the DC ressource. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-howto-api/guide.pt-pt.md b/pages/network/ovhcloud_connect/occ-howto-api/guide.pt-pt.md deleted file mode 100644 index a9207b2a78b..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/guide.pt-pt.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -title: Configuration of OVHcloud Connect using OVHcloud APIv6 -excerpt: 'Find out how to set up OVHcloud Connect using OVHcloud APIv6' -updated: 2020-09-14 ---- - -## Objective - -Configuring the OVHcloud Connect solution can be done via API. - -**Find out how to set up OVHcloud Connect using OVHcloud APIv6.** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- an [OVHcloud Connect service](/links/network/ovhcloud-connect) -- access to the [OVHcloud APIv6](/links/api) (create your credentials by consulting [this guide](/pages/manage_and_operate/api/first-steps)) - -## Instructions - -### Step 1: Configuring vRack - -As a mandatory first step, the service must be interconnected with a vRack to enable the configuration. - -Verify that the service is available with the following call: - -> [!api] -> -> @api {v1} /vrack GET /vrack/{serviceName}/ovhCloudConnect -> - -It will return UUIDs of eligible services. Then you can link OVHcloud Connect with the vRack: - -> [!api] -> -> @api {v1} /vrack POST /vrack/{serviceName}/ovhCloudConnect -> - -Enter the vRack name as well as the UUID of OVHcloud Connect. - -### Step 2: Configuring the PoP - -This step is important because you have to choose between L2 and L3. - -> [!warning] -> Please be aware of the ramifications of this decision. To switch between L2 and L3 later, you will have to delete the whole configuration. -> - -#### Obtaining the interface ID - -Your service is attached to an interface with an ID. Use this call to obtain the ID: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface -> - -It will return the ID of the interface dedicated to your service. - -The following call provides more service details: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/interface/{id} -> - -The LightStatus parameter is refreshed every 5 minutes for monitoring purposes. - -#### Configuration with Layer 2 (L2) - -This is the simplest configuration. Use this call: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L2. - -#### Configuration with Layer 3 (L3) - -This configuration is more complex because of the required BGP settings: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop -> - -- interface ID: enter the ID previously obtained. -- type: select L3. -- customerBgpArea: your BGP ASN, configured on your device which will be used for peering. -- ovhBgpArea: BGP ASN to be configured on the OVHcloud routing instance, pertaining to BGP session and AS path. -- subnet: a /30 IPv4 block. - -### Step 3: Data centre (DC) configuration - -> [!primary] -> If an OVHcloud Connect service is already configured in the vRack, the second service will inherit the data centre configuration. -> - -#### Obtaining available data centres - -You can list available data centres for configuration using the following calls: - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter -> - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/datacenter/{id} -> - -#### Configuration with Layer 2 (L2) - -Only the ID of the data centre is needed for the L2 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. - -#### Configuration with Layer 3 (L3) - -More parameters have to be provided for the L3 configuration: - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter -> - -- datacenterId: enter the DC ID previously obtained. -- ovhBgpArea: as with the PoP, you need to assign an ASN for the OVHcloud routing instance. It will appear in AS path. (It can be different from the PoP ASN.) -- subnet: an IPv4 block, any size is accepted from /28. - -By default, the data centre will be configured with a VRRP instance. You have to proceed with the next steps for static routing or dynamic routing using BGP. - -#### Layer 3 option: static route - -A static route is needed when you have one or more subnets behind a gateway. This may be Linux gateway (with IP forwarding enabled), a NSX edge or any instance capable of routing. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- nextHop: IP address in the subnet range acting as gateway. -- subnet: a prefix using the CIDR notation. -- type: 'network' - -#### Layer 3 option: BGP session - -A BGP session enables dynamic routing from your routing instance with OVHcloud Connect. Announcements are dynamically managed using the BGP protocol. Enabling a BGP session disables the VRRP configuration. You cannot have a BGP session and a static route in the same DC configuration. - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra -> - -- bgpNeighborArea: your BGP ASN. -- bgpNeighborIp: your IP address in the subnet range. -- type: 'bgp' - -### Removing resources - -Each resource can be deleted individually, but deleting a parent resource like DC or PoP will automatically delete all sub-resources. However, recursive deletion is slower than a sequential deletion of each resource. - -#### Global deletion - -The following call recursively deletes the entire configuration of an OVHcloud Connect service: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -Each sub-resource's status will change from 'active' to 'toDelete' but it takes some time to see the status change. - -Only one task ID is created. - -#### Deleting by resource - -Each resource can be deleted individually using the following call that will delete the smallest resource (extra): - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId}/extra/{extraId} -> - -The following call removes the DC configuration and recursively deletes any additional sub-resources: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId}/datacenter/{datacenterId} -> - -When all sub-resources have been deleted, the PoP configuration can be safely removed: - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/config/pop/{popId} -> - -> [!primary] -> If a DC configuration is shared between two or more OVHcloud Connect services, deleting the PoP configuration of only one will not affect the DC ressource. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-howto-api/meta.yaml b/pages/network/ovhcloud_connect/occ-howto-api/meta.yaml deleted file mode 100755 index 49489e4561f..00000000000 --- a/pages/network/ovhcloud_connect/occ-howto-api/meta.yaml +++ /dev/null @@ -1,2 +0,0 @@ -id: 57ad6fdf-2ddc-4441-bf78-d8ab93379530 -full_slug: network-ovhcloud-connect-api \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.de-de.md b/pages/network/ovhcloud_connect/occ-layer2/guide.de-de.md deleted file mode 100644 index e689d317313..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.de-de.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Layer 2 mode -excerpt: 'Details about using Layer 2 (L2) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 2 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 2 implementation - -![L2 Implementation](images/occ-l2-implementation.png){.thumbnail} - -The L2 tunnel is forwarded directly to/from the vRack, so all L2 traffic is forwarded to/from the customer inter-connection. - -L2 traffic refers to Ethernet frames, with an 802.1q header, if applicable: - -- Ethernet broadcast is forwarded. -- Unknown Ethernet unicast is forwarded. -- Multicast is forwarded (considered broadcast, limited to 20pps). -- Specific point-to-point Ethernet frames (like LLDP or LACP) are not forwarded - -Only one OVHcloud Connect L2 is supported per vRack: each PoP/EntryPoint can only be associated with one DC/EndPoint. - -![Supported and unsupported L2 Design](images/occ-l2-supported-unsupported.png){.thumbnail} - -With L2 mode, redundancy cannot be exploited between two PoP/EntryPoint. The only solution is to use a LAG on a PoP/EntryPoint. - -### Connection mode details - -L2 operates at the Ethernet level. The customer's vRack is extended "as-is" from OVHcloud and forwarded to the customer link. Transparent to VLANs, this mode is the best way to inter-connect the customer's legacy network with an OVHcloud vRack. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -The L2 mode is limited to a point-to-point topology: a backup link through a second PoP is not supported. - -![L2 Topologies](images/occ-l2-topologies.png){.thumbnail} - -LACP is mandatory for aggregation when 2 links are configured with PoP. - -Jumbo frames up to 9000 bytes are supported. - -Connections between a PoP and a DC benefit from the OVHcloud backbone. An internal link failure is therefore supported and will not impact customer traffic. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.en-asia.md b/pages/network/ovhcloud_connect/occ-layer2/guide.en-asia.md deleted file mode 100644 index e689d317313..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.en-asia.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Layer 2 mode -excerpt: 'Details about using Layer 2 (L2) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 2 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 2 implementation - -![L2 Implementation](images/occ-l2-implementation.png){.thumbnail} - -The L2 tunnel is forwarded directly to/from the vRack, so all L2 traffic is forwarded to/from the customer inter-connection. - -L2 traffic refers to Ethernet frames, with an 802.1q header, if applicable: - -- Ethernet broadcast is forwarded. -- Unknown Ethernet unicast is forwarded. -- Multicast is forwarded (considered broadcast, limited to 20pps). -- Specific point-to-point Ethernet frames (like LLDP or LACP) are not forwarded - -Only one OVHcloud Connect L2 is supported per vRack: each PoP/EntryPoint can only be associated with one DC/EndPoint. - -![Supported and unsupported L2 Design](images/occ-l2-supported-unsupported.png){.thumbnail} - -With L2 mode, redundancy cannot be exploited between two PoP/EntryPoint. The only solution is to use a LAG on a PoP/EntryPoint. - -### Connection mode details - -L2 operates at the Ethernet level. The customer's vRack is extended "as-is" from OVHcloud and forwarded to the customer link. Transparent to VLANs, this mode is the best way to inter-connect the customer's legacy network with an OVHcloud vRack. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -The L2 mode is limited to a point-to-point topology: a backup link through a second PoP is not supported. - -![L2 Topologies](images/occ-l2-topologies.png){.thumbnail} - -LACP is mandatory for aggregation when 2 links are configured with PoP. - -Jumbo frames up to 9000 bytes are supported. - -Connections between a PoP and a DC benefit from the OVHcloud backbone. An internal link failure is therefore supported and will not impact customer traffic. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.en-au.md b/pages/network/ovhcloud_connect/occ-layer2/guide.en-au.md deleted file mode 100644 index e689d317313..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.en-au.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Layer 2 mode -excerpt: 'Details about using Layer 2 (L2) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 2 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 2 implementation - -![L2 Implementation](images/occ-l2-implementation.png){.thumbnail} - -The L2 tunnel is forwarded directly to/from the vRack, so all L2 traffic is forwarded to/from the customer inter-connection. - -L2 traffic refers to Ethernet frames, with an 802.1q header, if applicable: - -- Ethernet broadcast is forwarded. -- Unknown Ethernet unicast is forwarded. -- Multicast is forwarded (considered broadcast, limited to 20pps). -- Specific point-to-point Ethernet frames (like LLDP or LACP) are not forwarded - -Only one OVHcloud Connect L2 is supported per vRack: each PoP/EntryPoint can only be associated with one DC/EndPoint. - -![Supported and unsupported L2 Design](images/occ-l2-supported-unsupported.png){.thumbnail} - -With L2 mode, redundancy cannot be exploited between two PoP/EntryPoint. The only solution is to use a LAG on a PoP/EntryPoint. - -### Connection mode details - -L2 operates at the Ethernet level. The customer's vRack is extended "as-is" from OVHcloud and forwarded to the customer link. Transparent to VLANs, this mode is the best way to inter-connect the customer's legacy network with an OVHcloud vRack. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -The L2 mode is limited to a point-to-point topology: a backup link through a second PoP is not supported. - -![L2 Topologies](images/occ-l2-topologies.png){.thumbnail} - -LACP is mandatory for aggregation when 2 links are configured with PoP. - -Jumbo frames up to 9000 bytes are supported. - -Connections between a PoP and a DC benefit from the OVHcloud backbone. An internal link failure is therefore supported and will not impact customer traffic. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.en-ca.md b/pages/network/ovhcloud_connect/occ-layer2/guide.en-ca.md deleted file mode 100644 index e689d317313..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.en-ca.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Layer 2 mode -excerpt: 'Details about using Layer 2 (L2) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 2 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 2 implementation - -![L2 Implementation](images/occ-l2-implementation.png){.thumbnail} - -The L2 tunnel is forwarded directly to/from the vRack, so all L2 traffic is forwarded to/from the customer inter-connection. - -L2 traffic refers to Ethernet frames, with an 802.1q header, if applicable: - -- Ethernet broadcast is forwarded. -- Unknown Ethernet unicast is forwarded. -- Multicast is forwarded (considered broadcast, limited to 20pps). -- Specific point-to-point Ethernet frames (like LLDP or LACP) are not forwarded - -Only one OVHcloud Connect L2 is supported per vRack: each PoP/EntryPoint can only be associated with one DC/EndPoint. - -![Supported and unsupported L2 Design](images/occ-l2-supported-unsupported.png){.thumbnail} - -With L2 mode, redundancy cannot be exploited between two PoP/EntryPoint. The only solution is to use a LAG on a PoP/EntryPoint. - -### Connection mode details - -L2 operates at the Ethernet level. The customer's vRack is extended "as-is" from OVHcloud and forwarded to the customer link. Transparent to VLANs, this mode is the best way to inter-connect the customer's legacy network with an OVHcloud vRack. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -The L2 mode is limited to a point-to-point topology: a backup link through a second PoP is not supported. - -![L2 Topologies](images/occ-l2-topologies.png){.thumbnail} - -LACP is mandatory for aggregation when 2 links are configured with PoP. - -Jumbo frames up to 9000 bytes are supported. - -Connections between a PoP and a DC benefit from the OVHcloud backbone. An internal link failure is therefore supported and will not impact customer traffic. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.en-gb.md b/pages/network/ovhcloud_connect/occ-layer2/guide.en-gb.md deleted file mode 100644 index e689d317313..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.en-gb.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Layer 2 mode -excerpt: 'Details about using Layer 2 (L2) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 2 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 2 implementation - -![L2 Implementation](images/occ-l2-implementation.png){.thumbnail} - -The L2 tunnel is forwarded directly to/from the vRack, so all L2 traffic is forwarded to/from the customer inter-connection. - -L2 traffic refers to Ethernet frames, with an 802.1q header, if applicable: - -- Ethernet broadcast is forwarded. -- Unknown Ethernet unicast is forwarded. -- Multicast is forwarded (considered broadcast, limited to 20pps). -- Specific point-to-point Ethernet frames (like LLDP or LACP) are not forwarded - -Only one OVHcloud Connect L2 is supported per vRack: each PoP/EntryPoint can only be associated with one DC/EndPoint. - -![Supported and unsupported L2 Design](images/occ-l2-supported-unsupported.png){.thumbnail} - -With L2 mode, redundancy cannot be exploited between two PoP/EntryPoint. The only solution is to use a LAG on a PoP/EntryPoint. - -### Connection mode details - -L2 operates at the Ethernet level. The customer's vRack is extended "as-is" from OVHcloud and forwarded to the customer link. Transparent to VLANs, this mode is the best way to inter-connect the customer's legacy network with an OVHcloud vRack. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -The L2 mode is limited to a point-to-point topology: a backup link through a second PoP is not supported. - -![L2 Topologies](images/occ-l2-topologies.png){.thumbnail} - -LACP is mandatory for aggregation when 2 links are configured with PoP. - -Jumbo frames up to 9000 bytes are supported. - -Connections between a PoP and a DC benefit from the OVHcloud backbone. An internal link failure is therefore supported and will not impact customer traffic. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.en-ie.md b/pages/network/ovhcloud_connect/occ-layer2/guide.en-ie.md deleted file mode 100644 index e689d317313..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.en-ie.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Layer 2 mode -excerpt: 'Details about using Layer 2 (L2) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 2 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 2 implementation - -![L2 Implementation](images/occ-l2-implementation.png){.thumbnail} - -The L2 tunnel is forwarded directly to/from the vRack, so all L2 traffic is forwarded to/from the customer inter-connection. - -L2 traffic refers to Ethernet frames, with an 802.1q header, if applicable: - -- Ethernet broadcast is forwarded. -- Unknown Ethernet unicast is forwarded. -- Multicast is forwarded (considered broadcast, limited to 20pps). -- Specific point-to-point Ethernet frames (like LLDP or LACP) are not forwarded - -Only one OVHcloud Connect L2 is supported per vRack: each PoP/EntryPoint can only be associated with one DC/EndPoint. - -![Supported and unsupported L2 Design](images/occ-l2-supported-unsupported.png){.thumbnail} - -With L2 mode, redundancy cannot be exploited between two PoP/EntryPoint. The only solution is to use a LAG on a PoP/EntryPoint. - -### Connection mode details - -L2 operates at the Ethernet level. The customer's vRack is extended "as-is" from OVHcloud and forwarded to the customer link. Transparent to VLANs, this mode is the best way to inter-connect the customer's legacy network with an OVHcloud vRack. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -The L2 mode is limited to a point-to-point topology: a backup link through a second PoP is not supported. - -![L2 Topologies](images/occ-l2-topologies.png){.thumbnail} - -LACP is mandatory for aggregation when 2 links are configured with PoP. - -Jumbo frames up to 9000 bytes are supported. - -Connections between a PoP and a DC benefit from the OVHcloud backbone. An internal link failure is therefore supported and will not impact customer traffic. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.en-sg.md b/pages/network/ovhcloud_connect/occ-layer2/guide.en-sg.md deleted file mode 100644 index e689d317313..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.en-sg.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Layer 2 mode -excerpt: 'Details about using Layer 2 (L2) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 2 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 2 implementation - -![L2 Implementation](images/occ-l2-implementation.png){.thumbnail} - -The L2 tunnel is forwarded directly to/from the vRack, so all L2 traffic is forwarded to/from the customer inter-connection. - -L2 traffic refers to Ethernet frames, with an 802.1q header, if applicable: - -- Ethernet broadcast is forwarded. -- Unknown Ethernet unicast is forwarded. -- Multicast is forwarded (considered broadcast, limited to 20pps). -- Specific point-to-point Ethernet frames (like LLDP or LACP) are not forwarded - -Only one OVHcloud Connect L2 is supported per vRack: each PoP/EntryPoint can only be associated with one DC/EndPoint. - -![Supported and unsupported L2 Design](images/occ-l2-supported-unsupported.png){.thumbnail} - -With L2 mode, redundancy cannot be exploited between two PoP/EntryPoint. The only solution is to use a LAG on a PoP/EntryPoint. - -### Connection mode details - -L2 operates at the Ethernet level. The customer's vRack is extended "as-is" from OVHcloud and forwarded to the customer link. Transparent to VLANs, this mode is the best way to inter-connect the customer's legacy network with an OVHcloud vRack. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -The L2 mode is limited to a point-to-point topology: a backup link through a second PoP is not supported. - -![L2 Topologies](images/occ-l2-topologies.png){.thumbnail} - -LACP is mandatory for aggregation when 2 links are configured with PoP. - -Jumbo frames up to 9000 bytes are supported. - -Connections between a PoP and a DC benefit from the OVHcloud backbone. An internal link failure is therefore supported and will not impact customer traffic. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.en-us.md b/pages/network/ovhcloud_connect/occ-layer2/guide.en-us.md deleted file mode 100644 index e689d317313..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.en-us.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Layer 2 mode -excerpt: 'Details about using Layer 2 (L2) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 2 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 2 implementation - -![L2 Implementation](images/occ-l2-implementation.png){.thumbnail} - -The L2 tunnel is forwarded directly to/from the vRack, so all L2 traffic is forwarded to/from the customer inter-connection. - -L2 traffic refers to Ethernet frames, with an 802.1q header, if applicable: - -- Ethernet broadcast is forwarded. -- Unknown Ethernet unicast is forwarded. -- Multicast is forwarded (considered broadcast, limited to 20pps). -- Specific point-to-point Ethernet frames (like LLDP or LACP) are not forwarded - -Only one OVHcloud Connect L2 is supported per vRack: each PoP/EntryPoint can only be associated with one DC/EndPoint. - -![Supported and unsupported L2 Design](images/occ-l2-supported-unsupported.png){.thumbnail} - -With L2 mode, redundancy cannot be exploited between two PoP/EntryPoint. The only solution is to use a LAG on a PoP/EntryPoint. - -### Connection mode details - -L2 operates at the Ethernet level. The customer's vRack is extended "as-is" from OVHcloud and forwarded to the customer link. Transparent to VLANs, this mode is the best way to inter-connect the customer's legacy network with an OVHcloud vRack. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -The L2 mode is limited to a point-to-point topology: a backup link through a second PoP is not supported. - -![L2 Topologies](images/occ-l2-topologies.png){.thumbnail} - -LACP is mandatory for aggregation when 2 links are configured with PoP. - -Jumbo frames up to 9000 bytes are supported. - -Connections between a PoP and a DC benefit from the OVHcloud backbone. An internal link failure is therefore supported and will not impact customer traffic. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.es-es.md b/pages/network/ovhcloud_connect/occ-layer2/guide.es-es.md deleted file mode 100644 index e689d317313..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.es-es.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Layer 2 mode -excerpt: 'Details about using Layer 2 (L2) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 2 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 2 implementation - -![L2 Implementation](images/occ-l2-implementation.png){.thumbnail} - -The L2 tunnel is forwarded directly to/from the vRack, so all L2 traffic is forwarded to/from the customer inter-connection. - -L2 traffic refers to Ethernet frames, with an 802.1q header, if applicable: - -- Ethernet broadcast is forwarded. -- Unknown Ethernet unicast is forwarded. -- Multicast is forwarded (considered broadcast, limited to 20pps). -- Specific point-to-point Ethernet frames (like LLDP or LACP) are not forwarded - -Only one OVHcloud Connect L2 is supported per vRack: each PoP/EntryPoint can only be associated with one DC/EndPoint. - -![Supported and unsupported L2 Design](images/occ-l2-supported-unsupported.png){.thumbnail} - -With L2 mode, redundancy cannot be exploited between two PoP/EntryPoint. The only solution is to use a LAG on a PoP/EntryPoint. - -### Connection mode details - -L2 operates at the Ethernet level. The customer's vRack is extended "as-is" from OVHcloud and forwarded to the customer link. Transparent to VLANs, this mode is the best way to inter-connect the customer's legacy network with an OVHcloud vRack. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -The L2 mode is limited to a point-to-point topology: a backup link through a second PoP is not supported. - -![L2 Topologies](images/occ-l2-topologies.png){.thumbnail} - -LACP is mandatory for aggregation when 2 links are configured with PoP. - -Jumbo frames up to 9000 bytes are supported. - -Connections between a PoP and a DC benefit from the OVHcloud backbone. An internal link failure is therefore supported and will not impact customer traffic. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.es-us.md b/pages/network/ovhcloud_connect/occ-layer2/guide.es-us.md deleted file mode 100644 index e689d317313..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.es-us.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Layer 2 mode -excerpt: 'Details about using Layer 2 (L2) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 2 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 2 implementation - -![L2 Implementation](images/occ-l2-implementation.png){.thumbnail} - -The L2 tunnel is forwarded directly to/from the vRack, so all L2 traffic is forwarded to/from the customer inter-connection. - -L2 traffic refers to Ethernet frames, with an 802.1q header, if applicable: - -- Ethernet broadcast is forwarded. -- Unknown Ethernet unicast is forwarded. -- Multicast is forwarded (considered broadcast, limited to 20pps). -- Specific point-to-point Ethernet frames (like LLDP or LACP) are not forwarded - -Only one OVHcloud Connect L2 is supported per vRack: each PoP/EntryPoint can only be associated with one DC/EndPoint. - -![Supported and unsupported L2 Design](images/occ-l2-supported-unsupported.png){.thumbnail} - -With L2 mode, redundancy cannot be exploited between two PoP/EntryPoint. The only solution is to use a LAG on a PoP/EntryPoint. - -### Connection mode details - -L2 operates at the Ethernet level. The customer's vRack is extended "as-is" from OVHcloud and forwarded to the customer link. Transparent to VLANs, this mode is the best way to inter-connect the customer's legacy network with an OVHcloud vRack. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -The L2 mode is limited to a point-to-point topology: a backup link through a second PoP is not supported. - -![L2 Topologies](images/occ-l2-topologies.png){.thumbnail} - -LACP is mandatory for aggregation when 2 links are configured with PoP. - -Jumbo frames up to 9000 bytes are supported. - -Connections between a PoP and a DC benefit from the OVHcloud backbone. An internal link failure is therefore supported and will not impact customer traffic. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.fr-ca.md b/pages/network/ovhcloud_connect/occ-layer2/guide.fr-ca.md deleted file mode 100644 index 6b281a7df1c..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.fr-ca.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Mode Layer 2 (L2) -excerpt: Détails sur le mode Layer 2 (L2) pour OVHcloud Connect -updated: 2020-09-14 ---- - -## Objectif - -**Découvrez les détails sur l'implémentation et le mode de connexion du mode Layer 2 (L2) pour l'offre OVHcloud Connect.** - -## En pratique - -### Implémentation du mode L2 - -![Implémentation L2](images/occ-l2-implementation.png){.thumbnail} - -Le tunnel L2 est directement transféré vers/depuis le vRack afin que tout le trafic L2 soit transféré vers/depuis l'interconnexion client. - -Par trafic L2, on entend les trames Ethernet, avec un en-tête 802.1q, le cas échéant: - -* Le broadcast Ethernet est transféré. -* L'unicast inconnu Ethernet est transféré. -* Le multicast est transféré (il est considéré comme broadcast et limité à 20 pps). -* Les trames Ethernet point-to-point spécifiques (telles que LLDP ou LACP) ne sont pas transférées. - -Un seul OVHcloud Connect L2 est pris en charge par vRack: un PoP/EntryPoint ne peut être associé qu'à un seul DC/EndPoint. - -![Conception L2 prise en charge](images/occ-l2-supported-unsupported.png){.thumbnail} - -Avec le mode L2, la redondance ne peut pas être exploitée entre deux PoP/EntryPoint. La seule solution consiste à utiliser un LAG sur un PoP/EntryPoint. - -### Détails du mode de connexion - -Le mode L2 signifie un fonctionnement au niveau Ethernet. Le vRack du client est étendu « en l’état » à partir de OVHcloud et transféré au lien du client. Ce mode est transparent pour les VLAN et constitue le meilleur moyen d'interconnecter le réseau existant du client avec le vRack OVHcloud. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -Le mode L2 est limité à la topologie point-to-point: la liaison de backup via un second PoP n'est pas prise en charge. - -![Topologies L2](images/occ-l2-topologies.png){.thumbnail} - -LACP est obligatoire pour l'agrégation lorsque 2 liens sont configurés avec PoP. - -Les trames Jumbo (Jumbo frames) jusqu'à 9000 octets sont prises en charge. - -La connexion entre un PoP et un Datacentre bénéficie du backbone OVHcloud, de sorte qu'une défaillance de liaison interne est prise en charge et n'affectera pas le trafic client. - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.fr-fr.md b/pages/network/ovhcloud_connect/occ-layer2/guide.fr-fr.md deleted file mode 100644 index 6b281a7df1c..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.fr-fr.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Mode Layer 2 (L2) -excerpt: Détails sur le mode Layer 2 (L2) pour OVHcloud Connect -updated: 2020-09-14 ---- - -## Objectif - -**Découvrez les détails sur l'implémentation et le mode de connexion du mode Layer 2 (L2) pour l'offre OVHcloud Connect.** - -## En pratique - -### Implémentation du mode L2 - -![Implémentation L2](images/occ-l2-implementation.png){.thumbnail} - -Le tunnel L2 est directement transféré vers/depuis le vRack afin que tout le trafic L2 soit transféré vers/depuis l'interconnexion client. - -Par trafic L2, on entend les trames Ethernet, avec un en-tête 802.1q, le cas échéant: - -* Le broadcast Ethernet est transféré. -* L'unicast inconnu Ethernet est transféré. -* Le multicast est transféré (il est considéré comme broadcast et limité à 20 pps). -* Les trames Ethernet point-to-point spécifiques (telles que LLDP ou LACP) ne sont pas transférées. - -Un seul OVHcloud Connect L2 est pris en charge par vRack: un PoP/EntryPoint ne peut être associé qu'à un seul DC/EndPoint. - -![Conception L2 prise en charge](images/occ-l2-supported-unsupported.png){.thumbnail} - -Avec le mode L2, la redondance ne peut pas être exploitée entre deux PoP/EntryPoint. La seule solution consiste à utiliser un LAG sur un PoP/EntryPoint. - -### Détails du mode de connexion - -Le mode L2 signifie un fonctionnement au niveau Ethernet. Le vRack du client est étendu « en l’état » à partir de OVHcloud et transféré au lien du client. Ce mode est transparent pour les VLAN et constitue le meilleur moyen d'interconnecter le réseau existant du client avec le vRack OVHcloud. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -Le mode L2 est limité à la topologie point-to-point: la liaison de backup via un second PoP n'est pas prise en charge. - -![Topologies L2](images/occ-l2-topologies.png){.thumbnail} - -LACP est obligatoire pour l'agrégation lorsque 2 liens sont configurés avec PoP. - -Les trames Jumbo (Jumbo frames) jusqu'à 9000 octets sont prises en charge. - -La connexion entre un PoP et un Datacentre bénéficie du backbone OVHcloud, de sorte qu'une défaillance de liaison interne est prise en charge et n'affectera pas le trafic client. - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.it-it.md b/pages/network/ovhcloud_connect/occ-layer2/guide.it-it.md deleted file mode 100644 index e689d317313..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.it-it.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Layer 2 mode -excerpt: 'Details about using Layer 2 (L2) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 2 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 2 implementation - -![L2 Implementation](images/occ-l2-implementation.png){.thumbnail} - -The L2 tunnel is forwarded directly to/from the vRack, so all L2 traffic is forwarded to/from the customer inter-connection. - -L2 traffic refers to Ethernet frames, with an 802.1q header, if applicable: - -- Ethernet broadcast is forwarded. -- Unknown Ethernet unicast is forwarded. -- Multicast is forwarded (considered broadcast, limited to 20pps). -- Specific point-to-point Ethernet frames (like LLDP or LACP) are not forwarded - -Only one OVHcloud Connect L2 is supported per vRack: each PoP/EntryPoint can only be associated with one DC/EndPoint. - -![Supported and unsupported L2 Design](images/occ-l2-supported-unsupported.png){.thumbnail} - -With L2 mode, redundancy cannot be exploited between two PoP/EntryPoint. The only solution is to use a LAG on a PoP/EntryPoint. - -### Connection mode details - -L2 operates at the Ethernet level. The customer's vRack is extended "as-is" from OVHcloud and forwarded to the customer link. Transparent to VLANs, this mode is the best way to inter-connect the customer's legacy network with an OVHcloud vRack. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -The L2 mode is limited to a point-to-point topology: a backup link through a second PoP is not supported. - -![L2 Topologies](images/occ-l2-topologies.png){.thumbnail} - -LACP is mandatory for aggregation when 2 links are configured with PoP. - -Jumbo frames up to 9000 bytes are supported. - -Connections between a PoP and a DC benefit from the OVHcloud backbone. An internal link failure is therefore supported and will not impact customer traffic. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.pl-pl.md b/pages/network/ovhcloud_connect/occ-layer2/guide.pl-pl.md deleted file mode 100644 index e689d317313..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.pl-pl.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Layer 2 mode -excerpt: 'Details about using Layer 2 (L2) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 2 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 2 implementation - -![L2 Implementation](images/occ-l2-implementation.png){.thumbnail} - -The L2 tunnel is forwarded directly to/from the vRack, so all L2 traffic is forwarded to/from the customer inter-connection. - -L2 traffic refers to Ethernet frames, with an 802.1q header, if applicable: - -- Ethernet broadcast is forwarded. -- Unknown Ethernet unicast is forwarded. -- Multicast is forwarded (considered broadcast, limited to 20pps). -- Specific point-to-point Ethernet frames (like LLDP or LACP) are not forwarded - -Only one OVHcloud Connect L2 is supported per vRack: each PoP/EntryPoint can only be associated with one DC/EndPoint. - -![Supported and unsupported L2 Design](images/occ-l2-supported-unsupported.png){.thumbnail} - -With L2 mode, redundancy cannot be exploited between two PoP/EntryPoint. The only solution is to use a LAG on a PoP/EntryPoint. - -### Connection mode details - -L2 operates at the Ethernet level. The customer's vRack is extended "as-is" from OVHcloud and forwarded to the customer link. Transparent to VLANs, this mode is the best way to inter-connect the customer's legacy network with an OVHcloud vRack. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -The L2 mode is limited to a point-to-point topology: a backup link through a second PoP is not supported. - -![L2 Topologies](images/occ-l2-topologies.png){.thumbnail} - -LACP is mandatory for aggregation when 2 links are configured with PoP. - -Jumbo frames up to 9000 bytes are supported. - -Connections between a PoP and a DC benefit from the OVHcloud backbone. An internal link failure is therefore supported and will not impact customer traffic. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer2/guide.pt-pt.md b/pages/network/ovhcloud_connect/occ-layer2/guide.pt-pt.md deleted file mode 100644 index e689d317313..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/guide.pt-pt.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Layer 2 mode -excerpt: 'Details about using Layer 2 (L2) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 2 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 2 implementation - -![L2 Implementation](images/occ-l2-implementation.png){.thumbnail} - -The L2 tunnel is forwarded directly to/from the vRack, so all L2 traffic is forwarded to/from the customer inter-connection. - -L2 traffic refers to Ethernet frames, with an 802.1q header, if applicable: - -- Ethernet broadcast is forwarded. -- Unknown Ethernet unicast is forwarded. -- Multicast is forwarded (considered broadcast, limited to 20pps). -- Specific point-to-point Ethernet frames (like LLDP or LACP) are not forwarded - -Only one OVHcloud Connect L2 is supported per vRack: each PoP/EntryPoint can only be associated with one DC/EndPoint. - -![Supported and unsupported L2 Design](images/occ-l2-supported-unsupported.png){.thumbnail} - -With L2 mode, redundancy cannot be exploited between two PoP/EntryPoint. The only solution is to use a LAG on a PoP/EntryPoint. - -### Connection mode details - -L2 operates at the Ethernet level. The customer's vRack is extended "as-is" from OVHcloud and forwarded to the customer link. Transparent to VLANs, this mode is the best way to inter-connect the customer's legacy network with an OVHcloud vRack. - -![L2 Trafic](images/occ-l2-trafic.png){.thumbnail} - -The L2 mode is limited to a point-to-point topology: a backup link through a second PoP is not supported. - -![L2 Topologies](images/occ-l2-topologies.png){.thumbnail} - -LACP is mandatory for aggregation when 2 links are configured with PoP. - -Jumbo frames up to 9000 bytes are supported. - -Connections between a PoP and a DC benefit from the OVHcloud backbone. An internal link failure is therefore supported and will not impact customer traffic. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer2/images/occ-l2-implementation.png b/pages/network/ovhcloud_connect/occ-layer2/images/occ-l2-implementation.png deleted file mode 100644 index 8226a4ca29f..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-layer2/images/occ-l2-implementation.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-layer2/images/occ-l2-supported-unsupported.png b/pages/network/ovhcloud_connect/occ-layer2/images/occ-l2-supported-unsupported.png deleted file mode 100644 index c56cf102cff..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-layer2/images/occ-l2-supported-unsupported.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-layer2/images/occ-l2-topologies.png b/pages/network/ovhcloud_connect/occ-layer2/images/occ-l2-topologies.png deleted file mode 100644 index 6fcb5e186dd..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-layer2/images/occ-l2-topologies.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-layer2/images/occ-l2-trafic.png b/pages/network/ovhcloud_connect/occ-layer2/images/occ-l2-trafic.png deleted file mode 100644 index ad72df31a4e..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-layer2/images/occ-l2-trafic.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-layer2/meta.yaml b/pages/network/ovhcloud_connect/occ-layer2/meta.yaml deleted file mode 100755 index 538797bebad..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer2/meta.yaml +++ /dev/null @@ -1,2 +0,0 @@ -id: 7d9dc89e-de7f-4797-abb7-04d9bd2906f4 -full_slug: network-ovhcloud-connect-layer2 \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.de-de.md b/pages/network/ovhcloud_connect/occ-layer3/guide.de-de.md deleted file mode 100644 index 9ea3b7e1cab..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.de-de.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Layer 3 mode -excerpt: 'Details about using Layer 3 (L3) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 3 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 3 implementation - -OVHcloud Connect configured in Layer 3 differs from Layer 2 as you have to configure the L3 domain on each PoP/EntryPoint and DC/EndPoint. - -![L3 Implementation](images/occ-l3-implementation.png){.thumbnail} - -A Layer 3 domain is composed of: - -- A subnet -- A BGP ASN - -The L3 domain is an IP routing instance provided by OVHcloud. Traffic is forwarded between PoP/EntryPoint and DC/Endpoint, not between two PoPs/EntryPoints. There is no need for internal IP addressing between PoP/EntryPoint and DC/EndPoint. In the data centre, the routing instance inside the L3 domain is composed of two devices, labelled ‘A’ and ‘B’. - -Based on this principle it is possible to manage several OVHcloud Connect services. - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -As a result, L3 makes it compatible with a multi-DC configuration. - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -The two examples above illustrate the configuration of two OVHcloud Connect services, as one OVHcloud Connect equals one PoP/EntryPoint. - -**Rules:** - -- You can have as many OVHcloud Connect L3 as you want in the same vRack. -- You can associate several PoPs/EntryPoints with one DC/EndPoint. -- You can associate several DCs/EndPoints with one PoP/EntryPoint. -- You cannot associate two PoPs/EntryPoints (i.e. you cannot forward traffic between them). -- One L3 domain can only be associated with one DC/EndPoint. -- One L3 domain (i.e. subnet) cannot be stretched between two DCs or two PoPs. -- An OVHcloud Connect L2 can be mixed with several OVHcloud Connect L3 in the same vRack. - -![L3 Rules](images/occ-l3-rules.gif){.thumbnail} - -The following schema shows the mix of L2 and L3. They can end in the same OVHcloud data centre or not. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Connection mode details - -![L3 Architecture](images/occ-l3-architecture.png){.thumbnail} - -On such an architecture, two L3 domains are needed: PoP/EntryPoint and DC/EndPoint. - -"IP Net A" is part of the L3 Domain in the DC. The following rules apply: - -- IP addressing plan (subnet and netmask) with a minimum netmask of /29. -- The first IP address is reserved for the virtual gateway (if running VRRP). -- The two following IP addresses are reserved for the OVHcloud routing instance. -- All other IP addresses are available to the customer. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud virtual router address (if enabled) | -| A.B.C.2 | OVHcloud router A | -| A.B.C.3 | OVHcloud router B | - -"IP Net B" is part of the L3 Domain in the PoP. The following rules apply: - -- Supported netmask: /30 (CIDR notation). -- The first IP address is reserved for the OVHcloud routing instance. -- The second IP address is used for customer equipment. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud router | -| A.B.C.2 | Customer router | -| A.B.C.3 | Subnet broadcast | - -#### VRRP configuration in the DC/EndPoint - -VRRP allows router redundancy on OVHcloud devices. - -- Each DC/EndPoint supports only one VRRP instance. -- The VRRP VRID value is provided by OVHcloud. -- By default, VRRP is master on ‘A’ device. -- Static routes can be configured. - -#### BGP configuration - -BGP is mandatory in a PoP/EntryPoint and optional in a DC/EndPoint. Enabling BGP in a DC/EndPoint disables VRRP configuration. - -- Each PoP/EntryPoint and DC/EndPoint needs an AS. This AS must be independent from the customer BGP AS to form an eBGP relation. The recommended value is in the range 64512-65534. -- Each PoP/EntryPoint supports only one BGP session (no eBGP Multihop). -- With two or more PoPs/EntryPoints, ECMP is automatically enabled. MED and/or AS-PATH must be tuned to have path selection. -- Each DC/EndPoint supports up to 4 BGP peers. -- Up to 100 prefixes can be announced per BGP session. -- For each DC/EndPoint you must establish a BGP session with ‘A’ device and ‘B’ device. -- By default, BFD is activated on all BGP sessions. This protocol is higly recommended on the DC side as well to have a faster convergence. - -For example, IP network 'B' will be announced to the OVHcloud router through BGP session. - -![L3 BGP vRack](images/occ-l3-bgpvrack.png){.thumbnail} - -At a more global level, BGP topology will look like this: - -![L3 BGP Global Topology](images/occ-l3-bgpglobal.png){.thumbnail} - -#### BGP path selection - -By default, all available paths are enabled using ECMP, with up to 4 paths supported. To have an active/passive topology with two PoPs/EntryPoints, you can use AS path prepending or MED. - -If AS path prepending is configured on the customer's devices in PoP2, the topology will look like this: - -![L3 BGP as-prepend](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Note: AS path prepending is not configurable on OVHcloud devices. - -Using MED is an alternative to achieve the same topology. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.en-asia.md b/pages/network/ovhcloud_connect/occ-layer3/guide.en-asia.md deleted file mode 100644 index 9ea3b7e1cab..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.en-asia.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Layer 3 mode -excerpt: 'Details about using Layer 3 (L3) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 3 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 3 implementation - -OVHcloud Connect configured in Layer 3 differs from Layer 2 as you have to configure the L3 domain on each PoP/EntryPoint and DC/EndPoint. - -![L3 Implementation](images/occ-l3-implementation.png){.thumbnail} - -A Layer 3 domain is composed of: - -- A subnet -- A BGP ASN - -The L3 domain is an IP routing instance provided by OVHcloud. Traffic is forwarded between PoP/EntryPoint and DC/Endpoint, not between two PoPs/EntryPoints. There is no need for internal IP addressing between PoP/EntryPoint and DC/EndPoint. In the data centre, the routing instance inside the L3 domain is composed of two devices, labelled ‘A’ and ‘B’. - -Based on this principle it is possible to manage several OVHcloud Connect services. - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -As a result, L3 makes it compatible with a multi-DC configuration. - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -The two examples above illustrate the configuration of two OVHcloud Connect services, as one OVHcloud Connect equals one PoP/EntryPoint. - -**Rules:** - -- You can have as many OVHcloud Connect L3 as you want in the same vRack. -- You can associate several PoPs/EntryPoints with one DC/EndPoint. -- You can associate several DCs/EndPoints with one PoP/EntryPoint. -- You cannot associate two PoPs/EntryPoints (i.e. you cannot forward traffic between them). -- One L3 domain can only be associated with one DC/EndPoint. -- One L3 domain (i.e. subnet) cannot be stretched between two DCs or two PoPs. -- An OVHcloud Connect L2 can be mixed with several OVHcloud Connect L3 in the same vRack. - -![L3 Rules](images/occ-l3-rules.gif){.thumbnail} - -The following schema shows the mix of L2 and L3. They can end in the same OVHcloud data centre or not. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Connection mode details - -![L3 Architecture](images/occ-l3-architecture.png){.thumbnail} - -On such an architecture, two L3 domains are needed: PoP/EntryPoint and DC/EndPoint. - -"IP Net A" is part of the L3 Domain in the DC. The following rules apply: - -- IP addressing plan (subnet and netmask) with a minimum netmask of /29. -- The first IP address is reserved for the virtual gateway (if running VRRP). -- The two following IP addresses are reserved for the OVHcloud routing instance. -- All other IP addresses are available to the customer. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud virtual router address (if enabled) | -| A.B.C.2 | OVHcloud router A | -| A.B.C.3 | OVHcloud router B | - -"IP Net B" is part of the L3 Domain in the PoP. The following rules apply: - -- Supported netmask: /30 (CIDR notation). -- The first IP address is reserved for the OVHcloud routing instance. -- The second IP address is used for customer equipment. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud router | -| A.B.C.2 | Customer router | -| A.B.C.3 | Subnet broadcast | - -#### VRRP configuration in the DC/EndPoint - -VRRP allows router redundancy on OVHcloud devices. - -- Each DC/EndPoint supports only one VRRP instance. -- The VRRP VRID value is provided by OVHcloud. -- By default, VRRP is master on ‘A’ device. -- Static routes can be configured. - -#### BGP configuration - -BGP is mandatory in a PoP/EntryPoint and optional in a DC/EndPoint. Enabling BGP in a DC/EndPoint disables VRRP configuration. - -- Each PoP/EntryPoint and DC/EndPoint needs an AS. This AS must be independent from the customer BGP AS to form an eBGP relation. The recommended value is in the range 64512-65534. -- Each PoP/EntryPoint supports only one BGP session (no eBGP Multihop). -- With two or more PoPs/EntryPoints, ECMP is automatically enabled. MED and/or AS-PATH must be tuned to have path selection. -- Each DC/EndPoint supports up to 4 BGP peers. -- Up to 100 prefixes can be announced per BGP session. -- For each DC/EndPoint you must establish a BGP session with ‘A’ device and ‘B’ device. -- By default, BFD is activated on all BGP sessions. This protocol is higly recommended on the DC side as well to have a faster convergence. - -For example, IP network 'B' will be announced to the OVHcloud router through BGP session. - -![L3 BGP vRack](images/occ-l3-bgpvrack.png){.thumbnail} - -At a more global level, BGP topology will look like this: - -![L3 BGP Global Topology](images/occ-l3-bgpglobal.png){.thumbnail} - -#### BGP path selection - -By default, all available paths are enabled using ECMP, with up to 4 paths supported. To have an active/passive topology with two PoPs/EntryPoints, you can use AS path prepending or MED. - -If AS path prepending is configured on the customer's devices in PoP2, the topology will look like this: - -![L3 BGP as-prepend](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Note: AS path prepending is not configurable on OVHcloud devices. - -Using MED is an alternative to achieve the same topology. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.en-au.md b/pages/network/ovhcloud_connect/occ-layer3/guide.en-au.md deleted file mode 100644 index 9ea3b7e1cab..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.en-au.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Layer 3 mode -excerpt: 'Details about using Layer 3 (L3) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 3 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 3 implementation - -OVHcloud Connect configured in Layer 3 differs from Layer 2 as you have to configure the L3 domain on each PoP/EntryPoint and DC/EndPoint. - -![L3 Implementation](images/occ-l3-implementation.png){.thumbnail} - -A Layer 3 domain is composed of: - -- A subnet -- A BGP ASN - -The L3 domain is an IP routing instance provided by OVHcloud. Traffic is forwarded between PoP/EntryPoint and DC/Endpoint, not between two PoPs/EntryPoints. There is no need for internal IP addressing between PoP/EntryPoint and DC/EndPoint. In the data centre, the routing instance inside the L3 domain is composed of two devices, labelled ‘A’ and ‘B’. - -Based on this principle it is possible to manage several OVHcloud Connect services. - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -As a result, L3 makes it compatible with a multi-DC configuration. - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -The two examples above illustrate the configuration of two OVHcloud Connect services, as one OVHcloud Connect equals one PoP/EntryPoint. - -**Rules:** - -- You can have as many OVHcloud Connect L3 as you want in the same vRack. -- You can associate several PoPs/EntryPoints with one DC/EndPoint. -- You can associate several DCs/EndPoints with one PoP/EntryPoint. -- You cannot associate two PoPs/EntryPoints (i.e. you cannot forward traffic between them). -- One L3 domain can only be associated with one DC/EndPoint. -- One L3 domain (i.e. subnet) cannot be stretched between two DCs or two PoPs. -- An OVHcloud Connect L2 can be mixed with several OVHcloud Connect L3 in the same vRack. - -![L3 Rules](images/occ-l3-rules.gif){.thumbnail} - -The following schema shows the mix of L2 and L3. They can end in the same OVHcloud data centre or not. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Connection mode details - -![L3 Architecture](images/occ-l3-architecture.png){.thumbnail} - -On such an architecture, two L3 domains are needed: PoP/EntryPoint and DC/EndPoint. - -"IP Net A" is part of the L3 Domain in the DC. The following rules apply: - -- IP addressing plan (subnet and netmask) with a minimum netmask of /29. -- The first IP address is reserved for the virtual gateway (if running VRRP). -- The two following IP addresses are reserved for the OVHcloud routing instance. -- All other IP addresses are available to the customer. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud virtual router address (if enabled) | -| A.B.C.2 | OVHcloud router A | -| A.B.C.3 | OVHcloud router B | - -"IP Net B" is part of the L3 Domain in the PoP. The following rules apply: - -- Supported netmask: /30 (CIDR notation). -- The first IP address is reserved for the OVHcloud routing instance. -- The second IP address is used for customer equipment. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud router | -| A.B.C.2 | Customer router | -| A.B.C.3 | Subnet broadcast | - -#### VRRP configuration in the DC/EndPoint - -VRRP allows router redundancy on OVHcloud devices. - -- Each DC/EndPoint supports only one VRRP instance. -- The VRRP VRID value is provided by OVHcloud. -- By default, VRRP is master on ‘A’ device. -- Static routes can be configured. - -#### BGP configuration - -BGP is mandatory in a PoP/EntryPoint and optional in a DC/EndPoint. Enabling BGP in a DC/EndPoint disables VRRP configuration. - -- Each PoP/EntryPoint and DC/EndPoint needs an AS. This AS must be independent from the customer BGP AS to form an eBGP relation. The recommended value is in the range 64512-65534. -- Each PoP/EntryPoint supports only one BGP session (no eBGP Multihop). -- With two or more PoPs/EntryPoints, ECMP is automatically enabled. MED and/or AS-PATH must be tuned to have path selection. -- Each DC/EndPoint supports up to 4 BGP peers. -- Up to 100 prefixes can be announced per BGP session. -- For each DC/EndPoint you must establish a BGP session with ‘A’ device and ‘B’ device. -- By default, BFD is activated on all BGP sessions. This protocol is higly recommended on the DC side as well to have a faster convergence. - -For example, IP network 'B' will be announced to the OVHcloud router through BGP session. - -![L3 BGP vRack](images/occ-l3-bgpvrack.png){.thumbnail} - -At a more global level, BGP topology will look like this: - -![L3 BGP Global Topology](images/occ-l3-bgpglobal.png){.thumbnail} - -#### BGP path selection - -By default, all available paths are enabled using ECMP, with up to 4 paths supported. To have an active/passive topology with two PoPs/EntryPoints, you can use AS path prepending or MED. - -If AS path prepending is configured on the customer's devices in PoP2, the topology will look like this: - -![L3 BGP as-prepend](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Note: AS path prepending is not configurable on OVHcloud devices. - -Using MED is an alternative to achieve the same topology. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.en-ca.md b/pages/network/ovhcloud_connect/occ-layer3/guide.en-ca.md deleted file mode 100644 index 9ea3b7e1cab..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.en-ca.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Layer 3 mode -excerpt: 'Details about using Layer 3 (L3) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 3 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 3 implementation - -OVHcloud Connect configured in Layer 3 differs from Layer 2 as you have to configure the L3 domain on each PoP/EntryPoint and DC/EndPoint. - -![L3 Implementation](images/occ-l3-implementation.png){.thumbnail} - -A Layer 3 domain is composed of: - -- A subnet -- A BGP ASN - -The L3 domain is an IP routing instance provided by OVHcloud. Traffic is forwarded between PoP/EntryPoint and DC/Endpoint, not between two PoPs/EntryPoints. There is no need for internal IP addressing between PoP/EntryPoint and DC/EndPoint. In the data centre, the routing instance inside the L3 domain is composed of two devices, labelled ‘A’ and ‘B’. - -Based on this principle it is possible to manage several OVHcloud Connect services. - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -As a result, L3 makes it compatible with a multi-DC configuration. - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -The two examples above illustrate the configuration of two OVHcloud Connect services, as one OVHcloud Connect equals one PoP/EntryPoint. - -**Rules:** - -- You can have as many OVHcloud Connect L3 as you want in the same vRack. -- You can associate several PoPs/EntryPoints with one DC/EndPoint. -- You can associate several DCs/EndPoints with one PoP/EntryPoint. -- You cannot associate two PoPs/EntryPoints (i.e. you cannot forward traffic between them). -- One L3 domain can only be associated with one DC/EndPoint. -- One L3 domain (i.e. subnet) cannot be stretched between two DCs or two PoPs. -- An OVHcloud Connect L2 can be mixed with several OVHcloud Connect L3 in the same vRack. - -![L3 Rules](images/occ-l3-rules.gif){.thumbnail} - -The following schema shows the mix of L2 and L3. They can end in the same OVHcloud data centre or not. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Connection mode details - -![L3 Architecture](images/occ-l3-architecture.png){.thumbnail} - -On such an architecture, two L3 domains are needed: PoP/EntryPoint and DC/EndPoint. - -"IP Net A" is part of the L3 Domain in the DC. The following rules apply: - -- IP addressing plan (subnet and netmask) with a minimum netmask of /29. -- The first IP address is reserved for the virtual gateway (if running VRRP). -- The two following IP addresses are reserved for the OVHcloud routing instance. -- All other IP addresses are available to the customer. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud virtual router address (if enabled) | -| A.B.C.2 | OVHcloud router A | -| A.B.C.3 | OVHcloud router B | - -"IP Net B" is part of the L3 Domain in the PoP. The following rules apply: - -- Supported netmask: /30 (CIDR notation). -- The first IP address is reserved for the OVHcloud routing instance. -- The second IP address is used for customer equipment. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud router | -| A.B.C.2 | Customer router | -| A.B.C.3 | Subnet broadcast | - -#### VRRP configuration in the DC/EndPoint - -VRRP allows router redundancy on OVHcloud devices. - -- Each DC/EndPoint supports only one VRRP instance. -- The VRRP VRID value is provided by OVHcloud. -- By default, VRRP is master on ‘A’ device. -- Static routes can be configured. - -#### BGP configuration - -BGP is mandatory in a PoP/EntryPoint and optional in a DC/EndPoint. Enabling BGP in a DC/EndPoint disables VRRP configuration. - -- Each PoP/EntryPoint and DC/EndPoint needs an AS. This AS must be independent from the customer BGP AS to form an eBGP relation. The recommended value is in the range 64512-65534. -- Each PoP/EntryPoint supports only one BGP session (no eBGP Multihop). -- With two or more PoPs/EntryPoints, ECMP is automatically enabled. MED and/or AS-PATH must be tuned to have path selection. -- Each DC/EndPoint supports up to 4 BGP peers. -- Up to 100 prefixes can be announced per BGP session. -- For each DC/EndPoint you must establish a BGP session with ‘A’ device and ‘B’ device. -- By default, BFD is activated on all BGP sessions. This protocol is higly recommended on the DC side as well to have a faster convergence. - -For example, IP network 'B' will be announced to the OVHcloud router through BGP session. - -![L3 BGP vRack](images/occ-l3-bgpvrack.png){.thumbnail} - -At a more global level, BGP topology will look like this: - -![L3 BGP Global Topology](images/occ-l3-bgpglobal.png){.thumbnail} - -#### BGP path selection - -By default, all available paths are enabled using ECMP, with up to 4 paths supported. To have an active/passive topology with two PoPs/EntryPoints, you can use AS path prepending or MED. - -If AS path prepending is configured on the customer's devices in PoP2, the topology will look like this: - -![L3 BGP as-prepend](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Note: AS path prepending is not configurable on OVHcloud devices. - -Using MED is an alternative to achieve the same topology. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.en-gb.md b/pages/network/ovhcloud_connect/occ-layer3/guide.en-gb.md deleted file mode 100644 index 9ea3b7e1cab..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.en-gb.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Layer 3 mode -excerpt: 'Details about using Layer 3 (L3) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 3 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 3 implementation - -OVHcloud Connect configured in Layer 3 differs from Layer 2 as you have to configure the L3 domain on each PoP/EntryPoint and DC/EndPoint. - -![L3 Implementation](images/occ-l3-implementation.png){.thumbnail} - -A Layer 3 domain is composed of: - -- A subnet -- A BGP ASN - -The L3 domain is an IP routing instance provided by OVHcloud. Traffic is forwarded between PoP/EntryPoint and DC/Endpoint, not between two PoPs/EntryPoints. There is no need for internal IP addressing between PoP/EntryPoint and DC/EndPoint. In the data centre, the routing instance inside the L3 domain is composed of two devices, labelled ‘A’ and ‘B’. - -Based on this principle it is possible to manage several OVHcloud Connect services. - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -As a result, L3 makes it compatible with a multi-DC configuration. - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -The two examples above illustrate the configuration of two OVHcloud Connect services, as one OVHcloud Connect equals one PoP/EntryPoint. - -**Rules:** - -- You can have as many OVHcloud Connect L3 as you want in the same vRack. -- You can associate several PoPs/EntryPoints with one DC/EndPoint. -- You can associate several DCs/EndPoints with one PoP/EntryPoint. -- You cannot associate two PoPs/EntryPoints (i.e. you cannot forward traffic between them). -- One L3 domain can only be associated with one DC/EndPoint. -- One L3 domain (i.e. subnet) cannot be stretched between two DCs or two PoPs. -- An OVHcloud Connect L2 can be mixed with several OVHcloud Connect L3 in the same vRack. - -![L3 Rules](images/occ-l3-rules.gif){.thumbnail} - -The following schema shows the mix of L2 and L3. They can end in the same OVHcloud data centre or not. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Connection mode details - -![L3 Architecture](images/occ-l3-architecture.png){.thumbnail} - -On such an architecture, two L3 domains are needed: PoP/EntryPoint and DC/EndPoint. - -"IP Net A" is part of the L3 Domain in the DC. The following rules apply: - -- IP addressing plan (subnet and netmask) with a minimum netmask of /29. -- The first IP address is reserved for the virtual gateway (if running VRRP). -- The two following IP addresses are reserved for the OVHcloud routing instance. -- All other IP addresses are available to the customer. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud virtual router address (if enabled) | -| A.B.C.2 | OVHcloud router A | -| A.B.C.3 | OVHcloud router B | - -"IP Net B" is part of the L3 Domain in the PoP. The following rules apply: - -- Supported netmask: /30 (CIDR notation). -- The first IP address is reserved for the OVHcloud routing instance. -- The second IP address is used for customer equipment. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud router | -| A.B.C.2 | Customer router | -| A.B.C.3 | Subnet broadcast | - -#### VRRP configuration in the DC/EndPoint - -VRRP allows router redundancy on OVHcloud devices. - -- Each DC/EndPoint supports only one VRRP instance. -- The VRRP VRID value is provided by OVHcloud. -- By default, VRRP is master on ‘A’ device. -- Static routes can be configured. - -#### BGP configuration - -BGP is mandatory in a PoP/EntryPoint and optional in a DC/EndPoint. Enabling BGP in a DC/EndPoint disables VRRP configuration. - -- Each PoP/EntryPoint and DC/EndPoint needs an AS. This AS must be independent from the customer BGP AS to form an eBGP relation. The recommended value is in the range 64512-65534. -- Each PoP/EntryPoint supports only one BGP session (no eBGP Multihop). -- With two or more PoPs/EntryPoints, ECMP is automatically enabled. MED and/or AS-PATH must be tuned to have path selection. -- Each DC/EndPoint supports up to 4 BGP peers. -- Up to 100 prefixes can be announced per BGP session. -- For each DC/EndPoint you must establish a BGP session with ‘A’ device and ‘B’ device. -- By default, BFD is activated on all BGP sessions. This protocol is higly recommended on the DC side as well to have a faster convergence. - -For example, IP network 'B' will be announced to the OVHcloud router through BGP session. - -![L3 BGP vRack](images/occ-l3-bgpvrack.png){.thumbnail} - -At a more global level, BGP topology will look like this: - -![L3 BGP Global Topology](images/occ-l3-bgpglobal.png){.thumbnail} - -#### BGP path selection - -By default, all available paths are enabled using ECMP, with up to 4 paths supported. To have an active/passive topology with two PoPs/EntryPoints, you can use AS path prepending or MED. - -If AS path prepending is configured on the customer's devices in PoP2, the topology will look like this: - -![L3 BGP as-prepend](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Note: AS path prepending is not configurable on OVHcloud devices. - -Using MED is an alternative to achieve the same topology. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.en-ie.md b/pages/network/ovhcloud_connect/occ-layer3/guide.en-ie.md deleted file mode 100644 index 9ea3b7e1cab..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.en-ie.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Layer 3 mode -excerpt: 'Details about using Layer 3 (L3) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 3 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 3 implementation - -OVHcloud Connect configured in Layer 3 differs from Layer 2 as you have to configure the L3 domain on each PoP/EntryPoint and DC/EndPoint. - -![L3 Implementation](images/occ-l3-implementation.png){.thumbnail} - -A Layer 3 domain is composed of: - -- A subnet -- A BGP ASN - -The L3 domain is an IP routing instance provided by OVHcloud. Traffic is forwarded between PoP/EntryPoint and DC/Endpoint, not between two PoPs/EntryPoints. There is no need for internal IP addressing between PoP/EntryPoint and DC/EndPoint. In the data centre, the routing instance inside the L3 domain is composed of two devices, labelled ‘A’ and ‘B’. - -Based on this principle it is possible to manage several OVHcloud Connect services. - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -As a result, L3 makes it compatible with a multi-DC configuration. - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -The two examples above illustrate the configuration of two OVHcloud Connect services, as one OVHcloud Connect equals one PoP/EntryPoint. - -**Rules:** - -- You can have as many OVHcloud Connect L3 as you want in the same vRack. -- You can associate several PoPs/EntryPoints with one DC/EndPoint. -- You can associate several DCs/EndPoints with one PoP/EntryPoint. -- You cannot associate two PoPs/EntryPoints (i.e. you cannot forward traffic between them). -- One L3 domain can only be associated with one DC/EndPoint. -- One L3 domain (i.e. subnet) cannot be stretched between two DCs or two PoPs. -- An OVHcloud Connect L2 can be mixed with several OVHcloud Connect L3 in the same vRack. - -![L3 Rules](images/occ-l3-rules.gif){.thumbnail} - -The following schema shows the mix of L2 and L3. They can end in the same OVHcloud data centre or not. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Connection mode details - -![L3 Architecture](images/occ-l3-architecture.png){.thumbnail} - -On such an architecture, two L3 domains are needed: PoP/EntryPoint and DC/EndPoint. - -"IP Net A" is part of the L3 Domain in the DC. The following rules apply: - -- IP addressing plan (subnet and netmask) with a minimum netmask of /29. -- The first IP address is reserved for the virtual gateway (if running VRRP). -- The two following IP addresses are reserved for the OVHcloud routing instance. -- All other IP addresses are available to the customer. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud virtual router address (if enabled) | -| A.B.C.2 | OVHcloud router A | -| A.B.C.3 | OVHcloud router B | - -"IP Net B" is part of the L3 Domain in the PoP. The following rules apply: - -- Supported netmask: /30 (CIDR notation). -- The first IP address is reserved for the OVHcloud routing instance. -- The second IP address is used for customer equipment. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud router | -| A.B.C.2 | Customer router | -| A.B.C.3 | Subnet broadcast | - -#### VRRP configuration in the DC/EndPoint - -VRRP allows router redundancy on OVHcloud devices. - -- Each DC/EndPoint supports only one VRRP instance. -- The VRRP VRID value is provided by OVHcloud. -- By default, VRRP is master on ‘A’ device. -- Static routes can be configured. - -#### BGP configuration - -BGP is mandatory in a PoP/EntryPoint and optional in a DC/EndPoint. Enabling BGP in a DC/EndPoint disables VRRP configuration. - -- Each PoP/EntryPoint and DC/EndPoint needs an AS. This AS must be independent from the customer BGP AS to form an eBGP relation. The recommended value is in the range 64512-65534. -- Each PoP/EntryPoint supports only one BGP session (no eBGP Multihop). -- With two or more PoPs/EntryPoints, ECMP is automatically enabled. MED and/or AS-PATH must be tuned to have path selection. -- Each DC/EndPoint supports up to 4 BGP peers. -- Up to 100 prefixes can be announced per BGP session. -- For each DC/EndPoint you must establish a BGP session with ‘A’ device and ‘B’ device. -- By default, BFD is activated on all BGP sessions. This protocol is higly recommended on the DC side as well to have a faster convergence. - -For example, IP network 'B' will be announced to the OVHcloud router through BGP session. - -![L3 BGP vRack](images/occ-l3-bgpvrack.png){.thumbnail} - -At a more global level, BGP topology will look like this: - -![L3 BGP Global Topology](images/occ-l3-bgpglobal.png){.thumbnail} - -#### BGP path selection - -By default, all available paths are enabled using ECMP, with up to 4 paths supported. To have an active/passive topology with two PoPs/EntryPoints, you can use AS path prepending or MED. - -If AS path prepending is configured on the customer's devices in PoP2, the topology will look like this: - -![L3 BGP as-prepend](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Note: AS path prepending is not configurable on OVHcloud devices. - -Using MED is an alternative to achieve the same topology. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.en-sg.md b/pages/network/ovhcloud_connect/occ-layer3/guide.en-sg.md deleted file mode 100644 index 9ea3b7e1cab..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.en-sg.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Layer 3 mode -excerpt: 'Details about using Layer 3 (L3) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 3 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 3 implementation - -OVHcloud Connect configured in Layer 3 differs from Layer 2 as you have to configure the L3 domain on each PoP/EntryPoint and DC/EndPoint. - -![L3 Implementation](images/occ-l3-implementation.png){.thumbnail} - -A Layer 3 domain is composed of: - -- A subnet -- A BGP ASN - -The L3 domain is an IP routing instance provided by OVHcloud. Traffic is forwarded between PoP/EntryPoint and DC/Endpoint, not between two PoPs/EntryPoints. There is no need for internal IP addressing between PoP/EntryPoint and DC/EndPoint. In the data centre, the routing instance inside the L3 domain is composed of two devices, labelled ‘A’ and ‘B’. - -Based on this principle it is possible to manage several OVHcloud Connect services. - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -As a result, L3 makes it compatible with a multi-DC configuration. - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -The two examples above illustrate the configuration of two OVHcloud Connect services, as one OVHcloud Connect equals one PoP/EntryPoint. - -**Rules:** - -- You can have as many OVHcloud Connect L3 as you want in the same vRack. -- You can associate several PoPs/EntryPoints with one DC/EndPoint. -- You can associate several DCs/EndPoints with one PoP/EntryPoint. -- You cannot associate two PoPs/EntryPoints (i.e. you cannot forward traffic between them). -- One L3 domain can only be associated with one DC/EndPoint. -- One L3 domain (i.e. subnet) cannot be stretched between two DCs or two PoPs. -- An OVHcloud Connect L2 can be mixed with several OVHcloud Connect L3 in the same vRack. - -![L3 Rules](images/occ-l3-rules.gif){.thumbnail} - -The following schema shows the mix of L2 and L3. They can end in the same OVHcloud data centre or not. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Connection mode details - -![L3 Architecture](images/occ-l3-architecture.png){.thumbnail} - -On such an architecture, two L3 domains are needed: PoP/EntryPoint and DC/EndPoint. - -"IP Net A" is part of the L3 Domain in the DC. The following rules apply: - -- IP addressing plan (subnet and netmask) with a minimum netmask of /29. -- The first IP address is reserved for the virtual gateway (if running VRRP). -- The two following IP addresses are reserved for the OVHcloud routing instance. -- All other IP addresses are available to the customer. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud virtual router address (if enabled) | -| A.B.C.2 | OVHcloud router A | -| A.B.C.3 | OVHcloud router B | - -"IP Net B" is part of the L3 Domain in the PoP. The following rules apply: - -- Supported netmask: /30 (CIDR notation). -- The first IP address is reserved for the OVHcloud routing instance. -- The second IP address is used for customer equipment. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud router | -| A.B.C.2 | Customer router | -| A.B.C.3 | Subnet broadcast | - -#### VRRP configuration in the DC/EndPoint - -VRRP allows router redundancy on OVHcloud devices. - -- Each DC/EndPoint supports only one VRRP instance. -- The VRRP VRID value is provided by OVHcloud. -- By default, VRRP is master on ‘A’ device. -- Static routes can be configured. - -#### BGP configuration - -BGP is mandatory in a PoP/EntryPoint and optional in a DC/EndPoint. Enabling BGP in a DC/EndPoint disables VRRP configuration. - -- Each PoP/EntryPoint and DC/EndPoint needs an AS. This AS must be independent from the customer BGP AS to form an eBGP relation. The recommended value is in the range 64512-65534. -- Each PoP/EntryPoint supports only one BGP session (no eBGP Multihop). -- With two or more PoPs/EntryPoints, ECMP is automatically enabled. MED and/or AS-PATH must be tuned to have path selection. -- Each DC/EndPoint supports up to 4 BGP peers. -- Up to 100 prefixes can be announced per BGP session. -- For each DC/EndPoint you must establish a BGP session with ‘A’ device and ‘B’ device. -- By default, BFD is activated on all BGP sessions. This protocol is higly recommended on the DC side as well to have a faster convergence. - -For example, IP network 'B' will be announced to the OVHcloud router through BGP session. - -![L3 BGP vRack](images/occ-l3-bgpvrack.png){.thumbnail} - -At a more global level, BGP topology will look like this: - -![L3 BGP Global Topology](images/occ-l3-bgpglobal.png){.thumbnail} - -#### BGP path selection - -By default, all available paths are enabled using ECMP, with up to 4 paths supported. To have an active/passive topology with two PoPs/EntryPoints, you can use AS path prepending or MED. - -If AS path prepending is configured on the customer's devices in PoP2, the topology will look like this: - -![L3 BGP as-prepend](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Note: AS path prepending is not configurable on OVHcloud devices. - -Using MED is an alternative to achieve the same topology. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.en-us.md b/pages/network/ovhcloud_connect/occ-layer3/guide.en-us.md deleted file mode 100644 index 9ea3b7e1cab..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.en-us.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Layer 3 mode -excerpt: 'Details about using Layer 3 (L3) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 3 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 3 implementation - -OVHcloud Connect configured in Layer 3 differs from Layer 2 as you have to configure the L3 domain on each PoP/EntryPoint and DC/EndPoint. - -![L3 Implementation](images/occ-l3-implementation.png){.thumbnail} - -A Layer 3 domain is composed of: - -- A subnet -- A BGP ASN - -The L3 domain is an IP routing instance provided by OVHcloud. Traffic is forwarded between PoP/EntryPoint and DC/Endpoint, not between two PoPs/EntryPoints. There is no need for internal IP addressing between PoP/EntryPoint and DC/EndPoint. In the data centre, the routing instance inside the L3 domain is composed of two devices, labelled ‘A’ and ‘B’. - -Based on this principle it is possible to manage several OVHcloud Connect services. - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -As a result, L3 makes it compatible with a multi-DC configuration. - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -The two examples above illustrate the configuration of two OVHcloud Connect services, as one OVHcloud Connect equals one PoP/EntryPoint. - -**Rules:** - -- You can have as many OVHcloud Connect L3 as you want in the same vRack. -- You can associate several PoPs/EntryPoints with one DC/EndPoint. -- You can associate several DCs/EndPoints with one PoP/EntryPoint. -- You cannot associate two PoPs/EntryPoints (i.e. you cannot forward traffic between them). -- One L3 domain can only be associated with one DC/EndPoint. -- One L3 domain (i.e. subnet) cannot be stretched between two DCs or two PoPs. -- An OVHcloud Connect L2 can be mixed with several OVHcloud Connect L3 in the same vRack. - -![L3 Rules](images/occ-l3-rules.gif){.thumbnail} - -The following schema shows the mix of L2 and L3. They can end in the same OVHcloud data centre or not. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Connection mode details - -![L3 Architecture](images/occ-l3-architecture.png){.thumbnail} - -On such an architecture, two L3 domains are needed: PoP/EntryPoint and DC/EndPoint. - -"IP Net A" is part of the L3 Domain in the DC. The following rules apply: - -- IP addressing plan (subnet and netmask) with a minimum netmask of /29. -- The first IP address is reserved for the virtual gateway (if running VRRP). -- The two following IP addresses are reserved for the OVHcloud routing instance. -- All other IP addresses are available to the customer. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud virtual router address (if enabled) | -| A.B.C.2 | OVHcloud router A | -| A.B.C.3 | OVHcloud router B | - -"IP Net B" is part of the L3 Domain in the PoP. The following rules apply: - -- Supported netmask: /30 (CIDR notation). -- The first IP address is reserved for the OVHcloud routing instance. -- The second IP address is used for customer equipment. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud router | -| A.B.C.2 | Customer router | -| A.B.C.3 | Subnet broadcast | - -#### VRRP configuration in the DC/EndPoint - -VRRP allows router redundancy on OVHcloud devices. - -- Each DC/EndPoint supports only one VRRP instance. -- The VRRP VRID value is provided by OVHcloud. -- By default, VRRP is master on ‘A’ device. -- Static routes can be configured. - -#### BGP configuration - -BGP is mandatory in a PoP/EntryPoint and optional in a DC/EndPoint. Enabling BGP in a DC/EndPoint disables VRRP configuration. - -- Each PoP/EntryPoint and DC/EndPoint needs an AS. This AS must be independent from the customer BGP AS to form an eBGP relation. The recommended value is in the range 64512-65534. -- Each PoP/EntryPoint supports only one BGP session (no eBGP Multihop). -- With two or more PoPs/EntryPoints, ECMP is automatically enabled. MED and/or AS-PATH must be tuned to have path selection. -- Each DC/EndPoint supports up to 4 BGP peers. -- Up to 100 prefixes can be announced per BGP session. -- For each DC/EndPoint you must establish a BGP session with ‘A’ device and ‘B’ device. -- By default, BFD is activated on all BGP sessions. This protocol is higly recommended on the DC side as well to have a faster convergence. - -For example, IP network 'B' will be announced to the OVHcloud router through BGP session. - -![L3 BGP vRack](images/occ-l3-bgpvrack.png){.thumbnail} - -At a more global level, BGP topology will look like this: - -![L3 BGP Global Topology](images/occ-l3-bgpglobal.png){.thumbnail} - -#### BGP path selection - -By default, all available paths are enabled using ECMP, with up to 4 paths supported. To have an active/passive topology with two PoPs/EntryPoints, you can use AS path prepending or MED. - -If AS path prepending is configured on the customer's devices in PoP2, the topology will look like this: - -![L3 BGP as-prepend](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Note: AS path prepending is not configurable on OVHcloud devices. - -Using MED is an alternative to achieve the same topology. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.es-es.md b/pages/network/ovhcloud_connect/occ-layer3/guide.es-es.md deleted file mode 100644 index 9ea3b7e1cab..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.es-es.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Layer 3 mode -excerpt: 'Details about using Layer 3 (L3) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 3 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 3 implementation - -OVHcloud Connect configured in Layer 3 differs from Layer 2 as you have to configure the L3 domain on each PoP/EntryPoint and DC/EndPoint. - -![L3 Implementation](images/occ-l3-implementation.png){.thumbnail} - -A Layer 3 domain is composed of: - -- A subnet -- A BGP ASN - -The L3 domain is an IP routing instance provided by OVHcloud. Traffic is forwarded between PoP/EntryPoint and DC/Endpoint, not between two PoPs/EntryPoints. There is no need for internal IP addressing between PoP/EntryPoint and DC/EndPoint. In the data centre, the routing instance inside the L3 domain is composed of two devices, labelled ‘A’ and ‘B’. - -Based on this principle it is possible to manage several OVHcloud Connect services. - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -As a result, L3 makes it compatible with a multi-DC configuration. - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -The two examples above illustrate the configuration of two OVHcloud Connect services, as one OVHcloud Connect equals one PoP/EntryPoint. - -**Rules:** - -- You can have as many OVHcloud Connect L3 as you want in the same vRack. -- You can associate several PoPs/EntryPoints with one DC/EndPoint. -- You can associate several DCs/EndPoints with one PoP/EntryPoint. -- You cannot associate two PoPs/EntryPoints (i.e. you cannot forward traffic between them). -- One L3 domain can only be associated with one DC/EndPoint. -- One L3 domain (i.e. subnet) cannot be stretched between two DCs or two PoPs. -- An OVHcloud Connect L2 can be mixed with several OVHcloud Connect L3 in the same vRack. - -![L3 Rules](images/occ-l3-rules.gif){.thumbnail} - -The following schema shows the mix of L2 and L3. They can end in the same OVHcloud data centre or not. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Connection mode details - -![L3 Architecture](images/occ-l3-architecture.png){.thumbnail} - -On such an architecture, two L3 domains are needed: PoP/EntryPoint and DC/EndPoint. - -"IP Net A" is part of the L3 Domain in the DC. The following rules apply: - -- IP addressing plan (subnet and netmask) with a minimum netmask of /29. -- The first IP address is reserved for the virtual gateway (if running VRRP). -- The two following IP addresses are reserved for the OVHcloud routing instance. -- All other IP addresses are available to the customer. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud virtual router address (if enabled) | -| A.B.C.2 | OVHcloud router A | -| A.B.C.3 | OVHcloud router B | - -"IP Net B" is part of the L3 Domain in the PoP. The following rules apply: - -- Supported netmask: /30 (CIDR notation). -- The first IP address is reserved for the OVHcloud routing instance. -- The second IP address is used for customer equipment. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud router | -| A.B.C.2 | Customer router | -| A.B.C.3 | Subnet broadcast | - -#### VRRP configuration in the DC/EndPoint - -VRRP allows router redundancy on OVHcloud devices. - -- Each DC/EndPoint supports only one VRRP instance. -- The VRRP VRID value is provided by OVHcloud. -- By default, VRRP is master on ‘A’ device. -- Static routes can be configured. - -#### BGP configuration - -BGP is mandatory in a PoP/EntryPoint and optional in a DC/EndPoint. Enabling BGP in a DC/EndPoint disables VRRP configuration. - -- Each PoP/EntryPoint and DC/EndPoint needs an AS. This AS must be independent from the customer BGP AS to form an eBGP relation. The recommended value is in the range 64512-65534. -- Each PoP/EntryPoint supports only one BGP session (no eBGP Multihop). -- With two or more PoPs/EntryPoints, ECMP is automatically enabled. MED and/or AS-PATH must be tuned to have path selection. -- Each DC/EndPoint supports up to 4 BGP peers. -- Up to 100 prefixes can be announced per BGP session. -- For each DC/EndPoint you must establish a BGP session with ‘A’ device and ‘B’ device. -- By default, BFD is activated on all BGP sessions. This protocol is higly recommended on the DC side as well to have a faster convergence. - -For example, IP network 'B' will be announced to the OVHcloud router through BGP session. - -![L3 BGP vRack](images/occ-l3-bgpvrack.png){.thumbnail} - -At a more global level, BGP topology will look like this: - -![L3 BGP Global Topology](images/occ-l3-bgpglobal.png){.thumbnail} - -#### BGP path selection - -By default, all available paths are enabled using ECMP, with up to 4 paths supported. To have an active/passive topology with two PoPs/EntryPoints, you can use AS path prepending or MED. - -If AS path prepending is configured on the customer's devices in PoP2, the topology will look like this: - -![L3 BGP as-prepend](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Note: AS path prepending is not configurable on OVHcloud devices. - -Using MED is an alternative to achieve the same topology. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.es-us.md b/pages/network/ovhcloud_connect/occ-layer3/guide.es-us.md deleted file mode 100644 index 9ea3b7e1cab..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.es-us.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Layer 3 mode -excerpt: 'Details about using Layer 3 (L3) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 3 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 3 implementation - -OVHcloud Connect configured in Layer 3 differs from Layer 2 as you have to configure the L3 domain on each PoP/EntryPoint and DC/EndPoint. - -![L3 Implementation](images/occ-l3-implementation.png){.thumbnail} - -A Layer 3 domain is composed of: - -- A subnet -- A BGP ASN - -The L3 domain is an IP routing instance provided by OVHcloud. Traffic is forwarded between PoP/EntryPoint and DC/Endpoint, not between two PoPs/EntryPoints. There is no need for internal IP addressing between PoP/EntryPoint and DC/EndPoint. In the data centre, the routing instance inside the L3 domain is composed of two devices, labelled ‘A’ and ‘B’. - -Based on this principle it is possible to manage several OVHcloud Connect services. - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -As a result, L3 makes it compatible with a multi-DC configuration. - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -The two examples above illustrate the configuration of two OVHcloud Connect services, as one OVHcloud Connect equals one PoP/EntryPoint. - -**Rules:** - -- You can have as many OVHcloud Connect L3 as you want in the same vRack. -- You can associate several PoPs/EntryPoints with one DC/EndPoint. -- You can associate several DCs/EndPoints with one PoP/EntryPoint. -- You cannot associate two PoPs/EntryPoints (i.e. you cannot forward traffic between them). -- One L3 domain can only be associated with one DC/EndPoint. -- One L3 domain (i.e. subnet) cannot be stretched between two DCs or two PoPs. -- An OVHcloud Connect L2 can be mixed with several OVHcloud Connect L3 in the same vRack. - -![L3 Rules](images/occ-l3-rules.gif){.thumbnail} - -The following schema shows the mix of L2 and L3. They can end in the same OVHcloud data centre or not. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Connection mode details - -![L3 Architecture](images/occ-l3-architecture.png){.thumbnail} - -On such an architecture, two L3 domains are needed: PoP/EntryPoint and DC/EndPoint. - -"IP Net A" is part of the L3 Domain in the DC. The following rules apply: - -- IP addressing plan (subnet and netmask) with a minimum netmask of /29. -- The first IP address is reserved for the virtual gateway (if running VRRP). -- The two following IP addresses are reserved for the OVHcloud routing instance. -- All other IP addresses are available to the customer. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud virtual router address (if enabled) | -| A.B.C.2 | OVHcloud router A | -| A.B.C.3 | OVHcloud router B | - -"IP Net B" is part of the L3 Domain in the PoP. The following rules apply: - -- Supported netmask: /30 (CIDR notation). -- The first IP address is reserved for the OVHcloud routing instance. -- The second IP address is used for customer equipment. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud router | -| A.B.C.2 | Customer router | -| A.B.C.3 | Subnet broadcast | - -#### VRRP configuration in the DC/EndPoint - -VRRP allows router redundancy on OVHcloud devices. - -- Each DC/EndPoint supports only one VRRP instance. -- The VRRP VRID value is provided by OVHcloud. -- By default, VRRP is master on ‘A’ device. -- Static routes can be configured. - -#### BGP configuration - -BGP is mandatory in a PoP/EntryPoint and optional in a DC/EndPoint. Enabling BGP in a DC/EndPoint disables VRRP configuration. - -- Each PoP/EntryPoint and DC/EndPoint needs an AS. This AS must be independent from the customer BGP AS to form an eBGP relation. The recommended value is in the range 64512-65534. -- Each PoP/EntryPoint supports only one BGP session (no eBGP Multihop). -- With two or more PoPs/EntryPoints, ECMP is automatically enabled. MED and/or AS-PATH must be tuned to have path selection. -- Each DC/EndPoint supports up to 4 BGP peers. -- Up to 100 prefixes can be announced per BGP session. -- For each DC/EndPoint you must establish a BGP session with ‘A’ device and ‘B’ device. -- By default, BFD is activated on all BGP sessions. This protocol is higly recommended on the DC side as well to have a faster convergence. - -For example, IP network 'B' will be announced to the OVHcloud router through BGP session. - -![L3 BGP vRack](images/occ-l3-bgpvrack.png){.thumbnail} - -At a more global level, BGP topology will look like this: - -![L3 BGP Global Topology](images/occ-l3-bgpglobal.png){.thumbnail} - -#### BGP path selection - -By default, all available paths are enabled using ECMP, with up to 4 paths supported. To have an active/passive topology with two PoPs/EntryPoints, you can use AS path prepending or MED. - -If AS path prepending is configured on the customer's devices in PoP2, the topology will look like this: - -![L3 BGP as-prepend](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Note: AS path prepending is not configurable on OVHcloud devices. - -Using MED is an alternative to achieve the same topology. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.fr-ca.md b/pages/network/ovhcloud_connect/occ-layer3/guide.fr-ca.md deleted file mode 100644 index 058a0e6132b..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.fr-ca.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -title: Mode Layer 3 (L3) -excerpt: Détails sur le mode Layer 3 (L3) pour OVHcloud Connect -updated: 2020-09-14 ---- - -## Objectif - -**Découvrez les détails sur l'implémentation et le mode de connexion du mode Layer 3 (L3) pour l'offre OVHcloud Connect.** - -## En pratique - -### Implémentation du mode L3 - -La configuration de OVHcloud Connect configuré en mode L3 diffère du mode L2 car vous devez configurer le domaine L3 sur chaque DC/EndPoint et PoP/EntryPoint. - -![Implémentation L3](images/occ-l3-implementation.png){.thumbnail} - -Un domaine L3 est composé de : - -* Un sous-réseau -* Un ASN BGP - -Le domaine L3 est une instance de routage IP fournie par OVHcloud. Le trafic est transféré entre un POP/EntryPoint et un DC/Endpoint, et non entre deux POP/EntryPoint. L'adressage IP interne entre les PoP/EntryPoint et DC/EndPoint n'est pas nécessaire. Dans le Datacentre, l'instance de routage à l'intérieur du domaine L3 est composée de deux équipements, appelés « A » et « B ». - -De ce principe, il est désormais possible de gérer plusieurs services OVHcloud Connect : - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -De ce fait, le L3 permet d'être compatibles avec du multi-DC : - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -Les deux exemples ci-dessus illustrent la configuration de deux services OVHcloud Connect, car chaque service OVHcloud équivaut à un PoP/EntryPoint. - -Règles : - -* Vous pouvez avoir autant de services OVHcloud Connect L3 que vous le souhaitez dans le même vRack. -* Vous pouvez associer plusieurs EntryPoint/PoP à un EndPoint/DC. -* Vous pouvez associer plusieurs EndPoint/DC à un seul EntryPoint/PoP. -* Vous ne pouvez pas associer deux EntryPoint/POP entre eux (c'est-à-dire que vous ne pouvez pas transférer le trafic entre eux). -* Un domaine L3 ne peut être associé qu'à un seul EndPoint/DC. -* Un domaine L3 (c'est-à-dire un sous-réseau) ne peut pas être étiré entre deux DC ou deux PoP. -* Un OVHcloud Connect L2 peut être mélangé avec plusieurs OVHcloud Connect L3 dans le même vRack. - -![Règles L3](images/occ-l3-rules.gif){.thumbnail} - -Le schéma ci-dessous montre la combinaison de L2 et L3. Ils peuvent se terminer dans le même DC OVHcloud ou non. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Détails du mode de connexion - -Sur une architecture telle que décrite dans le schéma ci-dessous, deux domaines L3 sont nécessaires : PoP/EntryPoint et DC/EndPoint. - -![Architecture L3](images/occ-l3-architecture.png){.thumbnail} - -« IP Net A » fait partie du domaine L3 dans le DC. Voici alors les informations requises : - -* Plan d'adressage IP (sous-réseau et masque de sous-réseau) avec une valeur minimale de masque de sous-réseau de /29. -* La première adresse IP est réservée à la passerelle virtuelle (si le protocole VRRP est utilisé). -* Les deux adresses IP suivantes sont réservées à l'instance de routage OVHcloud -* Toutes les autres adresses IP sont disponibles pour le client. - -| Adresse IP | Rôle | -|:-----:|:-----:| -| A.B.C.0 | Sous-réseau | -| A.B.C.1 | Adresse du routeur virtuel OVHcloud (si activé) | -| A.B.C.2 | Routeur OVHcloud A | -| A.B.C.3 | Routeur OVHcloud B | - -« IP Net B » fait partie du domaine L3 dans le POP. Voici alors les informations requises : - -* Masque de sous-réseau pris en charge : /30 (notation CIDR) -* Première adresse IP pour l'instance de routage OVHcloud. -* Deuxième adresse IP pour l'équipement client. - -| Adresse IP | Rôle | -|:-----:|:-----:| -| A.B.C.0 | Sous-réseau | -| A.B.C.1 | Routeur OVHcloud | -| A.B.C.2 | Routeur client | -| A.B.C.3 | Broadcast de sous-réseau | - -#### Configuration VRRP dans le DC/EndPoint - -Le protocole VRRP permet la redondance de routeurs sur les services OVHcloud. - -* Chaque EndPoint/DC ne prend en charge qu'une seule instance VRRP. -* La valeur VRID VRRP est fournie par OVHcloud. -* Par défaut, le VRRP est master sur l'équipement « A ». -* Des routes statiques peuvent être configurées. - -#### Configuration BGP - -Le protocole BGP est obligatoire dans le POP/EntryPoint et facultatif dans le DC/EndPoint. L'activation du protocole BGP dans le DC/EndPoint désactive la configuration VRRP. - -* Chaque EntryPoint/POP et EndPoint/DC nécessite un AS. Cet AS doit être indépendant de l'AS BGP du client pour former une relation eBGP. -La valeur recommandée est dans la plage 64512-65534. -* Chaque EntryPoint/POP ne prend en charge qu'une seule session BGP (pas de Multihop eBGP) -* Avec plusieurs EntryPoint/POP, ECMP est automatiquement activé. MED et/ou AS-PATH doivent être réglés pour que le chemin soit sélectionné. -* Chaque EndPoint/DC prend en charge jusqu'à 4 peers BGP. -* Jusqu'à 100 préfixes peuvent être annoncés par session BGP. -* Pour chaque EndPoint/DC, vous devez établir une session BGP avec un équipement « A » et un équipement « B ». -* Par défaut, le protocole BFD est activé sur toutes les sessions BGP. Ce protocole est fortement recommandé du côté DC pour avoir une convergence plus rapide. - -Par exemple, le réseau IP « B » sera annoncé au routeur OVHcloud via une session BGP. - -![Rack BGP L3](images/occ-l3-bgpvrack.png){.thumbnail} - -À un niveau plus global, la topologie BGP ressemblera à ceci : - -![Topologie globale BGP L3](images/occ-l3-bgpglobal.png){.thumbnail} - -#### Sélection du chemin BGP - -Par défaut, tous les chemins disponibles sont activés à l'aide d'ECMP, jusqu'à 4 chemins peuvent être pris en charge. Ainsi, pour avoir une topologie active/passive avec deux POP/EntryPoint, nous pouvons utiliser as-path via prepend ou MED. - -Si as-prepend est configuré sur les périphériques du client sur le POP2, la topologie ressemblera à : - -![BGP L3 as-prepend ou med](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Remarque : as-prepend n'est pas configurable sur les services OVHcloud. - -L'utilisation de MED est une autre alternative pour obtenir la même topologie. - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.fr-fr.md b/pages/network/ovhcloud_connect/occ-layer3/guide.fr-fr.md deleted file mode 100644 index 058a0e6132b..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.fr-fr.md +++ /dev/null @@ -1,131 +0,0 @@ ---- -title: Mode Layer 3 (L3) -excerpt: Détails sur le mode Layer 3 (L3) pour OVHcloud Connect -updated: 2020-09-14 ---- - -## Objectif - -**Découvrez les détails sur l'implémentation et le mode de connexion du mode Layer 3 (L3) pour l'offre OVHcloud Connect.** - -## En pratique - -### Implémentation du mode L3 - -La configuration de OVHcloud Connect configuré en mode L3 diffère du mode L2 car vous devez configurer le domaine L3 sur chaque DC/EndPoint et PoP/EntryPoint. - -![Implémentation L3](images/occ-l3-implementation.png){.thumbnail} - -Un domaine L3 est composé de : - -* Un sous-réseau -* Un ASN BGP - -Le domaine L3 est une instance de routage IP fournie par OVHcloud. Le trafic est transféré entre un POP/EntryPoint et un DC/Endpoint, et non entre deux POP/EntryPoint. L'adressage IP interne entre les PoP/EntryPoint et DC/EndPoint n'est pas nécessaire. Dans le Datacentre, l'instance de routage à l'intérieur du domaine L3 est composée de deux équipements, appelés « A » et « B ». - -De ce principe, il est désormais possible de gérer plusieurs services OVHcloud Connect : - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -De ce fait, le L3 permet d'être compatibles avec du multi-DC : - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -Les deux exemples ci-dessus illustrent la configuration de deux services OVHcloud Connect, car chaque service OVHcloud équivaut à un PoP/EntryPoint. - -Règles : - -* Vous pouvez avoir autant de services OVHcloud Connect L3 que vous le souhaitez dans le même vRack. -* Vous pouvez associer plusieurs EntryPoint/PoP à un EndPoint/DC. -* Vous pouvez associer plusieurs EndPoint/DC à un seul EntryPoint/PoP. -* Vous ne pouvez pas associer deux EntryPoint/POP entre eux (c'est-à-dire que vous ne pouvez pas transférer le trafic entre eux). -* Un domaine L3 ne peut être associé qu'à un seul EndPoint/DC. -* Un domaine L3 (c'est-à-dire un sous-réseau) ne peut pas être étiré entre deux DC ou deux PoP. -* Un OVHcloud Connect L2 peut être mélangé avec plusieurs OVHcloud Connect L3 dans le même vRack. - -![Règles L3](images/occ-l3-rules.gif){.thumbnail} - -Le schéma ci-dessous montre la combinaison de L2 et L3. Ils peuvent se terminer dans le même DC OVHcloud ou non. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Détails du mode de connexion - -Sur une architecture telle que décrite dans le schéma ci-dessous, deux domaines L3 sont nécessaires : PoP/EntryPoint et DC/EndPoint. - -![Architecture L3](images/occ-l3-architecture.png){.thumbnail} - -« IP Net A » fait partie du domaine L3 dans le DC. Voici alors les informations requises : - -* Plan d'adressage IP (sous-réseau et masque de sous-réseau) avec une valeur minimale de masque de sous-réseau de /29. -* La première adresse IP est réservée à la passerelle virtuelle (si le protocole VRRP est utilisé). -* Les deux adresses IP suivantes sont réservées à l'instance de routage OVHcloud -* Toutes les autres adresses IP sont disponibles pour le client. - -| Adresse IP | Rôle | -|:-----:|:-----:| -| A.B.C.0 | Sous-réseau | -| A.B.C.1 | Adresse du routeur virtuel OVHcloud (si activé) | -| A.B.C.2 | Routeur OVHcloud A | -| A.B.C.3 | Routeur OVHcloud B | - -« IP Net B » fait partie du domaine L3 dans le POP. Voici alors les informations requises : - -* Masque de sous-réseau pris en charge : /30 (notation CIDR) -* Première adresse IP pour l'instance de routage OVHcloud. -* Deuxième adresse IP pour l'équipement client. - -| Adresse IP | Rôle | -|:-----:|:-----:| -| A.B.C.0 | Sous-réseau | -| A.B.C.1 | Routeur OVHcloud | -| A.B.C.2 | Routeur client | -| A.B.C.3 | Broadcast de sous-réseau | - -#### Configuration VRRP dans le DC/EndPoint - -Le protocole VRRP permet la redondance de routeurs sur les services OVHcloud. - -* Chaque EndPoint/DC ne prend en charge qu'une seule instance VRRP. -* La valeur VRID VRRP est fournie par OVHcloud. -* Par défaut, le VRRP est master sur l'équipement « A ». -* Des routes statiques peuvent être configurées. - -#### Configuration BGP - -Le protocole BGP est obligatoire dans le POP/EntryPoint et facultatif dans le DC/EndPoint. L'activation du protocole BGP dans le DC/EndPoint désactive la configuration VRRP. - -* Chaque EntryPoint/POP et EndPoint/DC nécessite un AS. Cet AS doit être indépendant de l'AS BGP du client pour former une relation eBGP. -La valeur recommandée est dans la plage 64512-65534. -* Chaque EntryPoint/POP ne prend en charge qu'une seule session BGP (pas de Multihop eBGP) -* Avec plusieurs EntryPoint/POP, ECMP est automatiquement activé. MED et/ou AS-PATH doivent être réglés pour que le chemin soit sélectionné. -* Chaque EndPoint/DC prend en charge jusqu'à 4 peers BGP. -* Jusqu'à 100 préfixes peuvent être annoncés par session BGP. -* Pour chaque EndPoint/DC, vous devez établir une session BGP avec un équipement « A » et un équipement « B ». -* Par défaut, le protocole BFD est activé sur toutes les sessions BGP. Ce protocole est fortement recommandé du côté DC pour avoir une convergence plus rapide. - -Par exemple, le réseau IP « B » sera annoncé au routeur OVHcloud via une session BGP. - -![Rack BGP L3](images/occ-l3-bgpvrack.png){.thumbnail} - -À un niveau plus global, la topologie BGP ressemblera à ceci : - -![Topologie globale BGP L3](images/occ-l3-bgpglobal.png){.thumbnail} - -#### Sélection du chemin BGP - -Par défaut, tous les chemins disponibles sont activés à l'aide d'ECMP, jusqu'à 4 chemins peuvent être pris en charge. Ainsi, pour avoir une topologie active/passive avec deux POP/EntryPoint, nous pouvons utiliser as-path via prepend ou MED. - -Si as-prepend est configuré sur les périphériques du client sur le POP2, la topologie ressemblera à : - -![BGP L3 as-prepend ou med](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Remarque : as-prepend n'est pas configurable sur les services OVHcloud. - -L'utilisation de MED est une autre alternative pour obtenir la même topologie. - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.it-it.md b/pages/network/ovhcloud_connect/occ-layer3/guide.it-it.md deleted file mode 100644 index 9ea3b7e1cab..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.it-it.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Layer 3 mode -excerpt: 'Details about using Layer 3 (L3) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 3 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 3 implementation - -OVHcloud Connect configured in Layer 3 differs from Layer 2 as you have to configure the L3 domain on each PoP/EntryPoint and DC/EndPoint. - -![L3 Implementation](images/occ-l3-implementation.png){.thumbnail} - -A Layer 3 domain is composed of: - -- A subnet -- A BGP ASN - -The L3 domain is an IP routing instance provided by OVHcloud. Traffic is forwarded between PoP/EntryPoint and DC/Endpoint, not between two PoPs/EntryPoints. There is no need for internal IP addressing between PoP/EntryPoint and DC/EndPoint. In the data centre, the routing instance inside the L3 domain is composed of two devices, labelled ‘A’ and ‘B’. - -Based on this principle it is possible to manage several OVHcloud Connect services. - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -As a result, L3 makes it compatible with a multi-DC configuration. - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -The two examples above illustrate the configuration of two OVHcloud Connect services, as one OVHcloud Connect equals one PoP/EntryPoint. - -**Rules:** - -- You can have as many OVHcloud Connect L3 as you want in the same vRack. -- You can associate several PoPs/EntryPoints with one DC/EndPoint. -- You can associate several DCs/EndPoints with one PoP/EntryPoint. -- You cannot associate two PoPs/EntryPoints (i.e. you cannot forward traffic between them). -- One L3 domain can only be associated with one DC/EndPoint. -- One L3 domain (i.e. subnet) cannot be stretched between two DCs or two PoPs. -- An OVHcloud Connect L2 can be mixed with several OVHcloud Connect L3 in the same vRack. - -![L3 Rules](images/occ-l3-rules.gif){.thumbnail} - -The following schema shows the mix of L2 and L3. They can end in the same OVHcloud data centre or not. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Connection mode details - -![L3 Architecture](images/occ-l3-architecture.png){.thumbnail} - -On such an architecture, two L3 domains are needed: PoP/EntryPoint and DC/EndPoint. - -"IP Net A" is part of the L3 Domain in the DC. The following rules apply: - -- IP addressing plan (subnet and netmask) with a minimum netmask of /29. -- The first IP address is reserved for the virtual gateway (if running VRRP). -- The two following IP addresses are reserved for the OVHcloud routing instance. -- All other IP addresses are available to the customer. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud virtual router address (if enabled) | -| A.B.C.2 | OVHcloud router A | -| A.B.C.3 | OVHcloud router B | - -"IP Net B" is part of the L3 Domain in the PoP. The following rules apply: - -- Supported netmask: /30 (CIDR notation). -- The first IP address is reserved for the OVHcloud routing instance. -- The second IP address is used for customer equipment. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud router | -| A.B.C.2 | Customer router | -| A.B.C.3 | Subnet broadcast | - -#### VRRP configuration in the DC/EndPoint - -VRRP allows router redundancy on OVHcloud devices. - -- Each DC/EndPoint supports only one VRRP instance. -- The VRRP VRID value is provided by OVHcloud. -- By default, VRRP is master on ‘A’ device. -- Static routes can be configured. - -#### BGP configuration - -BGP is mandatory in a PoP/EntryPoint and optional in a DC/EndPoint. Enabling BGP in a DC/EndPoint disables VRRP configuration. - -- Each PoP/EntryPoint and DC/EndPoint needs an AS. This AS must be independent from the customer BGP AS to form an eBGP relation. The recommended value is in the range 64512-65534. -- Each PoP/EntryPoint supports only one BGP session (no eBGP Multihop). -- With two or more PoPs/EntryPoints, ECMP is automatically enabled. MED and/or AS-PATH must be tuned to have path selection. -- Each DC/EndPoint supports up to 4 BGP peers. -- Up to 100 prefixes can be announced per BGP session. -- For each DC/EndPoint you must establish a BGP session with ‘A’ device and ‘B’ device. -- By default, BFD is activated on all BGP sessions. This protocol is higly recommended on the DC side as well to have a faster convergence. - -For example, IP network 'B' will be announced to the OVHcloud router through BGP session. - -![L3 BGP vRack](images/occ-l3-bgpvrack.png){.thumbnail} - -At a more global level, BGP topology will look like this: - -![L3 BGP Global Topology](images/occ-l3-bgpglobal.png){.thumbnail} - -#### BGP path selection - -By default, all available paths are enabled using ECMP, with up to 4 paths supported. To have an active/passive topology with two PoPs/EntryPoints, you can use AS path prepending or MED. - -If AS path prepending is configured on the customer's devices in PoP2, the topology will look like this: - -![L3 BGP as-prepend](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Note: AS path prepending is not configurable on OVHcloud devices. - -Using MED is an alternative to achieve the same topology. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.pl-pl.md b/pages/network/ovhcloud_connect/occ-layer3/guide.pl-pl.md deleted file mode 100644 index 9ea3b7e1cab..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.pl-pl.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Layer 3 mode -excerpt: 'Details about using Layer 3 (L3) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 3 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 3 implementation - -OVHcloud Connect configured in Layer 3 differs from Layer 2 as you have to configure the L3 domain on each PoP/EntryPoint and DC/EndPoint. - -![L3 Implementation](images/occ-l3-implementation.png){.thumbnail} - -A Layer 3 domain is composed of: - -- A subnet -- A BGP ASN - -The L3 domain is an IP routing instance provided by OVHcloud. Traffic is forwarded between PoP/EntryPoint and DC/Endpoint, not between two PoPs/EntryPoints. There is no need for internal IP addressing between PoP/EntryPoint and DC/EndPoint. In the data centre, the routing instance inside the L3 domain is composed of two devices, labelled ‘A’ and ‘B’. - -Based on this principle it is possible to manage several OVHcloud Connect services. - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -As a result, L3 makes it compatible with a multi-DC configuration. - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -The two examples above illustrate the configuration of two OVHcloud Connect services, as one OVHcloud Connect equals one PoP/EntryPoint. - -**Rules:** - -- You can have as many OVHcloud Connect L3 as you want in the same vRack. -- You can associate several PoPs/EntryPoints with one DC/EndPoint. -- You can associate several DCs/EndPoints with one PoP/EntryPoint. -- You cannot associate two PoPs/EntryPoints (i.e. you cannot forward traffic between them). -- One L3 domain can only be associated with one DC/EndPoint. -- One L3 domain (i.e. subnet) cannot be stretched between two DCs or two PoPs. -- An OVHcloud Connect L2 can be mixed with several OVHcloud Connect L3 in the same vRack. - -![L3 Rules](images/occ-l3-rules.gif){.thumbnail} - -The following schema shows the mix of L2 and L3. They can end in the same OVHcloud data centre or not. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Connection mode details - -![L3 Architecture](images/occ-l3-architecture.png){.thumbnail} - -On such an architecture, two L3 domains are needed: PoP/EntryPoint and DC/EndPoint. - -"IP Net A" is part of the L3 Domain in the DC. The following rules apply: - -- IP addressing plan (subnet and netmask) with a minimum netmask of /29. -- The first IP address is reserved for the virtual gateway (if running VRRP). -- The two following IP addresses are reserved for the OVHcloud routing instance. -- All other IP addresses are available to the customer. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud virtual router address (if enabled) | -| A.B.C.2 | OVHcloud router A | -| A.B.C.3 | OVHcloud router B | - -"IP Net B" is part of the L3 Domain in the PoP. The following rules apply: - -- Supported netmask: /30 (CIDR notation). -- The first IP address is reserved for the OVHcloud routing instance. -- The second IP address is used for customer equipment. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud router | -| A.B.C.2 | Customer router | -| A.B.C.3 | Subnet broadcast | - -#### VRRP configuration in the DC/EndPoint - -VRRP allows router redundancy on OVHcloud devices. - -- Each DC/EndPoint supports only one VRRP instance. -- The VRRP VRID value is provided by OVHcloud. -- By default, VRRP is master on ‘A’ device. -- Static routes can be configured. - -#### BGP configuration - -BGP is mandatory in a PoP/EntryPoint and optional in a DC/EndPoint. Enabling BGP in a DC/EndPoint disables VRRP configuration. - -- Each PoP/EntryPoint and DC/EndPoint needs an AS. This AS must be independent from the customer BGP AS to form an eBGP relation. The recommended value is in the range 64512-65534. -- Each PoP/EntryPoint supports only one BGP session (no eBGP Multihop). -- With two or more PoPs/EntryPoints, ECMP is automatically enabled. MED and/or AS-PATH must be tuned to have path selection. -- Each DC/EndPoint supports up to 4 BGP peers. -- Up to 100 prefixes can be announced per BGP session. -- For each DC/EndPoint you must establish a BGP session with ‘A’ device and ‘B’ device. -- By default, BFD is activated on all BGP sessions. This protocol is higly recommended on the DC side as well to have a faster convergence. - -For example, IP network 'B' will be announced to the OVHcloud router through BGP session. - -![L3 BGP vRack](images/occ-l3-bgpvrack.png){.thumbnail} - -At a more global level, BGP topology will look like this: - -![L3 BGP Global Topology](images/occ-l3-bgpglobal.png){.thumbnail} - -#### BGP path selection - -By default, all available paths are enabled using ECMP, with up to 4 paths supported. To have an active/passive topology with two PoPs/EntryPoints, you can use AS path prepending or MED. - -If AS path prepending is configured on the customer's devices in PoP2, the topology will look like this: - -![L3 BGP as-prepend](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Note: AS path prepending is not configurable on OVHcloud devices. - -Using MED is an alternative to achieve the same topology. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer3/guide.pt-pt.md b/pages/network/ovhcloud_connect/occ-layer3/guide.pt-pt.md deleted file mode 100644 index 9ea3b7e1cab..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/guide.pt-pt.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Layer 3 mode -excerpt: 'Details about using Layer 3 (L3) with OVHcloud Connect' -updated: 2020-09-14 ---- - -## Objective - -**Learn more about Layer 3 implementation and connection for the OVHcloud Connect solution.** - -## Instructions - -### Layer 3 implementation - -OVHcloud Connect configured in Layer 3 differs from Layer 2 as you have to configure the L3 domain on each PoP/EntryPoint and DC/EndPoint. - -![L3 Implementation](images/occ-l3-implementation.png){.thumbnail} - -A Layer 3 domain is composed of: - -- A subnet -- A BGP ASN - -The L3 domain is an IP routing instance provided by OVHcloud. Traffic is forwarded between PoP/EntryPoint and DC/Endpoint, not between two PoPs/EntryPoints. There is no need for internal IP addressing between PoP/EntryPoint and DC/EndPoint. In the data centre, the routing instance inside the L3 domain is composed of two devices, labelled ‘A’ and ‘B’. - -Based on this principle it is possible to manage several OVHcloud Connect services. - -![L3 Two POP](images/occ-l3-twopop.png){.thumbnail} - -As a result, L3 makes it compatible with a multi-DC configuration. - -![L3 Multi DC](images/occ-l3-multidc.png){.thumbnail} - -The two examples above illustrate the configuration of two OVHcloud Connect services, as one OVHcloud Connect equals one PoP/EntryPoint. - -**Rules:** - -- You can have as many OVHcloud Connect L3 as you want in the same vRack. -- You can associate several PoPs/EntryPoints with one DC/EndPoint. -- You can associate several DCs/EndPoints with one PoP/EntryPoint. -- You cannot associate two PoPs/EntryPoints (i.e. you cannot forward traffic between them). -- One L3 domain can only be associated with one DC/EndPoint. -- One L3 domain (i.e. subnet) cannot be stretched between two DCs or two PoPs. -- An OVHcloud Connect L2 can be mixed with several OVHcloud Connect L3 in the same vRack. - -![L3 Rules](images/occ-l3-rules.gif){.thumbnail} - -The following schema shows the mix of L2 and L3. They can end in the same OVHcloud data centre or not. - -![L3 Mix L2](images/occ-l3-mixl2.png){.thumbnail} - -### Connection mode details - -![L3 Architecture](images/occ-l3-architecture.png){.thumbnail} - -On such an architecture, two L3 domains are needed: PoP/EntryPoint and DC/EndPoint. - -"IP Net A" is part of the L3 Domain in the DC. The following rules apply: - -- IP addressing plan (subnet and netmask) with a minimum netmask of /29. -- The first IP address is reserved for the virtual gateway (if running VRRP). -- The two following IP addresses are reserved for the OVHcloud routing instance. -- All other IP addresses are available to the customer. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud virtual router address (if enabled) | -| A.B.C.2 | OVHcloud router A | -| A.B.C.3 | OVHcloud router B | - -"IP Net B" is part of the L3 Domain in the PoP. The following rules apply: - -- Supported netmask: /30 (CIDR notation). -- The first IP address is reserved for the OVHcloud routing instance. -- The second IP address is used for customer equipment. - -| IP address | Role | -|:-----:|:-----:| -| A.B.C.0 | Subnet | -| A.B.C.1 | OVHcloud router | -| A.B.C.2 | Customer router | -| A.B.C.3 | Subnet broadcast | - -#### VRRP configuration in the DC/EndPoint - -VRRP allows router redundancy on OVHcloud devices. - -- Each DC/EndPoint supports only one VRRP instance. -- The VRRP VRID value is provided by OVHcloud. -- By default, VRRP is master on ‘A’ device. -- Static routes can be configured. - -#### BGP configuration - -BGP is mandatory in a PoP/EntryPoint and optional in a DC/EndPoint. Enabling BGP in a DC/EndPoint disables VRRP configuration. - -- Each PoP/EntryPoint and DC/EndPoint needs an AS. This AS must be independent from the customer BGP AS to form an eBGP relation. The recommended value is in the range 64512-65534. -- Each PoP/EntryPoint supports only one BGP session (no eBGP Multihop). -- With two or more PoPs/EntryPoints, ECMP is automatically enabled. MED and/or AS-PATH must be tuned to have path selection. -- Each DC/EndPoint supports up to 4 BGP peers. -- Up to 100 prefixes can be announced per BGP session. -- For each DC/EndPoint you must establish a BGP session with ‘A’ device and ‘B’ device. -- By default, BFD is activated on all BGP sessions. This protocol is higly recommended on the DC side as well to have a faster convergence. - -For example, IP network 'B' will be announced to the OVHcloud router through BGP session. - -![L3 BGP vRack](images/occ-l3-bgpvrack.png){.thumbnail} - -At a more global level, BGP topology will look like this: - -![L3 BGP Global Topology](images/occ-l3-bgpglobal.png){.thumbnail} - -#### BGP path selection - -By default, all available paths are enabled using ECMP, with up to 4 paths supported. To have an active/passive topology with two PoPs/EntryPoints, you can use AS path prepending or MED. - -If AS path prepending is configured on the customer's devices in PoP2, the topology will look like this: - -![L3 BGP as-prepend](images/occ-l3-bgpasprepend-med.png){.thumbnail} - -Note: AS path prepending is not configurable on OVHcloud devices. - -Using MED is an alternative to achieve the same topology. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-architecture.png b/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-architecture.png deleted file mode 100644 index 2d7c5ae48e0..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-architecture.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-bgpasprepend-med.png b/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-bgpasprepend-med.png deleted file mode 100644 index 4845b33632d..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-bgpasprepend-med.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-bgpglobal.png b/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-bgpglobal.png deleted file mode 100644 index 75a165b9a0a..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-bgpglobal.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-bgpvrack.png b/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-bgpvrack.png deleted file mode 100644 index 2e0088df4c6..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-bgpvrack.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-implementation.png b/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-implementation.png deleted file mode 100644 index 332e7f21a0e..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-implementation.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-mixl2.png b/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-mixl2.png deleted file mode 100644 index ef116c73fb6..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-mixl2.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-multidc.png b/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-multidc.png deleted file mode 100644 index c0f99371c61..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-multidc.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-rules.gif b/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-rules.gif deleted file mode 100644 index abd7e89e479..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-rules.gif and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-twopop.png b/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-twopop.png deleted file mode 100644 index 499d11879e9..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-layer3/images/occ-l3-twopop.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-layer3/meta.yaml b/pages/network/ovhcloud_connect/occ-layer3/meta.yaml deleted file mode 100755 index 821f93e0429..00000000000 --- a/pages/network/ovhcloud_connect/occ-layer3/meta.yaml +++ /dev/null @@ -1,2 +0,0 @@ -id: ffc85f6d-7a0d-4e7f-afe3-6c8030feaf5a -full_slug: network-ovhcloud-connect-layer3 \ No newline at end of file diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.de-de.md b/pages/network/ovhcloud_connect/occ-limits/guide.de-de.md deleted file mode 100644 index eeca25e2675..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.de-de.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Technical capabilities and limitations -excerpt: 'Learn the technical capabilities and limitations of the OVHcloud Connect solution' -updated: 2025-10-03 ---- - -## Objective - -**This page provides an overview of the technical capabilities and limitations of the OVHcloud Connect solution.** - -## Instructions - -### Link capabilities - -- 1000Base-LX/LH for 1Gb -- 10GBase-LR for 10Gb -- 100GBase-LR4 for 100Gb -- Jumbo frame up to 9000 bytes -- Autonegotiation not supported - -### Technical limitations - -#### Layer 2 mode - -- The number of client-side MAC addresses is limited to 512 per port -- The maximum bandwidth is 10Gb per port - -#### Layer 3 mode - -- Each EntryPoint/POP supports only one BGP session (no eBGP Multihop) -- Each EndPoint/DC supports up to 4 BGP peers -- Up to 100 prefixes can be announced per BGP session - -### Unsupported features - -#### Layer 2 mode - -- 802.1p CoS-based -- DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) -- TRILL, SPF and FabricPath -- FCoE -- Spannning-tree -- IGMP and Multicast -- EtherChannel, PaGP for aggregation - -#### Layer 3 mode - -- IPv6 -- Any QoS mechanism -- 802.1q tag -- Multi-VRF -- eBGP Multi-Hop -- iBGP -- Static routing in EntryPoint/PoP - -### Known issues - -| Description | Detail | Cause | Workaround | Affected sites | -|:-----:|:------:|:-----:|:----------:|:--------------:| -| DC routes not propagated to PoP | When using AS65501, routes announced using BGP in vRack are not propagated to PoP | OVHcloud internal configuration | Do not use AS65501 | ALL | -| Light received but port is down | Device fails to change interface status to UP despite optical levels on RX are correct | Autonegotiation is configured | Unconfigure autonegotiation | ALL PoPs | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.en-asia.md b/pages/network/ovhcloud_connect/occ-limits/guide.en-asia.md deleted file mode 100644 index eeca25e2675..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.en-asia.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Technical capabilities and limitations -excerpt: 'Learn the technical capabilities and limitations of the OVHcloud Connect solution' -updated: 2025-10-03 ---- - -## Objective - -**This page provides an overview of the technical capabilities and limitations of the OVHcloud Connect solution.** - -## Instructions - -### Link capabilities - -- 1000Base-LX/LH for 1Gb -- 10GBase-LR for 10Gb -- 100GBase-LR4 for 100Gb -- Jumbo frame up to 9000 bytes -- Autonegotiation not supported - -### Technical limitations - -#### Layer 2 mode - -- The number of client-side MAC addresses is limited to 512 per port -- The maximum bandwidth is 10Gb per port - -#### Layer 3 mode - -- Each EntryPoint/POP supports only one BGP session (no eBGP Multihop) -- Each EndPoint/DC supports up to 4 BGP peers -- Up to 100 prefixes can be announced per BGP session - -### Unsupported features - -#### Layer 2 mode - -- 802.1p CoS-based -- DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) -- TRILL, SPF and FabricPath -- FCoE -- Spannning-tree -- IGMP and Multicast -- EtherChannel, PaGP for aggregation - -#### Layer 3 mode - -- IPv6 -- Any QoS mechanism -- 802.1q tag -- Multi-VRF -- eBGP Multi-Hop -- iBGP -- Static routing in EntryPoint/PoP - -### Known issues - -| Description | Detail | Cause | Workaround | Affected sites | -|:-----:|:------:|:-----:|:----------:|:--------------:| -| DC routes not propagated to PoP | When using AS65501, routes announced using BGP in vRack are not propagated to PoP | OVHcloud internal configuration | Do not use AS65501 | ALL | -| Light received but port is down | Device fails to change interface status to UP despite optical levels on RX are correct | Autonegotiation is configured | Unconfigure autonegotiation | ALL PoPs | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.en-au.md b/pages/network/ovhcloud_connect/occ-limits/guide.en-au.md deleted file mode 100644 index eeca25e2675..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.en-au.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Technical capabilities and limitations -excerpt: 'Learn the technical capabilities and limitations of the OVHcloud Connect solution' -updated: 2025-10-03 ---- - -## Objective - -**This page provides an overview of the technical capabilities and limitations of the OVHcloud Connect solution.** - -## Instructions - -### Link capabilities - -- 1000Base-LX/LH for 1Gb -- 10GBase-LR for 10Gb -- 100GBase-LR4 for 100Gb -- Jumbo frame up to 9000 bytes -- Autonegotiation not supported - -### Technical limitations - -#### Layer 2 mode - -- The number of client-side MAC addresses is limited to 512 per port -- The maximum bandwidth is 10Gb per port - -#### Layer 3 mode - -- Each EntryPoint/POP supports only one BGP session (no eBGP Multihop) -- Each EndPoint/DC supports up to 4 BGP peers -- Up to 100 prefixes can be announced per BGP session - -### Unsupported features - -#### Layer 2 mode - -- 802.1p CoS-based -- DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) -- TRILL, SPF and FabricPath -- FCoE -- Spannning-tree -- IGMP and Multicast -- EtherChannel, PaGP for aggregation - -#### Layer 3 mode - -- IPv6 -- Any QoS mechanism -- 802.1q tag -- Multi-VRF -- eBGP Multi-Hop -- iBGP -- Static routing in EntryPoint/PoP - -### Known issues - -| Description | Detail | Cause | Workaround | Affected sites | -|:-----:|:------:|:-----:|:----------:|:--------------:| -| DC routes not propagated to PoP | When using AS65501, routes announced using BGP in vRack are not propagated to PoP | OVHcloud internal configuration | Do not use AS65501 | ALL | -| Light received but port is down | Device fails to change interface status to UP despite optical levels on RX are correct | Autonegotiation is configured | Unconfigure autonegotiation | ALL PoPs | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.en-ca.md b/pages/network/ovhcloud_connect/occ-limits/guide.en-ca.md deleted file mode 100644 index eeca25e2675..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.en-ca.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Technical capabilities and limitations -excerpt: 'Learn the technical capabilities and limitations of the OVHcloud Connect solution' -updated: 2025-10-03 ---- - -## Objective - -**This page provides an overview of the technical capabilities and limitations of the OVHcloud Connect solution.** - -## Instructions - -### Link capabilities - -- 1000Base-LX/LH for 1Gb -- 10GBase-LR for 10Gb -- 100GBase-LR4 for 100Gb -- Jumbo frame up to 9000 bytes -- Autonegotiation not supported - -### Technical limitations - -#### Layer 2 mode - -- The number of client-side MAC addresses is limited to 512 per port -- The maximum bandwidth is 10Gb per port - -#### Layer 3 mode - -- Each EntryPoint/POP supports only one BGP session (no eBGP Multihop) -- Each EndPoint/DC supports up to 4 BGP peers -- Up to 100 prefixes can be announced per BGP session - -### Unsupported features - -#### Layer 2 mode - -- 802.1p CoS-based -- DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) -- TRILL, SPF and FabricPath -- FCoE -- Spannning-tree -- IGMP and Multicast -- EtherChannel, PaGP for aggregation - -#### Layer 3 mode - -- IPv6 -- Any QoS mechanism -- 802.1q tag -- Multi-VRF -- eBGP Multi-Hop -- iBGP -- Static routing in EntryPoint/PoP - -### Known issues - -| Description | Detail | Cause | Workaround | Affected sites | -|:-----:|:------:|:-----:|:----------:|:--------------:| -| DC routes not propagated to PoP | When using AS65501, routes announced using BGP in vRack are not propagated to PoP | OVHcloud internal configuration | Do not use AS65501 | ALL | -| Light received but port is down | Device fails to change interface status to UP despite optical levels on RX are correct | Autonegotiation is configured | Unconfigure autonegotiation | ALL PoPs | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.en-gb.md b/pages/network/ovhcloud_connect/occ-limits/guide.en-gb.md deleted file mode 100644 index eeca25e2675..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.en-gb.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Technical capabilities and limitations -excerpt: 'Learn the technical capabilities and limitations of the OVHcloud Connect solution' -updated: 2025-10-03 ---- - -## Objective - -**This page provides an overview of the technical capabilities and limitations of the OVHcloud Connect solution.** - -## Instructions - -### Link capabilities - -- 1000Base-LX/LH for 1Gb -- 10GBase-LR for 10Gb -- 100GBase-LR4 for 100Gb -- Jumbo frame up to 9000 bytes -- Autonegotiation not supported - -### Technical limitations - -#### Layer 2 mode - -- The number of client-side MAC addresses is limited to 512 per port -- The maximum bandwidth is 10Gb per port - -#### Layer 3 mode - -- Each EntryPoint/POP supports only one BGP session (no eBGP Multihop) -- Each EndPoint/DC supports up to 4 BGP peers -- Up to 100 prefixes can be announced per BGP session - -### Unsupported features - -#### Layer 2 mode - -- 802.1p CoS-based -- DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) -- TRILL, SPF and FabricPath -- FCoE -- Spannning-tree -- IGMP and Multicast -- EtherChannel, PaGP for aggregation - -#### Layer 3 mode - -- IPv6 -- Any QoS mechanism -- 802.1q tag -- Multi-VRF -- eBGP Multi-Hop -- iBGP -- Static routing in EntryPoint/PoP - -### Known issues - -| Description | Detail | Cause | Workaround | Affected sites | -|:-----:|:------:|:-----:|:----------:|:--------------:| -| DC routes not propagated to PoP | When using AS65501, routes announced using BGP in vRack are not propagated to PoP | OVHcloud internal configuration | Do not use AS65501 | ALL | -| Light received but port is down | Device fails to change interface status to UP despite optical levels on RX are correct | Autonegotiation is configured | Unconfigure autonegotiation | ALL PoPs | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.en-ie.md b/pages/network/ovhcloud_connect/occ-limits/guide.en-ie.md deleted file mode 100644 index eeca25e2675..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.en-ie.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Technical capabilities and limitations -excerpt: 'Learn the technical capabilities and limitations of the OVHcloud Connect solution' -updated: 2025-10-03 ---- - -## Objective - -**This page provides an overview of the technical capabilities and limitations of the OVHcloud Connect solution.** - -## Instructions - -### Link capabilities - -- 1000Base-LX/LH for 1Gb -- 10GBase-LR for 10Gb -- 100GBase-LR4 for 100Gb -- Jumbo frame up to 9000 bytes -- Autonegotiation not supported - -### Technical limitations - -#### Layer 2 mode - -- The number of client-side MAC addresses is limited to 512 per port -- The maximum bandwidth is 10Gb per port - -#### Layer 3 mode - -- Each EntryPoint/POP supports only one BGP session (no eBGP Multihop) -- Each EndPoint/DC supports up to 4 BGP peers -- Up to 100 prefixes can be announced per BGP session - -### Unsupported features - -#### Layer 2 mode - -- 802.1p CoS-based -- DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) -- TRILL, SPF and FabricPath -- FCoE -- Spannning-tree -- IGMP and Multicast -- EtherChannel, PaGP for aggregation - -#### Layer 3 mode - -- IPv6 -- Any QoS mechanism -- 802.1q tag -- Multi-VRF -- eBGP Multi-Hop -- iBGP -- Static routing in EntryPoint/PoP - -### Known issues - -| Description | Detail | Cause | Workaround | Affected sites | -|:-----:|:------:|:-----:|:----------:|:--------------:| -| DC routes not propagated to PoP | When using AS65501, routes announced using BGP in vRack are not propagated to PoP | OVHcloud internal configuration | Do not use AS65501 | ALL | -| Light received but port is down | Device fails to change interface status to UP despite optical levels on RX are correct | Autonegotiation is configured | Unconfigure autonegotiation | ALL PoPs | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.en-sg.md b/pages/network/ovhcloud_connect/occ-limits/guide.en-sg.md deleted file mode 100644 index eeca25e2675..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.en-sg.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Technical capabilities and limitations -excerpt: 'Learn the technical capabilities and limitations of the OVHcloud Connect solution' -updated: 2025-10-03 ---- - -## Objective - -**This page provides an overview of the technical capabilities and limitations of the OVHcloud Connect solution.** - -## Instructions - -### Link capabilities - -- 1000Base-LX/LH for 1Gb -- 10GBase-LR for 10Gb -- 100GBase-LR4 for 100Gb -- Jumbo frame up to 9000 bytes -- Autonegotiation not supported - -### Technical limitations - -#### Layer 2 mode - -- The number of client-side MAC addresses is limited to 512 per port -- The maximum bandwidth is 10Gb per port - -#### Layer 3 mode - -- Each EntryPoint/POP supports only one BGP session (no eBGP Multihop) -- Each EndPoint/DC supports up to 4 BGP peers -- Up to 100 prefixes can be announced per BGP session - -### Unsupported features - -#### Layer 2 mode - -- 802.1p CoS-based -- DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) -- TRILL, SPF and FabricPath -- FCoE -- Spannning-tree -- IGMP and Multicast -- EtherChannel, PaGP for aggregation - -#### Layer 3 mode - -- IPv6 -- Any QoS mechanism -- 802.1q tag -- Multi-VRF -- eBGP Multi-Hop -- iBGP -- Static routing in EntryPoint/PoP - -### Known issues - -| Description | Detail | Cause | Workaround | Affected sites | -|:-----:|:------:|:-----:|:----------:|:--------------:| -| DC routes not propagated to PoP | When using AS65501, routes announced using BGP in vRack are not propagated to PoP | OVHcloud internal configuration | Do not use AS65501 | ALL | -| Light received but port is down | Device fails to change interface status to UP despite optical levels on RX are correct | Autonegotiation is configured | Unconfigure autonegotiation | ALL PoPs | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.en-us.md b/pages/network/ovhcloud_connect/occ-limits/guide.en-us.md deleted file mode 100644 index eeca25e2675..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.en-us.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Technical capabilities and limitations -excerpt: 'Learn the technical capabilities and limitations of the OVHcloud Connect solution' -updated: 2025-10-03 ---- - -## Objective - -**This page provides an overview of the technical capabilities and limitations of the OVHcloud Connect solution.** - -## Instructions - -### Link capabilities - -- 1000Base-LX/LH for 1Gb -- 10GBase-LR for 10Gb -- 100GBase-LR4 for 100Gb -- Jumbo frame up to 9000 bytes -- Autonegotiation not supported - -### Technical limitations - -#### Layer 2 mode - -- The number of client-side MAC addresses is limited to 512 per port -- The maximum bandwidth is 10Gb per port - -#### Layer 3 mode - -- Each EntryPoint/POP supports only one BGP session (no eBGP Multihop) -- Each EndPoint/DC supports up to 4 BGP peers -- Up to 100 prefixes can be announced per BGP session - -### Unsupported features - -#### Layer 2 mode - -- 802.1p CoS-based -- DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) -- TRILL, SPF and FabricPath -- FCoE -- Spannning-tree -- IGMP and Multicast -- EtherChannel, PaGP for aggregation - -#### Layer 3 mode - -- IPv6 -- Any QoS mechanism -- 802.1q tag -- Multi-VRF -- eBGP Multi-Hop -- iBGP -- Static routing in EntryPoint/PoP - -### Known issues - -| Description | Detail | Cause | Workaround | Affected sites | -|:-----:|:------:|:-----:|:----------:|:--------------:| -| DC routes not propagated to PoP | When using AS65501, routes announced using BGP in vRack are not propagated to PoP | OVHcloud internal configuration | Do not use AS65501 | ALL | -| Light received but port is down | Device fails to change interface status to UP despite optical levels on RX are correct | Autonegotiation is configured | Unconfigure autonegotiation | ALL PoPs | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.es-es.md b/pages/network/ovhcloud_connect/occ-limits/guide.es-es.md deleted file mode 100644 index eeca25e2675..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.es-es.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Technical capabilities and limitations -excerpt: 'Learn the technical capabilities and limitations of the OVHcloud Connect solution' -updated: 2025-10-03 ---- - -## Objective - -**This page provides an overview of the technical capabilities and limitations of the OVHcloud Connect solution.** - -## Instructions - -### Link capabilities - -- 1000Base-LX/LH for 1Gb -- 10GBase-LR for 10Gb -- 100GBase-LR4 for 100Gb -- Jumbo frame up to 9000 bytes -- Autonegotiation not supported - -### Technical limitations - -#### Layer 2 mode - -- The number of client-side MAC addresses is limited to 512 per port -- The maximum bandwidth is 10Gb per port - -#### Layer 3 mode - -- Each EntryPoint/POP supports only one BGP session (no eBGP Multihop) -- Each EndPoint/DC supports up to 4 BGP peers -- Up to 100 prefixes can be announced per BGP session - -### Unsupported features - -#### Layer 2 mode - -- 802.1p CoS-based -- DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) -- TRILL, SPF and FabricPath -- FCoE -- Spannning-tree -- IGMP and Multicast -- EtherChannel, PaGP for aggregation - -#### Layer 3 mode - -- IPv6 -- Any QoS mechanism -- 802.1q tag -- Multi-VRF -- eBGP Multi-Hop -- iBGP -- Static routing in EntryPoint/PoP - -### Known issues - -| Description | Detail | Cause | Workaround | Affected sites | -|:-----:|:------:|:-----:|:----------:|:--------------:| -| DC routes not propagated to PoP | When using AS65501, routes announced using BGP in vRack are not propagated to PoP | OVHcloud internal configuration | Do not use AS65501 | ALL | -| Light received but port is down | Device fails to change interface status to UP despite optical levels on RX are correct | Autonegotiation is configured | Unconfigure autonegotiation | ALL PoPs | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.es-us.md b/pages/network/ovhcloud_connect/occ-limits/guide.es-us.md deleted file mode 100644 index eeca25e2675..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.es-us.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Technical capabilities and limitations -excerpt: 'Learn the technical capabilities and limitations of the OVHcloud Connect solution' -updated: 2025-10-03 ---- - -## Objective - -**This page provides an overview of the technical capabilities and limitations of the OVHcloud Connect solution.** - -## Instructions - -### Link capabilities - -- 1000Base-LX/LH for 1Gb -- 10GBase-LR for 10Gb -- 100GBase-LR4 for 100Gb -- Jumbo frame up to 9000 bytes -- Autonegotiation not supported - -### Technical limitations - -#### Layer 2 mode - -- The number of client-side MAC addresses is limited to 512 per port -- The maximum bandwidth is 10Gb per port - -#### Layer 3 mode - -- Each EntryPoint/POP supports only one BGP session (no eBGP Multihop) -- Each EndPoint/DC supports up to 4 BGP peers -- Up to 100 prefixes can be announced per BGP session - -### Unsupported features - -#### Layer 2 mode - -- 802.1p CoS-based -- DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) -- TRILL, SPF and FabricPath -- FCoE -- Spannning-tree -- IGMP and Multicast -- EtherChannel, PaGP for aggregation - -#### Layer 3 mode - -- IPv6 -- Any QoS mechanism -- 802.1q tag -- Multi-VRF -- eBGP Multi-Hop -- iBGP -- Static routing in EntryPoint/PoP - -### Known issues - -| Description | Detail | Cause | Workaround | Affected sites | -|:-----:|:------:|:-----:|:----------:|:--------------:| -| DC routes not propagated to PoP | When using AS65501, routes announced using BGP in vRack are not propagated to PoP | OVHcloud internal configuration | Do not use AS65501 | ALL | -| Light received but port is down | Device fails to change interface status to UP despite optical levels on RX are correct | Autonegotiation is configured | Unconfigure autonegotiation | ALL PoPs | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.fr-ca.md b/pages/network/ovhcloud_connect/occ-limits/guide.fr-ca.md deleted file mode 100644 index b33f7b233fd..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.fr-ca.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Capacités et limites techniques -excerpt: 'Découvrez les capacités et limites techniques de l offre OVHcloud Connect' -updated: 2025-10-03 ---- - -## Objectif - -**Découvrez les capacités et limitations techniques de l'offre OVHcloud Connect.** - -## En pratique - -### Capacités de la connexion - -* 1000Base-LX/LH pour 1Gb -* 10GBase-LR pour 10Gb -* 100GBase-LR4 pour 100Gb -* Jumbo Frame: jusqu'à 9000 bytes -* Auto-négociation non supportée - -### Limitations techniques - -#### Mode Layer 2 - -* Le nombre d'adresses MAC coté client est limité à 512 par port -* La bande passante maximale est de 10Gb par port - -#### Mode Layer-3 - -* Chaque EntryPoint/POP ne prend en charge qu’une seule session BGP (pas de Multihop eBGP) -* Chaque EndPoint/DC prend en charge jusqu’à 4 peers BGP -* Jusqu’à 100 préfixes peuvent être annoncés par session BGP - -### Fonctionnalités non supportées - -#### Mode Layer 2 - -* CoS avec 802.1p -* DCBX et protocoles apparentés (802.1Qbb, -802.1Qaz, 802.1Qau) -* TRILL, SPF et FabricPath -* FCoE -* Spannning-tree -* IGMP et Multicast -* EtherChannel, PaGP pour l'aggrégation de liens - -#### Mode Layer-3 - -* IPv6 -* Tout mécanisme de qualité de service -* Tag 802.1q -* Multi-VRF -* eBGP Multi-Hop -* iBGP -* Routage statique sur EntryPoint/POP - -### Problèmes connus - -Les problèmes suivants sont présents sur OVHcloud Connect. - -| Problème | Détail | Cause | Contournement | Sites impactés | -|:--------:|:------:|:-----:|:-------------:|:--------------:| -| Routes du EndPoint/DC non propagées jusqu'au EntryPoint/POP | En utilisant l'AS65501, les routes annoncées en BGP depuis le vRack ne remontent pas | Configuration OVHcloud interne | Ne pas utiliser AS65501 | Tous | -| Lumière en réception mais absence de lien | L'équipement échoue à activer le lien malgré des valeurs optiques en réception correctes | L'auto-négociation est configurée | Désactiver l'auto-négociation | Tous les POP | - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.fr-fr.md b/pages/network/ovhcloud_connect/occ-limits/guide.fr-fr.md deleted file mode 100644 index b33f7b233fd..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.fr-fr.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Capacités et limites techniques -excerpt: 'Découvrez les capacités et limites techniques de l offre OVHcloud Connect' -updated: 2025-10-03 ---- - -## Objectif - -**Découvrez les capacités et limitations techniques de l'offre OVHcloud Connect.** - -## En pratique - -### Capacités de la connexion - -* 1000Base-LX/LH pour 1Gb -* 10GBase-LR pour 10Gb -* 100GBase-LR4 pour 100Gb -* Jumbo Frame: jusqu'à 9000 bytes -* Auto-négociation non supportée - -### Limitations techniques - -#### Mode Layer 2 - -* Le nombre d'adresses MAC coté client est limité à 512 par port -* La bande passante maximale est de 10Gb par port - -#### Mode Layer-3 - -* Chaque EntryPoint/POP ne prend en charge qu’une seule session BGP (pas de Multihop eBGP) -* Chaque EndPoint/DC prend en charge jusqu’à 4 peers BGP -* Jusqu’à 100 préfixes peuvent être annoncés par session BGP - -### Fonctionnalités non supportées - -#### Mode Layer 2 - -* CoS avec 802.1p -* DCBX et protocoles apparentés (802.1Qbb, -802.1Qaz, 802.1Qau) -* TRILL, SPF et FabricPath -* FCoE -* Spannning-tree -* IGMP et Multicast -* EtherChannel, PaGP pour l'aggrégation de liens - -#### Mode Layer-3 - -* IPv6 -* Tout mécanisme de qualité de service -* Tag 802.1q -* Multi-VRF -* eBGP Multi-Hop -* iBGP -* Routage statique sur EntryPoint/POP - -### Problèmes connus - -Les problèmes suivants sont présents sur OVHcloud Connect. - -| Problème | Détail | Cause | Contournement | Sites impactés | -|:--------:|:------:|:-----:|:-------------:|:--------------:| -| Routes du EndPoint/DC non propagées jusqu'au EntryPoint/POP | En utilisant l'AS65501, les routes annoncées en BGP depuis le vRack ne remontent pas | Configuration OVHcloud interne | Ne pas utiliser AS65501 | Tous | -| Lumière en réception mais absence de lien | L'équipement échoue à activer le lien malgré des valeurs optiques en réception correctes | L'auto-négociation est configurée | Désactiver l'auto-négociation | Tous les POP | - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.it-it.md b/pages/network/ovhcloud_connect/occ-limits/guide.it-it.md deleted file mode 100644 index eeca25e2675..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.it-it.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Technical capabilities and limitations -excerpt: 'Learn the technical capabilities and limitations of the OVHcloud Connect solution' -updated: 2025-10-03 ---- - -## Objective - -**This page provides an overview of the technical capabilities and limitations of the OVHcloud Connect solution.** - -## Instructions - -### Link capabilities - -- 1000Base-LX/LH for 1Gb -- 10GBase-LR for 10Gb -- 100GBase-LR4 for 100Gb -- Jumbo frame up to 9000 bytes -- Autonegotiation not supported - -### Technical limitations - -#### Layer 2 mode - -- The number of client-side MAC addresses is limited to 512 per port -- The maximum bandwidth is 10Gb per port - -#### Layer 3 mode - -- Each EntryPoint/POP supports only one BGP session (no eBGP Multihop) -- Each EndPoint/DC supports up to 4 BGP peers -- Up to 100 prefixes can be announced per BGP session - -### Unsupported features - -#### Layer 2 mode - -- 802.1p CoS-based -- DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) -- TRILL, SPF and FabricPath -- FCoE -- Spannning-tree -- IGMP and Multicast -- EtherChannel, PaGP for aggregation - -#### Layer 3 mode - -- IPv6 -- Any QoS mechanism -- 802.1q tag -- Multi-VRF -- eBGP Multi-Hop -- iBGP -- Static routing in EntryPoint/PoP - -### Known issues - -| Description | Detail | Cause | Workaround | Affected sites | -|:-----:|:------:|:-----:|:----------:|:--------------:| -| DC routes not propagated to PoP | When using AS65501, routes announced using BGP in vRack are not propagated to PoP | OVHcloud internal configuration | Do not use AS65501 | ALL | -| Light received but port is down | Device fails to change interface status to UP despite optical levels on RX are correct | Autonegotiation is configured | Unconfigure autonegotiation | ALL PoPs | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.pl-pl.md b/pages/network/ovhcloud_connect/occ-limits/guide.pl-pl.md deleted file mode 100644 index eeca25e2675..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.pl-pl.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Technical capabilities and limitations -excerpt: 'Learn the technical capabilities and limitations of the OVHcloud Connect solution' -updated: 2025-10-03 ---- - -## Objective - -**This page provides an overview of the technical capabilities and limitations of the OVHcloud Connect solution.** - -## Instructions - -### Link capabilities - -- 1000Base-LX/LH for 1Gb -- 10GBase-LR for 10Gb -- 100GBase-LR4 for 100Gb -- Jumbo frame up to 9000 bytes -- Autonegotiation not supported - -### Technical limitations - -#### Layer 2 mode - -- The number of client-side MAC addresses is limited to 512 per port -- The maximum bandwidth is 10Gb per port - -#### Layer 3 mode - -- Each EntryPoint/POP supports only one BGP session (no eBGP Multihop) -- Each EndPoint/DC supports up to 4 BGP peers -- Up to 100 prefixes can be announced per BGP session - -### Unsupported features - -#### Layer 2 mode - -- 802.1p CoS-based -- DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) -- TRILL, SPF and FabricPath -- FCoE -- Spannning-tree -- IGMP and Multicast -- EtherChannel, PaGP for aggregation - -#### Layer 3 mode - -- IPv6 -- Any QoS mechanism -- 802.1q tag -- Multi-VRF -- eBGP Multi-Hop -- iBGP -- Static routing in EntryPoint/PoP - -### Known issues - -| Description | Detail | Cause | Workaround | Affected sites | -|:-----:|:------:|:-----:|:----------:|:--------------:| -| DC routes not propagated to PoP | When using AS65501, routes announced using BGP in vRack are not propagated to PoP | OVHcloud internal configuration | Do not use AS65501 | ALL | -| Light received but port is down | Device fails to change interface status to UP despite optical levels on RX are correct | Autonegotiation is configured | Unconfigure autonegotiation | ALL PoPs | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-limits/guide.pt-pt.md b/pages/network/ovhcloud_connect/occ-limits/guide.pt-pt.md deleted file mode 100644 index eeca25e2675..00000000000 --- a/pages/network/ovhcloud_connect/occ-limits/guide.pt-pt.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Technical capabilities and limitations -excerpt: 'Learn the technical capabilities and limitations of the OVHcloud Connect solution' -updated: 2025-10-03 ---- - -## Objective - -**This page provides an overview of the technical capabilities and limitations of the OVHcloud Connect solution.** - -## Instructions - -### Link capabilities - -- 1000Base-LX/LH for 1Gb -- 10GBase-LR for 10Gb -- 100GBase-LR4 for 100Gb -- Jumbo frame up to 9000 bytes -- Autonegotiation not supported - -### Technical limitations - -#### Layer 2 mode - -- The number of client-side MAC addresses is limited to 512 per port -- The maximum bandwidth is 10Gb per port - -#### Layer 3 mode - -- Each EntryPoint/POP supports only one BGP session (no eBGP Multihop) -- Each EndPoint/DC supports up to 4 BGP peers -- Up to 100 prefixes can be announced per BGP session - -### Unsupported features - -#### Layer 2 mode - -- 802.1p CoS-based -- DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau) -- TRILL, SPF and FabricPath -- FCoE -- Spannning-tree -- IGMP and Multicast -- EtherChannel, PaGP for aggregation - -#### Layer 3 mode - -- IPv6 -- Any QoS mechanism -- 802.1q tag -- Multi-VRF -- eBGP Multi-Hop -- iBGP -- Static routing in EntryPoint/PoP - -### Known issues - -| Description | Detail | Cause | Workaround | Affected sites | -|:-----:|:------:|:-----:|:----------:|:--------------:| -| DC routes not propagated to PoP | When using AS65501, routes announced using BGP in vRack are not propagated to PoP | OVHcloud internal configuration | Do not use AS65501 | ALL | -| Light received but port is down | Device fails to change interface status to UP despite optical levels on RX are correct | Autonegotiation is configured | Unconfigure autonegotiation | ALL PoPs | - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-logs-2-customers/guide.fr-fr.md b/pages/network/ovhcloud_connect/occ-logs-2-customers/guide.fr-fr.md deleted file mode 100644 index a19ce565b50..00000000000 --- a/pages/network/ovhcloud_connect/occ-logs-2-customers/guide.fr-fr.md +++ /dev/null @@ -1,203 +0,0 @@ ---- -title: Transfert des logs (Log Forwarding) pour OVHcloud Connect -excerpt: Découvrez comment transférer vos logs depuis un service OCC vers Logs Data Platform -updated: 2025-08-28 ---- - -## Objectif - -L'objectif de ce guide est de vous montrer comment activer la redirection de logs de votre service OVHcloud Connect vers Logs Data Platform (LDP), une plateforme qui vous aide à stocker, archiver, interroger et visualiser vos logs. -Pour en savoir plus sur Logs Data Platform avant de lire ce guide, reportez-vous au [Guide d'introduction de Logs Data Platform](/pages/manage_and_operate/observability/logs_data_platform/getting_started_introduction_to_LDP). - -## Glossaire - -- **Logs Data Platform :** une plateforme de gestion de logs entièrement gérée et sécurisée par OVHcloud. Pour plus d'informations, consultez la page de présentation de la solution [Logs Data Platform](/links/manage-operate/ldp). -- **Data Stream:** une partition logique de logs que vous créez dans un compte LDP et que vous utiliserez lors de l'ingestion, de la visualisation ou de l'interrogation de vos logs. Plusieurs sources peuvent être stockées dans le même flux de données, et c'est l'unité qui peut être utilisée pour définir un pipeline de logs (politique de rétention, archivage, streaming live, etc.), des droits d'accès et des politiques d'alertes. -- **Transfert de logs :** fonctionnalité intégrée à un produit OVHcloud pour ingérer les logs de ses services dans un *Data Stream* d’un compte LDP dans le même compte OVHcloud. Cette fonctionnalité doit être activée par le client et par service. -- **Abonnement à la redirection de logs :** lors de l'activation de la redirection de logs pour un service OVHcloud donné vers un LDP *Data Stream* donné, un *Abonnement* est créé et attaché au *Data Stream* pour une gestion ultérieure par le client. - -## Prérequis - -- Un compte Logs Data Platform (LDP) avec au moins un *Stream* actif configuré. Ce guide vous accompagnera dans toutes les étapes nécessaires : [Quick start for Logs Data Platform (EN)](/pages/manage_and_operate/observability/logs_data_platform/getting_started_quick_start). - - Si vous ne connaissez pas toutes les possibilités de configuration d'un *Stream* LDP, il vous suffit d'en créer un nouveau avec les options par défaut (indexation & websocket activés, stockage longue durée désactivé) pour suivre ce guide. -- Un service [OVHcloud Connect](/pages/network/ovhcloud_connect/occ-concepts-overview) opérationnel. -- Le compte LDP et le compte OVHcloud Connect doivent appartenir au même compte OVHcloud. - -## Concepts & limites - -**Quels sont les logs d’un OVHcloud Connect ?** - -### Types de logs: - -Il existe quatre types de logs qui peuvent être transférés : - -- **service** : Événements liés au cycle de vie du service (suspendu, livré, etc). -- **service_configuration** : Événements liés à la configuration du service, y compris l'ajout ou la suppression de configurations DC/POP. -- **bgp** : Statut de la session BGP. -- **interface** : Événements liés à l'interface de fibre optique, y compris les signaux entrant et sortant. - -### Contenu des logs : - -| Nom du champ | Description | Type | -|------------|-------------|---------| -| kind | Le type de log transféré | String | -| message | Une description explicite de l'événement enregistré | String | -| neighbor | L'adresse distante dans le sous-réseau établi entre le service OVHcloud Connect et le PoP | IP | -| service_uuid | L'UUID du service OVHcloud Connect concerné par l'événement | String | -| timestamp | L'horodatage auquel l'événement a été enregistré | datetime (with millisecond resolution) e.g. 08/Sep/2025:11:35:19.854 | - -## En pratique - -Prenez en compte que l'activation du *forwarding* est gratuite, mais vous serez facturé pour l'utilisation du service Logs Data Platform selon le tarif standard. Pour la tarification du LDP, consultez cette [page](/links/manage-operate/ldp). - -### Activation du Log Forwarding d'OVHcloud Connect via API - -Vous devrez définir le *Stream* ciblé de l’un de vos comptes LDP vers lequel vous souhaitez transférer vos logs. L'activation du *forwarding* va créer un abonnement pour cet ID de flux. - -Vous pouvez récupérer les spécifications de l'API dans le portail [OVH API](/links/api) : - -> [!api] -> -> @api {v1} /dbaas/logs POST /dbaas/logs/{serviceName}/output/graylog/stream -> - -#### Étape 1 - Récupérer le Stream (et l'ID) cible - -Listez les flux de données de votre compte Logs Data Platform (renseignez votre identifiant LDP sous la forme ldp-xx-xxxx dans le champ « serviceName ») : - -> [!api] -> -> @api {v1} /dbaas/logs GET /dbaas/logs/{serviceName}/output/graylog/stream -> - -Obtenez les détails d'un flux de données : - -> [!api] -> -> @api {v1} /dbaas/logs GET /dbaas/logs/{serviceName}/output/graylog/stream/{streamId} -> - -#### Étape 2 - Créez votre abonnement - -Utilisez l'appel API suivant pour créer un abonnement : - -> [!api] -> -> @api {v1} /ovhCloudConnect POST /ovhCloudConnect/{serviceName}/log/subscription -> - -> [!primary] -> Vous devrez remplacer : -> -> - **serviceName** : il s'agit du nom interne de votre service OVHcloud Connect, que vous pouvez retrouver sur la page de gestion du OVHcloud Connect de votre espace client OVHcloud ou en utilisant l'appel API suivant : -> -> > [!api] -> > -> > @api {v1} /ovhCloudConnect GET /ovhCloudConnect -> > -> - -La requête POST a une charge utile qui nécessite : - -- `kind` : le type de journal que vous voulez transférer, parmi "service", "service_configuration", "bgp" et "interface". -- `streamId` : flux de données cible de votre compte LDP vers lequel vous souhaitez que vos logs du service OVHcloud Connect soient transférés. - -> [!primary] -> Vous pouvez trouver les types (`kind`) disponibles en utilisant l'appel API suivant : -> -> > [!api] -> > -> > @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/log/kind -> > -> - -```shell -POST /ovhCloudConnect/{serviceName}/log/subscription -{ - "kind": "string", // "http" or "tcp". - "streamId": "198ef9d5-c320-4000-8bee-236623da5b80" // Le streamID du stream ciblé. -} -``` - -Vous obtiendrez en réponse un `operationId` : - -```shell -{ - "operationId": "f550aa1c-89ab-4b1a-81ae-4fba4959966f", - "serviceName": "occ-xxxxx" -} -``` - -Vous pouvez utiliser le `operationId` pour récupérer le `subscriptionId` à des fins de gestion ultérieure à l'aide de l'appel API suivant : - -> [!api] -> -> @api {v1} /dbaas/logs GET /dbaas/logs/{serviceName}/operation/{operationId} -> - -Une fois l'opération terminée, vous pouvez également récupérer les abonnements à l'aide de l'appel API suivant : - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/log/subscription -> - -Une fois en possession du `subscriptionId`, vous pouvez obtenir les détails via l'appel API suivant : - -> [!api] -> -> @api {v1} /ovhCloudConnect GET /ovhCloudConnect/{serviceName}/log/subscription/{subscriptionId} -> - -```shell -GET /ovhCloudConnect/{serviceName}/log/subscription/{subscriptionId} - -{ -"createdAt": "2025-08-28T07:42:50.645Z", -"kind": "string", -"resource": { - "name": "string", - "type": "string" -}, -"serviceName": "string", -"streamId": "string", -"subscriptionId": "198efa11-f150-4000-8e8d-871b1e482b80", -"updatedAt": "2025-08-28T07:42:50.645Z" -} -``` - -### Comment utiliser les logs OVHcloud Connect ? - -Maintenant que vos logs sont ingérés et stockés dans votre flux de données Logs Data Platform, vous pouvez interroger vos logs et créer des tableaux de bord pour avoir une représentation graphique de vos logs en utilisant l'interface web de Graylog. - -- Dans votre espace client, récupérez le nom d'utilisateur LDP (ex: logs-xxxx) et son mot de passe sur la page d'accueil de votre compte Logs Data Platform. Vous pouvez vous référer au [Guide de démarrage rapide pour Logs Data Platform](/pages/manage_and_operate/observability/logs_data_platform/getting_started_quick_start). -- Ouvrez l'interface utilisateur Graylog. Vous pouvez récupérer le lien sur la page d'accueil de votre compte ou en utilisant votre point d'accès en fonction de la région de votre compte (par exemple : la région de Gravelines est `https://gra1.logs.ovh.com/`). -- Connectez-vous à Graylog en utilisant votre nom d'utilisateur et votre mot de passe Logs Data Platform. -- Parcourez vos logs dans le flux de données de votre compte Logs Data Platform. Vous pouvez consulter la documentation [Graylog writing search queries (EN)](https://go2docs.graylog.org/current/making_sense_of_your_log_data/writing_search_queries.html) pour plus de détails sur la syntaxe de recherche. - -Reportez-vous à la documentation suivante : [Logs Data Platform - Visualizing, querying and exploiting your logs (EN)](/products/observability-logs-data-platform-visualizing-querying-exploiting) pour plus de détails sur l'utilisation de vos logs avec Logs Data Platform, y compris sur la façon de : - -- mettre en place des alertes -- consulter les logs en temps réel via un WebSocket -- créer une visualisation avec les tableaux de bord OpenSearch -- créer une intégration avec l'API OpenSearch -- se connecter avec Grafana - -### Comment gérer vos abonnements ? - -À tout moment, vous pouvez récupérer les abonnements attachés à votre flux Logs Data Platform et choisir de désactiver la redirection en annulant votre abonnement sur votre flux, de sorte que votre flux Logs Data Platform ne reçoive plus vos journaux d'audit. - -Notez que cela ne supprime pas les journaux stockés avant l'annulation de l'abonnement, car les données stockées dans un flux de journal sont immuables, sauf si vous supprimez le flux entier. - -Pour supprimer votre abonnement, vous pouvez utiliser l'appel API suivant : - -> [!api] -> -> @api {v1} /ovhCloudConnect DELETE /ovhCloudConnect/{serviceName}/log/subscription/{subscriptionId} -> - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'assistance technique pour mettre en œuvre nos solutions, contactez votre représentant commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demandez à nos experts Professional Services de vous aider sur votre cas d'utilisation spécifique de votre projet. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.de-de.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.de-de.md deleted file mode 100644 index 2dd58f9580d..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.de-de.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Installation of OVHcloud Connect Provider from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Provider solution via the OVHcloud Control Panel** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Provider solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -### Step 1: Ordering your solution - -Once you have ordered your OVHcloud Connect Provider solution, you will receive an order confirmation via email, along with a service key. - -Depending on the provider you have chosen, go to their portal to log in via the link provided in the order confirmation email. Then enter your service key and confirm the order presented to you. - -Next, check the activation status of your solution. Click on it to confirm that its status has changed to "Active". - -### Step 2: Associating a vRack - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 3: Adding a PoP configuration - -> [!warning] -> The OVHcloud Connect Provider solution requires an L3 level configuration. -> - -Once you have connected your vRack, click the cogwheel button in the `PoP configuration`{.action} section and select the L3 configuration from the drop-down menu. - -![PoP addition](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![PoP addition](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![PoP addition](images/l3pop2.png){.thumbnail} - -### Step 4: Adding an availability zone configuration - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![adding AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the dropdown menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![adding AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![adding AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `...`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add AZ](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add AZ](images/l3dc3.png){.thumbnail} - -If you choose the BGP type, then enter the required information: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnet specified in the `AZ Configuration` menu | - -![add AZ](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Subnetwork | A prefix using CIDR notation | -| Next hop | IP address acting as gateway in the subnet range | - -![add AZ](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same availability zone. - -![add AZ](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or POP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a Routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting an AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepopl3.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-asia.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-asia.md deleted file mode 100644 index 2dd58f9580d..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-asia.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Installation of OVHcloud Connect Provider from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Provider solution via the OVHcloud Control Panel** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Provider solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -### Step 1: Ordering your solution - -Once you have ordered your OVHcloud Connect Provider solution, you will receive an order confirmation via email, along with a service key. - -Depending on the provider you have chosen, go to their portal to log in via the link provided in the order confirmation email. Then enter your service key and confirm the order presented to you. - -Next, check the activation status of your solution. Click on it to confirm that its status has changed to "Active". - -### Step 2: Associating a vRack - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 3: Adding a PoP configuration - -> [!warning] -> The OVHcloud Connect Provider solution requires an L3 level configuration. -> - -Once you have connected your vRack, click the cogwheel button in the `PoP configuration`{.action} section and select the L3 configuration from the drop-down menu. - -![PoP addition](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![PoP addition](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![PoP addition](images/l3pop2.png){.thumbnail} - -### Step 4: Adding an availability zone configuration - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![adding AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the dropdown menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![adding AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![adding AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `...`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add AZ](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add AZ](images/l3dc3.png){.thumbnail} - -If you choose the BGP type, then enter the required information: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnet specified in the `AZ Configuration` menu | - -![add AZ](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Subnetwork | A prefix using CIDR notation | -| Next hop | IP address acting as gateway in the subnet range | - -![add AZ](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same availability zone. - -![add AZ](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or POP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a Routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting an AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepopl3.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-au.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-au.md deleted file mode 100644 index 2dd58f9580d..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-au.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Installation of OVHcloud Connect Provider from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Provider solution via the OVHcloud Control Panel** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Provider solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -### Step 1: Ordering your solution - -Once you have ordered your OVHcloud Connect Provider solution, you will receive an order confirmation via email, along with a service key. - -Depending on the provider you have chosen, go to their portal to log in via the link provided in the order confirmation email. Then enter your service key and confirm the order presented to you. - -Next, check the activation status of your solution. Click on it to confirm that its status has changed to "Active". - -### Step 2: Associating a vRack - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 3: Adding a PoP configuration - -> [!warning] -> The OVHcloud Connect Provider solution requires an L3 level configuration. -> - -Once you have connected your vRack, click the cogwheel button in the `PoP configuration`{.action} section and select the L3 configuration from the drop-down menu. - -![PoP addition](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![PoP addition](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![PoP addition](images/l3pop2.png){.thumbnail} - -### Step 4: Adding an availability zone configuration - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![adding AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the dropdown menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![adding AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![adding AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `...`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add AZ](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add AZ](images/l3dc3.png){.thumbnail} - -If you choose the BGP type, then enter the required information: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnet specified in the `AZ Configuration` menu | - -![add AZ](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Subnetwork | A prefix using CIDR notation | -| Next hop | IP address acting as gateway in the subnet range | - -![add AZ](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same availability zone. - -![add AZ](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or POP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a Routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting an AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepopl3.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-ca.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-ca.md deleted file mode 100644 index 2dd58f9580d..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-ca.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Installation of OVHcloud Connect Provider from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Provider solution via the OVHcloud Control Panel** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Provider solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -### Step 1: Ordering your solution - -Once you have ordered your OVHcloud Connect Provider solution, you will receive an order confirmation via email, along with a service key. - -Depending on the provider you have chosen, go to their portal to log in via the link provided in the order confirmation email. Then enter your service key and confirm the order presented to you. - -Next, check the activation status of your solution. Click on it to confirm that its status has changed to "Active". - -### Step 2: Associating a vRack - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 3: Adding a PoP configuration - -> [!warning] -> The OVHcloud Connect Provider solution requires an L3 level configuration. -> - -Once you have connected your vRack, click the cogwheel button in the `PoP configuration`{.action} section and select the L3 configuration from the drop-down menu. - -![PoP addition](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![PoP addition](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![PoP addition](images/l3pop2.png){.thumbnail} - -### Step 4: Adding an availability zone configuration - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![adding AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the dropdown menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![adding AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![adding AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `...`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add AZ](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add AZ](images/l3dc3.png){.thumbnail} - -If you choose the BGP type, then enter the required information: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnet specified in the `AZ Configuration` menu | - -![add AZ](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Subnetwork | A prefix using CIDR notation | -| Next hop | IP address acting as gateway in the subnet range | - -![add AZ](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same availability zone. - -![add AZ](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or POP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a Routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting an AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepopl3.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-gb.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-gb.md deleted file mode 100644 index 2dd58f9580d..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-gb.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Installation of OVHcloud Connect Provider from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Provider solution via the OVHcloud Control Panel** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Provider solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -### Step 1: Ordering your solution - -Once you have ordered your OVHcloud Connect Provider solution, you will receive an order confirmation via email, along with a service key. - -Depending on the provider you have chosen, go to their portal to log in via the link provided in the order confirmation email. Then enter your service key and confirm the order presented to you. - -Next, check the activation status of your solution. Click on it to confirm that its status has changed to "Active". - -### Step 2: Associating a vRack - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 3: Adding a PoP configuration - -> [!warning] -> The OVHcloud Connect Provider solution requires an L3 level configuration. -> - -Once you have connected your vRack, click the cogwheel button in the `PoP configuration`{.action} section and select the L3 configuration from the drop-down menu. - -![PoP addition](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![PoP addition](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![PoP addition](images/l3pop2.png){.thumbnail} - -### Step 4: Adding an availability zone configuration - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![adding AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the dropdown menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![adding AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![adding AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `...`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add AZ](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add AZ](images/l3dc3.png){.thumbnail} - -If you choose the BGP type, then enter the required information: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnet specified in the `AZ Configuration` menu | - -![add AZ](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Subnetwork | A prefix using CIDR notation | -| Next hop | IP address acting as gateway in the subnet range | - -![add AZ](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same availability zone. - -![add AZ](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or POP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a Routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting an AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepopl3.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-ie.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-ie.md deleted file mode 100644 index 2dd58f9580d..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-ie.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Installation of OVHcloud Connect Provider from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Provider solution via the OVHcloud Control Panel** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Provider solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -### Step 1: Ordering your solution - -Once you have ordered your OVHcloud Connect Provider solution, you will receive an order confirmation via email, along with a service key. - -Depending on the provider you have chosen, go to their portal to log in via the link provided in the order confirmation email. Then enter your service key and confirm the order presented to you. - -Next, check the activation status of your solution. Click on it to confirm that its status has changed to "Active". - -### Step 2: Associating a vRack - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 3: Adding a PoP configuration - -> [!warning] -> The OVHcloud Connect Provider solution requires an L3 level configuration. -> - -Once you have connected your vRack, click the cogwheel button in the `PoP configuration`{.action} section and select the L3 configuration from the drop-down menu. - -![PoP addition](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![PoP addition](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![PoP addition](images/l3pop2.png){.thumbnail} - -### Step 4: Adding an availability zone configuration - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![adding AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the dropdown menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![adding AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![adding AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `...`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add AZ](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add AZ](images/l3dc3.png){.thumbnail} - -If you choose the BGP type, then enter the required information: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnet specified in the `AZ Configuration` menu | - -![add AZ](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Subnetwork | A prefix using CIDR notation | -| Next hop | IP address acting as gateway in the subnet range | - -![add AZ](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same availability zone. - -![add AZ](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or POP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a Routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting an AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepopl3.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-sg.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-sg.md deleted file mode 100644 index 2dd58f9580d..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-sg.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Installation of OVHcloud Connect Provider from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Provider solution via the OVHcloud Control Panel** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Provider solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -### Step 1: Ordering your solution - -Once you have ordered your OVHcloud Connect Provider solution, you will receive an order confirmation via email, along with a service key. - -Depending on the provider you have chosen, go to their portal to log in via the link provided in the order confirmation email. Then enter your service key and confirm the order presented to you. - -Next, check the activation status of your solution. Click on it to confirm that its status has changed to "Active". - -### Step 2: Associating a vRack - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 3: Adding a PoP configuration - -> [!warning] -> The OVHcloud Connect Provider solution requires an L3 level configuration. -> - -Once you have connected your vRack, click the cogwheel button in the `PoP configuration`{.action} section and select the L3 configuration from the drop-down menu. - -![PoP addition](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![PoP addition](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![PoP addition](images/l3pop2.png){.thumbnail} - -### Step 4: Adding an availability zone configuration - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![adding AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the dropdown menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![adding AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![adding AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `...`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add AZ](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add AZ](images/l3dc3.png){.thumbnail} - -If you choose the BGP type, then enter the required information: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnet specified in the `AZ Configuration` menu | - -![add AZ](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Subnetwork | A prefix using CIDR notation | -| Next hop | IP address acting as gateway in the subnet range | - -![add AZ](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same availability zone. - -![add AZ](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or POP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a Routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting an AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepopl3.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-us.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-us.md deleted file mode 100644 index 2dd58f9580d..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.en-us.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Installation of OVHcloud Connect Provider from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Provider solution via the OVHcloud Control Panel** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Provider solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -### Step 1: Ordering your solution - -Once you have ordered your OVHcloud Connect Provider solution, you will receive an order confirmation via email, along with a service key. - -Depending on the provider you have chosen, go to their portal to log in via the link provided in the order confirmation email. Then enter your service key and confirm the order presented to you. - -Next, check the activation status of your solution. Click on it to confirm that its status has changed to "Active". - -### Step 2: Associating a vRack - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 3: Adding a PoP configuration - -> [!warning] -> The OVHcloud Connect Provider solution requires an L3 level configuration. -> - -Once you have connected your vRack, click the cogwheel button in the `PoP configuration`{.action} section and select the L3 configuration from the drop-down menu. - -![PoP addition](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![PoP addition](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![PoP addition](images/l3pop2.png){.thumbnail} - -### Step 4: Adding an availability zone configuration - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![adding AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the dropdown menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![adding AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![adding AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `...`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add AZ](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add AZ](images/l3dc3.png){.thumbnail} - -If you choose the BGP type, then enter the required information: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnet specified in the `AZ Configuration` menu | - -![add AZ](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Subnetwork | A prefix using CIDR notation | -| Next hop | IP address acting as gateway in the subnet range | - -![add AZ](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same availability zone. - -![add AZ](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or POP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a Routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting an AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepopl3.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.es-es.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.es-es.md deleted file mode 100644 index 2dd58f9580d..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.es-es.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Installation of OVHcloud Connect Provider from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Provider solution via the OVHcloud Control Panel** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Provider solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -### Step 1: Ordering your solution - -Once you have ordered your OVHcloud Connect Provider solution, you will receive an order confirmation via email, along with a service key. - -Depending on the provider you have chosen, go to their portal to log in via the link provided in the order confirmation email. Then enter your service key and confirm the order presented to you. - -Next, check the activation status of your solution. Click on it to confirm that its status has changed to "Active". - -### Step 2: Associating a vRack - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 3: Adding a PoP configuration - -> [!warning] -> The OVHcloud Connect Provider solution requires an L3 level configuration. -> - -Once you have connected your vRack, click the cogwheel button in the `PoP configuration`{.action} section and select the L3 configuration from the drop-down menu. - -![PoP addition](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![PoP addition](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![PoP addition](images/l3pop2.png){.thumbnail} - -### Step 4: Adding an availability zone configuration - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![adding AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the dropdown menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![adding AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![adding AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `...`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add AZ](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add AZ](images/l3dc3.png){.thumbnail} - -If you choose the BGP type, then enter the required information: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnet specified in the `AZ Configuration` menu | - -![add AZ](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Subnetwork | A prefix using CIDR notation | -| Next hop | IP address acting as gateway in the subnet range | - -![add AZ](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same availability zone. - -![add AZ](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or POP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a Routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting an AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepopl3.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.es-us.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.es-us.md deleted file mode 100644 index 2f4c3fd6c3a..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.es-us.md +++ /dev/null @@ -1,164 +0,0 @@ ---- -title: Installation of OVHcloud Connect Provider from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Provider solution via the OVHcloud Control Panel** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Provider solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) -- Access to the [OVHcloud Control Panel](/links/manager) - -## Instructions - -### Step 1: Ordering your solution - -Once you have ordered your OVHcloud Connect Provider solution, you will receive an order confirmation via email, along with a service key. - -Depending on the provider you have chosen, go to their portal to log in via the link provided in the order confirmation email. Then enter your service key and confirm the order presented to you. - -Next, check the activation status of your solution in the [OVHcloud Control Panel](/links/manager). To do this, go to the `Bare Metal Cloud`{.action} section and click on `Network`{.action}. Next, open `OVHcloud Connect`{.action} and click on your solution. Your solution's status should have changed to “Active”. - -### Step 2: Associating a vRack - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and click on `Network`{.action}. Next, open `OVHcloud Connect`{.action} and click on your solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 3: Adding a PoP configuration - -> [!warning] -> The OVHcloud Connect Provider solution requires an L3 level configuration. -> - -Once you have connected your vRack, click the cogwheel button in the `PoP configuration`{.action} section and select the L3 configuration from the drop-down menu. - -![PoP addition](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![PoP addition](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![PoP addition](images/l3pop2.png){.thumbnail} - -### Step 4: Adding an availability zone configuration - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![adding AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the dropdown menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![adding AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![adding AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `...`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add AZ](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add AZ](images/l3dc3.png){.thumbnail} - -If you choose the BGP type, then enter the required information: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnet specified in the `AZ Configuration` menu | - -![add AZ](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Subnetwork | A prefix using CIDR notation | -| Next hop | IP address acting as gateway in the subnet range | - -![add AZ](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same availability zone. - -![add AZ](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or POP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a Routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting an AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepopl3.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.fr-ca.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.fr-ca.md deleted file mode 100644 index d95da5231a7..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.fr-ca.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -title: Mise en service de OVHcloud Connect Provider depuis l’espace client OVHcloud -excerpt: Découvrez comment mettre en service votre offre OVHcloud Connect Provider depuis votre espace client OVHcloud -updated: 2025-07-15 ---- - -## Objectif - -OVHcloud Connect permet d’étendre votre réseau d’entreprise avec votre réseau privé OVHcloud vRack sans passer par la création d’un tunnel VPN à travers Internet. Cette connexion sera ainsi plus rapide, plus fiable et avec une bande passante garantie. - -**Ce guide vous présente la mise en service de l'offre OVHcloud Connect Provider depuis l'espace client OVHcloud** - -## Prérequis - -> [!warning] -> Pour assurer un fonctionnement correct de ce service, vous devez prendre connaissance des [capacités et limites techniques de l'offre OVHcloud Connect](/pages/network/ovhcloud_connect/occ-limits) et configurer vos équipements réseau en accord avec celles-ci. -> - -- Avoir commandé une [offre OVHcloud Connect Provider](/links/network/ovhcloud-connect) -- Disposer d'un [vRack OVHcloud](/links/network/vrack) - - ---- - -### Accès à l'espace client OVHcloud - -- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## En pratique - -### Étape 1 : commande de votre offre - -Une fois votre offre OVHcloud Connect Provider commandée, vous recevrez une confirmation de commande par e-mail ainsi qu'une clé de service (ServiceKey). - -Selon le fournisseur que vous avez choisi, rendez-vous ensuite sur le portail de celui-ci pour vous identifier, le lien étant fourni dans l'e-mail de confirmation de commande. -Renseignez alors votre clé de service et validez la commande qui vous sera présentée. - -Vérifiez ensuite le statut d'activation de votre offre : cliquez sur elle pour confirmer que son statut est passé à « Actif ». - -### Étape 2 : associer un vRack - -Cliquez sur votre offre OVHcloud Connect. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -Vous devez commencer par associer un vRack à votre offre. Cliquez sur le bouton `Associer un vRack`{.action} et sélectionnez un vRack existant dans le menu déroulant. - -![associate vRack](images/vrack01.png){.thumbnail} - -Un message vous confirmera l'association du vRack. - -![associate vRack](images/vrack2.png){.thumbnail} - -### Étape 3 : ajouter une configuration PoP - -> [!warning] -> L'offre OVHcloud Connect Provider nécessite une configuration de niveau L3. -> - -Une fois votre vRack associé, cliquez sur `Ajouter une configuration PoP`{.action} et sélectionnez la configuration L3 dans le menu déroulant. - -![ajout Pop](images/pop1.png){.thumbnail} - -Vous devrez alors saisir les éléments suivants : - -| Information | Description | -|:-------:|:------:| -| ASN client | Votre numéro d'AS BGP, qui est configuré sur votre routeur situé dans le PoP | -| ASN OVHcloud | Le numéro d'AS OVHcloud qui sera configuré sur les routeurs de OVHcloud Connect situés dans le PoP | -| Sous-réseau en /30 | Un bloc IPv4 de taille /30, utilisé pour le lien entre votre routeur et le routeur OVHcloud Connect situé dans le PoP | - -![ajout Pop](images/l3pop1-1.png){.thumbnail} - -Le menu `Configuration PoP` apparaîtra alors. - -![ajout Pop](images/l3pop2.png){.thumbnail} - -### Étape 4 : ajout d'une configuration Zone de disponibilité (AZ) - -Lorsque votre configuration PoP a été définie, cliquez sur `Ajouter une configuration`{.action} sous le menu `Configuration AZ`. - -![ajout AZ](images/l3dc0.png){.thumbnail} - -Sélectionnez une zone de disponibilité dans le menu déroulant puis renseignez les informations requises. - -| Information | Description | -|:-------:|:------:| -| ASN OVHcloud | Le numéro d'AS OVHcloud qui sera configuré sur les routeurs OVHcloud Connect situés dans l'AZ. Ce numéro peut être différent de l'ASN choisi pour le PoP | -| Sous-réseau en /28 | Un sous-réseau privé configuré dans votre vRack dans l'AZ sélectionnée. Cela peut être un bloc IPv4 de taille /28 ou supérieur | - -![ajout AZ](images/l3dc1.png){.thumbnail} - -Vous pouvez ajouter des configurations AZ supplémentaires en cliquant sur le bouton `+ Ajouter une configuration`{.action}. - -![ajout AZ](images/l3dc1-1.png){.thumbnail} - -Vous devez également ajouter une configuration de routage. - -##### **Ajout d'une configuration de routage** - -Cliquez sur le bouton `(...)`{.action} sur l'AZ voulue puis sur `Ajouter configuration de routage`{.action}. - -![ajout AZ](images/l3dc2.png){.thumbnail} - -Choisissez alors le type de routage entre « Static » et « BGP ». - -![ajout AZ](images/l3dc3.png){.thumbnail} - -Si vous choisissez le type « BGP », saisissez alors les informations requises : - -| Information | Description | -|:-------:|:------:| -| ASN client | Votre numéro d'AS BGP, qui est configuré sur votre routeur situé dans l'AZ | -| IP Neighbor | Adresse IP du neighbor BGP de votre routeur dans l'AZ. Cette adresse doit faire partie du sous-réseau renseigné dans la `Configuration AZ` | - -![ajout AZ](images/l3dc5.png){.thumbnail} - -Si vous choisissez le type « Static », saisissez les informations requises : - -| Information | Description | -|:-------:|:------:| -| Sous-réseau | Un préfixe utilisant la notation CIDR | -| Nexthop | Adresse IP agissant comme passerelle dans la plage de sous-réseau | - -![ajout AZ](images/l3dc4.png){.thumbnail} - -Vous pouvez ajouter plusieurs configurations de routage au sein d'une même zone de disponibilité. Le type de configuration (BGP ou Static) choisi sur votre première configuration s'appliquera alors aux suivantes sur la même zone de disponibilité. - -![ajout AZ](images/l3dc6.png){.thumbnail} - -### Suppression des ressources - -Chaque ressource (PoP ou AZ) peut être supprimée individuellement, mais la suppression d’une ressource parente telle que AZ ou POP supprimera automatiquement toutes les sous-ressources. - -La suppression récursive est plus lente que la suppression séquentielle de chaque ressource. - -> [!primary] -> Si une configuration AZ est partagée entre au moins deux services OVHcloud Connect, la suppression de la configuration PoP d’un seul service OVHcloud Connect n’affectera pas la ressource AZ. -> - -#### Suppression d'une configuration de routage - -Pour supprimer une configuration de routage, cliquez sur le bouton `(...)`{.action} sur la configuration de routage à supprimer puis sur `Supprimer`{.action}. - -![suppression configuration routage](images/deleterouting.png){.thumbnail} - -#### Suppression d'une configuration AZ - -Pour supprimer une configuration AZ, cliquez sur le bouton `(...)`{.action} sur la configuration AZ à supprimer puis sur `Supprimer`{.action}. - -![suppression configuration DC](images/deletedc.png){.thumbnail} - -> [!primary] -> La suppression d'une configuration AZ entraînera la suppression des configurations de routage liées. -> - -#### Suppression de la configuration PoP - -Pour supprimer une configuration PoP, cliquez sur le bouton `(...)`{.action} sur la configuration PoP puis sur `Supprimer la configuration`{.action}. - -![suppression configuration PoP](images/deletepopl3.png){.thumbnail} - -> [!primary] -> La suppression d'une configuration PoP entraînera la suppression des configurations AZ et de routage. -> - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.fr-fr.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.fr-fr.md deleted file mode 100644 index d95da5231a7..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.fr-fr.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -title: Mise en service de OVHcloud Connect Provider depuis l’espace client OVHcloud -excerpt: Découvrez comment mettre en service votre offre OVHcloud Connect Provider depuis votre espace client OVHcloud -updated: 2025-07-15 ---- - -## Objectif - -OVHcloud Connect permet d’étendre votre réseau d’entreprise avec votre réseau privé OVHcloud vRack sans passer par la création d’un tunnel VPN à travers Internet. Cette connexion sera ainsi plus rapide, plus fiable et avec une bande passante garantie. - -**Ce guide vous présente la mise en service de l'offre OVHcloud Connect Provider depuis l'espace client OVHcloud** - -## Prérequis - -> [!warning] -> Pour assurer un fonctionnement correct de ce service, vous devez prendre connaissance des [capacités et limites techniques de l'offre OVHcloud Connect](/pages/network/ovhcloud_connect/occ-limits) et configurer vos équipements réseau en accord avec celles-ci. -> - -- Avoir commandé une [offre OVHcloud Connect Provider](/links/network/ovhcloud-connect) -- Disposer d'un [vRack OVHcloud](/links/network/vrack) - - ---- - -### Accès à l'espace client OVHcloud - -- **Lien direct :** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Pour accéder à vos services :** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## En pratique - -### Étape 1 : commande de votre offre - -Une fois votre offre OVHcloud Connect Provider commandée, vous recevrez une confirmation de commande par e-mail ainsi qu'une clé de service (ServiceKey). - -Selon le fournisseur que vous avez choisi, rendez-vous ensuite sur le portail de celui-ci pour vous identifier, le lien étant fourni dans l'e-mail de confirmation de commande. -Renseignez alors votre clé de service et validez la commande qui vous sera présentée. - -Vérifiez ensuite le statut d'activation de votre offre : cliquez sur elle pour confirmer que son statut est passé à « Actif ». - -### Étape 2 : associer un vRack - -Cliquez sur votre offre OVHcloud Connect. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -Vous devez commencer par associer un vRack à votre offre. Cliquez sur le bouton `Associer un vRack`{.action} et sélectionnez un vRack existant dans le menu déroulant. - -![associate vRack](images/vrack01.png){.thumbnail} - -Un message vous confirmera l'association du vRack. - -![associate vRack](images/vrack2.png){.thumbnail} - -### Étape 3 : ajouter une configuration PoP - -> [!warning] -> L'offre OVHcloud Connect Provider nécessite une configuration de niveau L3. -> - -Une fois votre vRack associé, cliquez sur `Ajouter une configuration PoP`{.action} et sélectionnez la configuration L3 dans le menu déroulant. - -![ajout Pop](images/pop1.png){.thumbnail} - -Vous devrez alors saisir les éléments suivants : - -| Information | Description | -|:-------:|:------:| -| ASN client | Votre numéro d'AS BGP, qui est configuré sur votre routeur situé dans le PoP | -| ASN OVHcloud | Le numéro d'AS OVHcloud qui sera configuré sur les routeurs de OVHcloud Connect situés dans le PoP | -| Sous-réseau en /30 | Un bloc IPv4 de taille /30, utilisé pour le lien entre votre routeur et le routeur OVHcloud Connect situé dans le PoP | - -![ajout Pop](images/l3pop1-1.png){.thumbnail} - -Le menu `Configuration PoP` apparaîtra alors. - -![ajout Pop](images/l3pop2.png){.thumbnail} - -### Étape 4 : ajout d'une configuration Zone de disponibilité (AZ) - -Lorsque votre configuration PoP a été définie, cliquez sur `Ajouter une configuration`{.action} sous le menu `Configuration AZ`. - -![ajout AZ](images/l3dc0.png){.thumbnail} - -Sélectionnez une zone de disponibilité dans le menu déroulant puis renseignez les informations requises. - -| Information | Description | -|:-------:|:------:| -| ASN OVHcloud | Le numéro d'AS OVHcloud qui sera configuré sur les routeurs OVHcloud Connect situés dans l'AZ. Ce numéro peut être différent de l'ASN choisi pour le PoP | -| Sous-réseau en /28 | Un sous-réseau privé configuré dans votre vRack dans l'AZ sélectionnée. Cela peut être un bloc IPv4 de taille /28 ou supérieur | - -![ajout AZ](images/l3dc1.png){.thumbnail} - -Vous pouvez ajouter des configurations AZ supplémentaires en cliquant sur le bouton `+ Ajouter une configuration`{.action}. - -![ajout AZ](images/l3dc1-1.png){.thumbnail} - -Vous devez également ajouter une configuration de routage. - -##### **Ajout d'une configuration de routage** - -Cliquez sur le bouton `(...)`{.action} sur l'AZ voulue puis sur `Ajouter configuration de routage`{.action}. - -![ajout AZ](images/l3dc2.png){.thumbnail} - -Choisissez alors le type de routage entre « Static » et « BGP ». - -![ajout AZ](images/l3dc3.png){.thumbnail} - -Si vous choisissez le type « BGP », saisissez alors les informations requises : - -| Information | Description | -|:-------:|:------:| -| ASN client | Votre numéro d'AS BGP, qui est configuré sur votre routeur situé dans l'AZ | -| IP Neighbor | Adresse IP du neighbor BGP de votre routeur dans l'AZ. Cette adresse doit faire partie du sous-réseau renseigné dans la `Configuration AZ` | - -![ajout AZ](images/l3dc5.png){.thumbnail} - -Si vous choisissez le type « Static », saisissez les informations requises : - -| Information | Description | -|:-------:|:------:| -| Sous-réseau | Un préfixe utilisant la notation CIDR | -| Nexthop | Adresse IP agissant comme passerelle dans la plage de sous-réseau | - -![ajout AZ](images/l3dc4.png){.thumbnail} - -Vous pouvez ajouter plusieurs configurations de routage au sein d'une même zone de disponibilité. Le type de configuration (BGP ou Static) choisi sur votre première configuration s'appliquera alors aux suivantes sur la même zone de disponibilité. - -![ajout AZ](images/l3dc6.png){.thumbnail} - -### Suppression des ressources - -Chaque ressource (PoP ou AZ) peut être supprimée individuellement, mais la suppression d’une ressource parente telle que AZ ou POP supprimera automatiquement toutes les sous-ressources. - -La suppression récursive est plus lente que la suppression séquentielle de chaque ressource. - -> [!primary] -> Si une configuration AZ est partagée entre au moins deux services OVHcloud Connect, la suppression de la configuration PoP d’un seul service OVHcloud Connect n’affectera pas la ressource AZ. -> - -#### Suppression d'une configuration de routage - -Pour supprimer une configuration de routage, cliquez sur le bouton `(...)`{.action} sur la configuration de routage à supprimer puis sur `Supprimer`{.action}. - -![suppression configuration routage](images/deleterouting.png){.thumbnail} - -#### Suppression d'une configuration AZ - -Pour supprimer une configuration AZ, cliquez sur le bouton `(...)`{.action} sur la configuration AZ à supprimer puis sur `Supprimer`{.action}. - -![suppression configuration DC](images/deletedc.png){.thumbnail} - -> [!primary] -> La suppression d'une configuration AZ entraînera la suppression des configurations de routage liées. -> - -#### Suppression de la configuration PoP - -Pour supprimer une configuration PoP, cliquez sur le bouton `(...)`{.action} sur la configuration PoP puis sur `Supprimer la configuration`{.action}. - -![suppression configuration PoP](images/deletepopl3.png){.thumbnail} - -> [!primary] -> La suppression d'une configuration PoP entraînera la suppression des configurations AZ et de routage. -> - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.it-it.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.it-it.md deleted file mode 100644 index 2dd58f9580d..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.it-it.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Installation of OVHcloud Connect Provider from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Provider solution via the OVHcloud Control Panel** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Provider solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -### Step 1: Ordering your solution - -Once you have ordered your OVHcloud Connect Provider solution, you will receive an order confirmation via email, along with a service key. - -Depending on the provider you have chosen, go to their portal to log in via the link provided in the order confirmation email. Then enter your service key and confirm the order presented to you. - -Next, check the activation status of your solution. Click on it to confirm that its status has changed to "Active". - -### Step 2: Associating a vRack - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 3: Adding a PoP configuration - -> [!warning] -> The OVHcloud Connect Provider solution requires an L3 level configuration. -> - -Once you have connected your vRack, click the cogwheel button in the `PoP configuration`{.action} section and select the L3 configuration from the drop-down menu. - -![PoP addition](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![PoP addition](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![PoP addition](images/l3pop2.png){.thumbnail} - -### Step 4: Adding an availability zone configuration - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![adding AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the dropdown menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![adding AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![adding AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `...`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add AZ](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add AZ](images/l3dc3.png){.thumbnail} - -If you choose the BGP type, then enter the required information: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnet specified in the `AZ Configuration` menu | - -![add AZ](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Subnetwork | A prefix using CIDR notation | -| Next hop | IP address acting as gateway in the subnet range | - -![add AZ](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same availability zone. - -![add AZ](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or POP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a Routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting an AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepopl3.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.pl-pl.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.pl-pl.md deleted file mode 100644 index 2dd58f9580d..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.pl-pl.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Installation of OVHcloud Connect Provider from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Provider solution via the OVHcloud Control Panel** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Provider solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -### Step 1: Ordering your solution - -Once you have ordered your OVHcloud Connect Provider solution, you will receive an order confirmation via email, along with a service key. - -Depending on the provider you have chosen, go to their portal to log in via the link provided in the order confirmation email. Then enter your service key and confirm the order presented to you. - -Next, check the activation status of your solution. Click on it to confirm that its status has changed to "Active". - -### Step 2: Associating a vRack - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 3: Adding a PoP configuration - -> [!warning] -> The OVHcloud Connect Provider solution requires an L3 level configuration. -> - -Once you have connected your vRack, click the cogwheel button in the `PoP configuration`{.action} section and select the L3 configuration from the drop-down menu. - -![PoP addition](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![PoP addition](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![PoP addition](images/l3pop2.png){.thumbnail} - -### Step 4: Adding an availability zone configuration - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![adding AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the dropdown menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![adding AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![adding AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `...`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add AZ](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add AZ](images/l3dc3.png){.thumbnail} - -If you choose the BGP type, then enter the required information: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnet specified in the `AZ Configuration` menu | - -![add AZ](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Subnetwork | A prefix using CIDR notation | -| Next hop | IP address acting as gateway in the subnet range | - -![add AZ](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same availability zone. - -![add AZ](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or POP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a Routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting an AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepopl3.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.pt-pt.md b/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.pt-pt.md deleted file mode 100644 index 2dd58f9580d..00000000000 --- a/pages/network/ovhcloud_connect/occ-provider-control-panel/guide.pt-pt.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Installation of OVHcloud Connect Provider from the OVHcloud Control Panel -excerpt: Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel -updated: 2025-07-15 ---- - -## Objective - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -**This guide will show you how to set up the OVHcloud Connect Provider solution via the OVHcloud Control Panel** - -## Requirements - -> [!warning] -> To ensure correct operation of this service, you must be aware of the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) and configure your network devices accordingly. -> - -- An [OVHcloud Connect Provider solution](/links/network/ovhcloud-connect) -- An OVHcloud [vRack](/links/network/vrack) - - ---- - -### OVHcloud Control Panel Access - -- **Direct link:** [OVHcloud Connect](/links/control-panel/network-ovhcloud-connect) -- **Navigation path:** `Network`{.action} > `OVHcloud Connect`{.action} - ---- - -## Instructions - -### Step 1: Ordering your solution - -Once you have ordered your OVHcloud Connect Provider solution, you will receive an order confirmation via email, along with a service key. - -Depending on the provider you have chosen, go to their portal to log in via the link provided in the order confirmation email. Then enter your service key and confirm the order presented to you. - -Next, check the activation status of your solution. Click on it to confirm that its status has changed to "Active". - -### Step 2: Associating a vRack - -Click on your OVHcloud Connect solution. - -![ovhcloud connect selection](images/occ_01.png){.thumbnail} - -You will need to link a vRack to your solution first. Click the `Attach a vRack`{.action} button and select an existing vRack from the drop-down menu. - -![vRack association](images/vrack01.png){.thumbnail} - -A message will confirm the vRack association. - -![vRack association](images/vrack2.png){.thumbnail} - -### Step 3: Adding a PoP configuration - -> [!warning] -> The OVHcloud Connect Provider solution requires an L3 level configuration. -> - -Once you have connected your vRack, click the cogwheel button in the `PoP configuration`{.action} section and select the L3 configuration from the drop-down menu. - -![PoP addition](images/pop1.png){.thumbnail} - -You will then need to enter the following: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the PoP | -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the PoP | -| Subnetwork in /30 | A size /30 IPv4 block, used for the link between your router and the OVHcloud Connect router located in the PoP | - -![PoP addition](images/l3pop1-1.png){.thumbnail} - -The `PoP configuration` menu will then appear. - -![PoP addition](images/l3pop2.png){.thumbnail} - -### Step 4: Adding an availability zone configuration - -When your PoP configuration has been set, click `Add a configuration`{.action} under the `AZ configuration` menu. - -![adding AZ](images/l3dc0.png){.thumbnail} - -Select an availability zone from the dropdown menu, then enter the information required. - -| Information | Description | -|:-------:|:------:| -| OVHcloud ASN | The OVHcloud AS number that will be configured on the OVHcloud Connect routers located in the AZ. This number may be different from the ASN chosen for the PoP | -| A /28 subnetwork | A private subnetwork configured in your vRack in the selected AZ. This can be an IPv4 block of size /28 or higher | - -![adding AZ](images/l3dc1.png){.thumbnail} - -You can add additional availability zone configurations by clicking on the `+ Add a configuration`{.action} button. - -![adding AZ](images/l3dc1-1.png){.thumbnail} - -You must also add a routing configuration. - -##### **Adding a routing configuration** - -Click on the `...`{.action} button on the desired availability zone then on `Add routing configuration`{.action}. - -![add AZ](images/l3dc2.png){.thumbnail} - -Then choose the routing type between Static and BGP. - -![add AZ](images/l3dc3.png){.thumbnail} - -If you choose the BGP type, then enter the required information: - -| Information | Description | -|:-------:|:------:| -| Customer ASN | Your AS BGP number, which is configured on your router located in the AZ | -| IP Neighbour | IP address of the BGP neighbour of your router in the AZ. This address must be part of the subnet specified in the `AZ Configuration` menu | - -![add AZ](images/l3dc5.png){.thumbnail} - -If you choose the Static type, enter the required information: - -| Information | Description | -|:-------:|:------:| -| Subnetwork | A prefix using CIDR notation | -| Next hop | IP address acting as gateway in the subnet range | - -![add AZ](images/l3dc4.png){.thumbnail} - -You can add multiple routing configurations within the same availability zone. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same availability zone. - -![add AZ](images/l3dc6.png){.thumbnail} - -### Deletion of vCenter resources - -Each resource (PoP or AZ) can be deleted individually, but deleting a parent resource such as AZ or POP will automatically delete all the subresources. - -Recursive removal is slower than sequential removal of each resource. - -> [!primary] -> If a AZ configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the AZ resource. -> - -#### Deleting a Routing Configuration - -To delete a routing configuration, click the `...`{.action} button on the routing configuration to delete, then click `Delete`{.action}. - -![deleting routing configuration](images/deleterouting.png){.thumbnail} - -#### Deleting a AZ configuration - -To delete a AZ configuration, click the `...`{.action} button on the AZ configuration to delete, then click `Delete`{.action}. - -![DC deletion](images/deletedc.png){.thumbnail} - -> [!primary] -> Deleting an AZ configuration will delete the related routing configurations. -> - -#### Deleting a PoP configuration - -To delete a PoP configuration, click the `...`{.action} button on the PoP configuration, then click `Delete configuration`{.action}. - -![deleting PoP configuration](images/deletepopl3.png){.thumbnail} - -> [!primary] -> Deleting a PoP configuration will delete the AZ and routing configurations. -> - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our [community of users](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/deletedc.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/deletedc.png deleted file mode 100644 index a67ef16533f..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/deletedc.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/deletepopl3.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/deletepopl3.png deleted file mode 100644 index f72091af051..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/deletepopl3.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/deleterouting.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/deleterouting.png deleted file mode 100644 index e81ce8472b8..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/deleterouting.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc0.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc0.png deleted file mode 100644 index 0f41d687669..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc0.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc1-1.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc1-1.png deleted file mode 100644 index 39c3a93d016..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc1-1.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc1.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc1.png deleted file mode 100644 index a339eb59a37..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc1.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc2.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc2.png deleted file mode 100644 index 344db725880..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc2.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc3.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc3.png deleted file mode 100644 index 52eb63d5b5e..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc3.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc4.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc4.png deleted file mode 100644 index 0889754d659..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc4.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc5.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc5.png deleted file mode 100644 index 71dcb9cf158..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc5.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc6.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc6.png deleted file mode 100644 index 467788ced39..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3dc6.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3pop1-1.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3pop1-1.png deleted file mode 100644 index 34b8c4ab655..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3pop1-1.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3pop2.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3pop2.png deleted file mode 100644 index dcbf5565784..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/l3pop2.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/occ_01.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/occ_01.png deleted file mode 100644 index 2465d4aeaee..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/occ_01.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/pop1.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/pop1.png deleted file mode 100644 index 3a039fa0dca..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/pop1.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/vrack01.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/vrack01.png deleted file mode 100644 index 78c56edf1dc..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/vrack01.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/vrack2.png b/pages/network/ovhcloud_connect/occ-provider-control-panel/images/vrack2.png deleted file mode 100644 index 2ed3acd7aee..00000000000 Binary files a/pages/network/ovhcloud_connect/occ-provider-control-panel/images/vrack2.png and /dev/null differ diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.de-de.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.de-de.md deleted file mode 100644 index 550d9407b9f..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.de-de.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: Troubleshooting common errors setting up OVHcloud Connect -excerpt: Find out how to resolve the most common errors associated with setting up OVHcloud Connect -updated: 2021-09-02 ---- - -## Objective - -Find out how to resolve the most common errors associated with setting up OVHcloud Connect - -## Requirements - -- an [OVHcloud Connect solution](https://www.ovhcloud.com/de/network-security/ovhcloud-connect/) - -## Instructions - -An OVHcloud Connect service will appear in your OVHcloud Control Panel, and can only be configured when it is considered **delivered**. - -For the **OVHcloud Connect Direct** offer, the service is **delivered** in the following situations: - -- When OVHcloud detects light at the position indicated in the LOA. This detection suggests that the cross-connect was performed by the client. -- 60 days after the order if no light has been detected. - -### LOA verification - -A misinterpretation of the position on the Cross-Connect by the PoP can result in a lack of light on the OVHcloud Connect link. -For example, the PoP may indicate that there is no interconnection at the position mentioned on the LOA. - -#### How to read LOA information? - -Here is an example of information on the LOA: - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -This information is interpreted as follows: - -- Cabinet (position of the bay where the RACK is located): **103** -- Cage (RACK): **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (switch position): **PP:0103:1132697** -- Position (on switch): **16** -- FiberOptic / Port A: **31** -- FiberOptic / Port B: **32** -- Side (front or back): **BACK** -- Fiber Termination: **SC/PC** - -### OVHcloud Connect Direct (only): checking for light on the link - -> [!warning] -> -> - As a reminder, Cross-Connect is contractually your responsibility. -> - Before contacting the OVHcloud teams, you will need to open a ticket to the PoP concerned by the LOA. -> - -#### Before service delivery - -When you order an OVHcloud Connect link, the IN/OUT optical values can be checked on the OVHcloud side. You can request information about this from your support team. - -If the service has not yet been delivered, our support teams will be able to check the status of the IN and OUT optical values on the OVHcloud infrastructure side. - -#### After service delivery - -In the OVHcloud Control Panel, check the IN/OUT optical values: - -- If the **OUT** value is **DOWN**, , the following reasons may be the cause: - - the port on the OVHcloud side does not emit light - - the service is being cancelled - - the port is locked in your OVHcloud Control Panel - - there is an SFP issue -- If **IN** is **DOWN**, the following reasons may be the cause: - - your equipment is not yet connected - - the port can be disabled or has a defect that prevents it from emitting light - - there is a Cross-Connect issue - -### Tx/Rx Fiber inversion - -If there is a fiber inversion between Port A and Port B, the light is not received in the right place and the **IN (Rx)** port will display **DOWN**. If your service has not yet been delivered, contact the support teams so that the link status is checked. - -Contact the PoP concerned by the LOA to check that there is no Tx/Rx inversion on the Cross-Connect. - -### Peering verification - -The peering should be checked once the light is **UP** on both sides. - -If peering cannot be established (DOWN) on one or both sides, there may be several reasons: - -- An SFP issue -- Auto-negotiation is not disabled on the customer side -- IP address conflict -- BGP link misconfiguration - -#### SFP Configuration - -Optical values **UP** but no Ethernet link (interface **DOWN**) are a symptom of a misconfigured SFP. - -The SFP to use on the client device on an OVHcloud Connect link depends on the link you ordered. You must use an SFP that conforms to the ordered bandwidth. - -If you have ordered a 1 Gbps link, the SFP will be: 1000Base-LX/LH. - -``` -speed 1000 -``` - -If you have ordered a 10 Gbps link, the SFP will be: 10GBase-LR. - -``` -speed 10000 -``` - -For more information, please read the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) - -#### Disabling auto-negotiation - -Auto-negotiation is not supported in the OVHcloud Connect solution. This setting must be disabled. - -To disable auto-negotiation on a Cisco device, use the following command: - -``` -no negotiate auto -``` - -or - -``` -no speed negotiate -``` - -On Cisco IOS, use the following command: - -``` -speed nonegotiate -``` - -On Cisco NX-OS, use the following command: - -``` -speed 1000 -no negotiate auto -``` - -#### PoP/DC configuration - -An IP address conflict may occur if you are using an IP address(es) normally reserved for OVHcloud. - -The rules for assigning IP addresses according to the subnet are as follows: - -- DC-side subnet: /28 (minimum value) - The first three IP addresses are reserved for OVHcloud - Vlan fixed to 0 (untagged). -- PoP-side subnet: /30 (fixed value) - The first IP address is reserved for OVHcloud, the second IP address for the customer. - -#### Configuring the BGP link - -The BGP Area on the customer side must be different from the OVHcloud side. - -- Range Area = AS BGP -- AS number: We recommend ASNs between 64512 and 65534. The choice is your, with the exception of the following numbers, which are reserved for OVHcloud. - - 65501 if the PoP is in Europe - - 65502 if the PoP is in Canada - - 65519 if the PoP is in Asia -- The OVHcloud BGP AS zone and your BGP AS number (on the PoP side) must be different. -- The OVHcloud BGP AS zone: can be the same between the DC side and the PoP side configuration (recommended) - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-asia.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-asia.md deleted file mode 100644 index 9ac646d3983..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-asia.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: Troubleshooting common errors setting up OVHcloud Connect -excerpt: Find out how to resolve the most common errors associated with setting up OVHcloud Connect -updated: 2021-09-02 ---- - -## Objective - -Find out how to resolve the most common errors associated with setting up OVHcloud Connect - -## Requirements - -- an [OVHcloud Connect solution](https://www.ovhcloud.com/asia/network-security/ovhcloud-connect/) - -## Instructions - -An OVHcloud Connect service will appear in your OVHcloud Control Panel, and can only be configured when it is considered **delivered**. - -For the **OVHcloud Connect Direct** offer, the service is **delivered** in the following situations: - -- When OVHcloud detects light at the position indicated in the LOA. This detection suggests that the cross-connect was performed by the client. -- 60 days after the order if no light has been detected. - -### LOA verification - -A misinterpretation of the position on the Cross-Connect by the PoP can result in a lack of light on the OVHcloud Connect link. -For example, the PoP may indicate that there is no interconnection at the position mentioned on the LOA. - -#### How to read LOA information? - -Here is an example of information on the LOA: - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -This information is interpreted as follows: - -- Cabinet (position of the bay where the RACK is located): **103** -- Cage (RACK): **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (switch position): **PP:0103:1132697** -- Position (on switch): **16** -- FiberOptic / Port A: **31** -- FiberOptic / Port B: **32** -- Side (front or back): **BACK** -- Fiber Termination: **SC/PC** - -### OVHcloud Connect Direct (only): checking for light on the link - -> [!warning] -> -> - As a reminder, Cross-Connect is contractually your responsibility. -> - Before contacting the OVHcloud teams, you will need to open a ticket to the PoP concerned by the LOA. -> - -#### Before service delivery - -When you order an OVHcloud Connect link, the IN/OUT optical values can be checked on the OVHcloud side. You can request information about this from your support team. - -If the service has not yet been delivered, our support teams will be able to check the status of the IN and OUT optical values on the OVHcloud infrastructure side. - -#### After service delivery - -In the OVHcloud Control Panel, check the IN/OUT optical values: - -- If the **OUT** value is **DOWN**, , the following reasons may be the cause: - - the port on the OVHcloud side does not emit light - - the service is being cancelled - - the port is locked in your OVHcloud Control Panel - - there is an SFP issue -- If **IN** is **DOWN**, the following reasons may be the cause: - - your equipment is not yet connected - - the port can be disabled or has a defect that prevents it from emitting light - - there is a Cross-Connect issue - -### Tx/Rx Fiber inversion - -If there is a fiber inversion between Port A and Port B, the light is not received in the right place and the **IN (Rx)** port will display **DOWN**. If your service has not yet been delivered, contact the support teams so that the link status is checked. - -Contact the PoP concerned by the LOA to check that there is no Tx/Rx inversion on the Cross-Connect. - -### Peering verification - -The peering should be checked once the light is **UP** on both sides. - -If peering cannot be established (DOWN) on one or both sides, there may be several reasons: - -- An SFP issue -- Auto-negotiation is not disabled on the customer side -- IP address conflict -- BGP link misconfiguration - -#### SFP Configuration - -Optical values **UP** but no Ethernet link (interface **DOWN**) are a symptom of a misconfigured SFP. - -The SFP to use on the client device on an OVHcloud Connect link depends on the link you ordered. You must use an SFP that conforms to the ordered bandwidth. - -If you have ordered a 1 Gbps link, the SFP will be: 1000Base-LX/LH. - -``` -speed 1000 -``` - -If you have ordered a 10 Gbps link, the SFP will be: 10GBase-LR. - -``` -speed 10000 -``` - -For more information, please read the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) - -#### Disabling auto-negotiation - -Auto-negotiation is not supported in the OVHcloud Connect solution. This setting must be disabled. - -To disable auto-negotiation on a Cisco device, use the following command: - -``` -no negotiate auto -``` - -or - -``` -no speed negotiate -``` - -On Cisco IOS, use the following command: - -``` -speed nonegotiate -``` - -On Cisco NX-OS, use the following command: - -``` -speed 1000 -no negotiate auto -``` - -#### PoP/DC configuration - -An IP address conflict may occur if you are using an IP address(es) normally reserved for OVHcloud. - -The rules for assigning IP addresses according to the subnet are as follows: - -- DC-side subnet: /28 (minimum value) - The first three IP addresses are reserved for OVHcloud - Vlan fixed to 0 (untagged). -- PoP-side subnet: /30 (fixed value) - The first IP address is reserved for OVHcloud, the second IP address for the customer. - -#### Configuring the BGP link - -The BGP Area on the customer side must be different from the OVHcloud side. - -- Range Area = AS BGP -- AS number: We recommend ASNs between 64512 and 65534. The choice is your, with the exception of the following numbers, which are reserved for OVHcloud. - - 65501 if the PoP is in Europe - - 65502 if the PoP is in Canada - - 65519 if the PoP is in Asia -- The OVHcloud BGP AS zone and your BGP AS number (on the PoP side) must be different. -- The OVHcloud BGP AS zone: can be the same between the DC side and the PoP side configuration (recommended) - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-au.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-au.md deleted file mode 100644 index 65ecda9442c..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-au.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: Troubleshooting common errors setting up OVHcloud Connect -excerpt: Find out how to resolve the most common errors associated with setting up OVHcloud Connect -updated: 2021-09-02 ---- - -## Objective - -Find out how to resolve the most common errors associated with setting up OVHcloud Connect - -## Requirements - -- an [OVHcloud Connect solution](https://www.ovhcloud.com/en-au/network-security/ovhcloud-connect/) - -## Instructions - -An OVHcloud Connect service will appear in your OVHcloud Control Panel, and can only be configured when it is considered **delivered**. - -For the **OVHcloud Connect Direct** offer, the service is **delivered** in the following situations: - -- When OVHcloud detects light at the position indicated in the LOA. This detection suggests that the cross-connect was performed by the client. -- 60 days after the order if no light has been detected. - -### LOA verification - -A misinterpretation of the position on the Cross-Connect by the PoP can result in a lack of light on the OVHcloud Connect link. -For example, the PoP may indicate that there is no interconnection at the position mentioned on the LOA. - -#### How to read LOA information? - -Here is an example of information on the LOA: - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -This information is interpreted as follows: - -- Cabinet (position of the bay where the RACK is located): **103** -- Cage (RACK): **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (switch position): **PP:0103:1132697** -- Position (on switch): **16** -- FiberOptic / Port A: **31** -- FiberOptic / Port B: **32** -- Side (front or back): **BACK** -- Fiber Termination: **SC/PC** - -### OVHcloud Connect Direct (only): checking for light on the link - -> [!warning] -> -> - As a reminder, Cross-Connect is contractually your responsibility. -> - Before contacting the OVHcloud teams, you will need to open a ticket to the PoP concerned by the LOA. -> - -#### Before service delivery - -When you order an OVHcloud Connect link, the IN/OUT optical values can be checked on the OVHcloud side. You can request information about this from your support team. - -If the service has not yet been delivered, our support teams will be able to check the status of the IN and OUT optical values on the OVHcloud infrastructure side. - -#### After service delivery - -In the OVHcloud Control Panel, check the IN/OUT optical values: - -- If the **OUT** value is **DOWN**, , the following reasons may be the cause: - - the port on the OVHcloud side does not emit light - - the service is being cancelled - - the port is locked in your OVHcloud Control Panel - - there is an SFP issue -- If **IN** is **DOWN**, the following reasons may be the cause: - - your equipment is not yet connected - - the port can be disabled or has a defect that prevents it from emitting light - - there is a Cross-Connect issue - -### Tx/Rx Fiber inversion - -If there is a fiber inversion between Port A and Port B, the light is not received in the right place and the **IN (Rx)** port will display **DOWN**. If your service has not yet been delivered, contact the support teams so that the link status is checked. - -Contact the PoP concerned by the LOA to check that there is no Tx/Rx inversion on the Cross-Connect. - -### Peering verification - -The peering should be checked once the light is **UP** on both sides. - -If peering cannot be established (DOWN) on one or both sides, there may be several reasons: - -- An SFP issue -- Auto-negotiation is not disabled on the customer side -- IP address conflict -- BGP link misconfiguration - -#### SFP Configuration - -Optical values **UP** but no Ethernet link (interface **DOWN**) are a symptom of a misconfigured SFP. - -The SFP to use on the client device on an OVHcloud Connect link depends on the link you ordered. You must use an SFP that conforms to the ordered bandwidth. - -If you have ordered a 1 Gbps link, the SFP will be: 1000Base-LX/LH. - -``` -speed 1000 -``` - -If you have ordered a 10 Gbps link, the SFP will be: 10GBase-LR. - -``` -speed 10000 -``` - -For more information, please read the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) - -#### Disabling auto-negotiation - -Auto-negotiation is not supported in the OVHcloud Connect solution. This setting must be disabled. - -To disable auto-negotiation on a Cisco device, use the following command: - -``` -no negotiate auto -``` - -or - -``` -no speed negotiate -``` - -On Cisco IOS, use the following command: - -``` -speed nonegotiate -``` - -On Cisco NX-OS, use the following command: - -``` -speed 1000 -no negotiate auto -``` - -#### PoP/DC configuration - -An IP address conflict may occur if you are using an IP address(es) normally reserved for OVHcloud. - -The rules for assigning IP addresses according to the subnet are as follows: - -- DC-side subnet: /28 (minimum value) - The first three IP addresses are reserved for OVHcloud - Vlan fixed to 0 (untagged). -- PoP-side subnet: /30 (fixed value) - The first IP address is reserved for OVHcloud, the second IP address for the customer. - -#### Configuring the BGP link - -The BGP Area on the customer side must be different from the OVHcloud side. - -- Range Area = AS BGP -- AS number: We recommend ASNs between 64512 and 65534. The choice is your, with the exception of the following numbers, which are reserved for OVHcloud. - - 65501 if the PoP is in Europe - - 65502 if the PoP is in Canada - - 65519 if the PoP is in Asia -- The OVHcloud BGP AS zone and your BGP AS number (on the PoP side) must be different. -- The OVHcloud BGP AS zone: can be the same between the DC side and the PoP side configuration (recommended) - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-ca.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-ca.md deleted file mode 100644 index 84e10e037bc..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-ca.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: Troubleshooting common errors setting up OVHcloud Connect -excerpt: Find out how to resolve the most common errors associated with setting up OVHcloud Connect -updated: 2021-09-02 ---- - -## Objective - -Find out how to resolve the most common errors associated with setting up OVHcloud Connect - -## Requirements - -- an [OVHcloud Connect solution](https://www.ovhcloud.com/en-ca/network-security/ovhcloud-connect/) - -## Instructions - -An OVHcloud Connect service will appear in your OVHcloud Control Panel, and can only be configured when it is considered **delivered**. - -For the **OVHcloud Connect Direct** offer, the service is **delivered** in the following situations: - -- When OVHcloud detects light at the position indicated in the LOA. This detection suggests that the cross-connect was performed by the client. -- 60 days after the order if no light has been detected. - -### LOA verification - -A misinterpretation of the position on the Cross-Connect by the PoP can result in a lack of light on the OVHcloud Connect link. -For example, the PoP may indicate that there is no interconnection at the position mentioned on the LOA. - -#### How to read LOA information? - -Here is an example of information on the LOA: - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -This information is interpreted as follows: - -- Cabinet (position of the bay where the RACK is located): **103** -- Cage (RACK): **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (switch position): **PP:0103:1132697** -- Position (on switch): **16** -- FiberOptic / Port A: **31** -- FiberOptic / Port B: **32** -- Side (front or back): **BACK** -- Fiber Termination: **SC/PC** - -### OVHcloud Connect Direct (only): checking for light on the link - -> [!warning] -> -> - As a reminder, Cross-Connect is contractually your responsibility. -> - Before contacting the OVHcloud teams, you will need to open a ticket to the PoP concerned by the LOA. -> - -#### Before service delivery - -When you order an OVHcloud Connect link, the IN/OUT optical values can be checked on the OVHcloud side. You can request information about this from your support team. - -If the service has not yet been delivered, our support teams will be able to check the status of the IN and OUT optical values on the OVHcloud infrastructure side. - -#### After service delivery - -In the OVHcloud Control Panel, check the IN/OUT optical values: - -- If the **OUT** value is **DOWN**, , the following reasons may be the cause: - - the port on the OVHcloud side does not emit light - - the service is being cancelled - - the port is locked in your OVHcloud Control Panel - - there is an SFP issue -- If **IN** is **DOWN**, the following reasons may be the cause: - - your equipment is not yet connected - - the port can be disabled or has a defect that prevents it from emitting light - - there is a Cross-Connect issue - -### Tx/Rx Fiber inversion - -If there is a fiber inversion between Port A and Port B, the light is not received in the right place and the **IN (Rx)** port will display **DOWN**. If your service has not yet been delivered, contact the support teams so that the link status is checked. - -Contact the PoP concerned by the LOA to check that there is no Tx/Rx inversion on the Cross-Connect. - -### Peering verification - -The peering should be checked once the light is **UP** on both sides. - -If peering cannot be established (DOWN) on one or both sides, there may be several reasons: - -- An SFP issue -- Auto-negotiation is not disabled on the customer side -- IP address conflict -- BGP link misconfiguration - -#### SFP Configuration - -Optical values **UP** but no Ethernet link (interface **DOWN**) are a symptom of a misconfigured SFP. - -The SFP to use on the client device on an OVHcloud Connect link depends on the link you ordered. You must use an SFP that conforms to the ordered bandwidth. - -If you have ordered a 1 Gbps link, the SFP will be: 1000Base-LX/LH. - -``` -speed 1000 -``` - -If you have ordered a 10 Gbps link, the SFP will be: 10GBase-LR. - -``` -speed 10000 -``` - -For more information, please read the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) - -#### Disabling auto-negotiation - -Auto-negotiation is not supported in the OVHcloud Connect solution. This setting must be disabled. - -To disable auto-negotiation on a Cisco device, use the following command: - -``` -no negotiate auto -``` - -or - -``` -no speed negotiate -``` - -On Cisco IOS, use the following command: - -``` -speed nonegotiate -``` - -On Cisco NX-OS, use the following command: - -``` -speed 1000 -no negotiate auto -``` - -#### PoP/DC configuration - -An IP address conflict may occur if you are using an IP address(es) normally reserved for OVHcloud. - -The rules for assigning IP addresses according to the subnet are as follows: - -- DC-side subnet: /28 (minimum value) - The first three IP addresses are reserved for OVHcloud - Vlan fixed to 0 (untagged). -- PoP-side subnet: /30 (fixed value) - The first IP address is reserved for OVHcloud, the second IP address for the customer. - -#### Configuring the BGP link - -The BGP Area on the customer side must be different from the OVHcloud side. - -- Range Area = AS BGP -- AS number: We recommend ASNs between 64512 and 65534. The choice is your, with the exception of the following numbers, which are reserved for OVHcloud. - - 65501 if the PoP is in Europe - - 65502 if the PoP is in Canada - - 65519 if the PoP is in Asia -- The OVHcloud BGP AS zone and your BGP AS number (on the PoP side) must be different. -- The OVHcloud BGP AS zone: can be the same between the DC side and the PoP side configuration (recommended) - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-gb.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-gb.md deleted file mode 100644 index 6894a206a00..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-gb.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: Troubleshooting common errors setting up OVHcloud Connect -excerpt: Find out how to resolve the most common errors associated with setting up OVHcloud Connect -updated: 2021-09-02 ---- - -## Objective - -Find out how to resolve the most common errors associated with setting up OVHcloud Connect - -## Requirements - -- an [OVHcloud Connect solution](https://www.ovhcloud.com/en-gb/network-security/ovhcloud-connect/) - -## Instructions - -An OVHcloud Connect service will appear in your OVHcloud Control Panel, and can only be configured when it is considered **delivered**. - -For the **OVHcloud Connect Direct** offer, the service is **delivered** in the following situations: - -- When OVHcloud detects light at the position indicated in the LOA. This detection suggests that the cross-connect was performed by the client. -- 60 days after the order if no light has been detected. - -### LOA verification - -A misinterpretation of the position on the Cross-Connect by the PoP can result in a lack of light on the OVHcloud Connect link. -For example, the PoP may indicate that there is no interconnection at the position mentioned on the LOA. - -#### How to read LOA information? - -Here is an example of information on the LOA: - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -This information is interpreted as follows: - -- Cabinet (position of the bay where the RACK is located): **103** -- Cage (RACK): **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (switch position): **PP:0103:1132697** -- Position (on switch): **16** -- FiberOptic / Port A: **31** -- FiberOptic / Port B: **32** -- Side (front or back): **BACK** -- Fiber Termination: **SC/PC** - -### OVHcloud Connect Direct (only): checking for light on the link - -> [!warning] -> -> - As a reminder, Cross-Connect is contractually your responsibility. -> - Before contacting the OVHcloud teams, you will need to open a ticket to the PoP concerned by the LOA. -> - -#### Before service delivery - -When you order an OVHcloud Connect link, the IN/OUT optical values can be checked on the OVHcloud side. You can request information about this from your support team. - -If the service has not yet been delivered, our support teams will be able to check the status of the IN and OUT optical values on the OVHcloud infrastructure side. - -#### After service delivery - -In the OVHcloud Control Panel, check the IN/OUT optical values: - -- If the **OUT** value is **DOWN**, , the following reasons may be the cause: - - the port on the OVHcloud side does not emit light - - the service is being cancelled - - the port is locked in your OVHcloud Control Panel - - there is an SFP issue -- If **IN** is **DOWN**, the following reasons may be the cause: - - your equipment is not yet connected - - the port can be disabled or has a defect that prevents it from emitting light - - there is a Cross-Connect issue - -### Tx/Rx Fiber inversion - -If there is a fiber inversion between Port A and Port B, the light is not received in the right place and the **IN (Rx)** port will display **DOWN**. If your service has not yet been delivered, contact the support teams so that the link status is checked. - -Contact the PoP concerned by the LOA to check that there is no Tx/Rx inversion on the Cross-Connect. - -### Peering verification - -The peering should be checked once the light is **UP** on both sides. - -If peering cannot be established (DOWN) on one or both sides, there may be several reasons: - -- An SFP issue -- Auto-negotiation is not disabled on the customer side -- IP address conflict -- BGP link misconfiguration - -#### SFP Configuration - -Optical values **UP** but no Ethernet link (interface **DOWN**) are a symptom of a misconfigured SFP. - -The SFP to use on the client device on an OVHcloud Connect link depends on the link you ordered. You must use an SFP that conforms to the ordered bandwidth. - -If you have ordered a 1 Gbps link, the SFP will be: 1000Base-LX/LH. - -``` -speed 1000 -``` - -If you have ordered a 10 Gbps link, the SFP will be: 10GBase-LR. - -``` -speed 10000 -``` - -For more information, please read the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) - -#### Disabling auto-negotiation - -Auto-negotiation is not supported in the OVHcloud Connect solution. This setting must be disabled. - -To disable auto-negotiation on a Cisco device, use the following command: - -``` -no negotiate auto -``` - -or - -``` -no speed negotiate -``` - -On Cisco IOS, use the following command: - -``` -speed nonegotiate -``` - -On Cisco NX-OS, use the following command: - -``` -speed 1000 -no negotiate auto -``` - -#### PoP/DC configuration - -An IP address conflict may occur if you are using an IP address(es) normally reserved for OVHcloud. - -The rules for assigning IP addresses according to the subnet are as follows: - -- DC-side subnet: /28 (minimum value) - The first three IP addresses are reserved for OVHcloud - Vlan fixed to 0 (untagged). -- PoP-side subnet: /30 (fixed value) - The first IP address is reserved for OVHcloud, the second IP address for the customer. - -#### Configuring the BGP link - -The BGP Area on the customer side must be different from the OVHcloud side. - -- Range Area = AS BGP -- AS number: We recommend ASNs between 64512 and 65534. The choice is your, with the exception of the following numbers, which are reserved for OVHcloud. - - 65501 if the PoP is in Europe - - 65502 if the PoP is in Canada - - 65519 if the PoP is in Asia -- The OVHcloud BGP AS zone and your BGP AS number (on the PoP side) must be different. -- The OVHcloud BGP AS zone: can be the same between the DC side and the PoP side configuration (recommended) - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-ie.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-ie.md deleted file mode 100644 index a72d0658775..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-ie.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: Troubleshooting common errors setting up OVHcloud Connect -excerpt: Find out how to resolve the most common errors associated with setting up OVHcloud Connect -updated: 2021-09-02 ---- - -## Objective - -Find out how to resolve the most common errors associated with setting up OVHcloud Connect - -## Requirements - -- an [OVHcloud Connect solution](https://www.ovhcloud.com/en-ie/network-security/ovhcloud-connect/) - -## Instructions - -An OVHcloud Connect service will appear in your OVHcloud Control Panel, and can only be configured when it is considered **delivered**. - -For the **OVHcloud Connect Direct** offer, the service is **delivered** in the following situations: - -- When OVHcloud detects light at the position indicated in the LOA. This detection suggests that the cross-connect was performed by the client. -- 60 days after the order if no light has been detected. - -### LOA verification - -A misinterpretation of the position on the Cross-Connect by the PoP can result in a lack of light on the OVHcloud Connect link. -For example, the PoP may indicate that there is no interconnection at the position mentioned on the LOA. - -#### How to read LOA information? - -Here is an example of information on the LOA: - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -This information is interpreted as follows: - -- Cabinet (position of the bay where the RACK is located): **103** -- Cage (RACK): **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (switch position): **PP:0103:1132697** -- Position (on switch): **16** -- FiberOptic / Port A: **31** -- FiberOptic / Port B: **32** -- Side (front or back): **BACK** -- Fiber Termination: **SC/PC** - -### OVHcloud Connect Direct (only): checking for light on the link - -> [!warning] -> -> - As a reminder, Cross-Connect is contractually your responsibility. -> - Before contacting the OVHcloud teams, you will need to open a ticket to the PoP concerned by the LOA. -> - -#### Before service delivery - -When you order an OVHcloud Connect link, the IN/OUT optical values can be checked on the OVHcloud side. You can request information about this from your support team. - -If the service has not yet been delivered, our support teams will be able to check the status of the IN and OUT optical values on the OVHcloud infrastructure side. - -#### After service delivery - -In the OVHcloud Control Panel, check the IN/OUT optical values: - -- If the **OUT** value is **DOWN**, , the following reasons may be the cause: - - the port on the OVHcloud side does not emit light - - the service is being cancelled - - the port is locked in your OVHcloud Control Panel - - there is an SFP issue -- If **IN** is **DOWN**, the following reasons may be the cause: - - your equipment is not yet connected - - the port can be disabled or has a defect that prevents it from emitting light - - there is a Cross-Connect issue - -### Tx/Rx Fiber inversion - -If there is a fiber inversion between Port A and Port B, the light is not received in the right place and the **IN (Rx)** port will display **DOWN**. If your service has not yet been delivered, contact the support teams so that the link status is checked. - -Contact the PoP concerned by the LOA to check that there is no Tx/Rx inversion on the Cross-Connect. - -### Peering verification - -The peering should be checked once the light is **UP** on both sides. - -If peering cannot be established (DOWN) on one or both sides, there may be several reasons: - -- An SFP issue -- Auto-negotiation is not disabled on the customer side -- IP address conflict -- BGP link misconfiguration - -#### SFP Configuration - -Optical values **UP** but no Ethernet link (interface **DOWN**) are a symptom of a misconfigured SFP. - -The SFP to use on the client device on an OVHcloud Connect link depends on the link you ordered. You must use an SFP that conforms to the ordered bandwidth. - -If you have ordered a 1 Gbps link, the SFP will be: 1000Base-LX/LH. - -``` -speed 1000 -``` - -If you have ordered a 10 Gbps link, the SFP will be: 10GBase-LR. - -``` -speed 10000 -``` - -For more information, please read the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) - -#### Disabling auto-negotiation - -Auto-negotiation is not supported in the OVHcloud Connect solution. This setting must be disabled. - -To disable auto-negotiation on a Cisco device, use the following command: - -``` -no negotiate auto -``` - -or - -``` -no speed negotiate -``` - -On Cisco IOS, use the following command: - -``` -speed nonegotiate -``` - -On Cisco NX-OS, use the following command: - -``` -speed 1000 -no negotiate auto -``` - -#### PoP/DC configuration - -An IP address conflict may occur if you are using an IP address(es) normally reserved for OVHcloud. - -The rules for assigning IP addresses according to the subnet are as follows: - -- DC-side subnet: /28 (minimum value) - The first three IP addresses are reserved for OVHcloud - Vlan fixed to 0 (untagged). -- PoP-side subnet: /30 (fixed value) - The first IP address is reserved for OVHcloud, the second IP address for the customer. - -#### Configuring the BGP link - -The BGP Area on the customer side must be different from the OVHcloud side. - -- Range Area = AS BGP -- AS number: We recommend ASNs between 64512 and 65534. The choice is your, with the exception of the following numbers, which are reserved for OVHcloud. - - 65501 if the PoP is in Europe - - 65502 if the PoP is in Canada - - 65519 if the PoP is in Asia -- The OVHcloud BGP AS zone and your BGP AS number (on the PoP side) must be different. -- The OVHcloud BGP AS zone: can be the same between the DC side and the PoP side configuration (recommended) - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-sg.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-sg.md deleted file mode 100644 index 6dd90cca62d..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-sg.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: Troubleshooting common errors setting up OVHcloud Connect -excerpt: Find out how to resolve the most common errors associated with setting up OVHcloud Connect -updated: 2021-09-02 ---- - -## Objective - -Find out how to resolve the most common errors associated with setting up OVHcloud Connect - -## Requirements - -- an [OVHcloud Connect solution](https://www.ovhcloud.com/en-sg/network-security/ovhcloud-connect/) - -## Instructions - -An OVHcloud Connect service will appear in your OVHcloud Control Panel, and can only be configured when it is considered **delivered**. - -For the **OVHcloud Connect Direct** offer, the service is **delivered** in the following situations: - -- When OVHcloud detects light at the position indicated in the LOA. This detection suggests that the cross-connect was performed by the client. -- 60 days after the order if no light has been detected. - -### LOA verification - -A misinterpretation of the position on the Cross-Connect by the PoP can result in a lack of light on the OVHcloud Connect link. -For example, the PoP may indicate that there is no interconnection at the position mentioned on the LOA. - -#### How to read LOA information? - -Here is an example of information on the LOA: - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -This information is interpreted as follows: - -- Cabinet (position of the bay where the RACK is located): **103** -- Cage (RACK): **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (switch position): **PP:0103:1132697** -- Position (on switch): **16** -- FiberOptic / Port A: **31** -- FiberOptic / Port B: **32** -- Side (front or back): **BACK** -- Fiber Termination: **SC/PC** - -### OVHcloud Connect Direct (only): checking for light on the link - -> [!warning] -> -> - As a reminder, Cross-Connect is contractually your responsibility. -> - Before contacting the OVHcloud teams, you will need to open a ticket to the PoP concerned by the LOA. -> - -#### Before service delivery - -When you order an OVHcloud Connect link, the IN/OUT optical values can be checked on the OVHcloud side. You can request information about this from your support team. - -If the service has not yet been delivered, our support teams will be able to check the status of the IN and OUT optical values on the OVHcloud infrastructure side. - -#### After service delivery - -In the OVHcloud Control Panel, check the IN/OUT optical values: - -- If the **OUT** value is **DOWN**, , the following reasons may be the cause: - - the port on the OVHcloud side does not emit light - - the service is being cancelled - - the port is locked in your OVHcloud Control Panel - - there is an SFP issue -- If **IN** is **DOWN**, the following reasons may be the cause: - - your equipment is not yet connected - - the port can be disabled or has a defect that prevents it from emitting light - - there is a Cross-Connect issue - -### Tx/Rx Fiber inversion - -If there is a fiber inversion between Port A and Port B, the light is not received in the right place and the **IN (Rx)** port will display **DOWN**. If your service has not yet been delivered, contact the support teams so that the link status is checked. - -Contact the PoP concerned by the LOA to check that there is no Tx/Rx inversion on the Cross-Connect. - -### Peering verification - -The peering should be checked once the light is **UP** on both sides. - -If peering cannot be established (DOWN) on one or both sides, there may be several reasons: - -- An SFP issue -- Auto-negotiation is not disabled on the customer side -- IP address conflict -- BGP link misconfiguration - -#### SFP Configuration - -Optical values **UP** but no Ethernet link (interface **DOWN**) are a symptom of a misconfigured SFP. - -The SFP to use on the client device on an OVHcloud Connect link depends on the link you ordered. You must use an SFP that conforms to the ordered bandwidth. - -If you have ordered a 1 Gbps link, the SFP will be: 1000Base-LX/LH. - -``` -speed 1000 -``` - -If you have ordered a 10 Gbps link, the SFP will be: 10GBase-LR. - -``` -speed 10000 -``` - -For more information, please read the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) - -#### Disabling auto-negotiation - -Auto-negotiation is not supported in the OVHcloud Connect solution. This setting must be disabled. - -To disable auto-negotiation on a Cisco device, use the following command: - -``` -no negotiate auto -``` - -or - -``` -no speed negotiate -``` - -On Cisco IOS, use the following command: - -``` -speed nonegotiate -``` - -On Cisco NX-OS, use the following command: - -``` -speed 1000 -no negotiate auto -``` - -#### PoP/DC configuration - -An IP address conflict may occur if you are using an IP address(es) normally reserved for OVHcloud. - -The rules for assigning IP addresses according to the subnet are as follows: - -- DC-side subnet: /28 (minimum value) - The first three IP addresses are reserved for OVHcloud - Vlan fixed to 0 (untagged). -- PoP-side subnet: /30 (fixed value) - The first IP address is reserved for OVHcloud, the second IP address for the customer. - -#### Configuring the BGP link - -The BGP Area on the customer side must be different from the OVHcloud side. - -- Range Area = AS BGP -- AS number: We recommend ASNs between 64512 and 65534. The choice is your, with the exception of the following numbers, which are reserved for OVHcloud. - - 65501 if the PoP is in Europe - - 65502 if the PoP is in Canada - - 65519 if the PoP is in Asia -- The OVHcloud BGP AS zone and your BGP AS number (on the PoP side) must be different. -- The OVHcloud BGP AS zone: can be the same between the DC side and the PoP side configuration (recommended) - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-us.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-us.md deleted file mode 100644 index 769289a6bf9..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.en-us.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: Troubleshooting common errors setting up OVHcloud Connect -excerpt: Find out how to resolve the most common errors associated with setting up OVHcloud Connect -updated: 2021-09-02 ---- - -## Objective - -Find out how to resolve the most common errors associated with setting up OVHcloud Connect - -## Requirements - -- an [OVHcloud Connect solution](https://www.ovhcloud.com/en/network-security/ovhcloud-connect/) - -## Instructions - -An OVHcloud Connect service will appear in your OVHcloud Control Panel, and can only be configured when it is considered **delivered**. - -For the **OVHcloud Connect Direct** offer, the service is **delivered** in the following situations: - -- When OVHcloud detects light at the position indicated in the LOA. This detection suggests that the cross-connect was performed by the client. -- 60 days after the order if no light has been detected. - -### LOA verification - -A misinterpretation of the position on the Cross-Connect by the PoP can result in a lack of light on the OVHcloud Connect link. -For example, the PoP may indicate that there is no interconnection at the position mentioned on the LOA. - -#### How to read LOA information? - -Here is an example of information on the LOA: - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -This information is interpreted as follows: - -- Cabinet (position of the bay where the RACK is located): **103** -- Cage (RACK): **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (switch position): **PP:0103:1132697** -- Position (on switch): **16** -- FiberOptic / Port A: **31** -- FiberOptic / Port B: **32** -- Side (front or back): **BACK** -- Fiber Termination: **SC/PC** - -### OVHcloud Connect Direct (only): checking for light on the link - -> [!warning] -> -> - As a reminder, Cross-Connect is contractually your responsibility. -> - Before contacting the OVHcloud teams, you will need to open a ticket to the PoP concerned by the LOA. -> - -#### Before service delivery - -When you order an OVHcloud Connect link, the IN/OUT optical values can be checked on the OVHcloud side. You can request information about this from your support team. - -If the service has not yet been delivered, our support teams will be able to check the status of the IN and OUT optical values on the OVHcloud infrastructure side. - -#### After service delivery - -In the OVHcloud Control Panel, check the IN/OUT optical values: - -- If the **OUT** value is **DOWN**, , the following reasons may be the cause: - - the port on the OVHcloud side does not emit light - - the service is being cancelled - - the port is locked in your OVHcloud Control Panel - - there is an SFP issue -- If **IN** is **DOWN**, the following reasons may be the cause: - - your equipment is not yet connected - - the port can be disabled or has a defect that prevents it from emitting light - - there is a Cross-Connect issue - -### Tx/Rx Fiber inversion - -If there is a fiber inversion between Port A and Port B, the light is not received in the right place and the **IN (Rx)** port will display **DOWN**. If your service has not yet been delivered, contact the support teams so that the link status is checked. - -Contact the PoP concerned by the LOA to check that there is no Tx/Rx inversion on the Cross-Connect. - -### Peering verification - -The peering should be checked once the light is **UP** on both sides. - -If peering cannot be established (DOWN) on one or both sides, there may be several reasons: - -- An SFP issue -- Auto-negotiation is not disabled on the customer side -- IP address conflict -- BGP link misconfiguration - -#### SFP Configuration - -Optical values **UP** but no Ethernet link (interface **DOWN**) are a symptom of a misconfigured SFP. - -The SFP to use on the client device on an OVHcloud Connect link depends on the link you ordered. You must use an SFP that conforms to the ordered bandwidth. - -If you have ordered a 1 Gbps link, the SFP will be: 1000Base-LX/LH. - -``` -speed 1000 -``` - -If you have ordered a 10 Gbps link, the SFP will be: 10GBase-LR. - -``` -speed 10000 -``` - -For more information, please read the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) - -#### Disabling auto-negotiation - -Auto-negotiation is not supported in the OVHcloud Connect solution. This setting must be disabled. - -To disable auto-negotiation on a Cisco device, use the following command: - -``` -no negotiate auto -``` - -or - -``` -no speed negotiate -``` - -On Cisco IOS, use the following command: - -``` -speed nonegotiate -``` - -On Cisco NX-OS, use the following command: - -``` -speed 1000 -no negotiate auto -``` - -#### PoP/DC configuration - -An IP address conflict may occur if you are using an IP address(es) normally reserved for OVHcloud. - -The rules for assigning IP addresses according to the subnet are as follows: - -- DC-side subnet: /28 (minimum value) - The first three IP addresses are reserved for OVHcloud - Vlan fixed to 0 (untagged). -- PoP-side subnet: /30 (fixed value) - The first IP address is reserved for OVHcloud, the second IP address for the customer. - -#### Configuring the BGP link - -The BGP Area on the customer side must be different from the OVHcloud side. - -- Range Area = AS BGP -- AS number: We recommend ASNs between 64512 and 65534. The choice is your, with the exception of the following numbers, which are reserved for OVHcloud. - - 65501 if the PoP is in Europe - - 65502 if the PoP is in Canada - - 65519 if the PoP is in Asia -- The OVHcloud BGP AS zone and your BGP AS number (on the PoP side) must be different. -- The OVHcloud BGP AS zone: can be the same between the DC side and the PoP side configuration (recommended) - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.es-es.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.es-es.md deleted file mode 100644 index 25e0f624c31..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.es-es.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: Troubleshooting common errors setting up OVHcloud Connect -excerpt: Find out how to resolve the most common errors associated with setting up OVHcloud Connect -updated: 2021-09-02 ---- - -## Objective - -Find out how to resolve the most common errors associated with setting up OVHcloud Connect - -## Requirements - -- an [OVHcloud Connect solution](https://www.ovhcloud.com/es-es/network-security/ovhcloud-connect/) - -## Instructions - -An OVHcloud Connect service will appear in your OVHcloud Control Panel, and can only be configured when it is considered **delivered**. - -For the **OVHcloud Connect Direct** offer, the service is **delivered** in the following situations: - -- When OVHcloud detects light at the position indicated in the LOA. This detection suggests that the cross-connect was performed by the client. -- 60 days after the order if no light has been detected. - -### LOA verification - -A misinterpretation of the position on the Cross-Connect by the PoP can result in a lack of light on the OVHcloud Connect link. -For example, the PoP may indicate that there is no interconnection at the position mentioned on the LOA. - -#### How to read LOA information? - -Here is an example of information on the LOA: - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -This information is interpreted as follows: - -- Cabinet (position of the bay where the RACK is located): **103** -- Cage (RACK): **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (switch position): **PP:0103:1132697** -- Position (on switch): **16** -- FiberOptic / Port A: **31** -- FiberOptic / Port B: **32** -- Side (front or back): **BACK** -- Fiber Termination: **SC/PC** - -### OVHcloud Connect Direct (only): checking for light on the link - -> [!warning] -> -> - As a reminder, Cross-Connect is contractually your responsibility. -> - Before contacting the OVHcloud teams, you will need to open a ticket to the PoP concerned by the LOA. -> - -#### Before service delivery - -When you order an OVHcloud Connect link, the IN/OUT optical values can be checked on the OVHcloud side. You can request information about this from your support team. - -If the service has not yet been delivered, our support teams will be able to check the status of the IN and OUT optical values on the OVHcloud infrastructure side. - -#### After service delivery - -In the OVHcloud Control Panel, check the IN/OUT optical values: - -- If the **OUT** value is **DOWN**, , the following reasons may be the cause: - - the port on the OVHcloud side does not emit light - - the service is being cancelled - - the port is locked in your OVHcloud Control Panel - - there is an SFP issue -- If **IN** is **DOWN**, the following reasons may be the cause: - - your equipment is not yet connected - - the port can be disabled or has a defect that prevents it from emitting light - - there is a Cross-Connect issue - -### Tx/Rx Fiber inversion - -If there is a fiber inversion between Port A and Port B, the light is not received in the right place and the **IN (Rx)** port will display **DOWN**. If your service has not yet been delivered, contact the support teams so that the link status is checked. - -Contact the PoP concerned by the LOA to check that there is no Tx/Rx inversion on the Cross-Connect. - -### Peering verification - -The peering should be checked once the light is **UP** on both sides. - -If peering cannot be established (DOWN) on one or both sides, there may be several reasons: - -- An SFP issue -- Auto-negotiation is not disabled on the customer side -- IP address conflict -- BGP link misconfiguration - -#### SFP Configuration - -Optical values **UP** but no Ethernet link (interface **DOWN**) are a symptom of a misconfigured SFP. - -The SFP to use on the client device on an OVHcloud Connect link depends on the link you ordered. You must use an SFP that conforms to the ordered bandwidth. - -If you have ordered a 1 Gbps link, the SFP will be: 1000Base-LX/LH. - -``` -speed 1000 -``` - -If you have ordered a 10 Gbps link, the SFP will be: 10GBase-LR. - -``` -speed 10000 -``` - -For more information, please read the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) - -#### Disabling auto-negotiation - -Auto-negotiation is not supported in the OVHcloud Connect solution. This setting must be disabled. - -To disable auto-negotiation on a Cisco device, use the following command: - -``` -no negotiate auto -``` - -or - -``` -no speed negotiate -``` - -On Cisco IOS, use the following command: - -``` -speed nonegotiate -``` - -On Cisco NX-OS, use the following command: - -``` -speed 1000 -no negotiate auto -``` - -#### PoP/DC configuration - -An IP address conflict may occur if you are using an IP address(es) normally reserved for OVHcloud. - -The rules for assigning IP addresses according to the subnet are as follows: - -- DC-side subnet: /28 (minimum value) - The first three IP addresses are reserved for OVHcloud - Vlan fixed to 0 (untagged). -- PoP-side subnet: /30 (fixed value) - The first IP address is reserved for OVHcloud, the second IP address for the customer. - -#### Configuring the BGP link - -The BGP Area on the customer side must be different from the OVHcloud side. - -- Range Area = AS BGP -- AS number: We recommend ASNs between 64512 and 65534. The choice is your, with the exception of the following numbers, which are reserved for OVHcloud. - - 65501 if the PoP is in Europe - - 65502 if the PoP is in Canada - - 65519 if the PoP is in Asia -- The OVHcloud BGP AS zone and your BGP AS number (on the PoP side) must be different. -- The OVHcloud BGP AS zone: can be the same between the DC side and the PoP side configuration (recommended) - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.es-us.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.es-us.md deleted file mode 100644 index 025ea8cbbb9..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.es-us.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: Troubleshooting common errors setting up OVHcloud Connect -excerpt: Find out how to resolve the most common errors associated with setting up OVHcloud Connect -updated: 2021-09-02 ---- - -## Objective - -Find out how to resolve the most common errors associated with setting up OVHcloud Connect - -## Requirements - -- an [OVHcloud Connect solution](https://www.ovhcloud.com/es/network-security/ovhcloud-connect/) - -## Instructions - -An OVHcloud Connect service will appear in your OVHcloud Control Panel, and can only be configured when it is considered **delivered**. - -For the **OVHcloud Connect Direct** offer, the service is **delivered** in the following situations: - -- When OVHcloud detects light at the position indicated in the LOA. This detection suggests that the cross-connect was performed by the client. -- 60 days after the order if no light has been detected. - -### LOA verification - -A misinterpretation of the position on the Cross-Connect by the PoP can result in a lack of light on the OVHcloud Connect link. -For example, the PoP may indicate that there is no interconnection at the position mentioned on the LOA. - -#### How to read LOA information? - -Here is an example of information on the LOA: - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -This information is interpreted as follows: - -- Cabinet (position of the bay where the RACK is located): **103** -- Cage (RACK): **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (switch position): **PP:0103:1132697** -- Position (on switch): **16** -- FiberOptic / Port A: **31** -- FiberOptic / Port B: **32** -- Side (front or back): **BACK** -- Fiber Termination: **SC/PC** - -### OVHcloud Connect Direct (only): checking for light on the link - -> [!warning] -> -> - As a reminder, Cross-Connect is contractually your responsibility. -> - Before contacting the OVHcloud teams, you will need to open a ticket to the PoP concerned by the LOA. -> - -#### Before service delivery - -When you order an OVHcloud Connect link, the IN/OUT optical values can be checked on the OVHcloud side. You can request information about this from your support team. - -If the service has not yet been delivered, our support teams will be able to check the status of the IN and OUT optical values on the OVHcloud infrastructure side. - -#### After service delivery - -In the OVHcloud Control Panel, check the IN/OUT optical values: - -- If the **OUT** value is **DOWN**, , the following reasons may be the cause: - - the port on the OVHcloud side does not emit light - - the service is being cancelled - - the port is locked in your OVHcloud Control Panel - - there is an SFP issue -- If **IN** is **DOWN**, the following reasons may be the cause: - - your equipment is not yet connected - - the port can be disabled or has a defect that prevents it from emitting light - - there is a Cross-Connect issue - -### Tx/Rx Fiber inversion - -If there is a fiber inversion between Port A and Port B, the light is not received in the right place and the **IN (Rx)** port will display **DOWN**. If your service has not yet been delivered, contact the support teams so that the link status is checked. - -Contact the PoP concerned by the LOA to check that there is no Tx/Rx inversion on the Cross-Connect. - -### Peering verification - -The peering should be checked once the light is **UP** on both sides. - -If peering cannot be established (DOWN) on one or both sides, there may be several reasons: - -- An SFP issue -- Auto-negotiation is not disabled on the customer side -- IP address conflict -- BGP link misconfiguration - -#### SFP Configuration - -Optical values **UP** but no Ethernet link (interface **DOWN**) are a symptom of a misconfigured SFP. - -The SFP to use on the client device on an OVHcloud Connect link depends on the link you ordered. You must use an SFP that conforms to the ordered bandwidth. - -If you have ordered a 1 Gbps link, the SFP will be: 1000Base-LX/LH. - -``` -speed 1000 -``` - -If you have ordered a 10 Gbps link, the SFP will be: 10GBase-LR. - -``` -speed 10000 -``` - -For more information, please read the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) - -#### Disabling auto-negotiation - -Auto-negotiation is not supported in the OVHcloud Connect solution. This setting must be disabled. - -To disable auto-negotiation on a Cisco device, use the following command: - -``` -no negotiate auto -``` - -or - -``` -no speed negotiate -``` - -On Cisco IOS, use the following command: - -``` -speed nonegotiate -``` - -On Cisco NX-OS, use the following command: - -``` -speed 1000 -no negotiate auto -``` - -#### PoP/DC configuration - -An IP address conflict may occur if you are using an IP address(es) normally reserved for OVHcloud. - -The rules for assigning IP addresses according to the subnet are as follows: - -- DC-side subnet: /28 (minimum value) - The first three IP addresses are reserved for OVHcloud - Vlan fixed to 0 (untagged). -- PoP-side subnet: /30 (fixed value) - The first IP address is reserved for OVHcloud, the second IP address for the customer. - -#### Configuring the BGP link - -The BGP Area on the customer side must be different from the OVHcloud side. - -- Range Area = AS BGP -- AS number: We recommend ASNs between 64512 and 65534. The choice is your, with the exception of the following numbers, which are reserved for OVHcloud. - - 65501 if the PoP is in Europe - - 65502 if the PoP is in Canada - - 65519 if the PoP is in Asia -- The OVHcloud BGP AS zone and your BGP AS number (on the PoP side) must be different. -- The OVHcloud BGP AS zone: can be the same between the DC side and the PoP side configuration (recommended) - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.fr-ca.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.fr-ca.md deleted file mode 100644 index 45e3319c199..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.fr-ca.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: "Résoudre les erreurs fréquentes lors de la mise en service de OVHcloud Connect" -excerpt: "Découvrez comment résoudre les erreurs les plus fréquentes liées à la mise en service de OVHcloud Connect" -updated: 2021-09-02 ---- - -## Objectif - -Découvrez comment résoudre les erreurs les plus fréquentes liées à la mise en service de OVHcloud Connect. - -## Prérequis - -- Posséder une [offre OVHcloud Connect](https://www.ovhcloud.com/fr-ca/network-security/ovhcloud-connect/) - -## En pratique - -Un service OVHcloud Connect apparaît dans votre espace client OVHcloud et ne peut être configuré que lorsqu'il est considéré comme **livré**. - -En ce qui concerne l'offre **OVHcloud Connect Direct**, le service est **livré** dans les situations suivantes : - -- dès lors que OVHcloud détecte de la lumière sur la position indiquée dans la LOA. Cette détection suggère que l'interconnexion (Cross-Connect) a été réalisée par le client. -- au bout de 60 jours après la commande si aucune lumière n'a été détectée. - -### Vérification de la LOA - -Une mauvaise interprétation de la position sur l'interconnexion (Cross-Connect) par le PoP peut engendrer une absence de lumière sur le lien OVHcloud Connect Direct. -Par exemple, le PoP peut indiquer qu'il n'y a pas d'interconnexion sur la position mentionnée sur la LOA. - -#### Comment lire les informations sur la LOA ? - -Voici un exemple d'informations sur la LOA : - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -Voici l'interprétation de ces informations : - -- Cabinet (position de la baie où se trouve le RACK) : **103** -- Cage (RACK) : **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (position du switch) : **PP:0103:1132697** -- Position (sur le switch) : **16** -- FiberOptic / Port A : **31** -- FiberOptic / Port B : **32** -- Side (face avant ou arrière) : **BACK** -- Fiber Termination : **SC/PC** - -### OVHcloud Connect Direct (uniquement) : vérifier la présence de lumière sur le lien - -> [!warning] -> -> - Pour rappel, l'interconnexion (Cross-Connect) est contractuellement de votre responsabilité. -> - Avant de prendre contact avec les équipes OVHcloud, vous devez ouvrir un ticket auprès du PoP concerné par la LOA. -> - -#### Avant la livraison du service - -Lors de la commande d’un lien OVHcloud Connect Direct, il est possible de voir côté OVHcloud les valeurs optiques IN/OUT. Vous pouvez demander des informations à ce sujet à votre équipe support. - -Si le service n'est pas encore livré, nos équipes support pourront vérifier le statut des valeurs optiques IN et OUT côté infrastructure OVHcloud. - -#### Après la livraison du service - -Dans votre espace client OVHcloud, vérifiez les valeurs optiques IN/OUT : - -- Si la valeur **OUT** est « **DOWN** », les raisons suivantes peuvent en être à l'origine : - - le port côté OVHcloud n'émet pas de lumière; - - le service est en cours de résiliation; - - le port est verrouillé dans votre espace client OVHcloud; - - il y a un défaut sur le SFP. -- Si **IN** est « **DOWN** », les raisons suivantes peuvent en être à l'origine : - - votre équipement n'est pas encore branché; - - le port peut être désactivé ou a un défaut qui l'empêche d'émettre de la lumière; - - un défaut est présent au niveau de l'interconnexion (Cross Connect). - -### Inversion de fibre Tx/Rx - -S'il y a une inversion de fibre entre le Port A et le Port B, la lumière n'est pas reçue au bon endroit et le port **IN (Rx)** affichera **DOWN**. Si votre service n'est pas encore livré, contactez le support pour connaître l'état du lien. - -Prenez contact avec le PoP concerné par la LOA pour vérifier qu'il n'y a pas d'inversion Tx/Rx sur l'interconnexion (Cross Connect). - -### Vérification du peering - -La vérification du peering doit être faite une fois que la lumière est « **UP** » des deux côtés. - -Si le peering ne peut pas être établi (DOWN) d'un côté ou des deux côtés, cela peut avoir plusieurs raisons : - -- un défaut de SFP; -- l'auto-négociation n'est pas désactivée côté client; -- un conflit d'adresses IP; -- une mauvaise configuration du lien BGP. - -#### Configuration SFP - -Des valeurs optiques **UP** mais pas de lien Ethernet (interface **DOWN**) sont un symptôme d'un SFP mal configuré. - -Le SFP à utiliser sur l'équipement client pour une liaison OVHcloud Connect dépend du lien commandé. Vous devez utiliser un SFP conforme à la bande-passante commandée. - -Si vous avez commandé un lien 1 Gbit/s, le SFP sera: 1000Base-LX/LH. Utilisez la commande suivante : - -``` -speed 1000 -``` - -Si vous avez commandé un lien 10 Gbit/s, le SFP sera: 10GBase-LR. Utilisez la commande suivante : - -``` -speed 10000 -``` - -Pour plus d'informations, consultez les [capacités et limites techniques de l'offre OVHcloud Connect](/pages/network/ovhcloud_connect/occ-limits) - -#### Désactiver l'auto-négociation - -L'auto-négociation n'est pas supportée dans l'offre OVHcloud Connect. Ce paramètre doit être désactivé. - -Pour désactiver l'auto-négociation sur un équipement Cisco, utilisez la commande : - -``` -no negotiate auto -``` - -ou - -``` -no speed negotiate -``` - -Sur Cisco IOS, utilisez la commande suivante : - -``` -speed nonegotiate -``` - -Sur Cisco NX-OS, utilisez la commande suivante : - -``` -speed 1000 -no negotiate auto -``` - -#### Configuration IP du PoP/DC - -Un conflit d'adresses IP peut survenir si vous utilisez une/des adresse(s) IP normalement réservée(s) pour OVHcloud. - -Les règles d'attribution des adresses IP en fonction du subnet sont les suivantes : - -- subnet côté DC : /28 (valeur minimum) - Les trois premières adresses IP sont réservées pour OVHcloud - Vlan fixé à 0 (untagged). -- subnet côté PoP: /30 (valeur fixe) - La pemière adresse IP est réservée pour OVHcloud, deuxième adresse IP pour le client. - -#### Configuration du lien BGP - -La BGP Area côté client doit être différente de celle côté OVHcloud. - -- Range Area = AS BGP -- Numéro d'AS : Nous recommandons des ASN entre 64512 et 65534. Le choix reste libre, à l'exception des numéros suivants qui sont réservés pour OVHcloud : - - 65501 si le PoP est en Europe - - 65502 si le PoP est au Canada - - 65519 si le PoP est en Asie -- La zone AS d'OVHcloud BGP et votre numéro d'AS BGP (côté PoP) doivent être différents. -- La zone AS d'OVHcloud BGP : peut être la même entre la configuration côté DC et la configuration côté PoP (recommandé). - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.fr-fr.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.fr-fr.md deleted file mode 100644 index 3e1fb4be06d..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.fr-fr.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: "Résoudre les erreurs fréquentes lors de la mise en service de OVHcloud Connect" -excerpt: "Découvrez comment résoudre les erreurs les plus fréquentes liées à la mise en service de OVHcloud Connect" -updated: 2021-09-02 ---- - -## Objectif - -Découvrez comment résoudre les erreurs les plus fréquentes liées à la mise en service de OVHcloud Connect. - -## Prérequis - -- Posséder une [offre OVHcloud Connect](https://www.ovhcloud.com/fr/network-security/ovhcloud-connect/) - -## En pratique - -Un service OVHcloud Connect apparaît dans votre espace client OVHcloud et ne peut être configuré que lorsqu'il est considéré comme **livré**. - -En ce qui concerne l'offre **OVHcloud Connect Direct**, le service est **livré** dans les situations suivantes : - -- dès lors que OVHcloud détecte de la lumière sur la position indiquée dans la LOA. Cette détection suggère que l'interconnexion (Cross-Connect) a été réalisée par le client. -- au bout de 60 jours après la commande si aucune lumière n'a été détectée. - -### Vérification de la LOA - -Une mauvaise interprétation de la position sur l'interconnexion (Cross-Connect) par le PoP peut engendrer une absence de lumière sur le lien OVHcloud Connect Direct. -Par exemple, le PoP peut indiquer qu'il n'y a pas d'interconnexion sur la position mentionnée sur la LOA. - -#### Comment lire les informations sur la LOA ? - -Voici un exemple d'informations sur la LOA : - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -Voici l'interprétation de ces informations : - -- Cabinet (position de la baie où se trouve le RACK) : **103** -- Cage (RACK) : **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (position du switch) : **PP:0103:1132697** -- Position (sur le switch) : **16** -- FiberOptic / Port A : **31** -- FiberOptic / Port B : **32** -- Side (face avant ou arrière) : **BACK** -- Fiber Termination : **SC/PC** - -### OVHcloud Connect Direct (uniquement) : vérifier la présence de lumière sur le lien - -> [!warning] -> -> - Pour rappel, l'interconnexion (Cross-Connect) est contractuellement de votre responsabilité. -> - Avant de prendre contact avec les équipes OVHcloud, vous devez ouvrir un ticket auprès du PoP concerné par la LOA. -> - -#### Avant la livraison du service - -Lors de la commande d’un lien OVHcloud Connect Direct, il est possible de voir côté OVHcloud les valeurs optiques IN/OUT. Vous pouvez demander des informations à ce sujet à votre équipe support. - -Si le service n'est pas encore livré, nos équipes support pourront vérifier le statut des valeurs optiques IN et OUT côté infrastructure OVHcloud. - -#### Après la livraison du service - -Dans votre espace client OVHcloud, vérifiez les valeurs optiques IN/OUT : - -- Si la valeur **OUT** est « **DOWN** », les raisons suivantes peuvent en être à l'origine : - - le port côté OVHcloud n'émet pas de lumière; - - le service est en cours de résiliation; - - le port est verrouillé dans votre espace client OVHcloud; - - il y a un défaut sur le SFP. -- Si **IN** est « **DOWN** », les raisons suivantes peuvent en être à l'origine : - - votre équipement n'est pas encore branché; - - le port peut être désactivé ou a un défaut qui l'empêche d'émettre de la lumière; - - un défaut est présent au niveau de l'interconnexion (Cross Connect). - -### Inversion de fibre Tx/Rx - -S'il y a une inversion de fibre entre le Port A et le Port B, la lumière n'est pas reçue au bon endroit et le port **IN (Rx)** affichera **DOWN**. Si votre service n'est pas encore livré, contactez le support pour connaître l'état du lien. - -Prenez contact avec le PoP concerné par la LOA pour vérifier qu'il n'y a pas d'inversion Tx/Rx sur l'interconnexion (Cross Connect). - -### Vérification du peering - -La vérification du peering doit être faite une fois que la lumière est « **UP** » des deux côtés. - -Si le peering ne peut pas être établi (DOWN) d'un côté ou des deux côtés, cela peut avoir plusieurs raisons : - -- un défaut de SFP; -- l'auto-négociation n'est pas désactivée côté client; -- un conflit d'adresses IP; -- une mauvaise configuration du lien BGP. - -#### Configuration SFP - -Des valeurs optiques **UP** mais pas de lien Ethernet (interface **DOWN**) sont un symptôme d'un SFP mal configuré. - -Le SFP à utiliser sur l'équipement client pour une liaison OVHcloud Connect dépend du lien commandé. Vous devez utiliser un SFP conforme à la bande-passante commandée. - -Si vous avez commandé un lien 1 Gbit/s, le SFP sera: 1000Base-LX/LH. Utilisez la commande suivante : - -``` -speed 1000 -``` - -Si vous avez commandé un lien 10 Gbit/s, le SFP sera: 10GBase-LR. Utilisez la commande suivante : - -``` -speed 10000 -``` - -Pour plus d'informations, consultez les [capacités et limites techniques de l'offre OVHcloud Connect](/pages/network/ovhcloud_connect/occ-limits) - -#### Désactiver l'auto-négociation - -L'auto-négociation n'est pas supportée dans l'offre OVHcloud Connect. Ce paramètre doit être désactivé. - -Pour désactiver l'auto-négociation sur un équipement Cisco, utilisez la commande : - -``` -no negotiate auto -``` - -ou - -``` -no speed negotiate -``` - -Sur Cisco IOS, utilisez la commande suivante : - -``` -speed nonegotiate -``` - -Sur Cisco NX-OS, utilisez la commande suivante : - -``` -speed 1000 -no negotiate auto -``` - -#### Configuration IP du PoP/DC - -Un conflit d'adresses IP peut survenir si vous utilisez une/des adresse(s) IP normalement réservée(s) pour OVHcloud. - -Les règles d'attribution des adresses IP en fonction du subnet sont les suivantes : - -- subnet côté DC : /28 (valeur minimum) - Les trois premières adresses IP sont réservées pour OVHcloud - Vlan fixé à 0 (untagged). -- subnet côté PoP: /30 (valeur fixe) - La pemière adresse IP est réservée pour OVHcloud, deuxième adresse IP pour le client. - -#### Configuration du lien BGP - -La BGP Area côté client doit être différente de celle côté OVHcloud. - -- Range Area = AS BGP -- Numéro d'AS : Nous recommandons des ASN entre 64512 et 65534. Le choix reste libre, à l'exception des numéros suivants qui sont réservés pour OVHcloud : - - 65501 si le PoP est en Europe - - 65502 si le PoP est au Canada - - 65519 si le PoP est en Asie -- La zone AS d'OVHcloud BGP et votre numéro d'AS BGP (côté PoP) doivent être différents. -- La zone AS d'OVHcloud BGP : peut être la même entre la configuration côté DC et la configuration côté PoP (recommandé). - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.it-it.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.it-it.md deleted file mode 100644 index 8ebcf777431..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.it-it.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: Troubleshooting common errors setting up OVHcloud Connect -excerpt: Find out how to resolve the most common errors associated with setting up OVHcloud Connect -updated: 2021-09-02 ---- - -## Objective - -Find out how to resolve the most common errors associated with setting up OVHcloud Connect - -## Requirements - -- an [OVHcloud Connect solution](https://www.ovhcloud.com/it/network-security/ovhcloud-connect/) - -## Instructions - -An OVHcloud Connect service will appear in your OVHcloud Control Panel, and can only be configured when it is considered **delivered**. - -For the **OVHcloud Connect Direct** offer, the service is **delivered** in the following situations: - -- When OVHcloud detects light at the position indicated in the LOA. This detection suggests that the cross-connect was performed by the client. -- 60 days after the order if no light has been detected. - -### LOA verification - -A misinterpretation of the position on the Cross-Connect by the PoP can result in a lack of light on the OVHcloud Connect link. -For example, the PoP may indicate that there is no interconnection at the position mentioned on the LOA. - -#### How to read LOA information? - -Here is an example of information on the LOA: - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -This information is interpreted as follows: - -- Cabinet (position of the bay where the RACK is located): **103** -- Cage (RACK): **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (switch position): **PP:0103:1132697** -- Position (on switch): **16** -- FiberOptic / Port A: **31** -- FiberOptic / Port B: **32** -- Side (front or back): **BACK** -- Fiber Termination: **SC/PC** - -### OVHcloud Connect Direct (only): checking for light on the link - -> [!warning] -> -> - As a reminder, Cross-Connect is contractually your responsibility. -> - Before contacting the OVHcloud teams, you will need to open a ticket to the PoP concerned by the LOA. -> - -#### Before service delivery - -When you order an OVHcloud Connect link, the IN/OUT optical values can be checked on the OVHcloud side. You can request information about this from your support team. - -If the service has not yet been delivered, our support teams will be able to check the status of the IN and OUT optical values on the OVHcloud infrastructure side. - -#### After service delivery - -In the OVHcloud Control Panel, check the IN/OUT optical values: - -- If the **OUT** value is **DOWN**, , the following reasons may be the cause: - - the port on the OVHcloud side does not emit light - - the service is being cancelled - - the port is locked in your OVHcloud Control Panel - - there is an SFP issue -- If **IN** is **DOWN**, the following reasons may be the cause: - - your equipment is not yet connected - - the port can be disabled or has a defect that prevents it from emitting light - - there is a Cross-Connect issue - -### Tx/Rx Fiber inversion - -If there is a fiber inversion between Port A and Port B, the light is not received in the right place and the **IN (Rx)** port will display **DOWN**. If your service has not yet been delivered, contact the support teams so that the link status is checked. - -Contact the PoP concerned by the LOA to check that there is no Tx/Rx inversion on the Cross-Connect. - -### Peering verification - -The peering should be checked once the light is **UP** on both sides. - -If peering cannot be established (DOWN) on one or both sides, there may be several reasons: - -- An SFP issue -- Auto-negotiation is not disabled on the customer side -- IP address conflict -- BGP link misconfiguration - -#### SFP Configuration - -Optical values **UP** but no Ethernet link (interface **DOWN**) are a symptom of a misconfigured SFP. - -The SFP to use on the client device on an OVHcloud Connect link depends on the link you ordered. You must use an SFP that conforms to the ordered bandwidth. - -If you have ordered a 1 Gbps link, the SFP will be: 1000Base-LX/LH. - -``` -speed 1000 -``` - -If you have ordered a 10 Gbps link, the SFP will be: 10GBase-LR. - -``` -speed 10000 -``` - -For more information, please read the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) - -#### Disabling auto-negotiation - -Auto-negotiation is not supported in the OVHcloud Connect solution. This setting must be disabled. - -To disable auto-negotiation on a Cisco device, use the following command: - -``` -no negotiate auto -``` - -or - -``` -no speed negotiate -``` - -On Cisco IOS, use the following command: - -``` -speed nonegotiate -``` - -On Cisco NX-OS, use the following command: - -``` -speed 1000 -no negotiate auto -``` - -#### PoP/DC configuration - -An IP address conflict may occur if you are using an IP address(es) normally reserved for OVHcloud. - -The rules for assigning IP addresses according to the subnet are as follows: - -- DC-side subnet: /28 (minimum value) - The first three IP addresses are reserved for OVHcloud - Vlan fixed to 0 (untagged). -- PoP-side subnet: /30 (fixed value) - The first IP address is reserved for OVHcloud, the second IP address for the customer. - -#### Configuring the BGP link - -The BGP Area on the customer side must be different from the OVHcloud side. - -- Range Area = AS BGP -- AS number: We recommend ASNs between 64512 and 65534. The choice is your, with the exception of the following numbers, which are reserved for OVHcloud. - - 65501 if the PoP is in Europe - - 65502 if the PoP is in Canada - - 65519 if the PoP is in Asia -- The OVHcloud BGP AS zone and your BGP AS number (on the PoP side) must be different. -- The OVHcloud BGP AS zone: can be the same between the DC side and the PoP side configuration (recommended) - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.pl-pl.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.pl-pl.md deleted file mode 100644 index 07a17417264..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.pl-pl.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: Troubleshooting common errors setting up OVHcloud Connect -excerpt: Find out how to resolve the most common errors associated with setting up OVHcloud Connect -updated: 2021-09-02 ---- - -## Objective - -Find out how to resolve the most common errors associated with setting up OVHcloud Connect - -## Requirements - -- an [OVHcloud Connect solution](https://www.ovhcloud.com/pl/network-security/ovhcloud-connect/) - -## Instructions - -An OVHcloud Connect service will appear in your OVHcloud Control Panel, and can only be configured when it is considered **delivered**. - -For the **OVHcloud Connect Direct** offer, the service is **delivered** in the following situations: - -- When OVHcloud detects light at the position indicated in the LOA. This detection suggests that the cross-connect was performed by the client. -- 60 days after the order if no light has been detected. - -### LOA verification - -A misinterpretation of the position on the Cross-Connect by the PoP can result in a lack of light on the OVHcloud Connect link. -For example, the PoP may indicate that there is no interconnection at the position mentioned on the LOA. - -#### How to read LOA information? - -Here is an example of information on the LOA: - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -This information is interpreted as follows: - -- Cabinet (position of the bay where the RACK is located): **103** -- Cage (RACK): **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (switch position): **PP:0103:1132697** -- Position (on switch): **16** -- FiberOptic / Port A: **31** -- FiberOptic / Port B: **32** -- Side (front or back): **BACK** -- Fiber Termination: **SC/PC** - -### OVHcloud Connect Direct (only): checking for light on the link - -> [!warning] -> -> - As a reminder, Cross-Connect is contractually your responsibility. -> - Before contacting the OVHcloud teams, you will need to open a ticket to the PoP concerned by the LOA. -> - -#### Before service delivery - -When you order an OVHcloud Connect link, the IN/OUT optical values can be checked on the OVHcloud side. You can request information about this from your support team. - -If the service has not yet been delivered, our support teams will be able to check the status of the IN and OUT optical values on the OVHcloud infrastructure side. - -#### After service delivery - -In the OVHcloud Control Panel, check the IN/OUT optical values: - -- If the **OUT** value is **DOWN**, , the following reasons may be the cause: - - the port on the OVHcloud side does not emit light - - the service is being cancelled - - the port is locked in your OVHcloud Control Panel - - there is an SFP issue -- If **IN** is **DOWN**, the following reasons may be the cause: - - your equipment is not yet connected - - the port can be disabled or has a defect that prevents it from emitting light - - there is a Cross-Connect issue - -### Tx/Rx Fiber inversion - -If there is a fiber inversion between Port A and Port B, the light is not received in the right place and the **IN (Rx)** port will display **DOWN**. If your service has not yet been delivered, contact the support teams so that the link status is checked. - -Contact the PoP concerned by the LOA to check that there is no Tx/Rx inversion on the Cross-Connect. - -### Peering verification - -The peering should be checked once the light is **UP** on both sides. - -If peering cannot be established (DOWN) on one or both sides, there may be several reasons: - -- An SFP issue -- Auto-negotiation is not disabled on the customer side -- IP address conflict -- BGP link misconfiguration - -#### SFP Configuration - -Optical values **UP** but no Ethernet link (interface **DOWN**) are a symptom of a misconfigured SFP. - -The SFP to use on the client device on an OVHcloud Connect link depends on the link you ordered. You must use an SFP that conforms to the ordered bandwidth. - -If you have ordered a 1 Gbps link, the SFP will be: 1000Base-LX/LH. - -``` -speed 1000 -``` - -If you have ordered a 10 Gbps link, the SFP will be: 10GBase-LR. - -``` -speed 10000 -``` - -For more information, please read the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) - -#### Disabling auto-negotiation - -Auto-negotiation is not supported in the OVHcloud Connect solution. This setting must be disabled. - -To disable auto-negotiation on a Cisco device, use the following command: - -``` -no negotiate auto -``` - -or - -``` -no speed negotiate -``` - -On Cisco IOS, use the following command: - -``` -speed nonegotiate -``` - -On Cisco NX-OS, use the following command: - -``` -speed 1000 -no negotiate auto -``` - -#### PoP/DC configuration - -An IP address conflict may occur if you are using an IP address(es) normally reserved for OVHcloud. - -The rules for assigning IP addresses according to the subnet are as follows: - -- DC-side subnet: /28 (minimum value) - The first three IP addresses are reserved for OVHcloud - Vlan fixed to 0 (untagged). -- PoP-side subnet: /30 (fixed value) - The first IP address is reserved for OVHcloud, the second IP address for the customer. - -#### Configuring the BGP link - -The BGP Area on the customer side must be different from the OVHcloud side. - -- Range Area = AS BGP -- AS number: We recommend ASNs between 64512 and 65534. The choice is your, with the exception of the following numbers, which are reserved for OVHcloud. - - 65501 if the PoP is in Europe - - 65502 if the PoP is in Canada - - 65519 if the PoP is in Asia -- The OVHcloud BGP AS zone and your BGP AS number (on the PoP side) must be different. -- The OVHcloud BGP AS zone: can be the same between the DC side and the PoP side configuration (recommended) - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.pt-pt.md b/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.pt-pt.md deleted file mode 100644 index df6e1099ffa..00000000000 --- a/pages/network/ovhcloud_connect/occ-setup-diagnostics/guide.pt-pt.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -title: Troubleshooting common errors setting up OVHcloud Connect -excerpt: Find out how to resolve the most common errors associated with setting up OVHcloud Connect -updated: 2021-09-02 ---- - -## Objective - -Find out how to resolve the most common errors associated with setting up OVHcloud Connect - -## Requirements - -- an [OVHcloud Connect solution](https://www.ovhcloud.com/pt/network-security/ovhcloud-connect/) - -## Instructions - -An OVHcloud Connect service will appear in your OVHcloud Control Panel, and can only be configured when it is considered **delivered**. - -For the **OVHcloud Connect Direct** offer, the service is **delivered** in the following situations: - -- When OVHcloud detects light at the position indicated in the LOA. This detection suggests that the cross-connect was performed by the client. -- 60 days after the order if no light has been detected. - -### LOA verification - -A misinterpretation of the position on the Cross-Connect by the PoP can result in a lack of light on the OVHcloud Connect link. -For example, the PoP may indicate that there is no interconnection at the position mentioned on the LOA. - -#### How to read LOA information? - -Here is an example of information on the LOA: - -``` -Equipment: 103 PA3:OG:00GMC3:OVH Patch Panel: PP:0103:1132697 -Port: P16/FO31-32/BCK Fiber Termination: SC/PC -``` - -This information is interpreted as follows: - -- Cabinet (position of the bay where the RACK is located): **103** -- Cage (RACK): **PA3:OG:00GMC3:OVH** -- PatchPanel Z-side (switch position): **PP:0103:1132697** -- Position (on switch): **16** -- FiberOptic / Port A: **31** -- FiberOptic / Port B: **32** -- Side (front or back): **BACK** -- Fiber Termination: **SC/PC** - -### OVHcloud Connect Direct (only): checking for light on the link - -> [!warning] -> -> - As a reminder, Cross-Connect is contractually your responsibility. -> - Before contacting the OVHcloud teams, you will need to open a ticket to the PoP concerned by the LOA. -> - -#### Before service delivery - -When you order an OVHcloud Connect link, the IN/OUT optical values can be checked on the OVHcloud side. You can request information about this from your support team. - -If the service has not yet been delivered, our support teams will be able to check the status of the IN and OUT optical values on the OVHcloud infrastructure side. - -#### After service delivery - -In the OVHcloud Control Panel, check the IN/OUT optical values: - -- If the **OUT** value is **DOWN**, , the following reasons may be the cause: - - the port on the OVHcloud side does not emit light - - the service is being cancelled - - the port is locked in your OVHcloud Control Panel - - there is an SFP issue -- If **IN** is **DOWN**, the following reasons may be the cause: - - your equipment is not yet connected - - the port can be disabled or has a defect that prevents it from emitting light - - there is a Cross-Connect issue - -### Tx/Rx Fiber inversion - -If there is a fiber inversion between Port A and Port B, the light is not received in the right place and the **IN (Rx)** port will display **DOWN**. If your service has not yet been delivered, contact the support teams so that the link status is checked. - -Contact the PoP concerned by the LOA to check that there is no Tx/Rx inversion on the Cross-Connect. - -### Peering verification - -The peering should be checked once the light is **UP** on both sides. - -If peering cannot be established (DOWN) on one or both sides, there may be several reasons: - -- An SFP issue -- Auto-negotiation is not disabled on the customer side -- IP address conflict -- BGP link misconfiguration - -#### SFP Configuration - -Optical values **UP** but no Ethernet link (interface **DOWN**) are a symptom of a misconfigured SFP. - -The SFP to use on the client device on an OVHcloud Connect link depends on the link you ordered. You must use an SFP that conforms to the ordered bandwidth. - -If you have ordered a 1 Gbps link, the SFP will be: 1000Base-LX/LH. - -``` -speed 1000 -``` - -If you have ordered a 10 Gbps link, the SFP will be: 10GBase-LR. - -``` -speed 10000 -``` - -For more information, please read the [technical capabilities and limitations of the OVHcloud Connect solution](/pages/network/ovhcloud_connect/occ-limits) - -#### Disabling auto-negotiation - -Auto-negotiation is not supported in the OVHcloud Connect solution. This setting must be disabled. - -To disable auto-negotiation on a Cisco device, use the following command: - -``` -no negotiate auto -``` - -or - -``` -no speed negotiate -``` - -On Cisco IOS, use the following command: - -``` -speed nonegotiate -``` - -On Cisco NX-OS, use the following command: - -``` -speed 1000 -no negotiate auto -``` - -#### PoP/DC configuration - -An IP address conflict may occur if you are using an IP address(es) normally reserved for OVHcloud. - -The rules for assigning IP addresses according to the subnet are as follows: - -- DC-side subnet: /28 (minimum value) - The first three IP addresses are reserved for OVHcloud - Vlan fixed to 0 (untagged). -- PoP-side subnet: /30 (fixed value) - The first IP address is reserved for OVHcloud, the second IP address for the customer. - -#### Configuring the BGP link - -The BGP Area on the customer side must be different from the OVHcloud side. - -- Range Area = AS BGP -- AS number: We recommend ASNs between 64512 and 65534. The choice is your, with the exception of the following numbers, which are reserved for OVHcloud. - - 65501 if the PoP is in Europe - - 65502 if the PoP is in Canada - - 65519 if the PoP is in Asia -- The OVHcloud BGP AS zone and your BGP AS number (on the PoP side) must be different. -- The OVHcloud BGP AS zone: can be the same between the DC side and the PoP side configuration (recommended) - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.de-de.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.de-de.md deleted file mode 100644 index 50fbb184e40..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.de-de.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## OVHcloud Connect FAQ - -### What is the OVHcloud Connect solution designed for? - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -### Which products are compatible with OVHcloud Connect? - -OVHcloud Connect is an extension of your OVHcloud vRack private network, so all products with the vRack feature enabled will be compatible. - -### How do I choose between a Layer 2 or Layer 3 cross-connection for the OSI model? - -You will need to keep in mind the features associated with Layer 2 and Layer 3 networks as you build your infrastructure, in order to select the best cross-connection for your hybrid cloud requirements. - -#### Layer 2 OSI - -The OVHcloud Connect solution dedicated to Layer 2 means that the connection is transparent to the Ethernet protocol. - -The advantage of a Layer 2 connection is that it simplifies the way you connect your data centre’s campus network to your OVHcloud vRack private network. - -You will need basic knowledge of how to use LAN networks. - -Redundancy can be local within the same point of presence (PoP), using LACP 802.3ad protocol. - -The virtual local area networks (VLANs) are the same in your data centre and within OVHcloud data centres. - -#### Layer 3 OSI - -The OVHcloud Connect solution dedicated to Layer 3 is a connection managed by routers. - -The advantage of a Layer 3 cross-connection is that you can connect your company’s WAN network to your OVHcloud vRack private network, so that it is considered as a site within your WAN network. - -You will need an advanced understanding of MAN and WAN networks, as well as knowledge of how to manage inter-network routing. - -Layer 3 networks require one or more private external BGP sessions to be established between the company and OVHcloud. - -Redundancy can be local within the same PoP, and geographical between two PoPs using BGP redundancy mechanisms. - -The VLANs are **not** the same in your data centre and within OVHcloud data centres. - -### Can OVHcloud host my routers? - -OVHcloud does not host network hardware for customers in data centres and PoPs. Customers need to have their hardware hosted by an operator or by a third party, then request a connection to OVHcloud hardware in the MMR (meet-me room) of the PoP. Instructions on how to do this are provided in the Letter of Authorisation (LOA). - -### What connections are supported for OVHcloud Connect? - -We support single-mode fibre optic. Your SFP/SFP+ must support either 1000LX/LH or 10G-LR. - -### When will my OVHcloud Connect service be delivered and available for configuration? - -An OVHcloud Connect service has to be delivered first before it can be configured. - -OVHcloud Connect Provider solutions will be delivered as soon as the *service key* is sent to the customer by email. This happens a few minutes after subscribing to the corresponding service. - -OVHcloud Connect Direct solutions are considered delivered in the following cases: - -- The light indicating the connection to the customer's equipment is visible on OVHcloud's side. -- 60 days have passed since the subscription. -- The customer has explicitly arranged a manual delivery with their OVHcloud agent. - -After having subscribed, the customer will receive a Letter of Authorization (LOA) from OVHcloud to allow the customer to perform the cross-connection with OVHcloud's infrastructure. This cross-connection will then trigger the delivery based on the above mentioned cases. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-asia.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-asia.md deleted file mode 100644 index 50fbb184e40..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-asia.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## OVHcloud Connect FAQ - -### What is the OVHcloud Connect solution designed for? - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -### Which products are compatible with OVHcloud Connect? - -OVHcloud Connect is an extension of your OVHcloud vRack private network, so all products with the vRack feature enabled will be compatible. - -### How do I choose between a Layer 2 or Layer 3 cross-connection for the OSI model? - -You will need to keep in mind the features associated with Layer 2 and Layer 3 networks as you build your infrastructure, in order to select the best cross-connection for your hybrid cloud requirements. - -#### Layer 2 OSI - -The OVHcloud Connect solution dedicated to Layer 2 means that the connection is transparent to the Ethernet protocol. - -The advantage of a Layer 2 connection is that it simplifies the way you connect your data centre’s campus network to your OVHcloud vRack private network. - -You will need basic knowledge of how to use LAN networks. - -Redundancy can be local within the same point of presence (PoP), using LACP 802.3ad protocol. - -The virtual local area networks (VLANs) are the same in your data centre and within OVHcloud data centres. - -#### Layer 3 OSI - -The OVHcloud Connect solution dedicated to Layer 3 is a connection managed by routers. - -The advantage of a Layer 3 cross-connection is that you can connect your company’s WAN network to your OVHcloud vRack private network, so that it is considered as a site within your WAN network. - -You will need an advanced understanding of MAN and WAN networks, as well as knowledge of how to manage inter-network routing. - -Layer 3 networks require one or more private external BGP sessions to be established between the company and OVHcloud. - -Redundancy can be local within the same PoP, and geographical between two PoPs using BGP redundancy mechanisms. - -The VLANs are **not** the same in your data centre and within OVHcloud data centres. - -### Can OVHcloud host my routers? - -OVHcloud does not host network hardware for customers in data centres and PoPs. Customers need to have their hardware hosted by an operator or by a third party, then request a connection to OVHcloud hardware in the MMR (meet-me room) of the PoP. Instructions on how to do this are provided in the Letter of Authorisation (LOA). - -### What connections are supported for OVHcloud Connect? - -We support single-mode fibre optic. Your SFP/SFP+ must support either 1000LX/LH or 10G-LR. - -### When will my OVHcloud Connect service be delivered and available for configuration? - -An OVHcloud Connect service has to be delivered first before it can be configured. - -OVHcloud Connect Provider solutions will be delivered as soon as the *service key* is sent to the customer by email. This happens a few minutes after subscribing to the corresponding service. - -OVHcloud Connect Direct solutions are considered delivered in the following cases: - -- The light indicating the connection to the customer's equipment is visible on OVHcloud's side. -- 60 days have passed since the subscription. -- The customer has explicitly arranged a manual delivery with their OVHcloud agent. - -After having subscribed, the customer will receive a Letter of Authorization (LOA) from OVHcloud to allow the customer to perform the cross-connection with OVHcloud's infrastructure. This cross-connection will then trigger the delivery based on the above mentioned cases. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-au.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-au.md deleted file mode 100644 index 50fbb184e40..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-au.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## OVHcloud Connect FAQ - -### What is the OVHcloud Connect solution designed for? - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -### Which products are compatible with OVHcloud Connect? - -OVHcloud Connect is an extension of your OVHcloud vRack private network, so all products with the vRack feature enabled will be compatible. - -### How do I choose between a Layer 2 or Layer 3 cross-connection for the OSI model? - -You will need to keep in mind the features associated with Layer 2 and Layer 3 networks as you build your infrastructure, in order to select the best cross-connection for your hybrid cloud requirements. - -#### Layer 2 OSI - -The OVHcloud Connect solution dedicated to Layer 2 means that the connection is transparent to the Ethernet protocol. - -The advantage of a Layer 2 connection is that it simplifies the way you connect your data centre’s campus network to your OVHcloud vRack private network. - -You will need basic knowledge of how to use LAN networks. - -Redundancy can be local within the same point of presence (PoP), using LACP 802.3ad protocol. - -The virtual local area networks (VLANs) are the same in your data centre and within OVHcloud data centres. - -#### Layer 3 OSI - -The OVHcloud Connect solution dedicated to Layer 3 is a connection managed by routers. - -The advantage of a Layer 3 cross-connection is that you can connect your company’s WAN network to your OVHcloud vRack private network, so that it is considered as a site within your WAN network. - -You will need an advanced understanding of MAN and WAN networks, as well as knowledge of how to manage inter-network routing. - -Layer 3 networks require one or more private external BGP sessions to be established between the company and OVHcloud. - -Redundancy can be local within the same PoP, and geographical between two PoPs using BGP redundancy mechanisms. - -The VLANs are **not** the same in your data centre and within OVHcloud data centres. - -### Can OVHcloud host my routers? - -OVHcloud does not host network hardware for customers in data centres and PoPs. Customers need to have their hardware hosted by an operator or by a third party, then request a connection to OVHcloud hardware in the MMR (meet-me room) of the PoP. Instructions on how to do this are provided in the Letter of Authorisation (LOA). - -### What connections are supported for OVHcloud Connect? - -We support single-mode fibre optic. Your SFP/SFP+ must support either 1000LX/LH or 10G-LR. - -### When will my OVHcloud Connect service be delivered and available for configuration? - -An OVHcloud Connect service has to be delivered first before it can be configured. - -OVHcloud Connect Provider solutions will be delivered as soon as the *service key* is sent to the customer by email. This happens a few minutes after subscribing to the corresponding service. - -OVHcloud Connect Direct solutions are considered delivered in the following cases: - -- The light indicating the connection to the customer's equipment is visible on OVHcloud's side. -- 60 days have passed since the subscription. -- The customer has explicitly arranged a manual delivery with their OVHcloud agent. - -After having subscribed, the customer will receive a Letter of Authorization (LOA) from OVHcloud to allow the customer to perform the cross-connection with OVHcloud's infrastructure. This cross-connection will then trigger the delivery based on the above mentioned cases. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-ca.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-ca.md deleted file mode 100644 index 50fbb184e40..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-ca.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## OVHcloud Connect FAQ - -### What is the OVHcloud Connect solution designed for? - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -### Which products are compatible with OVHcloud Connect? - -OVHcloud Connect is an extension of your OVHcloud vRack private network, so all products with the vRack feature enabled will be compatible. - -### How do I choose between a Layer 2 or Layer 3 cross-connection for the OSI model? - -You will need to keep in mind the features associated with Layer 2 and Layer 3 networks as you build your infrastructure, in order to select the best cross-connection for your hybrid cloud requirements. - -#### Layer 2 OSI - -The OVHcloud Connect solution dedicated to Layer 2 means that the connection is transparent to the Ethernet protocol. - -The advantage of a Layer 2 connection is that it simplifies the way you connect your data centre’s campus network to your OVHcloud vRack private network. - -You will need basic knowledge of how to use LAN networks. - -Redundancy can be local within the same point of presence (PoP), using LACP 802.3ad protocol. - -The virtual local area networks (VLANs) are the same in your data centre and within OVHcloud data centres. - -#### Layer 3 OSI - -The OVHcloud Connect solution dedicated to Layer 3 is a connection managed by routers. - -The advantage of a Layer 3 cross-connection is that you can connect your company’s WAN network to your OVHcloud vRack private network, so that it is considered as a site within your WAN network. - -You will need an advanced understanding of MAN and WAN networks, as well as knowledge of how to manage inter-network routing. - -Layer 3 networks require one or more private external BGP sessions to be established between the company and OVHcloud. - -Redundancy can be local within the same PoP, and geographical between two PoPs using BGP redundancy mechanisms. - -The VLANs are **not** the same in your data centre and within OVHcloud data centres. - -### Can OVHcloud host my routers? - -OVHcloud does not host network hardware for customers in data centres and PoPs. Customers need to have their hardware hosted by an operator or by a third party, then request a connection to OVHcloud hardware in the MMR (meet-me room) of the PoP. Instructions on how to do this are provided in the Letter of Authorisation (LOA). - -### What connections are supported for OVHcloud Connect? - -We support single-mode fibre optic. Your SFP/SFP+ must support either 1000LX/LH or 10G-LR. - -### When will my OVHcloud Connect service be delivered and available for configuration? - -An OVHcloud Connect service has to be delivered first before it can be configured. - -OVHcloud Connect Provider solutions will be delivered as soon as the *service key* is sent to the customer by email. This happens a few minutes after subscribing to the corresponding service. - -OVHcloud Connect Direct solutions are considered delivered in the following cases: - -- The light indicating the connection to the customer's equipment is visible on OVHcloud's side. -- 60 days have passed since the subscription. -- The customer has explicitly arranged a manual delivery with their OVHcloud agent. - -After having subscribed, the customer will receive a Letter of Authorization (LOA) from OVHcloud to allow the customer to perform the cross-connection with OVHcloud's infrastructure. This cross-connection will then trigger the delivery based on the above mentioned cases. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-gb.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-gb.md deleted file mode 100644 index 50fbb184e40..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-gb.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## OVHcloud Connect FAQ - -### What is the OVHcloud Connect solution designed for? - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -### Which products are compatible with OVHcloud Connect? - -OVHcloud Connect is an extension of your OVHcloud vRack private network, so all products with the vRack feature enabled will be compatible. - -### How do I choose between a Layer 2 or Layer 3 cross-connection for the OSI model? - -You will need to keep in mind the features associated with Layer 2 and Layer 3 networks as you build your infrastructure, in order to select the best cross-connection for your hybrid cloud requirements. - -#### Layer 2 OSI - -The OVHcloud Connect solution dedicated to Layer 2 means that the connection is transparent to the Ethernet protocol. - -The advantage of a Layer 2 connection is that it simplifies the way you connect your data centre’s campus network to your OVHcloud vRack private network. - -You will need basic knowledge of how to use LAN networks. - -Redundancy can be local within the same point of presence (PoP), using LACP 802.3ad protocol. - -The virtual local area networks (VLANs) are the same in your data centre and within OVHcloud data centres. - -#### Layer 3 OSI - -The OVHcloud Connect solution dedicated to Layer 3 is a connection managed by routers. - -The advantage of a Layer 3 cross-connection is that you can connect your company’s WAN network to your OVHcloud vRack private network, so that it is considered as a site within your WAN network. - -You will need an advanced understanding of MAN and WAN networks, as well as knowledge of how to manage inter-network routing. - -Layer 3 networks require one or more private external BGP sessions to be established between the company and OVHcloud. - -Redundancy can be local within the same PoP, and geographical between two PoPs using BGP redundancy mechanisms. - -The VLANs are **not** the same in your data centre and within OVHcloud data centres. - -### Can OVHcloud host my routers? - -OVHcloud does not host network hardware for customers in data centres and PoPs. Customers need to have their hardware hosted by an operator or by a third party, then request a connection to OVHcloud hardware in the MMR (meet-me room) of the PoP. Instructions on how to do this are provided in the Letter of Authorisation (LOA). - -### What connections are supported for OVHcloud Connect? - -We support single-mode fibre optic. Your SFP/SFP+ must support either 1000LX/LH or 10G-LR. - -### When will my OVHcloud Connect service be delivered and available for configuration? - -An OVHcloud Connect service has to be delivered first before it can be configured. - -OVHcloud Connect Provider solutions will be delivered as soon as the *service key* is sent to the customer by email. This happens a few minutes after subscribing to the corresponding service. - -OVHcloud Connect Direct solutions are considered delivered in the following cases: - -- The light indicating the connection to the customer's equipment is visible on OVHcloud's side. -- 60 days have passed since the subscription. -- The customer has explicitly arranged a manual delivery with their OVHcloud agent. - -After having subscribed, the customer will receive a Letter of Authorization (LOA) from OVHcloud to allow the customer to perform the cross-connection with OVHcloud's infrastructure. This cross-connection will then trigger the delivery based on the above mentioned cases. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-ie.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-ie.md deleted file mode 100644 index 50fbb184e40..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-ie.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## OVHcloud Connect FAQ - -### What is the OVHcloud Connect solution designed for? - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -### Which products are compatible with OVHcloud Connect? - -OVHcloud Connect is an extension of your OVHcloud vRack private network, so all products with the vRack feature enabled will be compatible. - -### How do I choose between a Layer 2 or Layer 3 cross-connection for the OSI model? - -You will need to keep in mind the features associated with Layer 2 and Layer 3 networks as you build your infrastructure, in order to select the best cross-connection for your hybrid cloud requirements. - -#### Layer 2 OSI - -The OVHcloud Connect solution dedicated to Layer 2 means that the connection is transparent to the Ethernet protocol. - -The advantage of a Layer 2 connection is that it simplifies the way you connect your data centre’s campus network to your OVHcloud vRack private network. - -You will need basic knowledge of how to use LAN networks. - -Redundancy can be local within the same point of presence (PoP), using LACP 802.3ad protocol. - -The virtual local area networks (VLANs) are the same in your data centre and within OVHcloud data centres. - -#### Layer 3 OSI - -The OVHcloud Connect solution dedicated to Layer 3 is a connection managed by routers. - -The advantage of a Layer 3 cross-connection is that you can connect your company’s WAN network to your OVHcloud vRack private network, so that it is considered as a site within your WAN network. - -You will need an advanced understanding of MAN and WAN networks, as well as knowledge of how to manage inter-network routing. - -Layer 3 networks require one or more private external BGP sessions to be established between the company and OVHcloud. - -Redundancy can be local within the same PoP, and geographical between two PoPs using BGP redundancy mechanisms. - -The VLANs are **not** the same in your data centre and within OVHcloud data centres. - -### Can OVHcloud host my routers? - -OVHcloud does not host network hardware for customers in data centres and PoPs. Customers need to have their hardware hosted by an operator or by a third party, then request a connection to OVHcloud hardware in the MMR (meet-me room) of the PoP. Instructions on how to do this are provided in the Letter of Authorisation (LOA). - -### What connections are supported for OVHcloud Connect? - -We support single-mode fibre optic. Your SFP/SFP+ must support either 1000LX/LH or 10G-LR. - -### When will my OVHcloud Connect service be delivered and available for configuration? - -An OVHcloud Connect service has to be delivered first before it can be configured. - -OVHcloud Connect Provider solutions will be delivered as soon as the *service key* is sent to the customer by email. This happens a few minutes after subscribing to the corresponding service. - -OVHcloud Connect Direct solutions are considered delivered in the following cases: - -- The light indicating the connection to the customer's equipment is visible on OVHcloud's side. -- 60 days have passed since the subscription. -- The customer has explicitly arranged a manual delivery with their OVHcloud agent. - -After having subscribed, the customer will receive a Letter of Authorization (LOA) from OVHcloud to allow the customer to perform the cross-connection with OVHcloud's infrastructure. This cross-connection will then trigger the delivery based on the above mentioned cases. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-sg.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-sg.md deleted file mode 100644 index 50fbb184e40..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-sg.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## OVHcloud Connect FAQ - -### What is the OVHcloud Connect solution designed for? - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -### Which products are compatible with OVHcloud Connect? - -OVHcloud Connect is an extension of your OVHcloud vRack private network, so all products with the vRack feature enabled will be compatible. - -### How do I choose between a Layer 2 or Layer 3 cross-connection for the OSI model? - -You will need to keep in mind the features associated with Layer 2 and Layer 3 networks as you build your infrastructure, in order to select the best cross-connection for your hybrid cloud requirements. - -#### Layer 2 OSI - -The OVHcloud Connect solution dedicated to Layer 2 means that the connection is transparent to the Ethernet protocol. - -The advantage of a Layer 2 connection is that it simplifies the way you connect your data centre’s campus network to your OVHcloud vRack private network. - -You will need basic knowledge of how to use LAN networks. - -Redundancy can be local within the same point of presence (PoP), using LACP 802.3ad protocol. - -The virtual local area networks (VLANs) are the same in your data centre and within OVHcloud data centres. - -#### Layer 3 OSI - -The OVHcloud Connect solution dedicated to Layer 3 is a connection managed by routers. - -The advantage of a Layer 3 cross-connection is that you can connect your company’s WAN network to your OVHcloud vRack private network, so that it is considered as a site within your WAN network. - -You will need an advanced understanding of MAN and WAN networks, as well as knowledge of how to manage inter-network routing. - -Layer 3 networks require one or more private external BGP sessions to be established between the company and OVHcloud. - -Redundancy can be local within the same PoP, and geographical between two PoPs using BGP redundancy mechanisms. - -The VLANs are **not** the same in your data centre and within OVHcloud data centres. - -### Can OVHcloud host my routers? - -OVHcloud does not host network hardware for customers in data centres and PoPs. Customers need to have their hardware hosted by an operator or by a third party, then request a connection to OVHcloud hardware in the MMR (meet-me room) of the PoP. Instructions on how to do this are provided in the Letter of Authorisation (LOA). - -### What connections are supported for OVHcloud Connect? - -We support single-mode fibre optic. Your SFP/SFP+ must support either 1000LX/LH or 10G-LR. - -### When will my OVHcloud Connect service be delivered and available for configuration? - -An OVHcloud Connect service has to be delivered first before it can be configured. - -OVHcloud Connect Provider solutions will be delivered as soon as the *service key* is sent to the customer by email. This happens a few minutes after subscribing to the corresponding service. - -OVHcloud Connect Direct solutions are considered delivered in the following cases: - -- The light indicating the connection to the customer's equipment is visible on OVHcloud's side. -- 60 days have passed since the subscription. -- The customer has explicitly arranged a manual delivery with their OVHcloud agent. - -After having subscribed, the customer will receive a Letter of Authorization (LOA) from OVHcloud to allow the customer to perform the cross-connection with OVHcloud's infrastructure. This cross-connection will then trigger the delivery based on the above mentioned cases. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-us.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-us.md deleted file mode 100644 index 50fbb184e40..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.en-us.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## OVHcloud Connect FAQ - -### What is the OVHcloud Connect solution designed for? - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -### Which products are compatible with OVHcloud Connect? - -OVHcloud Connect is an extension of your OVHcloud vRack private network, so all products with the vRack feature enabled will be compatible. - -### How do I choose between a Layer 2 or Layer 3 cross-connection for the OSI model? - -You will need to keep in mind the features associated with Layer 2 and Layer 3 networks as you build your infrastructure, in order to select the best cross-connection for your hybrid cloud requirements. - -#### Layer 2 OSI - -The OVHcloud Connect solution dedicated to Layer 2 means that the connection is transparent to the Ethernet protocol. - -The advantage of a Layer 2 connection is that it simplifies the way you connect your data centre’s campus network to your OVHcloud vRack private network. - -You will need basic knowledge of how to use LAN networks. - -Redundancy can be local within the same point of presence (PoP), using LACP 802.3ad protocol. - -The virtual local area networks (VLANs) are the same in your data centre and within OVHcloud data centres. - -#### Layer 3 OSI - -The OVHcloud Connect solution dedicated to Layer 3 is a connection managed by routers. - -The advantage of a Layer 3 cross-connection is that you can connect your company’s WAN network to your OVHcloud vRack private network, so that it is considered as a site within your WAN network. - -You will need an advanced understanding of MAN and WAN networks, as well as knowledge of how to manage inter-network routing. - -Layer 3 networks require one or more private external BGP sessions to be established between the company and OVHcloud. - -Redundancy can be local within the same PoP, and geographical between two PoPs using BGP redundancy mechanisms. - -The VLANs are **not** the same in your data centre and within OVHcloud data centres. - -### Can OVHcloud host my routers? - -OVHcloud does not host network hardware for customers in data centres and PoPs. Customers need to have their hardware hosted by an operator or by a third party, then request a connection to OVHcloud hardware in the MMR (meet-me room) of the PoP. Instructions on how to do this are provided in the Letter of Authorisation (LOA). - -### What connections are supported for OVHcloud Connect? - -We support single-mode fibre optic. Your SFP/SFP+ must support either 1000LX/LH or 10G-LR. - -### When will my OVHcloud Connect service be delivered and available for configuration? - -An OVHcloud Connect service has to be delivered first before it can be configured. - -OVHcloud Connect Provider solutions will be delivered as soon as the *service key* is sent to the customer by email. This happens a few minutes after subscribing to the corresponding service. - -OVHcloud Connect Direct solutions are considered delivered in the following cases: - -- The light indicating the connection to the customer's equipment is visible on OVHcloud's side. -- 60 days have passed since the subscription. -- The customer has explicitly arranged a manual delivery with their OVHcloud agent. - -After having subscribed, the customer will receive a Letter of Authorization (LOA) from OVHcloud to allow the customer to perform the cross-connection with OVHcloud's infrastructure. This cross-connection will then trigger the delivery based on the above mentioned cases. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.es-es.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.es-es.md deleted file mode 100644 index 50fbb184e40..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.es-es.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## OVHcloud Connect FAQ - -### What is the OVHcloud Connect solution designed for? - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -### Which products are compatible with OVHcloud Connect? - -OVHcloud Connect is an extension of your OVHcloud vRack private network, so all products with the vRack feature enabled will be compatible. - -### How do I choose between a Layer 2 or Layer 3 cross-connection for the OSI model? - -You will need to keep in mind the features associated with Layer 2 and Layer 3 networks as you build your infrastructure, in order to select the best cross-connection for your hybrid cloud requirements. - -#### Layer 2 OSI - -The OVHcloud Connect solution dedicated to Layer 2 means that the connection is transparent to the Ethernet protocol. - -The advantage of a Layer 2 connection is that it simplifies the way you connect your data centre’s campus network to your OVHcloud vRack private network. - -You will need basic knowledge of how to use LAN networks. - -Redundancy can be local within the same point of presence (PoP), using LACP 802.3ad protocol. - -The virtual local area networks (VLANs) are the same in your data centre and within OVHcloud data centres. - -#### Layer 3 OSI - -The OVHcloud Connect solution dedicated to Layer 3 is a connection managed by routers. - -The advantage of a Layer 3 cross-connection is that you can connect your company’s WAN network to your OVHcloud vRack private network, so that it is considered as a site within your WAN network. - -You will need an advanced understanding of MAN and WAN networks, as well as knowledge of how to manage inter-network routing. - -Layer 3 networks require one or more private external BGP sessions to be established between the company and OVHcloud. - -Redundancy can be local within the same PoP, and geographical between two PoPs using BGP redundancy mechanisms. - -The VLANs are **not** the same in your data centre and within OVHcloud data centres. - -### Can OVHcloud host my routers? - -OVHcloud does not host network hardware for customers in data centres and PoPs. Customers need to have their hardware hosted by an operator or by a third party, then request a connection to OVHcloud hardware in the MMR (meet-me room) of the PoP. Instructions on how to do this are provided in the Letter of Authorisation (LOA). - -### What connections are supported for OVHcloud Connect? - -We support single-mode fibre optic. Your SFP/SFP+ must support either 1000LX/LH or 10G-LR. - -### When will my OVHcloud Connect service be delivered and available for configuration? - -An OVHcloud Connect service has to be delivered first before it can be configured. - -OVHcloud Connect Provider solutions will be delivered as soon as the *service key* is sent to the customer by email. This happens a few minutes after subscribing to the corresponding service. - -OVHcloud Connect Direct solutions are considered delivered in the following cases: - -- The light indicating the connection to the customer's equipment is visible on OVHcloud's side. -- 60 days have passed since the subscription. -- The customer has explicitly arranged a manual delivery with their OVHcloud agent. - -After having subscribed, the customer will receive a Letter of Authorization (LOA) from OVHcloud to allow the customer to perform the cross-connection with OVHcloud's infrastructure. This cross-connection will then trigger the delivery based on the above mentioned cases. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.es-us.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.es-us.md deleted file mode 100644 index 50fbb184e40..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.es-us.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## OVHcloud Connect FAQ - -### What is the OVHcloud Connect solution designed for? - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -### Which products are compatible with OVHcloud Connect? - -OVHcloud Connect is an extension of your OVHcloud vRack private network, so all products with the vRack feature enabled will be compatible. - -### How do I choose between a Layer 2 or Layer 3 cross-connection for the OSI model? - -You will need to keep in mind the features associated with Layer 2 and Layer 3 networks as you build your infrastructure, in order to select the best cross-connection for your hybrid cloud requirements. - -#### Layer 2 OSI - -The OVHcloud Connect solution dedicated to Layer 2 means that the connection is transparent to the Ethernet protocol. - -The advantage of a Layer 2 connection is that it simplifies the way you connect your data centre’s campus network to your OVHcloud vRack private network. - -You will need basic knowledge of how to use LAN networks. - -Redundancy can be local within the same point of presence (PoP), using LACP 802.3ad protocol. - -The virtual local area networks (VLANs) are the same in your data centre and within OVHcloud data centres. - -#### Layer 3 OSI - -The OVHcloud Connect solution dedicated to Layer 3 is a connection managed by routers. - -The advantage of a Layer 3 cross-connection is that you can connect your company’s WAN network to your OVHcloud vRack private network, so that it is considered as a site within your WAN network. - -You will need an advanced understanding of MAN and WAN networks, as well as knowledge of how to manage inter-network routing. - -Layer 3 networks require one or more private external BGP sessions to be established between the company and OVHcloud. - -Redundancy can be local within the same PoP, and geographical between two PoPs using BGP redundancy mechanisms. - -The VLANs are **not** the same in your data centre and within OVHcloud data centres. - -### Can OVHcloud host my routers? - -OVHcloud does not host network hardware for customers in data centres and PoPs. Customers need to have their hardware hosted by an operator or by a third party, then request a connection to OVHcloud hardware in the MMR (meet-me room) of the PoP. Instructions on how to do this are provided in the Letter of Authorisation (LOA). - -### What connections are supported for OVHcloud Connect? - -We support single-mode fibre optic. Your SFP/SFP+ must support either 1000LX/LH or 10G-LR. - -### When will my OVHcloud Connect service be delivered and available for configuration? - -An OVHcloud Connect service has to be delivered first before it can be configured. - -OVHcloud Connect Provider solutions will be delivered as soon as the *service key* is sent to the customer by email. This happens a few minutes after subscribing to the corresponding service. - -OVHcloud Connect Direct solutions are considered delivered in the following cases: - -- The light indicating the connection to the customer's equipment is visible on OVHcloud's side. -- 60 days have passed since the subscription. -- The customer has explicitly arranged a manual delivery with their OVHcloud agent. - -After having subscribed, the customer will receive a Letter of Authorization (LOA) from OVHcloud to allow the customer to perform the cross-connection with OVHcloud's infrastructure. This cross-connection will then trigger the delivery based on the above mentioned cases. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.fr-ca.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.fr-ca.md deleted file mode 100644 index a75d5808906..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.fr-ca.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## FAQ Ovhcloud Connect - -### À quoi sert la solution OVHcloud Connect ? - -OVHcloud Connect permet d'étendre votre réseau d'entreprise avec votre réseau privé OVHcloud vRack sans passer par l'établissement d'un tunnel VPN à travers Internet. Cette connexion sera ainsi plus rapide, plus fiable et avec une bande passante garantie. - -### Quels sont les produits compatibles avec OVHcloud Connect ? - -OVHcloud Connect est l'extension de votre réseau privé OVHcloud vRack donc tous les produits ayant la fonctionnalité vRack activée sont compatibles. - -### Comment choisir entre une interconnexion de niveau 2 ou de niveau 3 du modèle OSI ? - -Les caractéristiques associées aux réseaux de niveau 2 et 3 doivent être prises en compte lors de la phase de construction afin de répondre au mieux à vos besoins d'hybridation. - -#### Niveau 2 OSI - -Le produit OVHcloud Connect dédié de niveau 2 signifie que la connexion est transparente au protocole Ethernet. - -L'intérêt d'une interconnexion de niveau 2 est de pouvoir connecter le réseau campus de votre datacenter avec votre réseau privé OVHcloud vRack de manière simplifiée. - -La connaissance réseau nécéssaire est la maîtrise basique des réseaux de type LAN. - -La redondance peut-être locale au sein du même point de présense (PoP) en utilisant le protocole LACP 802.3ad. - -Les réseaux locaux virtuels (VLAN) sont les mêmes dans votre datacenter et au sein des datacenters OVHcloud. - -#### Niveau 3 OSI - -Le produit OVHcloud Connect dédié de niveau 3 est une connexion gérée par des routeurs. - -L'intérêt d'une interconnexion de niveau 3 est de pouvoir connecter le réseau WAN de votre entreprise avec votre réseau privé OVHcloud vRack afin qu'il soit vu comme un ou des sites du réseau WAN. - -Les connaissances réseau nécéssaires sont la maîtrise avancée des réseaux de type MAN et WAN ainsi que la gestion de routage entre réseaux. - -Les réseaux de niveau 3 nécessitent l'établissement d'une ou des sessions BGP externes privées entre l'entreprise et OVHcloud. - -La redondance peut-être locale au sein du même point de présense (PoP) et aussi géographique entre deux points de présence (PoP) en utilisant les mécanismes de redondance de BGP. - -Les réseaux locaux virtuels (VLAN) ne sont pas les mêmes dans vos datacenters et au sein des datacenters OVHcloud. - -### Est-ce que OVHcloud peut héberger mes routeurs ? - -OVHcloud n'héberge pas de matériel réseau pour les clients dans ses datacenters et points de présence (PoP). Le client doit faire héberger ses équipements par son opérateur ou par un tiers puis demander une connexion avec les équipements OVHcloud dans la MeetMeRoom (MMR) des points de présence grâce aux informations fournies dans la Letter of Authorization (LOA). - -### Quelles connectiques sont supportées par OVHcloud Connect ? - -Nous supportons la fibre optique mono-mode pour modules SFP/SFP+ compatible soit 1000LX/LH (1Gb/s) soit 10G-LR (10Gb/s). - -### Quand mon offre OVHcloud Connect sera-t-elle livrée et disponible pour la configuration ? - -Une offre OVHcloud Connect doit d'abord être livrée avant de pouvoir être configurée. - -Une solution OVHcloud Connect Provider sera livrée dès que la *clé de service* (Service Key) sera envoyée au client par e-mail. Cet e-mail sera envoyé quelques minutes après la finalisation de la commande du service correspondant. - -Une solution OVHcloud Connect Direct est considérée comme livrée dans les cas suivants : - -- La lumière indiquant la connexion à l'équipement du client est visible du côté de OVHcloud. -- 60 jours se sont écoulés depuis la commande. -- Le client a explicitement demandé une livraison manuelle auprès des services OVHcloud. - -Une fois la commande finalisée, OVHcloud fournira au client une Lettre d'autorisation (LOA) pour lui permettre d'effectuer l'interconnexion avec l'infrastructure OVHcloud. - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.fr-fr.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.fr-fr.md deleted file mode 100644 index a75d5808906..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.fr-fr.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## FAQ Ovhcloud Connect - -### À quoi sert la solution OVHcloud Connect ? - -OVHcloud Connect permet d'étendre votre réseau d'entreprise avec votre réseau privé OVHcloud vRack sans passer par l'établissement d'un tunnel VPN à travers Internet. Cette connexion sera ainsi plus rapide, plus fiable et avec une bande passante garantie. - -### Quels sont les produits compatibles avec OVHcloud Connect ? - -OVHcloud Connect est l'extension de votre réseau privé OVHcloud vRack donc tous les produits ayant la fonctionnalité vRack activée sont compatibles. - -### Comment choisir entre une interconnexion de niveau 2 ou de niveau 3 du modèle OSI ? - -Les caractéristiques associées aux réseaux de niveau 2 et 3 doivent être prises en compte lors de la phase de construction afin de répondre au mieux à vos besoins d'hybridation. - -#### Niveau 2 OSI - -Le produit OVHcloud Connect dédié de niveau 2 signifie que la connexion est transparente au protocole Ethernet. - -L'intérêt d'une interconnexion de niveau 2 est de pouvoir connecter le réseau campus de votre datacenter avec votre réseau privé OVHcloud vRack de manière simplifiée. - -La connaissance réseau nécéssaire est la maîtrise basique des réseaux de type LAN. - -La redondance peut-être locale au sein du même point de présense (PoP) en utilisant le protocole LACP 802.3ad. - -Les réseaux locaux virtuels (VLAN) sont les mêmes dans votre datacenter et au sein des datacenters OVHcloud. - -#### Niveau 3 OSI - -Le produit OVHcloud Connect dédié de niveau 3 est une connexion gérée par des routeurs. - -L'intérêt d'une interconnexion de niveau 3 est de pouvoir connecter le réseau WAN de votre entreprise avec votre réseau privé OVHcloud vRack afin qu'il soit vu comme un ou des sites du réseau WAN. - -Les connaissances réseau nécéssaires sont la maîtrise avancée des réseaux de type MAN et WAN ainsi que la gestion de routage entre réseaux. - -Les réseaux de niveau 3 nécessitent l'établissement d'une ou des sessions BGP externes privées entre l'entreprise et OVHcloud. - -La redondance peut-être locale au sein du même point de présense (PoP) et aussi géographique entre deux points de présence (PoP) en utilisant les mécanismes de redondance de BGP. - -Les réseaux locaux virtuels (VLAN) ne sont pas les mêmes dans vos datacenters et au sein des datacenters OVHcloud. - -### Est-ce que OVHcloud peut héberger mes routeurs ? - -OVHcloud n'héberge pas de matériel réseau pour les clients dans ses datacenters et points de présence (PoP). Le client doit faire héberger ses équipements par son opérateur ou par un tiers puis demander une connexion avec les équipements OVHcloud dans la MeetMeRoom (MMR) des points de présence grâce aux informations fournies dans la Letter of Authorization (LOA). - -### Quelles connectiques sont supportées par OVHcloud Connect ? - -Nous supportons la fibre optique mono-mode pour modules SFP/SFP+ compatible soit 1000LX/LH (1Gb/s) soit 10G-LR (10Gb/s). - -### Quand mon offre OVHcloud Connect sera-t-elle livrée et disponible pour la configuration ? - -Une offre OVHcloud Connect doit d'abord être livrée avant de pouvoir être configurée. - -Une solution OVHcloud Connect Provider sera livrée dès que la *clé de service* (Service Key) sera envoyée au client par e-mail. Cet e-mail sera envoyé quelques minutes après la finalisation de la commande du service correspondant. - -Une solution OVHcloud Connect Direct est considérée comme livrée dans les cas suivants : - -- La lumière indiquant la connexion à l'équipement du client est visible du côté de OVHcloud. -- 60 jours se sont écoulés depuis la commande. -- Le client a explicitement demandé une livraison manuelle auprès des services OVHcloud. - -Une fois la commande finalisée, OVHcloud fournira au client une Lettre d'autorisation (LOA) pour lui permettre d'effectuer l'interconnexion avec l'infrastructure OVHcloud. - -## Aller plus loin - -Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services. - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.it-it.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.it-it.md deleted file mode 100644 index 50fbb184e40..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.it-it.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## OVHcloud Connect FAQ - -### What is the OVHcloud Connect solution designed for? - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -### Which products are compatible with OVHcloud Connect? - -OVHcloud Connect is an extension of your OVHcloud vRack private network, so all products with the vRack feature enabled will be compatible. - -### How do I choose between a Layer 2 or Layer 3 cross-connection for the OSI model? - -You will need to keep in mind the features associated with Layer 2 and Layer 3 networks as you build your infrastructure, in order to select the best cross-connection for your hybrid cloud requirements. - -#### Layer 2 OSI - -The OVHcloud Connect solution dedicated to Layer 2 means that the connection is transparent to the Ethernet protocol. - -The advantage of a Layer 2 connection is that it simplifies the way you connect your data centre’s campus network to your OVHcloud vRack private network. - -You will need basic knowledge of how to use LAN networks. - -Redundancy can be local within the same point of presence (PoP), using LACP 802.3ad protocol. - -The virtual local area networks (VLANs) are the same in your data centre and within OVHcloud data centres. - -#### Layer 3 OSI - -The OVHcloud Connect solution dedicated to Layer 3 is a connection managed by routers. - -The advantage of a Layer 3 cross-connection is that you can connect your company’s WAN network to your OVHcloud vRack private network, so that it is considered as a site within your WAN network. - -You will need an advanced understanding of MAN and WAN networks, as well as knowledge of how to manage inter-network routing. - -Layer 3 networks require one or more private external BGP sessions to be established between the company and OVHcloud. - -Redundancy can be local within the same PoP, and geographical between two PoPs using BGP redundancy mechanisms. - -The VLANs are **not** the same in your data centre and within OVHcloud data centres. - -### Can OVHcloud host my routers? - -OVHcloud does not host network hardware for customers in data centres and PoPs. Customers need to have their hardware hosted by an operator or by a third party, then request a connection to OVHcloud hardware in the MMR (meet-me room) of the PoP. Instructions on how to do this are provided in the Letter of Authorisation (LOA). - -### What connections are supported for OVHcloud Connect? - -We support single-mode fibre optic. Your SFP/SFP+ must support either 1000LX/LH or 10G-LR. - -### When will my OVHcloud Connect service be delivered and available for configuration? - -An OVHcloud Connect service has to be delivered first before it can be configured. - -OVHcloud Connect Provider solutions will be delivered as soon as the *service key* is sent to the customer by email. This happens a few minutes after subscribing to the corresponding service. - -OVHcloud Connect Direct solutions are considered delivered in the following cases: - -- The light indicating the connection to the customer's equipment is visible on OVHcloud's side. -- 60 days have passed since the subscription. -- The customer has explicitly arranged a manual delivery with their OVHcloud agent. - -After having subscribed, the customer will receive a Letter of Authorization (LOA) from OVHcloud to allow the customer to perform the cross-connection with OVHcloud's infrastructure. This cross-connection will then trigger the delivery based on the above mentioned cases. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.pl-pl.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.pl-pl.md deleted file mode 100644 index 50fbb184e40..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.pl-pl.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## OVHcloud Connect FAQ - -### What is the OVHcloud Connect solution designed for? - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -### Which products are compatible with OVHcloud Connect? - -OVHcloud Connect is an extension of your OVHcloud vRack private network, so all products with the vRack feature enabled will be compatible. - -### How do I choose between a Layer 2 or Layer 3 cross-connection for the OSI model? - -You will need to keep in mind the features associated with Layer 2 and Layer 3 networks as you build your infrastructure, in order to select the best cross-connection for your hybrid cloud requirements. - -#### Layer 2 OSI - -The OVHcloud Connect solution dedicated to Layer 2 means that the connection is transparent to the Ethernet protocol. - -The advantage of a Layer 2 connection is that it simplifies the way you connect your data centre’s campus network to your OVHcloud vRack private network. - -You will need basic knowledge of how to use LAN networks. - -Redundancy can be local within the same point of presence (PoP), using LACP 802.3ad protocol. - -The virtual local area networks (VLANs) are the same in your data centre and within OVHcloud data centres. - -#### Layer 3 OSI - -The OVHcloud Connect solution dedicated to Layer 3 is a connection managed by routers. - -The advantage of a Layer 3 cross-connection is that you can connect your company’s WAN network to your OVHcloud vRack private network, so that it is considered as a site within your WAN network. - -You will need an advanced understanding of MAN and WAN networks, as well as knowledge of how to manage inter-network routing. - -Layer 3 networks require one or more private external BGP sessions to be established between the company and OVHcloud. - -Redundancy can be local within the same PoP, and geographical between two PoPs using BGP redundancy mechanisms. - -The VLANs are **not** the same in your data centre and within OVHcloud data centres. - -### Can OVHcloud host my routers? - -OVHcloud does not host network hardware for customers in data centres and PoPs. Customers need to have their hardware hosted by an operator or by a third party, then request a connection to OVHcloud hardware in the MMR (meet-me room) of the PoP. Instructions on how to do this are provided in the Letter of Authorisation (LOA). - -### What connections are supported for OVHcloud Connect? - -We support single-mode fibre optic. Your SFP/SFP+ must support either 1000LX/LH or 10G-LR. - -### When will my OVHcloud Connect service be delivered and available for configuration? - -An OVHcloud Connect service has to be delivered first before it can be configured. - -OVHcloud Connect Provider solutions will be delivered as soon as the *service key* is sent to the customer by email. This happens a few minutes after subscribing to the corresponding service. - -OVHcloud Connect Direct solutions are considered delivered in the following cases: - -- The light indicating the connection to the customer's equipment is visible on OVHcloud's side. -- 60 days have passed since the subscription. -- The customer has explicitly arranged a manual delivery with their OVHcloud agent. - -After having subscribed, the customer will receive a Letter of Authorization (LOA) from OVHcloud to allow the customer to perform the cross-connection with OVHcloud's infrastructure. This cross-connection will then trigger the delivery based on the above mentioned cases. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on . diff --git a/pages/network/ovhcloud_connect/occdedicated-faq/guide.pt-pt.md b/pages/network/ovhcloud_connect/occdedicated-faq/guide.pt-pt.md deleted file mode 100644 index 50fbb184e40..00000000000 --- a/pages/network/ovhcloud_connect/occdedicated-faq/guide.pt-pt.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: FAQ OVHcloud Connect -updated: 2020-09-14 ---- - -## OVHcloud Connect FAQ - -### What is the OVHcloud Connect solution designed for? - -With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. - -### Which products are compatible with OVHcloud Connect? - -OVHcloud Connect is an extension of your OVHcloud vRack private network, so all products with the vRack feature enabled will be compatible. - -### How do I choose between a Layer 2 or Layer 3 cross-connection for the OSI model? - -You will need to keep in mind the features associated with Layer 2 and Layer 3 networks as you build your infrastructure, in order to select the best cross-connection for your hybrid cloud requirements. - -#### Layer 2 OSI - -The OVHcloud Connect solution dedicated to Layer 2 means that the connection is transparent to the Ethernet protocol. - -The advantage of a Layer 2 connection is that it simplifies the way you connect your data centre’s campus network to your OVHcloud vRack private network. - -You will need basic knowledge of how to use LAN networks. - -Redundancy can be local within the same point of presence (PoP), using LACP 802.3ad protocol. - -The virtual local area networks (VLANs) are the same in your data centre and within OVHcloud data centres. - -#### Layer 3 OSI - -The OVHcloud Connect solution dedicated to Layer 3 is a connection managed by routers. - -The advantage of a Layer 3 cross-connection is that you can connect your company’s WAN network to your OVHcloud vRack private network, so that it is considered as a site within your WAN network. - -You will need an advanced understanding of MAN and WAN networks, as well as knowledge of how to manage inter-network routing. - -Layer 3 networks require one or more private external BGP sessions to be established between the company and OVHcloud. - -Redundancy can be local within the same PoP, and geographical between two PoPs using BGP redundancy mechanisms. - -The VLANs are **not** the same in your data centre and within OVHcloud data centres. - -### Can OVHcloud host my routers? - -OVHcloud does not host network hardware for customers in data centres and PoPs. Customers need to have their hardware hosted by an operator or by a third party, then request a connection to OVHcloud hardware in the MMR (meet-me room) of the PoP. Instructions on how to do this are provided in the Letter of Authorisation (LOA). - -### What connections are supported for OVHcloud Connect? - -We support single-mode fibre optic. Your SFP/SFP+ must support either 1000LX/LH or 10G-LR. - -### When will my OVHcloud Connect service be delivered and available for configuration? - -An OVHcloud Connect service has to be delivered first before it can be configured. - -OVHcloud Connect Provider solutions will be delivered as soon as the *service key* is sent to the customer by email. This happens a few minutes after subscribing to the corresponding service. - -OVHcloud Connect Direct solutions are considered delivered in the following cases: - -- The light indicating the connection to the customer's equipment is visible on OVHcloud's side. -- 60 days have passed since the subscription. -- The customer has explicitly arranged a manual delivery with their OVHcloud agent. - -After having subscribed, the customer will receive a Letter of Authorization (LOA) from OVHcloud to allow the customer to perform the cross-connection with OVHcloud's infrastructure. This cross-connection will then trigger the delivery based on the above mentioned cases. - -## Go further - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. - -Join our community of users on .