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.


CLI-based Configuration Guide - Network Management and Monitoring

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R009

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 UDP Jitter Test Instance

Configuring a UDP Jitter Test Instance


When configuring a UDP Jitter test instance, configure reachable routes between the UDP Jitter client and the UDP Jitter server.

You can set the number of packets to be sent consecutively in each test instance. This configuration is used to simulate certain traffic. For example, G.711 traffic can be simulated within 1 minute by sending 3000 UDP packets at an interval of 20 milliseconds.


Configuring NTP on the client and the server can effectively improve the accuracy of the test.

The NQA client also functions as the UDP Jitter client. The jitter obtained in this test is the UDP Jitter. Perform the following steps on the NQA client.

The timeout, probe-count, frequency, jitter-packetnum, and interval commands constrain each other; therefore, properly set the values when running the five 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 comply with the following rules:

    frequency > probe-count × jitter-packetnum × interval + timeout


  • Configure the UDP Jitter server.
    1. Run system-view

      The system view is displayed.

    2. Run nqa-server udpecho [ vpn-instance vpn-instance-name ] { auto-address | ip-address | ipv6 ipv6-address } port-number

      The monitoring IP address and port number of the UDP server are configured.

  • Configure the NQA client.
    1. Run system-view

      The system view is displayed.

    2. (Optional) Run nqa-jitter tag-version version-number

      The version number is configured for Jitter packets.

      By default, the version number of Jitter test packets is 1.

      After setting the version number of the Jitter test packets to 2 and enabling the NQA client to collect statistics about packet loss in one direction, you can view the number of lost packets on the link from the source to the destination, from the destination to the source, or from unknown directions. Based on these statistics, you can easily locate network faults and detect malicious attacks.

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

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

    4. Run test-type jitter

      The test type is set to Jitter.

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

      The destination address is configured.

    6. Run destination-port port-number

      The destination port number is configured.

    7. (Optional) Run the following commands as required to configure parameters for the Jitter test:

      • Run description string

        A description is configured for the test instance.

      • Run frequency interval

        The test period is set for the NQA test instance.

      • Run timeout time

        The timeout period of a probe is set for the NQA test instance.

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

        The source IP address is configured.

      • Run source-port port-number

        The source port number is configured.

      • Run ttl number

        The TTL value in the NQA test packet is set.

      • Run datasize size

        The packet size is set for the NQA test instance.

      • Run datafill fillstring

        The padding field is configured for the NQA test instance.

      • Run source-interface interface-type interface-number

        The source interface that sends test packets is configured.

      • Run sendpacket passroute

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

        By default, the NQA test packets are sent with searching the routing table.

      • Run probe-count number

        The number of probes in each test is set.

        By default, the number of probes is 3.

      • Run tos value

        Type of Service (TOS) is set for the test packet.

      • Run fail-percent percent

        The failure percentage is set for the NQA test instance.

        By default, the failure percentage is 100%, that is, the test is regarded failed only when all the probes fail.

      • Run interval { milliseconds interval | seconds interval }

        The interval at which test packets are sent is set.

        A shorter interval enables a test to be complete sooner. Delays occur during the sending and receiving of test packets on the processor. Therefore, if the interval for sending test packets is short, the Jitter test results are inaccurate.

      • Run jitter-packetnum number

        The number of test packets sent in each probe is set.

        By default, 20 packets are sent each time in each test.

        The Jitter test is used to collect and analyze the delay variation during the UDP packet transmission. To improve the accuracy of the test result, the system sends multiple test packets each time. The more test packets are sent, the more accurate the statistics are, and the longer the test lasts.


        The probe-count command sets the number of Jitter probes and the jitter-packetnum command sets the number of test packets sent during each probe. The product of probe count multiplied by the number of test packets must be smaller than or equal to 3000.

      • Run jitter-codec { g711a | g711u | g729a }

        The code type is configured for jitter tests of analog voice services.

        This command is applied only to jitter tests of analog voice services.

      • Run adv-factor factor-value

        The advantage factor is configured for analog voice test calculation.

        This command is applied only to jitter tests of analog voice services.

      • Run vpn-instance vpn-instance-name

        The VPN instance name is configured.

      • Run records history number

        The maximum number of historical records is set for the NQA test instance.

      • Run records result number

        The maximum number of result records is set for the NQA test instance.

      • Run agetime hh:mm:ss

        The aging time is set for the NQA test instance.

      • Run timestamp-unit millisecond

        The timestamp unit is set for the NQA test instance.

      • Run packet-rewrite-check { alternant-binary | same-binary }

        The NQA packet rewrite check function is configured by padding NQA packets.

Updated: 2019-05-17

Document ID: EDOC1000174072

Views: 120555

Downloads: 368

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next