NQA_1.3.6.1.2.1.81.0.2 traceRouteTestFailed

Trap Buffer Description

TraceRoute entry test failed. (OwnerIndex=[OwnerIndex], TestName=[TestName], TargetAddressType=[TargetAddressType], TargetAddress=[TargetAddress], AddressType=[AddressType], Address=[Address])

The number of consecutive probe failures reached the configured upper threshold.

Trap Attributes

Trap Attribute Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

DISMANTRACE_TESTFAIL

Trap OID

1.3.6.1.2.1.81.0.2

MIB

DISMAN-TRACEROUTE-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 an NQA test instance.

TestName

Name of an NQA test instance.

TargetAddressType

Destination address type of an NQA test instance.

TargetAddress

Destination address of an NQA test instance.

AddressType

Address type of an NQA test instance.

Address

Address of an NQA test instance.

VB Parameters

VB OID VB Name VB Index

1.3.6.1.2.1.81.1.2.1.3

traceRouteCtlTargetAddressType

traceRouteCtlOwnerIndex

traceRouteCtlTestName

1.3.6.1.2.1.81.1.2.1.4

traceRouteCtlTargetAddress

traceRouteCtlOwnerIndex

traceRouteCtlTestName

1.3.6.1.2.1.81.1.3.1.4

traceRouteResultsIpTgtAddrType

traceRouteCtlOwnerIndex

traceRouteCtlTestName

1.3.6.1.2.1.81.1.3.1.5

traceRouteResultsIpTgtAddr

traceRouteCtlOwnerIndex

traceRouteCtlTestName

Impact on the System

The system will not be affected.

Possible Causes

Cause 1: The destination address does not exist and the route is unreachable.

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

Cause 3: The destination address existed and the route was reachable, but the actual number of hops to the destination exceeded the preset maximum hops.

Cause 4: The network delay is great, causing the RTT of the packet to be 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 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 6.
  • If no, 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 and 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 5.
  • If the route is reachable, go to Step 3.

3. Run the tracert livetime command in the NQA test view to change the maximum number of hops based on the actual packet forwarding. (Run the display this command in the NQA test view to view the current maximum number of hops.) The value ranges from 1 to 255. You are advised to change the value to 255.Restart the test instance and check whether the alarm is cleared.

  • If yes, go to Step 6.
  • If no, go to Step 4.

4.Run the timeout command in the NQA test view to change the timeout interval 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 interval.Restart the test instance and check whether the alarm is cleared.

  • If yes, go to Step 6.
  • If no, go to Step 5.

5.In this case, contact Huawei technical support.

6. End

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >