MCR Connections to Oracle Cloud Infrastructure using FastConnect
To connect to FastConnect using MCR, you will need an Oracle Cloud ID (OCID) obtained via the Oracle Console.
Creating a VXC to Oracle OCI via FastConnect from an MCR is a straightforward process via the Portal. Follow the steps below to establish a private connection to your Oracle Virtual Cloud Network (VCN).
Before starting here are some key Oracle terms to understand:
Compartments help you organize resources to make it easier to control access to them. Your root compartment is created for you by Oracle when your tenancy is provisioned. An administrator can create more compartments in the root compartment and then add the access rules to control which users can take action in them. At the time you create a resource, such as a cloud network, you choose which compartment to create it in. Once you create a resource, you cannot move it to another compartment.
Virtual Cloud Network (VCN)
A Virtual Cloud Network (VCN) is a customizable and private network in Oracle Cloud Infrastructure. Just like a traditional data center network, the VCN provides you with complete control over your network environment. This includes assigning your own private IP address space, creating subnets, route tables and configuring stateful firewalls. A single tenant can have multiple VCNs, thereby providing grouping and isolation of related resources.
Dynamic Routing Gateway (DRG)
A Dynamic Routing Gateway is a virtual edge router attached to your VCN that is necessary for private peering. The DRG is a single point of entry for private traffic coming in to your VCN. After creating the DRG, you must attach it to your VCN and add a route for the DRG in the VCN’s route table to enable traffic flow.
An isolated network path that runs over one or more physical network connections to provide a single, logical connection between the edge of your existing network and Oracle Cloud Infrastructure.
Virtual Circuit Types
- Private Virtual Circuit
Private IPV4 addresses are advertised (typically RFC 1918). The connection is via a DRG you attach to your VCN
- Private Virtual Circuit
- Public Virtual Circuit
Regional Oracle Cloud Infrastructure public IPv4 addresses are advertised (for example, for object storage). You also provide public IP prefixes that you want to advertise.
Oracle Cloud Identifier (OCID)
An Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID). This ID is included as part of the resource’s information in both the Console and API.
When provisioning a FastConnect it’s important to remember that a Dynamic Routing Gateway (DRG) is a standalone object. To use it, you must attach it to a Virtual Cloud Network (VCN). A VCN can be attached to only one DRG at a time, and vice versa.
Oracle offers an SLA on its FastConnect connectivity, but in order to comply with this you must ensure to deploy two FastConnect virtual cross connects (VXCs) for redundancy.
A common FastConnect deployment using a Megaport Cloud Router (MCR) might look like this:
Pre-requisites for Private VCN connection
In order to connect from an existing MCR to a VCN in Oracle you’ll need to gather the following information:
- The Oracle OCID number.
- Oracle ASN #
- If you don’t currently have an existing MCR, you may refer to our main Megaport Cloud Router (MCR) article to create one.
Creating/confirming your Private ASN for FastConnect
In order to connect MCR to your target Oracle VCN, login to the Oracle Console and complete the following:
- Create a new FastConnect
- Copy the OCID number
- Confirm the AS number. The AS# can be confirmed in the Oracle console by viewing the connection details of the new FastConnect.
Completing an Oracle FastConnect request from MCR
From the steps completed above, you now have enough information to create the VXC request in the Megaport portal to Oracle from the selected MCR.
From the MCR choose ‘+Connection’
and select the Cloud tile:
Select Oracle and enter your FastConnect OCID.
After entering the OCID the destination ports will appear. Select the appropriate destination port and select ‘Next’
In the next screen, Connection Details you will be asked the name of the connection (for display in the Megaport dashboard) and the rate limit. Note that the rate limit for the VXC will be capped at the maximum allowable as per that queried from the OCID. After entering the information select ‘Next’.
The next screen, Connection Detail for MCR A End, allows you to enter details that will be used to set up the peering session between the selected MCR and the Oracle edge device.
On this first screen enter the IP Address and mask for the MCR interface facing Oracle. This will be the same address you entered on the Oracle Console to create the FastConnect. Then Select +ADD and Next
On the next screen select Add BGP Connection and enter the remainder of the BGP information to set up peering with Oracle. The Peer ASN is always 31898 for Oracle. Select Next
- Local ASN: ASN in this example – 65500 – however you may use another valid private (or public) value as required.
- Peer ASN: For Oracle via FastConnect this will be 31898. Ensure this value is correct.
- Local IP: Selected via a drop-down item, this will be populated from the IP addresses list entered above.
- Peer IP: This is a manually entered value and should be the CIDR notation of the IP address incremented +1 from that used above.
- BGP Authorization: This is not a mandatory field for Oracle connections as they traverse a private (non-Internet) path.
After these values have been entered (and checked) you may select Next, Add VXC and then Order.
Once the VXC connection is deployed successfully you will see it attached to the MCR on the Portal dashboard:
Clicking on the VXC name (Oracle FastConnect from Megaport MCR) will give visibility into the details of the connection.
Note under the Details tab that both the service status (Layer 2) and BGP (Layer 3) are UP.
If you go back to the Oracle Console the established FastConnect will look like this:
You must set up both BGP sessions as separate VXCs for the Oracle FastConnect availability SLA to be valid. This may be configured on a single MCR or across two MCR instances depending on your HA requirements.
To establish a separate BGP session create a new FastConnect on the Oracle Console and repeat the steps in the Megaport portal.