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.


CLI-based Configuration Guide - VPN

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document describes VPN features on the device and provides configuration procedures and configuration examples.
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).


Inter-AS VPLS refers to the application of the VPLS across multiple autonomous systems (ASs). There are two inter-AS VPLS implementation modes: Option A and Option C.

When using the inter-AS VPLS, you do not need to consider the learning or forwarding functions of VSIs, but consider the establishment of PWs between PEs. In this manner, the inter-AS VPLS has the same principle and implementation method as those of inter-AS L2VPN.

In Option A, configurations are easy, without the need to run MPLS between ASBRs or perform particular configurations for inter-AS communications. Nevertheless, this mode has the poor expansion ability and higher requirements for PEs. This mode is applicable in the early servicing stage when the number of inter-AS VPNs is small.

Inter-AS Martini VPLS (Option A)

Figure 12-9 shows the networking of the inter-AS Martini VPLS (Option A).

Figure 12-9  Networking diagram of inter-AS Martini VPLS (Option A)

The inter-AS Martini VPLS (Option A) is implemented as follows:

  • An IGP protocol is configured on the backbone network to implement the communications between devices in the same AS.

  • The basic MPLS functions are enabled on the backbone network; the dynamic LSP is set up between the PE and ASBR in the same AS; a remote LDP session is set up between the PE and ASBR if they are not directly connected.

  • The VPLS connection is set up between the PE and ASBR in the same AS.

Inter-AS Martini VPLS (Option C)

The OptionA scheme requires ASBRs to participate in the distribution and maintenance of PW labels. When multiple inter-AS PWs exist in each AS, ASBRs may be a bottleneck in network expansion.

Inter-AS VPWS Option C avoids this problem by freeing ASBRs from setting up and maintaining PWs. PW labels are directly switched between PEs, as shown in Figure 12-10.

In inter-AS VPWS Option C:
  • ASBRs advertise labeled IPv4 routes to PEs in their respective ASs through Multiprotocol Interior Border Gateway Protocol (MP-IBGP), and advertise labeled IPv4 routes received by PEs in their respective ASs to the ASBR peers in other ASs. ASBRs in the intermediate AS also advertise labeled IPv4 routes. As a result, an LDP LSP is set up between the ingress PE and the egress PE.
  • PEs in different ASs set up remote MPLS LDP sessions to exchange PW information.
Figure 12-10  Networking diagram of inter-AS Martini VPLS (Option C)

Inter-AS VPWS Option C has the following advantages:
  • Similar to the network on which L2VPN users belong to the same AS, intermediate devices do not need to store L2VPN information.

  • Only PEs need to store L2VPN information. The devices in intermediate ASs only need to function as ordinary ASBRs that support IP forwarding and do not need to support L2VPN. Inter-AS virtual private wire service (VPWS) Option C is preferred when users need to communicate across a large number of ASs.

Updated: 2019-08-07

Document ID: EDOC1100033725

Views: 142602

Downloads: 359

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