<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 Routing and BGP Configuration

For Layer 3 FastConnect, the EBGP session per virtual circuit runs between the Tata Communications MPLS PE (ASN 4755) and Oracle (ASN 31898). The service is built as an L3VPN so your remote sites reach the VCN across the Tata Communications network; you do not run a BGP session from your on-premises CPE to Oracle on Layer 3. (On Layer 2, BGP is yours to manage directly with Oracle – see Oracle L2VPN Services) 

Oracle uses ASN 31898; Tata Communications uses ASN 4755. MD5 is optional and customer-supplied. Private peering uses a /30 private subnet allocated by Tata Communications; Public peering uses a /30 public subnet allocated by Oracle. BFD runs at 300 ms × 3. Oracle enforces prefix limits per peer. 

BGP parameters

Parameter

Value

Oracle ASN

31898 (fixed)

Tata Communications ASN

4755 (fixed)

BGP sessions

One per virtual circuit; a pair (primary + secondary) for redundancy

MD5 authentication

Optional; provided by the customer and shared on both sides if used

BGP transit subnet (Private peering)

/30 private, allocated by Tata Communications

BGP transit subnet (Public peering)

/30 public, allocated by Oracle

BFD

300 ms hello × 3

Peering modes

  • Private peering reaches resources inside your VCN (compute instances, databases, private endpoints). Tata Communications allocates the /30 private transit subnet. Private peering accepts both public and private customer ASNs.

  • Public peering reaches Oracle public services (Object Storage, Autonomous Database, OCI APIs) over the dedicated connection. Oracle allocates the /30 public transit subnet, and a public customer ASN is required.

      Peering mode is selected by you in the OCI console when you create the FastConnect circuit.

      Prefix limits

      Oracle enforces a prefix limit per peer. If the limit is exceeded, the BGP session is dropped and re-establishes once advertised prefixes are back under the limit.

      Virtual circuit type

      Prefix limit

      Private

      2,000 IPv4 prefixes and 500 IPv6 prefixes

      Public

      200 prefixes

      Keep your outbound advertisements filtered to what Oracle needs, well within these limits, to avoid session resets.

      Prefix policy

      • Outbound (to Oracle): advertise only the on-premises prefixes Oracle needs to reach. Sending a default route to Oracle is rarely correct.

      • Inbound (from Oracle): accept the VCN CIDRs (Private peering) or the Oracle public-service prefixes (Public peering).

          Path control

          Where two circuits are used for redundancy, Tata Communications applies BGP Local Preference and AS-PATH prepending to make one path primary and the other secondary. The scheme and capacity planning are on Oracle Resiliency and High Availability.

          Quality of service

          Oracle does not honour QoS markings on FastConnect. On the Tata Communications backbone, a single class of service is applied to the circuit; you can select the class that suits your application, but only one class applies per circuit.

          Related pages