﻿1
00:00:01,916 --> 00:00:08,427
[music]

2
00:00:08,428 --> 00:00:15,467
Okay, in this section we're going to
be looking at using EIGRP for IPv6.

3
00:00:15,467 --> 00:00:23,250
Just like regular EIGRP this is fairly
simple, fairly straightforward.

4
00:00:23,251 --> 00:00:28,819
We do have two different ways we have
to look at configuring this though,

5
00:00:28,820 --> 00:00:34,234
so I'll sort of do a mix-and-match
on the routers as we go,

6
00:00:34,235 --> 00:00:36,765
to see the two different ways to configure it.

7
00:00:36,766 --> 00:00:42,955
We'll be, as always, sticking
with our base topology for now.

8
00:00:42,956 --> 00:00:51,678
We're going to be running EIGRP between
routers 3 and 6 and 5 and switch 4,

9
00:00:51,679 --> 00:00:55,559
just to give us a little area
there to run EIGRP to do a

10
00:00:55,560 --> 00:00:57,113
little bit of messing around.

11
00:00:57,114 --> 00:01:03,451
The other thing to note here is
I do have two segments here,

12
00:01:03,452 --> 00:01:10,339
VLAN 456 and VLAN 344, that are
running link local only addresses,

13
00:01:10,340 --> 00:01:12,830
indicated by those little dots there.

14
00:01:12,831 --> 00:01:15,774
I know it's a little hard to see,
but there's little dots there on

15
00:01:15,775 --> 00:01:19,865
the interfaces that indicate
that they are link local only.

16
00:01:19,866 --> 00:01:25,390
And I did this just to show that for the
routing protocols, it doesn't matter.

17
00:01:25,391 --> 00:01:29,561
You can run completely link local
addressing, because all the neighborship

18
00:01:29,562 --> 00:01:34,465
is done on link local addressing
as well as all the routes use link

19
00:01:34,466 --> 00:01:37,297
local addresses for their next-hop.

20
00:01:37,297 --> 00:01:42,167
So the basic way this works is we're
just going to be adding a new

21
00:01:42,168 --> 00:01:44,728
address family to EIGRP.

22
00:01:44,729 --> 00:01:51,283
It can be run in either legacy
or named configuration.

23
00:01:51,284 --> 00:01:56,321
Legacy or traditional,
whatever you want to call it.

24
00:01:56,322 --> 00:02:03,616
If we're going to run it in a VRF-- and we
will see this when we get to our MPLS lesson.

25
00:02:03,617 --> 00:02:07,542
I'm not going to get into a VRF
in this particular lesson,

26
00:02:07,543 --> 00:02:12,013
but I will show you the syntax
as to where you would do that.

27
00:02:12,014 --> 00:02:15,746
But we're not going to actually
set up a VRF right now.

28
00:02:15,747 --> 00:02:20,869
We're just going to do regular EIGRP to begin
with, but you do have to use named mode.

29
00:02:22,493 --> 00:02:27,848
And you'll see also when we do legacy mode
that this is going to cause the creation

30
00:02:27,849 --> 00:02:32,687
of the global process-- sorry, not
cause it, actually require it.

31
00:02:32,688 --> 00:02:37,854
We're going to have to do that, and
on some code you actually have

32
00:02:37,855 --> 00:02:40,890
to do a no shut under that global process.

33
00:02:40,891 --> 00:02:48,268
On this particular code we don't have
to, but nonetheless some code you do.

34
00:02:48,268 --> 00:02:55,294
And if you do named mode, you get this
automatically on all the IPv6 interfaces.

35
00:02:55,295 --> 00:02:58,875
And, again, these are just some
little notes I wanted to put on here.

36
00:02:58,876 --> 00:03:03,561
Of course, we're going to jump to the
command line and look at all of this.

37
00:03:03,562 --> 00:03:11,048
So let's switch over here - and
I think I'm on switch 4 from

38
00:03:11,049 --> 00:03:16,309
the other day, so we'll just
switch over here to router 3.

39
00:03:16,310 --> 00:03:24,243
We'll just start here. And on router 3 we
will start with just doing legacy mode here.

40
00:03:24,244 --> 00:03:39,595
So, on router 3 we will say
interface fa0/0.36, ipv6 eigrp 100.

41
00:03:39,596 --> 00:03:42,535
That's really all there is to it.

42
00:03:42,536 --> 00:03:45,084
You have to create the global process.

43
00:03:45,085 --> 00:03:50,589
If I said do show ipv6 eigrp interfaces,

44
00:03:55,325 --> 00:03:59,004
we'll find out that it's actually
not running anywhere yet.

45
00:03:59,005 --> 00:04:12,037
All we have to do is say ipv6 router eigrp
100, and now it's running on the interface.

46
00:04:14,556 --> 00:04:19,087
If you look back at our RIP lesson,
you'll realize all we literally

47
00:04:19,088 --> 00:04:24,508
did was turn on RIP under the
interfaces. Now, is there a IPv6

48
00:04:24,509 --> 00:04:28,336
router RIP, you know, RIPv3,
whatever you named the process?

49
00:04:28,337 --> 00:04:31,831
We didn't really go in there because
there's not a whole lot to configure

50
00:04:31,832 --> 00:04:34,183
until we get into redistribution.

51
00:04:34,184 --> 00:04:38,827
If you want it to [weight?] timers and things
like that, of course they're in there.

52
00:04:38,827 --> 00:04:41,348
That's the same thing here with EIGRP.

53
00:04:41,349 --> 00:04:43,473
If you take a look at what's actually here,

54
00:04:43,474 --> 00:04:48,050
these are just things that are going
to affect the overall EIGRP process.

55
00:04:48,051 --> 00:04:52,584
Again, it's very, very similar to IPv4.

56
00:04:52,585 --> 00:04:55,101
There's really not much difference here.

57
00:04:55,102 --> 00:05:00,284
We'll get to some of these things as we go
into redistribution and stuff like that.

58
00:05:00,285 --> 00:05:04,049
But this is where you would go if you
wanted to do a passive interface,

59
00:05:04,050 --> 00:05:08,212
control or distribute list [to?]
actually filter the routes.

60
00:05:08,213 --> 00:05:13,303
These are all the same commands
that you would use for traditional

61
00:05:13,304 --> 00:05:18,151
IPv4 route filtering and route
manipulation and so on.

62
00:05:18,152 --> 00:05:20,779
There's really not much difference here at all.

63
00:05:20,780 --> 00:05:24,737
So let's hop over to router 6.

64
00:05:24,738 --> 00:05:31,495
Just to show you, I'll use router 6 in named mode.

65
00:05:31,496 --> 00:05:35,938
Named mode with EIGRP is sort of a newer format.

66
00:05:35,939 --> 00:05:41,734
This is where they're headed with it,
and you're going to say here, router

67
00:05:41,735 --> 00:05:45,126
EIGRP and then give it a name.

68
00:05:45,127 --> 00:05:48,444
We'll call it IPv6.

69
00:05:48,445 --> 00:05:50,659
It doesn't really matter what we call it.

70
00:05:50,660 --> 00:05:54,469
It's a named process. Then you just hit Enter.

71
00:05:54,470 --> 00:06:00,032
This drops you into EIGRP
named configuration mode.

72
00:06:00,033 --> 00:06:06,039
From here, if you're new to named mode,
there's not much you're going to do.

73
00:06:06,040 --> 00:06:09,143
As you can see here, we can
go into an address-family,

74
00:06:09,143 --> 00:06:14,211
set a command to the default of course,
exit the structure, negate something -

75
00:06:14,212 --> 00:06:16,417
so take out something.

76
00:06:16,418 --> 00:06:18,586
You can enter a service family.

77
00:06:18,587 --> 00:06:21,967
We're not going to get into those
in this course, but that's another

78
00:06:21,968 --> 00:06:23,266
option that's available there.

79
00:06:23,267 --> 00:06:25,753
And of course, you can shut down the whole process.

80
00:06:25,754 --> 00:06:29,856
As you can see, there's really
only one choice we're going to do

81
00:06:29,857 --> 00:06:31,782
at this point, which is address-family.

82
00:06:31,783 --> 00:06:37,296
Now we can support either IPv4 or IPv6 from here.

83
00:06:37,297 --> 00:06:42,630
A couple things that are nice, all
your EIGRP configuration mode

84
00:06:42,631 --> 00:06:45,516
now moves here in named mode.

85
00:06:45,517 --> 00:06:52,064
It's under router config
mode for both IPv4 and IPv6.

86
00:06:52,065 --> 00:06:59,841
You're not typing router eigrp 100
ipv6 router eigrp 100 and having

87
00:06:59,842 --> 00:07:02,595
two separate configuration sections.

88
00:07:02,596 --> 00:07:05,564
It's really all just right here under named mode.

89
00:07:05,565 --> 00:07:08,734
Now, of course, what we want to say
for right now, since we're not

90
00:07:08,735 --> 00:07:15,023
here for IPv4 is, we want to type
ipv6, and then you have no choice

91
00:07:15,024 --> 00:07:17,179
but to say an AS number.

92
00:07:17,180 --> 00:07:20,265
Notice like hitting carriage return, not an option.

93
00:07:20,266 --> 00:07:23,772
This is where, if we were running a VRF,

94
00:07:23,773 --> 00:07:29,847
and we would call it CUSTOMERS
or something like that,

95
00:07:29,848 --> 00:07:32,242
we could then put the AS number.

96
00:07:32,243 --> 00:07:41,597
This would fire up IPv6 inside the VRF
CUSTOMERS and assign it an AS number.

97
00:07:41,598 --> 00:07:43,675
If you're not real familiar with VRFs,

98
00:07:43,675 --> 00:07:54,542
these are used mostly in regard to MPLS, but
certainly for lots of other features as well.

99
00:07:54,543 --> 00:07:59,249
The basic idea is creating multiple
routing tables on a router and

100
00:07:59,250 --> 00:08:04,114
therefore separating routing
tables and therefore traffic.

101
00:08:05,556 --> 00:08:08,570
Look at it as a form of virtualizing the router.

102
00:08:08,571 --> 00:08:11,102
It's what it's called, virtual
router and forwarder.

103
00:08:12,597 --> 00:08:14,027
We'll get to those.

104
00:08:14,028 --> 00:08:19,739
We'll do it, of course, in the
context of MPLS when we look at IPv6

105
00:08:19,740 --> 00:08:23,076
over MPLS later in the course.

106
00:08:23,077 --> 00:08:29,725
So, address-family ipv6-- this is
just sort of a little syntax thing

107
00:08:29,726 --> 00:08:32,422
that I think's a little bit interesting.

108
00:08:32,423 --> 00:08:39,836
If you look at the command here, the next
thing would be AU for Autonomous System,

109
00:08:39,836 --> 00:08:42,317
and then we say AS 100.

110
00:08:42,318 --> 00:08:48,722
That's fine. But, what if I said,
since everybody calls it this,

111
00:08:48,723 --> 00:08:54,496
AS, and I hit ?, it says unrecognized command.

112
00:08:54,497 --> 00:08:56,994
Now again this kind of little detail here,

113
00:08:56,995 --> 00:09:02,379
just so you understand, this kind of
little thing can vary code to code.

114
00:09:02,380 --> 00:09:05,462
This is just sort of an interesting
behavior on this code.

115
00:09:05,463 --> 00:09:09,095
Whatever code you're on may
not act exactly like this,

116
00:09:09,096 --> 00:09:14,078
but the interesting thing is we say
AS 100 and it takes it anyway.

117
00:09:14,079 --> 00:09:20,164
And my guess is they probably did a lot
of testing as they were developing this,

118
00:09:20,165 --> 00:09:24,131
then kept typing AS 100 by mistake
or something and realized,

119
00:09:24,132 --> 00:09:28,560
we probably better just make that work
because people are going to do it.

120
00:09:28,561 --> 00:09:32,262
And the funny thing is, is I
think I was doing it for quite

121
00:09:32,263 --> 00:09:39,455
some time before I realized, you know, that's
actually not the shortening of that command.

122
00:09:39,456 --> 00:09:47,065
It should be AU and then maybe tab it
out or just go from there - not AS.

123
00:09:47,066 --> 00:09:50,871
But it takes it anyway, which sort
of is a nice thing, since that's

124
00:09:50,872 --> 00:09:53,944
what I was in the habit of
typing and was doing it anyway.

125
00:09:53,945 --> 00:09:57,437
Okay, now, the next part with named mode,

126
00:09:57,438 --> 00:10:02,124
once you're in the address-family and
the AS number you want to be in.

127
00:10:02,125 --> 00:10:03,601
Couple things to note.

128
00:10:03,602 --> 00:10:09,158
First, if you look at our command prompt
there, EIGRP has already come up.

129
00:10:09,159 --> 00:10:12,500
There it is. We already have a
neighborship with router 3,

130
00:10:12,501 --> 00:10:21,754
and if I were to say, do show ipv6 interface--
and it did not want just interfaces,

131
00:10:23,770 --> 00:10:29,158
eigrp interfaces, a little more detail
than we needed on that other one.

132
00:10:29,159 --> 00:10:37,686
But you can see here, we are automatically
running EIGRP on all of our interfaces.

133
00:10:40,013 --> 00:10:43,965
In this particular case, on router 6,

134
00:10:43,966 --> 00:10:51,986
we didn't want to be running EIGRP
on his gigabit 0/1 interface.

135
00:10:51,987 --> 00:11:00,394
So what we need to do from here is take
a look at the subconfiguration modes.

136
00:11:00,395 --> 00:11:05,094
Again, I'm not going to go over shut no default,

137
00:11:05,095 --> 00:11:08,149
every time we go into something, or of course help.

138
00:11:08,150 --> 00:11:12,417
Exit address-family, also I
hope, fairly obvious here.

139
00:11:12,418 --> 00:11:18,771
But there are a few commands, eigrp for example,

140
00:11:20,025 --> 00:11:22,983
and in here you can say that it's a stub,

141
00:11:22,984 --> 00:11:28,414
you can set its router ID
for external eigrp routes.

142
00:11:30,620 --> 00:11:36,090
You can also, back here, set up the metric.

143
00:11:37,420 --> 00:11:44,627
So, metric weights, of course,
is to set the K values,

144
00:11:44,628 --> 00:11:49,267
which, generally speaking, we
shouldn't really have to mess with in

145
00:11:49,268 --> 00:11:55,686
EIGRP, unless you wanted to bring in
reliability or load into the value,

146
00:11:55,687 --> 00:12:02,219
and/or change the weighting
factor of bandwidth versus delay.

147
00:12:02,220 --> 00:12:08,580
Now, the other thing you might need to do is,

148
00:12:08,580 --> 00:12:13,981
if I back out of here-- and I don't think
we're going to have any routes just yet.

149
00:12:13,982 --> 00:12:18,654
Do show ipv6 eigrp topology.

150
00:12:20,342 --> 00:12:26,509
All we have right now is the stuff that
we are locally putting into the database,

151
00:12:26,510 --> 00:12:30,177
but what we can do-- and
we're not going to leave it

152
00:12:30,178 --> 00:12:32,723
this way but that's okay, at least for now.

153
00:12:32,724 --> 00:12:37,453
We can do-- you know what, let's go to router 5.

154
00:12:37,454 --> 00:12:41,680
Let's bring up router 5 awhile and
we'll do named mode on him as well.

155
00:12:41,681 --> 00:12:45,331
I'm actually starting to lean
more and more and more towards

156
00:12:45,332 --> 00:12:48,929
just doing named mode constantly,
but we do still of course need to

157
00:12:48,930 --> 00:12:51,186
look at the legacy as well.

158
00:12:51,187 --> 00:12:58,230
So router eigrp, and it doesn't
matter what you call it,

159
00:12:58,231 --> 00:13:01,727
we can call this one eigrp. I'm not going to.

160
00:13:01,728 --> 00:13:03,628
It is a local name.

161
00:13:03,629 --> 00:13:08,268
However, as we get into configuring
and moving back and forth between

162
00:13:08,269 --> 00:13:13,132
devices, it just gets, of course, very confusing
to remember what you named it everywhere.

163
00:13:13,133 --> 00:13:21,305
So I will call this one IPv6 as
well. Address-family ipv6 unicast

164
00:13:21,305 --> 00:13:33,315
for AS 100. And their neighbor with 456 comes
up, which means, do show ipv6 eigrp topology.

165
00:13:33,315 --> 00:13:37,393
We should now have some routes from the other side.

166
00:13:37,394 --> 00:13:41,453
The main reason I'm bringing this
in here to show you is I want to

167
00:13:41,454 --> 00:13:49,410
show you these metrics, because
if you say do show ipv6 protocol,

168
00:13:49,411 --> 00:13:58,688
what you're going to find - two things -
is the RIB scale and the metric version.

169
00:13:58,689 --> 00:14:01,780
The metric version defaults to 64-bit.

170
00:14:01,781 --> 00:14:05,800
These are what we refer to as EIGRP wide metrics.

171
00:14:05,800 --> 00:14:10,323
This is being done, of course, to
compensate for newer, faster links

172
00:14:10,324 --> 00:14:16,179
that are coming out, so we're
moving towards a wide metric.

173
00:14:16,180 --> 00:14:18,761
By the way, it's just a little side note here.

174
00:14:18,762 --> 00:14:23,084
With the wide metric, if you're in
that habit like so many people are,

175
00:14:23,085 --> 00:14:29,825
of, when you redistribute into
EIGRP, just saying metric 1 1 1 1 1,

176
00:14:29,826 --> 00:14:34,480
don't do that anymore, because with
wide metrics you've got to remember,

177
00:14:34,481 --> 00:14:38,802
that first number you put in is
bandwidth in kilobits per second.

178
00:14:38,803 --> 00:14:42,687
When you type 1, you're telling it
that it's 1 kilobit per second,

179
00:14:42,688 --> 00:14:46,662
which is like, I don't know, the
worst possible route imaginable.

180
00:14:48,281 --> 00:14:54,990
For wide metrics it'll actually say,
I forget the exact terminology,

181
00:14:54,991 --> 00:14:56,651
maybe we'll do it here later.

182
00:14:56,652 --> 00:15:03,110
It says something like the feasible
distance is infinity or maximum

183
00:15:03,110 --> 00:15:05,568
or something along those lines.
I think it says infinity.

184
00:15:05,569 --> 00:15:09,174
But the fact of the matter
is, it won't use the route,

185
00:15:09,175 --> 00:15:13,304
so you can't just do the 1
1 1 1 1 like you used to.

186
00:15:13,305 --> 00:15:18,719
But the main thing I want to show
you here is what the rib-scale

187
00:15:18,720 --> 00:15:20,986
and the metric version are for.

188
00:15:20,987 --> 00:15:23,972
There's not too much else that's changed.

189
00:15:23,973 --> 00:15:31,148
We pick up a K6 value. I'm not going to get
into, here, all the detail on what that's for.

190
00:15:31,149 --> 00:15:36,362
In this version of code it's not
being used, the K6 just stays at 0.

191
00:15:36,363 --> 00:15:42,614
It has to do with compatibility
and feature exchange.

192
00:15:42,615 --> 00:15:47,976
But in this case I do want to show
you these other things though.

193
00:15:47,977 --> 00:15:53,659
The rib-scale, what this is for is, 64-bit
metrics don't fit in the routing table,

194
00:15:53,660 --> 00:15:57,562
so if I said do show ipv6 route,

195
00:16:01,997 --> 00:16:06,157
and look at these metrics -
these are all connected.

196
00:16:06,158 --> 00:16:10,526
We'll pick on 36. We'll just pick on VLAN 36 here.

197
00:16:12,272 --> 00:16:19,163
If we look at the one up
here in our topology for 36,

198
00:16:19,164 --> 00:16:27,658
notice the value versus our routing table.

199
00:16:29,615 --> 00:16:39,599
The way this works is we simply take this
number and we divide by the rib-scale, 128.

200
00:16:39,600 --> 00:16:48,532
If you were to take 19660800,
divide by 128, you get this number.

201
00:16:48,533 --> 00:16:51,590
That's what it puts in the routing table.

202
00:16:51,591 --> 00:16:59,341
Again, this is done simply because 64-bit
metrics do not fit in the routing table.

203
00:16:59,342 --> 00:17:05,156
If you're going to stick with 64-bit metrics,
which would be the recommendation, of course,

204
00:17:05,157 --> 00:17:09,959
then a lot of people look at this and go,

205
00:17:09,960 --> 00:17:14,873
okay, so you said three minutes ago
that we're going with these to

206
00:17:14,874 --> 00:17:17,907
support the new higher-speed interfaces.

207
00:17:17,908 --> 00:17:24,568
Then we're taking this better-scaled
metric and we're dividing it

208
00:17:24,569 --> 00:17:27,038
by 128 to put it in the routing table, so then

209
00:17:27,039 --> 00:17:31,768
aren't we just losing the
granularity of the larger number?

210
00:17:31,769 --> 00:17:35,103
The answer is yes, you are.

211
00:17:35,104 --> 00:17:36,787
You're losing the granularity.

212
00:17:36,788 --> 00:17:42,340
However, the actual decision on the
best route happens in the EIGRP

213
00:17:42,341 --> 00:17:46,826
topology table when EIGRP chooses its best path.

214
00:17:46,827 --> 00:17:51,515
My point is, I really don't care if it
puts it in the routing table with a 4

215
00:17:51,515 --> 00:17:56,779
or a 100 or just any random number.

216
00:17:56,780 --> 00:18:01,210
It really doesn't matter what's in
the routing table, because once

217
00:18:01,211 --> 00:18:06,971
it's in the routing table from
EIGRP, admin distance, of course,

218
00:18:06,972 --> 00:18:10,028
is going to kick in and determine
is it going to be EIGRP,

219
00:18:10,029 --> 00:18:12,590
is it going to be RIP, is it going to be OSPF,

220
00:18:12,590 --> 00:18:15,134
who's putting the route in the routing table?

221
00:18:15,135 --> 00:18:18,939
But once admin distance has kicked
in and it's been determined that

222
00:18:18,940 --> 00:18:24,496
we're going to be using the EIGRP route,
I really don't care what that metric is.

223
00:18:24,497 --> 00:18:26,500
I mean look at these two.

224
00:18:26,501 --> 00:18:30,312
Here's RIP with a metric of 2.

225
00:18:30,313 --> 00:18:32,654
Again, who cares?

226
00:18:32,655 --> 00:18:39,310
The metric is only used within the routing
protocol for it to choose its best route.

227
00:18:39,311 --> 00:18:43,868
Once that decision's been made, I really
don't care what's in the routing table here.

228
00:18:43,869 --> 00:18:45,695
It really makes no difference.

229
00:18:45,696 --> 00:18:50,809
Right here we have 153600 right next to a 2,

230
00:18:50,810 --> 00:18:54,175
and it doesn't matter because they're
from two different routing protocols,

231
00:18:54,176 --> 00:18:57,676
and since that's the only way
I'm learning them right now,

232
00:18:57,677 --> 00:19:01,290
then that's the one that wins
and goes in the routing table.

233
00:19:01,291 --> 00:19:05,876
This whole metric scale, the rib-scale thing,

234
00:19:05,877 --> 00:19:10,623
it really sometimes freaks people
out a little bit, especially if

235
00:19:10,624 --> 00:19:13,821
you've not actually seen this, because
you're looking at this up here,

236
00:19:13,822 --> 00:19:17,265
looking at the topology table, and
then looking at the routing table

237
00:19:17,266 --> 00:19:20,907
and you're like, okay, where
did that number come from?

238
00:19:20,908 --> 00:19:24,463
The fact of the matter is, it
just scaled it down. That's all.

239
00:19:24,464 --> 00:19:28,699
If for some reason - and I
do not recommend this, but I

240
00:19:28,700 --> 00:19:32,202
like to show it, just completeness,
just so everybody's seen it -

241
00:19:32,203 --> 00:19:42,902
if you needed to, you could
say metric version 32bit.

242
00:19:42,903 --> 00:19:48,690
Then when you say do show ipv6 eigrp topology--

243
00:19:50,628 --> 00:19:52,700
it didn't scale them down yet.

244
00:19:52,701 --> 00:19:54,521
Give it its chance to sync there.

245
00:19:54,522 --> 00:19:56,105
I'm like, those aren't right.

246
00:19:56,106 --> 00:19:59,537
There we go. It will scale these down.

247
00:19:59,538 --> 00:20:06,206
Then you say, do show ipv6 route eigrp.

248
00:20:06,207 --> 00:20:09,519
Then you can see these match up now.

249
00:20:09,520 --> 00:20:15,858
So 36 is 30720, 30720.

250
00:20:15,859 --> 00:20:18,689
That does not mean, by the way,
that they're going to be the same

251
00:20:18,690 --> 00:20:21,147
numbers as they were above, because
a lot of people then look back

252
00:20:21,148 --> 00:20:25,500
at what we did a minute ago and say, wait
a minute, those numbers don't match.

253
00:20:25,501 --> 00:20:31,899
That's because this number before was
a scaled down - divided by 128 -

254
00:20:31,900 --> 00:20:33,866
of the 64-bit metric.

255
00:20:33,867 --> 00:20:36,665
This is flat-out a 32-bit metric.

256
00:20:36,666 --> 00:20:38,955
It's a whole different scale.

257
00:20:38,956 --> 00:20:42,007
It doesn't mean that it's going to
be half the other value because

258
00:20:42,008 --> 00:20:43,613
it's half the number of bits.

259
00:20:43,614 --> 00:20:45,194
It doesn't work like that.

260
00:20:45,195 --> 00:20:51,134
If you wanted to, you could back
this off and go back to using more

261
00:20:51,135 --> 00:20:54,204
traditional methods, so to speak.

262
00:20:54,205 --> 00:21:01,304
Traditional, like if we went up router 3
and said do show ipv6 eigrp topology,

263
00:21:01,305 --> 00:21:04,263
he would be using the old method,

264
00:21:06,399 --> 00:21:11,189
and he would have those older
numbers, see like 30720.

265
00:21:14,406 --> 00:21:18,092
In fact, I don't think you can even--

266
00:21:22,539 --> 00:21:25,675
yeah, see, it doesn't even support changing it.

267
00:21:25,676 --> 00:21:29,323
Remember that router 3 is running legacy mode.

268
00:21:29,324 --> 00:21:34,122
I'm not saying that there wouldn't be code
that does support it, but this code doesn't.

269
00:21:34,123 --> 00:21:37,504
And by the way, in case you're
wondering why I hit question mark,

270
00:21:37,505 --> 00:21:42,006
looked at this, and then went ahead
and tried to type it anyway--

271
00:21:44,050 --> 00:21:48,616
If you go back to where we were changing
it a minute ago on router 5 here,

272
00:21:48,617 --> 00:21:50,593
I'm going to change it back.

273
00:21:50,594 --> 00:21:56,899
If you say metric version, notice that
the metric here looks exactly the same.

274
00:21:56,900 --> 00:22:01,008
It's slightly different numbers.
You've got rib-scale and weights.

275
00:22:01,009 --> 00:22:02,524
Version is not here either,

276
00:22:02,525 --> 00:22:07,318
but if you say version 64bit, it takes it.

277
00:22:07,319 --> 00:22:13,419
Do show ipv6 eigrp topology, let's give
it a second to reset before we do this.

278
00:22:17,513 --> 00:22:23,659
There we go, [soft?] reconfig, hit Enter,
and we're back to the regular numbers.

279
00:22:23,660 --> 00:22:30,107
So it's really not recommended to change it,
that's sort of why Cisco hid that command.

280
00:22:30,108 --> 00:22:32,515
They don't want you changing
it, I would not change it,

281
00:22:32,516 --> 00:22:37,797
but just to show you how the whole rib
factor and the wide metrics work,

282
00:22:37,798 --> 00:22:41,532
there you go. By the way, just as a side note,

283
00:22:41,533 --> 00:22:45,811
it's not really our topic here,
but as a side note, remember that

284
00:22:45,812 --> 00:22:53,025
EIGRP for IPv4 with named mode
does this exact same thing.

285
00:22:53,026 --> 00:22:57,225
Other things you can do from here
is-- there's not really a whole lot.

286
00:22:57,226 --> 00:23:00,020
Like I said, we can adjust some of
the timers and you can put in manual

287
00:23:00,021 --> 00:23:04,359
neighbors and stuff like that here,
but the main thing is we have

288
00:23:04,360 --> 00:23:07,394
two other sub-configuration modes.

289
00:23:07,395 --> 00:23:11,583
One of those is af-interface.

290
00:23:11,584 --> 00:23:17,277
One of the big things that changes
with named mode is, none,

291
00:23:17,278 --> 00:23:24,819
and I mean zero, of our config goes
under the interface now for EIGRP.

292
00:23:24,820 --> 00:23:28,901
All those commands such as summary address,

293
00:23:28,902 --> 00:23:33,579
and turning off split horizon, and
all of those kind of things that

294
00:23:33,580 --> 00:23:41,611
went under the interface, are now under the
router config under the af-interface command.

295
00:23:41,612 --> 00:23:45,466
You would go into any interface, so
in our case we could say interface

296
00:23:45,467 --> 00:23:47,934
fa0/1, if you remember.

297
00:23:47,935 --> 00:23:50,100
I'm sorry, not on router 5 though.

298
00:23:50,101 --> 00:23:52,359
Let's switch over to router 6 actually.

299
00:23:52,360 --> 00:23:55,659
So let me back out of that before
I mess something up on router 5.

300
00:23:55,660 --> 00:24:01,967
It was actually on router 6 where we were
running-- let me go back to the command.

301
00:24:03,687 --> 00:24:09,464
Where we're running EIGRP on gigabit
0/1, and if you look back to our

302
00:24:09,465 --> 00:24:12,924
topology diagram, we're not supposed to be.

303
00:24:15,128 --> 00:24:24,292
We say af-interface - yeah, I know
it's not complete - gigabit 0/1.

304
00:24:24,293 --> 00:24:27,125
There's actually two commands you can do here.

305
00:24:27,126 --> 00:24:34,088
Just from a practical standpoint,
I've not really come up with a

306
00:24:34,089 --> 00:24:35,387
good difference between them.

307
00:24:35,388 --> 00:24:37,299
Let me show you what I mean by that.

308
00:24:37,300 --> 00:24:45,856
If I switch over to router 5 and I
say do show ipv6 route for eigrp,

309
00:24:45,857 --> 00:24:54,480
he should have subnet 69, which
is the link going up to switch 3.

310
00:24:54,481 --> 00:24:58,448
Just as a reminder here, because I know
you're not that familiar with it and

311
00:24:58,449 --> 00:25:03,403
we haven't looked at it for a little
while here. If I switch back over

312
00:25:03,404 --> 00:25:05,652
to the topology here,

313
00:25:05,653 --> 00:25:12,994
we're talking about this link up
here at the top between router 3

314
00:25:12,995 --> 00:25:17,210
and router 6. That's the link
we're talking about right now.

315
00:25:17,211 --> 00:25:23,396
And if we take a look at this, I don't
need to be running EIGRP on that,

316
00:25:23,397 --> 00:25:31,421
so we come back to router 6 and we say shut.

317
00:25:31,422 --> 00:25:35,549
We shut that interface for the EIGRP process,

318
00:25:35,550 --> 00:25:46,316
and then we say, do show ipv6 eigrp interface,

319
00:25:46,317 --> 00:25:50,638
and it shows that we're not running
it on gigabit 0/1 anymore.

320
00:25:50,639 --> 00:25:55,817
So, that means you're not sending out
hellos or any of that kind of stuff.

321
00:25:55,818 --> 00:25:57,861
You would not bring up a neighborship,

322
00:25:57,862 --> 00:26:06,934
but if you go back here to router 5, it disappears.

323
00:26:06,935 --> 00:26:13,481
This is really the difference
between a shut and a pass.

324
00:26:13,482 --> 00:26:18,776
If I go back to router 6, maybe I
did want that network in EIGRP,

325
00:26:18,777 --> 00:26:25,464
I could say no shut, pass, and if I did that,

326
00:26:25,465 --> 00:26:32,807
do show ipv6 eigrp interface,
it keeps it off the list.

327
00:26:32,808 --> 00:26:34,622
So a lot of people look at this and they're like,

328
00:26:34,623 --> 00:26:37,339
well what's the difference
between a shut and a pass?

329
00:26:37,340 --> 00:26:39,374
That's what I'm trying to get to here.

330
00:26:39,375 --> 00:26:44,335
So if I do that and I go back to router 5,
we should've picked that network up again.

331
00:26:44,336 --> 00:26:45,717
Okay, there we go.

332
00:26:45,718 --> 00:26:52,797
So the difference is, do you want that advertised
into the routing process or don't you?

333
00:26:52,798 --> 00:26:58,036
That's the difference between
the shut and the pass.

334
00:26:58,037 --> 00:27:01,722
Now, again, we don't want it in
there at all because we're going

335
00:27:01,723 --> 00:27:04,216
to use it for other fun stuff later.

336
00:27:04,217 --> 00:27:08,964
I'm going to say no pass and then
I'm going to say shut again.

337
00:27:08,965 --> 00:27:12,028
I just wanted you to see the
difference between those.

338
00:27:12,029 --> 00:27:14,757
Now, once again, here under the interface,

339
00:27:14,758 --> 00:27:19,353
this is where you would now put all
the things that you would normally

340
00:27:19,354 --> 00:27:24,770
put for EIGRP under the
interface, but now they go heon't you? That's the difference
 between the shut and the pass.

0:26:58.200000 --> 0:27:01.680000
 Okay, now again, we don't want it in
 there at all because we're going

0:27:01.680000 --> 0:27:02.660000
 to use it for other things.

0:27:02.660000 --> 0:27:04.420000
 We'll do other fun stuff later.

0:27:04.420000 --> 0:27:09.060000
 So, I'm going to say no pass and
 then I'm going to say shut again.

0:27:09.060000 --> 0:27:11.540000
 But I just wanted to see the
 difference between those.

0:27:11.540000 --> 0:27:15.560000
 Okay, now once again, here under the
 interface, this is where you would

0:27:15.560000 --> 0:27:21.760000
 now put all the things that you would
 normally put for EIGRP under the

0:27:21.760000 --> 0:27:25.140000
 interface. But now they go here.

0:27:25.140000 --> 0:27:29.500000
 Okay, so just as a case of discussion
 and again, I'm not going to leave

0:27:29.500000 --> 0:27:33.300000
 it here, but I can say
 this is the interface.

0:27:33.300000 --> 0:27:36.060000
 We're under the wrong
 interface right now.

0:27:36.060000 --> 0:27:40.700000
 So, AF interface gigabit 00.456.

0:27:40.700000 --> 0:27:44.900000
 This is the interface facing
 down towards router 5.

0:27:44.900000 --> 0:27:49.760000
 I could do summary address
 colon colon slash zero.

0:27:49.760000 --> 0:27:55.320000
 Okay, I get a summary
 reconfigured.

0:27:55.320000 --> 0:27:58.800000
 Go back to router 5 and our routing
 table is going to look just a little

0:27:58.800000 --> 0:28:00.520000
 bit different now.

0:28:00.520000 --> 0:28:04.420000
 Okay, so again, the main thing I'm
 trying to show you that this is not

0:28:04.420000 --> 0:28:08.080000
 about, you know, obviously we can't go
 over every detail of every routing

0:28:08.080000 --> 0:28:15.520000
 protocol. Our focus is on IPv6 and
 the differences between them.

0:28:15.520000 --> 0:28:21.820000
 So, mostly I guess what I'm trying to
 show you here is that it's the same.

0:28:21.820000 --> 0:28:29.460000
 Really? Okay, we do
 it the same way.

0:28:29.460000 --> 0:28:34.360000
 So, I'm going to do this versus normal
 mode versus IPv4 versus IPv6.

0:28:34.360000 --> 0:28:37.900000
 This is really just named
 mode versus legacy mode.

0:28:37.900000 --> 0:28:40.960000
 It really doesn't matter what
 address family we're in.

0:28:40.960000 --> 0:28:46.040000
 It's just you got to remember that you're
 dealing with IPv6 addressing.

0:28:46.040000 --> 0:28:51.700000
 So, when I just summarize to the default
 there, it's of course an IPv6

0:28:51.700000 --> 0:28:53.840000
 default. So, let's
 take that back out.

0:28:53.840000 --> 0:28:56.000000
 I don't actually want
 to do it right now.

0:28:56.000000 --> 0:28:59.040000
 But this is also where you would change
 hello times and of course, you

0:28:59.040000 --> 0:29:05.100000
 know, next top, excuse me, next
 top behavior, things like that.

0:29:05.100000 --> 0:29:08.840000
 So, none of the commands go
 on to the interface anymore.

0:29:08.840000 --> 0:29:15.220000
 And what can really confuse people
 is if you say interface gigabit 00

0:29:15.220000 --> 0:29:21.300000
.456, that's not right.

0:29:21.300000 --> 0:29:25.120000
 Or you just create
 a whole new one.

0:29:25.120000 --> 0:29:43.040000
 IPv6 summary address for EIGRP 100
 and tell it to do colon colon slash

0:29:43.040000 --> 0:29:49.440000
 zero. So, tell it to go ahead and create
 the summary address under the

0:29:49.440000 --> 0:29:58.860000
 interface. That's what you
 would do in legacy config.

0:29:58.860000 --> 0:30:03.800000
 And quick thing to note, we could
 go look that this hasn't happened.

0:30:03.800000 --> 0:30:08.920000
 Or you could just go by the fact
 that you haven't seen a resync.

0:30:08.920000 --> 0:30:12.920000
 Every time up here when we created
 a summary, we did a resync.

0:30:12.920000 --> 0:30:14.400000
 Take the summary off.

0:30:14.400000 --> 0:30:17.720000
 Resync. Put the summary
 on the interface.

0:30:17.720000 --> 0:30:22.220000
 Nothing. Okay. We can go
 over to router five.

0:30:22.220000 --> 0:30:23.880000
 We can look at this routing table.


0:30:23.880000 --> 0:30:30.660000
 Okay. And we've picked up our 36 and
 our 100 again and lost our default.

0:30:30.660000 --> 0:30:34.300000
 Okay. This is what I'm talking about
 when I say with named mode, none

0:30:34.300000 --> 0:30:37.640000
 of the config goes
 on the interfaces.

0:30:37.640000 --> 0:30:40.760000
 Now, the commands don't magically
 disappear off the interface.

0:30:40.760000 --> 0:30:42.560000
 And I'm not going to
 leave that in there.

0:30:42.560000 --> 0:30:45.080000
 Because of course, it's not
 doing anything anyway.

0:30:45.080000 --> 0:30:48.720000
 Because, you know, the router doesn't
 know if you're going to switch over

0:30:48.720000 --> 0:30:52.320000
 and do legacy EIGRP config.

0:30:52.320000 --> 0:30:55.400000
 In which case, the commands would
 go under the interface.

0:30:55.400000 --> 0:30:59.680000
 So, I'm just trying to point out, you
 know, again, this is not really

0:30:59.680000 --> 0:31:00.860000
 IPv4 versus the USB.

0:31:00.860000 --> 0:31:02.300000
 This is IPv6 here.

0:31:02.300000 --> 0:31:06.280000
 This is named mode
 versus legacy mode.

0:31:06.280000 --> 0:31:10.140000
 But we're going to need
 named mode for IPv6.

0:31:10.140000 --> 0:31:12.700000
 Especially for VR apps.

0:31:12.700000 --> 0:31:16.320000
 So, we have to move to this.

0:31:16.320000 --> 0:31:20.780000
 Okay. So, let's go back into
 our named mode again.

0:31:20.780000 --> 0:31:30.960000
 So, router, EIGRP, IPv6, address
 family, IPv6, unicast, for AS100.

0:31:30.960000 --> 0:31:34.900000
 And the other thing we didn't look
 at yet is, oh, one more thing with

0:31:34.900000 --> 0:31:36.540000
 AF interface, by the way.

0:31:36.540000 --> 0:31:39.860000
 There's also an AF interface
 default command.

0:31:39.860000 --> 0:31:45.680000
 And if you do that, what you're doing
 is you're configuring all of the

0:31:45.680000 --> 0:31:52.820000
 interfaces. So, if I said pass, this
 would be like the old, you know,

0:31:52.820000 --> 0:31:54.480000
 passive interface default.

0:31:54.480000 --> 0:31:56.720000
 And then no pass, whatever.

0:31:56.720000 --> 0:32:00.380000
 So, you know, you can still do those
 same kind of constructions.

0:32:00.380000 --> 0:32:05.440000
 It's just that you use AF
 interface default instead.

0:32:05.440000 --> 0:32:11.060000
 Okay. And one other thing too to note,
 one thing you cannot do under default

0:32:11.060000 --> 0:32:15.160000
 specifically. And it's a little hard
 to highlight something that's not

0:32:15.160000 --> 0:32:20.400000
 here. But if you look down here at
 the bottom, you don't have summary

0:32:20.400000 --> 0:32:26.000000
 address. Okay. Up here, we typed summary
 address and then put in the default

0:32:26.000000 --> 0:32:27.180000
 under the address family.

0:32:27.180000 --> 0:32:27.980000
 See right there?

0:32:27.980000 --> 0:32:29.660000
 Summary address.

0:32:29.660000 --> 0:32:32.180000
 You can't do that
 under the default.

0:32:32.180000 --> 0:32:34.180000
 Okay. But everything else
 you can configure.

0:32:34.180000 --> 0:32:40.060000
 And this would be doing all of your
 interfaces at the same time.

0:32:40.060000 --> 0:32:44.220000
 Okay. And one more quick thing
 about that shut in the past.

0:32:44.220000 --> 0:32:46.560000
 I just want to make sure
 we're clear on something.

0:32:46.560000 --> 0:32:49.820000
 When we went into named mode, and I
 don't know if anybody necessarily

0:32:49.820000 --> 0:32:52.000000
 directly picked up on this.

0:32:52.000000 --> 0:32:56.360000
 I did say it in the slides earlier,
 but I just want to make sure you got

0:32:56.360000 --> 0:33:02.200000
 it. That as soon as we went into named
 mode and put in the address family,

0:33:02.200000 --> 0:33:03.680000
 our neighbors came up.

0:33:03.680000 --> 0:33:11.740000
 So this immediately brings up
 IPv6 on all of the interfaces.

0:33:11.740000 --> 0:33:15.480000
 Okay. One last thing for now, and we
 will be back to this as we get to

0:33:15.480000 --> 0:33:17.600000
 redistribution and
 things like that.

0:33:17.600000 --> 0:33:22.240000
 But if I exit out of AF interface,
 there's also topology.

0:33:22.240000 --> 0:33:25.720000
 And this does support multi
-topology on some code.

0:33:25.720000 --> 0:33:26.960000
 This code does not.

0:33:26.960000 --> 0:33:29.000000
 So we just say topology base.

0:33:29.000000 --> 0:33:34.380000
 And this is where you would do all the
 things related to the EIGRP topology.

0:33:34.380000 --> 0:33:38.200000
 Okay. So again, things like maximum
 paths, changing the variance to do

0:33:38.200000 --> 0:33:40.360000
 one equal cross load sharing.

0:33:40.360000 --> 0:33:43.980000
 Putting in a summary metric.

0:33:43.980000 --> 0:33:47.460000
 Putting in redistribution, which
 is the part we'll get back to.

0:33:47.460000 --> 0:33:49.700000
 This is where you would put
 your distribute list.

0:33:49.700000 --> 0:33:51.540000
 Change the admin distance.

0:33:51.540000 --> 0:33:56.180000
 All of those things you would normally
 do under EIGRP global mode.

0:33:56.180000 --> 0:34:03.400000
 Okay. So at this point, that takes care
 of EIGRP on router six and router

0:34:03.400000 --> 0:34:04.720000
 three and router five.

0:34:04.720000 --> 0:34:07.000000
 We did not do switch four.

0:34:07.000000 --> 0:34:09.900000
 So interface VLAN.

0:34:09.900000 --> 0:34:13.520000
 We'll just do legacy mode over
 here just so we have a couple.

0:34:13.520000 --> 0:34:25.820000
 So interface VLAN 456,
 IPv6, EIGRP 100.

0:34:25.820000 --> 0:34:30.960000
 And then router, whoops.

0:34:30.960000 --> 0:34:36.320000
 IPv6 router, EIGRP 100 to
 create the global process.

0:34:36.320000 --> 0:34:38.800000
 And the neighbor should come up.

0:34:38.800000 --> 0:34:40.100000
 And there we go.

0:34:40.100000 --> 0:34:47.180000
 Do show IPv6 route, EIGRP.

0:34:47.180000 --> 0:34:51.160000
 And we're up and running
 with EIGRP.

0:34:51.160000 --> 0:34:53.680000
 And the other thing to point out, and
 this is the first time we really

0:34:53.680000 --> 0:34:58.160000
 started jumping into the routing table,
 is notice that all of the next

0:34:58.160000 --> 0:35:04.020000
 hops to all of these networks are
 all the link local addresses.

0:35:04.020000 --> 0:35:10.640000
 Okay. So if I were to say, you know,
 do trace to, let's see what should

0:35:10.640000 --> 0:35:18.820000
 we go to. We actually have a lot of
 networks in the EIGRP here I don't

0:35:18.820000 --> 0:35:20.600000
 want. We'll be with
 that in a minute.

0:35:20.600000 --> 0:35:29.180000
 But let's just trace to router
 six's loop back here.

0:35:29.180000 --> 0:35:31.920000
 Looking good. Looking good.

0:35:31.920000 --> 0:35:41.160000
 Problem here. Nobody has
 any way to answer me.

0:35:41.160000 --> 0:35:43.680000
 I think is what's going on here.

0:35:43.680000 --> 0:35:53.040000
 Because I didn't bring anything on switch
 four into the routing process.

0:35:53.040000 --> 0:35:57.900000
 So they have no way
 to get back to me.

0:35:57.900000 --> 0:36:02.160000
 If we go to the other devices, they
 have no, they have no routes.

0:36:02.160000 --> 0:36:04.400000
 So we'll take a look
 at some of this more.

0:36:04.400000 --> 0:36:05.200000
 Well, you know what we could do?

0:36:05.200000 --> 0:36:07.680000
 We could just do bring switch
 four's loop back in.

0:36:07.680000 --> 0:36:11.460000
 Interface, loop back zero.

0:36:11.460000 --> 0:36:17.840000
 Give me that other one.

0:36:17.840000 --> 0:36:26.160000
 And then the one back
 out of the interface.

0:36:26.160000 --> 0:36:29.840000
 Did I? Let's give him
 an actual address.

0:36:29.840000 --> 0:36:44.180000
 Let's go to router six.

0:36:44.180000 --> 0:36:46.540000
 To filter that, but that's okay.

0:36:46.540000 --> 0:36:52.360000
 Oh, he still has a static
 default in there.

0:36:52.360000 --> 0:37:32.560000
 We need to get rid of that.

0:37:32.560000 --> 0:37:35.700000
 There we go. A little bit better.

0:37:35.700000 --> 0:37:38.980000
 Okay. And just make sure
 we're working both ways.

0:37:38.980000 --> 0:37:43.120000
 If we go back to switch four, he should
 be able to do that one that didn't

0:37:43.120000 --> 0:37:44.620000
 work there for us.

0:37:44.620000 --> 0:37:49.500000
 Much better. A little bit of
 goofy routing going on there.

0:37:49.500000 --> 0:38:02.020000
 Okay. So that takes care
 of running the edge.

0:38:02.020000 --> 0:38:05.280000
 Redistribution coming up
 in a future lesson here.

0:38:05.280000 --> 0:38:09.200000
 So we're not, of course, done with the
 IDRP, but that's just the basics

0:38:09.200000 --> 0:38:12.800000
 of getting it up and
 running with IPV six.

