So at this part of our journey, we're going to go and create the tier one
stretch gateway
and make it available to both site one and site two.
We'll link it to the tier zero gateway.
We'll also tell the tier one gateway that we wanted to share any of its
directly connected
networks like the segment 10 that we'll be adding to make sure we share that up
to the
tier zero as well.
And then we'll create segment 10 and associate it with the tier one gateway.
And we'll use the IP dressing space of 10, 10, 0, 0.
And we'll give the tier one gateway the address of dot one on that segment.
So once again, we'll head up to the global manager. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So once again, we'll head up to the global manager.
We'll let our tier one gateway and connect the segment to it.
So back at the global manager, verifying we're on the right device, we are
fantastic.
And with the networking tab selected on the left hand side, we'll go down to
tier one
gateways.
So currently we have no tier one gateways anywhere.
So we'll click on add tier one gateway.
Let's call the stretched tier one and we'll use active standby.
And then we'll associate this tier one gateway with our tier zero right above
it, which is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the tier zero we created earlier.
So we'll associate it there.
And then I'm also going to set this up to be preemptive like I did on the tier
zero.
And then we scroll down.
It's already presuming that because site one and site two are already
associated with
and able to use the tier zero gateway, this tier one gateway that we just
connected that
tier zero gateway, it also assumes we want to available at both sites.
But we could click on a little trash can here and remove it from one or both
sites.
We don't have to have this new T one gateway available at both sites. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We don't have to have this new T one gateway available at both sites.
So because we do want it, we'll leave that in place.
Now we also get to choose who gets to be the primary and who gets to be the
secondary site
one or site two.
So to make this consistent with the actual T zero, let me go ahead and set the
site one
as the primary and set site two as the secondary.
And then if you have multiple edge cluster nodes, you can select the one you
want to use.
So at each site, I only have one edge cluster.
So I'll choose that edge cluster for site two and I'll use the respective edge
cluster
at site one and it'll automatically allocate the edges for that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
at site one and it'll automatically allocate the edges for that.
So if you want to specify specific edge nodes within a cluster to go ahead and
use, you
can go ahead and specify it.
So I'm going to say go ahead and auto allocate the edges and then also under
route advertisement
right here, which simply says, please Mr tier one gateway, please advertise up
to your
tier zero, any directly connected segments that may come along.
So when we start adding segments like the 10 10 network and the 10 20 network,
that
routing information can be advertised up to the tier zero gateway, which is a
good idea. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
good idea.
So we'll go ahead and set that as well.
And let's click on save.
So let's click on yes to continue editing and we could further set up the D HCP
.
However, there's a few additional steps that we need for the D HCP services
with D H P
relay, including sitting up an additional external interface up at the tier
zero.
So we'll do that in a separate step.
So let me just check our work real quick.
So we got site one site to site one primary site to secondary that all looks
good.
So we'll go ahead and click on close there.
And just for a moment, I'm going to go back up to the tier zero gateways and
just to confirm WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
just to confirm
to see which of our two sites is going to be the primary.
So I'll click on edit and scroll down.
And so for the tier zero gateway as well site one is primary and site two is
secondary.
So I'll go ahead and close that.
And our last piece here was to go ahead and create a segment.
So we'll click on segments again here at the NSX global manager and we'll click
on add
segment.
Let's go ahead and call this stretched sag 10 and we'll go ahead and connect
this to
our tier one gateway right there from the drop down.
And then we'll give the logical interface address for the segment of 10 dot 10 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then we'll give the logical interface address for the segment of 10 dot 10
dot zero
dot one with a 24 bit mask and for our two sites, it took the overlay transport
zone that
was identified as the default transport zone and this new segment, which is
connected to
the tier one gateway, which is being used by both sites.
This new segment is going to be associated with those respective transport
zones.
So we'll scroll down and that looks good.
So we'll click on save and then click on no.
So now if we were to pop over to the local manager at site one or site two, we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So now if we were to pop over to the local manager at site one or site two, we
can get
a nice beautiful picture of the topologies.
Let's jump over to site two.
So from global manager, we use the drop down to site two.
Let's go to the networking tab here at the local manager at site two and click
on network
topology.
So from site two's perspective, here is the topology.
We have our two external interfaces 24, one, two, sixty one and sixty two.
We have our stretch tier zero gateway.
If we scroll down, then we have our tier one gateway and that's connected to
this segment
right here, 10, 10, zero.
Now before we start attaching clients here at site one or site two to this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now before we start attaching clients here at site one or site two to this
stretch segment
10, I also want to set up DHCP services.
So join me in the next video as we implement DHCP services in our NSX
federation.