Installation of OVHcloud Connect Provider from the OVHcloud Control Panel

Find out how to set up your OVHcloud Connect Provider solution via the OVHcloud Control Panel

Last updated 28th September 2020

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

To ensure correct operation of this service, you must be aware of the technical capabilities and limitations of the OVHcloud Connect solution and configure your network devices accordingly.

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. To do this, click Bare Metal Cloud in the top navigation bar, then select Network from the left-hand menu. Open OVHcloud Connect 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, click Bare Metal Cloud in the top navigation bar, then select Network from the left-hand menu. Open OVHcloud Connect and click on your solution.

ovhcloud connect selection

You will need to link a vRack to your solution first. Click the Attach a vRack button and select an existing vRack from the drop-down menu.

vRack association

A message will confirm the vRack association.

vRack association

Step 3: Adding a PoP configuration

The OVHcloud Connect Provider solution requires an L3 level configuration.

Once you have connected your vRack, click Add a PoP configuration and select the L3 configuration from the drop-down menu.

PoP addition

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

The PoP configuration menu will then appear.

PoP addition

Step 4: Adding a data centre configuration

When your PoP configuration has been set, click Add a configuration under the DC configuration menu.

adding datacentre

Select a data centre 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 DC. 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 DC. This can be an IPv4 block of size /28 or higher

adding datacentre

You can add additional data centre configurations by clicking on the ... button, then Add a configuration.

adding datacentre

You must also add a routing configuration.

Adding a routing configuration

Click on the ... button on the desired data centre then on Add routing configuration configuration.

add datacentre

Then choose the routing type between Static and BGP.

add datacentre

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 DC
IP Neighbour IP address of the BGP neighbour of your router in the DC. This address must be part of the subnet specified in the DC Configuration menu

add datacentre

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 datacentre

You can add multiple routing configurations within the same data centre. The configuration type (BGP or Static) chosen for your first configuration will then apply to the next configuration in the same data centre.

add datacentre

Deletion of vCenter resources

Each resource (PoP or DC) can be deleted individually, but deleting a parent resource such as DC or POP will automatically delete all the subresources.

Recursive removal is slower than sequential removal of each resource.

If a DC configuration is shared between two or more OVHcloud Connect services, removing the PoP configuration from a single OVHcloud Connect service will not affect the DC resource.

Deleting a Routing Configuration

To delete a routing configuration, click the ... button on the routing configuration to delete, then click Delete.

deleting routing configuration

Deleting a DC configuration

To delete a DC configuration, click the ... button on the DC configuration to delete, then click Delete.

DC deletion

Deleting a DC configuration will delete the related routing configurations.

Enabling the configuration

To delete a PoP configuration, click the ... button on the PoP configuration, then click Delete configuration.

deleting PoP configuration

Deleting a PoP configuration will delete the DC and routing configurations.

Go further

Join our community of users on https://community.ovh.com/en/.


Did you find this guide useful?

Please feel free to give any suggestions in order to improve this documentation.

Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.

Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.

Thank you. Your feedback has been received.


These guides might also interest you...

OVHcloud Community

Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.

Discuss with the OVHcloud community