|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-8 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
Provisioning L3 VPN services across different platforms requires consistent service modeling and reliable configuration delivery. Device-specific configuration differences in multi-vendor environments add integration complexity. Using controller-driven provisioning with NETCONF and YANG enables service abstraction and ensures standardized, repeatable deployment. In this test, we validated L3 VPN provisioning with NETCONF and YANG-based service models across several vendor implementations. |
|
|
8 |
For each run, the controller created an L3 VPN service using a structured service instance. The service model instance specified the VPN topology, participating nodes, and per-site parameters. It included creating VRFs (network instances) with associated route distinguishers and route targets, as well as service attachment via 802.1Q subinterfaces with customer VLAN identifiers. PE–CE routing was established using BGP within the VPN context. Routing policy configuration was also provisioned as part of the service, including VRF import/export policies and BGP neighbor policy attachment where supported. |
|
|
9 |
The controller delivered the generated configuration to both service endpoints and verified successful deployment. We validated the service by verifying the operational VRFs and confirming successful VPN route exchange between the participating nodes. |
|
|
10 |
Both SR-MPLS and SRv6 transport variants were covered. In the SRv6 scenario, the service deployment included per-VRF SRv6 behavior with an associated locator and VPN-specific SID handling at the headend. |
|
|
11 |
|
|
|
12 |
[[~[~[Figure 56: L3VPN Service Provisioning via NETCONF~>~>image:487484161363869697_SDN-19-1-v3.png~|~|alt="Figure 56" width="550"~]~]>>attach:487484161363869697_SDN-19-1-v3.png||target="_blank"]] |
|
|
13 |
|
|
|
14 |
{{container cssClass="tc-role-table"}} |
|
|
15 |
(% class="table-bordered" %) |
|
|
16 |
|=Controller|=Network Node |
|
|
17 |
|Cisco Crosswork Automation|((( |
|
|
18 |
Cisco 8201-24H8FH, |
|
|
19 |
HPE MX204 |
|
|
20 |
))) |
|
|
21 |
|Cisco Crosswork Automation|((( |
|
|
22 |
Cisco 8201-24H8FH, |
|
|
23 |
Ribbon NPT-2507 |
|
|
24 |
))) |
|
|
25 |
|
|
|
26 |
Table 23: L3VPN Service Provisioning via NETCONF - L3 Service over SR-MPLS |
|
|
27 |
{{/container}} |
|
|
28 |
|
|
|
29 |
{{container cssClass="tc-role-table"}} |
|
|
30 |
(% class="table-bordered" %) |
|
|
31 |
|=Controller|=Network Node |
|
|
32 |
|Cisco Crosswork Automation|((( |
|
|
33 |
Arista 7280R3, |
|
|
34 |
Cisco 8201-24H8FH |
|
|
35 |
))) |
|
|
36 |
|
|
|
37 |
Table 24: L3VPN Service Provisioning via NETCONF - L3 Service over SRv6 |
|
|
38 |
{{/container}} |
|
|
39 |
|
|
|
40 |
(% id="prev-next-links" %) |
|
|
41 |
|[[< Previous>>doc:PCEP over IPv6]]|[[Next ~>>>doc:Latency-Based Optimization]] |
|
|
42 |
))) |
|
|
43 |
|
|
|
44 |
(% class="col-xs-12 col-sm-4 test-report-sidebar" %) |
|
|
45 |
((( |
|
|
46 |
{{box}} |
|
|
47 |
{{include reference="Main.EANTC Transport & Cloud Networks Interop Test Report 2026.Sidebar Nav"/}} |
|
|
48 |
{{/box}} |
|
|
49 |
))) |
|
|
50 |
))) |
