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
Context
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.
Generally, the following commands are used in the NQA test instance view. Only the display commands can be used in any view.
Procedure
- Run the ping command on the NQA client to check whether the route to the destination address is reachable.
- 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. When the value is 2, this parameter is displayed in the configuration file.
- 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 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 the same as the destination IP address set using the destination-address ipv4 ip-address command on the NQA client. The port-number configured on the NQA server must be the same as that set using the destination-port port-number command on the NQA client.