Show last authors
1 (% class="row" %)
2 (((
3 (% class="col-xs-12 col-sm-8 test-report-content" %)
4 (((
5 ----
6
7 Segment Routing Traffic Engineering (SR-TE) refers to the computation and installation of constraint-based Segment Lists used to steer traffic along optimized paths. SR Policies provide the general framework for associating traffic with one or more candidate paths, while SR-TE specifically focuses on computing paths that satisfy explicit traffic-engineering constraints. In deployments with a centralized controller, a Path Computation Element (PCE) can compute such paths based on a global view of the network topology. This enables the instantiation of paths that meet requirements such as disjointness, affinity constraints, or cumulative metric bounds, which cannot always be efficiently solved by local router-based computation alone.
8
9 In this test, we verified the interoperability between the PCE and PCC of the SR-TE computation and signaling workflow.
10 We covered both PCE-initiated SR-TE and PCC-initiated, delegated SR-TE over PCEP. In the delegated scenarios, the headend router requested path computation from the PCE and installed the returned Segment Lists. The validation used SR-MPLS as the primary dataplane, with additional runs over SRv6-µSIDs.
11 The primary constraint used in the test runs was delay. The PCE computed paths that minimized end-to-end latency, and in selected scenarios, a delay bound was applied. In those cases, a path was considered valid only if its cumulative delay remained below a configured threshold. In all scenarios, the PCC installed the computed paths and reported their operational state to the PCE, confirming correct signaling and state synchronization.
12
13 [[~[~[Figure 53: SR-TE Computation and Signaling using BGP-SR~>~>image:485744699448164353_SDN-3-1-v2.png~|~|alt="Figure 53" width="550"~]~]>>attach:485744699448164353_SDN-3-1-v2.png||target="_blank"]]
14
15 {{container cssClass="tc-role-table"}}
16 (% class="table-bordered" %)
17 |=PCE|=PCC
18 |Keysight IxNetwork|HPE MX204
19 |Keysight IxNetwork|ZTE ZXR10 M6000-4SE
20
21 Table 14: SR-TE SR Computation and Signaling over SRv6 µSID (Initiator: PCE; Destination IP: IPv6)
22 {{/container}}
23
24 {{container cssClass="tc-role-table"}}
25 (% class="table-bordered" %)
26 |=PCE|=PCC|=Initiator|=Des. IP|=Notes
27 |Cisco Crosswork Automation|Keysight IxNetwork|PCC-initiated and delegated|IPv4|
28 |Cisco Crosswork Automation|Nokia 7730 SXR-1x-44s|PCC-initiated and delegated|IPv4|Delay optimization
29 |Cisco Crosswork Automation|Nokia 7750 SR-1|PCC-initiated and delegated|IPv4|Delay optimization
30 |Keysight IxNetwork|HPE MX204|PCE|IPv6|
31 |Nokia Network Services Platform (NSP)|Cisco ASR-9901|PCC-initiated and delegated|IPv4|Delay optimization and delay bound
32 |Nokia Network Services Platform (NSP)|Cisco ASR-9901|PCE|IPv4|Delay optimization and delay bound
33 |Nokia Network Services Platform (NSP)|HPE MX204|PCC-initiated and delegated|IPv4|Delay optimization
34 |Nokia Network Services Platform (NSP)|HPE MX204|PCE|IPv4|Delay optimization
35 |Nokia Network Services Platform (NSP)|HPE PTX10002-36QDD|PCC-initiated and delegated|IPv4|Delay optimization and delay bound
36 |Nokia Network Services Platform (NSP)|Keysight IxNetwork|PCC-initiated and delegated|IPv4|Delay optimization
37 |ZTE ZENIC ONE R22|Cisco 8201-24H8FH|PCE|IPv4|
38 |ZTE ZENIC ONE R22|HPE MX204|PCE|IPv4|
39 |ZTE ZENIC ONE R22|HPE PTX10002-36QDD|PCE|IPv4|
40
41 Table 15: SR-TE Computation and Signaling over SR-MPLS
42 {{/container}}
43
44 (% id="prev-next-links" %)
45 |[[< Previous>>doc:SR-Policy Computation and Signaling using BGP-SR]]|[[Next ~>>>doc:Bidirectional Path Computation]]
46 )))
47
48 (% class="col-xs-12 col-sm-4 test-report-sidebar" %)
49 (((
50 {{box}}
51 {{include reference="Main.EANTC Transport & Cloud Networks Interop Test Report 2026.Sidebar Nav"/}}
52 {{/box}}
53 )))
54 )))

Interested in our testing services?

If you are interested and would like to receive more information, please send us an email and sign up for our newsletter to stay up-to-date.