WEBVTT 1 00:00.180 --> 00:02.220 So now that we have Segment 10 implemented 2 00:02.220 --> 00:04.380 and tested and verified, let's go ahead 3 00:04.380 --> 00:07.470 and walk through the process of creating segment 20. 4 00:07.470 --> 00:08.790 So here we'll create a new VM 5 00:08.790 --> 00:12.960 and we'll call it VM A 20.0.0.20. 6 00:12.960 --> 00:17.190 And over here on the ESXiB side, we'll make VM B 7 00:17.190 --> 00:21.720 and we'll put it at the IPS of 20.0.0.21, 8 00:21.720 --> 00:23.850 and we'll include the new segment called Seg 20. 9 00:23.850 --> 00:24.990 We'll include that as part 10 00:24.990 --> 00:26.970 of our A B overlay transport zone, 11 00:26.970 --> 00:31.440 and that way both ESXi-A and ESXi-B will have access to it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:26.970 --> 00:31.440 and that way both ESXi-A and ESXi-B will have access to it 12 00:31.440 --> 00:34.410 for the connection of the new VMs to that segment. 13 00:34.410 --> 00:35.370 So without further ado, 14 00:35.370 --> 00:38.430 let's implement our new overlay segment called Segment 20, 15 00:38.430 --> 00:40.200 and we'll add our two VMs to it. 16 00:40.200 --> 00:42.000 So here in the NSX manager, 17 00:42.000 --> 00:43.920 we'll click on the networking tab 18 00:43.920 --> 00:46.740 and that's where we would go to create another segment. 19 00:46.740 --> 00:49.830 So currently we have one segment that's segment 10. 20 00:49.830 --> 00:52.860 So we are gonna, on the left hand side, click on segments, 21 00:52.860 --> 00:55.680 and then we'll click on add segment to create another one 22 00:55.680 --> 00:58.050 and listening to SEG 20 pink. 23 00:58.050 --> 01:00.690 And we don't have any logical layer three gateways yet WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 00:58.050 --> 01:00.690 And we don't have any logical layer three gateways yet 24 01:00.690 --> 01:02.580 even to associate with that new segment. 25 01:02.580 --> 01:03.810 So we'll leave that empty. 26 01:03.810 --> 01:05.880 But we will associate this new segment 27 01:05.880 --> 01:09.840 with our overlay zone, and that's our A B overlay zone, 28 01:09.840 --> 01:13.230 which both ESXi-A and B are both supporting 29 01:13.230 --> 01:15.420 so that means this new segment should be available 30 01:15.420 --> 01:17.010 to both those hosts as well. 31 01:17.010 --> 01:19.800 So we'll scroll down and click on save. 32 01:19.800 --> 01:22.410 And it's gonna ask us, do you wanna continue configuring? 33 01:22.410 --> 01:23.610 We'll say no. 34 01:23.610 --> 01:26.700 And now we have Seg 10 yellow and SEG 20 pink. 35 01:26.700 --> 01:28.590 So let's head over to the vSphere client 36 01:28.590 --> 01:31.680 and create a couple new VMs and attach both of them WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 01:28.590 --> 01:31.680 and create a couple new VMs and attach both of them 37 01:31.680 --> 01:33.450 to this new network segment. 38 01:33.450 --> 01:36.600 So here in the vSphere client, let's go to the network tab 39 01:36.600 --> 01:39.900 just to verify that it does show up so there's segment 20. 40 01:39.900 --> 01:41.040 So if we click on summary here, 41 01:41.040 --> 01:43.920 it's showing us the VNI number right there, 42 01:43.920 --> 01:45.300 which could be handy at the CLI 43 01:45.300 --> 01:46.920 if we ever need to use the CLI. 44 01:46.920 --> 01:48.750 It's showing us the transport zone that 45 01:48.750 --> 01:50.400 that new segment belongs to. 46 01:50.400 --> 01:51.960 It's also showing us right here 47 01:51.960 --> 01:53.670 the actual name of the segment 48 01:53.670 --> 01:56.280 and also down here that we have two transport nodes 49 01:56.280 --> 01:57.810 that are currently supporting it. 50 01:57.810 --> 01:59.610 If we click on configure, once again, 51 01:59.610 --> 02:01.470 it doesn't give us options for really configuring it, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 51 01:59.610 --> 02:01.470 it doesn't give us options for really configuring it, 52 02:01.470 --> 02:04.500 but rather to see the details regarding that segment. 53 02:04.500 --> 02:07.140 So let's create a couple new VMs and connect them over 54 02:07.140 --> 02:08.040 based on our plan. 55 02:08.040 --> 02:10.140 So we'll go to our templates here, 56 02:10.140 --> 02:11.910 right click on our tiny template 57 02:11.910 --> 02:14.880 and click on new VM from this template. 58 02:14.880 --> 02:18.450 And for the first one, we'll call it VM A space. 59 02:18.450 --> 02:20.970 This is gonna be 20.0.0.20, 60 02:20.970 --> 02:24.360 and I'm gonna put this in the folder called VMs for testing 61 02:24.360 --> 02:26.040 and we'll click on Next. 62 02:26.040 --> 02:28.080 Alright, as far as the compute resource, 63 02:28.080 --> 02:30.750 we want this first one to be on ESXi-A. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 63 02:28.080 --> 02:30.750 we want this first one to be on ESXi-A. 64 02:30.750 --> 02:33.000 So we'll select that and click on next. 65 02:33.000 --> 02:36.480 And then we'll use the data store there, local on ESXi-A, 66 02:36.480 --> 02:38.640 click on next and we'll customize it 67 02:38.640 --> 02:41.160 to put in the right segment and then we'll power it on 68 02:41.160 --> 02:42.210 when we're done with that. 69 02:42.210 --> 02:43.470 And we'll click on next. 70 02:43.470 --> 02:45.080 And so we wanna put this on segment 20. 71 02:45.080 --> 02:48.690 So we'll browse, click on segment 20, click on okay. 72 02:48.690 --> 02:49.620 And then just confirm 73 02:49.620 --> 02:51.810 that we have the right network segment, which we do. 74 02:51.810 --> 02:53.100 And we'll click on next. 75 02:53.100 --> 02:54.990 That all looks good, we'll click on finish 76 02:54.990 --> 02:56.880 and we'll do it one more time for the second VM 77 02:56.880 --> 02:58.740 that we're gonna put on that pink segment. 78 02:58.740 --> 03:00.750 So right click on our template. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 78 02:58.740 --> 03:00.750 So right click on our template. 79 03:00.750 --> 03:03.480 From the menu, we'll click new VM from this template. 80 03:03.480 --> 03:06.930 So we'll give it the name VM B 20.0.0.21, 81 03:06.930 --> 03:08.610 and then we'll make sure we put that in a folder 82 03:08.610 --> 03:09.810 called VMs for testing. 83 03:09.810 --> 03:10.643 Click on next. 84 03:10.643 --> 03:14.370 And then we wanna put this on the compute resource of ESXi-B 85 03:14.370 --> 03:15.780 and click on next. 86 03:15.780 --> 03:17.340 We'll use the local data store there. 87 03:17.340 --> 03:19.260 Click on next to continue. 88 03:19.260 --> 03:20.430 We'll click customize to make sure 89 03:20.430 --> 03:21.990 we can put on the right network segment 90 03:21.990 --> 03:23.470 and then we'll have it powered on when we're done with that. 91 03:23.470 --> 03:24.930 We'll click on next. 92 03:24.930 --> 03:27.060 And then we're gonna have the network adapter one 93 03:27.060 --> 03:30.450 be placed on network Segment 20 pink. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 93 03:27.060 --> 03:30.450 be placed on network Segment 20 pink. 94 03:30.450 --> 03:33.150 We'll click on okay, and then we'll click on next. 95 03:33.150 --> 03:35.370 That all looks good. We'll click on finish. 96 03:35.370 --> 03:37.650 And then I'd like to go ahead and verify our work as well 97 03:37.650 --> 03:39.300 just to make sure we have the right VMs 98 03:39.300 --> 03:40.620 and the right host and the right segments. 99 03:40.620 --> 03:42.150 And one easy way of doing that 100 03:42.150 --> 03:44.130 is going to the networks tab up here, 101 03:44.130 --> 03:46.020 selecting the Segment 20 pink, 102 03:46.020 --> 03:48.600 and then over here clicking on VMs. 103 03:48.600 --> 03:50.610 Also for the columns, I'd like to make sure 104 03:50.610 --> 03:51.990 I have the host shown here. 105 03:51.990 --> 03:54.690 If it's not shown, you can go to manage columns down here, 106 03:54.690 --> 03:56.430 make sure that host is selected. 107 03:56.430 --> 03:59.220 And this can confirm for us that we have VM 20 here 108 03:59.220 --> 04:02.580 on ESXi-A, and VM 20 is running ESXi-B WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 108 03:59.220 --> 04:02.580 on ESXi-A, and VM 20 is running ESXi-B 109 04:02.580 --> 04:04.770 and they're both connected to segment 20 110 04:04.770 --> 04:06.660 'cause that's where we started from over here on the left. 111 04:06.660 --> 04:08.220 So with that in mind, let's go ahead 112 04:08.220 --> 04:10.470 and bring up consoles to each of those. 113 04:10.470 --> 04:14.160 So we'll bring a web console up for VM B. 114 04:14.160 --> 04:15.750 And while we're here, let's configure an IP address 115 04:15.750 --> 04:19.260 with a pseudo IF config ethernet zero. 116 04:19.260 --> 04:22.260 And we want this one to be 20.0.0.21. 117 04:22.260 --> 04:24.420 It's okay if it's gonna default to an eight bit mask. 118 04:24.420 --> 04:25.253 That'll work. 119 04:25.253 --> 04:29.460 Next, let's go ahead and open up a console for VMA 20.0.0.20 120 04:29.460 --> 04:31.560 by clicking here on Launch Web Console. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 120 04:29.460 --> 04:31.560 by clicking here on Launch Web Console. 121 04:31.560 --> 04:33.390 And we'll give it an IP address as well. 122 04:33.390 --> 04:37.200 And this IP address is gonna be 20.0.0.20 123 04:37.200 --> 04:38.520 and we'll press enter. 124 04:38.520 --> 04:40.290 And let me just confirm my work on both. 125 04:40.290 --> 04:43.470 So here is the terminal window for 20.0.0.20 126 04:43.470 --> 04:45.120 with the IP address of 20.0.0.20. 127 04:45.120 --> 04:45.953 Fantastic! 128 04:45.953 --> 04:49.440 And here is 2021 and it has the IP address of 2021. 129 04:49.440 --> 04:51.600 So let's send some traffic back and forth. 130 04:51.600 --> 04:54.060 So let's go to this PC at 20.0.0.20 131 04:54.060 --> 04:58.740 and we'll do a ping over to 20.0.0.21 and press enter. 132 04:58.740 --> 05:01.500 So that seems to be working great. We'll do a control C. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 132 04:58.740 --> 05:01.500 So that seems to be working great. We'll do a control C. 133 05:01.500 --> 05:03.510 And one other great way to verify 134 05:03.510 --> 05:06.180 whether or not connectivity is gonna work across the segment 135 05:06.180 --> 05:08.580 is by using a really cool option under plan 136 05:08.580 --> 05:11.160 and troubleshoot here in the NSX manager. 137 05:11.160 --> 05:12.000 Check this out. 138 05:12.000 --> 05:14.520 With plan and troubleshoot select over on the left, 139 05:14.520 --> 05:16.710 we're gonna click traffic analysis. 140 05:16.710 --> 05:18.780 And then for trace flow right here, 141 05:18.780 --> 05:20.850 we'll click on get started. 142 05:20.850 --> 05:22.140 And from here we have a lot of options 143 05:22.140 --> 05:23.610 for connectivity testing. 144 05:23.610 --> 05:24.690 And so what I wanna do here is 145 05:24.690 --> 05:27.750 I wanna select virtual machine on the left hand side, 146 05:27.750 --> 05:31.860 and let's go ahead and pick 20.0.0.20 as a starting point. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 146 05:27.750 --> 05:31.860 and let's go ahead and pick 20.0.0.20 as a starting point. 147 05:31.860 --> 05:34.320 I'll scroll up here, it's also showing us the details, 148 05:34.320 --> 05:36.060 including the Mac addresses involved. 149 05:36.060 --> 05:39.420 And then for the destination, we'll go ahead and also use VM 150 05:39.420 --> 05:42.620 and we'll go ahead and select 20.0.0.21. 151 05:42.620 --> 05:45.570 So this is going to do connectivity testing 152 05:45.570 --> 05:48.450 between this virtual machine and this one. 153 05:48.450 --> 05:51.090 So I'll scroll down and click on trace 154 05:51.090 --> 05:54.330 and we'll give that a moment to crank it out and it is done 155 05:54.330 --> 05:56.040 and it's giving us a beautiful representation 156 05:56.040 --> 05:59.100 of what happened so the VM here running on this host. 157 05:59.100 --> 06:01.800 So if we click on that host, it shows us that's ESXi-A. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 157 05:59.100 --> 06:01.800 So if we click on that host, it shows us that's ESXi-A. 158 06:01.800 --> 06:03.750 And if we click on this little VM, 159 06:03.750 --> 06:05.730 it shows us that's the VM at 20.0.0.20. 160 06:05.730 --> 06:06.780 Fantastic. 161 06:06.780 --> 06:09.180 Then that traffic is logically going through this segment 162 06:09.180 --> 06:12.390 and it's being delivered down to 20.0.0.21. 163 06:12.390 --> 06:14.670 It's also showing us right here with the dotted line, 164 06:14.670 --> 06:17.730 the compute resource that's supporting or running this VM. 165 06:17.730 --> 06:20.250 So if we click here, that should be ESXi-B, 166 06:20.250 --> 06:21.360 which it is fantastic. 167 06:21.360 --> 06:23.850 Then for the play by play, if we scroll up here, 168 06:23.850 --> 06:25.200 it's showing us all the details. 169 06:25.200 --> 06:28.350 So the traffic was injected here at ESXi-A 170 06:28.350 --> 06:30.090 via network adapter one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 170 06:28.350 --> 06:30.090 via network adapter one. 171 06:30.090 --> 06:30.930 Then it was processed 172 06:30.930 --> 06:32.940 through a logical distributed firewall, 173 06:32.940 --> 06:35.010 which by default permits the traffic. 174 06:35.010 --> 06:36.360 That's why I was able to go. 175 06:36.360 --> 06:38.760 And then it went to the physical network. 176 06:38.760 --> 06:40.500 So they're showing us the tunneling 177 06:40.500 --> 06:42.510 that took place from ESXi-A to B, 178 06:42.510 --> 06:45.600 starting at the tunnel endpoint for ESXi-A. 179 06:45.600 --> 06:47.790 And the endpoint of the tunnel was ESXi-B. 180 06:47.790 --> 06:52.140 And then, ESXi-B received it via that same tunnel pair 181 06:52.140 --> 06:53.070 and then we scrolled down. 182 06:53.070 --> 06:56.190 Then it logically went through a distributed firewall rule, 183 06:56.190 --> 06:59.100 which it passed because the default is allowing the traffic 184 06:59.100 --> 07:01.170 and then the traffic was delivered successfully. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 184 06:59.100 --> 07:01.170 and then the traffic was delivered successfully. 185 07:01.170 --> 07:03.540 And again, here's a graphical representation of that, 186 07:03.540 --> 07:04.710 and if you wanna see it full screen, 187 07:04.710 --> 07:06.330 we could click right here as well. 188 07:06.330 --> 07:08.970 And that shows us a full screen and you can actually zoom in 189 07:08.970 --> 07:11.070 and add on that as well as needed. 190 07:11.070 --> 07:12.930 Now also, because we had some traffic 191 07:12.930 --> 07:14.760 actually going over our tunnels, 192 07:14.760 --> 07:16.500 we go back to system up here on top 193 07:16.500 --> 07:19.290 and on the left if we expand our fabric section right here 194 07:19.290 --> 07:20.880 and look at hosts, and I'll go ahead 195 07:20.880 --> 07:22.080 and minimize that left hand column. 196 07:22.080 --> 07:24.360 So we're looking at host transport nodes. 197 07:24.360 --> 07:27.030 They'll expand the cluster where ESXi-A and B are. 198 07:27.030 --> 07:28.500 Now it's also gonna show us 199 07:28.500 --> 07:30.210 that we have tunnels that are up. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 199 07:28.500 --> 07:30.210 that we have tunnels that are up. 200 07:30.210 --> 07:32.070 So if we click here on the tunnels, 201 07:32.070 --> 07:34.800 here, we have a tunnel from ESXi-A's perspective 202 07:34.800 --> 07:37.890 starting at 11.11.11 going over to 22, et cetera. 203 07:37.890 --> 07:40.290 And that tunnel is up, and that's the GENEVE tunnel. 204 07:40.290 --> 07:43.680 And the endpoint on the local side is VM K10. 205 07:43.680 --> 07:46.080 That's the logical layer three interface 206 07:46.080 --> 07:48.360 that ESXi is using for that end of the tunnel. 207 07:48.360 --> 07:49.830 Another interesting note is that 208 07:49.830 --> 07:53.310 if we had not brought up VMs and we not sent traffic across, 209 07:53.310 --> 07:55.830 the tunnels are not always gonna be just generated 210 07:55.830 --> 07:57.090 just because they can be. 211 07:57.090 --> 07:59.250 They are brought up as they are needed. 212 07:59.250 --> 08:01.110 So just be aware that in a new environment, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 212 07:59.250 --> 08:01.110 So just be aware that in a new environment, 213 08:01.110 --> 08:02.520 if you're not yet setting traffic 214 08:02.520 --> 08:03.810 that needs to go over a tunnel, 215 08:03.810 --> 08:06.450 it may not bother even creating the tunnels. 216 08:06.450 --> 08:08.190 Also, I've noticed here in my lab environment 217 08:08.190 --> 08:10.860 that sometimes it may take, I don't know, a few minutes 218 08:10.860 --> 08:12.180 for the tunnel information 219 08:12.180 --> 08:14.100 to be correctly reflected right here. 220 08:14.100 --> 08:15.660 So if we go to the IP addresses, 221 08:15.660 --> 08:18.570 the IP addresses for the tunnels may show up right here. 222 08:18.570 --> 08:21.030 However, the actual tunnel itself may not show up 223 08:21.030 --> 08:24.270 for a few minutes after that tunnel has been established. 224 08:24.270 --> 08:27.330 So if we click right here on tunnels, that's a hyperlink 225 08:27.330 --> 08:29.250 that can take us back to this page as well, 226 08:29.250 --> 08:30.960 showing us the tunnel information. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 226 08:29.250 --> 08:30.960 showing us the tunnel information. 227 08:30.960 --> 08:33.990 And also because those tunnels are up and being used, 228 08:33.990 --> 08:36.930 we should be able to ping the IP addresses of those tunnels 229 08:36.930 --> 08:38.790 from the transport network. 230 08:38.790 --> 08:40.740 For example, our top of rack switches. 231 08:40.740 --> 08:43.200 So to verify that here at my top of rack switch, 232 08:43.200 --> 08:47.730 if it did a ping over to 11.11.11.11, that should work. 233 08:47.730 --> 08:50.700 Then we wanna ping ESXi-B's tunnel endpoint. 234 08:50.700 --> 08:54.660 It's at 22.22.22.22, and that works as well. 235 08:54.660 --> 08:56.700 It's also the physical network infrastructure 236 08:56.700 --> 09:00.150 that's providing the routing between the endpoints. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 236 08:56.700 --> 09:00.150 that's providing the routing between the endpoints. 237 09:00.150 --> 09:02.490 So in my lab environment, that's this catalyst switch 238 09:02.490 --> 09:04.170 providing that routing as well. 239 09:04.170 --> 09:06.870 So regarding the creation and verification now 240 09:06.870 --> 09:08.970 of our overlay segments, we are done. 241 09:08.970 --> 09:11.520 We created overlay segment 10 and overlay segment 20. 242 09:11.520 --> 09:13.890 We connected the VMs, we verified connectivity. 243 09:13.890 --> 09:16.470 We went to the command line with the NSX CLI 244 09:16.470 --> 09:19.440 both at an ESXi host and also at the NSX manager, 245 09:19.440 --> 09:21.330 just to verify the details there. 246 09:21.330 --> 09:23.160 And also to confirm, the NSX is acting 247 09:23.160 --> 09:25.140 as the centralized control plane 248 09:25.140 --> 09:27.270 and that the respective transport nodes 249 09:27.270 --> 09:29.070 are gonna have a local control plane 250 09:29.070 --> 09:30.720 with the information that they need WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 250 09:29.070 --> 09:30.720 with the information that they need 251 09:30.720 --> 09:33.360 regarding forwarding like Mac tables and so forth. 252 09:33.360 --> 09:36.450 So now that we've deployed two NSX overlay segments, 253 09:36.450 --> 09:37.320 we can think of them like 254 09:37.320 --> 09:40.050 two logical layer 2 broadcast domains, 255 09:40.050 --> 09:41.790 even though we may have to in the background, 256 09:41.790 --> 09:42.930 do some tunneling between them. 257 09:42.930 --> 09:46.440 The next challenge is what about if we need clients 258 09:46.440 --> 09:50.040 on the 10 network segment 10 to be able to access devices 259 09:50.040 --> 09:53.730 or VMs over on segment 20, how do we route between them? 260 09:53.730 --> 09:55.710 And the answer is we're gonna use a router, 261 09:55.710 --> 09:57.960 but we're not gonna use a top of rack router to do that 262 09:57.960 --> 10:00.900 because the top of rack router on the physical network WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 262 09:57.960 --> 10:00.900 because the top of rack router on the physical network 263 10:00.900 --> 10:03.270 is only dealing with the physical stuff. 264 10:03.270 --> 10:07.320 And our overlay segments are purely a construct of NSX. 265 10:07.320 --> 10:09.510 So as we proceed forward together 266 10:09.510 --> 10:10.890 in building the infrastructure, 267 10:10.890 --> 10:13.680 we can then proceed to the next step of actually carving out 268 10:13.680 --> 10:16.200 and setting up those logical layer 3 routers 269 10:16.200 --> 10:19.230 or in the world of NSX, referred to as gateways. 270 10:19.230 --> 10:22.383 So we have all that to look forward to together.