ALM-1098063877 NQA ICMP Test Failed

Description

NQA/4/PINGFAIL:OID [OID] Ping entry test failed. (Admin=[OCTET], Tag=[OCTET])

The trap was generated when the number of continuous test failures reached the threshold. The default threshold was 1. You can run the test-failtimes command to modify the threshold.

Attribute

Alarm ID	OID	Alarm Severity	Alarm Type
1098063877	1.3.6.1.2.1.80.0.2	Warning	Communication alarm

Parameters

Name	Meaning
OID	Indicates the MIB object ID of the alarm.
Admin	Indicates the index of the test administrator.
Tag	Indicates the index of the test name.

Impact on the System

None

Possible Causes

This trap occurred in the NQA test.

1. The destination address was inexistent and the route was unreachable.

2. The destination address existed, but the route was unreachable.

3. Because of the network delay, the RTT of the packet was longer than the set timeout period.

Procedure

Run the display this command in the NQA test view to check whether the destination address is correctly configured. If not, run the destination-address command in the NQA test view to modify the destination address.
Perform the test again to check whether the alarm is cleared.
- If so, go to Step 5.
- If not, go to Step 2.
Run the ping command in the NQA test view to check whether the route is reachable.
- If the destination address is correctly configured, but the route is not reachable, run the display ip routing-table command to check the routing table and rectify the routing fault. If the test fails again, go to Step 4.
- If the route is reachable, go to Step 3.
Run the timeout command in the NQA test view to modify the timeout period according to the status of the current network. It is recommended that you modify the timeout period to the default value, that is, three seconds. The value of the timeout period ranges from 1 second to 60 seconds. You can run the display this command in the NQA test view to view the current timeout period.
Perform the test again to check whether the alarm is cleared.
- If so, go to Step 5.
- If not, go to Step 4.
Run the display ospf interface interface-type interface-number command and view the State field to check whether the interface where the OSPF neighbor is configured is in the Down state.
- If the interface is in the Down state, go to to Step 6.
- If the interface is in another state, go to step 5.
Collect alarm information and configuration information, and then contact technical support personnel.
End.