Configuring a UDP Jitter Test

A UDP jitter test measures the end-to-end jitter time for various services or simulates a voice test. Although the Internet Control Message Protocol (ICMP) reply function may be disabled on devices on the public network to defend against network attacks, the UDP jitter test can still be conducted.

Procedure

Configure the NQA server for the UDP jitter test.
1. Run system-view
  
  The system view is displayed.
2. Run nqa-server udpecho [ vpn-instance vpn-instance-name ] ip-address port-number
  
  The IP address and number of the port used to monitor UDP services are specified on the NQA server.
3. Run commit
  
  The configuration is committed.
Configure the NQA client for the UDP jitter test.
1. Run system-view
  The system view is displayed.
2. (Optional) Run nqa-jitter tag-version version-number
  The packet version is configured for a UDP jitter test instance.
  
  Packet statistics collected in version 2 is more accurate than those in version 1. Packet version 2 is recommended.
3. Create an NQA test instance and set the test instance type to UDP jitter.
  1. Run nqa test-instance admin-name test-name
    
    An NQA test instance is created, and the view of the test instance is displayed.
  2. Run test-type jitter
    The test instance type is set to UDP jitter.
  3. (Optional) Run description description
    
    A description is configured for the test instance.
4. The destination address and destination port number are set for the test instance.
  1. (Optional) Run destination-address { ipv4 destAddress | ipv6 destAddress6 }
    The client's destination address that is the NQA server address is specified.
  2. Run destination-port port-number
    
    The destination port number is specified for the UDP jitter test.
5. (Optional) Run hardware-based enable
  The hardware forwarding engine on an interface board is enabled to send packets and add timestamps to the packets.
6. (Optional) Run timestamp-unit { millisecond | microsecond }
  A timestamp unit is configured for the NQA test instance.
  
  The timestamp units need to be configured only after the hardware-based enable command is run.
7. (Optional) Configure the code type and advantage factor for simulated voice test calculation.
  1. Run jitter-codec { g711a | g711u | g729a }
    
    The code type is set for the simulated voice test.
  2. Run adv-factor factor-value
    
    The advantage factor for simulated voice test calculation is set.
8. (Optional) Set parameters for the test instance to simulate packets.
  1. Run datasize datasizeValue
    
    The size of the data field in an NQA test packet is configured.
  2. Run jitter-packetnum number
    
    The number of packets sent each time in a probe is set.
  3. Run probe-count number
    
    The number of probes is set for an NQA test instance.
  4. Run interval { milliseconds interval | seconds interval }
    
    The interval at which NQA test packets are sent is set for the NQA test instance.
  5. Run sendpacket passroute
    
    The NQA test instance is configured to send packets without searching the routing table.
    
    IPv6 network does not support this function.
  6. Run source-address{ ipv4 ip-address | ipv6 ipv6–address }
    The source IP address of NQA test packets is set.
  7. Run source-port portValue
    
    The source port number is set for the NQA test instance.
  8. Run tos tos-value
    
    The ToS value in NQA test packets is set.
  9. Run ttl ttlValue
    
    The TTL value in NQA test packets is set.
9. (Optional) Configure test failure conditions.
  - Run timeout time
    
    The response timeout period is set.
    
    If no response packets are received after the configured period elapses, the probe fails.
  - Run fail-percent percent
    
    The failure percentage is set for the NQA test instance.
    
    If the percentage of failed probes is greater than or equal to the configured failure percentage, the test is considered as a failure.
10. (Optional) Configure the NQA statistics function.
  Run records { history number | result number }
  
  The maximum number of historical records and the maximum number of result records that can be saved for the NQA test instance are set.
11. (Optional) Enable the device to send traps to the NMS.
  1. Run test-failtimes failTimes
    
    The NQA test instance is configured to send a trap message to the NMS when the number of continuous probe failures reaches the specified value.
  2. Run threshold { owd-ds owd-ds-value | owd-sd owd-sd-value | rtd thresholdRtd }
    
    The thresholds for the round-trip delay (RTD) and one-way delay (OWD) are set.
  3. Run send-trap { all | [ owd-ds | owd-sd | rtd | testfailure ]^* }
    
    The condition for triggering a trap is configured.
12. (Optional) Run vpn-instance vpn-instance-name
  The VPN instance name is configured for the NQA test instance.
13. Schedule the NQA test instance.
  1. (Optional) Run frequency frequencyValue
    
    The test period is set for the NQA test instance.
  2. Run start
    
    An NQA test is started.
    
    The start command has multiple formats. Choose one of the following formats as needed.
    - To start an NQA test instance immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.
    - To start an NQA test instance at a specified time, run the start at [ yyyy/mm/dd ] hh:mm:ss [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.
    - To start an NQA test instance after a specified delay, run the start delay { seconds second | hh:mm:ss } [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.
    - To start an NQA test instance at a specified time every day, run the start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.
14. Run commit
  The configuration is committed.