The UDP-tracert test is used to detect the path for forwarding packets from the NQA client to the destination device and record the delay of packet forwarding from the source device to each intermediate device.
nqa test-instance admin-name test-name
test-type trace
destination-address ipv4 ip-address
| Item | Command | Description |
|---|---|---|
| Configuring description of a test instance | description description-information | - |
| Configuring a tested VPN instance | vpn-instance vpn-instance-name | - |
| Configuring the destination port | destination-port port-number | - |
| Configuring the number of failed hops for the Traceroute test instance | tracert-hopfailtimes times | By default, the number of failed hops is set to 5. |
| Configuring the initial TTL and maximum TTL of the test packet | tracert-livetime first-ttl first-ttl max-ttl max-ttl | By default, the initial TTL value is set to 1 and the maximum TTL value is set to 30. |
| Setting the source IP address of test packets | source-address ipv4 ip-address | By default, no source IP address is specified for test packets. The packets use the primary IP address of the outbound interface as their source IP address. The specified source IP address must be the IP address of an Up interface on the FW. Otherwise, the test will fail. |
| Setting the payload size of test packets | datasize size | By default, the payload size is 12 bytes. When the value of datasize is smaller than 12, the FW still constructs the payload of a packet based on 12 bytes. When the value of datasize is larger than 12, the FW constructs the payload of a packet based on the value of datasize. |
| Setting the padding field of test packets | datafill string | By default, the FW pads the payload using a fixed string. The character string specified by datafill is used to circularly fill in the payload from the 12th byte. That is, the datafill configuration is valid only when the value of datasize is larger than 12. |
| Configuring the number of probes in a single test (a probe indicates that a probe packet is sent to a node with a specific TTL value) | probe-count number | By default, one test initiates three probes. |
| Setting the test interval | frequency interval | By default, no test interval is set, and the test runs only once. |
| Setting the timeout for a single probe | timeout time | By default, the expiration time for a single probe in the UDP-tracert test is 3s. |
| Configuring the maximum number of historical records | records history number | By default, there are a maximum of 50 historical records. |
| Configuring the maximum number of test result records | records result number | By default, a maximum of five test results are recorded. |
| Setting the aging time of a test instance | agetime hh:mm:ss | The default value is 0. That is, test instances are never aged. |
| Configuring the system to send test packets without querying the routing table | sendpacket passroute | By default, the FW forwards the test packets based on the route queried in the routing table. |
Select one of the following start modes as required.
Start the NQA test immediately.
start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } ]
Start the NQA test at a specified time point.
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 } ]
Start the NQA test after the delay of a specified period.
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 } ]
Run the display nqa results command to view the test results.
<FW> display nqa results NQA entry(admin, trace) :testFlag is inactive ,testtype is trace 1 . Test 1 result The test is finished Completion:success Attempts number:1 Disconnect operation number:0 Operation timeout number:1 System busy operation number:0 Connection fail number:0 Operation sequence errors number:0 RTT Status errors number:0 Drop operation number:0 Last good path Time:2016-01-21 14:38:58.5 1 . Hop 1 Send operation times: 3 Receive response times: 3 Min/Max/Average Completion Time: 46/47/41 Sum/Square-Sum Completion Time: 125/5349 RTD OverThresholds number: 0 Last Good Probe Time: 2016-01-21 14:38:58.3 Destination ip address:10.1.1.2 2 . Hop 2 Send operation times: 3 Receive response times: 3 Min/Max/Average Completion Time: 31/79/62 Sum/Square-Sum Completion Time: 188/13286 RTD OverThresholds number: 0 Last Good Probe Time: 2016-01-21 14:38:58.5 Destination ip address:10.2.1.2
Item |
Description |
|---|---|
Completion |
Test completion state:
|
Attempts number |
Number of tests |
Disconnect operation number |
Number of times the peer tears down the connection |
Operation timeout number |
Number of expiration times in the test |
System busy operation number |
Number of initialization or resource application failures |
Connection fail number |
Number of connection establishment failures |
Operation sequence errors number |
Number of received out-of-order packets |
RTT Stats errors number |
Number of RTT measurement failures |
Drop operation number |
Number of test packet sending failures |
Last good path Time |
Time for obtaining the latest complete trace path |
Hop 1 |
First hop |
Send operation times |
Number of sent test packets |
Receive response times |
Number of received test packets |
Min/Max/Average Completion Time |
Minimum, maximum, and average test completion periods |
Sum/Square-Sum Completion Time |
Sum and quadratic sum of completion periods |
RTD OverThresholds number |
Number of times the RTD exceeds the specified threshold |
Last Good Probe Time |
Time the last probe is complete |
Destination ip address |
Destination IP address |