WEBVTT 1 00:00.000 --> 00:03.680 All right, let's have a little bit of an interactive quiz session. 2 00:03.680 --> 00:06.630 So I'm going to ask a question, be sure to pause the video, make sure you can 3 00:06.630 --> 00:07.040 answer this 4 00:07.040 --> 00:10.280 question before we get right into the answer. 5 00:10.280 --> 00:14.350 So to start with, how does SD-WAN deliver a consistent, controllable 6 00:14.350 --> 00:15.320 architecture over 7 00:15.320 --> 00:18.280 a diversity of WAN circuit types? 8 00:18.280 --> 00:23.150 So the whole premise of SD-WAN is I can have all kinds of complexity, again, 9 00:23.150 --> 00:24.400 diverse WAN 10 00:24.400 --> 00:29.240 circuit types, MPLS, Internet, LitFiber services, all kinds of things. 11 00:29.240 --> 00:31.520 And I'm going to create my own architecture. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:29.240 --> 00:31.520 And I'm going to create my own architecture. 12 00:31.520 --> 00:36.260 So anytime we're talking about software-defined networking, we have the overlay 13 00:36.260 --> 00:36.880 concept, 14 00:36.880 --> 00:42.950 which is the network I want, and we have the underlay, which is the network 15 00:42.950 --> 00:44.120 that I have. 16 00:44.120 --> 00:48.160 This is the way that we can kind of keep track of which one is which. 17 00:48.160 --> 00:53.250 And so if I have a bunch of diverse circuit types, what I want is something a 18 00:53.250 --> 00:54.000 little bit 19 00:54.000 --> 00:56.960 more consistent and controllable. 20 00:56.960 --> 01:00.110 And more often than not, I'm going to build that overlay using some form of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 20 00:56.960 --> 01:00.110 And more often than not, I'm going to build that overlay using some form of 21 01:00.110 --> 01:01.360 tunneling mechanism. 22 01:01.360 --> 01:03.080 Now we've got a lot of tunnels out there. 23 01:03.080 --> 01:08.080 And the way that SD-WAN delivers it is C via IPsec tunnels. 24 01:08.080 --> 01:10.800 A lot of data center deployments will use VXLAN. 25 01:10.800 --> 01:14.400 We'll see that software-defined access uses VXLAN as well. 26 01:14.400 --> 01:19.710 GRE and DMVPN are traditional ways that we can build tunnels in the network as 27 01:19.710 --> 01:20.400 well. 28 01:20.400 --> 01:24.070 But what we're going to find is even if we have something like DMVPN, we're 29 01:24.070 --> 01:24.400 going to 30 01:24.400 --> 01:29.230 want to build IPsec tunnels over the top of that, because this will be part of 31 01:29.230 --> 01:30.920 the underlay WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 31 01:29.230 --> 01:30.920 the underlay 32 01:30.920 --> 01:34.200 and we're still going to build our own overlay over the top of that. 33 01:34.200 --> 01:39.760 So C IPsec tunnels, that is how we build out an SD-WAN architecture. 34 01:39.760 --> 01:41.920 Question two, and there are four questions by the way. 35 01:41.920 --> 01:46.440 What Cisco SD-WAN device is responsible for route distribution? 36 01:46.440 --> 01:49.960 The answer here has to do with, well, it's route distribution, it's probably 37 01:49.960 --> 01:50.640 our control 38 01:50.640 --> 01:54.960 plane device, and our control plane device would be the VSmart. 39 01:54.960 --> 01:58.590 Certainly one of the key takeaways from the skills is going to be making sure 40 01:58.590 --> 01:59.040 we know 41 01:59.040 --> 02:03.420 what all of these different devices are doing and which plane that they belong WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 41 01:59.040 --> 02:03.420 what all of these different devices are doing and which plane that they belong 42 02:03.420 --> 02:03.840 to. 43 02:03.840 --> 02:06.320 In our case, VSmart belongs to control plane. 44 02:06.320 --> 02:11.010 It's going to run that overlay management protocol or OMP routing protocol, 45 02:11.010 --> 02:11.560 which is 46 02:11.560 --> 02:14.440 very BGP-like in the way it behaves. 47 02:14.440 --> 02:18.090 And we're going to push routes down to all of our WAN edge devices, informing 48 02:18.090 --> 02:19.160 them of which 49 02:19.160 --> 02:23.240 tunnels should be used for which types of traffic. 50 02:23.240 --> 02:28.350 So right back to it with another SD-WAN device, which one has to have a public 51 02:28.350 --> 02:29.400 IP address? 52 02:29.400 --> 02:33.670 It's very important for us to understand this because it does speak to the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 52 02:29.400 --> 02:33.670 It's very important for us to understand this because it does speak to the 53 02:33.670 --> 02:34.840 responsibilities 54 02:34.840 --> 02:36.680 of this particular device. 55 02:36.680 --> 02:39.540 For example, we look at the planes of operation, we're going to look at that 56 02:39.540 --> 02:41.200 orchestration plane, 57 02:41.200 --> 02:47.120 and part of the responsibility of the orchestration plane is to do onboarding. 58 02:47.120 --> 02:51.160 If we are going to onboard devices and form tunnels to one another, we might 59 02:51.160 --> 02:52.000 have to perform 60 02:52.000 --> 02:56.910 NAT traversal, and NAT traversal is going to require us to have that public IP 61 02:56.910 --> 02:57.680 address, 62 02:57.680 --> 03:00.840 which is one of the reasons why we're calling this out. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 62 02:57.680 --> 03:00.840 which is one of the reasons why we're calling this out. 63 03:00.840 --> 03:05.160 Ultimately, the orchestration plane device is indeed the VBond, so D would be 64 03:05.160 --> 03:05.840 the answer 65 03:05.840 --> 03:06.840 here. 66 03:06.840 --> 03:09.360 It's going to have to sit somewhere with a public IP address. 67 03:09.360 --> 03:12.920 We often do see them deployed into public clouds, and it's going to help our 68 03:12.920 --> 03:13.560 devices get 69 03:13.560 --> 03:17.760 onboarded and to be able to find one another. 70 03:17.760 --> 03:22.620 And last question here, which SD-WAN device uses programmatic interfaces for 71 03:22.620 --> 03:23.520 northbound, 72 03:23.520 --> 03:28.400 which is using rest, and southbound, which is using net-conf communication. 73 03:28.400 --> 03:32.850 So this gets into the fact that this is a software defined architecture, and as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 73 03:28.400 --> 03:32.850 So this gets into the fact that this is a software defined architecture, and as 74 03:32.850 --> 03:33.960 part of software 75 03:33.960 --> 03:37.440 defined architectures, we expect controllers to be involved. 76 03:37.440 --> 03:41.990 Well our controller is going to be part of the management plane, and as we said 77 03:41.990 --> 03:42.600 earlier, 78 03:42.600 --> 03:46.040 the name management, it's right there, it's our V-manage. 79 03:46.040 --> 03:50.670 The V-manage is how we as admins log in and perform configuration via the 80 03:50.670 --> 03:51.520 graphical 81 03:51.520 --> 03:57.510 user interface, but I can also use some kind of API access, whether that's 82 03:57.510 --> 03:58.880 using it manually 83 03:58.880 --> 04:02.550 myself, maybe writing some Python scripts, or having an automation software WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 83 03:58.880 --> 04:02.550 myself, maybe writing some Python scripts, or having an automation software 84 04:02.550 --> 04:03.160 package out 85 04:03.160 --> 04:04.880 there that does this for me. 86 04:04.880 --> 04:07.920 And so this is what we call the northbound side of things. 87 04:07.920 --> 04:12.230 And then the southbound side, we are pushing configuration out to the different 88 04:12.230 --> 04:12.760 devices 89 04:12.760 --> 04:16.040 out here, and this is going to use net-conf. 90 04:16.040 --> 04:20.600 This is an architecture that's pretty common in SD, or SD, I'll just say 91 04:20.600 --> 04:21.800 software defined 92 04:21.800 --> 04:27.210 networking infrastructures, whether that's SD-WAN or SD-Ns, but either way, we 93 04:27.210 --> 04:28.080 're often going 94 04:28.080 --> 04:34.110 to find that on the user side of things that we like to use rest for API access WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 94 04:28.080 --> 04:34.110 to find that on the user side of things that we like to use rest for API access 95 04:34.110 --> 04:34.960 , and net-conf 96 04:34.960 --> 04:38.390 was built specifically to control networking devices, so it's not at all 97 04:38.390 --> 04:39.120 uncommon to see 98 04:39.120 --> 04:43.800 our admins using rest in our network devices relying on net-conf. 99 04:43.800 --> 04:46.360 So this brings us to the end of this skill. 100 04:46.360 --> 04:49.850 If we've this quiz identified any areas of weakness, it's a great opportunity 101 04:49.850 --> 04:50.880 to go back 102 04:50.880 --> 04:54.830 and maybe watch parts of the video again, or maybe take the quiz questions 103 04:54.830 --> 04:55.440 again, just 104 04:55.440 --> 04:57.880 to make sure that we've got it all down before moving on. 105 04:57.880 --> 05:01.910 Either way, we're going to continue to dive into more details around how SD-WAN WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 105 04:57.880 --> 05:01.910 Either way, we're going to continue to dive into more details around how SD-WAN 106 05:01.910 --> 05:02.120 comes 107 05:02.120 --> 05:03.120 together. 108 05:03.120 --> 05:06.780 At a foundational level, again, we do need to understand these four different 109 05:06.780 --> 05:07.240 devices 110 05:07.240 --> 05:09.440 and the four different planes in which they operate. 111 05:09.440 --> 05:12.040 I hope there's been informative for you, and I'd like to thank you for viewing.