WEBVTT 1 00:00.220 --> 00:01.053 So, in this video, 2 00:01.053 --> 00:02.720 I'd like to walk through creating a pool 3 00:02.720 --> 00:04.120 of addresses that can be used 4 00:04.120 --> 00:06.260 if we're using VLAN 101, 5 00:06.260 --> 00:07.420 and other pool of addresses 6 00:07.420 --> 00:09.070 that we can use for tunnel endpoints 7 00:09.070 --> 00:12.797 if we're using the network 10.22.22, and VLAN 102. 8 00:12.797 --> 00:15.100 And then once we've created those pools of addresses 9 00:15.100 --> 00:16.480 that can be used, 10 00:16.480 --> 00:17.680 we'll also walk through the creation 11 00:17.680 --> 00:18.990 of some uplink profiles. 12 00:18.990 --> 00:20.429 We simply say, 13 00:20.429 --> 00:21.890 hey, which VLAN do we want to use 14 00:21.890 --> 00:23.880 for the transport network? 15 00:23.880 --> 00:25.970 And which uplinks do we want to go ahead 16 00:25.970 --> 00:28.030 and use on the ESXi hosts? 17 00:28.030 --> 00:30.550 So, to do this, we're going to log into the NSX Manager, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 17 00:28.030 --> 00:30.550 So, to do this, we're going to log into the NSX Manager, 18 00:30.550 --> 00:32.079 and we're going to use the virtual IP address 19 00:32.079 --> 00:33.390 that we set up, 20 00:33.390 --> 00:34.799 which is at .10 on the management network. 21 00:34.799 --> 00:37.600 So, I'll log in as admin, supply the password, 22 00:37.600 --> 00:39.080 and click log in. 23 00:39.080 --> 00:41.803 Also, one of the other things I definitely want to do 24 00:41.803 --> 00:42.800 before we get too far along is 25 00:42.800 --> 00:44.620 I want to make sure that this VM, 26 00:44.620 --> 00:46.460 this NSX Manager VM, 27 00:46.460 --> 00:48.840 is set to automatically power up 28 00:48.840 --> 00:50.870 when my ESXi host comes up. 29 00:50.870 --> 00:52.489 So, let's go back to the vSphere client just 30 00:52.489 --> 00:53.739 for a moment. 31 00:53.739 --> 00:54.400 And here at the vSphere client, 32 00:54.400 --> 00:56.470 go back to the host and clusters view. 33 00:56.470 --> 00:58.780 We'll go to our management cluster. 34 00:58.780 --> 01:02.320 We'll go to ESXIC, and we'll go to configure. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 34 00:58.780 --> 01:02.320 We'll go to ESXIC, and we'll go to configure. 35 01:02.320 --> 01:03.500 Then in this middle column, 36 01:03.500 --> 01:06.740 we'll go down to VM startup shutdown. 37 01:06.740 --> 01:08.320 And currently, this is showing with this tab, 38 01:08.320 --> 01:10.260 the automatic ordered and automatic. 39 01:10.260 --> 01:14.750 Yeah, this little NSX Manager VM is not set for any kind 40 01:14.750 --> 01:15.940 of automatic startup. 41 01:15.940 --> 01:18.440 So currently, it's set up for manual startup, 42 01:18.440 --> 01:20.723 which means it's not going to automatically power on 43 01:20.723 --> 01:22.870 if I have to reboot the NSX host 44 01:22.870 --> 01:24.019 for any reason. 45 01:24.019 --> 01:26.450 So, to solve that, I'm going to click on edit. 46 01:26.450 --> 01:27.750 And I'm going to go ahead and click here 47 01:27.750 --> 01:31.560 on manual startup and select the NSX Manager VM, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 47 01:27.750 --> 01:31.560 on manual startup and select the NSX Manager VM, 48 01:31.560 --> 01:34.420 where the automatic startup is currently disabled. 49 01:34.420 --> 01:36.830 And I'm going to go ahead and click here on move to. 50 01:36.830 --> 01:40.090 And I want to move this to the automatic ordered. 51 01:40.090 --> 01:41.440 So, it's removed from this list now. 52 01:41.440 --> 01:43.270 Now it's under the automatic order 53 01:43.270 --> 01:45.549 and it's in startup order number one. 54 01:45.549 --> 01:46.909 Fantastic. 55 01:46.909 --> 01:48.480 So, I want to make that change before we go any further 56 01:48.480 --> 01:50.230 because it can take like 10 to 15 minutes 57 01:50.230 --> 01:51.930 for this little VM to fully initialize. 58 01:51.930 --> 01:54.600 And so, if it automatically is going to start it every time 59 01:54.600 --> 01:56.430 the host is rebooted, 60 01:56.430 --> 01:57.590 it's going to save me some frustration later. 61 01:57.590 --> 02:00.130 So, with that set, I'll click on OK. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 61 01:57.590 --> 02:00.130 So, with that set, I'll click on OK. 62 02:00.130 --> 02:01.340 And then just to verify here, 63 02:01.340 --> 02:02.830 if we click on the automatic ordered, 64 02:02.830 --> 02:04.010 it's showing up right there. 65 02:04.010 --> 02:05.059 That looks great. 66 02:05.059 --> 02:06.766 All right, so what we want to do is go back 67 02:06.766 --> 02:08.270 to the NSX Manager. 68 02:08.270 --> 02:10.009 So, here we have the NSX Manager. 69 02:10.009 --> 02:13.370 And let's go ahead and create some IP pools. 70 02:13.370 --> 02:14.870 So, to do that, we're going to click 71 02:14.870 --> 02:17.690 on the networking tab right here at the top. 72 02:17.690 --> 02:19.830 Here is giving us a nice network overview. 73 02:19.830 --> 02:21.570 We have pretty much nothing going on 74 02:21.570 --> 02:24.010 as far as layer three routing or anything else. 75 02:24.010 --> 02:26.010 So, what we're going to scroll down on the left, 76 02:26.010 --> 02:27.650 we're going to go down under IP management 77 02:27.650 --> 02:30.120 and click right here on IP address pools. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 77 02:27.650 --> 02:30.120 and click right here on IP address pools. 78 02:30.120 --> 02:32.309 And then there's no IP address pools by default. 79 02:32.309 --> 02:34.139 So, let's go ahead and create some. 80 02:34.139 --> 02:36.670 So, click here on add IP address pool. 81 02:36.670 --> 02:38.020 And let's name this pool. 82 02:38.020 --> 02:40.480 I'm going to go ahead and call it 10.11.11. 83 02:40.480 --> 02:42.620 So, I'll remember what it is just by looking at it. 84 02:42.620 --> 02:43.740 And then we'll click right here 85 02:43.740 --> 02:45.940 on set underneath the subnets column. 86 02:45.940 --> 02:47.540 We'll click add subnet. 87 02:47.540 --> 02:49.560 And let's do a range of addresses. 88 02:49.560 --> 02:50.620 And how about for this one? 89 02:50.620 --> 02:55.323 We'll do 10.11.11.151 90 02:55.323 --> 02:58.429 through 10.11.11.200. 91 02:58.429 --> 03:00.379 And that'll be 50 addresses that are available. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 91 02:58.429 --> 03:00.379 And that'll be 50 addresses that are available. 92 03:00.379 --> 03:02.150 Then also specify the length of the mask 93 03:02.150 --> 03:03.240 with the cider notation. 94 03:03.240 --> 03:07.579 So, it'll be in the 10.11.11.0 with a /24. 95 03:07.579 --> 03:09.120 We'll hit tab. 96 03:09.120 --> 03:10.330 And then for the gateway address, this is important 97 03:10.330 --> 03:12.830 because if we have a device that gets an IP address 98 03:12.830 --> 03:15.009 on the 10.11.11 network, 99 03:15.009 --> 03:18.450 and it needs to route or reach some other destination, 100 03:18.450 --> 03:20.250 it's going to need a default gateway. 101 03:20.250 --> 03:23.650 So, the switch that we configured in the previous video, 102 03:23.650 --> 03:26.110 it's at 10.11.11.1. 103 03:26.110 --> 03:27.870 And that's the IP address we configured on it. 104 03:27.870 --> 03:29.639 It'll act as the default gateway. 105 03:29.639 --> 03:30.969 And then for the DNS servers, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 105 03:29.639 --> 03:30.969 And then for the DNS servers, 106 03:30.969 --> 03:32.880 we'll put the management DNS server 107 03:32.880 --> 03:36.039 at 192.168.1.100. 108 03:36.039 --> 03:37.860 We also want to make sure 109 03:37.860 --> 03:38.950 that that's going to be reachable 110 03:38.950 --> 03:40.360 by a client if it needs it. 111 03:40.360 --> 03:41.730 And then for the DNS suffix, 112 03:41.730 --> 03:44.120 let's go ahead and use ogit.local. 113 03:44.120 --> 03:46.690 That's the suffix I'm using in my lab here. 114 03:46.690 --> 03:48.059 All right. 115 03:48.059 --> 03:48.630 So, we'll click on add. 116 03:48.630 --> 03:51.049 And then we'll click on apply down here. 117 03:51.049 --> 03:52.660 And then we'll click on save. 118 03:52.660 --> 03:56.580 And boom, we now have a pool called pool 10.11.11. 119 03:56.580 --> 03:58.530 Let's make one more 120 03:58.530 --> 04:00.750 for the 10.22.22 network address space. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 120 03:58.530 --> 04:00.750 for the 10.22.22 network address space. 121 04:00.750 --> 04:03.059 So, we'll click on the add IP address pool. 122 04:03.059 --> 04:06.420 We'll call it pool 10.22.22. 123 04:06.420 --> 04:07.700 We'll tab over a couple of times. 124 04:07.700 --> 04:10.139 Click on set right here for the subnets 125 04:10.139 --> 04:11.770 and click on add subnet. 126 04:11.770 --> 04:13.370 And then click on IP ranges. 127 04:13.370 --> 04:16.790 And let's use the range of 10.22.22. 128 04:16.790 --> 04:18.720 And to be consistent, 129 04:18.720 --> 04:22.089 let's just use 151 through 10.22.22.200. 130 04:22.089 --> 04:23.690 And 50 addresses will be more 131 04:23.690 --> 04:24.849 than enough for my lab environment. 132 04:24.849 --> 04:27.990 And then for the network address space that we're in, 133 04:27.990 --> 04:30.940 I'll specify it's 10.22.22.0 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 133 04:27.990 --> 04:30.940 I'll specify it's 10.22.22.0 134 04:30.940 --> 04:32.290 with a 24-bit mask. 135 04:32.290 --> 04:35.990 And then we'll specify the default gateway, 10.22.22.1. 136 04:35.990 --> 04:37.650 That's the switched virtual interface 137 04:37.650 --> 04:38.990 that we looked at in the previous video 138 04:38.990 --> 04:41.660 on my multilayer switch on the physical network. 139 04:41.660 --> 04:44.319 So, my DNS server is 192.168.1.100. 140 04:44.319 --> 04:46.930 And the DNS suffix is ogit.local. 141 04:46.930 --> 04:48.480 So, the actual DNS suffix 142 04:48.480 --> 04:50.500 and the DNS server is going to be too critical 143 04:50.500 --> 04:53.770 for our ESXi host if they're using this IP address space. 144 04:53.770 --> 04:56.660 But what will be important is the default gateway should 145 04:56.660 --> 04:58.690 the need to route or reach 146 04:58.690 --> 05:00.280 another tunnel endpoint, for example, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 146 04:58.690 --> 05:00.280 another tunnel endpoint, for example, 147 05:00.280 --> 05:03.250 from ESXi A to ESXi B or vice versa, 148 05:03.250 --> 05:04.779 that's on a different subnet. 149 05:04.779 --> 05:07.790 So, I'll click on add here and click on apply, 150 05:07.790 --> 05:09.070 and click on save. 151 05:09.070 --> 05:11.560 And now we have two pools of addresses, 152 05:11.560 --> 05:15.320 one called 10.11.11, one called 10.22.22, 153 05:15.320 --> 05:17.180 which are both available. 154 05:17.180 --> 05:17.760 So over here, 155 05:17.760 --> 05:18.940 it says this second one is not yet initialized. 156 05:18.940 --> 05:21.530 So, we'll click on the refresh button and boom, 157 05:21.530 --> 05:23.620 now it's ready to go. 158 05:23.620 --> 05:24.800 Now, the way we communicate to an ESXi host 159 05:24.800 --> 05:27.480 about which of the uplinks it should use 160 05:27.480 --> 05:29.030 for the NSX traffic, 161 05:29.030 --> 05:31.610 we are going to use what's called an uplink profile. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 161 05:29.030 --> 05:31.610 we are going to use what's called an uplink profile. 162 05:31.610 --> 05:32.830 So, that'll be our next step, 163 05:32.830 --> 05:34.160 and let's create three of them. 164 05:34.160 --> 05:36.580 We'll create one uplink profile that says 165 05:36.580 --> 05:38.679 to ESXi-A use these two ports 166 05:38.679 --> 05:40.430 and VLAN 101. 167 05:40.430 --> 05:42.020 We'll create one uplink profile 168 05:42.020 --> 05:44.030 that we're going to use with ESXi-B that's going to say 169 05:44.030 --> 05:47.080 use these two uplinks and VLAN 102. 170 05:47.080 --> 05:49.580 We'll also specify the appropriate IP address. 171 05:49.580 --> 05:52.740 We'll also create a third uplink profile in the event 172 05:52.740 --> 05:55.142 that we want to configure a whole cluster 173 05:55.142 --> 05:57.400 of ESXi hosts as transport nodes 174 05:57.400 --> 05:59.509 all at the same time. 175 05:59.509 --> 05:59.959 And if we do that, we then could refer 176 05:59.959 --> 06:02.570 to the common uplink profile WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 176 05:59.959 --> 06:02.570 to the common uplink profile 177 06:02.570 --> 06:03.990 that they would then both use. 178 06:03.990 --> 06:05.960 So, let's go back to the NSX manager 179 06:05.960 --> 06:07.980 and let's create our uplink profiles. 180 06:07.980 --> 06:10.030 So back here at the NSX manager, 181 06:10.030 --> 06:13.330 the question is where are the uplink profiles kept? 182 06:13.330 --> 06:14.610 Where do we go to configure them? 183 06:14.610 --> 06:17.529 And the answer to that is by going here to system. 184 06:17.529 --> 06:19.840 And here at the top with system selected on the left, 185 06:19.840 --> 06:21.950 we are going to expand the fabric 186 06:21.950 --> 06:24.090 section here. 187 06:24.090 --> 06:24.180 And with fabric expanded, 188 06:24.180 --> 06:26.849 we're going to click right here on profiles. 189 06:26.849 --> 06:27.990 So, here are profiles. 190 06:27.990 --> 06:30.170 Instead of using one of the default ones WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 190 06:27.990 --> 06:30.170 Instead of using one of the default ones 191 06:30.170 --> 06:32.380 that's currently in place, let's create one. 192 06:32.380 --> 06:33.530 In fact, we're going to create three. 193 06:33.530 --> 06:36.550 We're going to create one for ESXi-A, one for ESXi-B, 194 06:36.550 --> 06:38.320 and also one that we could use 195 06:38.320 --> 06:40.940 if we're configuring a whole cluster at the same time. 196 06:40.940 --> 06:45.830 So, for this first one, let's call it ESXi-A uplink V101 197 06:45.830 --> 06:46.970 to represent that we are going 198 06:46.970 --> 06:50.280 to be using VLAN 101 for the transport network 199 06:50.280 --> 06:53.000 if this uplink profile is called upon. 200 06:53.000 --> 06:55.150 And then if we're using link aggregation, 201 06:55.150 --> 06:58.130 think of like link aggregation control protocol 202 06:58.130 --> 07:00.380 and ether channel bundles in the world of Cisco. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 202 06:58.130 --> 07:00.380 and ether channel bundles in the world of Cisco. 203 07:00.380 --> 07:01.630 If you have those set up and you want 204 07:01.630 --> 07:03.400 to use those link aggregation groups, 205 07:03.400 --> 07:05.809 you could specify them here in my lab environment. 206 07:05.809 --> 07:07.750 I'm simply using single interfaces. 207 07:07.750 --> 07:09.450 So, we're going to go down to teamings 208 07:09.450 --> 07:11.329 and we're going to simply use 209 07:11.329 --> 07:12.150 the default teaming method. 210 07:12.150 --> 07:14.070 So, here the current default method here 211 07:14.070 --> 07:15.440 is failover order. 212 07:15.440 --> 07:17.030 So, it's going to use the active uplinks, 213 07:17.030 --> 07:19.710 whatever we have set here, followed by standby. 214 07:19.710 --> 07:21.740 So, if we want to change that, we could double click, 215 07:21.740 --> 07:23.100 and you could say I want to load balance 216 07:23.100 --> 07:24.690 based on source or load balance based 217 07:24.690 --> 07:26.870 on source MAC address. 218 07:26.870 --> 07:28.160 But for our purposes, we want to failover order, 219 07:28.160 --> 07:30.150 and I want to use a single uplink because WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 219 07:28.160 --> 07:30.150 and I want to use a single uplink because 220 07:30.150 --> 07:32.480 that's going to give us a single tap, a total endpoint, 221 07:32.480 --> 07:34.560 and that's going to make it much easier to track. 222 07:34.560 --> 07:36.540 So, for ESXi-A, 223 07:36.540 --> 07:40.070 let's go ahead and call the first active uplink. 224 07:40.070 --> 07:44.099 Let's call it use-VMNIC-2. 225 07:44.099 --> 07:45.839 And that's also going to help remind me 226 07:45.839 --> 07:48.650 which interface on the distributed switch I want 227 07:48.650 --> 07:50.920 to go ahead and use, which is going to be VMNIC 2 228 07:50.920 --> 07:52.850 for the first one, then for the standby. 229 07:52.850 --> 07:54.640 I'm going to go ahead and give this a label 230 07:54.640 --> 07:56.090 and I'm going to call this standby. 231 07:56.090 --> 07:57.220 And I'll put a dash three 232 07:57.220 --> 07:59.840 there just to remind myself this can be VMNIC 3. 233 07:59.840 --> 08:02.070 So, these labels are just associated WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 233 07:59.840 --> 08:02.070 So, these labels are just associated 234 08:02.070 --> 08:04.190 with this uplink profile, and they don't really 235 08:04.190 --> 08:07.550 mean anything until we use this uplink profile, 236 08:07.550 --> 08:10.410 specifically called ESXi-A uplink with V101. 237 08:10.410 --> 08:13.680 And we apply that in association with a transport host. 238 08:13.680 --> 08:14.929 So currently we have a name, 239 08:14.929 --> 08:17.820 we've specified the active and standby links here, 240 08:17.820 --> 08:19.240 the labels for them anyway. 241 08:19.240 --> 08:20.829 And then down here, 242 08:20.829 --> 08:22.520 we also want to specify the transport VLAN to use. 243 08:22.520 --> 08:26.150 So, for ESXi-A, if we want it to use VLAN 101 244 08:26.150 --> 08:28.300 for the transport network, we want to go ahead 245 08:28.300 --> 08:31.050 and put the transport VLAN 101 right here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 245 08:28.300 --> 08:31.050 and put the transport VLAN 101 right here. 246 08:31.050 --> 08:33.620 And because with the current flavor of NSX, 247 08:33.620 --> 08:35.620 if we're using a virtual distributed switch 248 08:35.620 --> 08:39.130 in vSphere, which we are, and it has a huge MTU, 249 08:39.130 --> 08:40.340 we don't need to do anything 250 08:40.340 --> 08:43.110 about the MTU right here because the MTU, as it says, 251 08:43.110 --> 08:46.510 is not applicable for a virtual distributed switch. 252 08:46.510 --> 08:48.410 But at the same time, we also want to make sure 253 08:48.410 --> 08:49.920 that in the physical environment that 254 08:49.920 --> 08:53.700 we can support frames larger than the default of 1500. 255 08:53.700 --> 08:54.799 So, in the physical environment, 256 08:54.799 --> 08:56.580 I've got my Cisco switch set up 257 08:56.580 --> 08:58.430 to support 9,000 for the MTU. 258 08:58.430 --> 09:01.830 And when we deploy our distributed switch in vSphere, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 258 08:58.430 --> 09:01.830 And when we deploy our distributed switch in vSphere, 259 09:01.830 --> 09:05.010 we'll also set up a larger than default MTU as well. 260 09:05.010 --> 09:08.040 So, we'll click on add, and then we will check our work. 261 09:08.040 --> 09:13.040 So, for this profile called ESXi-A uplink with V101, 262 09:13.040 --> 09:14.830 we're using the transport VLAN of 101. 263 09:15.670 --> 09:17.410 Fantastic. 264 09:17.410 --> 09:18.469 And then we scroll down, 265 09:18.469 --> 09:19.470 we have our active uplink label 266 09:19.470 --> 09:22.110 and our standby uplink label set up. 267 09:22.110 --> 09:23.090 And that looks great. 268 09:23.090 --> 09:24.590 So, let's make one more for ESXi-B. 269 09:24.590 --> 09:27.530 So, we'll click on plus, and we'll go ahead 270 09:27.530 --> 09:30.930 and say this is going to be ESXi-B, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 270 09:27.530 --> 09:30.930 and say this is going to be ESXi-B, 271 09:30.930 --> 09:34.480 and I see a little copy paste action there with VLAN 102. 272 09:34.480 --> 09:35.980 I'll scroll down. 273 09:35.980 --> 09:38.600 I want to use VLAN 102 for the transport 274 09:38.600 --> 09:40.740 for this profile because we're going to associate 275 09:40.740 --> 09:42.370 this with ESXi-B. 276 09:42.370 --> 09:44.679 And for the actual uplinks, 277 09:44.679 --> 09:46.710 let's go ahead for the active uplink, let's go ahead 278 09:46.710 --> 09:49.670 and use DOS to remind myself in Spanish 279 09:49.670 --> 09:51.710 that I want to use uplink number two. 280 09:51.710 --> 09:54.410 And for the standby, we'll use trace, 281 09:54.410 --> 09:56.460 which is going to help mostly remind me 282 09:56.460 --> 09:59.370 that we are going to be using VMNIC 3. 283 09:59.370 --> 10:02.320 So again, in the uplink profiles, these are just labels, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 283 09:59.370 --> 10:02.320 So again, in the uplink profiles, these are just labels, 284 10:02.320 --> 10:04.320 which when we apply the uplink profiles, 285 10:04.320 --> 10:06.460 we'll associate with the actual uplinks 286 10:06.460 --> 10:07.830 on our distributed switch. 287 10:07.830 --> 10:09.610 So, we'll go ahead and click on add, 288 10:09.610 --> 10:11.000 and then we'll verify our work. 289 10:11.000 --> 10:14.220 So, for this uplink profile, ESXi-B uplink with V102, 290 10:14.220 --> 10:15.440 our VLAN is 102. 291 10:15.440 --> 10:17.260 That looks great. 292 10:17.260 --> 10:19.260 And for the teamings, I've got the first label 293 10:19.260 --> 10:21.380 and second label for the active and standby. 294 10:21.380 --> 10:22.410 That looks fantastic. 295 10:22.410 --> 10:25.110 And let's make one more that if we choose 296 10:25.110 --> 10:27.820 to deploy a whole cluster of ESXi hosts 297 10:27.820 --> 10:30.930 and make them transport nodes, we could refer to this. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 297 10:27.820 --> 10:30.930 and make them transport nodes, we could refer to this. 298 10:30.930 --> 10:32.910 So, we'll call this uplinks for cluster. 299 10:32.910 --> 10:35.030 And again, I don't have any link aggregation going on, 300 10:35.030 --> 10:37.090 so I'll go ahead for the teamings 301 10:37.090 --> 10:38.480 and I'll say for the teamings, 302 10:38.480 --> 10:39.540 let me go ahead 303 10:39.540 --> 10:43.043 and specify that instead of using a failover order, 304 10:43.043 --> 10:44.509 I wanna do load balancing. 305 10:44.509 --> 10:45.870 And let me put them both right here. 306 10:45.870 --> 10:49.280 So, I'll put two comma three, just as labels once again, 307 10:49.280 --> 10:51.580 to remind myself of which VM NICs, 308 10:51.580 --> 10:53.660 I hope to actually associate with those. 309 10:53.660 --> 10:56.920 And I intentionally made the actual labels here different 310 10:56.920 --> 10:59.020 on each of the uplink profiles. 311 10:59.020 --> 11:02.599 So, if we are going to use this uplinks for cluster profile, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 311 10:59.020 --> 11:02.599 So, if we are going to use this uplinks for cluster profile, 312 11:02.599 --> 11:03.750 what VLAN do we want to use? 313 11:03.750 --> 11:06.469 Let's just double up on VLAN 101. 314 11:06.469 --> 11:07.870 So, I'm going to add that to the title as well, 315 11:07.870 --> 11:09.600 just to remind myself when I see it 316 11:09.600 --> 11:12.580 about exactly which VLAN we're going to be using. 317 11:12.580 --> 11:15.741 If we choose to use this uplink profile called uplinks 318 11:15.741 --> 11:18.153 for cluster V101, and we'll click on add, 319 11:18.153 --> 11:20.690 then I'll verify my work there by clicking on it, 320 11:20.690 --> 11:23.430 and just verifying transport VLAN 101, 321 11:23.430 --> 11:26.260 and labels two and three for two active uplink. 322 11:26.260 --> 11:29.490 So, if we did use this uplink profile, 323 11:29.490 --> 11:31.570 because we have two active uplinks, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 323 11:29.490 --> 11:31.570 because we have two active uplinks, 324 11:31.570 --> 11:35.139 it's going to end up with two tunnel endpoint addresses, 325 11:35.139 --> 11:37.150 one for each of the active uplinks. 326 11:37.150 --> 11:40.420 So, at this point, we have our uplink profiles created. 327 11:40.420 --> 11:43.110 We haven't applied them yet to either of the ESXi host, 328 11:43.110 --> 11:44.670 but we'll get to that. 329 11:44.670 --> 11:46.280 But we do have the uplink profiles ready in the wings. 330 11:46.280 --> 11:48.680 We also have a couple of pools of IP addresses 331 11:48.680 --> 11:51.559 that we can pull from one in the 10.11.11 range, 332 11:51.559 --> 11:53.830 one in the 10.22.22 range. 333 11:53.830 --> 11:55.230 And so, for our next step, 334 11:55.230 --> 11:59.170 we are gonna create a new overlay transport zone. 335 11:59.170 --> 12:00.880 And just like our uplink profiles, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 335 11:59.170 --> 12:00.880 And just like our uplink profiles, 336 12:00.880 --> 12:03.140 they're really not going to be doing too much until 337 12:03.140 --> 12:05.070 we associate these objects, 338 12:05.070 --> 12:08.099 including the uplink profiles and the transport zones, 339 12:08.099 --> 12:09.889 until we associate them 340 12:09.889 --> 12:12.400 with an ESXi host that's been enabled for NSX, 341 12:12.400 --> 12:15.339 which is now going to be called a host transport node. 342 12:15.339 --> 12:16.959 So again, this is all in preparation 343 12:16.959 --> 12:19.310 for the actual deployment where we'll configure 344 12:19.310 --> 12:20.800 our ESXi host. 345 12:20.800 --> 12:21.940 So, join me in the next video 346 12:21.940 --> 12:24.420 as we create a brand-new transport zone 347 12:24.420 --> 12:25.610 that we can use as part of our configuration.