WEBVTT 1 00:00.210 --> 00:03.000 So let's do a quick recap of our topology. 2 00:03.000 --> 00:05.880 We currently have three gateways set up 3 00:05.880 --> 00:07.110 as part of our NSX, 4 00:07.110 --> 00:09.360 two tier ones and one tier zero. 5 00:09.360 --> 00:11.730 And those three logical gateways exist 6 00:11.730 --> 00:14.550 as distributed routers on each of our transport nodes. 7 00:14.550 --> 00:15.960 So any one of these devices 8 00:15.960 --> 00:18.600 could make logical routing decisions for traffic going, 9 00:18.600 --> 00:21.690 for example, from VM-1 here or to VM-4 here. 10 00:21.690 --> 00:23.490 And also, let me let you in on a little secret. 11 00:23.490 --> 00:26.070 Up to this point, I've been specifically focusing 12 00:26.070 --> 00:28.020 on the distributed router function 13 00:28.020 --> 00:31.350 for these virtual routers, for these gateways. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:28.020 --> 00:31.350 for these virtual routers, for these gateways. 14 00:31.350 --> 00:34.380 So with routing, whatever device sees the traffic first. 15 00:34.380 --> 00:36.690 For example, if it's traffic coming in from VM-1, 16 00:36.690 --> 00:39.300 it's gonna be ESXI host A, 17 00:39.300 --> 00:41.130 acting as a host transport node 18 00:41.130 --> 00:43.140 with a full compliment of the distributed routers 19 00:43.140 --> 00:44.790 who's gonna make all the routing decisions 20 00:44.790 --> 00:47.160 and then finally forward it off if it needs to, 21 00:47.160 --> 00:49.500 to another host or another transport node 22 00:49.500 --> 00:50.670 over the Geneve tunnel. 23 00:50.670 --> 00:53.280 And everything we've been demonstrating up to this point 24 00:53.280 --> 00:55.290 has been been using our Geneve tunnel 25 00:55.290 --> 00:57.000 between the host transport node A 26 00:57.000 --> 00:58.110 and the host transport node B, 27 00:58.110 --> 01:00.450 because those two ESXI hosts, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 27 00:58.110 --> 01:00.450 because those two ESXI hosts, 28 01:00.450 --> 01:02.880 they have all the routing information. 29 01:02.880 --> 01:05.970 They're also the only two hosts that are hosting any VMs. 30 01:05.970 --> 01:08.280 So up to this point, there hasn't been any reason 31 01:08.280 --> 01:11.310 for traffic to be tunneled up to our edge nodes, 32 01:11.310 --> 01:13.140 because the distributed router function 33 01:13.140 --> 01:15.180 on these two hosts where all the VMs exist, 34 01:15.180 --> 01:16.680 it can be done all logically 35 01:16.680 --> 01:19.080 here on the respective ESXI host. 36 01:19.080 --> 01:21.210 And for a routing decision, the transport node 37 01:21.210 --> 01:23.010 closest to the source of that traffic 38 01:23.010 --> 01:24.720 is gonna actually make the routing decision, 39 01:24.720 --> 01:26.880 and then forward it over the tunnel when needed 40 01:26.880 --> 01:28.620 to another transport node. 41 01:28.620 --> 01:30.210 And that's all due to the wonderful WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 41 01:28.620 --> 01:30.210 And that's all due to the wonderful 42 01:30.210 --> 01:31.350 distributed router function 43 01:31.350 --> 01:34.080 that's capable and available inside of NSX. 44 01:34.080 --> 01:35.550 So currently for our distributed router function, 45 01:35.550 --> 01:37.530 we have T-0, that's gateway zero, 46 01:37.530 --> 01:39.120 and we have a distributed router 47 01:39.120 --> 01:41.010 replicated everywhere that needs to be 48 01:41.010 --> 01:43.830 for gateway A, which is a tier one router. 49 01:43.830 --> 01:45.300 We also have a distributed router 50 01:45.300 --> 01:47.250 for gateway B over here on the right. 51 01:47.250 --> 01:49.300 So let's imagine we now want to add 52 01:50.243 --> 01:51.930 on top of this distributed routed environment 53 01:51.930 --> 01:53.640 some additional network services. 54 01:53.640 --> 01:55.230 For example, maybe we wanna implement 55 01:55.230 --> 01:57.060 network address translation right here 56 01:57.060 --> 01:58.440 on our T-0 gateway. 57 01:58.440 --> 02:00.750 So I'll list NAT, network address translation, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 57 01:58.440 --> 02:00.750 So I'll list NAT, network address translation, 58 02:00.750 --> 02:03.330 as a IP network service we may wanna add, 59 02:03.330 --> 02:05.580 or we may wanna set up a VPN, 60 02:05.580 --> 02:08.190 or we may need connectivity to the physical network. 61 02:08.190 --> 02:09.390 So for example, right here, 62 02:09.390 --> 02:12.810 maybe this is our physical network is a physical router. 63 02:12.810 --> 02:14.970 And what we wanna do is provide connectivity 64 02:14.970 --> 02:19.080 between our NSX logical layer three-routed environment here 65 02:19.080 --> 02:20.460 and the physical network. 66 02:20.460 --> 02:22.800 Whenever we do any of those functions, 67 02:22.800 --> 02:24.990 network address translation, VPN, 68 02:24.990 --> 02:26.280 or we provide connectivity 69 02:26.280 --> 02:29.310 between the NSX routed environment and the physical network, 70 02:29.310 --> 02:31.380 whenever we implement any of those features, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 70 02:29.310 --> 02:31.380 whenever we implement any of those features, 71 02:31.380 --> 02:34.500 that's going to also by default in the background, 72 02:34.500 --> 02:36.600 implement something called an SR, 73 02:36.600 --> 02:38.520 which is a services router. 74 02:38.520 --> 02:40.170 And it's only implemented where it's needed. 75 02:40.170 --> 02:41.880 So if we set up, for example, 76 02:41.880 --> 02:45.570 basic connectivity from this tier zero gateway 77 02:45.570 --> 02:47.130 out to the physical network. 78 02:47.130 --> 02:49.620 So for example, maybe this is network 10 dot 10, 79 02:49.620 --> 02:51.750 and this is 10 dot 20, 80 02:51.750 --> 02:53.340 and then here's our interlink segments, 81 02:53.340 --> 02:54.540 their auto IP addressed. 82 02:54.540 --> 02:55.920 And then out here on the physical network, 83 02:55.920 --> 02:59.700 maybe this is 192.168.1.0 84 02:59.700 --> 03:00.780 with a 24 bit mask, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 84 02:59.700 --> 03:00.780 with a 24 bit mask, 85 03:00.780 --> 03:02.280 maybe our default gateways is at dot one. 86 03:02.280 --> 03:04.767 And what we wanna do is have reachability 87 03:04.767 --> 03:07.861 and routability between 10.10, 10.20, 88 03:07.861 --> 03:10.080 and VMs there, as well as the physical network. 89 03:10.080 --> 03:12.450 And with the correct NAT and routing setup 90 03:12.450 --> 03:14.520 to points beyond, including the internet. 91 03:14.520 --> 03:16.860 So when we implement that functionality, that connectivity, 92 03:16.860 --> 03:18.270 between the logical network here 93 03:18.270 --> 03:19.710 and the physical network here, 94 03:19.710 --> 03:20.940 we're gonna immediately see here 95 03:20.940 --> 03:22.620 on tier zero on this gateway, 96 03:22.620 --> 03:25.470 an additional logical router called a services router 97 03:25.470 --> 03:27.000 that's providing that functionality. 98 03:27.000 --> 03:30.870 Think of the services router as a special purpose function WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 98 03:27.000 --> 03:30.870 Think of the services router as a special purpose function 99 03:30.870 --> 03:33.600 for things like connectivity to a physical network 100 03:33.600 --> 03:37.080 or for IP services like NAT or VPN. 101 03:37.080 --> 03:38.130 And we don't have to go in 102 03:38.130 --> 03:39.690 and specifically tell this gateway, 103 03:39.690 --> 03:42.540 hey, please inject or install this services router. 104 03:42.540 --> 03:46.110 All we do is specify the service that we want to implement, 105 03:46.110 --> 03:46.980 and in the background, 106 03:46.980 --> 03:49.230 it implements a services router for us. 107 03:49.230 --> 03:50.130 And here's the cool thing, 108 03:50.130 --> 03:51.870 as we implement our connectivity here, 109 03:51.870 --> 03:54.750 as we add that, I'm gonna show you before and after, 110 03:54.750 --> 03:57.030 how this services router component 111 03:57.030 --> 03:58.770 for whatever feature we're gonna implement, 112 03:58.770 --> 04:00.510 is automatically added. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 112 03:58.770 --> 04:00.510 is automatically added. 113 04:00.510 --> 04:02.880 So let me clean this up a little bit 114 04:02.880 --> 04:05.160 and let me just label this real quick again, 115 04:05.160 --> 04:08.790 as the physical network and also this as a physical router. 116 04:08.790 --> 04:10.470 And let me also share something really important 117 04:10.470 --> 04:13.440 about services routers, or SRs for short. 118 04:13.440 --> 04:15.780 Most of those functions are gonna be implemented 119 04:15.780 --> 04:17.580 by our edge nodes. 120 04:17.580 --> 04:19.080 And here's effectively what that means. 121 04:19.080 --> 04:22.170 In the past with just distributed routing functionality 122 04:22.170 --> 04:24.330 between these networks here 123 04:24.330 --> 04:26.940 and these VMs here with the east-west routing, 124 04:26.940 --> 04:28.710 these two ESXI hosts can make 125 04:28.710 --> 04:30.600 all the routing decisions they need, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 125 04:28.710 --> 04:30.600 all the routing decisions they need, 126 04:30.600 --> 04:31.890 and then forward when needed 127 04:31.890 --> 04:33.930 to the other host over the tunnel. 128 04:33.930 --> 04:36.090 So when we're implementing services 129 04:36.090 --> 04:39.090 that require a services router function to be implemented, 130 04:39.090 --> 04:41.040 most of the time, virtually all the time, 131 04:41.040 --> 04:43.530 those are gonna be implemented on our edge nodes. 132 04:43.530 --> 04:46.620 So for example, here on our host transport nodes, 133 04:46.620 --> 04:49.770 they can have a full complement of the distributed router. 134 04:49.770 --> 04:51.450 So they've got three distributed routers, 135 04:51.450 --> 04:53.370 one for tier zero gateway, 136 04:53.370 --> 04:56.160 tier one gateway A, and tier one gateway B, no problem. 137 04:56.160 --> 04:58.620 However, when it comes to the services router 138 04:58.620 --> 05:01.500 for the function of connectivity to the external network, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 138 04:58.620 --> 05:01.500 for the function of connectivity to the external network, 139 05:01.500 --> 05:04.140 that services router is only gonna be available 140 05:04.140 --> 05:06.390 and supported on our edge nodes. 141 05:06.390 --> 05:09.330 So I'm gonna put this services router function here in red. 142 05:09.330 --> 05:11.370 So I'm gonna go ahead and call it SR. 143 05:11.370 --> 05:13.020 And just to be clear over here, 144 05:13.020 --> 05:14.430 this is a distributed router function, 145 05:14.430 --> 05:17.340 distributed router function, distributed router function. 146 05:17.340 --> 05:19.860 And then over here for the access to the physical network, 147 05:19.860 --> 05:22.260 it's another logical function called the SR, 148 05:22.260 --> 05:23.850 which we would then have included 149 05:23.850 --> 05:25.680 or automatically would be included here 150 05:25.680 --> 05:27.390 as part of our tier zero gateway. 151 05:27.390 --> 05:29.340 So our edge nodes would also have a copy of that. 152 05:29.340 --> 05:32.010 I'll put that here in red as our services router. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 152 05:29.340 --> 05:32.010 I'll put that here in red as our services router. 153 05:32.010 --> 05:33.150 I'll put a little arrow there. 154 05:33.150 --> 05:34.980 However, our host transport nodes, 155 05:34.980 --> 05:37.470 they would not have or need a instance 156 05:37.470 --> 05:38.340 of that services router 157 05:38.340 --> 05:40.890 because they are not actually providing the connectivity 158 05:40.890 --> 05:42.480 to that outside physical network. 159 05:42.480 --> 05:43.313 That's only gonna be done 160 05:43.313 --> 05:45.000 by one of our edge transport nodes. 161 05:45.000 --> 05:46.350 So one of the questions would be, okay, 162 05:46.350 --> 05:48.120 so how do we tie all this together? 163 05:48.120 --> 05:50.220 For example, what if VM-1 here 164 05:50.220 --> 05:52.560 is trying to go out to the internet? 165 05:52.560 --> 05:55.530 So the host transport node that VM is running on 166 05:55.530 --> 05:57.390 is gonna do a lot of the routing decisions. 167 05:57.390 --> 06:00.090 But how do we then forward it or know when to forward it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 167 05:57.390 --> 06:00.090 But how do we then forward it or know when to forward it 168 06:00.090 --> 06:02.100 over to the services router function 169 06:02.100 --> 06:03.840 over on one of our edge devices? 170 06:03.840 --> 06:06.120 So we can actually do the forwarding of that traffic app 171 06:06.120 --> 06:08.070 to the physical network and points beyond. 172 06:08.070 --> 06:11.850 And the answer is, we are gonna use plain old routing. 173 06:11.850 --> 06:14.400 And let me explain how this works in this overview. 174 06:14.400 --> 06:17.820 Let's imagine that this router right here, gateway A, 175 06:17.820 --> 06:20.730 that its interface address right here is A, 176 06:20.730 --> 06:23.190 and then the interface address here is B. 177 06:23.190 --> 06:25.380 And then the interface IP address here 178 06:25.380 --> 06:28.710 on the distributed router for the T-0 router is C. 179 06:28.710 --> 06:30.210 And then we're also gonna draw this logical WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 179 06:28.710 --> 06:30.210 And then we're also gonna draw this logical 180 06:30.210 --> 06:31.590 back plane connection 181 06:31.590 --> 06:33.420 between the distributed router function 182 06:33.420 --> 06:36.960 on tier zero, gateway zero, and what will be installed, 183 06:36.960 --> 06:40.170 the services router function here also on T-0. 184 06:40.170 --> 06:42.150 So let's say that logical connection there 185 06:42.150 --> 06:44.640 is this interface has the IP address of D, 186 06:44.640 --> 06:48.150 and now the services router that has the IP address of E. 187 06:48.150 --> 06:50.130 We're also gonna have virtual network identifiers 188 06:50.130 --> 06:52.050 for each of these segments as well. 189 06:52.050 --> 06:54.480 So down here, let's go ahead for A, 190 06:54.480 --> 06:57.240 let's go ahead and use a VNI of one. 191 06:57.240 --> 06:58.980 So I'll put the VNIs here in pink, 192 06:58.980 --> 07:00.210 even though it's gonna be a longer number. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 192 06:58.980 --> 07:00.210 even though it's gonna be a longer number. 193 07:00.210 --> 07:02.910 It's just for reference, I'm gonna call this VNI one 194 07:02.910 --> 07:05.693 and VNI two and VNI three. 195 07:05.693 --> 07:09.150 And the services router function here on T--, gateway zero. 196 07:09.150 --> 07:10.320 That's providing the connectivity 197 07:10.320 --> 07:11.520 over to the physical network. 198 07:11.520 --> 07:13.770 So if we follow the logical process here 199 07:13.770 --> 07:15.600 with our VNI numbers here in pink 200 07:15.600 --> 07:18.930 and the IP next top addresses here in yellow, 201 07:18.930 --> 07:21.750 when VM one here wants to go out to the internet, 202 07:21.750 --> 07:24.060 the compute host here where VM one is running 203 07:24.060 --> 07:25.770 has the distributed router. 204 07:25.770 --> 07:26.970 So it knows all about gateway A. 205 07:26.970 --> 07:29.940 So it'll say, okay, the traffic from a routing perspective, 206 07:29.940 --> 07:31.980 it's gonna come in here on this interface. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 206 07:29.940 --> 07:31.980 it's gonna come in here on this interface. 207 07:31.980 --> 07:36.360 And the next top address is gonna be my tier zero DR. 208 07:36.360 --> 07:38.070 And that gateway address is C. 209 07:38.070 --> 07:40.320 And then from the logical perspective of routing, 210 07:40.320 --> 07:43.740 the next top after that from the tier zero DR 211 07:43.740 --> 07:46.260 is gonna be the tier zero SR. 212 07:46.260 --> 07:48.390 And that's the logical process or function 213 07:48.390 --> 07:50.670 that allows connectivity to that physical network. 214 07:50.670 --> 07:55.050 So effectively from the perspective of ESXI-A, 215 07:55.050 --> 07:57.990 the next top that we need to reach is E, 216 07:57.990 --> 08:01.590 which is on segment three, at which point ESXI-A says, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 216 07:57.990 --> 08:01.590 which is on segment three, at which point ESXI-A says, 217 08:01.590 --> 08:04.530 okay, I need to get to this IP address on segment three 218 08:04.530 --> 08:06.930 because ESXI-A has that logical router, 219 08:06.930 --> 08:08.280 tier zero, gateway zero. 220 08:08.280 --> 08:10.560 It knows exactly what that segment is, 221 08:10.560 --> 08:11.940 segment three in this case. 222 08:11.940 --> 08:13.830 And then ESXI-A is gonna say, okay, 223 08:13.830 --> 08:16.350 for this segment three where the next top is 224 08:16.350 --> 08:19.320 and the IP address of E, what is the layer two address? 225 08:19.320 --> 08:20.550 And this layer two address 226 08:20.550 --> 08:21.990 provided by the SR function 227 08:21.990 --> 08:25.260 is gonna be on one of our edge nodes, edge one or edge two. 228 08:25.260 --> 08:27.720 If we're doing active standby and edge one is active 229 08:27.720 --> 08:28.980 and edge two is standby, 230 08:28.980 --> 08:31.530 it'd be edge one supporting that address. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 230 08:28.980 --> 08:31.530 it'd be edge one supporting that address. 231 08:31.530 --> 08:33.150 So then this host transport node would say, 232 08:33.150 --> 08:35.790 oh, okay, to get to that next hop of E, 233 08:35.790 --> 08:37.020 I need to forward it over to the, 234 08:37.020 --> 08:39.810 let's say it's edge one that has that services router, 235 08:39.810 --> 08:40.980 and supporting that IP address 236 08:40.980 --> 08:42.600 and the corresponding layer two address. 237 08:42.600 --> 08:45.750 At that point, ESXI-A would send the traffic 238 08:45.750 --> 08:48.060 tunneled over to edge one. 239 08:48.060 --> 08:49.710 Again, that'd be the Geneve tunnel 240 08:49.710 --> 08:52.560 because ESXI-A had already made the routing decisions 241 08:52.560 --> 08:54.240 inside the Geneve header, it would indicate, 242 08:54.240 --> 08:55.800 oh, this is for segment three. 243 08:55.800 --> 08:57.840 And then edge one would de-encapsulate that. 244 08:57.840 --> 08:59.880 It would see that the traffic is destined 245 08:59.880 --> 09:01.290 for this layer two address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 245 08:59.880 --> 09:01.290 for this layer two address 246 09:01.290 --> 09:03.090 of this interface here, 247 09:03.090 --> 09:05.130 which that SR is running on edge one. 248 09:05.130 --> 09:07.320 So edge one would continue to process the traffic, 249 09:07.320 --> 09:09.480 and then edge one would make a routing decision. 250 09:09.480 --> 09:10.950 The egress interface would be here 251 09:10.950 --> 09:13.710 on this logical services router on our tier zero gateway, 252 09:13.710 --> 09:15.900 and then it could forward it over to the physical network. 253 09:15.900 --> 09:18.210 So as a summary, this ESXI host, 254 09:18.210 --> 09:21.630 which has all the information about the distributed router 255 09:21.630 --> 09:24.360 for the tier zero and the two tier ones, 256 09:24.360 --> 09:26.040 it can make all the routing decisions 257 09:26.040 --> 09:29.130 up to the next hop of the services router, 258 09:29.130 --> 09:30.570 at which point it does a lookup WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 258 09:29.130 --> 09:30.570 at which point it does a lookup 259 09:30.570 --> 09:32.100 and says, okay, for that segment 260 09:32.100 --> 09:33.270 and that layer three address, 261 09:33.270 --> 09:35.520 the corresponding layer two address is reachable 262 09:35.520 --> 09:36.510 over at edge one, 263 09:36.510 --> 09:38.370 it causes it to forward it to edge one, 264 09:38.370 --> 09:40.200 who then receives it and continues forwarding. 265 09:40.200 --> 09:43.080 And that's the logic about how in the world 266 09:43.080 --> 09:46.890 does NSX know how to or when to forward 267 09:46.890 --> 09:49.620 to a specific services router for some network service? 268 09:49.620 --> 09:51.390 In this case, it's access to the physical network. 269 09:51.390 --> 09:53.700 And the answer is routing tables. 270 09:53.700 --> 09:56.370 It's the routing tables on these distributed routers, 271 09:56.370 --> 09:58.050 they're gonna have a next hop 272 09:58.050 --> 09:59.910 of the services router IP address, 273 09:59.910 --> 10:02.040 and that's what causes our host transport nodes WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 273 09:59.910 --> 10:02.040 and that's what causes our host transport nodes 274 10:02.040 --> 10:04.740 to then forward the traffic to the appropriate edge, 275 10:04.740 --> 10:06.540 who's supporting an SR function, 276 10:06.540 --> 10:09.090 who can then continue processing the packet and the frame, 277 10:09.090 --> 10:10.230 make a routing decision 278 10:10.230 --> 10:12.060 and forward it on to its next hop. 279 10:12.060 --> 10:13.440 So let me clean that up a little bit 280 10:13.440 --> 10:15.090 and let's talk about one other concept. 281 10:15.090 --> 10:19.380 If we do want to take this gateway here, the tier zero, 282 10:19.380 --> 10:22.590 which currently is just a DR, a distributed router, 283 10:22.590 --> 10:25.800 and we want to add the functionality of connectivity 284 10:25.800 --> 10:27.390 to the physical network here 285 10:27.390 --> 10:30.630 on behalf of our clients and VMs inside of NSX, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 285 10:27.390 --> 10:30.630 on behalf of our clients and VMs inside of NSX, 286 10:30.630 --> 10:33.840 we need to create a new type of segment. 287 10:33.840 --> 10:36.600 So up to this point, we've been creating overlay segments, 288 10:36.600 --> 10:37.770 and what we're gonna do up here, 289 10:37.770 --> 10:38.670 we are going to create 290 10:38.670 --> 10:41.706 a new type of segment, VLAN backed segment. 291 10:41.706 --> 10:43.350 And all the VLAN backed segment says is, 292 10:43.350 --> 10:46.710 hey, this is a segment, a logical segment in NSX, 293 10:46.710 --> 10:49.350 but it's gonna refer to, for example, 294 10:49.350 --> 10:53.640 VLAN 10 or VLAN 20 or VLAN 30 on the physical network. 295 10:53.640 --> 10:55.530 And that way our services router, 296 10:55.530 --> 10:58.530 we can go ahead and logically connect it via that segment, 297 10:58.530 --> 10:59.820 that VLAN backed segment, 298 10:59.820 --> 11:02.790 to whatever the VLAN is right here on this network segment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 298 10:59.820 --> 11:02.790 to whatever the VLAN is right here on this network segment 299 11:02.790 --> 11:04.200 that we want connectivity to. 300 11:04.200 --> 11:07.620 So in preparation for implementing our connectivity here 301 11:07.620 --> 11:10.380 and adding the services router component here at tier zero 302 11:10.380 --> 11:12.270 for access to the physical network, 303 11:12.270 --> 11:16.530 I propose in the next video we put a very specific plan 304 11:16.530 --> 11:19.890 together and then you and I together will follow that plan. 305 11:19.890 --> 11:22.440 So I'll see you in the next video for exactly that.