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


To have a better experience, please upgrade your IE browser.


Configuration Guide - IP Unicast Routing

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of IP Unicast Routing, including IP Routing, Static Route, RIP, RIPng, OSPF, OSPFv3, IPv4 IS-IS, IPv6 IS-IS, BGP, Routing Policy, and PBR.
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).
(Optional) Configuring Association Between LDP and Static Routes

(Optional) Configuring Association Between LDP and Static Routes

Application Scenario

On an MPLS network with primary and secondary LSPs established using static routes, association between LDP and static routes prevents traffic from being interrupted during traffic switchover from the primary LSP to the secondary LSP when the LDP session on the primary link fails (not because of a link fault) or during traffic switchback when the primary link recovers from a fault.


Only static routes with outbound interfaces specified can be associated with LDP.

Pre-configuration Tasks

Before configuring association between LDP and static routes, complete the following tasks:

  • Enable MPLS.

  • Enable MPLS LDP globally and on interfaces.

  • Ensure that LDP sessions have been set up between devices.


  • Enable association between LDP and static routes.
    1. Run system-view

      The system view is displayed.

    2. Run ip route-static [ vpn-instance vpn-instance-name ] ip-address { mask | mask-length } interface-type interface-number [ nexthop-address ] [ preference preference | tag tag ] * ldp-sync [ arp-detect interface-type interface-number ] [ description text ]

      Association between LDP and static routes is configured.

      By default, association between LDP and static routes is not enabled.

    3. Run commit

      The configuration is committed.

  • (Optional) Set a Hold-down timer.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The outbound interface view of the primary link of the static route is displayed.

    3. On an Ethernet interface, run undo portswitch

      The interface is switched to Layer 3 mode.

      By default, an Ethernet interface works in Layer 2 mode.

      The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.


      If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

    4. Run static-route timer ldp-sync hold-down { timer | infinite }

      A period in which the static route is inactive and waits for the establishment of an LDP session is set.

      The default Hold-down time is 10s.

      • If the Hold-down time is 0s, association between LDP and static routes on the interface is disabled.

      • If the Hold-down time is infinite, the static route becomes active and MPLS traffic switching is performed only after an LDP session is established.

    5. Run commit

      The configuration is committed.

      The preceding configurations need to be performed on both ends of the primary and secondary links.

Updated: 2019-04-20

Document ID: EDOC1100074760

Views: 46937

Downloads: 58

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