The communication data between two devices on a network may need to traverse other devices. To fully monitor a network, you can configure path jitter test.
Perform the following configurations on the NQA client:
The system view is displayed.
An NQA test instance is created and the test instance view is displayed.
The test type is set to path jitter.
The destination address is configured.
To configure description for the test instance, run the description string command.
To set the test interval, run the frequency interval command.
To set the timeout period for a probe in an NQA test instance, run the timeout time command.
To set the Type of Service (ToS) for the test instance, run the tos value command.
To set the maximum number of historical records, run the records history number command.
To set the aging time of the test instance, run the agetime hh:mm:ss command.
To set the test mode of the path jitter test, run the icmp-jitter-mode { icmp-echo | icmp-timestamp } command.
By default, the test mode is icmp-timestamp.
The datafill and datasize parameters are valid only when the icmp-jitter-mode is set to icmp-echo.
To configure the pad characters, run the datafill fillstring command.
To set the size of Echo Request packets excluding the IP header, run the datasize size command.
Run vpn-instance vpn-instance-name
The VPN instance name is configured.
To configure the source IP address, run the source-address ipv4 ipv4-address command.
To set the number of probes sent each time, run the probe-count number command.
To set the number of test packets sent during each test, run the jitter-packetnum number command.
The probe-count command sets the number of path jitter tests and the jitter-packetnum command sets the number of test packets sent during each test. The value of probe-count multiplied by the value of jitter-packetnum cannot exceed 3000.
To set an interval for sending test packets, run the interval { milliseconds interval | seconds interval } command.
The shorter the interval is, the sooner the test is complete. Generally, the CPU has a delay in sending and receiving test packets. Therefore, an excessively short interval will make the test statistics inaccurate.
To set the percentage of the failed NQA test instances, run the fail-percent percent command.