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

ME60 Troubleshooting Guide V1.0 (VRPv8)

This document provides the maintenance guide of the device, including daily maintenance, emergence maintenance, and typical 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).
NQA Troubleshooting

NQA Troubleshooting

This chapter describes common causes of NQA faults, and provides the corresponding troubleshooting flowcharts, troubleshooting procedures, alarms, and logs.

A UDP Jitter Test Instance Fails to Be Started

This chapter describes common causes of the fault that a UDP jitter test instance fails to be started, and provides the corresponding troubleshooting flowcharts and examples.

Common Causes

The common cause is that the mandatory parameter of the test instance is incorrect.

Troubleshooting Flowchart
Figure 4-14 Troubleshooting flowchart for the fault that a UDP Jitter test instance fails to be started

Troubleshooting Procedure

Context

NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

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 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, go to Step 5.
      • If the fault persists, go to Step 2.

  2. Run 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, go to Step 5.
      • If the fault persists, go to Step 3.

  3. Run 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, go to Step 5.
      • If the fault persists, go to Step 4.

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

    • Results of this troubleshooting procedure
    • Configuration files, log files, and alarm files of the devices

  5. End.
Relevant Alarms and Logs
Relevant Alarms
None
Relevant Logs
None

A Timeout Record Exists in the UDP Jitter Test Result

This chapter describes common causes of the fault that a timeout record exists in the UDP jitter test result, and provides the corresponding troubleshooting flowcharts and examples.

Common Causes

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

This fault commonly results from one of the following causes:
  • The destination address does not exist, but the route to the network segment of the destination address exists in the routing table.
  • The receiver is not configured with a UDP server.
Troubleshooting Flowchart
Figure 4-15 Troubleshooting flowchart for the fault that a timeout record exists in the UDP jitter test

Troubleshooting Procedure

Context

NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

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, 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; 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, go to Step 5.
      • If the fault persists, go to Step 4.

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

    • Results of this troubleshooting procedure
    • Configuration files, log files, and alarm files of the devices

  5. End.
Relevant Alarms and Logs
Relevant Alarms
None
Relevant Logs
None

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

This chapter describes common causes of the fault that the UDP jitter test result is "Failed", "No Result" or "Packet Loss", and provides the corresponding troubleshooting flowcharts and examples.

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", it indicates that the test fails.
  • If the "Completion" field is displayed as "no result", it indicates that the test has no result.
  • If the "lost packet ratio" field is not 0%, it indicates that packet loss occurs.
This fault commonly results from one of the following causes:
  • 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 4-16 Troubleshooting flowchart for the fault that the UDP Jitter test result is "failed", "no result", or "packet loss"

Troubleshooting Procedure

Context

NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

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 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 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*probe-count*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*probe-count*jitter-packetnum). If the value of the frequency is smaller than that of the (interval*probe-count*jitter-packetnum), you 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 the frequency is set to proper value, go to Step 3.

  3. Run 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 this troubleshooting procedure
    • Configuration files, log files, and alarm files of the devices

  5. End.
Relevant Alarms and Logs
Relevant Alarms
None
Relevant Logs
None
Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 4623

Downloads: 209

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