In this video, I'd love to do two things.
Number one, I'd like to do a quick review of the concept of an NSX Federation.
Now, we covered the basics of it in a previous skill.
So if you haven't checked out that one yet, I would encourage you to see that
skill first.
And then after we do a quick review of NSX Federation, I'd like to put a game
plan together
for implementing stretched gateways and also stretched segments that go across
multiple sites.
And as a quick review of an NSX Federation, we are going to use a global
manager, like this one right here,
and in a production environment, we'd have a cluster of global managers for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and in a production environment, we'd have a cluster of global managers for
fault tolerance.
And then that global manager would manage our local managers at site one and
site two.
And one of the major benefits of using a global manager is that as we tunnel
traffic back and forth
between the edges at these sites, where they're going to be using the remote
tunnel endpoints,
when doing so, the edges can actually fragment the traffic.
And as a result, we don't need a larger than normal MTU because we can do the
fragmentation.
And we don't have to have less than or equal to 10 milliseconds of latency WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we don't have to have less than or equal to 10 milliseconds of latency
between the global manager
and the edges because the local edges are managed by their local managers.
So the play-by-play is the global manager interacts with the local managers and
the local managers
interact with their specific edges.
And once again, because we're not directly dealing from the global manager down
to the edges at site one
or with the edges at site two, we don't have to have that extremely low latency
.
So for our game plan, as we take this existing infrastructure that we set up in
our previous skill
regarding NSX federations, for our game plan, let's do the following. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
regarding NSX federations, for our game plan, let's do the following.
The first thing we get to do is we're going to do some cleanup of some of the
existing gateways
and segments that are in our current topology.
So that won't take too long to do.
And also it'll give us the opportunity to walk through how to do that from the
global manager.
So you and I, we can go ahead and sit here at the global manager and do all the
configurations
and access the local managers via the global manager.
And for our second step, let's create some new external segments, some VLAN
back segments
for connectivity to the external networks at both site one and site two. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So for site one, we're going to go ahead and create an external VLAN back
segment to support VLAN 23.
And for the VLAN back segment to the external network over at site two, it's
going to be using VLAN 24.
So I'll make a little note there in our game plan.
And then with those two external segments in place, we'll then go ahead and
create a stretched tier zero gateway.
That can be available to both site one and site two.
And as part of that configuration, we'll configure interfaces that connect to
the external networks.
And in doing so for this tier zero gateway right here at site one, we'll have WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And in doing so for this tier zero gateway right here at site one, we'll have
two edge interfaces
provided by edge one and edge two.
And let's use this naming convention right here.
So S one means site one, E one means edge one, V 23 represents VLAN 23.
And 61 is going to help remind me what I want to use as the last octet for the
IP address
on that 23.1.2 network.
And very similar treatment over here at site two, which also has two edge nodes
.
So it's site two for edge one and edge two, both will be on VLAN 24.
And I'll use the IP addresses dot 61 and dot 62. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So this logical shared tier zero gateway is going to have four interfaces to
over here at site one
and two over here at site two.
Now, in addition to having interfaces on this tier zero gateway, we'd also want
to make sure that we have the routing in place.
So as part of our game plan, we could configure border gateway protocol between
the tier zero gateway
and the external networks off of VLAN 23 and 24 respectively.
Or we could just create a default route here for the tier zero for the benefit
of site one WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and a default route for the tier zero gateway at site two.
So the cool thing is that even though we have this shared T zero stretched
gateway,
we can specify exactly which interfaces and which routing and so forth we want
to use at each site.
And if we ever want to have these VMs VM blue and VM green here at these two
sites,
if we want them to be able to go to the internet, we also need to make sure
that we set up network address translation
here at the T zero gateway at site one and also that at the tier zero gateway
at site two.
So let's also set up network address translation specifically source that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's also set up network address translation specifically source that.
And the cool thing is about doing this with an NSX federation is I can walk you
through the step by step
for doing the interfaces and the routing and the net on a per site basis,
even though we're talking about the same logical gateway.
And then once we have that tier zero gateway set up, let's create a tier one
gateway.
That'd be this guy right here.
And we'll connect this tier one gateway to the tier zero gateway.
Another cool thing to notice that if we have a tier zero gateway that's
stretched across four or five sites,
we don't have to have the tier one gateway below that at all the same sites. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we don't have to have the tier one gateway below that at all the same sites.
So for example, if the tier zero is stretched across five sites, we get out of
tier one gateway at two of the sites,
so one way of thinking about that is if we have like five or six sites, there's
like one and two and three and four.
And I'll go ahead and put little blocks there to represent those sites.
We could create a tier zero that's available at all four sites and then we
could go ahead and we could narrow it down as we go.
So for example, maybe says our tier zero gateway and then for the tier one, for
example,
maybe we only want to at site one, two and three. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
maybe we only want to at site one, two and three.
So we make that available to one, two and three, but it's not available at site
four,
which reminds me of a common phrase my mom would use like many decades ago.
She'd say, Keith, take a jacket because you can always take it off, but you can
't put it on if you don't have it.
So if you have the T zero available everywhere, we can then pick and choose
where we're going to have the T ones.
We don't have to have the same T ones available at all those sites.
So for our lab environment here, I only have two sites and we're going to have
our T zero available at both sites WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and both of the tier one available at both sites as well.
And then after we have that tier one set up, we'll also go ahead and create our
segment.
So we'll create segment 10 there.
Now, one other element that we probably want also if we have clients that are
getting IP addresses dynamically
is we'd probably also want to enable DHCP services.
Now, as you already know from our previous skills, if we're enabling DHCP
services,
it's going to require the services of an edge node in the background to do that
.
And one of our caveat is that when we're using NSX federations and we have a
stretched gateway, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
one of the limitations is that with a stretched gateway, for example, this tier
one gateway that's available at multiple sites,
we don't have the option of using a gateway based DHCP server.
But what we can do for the segment is we can set up a DHCP relay.
So as part of our plan, I've got a little external DHCP server at 10.21.0.1,
which is on VLAN 21.
And to actually reach that server, we're also going to need to create another
external segment for VLAN 21
and then use that additional segment with one of our edge nodes for another WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and then use that additional segment with one of our edge nodes for another
interface on our tier zero gateways
so that we can actually reach that DHCP server. So we'll set that up as well
when we get to that point.
And then once it's all set up, we should be able to bring up the blue VM and
the green VM
and they should be able to ping each other. They should also go ahead and be
able to access the Internet
presuming that we've done all these steps correctly.
And as a public service announcement and also to keep it real, I just want to
remind you that we have covered
most of these concepts before regarding setting up the concept of a T zero WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
most of these concepts before regarding setting up the concept of a T zero
gateway and a T one gateway
and same DHCP services. So most of the work that we do here in configuring is
going to be very similar
as what we've done previously. But this time, we're going to be doing it from
the global manager.
And it'll be a great reinforcement of many of those concepts. And I do want to
point out that this should not be
your first introduction to the world of NSX and these components. It's going to
be more of a reinforcement at this point.
So if you need a deeper dive into setting up external segments or tier zero
gateways or tier one gateways
just on a local manager, please check out our other sets of videos and skills WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
just on a local manager, please check out our other sets of videos and skills
prior to this one as part of this course.
So with that in mind, our very next step in getting this game plan kicked off
is to do some cleanup of the existing topology,
which is what you and I get to do in the very next video. So I'll see you there
in just a moment.