All right, let's draw some tunnels here on this diagram.
So we're talking about the TLS and DTLS tunnel for non-data plane traffic.
We're really talking about seeing these tunnels establish among all of the
different devices
for the most part.
And so we're going to see, for example, our edges form TLS or DTLS tunnels to
the V smart
and same thing over to the V manage.
But one thing to keep in mind is that even though we do form DTLS connections WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But one thing to keep in mind is that even though we do form DTLS connections
to the
V bond, which only supports DTLS, as we recall, those actually get broken down.
So we start by forming these tunnels, but then they do end up going away.
Meanwhile, we do maintain a full mesh of TLS or DTLS connections among the
different non-data
plane nodes as well.
So quite a few of these TLS or DTLS tunnels in our environment.
So let's now talk about the IPsect tunnels. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's now talk about the IPsect tunnels.
So the IPsect tunnels are going to be used for data plane traffic, and those
are only
going to be maintained among the edge devices.
Now these IPsect tunnels usually are going to end up being built in a full mesh
fashion
across different WAN fabrics.
So if we have multiple WAN fabrics, then we need to figure out, okay, well,
maybe I form tunnels through this one as well as through this one in order to
get to the
same WAN edge device. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
same WAN edge device.
For now, we're just going to show this as a full mesh among the edge devices,
but do
keep in mind as well that we have partial mesh options.
So it's not so much that it has to be full mesh.
We could do partial mesh.
We have control over that, but in a lot of situations, we're forming a lot of
IPsect
tunnels among our edge devices.
Now lastly is the OMP route exchanges.
As we talked about in the quiz, if I am exchanging routes with the V smart as a
edge device,
well, those routes will get pushed down from the V smart to the other edge WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
well, those routes will get pushed down from the V smart to the other edge
devices thanks
to the fact that it's going to serve as a sort of a route reflector.
So I don't need to share routes directly with other edge devices, and we don't
need
to share routes outside of the V smarts.
So that's how a lot of these connections come together.
Let's just try to remember how the different tunnels are formed and what those
look like
and which devices are forming those tunnels.