Hi Douglas,

On Thu, Oct 29, 2026 at 06:34:19AM -0300, Douglas Fischer wrote:

[…] “BGP Session Stateful Failover across multiple BIRD instances” […]

I should mention upfront that I am not aware if this functionality already exists in BIRD (or any other open-source routing daemon).

There is nothing like this in BIRD, for now.

The goal is to optimize availability in a scenario where BGP sessions are disaggregated from the actual forwarding boxes.

Is there any real advantage of this over simply setting up several BGP sessions to different unicast addresses?

Scenario 1—the most basic one—is straightforward: - Each node is configured with 100% of the peers and their respective policies. - Metrics, such as IGP cost, determine which Anycast instance a given BGP client connects to. - These nodes handle the BGP heavy lifting—managing route exchanges and applying filters for the downstream peers. - They then propagate these routes to the forwarding devices, providing them in the most streamlined (filtered/optimized) form possible.

Are you looking for a failover or for load balancing?

The problem arises when an event causes a specific set of downstream clients to switch from one Route Reflector (RR) node to another. […] The conclusion I’ve reached is that the healthiest approach would be for a BGP session to be resumed from a different node, in such a way that the BGP client remains unaware that this has occurred.

I’m kinda afraid that resuming long-lived TCP sessions from a different node is quite a crazy thing to try to achieve.

[…] I am aware that “graceful restart” is a prerequisite for this kind of implementation.

I would say it’s orthogonal. Graceful restart is useful for situations where the BGP session ends.

I imagine it would require some form of copying or replication of the active BGP session state table to the nodes that are currently in a passive state.

You would have to migrate:

Logically, this would also likely necessitate a quorum mechanism to determine which node is the active one.

All this while possibly actively transferring route data.

I would welcome any guidance or suggestions as to whether you have encountered a solution for this issue.

All possible solutions ended with the same conclusion – it is theoretically possible to do it but you get way more complications than feasible, at least for now.

Yet, we do expect that it should be possible to export all relevant data from BIRD via the upcoming CORECONF API, even by streaming, and it may be possible to hook this functionality onto that. Theoretically we may achieve flapless BIRD upgrade later with this.

Do you have any specific large-scale business deployment for which you somehow need this to work? If yes, please contact me off-list and we’ll figure something out.

P.S.1: I suspect that companies like Google and AWS, which utilize disaggregation in their peering scenarios, likely already implement some form of stateful failover for BGP sessions across multiple boxes.

I have no idea about that and I would expect that they have their own BGP implementation completely tailored for their business.

–
Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.