Configuring an ICMP Jitter Test

Procedure

1. Run system-view

   The system view is displayed.

2. Create an NQA test instance and set the test instance type to ICMP 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 icmpjitter

      The test instance type is set to ICMP Jitter.

   3. (Optional) Run description description

      A description is configured for the NQA test instance.

3. Run destination-address { ipv4 destAddress | ipv6 destAddress6 }

   The destination address (that is, the NQA server address) of the client is specified.

4. (Optional) Run hardware-based enable

   The hardware forwarding engine on an interface board is enabled to send packets.

   

   After you enable the interface board to send packets on a client, run the nqa-server icmp-server [ vpn-instance vpn-instance-name ] ip-address command on the NQA server to specify the IP address of the ICMP services monitored by the NQA server.

5. (Optional) Set timestamp units for the NQA test instance.
   

   The timestamp units need to be configured only after the hardware-based enable command is run.

   1. Run timestamp-unit { millisecond | microsecond }

      A timestamp unit is configured for the source in the NQA test instance.

   2. Run receive-timestamp-unit { millisecond | microsecond }

      A timestamp unit is configured for the destination in the NQA test instance.

      In a scenario where a Huawei device is connected to a non-Huawei device, an ICMP jitter test in which the Huawei device functions as the source (client) is configured to detect the delay, jitter, and packet loss on the network. To set the timestamp unit of the ICMP timestamp packet returned by the destination, run the receive-timestamp-unit command.

      The source's timestamp unit configured using the timestamp-unit { millisecond | microsecond } command must be the same as the destination's timestamp unit configured using the receive-timestamp-unit command. If the timestamp unit is set to microseconds and the interface board's precision that the device supports is milliseconds, the device uses milliseconds as the timestamp unit.

6. Set parameters for the test instance to simulate packets.
   1. Run agetime ageTimeValue

      The aging time of an NQA test is configured.

   2. Run icmp-jitter-mode { icmp-echo | icmp-timestamp }

      The mode for an ICMP jitter test is set.

      

      IPv6 network does not support this function.

   3. Run datafill fill-string

      Padding characters in NQA test packets are configured.

      This parameter can be configured only when icmp-jitter-mode is icmp-echo.

   4. Run datasize datasizeValue

      The size of the data field in an NQA test packet is set.

   5. Run jitter-packetnum packetNum

      The number of packets sent each time in a probe is set.

   6. Run probe-count number

      The number of probes in a test is set for the NQA test instance.

   7. Run interval { milliseconds interval | seconds interval }

      The interval at which NQA test packets are sent is set for the NQA test instance.

   8. Run source-address{ ipv4 srcAddress | ipv6 srcAddr6 }

      The source IP address of NQA test packets is set.

   9. Run ttl ttlValue

      The TTL value in NQA test packets is set.

   10. Run tos tos-value

       The ToS value in NQA test packets is set.

7. (Optional) Configure test failure conditions.
   1. Run timeout time

      The response timeout period is set.

   2. Run fail-percent percent

      The failure percentage is set for the NQA test instance.

8. (Optional) Configure the NQA statistics function.

   Run records { history number | result number }

   The maximum number of history records and the maximum number of result records that can be saved for the NQA test instance are set.

9. (Optional) Run vpn-instance vpn-instance-name

   The VPN instance name is configured for the NQA test instance.

10. Schedule the 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 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 startat [ 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 startdailyhh:mm:sstohh:mm:ss [ beginyyyy/mm/dd ] [ endyyyy/mm/dd ] command.

11. Run commit

    The configuration is committed.