From: EA Louie (elouie@xxxxxxxxx)
Date: Thu Dec 13 2001 - 16:55:19 GMT-3
> I would argue that an OSPF/EIGRP summary route is more of a "static
> violation" than the examples you mentioned seeing as they both install
> routes to null0. Default information-originate does not, to my knowledge,
> affect the local routing table- it is the neighbors that learn a 0.0.0.0/0
> back to the advertising router.
>
Check again - I *believe* it introduces a gateway of last resort on the
sourcing router, but I could be mistaken. I'll verify when I get home
tonight.
> I feel that the improper use of ip-default network, which creates a
static
> route in the configuration, is a trap that will be intentionally laid in
the
> CCIE lab. Anyone expecting to emerge with a number should know how to
> overcome this issue.
>
True - if it's configured incorrectly, a static route gets installed in the
configuration, which can't be distinguished from a static route that's
entered manually.
> > In some of my practice labs I have of course seen the phrase do not use
> > any statics to accomplish goals in this lab unless specifically
> > specified to do so.
> >
> > In some of these instances the only way to make some of it work is to
> > either use the IP DEFAULT-NETWORK command ( Which of course creates a
> > static route, or use the DEFAULT-INFORMATION ORIGINATE ( Which is also
> > sort of a static injected type route.).
>From a static route perspective, although there are commands that inject
routes into the routing table (i.e. null0 routes), as long as it doesn't
show up as a static IN THE RUNNING CONFIGURATION I'd say you're fine. Thus,
default originate etc. are ways to inject the 0.0.0.0 route without a static
route configured. I believe that is the intent of the 'no static route'
restriction - to challenge us to find other methods to inject that
default/summary route.
In real life, I prefer to have the static route in the config, because it's
documentation that most people (who understand) can comprehend. Otherwise,
it gets hidden in an interface summary route statement or within the routing
protocol configuration.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:32:43 GMT-3