Introduction 

This is the main page of a three-part blog series in which I will present how to connect two Oracle Cloud Infrastructure (OCI) regions using Equinix Fabric. This solution can replace the OCI Remote Peering Connection (RPC) and has all the benefits of the Equinix SLAs.

For this connectivity model, we will use two FastConnects with Equinix as a Partner, one Equinix Network EDGE Virtual Device, two Equinix Connections, and the Equinix Fabric. I will not focus on redundancy options.

01 Equinix Main

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/

–        Equinix as a Partner – for more information, please access official documentation at https://docs.equinix.com/en-us/Content/Interconnection/Fabric/connections/Fabric-oracle-fast-connect.htm

–        Equinix Network EDGE Virtual Device – for more information, please access official documentation at https://docs.equinix.com/en-us/Content/Interconnection/NE/user-guide/NE-create-device.htm

 

Prerequisites 

This blog will cover how to provision OCI FastConnect and Equinix Fabric. To do this, we will need the following resources already provisioned and configured:

1.     VCNs—In our case, we will have a VCN in the Ashburn region with 10.10.0.0/16 CIDR and another VCN in the 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.     There are two 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.     In our case, there are two compute VMs: one in Ashburn with IP 10.10.10.193 and one in Phoenix with IP 10.20.10.165.

4.     Access to the Equinix portal to provision and Order required components.

5.     Prepare and have all the needed data handy 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

# Equinix BGP ASN = 65000

# Oracle BGP ASN = 31898

 

Solution Description  

1.     For OCI side configuration, please go here for complete details.

2.     For Equinix side configuration, please go here for complete details.

3.     For the Network EDGE virtual device configuration, please go here for complete details.

 

You can follow along on this video to see the step by step process in action.

I hope you enjoyed this blog. Thank you for reading!