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

A Drop Record Exists in the UDP Jitter Test Result

Common Causes

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

This fault is commonly caused by one of the following:
  • The destination IP address does not exist or the route to the network segment to which the destination IP address belongs does not exist in the routing table.
  • The source IP address is incorrect.

Troubleshooting Flowchart

Figure 14-9  Troubleshooting flowchart used when a drop record exists in the UDP jitter test

Troubleshooting Procedure

Context

NOTE:

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

Procedure

  1. Run the display ip routing-table command on the NQA client to check whether the route along the test path exists.

    • If the route exists, run the ping command to check whether devices can successfully ping each other.
      • If devices can successfully ping each other, go to Step 2.
      • If devices cannot successfully ping each other, see The Ping Operation Fails.
    • If the route does not exist, run the corresponding command to reconfigure the route.

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

    • If the source IP address is configured, run the display ip interface brief on the NQA client to check whether the interface configured with the source IP address exists.
      • If the interface exists, run the display ip routing-table command on the NQA server to check whether the route to the source IP address exists.
        • If the route exists, run the ping command to check whether the source IP address is reachable.
          • If the source IP address is reachable, go to Step 3.
          • If the source IP address is unreachable, see The Ping Operation Fails.
        • If the route does not exist, run the corresponding command to reconfigure the route.
      • If the interface configured with the source IP address does not exist, run the corresponding command to reconfigure IP addresses and recheck the configuration about NQA.
    • If the source IP address is not configured, go to Step 3.

  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

Translation
Download
Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 451780

Downloads: 4311

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