WEBVTT 1 00:00.150 --> 00:02.250 So now that we have a couple of edge nodes 2 00:02.250 --> 00:03.960 that are both deployed, they're running 3 00:03.960 --> 00:05.880 and they're set up as a cluster. 4 00:05.880 --> 00:09.084 Let's talk just for a moment at a high level about when 5 00:09.084 --> 00:12.180 those edge nodes would actually be used. 6 00:12.180 --> 00:15.480 So let's imagine within NSX, we wanna set up some routing. 7 00:15.480 --> 00:16.650 So we wanna do some routing. 8 00:16.650 --> 00:18.450 We'll put a little R there for router. 9 00:18.450 --> 00:19.620 And let's imagine we wanna route 10 00:19.620 --> 00:22.320 between segment 10, which is right here. 11 00:22.320 --> 00:23.580 I'll put that in yellow 12 00:23.580 --> 00:26.550 and segment 20, we'll put that right here in pink. 13 00:26.550 --> 00:29.130 Let's also imagine we have a few VMs that are running 14 00:29.130 --> 00:30.570 and connected to those segments WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 14 00:29.130 --> 00:30.570 and connected to those segments 15 00:30.570 --> 00:32.430 and we wanna be able to do routing between those two. 16 00:32.430 --> 00:36.180 Now we're gonna have a separate whole skill on routing 17 00:36.180 --> 00:37.860 and setting up routing services. 18 00:37.860 --> 00:40.140 However, for right now I just wanna give you a big insight 19 00:40.140 --> 00:44.670 as to when an edge transport node is needed or not needed. 20 00:44.670 --> 00:46.980 So if we have ESXI-A and ESXI-B, 21 00:46.980 --> 00:48.660 and they both have access to segment 10 22 00:48.660 --> 00:51.330 and they both have access to segment 20, lemme go ahead 23 00:51.330 --> 00:52.680 and put a couple VMs there, 24 00:52.680 --> 00:56.940 A couple here running on ESXI-A couple here on ESXI-B. 25 00:56.940 --> 00:59.040 And let's also connect into the respective segment. 26 00:59.040 --> 01:01.770 So this one on the left will connect to segment 10, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 26 00:59.040 --> 01:01.770 So this one on the left will connect to segment 10, 27 01:01.770 --> 01:03.570 and the one here on the right will connect 28 01:03.570 --> 01:05.760 to segment 20, just like that. 29 01:05.760 --> 01:08.040 Fantastic. Then over here I need a ESXI-B. 30 01:08.040 --> 01:11.460 For this VM we'll connect it to segment 10. 31 01:11.460 --> 01:12.660 And for the VM here on the right, 32 01:12.660 --> 01:13.980 we'll connect to segment 20. 33 01:13.980 --> 01:15.900 So if we're gonna set up logical routing 34 01:15.900 --> 01:20.190 between these two segments, ESXI-A has the ability to do 35 01:20.190 --> 01:22.800 that routing for VMs on either segment 36 01:22.800 --> 01:24.660 because it's connected to both of them. 37 01:24.660 --> 01:27.660 And we can have our routing function here on ESXI-A 38 01:27.660 --> 01:29.250 that can logically do that routing. 39 01:29.250 --> 01:32.070 And that router could also be located here on ESXI-B, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 39 01:29.250 --> 01:32.070 And that router could also be located here on ESXI-B, 40 01:32.070 --> 01:35.220 and it could do the logical routing between these two VMs. 41 01:35.220 --> 01:37.560 And in the event that VM number one here needs 42 01:37.560 --> 01:39.360 to communicate with VM number four, 43 01:39.360 --> 01:43.260 so VM one's on the segment 10 on the 10.10. 0 network 44 01:43.260 --> 01:46.290 and VM four is over here on ESXI-B on 45 01:46.290 --> 01:47.400 the segment 20 network. 46 01:47.400 --> 01:50.130 And it has an IP address in the 10.20.0 subnet range. 47 01:50.130 --> 01:51.960 If they wanted to communicate with each other, let's imagine 48 01:51.960 --> 01:54.510 that this VM right here wants to communicate with 49 01:54.510 --> 01:58.140 that VM over there based on their IP addressing, this ESXI 50 01:58.140 --> 02:00.780 host could go ahead and take that incoming packet, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 50 01:58.140 --> 02:00.780 host could go ahead and take that incoming packet, 51 02:00.780 --> 02:02.040 make a routing decision 52 02:02.040 --> 02:05.280 because it has a copy effectively of that distributed router 53 02:05.280 --> 02:06.870 as a function of NSX. 54 02:06.870 --> 02:09.090 And then after making a routing decision, can also identify 55 02:09.090 --> 02:11.190 that, hey, that destination layer to address 56 02:11.190 --> 02:13.290 for this VM is not reachable locally, 57 02:13.290 --> 02:16.950 but it's reachable over the tunnel over here to ESXI-B. 58 02:16.950 --> 02:19.680 So after having made the routing decision in its mind, 59 02:19.680 --> 02:21.480 if you will, with this distributed router, 60 02:21.480 --> 02:23.550 it would then encapsulate the traffic, forward it 61 02:23.550 --> 02:26.370 through the tunnel, ESXI-B would de-encapsulate it 62 02:26.370 --> 02:28.860 and then forward on to the final destination here, VM 4. 63 02:28.860 --> 02:31.230 So even though we're gonna have a whole separate skill WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 63 02:28.860 --> 02:31.230 So even though we're gonna have a whole separate skill 64 02:31.230 --> 02:33.600 and details, we're regard setting up these routers 65 02:33.600 --> 02:36.510 and doing routing inside of NSX, I wanted to point out 66 02:36.510 --> 02:39.390 that these ESXI host on their own ESXI-A 67 02:39.390 --> 02:41.070 and B with this topology right here. 68 02:41.070 --> 02:44.550 They can do all the routing on their own without ever having 69 02:44.550 --> 02:46.230 to call upon the services of one 70 02:46.230 --> 02:47.790 of these edge transport nodes 71 02:47.790 --> 02:51.000 because each of these ESXI nodes can do all the routing 72 02:51.000 --> 02:53.760 between these two subnets and they can send the traffic back 73 02:53.760 --> 02:55.399 and forth between ESXI-A 74 02:55.399 --> 02:57.060 and ESXI-B over the tunnel. 75 02:57.060 --> 02:58.650 So at this point, with that distributed 76 02:58.650 --> 03:00.620 router function existing on both WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 76 02:58.650 --> 03:00.620 router function existing on both 77 03:00.620 --> 03:03.045 of our host transport nodes, we really don't 78 03:03.045 --> 03:05.493 yet have any need for these edge VMs 79 03:05.493 --> 03:07.530 as edge transport nodes. 80 03:07.530 --> 03:09.840 So the question might come up, okay, Keith, 81 03:09.840 --> 03:11.250 please give us a heads up. 82 03:11.250 --> 03:13.350 Why then would we even want to deploy 83 03:13.350 --> 03:15.960 or need to deploy an edge transport node? 84 03:15.960 --> 03:18.540 And here's the answer, anytime that we need 85 03:18.540 --> 03:20.820 to provide some type of a service. 86 03:20.820 --> 03:23.040 And examples of a service would include things such 87 03:23.040 --> 03:25.200 as active standby support. 88 03:25.200 --> 03:28.530 For example, a single E ES XI host on its own cannot provide 89 03:28.530 --> 03:30.360 fault tolerance for this routing function. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 89 03:28.530 --> 03:30.360 fault tolerance for this routing function. 90 03:30.360 --> 03:32.460 So if we wanted to leverage active standby, 91 03:32.460 --> 03:34.290 that would be a network service that would be 92 03:34.290 --> 03:37.950 provided courtesy of the edge transport nodes, for example, 93 03:37.950 --> 03:41.160 Edge one and Edge two as part of a edge cluster. 94 03:41.160 --> 03:43.680 Another example of a service that would require the services 95 03:43.680 --> 03:46.380 of an Edge transport node would be a network service such 96 03:46.380 --> 03:49.950 as network address translation or setting up a VPN 97 03:49.950 --> 03:53.280 or setting up some centralized DHCP services 98 03:53.280 --> 03:56.880 or setting up some gateway specific firewall rules. 99 03:56.880 --> 03:58.110 And the list goes on. 100 03:58.110 --> 04:00.060 So anytime that we have a network service WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 100 03:58.110 --> 04:00.060 So anytime that we have a network service 101 04:00.060 --> 04:03.570 where an ESXI host can't do it on its own, it's at 102 04:03.570 --> 04:06.240 that time when we're gonna start tunneling our traffic based 103 04:06.240 --> 04:08.550 on routing decisions to our edge nodes 104 04:08.550 --> 04:10.650 who are gonna provide those types of services. 105 04:10.650 --> 04:13.560 And also to help reinforce a couple of concepts in NSX 106 04:13.560 --> 04:15.000 regarding providing these services, 107 04:15.000 --> 04:17.340 there's a concept called a DR, which stands 108 04:17.340 --> 04:19.380 for a distributed router. 109 04:19.380 --> 04:21.180 Think of it like a logical router 110 04:21.180 --> 04:22.500 that everybody knows about. 111 04:22.500 --> 04:25.440 So the edge nodes would be aware of this logical router 112 04:25.440 --> 04:27.270 and how to route between these two segments 113 04:27.270 --> 04:28.890 and ESXI-A with a copy of 114 04:28.890 --> 04:30.930 that distributed router would know how to route locally WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 114 04:28.890 --> 04:30.930 that distributed router would know how to route locally 115 04:30.930 --> 04:33.240 between those two segments and ESXI-B 116 04:33.240 --> 04:34.310 with a copy of that router. 117 04:34.310 --> 04:35.310 We know how to route. 118 04:35.310 --> 04:36.510 So in that sense, we could say 119 04:36.510 --> 04:37.710 that the edge nodes 120 04:37.710 --> 04:40.860 and each of our transport nodes all have a effectively a 121 04:40.860 --> 04:43.230 copy of the distributed router. 122 04:43.230 --> 04:44.430 I'll point to it right here. 123 04:44.430 --> 04:47.250 And when we start adding on additional services 124 04:47.250 --> 04:50.820 that require these services of an edge node, we are going 125 04:50.820 --> 04:53.820 to also be implementing a Logical services router. 126 04:53.820 --> 04:55.350 The acronym for that is SR. 127 04:55.350 --> 04:57.720 And again, we'll have a further discussion on how 128 04:57.720 --> 04:59.340 to implement that and set that up. 129 04:59.340 --> 05:01.200 However, it's critical at this stage in the game WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 129 04:59.340 --> 05:01.200 However, it's critical at this stage in the game 130 05:01.200 --> 05:03.660 that you're aware that anytime we're adding on some type 131 05:03.660 --> 05:05.700 of a network service where the ESXI host can't do it 132 05:05.700 --> 05:08.010 on their own, we're also be including an SR 133 05:08.010 --> 05:10.620 and that SR function, that services router function, 134 05:10.620 --> 05:12.540 is gonna be included on the edge nodes. 135 05:12.540 --> 05:14.790 So for the full picture, the distributed router would be, 136 05:14.790 --> 05:17.820 and here and here and here. 137 05:17.820 --> 05:19.320 And then we start adding on services 138 05:19.320 --> 05:22.680 that the ESXI host can't do on their own like active standby 139 05:22.680 --> 05:23.970 or NAT and so forth. 140 05:23.970 --> 05:25.350 Then on the edge nodes, 141 05:25.350 --> 05:27.600 we're also gonna be including an instance 142 05:27.600 --> 05:29.520 of an SRA services router. 143 05:29.520 --> 05:31.350 So think of a services router WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 143 05:29.520 --> 05:31.350 So think of a services router 144 05:31.350 --> 05:34.710 as a additional function in addition to the normal routing 145 05:34.710 --> 05:37.740 that a edge node can do to provide some type 146 05:37.740 --> 05:39.270 of network service. 147 05:39.270 --> 05:41.790 Another great example of when this is needed is if we're 148 05:41.790 --> 05:43.890 going to be connecting, for example, this router 149 05:43.890 --> 05:45.120 to the outside world. 150 05:45.120 --> 05:48.210 So at that point we'd be using an edge node which would have 151 05:48.210 --> 05:49.980 a services router function on it for 152 05:49.980 --> 05:53.400 that connectivity from our VMs inside of NSX 153 05:53.400 --> 05:54.690 to the outside world. 154 05:54.690 --> 05:56.640 So I was thinking to myself, what would be a great way 155 05:56.640 --> 05:59.580 for you I to reinforce this concept 156 05:59.580 --> 06:02.430 that sometimes an edge node may not be needed, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 156 05:59.580 --> 06:02.430 that sometimes an edge node may not be needed, 157 06:02.430 --> 06:03.810 but sometimes it is. 158 06:03.810 --> 06:07.020 So I thought a simple example of that would be to go ahead 159 06:07.020 --> 06:09.780 and set up a simple distributed router just 160 06:09.780 --> 06:12.870 as a demonstration that the host transport nodes 161 06:12.870 --> 06:15.900 and the edge nodes, once we set up a distributed router, all 162 06:15.900 --> 06:17.040 of them are gonna have a copy of 163 06:17.040 --> 06:19.200 that information about the routing in this case 164 06:19.200 --> 06:21.330 between segment 10 and segment 20. 165 06:21.330 --> 06:23.820 And then the moment we start adding an additional network 166 06:23.820 --> 06:26.310 service like Active standby or NAT 167 06:26.310 --> 06:29.220 or some other feature that requires an edge node, 168 06:29.220 --> 06:30.660 we would then see that additional service WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 168 06:29.220 --> 06:30.660 we would then see that additional service 169 06:30.660 --> 06:33.842 that services router function on our edge nodes while the 170 06:33.842 --> 06:36.570 ESXI hosts who can't provide that service, 171 06:36.570 --> 06:38.820 they wouldn't have that additional service router there. 172 06:38.820 --> 06:41.670 So to reinforce the concept that the distributed router, 173 06:41.670 --> 06:43.380 for example, the logical router 174 06:43.380 --> 06:44.670 that can do the logical routing 175 06:44.670 --> 06:46.950 between a couple different segments here, 176 06:46.950 --> 06:48.990 that distributed router can exist on our 177 06:48.990 --> 06:50.250 host transport nodes. 178 06:50.250 --> 06:52.950 It'll also exist on our edge nodes. 179 06:52.950 --> 06:56.070 And when we start to include additional services like Active 180 06:56.070 --> 06:57.240 Standby or NAT 181 06:57.240 --> 06:59.040 and so forth, that additional service 182 06:59.040 --> 07:02.040 that services router function will appear here on our edge WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 182 06:59.040 --> 07:02.040 that services router function will appear here on our edge 183 07:02.040 --> 07:04.860 nodes while the ESXI hosts, who are not gonna be providing 184 07:04.860 --> 07:06.840 that specific service, will still just have a 185 07:06.840 --> 07:08.850 copy of the distributed router. 186 07:08.850 --> 07:10.800 And to reinforce that, let's do two things. 187 07:10.800 --> 07:14.070 Number one, I'd like to give you a foreshadowing of how 188 07:14.070 --> 07:16.170 to create a logical router. 189 07:16.170 --> 07:17.790 And again, this video is just for the demonstration 190 07:17.790 --> 07:19.650 that distributed router is going 191 07:19.650 --> 07:23.280 to exist on all our transport nodes that need access to it. 192 07:23.280 --> 07:25.860 And then secondly, we'll modify the configuration 193 07:25.860 --> 07:27.990 so this router isn't just a distributed router, 194 07:27.990 --> 07:30.930 but we also want active standby services, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 194 07:27.990 --> 07:30.930 but we also want active standby services, 195 07:30.930 --> 07:32.550 which will cause the SR component 196 07:32.550 --> 07:34.500 to show up here on our edges. 197 07:34.500 --> 07:37.710 So to demonstrate that I have here edge one at the top, 198 07:37.710 --> 07:39.570 and I've got ESXI-A at the bottom, 199 07:39.570 --> 07:41.610 both are in NSX CLI mode. 200 07:41.610 --> 07:45.270 So if we issue the command, for example, get gateways, 201 07:45.270 --> 07:47.160 that's gonna show us our existing gateways 202 07:47.160 --> 07:49.470 that we currently have inside of NSX. 203 07:49.470 --> 07:52.410 So our edge transport nodes are gonna have a logical gateway 204 07:52.410 --> 07:55.620 and that gateway is set up for their transport network. 205 07:55.620 --> 07:58.563 So for example, here on edge one, if we said, Hey, 206 07:58.563 --> 08:01.440 let's get the gateway information and I'll just copy WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 206 07:58.563 --> 08:01.440 let's get the gateway information and I'll just copy 207 08:01.440 --> 08:04.410 and paste this UUID and paste it in 208 08:04.410 --> 08:06.780 and then say forwarding, press enter. 209 08:06.780 --> 08:08.850 This is gonna show us the routing table 210 08:08.850 --> 08:11.520 for the transport network that this edge node uses. 211 08:11.520 --> 08:14.970 So its IP address is 33.33, et cetera. 212 08:14.970 --> 08:16.860 That's shown right here. It's connected logically 213 08:16.860 --> 08:19.530 to the 24 bit network, 33, et cetera. 214 08:19.530 --> 08:21.900 And there's this default gateway on the transport network. 215 08:21.900 --> 08:24.510 So that's the refer to as VRF 0. 216 08:24.510 --> 08:26.160 Think of it like the default routing 217 08:26.160 --> 08:27.450 table for our edge node. 218 08:27.450 --> 08:30.030 So if you're gonna look at Edge two, it has the IP address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 218 08:27.450 --> 08:30.030 So if you're gonna look at Edge two, it has the IP address 219 08:30.030 --> 08:31.710 of 44.44, et cetera. 220 08:31.710 --> 08:35.040 So it's routing table for its logical gateway 221 08:35.040 --> 08:36.750 that it's using for the transport network, 222 08:36.750 --> 08:38.040 would show that information. 223 08:38.040 --> 08:39.210 So to start off, this command here 224 08:39.210 --> 08:42.120 of get gateways is just gonna show us the gateways 225 08:42.120 --> 08:43.680 that exist on our devices. 226 08:43.680 --> 08:46.200 And again, here on the edge, it's the gateway that's used 227 08:46.200 --> 08:48.450 for the transport network by Edge One. 228 08:48.450 --> 08:50.217 And down here, ESXI-A 229 08:50.217 --> 08:53.820 and NSX CLI mode is showing no logical gateways. 230 08:53.820 --> 08:56.190 So just as a reinforcement of the concept 231 08:56.190 --> 08:58.740 that a distributed router when we create one, 232 08:58.740 --> 09:01.200 it's gonna show up everywhere it's needed, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 232 08:58.740 --> 09:01.200 it's gonna show up everywhere it's needed, 233 09:01.200 --> 09:04.080 let's create a simple distributed router. 234 09:04.080 --> 09:06.240 And our goal here is just to reinforce the concept 235 09:06.240 --> 09:08.850 that if we create this logical distributed router, 236 09:08.850 --> 09:11.820 this logical gateway, it's gonna show up everywhere 237 09:11.820 --> 09:15.180 that it's needed, including our host and transport nodes. 238 09:15.180 --> 09:16.920 So if we go to networking 239 09:16.920 --> 09:18.330 and we click here on network topology, 240 09:18.330 --> 09:21.540 currently we have two segments with two VMs connected 241 09:21.540 --> 09:24.570 to each of those segments, and we have no logical routers. 242 09:24.570 --> 09:28.230 So if we wanna create a gateway here in NSX, 243 09:28.230 --> 09:30.480 we go here under networking, under connectivity, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 243 09:28.230 --> 09:30.480 we go here under networking, under connectivity, 244 09:30.480 --> 09:31.530 go to tier one gateways. 245 09:31.530 --> 09:33.600 And again, don't worry about the actual tier 246 09:33.600 --> 09:35.100 one versus tier zero. 247 09:35.100 --> 09:37.470 We'll cover all of that in an upcoming video. 248 09:37.470 --> 09:40.110 For now, we're just gonna create a simple tier one gateway 249 09:40.110 --> 09:42.270 by clicking on add tier one gateway, 250 09:42.270 --> 09:43.980 and I'm gonna name it Demo gateway. 251 09:43.980 --> 09:45.990 And then for the HA mode here, 252 09:45.990 --> 09:47.670 I'm gonna specify, to start with, that 253 09:47.670 --> 09:49.170 I don't want active standby 254 09:49.170 --> 09:50.880 'cause that would require an edge node. 255 09:50.880 --> 09:52.230 I don't want Active Active 256 09:52.230 --> 09:54.270 'cause that would require the special services router 257 09:54.270 --> 09:55.620 function on an edge node, 258 09:55.620 --> 09:58.020 but I wanna do a distributed router only. 259 09:58.020 --> 10:01.470 So with only that selected, I'll go ahead and click on save. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 259 09:58.020 --> 10:01.470 So with only that selected, I'll go ahead and click on save. 260 10:01.470 --> 10:03.180 And now we have this new gateway. 261 10:03.180 --> 10:04.530 If we go look at the topology 262 10:04.530 --> 10:07.020 by clicking here on network topology is showing us 263 10:07.020 --> 10:09.567 that da da da da, we have this demo gateway. 264 10:09.567 --> 10:12.240 And if we wanna link it to these two network segments like 265 10:12.240 --> 10:15.090 connecting an interface to segment 10, another interface 266 10:15.090 --> 10:17.850 to segment 20, we do that in NSX by going to each 267 10:17.850 --> 10:19.050 of the segments and saying, Hey, 268 10:19.050 --> 10:20.940 please connect this to this gateway. 269 10:20.940 --> 10:22.830 So again, as a demonstration, 270 10:22.830 --> 10:24.120 let's go ahead and do that right now. 271 10:24.120 --> 10:26.010 We'll go to segments, we'll edit segment 10 272 10:26.010 --> 10:27.330 by clicking on the three dots, 273 10:27.330 --> 10:29.250 clicking on edit, and they'll say, you know what? 274 10:29.250 --> 10:33.510 We want this segment to be connected to our demo gateway WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 274 10:29.250 --> 10:33.510 We want this segment to be connected to our demo gateway 275 10:33.510 --> 10:34.890 and boom, we're done. 276 10:34.890 --> 10:37.440 And we click on save and then click on close editing. 277 10:37.440 --> 10:39.980 And then we'll repeat that over here for segment 20. 278 10:39.980 --> 10:42.450 So we'll click on the three dots for segment 20, 279 10:42.450 --> 10:44.820 click on edit and say we simply wanna connect that 280 10:44.820 --> 10:46.170 to our demo gateway. 281 10:46.170 --> 10:49.860 Again, it's like connecting a interface on a physical router 282 10:49.860 --> 10:53.100 over to a subnet or connecting it to a specific VLAN. 283 10:53.100 --> 10:54.930 So scroll down, we'll click on save 284 10:54.930 --> 10:56.370 and click on close editing. 285 10:56.370 --> 10:57.630 Alright, fantabulous. 286 10:57.630 --> 10:59.370 So now if we wanna see the network topology 287 10:59.370 --> 11:01.050 by clicking on network topology, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 287 10:59.370 --> 11:01.050 by clicking on network topology, 288 11:01.050 --> 11:02.610 it's now showing us we have our demo gateway 289 11:02.610 --> 11:04.770 and it's connected to the 10 network and the 20 network. 290 11:04.770 --> 11:05.850 So we could go ahead 291 11:05.850 --> 11:09.330 and tell these VMs over here that their default gateway is 292 11:09.330 --> 11:10.830 for example, 10.10.0 dot 293 11:10.830 --> 11:13.020 and whatever IP address we signed here on this interface. 294 11:13.020 --> 11:15.090 And then over here, these VMs we could say, Hey, 295 11:15.090 --> 11:17.130 your default gateway is 10.20.0 dot 296 11:17.130 --> 11:18.600 and whatever IP address we signed here. 297 11:18.600 --> 11:20.700 And in the background I also set up two IP 298 11:20.700 --> 11:22.290 addresses, do one on each subnet. 299 11:22.290 --> 11:24.900 Again, we'll cover more details on how to set that up 300 11:24.900 --> 11:27.090 and how to confirm that in a separate skill. 301 11:27.090 --> 11:29.730 But for now we have this new gateway 302 11:29.730 --> 11:33.560 and this new gateway logically lives on all WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 302 11:29.730 --> 11:33.560 and this new gateway logically lives on all 303 11:33.560 --> 11:37.200 of our transport noes, including edge one and Edge two 304 11:37.200 --> 11:39.480 and ESXI-A and ESXI-B. 305 11:39.480 --> 11:40.770 And to verify that, 306 11:40.770 --> 11:42.720 let's go take a look at the command line. 307 11:42.720 --> 11:45.480 And I also wanna point out that I've got VMs running on 308 11:45.480 --> 11:48.360 ESXI-A and ESXI-B that are currently connected 309 11:48.360 --> 11:51.330 to those relevant segments of segment 10 and segment 20. 310 11:51.330 --> 11:53.400 So a moment ago when we said get gateways 311 11:53.400 --> 11:54.570 and an older way of saying 312 11:54.570 --> 11:57.540 that is get logical dash routers either way is great, 313 11:57.540 --> 12:01.440 that's gonna show us the logical layer three routers in NSX. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 313 11:57.540 --> 12:01.440 that's gonna show us the logical layer three routers in NSX. 314 12:01.440 --> 12:04.410 So previously on Edge one, we just had the default router 315 12:04.410 --> 12:06.870 for the transport network on the edge one device. 316 12:06.870 --> 12:08.670 And here in ESXI-A, it had nothing. 317 12:08.670 --> 12:10.920 But now if we do that same command again 318 12:10.920 --> 12:13.890 of get gateways on both devices, check this out. 319 12:13.890 --> 12:15.710 In addition to the default route on Edge one, 320 12:15.710 --> 12:19.620 it now has logical router with this UUID starting 321 12:19.620 --> 12:21.660 with 24 ending with af. 322 12:21.660 --> 12:24.642 And we have that same identical distributed router 323 12:24.642 --> 12:27.150 configured here on ESXI-A 324 12:27.150 --> 12:30.180 because it's the same exact logical router. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 324 12:27.150 --> 12:30.180 because it's the same exact logical router. 325 12:30.180 --> 12:32.310 The IP addresses are the same, 326 12:32.310 --> 12:34.320 the layer two addresses are the same. 327 12:34.320 --> 12:35.700 And up here in the output 328 12:35.700 --> 12:38.160 of the edge one showing us the actual name of 329 12:38.160 --> 12:41.820 that gateway itself, Dr dash demo Space Gateway, 330 12:41.820 --> 12:43.950 that's the name we gave it and we scroll to the right. 331 12:43.950 --> 12:45.660 So here at the edge it's also showing us 332 12:45.660 --> 12:47.670 that it's a distributed router, 333 12:47.670 --> 12:49.830 specifically a tier one distributed router. 334 12:49.830 --> 12:51.840 So long story short edge one 335 12:51.840 --> 12:56.580 and the ESXI host transport node called ESXI-A. 336 12:56.580 --> 13:00.690 They both have a copy of that same exact distributed router. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 336 12:56.580 --> 13:00.690 They both have a copy of that same exact distributed router. 337 13:00.690 --> 13:03.690 So if we did a command like get gateway, I'm gonna plug in 338 13:03.690 --> 13:06.540 that UUID here just by pasting it in. 339 13:06.540 --> 13:08.100 And then we said forwarding, 340 13:08.100 --> 13:11.430 that's gonna show us effectively the routing table on 341 13:11.430 --> 13:12.750 that distributed router. 342 13:12.750 --> 13:14.670 So if you notice, they both have a route 343 13:14.670 --> 13:16.650 for the 10.10.0.24 network. 344 13:16.650 --> 13:18.810 So appears Edge one down here is ESXI-A. 345 13:18.810 --> 13:22.260 They both have a route for the 10.20.0.24 bit network. 346 13:22.260 --> 13:24.000 And again, on the top it's edge one reflecting 347 13:24.000 --> 13:26.430 that here at the bottom it's ESXI-A reflecting that. 348 13:26.430 --> 13:28.410 So effectively they both have the same information. 349 13:28.410 --> 13:32.640 However, if we were to add some type of network service WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 349 13:28.410 --> 13:32.640 However, if we were to add some type of network service 350 13:32.640 --> 13:35.430 that required a services router instance, 351 13:35.430 --> 13:38.160 the edges would receive that services router function, 352 13:38.160 --> 13:40.560 for example, like setting up active standby 353 13:40.560 --> 13:43.050 or setting up nat, something that requires 354 13:43.050 --> 13:45.210 the edge services to be used. 355 13:45.210 --> 13:48.180 And the ESXI host wouldn't bother getting a copy of 356 13:48.180 --> 13:50.250 that services router because they can't provide 357 13:50.250 --> 13:51.630 that functionality again, such 358 13:51.630 --> 13:54.030 as active standby or active active. 359 13:54.030 --> 13:55.500 So back at our NSX manager, 360 13:55.500 --> 13:59.040 if we double clicked on this gateway, our demo gateway, 361 13:59.040 --> 14:00.930 it's gonna show us what they call the fabric view, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 361 13:59.040 --> 14:00.930 it's gonna show us what they call the fabric view, 362 14:00.930 --> 14:02.490 which is what's making up 363 14:02.490 --> 14:04.800 or providing the resources for the gateway. 364 14:04.800 --> 14:06.630 So here it says DR distributed router, 365 14:06.630 --> 14:10.380 which means this distributed router function can exist on 366 14:10.380 --> 14:12.272 any of our transport nodes that need it. 367 14:12.272 --> 14:16.110 ESXI-A, ESXI-B, edge one and edge two. 368 14:16.110 --> 14:18.810 So if we did a trace, for example, from VM one over 369 14:18.810 --> 14:22.050 to VM two, and both those two VMs are being hosted 370 14:22.050 --> 14:26.130 by ESXI-A, ESXI-A could do all the routing 371 14:26.130 --> 14:29.190 logically on its own between those two segments 372 14:29.190 --> 14:30.570 and to verify that if we went to plan WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 372 14:29.190 --> 14:30.570 and to verify that if we went to plan 373 14:30.570 --> 14:32.520 and troubleshoot over here on the left, if we go 374 14:32.520 --> 14:34.380 to traffic analysis and go to trace flow 375 14:34.380 --> 14:35.790 and click here to get started, 376 14:35.790 --> 14:38.400 here we can say we wanna do a test from, for example, 377 14:38.400 --> 14:42.960 VM one at 10.10.0.10, which is being hosted by ESXI-A. 378 14:42.960 --> 14:46.590 And for the target we can specify VM two at 10.20.0.20. 379 14:46.590 --> 14:49.440 Also, let's just verify real quick that VM one 380 14:49.440 --> 14:52.710 and VM two are both being by ESXI-A. 381 14:52.710 --> 14:55.770 So to do that we'll head over here to the vSphere client. 382 14:55.770 --> 14:57.750 And here we have VM one and VM two 383 14:57.750 --> 14:58.890 and I've got the column for host 384 14:58.890 --> 15:01.140 and the first one's being hosted by ESXI-A WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 384 14:58.890 --> 15:01.140 and the first one's being hosted by ESXI-A 385 15:01.140 --> 15:03.690 and the second one's being hosted also by ESXI-A. 386 15:03.690 --> 15:06.720 So if we go back and we run this trace by clicking on trace, 387 15:06.720 --> 15:10.140 it's gonna show us that all of that logical routing 388 15:10.140 --> 15:11.340 between segment 10 389 15:11.340 --> 15:15.120 and segment 20, all of that was done by ESXI-A 390 15:15.120 --> 15:17.280 because they has a copy of the distributed router. 391 15:17.280 --> 15:19.140 All that work is being done by ESXI-A. 392 15:19.140 --> 15:21.540 So if we clicked over here on the left, it's gonna show us 393 15:21.540 --> 15:24.150 that's ESXI-A where VM one is. 394 15:24.150 --> 15:26.250 If we click here for the demo gateway, 395 15:26.250 --> 15:27.840 if we click on the host involved, 396 15:27.840 --> 15:29.277 it's gonna show us it was ESXI-A 397 15:29.277 --> 15:31.020 and for the final delivery as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 397 15:29.277 --> 15:31.020 and for the final delivery as well. 398 15:31.020 --> 15:34.080 If we click over here, once again, it was ESXI-A 399 15:34.080 --> 15:35.700 because it has a copy of the distributed router. 400 15:35.700 --> 15:38.910 Now if we modify this demo gateway 401 15:38.910 --> 15:41.010 and we said, you know what, we wanna provide some kind 402 15:41.010 --> 15:43.380 of network service that an ESXI 403 15:43.380 --> 15:46.770 host transport node can't do on its own like active standby 404 15:46.770 --> 15:48.840 or active active at that point, 405 15:48.840 --> 15:50.250 it's then gonna require the use 406 15:50.250 --> 15:52.170 and services of an edge node. 407 15:52.170 --> 15:54.270 So to demonstrate that, we'll go back to networking. 408 15:54.270 --> 15:57.060 Let's go to our tier one gateways by clicking on it 409 15:57.060 --> 15:58.710 and then we'll edit our demo gateway 410 15:58.710 --> 16:00.390 and say, you know what, you're not just gonna be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 410 15:58.710 --> 16:00.390 and say, you know what, you're not just gonna be 411 16:00.390 --> 16:01.830 distributed only. 412 16:01.830 --> 16:03.810 I wanna go ahead and use some additional services. 413 16:03.810 --> 16:06.570 And for the demo we're gonna say, let's use active standby. 414 16:06.570 --> 16:07.770 So we'll click on the three dots 415 16:07.770 --> 16:09.990 for our demo gateway, click on edit. 416 16:09.990 --> 16:11.880 And then for the HA mode we'll use the dropdown 417 16:11.880 --> 16:13.680 and say we want active standby. 418 16:13.680 --> 16:16.710 Now that's going to require our edge services. 419 16:16.710 --> 16:18.420 And as a result, it's also asking, Hey, 420 16:18.420 --> 16:20.520 which edge cluster do you wanna use? 421 16:20.520 --> 16:21.723 We only have one. And in 422 16:21.723 --> 16:23.432 that cluster it's Edge one and Edge two. 423 16:23.432 --> 16:26.190 Fantastic. And now we'll click on save. 424 16:26.190 --> 16:28.590 So it says it was successfully updated. Fantastic. 425 16:28.590 --> 16:30.300 We'll click here on close editing. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 425 16:28.590 --> 16:30.300 We'll click here on close editing. 426 16:30.300 --> 16:32.940 This is a quick recap before we create any gateways. 427 16:32.940 --> 16:35.130 The edge knew about its transport network. 428 16:35.130 --> 16:38.730 The ESXI host knew about no virtual gateways, 429 16:38.730 --> 16:40.290 no logical layer three routers. 430 16:40.290 --> 16:42.690 And then as we added the first router, then 431 16:42.690 --> 16:44.730 that additional router showed up on our edge, 432 16:44.730 --> 16:45.960 which is the top here. 433 16:45.960 --> 16:48.570 It also showed up on our ESXI host 434 16:48.570 --> 16:51.870 and notice again the same UUID, so that's the UUID 435 16:51.870 --> 16:55.680 for the distributed router that exists on the edge node here 436 16:55.680 --> 16:57.060 and also on the transport node. 437 16:57.060 --> 16:59.700 And then when we just made that final change 438 16:59.700 --> 17:00.930 and we said, Hey, we wanna go ahead WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 438 16:59.700 --> 17:00.930 and we said, Hey, we wanna go ahead 439 17:00.930 --> 17:03.390 and do active standby, if we now do the command 440 17:03.390 --> 17:05.160 of get gateways, check this out. 441 17:05.160 --> 17:08.190 We still have the same distributed router on ESXI-A. 442 17:08.190 --> 17:11.010 That's the same as the one right here on our edge 443 17:11.010 --> 17:12.420 node, edge one. 444 17:12.420 --> 17:14.880 But look at this, the edge node now has an 445 17:14.880 --> 17:16.620 additional logical gateway. 446 17:16.620 --> 17:19.380 Think of it like an additional routing function 447 17:19.380 --> 17:22.740 or service that exists on edge node to provide some service 448 17:22.740 --> 17:24.900 where the ESXI host can't do it on their own. 449 17:24.900 --> 17:27.150 And the example I'm using here is the function 450 17:27.150 --> 17:30.630 of active standby for the gateway services, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 450 17:27.150 --> 17:30.630 of active standby for the gateway services, 451 17:30.630 --> 17:33.450 which is gonna require the edge nodes working as a cluster. 452 17:33.450 --> 17:35.370 So for Edge one, there's the UUID, 453 17:35.370 --> 17:36.330 there's the name we gave it, 454 17:36.330 --> 17:38.400 and if we scroll to the right, in fact I'll highlight 455 17:38.400 --> 17:40.560 that entire row and we'll scroll to the right. 456 17:40.560 --> 17:43.530 It's also indicating that is a service router. 457 17:43.530 --> 17:45.450 Again, think of it like providing some additional service. 458 17:45.450 --> 17:47.280 In this case, active standby services, 459 17:47.280 --> 17:50.010 which an ESXI host can't do on its own. 460 17:50.010 --> 17:53.490 And so here on ESXI-A, if we did a get gateway 461 17:53.490 --> 17:56.610 and I'll plug in the UUID of our distributed router 462 17:56.610 --> 17:59.490 and I'll go ahead and type in forwarding and press enter. 463 17:59.490 --> 18:02.247 Here's showing us the routing for IPV4 and IPV6. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 463 17:59.490 --> 18:02.247 Here's showing us the routing for IPV4 and IPV6. 464 18:02.247 --> 18:04.467 And for a default route is pointing to this IP address, 465 18:04.467 --> 18:07.920 169.254.0.2. 466 18:07.920 --> 18:10.830 Now let me share with you whose IP address that is. 467 18:10.830 --> 18:12.870 That is an IP address that's owned by the services router. 468 18:12.870 --> 18:16.230 So here on the edge if we did a get gateway 469 18:16.230 --> 18:17.550 and then I'm gonna go ahead and copy 470 18:17.550 --> 18:21.150 and paste the UUID for our services router function, here. 471 18:21.150 --> 18:23.845 I'll do a space, I'm gonna type in interface. 472 18:23.845 --> 18:25.950 I'm gonna a space and I'm gonna do a pipe symbol 473 18:25.950 --> 18:27.690 and then find, space. 474 18:27.690 --> 18:29.850 And then I'm gonna plug in this IP address again, 475 18:29.850 --> 18:32.490 the purpose here is just to help reinforce the concept WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 475 18:29.850 --> 18:32.490 the purpose here is just to help reinforce the concept 476 18:32.490 --> 18:35.340 that a services router function is added 477 18:35.340 --> 18:37.710 and that's implemented when there's no option to do 478 18:37.710 --> 18:39.510 that on the actual host transport node. 479 18:39.510 --> 18:41.730 That's where we're leveraging the edge nodes. 480 18:41.730 --> 18:43.710 So in this output, all I'm saying is that 481 18:43.710 --> 18:47.160 for the services router function, show me the interfaces 482 18:47.160 --> 18:49.830 and show me only interface information in the output 483 18:49.830 --> 18:53.370 where we have this string, which is 169.254.0.2. 484 18:53.370 --> 18:54.660 And this is just confirming that 485 18:54.660 --> 18:58.980 that IP address is associated with this services router. 486 18:58.980 --> 19:02.310 So from a routing perspective, the transport node says, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 486 18:58.980 --> 19:02.310 So from a routing perspective, the transport node says, 487 19:02.310 --> 19:04.110 well, from a routing perspective, if I need 488 19:04.110 --> 19:06.420 to forward traffic and I don't have a better route in my 489 19:06.420 --> 19:08.040 routing table, I'm gonna forward it 490 19:08.040 --> 19:10.080 to this next top address, which 491 19:10.080 --> 19:12.690 that next top address belongs to the services router. 492 19:12.690 --> 19:14.340 And we'll take a closer look at that 493 19:14.340 --> 19:18.480 as we implement multi-tiered routing inside of NSX. 494 19:18.480 --> 19:19.890 So the key takeaway is this. 495 19:19.890 --> 19:21.450 If we do a get gateways, 496 19:21.450 --> 19:24.720 the services router function will show up on our edge nodes 497 19:24.720 --> 19:27.840 when we need specific services that are not able 498 19:27.840 --> 19:32.040 to be implemented on a standalone ESXI host transport node. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 498 19:27.840 --> 19:32.040 to be implemented on a standalone ESXI host transport node. 499 19:32.040 --> 19:34.440 And this is an example of doing that right here. 500 19:34.440 --> 19:36.960 Again, they both have a copy of the distributed router, 501 19:36.960 --> 19:40.290 which in our case is our DR dash demo gateway. 502 19:40.290 --> 19:42.450 But only the edge nodes are gonna have a copy 503 19:42.450 --> 19:43.830 of the services router. 504 19:43.830 --> 19:45.060 And from a routing perspective, 505 19:45.060 --> 19:47.940 if the ESXI host ever need to forward traffic to 506 19:47.940 --> 19:51.000 that services router function in their routing tables, 507 19:51.000 --> 19:53.450 they know the IP address they need to send it to.