|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-7 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
In this section, we focus on asymmetric IRB (Integrated Routing and Bridging) solutions. In asymmetric IRB, the lookup operations differ between the ingress and egress Provider Edge (PE) devices. The ingress PE executes three lookups: first, a MAC lookup, followed by an IP lookup, and then another MAC lookup. In contrast, the egress PE performs just a single MAC lookup. |
|
|
8 |
For our tests, we utilized one type of service interface: VLAN-based. We conducted a full-mesh unicast traffic test to simultaneously verify both routing and bridging functions, without performing any switchover. We completed two iterations, as some vendors only support single-homing this year. |
|
|
9 |
Spirent TestCenter was used as the traffic generator for this test. |
|
|
10 |
|
|
|
11 |
[[Figure 22: EVPN SR-MPLS Asymmetric VLAN-based IRB combi1>>image:433995712615546881_1.18-mpls-1.png||alt="Figure 22" width="550"]] |
|
|
12 |
|
|
|
13 |
[[Figure 23: EVPN SR-MPLS Asymmetric VLAN-based IRB combi2>>image:433995712615612417_1.18-mpls-2.png||alt="Figure 23" width="550"]] |
|
|
14 |
|
|
|
15 |
(% id="prev-next-links" %) |
|
|
16 |
|[[< Previous>>doc:Symmetric IRB with VLAN-based and VLAN-aware bundle interface]]|[[Next ~>>>doc:EVPN-VXLAN and EVPN-MPLS Interworking]] |
|
|
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 |
))) |
