[j-nsp] Krt queue issues
JTyler at fiberutilities.com
Wed Oct 3 14:45:13 UTC 2012
Look into Static route retain. Should keep the route in the forwarding table.
>From Jniper site
By default, static routes are not retained in the forwarding table when the routing process shuts down. When the routing process starts up again, any routes configured as static routes must be added to the forwarding table again. To avoid this latency, routes can be flagged as retain, so that they are kept in the forwarding table even after the routing process shuts down. Retention ensures that the routes are always in the forwarding table, even immediately after a system reboot.
Sr Engineering Manager
Fiberutilities Group, LLC
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Benny Amorsen
Sent: Wednesday, October 03, 2012 8:32 AM
To: Jared Mauch
Cc: Saku Ytti; juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Krt queue issues
Jared Mauch <jared at puck.nether.net> writes:
> As far as the fallback 'default' route, if you are purchasing transit
> from someone, you could consider a last-resort default pointed at
> them. You can exclude routes like 10/8 etc by routing these to discard
> + install on your devices.
That only helps if the default gets installed first, though. If the default has to wait at boot in the krt-queue behind the 300k+ Internet-routes, I have not really gained anything...
I suppose it is likely that a static default would be installed before the BGP sessions even come up.
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the NANOG