WEBVTT 1 00:00.000 --> 00:05.000 So now that we've deployed the automation VM right here at dot six on our 2 00:05.000 --> 00:08.100 management network and because we told it to go ahead and put the plug in there 3 00:08.100 --> 00:09.800 here as part of the NSX manager. 4 00:09.800 --> 00:13.760 If everything went well we should have this new plug in now available and 5 00:13.760 --> 00:16.200 usable right here from the NSX manager. 6 00:16.200 --> 00:17.300 So there's a couple of options. 7 00:17.300 --> 00:20.600 One is we could go ahead and use the automation wizard right here. 8 00:20.600 --> 00:24.900 Once the plug in is installed with that VM running or we could log in directly 9 00:24.900 --> 00:27.700 to this VM and run the automation from there. 10 00:27.700 --> 00:31.380 Either way we can launch the automation for deploying the Kubernetes cluster WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 10 00:27.700 --> 00:31.380 Either way we can launch the automation for deploying the Kubernetes cluster 11 00:31.380 --> 00:35.500 environment with Tanzu followed up by applying the NSX application platform as 12 00:35.500 --> 00:37.200 well on top of the Kubernetes environment. 13 00:37.200 --> 00:41.070 So also as part of the deployment that we just did in the previous video when I 14 00:41.070 --> 00:44.800 was checking on the status about I don't know 30 minutes ago it had failed. 15 00:44.800 --> 00:49.100 So what I did was simply run the deployment again to deploy that VM. 16 00:49.100 --> 00:53.210 So the very first thing I like to verify is just to confirm that that VM was 17 00:53.210 --> 00:57.300 correctly deployed that it finished and also that the plug in is right here. 18 00:57.300 --> 00:59.400 Available on the NSX manager. 19 00:59.400 --> 01:00.800 So let's do both right now. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 19 00:59.400 --> 01:00.800 So let's do both right now. 20 01:00.800 --> 01:04.500 So here in the vSphere client looks like it's not quite done yet. 21 01:04.500 --> 01:08.710 So we'll give that a moment to complete and just to confirm where that is we go 22 01:08.710 --> 01:10.700 to the VM and templates view here. 23 01:10.700 --> 01:15.800 Here's the nap automation VM right there in the folder called NSX VMs. 24 01:15.800 --> 01:19.600 So I'll give that just another moment or two to complete its deployment. 25 01:19.600 --> 01:22.800 Also prior to it being done over here at the NSX manager. 26 01:22.800 --> 01:27.300 Notice here in the NSX manager on the system tab over on the left we don't yet 27 01:27.300 --> 01:31.300 have the plug in for the NSX application platform automation. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 27 01:27.300 --> 01:31.300 have the plug in for the NSX application platform automation. 28 01:31.300 --> 01:35.800 And again once the automation VM is completely deployed and as that plug in 29 01:35.800 --> 01:37.800 that plug in should show up right here. 30 01:37.800 --> 01:41.610 So I'm going to give this a few more minutes to let it complete the deployment 31 01:41.610 --> 01:42.800 of the automation VM. 32 01:42.800 --> 01:43.800 All right. 33 01:43.800 --> 01:46.400 So that deployment it says is done. 34 01:46.400 --> 01:50.310 Let's go ahead and open a remote console and take a peek at what it shows on 35 01:50.310 --> 01:51.700 the console for that VM. 36 01:51.700 --> 01:56.200 So click here on launch remote console and here is the remote console. 37 01:56.200 --> 01:58.400 So this is not quite ready. 38 01:58.400 --> 02:02.600 So once it's fully ready it'll give us an indication right here on the screen WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 38 01:58.400 --> 02:02.600 So once it's fully ready it'll give us an indication right here on the screen 39 02:02.600 --> 02:07.960 that the plug in has been deployed over at the NSX manager and that we're ready 40 02:07.960 --> 02:08.200 to go. 41 02:08.200 --> 02:09.000 And there we go. 42 02:09.000 --> 02:10.700 It just refreshed and this looks great. 43 02:10.700 --> 02:12.000 Let me make this a little bit bigger. 44 02:12.000 --> 02:16.730 So here's showing us the IP address that's reachable at 10 11 11 6 and that the 45 02:16.730 --> 02:19.700 NSX user interface plug in was successful. 46 02:19.700 --> 02:23.780 And as a result we can either use the automation tool directly from the 47 02:23.780 --> 02:28.700 automation VM or we can use the plug in over here at the NSX manager. 48 02:28.700 --> 02:32.140 Additionally if we want to do it at the command line we have options for doing WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 48 02:28.700 --> 02:32.140 Additionally if we want to do it at the command line we have options for doing 49 02:32.140 --> 02:33.700 it at the command line as well. 50 02:33.700 --> 02:38.540 So to verify this let me first show you the actual interface here at 10 dot 11 51 02:38.540 --> 02:40.700 dot 11 dot 6 from a browser. 52 02:40.700 --> 02:45.850 So here's our connection over to 10 11 11 dot 6 and I'm going to go ahead and 53 02:45.850 --> 02:48.200 say advanced and say go ahead and proceed anyway. 54 02:48.200 --> 02:52.750 Even though we can't validate the certificate and here is the login for the NSX 55 02:52.750 --> 02:55.200 application platform automation VM. 56 02:55.200 --> 02:59.750 So if we log in here as admin and supply the password we set up and we click 57 02:59.750 --> 03:04.820 login it then gives the opportunity to go ahead and start the NSX application WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 57 02:59.750 --> 03:04.820 login it then gives the opportunity to go ahead and start the NSX application 58 03:04.820 --> 03:07.200 platform automation which effectively is running a wizard. 59 03:07.200 --> 03:12.610 Now if we don't want to do it right here at the interface for the automation VM 60 03:12.610 --> 03:16.200 itself because we opted to include the plug in at the NSX manager. 61 03:16.200 --> 03:21.200 We could run the same exact automation wizard over at the NSX manager. 62 03:21.200 --> 03:24.370 So here at the NSX manager with systems selected over here on the left I don't 63 03:24.370 --> 03:25.200 see the plug in. 64 03:25.200 --> 03:30.200 Let me go ahead and do an F5 on my Windows computer and refresh this screen. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 64 03:25.200 --> 03:30.200 Let me go ahead and do an F5 on my Windows computer and refresh this screen. 65 03:30.200 --> 03:32.200 Alright and that's a lot better. 66 03:32.200 --> 03:36.430 So now it's showing us the plug in right here that was included as part of the 67 03:36.430 --> 03:40.200 deployment and integration of the automation VM. 68 03:40.200 --> 03:45.220 So if we click here on nap automation from the NSX manager this screen right 69 03:45.220 --> 03:47.200 here looks very similar. 70 03:47.200 --> 03:52.460 So it's the exact same wizard that we can now run here at the NSX manager or we 71 03:52.460 --> 03:56.580 could launch it from the graphical user interface over at the automation VM 72 03:56.580 --> 03:57.200 itself. 73 03:57.200 --> 04:00.200 Also notice here for the nap automation before allows you to start this wizard. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 73 03:57.200 --> 04:00.200 Also notice here for the nap automation before allows you to start this wizard. 74 04:00.200 --> 04:03.200 It says please read this before you start. 75 04:03.200 --> 04:07.200 So the start button is grayed out until you click on read this before you start 76 04:07.200 --> 04:09.200 because there's a whole bunch of prerequisites that is there not met. 77 04:09.200 --> 04:11.200 This deployment is going to fail. 78 04:11.200 --> 04:14.320 So here in the prerequisites it says we need three routable networks, 79 04:14.320 --> 04:16.200 management workload and front end. 80 04:16.200 --> 04:18.200 We verified those previously in a previous skill. 81 04:18.200 --> 04:21.770 We need to make sure we're permitting the appropriate ports and protocols 82 04:21.770 --> 04:23.200 between those networks. 83 04:23.200 --> 04:27.200 Also on the management network which in our case is the 10/11/11 network. 84 04:27.200 --> 04:30.200 We need five consecutive available IP addresses. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 84 04:27.200 --> 04:30.200 We need five consecutive available IP addresses. 85 04:30.200 --> 04:33.200 So we're going to start with .41 for those. 86 04:33.200 --> 04:37.520 And on the workload network we're going to need to have 16 IP addresses that 87 04:37.520 --> 04:38.200 can be used. 88 04:38.200 --> 04:43.200 And so on the workload network which is VLAN 13 and our 10/13/13 subnet. 89 04:43.200 --> 04:47.120 We're going to go ahead and also start with the IP address of .41 on that 90 04:47.120 --> 04:48.200 network as well. 91 04:48.200 --> 04:51.780 And then here it says we need to make sure that the NSX manager, the automation 92 04:51.780 --> 04:56.310 appliance that's a .6 that we just deployed and vCenter all have IP 93 04:56.310 --> 04:57.200 connectivity. 94 04:57.200 --> 05:01.200 We also want to make sure that we have an NSX license as active and applied. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 94 04:57.200 --> 05:01.200 We also want to make sure that we have an NSX license as active and applied. 95 05:01.200 --> 05:05.040 And the next DNS, NTB and DHCP servers make sure they're configured and make 96 05:05.040 --> 05:08.200 sure you know what the IP addresses are involved with those. 97 05:08.200 --> 05:11.120 So we've already deployed and verified those services as part of our 98 05:11.120 --> 05:12.200 infrastructure network. 99 05:12.200 --> 05:15.720 It's also saying we need to have a VM storage policy configured and mapped to 100 05:15.720 --> 05:18.200 the data store that you'll be using for the NAP deployment. 101 05:18.200 --> 05:20.200 Now that is something that I did not do. 102 05:20.200 --> 05:24.200 So before we actually try to run the wizard, I'm going to click right here. 103 05:24.200 --> 05:25.200 I am ready. 104 05:25.200 --> 05:29.010 So before we actually run the wizard, I'm also going to go ahead and set up a 105 05:29.010 --> 05:32.850 storage policy and associate it with the data store we're going to be using for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 105 05:29.010 --> 05:32.850 storage policy and associate it with the data store we're going to be using for 106 05:32.850 --> 05:33.200 NAP. 107 05:33.200 --> 05:36.460 And if we don't have a storage policy associated with that data store, it is 108 05:36.460 --> 05:38.200 going to stop in its tracks. 109 05:38.200 --> 05:40.200 So let's head back to the vSphere client here for a moment. 110 05:40.200 --> 05:44.200 And let's go to our data stores and let's go down to iSCSI 2. 111 05:44.200 --> 05:47.200 We're going to use iSCSI 2 as our data store. 112 05:47.200 --> 05:48.200 I'm going to right click on it. 113 05:48.200 --> 05:51.470 And then from the menu, we're going to click right here on tags and custom 114 05:51.470 --> 05:53.200 attributes and let me assign a tag. 115 05:53.200 --> 05:56.200 So I've got a tag I've already set up called OGA T dash tag. 116 05:56.200 --> 05:58.200 I'm going to associate that with this data store. 117 05:58.200 --> 06:02.200 So I'll click on assign and then we click on summary for that data store. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 117 05:58.200 --> 06:02.200 So I'll click on assign and then we click on summary for that data store. 118 06:02.200 --> 06:04.200 Here is our tag right there. 119 06:04.200 --> 06:08.540 So previously, I'd use the hamburger menu here and went to policies and 120 06:08.540 --> 06:09.200 profiles. 121 06:09.200 --> 06:12.620 And I created a VM storage policy and it's right here called the KB storage 122 06:12.620 --> 06:13.200 policy. 123 06:13.200 --> 06:17.200 And as part of that policy, I'm looking for that specific tag. 124 06:17.200 --> 06:19.200 So I've got a storage compatibility. 125 06:19.200 --> 06:22.510 So again, it's important to have that done before we run the wizard because it 126 06:22.510 --> 06:25.200 's going to ask us about which data store we want to use. 127 06:25.200 --> 06:28.410 And if there's no storage policy associated with it, it's going to stop us 128 06:28.410 --> 06:29.200 right there. 129 06:29.200 --> 06:33.360 All right. So back to the NSX manager with system selected and on the left, the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 129 06:29.200 --> 06:33.360 All right. So back to the NSX manager with system selected and on the left, the 130 06:33.360 --> 06:35.200 plugin for NAP Automation selected. 131 06:35.200 --> 06:39.200 Now we can go ahead and click on start to start the deployment wizard. 132 06:39.200 --> 06:41.620 So we'll click on start and I'm going to go ahead on the left hand side and 133 06:41.620 --> 06:43.200 collapse that for a little bit more room. 134 06:43.200 --> 06:46.200 So the first question is which vCenter are we going to be using? 135 06:46.200 --> 06:48.200 So I'm going to click right here on connect now. 136 06:48.200 --> 06:52.200 I'm going to go ahead and put in the DNS name of our vCenter again. 137 06:52.200 --> 06:56.200 That's just confirming as we go that our name resolution is working. 138 06:56.200 --> 07:00.750 So I'm going to do an NS look up for 10 dot 11 dot 11 dot 11 dot 11, which is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 138 06:56.200 --> 07:00.750 So I'm going to do an NS look up for 10 dot 11 dot 11 dot 11 dot 11, which is 139 07:00.750 --> 07:02.200 the IP address of our vCenter. 140 07:02.200 --> 07:06.480 And that way I can just highlight it right here, the DNS name press enter and 141 07:06.480 --> 07:09.200 then go back to the wizard and right click and just paste it in. 142 07:09.200 --> 07:13.200 Then I'll supply the login and the password to log in to that vCenter. 143 07:13.200 --> 07:18.750 So there is the single sign on admin name for that vCenter and I've supplied 144 07:18.750 --> 07:20.200 the password and we'll click on connect. 145 07:20.200 --> 07:23.150 So now it's connected to this that vCenter and so I'm going to choose the data 146 07:23.150 --> 07:24.200 center I want to use. 147 07:24.200 --> 07:25.200 So I only have one. 148 07:25.200 --> 07:29.340 That's the LV lab one and then the cluster I want to use, which is the host for 149 07:29.340 --> 07:30.200 NAP cluster. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 149 07:29.340 --> 07:30.200 NAP cluster. 150 07:30.200 --> 07:33.200 And then the data store I want to use, which I want to use. 151 07:33.200 --> 07:35.200 I SCSI dash two. 152 07:35.200 --> 07:40.200 And then based on that, we should have as an option a storage policy and that's 153 07:40.200 --> 07:42.200 the KB storage policy that I created and I'm going to use a storage policy. 154 07:42.200 --> 07:45.980 And then I want to use a storage policy that I created and associated with that 155 07:45.980 --> 07:46.200 data store. 156 07:46.200 --> 07:47.200 And that's what I want to use. 157 07:47.200 --> 07:52.040 So if you want to use the storage policy called VM encryption, you also need to 158 07:52.040 --> 07:56.200 make sure you take a few steps at vCenter and set up TPM support. 159 07:56.200 --> 07:58.200 However, that's just one more layer of things that can go wrong. 160 07:58.200 --> 08:02.920 So I'm going to use my KB storage policy and in that policy, we're just doing WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 160 07:58.200 --> 08:02.920 So I'm going to use my KB storage policy and in that policy, we're just doing 161 08:02.920 --> 08:04.200 thin provisioning wherever possible. 162 08:04.200 --> 08:07.740 So in this first section done, we'll click on next and continue on with the 163 08:07.740 --> 08:08.200 wizard. 164 08:08.200 --> 08:12.430 So it's asking us about the three networks that we're going to be using for the 165 08:12.430 --> 08:15.200 deployment of our NAP and our Kubernetes. 166 08:15.200 --> 08:18.220 So for the management network, we use the dropdown and we're going to select 167 08:18.220 --> 08:21.200 the port group associated with VLAN 11, which is that one. 168 08:21.200 --> 08:25.200 And then for the front end, we'll use our port group associated with VLAN 12, 169 08:25.200 --> 08:26.200 which is that one. 170 08:26.200 --> 08:29.880 And for the workload, we're going to go ahead and use the dropdown and select 171 08:29.880 --> 08:32.200 this port group associated with VLAN 13. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 171 08:29.880 --> 08:32.200 this port group associated with VLAN 13. 172 08:32.200 --> 08:39.200 So that's an important reminder. We want to have all of those networks and port 173 08:39.200 --> 08:39.200 groups set up and verified before we get to this point. 174 08:39.200 --> 08:42.200 And then it's asking us about the default gateway for each of those networks. 175 08:42.200 --> 08:45.610 So based on our topology for those three networks, the default gateway is at 176 08:45.610 --> 08:46.200 dot one. 177 08:46.200 --> 08:50.480 So this is not just carrying about the default gateway, but it also wants to 178 08:50.480 --> 08:54.200 know the mask associated with each of those subnets. 179 08:54.200 --> 08:55.200 So that's what we're going to supply next. 180 08:55.200 --> 08:59.710 So for the management network, which is the 10 11 11 network, the default 181 08:59.710 --> 09:04.200 gateway is 10 dot 11 dot 11 dot one, and then we'll put a slash 24. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 181 08:59.710 --> 09:04.200 gateway is 10 dot 11 dot 11 dot one, and then we'll put a slash 24. 182 09:04.200 --> 09:07.350 And that's also supplying that information to the wizard regarding the length 183 09:07.350 --> 09:08.200 of the networks. 184 09:08.200 --> 09:12.200 So for the front end network, the default gateway is 10 dot 12 dot 12 dot one 185 09:12.200 --> 09:14.200 with a 24 bit mask. 186 09:14.200 --> 09:18.990 And then for the workload network, the default gateway is 10 dot 13 dot 13 dot 187 09:18.990 --> 09:20.200 one with a 24 mask. 188 09:20.200 --> 09:25.200 And then for NTP server, it's reachable at 10 dot 10 dot 100. 189 09:25.200 --> 09:29.190 And the DNS server is the same IP address. So I'm going to go ahead and copy 190 09:29.190 --> 09:32.200 paste that. And then the search domain is OG a T dot lab. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 190 09:29.190 --> 09:32.200 paste that. And then the search domain is OG a T dot lab. 191 09:32.200 --> 09:35.200 So with that supplied, we'll go ahead and click on next. 192 09:35.200 --> 09:39.200 Now it's asking us about the details for the proxy. It's going to deploy. 193 09:39.200 --> 09:43.490 So for that little VM, the proxy VM, we're going to use the IP address of dot 194 09:43.490 --> 09:48.200 five on the management network and dot five on the front end network and dot 195 09:48.200 --> 09:49.200 five on the workload network. 196 09:49.200 --> 09:52.830 So we'll supply that information next. So on the management network, we'll go 197 09:52.830 --> 09:56.200 ahead and use 10 dot 11 dot five. 198 09:56.200 --> 09:59.210 And it already knows the mask associated with that network because we did that 199 09:59.210 --> 10:00.200 in the previous step. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 199 09:59.210 --> 10:00.200 in the previous step. 200 10:00.200 --> 10:05.200 And for the front end, we want the proxy to use 10 dot 12 dot 12 dot five. 201 10:05.200 --> 10:09.510 And for the workload network, we're going to use 10 dot 13 dot 13 dot five just 202 10:09.510 --> 10:10.200 like that. 203 10:10.200 --> 10:14.200 And then we'll supply a password over here for the proxy VM. 204 10:14.200 --> 10:16.200 So I'll go ahead and supply that password right there. 205 10:16.200 --> 10:19.890 So based on the network address space for using for the front end, it wants to 206 10:19.890 --> 10:24.920 use this range of addresses for the virtual IP addresses for the load balancer 207 10:24.920 --> 10:26.200 on that subnet. 208 10:26.200 --> 10:30.200 So effectively, that's 10, 12, 12, 16 all the way through 31. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 208 10:26.200 --> 10:30.200 So effectively, that's 10, 12, 12, 16 all the way through 31. 209 10:30.200 --> 10:34.200 That's the range covered by this address space with that slash 28. 210 10:34.200 --> 10:37.620 And for a deeper dive into the world of IP addressing and subnetting, check out 211 10:37.620 --> 10:39.200 our courses here at CV tonight. 212 10:39.200 --> 10:43.750 It's either the network plus course that's going to have a lot of great details 213 10:43.750 --> 10:47.200 there as well as the Cisco CCNA course where here at CVT. 214 10:47.200 --> 10:49.200 That gets for more details on subnetting. 215 10:49.200 --> 10:53.000 So that was automatically recommended based on the IP addressing space we're 216 10:53.000 --> 10:54.200 using on the front end. 217 10:54.200 --> 10:56.200 So I'm going to go ahead and take that recommendation and use it. 218 10:56.200 --> 10:59.790 So then we'll click on next and that takes us to the next step, which is to 219 10:59.790 --> 11:02.200 configure the management and workload IPs. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 219 10:59.790 --> 11:02.200 configure the management and workload IPs. 220 11:02.200 --> 11:06.600 And so here's where we wanted to use dot 41 as the starting range for those 221 11:06.600 --> 11:12.200 addresses on the 10 11 11 network and also on the 10 13 13 network. 222 11:12.200 --> 11:17.500 So for the 10 11 11 management network, we'll put in 10 dot 11 dot 11 dot 41 223 11:17.500 --> 11:21.200 and it'll automatically calculate the next four consecutive IPs. 224 11:21.200 --> 11:24.200 So it'll be 41 all the way through 45. 225 11:24.200 --> 11:27.800 And then on the workload network, let's also use the dot 41 for the beginning 226 11:27.800 --> 11:31.200 of that range, so we'll type in 10 dot 13 dot 13 dot 41. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 226 11:27.800 --> 11:31.200 of that range, so we'll type in 10 dot 13 dot 13 dot 41. 227 11:31.200 --> 11:35.620 And once again, it automatically calculates 41 with 16 IP addresses through the 228 11:35.620 --> 11:37.200 ending range of dot 56. 229 11:37.200 --> 11:41.200 So if that's what we want to use, we'll put those in and click on next. 230 11:41.200 --> 11:43.200 And now it's asking us for the repository type. 231 11:43.200 --> 11:47.520 Do you want to use VMware's public VMware hosted repository or do you already 232 11:47.520 --> 11:51.200 have a repository for the helm and the Docker set up locally. 233 11:51.200 --> 11:55.740 Now, I'm going to use the public repository. So I'm going to choose public and 234 11:55.740 --> 11:59.200 use the defaults here and then we'll scroll down and click on next. 235 11:59.200 --> 12:03.220 And now it's step six with the automation. It's asking us about details for the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 235 11:59.200 --> 12:03.220 And now it's step six with the automation. It's asking us about details for the 236 12:03.220 --> 12:04.200 nap instance. 237 12:04.200 --> 12:07.480 So I'm going to go ahead where it says default. I'm going to click on the three 238 12:07.480 --> 12:09.200 dots and say delete and remove that. 239 12:09.200 --> 12:12.440 And I'm going to go ahead and put in a custom instance that we can easily 240 12:12.440 --> 12:13.200 recognize. 241 12:13.200 --> 12:17.110 So I'll click here and add nap instance. And I'm going to call this our nap 242 12:17.110 --> 12:18.200 instance one. 243 12:18.200 --> 12:22.170 And this has to be lowercase. And the reason I'm going to call it our nap 244 12:22.170 --> 12:25.520 instance one is that if we have to troubleshoot and do it again, we can go 245 12:25.520 --> 12:27.200 ahead and use nap instance two or three. 246 12:27.200 --> 12:32.050 And now it's asking us about the IP address or fully qualified domain name for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 246 12:27.200 --> 12:32.050 And now it's asking us about the IP address or fully qualified domain name for 247 12:32.050 --> 12:37.200 the NSX manager. So just to verify that, let's go ahead and do a look up. 248 12:37.200 --> 12:40.670 I'll do a reverse look up for 121, which is the IP address for using for NSX 249 12:40.670 --> 12:43.200 manager. And there is its domain name right there. 250 12:43.200 --> 12:47.690 So I'm going to copy that and paste it in. So there's the NSX manager fully 251 12:47.690 --> 12:50.200 qualified domain name right there. 252 12:50.200 --> 12:54.470 And then I'll specify the username and password required to log in to that NSX 253 12:54.470 --> 12:57.200 manager. And then with that supplied, we'll click on next. 254 12:57.200 --> 13:01.110 So now it's asking us about the version and the form factor. And so from the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 254 12:57.200 --> 13:01.110 So now it's asking us about the version and the form factor. And so from the 255 13:01.110 --> 13:06.200 drop down here, it's only going to give you the options that are compatible 256 13:06.200 --> 13:08.200 with the version of NSX that we're currently using. 257 13:08.200 --> 13:12.040 And that's going to be helpful in not choosing an older version of the nap that 258 13:12.040 --> 13:16.200 may not be compatible with the flavor or the version of NSX that we're running. 259 13:16.200 --> 13:20.470 So it's already chosen for me this four dot one, one, which I'll go ahead and 260 13:20.470 --> 13:24.170 select. And then for the form factor, I'm going to go ahead and choose 261 13:24.170 --> 13:25.200 evaluation. 262 13:25.200 --> 13:29.770 So if we choose evaluation, it's not going to require the quantity of workers 263 13:29.770 --> 13:33.200 and control nodes as part of Kubernetes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 263 13:29.770 --> 13:33.200 and control nodes as part of Kubernetes. 264 13:33.200 --> 13:36.410 That would be required if we're doing a production environment. So for a lab 265 13:36.410 --> 13:39.770 environment, that's perfectly fine. Also for a lab environment, we don't have 266 13:39.770 --> 13:42.200 to reserve all the CPU and memory for each of those. 267 13:42.200 --> 13:45.640 So I'm going to go ahead for my lab and say, you know what, I'm not going to 268 13:45.640 --> 13:49.040 reserve the memory and CPU for all the VMs that are deployed as part of the 269 13:49.040 --> 13:51.200 supervisors and Kubernetes cluster. 270 13:51.200 --> 13:55.450 So with that selected, we'll click on next. And now it's asking us to put in 271 13:55.450 --> 14:00.650 two fully qualified domain names that map to these two IP addresses 10, 12, 19 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 271 13:55.450 --> 14:00.650 two fully qualified domain names that map to these two IP addresses 10, 12, 19 272 14:00.650 --> 14:04.200 and 10, 12, 12, 20, respectively. 273 14:04.200 --> 14:08.480 Now we have our DNS server, which in my environment is running on Windows 274 14:08.480 --> 14:12.200 Server. And that's the server over at 10 dot 10 dot 100. 275 14:12.200 --> 14:16.490 So I've already set up IPV for a records in DNS regarding those two IP 276 14:16.490 --> 14:20.070 addresses and to verify those. Once again, I'm going to go to a client and 277 14:20.070 --> 14:21.200 verify it right here. 278 14:21.200 --> 14:25.170 So the first one I want to verify is the 10, 12, 12, 19, so we'll do an NS 279 14:25.170 --> 14:29.720 lookup or 10 dot 12 dot 19. And because I created pointer records for reverse 280 14:29.720 --> 14:32.200 lookup, this is going to be very helpful right here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 280 14:29.720 --> 14:32.200 lookup, this is going to be very helpful right here. 281 14:32.200 --> 14:36.530 So there is the fully qualified domain name that maps to this IP address right 282 14:36.530 --> 14:39.200 there. So I'm going to go ahead and copy that. 283 14:39.200 --> 14:42.340 And for the service name, I'm going to go ahead and paste it in right there. 284 14:42.340 --> 14:45.550 And then for the messaging name, I'm going to go ahead and hit the up arrow key 285 14:45.550 --> 14:49.650 and let's do a reverse lookup for the name behind 10, 12, 12, 20, which I 286 14:49.650 --> 14:50.200 created in my DNS. 287 14:50.200 --> 14:54.700 And there is the name right there. So once again, I'm going to go ahead and 288 14:54.700 --> 14:58.650 copy that and paste it right there. So I verified that these two names resolve 289 14:58.650 --> 15:01.200 to those two IP addresses respectively. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 289 14:58.650 --> 15:01.200 to those two IP addresses respectively. 290 15:01.200 --> 15:05.950 And then once that's done, we'll click on add. So those here that in step six, 291 15:05.950 --> 15:10.030 it has our instance name right here. It has the NSX manager and the net version 292 15:10.030 --> 15:11.200 and they form factor. 293 15:11.200 --> 15:14.600 But as far as the control plane nodes and the worker nodes, those should show 294 15:14.600 --> 15:18.620 one each. So I'm going to click right here on done with configuration run pre 295 15:18.620 --> 15:19.200 check. 296 15:19.200 --> 15:23.170 And that's going to do the pre checks, which all look good. Now the reason all 297 15:23.170 --> 15:26.670 of this looks good is because we did the pre work earlier to make sure that our 298 15:26.670 --> 15:30.200 network infrastructure, including DNS and everything else was correct. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 298 15:26.670 --> 15:30.200 network infrastructure, including DNS and everything else was correct. 299 15:30.200 --> 15:34.840 So also, I'm going to click on back here, just to verify our steps. So because 300 15:34.840 --> 15:39.200 we just click on back, we just click on next confirm each of our steps. 301 15:39.200 --> 15:42.780 And you may have to run through this wizard a couple of times, just to make 302 15:42.780 --> 15:46.340 sure everything takes like if it stalls or stops, you may have to go ahead and 303 15:46.340 --> 15:47.200 run it back. 304 15:47.200 --> 15:51.810 So now it's showing control plane nodes is one worker nodes is one. We'll click 305 15:51.810 --> 15:54.200 on done with configuration run pre checks. 306 15:54.200 --> 15:57.830 And then this is the pre check information from before. And if we want to run 307 15:57.830 --> 16:01.430 the pre checks again, which is not a bad idea, we'll simply click here on run WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 307 15:57.830 --> 16:01.430 the pre checks again, which is not a bad idea, we'll simply click here on run 308 16:01.430 --> 16:02.200 pre check. 309 16:02.200 --> 16:05.630 And that's going to run the pre checks again. Now, if any of these fail or 310 16:05.630 --> 16:09.670 stall or they don't work and you think they're correct, you can just click on 311 16:09.670 --> 16:12.200 back, put in the details again. 312 16:12.200 --> 16:15.750 Like right now, it is stalling here on the check supervisor cluster networking, 313 16:15.750 --> 16:20.200 which it passed previously. So I'm going to go ahead and give it what it wants. 314 16:20.200 --> 16:24.010 So I'm going to go ahead and click on back and simply confirm all these 315 16:24.010 --> 16:28.720 settings by checking them, clicking a next and next and next and next, and then 316 16:28.720 --> 16:32.200 clicking on done with configuration run pre checks. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 316 16:28.720 --> 16:32.200 clicking on done with configuration run pre checks. 317 16:32.200 --> 16:36.380 So here I'm going to go ahead and click on run pre check one more time. And I 318 16:36.380 --> 16:39.850 want to make sure that everything passes. And that all looks good. So with all 319 16:39.850 --> 16:42.200 the pre checks done, let's go ahead and click on next. 320 16:42.200 --> 16:46.540 So what we're going to do here is super important to pay attention to this is 321 16:46.540 --> 16:51.170 talking about the connectivity required between source and destination, 322 16:51.170 --> 16:54.200 including what protocols and services are needed. 323 16:54.200 --> 16:58.030 So we want to make sure that we're using any kind of distributed firewall or 324 16:58.030 --> 17:01.320 filtering of any type. We want to make sure we're allowing from these sources WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 324 16:58.030 --> 17:01.320 filtering of any type. We want to make sure we're allowing from these sources 325 17:01.320 --> 17:03.200 to these destinations, these protocols. 326 17:03.200 --> 17:06.950 So we're going to go ahead and click on next and then now we're in the stage 327 17:06.950 --> 17:16.200 right here for the deploying Tanzu Kubernetes grid, the TKGs. 328 17:16.200 --> 17:20.980 And to kick this part off, we then go ahead down here on the bottom right and 329 17:20.980 --> 17:27.400 click on deploy slash update. And that's going to go ahead and start the 330 17:27.400 --> 17:34.200 process of making sure we have DRS and HA enabled on our cluster. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 330 17:27.400 --> 17:34.200 process of making sure we have DRS and HA enabled on our cluster. 331 17:34.200 --> 17:41.610 And that was deploying the H a proxy. And at any point of it stops or stalls, 332 17:41.610 --> 17:47.630 we may need to go back and run the wizard again. And the cool news is it can 333 17:47.630 --> 17:51.200 pick up where it left off. You don't have to do the whole thing from scratch. 334 17:51.200 --> 17:56.480 So this process right here about, I don't know, an hour to complete because it 335 17:56.480 --> 18:01.200 will take a little while for the deployment of all the components. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 335 17:56.480 --> 18:01.200 will take a little while for the deployment of all the components. 336 18:01.200 --> 18:05.590 So join me the next video as we pick up where this one left off, and we'll 337 18:05.590 --> 18:10.520 either pick up where it completed successfully or we'll pick up where it ceases 338 18:10.520 --> 18:13.200 to work, and we'll do the troubleshooting. 339 18:13.200 --> 18:15.800 I'll see you in the next video for the next step.