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

Configuration Guide - VPN 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - 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).
Configuring Inter-AS VPN Option C in an Independent Labeled Address Family (Solution 2)

Configuring Inter-AS VPN Option C in an Independent Labeled Address Family (Solution 2)

After LDP LSPs are established for the labeled BGP routes of the public network, multi-hop EBGP connections are established between PEs of different ASs to exchange VPNv4 routes. An independent labeled address family can also be used to negotiate the label capability.

Usage Scenario

If the MPLS backbone network bearing VPN routes spans multiple ASs, the inter-AS VPN is required.

If each AS needs to exchange a large number of VPN routes, inter-AS VPN-Option C is a good choice to prevent the ASBR from becoming a bottleneck that impedes network expansion. The following solutions can be used to implement inter-AS VPN-Option C:

  • Solution 1: After learning the labeled BGP routes of the public network in the remote AS from the remote ASBR, the local ASBR allocates labels for these routes, and advertises these routes to the IBGP peer that supports the label switching capability. In this manner, a complete LSP is set up.
  • Solution 2: The IBGP peer relationship between the PE and ASBR is not needed. In this solution, an ASBR learns the labeled public BGP routes of the remote AS from the peer ASBR. Then these labeled public BGP routes are imported to an IGP to trigger the establishment of an LDP LSP. In this manner, a complete LDP LSP can be established between the two PEs.

If an ASBR is ready to access a large number of PEs, solution 2 is recommended for its easy configuration.

NOTE:

In inter-AS VPN-Option C mode, do not enable LDP between ASBRs. If LDP is enabled on the interfaces between ASBRs, LDP sessions are then established between the ASBRs. As a result, the ASBRs establish an egress LSP and send Mapping messages to upstream ASBRs. After receiving Mapping messages, the upstream ASBRs establish a transit LSP. When there are high-volume BGP routes, enabling LDP on the interfaces between ASBRs leads to the occupation of a large number of LDP labels.

Pre-configuration Tasks

Before configuring inter-AS VPN Option C (solution 2), complete the following tasks:

  • Configure an IGP for the MPLS backbone network of each AS to ensure IP connectivity of the backbone network in each AS.
  • Configure MPLS and MPLS LDP both globally and per interface on each node of the MPLS backbone network in each AS.
  • Configure a VPN instance on each PE and bind the interface that connects a PE to a CE to the VPN instance on that PE.
  • Configure an IP address for the interface connecting a CE to a PE.
  • Configure a name for the prefix list used to filter labeled BGP routes of the public network.

Configuration Procedures

Perform one or more of the following configurations as required.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 37200

Downloads: 61

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