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

NE40E V800R010C00 Configuration Guide - MPLS 01

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

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 assign 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-assign an MPLS label to the transit node and advertises the label upstream.

Procedure

  • Perform the following steps on each CSG 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 assign a label to an IPv4 route.

    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 or a 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. Run:

      commit

      The configuration is committed.

  • Perform the following steps on each AGG, 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.

    4. Run:

      apply mpls-label

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

    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.

      NOTE:

      Repeat this step for each BGP peer.

    8. Run:

      commit

      The configuration is committed.

    NOTE:

    If the MTU of LDP LSPs is different from that of BGP LSPs, traffic may fail to be forwarded. To set an MTU for BGP LSPs, run the bgp-lsp mtu mtu command.

    If the MTU of LDP LSPs is different from that of BGP local IFNET tunnels, traffic may fail to be forwarded. To set an MTU for BGP local IFNET tunnels, run the bgp-local-ifnet mtu mtu command.

Download
Updated: 2018-07-12

Document ID: EDOC1100028530

Views: 101072

Downloads: 336

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