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.


Configuration Guide - VPN

CloudEngine 12800 and 12800E V200R005C10

This document describes the configurations of VPN, including GRE, BGP/MPLS IP VPN, BGP/MPLS IPv6 VPN, VLL, PWE3, and VPLS.
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 MP-IBGP Between the PE and ASBR in the Same AS

Configuring MP-IBGP Between the PE and ASBR in the Same AS


Perform the following steps on the PE and ASBR in the same AS.


  1. Run system-view

    The system view is displayed.

  2. Run bgp { as-number-plain | as-number-dot }

    The BGP view is displayed.

  3. Run peer ipv4-address as-number as-number-plain

    An IBGP peer relationship is established between the PE and ASBR in the same AS.

  4. Run peer ipv4-address connect-interface loopback interface-number

    The loopback interface is specified as the outbound interface of the BGP session.


    The 32-bit mask IP addresses of the loopback interfaces must be used to establish the MP-IBGP peer relationship between PEs. This ensures that the tunnel can be iterated. The route destined to the loopback interface is advertised to the remote PE using IGP on the MPLS backbone network.

  5. Run ipv4-family vpnv4 [ unicast ]

    The BGP-VPNv4 address family is displayed.

  6. Run peer ipv4-address enable

    The PE and ASBR in the same AS are enabled to exchange VPNv4 routes.


    An ASBR can change the next-hop address of a VPNv4 route to its own address before advertising the route to a PE.

  7. Run commit

    The configuration is committed.

Updated: 2019-04-03

Document ID: EDOC1100075353

Views: 14471

Downloads: 25

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