Alright, what we want to do is we want to make sure we can walk through a
couple of architectural exercises,
make sure we understand which on-ramp solution would make the most sense in any
given scenario.
So you're welcome to pause the video and try to figure out, okay, based on the
scenario, which one would I deploy,
I understand some of these icons might not make as much sense as what it would
if it was explained,
so also you could wait and allow me to explain each scenario and then pause the
video at that point.
But either way, we just want to recognize which scenarios belong to which
specific solution.
So, number one here, what we have is we have a physical edge that needs to
connect out to an AWS,
or maybe an Azure or Google site.
Now, again, when we think about these vendors, these are these infrastructure
as a service vendors.
I'm going to spin up corporate virtual machines, and I'm going to place them
inside of these networking spaces.
Now, the implication here with these dots is that not only do I have three of
these networking spaces,
I actually have a lot of them.
So what we're going to do when we see IaaS at play here is we're going to look
at on-ramp for multi-cloud.
Remember, on-ramp for multi-cloud sort of came out of the IaaS space.
We can still deploy a basic on-ramp for IaaS type of solution where I deploy a
virtual edge into one of these,
or really all of these virtual networking spaces, but as we said, it doesn't
scale very well.
Instead, what I can do is I could deploy a couple of virtual edges here at the
cloud edge,
and I can interact with their cloud gateways, squeeze that in here, which then
tie into all of the different virtual networks.
And so at that point, we are running a very scalable version of this, but keep
in mind that we do have some options there.
Now, number two here, what we have is we have an edge site that's trying to get
out to the software vendor.
So when we see a software vendor out on the cloud, especially hanging off of
the internet,
now we're talking about software as a service, which is probably a pretty big
giveaway for what we're on-ramp solution we're going to deploy here.
Here's the idea. We probably think that we want to take this direct path, but
what would happen if I took this path through the WAN connection,
which by the way, I'm going to have an IPsec tunnel here, and then I take this
internet circuit.
Well, if this internet circuit on the left is small, and this one on the right
is much larger, this might actually make sense.
And so we're going to leverage that quality of experience value between zero
and 10, and just allow the system to figure out which one makes the
which pathway has the better experience for the end users.
So if this side has an eight and this side has a six, well, then we know that
we should use the WAN circuit,
although if it's the other way around, because we do have a good local internet
circuit, then of course, we would just take the local one at that point.
But this is going to be our on-ramp for SaaS solution, and it's a very good one
that allows us to integrate or that we can integrate into our SD WAN
environment.
So lastly, we have this final solution, this virtual infrastructure with baked
in hardware. This should be a really good giveaway that we're talking about on-
ramp for co-location.
And naturally, a minimum, we have process elimination, because that's the only
one left.
The idea here is that I can take my users, and rather than sending them
directly over to another edge site through whatever internet circuits we have
available,
I can instead find a regional co-location here, and then not only just deploy a
virtual edge or even a physical edge at that point, but rather instead I'll
deploy a whole virtual infrastructure.
Now, as virtual infrastructure still has hardware, remember we have a pair of
catalyst 9500s, and we also have a pair of the servers, those CSP 5000s, which
will run the virtual infrastructure.
So we're talking about a pretty nice Cisco infrastructure here, Cisco hardware,
and then taking advantage of these big fat pipes to leverage the concept of
that middle mile optimization.
So quite a few takeaways from the skill, understanding the concept of middle
mile optimization is huge, but just generally speak, I mean, look at number two
there, we're going to take this WAN circuit to use somebody else's internet,
because that actually might be a better end user experience.
It's kind of fascinating to recognize this. Now, naturally, if we have more of
a local regional play, we probably don't need to worry too much about this, but
the more global our corporation is, the more likely we are going to find that
different points of presence around the world might actually create
better end user experiences for our users, especially if we're already trying
to funnel user traffic one way, and maybe it would be better if we allowed it
to do something else.
Either way, Cisco has three primary solutions here that are very, very good,
and we definitely want to know the difference, how each one works, and in which
situations we'd want to consider using them.
I hope there's been a formative for you, and I'd like to thank you for viewing.