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 - Network Management and Monitoring

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of Network Management and Monitoring, including SNMP, RMON, NETCONF, OpenFlow, LLDP, NQA, Mirroring, Packet Capture, Packet Trace, Path and Connectivity Detection Configuration, NetStream, sFlow, and iPCA.
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 the LSP Trace Test

Configuring the LSP Trace Test


The NQA LSP Trace test can be used to test the invalid nodes on the LSP tunnel.


Perform the following steps on the NQA client.

The timeout, probe-count, and frequency commands constrain each other; therefore, properly set the values when running the three commands. Improper command settings may lead to test failure.

  • On a network with poor quality and low transmission rate, increase the timeout value to ensure that the response to NQA detection packets can be received.
  • On a network with low reliability, increase the probe-count value because multiple detection packets may need to be sent to ensure successful detection.
  • The frequency value must be greater than or equal to 60s.


  1. Run system-view

    The system view is displayed.

  2. Run nqa test-instance admin-name test-name

    An NQA test instance is created and the test instance view is displayed.

  3. Run test-type lsptrace

    The test type is set to LSP Trace.

  4. Configure the LSP trace test for the LSP tunnel.

    • Run lsp-type ipv4

      The test type of LSP Trace is configured.

    • Run destination-address ipv4 ipv4-address [ lsp-masklen masklen | lsp-loopback loopback-address ] *

      The destination IP address to be tested is configured.

  5. (Optional) Perform the following as required to configure other parameters for the LSP Trace test:

    • Run lsp-replymode { level-control-channel | no-reply | udp }

      The response mode of the LSP trace test is set.


      In a uni-directional LSP Trace test, if the lsp-replymode no-reply command is configured, the test result shows that the test fails regardless of whether the test is successful or fails. If the test is successful, the test result also displays the number of the timeout packets. If the test fails, the test result displays the number of the discarded packets.

    • Run lsp-exp exp

      The LSP EXP value is set.

    • Run tracert-hopfailtimes times

      The number of hops after which the test is considered failed is set.

    • Run tracert-livetime first-ttl first-ttl max-ttl max-ttl

      The initial and the maximum TTL values of the packet are set.

    • Run fragment enable

      MPLS packet fragmentation is enabled for an NQA test instance.

    • Run description string

      A description is configured for the test instance.

    • Run frequency interval

      The interval at which an NQA test instance is automatically performed is set.

    • Run timeout time

      The timeout period of a probe is set.

    • Run source-address ipv4 ipv4-address

      The source IP address is configured.

    • Run probe-count number

      The number of probes in each test is set.

    • Run records history number

      The maximum number of historical records is set.

    • Run records result number

      The maximum number of result records is set.

    • Run agetime hh:mm:ss

      The aging time is set for the test instance.

  6. Run commit

    The configuration is committed.

Updated: 2019-04-20

Document ID: EDOC1100075365

Views: 40540

Downloads: 127

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