So in the previous video,
we confirmed that those three distributed routers
exist on our transport nodes.
And now the challenge is that Tier Zero has
no idea from a routing perspective how to
reach the 10.10 network or the 10.20 network.
So to solve that, we're gonna train the tier one level
routers to advertise their directly connected networks.
So that's what we get to do right now.
So to train Gateway A and Gateway B to advertise
their directly connected networks,
so in Gateway A, it'd be the 10.10.0 address base.
And on gateway B, it'd be 10.20.0 address base. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And on gateway B, it'd be 10.20.0 address base.
To do that, we're gonna go to each of the tier one gateways
and tell them please advertise.
So with networking selected over on the left,
we'll click on our tier one gateways
and let's go ahead and begin with Gateway A.
So we expand that and we go down
here to route advertisement.
Currently we are not by default advertising
all connected segments, so we wanna do that.
So we'll click on the three dots, click on edit
and then here in the route advertisement section.
And we'll simply tell that we do wanna
advertise all connected segments.
We'll scroll down and click on save.
And then we'll close editing for that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then we'll close editing for that
first gateway, Gateway A, we'll collapse that.
And then we'll do the same thing for Gateway B,
we'll click on edit for Gateway B.
And then under route advertisement,
we'll tell it that we want to go ahead
and advertise all connected segments.
Scroll down a little further, click on save
and then click on close editing.
And now, if we go back to the routing table
for this logical Tier Zero Gateway, zero device,
what we should see is we should see routes
and information in the routing table on how to
reach the 10.10 network and also the 10.20 network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
reach the 10.10 network and also the 10.20 network.
And to verify that this Tier Zero Gateway now has
the routes to 10.10 and also to 10.20,
we could go to any one of our transport nodes,
the edge nodes or the host transport nodes,
all of them because they'll have a copy effectively of
that routing instance for Tier Zero Gateway.
Any one of them would be able
to show us that information.
So let's actually do a couple.
Let's go to ESXi-A as a transport node
and also edge One.
And we'll ask both of them to confirm
the routing table here on our Tier Zero Gateway. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the routing table here on our Tier Zero Gateway.
So at the top we've got the NSX CLI for edge one,
and I've just SSH here to ESXi-A.
So here in the window for E ESXi-A, let's go ahead
and type in NSX CLI and press enter.
That'll take us to the NSX CLI interface.
Fantastic.
And then from here the commands, even though we can
get the same information they're slightly different
on an edge node versus a host transport nodes.
So a couple of commands might be identical.
And then for example, going into VRFs on the edge
is slightly different.
So let me bring up the command window.
We'll click on view, command window.
And for the commands that are the same, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And for the commands that are the same,
we can just use the command window to send it
to both sessions at the same time.
Let's do a get gateways and press enter.
So on the edge VRF zero is the transport
network information as it works with
and interacts with the physical network
or the transport network.
And then the bottom three represent Gateway A,
Gateway B and our Tier Zero Gateway.
So we can confirm that as well.
So here we have the Gateway A matching up
with this one right here down on ESXi-A.
So the UUID is exactly the same
because it's the same distributed router.
And then we go to Gateway B WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then we go to Gateway B
and look at it here on edge one.
That's also right here on ESXi-A.
And then for the Tier Zero Gateway,
and here's that same UUID here on ESXi-A.
So here if we did a get gateway space
and we plugged in this UUID
or let's go ahead and do it for the Tier Zero Gateway.
So I'll go ahead and take that UUID and paste it in.
Then we did space and let's do forwarding and press enter.
So this has both the IPV four
and IPV six information.
Let me scroll down just a little bit in both windows. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let me scroll down just a little bit in both windows.
And here we have the routing table on both.
So here is the 10.10 network from the
perspective of edge one for that virtual router.
And here's the same route for that logical router.
Here on ESXi-A there's the route for the 10.20 network.
And that same route here again on
two different transport nodes,
on the top we have the edge.
And at the bottom we have the host transport node.
And then for these two subnets right here,
the /31s they also exist here,
shown here and here.
So up on edge one, we have a 32 bit route
for an actual interface IP address. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for an actual interface IP address.
That's a 32 bit route.
While at the same time for that 10.64.0 network,
we simply have the network route here on our transport node.
And instead of forwarding, we use the option
of interfaces and pressed enter.
It's now showing us the interfaces
associated with that gateway.
So we scroll up on each of them.
Even though the output is
formatted a little bit differently.
Here we have the UUID for each interface, which again,
is the same on both 'cause we're talking about
the same logical router interface.
And for the interface, it has this IP address
that's one of the interface addresses we're using WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that's one of the interface addresses we're using
on the uplink between Tier Zero and T one.
Here's the layer two address associated
with that IP address.
There's the VNI on both of them.
Also up here on the edge it's showing the name.
So the formatting and the output is slightly different,
but the information's the same.
So the LRP at the end here simply represents
logical router report in the name.
So this is the Gateway Zero interface that's connecting
based on the name down here to Gateway B.
And if we scroll down far enough, we should also have
an interface for the connection down to Gateway A,
which we do right here.
So here is the UUID.
This is from the perspective of edge one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
This is from the perspective of edge one.
And if we find that same interface down here
on the transport node, here it is right here,
same exact UUID, same exact VNI number as shown on both.
Same exact layer three and layer two
information shown on both.
And one of the differences as far as commands go
is that if we do a get gateways and press enter here,
the edge is gonna have its own VRF zero,
which is all that its own transport routes.
And the actual host transport nodes are not going to
include that in the output of get gateway.
So you might ask, well, how does the ESXi host WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So you might ask, well, how does the ESXi host
keep traffic with its own routes if the edge
is using VRF Zero, what does the host do?
And the answer to that is the host has its own default
routing set up based on the ESXi host we're sitting at.
So if we typed in exit here to exit out
of the NSX CLI for ESXi-A,
so here out of NSX CLI mode if we use the
traditional ESX CLI we use the command ESX CLI
network IP route IPV four list, that's a mouthful I know.
But that will show us the routing table on this ESXi host.
So here it's showing that with my VM kernel zero adapter, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here it's showing that with my VM kernel zero adapter,
I'm connected to the 192.168.1 network.
And that's for management of this ESXi host.
I'm also connected to the 10.4.0 network using the
VM kernel adapter of VM Gate One and that's for access
to an iSCSI data store on a iSCSI network.
Then I have a default route also associated
with VM kernel zero that's using a
default route next top of 192.168.1.1.