---
title: "'Quick Start: OVHcloud Connect Direct'"
description: "'Walk through the essential steps to establish a direct, private connection to OVHcloud'"
url: https://docs.ovhcloud.com/pl/guides/network/ovhcloud-connect/occ-direct-control-panel-setup
lang: pl
lastUpdated: 2026-06-16
---
# Quick Start: OVHcloud Connect Direct

## 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](/pl/guides/network/ovhcloud-connect/pop-locations-regions.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)

Log in to your OVHcloud Control Panel
 and go to `Network
` > `OVHcloud Connect
`.
## Steps overview

![Overview of the steps to set up OVHcloud Connect Direct from the Control Panel](/images/network/ovhcloud-connect/occ-direct-control-panel-setup/fig-1.svg)
### Step 1 — Order OVHcloud Connect Direct

1. Select <code className="action">OVHcloud Connect Direct</code>.
2. Choose your **PoP location** and **bandwidth** (e.g. 1, 10 or 100 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](/pl/guides/network/ovhcloud-connect/order-direct.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](/pl/guides/network/ovhcloud-connect/associate-vrack.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](/pl/guides/network/ovhcloud-connect/l3-bgp.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](/pl/guides/network/ovhcloud-connect/incident-followup.md) with your BGP output, interface status, and traceroute results.

## What's next?

- For a managed connection, see [Quick Start: Provider Connection](/pl/guides/network/ovhcloud-connect/occ-provider-control-panel-setup.md)
- For resilient setups, see [Resilient On-Prem tutorial](/pl/guides/network/ovhcloud-connect/resilient-architecture.md)
- Set up [monitoring](/pl/guides/network/ovhcloud-connect/monitor.md) for your connection

## Go further

For training or technical assistance implementing our solutions, contact your sales representative or visit our [Professional Services](https://www.ovhcloud.com/pl/professional-services/) page to request a quote and have your project analyzed by our experts.

Join our [community of users](https://community.ovhcloud.com/).