Set up a simple OVHcloud Connect architecture

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

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

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

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.
• Provider: If the connection is managed by a provider. See 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.

4. Associate with vRack and configure subnets

Link to your vRack and set up the required subnets. See Associate with vRack and Set up your vRack network.

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:

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.

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

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.

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

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.

6. Test connectivity

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.

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

When to use

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

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

7. Verify connectivity

BGP route flow

There are three BGP segments in this architecture:

Troubleshooting

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

When to use

GCP Interconnect types

GCP offers two main interconnect options:

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 <random>/<region>/<edge-availability-domain>

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.

Ensure the provider MCR:

• Advertises GCP VPC prefixes (10.3.0.0/16) toward OVHcloud (BGP AS 65501 for Europe, 65502 for Canada, 65519 for 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.

7. Verify connectivity

BGP route flow

Troubleshooting