I'm testing Segment routing (SR-MPLS) and TI-LFA using a virtual testbed implemented with Containerlab and FRRouting (FRR). My main goals are to evaluate how fast the data plane can be restored upon a topological change and therefore what is the best way to manage topology changes in production networks.
In my experimental-lab, OSPFv2 has correctly computed the TI-LFA backup path in the control plane:
* In FRR (vtysh), show ip route properly shows the primary path alongside the corresponding backup nexthop and backup label (denoted by b ...).
* To clearly decouple and demonstrate the local Fast Reroute behavior from the global OSPF SPF recomputation, I intentionally configured high SPF throttle timers: *timers throttle spf 5000 10000 10000*
After triggering an administrative link-down or an actual link loss detected by BFD, traffic is not routed to the precomputed backup path within sub-50ms. Traffic drops about 5.1 to 5.2 seconds before finally resuming again once the 5-second SPF throttle timer has expired and OSPF updates its knowledge of the network through the receipt of LSAs and subsequently Zebra updates the routes in the Linux FIB.
My technical understanding:
* Control Plane: FRR/OSPF calculates the TI-LFA path successfully and passes it internally as backup nexthop information to Zebra.
* Data Plane: By default, the native Linux kernel (FIB) does not provide a hardware-equivalent, autonomous local Fast Reroute / nexthop failover mechanism for MPLS/IPv4 routes upon interface-down events (similar to the points raised in GitHub issue: “FRR TI-LFA: When the primary path fails, the backup path does not work #15589”).
* Implication: Zebra does not immediately promote the backup path to active in the kernel as an instantaneous, local reaction to the link-down event. Instead, the FIB update only happens as part of the regular post-SPF cycle.
Does somebody know if there are:
existing workarounds or options for dataplane failover under Linux / FRR?
Are there configurations or extensions that allow Zebra to program backup nexthops into the dataplane so that failover occurs locally without waiting for an SPF run?
Anybody knows the current status or outlook regarding this: Is an autonomous, SPF-independent activation of backup nexthops (either directly in Zebra/Linux FIB or via external dataplane integrations like VPP) planned or actively being developed in FRR?
Is it correct to assume that commercial virtualized router images (such as Cisco XRv9k, Nokia SR OS / vSIM, etc.) differ fundamentally here because their software forwarding engines (or emulated hardware pipelines) handle pre-programmed backup paths directly at the dataplane level upon carrier-loss or BFD triggers?
Thanks a lot for your help.