So now that we've deployed the automation VM right here at dot six on our
management network and because we told it to go ahead and put the plug in there
here as part of the NSX manager.
If everything went well we should have this new plug in now available and
usable right here from the NSX manager.
So there's a couple of options.
One is we could go ahead and use the automation wizard right here.
Once the plug in is installed with that VM running or we could log in directly
to this VM and run the automation from there.
Either way we can launch the automation for deploying the Kubernetes cluster WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Either way we can launch the automation for deploying the Kubernetes cluster
environment with Tanzu followed up by applying the NSX application platform as
well on top of the Kubernetes environment.
So also as part of the deployment that we just did in the previous video when I
was checking on the status about I don't know 30 minutes ago it had failed.
So what I did was simply run the deployment again to deploy that VM.
So the very first thing I like to verify is just to confirm that that VM was
correctly deployed that it finished and also that the plug in is right here.
Available on the NSX manager.
So let's do both right now. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's do both right now.
So here in the vSphere client looks like it's not quite done yet.
So we'll give that a moment to complete and just to confirm where that is we go
to the VM and templates view here.
Here's the nap automation VM right there in the folder called NSX VMs.
So I'll give that just another moment or two to complete its deployment.
Also prior to it being done over here at the NSX manager.
Notice here in the NSX manager on the system tab over on the left we don't yet
have the plug in for the NSX application platform automation. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
have the plug in for the NSX application platform automation.
And again once the automation VM is completely deployed and as that plug in
that plug in should show up right here.
So I'm going to give this a few more minutes to let it complete the deployment
of the automation VM.
All right.
So that deployment it says is done.
Let's go ahead and open a remote console and take a peek at what it shows on
the console for that VM.
So click here on launch remote console and here is the remote console.
So this is not quite ready.
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
So once it's fully ready it'll give us an indication right here on the screen
that the plug in has been deployed over at the NSX manager and that we're ready
to go.
And there we go.
It just refreshed and this looks great.
Let me make this a little bit bigger.
So here's showing us the IP address that's reachable at 10 11 11 6 and that the
NSX user interface plug in was successful.
And as a result we can either use the automation tool directly from the
automation VM or we can use the plug in over here at the NSX manager.
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
Additionally if we want to do it at the command line we have options for doing
it at the command line as well.
So to verify this let me first show you the actual interface here at 10 dot 11
dot 11 dot 6 from a browser.
So here's our connection over to 10 11 11 dot 6 and I'm going to go ahead and
say advanced and say go ahead and proceed anyway.
Even though we can't validate the certificate and here is the login for the NSX
application platform automation VM.
So if we log in here as admin and supply the password we set up and we click
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
login it then gives the opportunity to go ahead and start the NSX application
platform automation which effectively is running a wizard.
Now if we don't want to do it right here at the interface for the automation VM
itself because we opted to include the plug in at the NSX manager.
We could run the same exact automation wizard over at the NSX manager.
So here at the NSX manager with systems selected over here on the left I don't
see the plug in.
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
Let me go ahead and do an F5 on my Windows computer and refresh this screen.
Alright and that's a lot better.
So now it's showing us the plug in right here that was included as part of the
deployment and integration of the automation VM.
So if we click here on nap automation from the NSX manager this screen right
here looks very similar.
So it's the exact same wizard that we can now run here at the NSX manager or we
could launch it from the graphical user interface over at the automation VM
itself.
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
Also notice here for the nap automation before allows you to start this wizard.
It says please read this before you start.
So the start button is grayed out until you click on read this before you start
because there's a whole bunch of prerequisites that is there not met.
This deployment is going to fail.
So here in the prerequisites it says we need three routable networks,
management workload and front end.
We verified those previously in a previous skill.
We need to make sure we're permitting the appropriate ports and protocols
between those networks.
Also on the management network which in our case is the 10/11/11 network.
We need five consecutive available IP addresses. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We need five consecutive available IP addresses.
So we're going to start with .41 for those.
And on the workload network we're going to need to have 16 IP addresses that
can be used.
And so on the workload network which is VLAN 13 and our 10/13/13 subnet.
We're going to go ahead and also start with the IP address of .41 on that
network as well.
And then here it says we need to make sure that the NSX manager, the automation
appliance that's a .6 that we just deployed and vCenter all have IP
connectivity.
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
We also want to make sure that we have an NSX license as active and applied.
And the next DNS, NTB and DHCP servers make sure they're configured and make
sure you know what the IP addresses are involved with those.
So we've already deployed and verified those services as part of our
infrastructure network.
It's also saying we need to have a VM storage policy configured and mapped to
the data store that you'll be using for the NAP deployment.
Now that is something that I did not do.
So before we actually try to run the wizard, I'm going to click right here.
I am ready.
So before we actually run the wizard, I'm also going to go ahead and set up a
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
storage policy and associate it with the data store we're going to be using for
NAP.
And if we don't have a storage policy associated with that data store, it is
going to stop in its tracks.
So let's head back to the vSphere client here for a moment.
And let's go to our data stores and let's go down to iSCSI 2.
We're going to use iSCSI 2 as our data store.
I'm going to right click on it.
And then from the menu, we're going to click right here on tags and custom
attributes and let me assign a tag.
So I've got a tag I've already set up called OGA T dash tag.
I'm going to associate that with this data store.
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
So I'll click on assign and then we click on summary for that data store.
Here is our tag right there.
So previously, I'd use the hamburger menu here and went to policies and
profiles.
And I created a VM storage policy and it's right here called the KB storage
policy.
And as part of that policy, I'm looking for that specific tag.
So I've got a storage compatibility.
So again, it's important to have that done before we run the wizard because it
's going to ask us about which data store we want to use.
And if there's no storage policy associated with it, it's going to stop us
right there.
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
All right. So back to the NSX manager with system selected and on the left, the
plugin for NAP Automation selected.
Now we can go ahead and click on start to start the deployment wizard.
So we'll click on start and I'm going to go ahead on the left hand side and
collapse that for a little bit more room.
So the first question is which vCenter are we going to be using?
So I'm going to click right here on connect now.
I'm going to go ahead and put in the DNS name of our vCenter again.
That's just confirming as we go that our name resolution is working.
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
So I'm going to do an NS look up for 10 dot 11 dot 11 dot 11 dot 11, which is
the IP address of our vCenter.
And that way I can just highlight it right here, the DNS name press enter and
then go back to the wizard and right click and just paste it in.
Then I'll supply the login and the password to log in to that vCenter.
So there is the single sign on admin name for that vCenter and I've supplied
the password and we'll click on connect.
So now it's connected to this that vCenter and so I'm going to choose the data
center I want to use.
So I only have one.
That's the LV lab one and then the cluster I want to use, which is the host for
NAP cluster. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
NAP cluster.
And then the data store I want to use, which I want to use.
I SCSI dash two.
And then based on that, we should have as an option a storage policy and that's
the KB storage policy that I created and I'm going to use a storage policy.
And then I want to use a storage policy that I created and associated with that
data store.
And that's what I want to use.
So if you want to use the storage policy called VM encryption, you also need to
make sure you take a few steps at vCenter and set up TPM support.
However, that's just one more layer of things that can go wrong.
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
So I'm going to use my KB storage policy and in that policy, we're just doing
thin provisioning wherever possible.
So in this first section done, we'll click on next and continue on with the
wizard.
So it's asking us about the three networks that we're going to be using for the
deployment of our NAP and our Kubernetes.
So for the management network, we use the dropdown and we're going to select
the port group associated with VLAN 11, which is that one.
And then for the front end, we'll use our port group associated with VLAN 12,
which is that one.
And for the workload, we're going to go ahead and use the dropdown and select
this port group associated with VLAN 13. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
this port group associated with VLAN 13.
So that's an important reminder. We want to have all of those networks and port
groups set up and verified before we get to this point.
And then it's asking us about the default gateway for each of those networks.
So based on our topology for those three networks, the default gateway is at
dot one.
So this is not just carrying about the default gateway, but it also wants to
know the mask associated with each of those subnets.
So that's what we're going to supply next.
So for the management network, which is the 10 11 11 network, the default
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
gateway is 10 dot 11 dot 11 dot one, and then we'll put a slash 24.
And that's also supplying that information to the wizard regarding the length
of the networks.
So for the front end network, the default gateway is 10 dot 12 dot 12 dot one
with a 24 bit mask.
And then for the workload network, the default gateway is 10 dot 13 dot 13 dot
one with a 24 mask.
And then for NTP server, it's reachable at 10 dot 10 dot 100.
And the DNS server is the same IP address. So I'm going to go ahead and copy
paste that. And then the search domain is OG a T dot lab. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
paste that. And then the search domain is OG a T dot lab.
So with that supplied, we'll go ahead and click on next.
Now it's asking us about the details for the proxy. It's going to deploy.
So for that little VM, the proxy VM, we're going to use the IP address of dot
five on the management network and dot five on the front end network and dot
five on the workload network.
So we'll supply that information next. So on the management network, we'll go
ahead and use 10 dot 11 dot five.
And it already knows the mask associated with that network because we did that
in the previous step. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
in the previous step.
And for the front end, we want the proxy to use 10 dot 12 dot 12 dot five.
And for the workload network, we're going to use 10 dot 13 dot 13 dot five just
like that.
And then we'll supply a password over here for the proxy VM.
So I'll go ahead and supply that password right there.
So based on the network address space for using for the front end, it wants to
use this range of addresses for the virtual IP addresses for the load balancer
on that subnet.
So effectively, that's 10, 12, 12, 16 all the way through 31. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So effectively, that's 10, 12, 12, 16 all the way through 31.
That's the range covered by this address space with that slash 28.
And for a deeper dive into the world of IP addressing and subnetting, check out
our courses here at CV tonight.
It's either the network plus course that's going to have a lot of great details
there as well as the Cisco CCNA course where here at CVT.
That gets for more details on subnetting.
So that was automatically recommended based on the IP addressing space we're
using on the front end.
So I'm going to go ahead and take that recommendation and use it.
So then we'll click on next and that takes us to the next step, which is to
configure the management and workload IPs. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
configure the management and workload IPs.
And so here's where we wanted to use dot 41 as the starting range for those
addresses on the 10 11 11 network and also on the 10 13 13 network.
So for the 10 11 11 management network, we'll put in 10 dot 11 dot 11 dot 41
and it'll automatically calculate the next four consecutive IPs.
So it'll be 41 all the way through 45.
And then on the workload network, let's also use the dot 41 for the beginning
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
of that range, so we'll type in 10 dot 13 dot 13 dot 41.
And once again, it automatically calculates 41 with 16 IP addresses through the
ending range of dot 56.
So if that's what we want to use, we'll put those in and click on next.
And now it's asking us for the repository type.
Do you want to use VMware's public VMware hosted repository or do you already
have a repository for the helm and the Docker set up locally.
Now, I'm going to use the public repository. So I'm going to choose public and
use the defaults here and then we'll scroll down and click on next.
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
And now it's step six with the automation. It's asking us about details for the
nap instance.
So I'm going to go ahead where it says default. I'm going to click on the three
dots and say delete and remove that.
And I'm going to go ahead and put in a custom instance that we can easily
recognize.
So I'll click here and add nap instance. And I'm going to call this our nap
instance one.
And this has to be lowercase. And the reason I'm going to call it our nap
instance one is that if we have to troubleshoot and do it again, we can go
ahead and use nap instance two or three.
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
And now it's asking us about the IP address or fully qualified domain name for
the NSX manager. So just to verify that, let's go ahead and do a look up.
I'll do a reverse look up for 121, which is the IP address for using for NSX
manager. And there is its domain name right there.
So I'm going to copy that and paste it in. So there's the NSX manager fully
qualified domain name right there.
And then I'll specify the username and password required to log in to that NSX
manager. And then with that supplied, we'll click on next.
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
So now it's asking us about the version and the form factor. And so from the
drop down here, it's only going to give you the options that are compatible
with the version of NSX that we're currently using.
And that's going to be helpful in not choosing an older version of the nap that
may not be compatible with the flavor or the version of NSX that we're running.
So it's already chosen for me this four dot one, one, which I'll go ahead and
select. And then for the form factor, I'm going to go ahead and choose
evaluation.
So if we choose evaluation, it's not going to require the quantity of workers
and control nodes as part of Kubernetes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and control nodes as part of Kubernetes.
That would be required if we're doing a production environment. So for a lab
environment, that's perfectly fine. Also for a lab environment, we don't have
to reserve all the CPU and memory for each of those.
So I'm going to go ahead for my lab and say, you know what, I'm not going to
reserve the memory and CPU for all the VMs that are deployed as part of the
supervisors and Kubernetes cluster.
So with that selected, we'll click on next. And now it's asking us to put in
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
two fully qualified domain names that map to these two IP addresses 10, 12, 19
and 10, 12, 12, 20, respectively.
Now we have our DNS server, which in my environment is running on Windows
Server. And that's the server over at 10 dot 10 dot 100.
So I've already set up IPV for a records in DNS regarding those two IP
addresses and to verify those. Once again, I'm going to go to a client and
verify it right here.
So the first one I want to verify is the 10, 12, 12, 19, so we'll do an NS
lookup or 10 dot 12 dot 19. And because I created pointer records for reverse
lookup, this is going to be very helpful right here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
lookup, this is going to be very helpful right here.
So there is the fully qualified domain name that maps to this IP address right
there. So I'm going to go ahead and copy that.
And for the service name, I'm going to go ahead and paste it in right there.
And then for the messaging name, I'm going to go ahead and hit the up arrow key
and let's do a reverse lookup for the name behind 10, 12, 12, 20, which I
created in my DNS.
And there is the name right there. So once again, I'm going to go ahead and
copy that and paste it right there. So I verified that these two names resolve
to those two IP addresses respectively. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to those two IP addresses respectively.
And then once that's done, we'll click on add. So those here that in step six,
it has our instance name right here. It has the NSX manager and the net version
and they form factor.
But as far as the control plane nodes and the worker nodes, those should show
one each. So I'm going to click right here on done with configuration run pre
check.
And that's going to do the pre checks, which all look good. Now the reason all
of this looks good is because we did the pre work earlier to make sure that our
network infrastructure, including DNS and everything else was correct. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
network infrastructure, including DNS and everything else was correct.
So also, I'm going to click on back here, just to verify our steps. So because
we just click on back, we just click on next confirm each of our steps.
And you may have to run through this wizard a couple of times, just to make
sure everything takes like if it stalls or stops, you may have to go ahead and
run it back.
So now it's showing control plane nodes is one worker nodes is one. We'll click
on done with configuration run pre checks.
And then this is the pre check information from before. And if we want to run
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
the pre checks again, which is not a bad idea, we'll simply click here on run
pre check.
And that's going to run the pre checks again. Now, if any of these fail or
stall or they don't work and you think they're correct, you can just click on
back, put in the details again.
Like right now, it is stalling here on the check supervisor cluster networking,
which it passed previously. So I'm going to go ahead and give it what it wants.
So I'm going to go ahead and click on back and simply confirm all these
settings by checking them, clicking a next and next and next and next, and then
clicking on done with configuration run pre checks. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
clicking on done with configuration run pre checks.
So here I'm going to go ahead and click on run pre check one more time. And I
want to make sure that everything passes. And that all looks good. So with all
the pre checks done, let's go ahead and click on next.
So what we're going to do here is super important to pay attention to this is
talking about the connectivity required between source and destination,
including what protocols and services are needed.
So we want to make sure that we're using any kind of distributed firewall or
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
filtering of any type. We want to make sure we're allowing from these sources
to these destinations, these protocols.
So we're going to go ahead and click on next and then now we're in the stage
right here for the deploying Tanzu Kubernetes grid, the TKGs.
And to kick this part off, we then go ahead down here on the bottom right and
click on deploy slash update. And that's going to go ahead and start the
process of making sure we have DRS and HA enabled on our cluster. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
process of making sure we have DRS and HA enabled on our cluster.
And that was deploying the H a proxy. And at any point of it stops or stalls,
we may need to go back and run the wizard again. And the cool news is it can
pick up where it left off. You don't have to do the whole thing from scratch.
So this process right here about, I don't know, an hour to complete because it
will take a little while for the deployment of all the components. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
will take a little while for the deployment of all the components.
So join me the next video as we pick up where this one left off, and we'll
either pick up where it completed successfully or we'll pick up where it ceases
to work, and we'll do the troubleshooting.
I'll see you in the next video for the next step.