So now that we have our global manager, let's do the next logical step and that
is to add our
sites that this global manager can work with. So we'll add site one and site
two and we'll be
leveraging the virtual IP address associated with the management cluster at
each of those sites,
including at site one, the dot 10 address and at site two over here, the dot 14
address.
So back at the NSX global manager and we can confirm that by clicking on the
system tab up on top
and then with system overview selected. And this confirms for us that we are at
the global manager
also, if we went to networking before we onboard any of our sites by clicking WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
also, if we went to networking before we onboard any of our sites by clicking
here the networking tab
you'll notice that we have no tier zero gateways, no tier one gateways, no
segments,
absolutely nothing because we haven't onboarded or created any of those yet.
However, that's
about to change as we onboard and then import the configurations from site one
and site two.
So to onboard the sites, we're going to go to the system tab here on the global
manager and with
system selected on the left, we're going to go under configuration and click on
location manager WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
location manager
right there. And then here the main pane, we have our NSX global and if he's
scroll down,
we have the option to add a new location. So we click right here on add on-prem
location,
we can get the ball rolling and let's start with site one. So we'll click here
on add on-prem
location and let's go ahead and call this site one for a friendly name. And
then I have set up
in DNS, I've got a fully qualified domain name that represents the virtual IP
address
at site one for that NSX management cluster. And let me just confirm that that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
at site one for that NSX management cluster. And let me just confirm that that
's in place.
So here is my Windows server that's acting as the DNS server. Let me make that
a little bit bigger.
And let me bring up the DNS manager and there it is. And here is the OGA T.Lab
domain. And sure enough
right there, I've got an NSX-1-VAP.OGAT.Lab at 192.168.1.10. And that is the
virtual IP address
that we set up the NSX management cluster at site one. So that's going to be
great. So we'll put in
that name that maps to that dot 10 address. And then I'll put in the username WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that name that maps to that dot 10 address. And then I'll put in the username
and password
required to log in to that NSX cluster. So I've supplied that username and that
password.
It's also requiring a space on this red asterisk to supply the shop 256th thumb
print for that NSX
cluster. It's going to help confirm that we're at the right device. So let's
make a road trip with
command line interface over to this cluster right here and just verify what
that fingerprint is.
So here at the CLI, I'm SSHing over to the NSX-1-VAP address. And we are logged WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here at the CLI, I'm SSHing over to the NSX-1-VAP address. And we are logged
in. And to get that
thumbprint value, we're going to type in get space certificate cluster space
and a question mark
and thumbprint and then press enter. And there is the thumbprint where you need
right there. So I'll
go ahead and copy that to my buffer and we'll just paste that in as part of the
onboarding
of site one with our global manager. So we minimize that. So another we've
taken that
thumbprint, let's go back to the global manager and continue the onboarding. So
here in the shop,
256th thumbprint section, we'll go ahead and right click and paste to paste WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
256th thumbprint section, we'll go ahead and right click and paste to paste
that in.
And before we can click on save and continue this, we're also required to go
ahead and check
version compatibility. So because I'm running the exact same version at the
global manager,
as I am at the local manager at site one, we shouldn't have a problem. So we'll
click right
here on check version compatibility, give that a minute to process and boom,
fantastic. So there
is the version and a little check says we are compatible. So let's go ahead and
click on save. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
click on save.
And that will take just a few moments to complete. So while that's finishing up
, let's go ahead and
also onboard site two at the virtual IP address of dot 14. I also have a DNS
name already set up
that maps to that dot 14 address as well. So back at the global manager, I have
a little message
saying, Hey, the default transport zone could not be found for the local
manager at site one.
That'll take a minute or two to actually complete. So while that's finishing,
let's scroll down
here. Again, we're at system location manager, and we're going to click on this
button one more WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
button one more
time to add on prem location to add our site to. So this will be site two. So
we'll put the name in
there. So I've got a DNS entry that maps to that dot 14 address. And the name
is NSX - 2 - VIP dot
OJT dot lab. I'll specify the credentials to log in. And then once again, we
need to grab the
shock to do six thumbprint. But this time from site to NSX management cluster.
So let's make a
road trip over there and get that thumbprint. So this is the command we used at
NSX manager one.
I'm going to go ahead and copy that, save myself a moment. And let's go over to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I'm going to go ahead and copy that, save myself a moment. And let's go over to
NSX manager two,
which is right there. Also, since I'm done with NSX manager one, I'll go ahead
and close that
window. And here is our login to NSX manager two. I'll right click and paste
that same command,
get certificate cluster thumbprint. And there is the thumbprint for our cluster
over at site two.
So I'll go ahead and copy that down to my buffer. We'll minimize that and
continue on with the
wizard here by pasting that in and then clicking here on check version WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
wizard here by pasting that in and then clicking here on check version
compatibility, which is
compatible, fantastic. And we'll click on save. And that is taking just a
moment to complete. So we'll
let that finish just to confirm that we've now added site one and site two. Now
, if we scroll down
here under locations under site two, it says, Hey, the default transport zone
is not found for site two.
But that same message for site one was up here just a few minutes ago. But now
it's saying, Hey,
we found objects and policies in this location. Do you want to import? So from
here, we could say
import or we could go to actions and then import to global manager. And we'll WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
import or we could go to actions and then import to global manager. And we'll
have a chance in just a
few minutes to do the same exact process here for site two. So if we check our
game plan, we have
now added site one and site two. And I get our next step is to import the
configurations from
each of those sites. So once again, we'll give them just a few moments to
settle. And in the next
video, we'll pick up where we left off. And we'll do the import for the
configurations from site one
and site two. So see you in the next video for exactly that.
[ Pause ]