All right, I'd like to share with you some logic and also
some shortcuts that can help us understand what
are the correct commands that will work with the show
commands to see the output that we need to see.
[MUSIC PLAYING]
So to do that, I'm going to use the lab experience that we
had in the previous video with the full adjacencies that
are in place between the adjacent routers
for both IPv4 and IPv6 using OSPF version 3.
Now, I'd like you to think of something that's going WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now, I'd like you to think of something that's going
to help with the show commands.
It's like, hey, the show command still works
and this show command doesn't work.
With OSPF version 3, previously when
we implemented it with the older commands,
it was still OSPF version 3.
So it's really like, the same commands
that used to work with IPv6--
most of those same show commands still work.
But what's different is most of the commands that
were specific to IPv4's flavor of OSPF
don't work as-is because we need to include the keyword OSPFv3 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
don't work as-is because we need to include the keyword OSPFv3
and then specify we want to look at the IPv4 related
within that.
So think of the IPv4 routing as kind of a guest inside of OSPF
version 3, and that's why its show commands need
little more help.
Also, something that can help as well,
is that in a previous command, if you ever
had the command of ipv6 space ospf,
if that was in the output of your show,
like show ipv6 ospf neighbor or show ipv6 ospf database,
instead of typing in ipv6 ospf, you can use the word ospfv3 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
instead of typing in ipv6 ospf, you can use the word ospfv3
and that will give you the resulting
output that this used to.
Although the older IPv6 commands, most of them
still work because we were running OSPF version 3.
We just weren't using address families.
So ospfv3 instead of ipv6 space ospf--
if you get in a clinch, that will also work.
All right, let me share with you several commands in the lab.
And the reason this is important is
because if you're in a site or work in a company,
even if you don't traditionally use address families for OSPF, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
even if you don't traditionally use address families for OSPF,
if the company has them implemented,
it's convenient to have a clue as far as how to do the show
commands you're used to with the OSPF version 3.
All right, let's take a look at R3 as our focal point
as we look at our show comments.
So here on R3, I'm just going to make sure I have routes.
Do show ip route--
that works-- and there's some OSPF learned routes,
so we'll do a show ipv6 route, and we
have some IPv6 learned routes.
That's great.
So let's start off with some basic show
commands that used to work that don't work anymore. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
commands that used to work that don't work anymore.
With a show ip ospf interface brief, press Enter.
And it's just saying you know what--
that would work if you're running the older OSPF
version 2 that was supporting IPv4,
but we're using OSPF version 3, which is also supporting
the address family of IPv4.
So alternatively, if we want to see that information
with a show ospfv3, then we'll do a question mark,
and then we'll specify this guy right here--
ipv4 because that's the related information we want to see--
ipv4 question mark and then we'll specify interface WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
ipv4 question mark and then we'll specify interface
and then if we want to do brief we'll type in brief,
press Enter and that will give us
the equivalent information as our older show ip ospf
interface brief.
And so that practice, just doing it a few times,
is going to help you if you're at a site or at a location
and they're running OSPF v3 so you can see the actual output.
And if we did the up arrow key and we did a show ospfv3 ipv6
interface brief, of course, that'll
work for IPv6 neighbors.
And if we did a show ipv6 ospf interface brief, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And if we did a show ipv6 ospf interface brief,
this command will also work because we are still
running OSPF version 3 after all, so this command will still
give us the output that we desire.
OK, next on my list is show ip route,
and I always like filtering the routes.
Like, I see the routes that were learned
via this routing protocol or that routing protocol.
So if we type in ospf and it's like, what, no OSPF learned
routes, that's because it wasn't really learned via OSPF,
it was learned via OSPF v3, and that will show us WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it was learned via OSPF v3, and that will show us
our OSPF learned rules for IPv4 if it's implemented
with address families.
And if we do show ipv6 route ospf and press Enter,
that still works just like it used to
and that's because we are still running OSPF version 3.
So most of the IPv6-related commands
are still going to function like they used to, even if we've
implemented address families.
All right, another one of my favorites is show ip ospf.
This is great.
It shows us about authentication for the areas
and the process and the router ID and lots of other details, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and the process and the router ID and lots of other details,
but because IPv4 is a guest within the routing process
for OSPF version 3, the syntax is
going to be slightly different.
It's going to be show ospfv3 space and a question mark.
And then we'll specify ipv4 space and a question mark.
But this will show us the output that show ip ospf used to.
So there is information about the process
that we're running--
OSPF version 3-- the address family for IPv4,
and then the details, including the backbone WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and then the details, including the backbone
and the other areas that this router's
connected to, which makes this device an area border router.
And if we want to see the OSPF for version 6,
we'd use the same command that's just like, show ospfv3 for ipv6
and press Enter.
And that will show us the address family IPv6 related
information for OSPF.
And if we just did the command show ospfv3 and press Enter,
it would show us first the address family for IPv4,
and if we go down a little bit, it
would show us the address family information for IPv6. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
would show us the address family information for IPv6.
We could page through that as well.
So next, what about the OSPF link-state database?
We have a link-state database for IPv4 and for IPv6.
It's all being controlled by OSPF version 3, however.
So we would show ip ospf database--
a command that many, many of us have issued for decades--
what's going on?
Well, they're still there.
We just need to specifically say it's the OSPF version 3
database for IPv4, which would go something like this-- show
ospfv3 ipv4 and then database. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
ospfv3 ipv4 and then database.
And then we could get more granular.
So we can say I want to see all the type
ones, which is the router LSAs.
And then, more specifically, I want
to go ahead and take a look at LSA type ones
that were generated by this router, R3.
So we could have been self-originate, press Enter.
And so the first syntax is the part
that's a little bit different.
Everything before the word database
needs be modified, so that's show ospfv3 ipv4, then WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
needs be modified, so that's show ospfv3 ipv4, then
the parameters as you would normally do after that.
So here are the two LSA type ones,
one for each area that R3 is generating--
one for the backbone area, one for Area 1, good to go.
And for IPv6, we'll use that same command again,
except we'll specify ipv6.
And the more exposure you have to this slightly different
syntax and the more practice you do with it, the easier it
will be for you to troubleshoot if you get into a situation
where you need to look at the link-state advertisements
for IPv4 or IPv6. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for IPv4 or IPv6.
And then if we want to take a look
at the entire link-state database,
press Enter, and that will go through all the LSAs including
the type eights and type nines, which are unique to IPv6.
So this router, being an area border router,
has a bunch of LSAs for both Area 0 and also for Area 1.
All right, and I've got a couple more
that I'd like us to practice and be aware of
and that is the good ol' favorite,
show ip ospf neighbor.
Oh no, no neighborships. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Oh no, no neighborships.
Well, the problem here is that it's
asking for the older OSPF version 2 process, which
doesn't exist.
So the correct way of doing this would be show--
instead of saying ip ospf, we'll say ospfv3 space protocol ipv4,
and then the keyword neighbor.
And that will show us our IPv4 neighbors under OSPF version 3,
and if we swap that out with a 6,
that will show us the IPv6 neighbors.
And if we did the older command of show ipv6 ospf neighbor,
that still works because it's still OSPF version 3 after all. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that still works because it's still OSPF version 3 after all.
So the real changes are for IPv4-related content
that we need to include the OSPFv3, and then
the address family of IPv4 to include the right output
that we want to see.
I have enjoyed our time together,
and the hands-on labs, as well, regarding address families
for OSPF.
And address families may not be the most common way
a small organization is going to implement OSPF.
However, as we have solutions like MPLS,
layer 3 VPNs that use VRFs and we're containing or keeping WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
layer 3 VPNs that use VRFs and we're containing or keeping
the address families in certain routing protocols
separate that we can have just for a certain customer,
address families have a very important use
if you have an application that needs them.
So I wanted to, in this video, to give you
some heads-up and preparation for not only how
to configure them within OSPF, but also
how to do some basic show commands that-- hey,
my show commands don't work anymore-- these labs
will help you reinforce and verify
that you can see the output like you had previously.
So going forward in the next sets of videos, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So going forward in the next sets of videos,
we're going to be doing a lot of troubleshooting with OSPF--
troubleshooting things like authentication and things
like network types that don't match
and things like MTU and timers and so forth.
And for the upcoming sets of videos,
I'm going to go back to the more traditional way of implementing
and configuring OSPF because it's
what most people are used to.
And it's also what most organizations are going
to be seeing on a daily basis.
So I did want you to be aware of the address families for OSPF, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I did want you to be aware of the address families for OSPF,
but I also wanted you to be aware
that the traditional method that we've used for decades
is also still alive and well and we should be aware
that they both exist.
So thanks for joining me in this set of videos.
I'll see you in the very next one.
Meanwhile, I hope this has been informative for you,
and I'd like to thank you for viewing.