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 - MPLS

S7700 and S9700 V200R010C00

This document describes MPLS configurations supported by the switch, including the principle and configuration procedures of static LSPs, MPLS LDP, MPLS TE, MPLS QoS, MPLS OAM, Seamless MPLS, and MPLS common features, and provides configuration examples.
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 a BGP LSP

Configuring a BGP LSP

Context

Before a BGP LSP is established, a routing policy must be configured to control label distribution. The egress of the BGP LSP to be established needs to distribute an MPLS label to the route advertised to an upstream node. If a transit node receives a labeled IPv4 route from downstream, the downstream node must re-distribute an MPLS label to the transit node and advertises the label upstream.

Procedure

  • Perform the following steps on each AGG and MASG:
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      route-policy route-policy-name permit node node

      A Route-Policy node is created.

    3. Run:

      apply mpls-label

      The local device is enabled to distribute a label to an IPv4 route.

      By default, the action of distributing MPLS labels to public routes is not configured in the routing policy.

    4. Run:

      quit

      Return to the system view.

    5. Run:

      bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    6. Run:

      peer { ipv4-address | group-name } route-policy route-policy-name export

      A routing policy for advertising routes matching Route-Policy conditions to a BGP peer (group) is configured.

      By default, no policy for filtering routes from its BGP peer (group) or routes to be advertised to its BGP peer (group) is configured.

      NOTE:

      Repeat this step for each BGP peer.

    7. Run:

      network ip-address [ mask | mask-length ] [ route-policy route-policy-name ]

      The route destined for the loopback interface address is advertised.

      This route is labeled and advertised along a path over which a BGP LSP is established.

    8. (Optional) Run:

      peer { group-name | ipv4-address } mpls-local-ifnet disable

      The ability to establish an MPLS local IFNET tunnel between an AGG and MASG is disabled.

      In the inter-AS seamless MPLS+HVPN network transmitting L3VPN services, an AGG and MASG establish an MP-EBGP peer relationship. Therefore, an MPLS local IFNET tunnel between the AGG and MASG is established over the MP-EBGP peer relationship. The MPLS local IFNET tunnel fails to transmit traffic because the AGG and MASG are indirectly connected.

      If a fault occurs on the BGP LSP between the AGG and MASG, traffic is iterated to the MPLS local IFNET tunnel, not an FRR bypass tunnel. As the MPLS local IFNET tunnel cannot forward traffic, traffic is interrupted. To prevent the traffic interruption, run the peer mpls-local-ifnet disable command to disable the establishment of an MPLS local IFNET tunnel between the AGG and MASG.

  • Perform the following steps on each AGG ASBR and core ASBR:
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      route-policy route-policy-name permit node node

      A Route-Policy node is created.

    3. Run:

      if-match mpls-label

      An IPv4 route is enabled to match an MPLS label.

      By default, no MPLS label-based matching rule is configured in the routing policy.

    4. Run:

      apply mpls-label

      The local device is enabled to distribute a label to an IPv4 route.

      By default, the action of distributing MPLS labels to public routes is not configured in the routing policy.

    5. Run:

      quit

      Return to the system view.

    6. Run:

      bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    7. Run:

      peer { ipv4-address | group-name } route-policy route-policy-name export

      A routing policy for advertising routes matching Route-Policy conditions to a BGP peer or a BGP peer group is configured.

      By default, no policy for filtering routes from its BGP peer (group) or routes to be advertised to its BGP peer (group) is configured.

      NOTE:

      Repeat this step for each BGP peer.

Translation
Download
Updated: 2019-04-18

Document ID: EDOC1000141902

Views: 70357

Downloads: 189

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