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

AR Router Troubleshooting Guide

This Product Documentation provides guidance for maintaining AR Enterprise Router, covering common information collection and fault diagnostic commands, typical fault troubleshooting guide, and troubleshooting.
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).
The UDP Jitter Test Result Is "Failed", "No Result" or "Packet Loss"

The UDP Jitter Test Result Is "Failed", "No Result" or "Packet Loss"

Common Causes

The UDP jitter test result displayed in the display nqa results command output can be "failed", "no result", or "packet loss". In the command output,
  • If the "Completion" field is displayed as "failed", the test fails.
  • If the "Completion" field is displayed as "no result", the test has no result.
  • If the "lost packet ratio" field is not 0%, packet loss occurs.
This fault is commonly caused by one of the following:
  • A drop record exists in the UDP jitter test result.
  • A busy record exists in the UDP jitter test result.
  • A timeout record exists in the UDP jitter test result.
  • The TTL expires.
  • The parameter frequency is incorrect.
  • The parameter fail-percent is incorrect.

Troubleshooting Flowchart

Figure 14-12  Troubleshooting flowchart used when the UDP Jitter test result is "failed", "no result", or "packet loss"

Troubleshooting Procedure

Context

NOTE:

Save the operation results of follow-up steps so that you can refer to them during troubleshooting.

All the following commands, except the display commands, are used in the NQA test instance view. The display commands can be used in any views.

Procedure

  1. Run the display nqa-agent admin-name test-name [ verbose ] command on the NQA client or the display this command in the NQA test instance view to check whether the TTL is configured.

    • If the TTL is configured, you can run the ttl number command in the NQA test instance view to set the value of the TTL to 255. If the fault persists after the TTL is set to 255, go to Step 2.
    • If the TTL is not configured, you can run the ttl number command in the NQA test instance view to set the value of the TTL to 255. If the fault persists after the TTL is set to 255, go to Step 2.

  2. Run the display nqa-agent admin-name test-name [ verbose ] command on the NQA agent or the display this command in the NQA test instance view to check whether the parameter frequency is configured.

    • If the parameter frequency is configured, compare the value of the frequency and that of the (interval x probe-count x jitter-packetnum). To ensure that the UDP Jitter test instance can be complete normally, the value of the frequency must be greater than that of the (interval x probe-count x jitter-packetnum). If the value of the frequency is less than that of the (interval x probe-count x jitter-packetnum), run the frequency interval command in the NQA test instance view to increase the value of the frequency.
    • If the frequency is not configured or the fault persists after a proper frequency value is set, go to Step 3.

  3. Run the display nqa-agent admin-name test-name [ verbose ] command on the NQA agent or the display this command in the NQA test instance view to check whether the parameter fail-percent is configured.

    • If the fail-percent is configured, run the undo fail-percent command in the NQA test instance view to delete the fail-percent. If the fault persists after the fail-percent is deleted, go to Step 4.
    • If the fail-percent is not configured, go to Step 4.

  4. If the fault persists, collect the following information and contact technical support personnel:

    • Results of the preceding troubleshooting procedures
    • Configuration files, log files, and alarm files of the devices

Translation
Download
Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 455503

Downloads: 4320

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