WEBVTT 1 00:00.180 --> 00:01.290 So for our deployment, 2 00:01.290 --> 00:02.940 we should also just take a moment 3 00:02.940 --> 00:04.950 and verify a couple of things. 4 00:04.950 --> 00:07.590 Number one, if we are gonna be using Uplink three 5 00:07.590 --> 00:10.950 and VLAN 103 for Edge-1 and Uplink three 6 00:10.950 --> 00:14.760 and VLAN 104 as the transport VLAN, we wanna make sure 7 00:14.760 --> 00:17.040 that we have Uplink profiles currently in place, 8 00:17.040 --> 00:18.810 and if we don't, we'd wanna go ahead and create them. 9 00:18.810 --> 00:21.277 So we'd create an Uplink profile that says 10 00:21.277 --> 00:25.320 "Hey, please use the VLAN 103 and one for 104". 11 00:25.320 --> 00:27.930 And we'd also specify in those same Uplink profiles 12 00:27.930 --> 00:29.790 that we wanna use Uplink three. 13 00:29.790 --> 00:32.940 So for Edge-1, that'll be Uplink three on Edge-A, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:29.790 --> 00:32.940 So for Edge-1, that'll be Uplink three on Edge-A, 14 00:32.940 --> 00:34.920 and for Edge-2, that'd be Uplink three 15 00:34.920 --> 00:36.960 over here on ESXI-B. 16 00:36.960 --> 00:39.270 And then over on the Transport Network, we'd also be wise 17 00:39.270 --> 00:41.130 to take a moment just to verify 18 00:41.130 --> 00:43.140 that we have those existing VLANs 19 00:43.140 --> 00:45.600 and also that we have the routing capability 20 00:45.600 --> 00:49.140 between the 33 network and the 44 network space. 21 00:49.140 --> 00:50.970 Because if they have to route between each other, 22 00:50.970 --> 00:53.700 we wanna make sure we have all those routing services on the 23 00:53.700 --> 00:56.220 physical network provided by, or through 24 00:56.220 --> 00:57.540 our top of rack switches. 25 00:57.540 --> 00:59.730 So to give us a little bias towards success, 26 00:59.730 --> 01:00.960 let's take a moment right now WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 26 00:59.730 --> 01:00.960 let's take a moment right now 27 01:00.960 --> 01:03.930 and verify some of those infrastructure components 28 01:03.930 --> 01:05.490 and make sure that they're in place. 29 01:05.490 --> 01:07.380 So let's start with the infrastructure. 30 01:07.380 --> 01:09.960 This is gonna represent our top of rack switch. 31 01:09.960 --> 01:11.640 And let's go ahead and just verify 32 01:11.640 --> 01:13.830 with the Cisco Catalyst switch, 33 01:13.830 --> 01:15.570 which happens to be a multi-layer switch, 34 01:15.570 --> 01:17.820 so it can do layer two switching and also routing. 35 01:17.820 --> 01:19.560 So let's do a show VLAN brief. 36 01:19.560 --> 01:22.090 There is VLAN 103 37 01:22.090 --> 01:23.550 and VLAN 104. 38 01:23.550 --> 01:24.720 They both exist. 39 01:24.720 --> 01:26.730 So let's also do a show IP interface brief. 40 01:26.730 --> 01:27.840 Then I'm gonna use a pipe symbol, 41 01:27.840 --> 01:32.190 say please exclude in the output anything that has the word WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 41 01:27.840 --> 01:32.190 say please exclude in the output anything that has the word 42 01:32.190 --> 01:34.770 or the string of text U-N-A-S-S-I 43 01:34.770 --> 01:36.930 for unassigned and press enter. 44 01:36.930 --> 01:39.780 And here are logical layer three interfaces. 45 01:39.780 --> 01:41.880 So I've got routing capabilities 46 01:41.880 --> 01:42.900 with an IP address 47 01:42.900 --> 01:46.380 in VLAN 103 of 33, 33, 33.1, 48 01:46.380 --> 01:48.342 and a VLAN 104 49 01:48.342 --> 01:49.675 of 44, 44, 44.1. 50 01:50.532 --> 01:53.340 So if we do a show IP route, I've got routing capability 51 01:53.340 --> 01:54.960 between those two network address spaces. 52 01:54.960 --> 01:58.200 So there's my route for the 33 et cetera network. 53 01:58.200 --> 02:01.140 And here's my route for the 44 network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 53 01:58.200 --> 02:01.140 And here's my route for the 44 network. 54 02:01.140 --> 02:03.630 And on this multilayer switch, it is directly connected 55 02:03.630 --> 02:06.330 to both networks via its VLAN interfaces. 56 02:06.330 --> 02:09.120 So I just wanna verify that we have the physical components 57 02:09.120 --> 02:11.520 ready to go to support our Edge nodes. 58 02:11.520 --> 02:13.890 So this top of rack switch has not only the VLANs 59 02:13.890 --> 02:16.560 but also has the routing for the IP subnets 60 02:16.560 --> 02:18.630 associated with those VLANs. 61 02:18.630 --> 02:21.450 And I've also got, I believe, DHCP services set up should we 62 02:21.450 --> 02:23.519 choose to use those as well. 63 02:23.519 --> 02:26.580 So if we do a show IP DHCP pool and press enter, 64 02:26.580 --> 02:30.480 I've got a pool for the 33 address base right there, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 64 02:26.580 --> 02:30.480 I've got a pool for the 33 address base right there, 65 02:30.480 --> 02:32.160 and another one for the 44 address base. 66 02:32.160 --> 02:35.407 So in the event for our Edge nodes, if we wanna say 67 02:35.407 --> 02:37.560 "Hey, use a DHCP assigned address", 68 02:37.560 --> 02:38.910 we have that option as well. 69 02:38.910 --> 02:40.350 However, for our purposes, 70 02:40.350 --> 02:43.110 we're gonna hard code the tunnel endpoint addresses 71 02:43.110 --> 02:45.750 as 3 3, 3 3, 3 3, 3 3 72 02:45.750 --> 02:47.250 for Edge-1 73 02:47.250 --> 02:49.920 and 44, 44, 44, 44 74 02:49.920 --> 02:50.790 for Edge-2. 75 02:50.790 --> 02:52.380 And that way when we see those IP address, 76 02:52.380 --> 02:54.000 we'll know exactly what they are. 77 02:54.000 --> 02:56.640 Next, let's head over to the NSX manager to verify 78 02:56.640 --> 02:58.950 that we have Uplink profiles that we can use 79 02:58.950 --> 03:00.900 for Edge-1 and Edge-2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 79 02:58.950 --> 03:00.900 for Edge-1 and Edge-2. 80 03:00.900 --> 03:04.590 So here in the NSX manager, let's go to the system tab. 81 03:04.590 --> 03:06.660 And under fabric on the left, we're gonna go down 82 03:06.660 --> 03:08.070 to profiles. 83 03:08.070 --> 03:10.470 And so here's a bunch of Uplink profiles 84 03:10.470 --> 03:13.620 that I made previously and we can just pick one 85 03:13.620 --> 03:14.940 or two of those and verify they're 86 03:14.940 --> 03:16.380 correct before we use them. 87 03:16.380 --> 03:20.760 So for Edge-1 it's gonna be using Uplink three 88 03:20.760 --> 03:22.860 on its respective host that's running it 89 03:22.860 --> 03:26.670 and it's gonna use on that Uplink VLAN 103. 90 03:26.670 --> 03:28.980 So that looks like a winner right there. 91 03:28.980 --> 03:31.230 If we just click on it to confirm. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 91 03:28.980 --> 03:31.230 If we just click on it to confirm. 92 03:31.230 --> 03:35.700 So this Uplink profile called V103 vmnic three says 93 03:35.700 --> 03:38.040 use 103 for the transport VLAN, 94 03:38.040 --> 03:40.890 and if we scroll down, we're using vmnic three. 95 03:40.890 --> 03:42.750 Now here it's just a label in NSX, 96 03:42.750 --> 03:44.430 but we'll wanna map that over 97 03:44.430 --> 03:47.880 to the corresponding vmnic three on the respective host. 98 03:47.880 --> 03:50.520 So here for Edge-2 we're also gonna use Uplink three 99 03:50.520 --> 03:54.180 on its respective host, but we're gonna be using VLAN 104. 100 03:54.180 --> 03:57.810 So Uplink three right here and VLAN 104. 101 03:57.810 --> 04:01.110 So here in NSX manager, let's take a peek at these. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 101 03:57.810 --> 04:01.110 So here in NSX manager, let's take a peek at these. 102 04:01.110 --> 04:03.870 We're looking for VLAN 104 and vmnic three, 103 04:03.870 --> 04:06.090 and that looks, based on the title, like it might be it. 104 04:06.090 --> 04:08.100 So if we click on it to confirm, sure enough, 105 04:08.100 --> 04:10.530 that's using Transport VLAN 104. 106 04:10.530 --> 04:13.680 And the label regarding this Uplink profile says 107 04:13.680 --> 04:14.820 vmnic three. 108 04:14.820 --> 04:17.130 So we'd wanna map that correctly, this label called 109 04:17.130 --> 04:20.040 vmnic three over to the associated Uplink 110 04:20.040 --> 04:22.650 on the distributed switch that leads out to 111 04:22.650 --> 04:23.880 vmnic three physically. 112 04:23.880 --> 04:25.860 In fact, to make that a little more clear, let's go ahead 113 04:25.860 --> 04:28.380 and edit this Uplink profile. 114 04:28.380 --> 04:31.260 And instead of calling the Uplink vmnic three, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 114 04:28.380 --> 04:31.260 And instead of calling the Uplink vmnic three, 115 04:31.260 --> 04:33.686 I'll go ahead and double click here to edit it. 116 04:33.686 --> 04:37.080 Let's go ahead and call it vmnic dash T-R-E-S, 117 04:37.080 --> 04:39.060 for three in Espanol. 118 04:39.060 --> 04:40.170 And that way when we see it, 119 04:40.170 --> 04:41.880 we'll know exactly where that came from. 120 04:41.880 --> 04:43.380 It came from this Uplink profile, 121 04:43.380 --> 04:46.230 and then we'll map it to the appropriate Uplink 122 04:46.230 --> 04:47.550 over on the distributed switch. 123 04:47.550 --> 04:48.780 So we'll click on save. 124 04:48.780 --> 04:51.840 So we verified that we not only have the appropriate 125 04:51.840 --> 04:54.570 VLANs available on the physical transport network, 126 04:54.570 --> 04:56.850 but we also verified that we have appropriate 127 04:56.850 --> 04:58.830 Uplink profiles that we can use. 128 04:58.830 --> 05:00.690 This one right here for Edge-1 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 128 04:58.830 --> 05:00.690 This one right here for Edge-1 129 05:00.690 --> 05:02.550 and this one right here for Edge-2. 130 05:02.550 --> 05:05.190 So to deploy an Edge node it's super easy 131 05:05.190 --> 05:06.960 to do right here from the NSX manager. 132 05:06.960 --> 05:09.300 We simply go to system where we currently are, 133 05:09.300 --> 05:12.420 and then on the left we simply go to nodes. 134 05:12.420 --> 05:15.180 So as time goes on, they may rearrange things a little bit, 135 05:15.180 --> 05:17.490 but at the moment with the current flavor of NSX, 136 05:17.490 --> 05:18.510 it is right here. 137 05:18.510 --> 05:21.420 Now, currently it shows that we have an edge node 138 05:21.420 --> 05:24.300 called Edge-1 already in place, and I'll tell you why. 139 05:24.300 --> 05:28.260 This takes about an hour to deploy an Edge node 140 05:28.260 --> 05:30.870 and part of the time there is gonna deploy the full VM on WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 140 05:28.260 --> 05:30.870 and part of the time there is gonna deploy the full VM on 141 05:30.870 --> 05:34.380 the ESXI host, it's going to initialize that Edge node 142 05:34.380 --> 05:35.430 and then once it's up and running, 143 05:35.430 --> 05:37.020 it takes a little longer to get fully baked. 144 05:37.020 --> 05:39.420 So from start to finish, it probably takes somewhere 145 05:39.420 --> 05:43.020 between 45 minutes and an hour to deploy an Edge. 146 05:43.020 --> 05:45.120 So what I did earlier is I deployed this Edge, 147 05:45.120 --> 05:47.160 ran an errand, and then came back. 148 05:47.160 --> 05:50.520 And so Edge-1 is already in place, but have no fear, 149 05:50.520 --> 05:52.170 what we get to do is we're gonna go 150 05:52.170 --> 05:54.510 through the exact same steps, but for Edge-2, 151 05:54.510 --> 05:57.330 and that way as we wait for Edge-2 to finish, 152 05:57.330 --> 06:01.050 we can take the steps of validating our existing Edge node WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 152 05:57.330 --> 06:01.050 we can take the steps of validating our existing Edge node 153 06:01.050 --> 06:02.430 that's already in place. 154 06:02.430 --> 06:04.500 So let's go ahead and deploy Edge-2. 155 06:04.500 --> 06:06.630 And lemme go ahead and arrow this to the left a little bit 156 06:06.630 --> 06:08.700 so we can have a little more real estate right here. 157 06:08.700 --> 06:12.570 And let's click on add Edge node and let's add Edge-2. 158 06:12.570 --> 06:14.700 And just as a reminder about the details for that, 159 06:14.700 --> 06:15.840 Edge-2 is gonna have the 160 06:15.840 --> 06:19.770 management address of 192, 168, 1.192. 161 06:19.770 --> 06:21.690 We're gonna use a static configured IP address 162 06:21.690 --> 06:24.600 of 44, et cetera for the tunnel endpoint, 163 06:24.600 --> 06:27.480 we'll use Uplink three over here on ESXIB 164 06:27.480 --> 06:30.540 and we'll use VLAN 104 for the transport VLAN. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 164 06:27.480 --> 06:30.540 and we'll use VLAN 104 for the transport VLAN. 165 06:30.540 --> 06:31.890 So with that in mind, let's go back 166 06:31.890 --> 06:33.870 and do the deployment of Edge-2. 167 06:33.870 --> 06:35.850 So we'll go ahead and call this Edge-2, 168 06:35.850 --> 06:38.640 and then it's asking for a fully qualified domain name. 169 06:38.640 --> 06:42.120 So let me also verify I've got that set up in DNS. 170 06:42.120 --> 06:44.010 So here is a command prompt, 171 06:44.010 --> 06:46.080 and I'm gonna be using my lab DNS server, 172 06:46.080 --> 06:47.130 which is at dot 100, 173 06:47.130 --> 06:49.110 so we'll go ahead and do an NS lookup. 174 06:49.110 --> 06:49.943 And there we go. 175 06:49.943 --> 06:52.080 We're using the DNS server, the same one I'm gonna be 176 06:52.080 --> 06:53.910 telling this Edge node to use. 177 06:53.910 --> 06:57.720 And lemme do a lookup for Edge-2.OGIT.local, 178 06:57.720 --> 06:58.553 and press enter. 179 06:58.553 --> 07:01.320 And sure enough, it does have a record there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 179 06:58.553 --> 07:01.320 And sure enough, it does have a record there. 180 07:01.320 --> 07:02.790 And let's also do a reverse lookup 181 07:02.790 --> 07:07.680 by putting in net address 192.168.1.192 and pressing enter. 182 07:07.680 --> 07:09.810 So both forward and reverse look-ups are working. 183 07:09.810 --> 07:10.920 That's fantastic. 184 07:10.920 --> 07:14.400 So that's the name we're gonna use: Edge-2.OGIT.Local. 185 07:14.400 --> 07:16.230 So I'm gonna highlight that, press enter to copy it 186 07:16.230 --> 07:18.150 to my buffer and then go back here, 187 07:18.150 --> 07:20.790 right click and simply paste it in. 188 07:20.790 --> 07:22.530 Next, it's asking this for the form factor. 189 07:22.530 --> 07:25.050 This is a question about how many resources do we wanna 190 07:25.050 --> 07:27.720 throw at this Edge VM? 191 07:27.720 --> 07:29.640 And so I'm gonna go ahead and choose medium, 192 07:29.640 --> 07:31.920 which will chew up four CPUs and eight gigabytes of RAM. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 192 07:29.640 --> 07:31.920 which will chew up four CPUs and eight gigabytes of RAM. 193 07:31.920 --> 07:34.680 But just be aware, especially in the lab environment, 194 07:34.680 --> 07:38.370 that by default it's gonna take all the RAM that you give it 195 07:38.370 --> 07:41.700 as a guarantee, meaning there's gonna be a reservation. 196 07:41.700 --> 07:43.140 So if we scroll down a little bit, 197 07:43.140 --> 07:46.050 instead of saying a hundred percent memory reservation, 198 07:46.050 --> 07:48.120 I'm gonna cut that back to 50. 199 07:48.120 --> 07:49.890 And that way if push comes to shove, 200 07:49.890 --> 07:52.770 I can still bring up this Edge VM, 201 07:52.770 --> 07:55.710 even if there isn't a full quantity of RAM 202 07:55.710 --> 07:57.150 that I can allocate to it based on 203 07:57.150 --> 07:59.010 other resources needing that memory. 204 07:59.010 --> 08:02.490 So I'm gonna just set it up to reserve 50% of that RAM, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 204 07:59.010 --> 08:02.490 So I'm gonna just set it up to reserve 50% of that RAM, 205 08:02.490 --> 08:04.110 but I'm gonna go for the medium size 206 08:04.110 --> 08:05.430 and click on "next". 207 08:05.430 --> 08:08.250 I'll go ahead and supply a password for admin 208 08:08.250 --> 08:09.210 and also for root. 209 08:09.210 --> 08:12.750 I'm also gonna say I want to allow SSH logins. 210 08:12.750 --> 08:15.480 So those passwords have been supplied and confirmed. 211 08:15.480 --> 08:17.550 We'll scroll down and I'm not too worried about, 212 08:17.550 --> 08:18.930 for my lab, the audit credentials, 213 08:18.930 --> 08:21.390 so I'm gonna leave those blank and click on "next". 214 08:21.390 --> 08:22.860 Now it's asking me about where do you want 215 08:22.860 --> 08:24.030 to deploy this VM? 216 08:24.030 --> 08:28.470 So based on our plan, Edge-2 is gonna be placed on ESXIB, 217 08:28.470 --> 08:30.900 which is under the control of vCenter, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 217 08:28.470 --> 08:30.900 which is under the control of vCenter, 218 08:30.900 --> 08:33.630 the vCenter that we identified in NSX manager 219 08:33.630 --> 08:34.950 as our vCenter. 220 08:34.950 --> 08:37.770 And then as far as which cluster is that ESXI host in, 221 08:37.770 --> 08:40.380 it's in the host transport nodes. 222 08:40.380 --> 08:42.270 And then I don't have a specific resource pool 223 08:42.270 --> 08:44.490 that I wanna put 'em in, but I do wanna specify the host. 224 08:44.490 --> 08:46.170 And so I am gonna choose the host 225 08:46.170 --> 08:49.260 and we're gonna choose ESXIB based on our plan. 226 08:49.260 --> 08:52.170 And then for the data store for this little VM, 227 08:52.170 --> 08:54.750 I'm gonna choose the local data store on ESXIB, 228 08:54.750 --> 08:56.010 and then we'll click on "next". 229 08:56.010 --> 08:59.400 Now it's asking about the management interface for Edge-2. 230 08:59.400 --> 09:01.770 So let's take a look at our plan once again. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 230 08:59.400 --> 09:01.770 So let's take a look at our plan once again. 231 09:01.770 --> 09:05.610 So in our plan we wanna use 192, 168, 1.192 232 09:05.610 --> 09:08.760 with a 24 bit mask as the management IP address. 233 09:08.760 --> 09:10.320 So we'll put that in next. 234 09:10.320 --> 09:12.060 So we'll click here to say that we want 235 09:12.060 --> 09:13.950 to have a statically assigned IP address, 236 09:13.950 --> 09:17.730 and we'll use the address of 192.168.1.1.92 237 09:17.730 --> 09:19.260 with a 24 bit mask. 238 09:19.260 --> 09:20.610 And it wants the default gateway, 239 09:20.610 --> 09:23.250 so in my lab environment on my management network, 240 09:23.250 --> 09:26.130 it is 192.168.1.1. 241 09:26.130 --> 09:29.120 And now it's asking me for which interface do we wanna use 242 09:29.120 --> 09:30.600 for the management network? WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 242 09:29.120 --> 09:30.600 for the management network? 243 09:30.600 --> 09:32.040 So we're gonna select a port group. 244 09:32.040 --> 09:34.080 So here is a port group that leads off 245 09:34.080 --> 09:35.070 to my management network. 246 09:35.070 --> 09:38.430 So I'm gonna choose that for the connection for this VM 247 09:38.430 --> 09:40.140 to connect to the management network. 248 09:40.140 --> 09:41.520 And we'll click on "save". 249 09:41.520 --> 09:45.030 And then for the search domains, I'm in the OGIT.local, 250 09:45.030 --> 09:46.440 and then the DNS servers can be my 251 09:46.440 --> 09:49.830 Windows server at 192.168.1.100. 252 09:49.830 --> 09:54.090 And the same Windows server at 192.168.1.100 253 09:54.090 --> 09:57.570 is acting as a network time protocol server, as well. 254 09:57.570 --> 10:00.630 And then down here it's asking if we want to enable UPT mode WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 254 09:57.570 --> 10:00.630 And then down here it's asking if we want to enable UPT mode 255 10:00.630 --> 10:02.640 and I don't have the Smartnicks to support that, 256 10:02.640 --> 10:04.110 so I'm gonna go ahead and leave that off, 257 10:04.110 --> 10:05.970 and then we'll click on "next" to continue. 258 10:05.970 --> 10:08.340 So NSX has been through several iterations 259 10:08.340 --> 10:10.950 and several versions like two and two x and three 260 10:10.950 --> 10:12.330 and three x, and now we're at four. 261 10:12.330 --> 10:15.570 And currently we're at 4.1.1 as of this recording. 262 10:15.570 --> 10:17.250 So as far as the Edge Switch name, 263 10:17.250 --> 10:18.600 we don't have to deal with that anymore, 264 10:18.600 --> 10:20.070 we can just leave that as the default. 265 10:20.070 --> 10:22.830 And then now we're gonna specify which transport zones we 266 10:22.830 --> 10:24.660 want this Edge to be able to support. 267 10:24.660 --> 10:27.090 So again, the transport zone is like the range of 268 10:27.090 --> 10:28.890 how far a segment can go. 269 10:28.890 --> 10:32.910 So currently, everywhere else, our host transport nodes WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 269 10:28.890 --> 10:32.910 So currently, everywhere else, our host transport nodes 270 10:32.910 --> 10:36.090 and also Edge-1, which I already deployed, I specified 271 10:36.090 --> 10:39.420 that I just wanna support at the moment one transport zone, 272 10:39.420 --> 10:41.610 and that's the one we created a few skills go, 273 10:41.610 --> 10:44.100 that's our AB overlay transport zone. 274 10:44.100 --> 10:45.150 And so we can add more later, 275 10:45.150 --> 10:48.420 but at the moment I just want this one Edge, Edge-2 276 10:48.420 --> 10:50.250 to be able to support any segments in 277 10:50.250 --> 10:51.900 that overlay transport zone. 278 10:51.900 --> 10:54.900 And next it's asking us about the Uplink profile. 279 10:54.900 --> 10:56.460 And so we already confirmed earlier 280 10:56.460 --> 10:58.500 that we have an Uplink profile that we can use. 281 10:58.500 --> 11:00.750 And based on our plan, we want the Uplink profile WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 281 10:58.500 --> 11:00.750 And based on our plan, we want the Uplink profile 282 11:00.750 --> 11:03.120 that's gonna support Uplink three here on 283 11:03.120 --> 11:06.470 ESXIB once it gets deployed, and VLAN 104. 284 11:06.470 --> 11:08.910 So we'll grab the appropriate Uplink profile 285 11:08.910 --> 11:10.350 that does exactly that. 286 11:10.350 --> 11:15.350 So we'll use the dropdown and we want VLAN 104 287 11:15.360 --> 11:17.490 and Uplink three, and so we're gonna grab 288 11:17.490 --> 11:18.930 that one right there. 289 11:18.930 --> 11:20.520 So there's our Uplink profile 290 11:20.520 --> 11:22.110 and as a result of that, it's now asking us 291 11:22.110 --> 11:25.050 to map over the label that we put associated 292 11:25.050 --> 11:26.100 with that Uplink profile. 293 11:26.100 --> 11:29.040 There it is, vmnic-tres, and then map it over 294 11:29.040 --> 11:32.070 to an actual port group on a distributed switch. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 294 11:29.040 --> 11:32.070 to an actual port group on a distributed switch. 295 11:32.070 --> 11:33.480 So currently on the distributed switch, 296 11:33.480 --> 11:37.830 I currently have a port group called this: "DPG leads 297 11:37.830 --> 11:39.300 to vmnic3". 298 11:39.300 --> 11:40.980 In fact, let's pause for just a moment 299 11:40.980 --> 11:44.220 and make a road trip over to the vSphere Client. 300 11:44.220 --> 11:46.170 And let me show you that port group. 301 11:46.170 --> 11:47.520 So here on the vSphere Client, 302 11:47.520 --> 11:49.320 if we go to the network tab here, 303 11:49.320 --> 11:52.170 and then we open up this DS for NSX, 304 11:52.170 --> 11:53.280 I have this port group. 305 11:53.280 --> 11:54.240 Notice there's no end there, 306 11:54.240 --> 11:56.760 this is just a normal distributed switch port group 307 11:56.760 --> 11:59.310 that's available to both ESXIA and B. 308 11:59.310 --> 12:00.960 And if you look at the properties of this, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 308 11:59.310 --> 12:00.960 And if you look at the properties of this, 309 12:00.960 --> 12:03.870 right click and click on "edit settings", 310 12:03.870 --> 12:06.510 and then I'll take you down to teaming and failover. 311 12:06.510 --> 12:09.270 So as part of this pork group called "DPG leads 312 12:09.270 --> 12:12.150 to vmnic3", the only active Uplink we're using 313 12:12.150 --> 12:13.140 is vmnic three. 314 12:13.140 --> 12:15.570 So you certainly could add in additional fault tolerance 315 12:15.570 --> 12:18.180 with standby links, or if you wanna have two taps, 316 12:18.180 --> 12:20.520 you could go ahead and do two active Uplinks, 317 12:20.520 --> 12:21.930 based on the Uplink profile you're using. 318 12:21.930 --> 12:23.490 But I just wanna verify and show you 319 12:23.490 --> 12:27.090 that this port group called "DPG leads to vmnic3" 320 12:27.090 --> 12:30.420 is only using the Uplink vmnic three on WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 320 12:27.090 --> 12:30.420 is only using the Uplink vmnic three on 321 12:30.420 --> 12:32.160 the respective host that it's currently running on. 322 12:32.160 --> 12:33.720 So I'll click on "cancel". 323 12:33.720 --> 12:36.210 We could also go ahead and click on the parent switch here, 324 12:36.210 --> 12:37.500 this distributed switch, 325 12:37.500 --> 12:39.990 and click on "configure" and go to "topology", 326 12:39.990 --> 12:41.670 and that would also show us the story there. 327 12:41.670 --> 12:46.350 So this port group right here only uses vmnic three, 328 12:46.350 --> 12:47.790 and that's what this represents. 329 12:47.790 --> 12:50.250 And there's Edge-1 that I deployed earlier today 330 12:50.250 --> 12:52.140 and we're about to deploy Edge-2, 331 12:52.140 --> 12:54.600 which will also be using this port group 332 12:54.600 --> 12:56.130 for its transport network. 333 12:56.130 --> 13:00.540 Except, unlike Edge-1, Edge-2 is gonna be using VLAN 104 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 333 12:56.130 --> 13:00.540 Except, unlike Edge-1, Edge-2 is gonna be using VLAN 104 334 13:00.540 --> 13:03.390 and Edge-1 is using VLAN 103 335 13:03.390 --> 13:05.340 as it communicates over the transport network. 336 13:05.340 --> 13:08.070 And again, you can use the same exact VLAN if you want to, 337 13:08.070 --> 13:09.360 the same exact subnet, 338 13:09.360 --> 13:11.070 but for the purpose of education and learning, 339 13:11.070 --> 13:13.290 I thought having completely separate 340 13:13.290 --> 13:16.170 IP addresses and separate ranges is gonna make it more clear 341 13:16.170 --> 13:18.030 about which end of the tunnel goes where. 342 13:18.030 --> 13:21.990 Alright, so back at the NSX deployment of Edge-2, 343 13:21.990 --> 13:24.690 we're gonna choose "DPG leads to vmnic3" 344 13:24.690 --> 13:27.720 as the port group that uses vmnic three that we wanna use. 345 13:27.720 --> 13:29.040 We'll click on "save" there. 346 13:29.040 --> 13:30.570 And now it's asking us about the assignment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 346 13:29.040 --> 13:30.570 And now it's asking us about the assignment 347 13:30.570 --> 13:32.970 of the IP address for the tunnel endpoint. 348 13:32.970 --> 13:35.640 So we're gonna go ahead and use a static IP list 349 13:35.640 --> 13:37.440 and then we'll scroll down and go ahead and put that in. 350 13:37.440 --> 13:40.650 And that's gonna be 44.44.44.44. 351 13:40.650 --> 13:43.470 And the default gateway is my top of rack switch 352 13:43.470 --> 13:45.150 or the top of rack infrastructure, 353 13:45.150 --> 13:47.490 which is 44.44.44.1, 354 13:47.490 --> 13:50.130 we looked at that earlier, verified that was in place. 355 13:50.130 --> 13:51.540 And we're using a 24 bit mask, 356 13:51.540 --> 13:53.040 so we'll put that in, as well. 357 13:53.040 --> 13:56.370 And I think we have specified all the details here 358 13:56.370 --> 13:57.720 that we need to for Edge-2. 359 13:57.720 --> 14:02.070 So we'll click on "finish" and it is on its way. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 359 13:57.720 --> 14:02.070 So we'll click on "finish" and it is on its way. 360 14:02.070 --> 14:03.520 So lemme manage the columns a little bit right here. 361 14:03.520 --> 14:05.940 Lemme go ahead and remove ID for a moment 362 14:05.940 --> 14:07.380 and the deployment type, 363 14:07.380 --> 14:09.660 and the management IP address, I'll remove. 364 14:09.660 --> 14:11.670 And the host that's running on, I'll remove. 365 14:11.670 --> 14:13.230 And I'll leave everything else 366 14:13.230 --> 14:15.330 and that'll make it just a little bit easier to read. 367 14:15.330 --> 14:18.120 So this Edge-2, which is now being deployed, again, 368 14:18.120 --> 14:20.250 this takes somewhere between 45 minutes 369 14:20.250 --> 14:22.590 and an hour to complete. 370 14:22.590 --> 14:24.000 So here on the vSphere Client, 371 14:24.000 --> 14:27.690 if we look at the tasks, it's now doing the deployment of 372 14:27.690 --> 14:30.360 that OVF template, effectively Edge-2, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 372 14:27.690 --> 14:30.360 that OVF template, effectively Edge-2, 373 14:30.360 --> 14:33.450 and it's deploying it now over on ESXIB. 374 14:33.450 --> 14:36.510 So if we went over to the VM and templates view, 375 14:36.510 --> 14:38.436 down here we have Edge-1 on it, 376 14:38.436 --> 14:39.269 that's the one I deployed earlier, 377 14:39.269 --> 14:40.530 and I'm just gonna drag and drop that 378 14:40.530 --> 14:44.040 into the folder called "Edge Node VMs" right there 379 14:44.040 --> 14:46.590 and then Edge-2, I'm not gonna try to move that 380 14:46.590 --> 14:49.230 until it is completely deployed. 381 14:49.230 --> 14:50.340 So I'm gonna go ahead and give 382 14:50.340 --> 14:53.430 that deployment probably another 45 minutes to an hour 383 14:53.430 --> 14:55.053 to go ahead and finish.