Configuring a Trace Test

Procedure

1. Run system-view

   The system view is displayed.

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

      The test instance type is set to trace.

   3. (Optional) Run description description

      A description is configured for the NQA test instance.

3. Specify the destination address and destination port number for the test instance.
   1. Run destination-address { ipv4 destAddress | ipv6 destAddress6 }

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

   2. (Optional) Run destination-port port-number

      The destination port number is specified for the NQA test instance.

4. (Optional) Set parameters for the test instance to simulate packets.
   1. Run agetime ageTimeValue

      The aging time of an NQA test instance is configured.

   2. Run datafill fill-string

      Padding characters in NQA test packets are configured.

   3. Run datasize datasizeValue

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

   4. Run probe-count number

      The number of probes in a test 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.

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

      The source IP address of NQA test packets is set.

   7. Run source-interface ifType ifNum

      The source interface of NQA test packets is set.

   8. Run tos tos-value [ dscp ]

      The ToS value of NQA test packets is set.

   9. Run nexthop { ipv4 ipv4Address | ipv6 ipv6Address }

      The next-hop address of the test instance is set.

   10. Run tracert-livetime first-ttl first-ttl max-ttl max-ttl

       The TTL of test packets is set.

5. (Optional) Run the set-df command to prevent packet fragmentation.

   Use a trace test instance to obtain the path MTU as follows:

   Run the set-df command to disable packet fragmentation. Then, run the datasize command to set the size of the packet data area. After that, start the test instance. If the test is successful, the size of the sent packet's data area is smaller than the path MTU. Then, keep increasing the packet data area size using the datasize command until the test fails. If the test fails, the size of the sent packet's data area is greater than the path MTU. The maximum size of the packet that can be sent without being fragmented is used as the path MTU.

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

      The response timeout period is set.

      If no response packets are received before the set period expires, the probe is regarded as a failure.

   2. Run tracert-hopfailtimes hopfailtimesValue

      The maximum number of hop failures in a probe is set.

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

8. (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 test failures reaches the specified value.

   2. Run threshold rtd thresholdRtd

      The RTD threshold is set.

   3. Run send-trap{ all | [ rtd | testfailure | testcomplete ]^* }

      The condition for triggering a trap is configured.

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.