So now that we've verified
our infrastructure,
our next step is to deploy the first NSX manager,
which we're gonna do right here
with this name NSX-mgr-11.
And we'll have it use the IP address of .11.
So as a starting point for this, I downloaded the image,
the OVA image to my local management computer,
and I have a license that we're gonna use a little bit later
in the steps here that I got as part
of my VM mug Advantage membership.
So we're gonna take this VM template here that we got
as an OVA file and deploy it right here on ESXi-C. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
as an OVA file and deploy it right here on ESXi-C.
So back here in the vSphere Client,
we could either be here in the host and clusters view,
or the VM and templates view either way is great.
And I wanna put the new VM in the LV-DataCenter.
So I'll right click on that.
And from the dropdown, we'll choose this bad boy right here,
deploy OVF template.
And now it's asking us if we wanna reach out
over the network and grab this file.
Or do you have it locally?
So because I already downloaded the OVA CD on my local
file system, I'm gonna click right here, local file,
and then click right here, upload files to identify
where it is on my local file system. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
where it is on my local file system.
So here I have a couple of 'em, one is 4.1.0 is 4.1.1
that's the latest and greatest as of this recording.
So I'll grab this one right here.
There's the name of the actual file
and I'll click on next to continue.
So let's call this nsx-mgr-demo
for the demonstration for the install.
And the reason I'm doing it as the name demo
is because the actual deployment of this VM,
it takes like 30 to 40 minutes for the deployment.
And then once it's deployed after you power it on,
it takes another 20 or 30 minutes to fully initialize. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it takes another 20 or 30 minutes to fully initialize.
And so in the wings, I've got a VM all ready to go
and it's currently called nsx-mgr-11.
So I'm gonna walk through this as a demo
and then cut over to the one that's currently installed.
All right, so we'll call this one nsx-mgr-demo
and we'll click on next.
As far as the compute resource, where we want this to live,
this new VM to be placed,
we wanna be in the management cluster
and specifically on ESXi-C based on our plan.
And then we'll go ahead and select ESXi-C WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then we'll go ahead and select ESXi-C
as the compute resource and click on next.
So it's asking me to now verify the template details.
It has some certificates that I can't verify, that's okay.
I'll click on ignore all for those.
So the publisher is VMware.Inc.
The product is nsx-unified-appliance.
The version is 411.
The download size is about 14 gigs.
And then the size on the disc, once it's deployed,
it's either gonna be seven gig, which is what I'm gonna do
within provisioning or 300 gigs.
So in my lab environment, I'm gonna go ahead
and use a thin provisioned nsx manager appliance. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and use a thin provisioned nsx manager appliance.
And it's showing us all the details here in our advanced
configuration about what comes with this template,
including the fact that by default it's not allowing you
to take snapshots of the VM.
And that's a good thing because if you have two
or three in the cluster
and they're all synchronizing their database,
we don't wanna snapshot one
and restore it later, that's gonna cause a problem.
All right, so we'll click next to continue
and then we're gonna choose the size
of our deployment based on what we intend to do.
So in a lab environment,
if you don't have a lot of resources to play with, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
if you don't have a lot of resources to play with,
you can choose extra small,
which is gonna dedicate two virtual CPUs
and eight gigs of ram.
And then based on how we per the storage up to 300 gigabytes
of storage.
And even though it says it's only supportive
for the nsx-cloud-service-manager role,
it'll also work in a lab environment,
even if you just managing your own lab gear.
Then we have small, which is using more CPU
and more RAM medium, more CPU, more RAM,
and large more CPU and more RAM.
Now one of the considerations also is that when we deploy,
for example, a medium here, as we deploy the second WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for example, a medium here, as we deploy the second
and third NSX manager as part of the cluster,
we'd want to use the same sizing for those as well.
So I'm gonna go ahead and choose the default option here
of Medium, which is gonna allocate six virtual CPUs
and 24 gigs of RAM and click on Next.
Now it's asking me on that server
where I'm gonna be hosting this VM,
where do I wanna store the VMs files?
So I have a local data store on ESXi-C, I've also got one
that's network reachable for the demo here,
I'm just gonna use the ESXi-C data store.
And I'm also gonna say, please do thin provisioning WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And I'm also gonna say, please do thin provisioning
and not tie up 300 gigabytes of space,
but only tie up as much as you really need.
So having selected thin provisioning,
I'll click on next to continue.
Now it's asking us for the management interface,
the management network interface on this VM.
What port group do we wanna associate it with?
So currently, because we only have one port group available
called management, which we documented earlier,
leads to my management network,
this is the port group we're gonna choose and click on okay.
Then for the IP addressing, do we want IPv4,
IPv6, we're gonna choose IPv4 and click on next. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
IPv6, we're gonna choose IPv4 and click on next.
And then we're gonna put in passwords
for the GRUB Root User.
We're also gonna specify a timeout.
I'll put 10 seconds there.
That way if it's booting up,
I need to interrupt the boot menu, I can,
I'll get 10 seconds to do it.
And then I'm gonna supply a System Root User password
and an admin user password and an audit user password.
And I'll use the default CLI names of admin and audit.
So lemme go ahead and scroll back to the top
and put those details in.
All right, so the password for the GRUB Root User are in.
Also this little icon here is for my local password manager. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Also this little icon here is for my local password manager.
That's just part of my browser.
So I'll scroll down.
And for the system root user,
I'll put it in a password there as well
and confirm that password.
So if you ever need to do N-S-X-C-L-I commands
or NSX related commands, we'd wanna log in as admin
to do that and not as root.
So lemme go down and put in the passwords.
And now we have a password for the audit user.
So I'll supply that and confirm it as well.
I'll use the default names, I won't change those.
And then for optional parameters,
it says for internal use only.
So I'll leave those alone, then we'll scroll down WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I'll leave those alone, then we'll scroll down
and that wants a host name for this VM.
So I'll call this nsx-mgr-demo.
And then for the role, do we want it to be an NSX manager?
In our case, we do.
Or if we wanted to be a NSX Cloud Service Manager,
we could specify that.
Or if we're implementing NSX federations,
we would choose the NSX global manager role.
So in our case, we're gonna use NSX manager
and then we're gonna give the IP address
that we wanted to use.
And based on our plan, that IP address is 192.168.1.11.
So next we'd put in the mask. So that's a 24 bit mask. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So next we'd put in the mask. So that's a 24 bit mask.
And then the default gateway is 192.1 68.1.1.
And then if we're using IPv6
we'd put in the IPv6 address and the prefix length here
and the IPv6 default gateway.
But just be aware that if you're using IPv6
we'd also wanna have those quad A records
and the pointer records for reverse lookups also set in DNS.
So for our deployment, we're not gonna be using IPv6
we're just using IPv4.
So we'll continue to scroll down.
And now it's asking us for the DNS server information,
which is 192.168.1.100. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
which is 192.168.1.100.
And the domain search list is ogit.local.
So if the manager's trying to resolve a name
and it fails, it'll also tack on ogit.local
to the name to try to resolve it again that way.
Then we'll scroll down.
Here's our NTP setting.
So we will specify our same Windows server as an NTP server,
192.1.68.1.100.
And I'm also gonna enable SSH
and I'm also gonna enable Route SSH login as well,
even though in a production environment,
if you don't need it, don't enable it.
But in my lab environment, I'm gonna enable both.
And the rest of this says please do not set these WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And the rest of this says please do not set these
parameters internal properties.
So I won't, and I'll click on next to continue.
All right, so here we are at the step nine,
the ready to complete.
So if we confirm our settings here,
there's the management IP address we're gonna use.
There's the mask below it, the default gateway,
no IPv6 DNS server at 100 NTP server at 100,
enabling SSH.
And then if this is all correct, we'd click on finish
to deploy this to the ESXi-C host
that we specified should be the compute resource for this VM WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for this NSX manager.
Now, as I mentioned earlier, I already have deployed this
and the reason I did it earlier was
because this process here takes 30
to 45 minutes for the deployment.
And then once it's deployed, you then turn on that machine,
you power it up, and that takes another 30
or 40 minutes to fully initialize.
And that's why in the background,
I already have an nsx manager that I deployed earlier today
where I gave it plenty of time to fully deploy
and then I hit the power button powered on.
But I have not done anything else besides that.
So I'm gonna click on cancel here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I'm gonna click on cancel here.
Let's take a peek over here at NSX managers
and there is NSX manager right there.
And again, I've done nothing to this.
I haven't even logged on, I just deployed it
with the steps we just looked at.
I went to that VM and hit the power button to turn it on.
And that's all I did.