Oracle FastConnect is a network connectivity alternative to using the public internet for connecting your network with Oracle Cloud Infrastructure and other Oracle Cloud services. FastConnect provides an easy, elastic, and economical way to create a dedicated and private connection with higher bandwidth options, and a more reliable and consistent networking experience when compared to internet-based connections. For more details on Oracle FastConnect see https://cloud.oracle.com/fastconnect.
Equinix supports all FastConnect connectivity models including dedicated and exchange for:
- Oracle Cloud Infrastructure
- Oracle Cloud Infrastructure Classic
- Oracle Government Cloud
For more detailed information from Oracle please review:
Private Peering Networking on ECXF
FastConnect Connection Workflow
- Log into OCI Console and selection desired region
- Create the Dynamic Routing Gateway (DRG)
- Attach DRG to a Virtual Cloud Network (VCN)
- Configure VCN subnet route table to send traffic to DRG
- Create Connection selecting Equinix CloudExchange as provider
- Copy the unique OCID and continue process in ECXF portal
- Log into the ECXF portal and Create Connection
- Select the desired Oracle Cloud Service Profile (eg OCI – FastConnect Layer 2)
- Select connection source and destination metro
- Complete connection request form and submit order
- Complete BGP setup in Oracle Cloud Console
Step 1: Log into OCI Console and select desired region
From the top menu select the region where you wish to provision FastConnect.
Step 2: Create the Dynamic Routing Gateway (DRG)
In the Networking menu select Dynamic Routing Gateway (DRG). Complete the form and submit. Please wait for the DRG to be provisioned.
Step 3: Attach DRG to a Virtual Cloud Network (VCN)
Select your previously created DRG and select “Attach to Virtual Cloud Network”. Make sure this is associated with your desired VCN Compartment and VCN.
Step 4: Configure VCN subnet route table to send traffic to DRG
Select Virtual Cloud Networks in the Networking menu and select your desired VCN in the Compartment.
Step 5: Create Connection selecting “Equinix CloudExchange” as provider
Select FastConnect from the Networking menu and Create Connection. Choose “Equinix CloudExchange” as the Provider from the menu and click continue.
Complete the Connection Connection form and click Continue.
Step 6: Copy the unique OCID and continue process in ECXF portal
Copy to OCID in the Connection Created confirmation. The Virtual Circuit is now in Pending Provider state.
Step 7: Log into the ECXF portal (https://ecxfabric.equinix.com/) and Create Connection
Step 8: Select the desired Oracle Cloud Service Profile (eg OCI – FastConnect Layer 2)
Step 9: Select connection source and destination metro
Step 10: Complete connection request form and submit order
Step 11: Complete BGP setup in Oracle Cloud Console
Configure your CPE to establish BGP session(s) with the DRG and exchange routes. Note that Oracle’s ASN is 31898 which is needed when setting up the BGP peering session. Here are some suggested steps:
- Check BGP is up – this can be viewed on your CPE or in the Oracle Console via the FastConnect VC state
- Check prefixes received and sent on your CPE
- Ping or trace route to the DRG using the IP that was setup as the Oracle BGP Peer IP
- Ping or trace route to the Bare Metal host or VM within Oracle Cloud
- Establish fail over testing to validate network design as needed
VCN Subnet Routing Notes
- Customers can announce up to a max of 2000 IPv4 prefixes to Oracle.
- Individual VCN subnet addresses are announced back to the CPE over FastConnect BGP. If a new subnet is added it will be automatically announced over BGP. The main VCN CIDR is not announced.
- CPE routes announced over FastConnect with BGP are not automatically propagated to subnets associated with route table associated with the DRG.
- Consequently, if a new route is announced from on-prem CPE an entry must be made in the route table to enable reachability of the on-prem route.
- To minimize the effect of change it is recommended to either consolidate multiple routes into a larger prefix or use the default route.