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).
A UDP Jitter Test Instance Fails to Be Started

A UDP Jitter Test Instance Fails to Be Started

Common Causes

This fault is commonly caused by one of the following:

  • The mandatory parameter of the test instance is incorrect.

Troubleshooting Flowchart

Figure 14-8  Troubleshooting flowchart used when a UDP Jitter test instance fails to be started

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 test type is Jitter.

    • If the test type is Jitter, go to Step 2.
    • If the test type is not Jitter, run the test-type jitter command to configure the test type to UDP Jitter.
      • If the fault is rectified, the operation ends.
      • If the fault persists, go to Step 2.

  2. 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 destination IP address is configured.

    • If the destination IP address is configured, go to Step 3.
    • If the destination IP address is not configured, run the destination-address ipv4 ip-address command in the NQA test instance view to configure the destination IP address.
      • If the fault is rectified, the operation ends.
      • If the fault persists, go to Step 3.

  3. 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 destination port is configured.

    • If the destination port is configured, go to Step 4.
    • If the destination port is configured, run the destination-port port-number command in the NQA test instance view to configure the destination port.
      • If the fault is rectified, the operation ends.
      • If the fault persists, 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: 444489

Downloads: 4295

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