|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-8 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
This test verified that IPv4 and IPv6 global routing prefixes can be transported natively over an SRv6 network without using VRF-based VPN services. The participant nodes exchanged the IPv4 and IPv6 unicast prefixes using BGP global address families, while SRv6 was used as the data-plane encapsulation mechanism. |
|
|
8 |
The egress PE advertised IPv4 and IPv6 prefixes via BGP, along with an SRv6 service SID reachable through the IPv6 next-hop. The ingress PE installed these prefixes in the global IPv4 and IPv6 forwarding tables with IPv6 SRv6 SIDs as the forwarding next-hop. |
|
|
9 |
We verified the data plane by generating traffic over these prefixes with no packet loss. |
|
|
10 |
|
|
|
11 |
{{container cssClass="tc-role-table"}} |
|
|
12 |
(% class="table-bordered" %) |
|
|
13 |
|=PE|=Traffic Generator |
|
|
14 |
|((( |
|
|
15 |
ZTE ZXR10 M6000-4SE, |
|
|
16 |
ZTE ZXR10 M6000-3S Plus, |
|
|
17 |
Raisecom iTN8800-A |
|
|
18 |
)))|Keysight IxNetwork |
|
|
19 |
|
|
|
20 |
Table 54: Global IPv4/IPv6 Routing Table - µSID |
|
|
21 |
{{/container}} |
|
|
22 |
|
|
|
23 |
(% id="prev-next-links" %) |
|
|
24 |
|[[< Previous>>doc:IRB EVPN ELAN over SRv6 ]]|[[Next ~>>>doc:SRv6 Flexible Algorithm]] |
|
|
25 |
))) |
|
|
26 |
|
|
|
27 |
(% class="col-xs-12 col-sm-4 test-report-sidebar" %) |
|
|
28 |
((( |
|
|
29 |
{{box}} |
|
|
30 |
{{include reference="Main.EANTC Transport & Cloud Networks Interop Test Report 2026.Sidebar Nav"/}} |
|
|
31 |
{{/box}} |
|
|
32 |
))) |
|
|
33 |
))) |
