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.


Feature Description - VPN 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Feature Description - VPN
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 VPWS is an L2VPN technology that enables users to communicate across multiple autonomous systems (ASs).

Unlike inter-AS VLL, which provides inter-AS communication by setting a static LSP between autonomous system boundary routers (ASBRs), inter-AS VPWS is more like inter-AS L3VPN in terms of implementation.

In inter-AS VPWS Option A, the link type between ASBRs must be the same as the VC type. The disadvantage of inter-AS VPWS Option A is that each ASBR must reserve a sub-interface for each inter-AS VC. Inter-AS VPWS Option A applies to scenarios in which the number of inter-AS VCs is small. Compared with inter-AS L3VPN Option A, inter-AS VPWS Option A consumes more resources and requires more configuration workload.


With the popularity of MPLS VPN, the requirements for communication between the MANs of different carriers or between different backbone networks become common. As a result, inter-AS VPWS is introduced to solve the inter-AS communication problem.

Figure 6-28 Origin of inter-AS VPN

On the L2VPN shown in Figure 6-28, some users belong to AS1, and some to AS2. If MPLS forwarding is not implemented, L2VPN users in different ASs cannot communicate. Figure 6-28 shows a scenario in which L2VPN users of only two ASs need to communicate. In reality, L2VPN users of more ASs may need to communicate.

Inter-AS VPWS Option A

In inter-AS VPWS Option A, ASBRs in two ASs are directly connected. The two ASBRs function as PEs in their respective ASs, but regard each other as a CE.

Figure 6-29 Networking diagram of the inter-AS L2VPN Option A

On the network shown in Figure 6-29, ASBR2 is a CE for ASBR1. Similarly, ASBR1 is a CE for ASBR2.

The characteristics of inter-AS VPWS Option A are as follows:

  • Easy to implement

    MPLS forwarding is not required between the PEs functioning as ASBRs, because common IP forwarding can be adopted, and no special inter-AS configuration is required.

  • Poor scalability

    • The PEs functioning as ASBRs need to manage information about all L2VPNs, which leads to a great deal of L2VPN information on the PEs and therefore burdens the PEs.
    • An AC interface must be reserved for each PW, because the PE functions as an ASBR in the local AS.
    • If users need to communicate across multiple ASs, intermediate ASs must support L2VPN. This causes heavy configuration and affects the intermediate ASs.

Inter-AS VPWS Option A applies to scenarios in which a VPWS network crosses only a few ASs.

Inter-AS VPWS Option C

The preceding scheme require 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 6-30.

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 6-30 Networking diagram of inter-AS VPWS 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 VPWS Option C is preferred when users need to communicate across a large number of ASs.

Updated: 2019-01-14

Document ID: EDOC1100058940

Views: 19414

Downloads: 34

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