WEBVTT 1 00:00.000 --> 00:03.920 So it has been, I don't know, 15, 20 minutes, 2 00:03.920 --> 00:06.920 and it seems to be stuck right here waiting for certificates. 3 00:06.920 --> 00:10.760 So it said it checked DRS, make sure it's fully automated, 4 00:10.760 --> 00:14.320 and the HA was enabled on the cluster called HOSFRNAP, 5 00:14.320 --> 00:16.160 then it deployed the load balancer VM, 6 00:16.160 --> 00:17.560 and now it's waiting for certificates. 7 00:17.560 --> 00:18.680 So I'm going to do a couple of things. 8 00:18.680 --> 00:20.320 I'm going to click on back right here, 9 00:20.320 --> 00:23.840 and then back again, and then back again, 10 00:23.840 --> 00:25.960 and I just want to confirm all my settings here, 11 00:25.960 --> 00:28.200 and then we'll take a look at the vSphere client as well. 12 00:28.200 --> 00:32.840 So that hasn't changed, nor has that, nor has that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 12 00:28.200 --> 00:32.840 So that hasn't changed, nor has that, nor has that. 13 00:32.840 --> 00:36.600 That all looks good, and click on next, and next, 14 00:36.600 --> 00:39.280 and that looks good, click on next. 15 00:39.280 --> 00:40.360 All right, so all this looks pretty good. 16 00:40.360 --> 00:44.360 I'll click on done, and let me run the prechecks one more time. 17 00:44.360 --> 00:47.480 So the prechecks all look good, so we'll click on next, 18 00:47.480 --> 00:49.320 and then next, and sure enough, 19 00:49.320 --> 00:51.680 it is still waiting right there. 20 00:51.680 --> 00:53.560 So I'm going to go back to the vSphere client, 21 00:53.560 --> 00:54.960 and let's check a couple things. 22 00:54.960 --> 00:57.120 And let's go to the vCenter itself on top, 23 00:57.120 --> 01:01.080 and let's go to monitor, and let's take a look at tasks. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 00:57.120 --> 01:01.080 and let's go to monitor, and let's take a look at tasks. 24 01:01.080 --> 01:02.840 What I'm looking for is anything that fails. 25 01:02.840 --> 01:06.920 So right here, power on virtual machine, HAProxy. 26 01:06.920 --> 01:10.040 No host is compatible with the virtual machine. 27 01:10.040 --> 01:13.360 So it could never deploy that, and why is that? 28 01:13.360 --> 01:14.640 So let's go take a look. 29 01:14.640 --> 01:16.280 So let's go to the VM and templates view. 30 01:16.280 --> 01:18.360 So there's our HAProxy right there. 31 01:18.360 --> 01:19.960 I'm going to go ahead and right click, 32 01:19.960 --> 01:22.880 and I'm going to delete that from disk, just to get rid of it. 33 01:22.880 --> 01:24.960 And that was attempting to be deployed 34 01:24.960 --> 01:26.480 in this cluster right here. 35 01:26.480 --> 01:29.640 So if we go to that cluster, as part of the automation tasks, 36 01:29.640 --> 01:32.600 it said it was confirming that on this cluster WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 01:29.640 --> 01:32.600 it said it was confirming that on this cluster 37 01:32.600 --> 01:36.680 that we had DRS and HA enabled for that cluster. 38 01:36.680 --> 01:39.080 So if I go to that cluster and go to configure, 39 01:39.080 --> 01:43.440 so for DRS, it is enabled, and for availability, 40 01:43.440 --> 01:48.160 it is also, so I did not enable HA on this cluster. 41 01:48.160 --> 01:50.480 That was the automation that did it for us. 42 01:50.480 --> 01:53.160 So it could be that it deployed the vSphere HA, 43 01:53.160 --> 01:56.760 and then attempted to deploy the HAProxy 44 01:56.760 --> 02:00.400 before the HA was completely activated and running. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 44 01:56.760 --> 02:00.400 before the HA was completely activated and running. 45 02:00.400 --> 02:03.600 So then we verified that the HA is turned on. 46 02:03.600 --> 02:05.880 I'm also going to take a moment for this cluster 47 02:05.880 --> 02:08.360 and go to updates and just validate 48 02:08.360 --> 02:11.320 that all the hosts in this cluster are in compliance. 49 02:11.320 --> 02:13.320 So we'll click here on check compliance. 50 02:13.320 --> 02:15.280 And once we've confirmed that these three hosts 51 02:15.280 --> 02:17.440 are compliant with the cluster, 52 02:17.440 --> 02:19.440 meaning they also support HA, 53 02:19.440 --> 02:21.520 let's go ahead and we'll go back to the automation wizard 54 02:21.520 --> 02:22.640 and we'll try it again. 55 02:22.640 --> 02:24.680 All right, so it's showing us that for this cluster, 56 02:24.680 --> 02:27.040 all three hosts are compliant, fantastic. 57 02:27.040 --> 02:29.520 So let's go back to the NSX manager 58 02:29.520 --> 02:31.880 and let's go to the automation plugin once again. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 58 02:29.520 --> 02:31.880 and let's go to the automation plugin once again. 59 02:31.880 --> 02:35.760 So back here, we'll click on back and back and back, 60 02:35.760 --> 02:37.600 and I'm gonna go through all the steps again, 61 02:37.600 --> 02:38.960 just to confirm my settings, 62 02:38.960 --> 02:40.720 and then we'll try the deployment again. 63 02:40.720 --> 02:44.080 So next, and that looks good for step two next, 64 02:44.080 --> 02:48.160 and here's the HAProxy information, click next and next. 65 02:48.160 --> 02:50.200 And there's our public registry that we're gonna be using 66 02:50.200 --> 02:51.400 and click on next. 67 02:51.400 --> 02:54.280 And here is our NAP instance that we're gonna be using, 68 02:54.280 --> 02:57.600 and we'll click on done with configuration, run precheck, 69 02:57.600 --> 02:59.840 and then we'll click here on rerun precheck, 70 02:59.840 --> 03:01.560 just to validate that everything's in place, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 70 02:59.840 --> 03:01.560 just to validate that everything's in place, 71 03:01.560 --> 03:03.040 ready to go, that looks good, 72 03:03.040 --> 03:04.520 and then we'll click on next. 73 03:04.520 --> 03:05.800 And there's the permissions that are needed 74 03:05.800 --> 03:07.840 between these sources and these destinations 75 03:07.840 --> 03:09.960 with these services and our ports and protocols, 76 03:09.960 --> 03:11.520 and we'll click on next. 77 03:11.520 --> 03:14.840 So look at this, now it shows that the HAProxy certificate 78 03:14.840 --> 03:17.040 is generated and that also implies 79 03:17.040 --> 03:20.400 that it redeployed the HAProxy. 80 03:20.400 --> 03:22.040 So let's go back to the vSphere client 81 03:22.040 --> 03:24.880 and just verify that the HAProxy that we deleted 82 03:24.880 --> 03:27.400 a few minutes ago, did it redeployed that. 83 03:27.400 --> 03:29.160 So back here at the vSphere client, 84 03:29.160 --> 03:31.520 let's go to the VM and templates view, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 84 03:29.160 --> 03:31.520 let's go to the VM and templates view, 85 03:31.520 --> 03:35.160 and let's go to the very top here and click on VMs, 86 03:35.160 --> 03:38.880 and I do not see the HAProxy, 87 03:38.880 --> 03:42.240 which means that it thinks it's deployed, 88 03:42.240 --> 03:44.680 but it is not there because I deleted it. 89 03:44.680 --> 03:45.840 So let's go back to the automation, 90 03:45.840 --> 03:47.600 so it's currently in the process 91 03:47.600 --> 03:51.200 of deploying the content library that's gonna be used 92 03:51.200 --> 03:52.880 as part of the Kubernetes, 93 03:52.880 --> 03:57.520 but what we really need to do is have it redeploy the HAProxy. 94 03:57.520 --> 03:59.480 So to facilitate that, I'm gonna go ahead 95 03:59.480 --> 04:02.480 and click on back and back and back, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 95 03:59.480 --> 04:02.480 and click on back and back and back, 96 04:02.480 --> 04:05.520 and I'm gonna go ahead and change the instance name 97 04:05.520 --> 04:08.080 so it can go ahead and redeploy the HAProxy. 98 04:08.080 --> 04:10.360 So I'm gonna use the same data center, 99 04:10.360 --> 04:13.480 same cluster, same data store, same storage policy, 100 04:13.480 --> 04:18.480 next and next and next and next, and then for the NAP instance, 101 04:18.480 --> 04:22.480 I'm gonna go ahead and delete this one and click on remove, 102 04:22.480 --> 04:23.920 and then click on add. 103 04:23.920 --> 04:27.440 For the instance, I'm gonna go ahead and put our N number two, 104 04:27.440 --> 04:29.980 just to make it different from our first one. 105 04:29.980 --> 04:32.080 Then our NSX manager is here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 105 04:29.980 --> 04:32.080 Then our NSX manager is here, 106 04:32.080 --> 04:35.480 I'll put in the username and password for the NSX manager, 107 04:35.480 --> 04:36.960 and then click on next, 108 04:36.960 --> 04:39.820 and then we'll go ahead and use that NAP version, fantastic. 109 04:39.820 --> 04:42.280 We use the evaluation form factor. 110 04:42.280 --> 04:44.880 We won't reserve all the CPU and memory for all those nodes, 111 04:44.880 --> 04:46.680 click on next, and then we'll put in the names 112 04:46.680 --> 04:50.840 that resolve to 12, 12, 19 and 12, 12, 20, respectively. 113 04:50.840 --> 04:53.680 So this first one is lab-service.ogat.lab 114 04:53.680 --> 04:55.440 that resolves to that IP address, 115 04:55.440 --> 04:58.160 and then this DNS name resolves to that IP address. 116 04:58.160 --> 05:00.740 We verified that earlier, so we'll click on add, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 116 04:58.160 --> 05:00.740 We verified that earlier, so we'll click on add, 117 05:00.740 --> 05:02.360 and then we'll click on done, 118 05:02.360 --> 05:05.800 and then we'll rerun the pre-check by clicking on rerun pre-check, 119 05:05.800 --> 05:07.440 and that is completed, that's great, 120 05:07.440 --> 05:10.000 and then we'll click on next, and then next. 121 05:10.000 --> 05:13.360 And it looks like at this point, it's still not going back 122 05:13.360 --> 05:16.560 to redeploy the HA proxy VM. 123 05:16.560 --> 05:19.480 So I am going to do one additional thing, 124 05:19.480 --> 05:21.420 and that is this. 125 05:21.420 --> 05:23.200 Let's go back to the beginning. 126 05:23.200 --> 05:24.760 So I'm gonna go ahead and cancel, 127 05:24.760 --> 05:27.720 and I'm gonna go to settings, and I say reset, 128 05:27.720 --> 05:30.480 to reset everything, and then we can start from scratch, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 128 05:27.720 --> 05:30.480 to reset everything, and then we can start from scratch, 129 05:30.480 --> 05:32.200 including using a new instance, 130 05:32.200 --> 05:34.720 and for this time, I'm gonna go ahead and use instance three. 131 05:34.720 --> 05:38.000 So once again here at the plugin for NAP automation, 132 05:38.000 --> 05:40.400 we'll go ahead and we will run the wizard again. 133 05:40.400 --> 05:41.360 So start. 134 05:41.360 --> 05:42.800 So then we'll put the details in again. 135 05:42.800 --> 05:45.320 Now also, probably in a production environment, 136 05:45.320 --> 05:47.840 what we'd wanna do is allow or wait 137 05:47.840 --> 05:51.520 for the previous deployment to completely fail and stop. 138 05:51.520 --> 05:53.240 And then make sure we have a nice fresh start. 139 05:53.240 --> 05:55.120 So here, I'm gonna click on next, 140 05:55.120 --> 05:57.880 and it appears that it still remembers everything 141 05:57.880 --> 05:59.080 from what we did earlier. 142 05:59.080 --> 06:01.800 So I'm gonna click on next a few more times. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 142 05:59.080 --> 06:01.800 So I'm gonna click on next a few more times. 143 06:01.800 --> 06:05.060 Let's go ahead and just confirm all those details, 144 06:05.060 --> 06:07.840 and then let me go ahead and make yet another instance here, 145 06:07.840 --> 06:09.680 and then we go ahead and delete the existing one. 146 06:09.680 --> 06:12.400 That's NAP two, we'll click on remove and add. 147 06:12.400 --> 06:14.080 We'll call this one NAP three, 148 06:14.080 --> 06:17.400 we'll put in a NSX manager information, click on next, 149 06:17.400 --> 06:19.960 select the form factor of evaluation 150 06:19.960 --> 06:22.800 with no reservations for a CPU memory, next. 151 06:22.800 --> 06:25.160 And then again, the names that resulted that 19 and 20. 152 06:25.160 --> 06:26.400 And then click on add. 153 06:26.400 --> 06:28.920 And then click on done, it's running the pre-checks, 154 06:28.920 --> 06:31.400 click on next, and we'll click on next. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 154 06:28.920 --> 06:31.400 click on next, and we'll click on next. 155 06:31.400 --> 06:34.160 And then we'll click right here on deploy slash update, 156 06:34.160 --> 06:35.960 and that looks a lot better. 157 06:35.960 --> 06:37.800 So it's gonna start the process over, 158 06:37.800 --> 06:40.800 including deploying the HA proxy. 159 06:40.800 --> 06:43.800 So in the documentation for the NAP automation, 160 06:43.800 --> 06:45.720 it mentions that you may have to go back and forth 161 06:45.720 --> 06:47.720 a couple of times inside these wizards 162 06:47.720 --> 06:51.080 as part of the automation to make sure everything works. 163 06:51.080 --> 06:53.320 So at this point, just like we did previously, 164 06:53.320 --> 06:56.320 we'll let this go ahead and run for anywhere between 30 165 06:56.320 --> 07:00.480 and 45 minutes until it gets stuck at one of the points, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 165 06:56.320 --> 07:00.480 and 45 minutes until it gets stuck at one of the points, 166 07:00.480 --> 07:03.400 at which point we'll troubleshoot or until it completes. 167 07:03.400 --> 07:07.560 But now that we already have DRS and HA already enabled 168 07:07.560 --> 07:11.680 on the cluster, as it deploys this HA VM on that cluster 169 07:11.680 --> 07:15.120 that requires DRS and HA, hopefully that'll complete 170 07:15.120 --> 07:15.960 successfully. 171 07:15.960 --> 07:17.800 In fact, before we leave this video, 172 07:17.800 --> 07:21.120 let's just verify real quick that that HA VM 173 07:21.120 --> 07:23.680 is currently deployed as it just as it did 174 07:23.680 --> 07:25.520 and make sure that it is running. 175 07:25.520 --> 07:28.000 So to do that, let's hop over to the vSphere client. 176 07:28.000 --> 07:30.600 So here at the vSphere client, there it is right there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 176 07:28.000 --> 07:30.600 So here at the vSphere client, there it is right there. 177 07:30.600 --> 07:34.000 There's the HA proxy and it is running, 178 07:34.000 --> 07:35.640 which is fantastic news. 179 07:35.640 --> 07:39.680 And if we go to recent tasks and we look at all recent tasks 180 07:39.680 --> 07:41.280 and bring that up a little bit, 181 07:41.280 --> 07:43.920 I don't have any errors here about the deployment 182 07:43.920 --> 07:46.080 of that HA proxy failing. 183 07:46.080 --> 07:48.440 And earlier we had one of those errors. 184 07:48.440 --> 07:50.400 So it looks like now we are now proceeding 185 07:50.400 --> 07:52.960 with the automation and the deployment, 186 07:52.960 --> 07:55.440 at least past the point of successfully deploying 187 07:55.440 --> 07:57.720 the HA proxy VM. 188 07:57.720 --> 07:58.840 And if we take a look at the networks 189 07:58.840 --> 08:01.160 that that HA proxy VM is connected to, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 189 07:58.840 --> 08:01.160 that that HA proxy VM is connected to, 190 08:01.160 --> 08:06.160 it is connected to 10, 11, 11, 10, 12, 12, and 10, 13, 13, 191 08:06.160 --> 08:09.160 all the dot five on each of those subnets. 192 08:09.160 --> 08:13.240 And great news, the NSX Automation Wizard is continuing on. 193 08:13.240 --> 08:16.040 So once again, we'll come back here in 30 to 40 minutes 194 08:16.040 --> 08:17.800 and verify where it's currently at. 195 08:17.800 --> 08:19.640 So I'll see you in the next video.