No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document provides the explanations, causes, and recommended actions of alarms on the product.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
NQA_1.3.6.1.2.1.81.0.2 traceRouteTestFailed

NQA_1.3.6.1.2.1.81.0.2 traceRouteTestFailed

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.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

traceRouteTestFailed

Trap OID

1.3.6.1.2.1.81.0.2

Alarm ID

This is an event trap and does not involve alarm ID.

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

This is an event trap and does not involve the matching trap.

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

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

None

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 so, go to Step 2.
    • If not, run the destination-address command in the NQA test view to modify the destination address. Then, perform the test instance again to check whether the test is successful.

      • If so, go to Step 6.
      • 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 route is reachable, go to Step 3.
    • If the destination address is correctly configured, but the route is not reachable, run the display ip routing-table command to check and routing table and rectify the routing fault. Then, perform the test instance again to check whether the test is successful.
      • If so, go to Step 6.
      • If not, go to Step 3.

  3. Run the tracert livetime command in the NQA test instance view to modify the number of the maximum hops based on the packet forwarding status. The value ranges form 1 to 255. It is recommended to be set as 255. Restart the test instance to check whether the test succeeds.

    • If so, go to Step 6.
    • If not, go to Step 4.

  4. 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 see the current timeout period.

    Then, perform the test instance again to check whether the test is successful.

    • If so, go to Step 6.
    • If not, go to Step 5.

  5. Contact technical support personnel.
  6. End.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 22924

Downloads: 30

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next