Configure OVHcloud Connect L3 with static routes

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.

When to use static routing vs BGP

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
• An AZ configuration created — see Set up vRack networking
• 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 guide.

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

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

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.

Request parameters:

Example request:

{
  "interfaceId": 101,
  "type": "l3",
  "customerBgpArea": 65001,
  "subnet": "192.0.2.0/30"
}

Step 3 — Verify the PoP configuration

Example response:

{
  "id": 5678,
  "interfaceId": 101,
  "type": "l3",
  "customerBgpArea": 65001,
  "ovhBgpArea": 35540,
  "subnet": "192.0.2.0/30",
  "status": "active"
}

From this response:

Step 4 — Create AZ extra configuration (static)

After the PoP configuration and a AZ configuration, create a network extra configuration to define static routes within the AZ.

Request parameters:

Example request — route your on-premises subnet through the OVHcloud Connect link:

{
  "type": "network",
  "nextHop": "172.16.1.1",
  "subnet": "10.0.0.0/16"
}

Add multiple static routes

Create one extra configuration per destination subnet. Repeat the POST .../extra call with a different subnet each time:

{
  "type": "network",
  "nextHop": "172.16.1.1",
  "subnet": "10.1.0.0/16"
}

Verify the extra configuration

Example response:

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

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:

From the OVHcloud API

Check interface status:

Check PoP configuration status:

Run a diagnostic

Available diagnostic names: diagPeering, diagPeeringExtra, diagRoutes, diagMacs.

Limitations of static routing

Delete configurations

Delete in reverse order:

Go further

• Set up vRack networking — If you have not configured AZ subnets yet
• Associate OVHcloud Connect with your vRack
• 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.