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 a Trace Test Instance

Configuring a Trace Test Instance


An NQA trace test detects the forwarding path between the source and the destination and collects statistics, such as delay, about each device along the forwarding path. The function of a trace test is similar to the function of the tracert command, except that the trace test provides more information. Information about each hop includes the average delay, packet loss ratio, and time of receiving the last packet.


  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 NQA view is displayed.

  3. Run test-type trace

    The test type is set to trace.

  4. Run destination-address { ipv4 ipv4-address | ipv6 ipv6-address }

    The destination address for the trace instance test is configured.

  5. (Optional) Run the following commands as required to configure parameters for the trace test instance.

    • Run description string

      A description is configured for the test instance.

    • Run destination-port port-number

      The destination port number is configured.

    • Run source-address { ipv4 ipv4-address | ipv6 ipv6-address }

      The source IP address is configured.

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

      The initial and the maximum TTL values of packets are configured.

    • Run tracert-hopfailtimes times

      The hop fail times are set.

    • Run set-df

      Packet fragmentation is prohibited.


      This command is invalid when the source and destination addresses are IPv6 addresses.

    • Run datasize size

      The packet size is set.

    • Run datafill fillstring

      The padding field is configured.

    • Run sendpacket passroute

      The NQA test instance is configured to send packets without searching the routing table.

    • Run vpn-instance vpn-instance-name

      The VPN instance name is configured.

    • 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.

    • Run timeout time

      The timeout period of a probe is set.

    • Run probe-count number

      The number of probes in a test is set.


      When a trace test instance is used, the number of probes for each test cannot be larger than 10.

    • Run frequency interval

      The test period is set.

      • When a trace test instance is used, the test period cannot be shorter than 60s.

      • 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.

  6. Run commit

    The configuration is committed.

Updated: 2019-04-20

Document ID: EDOC1100075365

Views: 35265

Downloads: 123

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