Hi, On Mon, Nov 23, 2009 at 10:29:24AM -0800, Kevin Graham wrote: > Similar to Gert's question on on delayed eBGP startup, is there a good way > to delay IGP default-route generation?
I'm not sure if it helps for the "default-route" case, but you could try
"max-metric router-lsa on-startup 300" (under "router ospf ...").
This is similar to the ISIS overload bit - for the first 300 seconds,
OSPF will announce bad metrics, so that no other router will voluntarily
pick a path through the newly-booted router (if another path exists).
Loopbacks work, since there is no other path.
But as I said, I'm not sure if that works for default-route origination
as well.
gert
PS: this is one of my *other* problems - we use EIGRP for "carry loopback"
(which has much nicer fast-convergence properties than OSPF and ISIS
built right in...), and it has no similar mechanism, as far as I know.
*grumble at Cisco*.
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]
fax: +49-89-35655025 [email protected]
pgpDaY85FJ1D5.pgp
Description: PGP signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
