So in this video, I'm going to take just a moment and let's enable OSPF on this
external devices at .1 and also while we're at it, let me also enable OSPF on a
second device.
And that's going to be a multi-layer switch.
And it also happens to do the same top of rack switch, this providing the
transport network and the routing on the transport network between any of the
transport nodes, whether edge nodes or host transport nodes.
Anytime we're sending traffic back and forth over the Geneva tunnels, it's
actually being performed in the background by this multi-layer switch, but it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
actually being performed in the background by this multi-layer switch, but it
also has a connection to this 192.1 state 1 network.
It also supports OSPF.
So what we're going to do is we're going to configure this device and enable it
for OSPF and will enable this device for OSPF.
So this one, if we do it first should be the designated router.
This should become the backup designated router.
So the edge nodes should be forming full adjacencies to each of the DR
functions. So to the DR and BDR from edge 1 and from edge 2 to the DR and BDR.
And edge 1 is going to be using .61 and edge 2 is using .62. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And edge 1 is going to be using .61 and edge 2 is using .62.
Also for fun and because it's pretty quick to do, I'd like to also show you
walking through the configuration of the OSPF on this device and this device.
So behind the scenes, this device is really a 4 to 8 firewall and this device
over here is a multi-layer switch with a VLAN 1 interface with a VLAN 1
interface is logically connected right here.
So without further ado, let's take a look at these two devices and enable OSPF
on them respectively.
So this is the graphical user interface for the 4 to 8 firewall, which is
acting as our physical device at .1 on the 192.1 state 1 network and we are in WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
acting as our physical device at .1 on the 192.1 state 1 network and we are in
the OSPF configuration here.
And currently this firewall is not configured for OSPF. So let's go ahead and
let's set it up so for areas.
We'll click here on Create New and let's go ahead and use area 0, 0, 0, 0,
click on OK and boom.
Now it knows about area zero or will once we click here on apply and then for
including networks as part of OSPF, I'm going to click right here and create
new and I want to enable at least the network address space that's being used
by this firewall as it connects to the 192.1 state 1 network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
by this firewall as it connects to the 192.1 state 1 network.
So I'm going to go ahead and specify that for area zero. I want to go ahead and
include any interfaces on this gateway that begin with 192.168.1 anything and I
'll go and put a slash 24 there.
So effectively what that means to this device is that hey any interfaces that
begin with 192.1 state 1, go ahead and include them as part of OSPF.
So I'll click on OK and then I'll click on apply and let's go back to our
interface for the NSX manager. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
interface for the NSX manager.
So here at the NSX manager on the tier zero gateway previously when we looked
at the tier zero gateway and we looked at the details.
If we went down to the OSPF section and under OSPF neighbors and clicked on
view, we just saw the two edges, but check this out.
Now we see a couple more hearings. So this top one right here that I've
highlighted is edge one setting up a neighborhood and getting all dialed in
with the device at 192.168.1.1, which is my physical 48 firewall acting as a
physical layer three router.
And then I have edge two right here that is peering up with that same IP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then I have edge two right here that is peering up with that same IP
address, which once again is my physical layer three routing device. In my case
, it's the 48 firewall.
Now when I clicked on the original link here, it cut it in the state called X-D
ART.
So on the way to becoming fully adjacent neighbors, it's a lot like going
through school, hit to start with grade school and college, etc.
So with OSPF, we're going to go through states like the init state and the two
way state and the X-DART and X-Change until we finally get to the full state.
So when I clicked on the link to show the neighbors, at that point where we cut WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So when I clicked on the link to show the neighbors, at that point where we cut
it, it was edge one and edge two going through the various states and we cut it
at X-DART.
So if we clicked right here on the refresh icon, which I'll do right now, if
everything went well, our state should be full, which implies a fully adjacent
state.
So edge one has a fully adjacent neighborship with my physical router and so
does edge two.
Now let me leave this screen up as it is and let's also bring in one more OSPF
speaking device and that's going to be our multi layer switch. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
speaking device and that's going to be our multi layer switch.
So this is a Cisco catalyst multi layer switch. And so if we go into
configuration mode on this multi layer switch, if we want to start the routing
process for OSPF on this platform, the command is router space OSPF space, and
then we have to give it a process ID.
So I'll give it process ID one and for interface VLAN one, which is my logical
interface.
I'm using to connect to that 192.168.1 network. I'm going to simply say IP OSPF
space of question mark.
I'm going to specify the OSPF process ID of one that I just created a few
moments ago, then I'll specify that I want this interface to be in area zero. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
moments ago, then I'll specify that I want this interface to be in area zero.
And then if we do show IP OSPF neighbors and I type in summary and press enter,
it's going to show us our current status.
So at the time I issued the command, I already had these two that just popped
in these two full adjacencies.
And that's from edge one and edge two based on their IP addresses there.
And then I have a third one right here that was still forming.
And I see down here that it's completely formed. So now I should have three
full adjacencies.
So I've got a full adjacency with all three of them.
So with the physical device that's my 48 there at one dot one, it is a DR. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So with the physical device that's my 48 there at one dot one, it is a DR.
And then for my full adjacency, I have to 6162 those devices are DR others.
That's because they didn't want to do the DR or the BDR role.
And that's why they're showing as DR others.
And then we did a show IP OSPF interface brief here on this KELA switch.
It's also showing us that on this interface interface VLAN one that it on this
interface, which has the IP address ending in 136.
It is acting as a BDR on the segment.
So the physical 40 gate device is our DR. This multi layer switch is the BDR WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So the physical 40 gate device is our DR. This multi layer switch is the BDR
and the two edge nodes at dot 61 and 62 are acting as DR others.
So on this segment here 192.168.1.0. We've got our 40 gate at dot one. It's the
DR.
We have the multi layer switch. It's at dot 136. It's acting as the backup
designated router.
And then we have our two edge nodes, edge one and edge two and there at dot 61
and 62.
And collectively those two edge nodes are providing the functionality of our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And collectively those two edge nodes are providing the functionality of our
services router on gateway zero.
So if we went back to the GUI interface on the NSX manager and we said, hey,
please show us the OSPF adjacency is what we should see is we should see full
adjacency is here and here and here and here.
And then between edge one and edge two, as we said before, they should be in
the two way state.
So let's go verify that back in the NSX manager. So back in the NSX manager,
all I'm going to do right here is simply click on refresh and survey says there
we go.
So edge one has a full adjacency with 136, which is our multi layer switch and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So edge one has a full adjacency with 136, which is our multi layer switch and
so does edge two. So I'm going to close that.
Now, if we went back to our topology here for a moment and we took a close look
at the routing table here on our tier zero gateway, even though we have OSPF,
neighborships and adjacencies all set up, it doesn't mean that we're
advertising anything.
So if we're going to take a look at the tier zero gateway and its routing table
, it would pretty much be identical as to what it was before we enabled OSPF.
So now here in the VRA for a services router, if we didn't get route and press
enter, in those that we have the same routes that we had previously. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
enter, in those that we have the same routes that we had previously.
So our next logical step that is to go ahead and start training both our
gateway zero and also our external OSPF routers to start advertising the routes
that they want to advertise into OSPF.
And that gives us the benefit of learning routes via OSPF.
So we'll take that next logical step in the next video.
video.