Introduction
This is the main page of a two-part blog series, in which I will present how to connect two Oracle Cloud Infrastructure (OCI) regions using Megaport Infrastructure. This solution can be used as a replacement for the OCI Remote Peering Connection (RPC) and has all the benefits of the Megaport SLAs.
For this connectivity model, we will use 2 FastConnects using Megaport as a Partner, 2 Megaport MCRs, and the Megaport Infrastructure, and will not focus on redundancy options.
In this scenario, we will use the following technologies:
– Virtual Cloud Network (VCN) – for more information, please access official documentation at https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/managingVCNs.htm
– Dynamic Routing Gateway v2 (DRGv2) – for more information, please access official documentation at https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/managingDRGs.htm
– OCI Compute – for more information, please access official documentation at https://www.oracle.com/cloud/compute/
– OCI FastConnect Partner Connectivity Model – for more information, please access official documentation at https://www.oracle.com/cloud/networking/fastconnect/connectivity-models/
– Megaport as a Partner – for more information, please access official documentation at https://www.megaport.com/services/oracle-cloud-fastconnect/
– Megaport Cloud Router (MCR) Partner – for more information, please access official documentation at https://www.megaport.com/services/megaport-cloud-router/
Prerequisites
This blog will cover how to provision OCI FastConnect and Megaport Infrastructure. To do this, we will need the following resources already provisioned and configured:
1. VCNs – in our case, we will have a VCN in Ashburn region with 10.10.0.0/16 CIDR and another VCN in Phoenix region with 10.20.0.0/16 CIDR with all routing and Security List / Network Security Groups to allow connectivity between Ashburn and Phoenix CIDR Blocks.
2. 2 DRGs – in our case, one DRG in Ashburn and one DRG in Phoenix with VCN attachments and routing in place to allow traffic between Ashburn VCN and Phoenix VCN.
3. 2 Compute VMs – in our case, one compute VM in Ashburn with IP 10.10.10.193 and one in Phoenix with IP 10.20.10.165.
4. Access to the Megaport portal with the possibility to provision and Order required components.
5. Prepare and have in handy all the needed data to configure this solution. In our case, what I have prepared is:
# Ashburn VCN CIDR = 10.10.0.0/16
# Ashburn subnet = 10.10.10.0/24
# Ashburn Compute instance IP = 10.10.10.193
# Ashburn FastConnect BGP subnet = 172.16.0.0/30
# Phoenix VCN CIDR = 10.20.0.0/16
# Phoenix subnet = 10.20.10.0/24
# Phoenix Compute instance IP = 10.20.10.165
# Phoenix FastConnect BGP subnet = 172.16.0.4/30
# Megaport MCR’s Link subnet = 192.168.0.0/30
# Megaport BGP ASN = 133937
# Oracle BGP ASN = 31898
Solution Description
1. For OCI side configuration, please go here for complete details.
2. For Megaport side configuration, please go here for complete details.
You can follow along on this video to see the step by step process in action.