|
0:00:13
|
Next, let's take a look at how RIP
|
|
0:00:18
|
with the Interface Level
|
|
0:00:22
|
Now, there's two requirements that we need to be
|
|
0:00:29
|
is that in order to generate the
|
|
0:00:32
|
we need to make sure first that there is
|
|
0:00:37
|
So, if I have two /25 networks and
|
|
0:00:43
|
it means that at least one of those /25's
|
|
0:00:48
|
So, I would need a corresponding
|
|
0:00:52
|
or some other method,
|
|
0:00:56
|
Secondly, we cannot summarize in RIP
|
|
0:01:04
|
So that means that if we were to have...
|
|
0:01:06
|
Let's say...
|
|
0:01:08
|
Four class C networks that were...
|
|
0:01:14
|
192.168.0.0/24,
|
|
0:01:22
|
192.168.1.0/24, 2.0 and 3.0.
|
|
0:01:33
|
Ideally, we could summarize
|
|
0:01:43
|
If we look at the third
|
|
0:01:47
|
In this first prefix, in binary,
|
|
0:01:55
|
The second one we
|
|
0:02:00
|
Third one 0000 0010
|
|
0:02:05
|
and then, 0000 0011
|
|
0:02:09
|
So this means that in the third octet,
|
|
0:02:18
|
So, we have 8 plus 8 plus 6.
|
|
0:02:24
|
So, we could have 192.168.0.0/22.
|
|
0:02:30
|
So, this is a perfectly valid summary.
|
|
0:02:33
|
The problem is with RIP, when
|
|
0:02:37
|
it's gonna tell us this is not supported because
|
|
0:02:42
|
In this case, all four of these
|
|
0:02:48
|
where the major network
|
|
0:02:52
|
So, with RIP's implementation,
|
|
0:02:56
|
with the summarization command itself.
|
|
0:03:00
|
Now, there are some workarounds
|
|
0:03:03
|
We could do like a static route to null
|
|
0:03:07
|
So, RIP does support the
|
|
0:03:12
|
So, any prefix and any prefix length.
|
|
0:03:15
|
Just for whatever reason in the actual
|
|
0:03:19
|
it has an error check that is not gonna
|
|
0:03:27
|
So, if we were to look
|
|
0:03:29
|
let's say, between the...
|
|
0:03:34
|
switch 1 and switch 3,
|
|
0:03:37
|
I want to aggregate their
|
|
0:03:40
|
So, switch 1 has 150.10.7.0/24,
|
|
0:03:46
|
where switch 3 has 150.10.9.0/24.
|
|
0:03:54
|
So, I wanna take these two loopbacks and
|
|
0:03:59
|
Then, on switch 1, I'm gonna
|
|
0:04:03
|
The link to router 6 and
|
|
0:04:07
|
So now, I need to know first,
|
|
0:04:09
|
What is the summary that's
|
|
0:04:15
|
So, I have 150.10.7.0, 150.10.9.0.
|
|
0:04:23
|
So, 7 in binary is gonna be what?
|
|
0:04:29
|
It's gonna be a 4, a 2, and a 1.
|
|
0:04:35
|
So 1 in a 2 is 3 and a 4 is 7.
|
|
0:04:40
|
So, followed by five 0's.
|
|
0:04:45
|
Then, a 9...
|
|
0:04:49
|
is gonna be what?
|
|
0:04:52
|
It's gonna an 8 and a 1.
|
|
0:04:54
|
So, 0000 1001
|
|
0:05:02
|
So, that's an 8 and a 1, which
|
|
0:05:06
|
we have /16 to start then 17, 18, 19, 20.
|
|
0:05:13
|
So, I could say 150.10. what?
|
|
0:05:21
|
So, I know it's gonna be /20, what would
|
|
0:05:28
|
If this is /20.
|
|
0:05:33
|
So, we're excluding the...
|
|
0:05:38
|
Firts four bits, it would be whatever
|
|
0:05:43
|
So, it would actually be 0000.
|
|
0:05:45
|
So, the 150.10.0.0/20.
|
|
0:05:50
|
So, configuration wise, this is just pretty
|
|
0:05:54
|
the device we wanna do
|
|
0:05:56
|
Look at the Show IP Route Connected,
|
|
0:05:59
|
and I wanna do this on my VLAN 67,
|
|
0:06:04
|
And on my Fast Ethernet 0/3,
|
|
0:06:10
|
So, on fa0/3, we'll say,
|
|
0:06:15
|
Or IP...
|
|
0:06:19
|
IP Summary Address RIP.
|
|
0:06:21
|
150.10.0.0.255.255. what?
|
|
0:06:33
|
240 right?
|
|
0:06:39
|
If we do this on VLAN 67 as well,
|
|
0:06:45
|
then, look at the result of
|
|
0:06:48
|
If I were to go on router 3 and say, what is now
|
|
0:06:57
|
So, the 150.10.7.7 and 150.10.9.9.
|
|
0:07:03
|
Once the old information
|
|
0:07:07
|
and I can do this just by
|
|
0:07:13
|
We see now, the longest match is
|
|
0:07:23
|
One way to check here whether
|
|
0:07:27
|
is to look at the Show I Route
|
|
0:07:30
|
and then, whatever the final destination
|
|
0:07:34
|
So, in this case, it was
|
|
0:07:40
|
Both of these are match
|
|
0:07:44
|
So, I know the summary is
|
|
0:07:49
|
If we go farther,
|
|
0:07:52
|
and let's say I wanna know what is the last
|
|
0:08:00
|
If I look at the route to 150.10.16.0,
|
|
0:08:10
|
but one bit less, 15.255,
|
|
0:08:18
|
So, this means that
|
|
0:08:22
|
is encompassing the address as
|
|
0:08:33
|
Because it's a /20.
|
|
0:08:38
|
So, pretty straightforward
|
|
0:08:40
|
assuming that you do the calculation
|
|
0:08:44
|
then, it's simply just the IP
|
|
0:08:49
|
Again, the usual comes in when we try
|
|
0:08:54
|
or pass the major network boundary.
|
|
0:08:56
|
So, if I were to go in any of these interfaces
|
|
0:09:10
|
it's not gonna allow me to do that.
|
|
0:09:12
|
So, the summary mask must be
|
|
0:09:15
|
which in this case, the
|
|
0:09:21
|
Now, I could technically workaround this
|
|
0:09:24
|
if I just configure some routes statically
|
|
0:09:29
|
So, I could say on switch 1 that the prefix
|
|
0:09:38
|
So, I'm just using this
|
|
0:09:41
|
Then, under the RIP process, router RIP.
|
|
0:09:48
|
I'll say, Redistribute Static, and then,
|
|
0:09:55
|
So no, if I were to look at router 3,
|
|
0:09:59
|
one of the connected neighbors,
|
|
0:10:10
|
We see, the summary 150...
|
|
0:10:13
|
150.0.0.0/8 is learned.
|
|
0:10:17
|
So, it's not a restriction of the
|
|
0:10:21
|
It's simply that the way the summary
|
|
0:10:26
|
there's a check in the parser that says,
|
|
0:10:34
|
But again, we got around
|
|
0:10:37
|
the device where we wanna
|
|
0:10:40
|
use the static route to
|
|
0:10:43
|
and then, we're redistributing the syn.
|