[c-nsp] Delayed IGP default-originate?

Gert Doering gert at greenie.muc.de
Mon Nov 23 16:58:19 EST 2009


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                             gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 305 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20091123/10033edd/attachment-0001.bin>


More information about the cisco-nsp mailing list