Alright, let's jump into this topology challenge.
So what we have here is a topology with a couple of plain circuits, just a
couple of
routers to keep things simple here.
And the first question is how many tunnels will be formed?
Well, when we're thinking about tunnels, we have to think about things from
both a control
plane and a data plane perspective.
From a data plane perspective, we're going to form a tunnel this way through
the MPLS
provider and a tunnel this way through the internet provider. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
provider and a tunnel this way through the internet provider.
And so that would be two IPsec tunnels.
Hopefully we're using IPsec.
But we're not done there because we have to consider the control plane tunnels.
I am actually building tunnels out to not just the V-Smart, so there's another
two to
the V-Smart, but I'm also building tunnels out to the V-Manage, which wasn't
listed
here.
So keep that in mind that we're going to need to form tunnels this way to
secure the
communication between the V-Manage and the WAN edge. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
communication between the V-Manage and the WAN edge.
So if we count up all of these tunnels, then we actually have a total of six
tunnels
because we have also two tunnels going to the V-Smart.
And so these would be TLS or DTLS and two going to the V-Manage, again TLS or D
TLS.
Now what about the V-Bond?
Well remember the V-Bond, we do form DTLS tunnels, but they actually end up
breaking down
to the SD-WAN edge devices after they've been torn down. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to the SD-WAN edge devices after they've been torn down.
But we do form tunnels to the V-Manage.
So we're still not done because we have two to the V-Manage from the SD-WAN
devices, but
we also have two that the V-Bond is running.
And remember the V-Bond always runs DTLS.
Oh, and let's not forget that we do have a tunnel forming between the V-Manage
and the
V-Smart.
So we'll actually add one more onto this.
And so that gives us a total of nine tunnels. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And so that gives us a total of nine tunnels.
So again, it's important for us to recognize it's not just about the data plane
tunnels,
but we also have tunnels on the control plane side of things, which includes
the management
and orchestration planes and devices as well.
Now next, given the multi-tenant environment, how many VPNs will be used in
total?
So we know that we're going to need VPNs for each of the customers.
Let's say again, VPN 10 for customer A and VPN 20 for customer B. Just remember WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's say again, VPN 10 for customer A and VPN 20 for customer B. Just remember
that we're
also using VPN 0 for the underlay.
And we're using VPN 512 for the sake of management information.
So we're actually using four total VPNs in this environment.
Now next map out the OMP adjacencies that exist.
Well, OMP is going to only exist between an edge device and V-Smart.
And if we have multiple V-Smarts, then we'll have multiple connections per one WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And if we have multiple V-Smarts, then we'll have multiple connections per one
edge device.
But when we're talking about just a single V-Smart as we have in the diagram
here, my OMP
connections are going to be here.
For OMP and here as well, which means that we have a total of two adjacencies.
The key point here, we do not form OMP adjacencies from when edge to when edge.
The benefit of OMP and using the V-Smart is essentially a route reflector is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
The benefit of OMP and using the V-Smart is essentially a route reflector is
that we don't
have to have a full mesh.
All of my subnets that I'm learning will be advertised via OMP to the V-Smart
and then
pushed down to the other when edge devices.
Now lastly, we're forming all of these tunnels, especially the data plane
tunnels via these
pseudo interfaces that we're calling T-Locks.
But the T-Locks don't have an IP address associated.
So how do I know how to connect?
Well that is the job of OMP.
OMP has those T-Lock routes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
OMP has those T-Lock routes.
Remember there are three different route types.
The T-Lock route is going to say, hey, if you want to connect to T-Lock A, use
this IP
address.
Because the T-Locks have the color information, I also know which WAN circuit
provider to use.
So this challenge was just intended to bring together a bunch of the different
concepts
that we talked about throughout the skill.
There's a lot of information in here, but we just have a few key takeaways here
.
Namely, how many tunnels are formed, where tunnels are formed, what type of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Namely, how many tunnels are formed, where tunnels are formed, what type of
tunnels
are formed, and then also how T-Locks come together.
We're going to want to remember those three pieces of information that make up
a T-Lock.
The fact that a T-Lock doesn't include its own IP address.
And so we need to know how to connect to that and OMP is sort of the glue that
brings
everything together.
I hope there's been informative for you and I'd like to thank you for viewing.