﻿1
00:00:02,297 --> 00:00:08,677
[music]

2
00:00:08,677 --> 00:00:14,479
OSPF, once again, we're
going to be running here.

3
00:00:14,479 --> 00:00:18,485
And we're going to be running
this over our DMVPN cloud.

4
00:00:18,485 --> 00:00:23,213
Now, we've not looked of course
at the DMVPN configuration,

5
00:00:23,213 --> 00:00:26,094
but it's already there,
it's already set up,

6
00:00:26,094 --> 00:00:27,847
I've already enumerated it.

7
00:00:27,847 --> 00:00:30,175
We will get back to looking at that later.

8
00:00:30,175 --> 00:00:34,672
We'll probably do it in
a slightly different

9
00:00:34,684 --> 00:00:38,091
topology when we
do go over DMVPN.

10
00:00:38,289 --> 00:00:44,500
So, really, for right now, all that
really matters to us is that in

11
00:00:44,500 --> 00:00:50,003
the OSPF environment here,
Router 1 is our hub.

12
00:00:50,182 --> 00:01:00,305
So for the sake of OSPF it's really just
going to act like a NBMA network for us.

13
00:01:00,305 --> 00:01:02,726
So that's the only reason
I even have it there.

14
00:01:02,726 --> 00:01:07,010
This is not the time to be
jumping into DMVPN with IPv6,

15
00:01:07,010 --> 00:01:12,036
but it's there, it's built, and it's
going to act like a WAN environment

16
00:01:12,036 --> 00:01:14,430
for us here for OSPF.

17
00:01:14,775 --> 00:01:18,555
We're, of course, going to
also run it over VLAN 344,

18
00:01:18,555 --> 00:01:26,436
VLAN 24, and then over there between
Routers 4 and 5 on the serial links.

19
00:01:26,436 --> 00:01:28,274
We will run it over there as well,

20
00:01:28,274 --> 00:01:31,537
but we will run a separate
area - 45 - over there,

21
00:01:31,615 --> 00:01:36,353
and then that way when we do some
redistribution and this sort of

22
00:01:36,353 --> 00:01:41,561
thing we'll get the chance to see
all of the LSA types when we get

23
00:01:41,561 --> 00:01:44,193
to looking at the database.

24
00:01:44,570 --> 00:01:47,784
So let's jump in and get our Area 0 set up.

25
00:01:48,160 --> 00:01:51,527
And we will be bringing all
of these devices' loopbacks

26
00:01:51,527 --> 00:01:54,592
into OSPF as well as we go.

27
00:01:54,592 --> 00:02:00,201
Now, very similar to what we
talked about in our EIGRP lesson,

28
00:02:00,279 --> 00:02:06,222
OSPF version 3 - which is
what you need for IPv6 -

29
00:02:06,374 --> 00:02:09,120
can be configured two different ways.

30
00:02:09,165 --> 00:02:14,119
There's, again, the
legacy IPv6 router OSPF.

31
00:02:14,233 --> 00:02:17,057
This cannot use a VRF.

32
00:02:17,057 --> 00:02:19,315
I'll show you this syntax in a minute.

33
00:02:19,315 --> 00:02:25,595
Then you have the newer syntax,
which is router OSPFv3 X,

34
00:02:25,595 --> 00:02:30,793
where, of course, in this case, X is
the process number in both of these.

35
00:02:31,118 --> 00:02:35,430
This is the newer method and supports VRFs.

36
00:02:35,522 --> 00:02:40,981
Just like EIGRP and its two
methods of being configured,

37
00:02:40,981 --> 00:02:46,782
OSPF, we have this same situation
with the whole VRF support

38
00:02:46,782 --> 00:02:48,695
and where things are headed.

39
00:02:48,695 --> 00:02:55,324
Things are headed towards router
OSPFv3 and away from the IPv6 router.

40
00:02:55,489 --> 00:03:02,003
So, again, most of the OSPFv3
syntax we need for when we get

41
00:03:02,003 --> 00:03:08,182
to MPLS support, but, nonetheless,
we will take a look at it.

42
00:03:08,182 --> 00:03:11,741
And just like I did EIGRP,
we'll do a mix and match

43
00:03:11,741 --> 00:03:14,951
on some of the routers which ones we run.

44
00:03:16,587 --> 00:03:22,627
The other nice thing too is if you
use the router OSPFv3 command

45
00:03:22,627 --> 00:03:31,054
you can actually run, and exchange
rather, IPv4 routes over OSPF version 3.

46
00:03:31,247 --> 00:03:35,243
With Legacy mode you would have, once more,

47
00:03:35,243 --> 00:03:42,419
IPv6 router OSPF 1, and then you
would have router OSPF 1 to run

48
00:03:42,419 --> 00:03:48,138
OSPF version 2 to support IPv4
just like we've always done.

49
00:03:48,390 --> 00:03:53,275
Problem is, that means you have
all of this information twice.

50
00:03:53,275 --> 00:03:59,908
You're essentially running two
completely separate OSPF protocols.

51
00:04:00,271 --> 00:04:02,955
The nice thing here - and I'm not
saying anybody's going to just

52
00:04:02,955 --> 00:04:08,248
jump right in this and start doing
it tomorrow - but the nice thing is,

53
00:04:08,248 --> 00:04:18,071
with OSPFv3 syntax that we can actually
support IPv4 address family over IPv6.

54
00:04:18,265 --> 00:04:20,935
So as we get our environments ready

55
00:04:20,935 --> 00:04:25,334
and we start moving towards IPv6
and we fire up OSPF version 3,

56
00:04:25,640 --> 00:04:29,319
it's just nice that we could - not
saying that we're going to right away,

57
00:04:29,319 --> 00:04:35,686
but as things progress - we can
actually get rid of OSPF version 2

58
00:04:35,686 --> 00:04:43,274
before we even turn off IPv4, and we
can support IPv4 over OSPF version 3.

59
00:04:43,274 --> 00:04:48,456
However, OSPF version 3
does still run over IPv6.

60
00:04:48,763 --> 00:04:54,003
If you try to type "router
OSPFv3 1" on a router,

61
00:04:54,256 --> 00:04:58,313
it will yell at you that you don't
have IPv6 Unicast routing enabled.

62
00:04:58,496 --> 00:05:01,731
So you can't run it over IPv4 only.

63
00:05:02,149 --> 00:05:04,947
So let's jump over to the command line,

64
00:05:05,198 --> 00:05:11,286
and let's take a look at
actually configuring this.

65
00:05:11,538 --> 00:05:17,603
So on Router 1, again, we'll stick with
the Legacy mode to start with here.

66
00:05:17,872 --> 00:05:22,239
So on Router 1 we will
say interface tunnel 0,

67
00:05:22,239 --> 00:05:24,067
because that says DMVPN.

68
00:05:24,321 --> 00:05:36,293
We will say, IPv6 OSPF 1 Area 0.

69
00:05:37,191 --> 00:05:41,368
Now, right away we have a little bit
of a danger to worry about here.

70
00:05:41,515 --> 00:05:44,744
Let's do interface-- well, let's
not go into the interface yet.

71
00:05:44,744 --> 00:05:50,033
Let's say, do show IPv6
OSPF interface brief.

72
00:05:50,616 --> 00:05:56,904
So there it is. And the
problem we have is the state.

73
00:05:58,440 --> 00:06:05,855
The state is point-to-point,
which is going to be a problem.

74
00:06:06,395 --> 00:06:08,100
Let me just show you here.

75
00:06:08,100 --> 00:06:13,226
If we go to interface loopback0
and turn it into area 0--

76
00:06:13,226 --> 00:06:17,343
I'm just going to fire up OSPF on the
interfaces here on Routers 1, 2 and 3.

77
00:06:17,898 --> 00:06:21,269
Just the routers connected
to the DMVPN cloud for now.

78
00:06:21,876 --> 00:06:25,231
So, interface, tunnel 0, remember
that Router 1 is the hub.

79
00:06:26,243 --> 00:06:41,057
Interface tunnel 0, IPv6 OSPF 1 area
0, interface loopback0, and Router 3.

80
00:06:52,155 --> 00:06:57,681
And I want you to note that the
tunnel process just came up with

81
00:06:57,681 --> 00:07:01,827
neighbor 1.1.1.1. And if
you look at Router 2,

82
00:07:02,287 --> 00:07:06,613
he says the same thing, so
neighbor 1.1.1.1 is up.

83
00:07:06,902 --> 00:07:11,863
If you look at Routers 2 and 3,
everything looks just wonderful,

84
00:07:11,982 --> 00:07:17,086
but if you go to Router 1, process is full,

85
00:07:17,086 --> 00:07:20,283
loading done, process
is full, loading done.

86
00:07:20,283 --> 00:07:22,730
Wonderful. It's all great.

87
00:07:23,530 --> 00:07:25,642
Let's take a look at the routes.

88
00:07:26,572 --> 00:07:28,592
Let's go to Router 2.

89
00:07:35,243 --> 00:07:39,132
All he knows about is Router 1's loopback.

90
00:07:39,985 --> 00:07:44,888
He doesn't know anything about Router 3.

91
00:07:46,547 --> 00:07:49,317
And this is just a fundamental problem.

92
00:07:49,317 --> 00:07:56,201
If I said do show IPv6
OSPF database router--

93
00:07:56,201 --> 00:08:02,042
we're going to get to all the changes
to the database and such in a minute.

94
00:08:03,659 --> 00:08:15,544
But, see, here's an LSA from Router
3. Link connected to another

95
00:08:15,544 --> 00:08:18,694
router point-to-point. That's all good,

96
00:08:18,694 --> 00:08:25,183
but just to let you know, when you
see things that say, "LSA ignored,"

97
00:08:25,585 --> 00:08:27,933
that's really not a good thing.

98
00:08:28,230 --> 00:08:35,391
The problem is, of course, we have a
complete logic problem here with OSPF.

99
00:08:35,711 --> 00:08:45,489
Router 1 right now sees two neighbors
on a point-to-point interface,

100
00:08:45,804 --> 00:08:49,092
and that's not allowed, that's not allowed.

101
00:08:49,272 --> 00:08:52,581
If we were running OSPF version 2, in fact,

102
00:08:52,581 --> 00:08:56,354
these neighbors would actually flap
back and forth between each other.

103
00:08:56,898 --> 00:09:02,442
OSPF version 3 allows the neighbors
to stay up, but it's still

104
00:09:02,442 --> 00:09:07,134
a logic problem in the database, and these
guys just don't know how to use it.

105
00:09:13,146 --> 00:09:16,766
Router 1 just happened
to get Router 2's first,

106
00:09:17,012 --> 00:09:20,649
so he's only believing
Router 2's interface.

107
00:09:20,649 --> 00:09:23,573
He's not learning anything from Router 3.

108
00:09:24,227 --> 00:09:35,886
Router 3 learns nothing.

109
00:09:42,608 --> 00:09:46,148
The problem is-- there you go, now
you can see it's actually flapping.

110
00:09:46,148 --> 00:09:51,039
We're actually not getting
[console?] messages on this one,

111
00:09:51,218 --> 00:09:53,092
but it's flapping them anyway.

112
00:09:53,092 --> 00:09:55,490
Let's see what Router 1
is saying right now.

113
00:10:01,585 --> 00:10:07,084
He says he's full with both
of them, but we know better.

114
00:10:07,551 --> 00:10:10,071
So, again, I'm not going to spend
a whole lot of time on this,

115
00:10:10,071 --> 00:10:14,208
this is just, of course,
a misconfiguration.

116
00:10:14,419 --> 00:10:18,368
If you're going to run-- and I'm
just trying to point out that OSPF

117
00:10:18,368 --> 00:10:24,789
version 3 is just like version
2 in almost every respect.

118
00:10:24,789 --> 00:10:30,863
Obviously it runs over IPv6, there's
been some fundamental changes

119
00:10:30,863 --> 00:10:35,092
to the database we need to look at,
but other than that, things like

120
00:10:35,092 --> 00:10:38,467
network types, areas
types, all of that stuff,

121
00:10:38,467 --> 00:10:44,495
they all stay the same. So we just
really have to say, interface tunnel 0.

122
00:10:44,743 --> 00:10:49,465
Now, this is going to also get
into a whole discussion of DMVPN,

123
00:10:49,465 --> 00:10:54,083
and do we want to be running
phase 1, phase 2, phase 3?

124
00:10:54,864 --> 00:11:00,319
We're just going to go with phase
2 today, because I just want the

125
00:11:00,319 --> 00:11:04,185
routes to get through, this
is not a DMVPN discussion.

126
00:11:05,199 --> 00:11:10,181
What that means is that we run OSPF
network type point-to-multipoint.

127
00:11:10,181 --> 00:11:17,989
So, IPv6 OSPF network point-to-multipoint.

128
00:11:20,416 --> 00:11:23,027
This will be enough to
get everything working.

129
00:11:23,499 --> 00:11:29,171
And again, if this was a
full blown OSPF discussion,

130
00:11:30,210 --> 00:11:36,072
we could talk about combining
point-to-multipoint with point-to-point.

131
00:11:36,239 --> 00:11:37,586
You can do that.

132
00:11:37,586 --> 00:11:39,384
You have to tweak the timers, of course,

133
00:11:39,384 --> 00:11:47,770
because if I said do show
IPv6 OSPF interface tunnel 0,

134
00:11:49,413 --> 00:11:55,131
it is now point-to-multipoint and
changes our timers to 30 and 120.

135
00:11:55,131 --> 00:12:00,253
Again, they didn't go radically
changing how OSPF works here.

136
00:12:00,579 --> 00:12:03,479
And of course, Router 2.

137
00:12:07,710 --> 00:12:13,931
If we leave it at point-to-point,
timers are 10 and 40.

138
00:12:14,607 --> 00:12:18,514
So what if I said, IPv6 OSPF--

139
00:12:26,873 --> 00:12:30,059
okay, that's not what I wanted at all.

140
00:12:34,939 --> 00:12:41,203
Dead interval. Seconds? About one.

141
00:12:50,647 --> 00:12:52,592
Don't know what I hit up on that.

142
00:12:58,808 --> 00:13:06,196
Hello interval 1. Got
a little problem there.

143
00:13:07,714 --> 00:13:09,340
So that's not going to be good.

144
00:13:10,267 --> 00:13:12,443
This does not support minimum.

145
00:13:12,638 --> 00:13:17,040
There are a couple little features
here and there that we don't just

146
00:13:17,040 --> 00:13:21,223
have yet, but it's okay, because
hopefully you're doing BFD anyway,

147
00:13:21,223 --> 00:13:22,516
so it doesn't really make any difference.

148
00:13:22,516 --> 00:13:27,184
But we'll set out dead interval back
to 4. We'll do 1 and 4.

149
00:13:39,863 --> 00:13:42,034
[?] trying to sneak in there.

150
00:13:57,235 --> 00:14:06,578
And I just configured them in a
loopback... I think... on Router 2.

151
00:14:08,601 --> 00:14:10,804
If anybody is familiar with the
Nexus I would really love the

152
00:14:10,804 --> 00:14:12,619
where command right now.

153
00:14:17,885 --> 00:14:19,776
Yep. Put another loopback.

154
00:14:35,821 --> 00:14:38,296
And I just typed the wrong
command in there too.

155
00:14:38,485 --> 00:14:39,672
Awesome.

156
00:14:43,704 --> 00:14:46,063
Thank goodness for copy and paste.

157
00:14:54,095 --> 00:14:56,538
It didn't take the dead interval anyway.

158
00:15:09,336 --> 00:15:12,407
Because it will default to
four times as much anyway.

159
00:15:19,995 --> 00:15:22,040
So 1 and 4 becomes the default.

160
00:15:22,040 --> 00:15:35,366
That's fine. And then Router
3, and that should come up.

161
00:15:35,878 --> 00:15:40,630
Again, you can combine point-to-point
and point-to-multipoint.

162
00:15:40,630 --> 00:15:44,083
That's not a problem, as long
as you set the timers right.

163
00:15:47,982 --> 00:15:49,725
Now we should have the routes.

164
00:15:49,856 --> 00:15:53,262
So, there's Router 1's
loopback, Router 2's loopback.

165
00:16:06,816 --> 00:16:10,280
There's Router 3's loopback,
Router 1's loopback - good.

166
00:16:10,419 --> 00:16:15,476
So that takes care of OSPF
over the DMVPN cloud,

167
00:16:15,609 --> 00:16:18,471
just running a combination
of point-to-multipoint,

168
00:16:18,570 --> 00:16:28,974
point-to-point, and of course,
sticking with Legacy config mode,

169
00:16:29,132 --> 00:16:31,025
and setting our timers.

170
00:16:31,338 --> 00:16:46,600
On Router 2, let's also say,
interface FA0/0 IPv6 OSPF 1 Area 0.

171
00:16:47,931 --> 00:16:53,660
Router 3 is interface FA0/0.344.

172
00:16:56,785 --> 00:17:02,116
And then just to show you the new
syntax, we'll go to Router 4.

173
00:17:03,132 --> 00:17:05,044
And this one gets a little bit different.

174
00:17:05,044 --> 00:17:18,933
So interface FA0/0.24 is OSPFv3, and then
you have to tell it the process ID, so 1.

175
00:17:19,093 --> 00:17:27,479
Then the actual protocol,
IPv6, and then Area 0.

176
00:17:30,101 --> 00:17:39,668
That comes up with Router 2, and then
interface FA0/0.344, same command.

177
00:17:42,025 --> 00:17:45,650
So that syntax, a little
bit different there.

178
00:17:46,809 --> 00:17:53,254
And again, we'll mostly see this as
we move into MPLS in that section.

179
00:17:53,627 --> 00:17:55,964
But that's just another
way to configure it.

180
00:17:56,271 --> 00:18:01,673
And then interface serial
0/0/0. Same co80000
 And that just turned router
 four into an ABR.

0:18:06.680000 --> 0:18:11.640000
 And then over on router five, we'll
 just do legacy mode over here again.

0:18:11.640000 --> 0:18:13.960000
 Interface, zero zero zero zero.

0:18:13.960000 --> 0:18:19.240000
 IPv6 OSPF one area forty five.

0:18:19.240000 --> 0:18:21.600000
 Interface loop back zero.

0:18:21.600000 --> 0:18:24.480000
 In area forty five.

0:18:24.480000 --> 0:18:26.440000
 We've done everything correctly.

0:18:26.440000 --> 0:18:28.540000
 Let's just go over to
 room four to one.

0:18:28.540000 --> 0:18:31.300000
 We'll just look the whole
 way furthest away.

0:18:31.300000 --> 0:18:35.900000
 Do show IPv6 route OSPF.

0:18:35.900000 --> 0:18:39.280000
 And we should have
 some O's and OIA's.

0:18:39.280000 --> 0:18:46.060000
 There we go. There's the forty five
 link between routers four and five.

0:18:46.060000 --> 0:18:47.980000
 Router five's loop back.

0:18:47.980000 --> 0:18:51.680000
 Of course, it's doing some unequal cost
 load sharing or sorry, equal cost

0:18:51.680000 --> 0:18:57.500000
 load sharing between routers two and
 three out of the DM VPN cloud.

0:18:57.500000 --> 0:18:59.360000
 And that's no problem.

0:18:59.360000 --> 0:19:04.880000
 So just as far as basic OSPF
 setup goes, that's it.

0:19:04.880000 --> 0:19:10.640000
 There's not. And again, on and on with
 all the OSPF config, pretty much

0:19:10.640000 --> 0:19:15.160000
 you got to get used to the new
 syntax with router OSPF v3.

0:19:15.160000 --> 0:19:19.780000
 And again, we'll see more of that as
 we get into redistribution and MPLS

0:19:19.780000 --> 0:19:22.600000
 and things like that.

0:19:22.600000 --> 0:19:26.280000
 But OSPF at the end of
 the day is still OSPF.

0:19:26.280000 --> 0:19:27.880000
 Area types are the same.

0:19:27.880000 --> 0:19:31.700000
 Network types are the same.

0:19:31.700000 --> 0:19:34.220000
 It's really just changes
 in the database.

0:19:34.220000 --> 0:19:37.560000
 And we will hit those
 in the next lesson.

