No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Configuration Guide - Ethernet Switching

CloudEngine 8800, 7800, 6800, and 5800 V200R003C00

This document describes the configuration of Ethernet services, including configuring MAC address table, link aggregation, VLANs, MUX VLAN, Voice VLAN, VLAN mapping, QinQ, GVRP, VCMP, STP/RSTP/MSTP, VBST, SEP, RRPP, ERPS, LBDT, and Layer 2 protocol transparent transmission.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Application Scenarios for VLAN Mapping

Application Scenarios for VLAN Mapping

VLAN-based VLAN Mapping

  • 1 to 1 VLAN mapping

    As shown in Figure 7-2, on a data center network, a network administrator deploys a new branch that is on the same network segment as the headquarters. However, VLAN IDs in the new branch and headquarters are inconsistent and VLAN deployment in the headquarters cannot be changed. To implement communication between the new branch and headquarters, configure 1 to 1 VLAN mapping on Switch2.

    Figure 7-2 Networking of 1 to 1 VLAN mapping
  • 2 to 1 VLAN mapping

    As shown in Figure 7-3, on a data center network, the office server and production server are deployed in the old branch, and the servers are connected to the core network through the access and aggregation switches. The network administrator deploys a new branch. To save VLAN resources and isolate different services, configure QinQ on the aggregation switch. To retain VLAN deployment of core switch Switch5, configure VLAN mapping on Switch5.

    Figure 7-3 Networking of 2 to 1 VLAN mapping
  • 2 to 2 VLAN mapping

    As shown in Figure 7-4, two branches of a data center are deployed in different positions. To save VLAN resources and plan private VLAN IDs in the data center, QinQ is used. That is, packets from branches to the ISP network carry double tags. Because VLAN IDs in packets from branches are different from the VLAN IDs allocated by the ISP network, user packets are discarded. As a result, communication between branches is interrupted. Configure 2 to 2 VLAN mapping on Switch2 and Switch3 to map double tags on the branch network to double tags on the ISP network so that branches can communicate.

    Figure 7-4 Networking of 2 to 2 VLAN mapping

MQC-based VLAN Mapping

As shown in Figure 7-5, on a data center network, servers store video and data information. Users are classified into gold and silver users, and gold and silver users belong to VLAN 200 and VLAN 300 respectively and access servers through the enterprise backbone network. The enterprise backbone network allocates VLAN 2 to gold users and VLAN 3 to silver users. Switch2 and Switch3 are edge devices of the enterprise backbone network. VLAN IDs planned by the video and data servers and enterprise backbone network are different. To ensure that gold users can access the video server and silver users can access the data server, configure MQC-based VLAN mapping on Switch2 and Switch3.

Figure 7-5 Networking of MQC-based VLAN mapping
Updated: 2019-05-08

Document ID: EDOC1100004351

Views: 125874

Downloads: 295

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next