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

ME60 Troubleshooting Guide V1.0 (VRPv8)

This document provides the maintenance guide of the device, including daily maintenance, emergence maintenance, and typical troubleshooting.
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).
SR-TE Troubleshooting

SR-TE Troubleshooting

This section describes how to troubleshoot common SR-TE faults.

SR-TE Tunnel Is Down

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that an SR-TE tunnel is Down.

Common Causes

This section describes common causes for the fault that an SR-TE tunnel is Down.

Common causes are as follows:

  • The SR-TE tunnel configuration is incomplete.

  • The controller incorrectly calculates a path.

  • The FES entry fails to be delivered.

  • A link along the SE-TE tunnel fails.

Troubleshooting Flowchart

This section describes the troubleshooting flowchart for the fault that an SR-TE tunnel is Down.

Run the display mpls te tunnel-interface command and check that the SR-TE LSP is Down.

The fault locating roadmap is as follows:
  • Check that the SR-TE tunnel configuration is incomplete.

  • Check that the controller incorrectly calculates a path.

  • Check that the FES entry fails to be delivered.

  • Check that a physical link fails.

Figure 4-100 illustrates the troubleshooting flowchart.

Figure 4-100 Troubleshooting flowchart for the fault that an SR-TE tunnel is Down

Troubleshooting Procedure

This section describes the troubleshooting procedure for the fault that an SR-TE tunnel is Down.

NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check that the SR-TE tunnel configuration is incomplete.

    Run the display current-configuration command on a node that has the tunnel reside. Check whether the following commands are run in the tunnel interface view. If any command is missing, the configuration is incomplete.

    #
    interface Tunnel1
     ip address unnumbered interface LoopBack0
     tunnel-protocol mpls te
     destination 3.3.3.3
     mpls te tunnel-id 1
     mpls te signal-protocol segment-routing
     mpls te pce delegate

    • If a configuration is missing, reconfigure it and run the commit command to make the modification take effect.

    • If the configuration is complete, go to Step 2.

  2. Check that the controller incorrectly calculates a path.

    Run the display mpls te tunnel path command on a forwarder to check SR-TE path information (label stack information). If output is displayed, the controller has delivered label stack information. If no output is displayed, the controller does not deliver label stack information.

    <HUAWEI> display mpls te tunnel path
    Tunnel Interface Name : Tunnel1
    Lsp ID : 1.1.1.1 :1 :21
    Hop Information
    Hop 0 Node label 330002 NAI 10.1.2.2
    Hop 1 Node label 330002 NAI 10.1.3.1
    Hop 2 Link label 1003
    Hop 3 Link label 1004

    • If the controller does not deliver label stack information, check the controller status and the path calculation process.

    • If the controller has delivered label stack information, go to Step 3.

  3. Check that the FES entry fails to be delivered.

    Run the display mpls te forwarding-table command on the forwarder to check FES entry delivery information. If FES entry information is displayed, the entry has been delivered. If no FES entry information is displayed, the entry fails to be delivered.

    • If the entry fails to be delivered, check the delivery process.

    • If the entry has been delivered, go to Step 4.

  4. Check that a physical link fails.

    1. Run the display mpls bfd session command on the forwarder to check BFD session information.
      <HUAWEI> display mpls bfd session
      -----------------------------------------------------------------------------
                              BFD Information: TE TUNNEL
      --------------------------------------------------------------------------------
      FEC                   DISC OUT IF          NEXTHOP         TUNNEL          STATE
      --------------------------------------------------------------------------------
      4.4.4.4              16385 GE3/0/0        192.168.12.1    Tun3/0/5001     Down
      --------------------------------------------------------------------------------
      • If the BFD session is not Up, check for link faults hop by hop based on path information.

      • If the BFD session is Up, go to Step b.

    2. Run the tracert lsp command on the forwarder to check for a faulty node on the path. If a node fails, rectify the node failure.
      <HUAWEI> tracert lsp segment-routing  te Tunnel 1
        LSP Trace Route FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1 , press CTRL_C to break.
        TTL    Replier            Time    Type      Downstream
        0                                 Ingress   3.4.0.3/[330000 ]
        1      3.3.3.3            2 ms    Egress 

  5. Collect the following information and contact technical support personnel.

    • Results of the preceding procedure
    • Configuration, log, and alarm files of the device

Relevant Alarms and Logs

This section describes relevant alarms and logs for the fault that an SR-TE tunnel is Down.

Relevant Alarms

None

Relevant Logs

None

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 13776

Downloads: 257

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