The NQA Probe Period Is Too Short
The probe period configured for an NQA test instance is too short. Consequently, when a probe is still going on, the next probe begins, leading to a "no result" error. As a result, association between NQA and another protocol fails.
Scenario
An NQA test instance is configured.
Configuration Requirements
The stop command is run in the NQA view to stop the test.
The frequency interval command is run in the NQA view to configure an NQA probe period. The following inequality must be met:
Frequency > (Probe-count – 1) x Interval + Timeout
The start now command is run in the NQA view to start the test.
Misconfiguration Risks
Risk description:
If the preceding inequality is not met, a "no result" error is reported, and the board on which the NQA test instance is configured restarts. If another protocol, such as a routing protocol or VRRP, is associated with NQA, the association fails, adversely affecting service forwarding.
Identification method:
Run the display current-configuration configuration nqa command in the user view to check whether the preceding inequality is met.
In the following example, Frequency, Probe-count, Interval, and Timeout are 20s, 5, 6s, and 4s, respectively. The preceding inequality is not met, and a "no result" error will be reported.
<HUAWEI> display current-configuration configuration nqa#
nqa test-instance 1 1
test-type icmp
destination-address ipv4 127.0.0.1 frequency 20
interval seconds 6
timeout 4
probe-count 5
start now
#Recovery measures:
Ensure that the preceding inequality is met.
