Oracle’s private connection model is called FastConnect. FastConnect Classic supports access to Oracle Cloud services. When you order FastConnect Classic at a particular location, you can only access the Oracle Cloud services that are provisioned at the same location. For example, to access an Oracle Cloud service that is provisioned at the Chicago data centre, you will order FastConnect Classic at Chicago. Here is a link to Oracle FastConnect Classic services.
Before starting, here are some key Oracle terms to understand:
A peering with FastConnect Classic edge routers through which you can access Oracle Public resources using public IP prefixes. Only public IP prefixes that are registered with IRR or RIR are publicly routable over the internet. IAAS, PAAS, and SAAS services available via Public Peering are listed here.
A peering with FastConnect Classic edge routers through which you can access Oracle Public resources using private IP prefixes. In this model, you will configure an IP Network and Private Gateway on the Oracle Console. IAAS and PAAS services available via Private Peering are listed here.
An IP network allows you to define an IP subnet in your account. The size of the IP subnet and the IP addresses in the subnet are determined by the IP address prefix that you specify while creating the IP network. Information on Oracle IP Networks can be found here.
Setting up a private gateway allows you to connect from your on-premise data centre to instances on IP networks using their private IP addresses. You can use this private gateway to establish a FastConnect Classic Private Peering connection. Information on Oracle Private Gateways can be found here.
A virtual circuit is a Layer 2 or Layer 3 Ethernet VLAN that isolates network traffic between customers. It is an isolated network path that runs over one or more physical network connections to provide a single logical connection between the router on the edge of your network and the Oracle router. Each virtual circuit is made up of information shared between you and Oracle, as well as an Oracle FastConnect Partner. Information on Oracle Virtual Connections can be found here.
Fast Connect Identifier (FCID)
An Oracle-assigned unique ID. This ID is included as part of the resource’s information in both the Console and API. This ID is for Oracle reference and does not need to be provided to Megaport.
Oracle FastConnect Classic customers can be provisioned as metered and non-metered as defined by Oracle and have different capabilities
within the Oracle FastConnect Classic customer portal:
Metered services are what Oracle calls ‘pay-as-you-go’.You might also hear metered services referred to as ‘committed’ or ‘a la carte.’With metered services, you are charged for your actual usage, meaning that all the services you use within OAC are accounted for and billed accordingly.
Non-metered services involve a pre-paid subscription for the cloud services you use. You might also hear non-metered services referred to as ‘uncommitted’ offerings.
The fixed nature of non-metered services means that your price won’t fluctuate regardless of your cloud usage. However, any unused services at the end of your twelve month subscription are non-refundable.
According to Oracle, this is the route to take if you are unsure what your organisation’s usage will be.
As shown below, metered customers can provision virtual circuits within the Oracle portal while non-metered customers need to engage their Oracle account team to fill out a questionnaire for the provisioning of the virtual circuits. Non-metered customers will need to provide Oracle the BGP IP addresses for peering.
There are two components involved with provisioning a FastConnect Classic connection. The first is establishing your connection with Oracle and the second is establishing your connection with Megaport.
Establishing FastConnect Classic with Oracle:
- For non-metered customers, contact your Oracle account team to confirm your requirements and complete the questionnaire for provisioning.
- For metered customers, log in to the Oracle FastConnect Classic Console.
- Navigate to Compute Classic, Open Service Console, FastConnect, Virtual Circuits, and Create Virtual Circuit. Give the virtual circuit a name, select Megaport as the provider, and select Public or Private peering and then select ‘Create’.
- Depending on your selection above of Public or Private, fields will appear that need to be populated to complete the request. If you selected Public Peering, as displayed here, you will require public prefixes to announce to Oracle. If you selected Private Peering, you will need to create an IP network and private gateway. In either case, private IPs can be used for BGP peering. Complete the required fields and select ‘Create’.
- (Optional) request for a redundant connection. 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 order redundant circuits. Note: This can be achieved from one MCR with two (2) virtual connections (VXCs). Please repeat the steps outlined in step 2 to order the redundant connection.
Establishing FastConnect Classic with Megaport:
- Log in to the Megaportal and provision the VXC(s) from your Megaport Cloud Router (MCR) to connect to your chosen FastConnect Classic location.
- Oracle offers an SLA on its FastConnect Classic connectivity but, in order to comply with this, you must ensure to deploy two FastConnect Classic VXCs for redundancy.
- A typical FastConnect Classic deployment might look like this:
- From your MCR choose +connection. Then select Megaport Marketplace.
- Select Oracle from the list of providers on the Megaport Marketplace.
- Select the Primary connection for the Oracle Region to which you want to connect. Oracle Fast Connect Classic on-ramps are designated as: OPC. Then select Next.
- The Oracle location you selected will be confirmed. Select ‘Next’. You will then be presented with the configuration screen for the FastConnect VXC. Continue with the configurations and complete the entries in the left-hand panel. Then, select ‘Next’.
- Name Your Connection. This section involves free text field allowing you to assign an easily identifiable name for this connection.
- Select your Rate Limit. Max Rate limit set by Oracle is 5gb (5000mbps)
- On the ‘Connection Detail for MCR A End’ page, you will enter details that are used to set up the BGP peering session between your MCR and the Oracle edge device.
The IP address entered here is the IP address of the MCR Interface facing Oracle that will be used for BGP peering.
For Oracle metered customers, please ensure to use the same IP addresses entered in the Oracle portal. For Oracle non-metered customers, please update oracle with the IP addresses you will be using.
Select +Add BGP Connections
Enter Peer ASN: Oracle ASN# 7160
Local IP: select from drop down
Peer IP: enter IP address for oracle edge device
Override MCR ASN: Oracle will only accept 2-byte ASNs. Please change the default AS number on the MCR to an integer between 64512 and 65534.
Once you have finished this configuration select add and then ADD VXC. Then select Order.
Wait a few minutes and you will see the dot on the left-hand side of your VXC turn from red to green. This indicates that Layer 2 connectivity has been established.After provisioning the VXC, copy the service ID# of the VXC and update your configurations in the appropriate field in the Oracle portal with the id#.
Oracle is automatically notified of the VXC request and will accept it within 24 to 48 hrs. To confirm the BGP is up in the Megaportal, click on the VXC and then on the Logs tab. It should show as ‘BGP Established’.
Should you wish to deploy a second FastConnect Classic (and this is recommended), repeat the steps above selecting the secondary location for the Oracle region to which you want to connect.
Additional useful links: