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.


NE40E-M2 V800R010C10SPC500 Feature Description - LAN Access and MAN Access 01

This is NE40E-M2 V800R010C10SPC500 Feature Description - LAN Access and MAN Access

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).
QinQ Mapping

QinQ Mapping


QinQ mapping maps VLAN tags in user packets to specified tags before the user packets are transmitted across the public network.

  • Before sending local VLAN frames, a sub-interface replaces the tags in the local frames with external VLAN tags.

  • Before receiving frames from external VLANs, a sub-interface replaces the tags in the external VLANs with local VLAN tags.

QinQ mapping allows a device to map a user VLAN tag to a carrier VLAN tag, shielding different user VLAN IDs in packets.

QinQ mapping is deployed on edge devices of a Metro Ethernet. It is applied in but not limited to the following scenarios:
  • VLAN IDs deployed at new sites and old sites conflict, but new sites need to communicate with old sites.

  • VLAN IDs planned by each site on the public network conflict. These sites do not need to communicate.

  • VLAN IDs on both ends of the public network are asymmetric.

Currently, only 1 to 1 QinQ mapping is supported. When a QinQ mapping-enabled sub-interface receives a single-tagged packet, the sub-interface replaces the VLAN ID in the frame with a specified VLAN ID.

Figure 7-8 QinQ mapping

As shown in Figure 7-8, 1 to 1 QinQ mapping is configured on Sub-interfaces 1 on Switch 2 and Switch 3. If PC1 wants to communicate with PC2:

  1. PC1 sends a frame to Switch 1.

  2. Upon receipt, Switch 1 adds VLAN ID 10 to the frame, and forwards the frame to Switch 2. After Sub-interface1 on Switch 2 receives the frame with VLAN ID 10, Sub-interface 1 on Switch 2 replaces VLAN ID 10 with carrier VLAN ID 50. Interface 2 on Switch 2 then sends the frame with carrier VLAN ID 50 to the Internet service provider (ISP) network.

  3. The ISP network transparently transmits the frame.

  4. After Sub-interface 1 on Switch 3 receives the tagged frame from Switch 2, Sub-interface 1 on Switch 3 replaces the carrier VLAN ID 50 with VLAN ID 30.

PC2 communicates with PC1 in a similar manner.

Comparison Between QinQ Mapping and VLAN Mapping

Table 7-3 describes the comparison between QinQ mapping and VLAN mapping.

Table 7-3 Comparison between QinQ mapping and VLAN mapping

Mapping Type



1 to 1

An interface maps the tag of a received single-tagged frame to the specified tag.

  • QinQ mapping

    • Performed on a sub-interface

    • Used for VPLS access

  • VLAN mapping

    • Performed on an interface

    • Used on Layer 2 networks where VLAN frames are forwarded

Updated: 2019-01-02

Document ID: EDOC1100058405

Views: 21040

Downloads: 29

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next