Wiki source code of L3VPN over SR MPLS

Show last authors
1 (% class="row" %)
2 (((
3 (% class="col-xs-12 col-sm-7 test-report-content" %)
4 (((
5 ----
6
7 L3VPN over SR‐MPLS has gained considerable attention as it combines the flexibility of Segment Routing with the scalability of traditional MPLS. Operators can steer traffic more efficiently while reducing protocol overhead by assigning segment identifiers (SIDs) within the control plane. This architecture suits a variety of scenarios, including enterprise WAN connectivity, inter‐data‐center links, and mobile backhaul applications where traffic engineering and high availability are essential.
8 Our testing focused on verifying that L3VPN services function consistently across two separate topologies, each leveraging different interior gateway protocols: one design used IS‐IS with two spine nodes, and the other used OSPF with a single spine node.
9
10 [[Figure 78: SR-MPLS L3VPN over IS-IS>>image:434086577237393409_SRMPLS-01-ISIS-Generic-3-v1.png||alt="Figure 78" width="550"]]
11
12 [[Figure 79: SR-MPLS L3VPN over OSPF>>image:434086577254170625_SRMPLS-01-OSPF-Generic-4-v1.png||alt="Figure 79" width="550"]]
13
14 In both cases, the initial step was to validate the underlying control plane, ensuring that the devices were distributing Segment Routing labels correctly and that BGP sessions exchanged VPN routes without error. Foundational checks confirmed proper label installation. Subsequently, we activated L3VPN services and injected IPv4 and IPv6 traffic.
15 We checked the routers' routing tables for the next hops and label bindings. Then, we generated traffic through all links to detect packet loss or route inconsistencies. We didn't detect packet loss in any of the flows, which shows that the SR-MPLS forwarding paths are reliable. The setup successfully handled IPv4 and IPv6 data streams, demonstrating multi-protocol forwarding capability.
16 The positive results from these tests demonstrate that the test setup supports the scalability and robustness needed for future services and establishes a solid foundation for further testing.
17
18 Note: The traffic generator was connected via a switch, enabling simultaneous communication with all PE devices.
19
20 {{container cssClass="tc-role-table"}}
21 (% class="table-bordered" %)
22 |=PE|=Spine|=Traffic Generator
23 |(((
24 Arista 7280R3,
25 Arrcus S9610-36D,
26 Ciena 5134,
27 Ciena 8140 Coherent Metro Router,
28 Ericsson Router6678,
29 H3C CR16000-M1A,
30 Huawei NetEngine 8000 M14,
31 Huawei NetEngine A816,
32 Juniper ACX7024,
33 Juniper Cloud-Native Router (JCNR),
34 Keysight IxNetwork,
35 Nokia 7730 SXR-1x-44s,
36 Nokia 7750 SR-1,
37 Ribbon NPT-2100
38 )))|(((
39 Arista 7280R3,
40 Juniper ACX7100-48L
41 )))|Keysight IxNetwork
42
43 Table 20: L3VPN over SR MPLS - Single-domain IPv4 IS-IS
44 {{/container}}
45
46 {{container cssClass="tc-role-table"}}
47 (% class="table-bordered" %)
48 |=PE|=Spine|=Traffic Generator
49 |(((
50 Arista 7280R3,
51 Ciena 5134,
52 Ciena 8140 Coherent Metro Router,
53 Ericsson Router6678,
54 H3C CR16000-M1A,
55 Huawei NetEngine 8000 M14,
56 Huawei NetEngine A816,
57 Juniper ACX7024,
58 Juniper Cloud-Native Router (JCNR),
59 Keysight IxNetwork,
60 Nokia 7750 SR-1,
61 Ribbon NPT-2100
62 )))|Juniper ACX7100-48L|Keysight IxNetwork
63
64 Table 21: L3VPN over SR MPLS - Single-domain IPv4 OSPF
65 {{/container}}
66 (% id="prev-next-links" %)
67 |[[< Previous>>doc:Main.Multi-Vendor MPLS & SDN Interoperability Test Report 2025.SR-MPLS.WebHome]]|[[Next ~>>>doc:Topology Independent Loop Free Alternative over SR-MPLS]]
68 )))
69
70 (% class="col-xs-12 col-sm-5 test-report-sidebar" %)
71 (((
72 {{box}}
73 {{include reference="Main.Multi-Vendor MPLS & SDN Interoperability Test Report 2025.Sidebar Nav"/}}
74 {{/box}}
75 )))
76 )))