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

A Timeout Record Exists in the UDP Jitter Test Result

Common Causes

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

This fault is commonly caused by one of the following:
  • The destination address does not exist, but the route to the network segment of the destination address exists in the routing table.
  • The value of the parameter "nqa-jitter tag-version" is 2, and the receiver is not configured with a UDP server.

Troubleshooting Flowchart

Figure 14-11 Troubleshooting flowchart used when a timeout 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.

Unless otherwise stated, all the following commands, except display commands that can be run in all views, need to be run in the NQA test instance view.

Procedure

  1. Run the ping command on the NQA client to check whether the route to the destination address is reachable.

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

  2. Run the display this command in the system view on the NQA client to check whether the value of the parameter "nqa-jitter tag-version" is 2. When the value of this parameter is set to 1 (the default value), this parameter is not displayed in the configuration file. This parameter is displayed in the configuration file when its value is set to 2.

    • If the value of the parameter "nqa-jitter tag-version" is 2, go to Step 3.
    • If the value of the parameter "nqa-jitter tag-version" is not 2, go to Step 4.

  3. Run the display nqa-server command on the NQA server to check whether the nqa-server udpecho ip-address port-number command has been configured on the NQA server.

    • If the nqa-server udpecho ip-address port-number command has been configured on the NQA server and is in the Active state, go to Step 4.
    • If the nqa-server udpecho ip-address port-number command is not configured on the NQA server, run the command to configure the NQA server. Note that the IP address of the NQA server must be identical with the destination IP address configured through the destination-address ipv4 ip-address command on the NQA client.

      If the local IPv4 address cannot be predicted because of dynamic address allocation by DHCP, specify the auto-address keyword to configure the UDP service on the NQA server to automatically monitor all IPv4 addresses.

      Also, the port number configured on the NQA server must be identical with that configured through the destination-port port-number command on the NQA client.
      • 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-08-09

Document ID: EDOC1000079719

Views: 497568

Downloads: 4543

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