|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-8 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
SR Policies (RFC 9256) enable operators to steer traffic flows along preferred paths to satisfy KPIs such as lower latency, bandwidth guarantees, or traffic separation. When computed by a PCE, they provide PCE-driven path control that adapts to changes in network topology and traffic conditions. |
|
|
8 |
An SR Policy links traffic to one or more candidate paths, each defined by a list of Segment Identifiers (SIDs). The headend selects the active candidate path based on preference and constraints. |
|
|
9 |
A Path Computation Element (PCE) computes these paths using the topology learned through the IGP (IS-IS in our test) and interoperates with Path Computation Clients (PCCs) over the Path Computation Element Communication Protocol (PCEP) to set up and update them. The test covered multiple SR Policy scenarios, including PCC-initiated SR Policies, PCE-initiated SR Policies, PCC-initiated SR Policies delegated to the PCE, and SR Policy state reporting without delegation. In addition, SR Policy instantiation via a gRPC-based API was verified for the first time. |
|
|
10 |
Across these scenarios, SR Policy computation, signaling, and state reporting between the PCC and the PCE were verified. Where applicable, the correct installation of the SR Policy on the PCC was also verified, including the associated candidate paths and SID lists. |
|
|
11 |
The tests covered both SR-MPLS and SRv6 data planes, including SRv6 with full SIDs and µSID. In some test runs, latency was used as the optimization metric for path calculation. We also tested SR Policies with multiple candidate paths for redundancy, as well as candidate paths carrying multiple Segment Lists for multipath forwarding. |
|
|
12 |
|
|
|
13 |
[[~[~[Figure 51: SR-Policy Computation and Signaling using PCEP~>~>image:485744699445018625_SDN-1-1-v2.png~|~|alt="Figure 51" width="550"~]~]>>attach:485744699445018625_SDN-1-1-v2.png||target="_blank"]] |
|
|
14 |
|
|
|
15 |
The following tables show the device combinations that have interoperated this year. |
|
|
16 |
|
|
|
17 |
{{container cssClass="tc-role-table"}} |
|
|
18 |
(% class="table-bordered" %) |
|
|
19 |
|=PCE|=PCC|=Destination IP|=Notes |
|
|
20 |
|Cisco Crosswork Automation|Ciena 5164|IPv4|PCC-initiated LSP subsequently delegated to PCE |
|
|
21 |
|Cisco Crosswork Automation|HPE MX204|IPv4|PCC-initiated LSP subsequently delegated to PCE |
|
|
22 |
|Cisco Crosswork Automation|Keysight IxNetwork|IPv4|PCC-initiated LSP |
|
|
23 |
|Keysight IxNetwork|Ciena 5164|IPv4|PCC-initiated LSP |
|
|
24 |
|Keysight IxNetwork|Ciena 5164|IPv4|PCC-initiated LSP subsequently delegated to PCE |
|
|
25 |
|Keysight IxNetwork|HPE MX204|IPv4|PCC-initiated LSP |
|
|
26 |
|ZTE ZENIC ONE R22|Cisco 8201-24H8FH|IPv4|PCC-initiated LSP |
|
|
27 |
|ZTE ZENIC ONE R22|HPE MX204|IPv4|PCC-initiated LSP |
|
|
28 |
|
|
|
29 |
Table 3: PCC-initiated SR-Policy over SR-MPLS |
|
|
30 |
{{/container}} |
|
|
31 |
|
|
|
32 |
{{container cssClass="tc-role-table"}} |
|
|
33 |
(% class="table-bordered" %) |
|
|
34 |
|=PCE|=PCC|=Destination IP|=Notes |
|
|
35 |
|Cisco Crosswork Automation|HPE MX204|IPv4|PCC-initiated LSP subsequently delegated to PCE |
|
|
36 |
|Cisco Crosswork Automation|HPE PTX10002-36QDD|IPv6|PCC-initiated LSP |
|
|
37 |
|Cisco Crosswork Automation|Keysight IxNetwork|IPv6|PCC-initiated LSP |
|
|
38 |
|Keysight IxNetwork|HPE MX204|IPv6|PCC-initiated LSP |
|
|
39 |
|ZTE ZENIC ONE R22|HPE MX204|IPv6|PCC-initiated LSP |
|
|
40 |
|
|
|
41 |
Table 4: PCC-initiated SR-Policy over SRv6 µSID |
|
|
42 |
{{/container}} |
|
|
43 |
|
|
|
44 |
{{container cssClass="tc-role-table"}} |
|
|
45 |
(% class="table-bordered" %) |
|
|
46 |
|=PCE|=PCC|=Destination IP|=Notes |
|
|
47 |
|Cisco Crosswork Automation|Arista 7280R3|IPv4|PCE-initiated LSP |
|
|
48 |
|Cisco Crosswork Automation|HPE MX204|IPv4|PCE-initiated LSP |
|
|
49 |
|Cisco Crosswork Automation|Ribbon NPT-2507|IPv4|PCE-initiated LSP |
|
|
50 |
|Cisco Crosswork Automation|ZTE ZXR10 M6000-4SE|IPv4|PCE-initiated LSP |
|
|
51 |
|Keysight IxNetwork|Arista 7280R3|IPv4|PCE-initiated LSP |
|
|
52 |
|Keysight IxNetwork|Arista 7280R3|IPv4|PCE-initiated LSP with multiple candidate paths |
|
|
53 |
|Keysight IxNetwork|HPE MX204|IPv4|PCE-initiated LSP |
|
|
54 |
|Keysight IxNetwork|Ribbon NPT-2507|IPv4|PCE-initiated LSP |
|
|
55 |
|ZTE ZENIC ONE R22|Arista 7280R3|IPv4|PCE-initiated LSP |
|
|
56 |
|ZTE ZENIC ONE R22|Arista 7280R3|IPv4|PCE-initiated LSP; single candidate path with two segment lists (Multipath) |
|
|
57 |
|ZTE ZENIC ONE R22|Cisco 8201-24H8FH|IPv4|PCE-initiated LSP |
|
|
58 |
|ZTE ZENIC ONE R22|HPE MX204|IPv4|PCE-initiated LSP |
|
|
59 |
|ZTE ZENIC ONE R22|Ribbon NPT-2507|IPv4|PCE-initiated LSP |
|
|
60 |
|
|
|
61 |
Table 5: PCE-initiated SR-Policy over SR-MPLS |
|
|
62 |
{{/container}} |
|
|
63 |
|
|
|
64 |
{{container cssClass="tc-role-table"}} |
|
|
65 |
(% class="table-bordered" %) |
|
|
66 |
|=PCE|=PCC|=Destination IP|=Notes |
|
|
67 |
|Cisco Crosswork Automation|HPE MX204|IPv6|PCE-initiated LSP |
|
|
68 |
|Cisco Crosswork Automation|HPE MX204|IPv6|PCE-initiated LSP; path requested via northbound API |
|
|
69 |
|Keysight IxNetwork|ZTE ZXR10 M6000-4SE|IPv6|PCE-initiated LSP |
|
|
70 |
|ZTE ZENIC ONE R22|Cisco 8201-24H8FH|IPv6|PCE-initiated LSP |
|
|
71 |
|ZTE ZENIC ONE R22|HPE MX204|IPv6|PCE-initiated LSP |
|
|
72 |
|ZTE ZENIC ONE R22|HPE MX204|IPv6|PCE-initiated LSP; single candidate path with two segment lists (Multipath) |
|
|
73 |
|ZTE ZENIC ONE R22|Keysight IxNetwork|IPv4|PCE-initiated LSP |
|
|
74 |
|
|
|
75 |
Table 6: PCE-initiated SR-Policy over SRv6 µSID |
|
|
76 |
{{/container}} |
|
|
77 |
|
|
|
78 |
{{container cssClass="tc-role-table"}} |
|
|
79 |
(% class="table-bordered" %) |
|
|
80 |
|=PCE|=PCC|=Destination IP|=Notes |
|
|
81 |
|ZTE ZENIC ONE R22|Keysight IxNetwork|IPv6|PCE-initiated LSP |
|
|
82 |
|
|
|
83 |
Table 7: PCE-initiated SR-Policy over SRv6 Full SID |
|
|
84 |
{{/container}} |
|
|
85 |
|
|
|
86 |
{{container cssClass="tc-role-table"}} |
|
|
87 |
(% class="table-bordered" %) |
|
|
88 |
|=PCE|=PCC|=Destination IP|=Notes |
|
|
89 |
|Cisco Crosswork Automation|Arista 7280R3|IPv4|SR Policy configured via CLI on PCC and reported to PCE |
|
|
90 |
|Cisco Crosswork Automation|Ciena 5164|IPv4|SR Policy reported only; no PCE-initiated delegation |
|
|
91 |
|Cisco Crosswork Automation|Nokia 7750 SR-1|IPv4|One and two candidate paths tested |
|
|
92 |
|Cisco Crosswork Automation|Ribbon NPT-2507|IPv4|Single candidate path tested |
|
|
93 |
|Cisco Crosswork Automation|Ribbon NPT-2507|IPv6|Single candidate path tested |
|
|
94 |
|Keysight IxNetwork|Arista 7280R3|IPv4|SR Policy configured via CLI on PCC and reported to PCE |
|
|
95 |
|Keysight IxNetwork|Ribbon NPT-2507|IPv4|Single candidate path tested |
|
|
96 |
|Nokia Network Services Platform (NSP)|Arista 7280R3|IPv4|One and two candidate paths tested |
|
|
97 |
|Nokia Network Services Platform (NSP)|Arista 7280R3|IPv4|Single candidate path with two segment lists (Multipath) |
|
|
98 |
|Nokia Network Services Platform (NSP)|Ciena 5164|IPv4|Single candidate path tested |
|
|
99 |
|Nokia Network Services Platform (NSP)|Cisco 8201-24H8FH|IPv4|One and two candidate paths tested |
|
|
100 |
|Nokia Network Services Platform (NSP)|HPE MX204|IPv4|Single candidate path tested |
|
|
101 |
|Nokia Network Services Platform (NSP)|HPE MX204|IPv4|Single candidate path with two segment lists (Multipath) |
|
|
102 |
|Nokia Network Services Platform (NSP)|Keysight IxNetwork|IPv4|One and two candidate paths tested |
|
|
103 |
|Nokia Network Services Platform (NSP)|Keysight IxNetwork|IPv6|One and two candidate paths tested |
|
|
104 |
|Nokia Network Services Platform (NSP)|Ribbon NPT-2507|IPv4|One and two candidate paths tested |
|
|
105 |
|Nokia Network Services Platform (NSP)|ZTE ZXR10 M6000-4SE|IPv4|Single candidate path with two segment lists (Multipath) |
|
|
106 |
|ZTE ZENIC ONE R22|Nokia 7750 SR-1|IPv4|Single candidate path with two segment lists (Multipath) |
|
|
107 |
|ZTE ZENIC ONE R22|Nokia 7750 SR-1|IPv6|Single candidate path with two segment lists (Multipath) |
|
|
108 |
|ZTE ZENIC ONE R22|Ribbon NPT-2507|IPv4|Single candidate path tested |
|
|
109 |
|
|
|
110 |
Table 8: Reported Only SR-Policy over SR-MPLS |
|
|
111 |
{{/container}} |
|
|
112 |
|
|
|
113 |
{{container cssClass="tc-role-table"}} |
|
|
114 |
(% class="table-bordered" %) |
|
|
115 |
|=PCE|=PCC|=Destination IP|=Notes |
|
|
116 |
|Cisco Crosswork Automation|Nokia 7750 SR-1|IPv6|One and two candidate paths tested |
|
|
117 |
|Cisco Crosswork Automation|ZTE ZXR10 M6000-4SE|IPv6|Over PCEPv6 |
|
|
118 |
|Nokia Network Services Platform (NSP)|Cisco 8201-24H8FH|IPv4|One and two candidate paths tested |
|
|
119 |
|Nokia Network Services Platform (NSP)|Cisco ASR-9901|IPv6|One and two candidate paths tested |
|
|
120 |
|Nokia Network Services Platform (NSP)|HPE MX204|IPv6|Single candidate path tested |
|
|
121 |
|Nokia Network Services Platform (NSP)|HPE MX204|IPv6|Single candidate path with two segment lists (Multipath) |
|
|
122 |
|Nokia Network Services Platform (NSP)|Keysight IxNetwork|IPv6|One and two candidate paths tested |
|
|
123 |
|ZTE ZENIC ONE R22|Cisco 8201-24H8FH|IPv6|Single candidate path tested |
|
|
124 |
|ZTE ZENIC ONE R22|Nokia 7750 SR-1|IPv6|One and two candidate paths tested |
|
|
125 |
|ZTE ZENIC ONE R22|Nokia 7750 SR-1|IPv6|Single candidate path with two segment lists (Multipath) |
|
|
126 |
|
|
|
127 |
Table 9: Reported Only SR-Policy over SRv6 µSID |
|
|
128 |
{{/container}} |
|
|
129 |
|
|
|
130 |
(% id="prev-next-links" %) |
|
|
131 |
|[[< Previous>>doc:Main.EANTC Transport & Cloud Networks Interop Test Report 2026.Orchestration and Automation.WebHome]]|[[Next ~>>>doc:SR-Policy Computation and Signaling using BGP-SR]] |
|
|
132 |
))) |
|
|
133 |
|
|
|
134 |
(% class="col-xs-12 col-sm-4 test-report-sidebar" %) |
|
|
135 |
((( |
|
|
136 |
{{box}} |
|
|
137 |
{{include reference="Main.EANTC Transport & Cloud Networks Interop Test Report 2026.Sidebar Nav"/}} |
|
|
138 |
{{/box}} |
|
|
139 |
))) |
|
|
140 |
))) |
