|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-7 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
Current network infrastructures, mainly for 5G services, employ differentiated traffic handling given constraints such as delay requirements, bandwidth, or path availability. In most cases, shortest‐path routing does not always evenly load the link traffic, causing congestion on critical links. Therefore, RFC 9350 introduced Flexible Algorithm (Flex‐Algo), which allows operators to proactively “slice” the network into multiple planes, each with their own routing rules and metrics. In our testing, we considered using three Flex‐Algo definitions—FA128, FA129, and FA130 to show different routing requirements. The FA128 prioritized paths with lower latency by using static or dynamic delay measurements to assess the path. The FA129 optimized traffic engineering (TE) metrics to balance link utilization among the available multiple links. Finally, we used FA130, which leveraged link affinities (or “colors”), a constraint that excludes certain links in the path computation. These enhancement measures are possible only because each node or router advertises its algorithm capabilities through the IGP. In IS-IS, these are presented in additional sub-TLVs and/or Application-Specific Link Attributes(ASLA) and assigned prefix SIDs mapped to the given Algorithm ID, making it possible to construct a novel logical topology given the constraints of the router. As defined in all three conditions, the routers successfully created paths and correctly installed them on MPLS forwarding tables, allowing end-to-end traffic to pass. This test confirms that Flex-Algo enables operators to deliver a good performance and resilience service class and simplifies configuration in SR‐MPLS environments. |
|
|
8 |
|
|
|
9 |
[[Figure 85: SR-MPLS Flexible Algorithm>>image:434086832502931457_SRMPLS-13-FlexAlgo-Generic-7-v1.png||alt="Figure 85" width="550"]] |
|
|
10 |
|
|
|
11 |
{{container cssClass="tc-role-table"}} |
|
|
12 |
(% class="table-bordered" %) |
|
|
13 |
|=PE|=Spine|=Traffic Generator |
|
|
14 |
|((( |
|
|
15 |
Arista 7280R3, |
|
|
16 |
Arrcus S9610-36D, |
|
|
17 |
Ciena 5134, |
|
|
18 |
Ciena 8140 Coherent Metro Router, |
|
|
19 |
H3C CR16000-M1A, |
|
|
20 |
Huawei NetEngine 8000 M14, |
|
|
21 |
Huawei NetEngine A816, |
|
|
22 |
Juniper ACX7024, |
|
|
23 |
Juniper PTX10002-36QDD, |
|
|
24 |
Keysight IxNetwork, |
|
|
25 |
Nokia 7750 SR-1, |
|
|
26 |
Ribbon NPT-2100 |
|
|
27 |
)))|((( |
|
|
28 |
Arista 7280R3, |
|
|
29 |
Juniper ACX7100-48L |
|
|
30 |
)))|Keysight IxNetwork |
|
|
31 |
|
|
|
32 |
Table 30: SR-MPLS Flexible Algorithm - IS-IS |
|
|
33 |
{{/container}} |
|
|
34 |
(% id="prev-next-links" %) |
|
|
35 |
|[[< Previous>>doc:Optical Networks Using 400ZRZR+ -800ZRZR+ Optical Plugs]]|[[Next ~>>>doc:SR-MPLS Flexible Algorithm using new constraints (excl\. Min Bandwidth, Max\. delay and Reverse affinity)]] |
|
|
36 |
))) |
|
|
37 |
|
|
|
38 |
(% class="col-xs-12 col-sm-5 test-report-sidebar" %) |
|
|
39 |
((( |
|
|
40 |
{{box}} |
|
|
41 |
{{include reference="Main.Multi-Vendor MPLS & SDN Interoperability Test Report 2025.Sidebar Nav"/}} |
|
|
42 |
{{/box}} |
|
|
43 |
))) |
|
|
44 |
))) |
