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).
Application of EVC VPWS Services

Application of EVC VPWS Services

Service Description

As globalization gains momentum, more and more enterprises set up branches in foreign countries and requirements for office flexibility are increasing. An urgent demand for carriers is to provide Layer 2 links for enterprises to set up their own enterprise networks, so that enterprise employees can conveniently visit enterprise intranets outside their offices.

By combining previous access modes with the current IP backbone network, VPWS prevents duplicate network construction and saves operation costs.

Networking Description

Figure 8-16 Configuring EVC VPWS Services

In the traditional service model supported by the NE40E, common sub-interfaces (VLAN type), Dot1q VLAN tag termination sub-interfaces, or QinQ VLAN tag termination sub-interfaces are created on the user-side interfaces of PEs. These sub-interfaces are bound to different VSIs on the carrier network. If Layer 2 devices use different access modes on a network, service management and configuration are complicated and difficult. To resolve this issue, configure an EVC to carry Layer 2 services. This implementation facilitates network planning and management, driving down enterprise costs.

On the VPWS network shown in Figure 8-16, VPN1 services use the EVC VPWS model. The traffic encapsulation type and behavior are configured on the PE to ensure service connectivity within the same VPN instance.

Feature Deployment

  1. Create a Layer 2 EVC sub-interface on the PE and specify the traffic encapsulation type and behavior on the Layer 2 sub-interface.
  2. Configure VPWS on the EVC Layer 2 sub-interface.
Updated: 2019-01-02

Document ID: EDOC1100058405

Views: 20656

Downloads: 28

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next