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

NE20E-S V800R010C10SPC500 Configuration Guide - MPLS 01

This is NE20E-S V800R010C10SPC500 Configuration Guide - MPLS
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).
Enabling BGP Peers to Exchange Labeled IPv4 Routes

Enabling BGP Peers to Exchange Labeled IPv4 Routes

In the seamless MPLS networking, before an E2E BGP LSP is established, BGP peers must be able to exchange labeled IPv4 routes with each other.

Procedure

  • Perform the following steps on each CSG, AGG, and MASG:
    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 | group-name } label-route-capability [ check-tunnel-reachable ]

      The ability to exchange labeled IPv4 routes between devices in the local AS is enabled.

      • If the check-tunnel-reachable is configured, a local device advertises an IPv4 unicast route to its peer if a tunnel between the local and remote devices is unreachable and advertises a labeled IPv4 route if the tunnel is reachable. This parameter helps prevent a data forwarding failure when an MP-EBGP peer relationship between the CSG and MASG is established but an LSP over the peer relationship fails to be established.

      • If the check-tunnel-reachable parameter is not configured, the local device advertises a labeled IPv4 route, regardless of whether a tunnel between the local and remote devices is unreachable.

    4. Run commit

      The configuration is committed.

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

      The system view is displayed.

    2. Run interface interface-type interface-number

      The view of the interface connected to the peer ASBR is displayed.

    3. Run ip address ip-address { mask | mask-length }

      An IP address is assigned to the interface.

    4. Run mpls

      MPLS is enabled.

    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 } label-route-capability [ check-tunnel-reachable ]

      The ability to exchange labeled IPv4 routes between BGP peers, including the peer ASBR and the devices in the local AS, is enabled.

      • If the check-tunnel-reachable is configured, a local device advertises an IPv4 unicast route to its peer if a tunnel between the local and remote devices is unreachable and advertises a labeled IPv4 route if the tunnel is reachable. This parameter helps prevent a data forwarding failure when an MP-EBGP peer relationship between the CSG and MASG is established but an LSP over the peer relationship fails to be established.
      • If the check-tunnel-reachable parameter is not configured, the local device advertises a labeled IPv4 route, regardless of whether a tunnel between the local and remote devices is unreachable.

    8. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055103

Views: 19767

Downloads: 35

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