WEBVTT

0:00:07.600000 --> 0:00:15.140000
 All right, let's take a look at the
 changes to the OSPF database.

0:00:15.140000 --> 0:00:22.760000
 Now the big changes are really just about
 the LSAs and how the information

0:00:22.760000 --> 0:00:26.360000
 gets advertised.

0:00:26.360000 --> 0:00:32.980000
 In IPv4, there was a little bit of a
 database, I don't know, of problems

0:00:32.980000 --> 0:00:35.160000
 the right word or whatever.

0:00:35.160000 --> 0:00:40.400000
 I mean obviously everything's fine, we've
 used it for years, but the issue

0:00:40.400000 --> 0:00:50.760000
 is by advertising prefixes in type 1
 LSAs, the problem is if a loopback

0:00:50.760000 --> 0:00:57.700000
 on a router goes down, we have to send
 out a new LSA and recalculate Dijkstra

0:00:57.700000 --> 0:01:01.280000
 and run the shortest path
 algorithm again and so on.

0:01:01.280000 --> 0:01:05.940000
 Now there have been optimization techniques
 and such over the years and

0:01:05.940000 --> 0:01:12.400000
 so on, but with OSPF version 3, they decided
 just to separate this information

0:01:12.400000 --> 0:01:17.580000
 out. So let's take a look at this, switch
 over here to the command line

0:01:17.580000 --> 0:01:21.980000
 and since I'm already sitting on router
 1 here, I will just start looking

0:01:21.980000 --> 0:01:24.620000
 at it on router 1.

0:01:24.620000 --> 0:01:34.100000
 So let me actually end out of this and
 we'll say show IPv6 OSPF database.

0:01:34.100000 --> 0:01:41.840000
 And just like OSPF version 2, this by
 itself will just give you a summary

0:01:41.840000 --> 0:01:48.280000
 and you can see before we even get started
 that we have a bit more information

0:01:48.280000 --> 0:01:55.440000
 here than you would have if you said
 show IP OSPF database and hit enter.

0:01:55.440000 --> 0:01:58.540000
 This is just going to show us now of
 course I have a lot more running

0:01:58.540000 --> 0:02:05.140000
 on that, but the main thing I want to
 show you is all you're getting is

0:02:05.140000 --> 0:02:09.640000
 router link states
 and netlink states.

0:02:09.640000 --> 0:02:13.780000
 This by the way is a whole different
 process, so sort of ignore this one

0:02:13.780000 --> 0:02:15.240000
 down here if you would.

0:02:15.240000 --> 0:02:20.380000
 That's to support the VMVPN cloud
 underneath all of this.

0:02:20.380000 --> 0:02:26.400000
 But yes, I have more routers and I have
 more information, but I only have

0:02:26.400000 --> 0:02:32.420000
 router link states and netlink states
 or type 1 and type 2 LSA's.

0:02:32.420000 --> 0:02:43.120000
 Where if we look up at the IPv6, type
 1s, type 2s, now this is of course

0:02:43.120000 --> 0:02:50.180000
 in fairness, this is because I have
 a separate area, area 45, so these

0:02:50.180000 --> 0:02:57.240000
 are your type 3 LSA's, but we pick
 up these two new ones, type 8s and

0:02:57.240000 --> 0:03:02.740000
 type 9s. And really what
 we're doing here is this.

0:03:02.740000 --> 0:03:12.340000
 If we were to say show me the IPv6
 OSPF database for router LSA's, so

0:03:12.340000 --> 0:03:18.480000
 this is type 1 LSA's, and you
 take a look at the database.

0:03:18.480000 --> 0:03:22.000000
 And all of this information up here,
 this tells you of course that it's

0:03:22.000000 --> 0:03:27.020000
 for IPv6 and so on, demand circuit
 bit, the routing bit is set and so

0:03:27.020000 --> 0:03:33.640000
 on. You know, the 32-bit router
 ID of who advertised it, okay.

0:03:33.640000 --> 0:03:40.520000
 By the way, with OSPF version 3, if
 you did happen to be running this

0:03:40.520000 --> 0:03:47.320000
 on an IPv6 only router, you would have
 to manually set the router ID under

0:03:47.320000 --> 0:03:49.040000
 the OSPF process.

0:03:49.040000 --> 0:03:55.400000
 Now I do have IPv4 on these routers
 as well, so it's not an issue, but

0:03:55.400000 --> 0:03:58.420000
 otherwise it won't be able to pick
 a router ID, so you have to give it

0:03:58.420000 --> 0:04:05.860000
 one. But the important point that I'm
 really in here to show you is this.

0:04:05.860000 --> 0:04:12.280000
 Link connected to another
 router, who 10222?

0:04:12.280000 --> 0:04:21.300000
 Okay. Out my interface 8 connected
 to his interface 10.

0:04:21.300000 --> 0:04:25.480000
 Now we don't even really care where
 these interface numbers come from.

0:04:25.480000 --> 0:04:31.300000
 I believe on this code it's the actual
 SNMP interface index number I believe.

0:04:31.300000 --> 0:04:33.580000
 We'd have to dig into
 that to look.

0:04:33.580000 --> 0:04:38.460000
 It really honestly doesn't matter, at
 this point because all we're really

0:04:38.460000 --> 0:04:46.040000
 trying to do is learn who's connected
 to whom on what interfaces.

0:04:46.040000 --> 0:04:48.140000
 That's what this is about.

0:04:48.140000 --> 0:04:51.560000
 And as far as the actual detail, you're
 not trying to be the routing protocol

0:04:51.560000 --> 0:04:54.500000
 here, at least I hope not.

0:04:54.500000 --> 0:05:00.340000
 CCIE level, you may start carrying
 a little bit more, but at least for

0:05:00.340000 --> 0:05:04.080000
 the fundamentals here, we don't have
 to get into the interface index IDs

0:05:04.080000 --> 0:05:10.640000
 and all that. But the main thing I'm trying
 to show you is that that information

0:05:10.640000 --> 0:05:14.780000
 right there, and when I say that information,
 I'm about that right there,

0:05:14.780000 --> 0:05:19.460000
 is 100% topology.

0:05:19.460000 --> 0:05:26.620000
 This guy's connected to that guy, this
 interface to this interface, and

0:05:26.620000 --> 0:05:29.280000
 it costs me a thousand
 to get there.

0:05:29.280000 --> 0:05:36.780000
 That's it. There is
 no IPv6 prefix.

0:05:36.780000 --> 0:05:43.720000
 So this is router one telling me he's
 connected to router two, which we

0:05:43.720000 --> 0:05:45.880000
 knew, that's his tunnel interface.


0:05:45.880000 --> 0:05:48.940000
 He's also going to tell me he's
 connected to router three.

0:05:48.940000 --> 0:06:18.040000
 There you go. Then we move on, and
 we have advertising router 102222.

0:06:18.040000 --> 0:06:21.060000
 So this is router two telling
 me his information.

0:06:21.060000 --> 0:06:25.240000
 The really cool thing, and this applies,
 of course, to all of OSPF.

0:06:25.240000 --> 0:06:28.020000
 Well, except for one exception
 in a minute.

0:06:28.020000 --> 0:06:33.520000
 But certainly for all of OSPF version
 two and for most of version three.

0:06:33.520000 --> 0:06:38.780000
 Since everybody in the area has to have
 the same database, you can really

0:06:38.780000 --> 0:06:40.920000
 look at the database
 from any router.

0:06:40.920000 --> 0:06:44.720000
 Now the exception I just mentioned is
 type eight LSA's are going to get

0:06:44.720000 --> 0:06:45.960000
 two in a minute here.

0:06:45.960000 --> 0:06:51.460000
 They are definitely different, so that's
 not going to be the case there.

0:06:51.460000 --> 0:06:58.460000
 But once again, this is router two
 telling me what he's connected to a

0:06:58.460000 --> 0:07:00.300000
 transit network.

0:07:00.300000 --> 0:07:07.480000
 Now if you guys have never really dealt
 and dove into the OSPF database,

0:07:07.480000 --> 0:07:14.740000
 a transit network simply means
 that there's a DR involved.

0:07:14.740000 --> 0:07:20.920000
 So this means that by default it's a
 broadcast segment or a non-broadcast

0:07:20.920000 --> 0:07:26.540000
 segment. There is a DR and transit
 network means you know what?

0:07:26.540000 --> 0:07:33.380000
 You're going to get this information
 from the DR from a type two LSA.

0:07:33.380000 --> 0:07:37.620000
 So that's all that's really
 telling us right now.

0:07:37.620000 --> 0:07:43.480000
 But again, I'm not too interested at
 this point in, and we could draw

0:07:43.480000 --> 0:07:48.320000
 this out. I do this a lot in the classroom
 in our OSPF section is just

0:07:48.320000 --> 0:07:49.740000
 draw out the whole database.

0:07:49.740000 --> 0:07:53.320000
 And what is this thing actually telling
 you and what's a transit network

0:07:53.320000 --> 0:07:57.400000
 and all that? I don't think we need that
 level of detail here where we're

0:07:57.400000 --> 0:07:59.620000
 trying to just focus on IPv6.

0:07:59.620000 --> 0:08:03.980000
 But again, the point I'm really trying
 to make here is if you look at

0:08:03.980000 --> 0:08:06.020000
 that, it's a transit network.

0:08:06.020000 --> 0:08:11.060000
 Go see this DR. My link
 to it is a one.

0:08:11.060000 --> 0:08:17.480000
 Okay. Again, no prefix.

0:08:17.480000 --> 0:08:18.920000
 That's the main point.

0:08:18.920000 --> 0:08:21.460000
 It's topology. Okay.

0:08:21.460000 --> 0:08:28.200000
 And by the way, little thing I like
 to always point out that the DR for

0:08:28.200000 --> 0:08:30.420000
 this segment is 1022.

0:08:30.420000 --> 0:08:33.460000
 Is that this router?

0:08:33.460000 --> 0:08:35.860000
 Advertising router 1022.

0:08:35.860000 --> 0:08:43.240000
 And a lot of people look at that and go,
 well, yeah, that's the same router.

0:08:43.240000 --> 0:08:46.760000
 No, it's actually not.

0:08:46.760000 --> 0:08:50.840000
 The DR is a virtual router.

0:08:50.840000 --> 0:08:54.140000
 It's an entity. It's
 a logical device.

0:08:54.140000 --> 0:08:56.120000
 It doesn't actually exist.

0:08:56.120000 --> 0:09:00.600000
 Is it using router 2's router ID?

0:09:00.600000 --> 0:09:07.160000
 Yes. For all intents and purposes, if
 we were out in the real world talking

0:09:07.160000 --> 0:09:12.060000
 to people and talking to other engineers,
 would we say, oh, yeah, router

0:09:12.060000 --> 0:09:14.400000
 2's the DR on that segment?

0:09:14.400000 --> 0:09:17.380000
 Yes. Yes, we would.

0:09:17.380000 --> 0:09:22.640000
 Okay. But at the end of the day, why
 in the world would you have a cost

0:09:22.640000 --> 0:09:28.000000
 to get to yourself?

0:09:28.000000 --> 0:09:31.660000
 Just saying. From a
 database standpoint.

0:09:31.660000 --> 0:09:34.740000
 And again, if we started mapping this
 whole thing out, we would have to

0:09:34.740000 --> 0:09:39.080000
 write the DR as a separate
 entity from router 2.

0:09:39.080000 --> 0:09:44.080000
 Is router 2 responsible
 for the DR?

0:09:44.080000 --> 0:09:47.020000
 Absolutely. Absolutely.

0:09:47.020000 --> 0:09:49.520000
 And that's why we say
 that he's the DR.

0:09:49.520000 --> 0:09:53.140000
 But I just want to point out from a
 completely technical standpoint, he

0:09:53.140000 --> 0:09:59.500000
 is not the DR. The DR is a logical entity
 being, I don't know, presented

0:09:59.500000 --> 0:10:04.040000
 by, being projected by, however
 you want to say it.

0:10:04.040000 --> 0:10:07.560000
 You can say being created
 by router 2.

0:10:07.560000 --> 0:10:13.540000
 Okay. But he is not the DR because we
 would not have a metric to the DR

0:10:13.540000 --> 0:10:18.200000
 if it was actually literally
 us from a logical standpoint.

0:10:18.200000 --> 0:10:22.320000
 Okay. Anyway, again, a little bit technical
 detail there, but I'm just

0:10:22.320000 --> 0:10:26.660000
 saying, you know, you would not
 have a metric if it was you.

0:10:26.660000 --> 0:10:31.420000
 Then of course he's advertising
 his link to router 1.

0:10:31.420000 --> 0:10:33.080000
 We're already aware of this.

0:10:33.080000 --> 0:10:35.420000
 And some other things
 to point out here.

0:10:35.420000 --> 0:10:40.960000
 I'm really just trying to show you that
 this is a hundred percent topology.

0:10:40.960000 --> 0:10:43.500000
 There are no IPv6 prefix.

0:10:43.500000 --> 0:10:46.240000
 And at that point, what would also
 be the point of advertising a loop

0:10:46.240000 --> 0:10:50.860000
 back? Notice the loopbacks
 aren't here.

0:10:50.860000 --> 0:10:52.920000
 There's nobody else out there.

0:10:52.920000 --> 0:10:55.040000
 It's not a link to
 another network.

0:10:55.040000 --> 0:10:56.540000
 It's not point to point.

0:10:56.540000 --> 0:10:57.840000
 It's not transit.

0:10:57.840000 --> 0:10:59.240000
 It's a loop back.

0:10:59.240000 --> 0:11:04.340000
 There'd be no point in putting
 that in topology announcements.

0:11:04.340000 --> 0:11:07.360000
 And that's 100 percent
 the point I'm making.

0:11:07.360000 --> 0:11:10.580000
 And I'm not going to sit here and go
 through the entire database at this

0:11:10.580000 --> 0:11:16.620000
 point. What I'm really here to show
 you is that the type 1 LSAs in OSPF

0:11:16.620000 --> 0:11:22.660000
 version 3 are now 100 percent
 topology information.

0:11:22.660000 --> 0:11:27.080000
 There is no IPv6 prefix
 information here at all.

0:11:27.080000 --> 0:11:31.020000
 And the exact same thing applies to the
 type 2s that we were just talking

0:11:31.020000 --> 0:11:35.820000
 about. So the network
 LSAs, same thing.

0:11:35.820000 --> 0:11:46.460000
 This is router 2 acting on behalf of
 the DR saying that this is link state

0:11:46.460000 --> 0:11:51.660000
 ID 2 on the DR. Okay.

0:11:51.660000 --> 0:11:56.760000
 And 10222 and 10444 are
 both attached to it.

0:11:56.760000 --> 0:12:04.960000
 Again, look at that.

0:12:04.960000 --> 0:12:09.940000
 I'm going to do this shared segment
 handled by the DR 10222.

0:12:09.940000 --> 0:12:14.560000
 Much like on the link between
 routers 3 and 4.

0:12:14.560000 --> 0:12:21.360000
 Okay. Between 3 and 4, we also have
 these routers attached, which also

0:12:21.360000 --> 0:12:26.180000
 shows me as a reminder here that
 we never configured switch for.

0:12:26.180000 --> 0:12:31.740000
 Or switch for if you look at our
 diagram, which I have handy here.

0:12:31.740000 --> 0:12:37.440000
 If we switch over to our diagram, see
 switch for right here is supposed

0:12:37.440000 --> 0:12:41.560000
 to be running OSPF
 and I missed it.

0:12:41.560000 --> 0:12:44.520000
 So this is another nice thing about
 going through the database.

0:12:44.520000 --> 0:12:46.700000
 And this is one of those things
 I always tell in class.

0:12:46.700000 --> 0:12:51.660000
 You verify everything because everybody's
 human and everybody makes mistakes.

0:12:51.660000 --> 0:12:54.760000
 And you really need to make
 sure that things are right.

0:12:54.760000 --> 0:13:01.100000
 So I should be seeing 10, 10, 10, 10
 on here, which is switch 4's, well,

0:13:01.100000 --> 0:13:03.160000
 it's going to be switch
 4's router ID.

0:13:03.160000 --> 0:13:07.560000
 So on switch 4, I need to
 say interface VLAN 344.

0:13:07.560000 --> 0:13:14.320000
 IPv6 OSPF 1 area 0 and
 interface loop back 0.

0:13:14.320000 --> 0:13:20.500000
 Also an area 0. Now, if we go back to
 router 1, that last command should

0:13:20.500000 --> 0:13:22.240000
 look just a little bit different.

0:13:22.240000 --> 0:13:25.940000
 There we go. Now we see
 the attached router.

0:13:25.940000 --> 0:13:31.720000
 10, 10, 10, 10. So again, one of the
 other things about going through

0:13:31.720000 --> 0:13:34.080000
 the database is making sure
 you didn't miss anything.

0:13:34.080000 --> 0:13:37.960000
 And everything's the way you
 expect to see it and so on.

0:13:37.960000 --> 0:13:45.720000
 But in any case, again, my main point,
 type 1, type 2 LSAs in IP version

0:13:45.720000 --> 0:13:48.060000
 4, that's all you would have had.

0:13:48.060000 --> 0:14:04.580000
 So again, if I said do show IP OSPF,
 let's say OSPF 1 database router,

0:14:04.580000 --> 0:14:10.240000
 if I looked at the type 1 LSAs for my
 IP version 2, this is exactly the

0:14:10.240000 --> 0:14:11.580000
 point I'm trying to make.

0:14:11.580000 --> 0:14:13.580000
 Notice what he's telling you.

0:14:13.580000 --> 0:14:15.840000
 Oh yes, it's topology.

0:14:15.840000 --> 0:14:19.220000
 I agree. There's topology
 information right there.

0:14:19.220000 --> 0:14:20.600000
 It's a stub network.

0:14:20.600000 --> 0:14:22.120000
 But what else is he telling you?

0:14:22.120000 --> 0:14:26.180000
 Oh, by the way, there's the IP address
 and there's the network mask.

0:14:26.180000 --> 0:14:32.340000
 See, he's announcing the prefix
 information in a type 1.

0:14:32.340000 --> 0:14:34.200000
 That's his loop back.

0:14:34.200000 --> 0:14:38.580000
 10, 1, 1, 1 is router 1's loop back
 that he's announcing right there.

0:14:38.580000 --> 0:14:40.620000
 And this is exactly the
 point I was making.

0:14:40.620000 --> 0:14:47.180000
 If that loop back went down, he would
 have to send a new type 1 LSA out

0:14:47.180000 --> 0:14:48.380000
 to his neighbors.

0:14:48.380000 --> 0:14:52.160000
 This is going to flood through the whole
 area and make everybody run Dijkstra

0:14:52.160000 --> 0:14:57.340000
 again. Where on the other hand, that
 same information from OSPF version

0:14:57.340000 --> 0:15:10.820000
 3, router 1 doesn't even
 mention his loop back.

0:15:10.820000 --> 0:15:13.040000
 It's not even mentioned.

0:15:13.040000 --> 0:15:14.320000
 What's the point?

0:15:14.320000 --> 0:15:15.860000
 That's not topology.

0:15:15.860000 --> 0:15:22.040000
 If his loop back goes down, pardon me
 for saying so, but nobody else cares,

0:15:22.040000 --> 0:15:27.180000
 nobody else in the entire network cares
 that his loop back went down.

0:15:27.180000 --> 0:15:31.380000
 That can in no way affect
 their topology.

0:15:31.380000 --> 0:15:37.320000
 Now, do they care that the prefix for
 that loop back is going to go away?

0:15:37.320000 --> 0:15:43.320000
 Of course. But what I'm trying to get
 us to is the importance in separating

0:15:43.320000 --> 0:15:49.180000
 the topology from the prefixes
 on that topology.

0:15:49.180000 --> 0:15:52.700000
 This is a much more efficient
 way of doing it.

0:15:52.700000 --> 0:15:57.660000
 But a lot of people get in here and they're
 just like, oh, okay, you know,

0:15:57.660000 --> 0:16:01.880000
 you read a book or whatever, and I'm
 sure as heck not coming down on that,

0:16:01.880000 --> 0:16:05.760000
 obviously. I'm just saying it's sometimes
 hard when you're going through

0:16:05.760000 --> 0:16:09.880000
 documentation and reading a book, and
 this and that to go, okay, I'm reading

0:16:09.880000 --> 0:16:14.080000
 here, that they added
 type 8 and 9 LSAs.

0:16:14.080000 --> 0:16:17.660000
 Great. Why? What's the difference?


0:16:17.660000 --> 0:16:21.400000
 OSPF version 2 didn't have
 those, and now we do.

0:16:21.400000 --> 0:16:26.480000
 And so hopefully this is helping
 to get you to why.

0:16:26.480000 --> 0:16:34.240000
 Okay. It's because this with IPv4 was a
 little, and again, it's not horrible.

0:16:34.240000 --> 0:16:36.880000
 We've been using it for
 years, and it's okay.

0:16:36.880000 --> 0:16:38.500000
 It's not horrible.

0:16:38.500000 --> 0:16:39.920000
 It's not the end of the world.

0:16:39.920000 --> 0:16:46.800000
 But it was a bit of an issue with advertising
 the prefixes in the LSAs

0:16:46.800000 --> 0:16:50.720000
 for IPv4. We just simply
 separated that out.

0:16:50.720000 --> 0:17:00.160000
 So with IPv6, your type 1s and type
 2s are 100% topology information.

0:17:00.160000 --> 0:17:03.600000
 Now, where do the prefixes go?

0:17:03.600000 --> 0:17:06.920000
 I'm so glad you asked.

0:17:06.920000 --> 0:17:12.740000
 The prefix information moves to the
 type 8s and 9s, and that's what's

0:17:12.740000 --> 0:17:19.700000
 new. So now we're going
 to say database link.

0:17:19.700000 --> 0:17:22.940000
 And these are your type 8s, okay?

0:17:22.940000 --> 0:17:27.560000
 And like always, the database, you
 know, on the outputs, sometimes it

0:17:27.560000 --> 0:17:32.520000
 gives you the LSA type up there,
 and sometimes it doesn't.

0:17:32.520000 --> 0:17:35.020000
 A little bit of inconsistency
 there.

0:17:35.020000 --> 0:17:38.600000
 But here's the point though.

0:17:38.600000 --> 0:17:44.180000
 The next part, okay, so type 1s
 and 2s, tell us our topology.

0:17:44.180000 --> 0:17:47.880000
 Great. Type 8s and 9s.

0:17:47.880000 --> 0:17:52.040000
 Okay, so this is going to tell us our
 prefix, and I know you're sitting

0:17:52.040000 --> 0:17:54.840000
 there going, okay,
 David, I got that.

0:17:54.840000 --> 0:17:57.060000
 Why 8s versus 9s?

0:17:57.060000 --> 0:18:06.800000
 Well, the difference is type 8s are going
 to be information about networks

0:18:06.800000 --> 0:18:11.140000
 that I am directly connected to.

0:18:11.140000 --> 0:18:15.240000
 So I'm on the link.

0:18:15.240000 --> 0:18:18.240000
 That's possibly the
 best way to say it.

0:18:18.240000 --> 0:18:21.920000
 Maybe not. That's my best
 way of saying it though.

0:18:21.920000 --> 0:18:27.960000
 It's information about the networks
 that you are connected to and need

0:18:27.960000 --> 0:18:30.640000
 to tell your neighbors about.

0:18:30.640000 --> 0:18:33.360000
 Not the whole database.

0:18:33.360000 --> 0:18:36.800000
 Let's take a look at what
 I mean here, okay?

0:18:36.800000 --> 0:18:40.940000
 These are all the LSA's
 that Router1 has.

0:18:40.940000 --> 0:18:43.640000
 And I just want to point
 out here a couple things.

0:18:43.640000 --> 0:18:45.580000
 So here's Router1.

0:18:45.580000 --> 0:18:48.920000
 So this is his own generated LSA.

0:18:48.920000 --> 0:18:54.520000
 And he's going to tell people about
 123 that, and I know you guys don't

0:18:54.520000 --> 0:18:56.460000
 have the topology memorized
 or anything.

0:18:56.460000 --> 0:18:59.620000
 Hopefully, maybe you printed
 it and have it close.

0:18:59.620000 --> 0:19:03.280000
 But that is the DMVPN cloud.

0:19:03.280000 --> 0:19:07.600000
 Now, I'm going to just stop
 right there for a second.

0:19:07.600000 --> 0:19:08.600000
 I'm going to filter this.

0:19:08.600000 --> 0:19:11.040000
 I'm going to say self-originated.

0:19:11.040000 --> 0:19:15.340000
 These are just the ones that
 Router1 is generating.

0:19:15.340000 --> 0:19:19.120000
 Or should I say the one that
 Router1 is generating?

0:19:19.120000 --> 0:19:26.660000
 And I just want to point out that he's
 only advertising his DMVPN network

0:19:26.660000 --> 0:19:33.520000
 in a Type 8. What am I pointing
 out the lack of?

0:19:33.520000 --> 0:19:35.200000
 Where's his loopback?

0:19:35.200000 --> 0:19:39.420000
 His loopback is not there.

0:19:39.420000 --> 0:19:45.800000
 Type 8s are only about your
 links to your neighbors.

0:19:45.800000 --> 0:19:49.640000
 That's it. So if I go back to looking
 at the whole thing again, we'll

0:19:49.640000 --> 0:19:52.020000
 take the self-originate
 off of there.

0:19:52.020000 --> 0:19:56.600000
 I want you to note that Router1's neighbors
 are only sending him Type

0:19:56.600000 --> 0:20:00.300000
 8s about the directly connected.

0:20:00.300000 --> 0:20:07.980000
 That's it. So this is Router1 telling
 everybody else about his DMVPN.

0:20:07.980000 --> 0:20:10.120000
 This is Router2.

0:20:10.120000 --> 0:20:13.100000
 Remember, I'm on Router1
 right now.

0:20:13.100000 --> 0:20:18.020000
 This is Router2 telling
 Router1 about what?

0:20:18.020000 --> 0:20:24.760000
 The DMVPN. This is Router3 telling
 Router1 about the DMVPN.

0:20:24.760000 --> 0:20:26.660000
 And that's going to be about it.

0:20:26.660000 --> 0:20:28.860000
 See? Command-line back.

0:20:28.860000 --> 0:20:34.540000
 That's it. Because that's the
 only stuff we're connected on.

0:20:34.540000 --> 0:20:41.200000
 Router2 is not telling Router1 about
 VLAN24 between Router2 and 4.

0:20:41.200000 --> 0:20:43.420000
 Router1's not connected to that.

0:20:43.420000 --> 0:20:45.220000
 He doesn't care.

0:20:45.220000 --> 0:20:50.000000
 Type 8s are about just what
 you're connected to.

0:20:50.000000 --> 0:20:52.500000
 And here's the important
 part and why.

0:20:52.500000 --> 0:20:55.460000
 Because again, I like
 to get to the why.

0:20:55.460000 --> 0:20:57.080000
 I think it helps people learn.

0:20:57.080000 --> 0:20:58.400000
 At least I hope that's
 the case for you.

0:20:58.400000 --> 0:21:01.280000
 Why is it like this?

0:21:01.280000 --> 0:21:04.600000
 Honestly, so we can
 get this right here.

0:21:04.600000 --> 0:21:06.860000
 Link local address.

0:21:06.860000 --> 0:21:11.720000
 Remember, all the routing
 is about link locals.

0:21:11.720000 --> 0:21:17.280000
 So as I do this, I'm learning the link
 locals of my directly connected

0:21:17.280000 --> 0:21:23.580000
 neighbors. And I'm tying that to the
 network that they are connected to

0:21:23.580000 --> 0:21:35.960000
 with me. Okay. And by the way, please
 note that this also ties back to

0:21:35.960000 --> 0:21:37.580000
 that interface ID.

0:21:37.580000 --> 0:21:41.620000
 If you remember on Router1, we pointed
 out earlier that the tunnel was

0:21:41.620000 --> 0:21:45.840000
 interface ID8. Notice
 what it's doing here.

0:21:45.840000 --> 0:21:54.340000
 This is basically now tying this prefix
 and this link local back to this

0:21:54.340000 --> 0:21:58.920000
 interface ID8. This interface which links
 it back to the appropriate type

0:21:58.920000 --> 0:22:01.880000
 1 or type 2 LSAT.

0:22:01.880000 --> 0:22:05.940000
 So from that respect, it's sort of like
 a little bit of a relational database

0:22:05.940000 --> 0:22:11.920000
 here where we're relating this prefix
 information back to the interfaces

0:22:11.920000 --> 0:22:16.840000
 now. But again, this is only for the
 stuff we're directly connected to.

0:22:16.840000 --> 0:22:21.720000
 We don't need this level of detail
 for all the other prefixes.

0:22:21.720000 --> 0:22:32.400000
 And all the other prefixes
 are under type 9s.

0:22:32.400000 --> 0:22:35.920000
 Okay. Now let's take
 a look at the type 9.

0:22:35.920000 --> 0:22:39.580000
 Notice the link state
 ID on this one is 0.

0:22:39.580000 --> 0:22:44.440000
 The referenced link state ID is 0.


0:22:44.440000 --> 0:22:49.940000
 Okay. Now, the reason for this?

0:22:49.940000 --> 0:22:52.700000
 If you really think this through.

0:22:52.700000 --> 0:22:57.880000
 Okay. I've built the
 entire OSPF database.

0:22:57.880000 --> 0:23:00.640000
 I know who everybody's linked to.

0:23:00.640000 --> 0:23:02.640000
 I know all my costs.

0:23:02.640000 --> 0:23:05.120000
 I've got all of that.

0:23:05.120000 --> 0:23:09.220000
 I know about what I'm directly connected
 to because I got that from a

0:23:09.220000 --> 0:23:14.240000
 type 8. Okay. Now what do I need?

0:23:14.240000 --> 0:23:17.060000
 I need all the other prefixes.

0:23:17.060000 --> 0:23:23.680000
 So this is router 1 telling
 everybody else about what.

0:23:23.680000 --> 0:23:31.440000
 Oh, by the way, I have this loop back
 and I have this DMVPN network.

0:23:31.440000 --> 0:23:33.240000
 What's router 2 telling me?

0:23:33.240000 --> 0:23:41.340000
 Router 2 is telling me about his
 loop back and the 123 network.

0:23:41.340000 --> 0:23:51.900000
 Okay. Router 2 is also telling
 me about the 24 network.

0:23:51.900000 --> 0:23:58.180000
 And yes, he's creating this
 per link, by the way.

0:23:58.180000 --> 0:24:05.780000
 Router 3 is telling me about his
 loop back and the DMVPN network.

0:24:05.780000 --> 0:24:08.160000
 And let's see, this is switch 4.

0:24:08.160000 --> 0:24:20.640000
 It should just be telling
 me his loop back.

0:24:20.640000 --> 0:24:31.840000
 Okay. So, this is all the
 prefix information.

0:24:31.840000 --> 0:24:39.140000
 And if you think about it, what's the need
 to know any more detailed information,

0:24:39.140000 --> 0:24:47.200000
 other than, okay, this 10, 10, 10, 10
 guy, he has this prefix with this

0:24:47.200000 --> 0:24:52.640000
 prefix length or for your IPV4 familiar
 folks, we can call that a mask,

0:24:52.640000 --> 0:24:56.800000
 right? But that's all
 he needs to know.

0:24:56.800000 --> 0:25:01.560000
 Because I go back to my type 1s and
 2s and go, okay, now how do I get

0:25:01.560000 --> 0:25:03.700000
 to 10, 10, 10, 10?

0:25:03.700000 --> 0:25:07.820000
 And a lot of people, again, look at this
 and go, you know, yeah, but what

0:25:07.820000 --> 0:25:16.020000
 prefixes it on? All they ask is stupid
 question, why do you care?

0:25:16.020000 --> 0:25:21.540000
 From router 1's perspective, why does
 he care what interface or link or

0:25:21.540000 --> 0:25:26.400000
 whatever, that prefix
 is on, on switch 4.

0:25:26.400000 --> 0:25:30.300000
 All I need to know is that to get to
 that prefix, I go to that router

0:25:30.300000 --> 0:25:37.020000
 ID. Done. Everything else I
 got from the type 1s and 2s.

0:25:37.020000 --> 0:25:39.180000
 That's all we need to know.

0:25:39.180000 --> 0:25:43.300000
 Okay? So that's your 8 to 9s.

0:25:43.300000 --> 0:25:47.180000
 Those are the big, big changes
 to the database.

0:25:47.180000 --> 0:25:57.160000
 Now, just to summarize here, if I said
 to look at database summary, now,

0:25:57.160000 --> 0:26:02.860000
 if you're familiar with IPV4 here real
 quick, let me do this, show IP,

0:26:02.860000 --> 0:26:06.280000
 oh, I'm not going to have any
 because everything's one area.

0:26:06.280000 --> 0:26:11.260000
 But IPV6, OSPF1, you know what?

0:26:11.260000 --> 0:26:14.000000
 We can cheat real quick,
 just so I can show you.

0:26:14.000000 --> 0:26:17.460000
 I'm going to go to router 2 and I'm
 going to say interface, loop back

0:26:17.460000 --> 0:26:24.580000
 0, IP, OSPF1, area 20, whatever.

0:26:24.580000 --> 0:26:28.420000
 I'm just going to put it in another
 area just so we have a summary to

0:26:28.420000 --> 0:26:40.080000
 look at real quick.

0:26:40.080000 --> 0:26:45.900000
 So there's the type 3 LSA for router 2's
 loop back now, since I just brought

0:26:45.900000 --> 0:26:47.580000
 it into another area.

0:26:47.580000 --> 0:26:51.320000
 Okay? And don't worry about the advertising
 router thing, that's all it

0:26:51.320000 --> 0:26:55.980000
 has to do with the underlying
 DMVPN cloud and such.

0:26:55.980000 --> 0:26:56.680000
 Don't worry about that.

0:26:56.680000 --> 0:27:04.240000
 Okay? But the point is, there is
 a good old type 3 summary LSA.

0:27:04.240000 --> 0:27:13.560000
 Problem is, is if I say do show IPV6
 database summary, I get an error.

0:27:13.560000 --> 0:27:22.520000
 And that's because there's not much
 difference in the type 3 LSA except

0:27:22.520000 --> 0:27:27.460000
 the name. They're now called
 inter-area prefix.

0:27:27.460000 --> 0:27:30.940000
 And I'm just going to quit out of the
 output there for a second because

0:27:30.940000 --> 0:27:36.400000
 I just want you to sort of see the
 version 2 versus the version 3.

0:27:36.400000 --> 0:27:40.460000
 And if you really look back and forth
 between them here, there's not a

0:27:40.460000 --> 0:27:42.120000
 whole lot different.

0:27:42.120000 --> 0:27:51.500000
 Basically it's advertising a prefix,
 the length, and the router ID that

0:27:51.500000 --> 0:27:52.680000
 you use to get there.

0:27:52.680000 --> 0:27:55.280000
 And we have the same thing here.

0:27:55.280000 --> 0:28:04.900000
 Right? We have the prefix, the mask,
 and where we go to get to it.

0:28:04.900000 --> 0:28:09.300000
 It's the same information,
 same information.

0:28:09.300000 --> 0:28:12.060000
 And of course, you know, the metric
 and various other things, right?

0:28:12.060000 --> 0:28:17.880000
 This guy's got a metric of 1, this guy's
 got a metric of 64, and so on.

0:28:17.880000 --> 0:28:20.980000
 But it's the same fundamental
 information.

0:28:20.980000 --> 0:28:25.760000
 Obviously the formatting is slightly
 different on the output, but it is

0:28:25.760000 --> 0:28:31.380000
 the same info. The type
 3s didn't change.

0:28:31.380000 --> 0:28:36.100000
 They just changed the name of them because
 with summary, I think it gets

0:28:36.100000 --> 0:28:37.680000
 confused some people.

0:28:37.680000 --> 0:28:43.940000
 When they heard that they were summary,
 link states, people got in their

0:28:43.940000 --> 0:28:47.280000
 head that it was a network
 summarization.

0:28:47.280000 --> 0:28:50.580000
 And if you know the OSPF database,
 you know that's not true.

0:28:50.580000 --> 0:28:56.300000
 It wasn't a network summary,
 it's a database summary.

0:28:56.300000 --> 0:28:59.000000
 And I think that really
 confused some people.

0:28:59.000000 --> 0:29:02.500000
 So when they did OSPF version
 3, they said, you know what?

0:29:02.500000 --> 0:29:05.600000
 Let's call this a little
 more appropriate.

0:29:05.600000 --> 0:29:11.300000
 We'll call it an inter-area prefix,
 which really makes sense anyway.

0:29:11.300000 --> 0:29:20.900000
 Because if you look at the prefix, the
 type 9s, they're called intra-area

0:29:20.900000 --> 0:29:27.100000
 prefix. So all we really did is go
 a bit more consistent on the naming

0:29:27.100000 --> 0:29:29.460000
 convention. Okay?

0:29:29.460000 --> 0:29:33.760000
 So it's inter-area
 versus intra-area.

0:29:33.760000 --> 0:29:37.380000
 Now, truth be told what they probably
 should have done is gone a little

0:29:37.380000 --> 0:29:39.900000
 better with the commands
 than two, huh?

0:29:39.900000 --> 0:29:47.380000
 You know, maybe it should have been
 inter-area prefix versus intra-area,

0:29:47.380000 --> 0:29:50.360000
 what I wouldn't work
 right anyway, right?

0:29:50.360000 --> 0:29:58.580000
 Versus intra-area, but either
 way, of course, it's not.

0:29:58.580000 --> 0:30:04.340000
 It's just prefix versus
 inter-area prefix.

0:30:04.340000 --> 0:30:10.320000
 Okay? So, you know, a little more
 consistency on the naming.

0:30:10.320000 --> 0:30:15.640000
 Not necessarily better consistency
 on the command, but nonetheless.

0:30:15.640000 --> 0:30:20.840000
 Okay? Now, what we have not looked
 at here in this section is type 4s

0:30:20.840000 --> 0:30:25.600000
 and 5s. I'm not going to leave them
 out, but I'm also not going to look

0:30:25.600000 --> 0:30:29.080000
 at them here because we've not
 done any redistribution yet.

0:30:29.080000 --> 0:30:35.120000
 So, I will save that for after
 we do redistribution.

0:30:35.120000 --> 0:30:43.040000
 I'll come back and we'll do OSPF
 type 4s and 5s for the database.

0:30:43.040000 --> 0:30:48.720000
 Just for the sake of completeness in
 this section, once again, they're

0:30:48.720000 --> 0:30:52.620000
 the same. They just
 changed the name.

0:30:52.620000 --> 0:30:55.940000
 So there's nothing to look at, but just
 in case you're watching this section,

0:30:55.940000 --> 0:31:05.060000
 hoping to get those commands out of
 it, its inter-area router would be

0:31:05.060000 --> 0:31:10.300000
 your type 4s, which, of course, we don't
 have any right now, and the other

0:31:10.300000 --> 0:31:14.640000
 command, and we'll see them later, like
 I said, but this one is exactly

0:31:14.640000 --> 0:31:20.440000
 like IPv4 external.

0:31:20.440000 --> 0:31:23.080000
 So, those are your
 commands for it.

0:31:23.080000 --> 0:31:27.780000
 We'll see them once we do some redistribution,
 but again, just for completeness

0:31:27.780000 --> 0:31:30.500000
 in this section, they're the same.


0:31:30.500000 --> 0:31:34.080000
 The type 4 hasn't changed any
 more than the type 3 did.

0:31:34.080000 --> 0:31:35.900000
 It just changed its name.

0:31:35.900000 --> 0:31:38.440000
 It's not an ASBR summary.

0:31:38.440000 --> 0:31:46.980000
 Now, it's just an inter-area router,
 and the type 5s, well, they really

0:31:46.980000 --> 0:31:49.100000
 haven't changed much at all.

0:31:49.100000 --> 0:31:53.260000
 This is going to be an advanced statement
 if you don't understand it.

0:31:53.260000 --> 0:31:56.920000
 I don't necessarily worry about that,
 but for some people who are maybe

0:31:56.920000 --> 0:32:01.640000
 a little more advanced in the LSPF
 department, if you're familiar with

0:32:01.640000 --> 0:32:07.340000
 the IP version 4, if you're familiar
 with the forwarding address, you

0:32:07.340000 --> 0:32:12.360000
 know, the forwarding address was a way
 for you to find your best possible

0:32:12.360000 --> 0:32:15.280000
 path to the real next hop.

0:32:15.280000 --> 0:32:22.600000
 It was a path optimization tool, but
 with IPv6, since everything and all

0:32:22.600000 --> 0:32:28.100000
 of our routing is on Link Local, telling
 somebody else my Link Local address

0:32:28.100000 --> 0:32:32.300000
 to get somewhere does nobody
 any good at all.

0:32:32.300000 --> 0:32:38.080000
 So, the whole forwarding
 address idea is gone.

0:32:38.080000 --> 0:32:39.840000
 It's just gone. It's
 just not there.

0:32:39.840000 --> 0:32:44.040000
 We'll see that in the redistribution
 section, but I didn't want to get

0:32:44.040000 --> 0:32:46.560000
 that, at least, said in here.

0:32:46.560000 --> 0:32:50.260000
 So, that goes away, but other than that,
 the type 5s are almost identical