So based on our game plan,
we are going to create this logical router right there.
And there are some additional options when we set this up.
We could say, you know what? I want some fault tolerance
with active active or active standby,
which is gonna call upon and using a lot of the services
provided by the edge node.
So for this demonstration,
I'd like to focus on a simple distributed router only
without using any additional fault tolerant features.
And that way we're not getting the edges directly involved.
So what we'll end up is we'll have this logical router
and this logical router. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and this logical router.
This distributed router function will live on ESXi-A,
that host transport node.
It'll also live here.
And that's because both of these transport nodes
have VMs connected to the respective segments
involved with this default gateway.
I also took a moment
and I renamed these VMs as VM one, two, three and four.
So it's easier to call out exactly where they are.
So here's where they are
as far as which host they reside on.
And I've also color coded them
and put their IP dresses here
to represent which IP addresses they currently have. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to represent which IP addresses they currently have.
So for this logical distributed router,
we wanna use a dot one here on the 10 10 zero network
and a dot one here on the 10 20 zero network.
And that's what the clients will then use
as a default gateway
if they ever need to route traffic off their local subnet.
So the first thing we're gonna do
is create this logical layer three router,
also known and loved as a gateway in the world of NSX.
So let's go to the NSX manager
and let's create it right now.
So here on the NSX manager on the homepage, it's showing us
that we don't have any gateways configured whatsoever yet. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that we don't have any gateways configured whatsoever yet.
If we click on networking, it can also confirm that
by showing us right here that we don't have any tier zero
or tier one gateways.
And if we click on the network topology,
it's gonna show us the topology with the 10 segment
and the 20 segment
and with the VMs that are attached to each of those.
But again, there's no routing currently
between those segments.
So let's fix that
by setting up an east west routing function.
And that is a tier one gateway.
So we'll click here on tier one gateways,
we'll click on add, and then we'll give it a name.
Let's go ahead and call this Our Tier-1 GW dash A, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's go ahead and call this Our Tier-1 GW dash A,
and that way if we have another tier one router as well,
we can call it tier one gateway B, et cetera.
And then as far as the HA mode, this is where for the demo,
I'm gonna go ahead and just choose distributed only.
And then later on what we'll do is we'll integrate this
with a tier zero router
and we'll also integrate it with edge nodes
for the benefit of some high availability.
But for now, I just wanna create a simple distributed
logical router that can exist on ESXi-A
and ESXi-B as host transport nodes.
So here's the name of our tier one gateway. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here's the name of our tier one gateway.
I don't have any tier zero gateways to link it to yet.
We'll do that in another skill.
And so we've created it, we'll click on save.
And this situation right here reminds me
of when I first got into networking,
'cause I bought a modular router
and I failed to buy interfaces.
So what good is a router if it doesn't have any interfaces?
So if we go back to our network topology,
here's our little router right here.
As far as the service goes,
it has a built-in gateway firewall rule
that's permitting all traffic by default,
but it's not connected. So we need to connect this gateway WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
but it's not connected. So we need to connect this gateway
to our two network segments.
So to do that, instead of going to the router
and saying, hey, connect to segment 10
or connect to segment 20,
we actually do it from the actual segments.
So we'll go to the configuration for segment 10
and say, you know what, please associate yourself
with this gateway.
And we'll do the same thing for segment 20.
So over the left, we'll go over to segments.
So here, let's start with segment 10.
So we'll click on the three dots
and then from that menu, we'll click on edit.
And what we're gonna do is we're gonna somebody say,
dear Mr. Segment 10, we want you to be associated
with this gateway from the dropdown. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
with this gateway from the dropdown.
And that's it. Let's how you connect 'em.
And then as far as what IP address this gateway should use
as it connects to this segment, we put it in right here.
So over here under subnets,
we'll put in the IP address we wanna use,
which is 10.10.0.1 with a 24 bit mask.
So we'll put that in, and that will be the IP address
that this logical interface is gonna use on the gateway
as it connects to this segment right there.
And then we'll scroll down and click on save.
And then before we continue,
let's go ahead and take a look at our network topology.
So now we have our gateway that's connected WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So now we have our gateway that's connected
to the yellow segment.
It's IP address is 10 10 0 1 as shown right there.
And then on that segment, currently I have two VMs,
VM one and VM three.
So our next step is go to segment 20 to do the same thing.
Go to segment 20, say, Hey, segment 20, we want you
to be associated with this gateway.
And then at that moment we'll also specify the IP address
that we wanna use on this gateway
as it connects to that segment.
So on the left, we'll go back over to segments,
we'll click on the three dots next to segment 20
from the menu, we'll click on edit,
and then we'll specify WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and then we'll specify
that we want this segment also be connected to our gateway.
So we'll select it from the dropdown
and then we'll get the IP address we wanted to use,
which is 10.20.0.1
with a 24 bit mask based on our plan.
And then we'll scroll down and click on save.
And in the background,
I've already trained all of the clients
to use those respective IP dresses of 10 10 zero one
or 10 20 zero one based on the segment they're on
as their default gateway.
So before we go too much further,
let's just do a quick spot check on these four VMs
to make sure that they really do have these IP addresses
and also that they have the dot one WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and also that they have the dot one
on their respective subnets as their default gateway.
So here is VM one at 10.10.0 11.
There's its IP address and there's its default gateway.
That looks good. Let's take a peek at VM number two.
So here at VM number two, it should be at 10 20 zero dot 20,
and it is, it's default gateway is 10 20 zero one
and two more to go.
So here it is, VM three, which should be at 10.10.0.10,
which it is and there's its default gateway.
And let's also take a peek at VM four. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's also take a peek at VM four.
And here is VM four,
which is at 10.20.0.21,
and it has a default gateway of 10 20 zero dot one.
Alright, all that looks good.
And let's go back to VM one for a moment
and let's do some pings.
So let's do a ping over to 10.10.0.10.
And that works. And that's VM three that we just pinged.
It's also ping 10.20.0.20, and that's working.
And let's also do a ping of 10.20.0.21. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's also do a ping of 10.20.0.21.
And that works.
So we just verified full connectivity between these VMs
and what's really happening
is this logical distributed router that we just created
and then we assigned it
and connected it to the two segments.
That little logical router function
that exists here on ESXi-A.
It also exists here on ESXi-B
as a distributed router function.