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.


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 Bypass Tunnel

Configuring a Bypass Tunnel

A path and attributes must be configured for a bypass tunnel after TE manual FRR is enabled on a PLR.


Bypass tunnels are established on selected links or nodes that are not on the protected primary tunnel. If a link or node on the protected primary tunnel is used for a bypass tunnel and fails, the bypass tunnel also fails to protect the primary tunnel.

  • FRR does not take effect if multiple nodes or links fail simultaneously. After FRR switching is performed to switch data from the primary tunnel to a bypass tunnel, the bypass tunnel must remain Up when forwarding data. If the bypass tunnel goes Down, the protected traffic is interrupted and FRR fails. Even though the bypass tunnel goes Up again, traffic is unable to flow through the bypass tunnel but travels through the primary tunnel after the primary tunnel recovers or is reestablished.

  • By default, the system searches for an optimal manual FRR tunnel for each primary tunnel at a specific interval and binds the bypass tunnel to the primary tunnel if there is an optimal bypass tunnel.


  1. Run:


    The system view is displayed.

  2. Run:

    interface tunnel tunnel-number

    The view of the bypass tunnel interface is displayed.

  3. Run:

    tunnel-protocol mpls te

    MPLS TE is configured.

  4. Run:

    destination ip-address

    The LSR ID of an MP is configured as the destination address of the bypass tunnel.

  5. Run:

    mpls te tunnel-id tunnel-id

    The bypass tunnel ID is configured.

  6. (Optional) Run:

    mpls te path explicit-path path-name [ secondary ]

    An explicit path is configured for the bypass tunnel.


    Physical links of a bypass tunnel cannot overlap protected physical links of the primary tunnel.

  7. (Optional) Run:

    mpls te bandwidth ct0 bandwidth

    Set the bandwidth for the bypass tunnel.

  8. Run:

    mpls te bypass-tunnel

    A bypass tunnel is configured.

  9. Run:

    mpls te protected-interface interface-type interface-number

    The interface on which the bypass tunnel protects traffic is specified.

  10. Run:


    The configurations are committed.

Follow-up Procedure

Routes and labels are automatically recorded after a bypass tunnel is configured.

A bypass tunnel is established over a configured explicit path on the PLR.

If a primary tunnel fails, traffic switches to a bypass tunnel. If the bypass tunnel also goes Down, the protected traffic is interrupted, and FRR fails. Even though the bypass tunnel goes Up, traffic cannot be forwarded. Traffic will be forwarded only after the primary tunnel has been restored or re-established.

  • The mpls te fast-reroute command and the mpls te bypass-tunnel command cannot be configured on the same tunnel interface.

  • After FRR switches traffic from a primary tunnel to a bypass tunnel, the bypass tunnel must be kept Up, and its path must remain unchanged when transmitting traffic. If the bypass tunnel goes Down, the protected traffic is interrupted and FRR fails.

Updated: 2018-07-12

Document ID: EDOC1100028530

Views: 101137

Downloads: 336

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