So based on our game plan, our first step is to do the preparation on the local
NSX
managers at site one and site two to make sure that we have identified the
default
overlay transport zone we want to use.
We also want to make sure that we have a virtual IP address set for the NSX
management cluster.
So at site one, it's dot 10 and at site two, it's going to be dot 14 here, my
lab
environment.
So for the demonstrations for site one, I'm going to be using light mode.
And then for site two, I'll go ahead and use dark mode.
And that way, as I go back and forth between them, we can be very clear on
which site we're working on. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
which site we're working on.
So let's begin our work right here at site one.
And here we go.
So I'm currently logged on to the NSX manager at site one, just to confirm.
I'm going to click on system.
And then on the left, let's click on appliances and let me just confirm the IP
address here, which is dot 11.
And I only have a single NSX manager.
And currently there is no virtual address set.
So let's go ahead and take care of that right now.
And we want to use based on our plan here for site one.
We want to use dot 10 as the virtual IP address to represent this NSX manager WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We want to use dot 10 as the virtual IP address to represent this NSX manager
cluster here at site one, the local manager.
So let's click on set virtual IP.
And also just peak to confirm that we want to use dot 10 and we do.
So we'll put the IP address of 192.168.1.10 and click on safe.
And we'll give that a moment to process and it's doing a refresh of the screen.
And sure enough, now we have a virtual IP address of dot 10.
And it's assigned to the node at dot 11, which is my lab environment, my single
NSX manager as part of this cluster. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
NSX manager as part of this cluster.
So the next step in our prep is we want to make sure this is backed up.
So we'll go ahead and click right here and go to backup and restore, which if
we
click here on system and on the left hand side, go down under lifecycle
management to backup and restore, this is where we set up right here.
So I currently have my windows server and my lab environment set up as an open
SSH server.
So we can use that for the backup.
So here in the backup configuration for site one, we'll click on edit.
I'll put in the IP address of my management server at 192.168.1.100.
And we'll specify the path and I have a folder. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we'll specify the path and I have a folder.
In fact, let me just peek at the folder real quick to make sure it's there.
So here on my local Windows server, I've got a NSX underscore backup's folder.
All set up.
Currently it is empty.
So we'll go back to the site one backup configuration for our cluster and
we'll put in that path, which is slash NSX underscore backups.
Just like that.
And then I'll specify the username and password that has permissions to go
ahead and use that folder for the backups.
And although administrator in a production environment, maybe excessive
rights in my lab environment, it'll work just fine. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
rights in my lab environment, it'll work just fine.
And then down here, what's also required is a passphrase that's going to be
needed
if we ever want to go ahead and restore from that backup.
So I'll supply that passphrase, confirm that passphrase and everything looks
good
here.
We'll click on save and we'll know in just a moment whether or not everything's
good.
So the fingerprint is missing.
We'll say add and continue and that looks good.
So let's go ahead and just kick off one backup.
So we'll click right here on start backup and let me re-back in the window
server.
So a moment ago, when we looked at this, there was nothing in this NSX backups WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So a moment ago, when we looked at this, there was nothing in this NSX backups
folder.
And now there is.
And then if we open that up below that, it has more details and there's the
backups
that are currently being made, including a timestamp.
Fantastic.
So that is working.
So I'll move that out of the way.
It also indicates here that the backup is currently running.
Fantastic.
If we scroll down, if we had backups, they would show up right here in the
backup
history.
All right.
So that backup is underway.
Let's take a look at our checklist.
So we said the virtual IP address for the site one.
We did the backup for site one and we also need to make sure that we have an
overlay
transport zone specified as our default overlay transport zone. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
transport zone specified as our default overlay transport zone.
So let's do that next.
So back here at our site one manager with system tabs selected, we'll go on the
left
and open up fabric and then in the fabric, we'll go down to transport zones.
And currently it has the two default transport zones from VMware that are
specified as the default and we want to make sure that our lab overlay
transport
zone is set as the default.
So I'll click on the three dots next to the lab overlay transport zone.
And then from the menu that comes up, click on set as default transport zone.
And then we'll confirm that with an okay. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then we'll confirm that with an okay.
And we don't really need to worry about the default VLAN back transport zone,
although I'm also going to set that as well to the one that we created for a
lab.
Slowly is the same process and set the VLAN back transport zone as the default.
So when the global manager is going to be talking to this local manager, the
global
manager is going to be retrieving the information about what is the default
overlay
transport zone because that's the transport zone it's going to be using when we
create
a new stretch segment and it's going to be associated with that zone.
So now that set, let's go ahead and check our game plan. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So now that set, let's go ahead and check our game plan.
So we have the default overlay transport zone, the virtual IP address
configured
and the backup done.
Let's do the similar process over here at site two.
And again, in site two, I'll go ahead and use dark mode to represent that we're
at site two.
All right.
So here's the vSphere client for VCSA dash two.
And that is for site two.
And here's the NSX manager for site two.
So if we click on networking, for example, on tickle, look at what's currently
there
and go to network topology, I've got a tier zero gateway called lab two, tier WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and go to network topology, I've got a tier zero gateway called lab two, tier
zero gateway zero.
And if we scroll down, I've got a couple tier one gateways also here at lab two
.
So I just want to confirm that we're on the right NSX manager.
So let's go to backup settings or to manually go there, we could go to system
and then
left go to backup from restore and we'll pretty much replicate what we just did
over at site one.
We'll go to the backup configuration, click on edit, put in the details,
including the address
of the backup server and with that supplied, we'll put in the path.
I'm going to use the same server here in my lab.
So we're connected to the same server.
I'm going to split that same folder and I'm also going to split the same WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I'm going to split that same folder and I'm also going to split the same
username and password.
And then down below, I'm going to specify a passphrase.
And that way, if we ever need to restore from this backup, we can go ahead and
use
that passphrase to allow that to happen.
And then we'll click on safe.
We'll add the fingerprint and continue.
And that looks good.
Didn't throw an error.
So let's go ahead and click on start backup.
We'll click on that once also down here in the history is showing us the backup
from the
other NSX manager because it's in that same folder.
So from site one, its management address was 192. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So from site one, its management address was 192.
One state one dot 11.
The VIP over there was 10.
And when this new backup is done, we'll have one coming in from this NSX
manager cluster
here at site two, which is show up as coming from the appliance at dot 13.
And the VIP for this cluster is dot 14.
In fact, let's just verify that real quick as well by clicking on system on the
left.
We'll click on appliances and just confirm right here that our current
appliance is at
dot 13.
And this one does have a virtual IP address already assigned and it is dot 14. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And this one does have a virtual IP address already assigned and it is dot 14.
So this one already has a virtual IP address in place.
So at site two, we have the virtual IP address.
We just did the backup.
Let's also make sure that we have a default overlay transport zone specified
here in the
NSX local manager at site two.
So here at site two with the system tab selected on the left, we'll go down to
fabric
underneath fabric.
We'll go to transport zones and currently here at site two, I do have the
default set
to the transport zone I want to use.
So this is my lab two overlay transport zone that's specified here as the
default. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
default.
Again, to change that we could go ahead and go to a different transport zone.
For example, here, click on the three dots and simply say set as default
transport zone.
And that would take that responsibility away and put it on this one.
However, we want this one right here, the lab two overlay transport zone to be
the default.
And it already is.
And that would be based on previous configuration where I said it to be the
default.
So if we look at our checklist here for both sites, for both local managers, it
's like one in site two,
we have set the default overlay transport zone.
We made sure we have a virtual IP address for the NSX management clusters at WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We made sure we have a virtual IP address for the NSX management clusters at
both sites.
And we've also done the backups of both local managers.
So at that done, our next logical step then is to deploy this global manager
right here.
And that's exactly what you and I get to do in the next video.
So I'll see you there in just a moment.