So our next step is to go ahead and deploy the global manager and that's this
guy right here.
And we're going to use .12 as the IP address here on my management network for
this global manager.
Now the actual host resource that we deploy this on doesn't have to be one of
our ES6I hosts at
site one or site two. It just needs to be some compute resource, some ES6I host
that can support
that VM. And the initial process for deploying a global manager is exactly the
same as the initial
process for deploying the initial local manager here at site one or site two. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
process for deploying the initial local manager here at site one or site two.
And that's using the
deploy template option inside of the vSphere client. So I have downloaded to my
management
computer the OVF template for the unified NSX manager. And here the vSphere
client will simply
right click on our data center and say we want to deploy an OVF template. It's
going to ask me
for the files. We'll say local file. Click here to upload the files. I've
selected the NSX
unified appliance, same version that I used to deploy the local NSX manager at WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
unified appliance, same version that I used to deploy the local NSX manager at
site one and site
two originally. And so with that selected, we'll click on next. I'm going to
call the name of this
VM NSX dash global. I'll also specify that I want to keep it in a folder called
NSX VMs.
Click on next and also be selected ESXI host as a compute resource for this to
run on.
And let me go ahead and pick ESXIC. Click on next, then I'll click on next to
continue.
And then the size of our deployment, extra small, small, medium or large, I'll
go ahead and pick
medium. It's going to use this many CPUs and that much RAM. We'll click on next WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
medium. It's going to use this many CPUs and that much RAM. We'll click on next
. I'll specify the
data store I want to use and I'm going to choose in my lab thin provisioning
and then click on next.
For its management network, I'm going to specify a port group that goes up to
my management network
and that is this one right here. So we'll click on OK. We're going to be using
IPv4. So we'll leave
that alone. Click on next. And that wants us to fill in details for the
passwords that we want
to use, including for the grab a root user. If we scroll down for the admin, if
we scroll down for
the audit user and so forth. So I'll go ahead and supply all those passwords. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the audit user and so forth. So I'll go ahead and supply all those passwords.
So I've filled in
those passwords and confirmed those passwords. If we scroll down, I'll leave
the default user
names for admin and audit as they are. Then there are optional parameters. This
says for internal
use only, I'll leave those blank and these little red indicators here for my
local password manager.
They're not part of the native interface for NSX and we'll scroll down. I'll go
ahead and call this NSX
dash global. We'll scroll down and it's here under the role name where we're
going to specify the
role we want this NSX manager to have. So the default is NSX manager. That's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
role we want this NSX manager to have. So the default is NSX manager. That's
what I have at site
one and site two. And from the drop down, we would here select NSX global
manager, which is effectively
going to give it the ability to be the global manager and then start to manage
and work with
the local managers, including those at site one and site two. And then we'll
specify the
management network IPV forward rest. So I'll specify that. So on the management
network, I'm
going to use dot 12 based on our plan. In fact, let me just confirm that real
quick. So sure enough,
as a confirmation, we want to use dot 12 fantastic. And we're using a 24 bit WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
as a confirmation, we want to use dot 12 fantastic. And we're using a 24 bit
mask. So I'll put that
in and dot a decimal. And then the default gateway on that management network
is 192.168.1.1. And
I'm not using IPV six. So I'll leave that part blank. And as we continue to go
down, we'll tell
it what DNS server to use. And in my lab environment, I have this server that's
providing DNS services.
So I'll supply that as the DNS server that this global manager should use. And
then for the search
list, I'll put in O G I T dot lab, which is the domain that all my devices are
in, and we'll scroll
down. And then I'll specify the NTP server to use. And in my lab, I'm also WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
down. And then I'll specify the NTP server to use. And in my lab, I'm also
using 192.168.1.100.
So it's doubling up as my DNS server and also my time server. And I'll also
enable SSH and root
SSH logins to this new NSX manager. And then we'll scroll down and all the rest
here for internal
use. So I'll leave those blank. And then after a few more clicks on next and
finish, it would then
begin the deployment of this new NSX global manager on that ESX I host that we
specified
as part of the deployment of this OV F now I'm going to go ahead and click on
cancel right here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
cancel right here.
And the reason for that is because I already have that NSX manager running. And
that is right
here. So I open up a new browser tab going to the dot 12 address, and then we
'll log in. So then
the login will specify admin and then the password we configured as part of the
deployment of that
OV F and we'll click login. So here in the interface for this NSX global
manager, it looks very similar
to what we have in our local NSX managers. However, we click here on system and
then open up fabric
over on the left, it doesn't have all the options beneath here that a local NSX WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
over on the left, it doesn't have all the options beneath here that a local NSX
manager would
normally have. However, it is on the system overview section right here. It is
telling us that the
global manager is not available. Why is that? That's because we also need to
specify that this
NSX global manager is active. And if we go back to our game plan, that's what
we're going to do
right now is we're going to tell this global manager that we're now in the
interface of that
it is the active manager. It also is begging us right here the system overview
to do that. So if
we click here on location manager, or we could just click on system on the top
and then left, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and then left,
go to location manager, we're just going to click on this tile right here, make
active. And that
makes it the active manager. So I'm going to give this global manager the name
of NSX-global,
click on save. And in a few moments, this is now the active manager. It's also
encouraging us
for the benefit of fault tolerance to add an additional global manager as part
of this cluster.
In a production environment, that would be a great idea in my lab environment.
I'm going to use a
single NSX VM acting as the global manager. And this also confirms the address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
single NSX VM acting as the global manager. And this also confirms the address
that we're currently
using, which is .12 for this global manager. If you want to add some fault
tolerance there,
we go to global manager appliances. And very similar to the process of adding
additional NSX
managers to a local manager, if you want to add a second or third NSX appliance
here for fault
tolerance, we're also going to need to take the step of going into fabric and
specifying a compute
manager. And by specifying a compute manager effectively a vCenter is then
getting us the
opportunity to choose from the host that are being managed by that vCenter,
which ESXi host can be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
which ESXi host can be
the home for these additional NSX appliances. So for my lab environment, I'm
just going to use the
one single NSX manager right here at .12, which is acting as our NSX global
manager. So based in
our game plan, we have now deployed our global manager. We sit it as active,
and that leads us
to the next step is to onboard site one and site two, including importing the
configurations
from those local managers. So we'll continue our journey in the next video. I
'll see you there WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
'll see you there
in just a moment.