Feature #9141
open
- Priority changed from Normal to Very Low
There is no sync in Quagga or OpenBGPD either.
AFAIR it was done deliberately since in nearly all cases it would be an error to run an identical configuration on two routers running a routing protocol. You'd want separate feeds/connections to neighbors and to work out the failover using priorities/cost/etc in the routing protocols.
It can monitor a CARP VIP for status to stop/start but that's a bit of a kludge.
Might get around to it eventually but it might cause more problems than it fixes.
To understand the set up then.
nodeA and nodeB will have sepearate routing neighbors probably exchanging the same route. Selecting nodeA as primary for routing purposes would include as metioned cost/local-pref or whatever it is for the protocol.
Downstream nodeA and nodeB will be in HA with the LAN assuming no dynamic neighbors needed.
If so makes sense just added complexity
In simple setups like mine I believe having the same BGP configuration on both Primary and Secondary members is what is required. The FRR Global configuration already has provision to monitor CARP status of a selected IP (vhid) and run the daemon only on primary.
No progress here obviously, just wanted to add that in the mean time I'm using a workaround: every time i change something on the primary GUI I transfer the raw FRR running config onto the standby cluster (as saved config).
Just following up to see if there is any progress.
In theory there isn’t really a good reason to not have the configs sync’s.
The more I thought about it the more nonsensical it is to not have this ability to sync FRR configs. If I am in a HA setup with the same feeds coming in, only one firewall would have the FRR daemon running. This works similarly to PanOs and JUNOS in that the secondary node in standby does not form a routing relationship.
The config sync here should happen. No good reason to not do it
Also available in: Atom
PDF
Updated by 
Updated by Viktor Gurov 
Updated by 
Updated by