WEBVTT 1 00:00.000 --> 00:03.420 So for the matching exercise right above this video, 2 00:03.420 --> 00:04.770 I wanted to take just a minute right now 3 00:04.770 --> 00:06.630 and review our answers together. 4 00:06.630 --> 00:09.360 So regarding these components, an overlay segment. 5 00:09.360 --> 00:12.270 An overlay segment really is a layer two 6 00:12.270 --> 00:14.100 logical broadcast domain. 7 00:14.100 --> 00:16.290 And think of a broadcast domain like a VLAN 8 00:16.290 --> 00:19.170 where if a broadcast is sent at layer two 9 00:19.170 --> 00:21.810 into that network segment it's gonna be forwarded 10 00:21.810 --> 00:24.420 or propagated to all other devices 11 00:24.420 --> 00:26.910 that are in that same logical broadcast domain. 12 00:26.910 --> 00:29.850 So just like a VLAN is a broadcast domain 13 00:29.850 --> 00:31.020 or a subsection if you will, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:29.850 --> 00:31.020 or a subsection if you will, 14 00:31.020 --> 00:33.240 of a physical switch like a separate room 15 00:33.240 --> 00:34.470 instead of a building. 16 00:34.470 --> 00:37.290 At layer two when we implement overlay segments 17 00:37.290 --> 00:38.520 instead of NSX, 18 00:38.520 --> 00:39.990 each of those overlay segments 19 00:39.990 --> 00:43.380 is also a logical layer two broadcast domain. 20 00:43.380 --> 00:45.030 And here's an example if this VM here, 21 00:45.030 --> 00:48.030 we'll call that VMA is being hosted on ESXi-A 22 00:48.030 --> 00:49.620 and it's connected to this logical segment 23 00:49.620 --> 00:50.790 called Segment 10. 24 00:50.790 --> 00:52.696 And then over here on ESXi-B 25 00:52.696 --> 00:55.140 for another VM over here is also connected 26 00:55.140 --> 00:56.700 to that same logical segment. 27 00:56.700 --> 00:58.900 VMA over here and VMB over here 28 00:58.900 --> 01:02.037 are both in the same layer two broadcast domain. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 28 00:58.900 --> 01:02.037 are both in the same layer two broadcast domain. 29 01:02.037 --> 01:04.170 And the same would be true for these two VMs here. 30 01:04.170 --> 01:07.110 If this was VMC, for example, and VMD 31 01:07.110 --> 01:10.230 and VMC is being hosted on ESXi-A over here, 32 01:10.230 --> 01:12.780 but connected to this logical segment called Segment 20. 33 01:12.780 --> 01:16.020 And over here VMD is being hosted by ESXi-B 34 01:16.020 --> 01:17.850 and is connected to this logical segment. 35 01:17.850 --> 01:20.602 Then VMC and VMD are both in the same 36 01:20.602 --> 01:23.010 layer two logical broadcast domain. 37 01:23.010 --> 01:26.910 So if this VM here VMC sent a broadcast in the network, 38 01:26.910 --> 01:30.810 that broadcast should be seen over by VMD over here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 38 01:26.910 --> 01:30.810 that broadcast should be seen over by VMD over here, 39 01:30.810 --> 01:31.830 over on ESXi-B. 40 01:31.830 --> 01:33.540 Now behind the scenes to make that all happen, 41 01:33.540 --> 01:36.540 ESXi-A would be forwarding that over the tunnel 42 01:36.540 --> 01:37.920 using GENEVE for encapsulation 43 01:37.920 --> 01:39.660 and send that information over the tunnel 44 01:39.660 --> 01:41.550 where ESXi-B would deencapsulate it 45 01:41.550 --> 01:43.320 and then forward it to the destination. 46 01:43.320 --> 01:45.589 Or in the case of layer two broadcast that destinations 47 01:45.589 --> 01:48.330 where that layer two broadcast need to be sent. 48 01:48.330 --> 01:50.400 So this topology, everybody in segment 20 49 01:50.400 --> 01:53.130 sees all the broadcasts for segment 20 50 01:53.130 --> 01:55.290 and everybody in segment 10 sees the broadcast 51 01:55.290 --> 01:56.730 associated with VLAN 10. 52 01:56.730 --> 01:59.131 Now there are some shortcuts as well that can be taken 53 01:59.131 --> 02:00.630 by the ESXi host. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 53 01:59.131 --> 02:00.630 by the ESXi host. 54 02:00.630 --> 02:04.920 For example, if there's an ARP request that VMA is making 55 02:04.920 --> 02:07.999 and ESXi-A knows exactly where that layer two address lives, 56 02:07.999 --> 02:10.440 it can go ahead and respond back to VMA 57 02:10.440 --> 02:12.300 and answer that ARP response 58 02:12.300 --> 02:14.430 without actually sending that traffic over the tunnel. 59 02:14.430 --> 02:17.400 But that's due to the control plane here of the NSX manager 60 02:17.400 --> 02:20.010 and it populating the ESXi transport nodes 61 02:20.010 --> 02:22.140 regarding where those MAC addresses live. 62 02:22.140 --> 02:23.799 But at the end of the day, an overlay segment 63 02:23.799 --> 02:26.325 is like a layer two broadcast domain. 64 02:26.325 --> 02:29.730 And that concept of the common layer two broadcast domain 65 02:29.730 --> 02:31.740 also leads us to this third option, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 65 02:29.730 --> 02:31.740 also leads us to this third option, 66 02:31.740 --> 02:33.120 which is part of our matching, 67 02:33.120 --> 02:35.280 which is VMs that should be on the same segment 68 02:35.280 --> 02:36.600 are VMs that are connected 69 02:36.600 --> 02:39.090 to the same layer two broadcast domain. 70 02:39.090 --> 02:41.997 So any VMs for example, VMA here 71 02:41.997 --> 02:43.518 and VMB here, if they're both connected 72 02:43.518 --> 02:45.274 to the overlay segment 10, 73 02:45.274 --> 02:48.300 they're both in the same layer two broadcast domain. 74 02:48.300 --> 02:50.910 And as a result, they should also at layer three 75 02:50.910 --> 02:53.190 have a IP address on the same subnet. 76 02:53.190 --> 02:57.597 So if we have a 10.10.10 network with a slash 24. 77 02:57.597 --> 02:59.400 Over here this one could be 78 02:59.400 --> 03:02.157 for example 10.10.10.50. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 78 02:59.400 --> 03:02.157 for example 10.10.10.50. 79 03:02.157 --> 03:05.850 And over here this could be 10.10.10.51 80 03:05.850 --> 03:09.210 both in the same layer three subnet of 10 10 zero. 81 03:09.210 --> 03:10.590 So I'm just gonna draw a little arrow here 82 03:10.590 --> 03:12.240 just to reinforce that Vms 83 03:12.240 --> 03:14.550 who are in the same layer two broadcast domain 84 03:14.550 --> 03:17.370 at layer two should also have an IP address 85 03:17.370 --> 03:19.080 in the same subnet at layer three. 86 03:19.080 --> 03:20.910 So lemme clean that up a little bit. 87 03:20.910 --> 03:23.564 And one of the matching options in the question above 88 03:23.564 --> 03:25.560 was about the IP address that's used 89 03:25.560 --> 03:27.450 to reach the other end of a GENEVE tunnel. 90 03:27.450 --> 03:29.523 And that IP address associated with the GENEVE tunnel 91 03:29.523 --> 03:31.760 is the tunnel endpoint address. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 91 03:29.523 --> 03:31.760 is the tunnel endpoint address. 92 03:31.760 --> 03:34.170 So here in this topology, this tunnel endpoint address, 93 03:34.170 --> 03:36.357 here on ESXi-A is at 11.111.11.11. 94 03:36.357 --> 03:39.960 And over here in ESXi-B it's 22.22.22.22. 95 03:39.960 --> 03:41.760 And if we were to look at the VM kernel adapters 96 03:41.760 --> 03:44.478 on each of these hosts, we would find a VM kernel adapter 97 03:44.478 --> 03:46.768 with that associated IP address. 98 03:46.768 --> 03:48.990 So this host is using the VM kernel adapter 99 03:48.990 --> 03:51.810 and it's corresponding IP address for the tunnel endpoint 100 03:51.810 --> 03:54.180 for the logical communication over the transport network 101 03:54.180 --> 03:55.500 as they send data back and forth, 102 03:55.500 --> 03:58.440 for example, from ESXi-A encapsulating the data 103 03:58.440 --> 04:00.390 and sending it over to ESXi-B. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 103 03:58.440 --> 04:00.390 and sending it over to ESXi-B. 104 04:00.390 --> 04:03.030 And then there was a couple matches about this option here 105 04:03.030 --> 04:05.220 of get segments and this option here 106 04:05.220 --> 04:06.780 about get logical switches. 107 04:06.780 --> 04:09.085 And just to confirm that in the world of NSX, 108 04:09.085 --> 04:11.460 let's head over to the command lane interface 109 04:11.460 --> 04:13.470 over here on ESXi-A. 110 04:13.470 --> 04:16.530 So here on ESXi-A, I've got an SSH session open 111 04:16.530 --> 04:18.180 to go into the NSX cli, 112 04:18.180 --> 04:20.790 we'll type in nsxcli, press enter. 113 04:20.790 --> 04:23.280 And boom, now we're at the nsxcli 114 04:23.280 --> 04:25.260 on this host transport node. 115 04:25.260 --> 04:27.150 So here, if we do the command get segments 116 04:27.150 --> 04:29.250 and press center, it's currently showing me 117 04:29.250 --> 04:30.731 that on this ESXi host, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 117 04:29.250 --> 04:30.731 that on this ESXi host, 118 04:30.731 --> 04:34.653 it has no logical segments associated with it. 119 04:35.501 --> 04:36.334 (laughs lightly) 120 04:36.334 --> 04:37.260 And I'm a little shocked. I'm like, whoa, why is that? 121 04:37.260 --> 04:39.960 And the reason here that it's showing those segments 122 04:39.960 --> 04:40.793 is because at the moment 123 04:40.793 --> 04:42.949 I'm doing this demonstration of this review, 124 04:42.949 --> 04:45.540 there are no VMs that are running 125 04:45.540 --> 04:47.279 that are attached to any of our segments. 126 04:47.279 --> 04:49.560 So I also recommend, let's just go ahead 127 04:49.560 --> 04:52.110 and power up a couple VMs and then come back 128 04:52.110 --> 04:52.943 and take a look here on ESXi-A 129 04:52.943 --> 04:57.210 and see whether or not it now knows about a segment. 130 04:57.210 --> 04:58.560 So here on the vSphere client, 131 04:58.560 --> 05:00.540 let's click on the network tab right here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 131 04:58.560 --> 05:00.540 let's click on the network tab right here. 132 05:00.540 --> 05:01.639 Let's go down to segment 10 133 05:01.639 --> 05:05.190 and let's identify a VM that's both connected to segment 10 134 05:05.190 --> 05:07.320 and also it's running on ESXi-A 135 05:07.320 --> 05:08.880 or will be once we powered on. 136 05:08.880 --> 05:10.620 So at the moment, this VM right here 137 05:10.620 --> 05:12.360 is not currently powered on. 138 05:12.360 --> 05:15.030 So we'll select it, we'll go ahead and we'll right click 139 05:15.030 --> 05:17.250 and we'll click on power and then power it on. 140 05:17.250 --> 05:20.730 And so now that this VM is now gonna be powered up 141 05:20.730 --> 05:23.646 and is connected to this segment, segment 10 yellow, 142 05:23.646 --> 05:27.450 if we go back now to the nsxcli on ESXi-A. 143 05:27.450 --> 05:29.123 ESXi-A is now gonna be aware 144 05:29.123 --> 05:31.170 of that layer two broadcast domain, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 144 05:29.123 --> 05:31.170 of that layer two broadcast domain, 145 05:31.170 --> 05:33.120 this segment called Seg 10 yellow. 146 05:33.120 --> 05:35.460 So let's go back to the cli and verify that. 147 05:35.460 --> 05:37.890 So back at the cli, my hands will never leave my arms. 148 05:37.890 --> 05:39.000 We'll simply hit the up arrow key. 149 05:39.000 --> 05:42.300 For get segments, press enter and baa bing baa boom. 150 05:42.300 --> 05:44.250 It now knows about this VNI 151 05:44.250 --> 05:46.636 is virtual network identifier for this segment. 152 05:46.636 --> 05:48.690 Here's the UUID for that segment 153 05:48.690 --> 05:51.090 and there's its name Seg 10 yellow. 154 05:51.090 --> 05:53.670 Now synonymous with this command of get segments, 155 05:53.670 --> 05:57.240 we could use the older command of get logical switches. 156 05:57.240 --> 05:59.504 Just like that to show us the logical switches. 157 05:59.504 --> 06:01.710 And that's also gonna show us the same logical switch. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 157 05:59.504 --> 06:01.710 And that's also gonna show us the same logical switch. 158 06:01.710 --> 06:05.079 So here we have the same VNI number, we have the same UUID, 159 06:05.079 --> 06:06.750 and we also have the same name. 160 06:06.750 --> 06:09.090 So even though the commands are being migrated 161 06:09.090 --> 06:12.284 from the logical dash switches over to the command segments, 162 06:12.284 --> 06:14.370 we still have a lot of backwards compatibility 163 06:14.370 --> 06:15.480 with the older set. 164 06:15.480 --> 06:16.440 And as of this recording, 165 06:16.440 --> 06:19.830 I'm in the version 4.1 X flavor of NSX. 166 06:19.830 --> 06:20.910 So for our matching game, 167 06:20.910 --> 06:22.050 the command get segments 168 06:22.050 --> 06:24.138 is synonymous with get logical switches 169 06:24.138 --> 06:26.370 and the command get logical switches 170 06:26.370 --> 06:28.080 is synonymous with get segments. 171 06:28.080 --> 06:30.810 So those two can be used interchangeably. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 171 06:28.080 --> 06:30.810 So those two can be used interchangeably. 172 06:30.810 --> 06:32.675 So thanks for joining me in this skill 173 06:32.675 --> 06:36.060 regarding deploying some NSX overlay segments 174 06:36.060 --> 06:37.095 and also verifying them. 175 06:37.095 --> 06:40.080 And I'll see you my friend, in the very next skill. 176 06:40.080 --> 06:42.450 Until then, I hope this has been informative 177 06:42.450 --> 06:44.793 and I'd like to thank you for viewing.