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).
Establishing MP-IBGP Peer Relationships Between PEs

Establishing MP-IBGP Peer Relationships Between PEs

MP-IBGP uses extended community attributes to advertise VPNv4 routes between PEs.

Context

If VPN sites in a basic BGP/MPLS IP VPN need to communicate, PEs must use MP-IBGP to advertise VPNv4 routes with the RD information to each other. Since all the PEs reside in the same AS, MP-IBGP peer relationships can be set up between them.

Perform the following steps on each PE.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

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

    The peer PE is configured as a BGP peer.

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

    An interface is used to set up a TCP connection with the BGP peer.

    NOTE:

    A PE must use a loopback interface address with a 32-bit mask to set up an MP-IBGP peer relationship with the peer PE so that VPN routes can be iterated to tunnels. The route to the local loopback interface is advertised to the peer PE using an IGP on the MPLS backbone network.

  5. Run ipv4-family vpnv4

    The BGP-VPNv4 address family view is displayed.

  6. (Optional) Run activate-route-tag compatible

    VPNv4 routes that carry a non-zero tag value are allowed to match the rule configured using the if-match tag

    By default, VPNv4 routes that carry a non-zero tag value are not allowed to match the rule configured using the if-match tag command.

    By default, the tag value of VPNv4 routes is 0, and the VPNv4 routes that carry tag 0 match the rule configured using the if-match tag command. If the tag carried in VPNv4 routes is not 0, the VPNv4 routes are not allowed to match the rule configured using the if-match tag command unless the activate-route-tag compatible command is run.

  7. Run peer ipv4-address enable

    The ability to exchange VPNv4 routes with the BGP peer is enabled.

  8. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 32987

Downloads: 59

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