1
00:00:00,000 --> 00:00:00,966

2
00:00:00,966 --> 00:00:04,347
[AUDIO LOGO]

3
00:00:04,347 --> 00:00:08,220

4
00:00:08,220 --> 00:00:11,560
The last protocol we have to
configure redistribution for

5
00:00:11,560 --> 00:00:13,470
is EIGRP.

6
00:00:13,470 --> 00:00:17,950
Now, like RIP, this is not
one of our major topics.

7
00:00:17,950 --> 00:00:20,730
However, again, it's
worth looking at just

8
00:00:20,730 --> 00:00:22,390
in case you run into it.

9
00:00:22,390 --> 00:00:25,200
So just like RIP, let's
just take a quick look

10
00:00:25,200 --> 00:00:26,140
at the topology.

11
00:00:26,140 --> 00:00:28,080
And then just jump right
into the command line

12
00:00:28,080 --> 00:00:31,140
and check out any
caveats that we have

13
00:00:31,140 --> 00:00:33,800
with dealing with the EIGRP.

14
00:00:33,800 --> 00:00:34,910
Small hint.

15
00:00:34,910 --> 00:00:37,490
Just like RIP, we're
going to have to specify

16
00:00:37,490 --> 00:00:39,860
a metric on the redistribution.

17
00:00:39,860 --> 00:00:42,380
There is no seed
metric in EIGRP.

18
00:00:42,380 --> 00:00:46,470
So again, let's jump
in and take a look.

19
00:00:46,470 --> 00:00:48,980
So now, we're going to
be dealing with EIGRP 100

20
00:00:48,980 --> 00:00:50,840
up here on router 9.

21
00:00:50,840 --> 00:00:53,210
And to get the routes
up there, we'll

22
00:00:53,210 --> 00:00:59,900
be redistributing on router
2 from OSPF into EIGRP.

23
00:00:59,900 --> 00:01:03,140
And we'll do the same
thing on router 1.

24
00:01:03,140 --> 00:01:06,080
So let's just go ahead and
jump into the command line

25
00:01:06,080 --> 00:01:07,550
and get this configured.

26
00:01:07,550 --> 00:01:10,280

27
00:01:10,280 --> 00:01:14,380
So we'll start here on router
9 with a show ip router eigrp.

28
00:01:14,380 --> 00:01:17,350
And we see that router 9 is
actually learning nothing

29
00:01:17,350 --> 00:01:19,370
from EIGRP at this point.

30
00:01:19,370 --> 00:01:22,240
So let's go ahead and
jump down to router 1

31
00:01:22,240 --> 00:01:24,490
and configure our
redistribution.

32
00:01:24,490 --> 00:01:29,650
So we'll go into configuration
mode, into our EIGRP process,

33
00:01:29,650 --> 00:01:31,960
into our address-family.

34
00:01:31,960 --> 00:01:35,560
And we'll say to
redistribute ospf 1.

35
00:01:35,560 --> 00:01:37,720
Now, we already
mentioned that EIGRP

36
00:01:37,720 --> 00:01:39,910
does require a seed metric.

37
00:01:39,910 --> 00:01:43,000
So watch what happens when
we commit the changes.

38
00:01:43,000 --> 00:01:45,340
We get a message
right away telling us

39
00:01:45,340 --> 00:01:51,070
that we're setting EIGRP to
redistribute with no metric.

40
00:01:51,070 --> 00:01:54,700
So it's pretty much just
not even accepting this.

41
00:01:54,700 --> 00:01:59,450
Now, one way we can do this
is to set a default metric.

42
00:01:59,450 --> 00:02:02,350
So let's go ahead and
set a default metric.

43
00:02:02,350 --> 00:02:04,570
The way you put the
metric in for EIGRP

44
00:02:04,570 --> 00:02:06,610
is first, the bandwidth.

45
00:02:06,610 --> 00:02:08,830
And these numbers aren't
all that critical.

46
00:02:08,830 --> 00:02:10,880
Of course, on a
production network,

47
00:02:10,880 --> 00:02:13,790
you would want to set
these to be accurate.

48
00:02:13,790 --> 00:02:16,120
I'm just going to set
them to say like, 1500.

49
00:02:16,120 --> 00:02:18,310
We'll pretend it's a T1 line.

50
00:02:18,310 --> 00:02:19,520
Then the delay.

51
00:02:19,520 --> 00:02:25,450
So we'll set this to
10, reliability, 255.

52
00:02:25,450 --> 00:02:28,870
Next is load, which
we'll set to 1.

53
00:02:28,870 --> 00:02:34,060
And the last thing is
the MTU, which is 1500.

54
00:02:34,060 --> 00:02:37,420
So once we have all these
values in, we'll just hit Enter

55
00:02:37,420 --> 00:02:39,490
and we'll hit Commit again.

56
00:02:39,490 --> 00:02:41,930
This time, we don't
get any errors.

57
00:02:41,930 --> 00:02:44,680
So now, let's go
back up to router 9.

58
00:02:44,680 --> 00:02:47,840
And let's look at our
EIGRP routes again.

59
00:02:47,840 --> 00:02:52,120
And now, we see we have all of
these external EIGRP routes.

60
00:02:52,120 --> 00:02:54,370
If we look at these
entries, again, we'll

61
00:02:54,370 --> 00:02:59,200
just pick on the one here at
the bottom, the 172.16.245.0.

62
00:02:59,200 --> 00:03:05,920
Things to note-- one, it is
flagged as external in EIGRP.

63
00:03:05,920 --> 00:03:09,430
EIGRP keeps track of
external networks.

64
00:03:09,430 --> 00:03:12,580
Also, notice that
all of these routes

65
00:03:12,580 --> 00:03:18,530
have the same
metric, the 1709312.

66
00:03:18,530 --> 00:03:21,440
That's simply the
value that each group

67
00:03:21,440 --> 00:03:25,983
calculates using its formula
based on the metrics we put in.

68
00:03:25,983 --> 00:03:28,400
They're all the same because
they're all being distributed

69
00:03:28,400 --> 00:03:29,960
with the same metric.

70
00:03:29,960 --> 00:03:32,220
So we would expect
this to be the same.

71
00:03:32,220 --> 00:03:34,160
And of course, we
could adjust this

72
00:03:34,160 --> 00:03:37,650
based on the metrics we used
on the redistribution line.

73
00:03:37,650 --> 00:03:39,950
In this particular case,
it's not that critical

74
00:03:39,950 --> 00:03:40,950
what they are.

75
00:03:40,950 --> 00:03:44,370
We're just trying to get
the routes into EIGRP group.

76
00:03:44,370 --> 00:03:47,360
So we saw how to configure
this using a default metric.

77
00:03:47,360 --> 00:03:49,910
Let's look at the
other option as we do

78
00:03:49,910 --> 00:03:52,460
the redistribution on router 2.

79
00:03:52,460 --> 00:03:56,540
So what we'll do here is we'll
set the metric a little bit

80
00:03:56,540 --> 00:03:59,390
different for say,
loopback interfaces

81
00:03:59,390 --> 00:04:01,800
than we do for everything else.

82
00:04:01,800 --> 00:04:06,020
So in order to do that, we're
going to need a prefix that.

83
00:04:06,020 --> 00:04:09,170
We'll just call
it like PS_LOOPS.

84
00:04:09,170 --> 00:04:12,410
That'll match on anything
that begins with a 10

85
00:04:12,410 --> 00:04:16,010
and has a mask of 32 bits.

86
00:04:16,010 --> 00:04:16,850
We'll end set.

87
00:04:16,850 --> 00:04:18,620
So that should
match on our loops.

88
00:04:18,620 --> 00:04:21,079
Now, let's write our policy.

89
00:04:21,079 --> 00:04:24,710
We'll just call it
RP_EIGRP_METRIC.

90
00:04:24,710 --> 00:04:29,810
We'll say if the destination
is in PS_LOOPS, then

91
00:04:29,810 --> 00:04:34,310
what we're going to do
is set the EIGRP metric.

92
00:04:34,310 --> 00:04:37,520
Let's set this one to 15000.

93
00:04:37,520 --> 00:04:40,170
We'll use the same
numbers for the rest.

94
00:04:40,170 --> 00:04:44,630
And then we'll say, else
set the eigrp-metric.

95
00:04:44,630 --> 00:04:47,520
And let's just add a
0 to the bandwidth.

96
00:04:47,520 --> 00:04:51,860
We'll end our if statement
and our policy, then

97
00:04:51,860 --> 00:04:56,780
in the router eigrp,
address-family ipv4.

98
00:04:56,780 --> 00:04:59,540
Once again, we're
redistributing OSPF 1.

99
00:04:59,540 --> 00:05:03,560
But this time, we're going to
run it through the route policy

100
00:05:03,560 --> 00:05:06,650
RP_EIGRP_METRIC.

101
00:05:06,650 --> 00:05:08,762
The difference here,
of course, being

102
00:05:08,762 --> 00:05:10,970
that we're going to be
setting the metric differently

103
00:05:10,970 --> 00:05:13,460
on different routes
using our policy,

104
00:05:13,460 --> 00:05:17,690
rather than just using a default
metric like we did on router 1.

105
00:05:17,690 --> 00:05:21,260
It just gives us more
power, more capability

106
00:05:21,260 --> 00:05:24,140
to control the
metrics if we want to.

107
00:05:24,140 --> 00:05:27,630
Now, let's go take a look
at these on router 9 again.

108
00:05:27,630 --> 00:05:29,630
So to compare the
routes to these,

109
00:05:29,630 --> 00:05:35,570
just keep in mind that
these are 1709312.

110
00:05:35,570 --> 00:05:37,970
Remember that the metric
here was exactly the same,

111
00:05:37,970 --> 00:05:40,130
except we did a 1500.

112
00:05:40,130 --> 00:05:43,970
The other ones we just did
have a higher bandwidth.

113
00:05:43,970 --> 00:05:45,960
Therefore, they should win.

114
00:05:45,960 --> 00:05:49,820
So all of these should
flip from going to router 1

115
00:05:49,820 --> 00:05:52,160
to going to router 2.

116
00:05:52,160 --> 00:05:54,080
We can see here that they have.

117
00:05:54,080 --> 00:05:56,180
And they have a
much better metric.

118
00:05:56,180 --> 00:06:00,290
And we see that the
non-loopback interfaces

119
00:06:00,290 --> 00:06:02,360
have an even better metric.

120
00:06:02,360 --> 00:06:08,390
So our loopbacks, for
example, here, have 173312.

121
00:06:08,390 --> 00:06:12,470
And then a
non-loopback interface

122
00:06:12,470 --> 00:06:16,227
is, for example, 19712.

123
00:06:16,227 --> 00:06:18,560
Now, this, of course, is going
to be a really long table

124
00:06:18,560 --> 00:06:20,930
because we should now be
getting all of the routes

125
00:06:20,930 --> 00:06:23,490
from our entire environment.

126
00:06:23,490 --> 00:06:26,060
However, that still
doesn't mean we

127
00:06:26,060 --> 00:06:28,460
have end-to-end reachability.

128
00:06:28,460 --> 00:06:32,180
If we trace that
88 loopback, notice

129
00:06:32,180 --> 00:06:35,360
that we're getting stuck
in the exact same routing

130
00:06:35,360 --> 00:06:40,530
loop that still exists because
we haven't fixed that yet.

131
00:06:40,530 --> 00:06:44,010
In this video, we saw how
to redistribute routes

132
00:06:44,010 --> 00:06:45,570
in the EIGRP.

133
00:06:45,570 --> 00:06:47,820
And again, the
main thing here is

134
00:06:47,820 --> 00:06:52,290
that you do have to supply a
seed metric because otherwise,

135
00:06:52,290 --> 00:06:54,720
they're redistributed
essentially as

136
00:06:54,720 --> 00:06:56,640
infinite like RIP.

137
00:06:56,640 --> 00:06:59,520
Although, in the case of EIGRP,
it just doesn't redistribute

138
00:06:59,520 --> 00:07:00,910
them at all.

139
00:07:00,910 --> 00:07:04,360
However, we can supply that
seed metric, of course.

140
00:07:04,360 --> 00:07:07,890
We can do it either
globally under the process

141
00:07:07,890 --> 00:07:10,110
by setting a default metric.

142
00:07:10,110 --> 00:07:14,130
Or of course, we can do
it with a route policy.

143
00:07:14,130 --> 00:07:16,980
Or if we were doing
this on IOS XE,

144
00:07:16,980 --> 00:07:20,200
we could, of course,
use a route map as well.

145
00:07:20,200 --> 00:07:24,120
Now, as we can see this still
doesn't solve the looping

146
00:07:24,120 --> 00:07:27,330
problem that still exists
in our environment,

147
00:07:27,330 --> 00:07:29,410
and we need to fix that.

148
00:07:29,410 --> 00:07:32,350
That is exactly what
we're going to do next.

149
00:07:32,350 --> 00:07:33,550
Until then.

150
00:07:33,550 --> 00:07:35,790
I hope this has been
informative for you,

151
00:07:35,790 --> 00:07:38,930
and I'd like to thank
you for viewing.

152
00:07:38,930 --> 00:07:43,000