1
00:00:00,000 --> 00:00:00,942

2
00:00:00,942 --> 00:00:04,239
[AUDIO LOGO]

3
00:00:04,239 --> 00:00:08,010

4
00:00:08,010 --> 00:00:09,480
So now, we're going
to take a look

5
00:00:09,480 --> 00:00:14,280
at redistributing into RIP or
Routing Information Protocol.

6
00:00:14,280 --> 00:00:17,340
Now, this is, of course,
not one of our main topics

7
00:00:17,340 --> 00:00:19,410
from a service
provider perspective.

8
00:00:19,410 --> 00:00:22,230
We're generally not going
to run into RIP very often,

9
00:00:22,230 --> 00:00:23,790
at least I certainly hope not.

10
00:00:23,790 --> 00:00:25,920
But it's still good
to be familiar with it

11
00:00:25,920 --> 00:00:29,130
in case you do run into a
customer running RIP, maybe

12
00:00:29,130 --> 00:00:30,780
as their CE-PE protocol.

13
00:00:30,780 --> 00:00:33,430
Although, I doubt the service
provider would support that.

14
00:00:33,430 --> 00:00:37,450
But if you do support customers
in a more direct fashion,

15
00:00:37,450 --> 00:00:40,290
then you may, in fact, run
into one that's running RIP.

16
00:00:40,290 --> 00:00:41,820
So it's not going
to hurt us just

17
00:00:41,820 --> 00:00:43,620
to take a quick
few minutes to take

18
00:00:43,620 --> 00:00:47,400
a look at some of the caveats
of redistributing into RIP.

19
00:00:47,400 --> 00:00:50,670
And honestly, there's
really only one caveat,

20
00:00:50,670 --> 00:00:55,150
and that is that the
default metric is infinite,

21
00:00:55,150 --> 00:00:57,600
which means we have
to set a metric when

22
00:00:57,600 --> 00:00:59,220
we do the redistribution.

23
00:00:59,220 --> 00:01:02,070
The only other thing to really
note as we go through this

24
00:01:02,070 --> 00:01:08,820
is that a bit like IS-IS, RIP
also has no tracking mechanism

25
00:01:08,820 --> 00:01:12,030
to know that this route came
from an external source.

26
00:01:12,030 --> 00:01:15,570
Internal and external routes
are treated exactly the same way

27
00:01:15,570 --> 00:01:16,470
in RIP.

28
00:01:16,470 --> 00:01:18,930
So that said, we're going
to look at the topology

29
00:01:18,930 --> 00:01:19,500
real quickly.

30
00:01:19,500 --> 00:01:21,960
We're just doing one
redistribution on one router.

31
00:01:21,960 --> 00:01:23,830
But let's just take
a look where that is.

32
00:01:23,830 --> 00:01:25,997
And then we'll jump into
the command line real quick

33
00:01:25,997 --> 00:01:27,570
and do that one redistribution.

34
00:01:27,570 --> 00:01:30,570
So this is just going to be a
quick one, but just so you're

35
00:01:30,570 --> 00:01:35,900
at least familiar with being
able to redistribute into RIP.

36
00:01:35,900 --> 00:01:38,390
So again, this is going to
be a very easy one we only

37
00:01:38,390 --> 00:01:41,570
have one environment running
RIP up here between router 6

38
00:01:41,570 --> 00:01:42,770
and router 10.

39
00:01:42,770 --> 00:01:44,870
So what we're going
to be configuring

40
00:01:44,870 --> 00:01:50,300
is simply router 6 to
redistribute IS-IS into RIP.

41
00:01:50,300 --> 00:01:52,430
And of course, we'll
be looking at router 10

42
00:01:52,430 --> 00:01:55,800
to see if those routes are
showing up as they should.

43
00:01:55,800 --> 00:01:58,320
So let's go ahead and jump
into the command line.

44
00:01:58,320 --> 00:02:03,160
We'll start on router 10 just to
see its current routing table.

45
00:02:03,160 --> 00:02:06,600
So let's do a show IP route
RIP here on router 10.

46
00:02:06,600 --> 00:02:08,639
And we can see that it's
literally only learning

47
00:02:08,639 --> 00:02:11,670
one route from RIP right
now coming from router 6.

48
00:02:11,670 --> 00:02:15,120
So let's go ahead and configure
that redistribution now

49
00:02:15,120 --> 00:02:16,560
on router 6.

50
00:02:16,560 --> 00:02:19,980
So all we have to do
is go into router RIP.

51
00:02:19,980 --> 00:02:23,010
Say redistribute and
choose our protocol.

52
00:02:23,010 --> 00:02:25,140
So isis 1.

53
00:02:25,140 --> 00:02:27,000
And we'll notice
with RIP, there's not

54
00:02:27,000 --> 00:02:28,600
a whole lot of choices here.

55
00:02:28,600 --> 00:02:32,560
We can choose which ISIS
routes to pull from.

56
00:02:32,560 --> 00:02:35,610
So we can choose level
1, level 1-2, or 2.

57
00:02:35,610 --> 00:02:37,680
We can, of course,
specify the metric,

58
00:02:37,680 --> 00:02:40,800
or we could use a route map,
which would either be used

59
00:02:40,800 --> 00:02:42,937
to filter or set the metric.

60
00:02:42,937 --> 00:02:44,520
But let's just go
ahead and hit Enter.

61
00:02:44,520 --> 00:02:46,380
Do a simple redistribution.

62
00:02:46,380 --> 00:02:50,280
And what we're going to find
is if we go back to router 10,

63
00:02:50,280 --> 00:02:53,140
we do our show ip
route rip again,

64
00:02:53,140 --> 00:02:55,570
we still don't have anything.

65
00:02:55,570 --> 00:02:58,260
And if we were to
do a debug ip rip,

66
00:02:58,260 --> 00:03:01,560
let's just wait for an update
to come in from router 6.

67
00:03:01,560 --> 00:03:03,330
They're sending an update.

68
00:03:03,330 --> 00:03:05,730
And there, we
receive the update.

69
00:03:05,730 --> 00:03:09,090
We see that that's the
only route we're receiving.

70
00:03:09,090 --> 00:03:11,910
This is, of course,
because as we said before,

71
00:03:11,910 --> 00:03:16,890
RIP uses infinite or infinity
as its default metric.

72
00:03:16,890 --> 00:03:19,570
Therefore, it doesn't
even send the updates.

73
00:03:19,570 --> 00:03:22,050
So we do have to
specify a metric.

74
00:03:22,050 --> 00:03:25,570
Let's go back over to
router 6 and do that.

75
00:03:25,570 --> 00:03:29,070
So back on router 6, we'll
simply specify a metric.

76
00:03:29,070 --> 00:03:32,760
Of course, it could be
anything from 0 to 16.

77
00:03:32,760 --> 00:03:35,730
But of course, depending on
the size of your environment,

78
00:03:35,730 --> 00:03:38,460
you probably want to go
somewhere towards the middle,

79
00:03:38,460 --> 00:03:40,560
like maybe a 5 or a 6.

80
00:03:40,560 --> 00:03:42,760
So we'll go ahead and
put that in there.

81
00:03:42,760 --> 00:03:45,513
And then let's go back
over to router 10.

82
00:03:45,513 --> 00:03:48,180
So back here on router 10, let's
go ahead and look at our routes

83
00:03:48,180 --> 00:03:49,560
again.

84
00:03:49,560 --> 00:03:52,620
And notice that we still
don't have anything.

85
00:03:52,620 --> 00:03:57,050
This is actually
a caveat of IS-IS.

86
00:03:57,050 --> 00:04:02,030
We have to tell RIP which
level to pull the routes from.

87
00:04:02,030 --> 00:04:05,750
Just like redistributing
into IS-IS,

88
00:04:05,750 --> 00:04:09,140
we're going to have to tell it
where to get the routes from,

89
00:04:09,140 --> 00:04:11,630
and the default is level 2.

90
00:04:11,630 --> 00:04:15,080
So we're going to have to
say we could either just

91
00:04:15,080 --> 00:04:16,640
say level 1 here,
or we could say

92
00:04:16,640 --> 00:04:19,260
level 1-2 to get everything.

93
00:04:19,260 --> 00:04:21,560
And now that we're
doing that, now

94
00:04:21,560 --> 00:04:24,670
let's see if we have
routes on router 10.

95
00:04:24,670 --> 00:04:26,820
So now, we can see those
routes from the whole rest

96
00:04:26,820 --> 00:04:29,760
of the environment coming
in here on router 10.

97
00:04:29,760 --> 00:04:33,300
And just to pick on one, we'll
pick on this very bottom one,

98
00:04:33,300 --> 00:04:37,780
the 192.168.78.0/24.

99
00:04:37,780 --> 00:04:40,980
Few things to note-- number
1, there is no indicator

100
00:04:40,980 --> 00:04:42,090
that it's external.

101
00:04:42,090 --> 00:04:45,820
And notice that it has
that metric of 5 on there,

102
00:04:45,820 --> 00:04:47,820
which is the one we
told it to put on

103
00:04:47,820 --> 00:04:49,860
during the redistribution.

104
00:04:49,860 --> 00:04:52,740
And once again, just since we
have some mutual redistribution

105
00:04:52,740 --> 00:04:55,600
going on, let's try
some connectivity.

106
00:04:55,600 --> 00:04:57,800
So we could trace,
say, to that 88 address

107
00:04:57,800 --> 00:04:58,800
we've been using before.

108
00:04:58,800 --> 00:05:03,100

109
00:05:03,100 --> 00:05:05,250
So as you can see,
we have reachability

110
00:05:05,250 --> 00:05:07,240
here to say the 88 network.

111
00:05:07,240 --> 00:05:09,450
So generally speaking,
our connectivity

112
00:05:09,450 --> 00:05:12,680
appears to be working.

113
00:05:12,680 --> 00:05:17,210
In this video, we saw how to
do redistribution into RIP.

114
00:05:17,210 --> 00:05:21,170
And the main thing, of course,
to keep in mind is with RIP,

115
00:05:21,170 --> 00:05:24,650
the default seed
metric is infinite.

116
00:05:24,650 --> 00:05:27,530
And of course, that's going to
prevent it from sending routes.

117
00:05:27,530 --> 00:05:30,950
So we need to specify
a seed metric.

118
00:05:30,950 --> 00:05:34,400
Also, in the case of
redistributing from IS-IS,

119
00:05:34,400 --> 00:05:36,830
don't forget we
also need to specify

120
00:05:36,830 --> 00:05:41,160
which level routes we wish to
pull into the other protocol.

121
00:05:41,160 --> 00:05:46,020
So all of that said, we now have
just one more protocol to do--

122
00:05:46,020 --> 00:05:47,240
EIGRP.

123
00:05:47,240 --> 00:05:49,920
And that's exactly what
we're going to be doing next.

124
00:05:49,920 --> 00:05:51,060
Until then.

125
00:05:51,060 --> 00:05:53,120
I hope this has been
informative for you,

126
00:05:53,120 --> 00:05:56,170
and I'd like to thank
you for viewing.

127
00:05:56,170 --> 00:05:59,000