Hello, Graceful restart allows not to flush the routes until the sessions are reestablished and converged, it does not save bgp internal state. And when the session is reestablished, the peers do initial exchange of their routes as with a fresh start, what you can see in your mrtdump. That is expected way of how things work. You might want the peers to somehow remember the state before the old BGP session disconnects and continue updates from that point later. But as far as I know, there are no standard mechanisms for that. Regards, Alexander On Fri, Jan 5, 2024 at 9:56 AM Ioannis Paterakis <jpat@codebgp.com> wrote:
Hello,
I have a bird setup with graceful restart enabled on kernel and bgp protocols. It seems to work fine.
My wonder is that despite the fact that graceful restart functionality persists the route tables during a broken bgp session, when the bgp session gets re-established the mrtdump protocol which is enabled as well dumping updates on a file gets filled with all the routes that are already present. Is there a way to prevent this from happening ?
Best wishes to everyone for 2024!
IP