From: Ronnie Angello (ronnie.angello@gmail.com)
Date: Tue Feb 24 2009 - 19:01:23 ARST
I would think that 'no default-information in' should work on the
router that's redistributing the static because it's redistributing
external information into the AS. I did lab this up and, as you said,
it does not work as expected. The default is marked as candidate on
the neighbor router. I verified that it has the D*EX designation.
Anyway, why would we want to redistribute a static default route if we
didn't want our neighbors to receive it anyway? Yes, I know... It's
the CCIE lab!
Is the requirement written "must not be received" or "must not be
used/installed in the neighbor routing table?" You could create a
summary on the neighbor router for 0.0.0.0/0 on a loopback interface
so that the discard route to null 0 is used instead of the external
route (because of AD of 5). That would make it so the neighbor would
not use the route or install it in its routing table, but technically
it does still receive it and puts it in the EIGRP topology table.
On Tue, Feb 24, 2009 at 12:09 PM, Robin.B <ro.betterley@gmail.com> wrote:
> Hello GS,
>
> My EIGRP has a default route being propagated via redistributed static. I
> understand that this is the nature of EIGRP process.
>
> I need to deny this default route from being received by my neighbors. Do not
> use any form of route-map or distribute-list. Can someone explain how should I
> place the "no default information-originate" ? I have tested it but it doesn't
> seems to achieve the result.
>
> Thanks in advance.
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- Ronald Angello CCIE 17846 CCDP, CCIP, CCNPBlogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:12 ARST