All right, so it's time to tackle step number one in our game plan.
And that's right.
Here's just to confirm our existing routing.
So here's what I would expect to see.
We should have default routes on our tier one gateways that they get
automatically by
being connected to tier zero.
Also previously, when we configured the tier one gateways, we specified to
include and
advertise their respective subnets.
So the 1010 network and the 1020 networks respectively should already be in the
routing
table on our tier zero gateway because the tier one gateways are advertising WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
table on our tier zero gateway because the tier one gateways are advertising
that information
up there.
So probably the easiest way of verifying all of our routing is to go to one of
our edge
nodes and we'll verify which one is the active edge node.
I believe it's edge one will confirm that.
And we can take a look at the routing table for tier zero at the edge, which
because of
the connectivity to the external network here is the edge transport nodes that
are providing
that functionality.
So there's a few different ways we could look at the routing table one is right
here
from the NSX manager, we could click on networking and with networking selected
, we could look
at our topology by clicking on the left here on network topology and then we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
at our topology by clicking on the left here on network topology and then we
could make
that a little bit bigger.
And then we wanted to we could go ahead and first of all, let's double click on
this
tier zero gateway zero just to verify who is supporting the services of that.
So here showing us that edge one is the active edge node and edge two is the
standby.
That's the two edge nodes that are providing the services for this tier zero
gateway.
And if we click again here on the gateway, it'll bring a panel over on the
right with
information about the tier zero gateway.
And from here, if we wanted to, we could go ahead and download the routing WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And from here, if we wanted to, we could go ahead and download the routing
table right
here.
So I'm going to go ahead and click on download routing table.
And that's going to download that to my downloads folder on my local management
computer.
And let's take a look at it together.
So I downloaded as a CSV file and then I happen to have Microsoft Excel on my
local management
computer.
So when I double clicked on it, it opened it with that by default.
So here's the route type.
So those we have T zero and T one.
We'll take a look at those here closer in a moment.
And then we also have the C versus an S regarding the type of route.
So let's go ahead and start with this IPV four route right here is the route WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's go ahead and start with this IPV four route right here is the route
for the 10 10
zero network.
There's the next top IP address.
It is a tier one connected route.
That's what the T one C is.
And then we have a similar route here for 10 20 zero network.
It's a T one connected route.
And that one's off of gateway B.
And there's the next top.
Then we have some directly connected networks.
These are the connections between gateway zero and gateway A and be
respectively.
So there's one of them.
There's the other one.
Then we have a route for the back plane.
So when the tier zero gateway is communicating internally between the DR and SR WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So when the tier zero gateway is communicating internally between the DR and SR
functions.
And in this context, that DR is the distributed router and the SR as a services
router.
It's going to use that subnet.
And then we also have a default route that we applied in an earlier skill.
And here is T zero S the S stands for a static route.
And that's the static route saying, hey, to get to anywhere that you don't have
a more
specific route for your next top is 192 168 1.1.
Now another way of seeing the routing table for our tier zero gateway is at the
command
line.
And that can be very useful as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that can be very useful as well.
So they minimize that.
So let's open up a command line interface on the management network and let's
connect
over to edge one with an SSH session.
So here we're connected to edge one.
And from here, if we do a get gateways, it'll give us a list of the gateways.
So as we discussed in a previous skill, the VRF zero that gateway is like the
transport
network routing table for the VM itself, in this case edge one.
And then for the services router, which is right here based on the label here,
services
router tier zero, an easy way of working with it and using commands just for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
router tier zero, an easy way of working with it and using commands just for
that one virtual
router is to go ahead and simply go into the VRF.
So currently this is VRF four.
So we type in VRF space for and press enter.
This is the prompt change to tell us that we're now in VRF number four here.
And now if we do a question mark, it'll show us the commands of can issues.
So we do a get space and then a question mark.
And let's go ahead and do a get route, see the IP routing table.
So we'll type get route press enter and the output here reflects what we also
saw in the
spreadsheet.
So here is our static default route with the next top of 192, once you see WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here is our static default route with the next top of 192, once you see
eight one
dot one.
And then we have two tier one connected routes that are connected to gateway
and be respectively.
And for this edge router to go ahead and reach those, there's the respective
next hops on
gateway and be.
And then we have the two networks associated with the router to router links
between tier
zero and gateway and gateway B.
And then we have a T zero directly connected network of 169 to 2,400, which is
showing
right here is the back plane connection.
So think of it like logically, if the DR function on the tier zero gateway WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So think of it like logically, if the DR function on the tier zero gateway
needed to communicate
with the SR function on the T zero gateway, it would do so on the back plane.
And then here we have our connection to the 192, 160 one network, which we have
connectivity
through courtesy of our edge nodes using dot 61 on edge one and dot 62 using
edge two.
And then we also have a virtual IP address of dot 60.
And then following that we have some IPV six routing information as well.
So since we're sitting right here also inside the VRF, let's also do a ping out
to 192.168.1.1.1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to 192.168.1.1.1.
And if that works, that would be great.
It does and that is our connectivity from our tier zero gateway to the physical
gateway
over a dot one.
And it's what it confirmed that we have that connectivity.
Also I would mind confirming just some basic connectivity with our VMs.
So let's go to our VM right here, which is VM one.
This is verified.
We can ping our other three VMs.
They'll confirm our East West traffic.
And let's also confirm that we can ping from VM one to the logical VIP address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's also confirm that we can ping from VM one to the logical VIP address
that we're
using up here on Gateway zero.
So we're going to avoid pinging the 192.168.1.1 because that router, that
device at this
moment has no idea about how to reach back or route back to the 10 10 or 10 20
network.
So let me bring a little remote console for this VM right here, VM one.
Let me also confirm it's IP address with an IF config.
And sure enough, it is 10 10 zero 10.
And let's also issue the command route just to confirm it has a default gateway
that points
to Gateway A's address of 10.10.0.1 as a default gateway. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to Gateway A's address of 10.10.0.1 as a default gateway.
So let's do a quick ping.
Let's do a ping over to VM three at 10.10.0.11.
That looks good.
We'll do a control C to break that.
Then we'll do a ping to 10.20.0.20 verify that works.
And then our last one is at 10.20.0.21.
So we'll go ahead and do that as well.
Just to verify we have East West connectivity.
And that looks good. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that looks good.
Let's also go ahead and do a ping to the virtual IP address up here at our tier
zero gateway.
We could also try a ping up to dot 61 and dot 62 because this gateway who owns
those
addresses knows how to route back to the 10 10 network.
So let's ping those IP addresses next once again from our VM number one.
So we'll bring back VM number one here and let's do a ping to 192.168.1.60.
Just a virtual address here on this gateway on the 192.168.1 segment.
Fantastic.
That works.
And let's also go ahead and do a ping of 61, which is the edge one interface WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's also go ahead and do a ping of 61, which is the edge one interface
address.
And we'll also go ahead and do it to dot 62, which is the IP address for edge
two.
And I just realized that we don't have active active setup.
We just have active standby.
So that ping to dot 62 is not working.
And here's why if we double click on the tier zero gateway, take a look at the
fabric.
Edge two is in standby.
So at the moment it's not being used.
It's very likely that's why it didn't respond to the ping when we tried to ping
dot 62.
Also while we're here in the NSX manager, let's go to the T zero gateway and I WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Also while we're here in the NSX manager, let's go to the T zero gateway and I
want to
just modify just a little bit.
It's default route.
So if we click on the three dots to edit our tier zero gateway and from the
menu, we
click on edit.
Then if he's scroll down a little bit down under routing, if we expand that
here, we
have one static route.
So there's a one there.
We'll go ahead and click on that.
So there's our static default route and I want to go ahead and edit that as
well.
And what I want to do is for the next hop, I want to leave it at 192.168.1.1,
but I want
to change the administrative distance.
So I'm going to change that to 150. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I'm going to change that to 150.
And let's talk about why I'm going to modify that.
Let's imagine that we have gateway zero and let's imagine we've trained gateway
zero about
how to reach the 10 dot 90 network.
So that's the networking question.
And this gateway, let's imagine it's learning it via a static route.
And let's also imagine it's learning it via OSPF.
Well if this gateway is being trained or learning about the same exact route,
the 10
90 zero network in this case, and it's learning it from two different sources,
which one should
it believe?
Which one should you use this one or this one?
And the answer as far as how is going to decide which one to use, which source WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And the answer as far as how is going to decide which one to use, which source
it's
going to use is based on the administrative distance, which is a lot like golf.
So if you think about golf, even if you're not a golf expert, which I am not, I
do know
that the person with the lowest score wins.
And so if we have a static route, for example, as we do right here with this
number, this
administrative distance of 150 and then OSPF as it's advertising that same
route into this
gateway, if it has an administrative distance is lower, like 110, that will WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
gateway, if it has an administrative distance is lower, like 110, that will
cause this gateway
to say, you know what, it's the same exact route.
I'm learning it from two different sources.
I'm going to go ahead and choose the one with the lowest administrative
distance.
And that's what this is right here.
So the reason I'm changing this is because in a little bit, as we start config
uring OSPF
and advertising a default route down to this gateway, I want to see this route,
which has
an administrative distance of 150, be replaced by the better and lower
administrative distance
being advertised by OSPF.
And that's why I want to go ahead and modify that right now. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that's why I want to go ahead and modify that right now.
So we'll go ahead and click on apply and save and then close and scroll down
and click
on close editing and then collapse that and I just want to confirm that it took
.
So one way of doing that is right here at the command line interface for edge
one and
I'm currently in the VRF4, which is effectively the services router for the
tier zero gateway.
And then I'm going to hit the upper okay a few times and we'll do that get
route one
more time.
So previously we had a static route.
So the S is right there and there is the default route and it had an AD of one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So the S is right there and there is the default route and it had an AD of one.
That's what this value is right here.
But now that we modified that AD to 150, so now if we scroll down, we still
have our static
route is still a static default route and now we have an AD of 150.
So if and when I might add, we advertise a default route from a physical route
running
OSPF with an AD by default of 110, we should automatically have this static
route replaced
in our routing table and instead have this default route learned via OSPF.
All right, so let's check our work so far. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
All right, so let's check our work so far.
So now that we have confirmed our existing routing in our infrastructure and we
've also
confirmed our connectivity up here to dot one from the VRF for our tier zero
gateway,
our next step is to go ahead and begin our configuration of OSPF right here on
this
tier zero gateway in preparation for sharing routing information back and forth
with this
external router.
So I look forward to seeing you in the next video as we take that next logical
step.
(clicking)