|
0:00:13
|
Our next topic here, we have
|
|
0:00:16
|
We talked a little bit about this
|
|
0:00:20
|
summary address command in order
|
|
0:00:25
|
There's also a couple different
|
|
0:00:29
|
with either the IP default network,
|
|
0:00:31
|
or the native advertisement
|
|
0:00:38
|
The reason that I mentioned
|
|
0:00:41
|
is that it can be confusing the way EIGRP
|
|
0:00:48
|
This is different than in RIP or OSPF where
|
|
0:00:55
|
This simply controls the Default
|
|
0:00:58
|
controls whether the router will accept
|
|
0:01:01
|
a default route, or whether it can
|
|
0:01:09
|
So, under the EIGRP process,
|
|
0:01:12
|
it means you will not accept an
|
|
0:01:18
|
If you say no Default Information Out, it means
|
|
0:01:23
|
you're not gonna continue to propagate it on.
|
|
0:01:26
|
Now, we talked a little bit about
|
|
0:01:29
|
previously in the general I routing session,
|
|
0:01:32
|
where originally, this came from
|
|
0:01:38
|
Because IGRP didn't support the
|
|
0:01:46
|
Now, the issue with this is
|
|
0:01:50
|
has to be something that is dynamically learned,
|
|
0:01:53
|
which implies it's not directly connected.
|
|
0:01:55
|
And it has to be a classful network.
|
|
0:01:59
|
So, for example, if we
|
|
0:02:05
|
who is connecting to BB3,
|
|
0:02:09
|
we are learning some prefixes in
|
|
0:02:14
|
Then, we could do redisrtibution
|
|
0:02:18
|
and as we do this, we could tag one
|
|
0:02:25
|
So, if we look at router 4,
|
|
0:02:27
|
and first, we'll run the RIP process
|
|
0:02:32
|
with that remote neighbor.
|
|
0:02:35
|
So, the network 204.12.10.0...
|
|
0:02:39
|
is running version 2.
|
|
0:02:43
|
We'll say No Auto-Summary.
|
|
0:02:46
|
We will redistribute EIGRP...
|
|
0:02:49
|
into RIP, and then under EIGRP,
|
|
0:02:54
|
And we'll use any arbitrary metric.
|
|
0:02:58
|
Now, if we look at the routing table
|
|
0:03:03
|
we have these networks that are part of the 30
|
|
0:03:09
|
If I were to tag one of these as the
|
|
0:03:17
|
when we now look at the routing table,
|
|
0:03:25
|
we see that the gateway of last resort
|
|
0:03:28
|
is the next hop value towards BB3
|
|
0:03:34
|
If we look at the 30 prefix,
|
|
0:03:39
|
which means that this is
|
|
0:03:44
|
Once this network is propagated
|
|
0:03:49
|
if we were to look at router 3,
|
|
0:03:53
|
we see that the asterisk will
|
|
0:03:59
|
So, we will use a default route
|
|
0:04:03
|
the path that the 30 network is following.
|
|
0:04:08
|
So, it's technically different here
|
|
0:04:14
|
but it has the same effect.
|
|
0:04:16
|
So, it means that however
|
|
0:04:22
|
this would be the same path
|
|
0:04:28
|
Again, we would have the same end
|
|
0:04:33
|
and say, "I'm just gonna advertise 0.0.0.0/0."
|
|
0:04:39
|
But this default network comes from
|
|
0:04:43
|
It only supported the flag and the update
|
|
0:04:49
|
Now, the actual 0.0.0.0 network, we saw previously
|
|
0:04:57
|
where in that case, we would automatically
|
|
0:05:02
|
because all networks are a subnet of /0.
|
|
0:05:06
|
So, anything /1 to /32, that's all a subnet of /0.
|
|
0:05:13
|
We could configure a manual static route
|
|
0:05:17
|
that points to an interface,
|
|
0:05:19
|
and then issue the network statement
|
|
0:05:23
|
So, this is what I was talking about previously with
|
|
0:05:31
|
If I were to go to router 4,
|
|
0:05:34
|
and remove the IP Default
|
|
0:05:38
|
we'll see that on router 3,
|
|
0:05:43
|
it says the gateway last resort is not set.
|
|
0:05:48
|
Now, on router 4, we'll configure a...
|
|
0:05:51
|
static default route.
|
|
0:05:54
|
I'll point it out Fast Ethernet
|
|
0:06:04
|
Now, under the EIGRP process,
|
|
0:06:12
|
If we look at router 3,
|
|
0:06:27
|
we should see here that
|
|
0:06:32
|
So, let's say Show Run
|
|
0:06:46
|
And let's Show IP Route...
|
|
0:06:49
|
Static. So, the static route is installed.
|
|
0:06:54
|
It has the asterisk which
|
|
0:06:58
|
If we Show IP EIGRP Topology,
|
|
0:07:12
|
and we don't see the prefix in there.
|
|
0:07:26
|
Let's try this under the process.
|
|
0:07:32
|
I believe this is gonna show
|
|
0:07:36
|
But we should have in
|
|
0:07:43
|
which we don't.
|
|
0:07:44
|
The other option here would
|
|
0:07:56
|
Which now, we can see,
|
|
0:08:00
|
The difference though is that now,
|
|
0:08:04
|
So, which show up as
|
|
0:08:12
|
but this syntax should work. I'm wondering
|
|
0:08:19
|
Let me remove the next hop.
|
|
0:08:23
|
And let's try it just with the...
|
|
0:08:27
|
the interface.
|
|
0:08:31
|
So then, under the routing process,
|
|
0:08:42
|
And now, it is installed.
|
|
0:08:44
|
And it's installed from us.
|
|
0:08:46
|
So, it says... What's kind of interesting about
|
|
0:08:53
|
From redistribute static.
|
|
0:08:55
|
But the route type is internal.
|
|
0:08:58
|
So, if we were to look at router 3,
|
|
0:09:04
|
notice that it is an internal
|
|
0:09:11
|
As opposed to when we did Redistribute Static,
|
|
0:09:14
|
that would be an external EIGRP
|
|
0:09:20
|
Now, the only time that this is really gonna
|
|
0:09:25
|
One that was an external route;
|
|
0:09:30
|
you would always prefer the
|
|
0:09:34
|
Simply based on the administrative distance.
|
|
0:09:37
|
So, if we look at the difference
|
|
0:09:40
|
under router 4, if we Show
|
|
0:09:45
|
or Router EIGRP, or...
|
|
0:09:48
|
Network 0.
|
|
0:09:53
|
So, this is advertising the static
|
|
0:09:59
|
As opposed to going under the
|
|
0:10:06
|
instead, we will just redistribute static routes
|
|
0:10:11
|
with whatever metric we want.
|
|
0:10:14
|
Now, when we look at this on router 3,
|
|
0:10:17
|
it's gonna see this as an external....
|
|
0:10:24
|
EIGRP route, not an internal route.
|
|
0:10:54
|
So let's see, router 3 says, "This is
|
|
0:11:06
|
Which in our topology is switch 1.
|
|
0:11:14
|
Then, let's see who is switch 1
|
|
0:11:24
|
That's coming from 6,
|
|
0:11:32
|
and then,6 is learning it from 4.
|
|
0:11:40
|
4 says it's directly connected via static.
|
|
0:11:45
|
if we look under th EIGRP process,
|
|
0:11:51
|
I no longer have the...
|
|
0:11:56
|
the network command that's matching 0.0.0.0,
|
|
0:12:01
|
When we look in the topology for 0.0.0.0,
|
|
0:12:09
|
this one says that the route type is internal.
|
|
0:12:15
|
So, it's kind of a strange result, because
|
|
0:12:20
|
it's still counting the prefix as internal route,
|
|
0:12:24
|
because it's coming from a directly
|
|
0:12:29
|
If the static route pointed
|
|
0:12:32
|
it would be treated differently.
|
|
0:12:34
|
Likewise, if we were learning
|
|
0:12:37
|
and then redistributing RIP into EIGRP,
|
|
0:12:41
|
then, the default would show up as external.
|
|
0:12:45
|
But again, in the end, it really doesn't
|
|
0:12:50
|
The only case that you would
|
|
0:12:55
|
was advertising the default as internal,
|
|
0:12:59
|
then, somewhere else let's say on router 2,
|
|
0:13:10
|
the one that router 4 is originating
|
|
0:13:14
|
because that has an internal
|
|
0:13:16
|
versus the external distance of 170.
|