Installation of OVHcloud Connect Direct from the OVHcloud Control Panel
Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel
Find out how to set up your OVHcloud Connect Direct solution via the OVHcloud Control Panel
Last updated 28th September 2020
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 Direct solution via the OVHcloud Control Panel.
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.
Log in to the OVHcloud Control Panel, go to the Bare Metal Cloud
section and click on Network
. Next, open OVHcloud Connect
and click on your solution.
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.
A message will confirm the vRack association.
Changing the PoP configuration from L2 to L3, or vice versa, would require deleting the entire configuration. We advise you to think carefully about your configuration choice before going any further.
For more details on the differences between levels L2 and L3, see our FAQ.
Once you have linked your vRack, two PoP configuration
menus will appear. Click the Add a PoP configuration
button in the first menu, select L2 from the drop-down menu, then confirm.
The L2 configuration will then be enabled in the two PoP configuration
menus.
Once you have connected your vRack, click Add a PoP configuration
and select the L3 configuration from the drop-down menu.
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 |
The PoP configuration
menu will then appear.
You can also add a second PoP L3 configuration via the second PoP configuration
menu.
When your PoP configuration is active, click Add a configuration
under the DC configuration
menu. Select a data centre from the drop-down menu and confirm.
The DC configuration will then begin.
When your PoP configuration has been set, click Add a configuration
under the DC configuration
menu.
Select a data centre from the drop-down 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 |
You can add additional data centre configurations by clicking on the ...
button, then Add a configuration
.
You must also add a routing configuration.
Click on the (...)
button on the desired data centre then on Add routing configuration
.
Then choose the routing type between Static and BGP.
If you choose the type BGP, 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 subnetwork specified in the DC Configuration section |
If you choose the Static type, enter the required information:
Information | Description |
---|---|
Network Focus | A prefix using CIDR notation |
Next hop | An IP address acting as gateway in the subnetwork range |
You can add multiple routing configurations within the same data centre. The configuration type (BGP or Static) chosen for your first routing configuration will then apply to the next configuration on the same data centre.
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.
To delete a routing configuration, click the ...
button on the routing configuration to delete, then click Delete
.
To delete a DC configuration, click the ...
button on the DC configuration to delete, then click Delete
.
Deleting a DC configuration will delete the related routing configurations.
To delete a PoP configuration, click the ...
button on the PoP configuration to delete, then click Delete configuration
.
Deleting a PoP configuration will delete the related DC and routing configurations.
Join our community of users on https://community.ovh.com/en/.
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.
Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.
Discuss with the OVHcloud community