Creating MCR Connections to OVHcloud Connect
Megaport makes it easy to provision fast, secure, and private connections to OVHcloud Connect through our global Software Defined Network (SDN). Megaport is an OVHcloud partner providing direct private access to the OVHcloud infrastructure. You can quickly provision connectivity from hundreds of Megaport-enabled locations to OVHcloud regions and OVHcloud Connect Points-of-Presence (PoPs) across North America, Europe, and Asia Pacific.
You can create a Virtual Cross Connect (VXC) from an MCR to OVHcloud Connect from the Megaport Portal. You can also create additional VXCs to other Cloud Service Providers (CSPs) for multicloud access from the MCR. Click the appropriate CSP link in the MCR Cloud Connectivity Overview navigation.
The benefits of direct connectivity to OVHcloud Connect through Megaport include:
- Secure, private connectivity throughout Megaport’s redundant network infrastructure. Your traffic will not transit the public internet.
- High performance and predictability of your network.
- Improved data and operational security.
- Flexible and scalable cloud networking options.
- Consistent connectivity while scaling bandwidth to OVHcloud Connect. This means no downtime when you need to change your VXC speed.
- Connect to multiple regions from a single interconnection point, which leverages multi-region redundancy at a fraction of the cost.
How it works
OVHcloud Connect consists of a physical network connection at a number of OVHcloud locations around the world. OVHcloud locations reside within facilities operated by co-located data centers where Megaport is enabled.
Physical fiber connections (NNIs) at each location between Megaport and OVHcloud are established to OVHcloud routers. These physical connections are maintained between OVHcloud and Megaport.
Connecting to OVHcloud follows these general steps through the Megaport Portal:
- Order Megaport Cloud Routers (MCRs) in Megaport locations of your choice. Two MCRs are required for redundancy.
- Order VXCs to OVHcloud in fixed increments of 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, or 5 Gbps.
VXCs to OVHcloud are established as a Layer 3 service between OVHcloud and the MCR. One VXC from each MCR is required for redundancy.
OVHcloud is available in these locations:
You can connect to multiple regions from a single interconnection point (which lets you leverage multi-region redundancy at a fraction of the cost).
For more details, see OVHcloud Connect.
Before you begin, notify OVHcloud. If you are an existing OVHcloud customer, contact your OVHcloud Account Manager and establish an agreement for OVHcloud services. If you are a new customer, you can order from the OVHcloud Connect website.
OVHcloud will provide you with a service key that is unique for each cloud peering location interface: one for the primary and one for the secondary cloud peering location interface.
The key includes the provider (Megaport), VLAN ID, speed, and OVHcloud port location.
To use your OVHcloud service key, you will need to create an MCR or connect your service key to an existing MCR from your Megaport Portal account. An MCR enables data transfer between multi-cloud and hybrid cloud environments, network service providers, and cloud service providers. For details, see Creating an MCR.
Setting up OVHcloud Connect
The easiest way to create a connection between Megaport and OVHcloud is with a service key. A service key includes the essential configuration details for your business and automates much of the configuration process. Once you receive your service key from OVH, you specify your Layer 3 connectivity information in the OVHcloud portal. You then create a VXC in the Megaport Portal to connect MCR to OVHcloud.
To configure your Point of Presence in OVHcloud
- Log in to the OVHcloud website.
If this is your first time, you will need to register for an account.
- Order an OVHcloud Connect with Megaport as the partner.
- Click Order Product.
- Select Megaport as the partner.
- Select the speed for the connection.
Select the OVHcloud Connect location.
Within minutes of placing the order, you will receive an email notification that includes your Service Key identifier.
When you use the service key created by OVHcloud, you are responsible for any VXC charges.
Select My Orders from the Dashboard navigation pane to verify if your order is complete and ready for service.
Once the Service Key is active in your OVHcloud portal account, you will attach a vRack.
- In the Dashboard view, select OVHcloud Connect.
- Choose Network > OVHcloud Connect, and select the Service Description that you created when ordering the OVHcloud Connect service key.
- Click Attach a vRack under vRack.
- Select the vRack to attach from the drop-down list and click Attach.
If required, you can click the link to order a new vRack.
Once the vRack is attached, you will provide the Layer 3 connection details.
- Specify the following details in the Add a PoP Configuration dialog box:
- Type – L3
- Customer ASN – Megaport ASN 133937
- OVHcloud ASN – Your customer desired ASN
- Subnetwork in /30 – The IP address subnet range to peer with MCR. For example, 172.16.0.0 /30. OVHcloud will use the first IP address from the subnet mask.
These details apply the required IP address with a subnet mask and ASN to establish your peering connection between OVHcloud and Megaport.
- Click Create.
To deploy a VXC from MCR to OVHcloud Connect
- Log in to the Megaport Portal and go to the Services page. If you don’t have a Megaport account, see Setting Up a Megaport Account.
- Select the MCR for the connection and click +Connection.
- Click Enter Service Key and click Next.
- Enter the service key provided by OVHcloud in the Megaport Service Key Id field.
Megaport validates the key. Data including VLAN ID, speed, and OVHcloud location are included in the key and populate automatically. For details on using a service key, see Creating a VXC with a service key.
- Click Next.
- Specify these connection details:
- Name your connection – Enter the name of the VXC using the label provided by OVH.
- Invoice Reference – This is an optional field for tracking purposes. It can be any text, such as a PO number or billing reference number.
- Rate Limit – Specify a speed for your connection in Mbps. The rate limit for the VXC is capped at the maximum allowable based on the OVHcloud Connect service key speed.
- Preferred B-End VLAN – This populates automatically based on the value defined in the service key.
- Click Next.
The MCR Connection detail page appears, where you set up the peering session between the MCR and OVHcloud.
- Enter your private IP address to connect to OVHcloud.
You will apply this IP /30 subnet within your OVHcloud Manager Portal for the vRack environment.
- Click +Add to assign the IP address to the MCR connection.
- Click +Add BGP Connection and specify these values:
- Local IP – The IP address on this interface (the MCR) that communicates with the BGP peer (OVHcloud Connect). The menu is autopopulated based on the address you specified in the MCR Connection detail. Select the IP address assigned to the MCR from the drop-down list.
- Peer IP – Specify the IP address for the BGP peer (OVHcloud Connect).
- Peer ASN – Enter the private peer autonomous system number (ASN) that you specified in the OVHcloud Manager Portal to connect to the MCR. Private ASNs must be between 64512 and 65535.
- BGP Auth – Optional field to specify the BGP MD5 key. If you leave this blank, Megaport negotiates a key automatically for you with OVHcloud which will be displayed in the Megaport Portal. (The key is not displayed in the OVHcloud Control Panel.) The shared key length is from 1 to 32 characters.
- Description – Optional field to identify this connection. The minimum description length is from 1 to 100 characters.
- BGP State – This option should be set to Enabled.
- Click Add to view the configured BGP connections.
- Click Next.
- Click Add VXC to proceed through the ordering process.
Repeat these steps to provision your secondary OVHcloud interface on a second MCR.
The second MCR must be in a different location from the primary MCR.
Review the Order Services agreement and click Order Now.
Once the VXC connection is deployed to OVHcloud, a single VLAN is assigned from your Megaport Portal account, with Layer 3 networking routing established using BGP between your MCR and OVHcloud VM vRack environment. Connections are private peering types, and will use private IPv4 addresses.
To establish full redundancy between your data center and OVH, we recommend deploying redundant VXCs between two different OVHCloud regions (or availability zones within a region) with two corresponding MCRs at each Megaport-enabled data center.
Fully redundant solution
Updating the service bandwidth
You can scale the service speed up to the OVHcloud Connect speed rate at any time. If you require additional capacity, you must place an order for a new connection speed on the OVHcloud website.
To change the OVHcloud Connect speed, you must delete the Cloud Connect and VXC connections, and then recreate them.
OVHcloud Frequently Asked Questions (FAQs)
Are there any OVHcloud port fees?
OVHcloud doesn’t charge for data transfer. Customers pay a flat, auto-renewable monthly rate.
What services are available using OVHcloud?
OVHcloud offers Private Cloud based on VMware platform, Bare Metal servers, Public Cloud based on Openstack and PaaS services as Kubernetes Managed, and Databases as a Service.
What if I’m not located within an OVHcloud PoP?
You don’t have to be located within the same facility as OVHcloud; you can establish a VXC to the closest OVHcloud location of your choice. Each VXC is carried across Megaport’s redundant network to OVHcloud.
Does OVHCloud support public or private ASNs?
OVHcloud supports public and private ASNs. If you are using a public ASN, you must own it. Private ASNs must be between 64512 and 65535. AS_PATH prepending does not work if you are using a private ASN for your public VIF. Your preference is requested at the time of order. This is a private connection, but customers can peer with their private or public ASN and an OVHcloud private ASN that they can choose.