WEBVTT 1 00:00.240 --> 00:01.440 Let's go ahead and take a look 2 00:01.440 --> 00:02.670 at our current topology 3 00:02.670 --> 00:06.120 at exactly what uplink profiles are being used 4 00:06.120 --> 00:08.190 by ESXI-A and ESXI-B, 5 00:08.190 --> 00:10.440 and then we can go back in and document it right here. 6 00:10.440 --> 00:12.120 So here in the NSX Manager, 7 00:12.120 --> 00:13.680 we're currently on the System tab. 8 00:13.680 --> 00:15.990 And then under Fabric we're looking at the hosts. 9 00:15.990 --> 00:18.000 I'm gonna go ahead and collapse this column over to the left 10 00:18.000 --> 00:20.070 to give us a little more real estate right here. 11 00:20.070 --> 00:22.560 And let's take a look at the details for ESXI-A. 12 00:22.560 --> 00:24.390 So we could either go in and start editing it 13 00:24.390 --> 00:27.150 or we could click right here on View Details. 14 00:27.150 --> 00:28.500 Either way would be great. 15 00:28.500 --> 00:30.420 So for the details of this E ESXI host, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 15 00:28.500 --> 00:30.420 So for the details of this E ESXI host, 16 00:30.420 --> 00:31.350 if we scroll to the right, 17 00:31.350 --> 00:33.363 and then I'm gonna use the right arrow there. 18 00:33.363 --> 00:35.640 It's showing us which uplink we're using. 19 00:35.640 --> 00:36.690 So we can see right here 20 00:36.690 --> 00:39.210 that it's using vmnic2 as its uplink. 21 00:39.210 --> 00:41.910 And if we click over here on Host Switch right there, 22 00:41.910 --> 00:43.410 so this is a hyperlink, 23 00:43.410 --> 00:45.390 it'll show us the details about the host switch. 24 00:45.390 --> 00:47.460 And right there it's showing us the uplink profile. 25 00:47.460 --> 00:48.780 So if we expand that, 26 00:48.780 --> 00:53.430 it's using the uplink profile called v101 vmnic 2. 27 00:53.430 --> 00:55.590 So that's the name of the uplink profile. 28 00:55.590 --> 00:58.950 And here it's showing us the logical name in NSX 29 00:58.950 --> 01:01.050 and the uplink on the distributed switch WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 29 00:58.950 --> 01:01.050 and the uplink on the distributed switch 30 01:01.050 --> 01:04.320 that again leads to a physical uplink on an ESXI host. 31 01:04.320 --> 01:05.280 And that's right here. 32 01:05.280 --> 01:06.900 So here it's confirming the uplink. 33 01:06.900 --> 01:09.450 and to verify exactly which VLAN we're using, 34 01:09.450 --> 01:12.240 Let's go take a closer look at that uplink profile 35 01:12.240 --> 01:14.880 that ESXI-A is currently using. 36 01:14.880 --> 01:16.140 So to do that, I'll go ahead 37 01:16.140 --> 01:19.260 and close the detailed view here of ESXI-A 38 01:19.260 --> 01:21.120 and I'll expand the left-hand side. 39 01:21.120 --> 01:24.060 So still on the System tab up here on the left 40 01:24.060 --> 01:27.030 in the Fabric section, let's go down to Profiles. 41 01:27.030 --> 01:28.770 And the profile that we had associated with that 42 01:28.770 --> 01:29.640 was this one right here. 43 01:29.640 --> 01:31.290 I made a whole bunch just so we could easily WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 43 01:29.640 --> 01:31.290 I made a whole bunch just so we could easily 44 01:31.290 --> 01:32.640 swap them out if we need to. 45 01:32.640 --> 01:36.510 So this is the uplink profile called v101 vmnic 2. 46 01:36.510 --> 01:38.070 I named it that when I created it. 47 01:38.070 --> 01:39.480 And if we expand that, 48 01:39.480 --> 01:41.580 and here it's confirming for us for the transport VLAN, 49 01:41.580 --> 01:44.760 that's the VLAN that's gonna be supporting the endpoints 50 01:44.760 --> 01:47.187 for our tunnels, it's gonna be using VLAN 101. 51 01:47.187 --> 01:48.930 And so if we scroll down here, 52 01:48.930 --> 01:52.470 here we have the label in NSX called vmnic2. 53 01:52.470 --> 01:54.390 And then when we configured ESXI-A 54 01:54.390 --> 01:56.790 and we associated this uplink profile with it, 55 01:56.790 --> 02:00.780 we also mapped this logical name right here, vmnic2, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 55 01:56.790 --> 02:00.780 we also mapped this logical name right here, vmnic2, 56 02:00.780 --> 02:03.450 with the uplink name on the distributed switch. 57 02:03.450 --> 02:05.550 So what that means is that we are using uplink 2. 58 02:05.550 --> 02:06.930 I'll go ahead and circle that. 59 02:06.930 --> 02:09.540 And as we send frames into the physical network, 60 02:09.540 --> 02:13.260 we're adding the 802.1Q tag of 101. 61 02:13.260 --> 02:15.810 And that way when the physical infrastructure, 62 02:15.810 --> 02:18.000 in our case, the top-of-rack switch receives that, 63 02:18.000 --> 02:19.740 and again this port is trunking, 64 02:19.740 --> 02:21.930 it'll then know that that frame is associated with 65 02:21.930 --> 02:24.300 and belongs to VLAN 101. 66 02:24.300 --> 02:27.000 Also, let's take a quick peek at ESXI-B 67 02:27.000 --> 02:30.210 just to verify which uplinks and VLANs it's using. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 67 02:27.000 --> 02:30.210 just to verify which uplinks and VLANs it's using. 68 02:30.210 --> 02:31.350 And based on that IP address 69 02:31.350 --> 02:32.640 that we're using on the tunnel endpoint, 70 02:32.640 --> 02:33.920 that is not in the same VLANs. 71 02:33.920 --> 02:35.100 So let's go take a look. 72 02:35.100 --> 02:36.780 So back to the NSX Manager we go 73 02:36.780 --> 02:38.370 with the System tab selected. 74 02:38.370 --> 02:40.560 Let's go under Fabric and click on Host, 75 02:40.560 --> 02:42.570 which is gonna show us not only our host 76 02:42.570 --> 02:45.000 but also those hosts that have been configured 77 02:45.000 --> 02:47.730 as ESXI host transport nodes. 78 02:47.730 --> 02:49.740 So here is ESXI-B right here. 79 02:49.740 --> 02:51.570 We'll go ahead and scroll to the right a little bit 80 02:51.570 --> 02:54.150 and click on View Details for ESXI-B. 81 02:54.150 --> 02:56.250 And here is a visual. Fantastic. 82 02:56.250 --> 02:57.480 We'll scroll to the right. 83 02:57.480 --> 02:58.350 And here for Host Switch, 84 02:58.350 --> 02:59.940 if we click on the hyperlink there, 85 02:59.940 --> 03:02.730 this is showing us that we're using an uplink profile WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 85 02:59.940 --> 03:02.730 this is showing us that we're using an uplink profile 86 03:02.730 --> 03:05.090 called v102 with vmnic 2. 87 03:05.090 --> 03:07.110 So we already verified the actual uplink. 88 03:07.110 --> 03:08.970 And based on the uplink profile, 89 03:08.970 --> 03:13.380 that one very likely is saying use VLAN 102 for the tagging. 90 03:13.380 --> 03:16.320 So to confirm that, we can go to Close, close that, 91 03:16.320 --> 03:18.000 and then go down to Profiles. 92 03:18.000 --> 03:20.700 Again, that's under System and Profiles. 93 03:20.700 --> 03:23.580 And there is v102 vmnic 2, 94 03:23.580 --> 03:27.180 which indeed is using Transport VLAN 102. 95 03:27.180 --> 03:30.180 So let's document that on our topology as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 95 03:27.180 --> 03:30.180 So let's document that on our topology as well. 96 03:30.180 --> 03:33.960 So over here on ESXI-B, it's using vmnic2. 97 03:33.960 --> 03:35.850 To go to its top-of-rack switch, 98 03:35.850 --> 03:37.650 AND again, that port on the top-of-rack switch 99 03:37.650 --> 03:39.720 is set up as an 802.1Q trunk. 100 03:39.720 --> 03:42.840 And the VLAN we're using is VLAN 102. 101 03:42.840 --> 03:45.090 So for 802.1Q tagging, 102 03:45.090 --> 03:46.950 for the frames that are being sent to the switch, 103 03:46.950 --> 03:48.870 it's gonna have the tag of 102. 104 03:48.870 --> 03:52.410 Also, what this implies is that for VLAN 101, 105 03:52.410 --> 03:56.520 we're using the IP adressing space of 11.11.11.0, 106 03:56.520 --> 03:57.750 with a 24-bit mask 107 03:57.750 --> 03:59.880 based on what we saw earlier at the switch. 108 03:59.880 --> 04:03.390 And for VLAN 102, we're using the IP address base WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 108 03:59.880 --> 04:03.390 And for VLAN 102, we're using the IP address base 109 04:03.390 --> 04:08.390 of 22.22,.22.0 with a 24-bit mask. 110 04:08.970 --> 04:11.040 And we have a routing function in the physical network 111 04:11.040 --> 04:12.570 between those two subnets. 112 04:12.570 --> 04:13.830 Also, in a production environment, 113 04:13.830 --> 04:15.000 it's super likely we're gonna have 114 04:15.000 --> 04:16.110 a whole bunch of redundancy here. 115 04:16.110 --> 04:17.490 So if we had, for example, 116 04:17.490 --> 04:21.030 three or four spine-layer switches, 117 04:21.030 --> 04:23.580 so I'll go ahead and draw this as a spine-layer switch, 118 04:23.580 --> 04:25.440 if we had, you know, some others here, 119 04:25.440 --> 04:29.100 we'll call this A and B and C, 120 04:29.100 --> 04:30.900 we would have full connectivity WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 120 04:29.100 --> 04:30.900 we would have full connectivity 121 04:30.900 --> 04:33.540 from each of our leaf-layer devices 122 04:33.540 --> 04:35.760 to each of our spine-layer devices. 123 04:35.760 --> 04:38.520 So we'd also have connections from this spine 124 04:38.520 --> 04:41.460 over to this leaf and this spine to this leaf. 125 04:41.460 --> 04:43.770 So every leaf is gonna have a full set of connections 126 04:43.770 --> 04:45.720 to all the spine-layer devices. 127 04:45.720 --> 04:46.770 And all these spine switches 128 04:46.770 --> 04:48.630 are gonna have a full compliment of connections 129 04:48.630 --> 04:50.460 to all the leaf switches. 130 04:50.460 --> 04:51.900 And what we are not going to implement 131 04:51.900 --> 04:53.550 in a spine-leaf architecture 132 04:53.550 --> 04:56.760 is we are not gonna connect two leaf switches 133 04:56.760 --> 04:57.810 directly together. 134 04:57.810 --> 04:59.670 So that part we don't implement physically 135 04:59.670 --> 05:01.140 or logically for that matter. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 135 04:59.670 --> 05:01.140 or logically for that matter. 136 05:01.140 --> 05:02.700 So let me go ahead and remove it. 137 05:02.700 --> 05:03.720 And that helps us to make sure 138 05:03.720 --> 05:05.910 that we have a scalable spine-leaf architecture. 139 05:05.910 --> 05:07.800 So if this switch right here, 140 05:07.800 --> 05:09.930 we'll call it top-of-rack switch A, 141 05:09.930 --> 05:12.840 needs to talk to top-of-rack switch B over here, 142 05:12.840 --> 05:16.380 these two top-of-rack switches acting at the leaf layer 143 05:16.380 --> 05:18.060 are gonna have to be forwarded through a switch, 144 05:18.060 --> 05:20.520 which is providing routing functionality from a switch 145 05:20.520 --> 05:21.750 that's in the spine layer. 146 05:21.750 --> 05:23.010 So I thought that would be helpful 147 05:23.010 --> 05:24.570 just to confirm and document, 148 05:24.570 --> 05:26.490 so that way there's less of a mystery 149 05:26.490 --> 05:28.650 on the physical infrastructure 150 05:28.650 --> 05:30.330 as far as the transport network WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 150 05:28.650 --> 05:30.330 as far as the transport network 151 05:30.330 --> 05:32.070 forwarding traffic back and forth. 152 05:32.070 --> 05:33.960 So lemme clean that up just a little bit. 153 05:33.960 --> 05:36.780 So with ESXI-A and ESXI-B over here, 154 05:36.780 --> 05:40.560 ESXI-A is using for its uplink the vmnic2 155 05:40.560 --> 05:44.130 and using VLAN 101 for the transport network connectivity, 156 05:44.130 --> 05:49.130 and ESXI-B is using its vmnic2 here and VLAN 102. 157 05:49.350 --> 05:51.180 Also, now that we've confirmed and documented that, 158 05:51.180 --> 05:52.950 lemme clean that up a little bit as well. 159 05:52.950 --> 05:55.140 Now, our objective for this set of videos 160 05:55.140 --> 05:58.500 is to implement a couple of overlay segments. 161 05:58.500 --> 05:59.340 So here's what we're gonna do. 162 05:59.340 --> 06:01.500 We're gonna implement overlay segment 10, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 162 05:59.340 --> 06:01.500 We're gonna implement overlay segment 10, 163 06:01.500 --> 06:03.210 which is in this yellow color here. 164 06:03.210 --> 06:06.240 And we're also gonna implement an overlay segment called 20. 165 06:06.240 --> 06:08.730 And from a vSphere perspective, 166 06:08.730 --> 06:10.980 it kinda looks like just a port group 167 06:10.980 --> 06:12.480 on a distributed switch; 168 06:12.480 --> 06:15.390 although because it's an overlay segment provided by NSX, 169 06:15.390 --> 06:17.550 these two ESXI hosts don't have to be 170 06:17.550 --> 06:20.130 on the common same layer 2 broadcast domain. 171 06:20.130 --> 06:22.080 They can be racks away from each other 172 06:22.080 --> 06:25.050 or even physical locations away from each other, 173 06:25.050 --> 06:26.550 and then they can take the traffic 174 06:26.550 --> 06:28.500 and tunnel it as needed to go back and forth. 175 06:28.500 --> 06:31.200 So as an example, let's imagine we have this VM right here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 175 06:28.500 --> 06:31.200 So as an example, let's imagine we have this VM right here 176 06:31.200 --> 06:34.020 that's gonna be connected to segment 10, 177 06:34.020 --> 06:35.160 and this VM right here 178 06:35.160 --> 06:37.650 which is gonna be connected to segment 20. 179 06:37.650 --> 06:40.500 And these two VMs are being hosted on ESXI-A. 180 06:40.500 --> 06:42.330 And then over here on ESXI-B, 181 06:42.330 --> 06:44.400 it's also hosting a couple of VMs. 182 06:44.400 --> 06:46.860 And for this VM we'll connect it to the segment 10. 183 06:46.860 --> 06:50.400 And for this VM we'll connect it to the NSX segment 20, 184 06:50.400 --> 06:51.233 just like that. 185 06:51.233 --> 06:54.210 And there's something magical that has to be put in place 186 06:54.210 --> 06:56.250 IF we want an IP network to function. 187 06:56.250 --> 06:59.790 And that magical element is IP addresses. 188 06:59.790 --> 07:02.160 So let's put a plan for that together as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 188 06:59.790 --> 07:02.160 So let's put a plan for that together as well. 189 07:02.160 --> 07:04.530 So here's what I propose we do for IP addressing 190 07:04.530 --> 07:08.280 for any VMs that are connected to the overlay segment 10. 191 07:08.280 --> 07:11.460 Let's use for segment 10, we'll label that real quick there. 192 07:11.460 --> 07:13.410 And for segment 10 here in yellow, 193 07:13.410 --> 07:17.430 let's use the address space of 10.0.0.0. 194 07:17.430 --> 07:19.800 And for simplicity, let's use an eight-bit mask. 195 07:19.800 --> 07:24.210 So 10-anything, we'll use on the overlay segment called 10. 196 07:24.210 --> 07:26.550 And then for the overlay segment called 20, 197 07:26.550 --> 07:27.660 which is here in pink, 198 07:27.660 --> 07:31.800 let's go ahead and use the adressing space of 20.0.0.0, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 198 07:27.660 --> 07:31.800 let's go ahead and use the adressing space of 20.0.0.0, 199 07:31.800 --> 07:32.910 again with an eight-bit mask. 200 07:32.910 --> 07:35.250 And that way when we see 10-anything we'll realize, oh, 201 07:35.250 --> 07:37.860 that's the IP adressing space we're using on segment 10. 202 07:37.860 --> 07:39.660 If we see 20-anything, 203 07:39.660 --> 07:40.980 we'll know that's the IP adressing space 204 07:40.980 --> 07:42.690 we're using on segment 20. 205 07:42.690 --> 07:45.030 So lemme go ahead and reconnect these devices. 206 07:45.030 --> 07:47.250 So we'll put this VM on segment 10. 207 07:47.250 --> 07:49.620 We'll put this VM on segment 20. 208 07:49.620 --> 07:51.450 And similar treatment over here on the VMs 209 07:51.450 --> 07:52.560 running on ESXI-B, 210 07:52.560 --> 07:55.350 we'll put this VM right here on segment 10 211 07:55.350 --> 07:57.090 and this VM on segment 20. 212 07:57.090 --> 08:00.090 So when we associate a VM with a segment, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 212 07:57.090 --> 08:00.090 So when we associate a VM with a segment, 213 08:00.090 --> 08:01.380 from a vSphere perspective, 214 08:01.380 --> 08:04.500 it just looks like associated with a port group. 215 08:04.500 --> 08:06.990 Because in the vSphere client, that's what it looks like. 216 08:06.990 --> 08:09.000 It looks like just a logical port group 217 08:09.000 --> 08:11.010 that you could associate a vmnic with. 218 08:11.010 --> 08:12.780 Also, as part of our game plan, 219 08:12.780 --> 08:14.550 because we already have this zone, 220 08:14.550 --> 08:17.670 this transport zone called Our A-B overlay transport zone 221 08:17.670 --> 08:21.360 that ESXI and ESXI-B are associated with, 222 08:21.360 --> 08:22.470 that way, if we create, 223 08:22.470 --> 08:24.840 or when we create these two new overlay segments, 224 08:24.840 --> 08:27.120 if we associate them with this transport zone, 225 08:27.120 --> 08:28.200 they'll both be available; 226 08:28.200 --> 08:31.260 both segments will be available for both of our ESXI hosts WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 226 08:28.200 --> 08:31.260 both segments will be available for both of our ESXI hosts 227 08:31.260 --> 08:32.940 who are also supporting that zone. 228 08:32.940 --> 08:34.770 So now that we have our game plan together 229 08:34.770 --> 08:36.960 and we've verified our existing topology, 230 08:36.960 --> 08:37.950 in the next video, 231 08:37.950 --> 08:40.920 let's create our first NSX overlay segment. 232 08:40.920 --> 08:42.820 And that's gonna be segment number 10.