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


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


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 Busy Record Exists in the UDP Jitter Test Result

A Busy Record Exists in the UDP Jitter Test Result

Common Causes

If the UDP jitter test result has busy records, the value of the "System busy operation number" field in the display nqa results command output is not 0.

This fault is commonly caused by one of the following:
  • The VPN route instance that is configured in the UDP Jitter test instance is unreachable.

Troubleshooting Flowchart

Figure 14-10 Troubleshooting flowchart used when a busy record exists in the UDP jitter test

Troubleshooting Procedure



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


  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 VPN instance is configured.

    • If the VPN instance is configured, go to Step 2.
    • If the VPN instance is not configured, go to Step 3.

  2. Run the ping -vpn-instance vpn-instance-name command on the NQA client to check whether the destination address is reachable.

    • If the destination address is reachable, go to Step 3.
    • If the destination address is unreachable, see the section The Ping Operation Fails.

  3. 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

Updated: 2019-08-09

Document ID: EDOC1000079719

Views: 490243

Downloads: 4514

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