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

Reminder

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

upgrade

AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009 CLI-based Configuration Guide - Ethernet Switching

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).
Using a Dot1q Termination Sub-interface to Connect to a VPN

Using a Dot1q Termination Sub-interface to Connect to a VPN

Using a Dot1q Termination Sub-interface to Connect to a PWE3/VLL Network

As shown in Figure 6-3, different branches of an enterprise are interconnected through a carrier's PWE3/VLL network. PEs serve as edge devices of the carrier's PWE3/VLL network and connect to branch networks through sub-interfaces, and packets sent by CEs to PEs carry one or double VLAN tags. User hosts in different branches need to communicate with each other.

Figure 6-3  Using a Dot1q termination sub-interface to connect to a PWE3/VLL network

Dot1q termination and PWE3/VLL are deployed on sub-interfaces of PE1 and PE2. When the outer VLAN tag of data packets sent by CE1 to PE1 matches the Dot1q termination configuration on Port1.1, PE1 encapsulates double MPLS labels into the packets and forwards the packets to the carrier's PWE3/VLL network. The VLAN tags are invisible on the carrier's PWE3/VLL network. Before sending packets, PE2 removes double MPLS labels from the packets. PE2 then forwards the packets to CE2 according to the Dot1q termination configuration on Port1.1. CE2 then forwards packets to user hosts to implement interworking of different branches, and so on.

Using a Dot1q Termination Sub-interface to Connect to an L3VPN

As shown in Figure 6-4, different branches of an enterprise are interconnected through a carrier's MPLS L3VPN. PEs serve as edge devices of the carrier's MPLS L3VPN and connect to branch networks through sub-interfaces, and packets sent by CEs to PEs carry one or double VLAN tags. Hosts of the same services in different branches need to communicate.

Figure 6-4  Using a Dot1q termination sub-interface to connect to an L3VPN

Dot1q termination and L3VPN are deployed on sub-interfaces of PE1 and PE2. When receiving data packets from CE1, PE1 removes the outer VLAN tag from the packets according to the Dot1q termination on Port1.1, binds the outer VLAN tag to the VPN instance VPN1, and then connects to the L3VPN. After the packets reach PE2, PE2 determines that the packets are destined for CE3 according to the VPN instance. PE2 adds the outer VLAN tag to the packets according to the configuration of Port1.1, and then forwards the packets. The packets then reach user hosts through CE3 to implement interworking, and so on.

Translation
Download
Updated: 2019-05-17

Document ID: EDOC1000174108

Views: 62330

Downloads: 50

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