(inspiring ambient music)
- [Sergio] Hello and welcome to this lesson on FastConnect.
It is a deep dive and we're seeing
design considerations for OCI FastConnect,
so let's go ahead and get started.
So the overview indicates that FastConnect
is a high speed, low latency private connection
between Oracle Cloud and your on-premises network.
And FastConnect can be configured for high availability
and it offers elasticity and you can scale it as you wish.
For example, you can have a one gigabit connection initially
and then grow it to a 10 gigabit
or even 100 gigabit connections.
The 100 gigabit connection is supported
on special configurations and link aggregation is supported
so if you have two one gigabit per second connection,
if you have two of them, then it could operate
as one two gigabit per second connection.
We have different connectivity options for FastConnect.
You can have private or public hearing.
And we'll take a deep dive shortly
and indicate what is the difference
between these two types appearing.
There is no data transfer charge.
And when do you need, what's a use case for FastConnect?
So whenever there's a need for low latency,
FastConnect can offer you low latency
and predictable performance.
When you're moving big data
or you need high performance computing
for data transfer needs,
then FastConnect is a solution that you can leverage.
Also, you can use FastConnect when the data
is so sensitive that it cannot go over the public internet.
And when you're moving the data from on-premises
to Oracle Cloud Infrastructure
and you're mandated to not move that data over the internet,
then FastConnect is pretty handy.
And when you're migrating either from on-premises
or from another cloud service provider, big amount of data,
you're migrating all your data,
you're migrating your virtual machines, your databases,
then FastConnect is the fastest way
to migrate from on-premises to Oracle Cloud Infrastructure.
And we mentioned that we were going to explain in detail
what's the difference between public peering
and private peering and here it is graphically.
Private peering is the one that we're most familiar with
because it connects your resources
from the virtual cloud network
into your local area network that you have on-premise.
So the private I address of any compute instance
sitting on a public or the IP address of a private instance,
communicating to your local area network
is done with the private peer.
Now the public peer is when you need to connect
to public facing resources from Oracle Services Network,
such as object storage, the autonomous data warehouse,
and Oracle Analytics Cloud.
All of these are resources that sits
on the Oracle Services network,
so you can use the public peering to bypass the internet.
So you're using OCI or your tenancy to connect
to the Oracle services network,
bypassing the internet together.
So each virtual circuit, whenever you're creating it,
there's three parties involved.
No matter what option you select,
there's always three parties.
There's Oracle Cloud Infrastructure,
either the third party provider,
the Oracle FastConnect partner,
and you yourself as the customer.
Now, there's several ways
that you can connect your FastConnect.
One link can serve the whole enterprise.
Every single resource sitting on premises
can leverage that link or you can have dedicated links
or CIDR blocks or CIDR blocks that you might have.
IPv4 CIDR blocks, IPv6, pre Pyxis for example.
Here you can have one FastConnect link
that serves this private IP CIDR block
and another one for this other one.
So you decide how is it that you want to configure this.
Now FastConnect uses Border Gateway Protocol.
So the routes that you have on premises
can be propagated to the dynamic routing gateway
through BGP and also the CIDR blocks
that you have from your subnet
or from your VCN can be propagated
as a route to your on-premise router.
And we already mentioned this.
Virtual circuits can either be private or public.
Now IPv6, I mentioned the IPv6 prefix, it is supported.
It is supported so when you're configuring
your virtual circuit, you will have a checkbox
for you to enable IPv6.
Now if you do that,
you need to provide the customer BGP IPv6 address
and also your own on the Oracle Cloud Infrastructure,
the Oracle BGP IPv6 address.
This is screen capture from the actual OCI console.
When you specify the address,
you must include the subnet mask,
and these are the subnets prefix
that you can work with.
Now we mentioned that we have several options
for you to leverage in FastConnect
and some of them might be available to you,
some of them might not be available to you.
So the easiest one and it's very quick,
is to do it through an Oracle partner and why?
Cause we already established relationship with that partner,
and all you have to do is select a partner,
go into the partners console
and start configuring on their console FastConnect.
And then you go into OCI and configure the OCI part.
And then through either the partner
or manually your IT person then will configure the portion
that goes from on-premises to the Oracle partner.
Now the third party provider is when you are using a vendor
that is not our partner and you want to use that vendor.
So they will take the circuit, the physical circuit,
all the way into the Oracle Cloud Infrastructure Data Center
and make all the necessary configurations
with a letter of authority
issued by Oracle Cloud Infrastructure.
Now this is a longer process and it's complex,
and it's more expensive.
Now, if you do not want to utilize
one of our Oracle partners,
but you have presence in the same data center
where Oracle Cloud Infrastructure has their cages
for their routers, then that's an easy configuration.
How you need to do is establish a patch cable
that goes from your cage
to the Oracle Cloud Infrastructure cage.
And this is less expensive
because you're not using a Telco partner,
you're using the data center partner.
So that's why I would say
that there's always three parties involved,
even in the co-location with Oracle.
So let's go ahead and take a look,
a deeper look into all these three options.
So the first one is with an Oracle Partner.
And here grade out we have the typical
software defined network, which is the virtual cloud network
and the supported services, either Dynamic Routing Gateway
or the Oracle Services Network.
But all of these are construct,
the physical hardware sits on the data centers
or the edge data centers.
And here's where you have your routers
that physically connect the circuit
to the partner portion or the partner's data center.
And then they'll extend this connectivity
to your customer premise equipment.
Here's network-to-network,
and this is the WAN Circuit that goes
from the partner to your customer premise equipment.
And notice how these are redundant.
So we have a cage
and we have redundancy through routers,
and we also have redundancy by a data center.
So we have two data centers,
each one of them with two routers.
Now once you have that,
you can select if you want to have layer two or layer three.
So layer two, the BGP session goes directly
from you into Oracle Cloud Infrastructure,
and the partner serves as a cable.
The autonomous systems are you
and Oracle Cloud Infrastructure.
Now layer three is when you go
to the partner first for your BGP session
and then here internally, the partner routes
their own BGP session to Oracle Cloud Infrastructure.
So we have three systems here.
Now how is that we connect with a third party provider?
Again, we do not have a partnership
with this third party provider,
a partnership in the sense that we already have an agreement
and you go into their council.
No, there's nothing like that
with the third party provider.
They will take physical circuits
into the Oracle Cloud Data Center
and establish all the necessary connectivity
for both private peering and public peering.
Of course, they're going to get a letter of authority
and emphasize this is a long process
because there's many moving parts that go.
But rest assured that Oracle Cloud Infrastructure
has experience with all offerings,
we are the ones offering it and this how it looks.
Basically this is the physical portion.
You go to the data center
and you connect to one of the routers
and you take this long cable
or this long circuit from your on-premises location,
and the provider will take it to the Oracle Data Center.
And then there will be a patch here
to cross connect as we call it and this is the WAN circuit
and this is the edge, this is the patch cable,
and then we have all the software defined
network services behind the physical network
of the Oracle Cloud Infrastructure region.
Now once you have all of that,
this is with greater detail,
you go from the customer equipment into the customer panel,
then the customer or the third party carrier
will this into their own panel.
And here's the patch panel
that goes into the Oracle Cloud Infrastructure.
And then we have the patch goes
from the Oracle Data Center to panel.
And of course this you need a letter of authority.
And these are the steps you need to submit
a cross connect order to the Colocation provider.
And Coresite is one of those Colocation providers.
And then they're the ones
that are going to be managing the letter of authority
and making sure that this physically happens.
And this is very important,
the customer may need to run a fiber
from Customer Cage to the Meet Me Room.
Because this doesn't again,
this is why this is more expensive than the other options.
Once you have all of that,
then you can establish your virtual circuit.
So this is the easy part,
you establish the virtual circuit,
and here's the Dynamic Broad Gateway,
establishing the FastConnect version circuit
to the customer premise equipment.
And also the same thing
for the virtual public peering virtual circuit.
Now the co-location with Oracle is a little bit easier
because the customer is already
at the same data center where our cage is.
So here you establish the patch cable
between your (indistinct) Customer Cage to the OCI Cage.
And then the BGP session, the virtual circuit is established
so this is the deep dive into FastConnect.
Thank you very much for watching,
this concludes this session,
this concludes this lecture, thank you very much.