Skip to Content
Hide last authors
EANTC Bot 1.1 1 (% class="row" %)
2 (((
3 (% class="col-xs-12 col-sm-7 test-report-content" %)
4 (((
5 ----
6
EANTC Bot 3.1 7 When unexpected problems arise in the network, some good plans for rerouting are essential to ensure that services keep running smoothly. Network operators use algorithm-based forwarding rules to control how backup paths are selected, guaranteeing that rerouted traffic upholds the same service objectives as the primary route. This method benefits uninterrupted connectivity applications like real‐time collaboration or distance learning. Integrating such streamlined protection schemes enables consistent performance, simplifies engineering tasks, and enhances end‐user experiences by minimizing the impact of network failures.
8 The TI-LFA specification ensures that the node SIDs associated with a certain Flexible Algorithm (Flex-Algo) will be safeguarded by loop-free alternates, allowing rapid convergence when a link or node fails. In addition, it demands that these "repairs" computed by those standards should only consider node SIDs or adjacent SIDs related to FlexAlgo.
9 In this evaluation, we performed the TI-LFA test within a network that runs FlexAlgo 128 (which prioritizes paths with lower latency). After DUT detected a link failure on the primary path, automated traffic switching occurred quite rapidly to the alternate route under the strict definitions of Flex-Algo 128. It didn't default to a standard IGP alternative when making its path decision. Our measured failover times stayed almost always under the threshold of 50 ms, fully aligned with our sub-50-ms target for highly available services.
EANTC Bot 1.1 10
11 [[Figure 88: SR-MPLS TI-LFA with Flex-Algo >>image:433782674696503297_SRMPLS-22-TILFAFLEXALGO-Generic-11-v1.png||alt="Figure 88" width="550"]]
12
EANTC Bot 3.1 13 This test has generally confirmed the applicability of TI-LFA in protecting SR-MPLS networks under FlexAlgo constraints in fast reroute settings and adapting to link failures. We can ensure multi-vendor interoperability even in advanced SR deployments with minor changes, like merging routing capability into IGP advertisements.
EANTC Bot 1.1 14
15 {{container cssClass="tc-role-table"}}
16 (% class="table-bordered" %)
17 |=PE|=Spine|=Traffic Generator
18 |(((
19 Arista 7280R3,
20 Ciena 5134,
21 Ciena 8140 Coherent Metro Router,
22 H3C CR16000-M1A,
23 Huawei NetEngine 8000 M14,
24 Huawei NetEngine A816,
25 Juniper PTX10002-36QDD,
26 Nokia 7750 SR-1,
27 Ribbon NPT-2100
28 )))|(((
29 Arista 7280R3,
30 Juniper ACX7100-48L
31 )))|Keysight IxNetwork
32
33 Table 34: TI-LFA with Flex-Algo over SR MPLS - IS-IS
34 {{/container}}
35 (% id="prev-next-links" %)
36 |[[< Previous>>doc:SR-MPLS with IPv6 Control Plane (Flex-Algo)]]|[[Next ~>>>doc:5G xHaul design with SR MPLS]]
37 )))
38
39 (% class="col-xs-12 col-sm-5 test-report-sidebar" %)
40 (((
41 {{box}}
42 {{include reference="Main.Multi-Vendor MPLS & SDN Interoperability Test Report 2025.Sidebar Nav"/}}
43 {{/box}}
44 )))
45 )))