If there was a graceful restart, that would probably work fine. However, I've read several times on the lists that there is no such thing for Quagga. If we do a graceful shut down and then start again, traffic will drop during that short period of time when the routes are removed, until OSPF learns the routes again and re-inserts them.
Why is everyone dancing around the main question here...which is: Why did someone decide to remove the code that filters out kernel routes that were put there by zebra, before they are put into the RIB? What benefit is there in removing that? These routes are inserted into the kernel with the proper flag, and they are detected as zebra routes when zebra starts up, but someone removed (actually commented out) the function that removes them from the kernel route list before inserting into zebra's RIB. My guess is that it was unintentional (hence it being commented out), either it was meant to be put back or someone didn't understand what it was doing. -Nate On Wed, Nov 16, 2016 at 3:24 PM, Mike Tancsa <m...@sentex.net> wrote: > On 11/16/2016 1:49 PM, Nathan Baker wrote: > > > > If you could suggest the proper way to restart zebra that would be > > appreciated. However, that would still not be ideal because the routes > > Not sure why they use a kill -9 to shut it down. If you gracefully shut > down bgpd ospfd and the zebra, the routes are all properly withdrawn. > You could also do a route flush before starting the quagga daemons. > > ---Mike > > > -- > ------------------- > Mike Tancsa, tel +1 519 651 3400 > Sentex Communications, m...@sentex.net > Providing Internet services since 1994 www.sentex.net > Cambridge, Ontario Canada http://www.tancsa.com/ >
_______________________________________________ Quagga-users mailing list Quagga-users@lists.quagga.net https://lists.quagga.net/mailman/listinfo/quagga-users
