NQA/4/NQA_JITTER_TEST_FAILED

Message

NQA/4/NQA_JITTER_TEST_FAILED: The NQA entry test failed. (OwnerIndex=[OwnerIndex], TestName=[TestName], TargetAddressType=[TargetAddressType], TargetAddress=[TargetAddress], OperStatus=[OperStatus], Index=[Index], RttSum=[RttSum], RttSum2Low=[RttSum2Low], RttSum2High=[RttSum2High], RttMin=[RttMin], RttMax=[RttMax], PacketOutOfSequences=[PacketOutOfSequences], Errors=[Errors], Busies=[Busies], Timeouts=[Timeouts], Drops=[Drops], ProbeResponses=[ProbeResponses], SentProbes=[SentProbes], MaxDelaySD=[MaxDelaySD], MaxDelayDS=[MaxDelayDS], JitterOut=[JitterOut], JitterIn=[JitterIn], OWSumSD=[OWSumSD], OWSumDS=[OWSumDS])

Description

The number of continuous NQA test failures reached the threshold. The default threshold is 1, indicating that each time an NQA test fails, an alarm is generated. The threshold can be changed by using the test-failtimes command.

Parameters

Parameter Name	Parameter Meaning
OwnerIndex	Indicates the administrator of an NQA test instance.
TestName	Indicates the name of an NQA test instance.
TargetAddressType	Indicates the destination address type of an NQA test instance.
TargetAddress	Indicates the destination address of an NQA test instance.
OperStatus	Indicates the status of an NQA test instance.
Index	Indicates the index of the result table.
RttSum	Indicates the RTT sum of an NQA test instance.
RttSum2Low	Indicates the lower 32 bits of the RTT square sum.
RttSum2High	Indicates the higher 32 bits of the RTT square sum.
RttMin	Indicates the minimum RTT value of an NQA test instance.
RttMax	Indicates the maximum RTT value of an NQA test instance.
PacketOutOfSequences	Indicates the number of packets with incorrect sequence numbers.
Errors	Indicates the number of packets with incorrect sequence numbers.
Busies	Indicates the number of initialization or resource application failures.
Timeouts	Indicates the number of times that no response is received within the timeout period.
Drops	Indicates the number of packets failed to be sent.
ProbeResponses	Indicates the number of received packets.
SentProbes	Indicates the number of sent packets.
MaxDelaySD	Indicates the maximum OWD from the source to the destination.
MaxDelayDS	Indicates the maximum OWD from the destination to the source.
JitterOut	Indicates the jitter in sending packets.
JitterIn	Indicates the jitter in receiving packets.
OWSumSD	Indicates the sum of OWD from the source to the destination.
OWSumDS	Indicates the sum of OWD from the destination to the source.

Possible Causes

Cause 1: The destination address was inexistent and unreachable. The number of continuous test failures in a test reached the set threshold.

Cause 2: The destination address existed, but the route was unreachable. The number of continuous test failures in a test reached the set threshold.

Cause 3: The destination port was not correctly configured, which led to the connection failure.

Procedure

1. Run the display this command in the NQA test view to check whether the destination address is correctly configured.If the destination address is incorrect, run the destination-address command in the NQA test view to change the destination address.Restart the test instance to check whether the test is successful.

If yes, go to Step 8.
If not, go to Step 2.

2. Run the ping command in the NQA test view to check whether the route is reachable.

If the destination address is correct but the route is unreachable, run the display ip routing-table command to check the routing table and rectify the route fault.If the test still fails, go to Step 7.
If the route is reachable, go to Step 3.

3. Run the display this command in the NQA test view to check whether the destination port is correctly configured.If the parameter settings are incorrect, run the destination-port command in the NQA test view to modify the parameter settings.Restart the test instance to check whether the test is successful.

If yes, go to Step 8.
If not, go to Step 4.

4. Run the display this command in the system view to check the packet version of the jitter test instance.

If the version number is 1, go to Step 7.
If the version number is 2, go to Step 5.

5. Run the display nqa-server command to check whether the port number configured on the NQA server is correct.

If yes, go to Step 7.
If not, go to Step 6.

6. Run the nqa-server udpecho command to change the port number configured on the server.Restart the test instance to check whether the test is successful.

If yes, go to Step 8.
If not, go to Step 7.

7. Collect log and configuration information, and contact technical support personnel.

8. End.