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.


NE20E-S2 V800R010C10SPC500 Feature Description - System Monitor 01

This is NE20E-S2 V800R010C10SPC500 Feature Description - System Monitor
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 Introduction

NQA Introduction


Network quality analysis (NQA) is a feature provided by the NE20E. Operating independently of hardware, NQA functions on the data link layer and assesses the performance of protocols running on network, transport, and application layers.


The NE20E provides NQA to help carriers monitor network quality of service (QoS) in real time and locate any faults occurring on a network.

Without NQA features on the NE20E, carriers provide the following services to help users evaluate network service quality:

  • Enable NE20Es to provide network service quality information.

    Carriers have to set parameters, such as the delay, jitter, and packet loss ratio on NE20Es to assess network performance, which allows different devices to collect index-specific statistics and analyze service changes.

  • Deploy probe devices to monitor network service quality.

    Deploying dedicated probe devices, such as the third-party probe device Brix, increases carriers' costs because the demand for probe devices grows with the increasing network scale.

The NE20E provides NQA tools that are integrated with network quality test functions. There is no need to set additional parameter on devices or deploy probe devices, which reduces carrier network costs. NQA accurately monitors the network operating status and collects statistics.

NQA measures the performance of each protocol running on a network and helps carriers collect network operation indicators, such as the delay time of a TCP connection, packet loss ratio, and path maximum transmission unit (MTU). Carriers provide users with differentiated services and charge users differently based on these indicators. NQA is also an effective tool to diagnose and locate faults in a network.

Although the ping operation can be used as a traditional method to monitor network quality, the ping operation provides less information than NQA. Table 4-1 describes the differences between NQA and the ping.

Table 4-1 Comparison between NQA and Ping





NQA initiates Internet Control Message Protocol (ICMP) tests to check if services, such as TCP and UDP, are enabled and calculate the response time of each service type. NQA conducts jitter tests to measure the jitter time.

The pings are performed using ICMP, only measure the round-trip time (RTT) of packets between the source and destination, and check the reachability of a specific destination.

A user can initiate only one ping at a time.


You can view NQA test results on an NQA client. Note the following:
  • NQA allows you to set parameters on a network management system (NMS). Statistics are displayed as test results and listed in history tables.
  • In most test instances, only an NQA client must be configured. In TCP, UDP, and jitter test instances, the NQA server must also be configured.
  • The NQA server uses the monitoring function to respond to a test request from an NQA client. The NQA server can respond to a test request only if it is assigned a destination IP address and port number. The IP address and port number specified in the monitoring service on the NQA server must be the same as those configured on the NQA client.

The ping command must be run on the console port to check the reachability of a specified IP address. The RTT or timeout period of every packet is displayed in real time.


NQA schedules test instances to prevent concurrent tests and therefore reduces the burden on the NE20E.

A single NQA test instance can be started or stopped in a specific mode:
  • Start modes: immediate start, delayed start, and timing start
  • End modes: auto-end, immediate end, delayed end, timing end, and end when the lifetime expires

If several tasks are performed simultaneously, the NE20E arranges the start time and test intervals for each task.

The ping operation can only be triggered manually.

Updated: 2019-01-02

Document ID: EDOC1100055478

Views: 5276

Downloads: 2

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