|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-7 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
The integration of EVPN and IPVPN enables customers to extend both Layer 2 and Layer 3 services across multiple routing domains, providing flexibility for various connectivity requirements. By utilizing the advantages of EVPN for Ethernet-based services and IPVPN for secure routing, the EVPN to IPVPN gateway can offer scalable, secure, and reliable connectivity between different routing domains. |
|
|
8 |
We conducted two test runs. The first run has Site Of Origin (SOO) enabled to prevent the loop, whereas the second run has the D-path enabled to prevent the loop. We sent full-mesh unicast traffic across two domains and observed no packet loss or duplication in either run. |
|
|
9 |
Spirent TestCenter was used as the traffic generator for this test. |
|
|
10 |
|
|
|
11 |
[[Figure 27: EVPN SR-MPLS to EVPN IPVPN gateway interworking combi1>>image:433995712635142145_1.25-1.png||alt="Figure 27" width="550"]] |
|
|
12 |
|
|
|
13 |
[[Figure 28: EVPN SR-MPLS to EVPN IPVPN gateway interworking combi2>>image:433995712635207681_1.25-2.png||alt="Figure 28" width="550"]] |
|
|
14 |
|
|
|
15 |
(% id="prev-next-links" %) |
|
|
16 |
|[[< Previous>>doc:EVPN-VXLAN to EVPN VXLAN Tunnel Stitching for DCI]]|[[Next ~>>>doc:MAC Mobility]] |
|
|
17 |
))) |
|
|
18 |
|
|
|
19 |
(% class="col-xs-12 col-sm-5 test-report-sidebar" %) |
|
|
20 |
((( |
|
|
21 |
{{box}} |
|
|
22 |
{{include reference="Main.Multi-Vendor MPLS & SDN Interoperability Test Report 2025.Sidebar Nav"/}} |
|
|
23 |
{{/box}} |
|
|
24 |
))) |
|
|
25 |
))) |
