Wiki source code of Asymmetric IRB with VLAN-Based Interface
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | (% class="row" %) |
| 2 | ((( | ||
| 3 | (% class="col-xs-12 col-sm-7 test-report-content" %) | ||
| 4 | ((( | ||
| 5 | ---- | ||
| 6 | |||
| |
4.1 | 7 | In this section, we focus on asymmetric IRB (Integrated Routing and Bridging) solutions. Asymmetric IRB has the same use case as symmetric IRB: interconnect the L2 and L3 for complex network conditions. It's just that the working mode is different. 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 tested one type of service interface: VLAN-based. DUTs had multiple VLANs configured. EANTC conducted a full-mesh unicast traffic simultaneously to verify both routing and bridging functions with Spirent TestCenter, without performing any switchover. We completed two iterations, as some vendors only support single-homing this year. | ||
| |
1.1 | 9 | |
| 10 | [[Figure 22: EVPN SR-MPLS Asymmetric VLAN-based IRB combi1>>image:433995712615546881_1.18-mpls-1.png||alt="Figure 22" width="550"]] | ||
| 11 | |||
| 12 | [[Figure 23: EVPN SR-MPLS Asymmetric VLAN-based IRB combi2>>image:433995712615612417_1.18-mpls-2.png||alt="Figure 23" width="550"]] | ||
| 13 | |||
| 14 | (% id="prev-next-links" %) | ||
| 15 | |[[< Previous>>doc:Symmetric IRB with VLAN-based and VLAN-aware bundle interface]]|[[Next ~>>>doc:EVPN-VXLAN and EVPN-MPLS Interworking]] | ||
| 16 | ))) | ||
| 17 | |||
| 18 | (% class="col-xs-12 col-sm-5 test-report-sidebar" %) | ||
| 19 | ((( | ||
| 20 | {{box}} | ||
| 21 | {{include reference="Main.Multi-Vendor MPLS & SDN Interoperability Test Report 2025.Sidebar Nav"/}} | ||
| 22 | {{/box}} | ||
| 23 | ))) | ||
| 24 | ))) |