1. Using Oracle Cloud Infrastructure FastConnect Classic
  2. Managing the Service
  3. Providing Redundancy to Ensure High Availability

Providing Redundancy to Ensure High Availability

When you set up FastConnect Classic, configure your routers to prefer traffic over the FastConnect Classic path. Should this path become unavailable, configure your routers to send and receive traffic over the public Internet till the peering issue is resolved.

Ensure the following while setting up the redundant connection:

  • Set up a redundant connection to the Oracle edge routers, so that even if one of your connections fails, you won’t lose connectivity.

  • Configure the redundant connection in active or standby failover configuration so that traffic flows through only one link at a time. The secondary link is used only if the connection through the primary link or router fails.

  • Configure your routers so that even if both connections to FastConnect Classic fail, you can still access your Oracle Cloud services through the public Internet. The default configuration is to prefer the routes received over FastConnect Classic. If FastConnect Classic is not available, then set rules to route traffic related to your Oracle Cloud services over the public Internet, until the peering issue is resolved.

  • Complete any additional configurations within your network, which you may require, to manage the traffic flow across FastConnect Classic.

To achieve end-to-end redundancy from your network edge and to obtain the service level agreement (SLA) of 99.9%, Oracle recommends that you set up a primary and a secondary link between your network edge routers and Oracle routers. You must also establish two redundant BGP peers. It is not mandated to set up two links, but you forfeit the SLA of 99.9% if you only have one link and one BGP peer.

If you are connecting through Oracle FastConnect Partner, you’ll need to work with the partner to leverage the redundant connections through the partner connectivity service. Oracle and your Oracle FastConnect Partner are connected to provide redundancy. Your Oracle FastConnect Partner is required to connect to FastConnect Classic with two links to protect against failure of a single peering.

If applicable, update the virtual circuit to map the primary and secondary virtual circuits. You are required to work with your provider to validate the routing configurations between your network and Oracle through the partner connectivity service for FastConnect Classic.

If you are connecting through Direct Cross Connects, create two cross connects: primary and secondary. While creating the virtual circuit, map both the cross connects.