WEBVTT 1 00:00.000 --> 00:06.000 Cisco's SD-WAN architecture is built on four planes of operation. 2 00:06.000 --> 00:09.520 We'll first learn about networking. We're typically introduced to the control 3 00:09.520 --> 00:11.000 and data plane, 4 00:11.000 --> 00:15.000 and that has expanded over time, and with SD-WAN, we're actually going to find 5 00:15.000 --> 00:16.000 we have four of these. 6 00:16.000 --> 00:21.000 And yes, it does start with the data plane and the control plane. 7 00:21.000 --> 00:25.000 But from there, we're going to find that we have a management plane. 8 00:25.000 --> 00:30.000 And here's what's interesting. We have also an orchestration plane. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 9 00:30.000 --> 00:35.330 This is perhaps the unique element of SD-WAN as it relates to our local area 10 00:35.330 --> 00:36.000 networks, 11 00:36.000 --> 00:41.000 because data control and management plane operations are pretty commonly cited. 12 00:41.000 --> 00:46.000 So what is orchestration? And for that matter, how does the SD-WAN architecture 13 00:46.000 --> 00:49.000 fit into all of these different planes? 14 00:49.000 --> 00:54.490 And what we're going to find is we have a single device that maps into each one 15 00:54.490 --> 00:56.000 of these planes. 16 00:56.000 --> 01:00.250 So we have a device at the data plane, a device at the control plane, a device WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 16 00:56.000 --> 01:00.250 So we have a device at the data plane, a device at the control plane, a device 17 01:00.250 --> 01:01.000 at the management plane, 18 01:01.000 --> 01:04.000 and a device at the orchestration plane. 19 01:04.000 --> 01:07.360 And so what we want to do here is go through the different devices as it 20 01:07.360 --> 01:11.000 relates to the individual plane of operation. 21 01:11.000 --> 01:14.000 So let's go ahead and start with the data plane. 22 01:14.000 --> 01:20.150 And at the data plane, the device in question is going to be known as a WAN 23 01:20.150 --> 01:21.000 edge. 24 01:21.000 --> 01:25.000 Now this device has seen a bunch of name changes over time. 25 01:25.000 --> 01:29.610 And a little bit is, this is a history lesson, because Cisco originally tried 26 01:29.610 --> 01:33.000 to develop their own software defined wide area networking solution. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 26 01:29.610 --> 01:33.000 to develop their own software defined wide area networking solution. 27 01:33.000 --> 01:36.000 They called it iWAN, an intelligent WAN. 28 01:36.000 --> 01:40.000 And it was essentially built on all of the traditional networking mechanisms, 29 01:40.000 --> 01:45.250 but it didn't really deliver on what you expect out of a software defined 30 01:45.250 --> 01:46.000 solution. 31 01:46.000 --> 01:50.720 We didn't have a controller that really did a lot of things for us in a very 32 01:50.720 --> 01:52.000 intuitive way. 33 01:52.000 --> 01:55.790 And so Cisco eventually recognized, "Okay, maybe we didn't build this correctly 34 01:55.790 --> 01:56.000 . 35 01:56.000 --> 01:59.790 We should go out and we should find a solution that was built correctly and 36 01:59.790 --> 02:01.000 made that our own." WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 01:59.790 --> 02:01.000 made that our own." 37 02:01.000 --> 02:04.920 Which is something that not only Cisco does, but plenty of other technology 38 02:04.920 --> 02:06.000 companies do. 39 02:06.000 --> 02:10.000 And so they acquired a company called Viptela. 40 02:10.000 --> 02:15.810 And this Viptela, because it starts with a V, they named a lot of their devices 41 02:15.810 --> 02:17.000 starting with a V. 42 02:17.000 --> 02:22.670 And so when they acquired Viptela, Viptela had a hardware solution that was 43 02:22.670 --> 02:25.000 their version of a WAN router. 44 02:25.000 --> 02:28.360 Because a wide area network is typically built on routers, not layer three 45 02:28.360 --> 02:29.000 switches. 46 02:29.000 --> 02:31.000 There's a lot of reasons for that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 46 02:29.000 --> 02:31.000 There's a lot of reasons for that. 47 02:31.000 --> 02:36.070 But the main reason is because, well, there's a few key reasons. First of all, 48 02:36.070 --> 02:39.000 WAN types might require T1 cards. 49 02:39.000 --> 02:42.000 Well, switches can't do T1. They can only do Ethernet. 50 02:42.000 --> 02:45.410 And there's lots of other different types of WAN circuits that only routers can 51 02:45.410 --> 02:46.000 support. 52 02:46.000 --> 02:49.000 The other aspect is quality of service matters greatly. 53 02:49.000 --> 02:52.000 And other software-driven components. 54 02:52.000 --> 02:55.950 And so that's why a software-driven platform, like a router, is usually the 55 02:55.950 --> 02:57.000 correct way to go 56 02:57.000 --> 03:01.340 versus a hardware-driven platform, like a switch. So a little bit of background WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 02:57.000 --> 03:01.340 versus a hardware-driven platform, like a switch. So a little bit of background 57 03:01.340 --> 03:04.000 information in all of this. 58 03:04.000 --> 03:08.340 But ultimately, what I'm driving at here is that this WAN edge device used to 59 03:08.340 --> 03:11.000 be referred to as a V edge. 60 03:11.000 --> 03:14.000 That little V in front doesn't stand for virtual. 61 03:14.000 --> 03:17.000 Sometimes we see that in the IT world. 62 03:17.000 --> 03:20.000 Instead, it actually is a reference to Viptela themselves. 63 03:20.000 --> 03:27.000 So when Cisco acquired Viptela, they had a hardware solution known as a V edge. 64 03:27.000 --> 03:31.010 Now, as you can imagine, Cisco being a company that literally started by WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 64 03:27.000 --> 03:31.010 Now, as you can imagine, Cisco being a company that literally started by 65 03:31.010 --> 03:35.000 building routers probably didn't want to rely on V edges for very long. 66 03:35.000 --> 03:41.000 Because they wanted to probably develop their own version of a WAN edge router. 67 03:41.000 --> 03:47.000 And so they took their ISRs and they turned them into what they called C edges. 68 03:47.000 --> 03:51.000 As part of this architecture, where the little C there stands for Cisco. 69 03:51.000 --> 03:56.000 Well, at this point in the architecture, Cisco has done away with the V edge 70 03:56.000 --> 03:58.000 and the C edge nomenclature. 71 03:58.000 --> 04:02.000 And instead, we just refer to these as WAN edge devices. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 71 03:58.000 --> 04:02.000 And instead, we just refer to these as WAN edge devices. 72 04:02.000 --> 04:05.000 So what exactly is a WAN edge device? 73 04:05.000 --> 04:08.550 Well, believe it or not, it's still either an ISR and integrated services 74 04:08.550 --> 04:14.000 router or likely in the modern network a catalyst 8000. 75 04:14.000 --> 04:19.000 If you look at Cisco's line of routers, this catalyst 8000 series pops up. 76 04:19.000 --> 04:20.000 And I always find it funny. 77 04:20.000 --> 04:24.000 Cisco doesn't call the catalyst 8000 a router. 78 04:24.000 --> 04:28.000 If you go on look at their website, they call it an edge platform. 79 04:28.000 --> 04:31.000 Because, well, I can't say because why. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 79 04:28.000 --> 04:31.000 Because, well, I can't say because why. 80 04:31.000 --> 04:33.000 I'm not on the Cisco marketing team. 81 04:33.000 --> 04:34.000 But it is kind of interesting. 82 04:34.000 --> 04:37.990 And so, especially when we look at this series of what I will call routers 83 04:37.990 --> 04:40.000 because it really is their function. 84 04:40.000 --> 04:44.000 And we refer to this as an edge platform. 85 04:44.000 --> 04:47.000 Well, this word edge is seen up here. 86 04:47.000 --> 04:50.000 And for that matter, down in the old names as well. 87 04:50.000 --> 04:53.370 We're calling it an edge because it sits at the edge of our network and it 88 04:53.370 --> 04:56.000 interfaces with the wide area network. 89 04:56.000 --> 05:00.000 So what we can expect here is I'm going to have my router. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 90 05:00.000 --> 05:03.440 And that router is going to connect to probably some kind of layer 3 switch at 91 05:03.440 --> 05:04.000 a site. 92 05:04.000 --> 05:05.000 This might be a large site. 93 05:05.000 --> 05:09.000 So this could be a distribution switch. This could be a very small site. 94 05:09.000 --> 05:13.000 So it could be a completely collapsed type of device. 95 05:13.000 --> 05:17.000 And it's going to connect into my edge device. 96 05:17.000 --> 05:21.000 And in the SD-WAN world, this would be a WAN edge. 97 05:21.000 --> 05:24.680 And then from here, we're expecting to communicate out and connect two 98 05:24.680 --> 05:26.000 different circuits. 99 05:26.000 --> 05:31.000 And yeah, this could be a T1 or something along those lines, a T1 E1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 99 05:26.000 --> 05:31.000 And yeah, this could be a T1 or something along those lines, a T1 E1. 100 05:31.000 --> 05:35.340 But in the modern network, we're expecting to probably see a little bit more MP 101 05:35.340 --> 05:36.000 LS here. 102 05:36.000 --> 05:39.000 Potentially some VPNs over the internet. 103 05:39.000 --> 05:43.610 And part of the value of SD-WAN is we can get the same experience regardless of 104 05:43.610 --> 05:45.000 what these circuit types are. 105 05:45.000 --> 05:49.500 It doesn't matter if it's two internet circuits or two MPLS or whatever it is 106 05:49.500 --> 05:50.000 that we have. 107 05:50.000 --> 05:53.000 We could truly have T1s and E1s in here. 108 05:53.000 --> 05:56.000 And the SD-WAN experience remains the same. 109 05:56.000 --> 06:00.000 Of note at this point, we're going to introduce a little bit of terminology. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 110 06:00.000 --> 06:04.000 We divide this router, as I just did in the diagram. 111 06:04.000 --> 06:08.000 We're going to find that we have a transport side, 112 06:08.000 --> 06:14.000 referring to WAN, or WAN circuits, as transports. 113 06:14.000 --> 06:19.000 And then we're going to have the service side over here on the left. 114 06:19.000 --> 06:24.000 As in, this is the network or these are the networks that we are servicing. 115 06:24.000 --> 06:26.000 So this would be the local area network side. 116 06:26.000 --> 06:28.000 This would be the wide area network side. 117 06:28.000 --> 06:31.000 There's a little bit of a tidbit there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 117 06:28.000 --> 06:31.000 There's a little bit of a tidbit there. 118 06:31.000 --> 06:37.000 And as we've said, the WAN edge device is responsible for forming IPsec tunnels 119 06:37.000 --> 06:40.000 that are going to go out these different circuits. 120 06:40.000 --> 06:45.040 So they're going to be capable of creating these IPsec tunnels to create our 121 06:45.040 --> 06:46.000 overlay. 122 06:46.000 --> 06:48.000 So that is the data plane. 123 06:48.000 --> 06:52.180 And at this point, we're going to be focusing in on the device that is known as 124 06:52.180 --> 06:53.000 the WAN edge, 125 06:53.000 --> 06:57.000 being the representative for that plane of operation. 126 06:57.000 --> 07:00.000 But as you can imagine, for this device to be operating, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 127 07:00.000 --> 07:02.000 it's going to need a lot of help. 128 07:02.000 --> 07:06.000 It's got to receive information, it's got to receive routing information, 129 07:06.000 --> 07:10.000 management information, configuration information, for that matter. 130 07:10.000 --> 07:12.000 It just needs to get onboarded. 131 07:12.000 --> 07:17.290 And that is the responsibility of the rest of these four planes is to help the 132 07:17.290 --> 07:18.000 WAN edge device 133 07:18.000 --> 07:21.000 to be able to perform and do what it needs to do, 134 07:21.000 --> 07:25.580 and ultimately take our service traffic and send it out into the transport side 135 07:25.580 --> 07:26.000 of things. 136 07:26.000 --> 07:31.000 So as we go through these, we can start with the control plane WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 136 07:26.000 --> 07:31.000 So as we go through these, we can start with the control plane 137 07:31.000 --> 07:35.940 and the device responsible for helping us with the control plane is known as 138 07:35.940 --> 07:37.000 the V-Smart. 139 07:37.000 --> 07:41.500 And yes, for the rest of these, we are going to see that Cisco has yet to reb 140 07:41.500 --> 07:43.000 rand that little V. 141 07:43.000 --> 07:47.000 So nice little nod to the VipTella acquisition here. 142 07:47.000 --> 07:51.000 But just keep that in mind for all I know, Cisco is going to rebrand these. 143 07:51.000 --> 07:54.000 At some point, just like they did with the V-Edges and the C-Edges. 144 07:54.000 --> 07:57.000 But for now, they're still calling it the V-Smart. 145 07:57.000 --> 08:00.000 So what is it responsible for? WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 146 08:00.000 --> 08:03.000 Well, it's responsible for control plane operations. 147 08:03.000 --> 08:05.000 And when we think about control plane operations, 148 08:05.000 --> 08:10.320 a lot of times what we're going to see thinking about is some form of route 149 08:10.320 --> 08:12.000 distribution. 150 08:12.000 --> 08:19.000 And not just route distribution, but potentially policy distribution as well. 151 08:19.000 --> 08:24.560 In other words, as far as the WAN Edge device is making decisions about what 152 08:24.560 --> 08:25.000 traffic to send out, 153 08:25.000 --> 08:29.400 which one of these links, that's going to have to be dictated at the control 154 08:29.400 --> 08:30.000 plane WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 155 08:30.000 --> 08:33.000 and the V-Smart is responsible for it. 156 08:33.000 --> 08:36.000 The V-Smart is going to be a device that sits out on the network. 157 08:36.000 --> 08:39.000 And then we build out our SD-WAN. 158 08:39.000 --> 08:41.000 So we've got a bunch of Edge devices out here. 159 08:41.000 --> 08:46.000 We've got a bunch of IP-Sect tunnels, potentially full mesh, potentially not. 160 08:46.000 --> 08:52.750 And this V-Smart over here is going to be responsible for not only receiving 161 08:52.750 --> 08:54.000 information 162 08:54.000 --> 08:58.000 from all of these different devices, all of these WAN edges, 163 08:58.000 --> 09:04.000 but then we're going to push our control plane information back down. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 163 08:58.000 --> 09:04.000 but then we're going to push our control plane information back down. 164 09:04.000 --> 09:09.180 And one of the key facets to this is going to be a protocol known as the Over 165 09:09.180 --> 09:15.000 lay Management Protocol or OMP. 166 09:15.000 --> 09:21.000 OMP is going to be a brand new protocol for most of us, 167 09:21.000 --> 09:25.460 anyone who really hasn't studied SD-WAN because this is a protocol that was 168 09:25.460 --> 09:27.000 developed just for this. 169 09:27.000 --> 09:32.010 And we'll find if we were to drill into the details of OMP, which is beyond the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 169 09:27.000 --> 09:32.010 And we'll find if we were to drill into the details of OMP, which is beyond the 170 09:32.010 --> 09:33.000 scope of this course, 171 09:33.000 --> 09:38.000 but when we're taking a look at what exactly it is, it's very BGP-like. 172 09:38.000 --> 09:41.000 It operates very similarly to BGP. 173 09:41.000 --> 09:45.000 It's going to receive information again about networks. 174 09:45.000 --> 09:47.000 So it's aware of what's out there. 175 09:47.000 --> 09:50.580 It's going to make routing decisions, but the routing decisions and what routes 176 09:50.580 --> 09:52.000 to install, 177 09:52.000 --> 09:57.000 those decisions are not made by the WAN edge device itself or themselves. 178 09:57.000 --> 10:02.000 It's going to be a responsibility of the V-Smart. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 178 09:57.000 --> 10:02.000 It's going to be a responsibility of the V-Smart. 179 10:02.000 --> 10:04.000 So that is the control plane. 180 10:04.000 --> 10:08.000 Now next up, we have these two other planes to talk about. 181 10:08.000 --> 10:14.000 And we'll go to the, I guess we'll say the management plane here, management. 182 10:14.000 --> 10:16.000 And this one's pretty straightforward. 183 10:16.000 --> 10:20.000 It's going to be called the V-manage. 184 10:20.000 --> 10:26.260 The name is right there in the, as far as relating back the device to the plane 185 10:26.260 --> 10:27.000 of operation. 186 10:27.000 --> 10:33.000 So the V-manage is responsible for all of our admin management. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 186 10:27.000 --> 10:33.000 So the V-manage is responsible for all of our admin management. 187 10:33.000 --> 10:37.230 So we are going to be very familiar with the V-manage because this is going to 188 10:37.230 --> 10:40.000 be a device that also sits out here 189 10:40.000 --> 10:45.380 and has, you know, sends information around and receives information, all of 190 10:45.380 --> 10:46.000 these things. 191 10:46.000 --> 10:51.000 But ultimately, you and me as the admins of the SD-WAN environment, 192 10:51.000 --> 10:56.000 we're going to log into V-manage and define all of the policies that we desire. 193 10:56.000 --> 11:01.000 We also have the ability to perform API configuration this way. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 193 10:56.000 --> 11:01.000 We also have the ability to perform API configuration this way. 194 11:01.000 --> 11:06.780 So we could use restful APIs in order to send the information to V-manage that 195 11:06.780 --> 11:07.000 way. 196 11:07.000 --> 11:09.000 That allows for programmatic access. 197 11:09.000 --> 11:15.000 And then V-manage on the other side of things is going to use NetConf. 198 11:15.000 --> 11:20.160 Here, it's going to use NetConf to push that information out to the other 199 11:20.160 --> 11:23.000 devices, especially the V-Smarts and the, 200 11:23.000 --> 11:27.090 well, I was going to say the V-Edges, but the edges themselves, as well as the 201 11:27.090 --> 11:28.000 last device. 202 11:28.000 --> 11:32.560 Now this runs as a virtual machine, so funny enough, V-M, which stood for V-man WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 202 11:28.000 --> 11:32.560 Now this runs as a virtual machine, so funny enough, V-M, which stood for V-man 203 11:32.560 --> 11:34.000 age a moment ago, is, 204 11:34.000 --> 11:37.670 I'm not going to write V-M here as a virtual machine, but we're probably going 205 11:37.670 --> 11:42.290 to run this either in a cloud environment or in our hypervisor of choice that's 206 11:42.290 --> 11:44.000 running inside of our own data center. 207 11:44.000 --> 11:48.020 Now lastly, but not least, they've come to the probably the more interesting 208 11:48.020 --> 11:51.000 one of the bunch, which is this orchestration plane. 209 11:51.000 --> 11:57.000 And at the orchestration plane, we have a device known as the V-Bond. 210 11:57.000 --> 12:00.000 The name V-Bond is very intentionally chosen. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 211 12:00.000 --> 12:05.610 We've got a lot of relationships in here, and among all of these devices that 212 12:05.610 --> 12:08.000 are all trying to communicate with one another. 213 12:08.000 --> 12:13.000 And how do we glue those connections together? How do we bond them together? 214 12:13.000 --> 12:17.580 Well, that is the responsibility of the orchestration plane, and specifically 215 12:17.580 --> 12:19.000 of the V-Bond device. 216 12:19.000 --> 12:26.000 It is responsible primarily for the onboarding of our devices. 217 12:26.000 --> 12:33.490 Which is kind of interesting, because what we find is that the V-Bond is going WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 217 12:26.000 --> 12:33.490 Which is kind of interesting, because what we find is that the V-Bond is going 218 12:33.490 --> 12:37.000 to sit out here, usually in a public cloud space. 219 12:37.000 --> 12:42.000 And the reason for that is because it must have a public IP address. 220 12:42.000 --> 12:46.960 It needs a public IP address because a lot of our WAN devices might be hidden 221 12:46.960 --> 12:48.000 behind NAT. 222 12:48.000 --> 12:53.720 And in order to help these two routers to form a relationship with one another, 223 12:53.720 --> 12:59.000 depending on the situation, we might need to perform NAT traversal. 224 12:59.000 --> 13:05.230 And NAT traversal is going to require a device that both of these devices can WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 224 12:59.000 --> 13:05.230 And NAT traversal is going to require a device that both of these devices can 225 13:05.230 --> 13:09.000 reach, which ideally is anything with a public IP address. 226 13:09.000 --> 13:14.490 And so the V-Bond is going to allow devices to come online and reach out and 227 13:14.490 --> 13:19.350 find the V-Bond. The V-Bond will then connect all of these other devices 228 13:19.350 --> 13:24.950 together to say, "Okay, as this WAN edge device comes online, here's your V-S 229 13:24.950 --> 13:27.000 mart, here's your V-Manage. 230 13:27.000 --> 13:32.000 And from there we can continue to connect all of the devices together. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 230 13:27.000 --> 13:32.000 And from there we can continue to connect all of the devices together. 231 13:32.000 --> 13:38.160 And so it's going to send a list as part of that process. It's going to send a 232 13:38.160 --> 13:43.000 list of all the V-Manage and the V-Smart IP addresses to the WAN edge device. 233 13:43.000 --> 13:47.840 And again, usually we're going to find that the public cloud is a good place to 234 13:47.840 --> 13:52.410 run the V-Bond, although we can run it in-house if we want to, as long as we 235 13:52.410 --> 13:54.000 have it set up with the public IP address. 236 13:54.000 --> 13:59.320 So as we zoom out and look at all of these devices, what we're going to find is 237 13:59.320 --> 14:04.000 that we're going to have many of our WAN edge devices out there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 237 13:59.320 --> 14:04.000 that we're going to have many of our WAN edge devices out there. 238 14:04.000 --> 14:10.060 We're going to have usually a primary or like an active and a standby V-Manage 239 14:10.060 --> 14:13.000 in case it goes down. Again, it's operating in a virtual machine. 240 14:13.000 --> 14:17.230 So we'll just have a spare running there. We'll do something similar with the V 241 14:17.230 --> 14:21.480 -Bond. But with the V-Smarts, we're going to find that we probably are going to 242 14:21.480 --> 14:23.000 run a lot of V-Smarts. 243 14:23.000 --> 14:28.420 Typically we're going to want to scale out by having lots of these and 244 14:28.420 --> 14:33.470 depending on where they live, how many we want to do, maybe on a per circuit WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 244 14:28.420 --> 14:33.470 depending on where they live, how many we want to do, maybe on a per circuit 245 14:33.470 --> 14:35.000 basis, that kind of situation. 246 14:35.000 --> 14:40.300 And that's all part of SD-WAN architecture and design. But understand that this 247 14:40.300 --> 14:44.540 isn't just a single V-Smart out there. In the same way it's not a single V-Edge 248 14:44.540 --> 14:45.000 out there. 249 14:45.000 --> 14:48.090 We've got a lot of devices that are going to come together and it all starts 250 14:48.090 --> 14:51.960 with understanding the four different planes of operation, as well as the 251 14:51.960 --> 14:54.000 devices that operate within that plane. 252 14:54.000 --> 14:56.220 playing.