05-System Volume

03-NQA Configuration

Chapters Download  (425.37 KB)

03-NQA Configuration


NQA Configuration

This chapter includes these sections:

·           NQA Overview

·           NQA Configuration Task List

·           Configuring the NQA Server

·           Enabling the NQA Client

·           Creating an NQA Test Group

·           Configuring an NQA Test Group

·           Configuring the Collaboration Function

·           Configuring Threshold Monitoring

·           Configuring the NQA Statistics Function

·           Configuring the History Records Saving Function

·           Configuring Optional Parameters Common to an NQA Test Group

·           Scheduling an NQA Test Group

·           Displaying and Maintaining NQA

·           NQA Configuration Examples

NQA Overview

Introduction to NQA

Network Quality Analyzer (NQA) analyzes network performance, services and service quality through sending test packets, and provides you with network performance and service quality parameters such as delay jitter, TCP connection delay, FTP connection delay and file transfer rate.

With the NQA test results, you can:

1.          Know network performance in time and then take corresponding measures.

2.          Diagnose and locate network faults.

Features of NQA

Supporting multiple test types

Ping can use only the Internet Control Message Protocol (ICMP) to test the reachability of the destination host and the round-trip time of a packet to the destination. As an enhancement to the Ping tool, NQA provides multiple test types and more functions.

At present, NQA supports 11 test types: ICMP echo, DHCP, DNS, FTP, HTTP, UDP jitter, SNMP, TCP, UDP echo, voice and DLSw.

In an NQA test, the client sends different types of test packets to the peer to detect the availability and the response time of the peer, helping you know protocol availability and network performance based on the test results.

Supporting the collaboration function

Collaboration is implemented by establishing reaction entries to monitor the detection results of the current test group. If the number of consecutive probe failures reaches a certain limit, NQA’s collaboration with other modules is triggered. The implementation of collaboration is shown in Figure 1.

Figure 1 Implementation of collaboration

 

The collaboration involves three parts: the application modules, the track module, and the detection modules.

·           The detection modules monitor the link status, network performance and so on, and inform the track module of the detection result.

·           Upon receiving the detection result, the track module changes the status of the track entry accordingly and informs the application modules. The track module works between the application modules and the detection modules and is mainly used to obscure the difference of various detection modules to provide a unified interface for application modules.

·           The application modules then deal with the changes accordingly based on the status of the track entry, and thus collaboration is implemented.

Take static routing as an example. You have configured a static route with the next hop 192.168.0.88. If 192.168.0.88 is reachable, the static route is valid; if 192.168.0.88 is unreachable, the static route is invalid. With the collaboration between NQA, track module and application modules, real time monitoring of reachability of the static route can be implemented:

1.          Monitor reachability of the destination 192.168.0.88 through NQA.

2.          If 192.168.0.88 is detected to be unreachable, NQA will inform the static routing module through track module.

3.          The static routing module then can know that the static route is invalid.

 

 

NOTE:

For more information about the track module, see Track Configuration in the System Volume.

 

Supporting threshold monitoring

NQA supports threshold monitoring for performance parameters such as average delay jitter and packet round-trip time. The performance parameters to be monitored are called monitored elements. NQA monitors threshold violations for a monitored element, and reacts to certain measurement conditions, for example, sending trap messages to the network management server. This helps network administrators understand the network service quality and network performance.

1.          Monitored elements

Table 1 describes the monitored elements and the NQA test types in which the elements can be monitored.

Table 1 Monitored elements and NQA test types

Monitored elements

Test type supported

Probe duration

Tests excluding UDP jitter test and voice test

Count of probe failures

Tests excluding UDP jitter test and voice test

Packet round-trip time

UDP jitter test and voice test

Count of discarded packets

UDP jitter test and voice test

One-way delay jitter (source-to-destination and destination-to-source)

UDP jitter test and voice test

One-way delay (source-to-destination and destination-to-source)

UDP jitter test and voice test

Calculated Planning Impairment Factor (ICPIF)

For description about ICPIF, see Configuring a Voice Test.

Voice test

Mean Opinion Scores (MOS)

For description about MOS, see Configuring a Voice Test.

Voice test

 

2.          Threshold types

The following threshold types are supported:

·           average: Monitors the average value of monitored data in a test. If the average value in a test exceeds the upper threshold or goes below the lower threshold, a threshold violation occurs. For example, you can monitor the average probe duration in a test.

·           accumulate: Monitors total number of times the monitored data violates the threshold in a test. If the total number of times reaches or exceeds a specified value, a threshold violation occurs.

·           consecutive: Monitors the number of consecutive times the monitored data violates the threshold since the test group starts. If the monitored data violates the threshold consecutively for a specified number of times, a threshold violation occurs.

 

TIP:

The accounting for the average or accumulate threshold type is performed per test, but that for the consecutive type is performed since the test group is started.

 

3.          Triggered actions

The following actions may be triggered:

·           none: NQA only records such events for terminal display; it does not send trap information to the network management server.

·           trap-only: NQA records such events and sends trap messages to the network management server.

 

 

NOTE:

NQA DNS tests do not support the action of sending trap messages. In other words, the action to be triggered in DNS tests can only be the default one, none.

 

4.          Reaction entry

In a reaction entry, a monitored element, a threshold type, and the action to be triggered are configured to implement threshold monitoring.

The state of a reaction entry can be invalid, over-threshold, or below-threshold.

·           Before an NQA test group starts, the reaction entry is in the state of invalid.

·           After each test or probe, threshold violations are counted according to the threshold type and range configured in the entry. If the threshold is violated consecutively or accumulatively for a specified number of times, the state of the entry is set to over-threshold; otherwise, the state of the entry is set to below-threshold.

If the action to be triggered is configured as trap-only for a reaction entry, when the state of the entry changes, a trap message is generated and sent to the network management server.

Basic Concepts of NQA

Test group

Before performing an NQA test, create an NQA test group, and configure NQA test parameters such as test type, destination address and destination port.

Each test group has an administrator name and operation tag, which can uniquely define a test group.

Test and probe

After an NQA test is started, one test is performed at a regular interval and you can set the interval as needed.

One NQA test involves multiple consecutive probes and you can set the number of the probes.

 

 

NOTE:

Only one probe can be made in one voice test.

 

In different test types, probe has different meanings:

·           For a TCP or DLSw test, one probe means one connection;

·           For a UDP jitter or a voice test, multiple packets are sent successively in one probe, and the number of packets sent in one probe depends on the configuration of the probe packet-number command;

·           For an FTP, HTTP, DHCP or DNS test, one probe means to carry out a corresponding function;

·           For an ICMP echo or UDP echo test, one packet is sent in one probe;

·           For an SNMP test, three packets are sent in one probe.

NQA client and server

NQA client is the device that initiates an NQA test and the NQA test group is created on the NQA client.

NQA server processes the test packets sent from the NQA client, as shown in Figure 2. The NQA server makes a response to the request sent by the NQA client by listening to the specified destination address and port number.

Figure 2 Relationship between the NQA client and NQA server

 

In most NQA tests, you only need to configure the NQA client; while in TCP, UDP echo, UDP jitter, and voice tests, you must configure the NQA server.

You can create multiple TCP or UDP listening services on the NQA server, each of which corresponds to a specified destination address and port number. The IP address and port number specified for a listening service on the server must be consistent with those on the client and must be different from those of an existing listening service.

NQA Test Operation

An NQA test operation involves the following steps:

1.          The NQA client constructs packets with the specified type, and sends them to the peer device.

2.          Upon receiving the packet, the peer device replies with a response with a timestamp.

3.          The NQA client computes the packet loss rate and RTT based on whether it has received the response and the timestamp in the response.

NQA Configuration Task List

To perform TCP, UDP jitter, UDP echo or voice tests, configure the NQA server on the peer device.

Complete the following task to enable the NQA server:

Task

Remarks

Configuring the NQA Server

Required for TCP, UDP echo, UDP jitter and voice tests

 

To perform an NQA test successfully, make the following configurations on the NQA client:

1.          Enable the NQA client;

2.          Create a test group and configure test parameters according to the test type. The test parameters may vary with test types;

3.          Start the NQA test.

To view test results about the test, use the display or debug commands.

Complete these tasks to configure NQA client:

Task

Remarks

Enabling the NQA Client

Required

Creating an NQA Test Group

Required

Configuring an NQA Test Group

Configuring an ICMP Echo Test

Required

Use any of the approaches

Configuring a DHCP Test

Configuring an FTP Test

Configuring a DNS Test

Configuring an HTTP Test

Configuring a UDP Jitter Test

Configuring an SNMP Test

Configuring a TCP Test

Configuring a UDP Echo Test

Configuring a Voice Test

Configuring a DLSw Test

Configuring the Collaboration Function

Optional

Configuring Threshold Monitoring

Optional

Configuring the NQA Statistics Function

Optional

Configuring the History Records Saving Function

Optional

Configuring Optional Parameters Common to an NQA Test Group

Optional

Scheduling an NQA Test Group

Required

 

Configuring the NQA Server

Before performing TCP, UDP echo, UDP jitter, or voice tests, configure the NQA server on the peer device. The NQA server makes a response to the request sent by the NQA client by listening to the specified destination address and port number.

Follow these steps to configure the NQA server:

To do…

Use the command…

Remarks

Enter system view

system-view

Enable the NQA server

nqa server enable

Required

Disabled by default.

Configure the listening service on the NQA server

nqa server { tcp-connect | udp-echo } ip-address port-number

Required

The IP address and port number must be consistent with those configured on the NQA client and must be different from those of an existing listening service.

 

Enabling the NQA Client

Configurations on the NQA client take effect only when the NQA client is enabled.

Follow these steps to enable the NQA client:

To do…

Use the command…

Remarks

Enter system view

system-view

Enable the NQA client

nqa agent enable

Optional

Enabled by default.

 

Creating an NQA Test Group

One test corresponds to one test group. You can configure test types after you create a test group and enter the test group view.

Follow theses steps to create an NQA test group:

To do…

Use the command…

Remarks

Enter system view

system-view

Create an NQA test group and enter the NQA test group view

nqa entry admin-name operation-tag

Required

 

 

NOTE:

If you execute the nqa entry command to enter the test group view with test type configured, you directly enter the test type view of the test group.

 

Configuring an NQA Test Group

Configuring an ICMP Echo Test

An ICMP echo test is used to test reachability of the destination host according to the ICMP echo reply or timeout information. An ICMP echo test has the same function as the ping command but provides more output information. It enables you to locate connectivity problems in a network.

Follow these steps to configure an ICMP echo test:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Configure the test type as ICMP echo and enter test type view

type icmp-echo

Required

Configure the destination address for a test operation

destination ip ip-address

Required

By default, no destination IP address is configured for a test operation.

Configure the size of probe packets sent

data-size size

Optional

100 bytes by default.

Configure the filler string of a probe packet sent

data-fill string

Optional

By default, the filler string of a probe packet is the hexadecimal number 00010203040506070809.

Specify a VPN instance

vpn-instance instance

Optional

Not specified by default.

Specify the IP address of an interface as the source IP address of an ICMP echo request

source interface interface-type interface-number

Optional

By default, no interface address is specified as the source IP address of ICMP probe requests.

If you use the source ip command to configure the source IP address of ICMP echo probe requests, the source interface command is invalid.

The interface specified by this command must be up. Otherwise, the probe will fail.

Configure the source IP address of a probe request

source ip ip-address

Optional

By default, no source IP address is specified.

If no source IP address is specified, but the source interface is specified, the IP address of the source interface is taken as the source IP address of ICMP probe requests.

The source IP address must be that of an interface on the device and the interface must be up. Otherwise, the probe will fail.

Configure the next hop IP address for an ICMP echo request

next-hop ip-address

Optional

By default, no next hop IP address is configured.

Configure common optional parameters

See Configuring Optional Parameters Common to an NQA Test Group

Optional

 

Configuring a DHCP Test

A DHCP test is mainly used to test the existence of a DHCP server on the network as well as the time necessary for the DHCP server to respond to a client request and assign an IP address to the client.

Configuration prerequisites

Before performing a DHCP test, configure the DHCP server. If the NQA (DHCP client) and the DHCP server are not in the same network segment, configure a DHCP relay agent. For more information about DHCP server and DHCP relay, see DHCP Configuration in the Firewall Web Configuration Manual.

Configuring a DHCP test

Follow these steps to configure a DHCP test:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Configure the test type as DHCP and enter test type view

type dhcp

Required

Specify an interface for a DHCP test

operation interface interface-type interface-number

Required

By default, no interface is specified to perform a DHCP test.

The interface specified by the source interface command must be up; otherwise, the test fails.

Configure common optional parameters

See Configuring Optional Parameters Common to an NQA Test Group

Optional

 

 

NOTE:

·       Because a DHCP test is a process to simulate address allocation in DHCP, the IP address of the interface that performs the DHCP test does not change.

·       When the DHCP test is completed, the NQA client sends a DHCP-RELEASE packet to release the obtained IP address.

 

Configuring a DNS Test

A DNS test is mainly used to test whether the NQA client can resolve a domain name into an IP address through a DNS server and the time required for resolution.

Configuration prerequisites

Before performing a DNS test, configure the mapping between a domain name and an IP address on a DNS server.

Configuring a DNS test

Follow these steps to configure a DNS test:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Configure the test type as DNS and enter test type view

type dns

Required

Specify a destination address for a DNS test

destination ip ip-address

Required

By default, no destination IP address is configured for a test operation.

The destination IP address must be the IP address of the DNS server.

Configure the domain name

resolve-target domain-name

Required

By default, no domain name is configured for a DNS test.

Configure optional parameters common to an NQA test group

See Configuring Optional Parameters Common to an NQA Test Group

Optional

 

 

 

NOTE:

Because a DNS test is a process to simulate the domain name resolution, the mapping between the domain name and the IP address is not saved.

 

Configuring an FTP Test

An FTP test is mainly used to test the connection between the NQA client and a specified FTP server and the time necessary for the FTP client to transfer a file to or download a file from the FTP server.

Configuration prerequisites

Before an FTP test, perform some configurations on the FTP server. For example, configure the username and password that are used to log in to the FTP server. For more information about FTP server configuration, see FTP and TFTP Configuration in the IP Services Volume.

Configuring an FTP test

Follow these steps to configure an FTP test:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Configure the test type as FTP and enter test type view

type ftp

Required

Configure the destination address for a test operation

destination ip ip-address

Required

By default, no destination IP address is configured for a test operation.

The destination IP address for a test operation is the IP address of the FTP server.

Configure the source IP address of a probe request

source ip ip-address

Required

By default, no source IP address is specified.

The source IP address must be that of an interface on the device and the interface must be up. Otherwise, the test will fail.

Configure the operation type

operation { get | put }

Optional

By default, the operation type for the FTP is get, which means obtaining files from the FTP server.

Configure a login username

username name

Required

By default, no login username is configured.

Configure a login password

password password

Required

By default, no login password is configured.

Specify a file to be transferred between the FTP server and the FTP client

filename file-name

Required

By default, no file is specified.

Set the data transmission mode for FTP tests

mode { active | passive }

Optional

active by default.

Configure common optional parameters

See Configuring Optional Parameters Common to an NQA Test Group

Optional

 

 

NOTE:

·       When you execute the put command, a file file-name with fixed size and content is created on the FTP server. When you execute the get command, the device does not save the files obtained from the FTP server.

·       When you execute the get command, the FTP test cannot succeed if a file named file-name does not exist on the FTP server.

·       When you execute the get command, use a file with a smaller size because a big file may result in test failure due to timeout, or may affect other services because of occupying too much network bandwidth.

 

Configuring an HTTP Test

An HTTP test is used to test the connection between the NQA client and a specified HTTP server and the time required to obtain data from the HTTP server, thus detecting the connectivity and performance of the HTTP server.

Configuration prerequisites

Before performing an HTTP test, configure the HTTP server.

Configuring an HTTP test

Follow these steps to configure an HTTP test:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Configure the test type as HTTP and enter test type view

type http

Required

Configure the destination address for a test operation

destination ip ip-address

Required

By default, no destination IP address is configured for a test operation.

The destination IP address for a test operation is the IP address of the HTTP server.

Configure the source IP address of a probe request

source ip ip-address

Optional

By default, no source IP address is specified.

The source IP address must be that of an interface on the device and the interface must be up. Otherwise, the test will fail.

Configure the operation type

operation { get | post }

Optional

By default, the operation type for the HTTP is get, which means obtaining data from the HTTP server.

Configure the website that an HTTP test visits

url url

Required

Configure the HTTP version used in the HTTP test

http-version v1.0

Optional

By default, HTTP 1.0 is used in an HTTP test.

Configure common optional parameters

See Configuring Optional Parameters Common to an NQA Test Group

Optional

 

 

NOTE:

The TCP port number for the HTTP server must be 80 in an HTTP test. Otherwise, the test will fail.

 

Configuring a UDP Jitter Test

 

 

NOTE:

It is recommended not to perform an NQA UDP jitter test on known ports, namely, ports from 1 to 1023. Otherwise, the NQA test will fail or the corresponding services of this port will be unavailable.

 

Real-time services such as voice and video have high requirements on delay jitters. With the UDP jitter test, uni/bi-directional delay jitters can be obtained to judge whether a network can carry real-time services.

Delay jitter refers to the difference between the interval of receiving two packets consecutively and the interval of sending these two packets. The procedure of a UDP jitter test is as follows:

·           The source sends packets at regular intervals to the destination port.

·           The destination affixes a time stamp to each packet that it receives and then sends it back to the source.

·           Upon receiving the packet, the source calculates the delay jitter, and the network status can be analyzed.

Configuration prerequisites

A UDP jitter test requires cooperation between the NQA server and the NQA client. Before the UDP jitter test, make sure that the UDP listening function is configured on the NQA server. For the configuration of the UDP listening function, see Configuring the NQA Server.

Configuring a UDP jitter test

Follow these steps to configure a UDP jitter test:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Configure the test type as UDP jitter and enter test type view

type udp-jitter

Required

Configure the destination address for a test operation

destination ip ip-address

Required

By default, no destination IP address is configured for a test operation.

The destination IP address must be consistent with that of the existing listening service on the NQA server.

Configure the destination port for a test operation

destination port port-number

Required

By default, no destination port number is configured for a test operation.

The destination port must be consistent with that of the existing listening service on the NQA server.

Specify the source port number for a request

source port port-number

Optional

By default, no source port number is specified.

Configure the size of a probe packet sent

data-size size

Optional

100 bytes by default.

Configure the filler string of a probe packet sent

data-fill string

Optional

By default, the filler string of a probe packet is the hexadecimal number 00010203040506070809.

Configure the number of packets sent in a UDP jitter probe

probe packet-number

packet-number

Optional

10 by default.

Configure the interval for sending packets in a UDP jitter probe

probe packet-interval packet-interval

Optional

20 milliseconds by default.

Configure the time for waiting for a response in a UDP jitter test

probe packet-timeout packet-timeout

Optional

3000 milliseconds by default.

Configure the source IP address of a probe request in a test operation

source ip ip-address

Optional

By default, no source IP address is specified.

The source IP address must be that of an interface on the device and the interface must be up. Otherwise, the test will fail.

Configure common optional parameters

See Configuring Optional Parameters Common to an NQA Test Group

Optional

 

 

NOTE:

The number of probes made in a UDP jitter test depends on the probe count command. The number of probe packets sent in each probe depends on the configuration of the probe packet-number command.

 

Configuring an SNMP Test

An SNMP query test is used to test the time the NQA client takes to send an SNMP query packet to the SNMP agent and then receive a response packet.

Configuration prerequisites

The SNMP agent function must be enabled on the device that serves as an SNMP agent before an SNMP test. For the configuration of SNMP agent, see SNMP Configuration in the System Volume.

Configuring an SNMP test

Follow these steps to configure an SNMP test:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Configure the test type as SNMP and enter test type view

type snmp

Required

Configure the destination address for a test operation

destination ip ip-address

Required

By default, no destination IP address is configured for a test operation.

Specify the source port number for a probe request in a test operation

source port port-number

Optional

By default, no source port number is specified.

Configure the source IP address of a probe request in a test operation

source ip ip-address

Optional

By default, no source IP address is specified.

The source IP address must be that of an interface on the device and the interface must be up. Otherwise, the test will fail.

Configure common optional parameters

See Configuring Optional Parameters Common to an NQA Test Group

Optional

 

Configuring a TCP Test

A TCP test is used to test the TCP connection between the client and the specified port on the NQA server and the setup time for the connection, thus judging the availability and performance of the services provided on the specified port on the server.

Configuration prerequisites

A TCP test requires cooperation between the NQA server and the NQA client. Configure the TCP listening function on the NQA server before the TCP test. For the configuration of the TCP listening function, see Configuring the NQA Server.

Configuring a TCP test

Follow these steps to configure a TCP test:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Configure the test type as TCP and enter test type view

type tcp

Required

Configure the destination address for a test operation

destination ip ip-address

Required

By default, no destination IP address is configured for a test operation.

The destination address must be the IP address of the listening service configured on the NQA server.

Configure the destination port

destination port port-number

Required

By default, no destination port number is configured for a test operation.

The destination port number must be consistent with port number of the listening service configured on the NQA server.

Configure the source IP address of a probe request in a test operation

source ip ip-address

Optional

By default, no source IP address is specified.

The source IP address must be that of an interface on the device and the interface must be up. Otherwise, the test will fail.

Configure common optional parameters

See Configuring Optional Parameters Common to an NQA Test Group

Optional

 

Configuring a UDP Echo Test

A UDP echo test is used to test the connectivity and round-trip time of a UDP echo packet from the client to the specified UDP port on the NQA server.

Configuration prerequisites

A UDP echo test requires cooperation between the NQA server and the NQA client. Configure the UDP listening function on the NQA server before the UDP echo test. For the configuration of the UDP listening function, see Configuring the NQA Server.

Configuring a UDP echo test

Follow these steps to configure a UDP echo test

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Configure the test type as UDP echo and enter test type view

type udp-echo

Required

Configure the destination address for a test operation

destination ip ip-address

Required

By default, no destination IP address is configured for a test operation.

The destination address must be the IP address of the listening service configured on the NQA server.

Configure the destination port

destination port port-number

Required

By default, no destination port number is configured for a test operation.

The destination port number must be the port number of the listening service configured on the NQA server.

Configure the size of probe packets sent

data-size size

Optional

100 bytes by default.

Configure the filler string of a probe packet sent

data-fill string

Optional

By default, the filler string of a probe packet is the hexadecimal number 00010203040506070809.

Specify a source port number for a probe request in a test operation

source port port-number

Optional

By default, no source port number is specified.

Configure the source IP address of a probe request in a test operation

source ip ip-address

Optional

By default, no source IP address is specified.

The source IP address must be that of an interface on the device and the interface must be up. Otherwise, the test will fail.

Configure common optional parameters

See Configuring Optional Parameters Common to an NQA Test Group

Optional

 

Configuring a Voice Test

 

 

NOTE:

It is recommended not to perform an NQA UDP jitter test on known ports, namely, ports from 1 to 1023. Otherwise, the NQA test will fail or the corresponding services of these ports will be unavailable.

 

A voice test is used to test voice over IP (VoIP) network status, and collect VoIP network parameters so that users can adjust the network according the network status. The procedure of a voice test is as follows:

1.          The source (NQA client) sends voice packets of G.711 A-law, G.711 µ-law or G.729 A-law codec type at regular intervals to the destination (NQA server).

2.          The destination affixes a time stamp to each packet that it receives and then sends it back to the source.

3.          Upon receiving the packets, the source calculates the delay jitter and delay by calculating the difference between the interval for the destination to receive two successive packets and the interval for the source to send these two successive packets, and thus the network status can be analyzed.

The voice parameter values that indicate VoIP network status can also be calculated in a voice test, including:

·           Calculated Planning Impairment Factor (ICPIF): Measures attenuation of voice data in a network, depending on packet loss and delay. A higher value represents a lower network quality.

·           Mean Opinion Scores (MOS): Measures quality of a VoIP network. A MOS value can be evaluated by using the ICPIF value, in the range 1 to 5. A higher value represents a higher quality of a VoIP network.

The evaluation of voice quality depends on users’ tolerance to voice quality, which should be taken into consideration. For users with higher tolerance to voice quality, use the advantage-factor command to configure the advantage factor. When the system calculates the ICPIF value, this advantage factor is subtracted to modify ICPIF and MOS values and thus both the objective and subjective factors are considered when you evaluate the voice quality.

Configuration prerequisites

A voice test requires cooperation between the NQA server and the NQA client. Before a voice test, make sure that the UDP listening function is configured on the NQA server. For the configuration of UDP listening function, see Configuring the NQA Server.

Configuring a voice test

Follow these steps to configure a voice test:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Configure the test type as voice and enter test type view

type voice

Required

Configure the destination address for a test operation

destination ip ip-address

Required

By default, no destination IP address is configured for a test operation.

The destination IP address must be consistent with that of the existing listening service on the NQA server.

Configure the destination port for a test operation

destination port port-number

Required

By default, no destination port number is configured for a test operation.

The destination port must be consistent with that of the existing listening service on the NQA server.

Configure the codec type

codec-type { g711a | g711u | g729a }

Optional

By default, the codec type is G.711 A-law.

Configure the advantage factor for calculating MOS and ICPIF values

advantage-factor factor

Optional

By default, the advantage factor is 0.

Specify the source IP address for the requests in a test operation

source ip ip-address

Optional

By default, no source IP address is specified.

The source IP address must be that of an interface on the device and the interface must be up. Otherwise, the test will fail.

Specify the source port number for the requests in a test operation

source port port-number

Optional

By default, no source port number is specified.

Configure the size of a probe packet to be sent

data-size size

Optional

By default, the probe packet size depends on the codec type. The default packet size is 172 bytes for G.711A-law and G.711 µ-law codec type, and is 32 bytes for G.729 A-law codec type.

Configure the filler string of a probe packet sent

data-fill string

Optional

By default, the filler string of a probe packet is the hexadecimal number 00010203040506070809.

Configure the number of packets sent in a voice probe

probe packet-number

packet-number

Optional

1000 by default.

Configure the interval for sending packets in a voice probe

probe packet-interval packet-interval

Optional

20 milliseconds by default.

Configure the timeout for waiting for a response in a voice test

probe packet-timeout packet-timeout

Optional

5000 milliseconds by default.

Configure common optional parameters

See Configuring Optional Parameters Common to an NQA Test Group

Optional

 

 

NOTE:

Only one probe can be made in one voice test, and the number of probe packets sent in each probe depends on the configuration of the probe packet-number command.

 

Configuring a DLSw Test

A DLSw test is used to test the response time of the DLSw device.

Configuration prerequisites

Enable the DLSw function on the peer device before DLSw test.

Configuring a DLSw test

Follow these steps to configure a DLSw test:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Configure the test type as DLSw and enter test type view

type dlsw

Required

Configure the destination address for a test operation

destination ip ip-address

Required

By default, no destination IP address is configured for a test operation.

Configure the source IP address of a probe request in a test operation

source ip ip-address

Optional

By default, no source IP address is specified.

The source IP address must be that of an interface on the device and the interface must be up. Otherwise, the test will fail.

Configure common optional parameters

See Configuring Optional Parameters Common to an NQA Test Group

Optional

 

Configuring the Collaboration Function

Collaboration is implemented by establishing reaction entries to monitor the detection results of the current test group. If the number of consecutive probe failures reaches the threshold, the configured action is triggered.

Follow these steps to configure the collaboration function:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Enter test type view of the test group

type { dhcp | dlsw | dns | ftp | http | icmp-echo | snmp | tcp | udp-echo }

The collaboration function is not supported in UDP jitter and voice tests.

Configure a reaction entry

reaction item-number checked-element probe-fail threshold-type consecutive consecutive-occurrences action-type trigger-only

Required

Not created by default.

Exit to system view

quit

Configure a track entry and associate it with the specified reaction entry of the NQA test group

track entry-number nqa entry admin-name operation-tag reaction item-number

Required

Not created by default.

 

 

NOTE:

·       You cannot modify the content of a reaction entry by using the reaction command after the reaction entry is created.

·       The collaboration function is not supported in a UDP jitter or voice test.

 

Configuring Threshold Monitoring

Configuration prerequisites

Before configuring threshold monitoring, configure the following:

·           Destination address of the trap message configured with the snmp-agent target-host command. For more information about the snmp-agent target-host command, see SNMP Commands in the System Volume.

·           Create an NQA test group and configure related parameters.

Configuring threshold monitoring

Follow these steps to configure threshold monitoring:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Enter test type view of the test group

type { dhcp | dlsw | dns | ftp | http | icmp-echo | snmp | tcp | udp-echo | udp-jitter | voice }

Configure to send traps to the network management server under specified conditions

reaction trap { probe-failure consecutive-probe-failures | test-complete | test-failure cumulate-probe-failures }

Required

Configure to send traps accordingly.

No traps are sent to the network management server by default.

Configure a reaction entry for monitoring the probe duration of a test (not supported in UDP jitter and voice tests)

reaction item-number checked-element probe-duration threshold-type { accumulate accumulate-occurrences | average | consecutive consecutive-occurrences } threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]

Configure a reaction entry for monitoring the probe failure times (not supported in UDP jitter and voice tests)

reaction item-number checked-element probe-fail threshold-type { accumulate accumulate-occurrences | consecutive consecutive-occurrences } [ action-type { none | trap-only } ]

Configure a reaction entry for monitoring packet round-trip time (only supported in UDP jitter and voice tests)

reaction item-number checked-element rtt threshold-type { accumulate accumulate-occurrences | average } threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]

Configure a reaction entry for monitoring the packet loss in each test (only supported in UDP jitter and voice tests)

reaction item-number checked-element packet-loss threshold-type accumulate accumulate-occurrences [ action-type { none | trap-only } ]

Configure a reaction entry for monitoring one-way delay jitter (only supported in UDP jitter and voice tests)

reaction item-number checked-element { jitter-ds | jitter-sd } threshold-type { accumulate accumulate-occurrences | average } threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]

Configure a reaction entry for monitoring the one-way delay (only supported in UDP jitter and voice tests)

reaction item-number checked-element { owd-ds | owd-sd } threshold-value upper-threshold lower-threshold

Configure a reaction entry for monitoring the ICPIF value (only supported in voice tests)

reaction item-number checked-element icpif threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]

Configure a reaction entry for monitoring the MOS value (only supported in voice tests)

reaction item-number checked-element mos threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]

 

 

NOTE:

·       NQA DNS tests do not support the action of sending trap messages. In other words, the action to be triggered in DNS tests can only be the default one, none.

·       Only the test-complete keyword is supported for the reaction trap command in a voice test.

 

Configuring the NQA Statistics Function

NQA puts the NQA tests completed in a specified interval into one group, and calculates the statistics of the test results of the group. These statistics form a statistics group. To view information of the statistics group, use the display nqa statistics command. To set the interval for collecting statistics, use the statistics interval command.

When the number of statistics groups kept reaches the upper limit, if a new statistics group is generated, the statistics group that is kept for the longest time is deleted. To set the maximum number of statistics groups that can be kept, use the statistics max-group command.

A statistics group is formed after the last test is completed within the specified interval. A statistics group has the aging mechanism. A statistics group will be deleted after it is kept for a period of time. To set the hold time of a statistics group, use the statistics hold-time command.

Follow these steps to configure the NQA statistics function:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Enter test type view of the test group

type { dlsw | dns | ftp | http | icmp-echo | snmp | tcp | udp-echo | udp-jitter | voice }

Configure the interval for collecting the statistics of the test results

statistics interval interval

Optional

60 minutes by default.

Configure the maximum number of statistics groups that can be kept

statistics max-group number

Optional

2 by default.

If the maximum number is 0, it indicates that no statistics is performed.

Configure the hold time of a statistics group

statistics hold-time hold-time

Optional

120 minutes by default.

 

 

NOTE:

·       The NQA statistics function is not supported in a DHCP test.

·       If you specify the interval argument in the frequency interval command as 0, no statistics group information is generated.

 

Configuring the History Records Saving Function

With the history records saving function enabled, the system saves the history records of the NQA test. To view the history records of a test group, use the display nqa history command.

The configuration task also allows you to configure:

·           Lifetime of the history records: The records are removed when the lifetime is reached.

·           The maximum number of history records that can be saved in a test group: If the number of history records in a test group exceeds the maximum number, the earliest history records are removed.

Follow these steps to configure the history records saving function of an NQA test group:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Enter NQA test type view

type { dhcp | dlsw | dns | ftp | http | icmp-echo | snmp | tcp | udp-echo | udp-jitter | voice }

Enable the saving of the history records of the NQA test group

history-record enable

Required

By default, history records of the NQA test group are not saved.

Set the lifetime of the history records in an NQA test group

history-record keep-time keep-time

Optional

By default, the history records in the NQA test group are kept for 120 minutes.

Configure the maximum number of history records that can be saved in a test group

history-record number number

Optional

By default, the maximum number of records that can be saved in a test group is 50

 

Configuring Optional Parameters Common to an NQA Test Group

Optional parameters common to an NQA test group are valid only for tests in this test group.

Unless otherwise specified, the following parameters are applicable to all test types and they can be configured according to the actual conditions.

Follow these steps to configure optional parameters common to an NQA test group:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter NQA test group view

nqa entry admin-name operation-tag

Enter test type view of a test group

type { dhcp | dlsw | dns | ftp | http | icmp-echo | snmp | tcp | udp-echo | udp-jitter | voice }

Configure the descriptive string for a test group

description text

Optional

By default, no descriptive string is available for a test group.

Configure the interval between two consecutive tests for a test group

frequency interval

Optional

By default, the interval between two consecutive tests for a test group is 0 milliseconds, that is, only one test is performed.

If the last test is not completed when the interval specified by the frequency command is reached, a new test is not started.

Configure the number of probes in an NQA test

probe count times

Optional

By default, one probe is performed in a test.

Only one probe can be made in one voice test. Therefore, this command is not available in a voice test.

Configure the NQA probe timeout time

probe timeout timeout

Optional

By default, the timeout time is 3000 milliseconds.

This parameter is not available for a UDP jitter test.

Configure the maximum number of hops a probe packet traverses in the network

ttl value

Optional

20 by default.

This parameter is not available for a DHCP test.

Configure the ToS field in an IP packet header in an NQA probe packet

tos value

Optional

0 by default.

This parameter is not available for a DHCP test.

Enable the routing table bypass function

route-option bypass-route

Optional

Disabled by default.

This parameter is not available for a DHCP test.

 

Scheduling an NQA Test Group

By configuring NQA test group scheduling, you can set the start time and test duration for a test group to perform NQA tests. The start time can take a specific value or can be now, which indicates that a test is started immediately; the test duration can take a specific value or can be forever, which indicates that a test does not stop until you use the undo nqa schedule command to stop the test.

A test group performs tests when the system time is between the start time and the end time (the start time plus test duration). If the system time is behind the start time when you execute the nqa schedule command, a test is started when the system time reaches the start time. If the system time is between the start time and the end time, a test is started at once. If the system time is ahead of the end time, no test is started. To view the current system time, use the display clock command.

Configuration prerequisites

Before scheduling an NQA test group, make sure:

·           Required test parameters corresponding to a test type have been configured;

·           For a test that needs the cooperation with the NQA server, configuration on the NQA server has been completed.

Scheduling an NQA test group

Follow these steps to schedule an NQA test group:

To do…

Use the command…

Remarks

Enter system view

system-view

Schedule an NQA test group

nqa schedule admin-name operation-tag start-time { hh:mm:ss [ yyyy/mm/dd ] | now } lifetime { lifetime | forever }

Required

Configure the maximum number of tests that the NQA client can simultaneously perform

nqa agent max-concurrent number

Optional

 

CAUTION:

·       After an NQA test group is scheduled, you cannot enter the test group view or test type view.

·       A started test group or a test group that has completed tests will not be influenced by the system time change; only a test group that is waiting to perform tests will be influenced by the system time change.

 

Displaying and Maintaining NQA

To do…

Use the command…

Remarks

Display history records of NQA test operation information

display nqa history [ admin-name operation-tag ]

Available in any view

Display the current monitoring results of reaction entries

display nqa reaction counters [ admin-name operation-tag [ item-number ] ]

Display the results of the last NQA test

display nqa result [ admin-name operation-tag ]

Display the statistics of a type of NQA test

display nqa statistics [ admin-name operation-tag ]

Display NQA server status

display nqa server status

 

NQA Configuration Examples

ICMP Echo Test Configuration Example

Network requirements

As shown in Figure 3, use the NQA ICMP function to test whether the NQA client (Device A) can send packets to the specified destination (Device B) and test the round-trip time of packets.

Figure 3 Network diagram for ICMP echo tests

 

Configuration procedure

# Create an ICMP echo test group and configure related test parameters.

<DeviceA> system-view

[DeviceA] nqa entry admin test

[DeviceA-nqa-admin-test] type icmp-echo

[DeviceA-nqa-admin-test-icmp-echo] destination ip 10.2.2.2

# Configure optional parameters.

[DeviceA-nqa-admin-test-icmp-echo] probe count 10

[DeviceA-nqa-admin-test-icmp-echo] probe timeout 500

[DeviceA-nqa-admin-test-icmp-echo] frequency 5000

# Enable the saving of history records.

[DeviceA-nqa-admin-test-icmp-echo] history-record enable

[DeviceA-nqa-admin-test-icmp-echo] history-record number 10

[DeviceA-nqa-admin-test-icmp-echo] quit

# Enable ICMP echo test.

[DeviceA] nqa schedule admin test start-time now lifetime forever

# Disable ICMP echo test after the test begins for a period of time.

[DeviceA] undo nqa schedule admin test

# Display results of the last ICMP echo test.

[DeviceA] display nqa result admin test

  NQA entry (admin admin, tag test) test results:

    Destination IP address: 10.2.2.2

      Send operation times: 10             Receive response times: 10

      Min/Max/Average round trip time: 2/5/3

      Square-Sum of round trip time: 96

      Last succeeded probe time: 2007-08-23 15:00:01.2

    Extended results:

      Packet loss in test: 0%

      Failures due to timeout: 0

      Failures due to disconnect: 0

      Failures due to no connection: 0

      Failures due to sequence error: 0

      Failures due to internal error: 0

      Failures due to other errors: 0

      Packet(s) arrived late: 0

# Display the history of ICMP echo tests.

[DeviceA] display nqa history admin test

  NQA entry (admin admin, tag test) history record(s):

    Index      Response     Status           Time

    370        3            Succeeded        2007-08-23 15:00:01.2

    369        3            Succeeded        2007-08-23 15:00:01.2

    368        3            Succeeded        2007-08-23 15:00:01.2

    367        5            Succeeded        2007-08-23 15:00:01.2

    366        3            Succeeded        2007-08-23 15:00:01.2

    365        3            Succeeded        2007-08-23 15:00:01.2

    364        3            Succeeded        2007-08-23 15:00:01.1

    363        2            Succeeded        2007-08-23 15:00:01.1

    362        3            Succeeded        2007-08-23 15:00:01.1

    361        2            Succeeded        2007-08-23 15:00:01.1

DHCP Test Configuration Example

Network requirements

As shown in Figure 4, use the NQA DHCP function to test the time necessary for Device A to obtain an IP address from the DHCP server Device B.

Figure 4 Network diagram for DHCP

 

Configuration procedure

# Create a DHCP test group and configure related test parameters.

<DeviceA> system-view

[DeviceA] nqa entry admin test

[DeviceA-nqa-admin-test] type dhcp

[DeviceA-nqa-admin-test-dhcp] operation interface gigabitethernet 0/1

# Enable the saving of history records.

[DeviceA-nqa-admin-test-dhcp] history-record enable

[DeviceA-nqa-admin-test-dhcp] quit

# Enable DHCP test.

[DeviceA] nqa schedule admin test start-time now lifetime forever

# Disable DHCP test after the test begins for a period of time.

[DeviceA] undo nqa schedule admin test

# Display results of the last DHCP test.

[DeviceA] display nqa result admin test

  NQA entry (admin admin, tag test) test results:

      Send operation times: 1              Receive response times: 1

      Min/Max/Average round trip time: 512/512/512

      Square-Sum of round trip time: 262144

      Last succeeded probe time: 2007-11-22 09:54:03.8

    Extended results:

      Packet loss in test: 0%

      Failures due to timeout: 0

      Failures due to disconnect: 0

      Failures due to no connection: 0

      Failures due to sequence error: 0

      Failures due to internal error: 0

      Failures due to other errors: 0

      Packet(s) arrived late: 0

# Display the history of DHCP tests.

[DeviceA] display nqa history admin test

  NQA entry (admin admin, tag test) history record(s):

    Index      Response     Status           Time

    1          512          Succeeded        2007-11-22 09:54:03.8

DNS Test Configuration Example

Network requirements

As shown in Figure 5, use the DNS function to test whether Device A can resolve the domain name host.com into an IP address through the DNS server and test the time required for resolution.

Figure 5 Network diagram for DNS tests

 

Configuration procedure

# Create a DNS test group and configure related test parameters.

<DeviceA> system-view

[DeviceA] nqa entry admin test

[DeviceA-nqa-admin-test] type dns

[DeviceA-nqa-admin-test-dns] destination ip 10.2.2.2

[DeviceA-nqa-admin-test-dns] resolve-target host.com

# Enable the saving of history records.

[DeviceA-nqa-admin-test-dns] history-record enable

[DeviceA-nqa-admin-test-dns] quit

# Enable DNS test.

[DeviceA] nqa schedule admin test start-time now lifetime forever

# Disable DNS test after the test begins for a period of time.

[DeviceA] undo nqa schedule admin test

# Display results of the last DNS test.

[DeviceA] display nqa result admin test

  NQA entry (admin admin, tag test) test results:

    Destination IP address: 10.2.2.2

      Send operation times: 1              Receive response times: 1

      Min/Max/Average round trip time: 62/62/62

      Square-Sum of round trip time: 3844

      Last succeeded probe time: 2008-11-10 10:49:37.3

    Extended results:

      Packet loss in test: 0%

      Failures due to timeout: 0

      Failures due to disconnect: 0

      Failures due to no connection: 0

      Failures due to sequence error: 0

      Failures due to internal error: 0

      Failures due to other errors: 0

      Packet(s) arrived late: 0

# Display the history of DNS tests.

[DeviceA] display nqa history admin test

  NQA entry (admin admin, tag test) history record(s):

    Index      Response     Status           Time

    1          62           Succeeded        2008-11-10 10:49:37.3

FTP Test Configuration Example

Network requirements

As shown in Figure 6, use the NQA FTP function to test the connection with a specified FTP server and the time necessary for Device A to upload a file to the FTP server. The login username is admin, the login password is systemtest, and the file to be transferred to the FTP server is config.txt.

Figure 6 Network diagram for FTP tests

 

Configuration procedure

# Create an FTP test group and configure related test parameters.

<DeviceA> system-view

[DeviceA] nqa entry admin test

[DeviceA-nqa-admin-test] type ftp

[DeviceA-nqa-admin-test-ftp] destination ip 10.2.2.2

[DeviceA-nqa-admin-test-ftp] source ip 10.1.1.1

[DeviceA-nqa-admin-test-ftp] operation put

[DeviceA-nqa-admin-test-ftp] username admin

[DeviceA-nqa-admin-test-ftp] password systemtest

[DeviceA-nqa-admin-test-ftp] filename config.txt

# Enable the saving of history records.

[DeviceA-nqa-admin-test-ftp] history-record enable

[DeviceA-nqa-admin-test-ftp] quit

# Enable FTP test.

[DeviceA] nqa schedule admin test start-time now lifetime forever

# Disable FTP test after the test begins for a period of time.

[DeviceA] undo nqa schedule admin test

# Display results of the last FTP test.

[DeviceA] display nqa result admin test

  NQA entry (admin admin, tag test) test results:

    Destination IP address: 10.2.2.2

      Send operation times: 1              Receive response times: 1

      Min/Max/Average round trip time: 173/173/173

      Square-Sum of round trip time: 29929

      Last succeeded probe time: 2007-11-22 10:07:28.6

    Extended results:

      Packet loss in test: 0%

      Failures due to timeout: 0

      Failures due to disconnect: 0

      Failures due to no connection: 0

      Failures due to sequence error: 0

      Failures due to internal error: 0

      Failures due to other errors: 0

      Packet(s) arrived late: 0

# Display the history of FTP tests.

[DeviceA] display nqa history admin test

  NQA entry (admin admin, tag test) history record(s):

    Index      Response     Status           Time

    1          173          Succeeded        2007-11-22 10:07:28.6

HTTP Test Configuration Example

Network requirements

As shown in Figure 7, use the HTTP function to test the connection with a specified HTTP server and the time required to obtain data from the HTTP server.

Figure 7 Network diagram for the HTTP tests

 

Configuration procedure

# Create an HTTP test group and configure related test parameters.

<DeviceA> system-view

[DeviceA] nqa entry admin test

[DeviceA-nqa-admin-test] type http

[DeviceA-nqa-admin-test-http] destination ip 10.2.2.2

[DeviceA-nqa-admin-test-http] operation get

[DeviceA-nqa-admin-test-http] url /index.htm

[DeviceA-nqa-admin-test-http] http-version v1.0

# Enable the saving of history records.

[DeviceA-nqa-admin-test-http] history-record enable

[DeviceA-nqa-admin-test-http] quit

# Enable HTTP test.

[DeviceA] nqa schedule admin test start-time now lifetime forever

# Disable HTTP test after the test begins for a period of time.

[DeviceA] undo nqa schedule admin test

# Display results of the last HTTP test.

[DeviceA] display nqa result admin test

  NQA entry (admin admin, tag test) test results:

    Destination IP address: 10.2.2.2

      Send operation times: 1              Receive response times: 1

      Min/Max/Average round trip time: 64/64/64

      Square-Sum of round trip time: 4096

      Last succeeded probe time: 2007-11-22 10:12:47.9

    Extended results:

      Packet loss in test: 0%

      Failures due to timeout: 0

      Failures due to disconnect: 0

      Failures due to no connection: 0

      Failures due to sequence error: 0

      Failures due to internal error: 0

      Failures due to other errors:

      Packet(s) arrived late: 0

# Display the history of HTTP tests.

[DeviceA] display nqa history admin test

  NQA entry (admin admin, tag test) history record(s):

    Index      Response     Status           Time

    1          64           Succeeded        2007-11-22 10:12:47.9

UDP Jitter Test Configuration Example

Network requirements

As shown in Figure 8, use the NQA UDP jitter function to test the delay jitter of packet transmission between Device A and Device B.

Figure 8 Network diagram for UDP jitter tests

 

Configuration procedure

Step1      Configure Device B

# Enable the NQA server and configure the listening IP address as 10.2.2.2 and port number as 9000.

<DeviceB> system-view

[DeviceB] nqa server enable

[DeviceB] nqa server udp-echo 10.2.2.2 9000

Step2      Configure Device A

# Create a UDP jitter test group and configure related test parameters.

<DeviceA> system-view

[DeviceA] nqa entry admin test

[DeviceA-nqa-admin-test] type udp-jitter

[DeviceA-nqa-admin-test-udp-jitter] destination ip 10.2.2.2

[DeviceA-nqa-admin-test-udp-jitter] destination port 9000

[DeviceA-nqa-admin-test-udp-jitter] frequency 1000

[DeviceA-nqa-admin-test-udp-jitter] quit

# Enable UDP jitter test.

[DeviceA] nqa schedule admin test start-time now lifetime forever

# Disable UDP jitter test after the test begins for a period of time.

[DeviceA] undo nqa schedule admin test

# Display the result of the last UDP jitter test.

[DeviceA] display nqa result admin test

  NQA entry (admin admin, tag test) test results:

    Destination IP address: 10.2.2.2

      Send operation times: 10             Receive response times: 10

      Min/Max/Average round trip time: 15/32/17

      Square-Sum of round trip time: 3235

      Last succeeded probe time: 2008-05-29 13:56:17.6

    Extended results:

      Packet loss in test: 0%

      Failures due to timeout: 0

      Failures due to disconnect: 0

      Failures due to no connection: 0

      Failures due to sequence error: 0

      Failures due to internal error: 0

      Failures due to other errors: 0

      Packet(s) arrived late: 0

    UDP-jitter results:

     RTT number: 10

      Min positive SD: 4                     Min positive DS: 1

      Max positive SD: 21                    Max positive DS: 28

      Positive SD number: 5                  Positive DS number: 4

      Positive SD sum: 52                    Positive DS sum: 38

      Positive SD average: 10                Positive DS average: 10

      Positive SD square sum: 754            Positive DS square sum: 460

      Min negative SD: 1                     Min negative DS: 6

      Max negative SD: 13                    Max negative DS: 22

      Negative SD number: 4                  Negative DS number: 5

      Negative SD sum: 38                    Negative DS sum: 52

      Negative SD average: 10                Negative DS average: 10

      Negative SD square sum: 460            Negative DS square sum: 754

    One way results:

      Max SD delay: 15                       Max DS delay: 16

      Min SD delay: 7                        Min DS delay: 7

      Number of SD delay: 10                 Number of DS delay: 10

      Sum of SD delay: 78                    Sum of DS delay: 85

      Square sum of SD delay: 666            Square sum of DS delay: 787

      SD lost packet(s): 0                   DS lost packet(s): 0

      Lost packet(s) for unknown reason: 0

# Display the statistics of UDP jitter tests.

[DeviceA] display nqa statistics admin test

  NQA entry (admin admin, tag test) test statistics:

    NO. : 1

    Destination IP address: 10.2.2.2

      Start time: 2008-05-29 13:56:14.0

      Life time: 47 seconds

      Send operation times: 410            Receive response times: 410

      Min/Max/Average round trip time: 1/93/19

      Square-Sum of round trip time: 206176

    Extended results:

      Packet loss in test: 0%

      Failures due to timeout: 0

      Failures due to disconnect: 0

      Failures due to no connection: 0

      Failures due to sequence error: 0

      Failures due to internal error: 0

      Failures due to other errors: 0

      Packet(s) arrived late: 0

    UDP-jitter results:

     RTT number: 410

      Min positive SD: 3                     Min positive DS: 1

      Max positive SD: 30                    Max positive DS: 79

      Positive SD number: 186                Positive DS number: 158

      Positive SD sum: 2602                  Positive DS sum: 1928

      Positive SD average: 13                Positive DS average: 12

      Positive SD square sum: 45304          Positive DS square sum: 31682

      Min negative SD: 1                     Min negative DS: 1

      Max negative SD: 30                    Max negative DS: 78

      Negative SD number: 181                Negative DS number: 209

      Negative SD sum: 181                   Negative DS sum: 209

      Negative SD average: 13                Negative DS average: 14

      Negative SD square sum: 46994          Negative DS square sum: 3030

    One way results:

      Max SD delay: 46                       Max DS delay: 46

      Min SD delay: 7                        Min DS delay: 7

      Number of SD delay: 410                Number of DS delay: 410

      Sum of SD delay: 3705                  Sum of DS delay: 3891

      Square sum of SD delay: 45987          Square sum of DS delay: 49393

      SD lost packet(s): 0                   DS lost packet(s): 0

      Lost packet(s) for unknown reason: 0

 

 

NOTE:

The display nqa history command does not show the results of UDP jitter tests. Therefore, to know the result of a UDP jitter test, you are recommended to use the display nqa result command to view the probe results of the latest NQA test, or use the display nqa statistics command to view the statistics of NQA tests.

 

SNMP Test Configuration Example

Network requirements

As shown in Figure 9, use the NQA SNMP query function to test the time it takes for Device A to send an SNMP query packet to the SNMP agent and receive a response packet.

Figure 9 Network diagram for SNMP tests

 

Configuration procedure

Step1      Configurations on SNMP agent

# Enable the SNMP agent service and set the SNMP version to all, the read community to public, and the write community to private.

<DeviceB> system-view

[DeviceB] snmp-agent sys-info version all

[DeviceB] snmp-agent community read public

[DeviceB] snmp-agent community write private

Step2      Configurations on Device A

# Create an SNMP query test group and configure related test parameters.

<DeviceA> system-view

[DeviceA] nqa entry admin test

[DeviceA-nqa-admin-test] type snmp

[DeviceA-nqa-admin-test-snmp] destination ip 10.2.2.2

# Enable the saving of history records.

[DeviceA-nqa-admin-test-snmp] history-record enable

[DeviceA-nqa-admin-test-snmp] quit

# Enable SNMP query test.

[DeviceA] nqa schedule admin test start-time now lifetime forever

# Disable SNMP query test after the test begins for a period of time.

[DeviceA] undo nqa schedule admin test

# Display results of the last SNMP test.

[DeviceA] display nqa result admin test

  NQA entry (admin admin, tag test) test results:

    Destination IP address: 10.2.2.2

      Send operation times: 1              Receive response times: 1

      Min/Max/Average round trip time: 50/50/50

      Square-Sum of round trip time: 2500

      Last succeeded probe time: 2007-11-22 10:24:41.1

    Extended results:

      Packet loss in test: 0%

      Failures due to timeout: 0

      Failures due to disconnect: 0

      Failures due to no connection: 0

      Failures due to sequence error: 0

      Failures due to internal error: 0

      Failures due to other errors: 0

      Packet(s) arrived late: 0

# Display the history of SNMP tests.

[DeviceA] display nqa history admin test

  NQA entry (admin admin, tag test) history record(s):

    Index      Response     Status           Time

    1          50           Timeout          2007-11-22 10:24:41.1

TCP Test Configuration Example

Network requirements

As shown in Figure 10, use the NQA TCP function to test the time for establishing a TCP connection between Device A and Device B. Port 9000 is used.

Figure 10 Network diagram for TCP tests

 

Configuration procedure

Step1      Configure Device B

# Enable the NQA server and configure the listening IP address as 10.2.2.2 and port number as 9000.

<DeviceB> system-view

[DeviceB] nqa server enable

[DeviceB] nqa server tcp-connect 10.2.2.2 9000

Step2      Configure Device A

# Create a TCP test group and configure related test parameters.

<DeviceA> system-view

[DeviceA] nqa entry admin test

[DeviceA-nqa-admin-test] type tcp

[DeviceA-nqa-admin-test-tcp] destination ip 10.2.2.2

[DeviceA-nqa-admin-test-tcp] destination port 9000

# Enable the saving of history records.

[DeviceA-nqa-admin-test-tcp] history-record enable

[DeviceA-nqa-admin-test-tcp] quit

# Enable TCP test.

[DeviceA] nqa schedule admin test start-time now lifetime forever

# Disable TCP test after the test begins for a period of time.

[DeviceA] undo nqa schedule admin test

# Display results of the last TCP test.

[DeviceA] display nqa result admin test

  NQA entry (admin admin, tag test) test results:

    Destination IP address: 10.2.2.2

      Send operation times: 1              Receive response times: 1

      Min/Max/Average round trip time: 13/13/13

      Square-Sum of round trip time: 169

      Last succeeded probe time: 2007-11-22 10:27:25.1

    Extended results:

      Packet loss in test: 0%

      Failures due to timeout: 0

      Failures due to disconnect: 0

      Failures due to no connection: 0

      Failures due to sequence error: 0

      Failures due to internal error: 0

      Failures due to other errors: 0

      Packet(s) arrived late: 0

# Display the history of TCP tests.

[DeviceA] display nqa history admin test

  NQA entry (admin admin, tag test) history record(s):

Index      Response     Status           Time

    1          13           Succeeded        2007-11-22 10:27:25.1

UDP Echo Test Configuration Example

Network requirements

As shown in Figure 11, use the NQA UDP echo function to test the round-trip time between Device A and Device B. The port number is 8000.

Figure 11 Network diagram for the UDP echo tests

 

Configuration procedure

Step1      Configure Device B

# Enable the NQA server and configure the listening IP address as 10.2.2.2 and port number as 8000.

<DeviceB> system-view

[DeviceB] nqa server enable

[DeviceB] nqa server udp-echo 10.2.2.2 8000

Step2      Configure Device A

# Create a UDP echo test group and configure related test parameters.

<DeviceA> system-view

[DeviceA] nqa entry admin test

[DeviceA-nqa-admin-test] type udp-echo

[DeviceA-nqa-admin-test-udp-echo] destination ip 10.2.2.2

[DeviceA-nqa-admin-test-udp-echo] destination port 8000

# Enable the saving of history records.

[DeviceA-nqa-admin-test-udp-echo] history-record enable

[DeviceA-nqa-admin-test-udp-echo] quit

# Enable UDP echo test.

[DeviceA] nqa schedule admin test start-time now lifetime forever

# Disable UDP echo test after the test begins for a period of time.

[DeviceA] undo nqa schedule admin test

# Display results of the last UDP echo test.

[DeviceA] display nqa result admin test

  NQA entry (admin admin, tag test) test results:

    Destination IP address: 10.2.2.2

      Send operation times: 1              Receive response times: 1

      Min/Max/Average round trip time: 25/25/25

      Square-Sum of round trip time: 625

      Last succeeded probe time: 2007-11-22 10:36:17.9

    Extended results:

      Packet loss in test: 0%

      Failures due to timeout: 0

      Failures due to disconnect: 0

      Failures due to no connection: 0

      Failures due to sequence error: 0

      Failures due to internal error: 0

      Failures due to other errors: 0

      Packet(s) arrived late: 0

# Display the history of UDP echo tests.

[DeviceA] display nqa history admin test

  NQA entry (admin admin, tag test) history record(s):

    Index      Response     Status           Time

    1          25           Succeeded        2007-11-22 10:36:17.9

Voice Test Configuration Example

Network requirements

As shown in Figure 12, use the NQA voice function to test the delay jitter of voice packet transmission and voice quality between Device A and Device B.

Figure 12 Network diagram for voice tests

 

Configuration procedure

Step1      Configure Device B

# Enable the NQA server and configure the listening IP address as 10.2.2.2 and port number as 9000.

<DeviceB> system-view

[DeviceB] nqa server enable

[DeviceB] nqa server udp-echo 10.2.2.2 9000

Step2      Configure Device A

# Create a voice test group and configure related test parameters.

<DeviceA> system-view

[DeviceA] nqa entry admin test

[DeviceA-nqa-admin-test] type voice

[DeviceA-nqa-admin-test-voice] destination ip 10.2.2.2

[DeviceA-nqa-admin-test-voice] destination port 9000

[DeviceA-nqa-admin-test-voice] quit

# Enable voice test.

[DeviceA] nqa schedule admin test start-time now lifetime forever

# Disable the voice test after the test begins for a period of time.

[DeviceA] undo nqa schedule admin test

# Display the result of the last voice test.

[DeviceA] display nqa result admin test

  NQA entry (admin admin, tag test) test results:

    Destination IP address: 10.2.2.2

      Send operation times: 1000           Receive response times: 1000

      Min/Max/Average round trip time: 31/1328/33

      Square-Sum of round trip time: 2844813

      Last succeeded probe time: 2008-06-13 09:49:31.1

    Extended results:

      Packet loss in test: 0%

      Failures due to timeout: 0

      Failures due to disconnect: 0

      Failures due to no connection: 0

      Failures due to sequence error: 0

      Failures due to internal error: 0

      Failures due to other errors: 0

      Packet(s) arrived late: 0

    Voice results:

     RTT number: 1000

      Min positive SD: 1                     Min positive DS: 1

      Max positive SD: 204                   Max positive DS: 1297

      Positive SD number: 257                Positive DS number: 259

      Positive SD sum: 759                   Positive DS sum: 1797

      Positive SD average: 2                 Positive DS average: 6

      Positive SD square sum: 54127          Positive DS square sum: 1691967

      Min negative SD: 1                     Min negative DS: 1

      Max negative SD: 203                   Max negative DS: 1297

      Negative SD number: 255                Negative DS number: 259

      Negative SD sum: 759                   Negative DS sum: 1796

      Negative SD average: 2                 Negative DS average: 6

      Negative SD square sum: 53655          Negative DS square sum: 1691776

    One way results:

      Max SD delay: 343                      Max DS delay: 985

      Min SD delay: 343                      Min DS delay: 985

      Number of SD delay: 1                  Number of DS delay: 1

      Sum of SD delay: 343                   Sum of DS delay: 985

      Square sum of SD delay: 117649         Square sum of DS delay: 970225

      SD lost packet(s): 0                   DS lost packet(s): 0

      Lost packet(s) for unknown reason: 0

    Voice scores:

      MOS value: 4.38                        ICPIF value: 0

# Display the statistics of voice tests.

[DeviceA] display nqa statistics admin test

  NQA entry (admin admin, tag test) test statistics:

    NO. : 1

    Destination IP address: 10.2.2.2

      Start time: 2008-06-13 09:45:37.8

      Life time: 331 seconds

      Send operation times: 4000           Receive response times: 4000

      Min/Max/Average round trip time: 15/1328/32

      Square-Sum of round trip time: 7160528

    Extended results:

      Packet loss in test: 0%

      Failures due to timeout: 0

      Failures due to disconnect: 0

      Failures due to no connection: 0

      Failures due to sequence error: 0

      Failures due to internal error: 0

      Failures due to other errors: 0

      Packet(s) arrived late: 0

    Voice results:

     RTT number: 4000

      Min positive SD: 1                     Min positive DS: 1

      Max positive SD: 360                   Max positive DS: 1297

      Positive SD number: 1030               Positive DS number: 1024

      Positive SD sum: 4363                  Positive DS sum: 5423

      Positive SD average: 4                 Positive DS average: 5

      Positive SD square sum: 497725         Positive DS square sum: 2254957

      Min negative SD: 1                     Min negative DS: 1

      Max negative SD: 360                   Max negative DS: 1297

      Negative SD number: 1028               Negative DS number: 1022

      Negative SD sum: 1028                  Negative DS sum: 1022

      Negative SD average: 4                 Negative DS average: 5

      Negative SD square sum: 495901         Negative DS square sum: 5419

    One way results:

      Max SD delay: 359                      Max DS delay: 985

      Min SD delay: 0                        Min DS delay: 0

      Number of SD delay: 4                  Number of DS delay: 4

      Sum of SD delay: 1390                  Sum of DS delay: 1079

      Square sum of SD delay: 483202         Square sum of DS delay: 973651

      SD lost packet(s): 0                   DS lost packet(s): 0

      Lost packet(s) for unknown reason: 0

    Voice scores:

      Max MOS value: 4.38                    Min MOS value: 4.38

      Max ICPIF value: 0                     Min ICPIF value: 0

 

 

NOTE:

The display nqa history command cannot show you the results of voice tests. Therefore, to know the result of a voice test, you are recommended to use the display nqa result command to view the probe results of the latest NQA test, or use the display nqa statistics command to view the statistics of NQA tests.

 

DLSw Test Configuration Example

Network requirements

As shown in Figure 13, use the NQA DLSw function to test the response time of the DLSw device.

Figure 13 Network diagram for the DLSw tests

 

Configuration procedure

# Create a DLSw test group and configure related test parameters.

<DeviceA> system-view

[DeviceA] nqa entry admin test

[DeviceA-nqa-admin-test] type dlsw

[DeviceA-nqa-admin-test-dlsw] destination ip 10.2.2.2

# Enable the saving of history records.

[DeviceA-nqa-admin-test-dlsw] history-record enable

[DeviceA-nqa-admin-test-dlsw] quit

# Enable DLSw test.

[DeviceA] nqa schedule admin test start-time now lifetime forever

# Disable DLSw test after the test begins for a period of time.

[DeviceA] undo nqa schedule admin test

# Display the result of the last DLSw test.

[DeviceA] display nqa result admin test

  NQA entry (admin admin, tag test) test results:

    Destination IP address: 10.2.2.2

      Send operation times: 1              Receive response times: 1

      Min/Max/Average round trip time: 19/19/19

      Square-Sum of round trip time: 361

      Last succeeded probe time: 2007-11-22 10:40:27.7

    Extended results:

      Packet loss in test: 0%

      Failures due to timeout: 0

      Failures due to disconnect: 0

      Failures due to no connection: 0

      Failures due to sequence error: 0

      Failures due to internal error: 0

      Failures due to other errors: 0

      Packet(s) arrived late: 0

# Display the history of DLSw tests.

[DeviceA] display nqa history admin test

  NQA entry (admin admin, tag test) history record(s):

    Index      Response     Status           Time

    1          19           Succeeded        2007-11-22 10:40:27.7

NQA Collaboration Configuration Example

Network requirements

As shown in Figure 14, configure a static route to Device C on Device A, with Device B as the next hop. Associate the static route, track entry, and NQA test group to verify whether the static route is active in real time.

Figure 14 Network diagram for NQA collaboration configuration example

 

Configuration procedure

Step1      Assign each interface an IP address. (omitted)

Step2      On Device A, configure a unicast static route and associate the static route with a track entry.

# Configure a static route, whose destination address is 10.2.1.1, and associate the static route with track entry 1.

<DeviceA> system-view

[DeviceA] ip route-static 10.1.1.2 24 10.2.1.1 track 1

Step3      On Device A, create an NQA test group.

# Create an NQA test group with the administrator name being admin and operation tag being test.

[DeviceA] nqa entry admin test

# Configure the test type of the NQA test group as ICMP echo.

[DeviceA-nqa-admin-test] type icmp-echo

# Configure the destination IP address of the ICMP echo test operation as 10.2.1.1.

[DeviceA-nqa-admin-test-icmp-echo] destination ip 10.2.1.1

# Configure the interval between two consecutive tests as 100 milliseconds.

[DeviceA-nqa-admin-test-icmp-echo] frequency 100

# Create reaction entry 1. If the number of consecutive probe failures reaches 5, collaboration with other modules is triggered.

[DeviceA-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only

[DeviceA-nqa-admin-test-icmp-echo] quit

# Configure the test start time and test duration for the test group.

[DeviceA] nqa schedule admin test start-time now lifetime forever

Step4      8On Device A, create the track entry.

# Create track entry 1 to associate it with Reaction entry 1 of the NQA test group (admin-test).

[DeviceA] track 1 nqa entry admin test reaction 1

Step5      Verify the configuration.

# On Device A, display information about all the track entries.

[DeviceA] display track all

Track ID: 1

  Status: Positive

  Notification delay: Positive 0, Negative 0 (in seconds)

  Reference object:

    NQA entry: admin test

    Reaction: 1

# Display brief information about active routes in the routing table on Device A.

[DeviceA] display ip routing-table

Routing Tables: Public

         Destinations : 5        Routes : 5

 

Destination/Mask    Proto  Pre  Cost         NextHop         Interface

 

10.1.1.0/24         Static 60   0            10.2.1.1        GE0/1

10.2.1.0/24         Direct 0    0            10.2.1.2        GE0/1

10.2.1.2/32         Direct 0    0            127.0.0.1       InLoop0

127.0.0.0/8         Direct 0    0            127.0.0.1       InLoop0

127.0.0.1/32        Direct 0    0            127.0.0.1       InLoop0

The information shows that the static route with the next hop 10.2.1.1 is active, and the status of the track entry is positive. The static route configuration works.

# Remove the IP address of Ethernet 1/1 on Device B.

<DeviceB> system-view

[DeviceB] interface ethernet 1/1

[DeviceB-Ethernet1/1] undo ip address

# On Device A, display information about all the track entries.

[DeviceA] display track all

Track ID: 1

  Status: Negative

  Notification delay: Positive 0, Negative 0 (in seconds)

  Reference object:

    NQA entry: admin test

    Reaction: 1

# Display brief information about active routes in the routing table on Device A.

[DeviceA] display ip routing-table

Routing Tables: Public

         Destinations : 4        Routes : 4

 

Destination/Mask    Proto  Pre  Cost         NextHop         Interface

 

10.2.1.0/24         Direct 0    0            10.2.1.2        GE0/1

10.2.1.2/32         Direct 0    0            127.0.0.1       InLoop0

127.0.0.0/8         Direct 0    0            127.0.0.1       InLoop0

127.0.0.1/32        Direct 0    0            127.0.0.1       InLoop0

The information shows that the next hop 10.2.1.1 of the static route is not reachable, and the status of the track entry is negative. The static route does not work.

 

H3C reserves the right to modify its collaterals without any prior notice. For the latest information of the collaterals, please consult H3C sales or call 400 hotline.