WEBVTT 1 00:00.000 --> 00:09.040 So, let's begin our discussion with an introduction to Cisco's SD-WAN. 2 00:09.040 --> 00:14.820 Our aim in this video is going to be to discuss what is SD-WAN and what 3 00:14.820 --> 00:16.040 advantages does this 4 00:16.040 --> 00:19.440 bring to the current networking environment. 5 00:19.440 --> 00:23.370 After that, we'll talk about the various different components as an 6 00:23.370 --> 00:24.800 introduction to those 7 00:24.800 --> 00:26.440 components. 8 00:26.440 --> 00:30.190 The rest of this skill, of course, will be talking about each of those WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 8 00:26.440 --> 00:30.190 The rest of this skill, of course, will be talking about each of those 9 00:30.190 --> 00:32.440 components in more detail. 10 00:32.440 --> 00:37.160 So let's go ahead and jump in with our introduction. 11 00:37.160 --> 00:40.950 So of course, the first thing we want to ask when we start talking about a new 12 00:40.950 --> 00:41.880 topic is 13 00:41.880 --> 00:43.380 why. 14 00:43.380 --> 00:48.580 Why do we care about SD-WAN, what's good about it, and what does it add to what 15 00:48.580 --> 00:49.200 we already 16 00:49.200 --> 00:51.880 have in networking? 17 00:51.880 --> 00:57.280 Well, first off, it is a software-defined solution. 18 00:57.280 --> 01:02.650 What this basically means is that we're going to use a controller to control WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 18 00:57.280 --> 01:02.650 What this basically means is that we're going to use a controller to control 19 01:02.650 --> 01:03.840 our network. 20 01:03.840 --> 01:05.080 Why? 21 01:05.080 --> 01:06.640 Why is this important? 22 01:06.640 --> 01:14.440 Well, for one thing, it is definitely easier and it's more consistent as far as 23 01:14.440 --> 01:16.400 configuration. 24 01:16.400 --> 01:20.000 Now keep in mind as we go through this discussion. 25 01:20.000 --> 01:25.160 Control management isn't really something new in networking. 26 01:25.160 --> 01:30.730 What's really new here is that we make changes on a controller and those WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 26 01:25.160 --> 01:30.730 What's really new here is that we make changes on a controller and those 27 01:30.730 --> 01:32.680 changes automatically 28 01:32.680 --> 01:37.640 and uniformly get pushed out to all of the devices. 29 01:37.640 --> 01:43.240 That's what makes this easier, more efficient, and more accurate. 30 01:43.240 --> 01:48.620 It's basically removing the possibility of mistakes from the equation and 31 01:48.620 --> 01:50.040 making everything 32 01:50.040 --> 01:53.480 essentially a one-click operation. 33 01:53.480 --> 01:58.060 So specifically, some of the things that it will simplify, support for, is 34 01:58.060 --> 01:59.000 connecting to 35 01:59.000 --> 02:00.480 multi-cloud. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 35 01:59.000 --> 02:00.480 multi-cloud. 36 02:00.480 --> 02:06.070 It makes this much easier as well as connecting to things such as platform as a 37 02:06.070 --> 02:07.480 service or 38 02:07.480 --> 02:09.640 software as a service. 39 02:09.640 --> 02:15.040 All of these are going to be much easier with SD-WAN because they are built in 40 02:15.040 --> 02:15.840 wizards to 41 02:15.840 --> 02:19.160 help you set all of this stuff up. 42 02:19.160 --> 02:24.130 And in addition to just making cloud services easier, we can also simplify 43 02:24.130 --> 02:25.160 things such as 44 02:25.160 --> 02:26.160 our routing. 45 02:26.160 --> 02:30.000 Again, it's going to make it more consistent. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 46 02:30.000 --> 02:31.240 Better security. 47 02:31.240 --> 02:35.640 Again, mostly through that whole idea of consistency. 48 02:35.640 --> 02:40.400 There will be a consistent security policy on all of the devices. 49 02:40.400 --> 02:45.180 And we sort of did already mention it does this all, of course, through this 50 02:45.180 --> 02:45.760 simplified 51 02:45.760 --> 02:48.000 and centralized management. 52 02:48.000 --> 02:53.160 That is the main advantage to the whole software defined model. 53 02:53.160 --> 02:59.780 And overall, it simply optimizes the whole cloud experience with, again, built 54 02:59.780 --> 03:00.680 in wizards WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 54 02:59.780 --> 03:00.680 in wizards 55 03:00.680 --> 03:07.320 and such such as Cisco on-ramp to help simplify cloud configuration. 56 03:07.320 --> 03:11.320 So what are the moving parts that make all of this work? 57 03:11.320 --> 03:17.720 So the SD-WAN solution is made up of four major components. 58 03:17.720 --> 03:21.440 There are a few optional components as well that we'll discuss. 59 03:21.440 --> 03:24.520 However, there are four major components. 60 03:24.520 --> 03:29.360 The first of those four major components is V-Manage. 61 03:29.360 --> 03:36.080 V-Manage is what offers that central management to the environment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 61 03:29.360 --> 03:36.080 V-Manage is what offers that central management to the environment. 62 03:36.080 --> 03:41.290 It's essentially a web page that we go to to do all of our configuration, 63 03:41.290 --> 03:42.520 management, 64 03:42.520 --> 03:44.680 and monitoring. 65 03:44.680 --> 03:48.240 Next is the V-Smart controller. 66 03:48.240 --> 03:53.360 This again is the controller of this entire environment. 67 03:53.360 --> 03:59.520 The V-Manage controller is what tells the V-Smart controller what to do, but 68 03:59.520 --> 03:59.800 keep in 69 03:59.800 --> 04:04.200 mind it's the V-Smart controller that's actually doing it. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 69 03:59.800 --> 04:04.200 mind it's the V-Smart controller that's actually doing it. 70 04:04.200 --> 04:10.060 So yes, V-Manage provides the graphical interface for us administrators, but 71 04:10.060 --> 04:10.960 when it comes to 72 04:10.960 --> 04:16.160 actually implementing this, it's being done by V-Smart. 73 04:16.160 --> 04:19.760 The next component is V-Bond. 74 04:19.760 --> 04:27.160 This one orchestrates the connections between the controller and the edge. 75 04:27.160 --> 04:30.940 The edge is what we're going to be talking about next, but this is essentially WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 75 04:27.160 --> 04:30.940 The edge is what we're going to be talking about next, but this is essentially 76 04:30.940 --> 04:31.680 the connection 77 04:31.680 --> 04:34.960 manager for SD-WAN. 78 04:34.960 --> 04:38.920 And finally, we have the WAN-edge devices. 79 04:38.920 --> 04:44.680 These are the actual devices, either physical or virtual, that are actually 80 04:44.680 --> 04:45.840 sitting at each 81 04:45.840 --> 04:48.160 location's edge. 82 04:48.160 --> 04:52.160 So you would basically say this is the data plane. 83 04:52.160 --> 04:57.380 Everything above this has been either management plane or control plane. 84 04:57.380 --> 04:59.720 This is the actual data plane. 85 04:59.720 --> 05:04.750 These are the devices that are being controlled by the V-Smart controller and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 85 04:59.720 --> 05:04.750 These are the devices that are being controlled by the V-Smart controller and 86 05:04.750 --> 05:05.800 are therefore 87 05:05.800 --> 05:08.720 doing the actual packet forwarding. 88 05:08.720 --> 05:19.410 Now just so you're aware, starting with version 20.12 and iOSXE version 17.12, 89 05:19.410 --> 05:20.680 Cisco decided 90 05:20.680 --> 05:23.840 to rename this product line. 91 05:23.840 --> 05:25.640 So what did they change? 92 05:25.640 --> 05:33.080 Well first, the overall solution is now called the Cisco Catalyst SD-WAN WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 92 05:25.640 --> 05:33.080 Well first, the overall solution is now called the Cisco Catalyst SD-WAN 93 05:33.080 --> 05:34.480 solution. 94 05:34.480 --> 05:41.400 So they changed the overall name from just SD-WAN to Cisco Catalyst SD-WAN. 95 05:41.400 --> 05:44.640 Then each component also got renamed. 96 05:44.640 --> 05:51.920 V-Manage is now referred to as the Cisco Catalyst SD-WAN Manager. 97 05:51.920 --> 05:59.000 V-Smart now becomes the Cisco Catalyst SD-WAN controller. 98 05:59.000 --> 06:03.240 You might be getting a little bit of a trend on how these names are running. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 98 05:59.000 --> 06:03.240 You might be getting a little bit of a trend on how these names are running. 99 06:03.240 --> 06:08.880 They all tend to begin with the product name Cisco Catalyst SD-WAN. 100 06:08.880 --> 06:18.200 Next up is V-Bond, which is the big surprise Cisco Catalyst SD-WAN validator. 101 06:18.200 --> 06:23.500 And finally there's another component we haven't really discussed yet called V- 102 06:23.500 --> 06:24.080 Analytics. 103 06:24.080 --> 06:29.680 This is now the Cisco Catalyst SD-WAN analytics. 104 06:29.680 --> 06:33.480 This is for collecting and analyzing information about our network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 104 06:29.680 --> 06:33.480 This is for collecting and analyzing information about our network. 105 06:33.480 --> 06:38.280 We'll talk about this in more detail in an upcoming video. 106 06:38.280 --> 06:43.560 And one other thing I want to point out, as we go through this course, we will 107 06:43.560 --> 06:44.280 be using 108 06:44.280 --> 06:51.280 the original names just because Cisco, through the entirety of the ENCC 109 06:51.280 --> 06:53.080 generally refers 110 06:53.080 --> 06:59.590 to these products by their older names, the V-Manage, the V-Smart, the V-Bond, 111 06:59.590 --> 07:00.280 and the WAN WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 111 06:59.590 --> 07:00.280 and the WAN 112 07:00.280 --> 07:01.440 Edge. 113 07:01.440 --> 07:06.480 Just be aware of these new names, just in case they update the exam. 114 07:06.480 --> 07:09.800 Be aware that both of these names are technically valid. 115 07:09.800 --> 07:15.070 But again in a lot of places, Cisco is still using the original names, so just 116 07:15.070 --> 07:15.720 be aware 117 07:15.720 --> 07:18.040 of this change. 118 07:18.040 --> 07:22.480 So in this video, we just jumped in with a quick introduction, hopefully 119 07:22.480 --> 07:23.320 answered that 120 07:23.320 --> 07:29.040 question, why SD-WAN, why do we care, what does it bring to the table. 121 07:29.040 --> 07:34.010 And we talked about the four major components that we have with SD-WAN, as well WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 121 07:29.040 --> 07:34.010 And we talked about the four major components that we have with SD-WAN, as well 122 07:34.010 --> 07:35.240 as the fact 123 07:35.240 --> 07:39.920 that the product names have changed a bit here in the newest versions of code. 124 07:39.920 --> 07:43.920 Next, let's take a closer look at that V-Manage server.