<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1705902170274878&amp;ev=PageView&amp;noscript=1">
Skip to content
Talk to Us
  • There are no suggestions because the search field is empty.

Oracle FastConnect Setup (Direct Interconnect)

IZO™+ Multi Cloud Connect delivers Oracle as a FastConnect circuit that you create in your own OCI console. The ordering journey is the standard Multi Cloud Connect flow, documented in full under Provisioning & Configuration. This page shows how that flow applies to Oracle, and the Oracle-side hand-off is the same whether you ordered IZO™+ Multi Cloud Connect Direct or IZO™+ Multi Cloud Connect Flex. 

This page sits alongside the ordering journey rather than repeating it. The TCx Portal steps that place and provision the connection are common to every IZO™+ Multi Cloud Connect order and live under Provisioning & Configuration. Here we focus on how the flow applies to Oracle: creating the FastConnect circuit and OCI/VC-ID, and completing the hand-off in your OCI console. 

[Prerequisites: Oracle side] : Before placing the order, in your OCI console: create a FastConnect circuit and choose the service provider – Tata Communications: IZO Multi Cloud Connect – Layer 3 (routed / BGP) or – Layer 2 (EoMPLS transport); choose your peering location and bandwidth (1 to 25 Gbps on the direct path); for Layer 3, select Private or Public peering and note the OCI/VC-ID Oracle generates. A single OCI/VC-ID is required for Layer 3, for Layer 2, create two OCI/VC-IDs (primary and secondary). 

How Oracle setup fits together

The end-to-end flow is the standard IZO™+ Multi Cloud Connect order, with the Oracle-side hand-off around it:

  1. Create the FastConnect circuit in your OCI console and note the OCI/VC-ID (single for Layer 3; two for Layer 2).

  2. Place your IZO™+ Multi Cloud Connect order for Oracle in the TCx Portal (Direct or Flex), sharing the OCI/VC-ID, the peering location, the bandwidth, the peering type, and – for Layer 2 – the IP subnet, ASN and MD5 key you will use.

  3. Tata Communications provisions the circuit and inputs the partner-side parameters.

  4. The configuration reflects automatically in your OCI console (provider-managed peering).

  5. Routing comes up.

Steps 2 and 3 are covered end to end under Provisioning & Configuration. See the IZO™+ Multi Cloud Connect Direct and IZO™+ Multi Cloud Connect Flex order pages for Oracle. This page covers the Oracle-side steps around them.

Addressing: provider-managed on Layer 3, customer-managed on Layer 2

On Layer 3 this is a provider-managed peering model: Tata Communications allocates the /30 private transit subnet (Private peering) and configures the BGP with Oracle, and the configuration reflects automatically in your OCI console. There is nothing for you to key in, and no CPE-to-Oracle BGP session to configure. (For Public peering, Oracle allocates the /30 public subnet.)

On Layer 2 you own the addressing: you configure the IP subnet, ASN and MD5 key on your CPE and in Oracle, and you run BGP to Oracle yourself over the EoMPLS transport.

On the Oracle side

Because Oracle is delivered as a FastConnect circuit in your own OCI tenancy, the Oracle-side hand-off is the same whether you ordered IZO™+ Multi Cloud Connect Direct or IZO™+ Multi Cloud Connect Flex. In your OCI console you:

  • Create the FastConnect circuit - Choose the service provider (Tata Communications: IZO™+ Multi Cloud Connect – Layer 3 or – Layer 2), the peering location and bandwidth, and – for Layer 3 – Private or Public peering. Note the OCI/VC-ID.

  • Attach the DRG and VCN - Associate the FastConnect virtual circuit with your Dynamic Routing Gateway and Virtual Cloud Network and set the VCN route tables.

  • Let routing come up - On Layer 3, Tata Communications runs the BGP to Oracle (ASN 4755 to Oracle's ASN 31898) and you reach OCI across the L3VPN, so there is no CPE session to configure. On Layer 2, bring up BGP from your CPE to Oracle using the IP, ASN and MD5 you set.

The click-by-click walkthrough is under Provisioning & Configuration. For the Oracle-specific detail on this side, see Oracle Routing and BGP Configuration for the routing, and Oracle L2VPN Services for the Layer 2 delivery.

Bandwidth changes

Bandwidth changes are initiated by you in the Oracle portal, subject to capacity. The OCI/VC-ID has a minimum of 1 Gbps; for sub-1 Gbps requirements use the Interconnection partner-routed path.

Related pages