Oracle Cloud Infrastructure Documentation

FastConnect: With an Oracle Provider

This topic is for customers who want to use Oracle Cloud Infrastructure FastConnect by connecting to an Oracle provider. For a summary of the different ways to connect, see the connectivity models.

If you instead want to use a network provider that is not on the list of Oracle providers, see FastConnect: With a Third-Party Provider. Or if you want to use FastConnect by colocating with Oracle, see FastConnect: Colocation with Oracle.

For general information about FastConnect, see FastConnect.

Warning

Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.

Network Design for Redundancy

This section gives guidelines on how to design your network for redundancy so that it meets requirements for the Oracle Cloud Infrastructure FastConnect Service-Level Agreement (SLA).

In general, you should design your network with both of these in mind:

  • Regularly scheduled maintenance by Oracle, your provider, or your own organization.
  • Unexpected failures on the part of Oracle, your provider, or you own networking components. Failures are rare but need to be planned for.

For redundancy, Oracle provides:

  • Multiple FastConnect locations within each metro area
  • Multiple routers in each FastConnect location
  • Multiple physical circuits in each FastConnect location

Oracle handles redundancy of the routers and physical circuits in the FastConnect locations. You should then handle redundancy of the physical connection between your existing network and the Oracle provider. To do that, create two virtual circuits. Ensure that each runs on a different physical network connection to the provider, and goes to a different FastConnect location in the same metro area. Both virtual circuits go to the same DRG (if they're private virtual circuits). You'll have two separate BGP sessions from your edge to Oracle (one per virtual circuit). See the following diagram. An active/active configuration for routing traffic across the two connections is recommended and supported by Oracle.

This image shows two virtual circuits, each to a different location

For more information about creating redundant connections between your existing network and Oracle Cloud Infrastructure, see the Connectivity Redundancy Guide (PDF).

Getting Started with FastConnect

The following flow chart shows the overall process of setting up FastConnect.

This flow chart shows the steps for getting started with FastConnect

Also see the sequence diagram in To get the status of your virtual circuit.

Task 1: Learn and plan
Task 2: Set up connection to the Oracle provider
Task 3: Set up a DRG (private peering only)
Task 4: Set up your virtual circuit
Task 5: Give the provider information about the virtual circuit
Task 6: Configure your edge
Task 7: Check light levels
Task 8: Confirm your interfaces are up

BGP Session Goes to Oracle

Task 9a: Ping the Oracle BGP IP address
Task 9b: Confirm the BGP session is established

BGP Session Goes to the Provider

Task 10a: Ping the provider's edge
Task 10b: Confirm the BGP session is established
Task 10c: Ping the Oracle BGP IP address
Task 11: Test the connection

Managing Your Virtual Circuit

To get the status of your virtual circuit
To edit a virtual circuit
To terminate a virtual circuit
To manage public IP prefixes for a public virtual circuit
To move a connection to a different compartment

Monitoring Your Connection

You can monitor the health, capacity, and performance of your Oracle Cloud Infrastructure resources by using metrics, alarms, and notifications. For more information, see Monitoring Overview and Notifications Overview.

For information about monitoring your connection, see FastConnect Metrics.

Troubleshooting

See FastConnect Troubleshooting.