NQA_1.3.6.1.2.1.80.0.2 pingTestFailed

Trap Buffer Description

Ping entry test failed. (OwnerIndex=[OwnerIndex], TestName=[TestName], TargetAddressType=[TargetAddressType], TargetAddress=[TargetAddress], OperStatus=[OperStatus], AddressType=[AddressType], Address=[Address], MinRtt=[MinRtt], MaxRtt=[MaxRtt], AverageRtt=[AverageRtt], ProbeResponses=[ProbeResponses], SentProbes=[SentProbes], RttSumOfSquares=[RttSumOfSquares], LastGoodProbe=[LastGoodProbe])

The number of consecutive failed test instances reached the threshold.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	DISMANPING_TESTFAIL
Trap OID	1.3.6.1.2.1.80.0.2
MIB	DISMAN-PING-MIB
Alarm ID	This is an event trap and does not involve alarm ID.
Alarm Name	This is an event trap and does not involve alarm name.
Alarm Type	This is an event trap and does not involve alarm type.
Raise or Clear	This is an event trap and does not involve alarm generation or clearance.
Match trap	-

Trap Buffer Parameters

Parameter	Description
OwnerIndex	Administrator of the test case.
TestName	Name of an NQA test instance.
TargetAddressType	Destination address type of an NQA test instance.
TargetAddress	Destination address of an NQA test instance.
OperStatus	Status of an NQA test instance.
AddressType	Address type of an NQA test instance.
Address	Address of an NQA test instance.
MinRtt	Minimum RTT value of an NQA test instance.
MaxRtt	Maximum RTT value of an NQA test instance.
AverageRtt	Average RTT value of an NQA test instance.
ProbeResponses	Statistics on received packets.
SentProbes	Statistics on sent packets.
RttSumOfSquares	Sum of RTT squared right 32 bits.
LastGoodProbe	Time when the latest returned packet is received.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.2.1.80.1.2.1.3	pingCtlTargetAddressType	pingCtlOwnerIndex pingCtlTestName
1.3.6.1.2.1.80.1.2.1.4	pingCtlTargetAddress	pingCtlOwnerIndex pingCtlTestName
1.3.6.1.2.1.80.1.3.1.1	pingResultsOperStatus	pingCtlOwnerIndex pingCtlTestName
1.3.6.1.2.1.80.1.3.1.2	pingResultsIpTargetAddressType	pingCtlOwnerIndex pingCtlTestName
1.3.6.1.2.1.80.1.3.1.3	pingResultsIpTargetAddress	pingCtlOwnerIndex pingCtlTestName
1.3.6.1.2.1.80.1.3.1.4	pingResultsMinRtt	pingCtlOwnerIndex pingCtlTestName
1.3.6.1.2.1.80.1.3.1.5	pingResultsMaxRtt	pingCtlOwnerIndex pingCtlTestName
1.3.6.1.2.1.80.1.3.1.6	pingResultsAverageRtt	pingCtlOwnerIndex pingCtlTestName
1.3.6.1.2.1.80.1.3.1.7	pingResultsProbeResponses	pingCtlOwnerIndex pingCtlTestName
1.3.6.1.2.1.80.1.3.1.8	pingResultsSentProbes	pingCtlOwnerIndex pingCtlTestName
1.3.6.1.2.1.80.1.3.1.9	pingResultsRttSumOfSquares	pingCtlOwnerIndex pingCtlTestName
1.3.6.1.2.1.80.1.3.1.10	pingResultsLastGoodProbe	pingCtlOwnerIndex pingCtlTestName

Impact on the System

The system will not be affected.

Possible Causes

Cause 1: The destination address was inexistent and unreachable.

Cause 2: The destination address exists, but the route was unreachable.

Cause 3: Because of the network latency, the Rtt of the packet was longer than the set timeout period.

Procedure

1. Run the display this command in the NQA test view to check whether the destination address is correctly configured.

If the parameter settings are correct, go to step 2.
If the parameter settings are incorrect, run the destination-address command in the NQA test view to change the destination address.Restart the test instance and check whether the alarm is cleared.
If yes, go to Step 5.
If no, go to Step 2.

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

If the route is reachable, go to step 3.
If the route is unreachable, run the display ip routing-table command to check the routing table and rectify the route fault.Restart the test instance and check whether the alarm is cleared.
If yes, go to Step 5.
If no, go to Step 3.

3. Run the timeout command in the NQA test instance view to change the timeout period based on the network conditions. The default value 3 is recommended. The value ranges from 1 to 60. You can run the display this command in the NQA test view to view the current timeout period.Restart the test instance and check whether the alarm is cleared.

If yes, go to Step 5.
If no, go to Step 4.

4.Collect alarm and configuration information and contact technical support engineers.

5.End