Skip to content

Creating MCR Connections to Oracle Cloud Infrastructure

The Oracle Cloud Infrastructure (OCI) private connection model is called FastConnect. FastConnect provides private connectivity and self-service provisioning, including full API-level integration.

When connecting to the Oracle Cloud Infrastructure (OCI) through FastConnect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection. Layer 3 BGP connectivity is established directly between you and Oracle.

A common FastConnect deployment might look like this: FastConnect deployment

This topic describes the basic steps needed to establish a FastConnect connection:

  • Create the FastConnect in the Oracle console with Megaport as the provider.
  • Provision the VXC in the Megaport Portal to connect to your FastConnect location.

Note

Oracle offers a service level agreement (SLA) for its FastConnect connectivity, as long as you configure two FastConnect VXCs for redundancy.

Tip

You can deploy a Megaport MCR using the OCI console without having to switch between the Oracle and Megaport Portals. For more information, see FastConnect integration with Megaport Cloud Router.

Creating the FastConnect

The first task before you connect MCR to your target Oracle Virtual Cloud Network (VCN) is to create a FastConnect in the Oracle console.

To create FastConnect in the OCI console

  1. Log in to the OCI console and select the region from the upper-right corner. FastConnect region

  2. Create a compartment or select an existing compartment to deploy these new resources.

    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. FastConnect compartment

  3. Select Networking > Virtual Cloud Networks. Create FastConnect

  4. Create your VCN, which is a customizable and private network in OCI.

  5. If you plan to use a private virtual circuit (private peering) to advertise private IPv4 addresses such as RFC 1918, you need to create a Dynamic Routing Gateway (DRG).

    A DRG is a virtual edge router attached to your VCN that provides a single point of entry for private traffic coming into your Virtual Cloud Network (VCN). Use the OCI console to set up a DRG and attach it to your VCN. A DRG can be attached to only one VCN at a time. Next, you need to update routing in your VCN to include a route rule to send traffic to the DRG. It's easy to forget to update the route table but without the route rule, no traffic will flow.

  6. Create the FastConnect.

    When you create the FastConnect in the Oracle Console, Oracle provides you with an Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID).

  7. Click the FastConnect to view its details.
    FastConnect details

  8. Copy the OCID.

  9. Confirm the autonomous system number (ASN).

  10. Log in to the Megaport Portal.

Creating a VXC to FastConnect

With an MCR configured, VXCs are needed to connect to services on the Megaport network. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MCR) and a B-End (a port location based on the FastConnect region).

To create the VXC to FastConnect

  1. In the Megaport Portal, choose Services and select the MCR you want to use.
    If you haven’t already created an MCR, see Creating an MCR.
  2. Add a VXC for the MCR.
    If this is the first connection for the MCR, click the Oracle tile. The tile is a shortcut to the Oracle Configuration page. Alternatively, click +Connection, click Cloud, and click Oracle.
    FastConnect details

  3. Enter the OCID you copied from the Oracle Console.
    The Megaport Portal verifies the OCID and displays the available port locations based on the FastConnect region. For example, if your FastConnect service is deployed in Ashburn, you only see the Ashburn FastConnect targets.

  4. Select a target location for your first connection and click Next. FastConnect details

  5. Specify the connection details:

    • Connection Name – The name of your VXC to be shown in the Megaport Portal.

    • Service Level Reference (optional) – Specify a unique identifying number for the VXC to be used for billing purposes, such as a cost center number or a unique customer ID. The service level reference number appears for each service under the Product section of the invoice. You can also edit this field for an existing service.

      Note

      Partner-managed accounts can apply a Partner Deal to a service. For more information, see Associating a Deal With a Service.

    • Rate Limit – The speed of your connection in Mbps. Enter the same rate or up to the rate you specified in the Oracle Console.

    • VXC State – Select Enabled or Shut Down to define the initial state of the connection. For more information, see Shutting Down a VXC for Failover Testing.

      Note

      If you select Shut Down, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.

    • Minimum Term – Select No Minimum Term, 12 Months, 24 Months, or 36 Months. Longer terms result in a lower monthly rate. 12 Months is selected by default.
      Take note of the information on the screen to avoid early termination fees (ETF). See VXC Pricing and Contract Terms and VXC, Megaport Internet, and IX Billing for more information.
      FastConnect details

  6. Click Next.

  7. Enter the IP address and mask for the MCR interface facing Oracle. This IP address matches the address you entered in the Oracle Console to create the FastConnect.

  8. Click Add BGP Connection.

  9. Specify the connection details:

    • Local IP – Select the IP address assigned to the MCR from the drop-down list. In this example, the local IP address is 192.168.100.1/30.

    • Peer IP – Specify the second available IP address in the /30 CIDR. In this example, the peer IP address is 192.168.100.2/30.

    • Peer ASN – Enter 31898, which is the peer ASN for FastConnect. The peer ASN is always 31898.

    • BGP Password (optional) – Specify a shared key to authenticate the BGP peer. The shared key length is from 1 to 32 characters. This is not a mandatory field for Oracle connections because they traverse a private path.

    • BGP State – Shuts down the connection without removing it. The initial setting will be taken from the setting on the A-End of the MCR. Enabling or shutting down the BGP state does not impact existing BGP sessions. The BGP state only affects new VXCs. This setting overrides the MCR state for an individual connection.

  10. Click Add.

  11. Click Next.
    A summary page appears that includes the monthly cost.

  12. Click Back to make changes or click Add VXC.

Once you have finished this configuration, you can configure additional VXCs or complete the order.

Viewing the VXC status

You can check the VXC status in the Megaport Portal Service page.

VXC established

To view the VXC connection details

  1. Click the VXC name.
    VXC connection details

  2. View the service status from the Details tab. In this example, both Service Status (Layer 2) and BGP IP Address (Layer 3) are green, indicating that the services are up.

  3. Return to the Oracle Console to view the FastConnect status.
    FastConnect status

Next steps

  • Oracle offers an SLA on its FastConnect connectivity. To comply with the SLA, you need to deploy two FastConnect VXCs for redundancy. You must set up both BGP sessions on separate VXCs. You can configure the VXCs on a single MCR or across two MCR instances, depending on your HA requirements.

  • To establish a separate BGP session, create a FastConnect on the Oracle Console and repeat the steps in the Megaport Portal.


Last update: 2024-04-15