From: Jonathan V Hays (jhays@jtan.com)
Date: Thu Nov 20 2003 - 18:53:34 GMT-3
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
JamesGEF
Sent: Thursday, November 20, 2003 4:19 PM
To: Jonathan V Hays; ccielab@groupstudy.com
Subject: Re: IPExpert Labs
Hi Jonathan, you're absolutely right about the route being an External.
That's why I mentionned it being a pain when mutually redistributing
into
RIP (EIGRP EX routes have higher admin distance than RIP).
But my question is if you want that network to be part of the EIGRP AS
and
don't want EIGRP packets going to that specific interface, you could
either
redistribute it as a connected or include it in your network statement
and
make that interface passive.
The latter requires less configuration and that is ultimate
question....If
not explicitly mentionned, why do all the IPExpert labs redistribute
their
connected networks rather than include them in the network statements
and
make the interface passive.
James
======
James,
You say "you want that network to be part of the EIGRP AS" but if you
"redistribute connected" then by definition it will NOT be a part of the
EIGRP AS. The fact is EIGRP will see the route as a FOREIGN protocol, a
non-EIGRP route. That is what is meant by "external."
You can actually inject a route as a native EIGRP route several ways.
Let's say you want to advertise 10.1.1.0/24 and only out ethernet 0.
Here's a few, and they don't all have the exact same effect.
router eigrp 1
network 10.0.0.0
passive-interface default
no passive-interface ethernet 0
no auto-summary
router eigrp 1
network 10.1.1.0 0.0.0.255
router eigrp 1
network 10.1.1.0 0.0.0.255
neighbor 10.1.1.2
But again, when you do this:
router eigrp 1
redistribute connected metric 10000 100 255 1 1500
you are telling EIGRP, "here is a non-EIGRP route that I am injecting
into EIGRP. Go ahead and tell other EIGRP routes about it, but make sure
you let them know it is NOT an EIGRP route."
HTH,
Jonathan
This archive was generated by hypermail 2.1.4 : Fri Dec 12 2003 - 12:29:15 GMT-3