Network quality analyzer (NQA) allows you to measure network performance, verify the service levels for IP services and applications, and troubleshoot network problems. It provides the following types of operations:

· ICMP echo.

· ICMP jitter.

· FTP.

· HTTP.

· SNMP.

· TCP.

· UDP echo.

· UDP jitter.

As shown in Figure 1, the NQA source device (NQA client) sends data to the NQA destination device by simulating IP services and applications to measure network performance. The obtained performance metrics include the packet loss, application performance, and server response time.

All types of NQA operations require the NQA client, but only the TCP, UDP echo, and UDP jitter operations require the NQA server. The NQA operations for services that are already provided by the destination device such as FTP do not need the NQA server.

You can configure the NQA server to listen and respond to specific IP addresses and ports to meet various test needs.

Figure 1 Network diagram

NQA operation

The following describes how NQA performs different types of operations:

· A TCP operation sets up a connection.

· An ICMP jitter or UDP jitter operation sends a number of probe packets. The number of probe packets is set by using the probe packet-number command.

· An FTP operation uploads or downloads a file.

· An HTTP operation gets a Web page.

· An ICMP echo operation sends an ICMP echo request.

· A UDP echo operation sends a UDP packet.

· An SNMP operation sends one SNMPv1 packet, one SNMPv2c packet, and one SNMPv3 packet.

Collaboration

NQA can collaborate with the Track module to notify application modules of state or performance changes so that the application modules can take predefined actions.

Figure 2 Collaboration

The following describes how a static route destined for 192.168.0.88 is monitored through collaboration:

1. NQA monitors the reachability to 192.168.0.88.

2. When 192.168.0.88 becomes unreachable, NQA notifies the Track module of the change.

3. The Track module notifies the static routing module of the state change.

4. The static routing module sets the static route to invalid according to a predefined action.

For more information about collaboration, see High Availability Configuration Guide.

Threshold monitoring

Threshold monitoring enables the NQA client to take a predefined action when the NQA operation performance metrics violate the specified thresholds.

Table 1 describes the relationships between performance metrics and NQA operation types.

Table 1 Performance metrics and NQA operation types

Performance metric	NQA operation types that can gather the metric
Probe duration	ICMP echo, FTP, HTTP, SNMP, TCP, UDP echo
Number of probe failures	ICMP echo, FTP, HTTP, SNMP, TCP, UDP echo
Round-trip time	ICMP jitter and UDP jitter
Number of discarded packets	ICMP jitter and UDP jitter
One-way jitter (source-to-destination or destination-to-source)	ICMP jitter and UDP jitter
One-way delay (source-to-destination or destination-to-source)	ICMP jitter and UDP jitter

NQA configuration task list

Tasks at a glance	Remarks
Configuring the NQA server	Required for TCP, UDP echo, and UDP jitter operations.
(Required.) Enabling the NQA client	N/A
(Required.) Perform at least one of the following tasks: · Configuring NQA operations on the NQA client · Configuring NQA templates on the NQA client	When you configure an NQA template to analyze network performance, the feature that uses the template performs the NQA operation.

Configuring the NQA server

To perform TCP, UDP echo, and UDP jitter operations, you must enable the NQA server on the destination device. The NQA server listens and responds to requests on the specified IP addresses and ports.

You can configure multiple TCP or UDP listening services on an NQA server, where each corresponds to a specific IP address and port number. The IP address and port number for a listening service must be unique on the NQA server and match the configuration on the NQA client.

To configure the NQA server:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable the NQA server.	nqa server enable	By default, the NQA server is disabled.
3. Configure a TCP or UDP listening service.	· TCP listening service: nqa server tcp-connect ip-address port-number [ tos tos ] · UDP listening service: nqa server udp-echo ip-address port-number [ tos tos ]	You can set the ToS value in the IP header of reply packets sent by the NQA server. The default ToS value is 0.

Enabling the NQA client

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable the NQA client.	nqa agent enable	By default, the NQA client is enabled. The NQA client configuration takes effect after you enable the NQA client.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Enable the NQA client.

nqa agent enable

By default, the NQA client is enabled.

The NQA client configuration takes effect after you enable the NQA client.

Configuring NQA operations on the NQA client

NQA operation configuration task list

Tasks at a glance
(Required.) Perform at least one of the following tasks: · Configuring the ICMP echo operation · Configuring the ICMP jitter operation · Configuring the FTP operation · Configuring the HTTP operation · Configuring the UDP jitter operation · Configuring the SNMP operation · Configuring the TCP operation · Configuring the UDP echo operation
(Optional.) Configuring optional parameters for the NQA operation
(Optional.) Configuring the collaboration feature
(Optional.) Configuring threshold monitoring
(Optional.) Configuring the NQA statistics collection feature
(Optional.) Configuring the saving of NQA history records
(Required.) Scheduling the NQA operation on the NQA client

Configuring the ICMP echo operation

The ICMP echo operation measures the reachability of a destination device. It has the same function as the ping command, but provides more output information. In addition, if multiple paths exist between the source and destination devices, you can specify the next hop for the ICMP echo operation.

The ICMP echo operation is not supported in IPv6 networks. To test the reachability of an IPv6 address, use the ping ipv6 command. For more information about the command, see Network Management and Monitoring Command Reference.

To configure the ICMP echo operation:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA operation and enter NQA operation view.	nqa entry admin-name operation-tag	By default, no NQA operations exist.
3. Specify the ICMP echo type and enter its view.	type icmp-echo	N/A
4. Specify the destination IP address for ICMP echo requests.	· IPv4 address: destination ip ip-address · IPv6 address: destination ipv6 ipv6-address	By default, no destination IP address is specified.
5. (Optional.) Set the payload size for each ICMP echo request.	data-size size	The default setting is 100 bytes.
6. (Optional.) Specify the payload fill string for ICMP echo requests.	data-fill string	The default payload fill string is the hexadecimal number 00010203040506070809.
7. (Optional.) Specify the output interface for ICMP echo requests.	out interface interface-type interface-number	By default, the output interface for ICMP echo requests is not specified. The NQA client determines the output interface based on the routing table lookup.
8. (Optional.) Specify the source IP address for ICMP echo requests.	· Use the IP address of the specified interface as the source IP address: source interface interface-type interface-number · Specify the source IPv4 address: source ip ip-address · Specify the source IPv6 address: source ipv6 ipv6-address	By default, no source IP address is specified. The requests take the primary IP address of the output interface as their source IP address. If you execute the source interface, source ip, and source ipv6 commands, the most recent configuration takes effect. The specified source interface must be up. The specified source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no probe packets can be sent out.
9. (Optional.) Specify the next hop IP address for ICMP echo requests.	· IPv4 address: next-hop ip ip-address · IPv6 address: next-hop ipv6 ipv6-address	By default, no next hop IP address is configured.

Configuring the ICMP jitter operation

The ICMP jitter operation measures unidirectional and bidirectional jitters. The operation result helps you to determine whether the network can carry jitter-sensitive services such as real-time voice and video services.

The ICMP jitter operation works as follows:

1. The NQA client sends ICMP packets to the destination device.

2. The destination device time stamps each packet it receives, and then sends the packet back to the NQA client.

3. Upon receiving the responses, the NQA client calculates the jitter according to the timestamps.

The display nqa history command does not display the results or statistics of the ICMP jitter operation. To view the results or statistics of the operation, use the display nqa result or display nqa statistics command.

To configure the ICMP jitter operation:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA operation and enter NQA operation view.	nqa entry admin-name operation-tag	By default, no NQA operations exist.
3. Specify the ICMP jitter type and enter its view.	type icmp-jitter	N/A
4. Specify the destination address for ICMP packets.	destination ip ip-address	By default, no destination IP address is specified. The destination IP address must be the same as the IP address of the listening service on the NQA server.
5. (Optional.) Specify the source IP address for ICMP packets.	source ip ip-address	By default, the source IP address of ICMP packets is the primary IP address of their output interface. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no ICMP packets can be sent out.
6. (Optional.) Set the number of ICMP packets sent per probe.	probe packet-number packet-number	The default setting is 10.
7. (Optional.) Set the interval for sending ICMP packets.	probe packet-interval interval	The default setting is 20 milliseconds.
8. (Optional.) Specify how long the NQA client waits for a response from the server before it regards the response times out.	probe packet-timeout timeout	The default setting is 3000 milliseconds.

Configuring the FTP operation

The FTP operation measures the time for the NQA client to transfer a file to or download a file from an FTP server.

When you configure the FTP operation, follow these restrictions and guidelines:

· When you perform the put operation with the filename command configured, make sure the file exists on the NQA client.

· If you get a file from the FTP server, make sure the file specified in the URL exists on the FTP server.

· The NQA client does not save the file obtained from the FTP server.

· Use a small file for the FTP operation. A big file might result in transfer failure because of timeout, or might affect other services because of the amount of network bandwidth it occupies.

To configure the FTP operation:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA operation and enter NQA operation view.	nqa entry admin-name operation-tag	By default, no NQA operations exist.
3. Specify the FTP type and enter its view.	type ftp	N/A
4. Specify the URL of the destination FTP server.	url url	By default, no URL is specified for the destination FTP server. Enter the URL in one of the following formats: · ftp://host/filename. · ftp://host:port/filename. When you perform the get operation, the file name is required.
5. (Optional.) Specify the source IP address of FTP request packets.	source ip ip-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no FTP requests can be sent out.
6. (Optional.) Specify the FTP operation type.	operation { get \| put }	By default, the FTP operation type is get, which means obtaining files from the FTP server.
7. Specify an FTP login username.	username username	By default, no FTP login username is configured.
8. Specify an FTP login password.	password { cipher \| simple } password	By default, no FTP login password is configured.
9. (Optional.) Specify the name of a file to be transferred.	filename file-name	By default, no file is specified. This step is required if you perform the put operation.
10. Set the data transmission mode.	mode { active \| passive }	The default mode is active.

Configuring the HTTP operation

An HTTP operation measures the time for the NQA client to obtain data from an HTTP server.

To configure an HTTP operation:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA operation and enter NQA operation view.	nqa entry admin-name operation-tag	By default, no NQA operations exist.
3. Specify the HTTP type and enter its view.	type http	N/A
4. Specify the URL of the destination HTTP server.	url url	By default, no URL is specified for the destination HTTP server. Enter the URL in one of the following formats: · http://host/resource. · http://host:port/resource.
5. Specify an HTTP login username.	username username	By default, no HTTP login username is specified.
6. Specify an HTTP login password.	password { cipher \| simple } password	By default, no HTTP login password is specified.
7. (Optional.) Specify the source IP address of request packets.	source ip ip-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no request packets can be sent out.
8. (Optional.) Specify the HTTP operation type.	operation { get \| post \| raw }	By default, the HTTP operation type is get, which means obtaining data from the HTTP server. If you set the HTTP operation type to raw, configure the content of the HTTP request to be sent to the HTTP server in raw request view.
9. Specify the HTTP version.	version { v1.0 \| v1.1 }	By default, HTTP 1.0 is used.
10. (Optional.) Enter raw request view.	raw-request	Every time you enter raw request view, the previously configured content of the HTTP request is removed.
11. (Optional.) Specify the HTTP request content.	Enter or paste the content.	By default, no contents are specified. This step is required for the raw operation.
12. Save the input and exit to HTTP operation view.	quit	N/A

Configuring the UDP jitter operation

CAUTION:

To ensure successful UDP jitter operations and avoid affecting existing services, do not perform the operations on well-known ports from 1 to 1023.

Jitter means inter-packet delay variance. A UDP jitter operation measures unidirectional and bidirectional jitters. You can verify whether the network can carry jitter-sensitive services such as real-time voice and video services through the UDP jitter operation.

The UDP jitter operation works as follows:

1. The NQA client sends UDP packets to the destination port.

2. The destination device takes a time stamp to each packet that it receives, and then sends the packet back to the NQA client.

3. Upon receiving the responses, the NQA client calculates the jitter according to the time stamps.

The UDP jitter operation requires both the NQA server and the NQA client. Before you perform the UDP jitter operation, configure the UDP listening service on the NQA server. For more information about UDP listening service configuration, see "Configuring the NQA server."

To configure a UDP jitter operation:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA operation and enter NQA operation view.	nqa entry admin-name operation-tag	By default, no NQA operations exist.
3. Specify the UDP jitter type and enter its view.	type udp-jitter	N/A
4. Specify the destination address of UDP packets.	destination ip ip-address	By default, no destination IP address is specified. The destination IP address must be the same as the IP address of the listening service on the NQA server.
5. Specify the destination port of UDP packets.	destination port port-number	By default, no destination port number is specified. The destination port number must be the same as the port number of the listening service on the NQA server.
6. (Optional.) Specify the source port number of UDP packets.	source port port-number	By default, no source port number is specified.
7. (Optional.) Set the payload size for each UDP packet.	data-size size	The default setting is 100 bytes.
8. (Optional.) Specify the payload fill string for UDP packets.	data-fill string	The default payload fill string is the hexadecimal number 00010203040506070809.
9. (Optional.) Set the number of UDP packets sent in one UDP jitter operation.	probe packet-number packet-number	The default setting is 10.
10. (Optional.) Set the interval for sending UDP packets.	probe packet-interval packet-interval	The default setting is 20 milliseconds.
11. (Optional.) Specify how long the NQA client waits for a response from the server before it regards the response times out.	probe packet-timeout packet-timeout	The default setting is 3000 milliseconds.
12. (Optional.) Specify the source IP address for UDP packets.	source ip ip-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no UDP packets can be sent out.
13. (Optional.) Specify the source port for UDP packets.	source port port-number	By default, no source port is specified.

NOTE:

Use the display nqa result or display nqa statistics command to verify the UDP jitter operation. The display nqa history command does not display the UDP jitter operation results or statistics.

Configuring the SNMP operation

The SNMP operation measures the time for the NQA client to get a response packet from an SNMP agent.

To configure the SNMP operation:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA operation and enter NQA operation view.	nqa entry admin-name operation-tag	By default, no NQA operations exist.
3. Specify the SNMP type and enter its view.	type snmp	N/A
4. Specify the destination address of SNMP packets.	destination ip ip-address	By default, no destination IP address is specified.
5. (Optional.) Specify the source port of SNMP packets.	source port port-number	By default, no source port number is specified.
6. (Optional.) Specify the source IP address of SNMP packets.	source ip ip-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no SNMP packets can be sent out.

Configuring the TCP operation

The TCP operation measures the time for the NQA client to establish a TCP connection to a port on the NQA server.

The TCP operation requires both the NQA server and the NQA client. Before you perform a TCP operation, configure a TCP listening service on the NQA server. For more information about the TCP listening service configuration, see "Configuring the NQA server."

To configure the TCP operation:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA operation and enter NQA operation view.	nqa entry admin-name operation-tag	By default, no NQA operations exist.
3. Specify the TCP type and enter its view.	type tcp	N/A
4. Specify the destination address of TCP packets.	destination ip ip-address	By default, no destination IP address is specified. The destination address must be the same as the IP address of the listening service configured on the NQA server.
5. Specify the destination port of TCP packets.	destination port port-number	By default, no destination port number is configured. The destination port number must be the same as the port number of the listening service on the NQA server.
6. (Optional.) Specify the source IP address of TCP packets.	source ip ip-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no TCP packets can be sent out.

Configuring the UDP echo operation

The UDP echo operation measures the round-trip time between the client and a UDP port on the NQA server.

The UDP echo operation requires both the NQA server and the NQA client. Before you perform a UDP echo operation, configure a UDP listening service on the NQA server. For more information about the UDP listening service configuration, see "Configuring the NQA server."

To configure the UDP echo operation:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA operation and enter NQA operation view.	nqa entry admin-name operation-tag	By default, no NQA operations exist.
3. Specify the UDP echo type and enter its view.	type udp-echo	N/A
4. Specify the destination address of UDP packets.	destination ip ip-address	By default, no destination IP address is specified. The destination address must be the same as the IP address of the listening service configured on the NQA server.
5. Specify the destination port of UDP packets.	destination port port-number	By default, no destination port number is specified. The destination port number must be the same as the port number of the listening service on the NQA server.
6. (Optional.) Set the payload size for each UDP packet.	data-size size	The default setting is 100 bytes.
7. (Optional.) Specify the payload fill string for UDP packets.	data-fill string	The default payload fill string is the hexadecimal number 00010203040506070809.
8. (Optional.) Specify the source port of UDP packets.	source port port-number	By default, no source port number is specified.
9. (Optional.) Specify the source IP address of UDP packets.	source ip ip-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no UDP packets can be sent out.

Configuring optional parameters for the NQA operation

Unless otherwise specified, the following optional parameters apply to all types of NQA operations.

The parameter settings take effect only on the current operation.

To configure optional parameters for an NQA operation:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA operation and enter NQA operation view.	nqa entry admin-name operation-tag	By default, no NQA operations exist.
3. Specify an NQA operation type and enter its view.	type { ftp \| http \| icmp-echo \| icmp-jitter \| snmp \| tcp \| udp-echo \| udp-jitter }	N/A
4. Configure a description.	description text	By default, no description is configured.
5. Set the interval at which the NQA operation repeats.	frequency interval	The default setting is 0 milliseconds. Only one operation is performed. If the operation is not completed when the interval expires, the next operation does not start.
6. Specify the probe times.	probe count times	By default, the NQA client performs one probe to the destination per operation.
7. Set the probe timeout time.	probe timeout timeout	The default setting is 3000 milliseconds. This command is not available for ICMP jitter or UDP jitter operations.
8. Set the maximum number of hops that the probe packets can traverse.	ttl value	The default setting is 20.
9. Set the ToS value in the IP header of probe packets.	tos value	The default setting is 0.
10. Enable the routing table bypass feature.	route-option bypass-route	By default, the routing table bypass feature is disabled.

Configuring the collaboration feature

Collaboration is implemented by associating a reaction entry of an NQA operation with a track entry. The reaction entry monitors the NQA operation. If the number of operation failures reaches the specified threshold, the configured action is triggered.

To configure the collaboration feature:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA operation and enter NQA operation view.	nqa entry admin-name operation-tag	By default, no NQA operations exist.
3. Specify an NQA operation type and enter its view.	type { ftp \| http \| icmp-echo \| snmp \| tcp \| udp-echo }	The collaboration feature is not available for ICMP jitter or UDP jitter operations.
4. Configure a reaction entry.	reaction item-number checked-element probe-fail threshold-type consecutive consecutive-occurrences action-type trigger-only	By default, no reaction entry is configured.
5. Exit to system view.	quit	N/A
6. Associate Track with NQA.	See High Availability Configuration Guide.	N/A
7. Associate Track with an application module.	See High Availability Configuration Guide.	N/A

Configuring threshold monitoring

This feature allows you to monitor the NQA operation running status.

Threshold types

An NQA operation supports the following threshold types:

· average—If the average value for the monitored performance metric either exceeds the upper threshold or goes below the lower threshold, a threshold violation occurs.

· accumulate—If the total number of times that the monitored performance metric is out of the specified value range reaches or exceeds the specified threshold, a threshold violation occurs.

· consecutive—If the number of consecutive times that the monitored performance metric is out of the specified value range reaches or exceeds the specified threshold, a threshold violation occurs.

Threshold violations for the average or accumulate threshold type are determined on a per NQA operation basis. The threshold violations for the consecutive type are determined from the time the NQA operation starts.

Triggered actions

The following actions might be triggered:

· none—NQA displays results only on the terminal screen. It does not send traps to the NMS.

· trap-only—NQA displays results on the terminal screen, and meanwhile it sends traps to the NMS.

· trigger-only—NQA displays results on the terminal screen, and meanwhile triggers other modules for collaboration.

Reaction entry

In a reaction entry, configure a monitored element, a threshold type, and an action to be triggered to implement threshold monitoring.

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

· Before an NQA operation starts, the reaction entry is in invalid state.

· If the threshold is violated, the state of the entry is set to over-threshold. Otherwise, the state of the entry is set to below-threshold.

If the action is trap-only for a reaction entry, a trap message is sent to the NMS when the state of the entry changes.

Configuration procedure

Before you configure threshold monitoring, configure the destination address of the trap messages by using the snmp-agent target-host command. For more information about the command, see Network Management and Monitoring Command Reference.

To configure threshold monitoring:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA operation and enter NQA operation view.	nqa entry admin-name operation-tag	By default, no NQA operations exist.
3. Enter NQA operation view.	type { ftp \| http \| icmp-echo \| icmp-jitter \| snmp \| tcp \| udp-echo \| udp-jitter }	N/A
4. Enable sending traps to the NMS when specific conditions are met.	reaction trap { probe-failure consecutive-probe-failures \| test-complete \| test-failure [ cumulate-probe-failures ] }	By default, no traps are sent to the NMS. The ICMP jitter and UDP jitter operations support only the test-complete keyword.
5. Configure threshold monitoring.	· Monitor the operation duration (not supported in the ICMP jitter, UDP jitter, or UDP tracert operations): 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 } ] · Monitor failure times (not supported in the ICMP jitter, UDP jitter, or UDP tracert operations): reaction item-number checked-element probe-fail threshold-type { accumulate accumulate-occurrences \| consecutive consecutive-occurrences } [ action-type { none \| trap-only } ] · Monitor the round-trip time (only for the ICMP jitter and UDP jitter operations): reaction item-number checked-element rtt threshold-type { accumulate accumulate-occurrences \| average } threshold-value upper-threshold lower-threshold [ action-type { none \| trap-only } ] · Monitor packet loss (only for the ICMP jitter and UDP jitter operations): reaction item-number checked-element packet-loss threshold-type accumulate accumulate-occurrences [ action-type { none \| trap-only } ] · Monitor the one-way jitter (only for the ICMP jitter and UDP jitter operations): 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 } ] · Monitor the one-way delay (only for the ICMP jitter and UDP jitter operations): reaction item-number checked-element { owd-ds \| owd-sd } threshold-value upper-threshold lower-threshold	N/A

Configuring the NQA statistics collection feature

NQA forms statistics within the same collection interval as a statistics group. To display information about the statistics groups, use the display nqa statistics command.

NQA does not generate any statistics group for the operation that runs once. To set the NQA operation to run only once, use the frequency command to set the interval to 0 milliseconds.

To configure the NQA statistics collection feature:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA operation and enter NQA operation view.	nqa entry admin-name operation-tag	By default, no NQA operations exist.
3. Specify an NQA operation type and enter its view.	type { ftp \| http \| icmp-echo \| icmp-jitter \| snmp \| tcp \| udp-echo \| udp-jitter }	The UDP tracert and path quality analysis operations do not support the NQA statistics collection feature.
4. (Optional.) Set the interval for collecting the statistics.	statistics interval interval	The default setting is 60 minutes.
5. (Optional.) Set the maximum number of statistics groups that can be saved.	statistics max-group number	The default setting is two groups. To disable NQA statistics collection, set the maximum number to 0. When the maximum number of statistics groups is reached, to save a new statistics group, the oldest statistics group is deleted.
6. (Optional.) Set the hold time of statistics groups.	statistics hold-time hold-time	The default setting is 120 minutes. A statistics group is deleted when its hold time expires.

Configuring the saving of NQA history records

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA operation and enter NQA operation view.	nqa entry admin-name operation-tag	By default, no NQA operations exist.
3. Enter NQA operation type view.	type { ftp \| http \| icmp-echo \| snmp \| tcp \| udp-echo }	The ICMP jitter and UDP jitter operations do not support saving history records.
4. Enable the saving of history records for the NQA operation.	history-record enable	By default, this feature is disabled.
5. (Optional.) Set the lifetime of history records.	history-record keep-time keep-time	The default setting is 120 minutes. A record is deleted when its lifetime is reached.
6. (Optional.) Set the maximum number of history records that can be saved.	history-record number number	The default setting is 50. If the maximum number of history records for an NQA operation is reached, the earliest history records are deleted.
7. (Optional.) Display NQA history records.	display nqa history	N/A

Scheduling the NQA operation on the NQA client

The NQA operation works between the specified start time and the end time (the start time plus operation duration). If the specified start time is ahead of the system time, the operation starts immediately. If both the specified start and end time are ahead of the system time, the operation does not start. To display the current system time, use the display clock command.

When you schedule an NQA operation, follow these restrictions and guidelines:

· You cannot enter the operation type view or the operation view of a scheduled NQA operation.

· A system time adjustment does not affect started or completed NQA operations. It affects only the NQA operations that have not started.

To schedule the NQA operation on the NQA client:

Step	Command
1. Enter system view.	system-view
2. Specify the scheduling parameters for an NQA operation.	nqa schedule admin-name operation-tag start-time { hh:mm:ss [ yyyy/mm/dd \| mm/dd/yyyy ] \| now } lifetime { lifetime \| forever } [ recurring ]

Configuring NQA templates on the NQA client

An NQA template is a set of operation parameters, such as the destination address, the destination port number, and the destination server URL. You can use an NQA template in load balancing, health monitoring, and other feature modules to provide statistics. You can create multiple templates on a device, and each template must be uniquely named.

NQA template supports the FTP, HTTP, HTTPS, ICMP, RADIUS, SSL, TCP, TCP half open, and UDP operation types.

Some operation parameters for an NQA template can be specified by the template configuration or the feature that uses the template. When both are specified, the parameters in the template configuration take effect. For example, the server load balancing uses the NQA ICMP template for health monitoring. If the destination IP address in the template is different from the real server address, the destination IP address in the template takes effect.

NQA template configuration task list

Tasks at a glance
(Required.) Perform at least one of the following tasks: · Configuring the ICMP template · Configuring the TCP template · Configuring the TCP half open template · Configuring the UDP template · Configuring the HTTP template · Configuring the HTTPS template · Configuring the FTP template · Configuring the RADIUS template · Configuring the SSL template
(Optional.) Configuring optional parameters for the NQA template

Tasks at a glance

(Required.) Perform at least one of the following tasks:

· Configuring the ICMP template

· Configuring the TCP template

· Configuring the TCP half open template

· Configuring the UDP template

· Configuring the HTTP template

· Configuring the HTTPS template

· Configuring the FTP template

· Configuring the RADIUS template

· Configuring the SSL template

(Optional.) Configuring optional parameters for the NQA template

Configuring the ICMP template

A feature that uses the ICMP template performs the ICMP operation to measure the reachability of a destination device. The ICMP template is supported in both IPv4 and IPv6 networks.

To configure the ICMP template:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an ICMP template and enter its view.	nqa template icmp name	By default, no ICMP templates exist.
3. (Optional.) Specify the destination IP address of the operation.	· IPv4 address: destination ip ip-address · IPv6 address: destination ipv6 ipv6-address	By default, no destination IP address is configured.
4. (Optional.) Set the payload size for each ICMP request.	data-size size	The default setting is 100 bytes.
5. (Optional.) Specify the payload fill string for requests.	data-fill string	The default payload fill string is the hexadecimal number 00010203040506070809.
6. (Optional.) Specify the source IP address for ICMP echo requests.	· Use the IP address of the specified interface as the source IP address: source interface interface-type interface-number · Specify the source IPv4 address: source ip ip-address · Specify the source IPv6 address: source ipv6 ipv6-address	By default, no source IP address is specified. The requests use the primary IP address of the output interface as their source IP address. If you execute the source interface, source ip, and source ipv6 commands, the most recent configuration takes effect. The specified source interface must be up. The specified source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no probe packets can be sent out.
7. (Optional.) Specify the next hop IP address for ICMP echo requests.	· IPv4 address: next-hop ip ip-address · IPv6 address: next-hop ipv6 ipv6-address	By default, no IP address of the next hop is configured.
8. (Optional.) Configure the probe result sending on a per-probe basis.	reaction trigger per-probe	By default, the probe result is sent to the feature that uses the template after three consecutive failed or successful probes. If you execute the reaction trigger per-probe command and the reaction trigger probe-pass or reaction trigger probe-fail command, the most recent configuration takes effect.

Configuring the TCP template

A feature that uses the TCP template performs the TCP operation to test whether the NQA client can establish a TCP connection to a specific port on the server.

In TCP template view, you can specify the expected data to be returned. If you do not specify the expected data, the TCP operation tests only whether the client can establish a TCP connection to the server.

To configure the TCP template:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a TCP template and enter its view.	nqa template tcp name	By default, no TCP templates exist.
3. (Optional.) Specify the destination IP address of the operation.	· IPv4 address: destination ip ip-address · IPv6 address: destination ipv6 ipv6-address	By default, no destination address is specified. The destination address must be the same as the IP address of the listening service configured on the NQA server.
4. (Optional.) Specify the destination port number for the operation.	destination port port-number	By default, no destination port number is specified. The destination port number must be the same as the port number of the listening service on the NQA server.
5. (Optional.) Specify the payload fill string for requests.	data-fill string	The default payload fill string is the hexadecimal number 00010203040506070809.
6. (Optional.) Specify the source IP address for the probe packets.	· IPv4 address: source ip ip-address · IPv6 address: source ipv6 ipv6-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no probe packets can be sent out.
7. (Optional.) Configure the expected data.	expect data expression [ offset number ]	By default, no expected data is configured. The NQA client performs expect data check only when you configure both the data-fill and expect-data commands.

Configuring the TCP half open template

A feature that uses the TCP half open template performs the TCP half open operation to test whether the TCP service is available on the server. The TCP half open operation is used when the feature cannot get a response from the TCP server through an existing TCP connection.

In the TCP half open operation, the NQA client sends a TCP ACK packet to the server. If the client receives an RST packet, it considers that the TCP service is available on the server.

To configure the TCP half open template:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a TCP half open template and enter its view.	nqa template tcphalfopen name	By default, no TCP half open templates exist.
3. (Optional.) Specify the destination IP address of the operation.	· IPv4 address: destination ip ip-address · IPv6 address: destination ipv6 ipv6-address	By default, no destination address is specified.
4. (Optional.) Specify the source IP address for the probe packets.	· IPv4 address: source ip ip-address · IPv6 address: source ipv6 ipv6-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no probe packets can be sent out.
5. (Optional.) Specify the next hop IP address for the probe packets.	· IPv4 address: next-hop ip ip-address · IPv6 address: next-hop ipv6 ipv6-address	By default, the IP address of the next hop is configured.
6. (Optional.) Configure the probe result sending on a per-probe basis.	reaction trigger per-probe	By default, the probe result is sent to the feature that uses the template after three consecutive failed or successful probes. If you execute the reaction trigger per-probe command and the reaction trigger probe-pass or reaction trigger probe-fail command, the most recent configuration takes effect.

Configuring the UDP template

A feature that uses the UDP template performs the UDP operation to test the following items:

· Reachability of a specific port on the NQA server.

· Availability of the requested service on the NQA server.

In UDP template view, you can specify the expected data to be returned. If you do not specify the expected data, the UDP operation tests only whether the client can receive the response packet from the server.

The UDP operation requires both the NQA server and the NQA client. Before you perform a UDP operation, configure a UDP listening service on the NQA server. For more information about the UDP listening service configuration, see "Configuring the NQA server."

To configure the UDP template:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a UDP template and enter its view.	nqa template udp name	By default, no UDP templates exist.
3. (Optional.) Specify the destination IP address of the operation.	· IPv4 address: destination ip ip-address · IPv6 address: destination ipv6 ipv6-address	By default, no destination address is specified. The destination address must be the same as the IP address of the listening service configured on the NQA server.
4. (Optional.) Specify the destination port number for the operation.	destination port port-number	By default, no destination port number is specified. The destination port number must be the same as the port number of the listening service on the NQA server.
5. (Optional.) Specify the payload fill string for the probe packets.	data-fill string	The default payload fill string is the hexadecimal number 00010203040506070809.
6. (Optional.) Set the payload size for the probe packets.	data-size size	The default setting is 100 bytes.
7. (Optional.) Specify the source IP address for the probe packets.	· IPv4 address: source ip ip-address · IPv6 address: source ipv6 ipv6-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no probe packets can be sent out.
8. (Optional.) Configure the expected data.	expect data expression [ offset number ]	By default, no expected data is configured. If you want to configure this command, make sure the data-fill command is already executed.

Configuring the HTTP template

A feature that uses the HTTP template performs the HTTP operation to measure the time it takes the NQA client to obtain data from an HTTP server.

The expected data is checked only when the expected data is configured and the HTTP response contains the Content-Length field in the HTTP header.

The status code of the HTTP packet is a three-digit field in decimal notation, and it includes the status information for the HTTP server. The first digit defines the class of response.

Configure the HTTP server before you perform the HTTP operation.

To configure the HTTP template:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an HTTP template and enter its view.	nqa template http name	By default, no HTTP templates exist.
3. Specify the URL of the destination HTTP server.	url url	By default, no URL is specified for the destination HTTP server. Enter the URL in one of the following formats: · http://host/resource. · http://host:port/resource.
4. Specify an HTTP login username.	username username	By default, no HTTP login username is specified.
5. Specify an HTTP login password.	password { cipher \| simple } password	By default, no HTTP login password is specified.
6. (Optional.) Specify the HTTP version.	version { v1.0 \| v1.1 }	By default, HTTP 1.0 is used.
7. (Optional.) Specify the HTTP operation type.	operation { get \| post \| raw }	By default, the HTTP operation type is get, which means obtaining data from the HTTP server. If you set the HTTP operation type to raw, use the raw-request command to specify the content of the HTTP request to be sent to the HTTP server.
8. (Optional.) Enter raw request view.	raw-request	This step is required for the raw operation. Every time you enter the raw request view, the previously configured request content is removed.
9. (Optional.) Enter or paste the content of the HTTP request for the HTTP operation.	N/A	This step is required for the raw operation. By default, the HTTP request content is not specified.
10. (Optional.) Exit to HTTP template view.	quit	The system automatically saves the configuration in raw request view before it exits to HTTP template view.
11. (Optional.) Specify the source IP address for the probe packets.	· IPv4 address: source ip ip-address · IPv6 address: source ipv6 ipv6-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no probe packets can be sent out.
12. (Optional.) Configure the expected status codes.	expect status status-list	By default, no expected status code is configured.
13. (Optional.) Configure the expected data.	expect data expression [ offset number ]	By default, no expected data is configured.

Configuring the HTTPS template

A feature that uses the HTTPS template performs the HTTPS operation to measure the time it takes for the NQA client to obtain data from an HTTPS server.

The expected data is checked only when the expected data is configured and the HTTPS response contains the Content-Length field in the HTTPS header.

The status code of the HTTPS packet is a three-digit field in decimal notation, and it includes the status information for the HTTPS server. The first digit defines the class of response.

Before you perform the HTTPS operation, configure the HTTPS server and the SSL client policy for the SSL client. For information about configuring SSL client policies, see Security Configuration Guide.

To configure the HTTPS template:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an HTTPS template and enter its view.	nqa template https name	By default, no HTTPS templates exist.
3. Specify the URL of the destination HTTPS server.	url url	By default, no URL is specified for the destination HTTPS server. Enter the URL in one of the following formats: · https://host/resource. · https://host:port/resource.
4. Specify an HTTPS login username.	username username	By default, no HTTPS login username is specified.
5. Specify an HTTPS login password.	password { cipher \| simple } password	By default, no HTTPS login password is specified.
6. Specify an SSL client policy.	ssl-client-policy policy-name	By default, no SSL client policy is specified.
7. (Optional.) Specify the HTTPS version.	version { v1.0 \| v1.1 }	By default, HTTPS 1.0 is used.
8. (Optional.) Specify the HTTPS operation type.	operation { get \| post \| raw }	By default, the HTTPS operation type is get, which means obtaining data from the HTTPS server. If you set the HTTPS operation type to raw, use the raw-request command to configure the content of the request to be sent to the HTTPS server.
9. (Optional.) Enter raw request view.	raw-request	This step is required for the raw operation. Every time you enter the raw request view, the previously configured request content is removed.
10. (Optional.) Enter or paste the content of the HTTPS request for the HTTPS operation.	N/A	This step is required for the raw operation. By default, the HTTPS request content is not specified.
11. (Optional.) Exit to HTTPS template view.	quit	The system automatically saves the configuration in raw request view before it exits to HTTPS template view.
12. (Optional.) Specify the source IP address for the probe packets.	· IPv4 address: source ip ip-address · IPv6 address: source ipv6 ipv6-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no probe packets can be sent out.
13. (Optional.) Configure the expected data.	expect data expression [ offset number ]	By default, no expected data is configured.
14. (Optional.) Configure the expected status codes.	expect status status-list	By default, no expected status code is configured.

Configuring the FTP template

A feature that uses the FTP template performs the FTP operation. The operation measures the time it takes the NQA client to transfer a file to or download a file from an FTP server.

Configure the username and password for the FTP client to log in to the FTP server before you perform an FTP operation. For information about configuring the FTP server, see Fundamentals Configuration Guide.

To configure the FTP template:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an FTP template and enter its view.	nqa template ftp name	By default, no FTP templates exist.
3. Specify the URL of the destination FTP server.	url url	By default, no URL is specified for the destination FTP server. Enter the URL in one of the following formats: · ftp://host/filename. · ftp://host:port/filename. When you perform the get operation, the file name is required. When you perform the put operation, the filename argument does not take effect, even if it is specified. The file name for the put operation is determined by the filename command.
4. (Optional.) Specify the FTP operation type.	operation { get \| put }	By default, the FTP operation type is get, which means obtaining files from the FTP server.
5. Specify an FTP login username.	username username	By default, no FTP login username is specified.
6. Specify an FTP login password.	password { cipher \| simple } password	By default, no FTP login password is specified.
7. (Optional.) Specify the name of a file to be transferred.	filename filename	This step is required if you perform the put operation. This configuration does not take effect for the get operation. By default, no file is specified.
8. Set the data transmission mode.	mode { active \| passive }	The default mode is active.
9. (Optional.) Specify the source IP address for the probe packets.	· IPv4 address: source ip ip-address · IPv6 address: source ipv6 ipv6-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no probe packets can be sent out.

Configuring the RADIUS template

A feature that uses the RADIUS template performs the RADIUS operation to check the availability of the authentication service on the RADIUS server.

The RADIUS operation authentication workflow is as follows:

1. The NQA client sends an authentication request (Access-Request) to the RADIUS server. The request includes the username and the user's password. The password has been encrypted by the MD5 algorithm and the shared key.

2. The RADIUS server authenticates the username and password.

¡ If the authentication succeeds, the server sends an Access-Accept packet to the NQA client.

¡ If the authentication fails, the server sends an Access-Reject packet to the NQA client.

If the NQA client can receive the Access-Accept or Access-Reject packet from the RADIUS server, the authentication service is available on the RADIUS server. Otherwise, the authentication service is not available on the RADIUS server.

Before you configure the RADIUS template, specify a username, password, and shared key on the RADIUS server. For more information about configuring the RADIUS server, see Security Configuration Guide.

To configure the RADIUS template:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a RADIUS template and enter its view.	nqa template radius name	By default, no RADIUS templates exist.
3. (Optional.) Specify the destination IP address of the operation.	· IPv4 address: destination ip ip-address · IPv6 address: destination ipv6 ipv6-address	By default, no destination IP address is configured.
4. (Optional.) Specify the destination port number for the operation.	destination port port-number	By default, the destination port number is 1812.
5. Specify a username.	username username	By default, no username is specified.
6. Specify a password.	password { cipher \| simple } password	By default, no password is specified.
7. Specify a shared key for secure RADIUS authentication.	key { cipher \| simple } string	By default, no shared key is specified for RADIUS authentication.
8. (Optional.) Specify the source IP address for the probe packets.	· IPv4 address: source ip ip-address · IPv6 address: source ipv6 ipv6-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no probe packets can be sent out.

Configuring the SSL template

A feature that uses the SSL template performs the SSL operation to measure the time required to establish an SSL connection to an SSL server.

Before you configure the SSL template, configure the SSL client policy. For information about configuring SSL client policies, see Security Configuration Guide.

To configure the SSL template:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an SSL template and enter its view.	nqa template ssl name	By default, no SSL templates exist.
3. (Optional.) Specify the destination IP address of the operation.	· IPv4 address: destination ip ip-address · IPv6 address: destination ipv6 ipv6-address	By default, no destination IP address is configured.
4. (Optional.) Specify the destination port number for the operation.	destination port port-number	By default, the destination port number is not specified.
5. (Optional.) Specify the source IP address for the probe packets.	· IPv4 address: source ip ip-address · IPv6 address: source ipv6 ipv6-address	By default, no source IP address is specified. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no probe packets can be sent out.
6. Specify an SSL client policy.	ssl-client-policy policy-name	By default, no SSL client policy is specified.

Configuring optional parameters for the NQA template

Unless otherwise specified, the following optional parameters apply to all types of NQA templates.

The parameter settings take effect only on the current NQA template.

To configure optional parameters for an NQA template:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an NQA template and enter its view.	nqa template { ftp \| http \| https \| icmp \| ssl \| tcp \| tcphalfopen \| udp } name	By default, no NQA templates exist.
3. Configure a description.	description text	By default, no description is configured.
4. Set the interval at which the NQA operation repeats.	frequency interval	The default setting is 5000 milliseconds. If the operation is not completed when the interval expires, the next operation does not start.
5. Set the probe timeout time.	probe timeout timeout	The default setting is 3000 milliseconds.
6. Set the TTL for probe packets.	ttl value	The default setting is 20.
7. Set the ToS value in the IP header of probe packets.	tos value	The default setting is 0.
8. Set the number of consecutive successful probes that lead to a successful operation.	reaction trigger probe-pass count	The default setting is 3. If the number of consecutive successful probes for an NQA operation is reached, the NQA client notifies the feature that uses the template of the successful operation event.
9. Set the number of consecutive probe failures that lead to an operation failure.	reaction trigger probe-fail count	The default setting is 3. If the number of consecutive probe failures for an NQA operation is reached, the NQA client notifies the feature that uses the NQA template of the operation failure.

Displaying and maintaining NQA

Execute display commands in any view.

Task	Command
Display history records of NQA operations.	display nqa history [ admin-name operation-tag ]
Display the current monitoring results of reaction entries.	display nqa reaction counters [ admin-name operation-tag [ item-number ] ]
Display the most recent result of the NQA operation.	display nqa result [ admin-name operation-tag ]
Display NQA statistics.	display nqa statistics [ admin-name operation-tag ]
Display NQA server status.	display nqa server status

NQA configuration examples

ICMP echo operation configuration example

Network requirements

As shown in Figure 3, configure an ICMP echo operation from the NQA client on the AC to Device A to test the round-trip time. The next hop of the AC is Device B.

Figure 3 Network diagram

Configuration procedure

# Assign each interface an IP address. (Details not shown.)

# Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

# Create an ICMP echo operation.

<AC> system-view

[AC] nqa entry admin test1

[AC-nqa-admin-test1] type icmp-echo

# Specify 10.2.2.2 as the destination IP address of ICMP echo requests.

[AC-nqa-admin-test1-icmp-echo] destination ip 10.2.2.2

# Specify 10.1.1.2 as the next hop. The ICMP echo requests are sent through Device B to Device A.

[AC-nqa-admin-test1-icmp-echo] next-hop ip 10.1.1.2

# Configure the ICMP echo operation to perform 10 probes.

[AC-nqa-admin-test1-icmp-echo] probe count 10

# Set the probe timeout time to 500 milliseconds for the ICMP echo operation.

[AC-nqa-admin-test1-icmp-echo] probe timeout 500

# Configure the ICMP echo operation to repeat every 5000 milliseconds.

[AC-nqa-admin-test1-icmp-echo] frequency 5000

# Enable saving history records.

[AC-nqa-admin-test1-icmp-echo] history-record enable

# Set the maximum number of history records to 10.

[AC-nqa-admin-test1-icmp-echo] history-record number 10

[AC-nqa-admin-test1-icmp-echo] quit

# Start the ICMP echo operation.

[AC] nqa schedule admin test1 start-time now lifetime forever

# After the ICMP echo operation runs for a period of time, stop the operation.

[AC] undo nqa schedule admin test1

# Display the most recent result of the ICMP echo operation.

[AC] display nqa result admin test1

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

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: 2011-08-23 15:00:01.2

Extended results:

Packet loss ratio: 0%

Failures due to timeout: 0

Failures due to internal error: 0

Failures due to other errors: 0

# Display the history records of the ICMP echo operation.

[AC] display nqa history admin test1

NQA entry (admin admin, tag test) history records:

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

The output shows that the packets sent by the AC can reach Device A through Device B. No packet loss occurs during the operation. The minimum, maximum, and average round-trip times are 2, 5, and 3 milliseconds, respectively.

ICMP jitter operation configuration example

Network requirements

As shown in Figure 4, configure an ICMP jitter operation to test the jitter between the AC and the device.

Figure 4 Network diagram

Configuration procedure

1. Assign IP addresses to interfaces, as shown in Figure 4. (Details not shown.)

2. Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

3. Configure the AC:

# Create an ICMP jitter operation.

<AC> system-view

[AC] nqa entry admin test1

[AC-nqa-admin-test1] type icmp-jitter

# Specify 10.2.2.2 as the destination address for the operation.

[AC-nqa-admin-test1-icmp-jitter] destination ip 10.2.2.2

# Configure the operation to repeat every 1000 milliseconds.

[AC-nqa-admin-test1-icmp-jitter] frequency 1000

[AC-nqa-admin-test1-icmp-jitter] quit

# Start the ICMP jitter operation.

[AC] nqa schedule admin test1 start-time now lifetime forever

# After the ICMP jitter operation runs for a period of time, stop the operation.

[AC] undo nqa schedule admin test1

# Display the most recent result of the ICMP jitter operation.

[AC] display nqa result admin test1

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

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 packet received time: 2011-05-29 13:56:17.6

Extended results:

Packet loss ratio: 0%

Failures due to timeout: 0

Failures due to internal error: 0

Failures due to other errors: 0

Packets out of sequence: 0

Packets arrived late: 0

ICMP-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

Lost packets for unknown reason: 0

# Display the statistics of the ICMP jitter operation.

[AC] display nqa statistics admin test1

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

NO. : 1

Start time: 2015-07-10 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 ratio: 0%

Failures due to timeout: 0

Failures due to internal error: 0

Failures due to other errors: 0

Packets out of sequence: 0

Packets arrived late: 0

ICMP-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

Lost packets for unknown reason: 0

FTP operation configuration example

Network requirements

As shown in Figure 5, configure an FTP operation to test the time required for the AC to upload a file to the FTP server. The login username and password are admin and systemtest, respectively. The file to be transferred to the FTP server is config.txt.

Figure 5 Network diagram

Configuration procedure

# Assign each interface an IP address. (Details not shown.)

# Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

# Create an FTP operation.

<AC> system-view

[AC] nqa entry admin test1

[AC-nqa-admin-test1] type ftp

# Specify the URL of the FTP server.

[AC-nqa-admin-test-ftp] url ftp://10.2.2.2

# Specify 10.1.1.1 as the source IP address.

[AC-nqa-admin-test1-ftp] source ip 10.1.1.1

# Configure the device to upload file config.txt to the FTP server.

[AC-nqa-admin-test1-ftp] operation put

[AC-nqa-admin-test1-ftp] filename config.txt

# Set the username to admin for the FTP operation.

[AC-nqa-admin-test1-ftp] username admin

# Set the password to systemtest for the FTP operation.

[AC-nqa-admin-test1-ftp] password simple systemtest

# Enable the saving of history records.

[AC-nqa-admin-test1-ftp] history-record enable

[AC-nqa-admin-test1-ftp] quit

# Start the FTP operation.

[AC] nqa schedule admin test1 start-time now lifetime forever

# After the FTP operation runs for a period of time, stop the operation.

[AC] undo nqa schedule admin test1

# Display the most recent result of the FTP operation.

[AC] display nqa result admin test1

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

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: 2011-11-22 10:07:28.6

Extended results:

Packet loss ratio: 0%

Failures due to timeout: 0

Failures due to disconnect: 0

Failures due to no connection: 0

Failures due to internal error: 0

Failures due to other errors: 0

# Display the history records of the FTP operation.

[AC] display nqa history admin test1

NQA entry (admin admin, tag test1) history records:

Index Response Status Time

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

The output shows that it took the AC 173 milliseconds to upload a file to the FTP server.

HTTP operation configuration example

Network requirements

As shown in Figure 6, configure an HTTP operation on the NQA client to test the time required to obtain data from the HTTP server.

Figure 6 Network diagram

Configuration procedure

# Assign each interface an IP address. (Details not shown.)

# Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

# Create an HTTP operation.

<AC> system-view

[AC] nqa entry admin test1

[AC-nqa-admin-test1] type http

# Specify the URL of the HTTP server.

[AC-nqa-admin-test-http] url http://10.2.2.2/index.htm

# Configure the HTTP operation to get data from the HTTP server.

[AC-nqa-admin-test1-http] operation get

# Configure the operation to use HTTP version 1.0.

[AC-nqa-admin-test1-http] version v1.0

# Enable the saving of history records.

[AC-nqa-admin-test1-http] history-record enable

[AC-nqa-admin-test1-http] quit

# Start the HTTP operation.

[AC] nqa schedule admin test1 start-time now lifetime forever

# After the HTTP operation runs for a period of time, stop the operation.

[AC] undo nqa schedule admin test1

# Display the most recent result of the HTTP operation.

[AC] display nqa result admin test1

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

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: 2011-11-22 10:12:47.9

Extended results:

Packet loss ratio: 0%

Failures due to timeout: 0

Failures due to disconnect: 0

Failures due to no connection: 0

Failures due to internal error: 0

Failures due to other errors: 0

# Display the history records of the HTTP operation.

[AC] display nqa history admin test1

NQA entry (admin admin, tag test1) history records:

Index Response Status Time

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

The output shows that it took the AC 64 milliseconds to obtain data from the HTTP server.

UDP jitter operation configuration example

Network requirements

As shown in Figure 7, configure a UDP jitter operation to test the jitter, delay, and round-trip time between the AC and the device.

Figure 7 Network diagram

Configuration procedure

1. Assign each interface an IP address. (Details not shown.)

2. Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

3. Configure NTP to ensure that the devices are time synchronized with each other. (Details not shown.)

4. Configure the device:

# Enable the NQA server.

<Device> system-view

[Device] nqa server enable

# Configure a listening service to listen on the IP address 10.2.2.2 and UDP port 9000.

[Device] nqa server udp-echo 10.2.2.2 9000

5. Configure the AC:

# Create a UDP jitter operation.

<AC> system-view

[AC] nqa entry admin test1

[AC-nqa-admin-test1] type udp-jitter

# Specify 10.2.2.2 as the destination address of the operation.

[AC-nqa-admin-test1-udp-jitter] destination ip 10.2.2.2

# Set the destination port number to 9000.

[AC-nqa-admin-test1-udp-jitter] destination port 9000

# Configure the operation to repeat every 1000 milliseconds.

[AC-nqa-admin-test1-udp-jitter] frequency 1000

[AC-nqa-admin-test1-udp-jitter] quit

# Start the UDP jitter operation.

[AC] nqa schedule admin test1 start-time now lifetime forever

# After the UDP jitter operation runs for a period of time, stop the operation.

[AC] undo nqa schedule admin test1

# Display the most recent result of the UDP jitter operation.

[AC] display nqa result admin test1

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

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 packet received time: 2011-05-29 13:56:17.6

Extended results:

Packet loss ratio: 0%

Failures due to timeout: 0

Failures due to internal error: 0

Failures due to other errors: 0

Packets out of sequence: 0

Packets 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 packets: 0 DS lost packets: 0

Lost packets for unknown reason: 0

# Display the statistics of the UDP jitter operation.

[AC] display nqa statistics admin test1

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

NO. : 1

Start time: 2011-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 ratio: 0%

Failures due to timeout: 0

Failures due to internal error: 0

Failures due to other errors: 0

Packets out of sequence: 0

Packets 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 packets: 0 DS lost packets: 0

Lost packets for unknown reason: 0

SNMP operation configuration example

Network requirements

As shown in Figure 8, configure an SNMP operation to test the time the NQA client uses to get a response from the SNMP agent.

Figure 8 Network diagram

Configuration procedure

1. Assign each interface an IP address. (Details not shown.)

2. Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

3. Configure the SNMP agent:

# Set the SNMP version to all.

<Device> system-view

[Device] snmp-agent sys-info version all

# Set the read community to public.

[Device] snmp-agent community read public

# Set the write community to private.

[Device] snmp-agent community write private

4. Configure the AC:

# Create an SNMP operation.

<AC> system-view

[AC] nqa entry admin test1

[AC-nqa-admin-test1] type snmp

# Specify 10.2.2.2 as the destination IP address of the SNMP operation.

[AC-nqa-admin-test1-snmp] destination ip 10.2.2.2

# Enable the saving of history records.

[AC-nqa-admin-test1-snmp] history-record enable

[AC-nqa-admin-test1-snmp] quit

# Start the SNMP operation.

[AC] nqa schedule admin test1 start-time now lifetime forever

# After the SNMP operation runs for a period of time, stop the operation.

[AC] undo nqa schedule admin test1

# Display the most recent result of the SNMP operation.

[AC] display nqa result admin test1

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

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: 2011-11-22 10:24:41.1

Extended results:

Packet loss ratio: 0%

Failures due to timeout: 0

Failures due to internal error: 0

Failures due to other errors: 0

# Display the history records of the SNMP operation.

[AC] display nqa history admin test1

NQA entry (admin admin, tag test1) history records:

Index Response Status Time

1 50 Succeeded 2011-11-22 10:24:41.1

The output shows that it took the AC 50 milliseconds to receive a response from the SNMP agent.

TCP operation configuration example

Network requirements

As shown in Figure 9, configure a TCP operation to test the time required for the AC and the device to establish a TCP connection.

Figure 9 Network diagram

Configuration procedure

1. Assign each interface an IP address. (Details not shown.)

2. Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

3. Configure the device:

# Enable the NQA server.

<Device> system-view

[Device] nqa server enable

# Configure a listening service to listen on the IP address 10.2.2.2 and TCP port 9000.

[Device] nqa server tcp-connect 10.2.2.2 9000

4. Configure the AC:

# Create a TCP operation.

<AC> system-view

[AC] nqa entry admin test1

[AC-nqa-admin-test1] type tcp

# Specify 10.2.2.2 as the destination IP address.

[AC-nqa-admin-test1-tcp] destination ip 10.2.2.2

# Set the destination port number to 9000.

[AC-nqa-admin-test1-tcp] destination port 9000

# Enable the saving of history records.

[AC-nqa-admin-test1-tcp] history-record enable

[AC-nqa-admin-test1-tcp] quit

# Start the TCP operation.

[AC] nqa schedule admin test1 start-time now lifetime forever

# After the TCP operation runs for a period of time, stop the operation.

[AC] undo nqa schedule admin test1

# Display the most recent result of the TCP operation.

[AC] display nqa result admin test1

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

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: 2011-11-22 10:27:25.1

Extended results:

Packet loss ratio: 0%

Failures due to timeout: 0

Failures due to disconnect: 0

Failures due to no connection: 0

Failures due to internal error: 0

Failures due to other errors: 0

# Display the history records of the TCP operation.

[AC] display nqa history admin test1

NQA entry (admin admin, tag test1) history records:

Index Response Status Time

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

The output shows that it took the AC 13 milliseconds to establish a TCP connection to port 9000 on the NQA server.

UDP echo operation configuration example

Network requirements

As shown in Figure 10, configure a UDP echo operation to test the round-trip time between the AC and the device. The destination port number is 8000.

Figure 10 Network diagram

Configuration procedure

1. Assign each interface an IP address. (Details not shown.)

2. Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

3. Configure the device:

# Enable the NQA server.

<Device> system-view

[Device] nqa server enable

# Configure a listening service to listen on the IP address 10.2.2.2 and UDP port 8000.

[Device] nqa server udp-echo 10.2.2.2 8000

4. Configure the AC:

# Create a UDP echo operation.

<AC> system-view

[AC] nqa entry admin test1

[AC-nqa-admin-test1] type udp-echo

# Specify 10.2.2.2 as the destination IP address.

[AC-nqa-admin-test1-udp-echo] destination ip 10.2.2.2

# Set the destination port number to 8000.

[AC-nqa-admin-test1-udp-echo] destination port 8000

# Enable the saving of history records.

[AC-nqa-admin-test1-udp-echo] history-record enable

[AC-nqa-admin-test1-udp-echo] quit

# Start the UDP echo operation.

[AC] nqa schedule admin test1 start-time now lifetime forever

# After the UDP echo operation runs for a period of time, stop the operation.

[AC] undo nqa schedule admin test1

# Display the most recent result of the UDP echo operation.

[AC] display nqa result admin test1

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

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: 2011-11-22 10:36:17.9

Extended results:

Packet loss ratio: 0%

Failures due to timeout: 0

Failures due to internal error: 0

Failures due to other errors: 0

# Display the history records of the UDP echo operation.

[AC] display nqa history admin test1

NQA entry (admin admin, tag test1) history records:

Index Response Status Time

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

The output shows that the round-trip time between the AC and port 8000 on the device is 25 milliseconds.

NQA collaboration configuration example

Network requirements

As shown in Figure 11, configure a static route to Switch B with Switch A as the next hop on the AC. Associate the static route, a track entry, and an ICMP echo operation to monitor the state of the static route.

Figure 11 Network diagram

Configuration procedure

1. Assign each interface an IP address. (Details not shown.)

2. On the AC, configure a static route, and associate the static route with track entry 1.

<AC> system-view

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

3. Configure an ICMP echo operation:

# Create an NQA operation with the administrator name admin and operation tag test1.

[AC] nqa entry admin test1

# Configure the NQA operation type as ICMP echo.

[AC-nqa-admin-test1] type icmp-echo

# Specify 10.2.1.1 as the destination IP address.

[AC-nqa-admin-test1-icmp-echo] destination ip 10.2.1.1

# Configure the operation to repeat every 100 milliseconds.

[AC-nqa-admin-test1-icmp-echo] frequency 100

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

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

[AC-nqa-admin-test1-icmp-echo] quit

# Start the ICMP operation.

[AC] nqa schedule admin test1 start-time now lifetime forever

4. Create track entry 1, and associate it with reaction entry 1 of the NQA operation.

[AC] track 1 nqa entry admin test1 reaction 1

Verifying the configuration

# Display information about all the track entries on the AC.

[AC] display track all

Track ID: 1

State: Positive

Duration: 0 days 0 hours 0 minutes 0 seconds

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

Tracked object:

NQA entry: admin test1

Reaction: 1

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

[AC] display ip routing-table

Destinations : 13 Routes : 13

Destination/Mask Proto Pre Cost NextHop Interface

0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

10.1.1.0/24 Static 60 0 10.2.1.1 Vlan3

10.2.1.0/24 Direct 0 0 10.2.1.2 Vlan3

10.2.1.0/32 Direct 0 0 10.2.1.2 Vlan3

10.2.1.2/32 Direct 0 0 127.0.0.1 InLoop0

10.2.1.255/32 Direct 0 0 10.2.1.2 Vlan3

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0

224.0.0.0/24 Direct 0 0 0.0.0.0 NULL0

255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

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

# Remove the IP address of VLAN-interface 3 on Switch A.

<SwitchA> system-view

[SwitchA] interface vlan-interface 3

[SwitchA-Vlan-interface3] undo ip address

# Display information about all the track entries on the AC.

[AC] display track all

Track ID: 1

State: Negative

Duration: 0 days 0 hours 0 minutes 0 seconds

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

Tracked object:

NQA entry: admin test1

Reaction: 1

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

[AC] display ip routing-table

Destinations : 12 Routes : 12

Destination/Mask Proto Pre Cost NextHop Interface

0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

10.2.1.0/24 Direct 0 0 10.2.1.2 Vlan3

10.2.1.0/32 Direct 0 0 10.2.1.2 Vlan3

10.2.1.2/32 Direct 0 0 127.0.0.1 InLoop0

10.2.1.255/32 Direct 0 0 10.2.1.2 Vlan3

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0

224.0.0.0/24 Direct 0 0 0.0.0.0 NULL0

255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0

The output shows that the static route does not exist, and the status of the track entry is negative.

ICMP template configuration example

Network requirements

As shown in Figure 12, configure an ICMP template for a feature to perform the ICMP echo operation from the AC to Device A.

Figure 12 Network diagram

Configuration procedure

# Assign each interface an IP address. (Details not shown.)

# Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

# Create ICMP template icmp.

<AC> system-view

[AC] nqa template icmp icmp

# Specify 10.2.2.2 as the destination IP address of ICMP echo requests.

[AC-nqatplt-icmp-icmp] destination ip 10.2.2.2

# Set the probe timeout time to 500 milliseconds for the ICMP echo operation.

[AC-nqatplt-icmp-icmp] probe timeout 500

# Configure the ICMP echo operation to repeat every 3000 milliseconds.

[AC-nqatplt-icmp-icmp] frequency 3000

# Configure the NQA client to notify the feature of the successful operation event if the number of consecutive successful probes reaches 2.

[AC-nqatplt-icmp-icmp] reaction trigger probe-pass 2

# Configure the NQA client to notify the feature of the operation failure if the number of consecutive failed probes reaches 2.

[AC-nqatplt-icmp-icmp] reaction trigger probe-fail 2

TCP template configuration example

Network requirements

As shown in Figure 13, configure a TCP template for a feature to perform the TCP operation. The operation tests whether the AC can establish a TCP connection to the device.

Figure 13 Network diagram

Configuration procedure

1. Assign each interface an IP address. (Details not shown.)

2. Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

3. Configure the device:

# Enable the NQA server.

<Device> system-view

[Device] nqa server enable

# Configure a listening service to listen to the IP address 10.2.2.2 and TCP port 9000.

[Device] nqa server tcp-connect 10.2.2.2 9000

4. Configure the AC:

# Create TCP template tcp.

<AC> system-view

[AC] nqa template tcp tcp

# Specify 10.2.2.2 as the destination IP address.

[AC-nqatplt-tcp-tcp] destination ip 10.2.2.2

# Set the destination port number to 9000.

[AC-nqatplt-tcp-tcp] destination port 9000

# Configure the NQA client to notify the feature of the successful operation event if the number of consecutive successful probes reaches 2.

[AC-nqatplt-tcp-tcp] reaction trigger probe-pass 2

# Configure the NQA client to notify the feature of the operation failure if the number of consecutive failed probes reaches 2.

[AC-nqatplt-tcp-tcp] reaction trigger probe-fail 2

TCP half open template configuration example

Network requirements

As shown in Figure 14, configure a TCP half open template for a feature to test whether the AC can provide the TCP service for the device.

Figure 14 Network diagram

Configuration procedure

1. Assign each interface an IP address. (Details not shown.)

2. Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

3. Configure the AC:

# Create TCP half open template test.

<AC> system-view

[AC] nqa template tcphalfopen test

# Specify 10.2.2.2 as the destination IP address.

[AC-nqatplt-tcphalfopen-test] destination ip 10.2.2.2

# Configure the NQA client to notify the feature of the successful operation event if the number of consecutive successful probes reaches 2.

[AC-nqatplt-tcphalfopen-test] reaction trigger probe-pass 2

# Configure the NQA client to notify the feature of the operation failure if the number of consecutive failed probes reaches 2.

[AC-nqatplt-tcphalfopen-test] reaction trigger probe-fail 2

UDP template configuration example

Network requirements

As shown in Figure 15, configure a UDP template for a feature to perform the UDP operation. The operation tests whether the AC can receive a response from the device.

Figure 15 Network diagram

Configuration procedure

1. Assign each interface an IP address. (Details not shown.)

2. Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

3. Configure the device:

# Enable the NQA server.

<Device> system-view

[Device] nqa server enable

# Configure a listening service to listen to the IP address 10.2.2.2 and UDP port 9000.

[Device] nqa server udp-echo 10.2.2.2 9000

4. Configure the AC:

# Create UDP template udp.

<AC> system-view

[AC] nqa template udp udp

# Specify 10.2.2.2 as the destination IP address.

[AC-nqatplt-udp-udp] destination ip 10.2.2.2

# Set the destination port number to 9000.

[AC-nqatplt-udp-udp] destination port 9000

# Configure the NQA client to notify the feature of the successful operation event if the number of consecutive successful probes reaches 2.

[AC-nqatplt-udp-udp] reaction trigger probe-pass 2

# Configure the NQA client to notify the feature of the operation failure if the number of consecutive failed probes reaches 2.

[AC-nqatplt-udp-udp] reaction trigger probe-fail 2

HTTP template configuration example

Network requirements

As shown in Figure 16, configure an HTTP template for a feature to perform the HTTP operation. The operation tests whether the NQA client can get data from the HTTP server.

Figure 16 Network diagram

Configuration procedure

# Assign each interface an IP address. (Details not shown.)

# Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

# Create HTTP template http.

<AC> system-view

[AC] nqa template http http

# Specify http://10.2.2.2/index.htm as the URL of the HTTP server.

[AC-nqatplt-http-http] url http://10.2.2.2/index.htm

# Configure the HTTP operation to get data from the HTTP server.

[AC-nqatplt-http-http] operation get

# Configure the NQA client to notify the feature of the successful operation event if the number of consecutive successful probes reaches 2.

[AC-nqatplt-http-http] reaction trigger probe-pass 2

# Configure the NQA client to notify the feature of the operation failure if the number of consecutive failed probes reaches 2.

[AC-nqatplt-http-http] reaction trigger probe-fail 2

HTTPS template configuration example

Network requirements

As shown in Figure 17, configure an HTTPS template for a feature to test whether the NQA client can get data from the HTTPS server.

Figure 17 Network diagram

Configuration procedure

# Assign each interface an IP address. (Details not shown.)

# Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

# Configure an SSL client policy named abc on the AC, and make sure the AC can use the policy to connect to the HTTPS server on the device. (Details not shown.)

# Create HTTPS template test.

<AC> system-view

[AC] nqa template https https

# Specify http://10.2.2.2/index.htm as the URL of the HTTPS server.

[AC-nqatplt-https-https] url https://10.2.2.2/index.htm

# Specify the SSL client policy abc for the HTTPS template.

[AC-nqatplt-https-https] ssl-client-policy abc

# Set the HTTPS operation type to get (the default HTTPS operation type).

[AC-nqatplt-https-https] operation get

# Set the HTTPS version to 1.0 (the default HTTPS version).

[AC-nqatplt-https-https] version v1.0

# Configure the NQA client to notify the feature of the successful operation event if the number of consecutive successful probes reaches 2.

[AC-nqatplt-https-https] reaction trigger probe-pass 2

# Configure the NQA client to notify the feature of the operation failure if the number of consecutive failed probes reaches 2.

[AC-nqatplt-https-https] reaction trigger probe-fail 2

FTP template configuration example

Network requirements

As shown in Figure 18, configure an FTP template for a feature to perform the FTP operation. The operation tests whether the AC can upload a file to the FTP server. The login username and password are admin and systemtest, respectively. The file to be transferred to the FTP server is config.txt.

Figure 18 Network diagram

Configuration procedure

# Assign each interface an IP address. (Details not shown.)

# Configure static routes or a routing protocol to make sure the AC and the device can reach each other. (Details not shown.)

# Create FTP template ftp.

<AC> system-view

[AC] nqa template ftp ftp

# Specify the URL of the FTP server.

[AC-nqatplt-ftp-ftp] url ftp://10.2.2.2

# Specify 10.1.1.1 as the source IP address.

[AC-nqatplt-ftp-ftp] source ip 10.1.1.1

# Configure the device to upload file config.txt to the FTP server.

[AC-nqatplt-ftp-ftp] operation put

[AC-nqatplt-ftp-ftp] filename config.txt

# Set the username to admin for the FTP server login.

[AC-nqatplt-ftp-ftp] username admin

# Set the password to systemtest for the FTP server login.

[AC-nqatplt-ftp-ftp] password simple systemtest

# Configure the NQA client to notify the feature of the successful operation event if the number of consecutive successful probes reaches 2.

[AC-nqatplt-ftp-ftp] reaction trigger probe-pass 2

# Configure the NQA client to notify the feature of the operation failure if the number of consecutive failed probes reaches 2.

[AC-nqatplt-ftp-ftp] reaction trigger probe-fail 2

RADIUS template configuration example

Network requirements

As shown in Figure 19, configure a RADIUS template for a feature to test whether the device can provide authentication service for the AC. The username and password are admin and systemtest, respectively. The shared key is 123456 for secure RADIUS authentication.

Figure 19 Network diagram

Configuration procedure

# Assign each interface an IP address. (Details not shown.)

# Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not shown.)

# Configure the RADIUS server on the device. (Details not shown.)

# Create RADIUS template radius.

<AC> system-view

[AC] nqa template radius radius

# Specify 10.2.2.2 as the destination IP address of the operation.

[AC-nqatplt-radius-radius] destination ip 10.2.2.2

# Set the username to admin.

[AC-nqatplt-radius-radius] username admin

# Set the password to systemtest.

[AC-nqatplt-radius-radius] password simple systemtest

# Set the shared key to 123456 in plain text for secure RADIUS authentication.

[AC-nqatplt-radius-radius] key simple 123456

# Configure the NQA client to notify the feature of the successful operation event if the number of consecutive successful probes reaches 2.

[AC-nqatplt-radius-radius] reaction trigger probe-pass 2

# Configure the NQA client to notify the feature of the operation failure if the number of consecutive failed probes reaches 2.

[AC-nqatplt-radius-radius] reaction trigger probe-fail 2

SSL template configuration example

Network requirements

As shown in Figure 20, configure an SSL template for a feature to test whether the AC can establish an SSL connection to the SSL server.

Figure 20 Network diagram

Configuration procedure

# Assign each interface an IP address. (Details not shown.)

# Configure static routes or a routing protocol to make sure the AC and the device can reach each other. (Details not shown.)

# Configure an SSL client policy named abc on the AC, and make sure the AC can use the policy to connect to the SSL server on the device. (Details not shown.)

# Create SSL template ssl.

<AC> system-view

[AC] nqa template ssl ssl

# Set the destination IP address and port number to 10.2.2.2 and 9000, respectively.

[AC-nqatplt-ssl-ssl] destination ip 10.2.2.2

[AC-nqatplt-ssl-ssl] destination port 9000

# Specify the SSL client policy abc for the SSL template.

[AC-nqatplt-ssl-ssl] ssl-client-policy abc

# Configure the NQA client to notify the feature of the successful operation event if the number of consecutive successful probes reaches 2.

[AC-nqatplt-ssl-ssl] reaction trigger probe-pass 2

# Configure the NQA client to notify the feature of the operation failure if the number of consecutive failed probes reaches 2.

[AC-nqatplt-ssl-ssl] reaction trigger probe-fail 2

12-Network Management and Monitoring

Configuring the TCP operation

Configuring the UDP echo operation

Threshold types

Triggered actions

Reaction entry

Configuration procedure

Scheduling the NQA operation on the NQA client

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration procedure

NQA collaboration configuration example

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us