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

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).
Establishing an MP-EBGP Peer Relationship Between PE Devices

Establishing an MP-EBGP Peer Relationship Between PE Devices

Context

By introducing extended community attributes into BGP, MP-EBGP can advertise VPNv4 routes between PEs.

Procedure

  • Configure an ASBR to send the loopback interface IP addresses of a PE device used for peer relationship establishment to the ASBRs of other ASs and peer PE devices.

    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 network ip-address [ mask | mask-length ] [ route-policy route-policy-name ]

      The loopback address of the PE in the local AS is advertised to the peer ASBR.

    4. Run commit

      The configuration is committed.

  • (Optional) Disable an ASBR from advertising BGP supernet labeled routes.

    In the inter-AS VPN Option C solution, a PE uses a routing policy to assign a label to its loopback address route and advertises this route as a BGP labeled route. When an ASBR receives the route, the route is a BGP supernet labeled route in which the destination address and next hop address are the same or the destination address is more detailed than the next hop address. In V100R002C00 or earlier, the ASBR does not advertise the received BGP supernet labeled route. After the ASBR is upgraded to a version later than V100R002C00, the ASBR can advertise the received BGP supernet labeled route to its peers. This advertisement may result in a different traffic path being used before and after the upgrade. To ensure that the traffic path remains unchanged, disable the ASBR from advertising BGP supernet labeled routes.

    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 supernet label-route advertise disable

      The ASBR is disabled from advertising BGP supernet labeled routes.

      To advertise the loopback address route of a PE in the local AS to a PE in another AS after this command is run, you can run the network command on the ASBR to advertise the BGP route to the loopback address of the PE in the same AS.

    4. Run commit

      The configuration is committed.

  • Establish an MP-EBGP peer relationship between the PE devices.

    Perform the following steps on the PE device:

    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 | as-number-dot }

      The peer PE is specified as the EBGP peer.

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

      The source interface that sends BGP packets is specified.

    5. Run peer ipv4-address ebgp-max-hop [ hop-count ]

      The maximum number of hops between the EBGP peers is configured.

      PEs of different ASs are generally not directly connected. To set up an EBGP peer relationship between them, configure the maximum number of hops between PEs and ensure that the PEs are reachable.

    6. (Optional) Run peer { group-name | ipv4-address } mpls-local-ifnet disable

      The ability to establish an MPLS local IFNET tunnel between PEs is disabled.

      In the Option C scenario, PEs establish an MP-EBGP peer relationship. Therefore, an MPLS local IFNET tunnel between PEs is established over the MP-EBGP peer relationship. The MPLS local IFNET tunnel fails to transmit traffic because PEs are indirectly connected.

      If a fault occurs on the BGP LSP between PEs, traffic is iterated to the MPLS local IFNET tunnel, not a backup BGP LSP. Because the MPLS local IFNET tunnel cannot forward traffic, traffic is interrupted. To prevent the traffic interruption, run this command to disable the establishment of an MPLS local IFNET tunnel between PEs.

    7. Run ipv4-family vpnv4 [ unicast ]

      The BGP VPNv4 address family is displayed.

    8. Run peer ipv4-address enable

      The PE is enabled to exchange VPN IPv4 routes with the peer PE.

    9. Run commit

      The configuration is committed.

Related Tasks

To improve scalability, specify an RR in each AS and establish MP-EBGP peer relationships between the RRs in ASs to save all VPNv4 routes on the RRs. Then configure PEs in each AS as the RR's clients to exchange VPNv4 routing information with the RR. The configuration is as follows:

  • Configure an ASBR to send the loopback interface IP addresses of a PE device used for peer relationship establishment to the ASBRs of other ASs and peer PE devices. The configuration is the same as Step 1 in this section.
  • Establish an MP-EBGP peer relationship between the RRs. The configuration procedure is similar to the procedure for establishing an MP-EBGP peer relationship between two PE devices. The difference is that you need to run the peer ipv4-address next-hop-invariable [ include-static-route ] command in the BGP-VPNv4 address family view of the RRs to configure them not to change the next hop when advertising routes to the EBGP peers.
  • Configure PE devices as the clients of the RR in the local AS to exchange VPNv4 routing information with the RR. For details about the configurations, see Configuring Route Reflection to Optimize the VPN Backbone Layer.
Translation
Download
Updated: 2019-04-03

Document ID: EDOC1100075353

Views: 16488

Downloads: 26

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