So for our OSPF game plan, let's do the following.
So the first thing we had to do is let's go ahead and confirm existing routing.
Because by default, when we link a tier 1 to a tier 0 gateway,
we should have a default route going that way and the same here.
And also, I believe in the previous skill, we actually did a default route that
went this way on our tier 0 gateway.
So I'd like to confirm that existing routing first.
I'd also like to confirm from our tier 0 gateway that we can ping this IP
address right here on this external router,
and that's at 192.1 state 1.1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and that's at 192.1 state 1.1.
That just verifies that we have connectivity from the tier 0 gateway to that
external interface on our external router.
So I'll put here confirm T0 to gateway at .1.
And that should be leveraging the external segment we have to the 192 network.
So I'll make a little note there that that's the external segment that we
should be using.
And as part of that connectivity to that external network, we're using the
virtual IP address of .60.
And then on edge 1 and edge 2, which are providing that edge connectivity,
on edge 1, we're using .61. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
on edge 1, we're using .61.
And on edge 2, we're using .62.
So as a group, these guys are providing that external connectivity
from our logical tier 0 gateway to the external segment here.
So before we begin setting up routing, I just want to verify we have that basic
connectivity right there.
So for our OSPF area, let's use area 0.0.
So in an NSX environment, it's referred to as area 0.0.0.
It's 32 bits long.
So in some vendors, they'll let you just put a 0 there.
Other vendors may require all four zeros.
But the area number is a 32-bit address. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But the area number is a 32-bit address.
And so it kind of looks like it could be an IPv4 address,
but it's really just four octets separated by three periods.
Unless your vendor allows you to put a 0 right there, which represents area 0
as well.
So to do one area, it'll be our backbone area.
And then once we establish that neighborhood between our tier 0 gateway,
which in the background would be using our edge nodes and the services router
function for that.
Once we verify that we have the neighborhood, the next step I'd like to take is
to advertise routes.
So in the tier 0 gateway, I'd like to advertise, I'll call our code these. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So in the tier 0 gateway, I'd like to advertise, I'll call our code these.
I'd like to advertise the 10, that 10 network and also the 1020 network and
advertise them up to the peer.
So I'll put a little adv there for advertise.
And that way, this external router will know how to forward in the direction of
1010-0 or 1020-0
if it ever needs to forward a packet in that direction.
So if this VM right here did a ping to the IP address of 192.168.1.1,
if we wanted to get a reply, this router right here, we need to have routing
information
on how to forward it back in this direction.
Also as part of our game plan, although we did a static default route in our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Also as part of our game plan, although we did a static default route in our
previous skill
here on the tier 0 gateway, I'd like to go ahead and dynamically learn a
default route from the
external router. So for our game plan, let's go ahead and specify this part as
the T0 learning,
the default route for IPv4 from the external router.
So that would imply we're going to need to configure this device or some other
device that
we put up here on this common segment to dynamically advertise a default route
so that tier 0 can WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
so that tier 0 can
learn that via OSPF. And then once it's all in place, we'd also want to do a
quick verification
that it all works. So I'll put verify routing right here. Now as far as
verification, just the heads
up, we should not. If from this VM right here, we should not be able to access
the internet yet
because we are using private RFC 1918 addresses and we need to do network
address translation at some
point, hand tent on a services router here before that packet is sent out to
the internet. But for
my test, what we should be able to do is we should be able to ping from any of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
my test, what we should be able to do is we should be able to ping from any of
these VMs
once it's all set up, we should be able to ping this IP address. And if this
has the routes,
it should be able to respond back. Or if we create a loopback interface here on
this router,
then we could attempt to ping that loopback address from any of these VMs. And
if we have a
default route that's been learned here at our tier 0 gateway, it should be able
to forward. And as
a result, this single router right here should be able to respond back. So we
'll put that all
into the category of verifying routing and just knowing ahead of time that we
're not yet ready
to go out to the internet because we're going to need to implement NAT, which WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to go out to the internet because we're going to need to implement NAT, which
will be in a separate
skill. So with this game, plan in mind, I'll see you in the next video as we
start our first step and
this to confirm our existing routing. So I'll see you there in just a moment.