[c-nsp] Best practice for lowest convergence time when rebooting router
Gert Doering
gert at greenie.muc.de
Tue Oct 14 03:07:45 EDT 2008
Hi,
On Mon, Oct 13, 2008 at 11:01:01PM -0400, Jay Nakamura wrote:
> Quick question,
>
> Does anyone do anything special before rebooting/shutting down a core or
> border router so routes on other routers converge faster around the rebooted
> router? I was thinking if it would be better if I heavily BGP prepend to
> upstream first so bordering peer router will still route to me until the
> better route from the other upstream propagated to that peer. What about
> OSPF inside our network? Putting the interfaces in passive mode first?
What we do is:
- shutdown all eBGP sessions (but leave the interfaces "up") - so while
the control plane converges, packets can still travel via that router
[this could be made a bit smoother by prepending / de-local-pref'ing
the routes first, but shutting down the BGP session before bringing down
the interface is smoother already than hard reloading]
- make internal routing 'passive' on all but one interface - so the iBGP
sessions can still be up, but other routers won't consider this router
for packets, as there are not IGP paths "across" it
- reload
- wait for iBGP to come back and converge
- bring back eBGP
- bring back IGP
(now this is something why I'm really really really tempted to switch to
IS-IS, the "overload" bit, making the 'bootup smoothly' process automatic)
gert
--
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: 304 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20081014/3da1ab41/attachment.bin>
More information about the cisco-nsp
mailing list