Set up the vRack network for OVHcloud Connect

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)

Requirements

You need to have cleared steps 1 through 3 of one of the following guides:

• Quick Start: Direct Connection to OVHcloud
• Quick Start: Connection to OVHcloud with a Provider

Log in to your OVHcloud Control Panel and go to Network > OVHcloud Connect.

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:

Subnet planning guidelines:

VRRP — Gateway redundancy

The OVHcloud AZ routing instance uses VRRP (Virtual Router Redundancy Protocol) to provide gateway redundancy between devices A and B.

vRack router limitations

Step 1 — Identify available AZs

Before creating an AZ configuration, check which AZs are available for your OVHcloud Connect service.

Example response:

{
  "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:

Create the AZ configuration:

Request parameters:

Example response:

{
  "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:

Example response:

{
  "id": 3456,
  "datacenterId": 1234,
  "subnet": "172.16.1.0/28",
  "ovhBgpArea": 65501,
  "status": "active"
}

Monitor task progress with:

Step 4 — Repeat for additional AZs (optional)

For a multi-AZ resilient setup, create an AZ configuration for each AZ:

# 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"
)

For more information, refer to our guide on Multi-AZ.

Delete an AZ configuration

Go further

Now that your AZ configuration is ready, configure the OVHcloud Connect L3 routing:

• Configure OVHcloud Connect L3 with BGP
• Configure OVHcloud Connect L3 with static routing
• Monitor your connection

For training or technical assistance implementing our solutions, contact your sales representative or visit our Professional Services page to request a quote and have your project analyzed by our experts.

Join our community of users.