WEBVTT 1 00:00.000 --> 00:03.360 All right, let's draw some tunnels here on this diagram. 2 00:03.360 --> 00:08.200 So we're talking about the TLS and DTLS tunnel for non-data plane traffic. 3 00:08.200 --> 00:13.040 We're really talking about seeing these tunnels establish among all of the 4 00:13.040 --> 00:14.240 different devices 5 00:14.240 --> 00:15.760 for the most part. 6 00:15.760 --> 00:23.580 And so we're going to see, for example, our edges form TLS or DTLS tunnels to 7 00:23.580 --> 00:24.720 the V smart 8 00:24.720 --> 00:27.640 and same thing over to the V manage. 9 00:27.640 --> 00:31.710 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 9 00:27.640 --> 00:31.710 But one thing to keep in mind is that even though we do form DTLS connections 10 00:31.710 --> 00:32.160 to the 11 00:32.160 --> 00:38.440 V bond, which only supports DTLS, as we recall, those actually get broken down. 12 00:38.440 --> 00:43.240 So we start by forming these tunnels, but then they do end up going away. 13 00:43.240 --> 00:50.300 Meanwhile, we do maintain a full mesh of TLS or DTLS connections among the 14 00:50.300 --> 00:51.760 different non-data 15 00:51.760 --> 00:53.080 plane nodes as well. 16 00:53.080 --> 00:58.120 So quite a few of these TLS or DTLS tunnels in our environment. 17 00:58.120 --> 01:02.680 So let's now talk about the IPsect tunnels. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 17 00:58.120 --> 01:02.680 So let's now talk about the IPsect tunnels. 18 01:02.680 --> 01:05.650 So the IPsect tunnels are going to be used for data plane traffic, and those 19 01:05.650 --> 01:06.120 are only 20 01:06.120 --> 01:11.120 going to be maintained among the edge devices. 21 01:11.120 --> 01:15.850 Now these IPsect tunnels usually are going to end up being built in a full mesh 22 01:15.850 --> 01:16.400 fashion 23 01:16.400 --> 01:19.320 across different WAN fabrics. 24 01:19.320 --> 01:23.020 So if we have multiple WAN fabrics, then we need to figure out, okay, well, 25 01:23.020 --> 01:28.320 maybe I form tunnels through this one as well as through this one in order to 26 01:28.320 --> 01:29.120 get to the 27 01:29.120 --> 01:31.040 same WAN edge device. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 27 01:29.120 --> 01:31.040 same WAN edge device. 28 01:31.040 --> 01:34.530 For now, we're just going to show this as a full mesh among the edge devices, 29 01:34.530 --> 01:34.640 but do 30 01:34.640 --> 01:39.320 keep in mind as well that we have partial mesh options. 31 01:39.320 --> 01:42.280 So it's not so much that it has to be full mesh. 32 01:42.280 --> 01:43.360 We could do partial mesh. 33 01:43.360 --> 01:47.230 We have control over that, but in a lot of situations, we're forming a lot of 34 01:47.230 --> 01:47.680 IPsect 35 01:47.680 --> 01:50.440 tunnels among our edge devices. 36 01:50.440 --> 01:53.000 Now lastly is the OMP route exchanges. 37 01:53.000 --> 01:58.680 As we talked about in the quiz, if I am exchanging routes with the V smart as a 38 01:58.680 --> 01:59.980 edge device, 39 01:59.980 --> 02:04.860 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 39 01:59.980 --> 02:04.860 well, those routes will get pushed down from the V smart to the other edge 40 02:04.860 --> 02:06.020 devices thanks 41 02:06.020 --> 02:10.900 to the fact that it's going to serve as a sort of a route reflector. 42 02:10.900 --> 02:15.500 So I don't need to share routes directly with other edge devices, and we don't 43 02:15.500 --> 02:15.900 need 44 02:15.900 --> 02:18.740 to share routes outside of the V smarts. 45 02:18.740 --> 02:22.060 So that's how a lot of these connections come together. 46 02:22.060 --> 02:25.830 Let's just try to remember how the different tunnels are formed and what those 47 02:25.830 --> 02:26.400 look like 48 02:26.400 --> 02:28.680 and which devices are forming those tunnels.