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 A

Configuring Inter-AS VPN Option A

If the number of VPNs that a PE accesses and the number of VPN routes are small, inter-AS VPN Option A can be adopted.

Usage Scenario

Inter-AS VPN Option A is a typical application of BGP/MPLS IP VPN in an inter-AS scenario. You do not need to perform special configurations. In inter-AS VPN Option A mode, an ASBR views the peer ASBR as its CE and advertises IPv4 routes to the peer ASBR through EBGP.

On the network shown in Figure 5-9, ASBR1 in AS100 views ASBR2 in AS200 as a CE. Similarly, ASBR2 also views ASBR1 as a CE.

Figure 5-9 Inter-AS VPN Option A networking

Inter-AS VPN Option A applies to scenarios in which the number of VPNs that a PE accesses and the number of VPN routes are small. In Inter-AS VPN Option A mode, ASBRs must support VPN instances and must be capable of managing VPN routes. In addition, ASBRs must reserve dedicated interfaces, for example, sub-interfaces, physical interfaces, and bound logical interfaces, for each inter-AS VPN network. Inter-AS VPN Option A requires high performance of ASBRs, and you do not need to perform any special configurations on the ASBRs.

Pre-configuration Tasks

Before configuring inter-AS VPN Option A, 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 the PEs and ASBRs.

  • Establish a tunnel (LSP or MPLS TE tunnel) between the PE and ASBR in the same AS.

  • Configure an IP address for the interface that connects a CE to a PE.

Procedure

  1. View ASBRs as PEs and configure a basic BGP/MPLS IP VPN for each AS.

    NOTE:

    In inter-AS VPN Option A networking, ensure that the VPN targets of the VPN instances on the ASBR match those of the VPN instances on the PE in the same AS. The VPN targets of the VPN instances on the PEs in different ASs do not need to match each other.

  2. On the ASBR, bind the interface connected to the remote ASBR to a VPN instance. For configuration details, see Binding Interfaces to a VPN Instance.
  3. Configure the routing protocol between ASBRs. For configuration details, see Configuring Route Exchange Between PEs and CEs.

Checking the Configurations

After configuring inter-AS VPN Option A, run the following commands to check previous configurations:

  • Run the display bgp vpnv4 all peer command on the PE or ASBR to check the status of the BGP VPNv4 peer relationship between the PE and ASBR in the same AS is "Established".

  • Run the display bgp vpnv4 all routing-table command on the PE or ASBR to check the VPNv4 routes.

  • Run the display ip routing-table vpn-instance command on the PE or ASBR to check the VPN routing table of the PE or ASBR.

Run the display bgp vpnv4 all routing-table command on an ASBR. The command output shows the VPNv4 routes on the ASBR.

<HUAWEI> display bgp vpnv4 all routing-table
BGP Local router ID is 2.2.2.9
 Status codes: * - valid, > - best, d - damped, x - best external, a - add path,
               h - history,  i - internal, s - suppressed, S - Stale
               Origin : i - IGP, e - EGP, ? - incomplete
 RPKI validation codes: V - valid, I - invalid, N - not-found
 Total number of routes from all PE: 2
 Route Distinguisher: 100:1
      Network            NextHop        MED        LocPrf    PrefVal Path/Ogn
 *>i  10.1.1.0/24        1.1.1.9         0          100        0      ?
 *>i  10.1.1.1/32        1.1.1.9         0          100        0      ?
 VPN-Instance vpn1, router ID 2.2.2.9:

 Total Number of Routes: 9
      Network            NextHop        MED        LocPrf    PrefVal Path/Ogn
 *>i  10.1.1.0/24        1.1.1.9         0          100        0      ?
 *>i  10.1.1.1/32        1.1.1.9         0          100        0      ?
 *>   10.2.1.0/24        192.168.1.2                           0      200?
 *>   10.2.1.1/32        192.168.1.2                           0      200?
 *>   192.168.1.0          0.0.0.0       0                     0      ?
 *                       192.168.1.2     0                     0      200?
 *>   192.168.1.1/32       0.0.0.0       0                     0      ?
 *                       192.168.1.2     0                     0      200?
 *>   192.168.1.2/32       0.0.0.0       0                     0      ?
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 27333

Downloads: 51

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