So it has been, I don't know, 15, 20 minutes,
and it seems to be stuck right here waiting for certificates.
So it said it checked DRS, make sure it's fully automated,
and the HA was enabled on the cluster called HOSFRNAP,
then it deployed the load balancer VM,
and now it's waiting for certificates.
So I'm going to do a couple of things.
I'm going to click on back right here,
and then back again, and then back again,
and I just want to confirm all my settings here,
and then we'll take a look at the vSphere client as well.
So that hasn't changed, nor has that, nor has that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So that hasn't changed, nor has that, nor has that.
That all looks good, and click on next, and next,
and that looks good, click on next.
All right, so all this looks pretty good.
I'll click on done, and let me run the prechecks one more time.
So the prechecks all look good, so we'll click on next,
and then next, and sure enough,
it is still waiting right there.
So I'm going to go back to the vSphere client,
and let's check a couple things.
And let's go to the vCenter itself on top,
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
and let's go to monitor, and let's take a look at tasks.
What I'm looking for is anything that fails.
So right here, power on virtual machine, HAProxy.
No host is compatible with the virtual machine.
So it could never deploy that, and why is that?
So let's go take a look.
So let's go to the VM and templates view.
So there's our HAProxy right there.
I'm going to go ahead and right click,
and I'm going to delete that from disk, just to get rid of it.
And that was attempting to be deployed
in this cluster right here.
So if we go to that cluster, as part of the automation tasks,
it said it was confirming that on this cluster WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it said it was confirming that on this cluster
that we had DRS and HA enabled for that cluster.
So if I go to that cluster and go to configure,
so for DRS, it is enabled, and for availability,
it is also, so I did not enable HA on this cluster.
That was the automation that did it for us.
So it could be that it deployed the vSphere HA,
and then attempted to deploy the HAProxy
before the HA was completely activated and running. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
before the HA was completely activated and running.
So then we verified that the HA is turned on.
I'm also going to take a moment for this cluster
and go to updates and just validate
that all the hosts in this cluster are in compliance.
So we'll click here on check compliance.
And once we've confirmed that these three hosts
are compliant with the cluster,
meaning they also support HA,
let's go ahead and we'll go back to the automation wizard
and we'll try it again.
All right, so it's showing us that for this cluster,
all three hosts are compliant, fantastic.
So let's go back to the NSX manager
and let's go to the automation plugin once again. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and let's go to the automation plugin once again.
So back here, we'll click on back and back and back,
and I'm gonna go through all the steps again,
just to confirm my settings,
and then we'll try the deployment again.
So next, and that looks good for step two next,
and here's the HAProxy information, click next and next.
And there's our public registry that we're gonna be using
and click on next.
And here is our NAP instance that we're gonna be using,
and we'll click on done with configuration, run precheck,
and then we'll click here on rerun precheck,
just to validate that everything's in place, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
just to validate that everything's in place,
ready to go, that looks good,
and then we'll click on next.
And there's the permissions that are needed
between these sources and these destinations
with these services and our ports and protocols,
and we'll click on next.
So look at this, now it shows that the HAProxy certificate
is generated and that also implies
that it redeployed the HAProxy.
So let's go back to the vSphere client
and just verify that the HAProxy that we deleted
a few minutes ago, did it redeployed that.
So back here at the vSphere client,
let's go to the VM and templates view, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
let's go to the VM and templates view,
and let's go to the very top here and click on VMs,
and I do not see the HAProxy,
which means that it thinks it's deployed,
but it is not there because I deleted it.
So let's go back to the automation,
so it's currently in the process
of deploying the content library that's gonna be used
as part of the Kubernetes,
but what we really need to do is have it redeploy the HAProxy.
So to facilitate that, I'm gonna go ahead
and click on back and back and back, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and click on back and back and back,
and I'm gonna go ahead and change the instance name
so it can go ahead and redeploy the HAProxy.
So I'm gonna use the same data center,
same cluster, same data store, same storage policy,
next and next and next and next, and then for the NAP instance,
I'm gonna go ahead and delete this one and click on remove,
and then click on add.
For the instance, I'm gonna go ahead and put our N number two,
just to make it different from our first one.
Then our NSX manager is here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Then our NSX manager is here,
I'll put in the username and password for the NSX manager,
and then click on next,
and then we'll go ahead and use that NAP version, fantastic.
We use the evaluation form factor.
We won't reserve all the CPU and memory for all those nodes,
click on next, and then we'll put in the names
that resolve to 12, 12, 19 and 12, 12, 20, respectively.
So this first one is lab-service.ogat.lab
that resolves to that IP address,
and then this DNS name resolves to that IP address.
We verified that earlier, so we'll click on add, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We verified that earlier, so we'll click on add,
and then we'll click on done,
and then we'll rerun the pre-check by clicking on rerun pre-check,
and that is completed, that's great,
and then we'll click on next, and then next.
And it looks like at this point, it's still not going back
to redeploy the HA proxy VM.
So I am going to do one additional thing,
and that is this.
Let's go back to the beginning.
So I'm gonna go ahead and cancel,
and I'm gonna go to settings, and I say reset,
to reset everything, and then we can start from scratch, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to reset everything, and then we can start from scratch,
including using a new instance,
and for this time, I'm gonna go ahead and use instance three.
So once again here at the plugin for NAP automation,
we'll go ahead and we will run the wizard again.
So start.
So then we'll put the details in again.
Now also, probably in a production environment,
what we'd wanna do is allow or wait
for the previous deployment to completely fail and stop.
And then make sure we have a nice fresh start.
So here, I'm gonna click on next,
and it appears that it still remembers everything
from what we did earlier.
So I'm gonna click on next a few more times. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I'm gonna click on next a few more times.
Let's go ahead and just confirm all those details,
and then let me go ahead and make yet another instance here,
and then we go ahead and delete the existing one.
That's NAP two, we'll click on remove and add.
We'll call this one NAP three,
we'll put in a NSX manager information, click on next,
select the form factor of evaluation
with no reservations for a CPU memory, next.
And then again, the names that resulted that 19 and 20.
And then click on add.
And then click on done, it's running the pre-checks,
click on next, and we'll click on next. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
click on next, and we'll click on next.
And then we'll click right here on deploy slash update,
and that looks a lot better.
So it's gonna start the process over,
including deploying the HA proxy.
So in the documentation for the NAP automation,
it mentions that you may have to go back and forth
a couple of times inside these wizards
as part of the automation to make sure everything works.
So at this point, just like we did previously,
we'll let this go ahead and run for anywhere between 30
and 45 minutes until it gets stuck at one of the points, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and 45 minutes until it gets stuck at one of the points,
at which point we'll troubleshoot or until it completes.
But now that we already have DRS and HA already enabled
on the cluster, as it deploys this HA VM on that cluster
that requires DRS and HA, hopefully that'll complete
successfully.
In fact, before we leave this video,
let's just verify real quick that that HA VM
is currently deployed as it just as it did
and make sure that it is running.
So to do that, let's hop over to the vSphere client.
So here at the vSphere client, there it is right there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here at the vSphere client, there it is right there.
There's the HA proxy and it is running,
which is fantastic news.
And if we go to recent tasks and we look at all recent tasks
and bring that up a little bit,
I don't have any errors here about the deployment
of that HA proxy failing.
And earlier we had one of those errors.
So it looks like now we are now proceeding
with the automation and the deployment,
at least past the point of successfully deploying
the HA proxy VM.
And if we take a look at the networks
that that HA proxy VM is connected to, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that that HA proxy VM is connected to,
it is connected to 10, 11, 11, 10, 12, 12, and 10, 13, 13,
all the dot five on each of those subnets.
And great news, the NSX Automation Wizard is continuing on.
So once again, we'll come back here in 30 to 40 minutes
and verify where it's currently at.
So I'll see you in the next video.