Network quality analyzer (NQA) allows you to monitor link status, 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

· DHCP

· FTP

· HTTP

· UDP jitter

· SNMP

· TCP

· UDP echo

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 one-way latency, jitter, packet loss, voice quality, application performance, and server response time.

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

You can configure the NQA server to listen and respond on specific ports to satisfy various test needs.

Figure 1 Network diagram

NQA operation

The following describes how different NQA operation types operate:

· A TCP operation sets up a connection.

· A UDP jitter operation sends a specific number of probe packets. The number of probe packets is configurable by using the probe packet-number command.

· An FTP operation uploads or downloads a file.

· An HTTP operation gets a Web page.

· A DHCP operation gets an IP address through DHCP.

· An ICMP echo operation sends an ICMP echo request or a UDP packet.

· 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 as 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 display results or send trap messages to the network management station (NMS) when the performance metrics that an NQA operation gathers 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	All NQA operation types excluding UDP jitter
Number of probe failures	All NQA operation types excluding UDP jitter
Round-trip time	UDP jitter
Number of discarded packets	UDP jitter
One-way jitter (source-to-destination and destination-to-source)	UDP jitter
One-way latency (source-to-destination and destination-to-source)	UDP jitter

NQA configuration task list

Complete the following task to configure the NQA server:

Task	Remarks
Configuring the NQA server	Required for NQA operations types of TCP, UDP echo, and UDP jitter

Complete these tasks to configure the NQA client:

Task	Remarks
Enabling the NQA client	Required.
Configuring an ICMP echo operation	Required. Use at least one method.
Configuring a DHCP operation
Configuring an FTP operation
Configuring an HTTP operation
Configuring a UDP jitter operation
Configuring an SNMP operation
Configuring a TCP operation
Configuring a UDP echo operation
Configuring optional parameters for an NQA operation	Optional.
Configuring the collaboration function	Optional.
Configuring threshold monitoring	Optional.
Configuring the NQA statistics function	Optional.
Configuring NQA history records saving function	Optional.
Scheduling an NQA operation	Required.

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. Each listening service corresponds to a specific destination IP address and port number. The destination IP address and port number must be the same as those configured on the NQA client and must be different from those of an existing listening service.

To configure the NQA server:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable the NQA server.	nqa server enable	Disabled by default.
3. Configure a listening service.	· Method 1: nqa server tcp-connect ip-address port-number · Method 2: nqa server udp-echo ip-address port-number	Use at least one method.

Configuring the NQA client

Enabling the NQA client

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable the NQA client.	nqa agent enable	Optional. Enabled by default.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Enable the NQA client.

nqa agent enable

Optional.

Enabled by default.

Configuring an ICMP echo operation

An 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 an 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 operation exits.
3. Specify the ICMP echo type and enter its view.	type icmp-echo	N/A
4. Specify the destination address of ICMP echo requests.	destination ip ip-address	By default, no destination IP address is configured.
5. Specify the payload size in each ICMP echo request.	data-size size	Optional. 100 bytes by default.
6. Configure the string to be filled in the payload of each ICMP echo request.	data-fill string	Optional. By default, the string is the hexadecimal number 00010203040506070809.
7. Specify the source interface or the source IP address of ICMP echo requests.	· Method 1: source interface interface-type interface-number · Method 2: source ip ip-address	Optional. By default, no source interface or source IP address is configured, and the requests take the primary IP address of the outgoing interface as their source IP address. If you configure both the source ip command and the source interface command, the source ip command takes effect. The specified source interface must be up. The source IP address must be the IP address of a local interface and the interface must be up.
8. Configure the next hop IP address for ICMP echo requests.	next-hop ip-address	Optional. By default, no next hop IP address is configured.

Configuring a DHCP operation

A DHCP operation measures the time it takes for the NQA client to get an IP address from a DHCP server.

The specified interface simulates the DHCP client to acquire an IP address and it does not change its IP address.

When the DHCP operation completes, the NQA client sends a packet to release the obtained IP address.

To configure a DHCP 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 operation exits.
3. Specify the DHCP type and enter its view.	type dhcp	N/A
4. Specify an interface to perform the DHCP operation.	operation interface interface-type interface-number	By default, no interface is specified to perform a DHCP operation. The specified interface must be up. Otherwise, no probe packets can be sent out.

Configuring an FTP operation

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

Follow these guidelines when you configure an FTP operation:

· Before you perform an FTP operation, obtain the username and password for logging in to the FTP server.

· When you execute the put command, the NQA client creates a file named file-name of fixed size on the FTP server. When you execute the get command, the client does not save the file obtained from the FTP server.

· If you get a file that does not exist on the FTP server, the FTP operation fails.

· Only use the get command to download a small file. A big file might result in transfer failure because of timeout, or might affect other services for occupying much network bandwidth.

To configure an 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 operation exits.
3. Specify the FTP type and enter its view.	type ftp	N/A
4. Specify the IP address of the FTP server as the destination address of FTP request packets.	destination ip ip-address	By default, no destination IP address is configured.
5. Configure 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. The local interface must be up. Otherwise, no FTP requests can be sent out.
6. Specify the operation type.	operation { get \| put }	Optional. By default, the operation type for the FTP operation is get, which means obtaining files from the FTP server.
7. Configure a login username.	username name	Optional. By default, no login username is configured.
8. Configure a login password.	password [ cipher \| simple ] password	Optional. By default, no login password is configured.
9. Specify the name of a file to be transferred.	filename file-name	By default, no file is specified.
10. Set the data transmission mode.	mode { active \| passive }	Optional. The default mode is active.

Configuring an HTTP operation

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

The TCP port number of the HTTP server must be 80. Otherwise, the HTTP operation fails.

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 operation exits.
3. Specify the HTTP type and enter its view.	type http	N/A
4. Configure the IP address of the HTTP server as the destination address of HTTP request packets.	destination ip ip-address	By default, no destination IP address is configured.
5. Configure the source IP address of request packets.	source ip ip-address	Optional. By default, no source IP address is specified. The source IP address must be the IP address of a local interface. The local interface must be up. Otherwise, no request packets can be sent out.
6. Configure the operation type.	operation { get \| post }	Optional. By default, the operation type for the HTTP is get, which means obtaining data from the HTTP server.
7. Specify the destination website URL.	url url	N/A
8. Specify the HTTP version.	http-version v1.0	Optional. By default, HTTP 1.0 is used.

Configuring a UDP jitter operation

CAUTION:

Do not perform the UDP jitter operation on well-known ports from 1 to 1023. Otherwise, the UDP jitter operation might fail or the service on the well-known port might become unavailable.

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

The UDP jitter operation works as follows:

1. The NQA client sends UDP packets to the destination port at a regular interval.

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 operation exits.
3. Specify the UDP jitter type and enter its view.	type udp-jitter	N/A
4. Configure the destination address of UDP packets.	destination ip ip-address	By default, no destination IP address is configured. The destination IP address must be the same as that of the listening service on the NQA server.
5. Configure the destination port of UDP packets.	destination port port-number	By default, no destination port number is configured. The destination port must be the same as that of the listening service on the NQA server.
6. Specify the source port number of UDP packets.	source port port-number	Optional. By default, no source port number is specified.
7. Configure Payload size in each UDP packet.	data-size size	Optional. 100 bytes by default.
8. Configure the string to be filled in the payload of each UDP packet.	data-fill string	Optional. By default, the string is the hexadecimal number 00010203040506070809.
9. Configure the number of UDP packets sent in one UDP jitter probe.	probe packet-number packet-number	Optional. 10 by default.
10. Configure the interval for sending UDP packets.	probe packet-interval packet-interval	Optional. 20 milliseconds by default.
11. Configure how long the NQA client waits for a response from the server before it regards the response times out.	probe packet-timeout packet-timeout	Optional. 3000 milliseconds by default.
12. Configure the source IP address for UDP packets.	source ip ip-address	Optional. By default, no source IP address is specified. The source IP address must be the IP address of a local interface. The local interface must be up. Otherwise, no UDP packets can be sent out.

NOTE:

The display nqa history command does not show the results of the UDP jitter operation. Use the display nqa result command to display the results, or use the display nqa statistics command to display the statistics of the operation.

Configuring an SNMP operation

An SNMP operation measures the time it takes for the NQA client to get a value from an SNMP agent.

To configure an 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 operation exits.
3. Specify the SNMP type and enter its view.	type snmp	N/A
4. Configure the destination address of SNMP packets.	destination ip ip-address	By default, no destination IP address is configured.
5. Specify the source port of SNMP packets.	source port port-number	Optional. By default, no source port number is specified.
6. Configure the source IP address of SNMP packets.	source ip ip-address	Optional. By default, no source IP address is specified. The source IP address must be the IP address of a local interface. The local interface must be up. Otherwise, no SNMP packets can be sent out.

Configuring a TCP operation

A TCP operation measures the time it takes for the NQA client to establish a TCP connection to a specific 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 a 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 operation exits.
3. Specify the TCP type and enter its view.	type tcp	N/A
4. Configure the destination address of TCP packets.	destination ip ip-address	By default, no destination IP address is configured. The destination address must be the same as the IP address of the listening service configured on the NQA server.
5. Configure 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 that of the listening service on the NQA server.
6. Configure the source IP address of TCP packets.	source ip ip-address	Optional. By default, no source IP address is specified. The source IP address must be the IP address of a local interface. The local interface must be up. Otherwise, no TCP packets can be sent out.

Configuring a UDP echo operation

A UDP echo operation measures the round-trip time between the client and a specific 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 a 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 operation exits.
3. Specify the UDP echo type and enter its view.	type udp-echo	N/A
4. Configure the destination address of UDP packets.	destination ip ip-address	By default, no destination IP address is configured. The destination address must be the same as the IP address of the listening service configured on the NQA server.
5. Configure the destination port of UDP packets.	destination port port-number	By default, no destination port number is configured. The destination port number must be the same as that of the listening service on the NQA server.
6. Configure Payload size in each UDP packet.	data-size size	Optional. 100 bytes by default.
7. Configure the string to be filled in the payload of each UDP packet.	data-fill string	Optional. By default, the string is the hexadecimal number 00010203040506070809.
8. Specify the source port of UDP packets.	source port port-number	Optional. By default, no source port number is specified.
9. Configure the source IP address of UDP packets.	source ip ip-address	Optional. By default, no source IP address is specified. The source IP address must be that of an interface on the device and the interface must be up. Otherwise, no UDP packets can be sent out.

Configuring optional parameters for an NQA operation

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

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 operation exits.
3. Specify an NQA operation type and enter its view.	type { dhcp \| ftp \| http \| icmp-echo \| snmp \| tcp \| udp-echo \| udp-jitter }	N/A
4. Configure a description.	description text	Optional. By default, no description is configured.
5. Specify the interval at which the NQA operation repeats.	frequency interval	Optional. By default, the interval 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	Optional. By default, an NQA operation performs one probe.
7. Specify the probe timeout time.	probe timeout timeout	Optional. By default, the timeout time is 3000 milliseconds. This setting is not available for the UDP jitter operation.
8. Specify the TTL for probe packets.	ttl value	Optional. 20 by default. This setting is not available for the DHCP operation.
9. Specify the ToS value in the IP packet header of probe packets.	tos value	Optional. 0 by default. This setting is not available for the DHCP operation.
10. Enable the routing table bypass function.	route-option bypass-route	Optional. Disabled by default. This setting is not available for the DHCP operation.

Configuring the collaboration function

Collaboration is implemented by associating a reaction entry of an NQA operation 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 function:

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 operation exits.
3. Specify an NQA operation type and enter its view.	type { dhcp \| ftp \| http \| icmp-echo \| snmp \| tcp \| udp-echo }	The collaboration function is not available for the UDP jitter operation.
4. Configure a reaction entry.	reaction item-number checked-element probe-fail threshold-type consecutive consecutive-occurrences action-type trigger-only	Not configured by default. You cannot modify the content of an existing reaction entry.
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

Introduction

1. 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, and threshold violations for the consecutive type are determined from the time the NQA operation starts.

2. 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.

3. Reaction entry

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

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

¡ Before an NQA 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 to be triggered is configured as trap-only for a reaction entry, when the state of the entry changes, a trap message is generated and sent to the NMS.

Configuration prerequisites

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.

Configuration procedure

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 operation exits.
3. Specify an NQA operation type and enter its view.	type { dhcp \| ftp \| http \| icmp-echo \| snmp \| tcp \| udp-echo \| udp-jitter }	N/A
4. Configure threshold monitoring.	· Enable sending traps to the NMS when specified conditions are met: reaction trap { probe-failure consecutive-probe-failures \| test-complete \| test-failure cumulate-probe-failures } · Configure a reaction entry for monitoring the duration of an NQA operation (not supported in the UDP jitter operation): reaction item-number checked-element probe-duration threshold-type { accumulate accumulate-occurrences \| average \| consecutive consecutive-occurrences } threshold-value upper-threshold lower-threshold [ action-type { none \| trap-only } ] · Configure a reaction entry for monitoring failure times (not supported in the UDP jitter operation): reaction item-number checked-element probe-fail threshold-type { accumulate accumulate-occurrences \| consecutive consecutive-occurrences } [ action-type { none \| trap-only } ] · Configure a reaction entry for monitoring the round-trip time (only supported in the UDP jitter operation): reaction item-number checked-element rtt threshold-type { accumulate accumulate-occurrences \| average } threshold-value upper-threshold lower-threshold [ action-type { none \| trap-only } ] · Configure a reaction entry for monitoring packet loss (only supported in the UDP jitter operation): reaction item-number checked-element packet-loss threshold-type accumulate accumulate-occurrences [ action-type { none \| trap-only } ] · Configure a reaction entry for monitoring one-way jitter (only supported in the UDP jitter operation): reaction item-number checked-element { jitter-ds \| jitter-sd } threshold-type { accumulate accumulate-occurrences \| average } threshold-value upper-threshold lower-threshold [ action-type { none \| trap-only } ] · Configure a reaction entry for monitoring the one-way delay (only supported in the UDP jitter operation): reaction item-number checked-element { owd-ds \| owd-sd } threshold-value upper-threshold lower-threshold	Configure the trap sending method as needed. No traps are sent to the NMS by default.

Configuring the NQA statistics function

NQA collects statistics for an operation in a statistics group. To view information about statistics groups, use the display nqa statistics command. To set the interval for collecting statistics, use the statistics interval command.

If a new statistics group is to be saved when the number of statistics groups reaches the upper limit, the oldest statistics group is deleted. To set the maximum number of statistics groups that can be saved, use the statistics max-group command.

A statistics group is formed after an operation is completed. Statistics groups have an aging mechanism. A statistics group is deleted when its hold time expires. To set the hold time, use the statistics hold-time command.

The DHCP operation does not support the NQA statistics function.

If you use the frequency command to set the interval between two consecutive operations to 0, only one operation is performed, and no statistics group information is generated.

To configure the NQA statistics collection function:

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 operation exits.
3. Specify an NQA operation type and enter its view.	type { ftp \| http \| icmp-echo \| snmp \| tcp \| udp-echo \| udp-jitter }	N/A
4. Configure the interval for collecting the statistics.	statistics interval interval	Optional. 60 minutes by default.
5. Configure the maximum number of statistics groups that can be saved.	statistics max-group number	Optional. 2 by default. To disable collecting NQA statistics, set the maximum number to 0.
6. Configure the hold time of statistics groups.	statistics hold-time hold-time	Optional. 120 minutes by default.

Configuring NQA history records saving function

Perform this task to enable the system to save the history records of NQA operations. To display NQA history records, use the display nqa history command.

This task also configures the following parameters:

· Lifetime of the history records.

The records are removed when the lifetime is reached.

· Maximum number of history records that can be saved for an NQA operation.

If the maxim number is reached, the earliest history record is removed when a new record is saved.

To configure the history records saving function:

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 operation exits.
3. Enter NQA operation type view.	type { dhcp \| ftp \| http \| icmp-echo \| snmp \| tcp \| udp-echo \| udp-jitter }	N/A
4. Enable saving history records for the NQA operation.	history-record enable	By default, this feature is not enabled.
5. Set the lifetime of history records.	history-record keep-time keep-time	Optional. By default, history records in the NQA operation are kept for 120 minutes.
6. Configure the maximum number of history records that can be saved.	history-record number number	Optional. By default, the maximum number of records that can be saved for the NQA operation is 50.

Scheduling an NQA operation

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 earlier than the current system time, the operation starts immediately. If both the specified start and end time are earlier than the current system time, the operation does not start. To view the current system time, use the display clock command.

You can configure the maximum number of NQA operations that can work simultaneously as needed to avoid excessive system resource consumption.

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 only affects the NQA operations that have not started.

To schedule an NQA operation:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure the scheduling parameters for an NQA operation.	nqa schedule admin-name operation-tag start-time { hh:mm:ss [ yyyy/mm/dd ] \| now } lifetime { lifetime \| forever }	N/A
3. Configure the maximum number of NQA operations that can work simultaneously.	nqa agent max-concurrent number	Optional. A maximum of two NQA operations can work simultaneously.

Displaying and maintaining NQA

Task	Command	Remarks
Display history records of NQA operations.	display nqa history [ admin-name operation-tag ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view.
Display the current monitoring results of reaction entries.	display nqa reaction counters [ admin-name operation-tag [ item-number ] ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view.
Display the result of the specified NQA operation.	display nqa result [ admin-name operation-tag ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view.
Display NQA statistics.	display nqa statistics [ admin-name operation-tag ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view.
Display NQA server status.	display nqa server status [ \| { begin \| exclude \| include } regular-expression ]	Available in any view.

NQA configuration examples

ICMP echo operation configuration example

Network requirements

As shown in Figure 3, configure and schedule an ICMP echo operation from the NQA client AC to Device B through Device C to test the round-trip time.

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 test operation, and specify 10.2.2.2 as the destination address.

<AC> system-view

[AC] nqa entry admin test

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

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

# Configure 10.1.1.2 as the next hop IP. The ICMP echo requests are sent through Device C to Device B (the destination).

[DeviceA-nqa-admin-test-icmp-echo] next-hop 10.1.1.2

# Configure the ICMP echo operation to perform 10 probes, specify the probe timeout time as 500 milliseconds, and configure the operation to repeat at an interval of 5000 milliseconds.

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

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

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

# Enable saving history records and configure the maximum number of history records that can be saved as 10.

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

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

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

# Start the ICMP echo operation.

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

# Stop the ICMP echo operation after a period of time.

[AC] undo nqa schedule admin test

# Display the results of the ICMP echo operation.

[AC] display nqa result admin test

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

Destination IP address: 10.2.2.2

Send operation times: 10 Receive response times: 10

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

Square-Sum of round trip time: 96

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

Extended results:

Packet loss in test: 0%

Failures due to timeout: 0

Failures due to disconnect: 0

Failures due to no connection: 0

Failures due to sequence error: 0

Failures due to internal error: 0

Failures due to other errors: 0

Packet(s) arrived late: 0

# Display the history records of the ICMP echo operation.

[AC] display nqa history admin test

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

Index Response Status Time

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

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

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

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

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

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

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

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

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

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

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

DHCP operation configuration example

Network requirements

As shown in Figure 4, configure and schedule a DHCP operation to test the time required for AC to obtain an IP address from the DHCP server (Device).

Figure 4 Network diagram

Configuration procedure

# Create a DHCP operation to be performed on interface VLAN-interface 2.

<AC> system-view

[AC] nqa entry admin test

[AC-nqa-admin-test] type dhcp

[AC-nqa-admin-test-dhcp] operation interface vlan-interface 2

# Enable the saving of history records.

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

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

# Start the DHCP operation.

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

# Stop the DHCP operation after a period of time.

[AC] undo nqa schedule admin test

# Display the results of the DHCP operation.

[AC] display nqa result admin test

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

Send operation times: 1 Receive response times: 1

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

Square-Sum of round trip time: 389376

Last succeeded probe time: 2007-11-22 09:56:03.2

Extended results:

Packet loss in test: 0%

Failures due to timeout: 0

Failures due to disconnect: 0

Failures due to no connection: 0

Failures due to sequence error: 0

Failures due to internal error: 0

Failures due to other errors: 0

Packet(s) arrived late: 0

# Display the history records of the DHCP operation.

[AC] display nqa history admin test

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

Index Response Status Time

1 624 Succeeded 2007-11-22 09:56:03.2

The output shows that AC takes 624 milliseconds to obtain an IP address from the DHCP server.

FTP operation configuration example

Network requirements

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

Figure 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 test

[AC-nqa-admin-test] type ftp

# Specify the IP address of the FTP server 10.2.2.2 as the destination IP address.

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

# Specify 10.1.1.1 as the source IP address.

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

# Set the FTP username to admin, and password to systemtest.

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

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

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

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

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

# Enable the saving of history records.

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

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

# Start the FTP operation.

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

# Stop the FTP operation after a period of time.

[AC] undo nqa schedule admin test

# Display the results of the FTP operation.

[AC] display nqa result admin test

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

Destination IP address: 10.2.2.2

Send operation times: 1 Receive response times: 1

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

Square-Sum of round trip time: 29929

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

Extended results:

Packet loss in test: 0%

Failures due to timeout: 0

Failures due to disconnect: 0

Failures due to no connection: 0

Failures due to sequence error: 0

Failures due to internal error: 0

Failures due to other errors: 0

Packet(s) arrived late: 0

# Display the history records of the FTP operation.

[AC] display nqa history admin test

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

Index Response Status Time

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

The output shows that AC takes 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 test

[AC-nqa-admin-test] type http

# Specify the IP address of the HTTP server 10.2.2.2 as the destination IP address.

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

# Configure the HTTP operation to get data from the HTTP server. (This step can be omitted because the default HTTP operation type is get.)

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

# Configure the HTTP operation to visit the website /index.htm.

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

# Configure the operation to use HTTP version 1.0. (This step can be omitted because version 1.0 is the default version.)

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

# Enable the saving of history records.

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

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

# Start the HTTP operation.

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

# Stop the HTTP operation after a period of time.

[AC] undo nqa schedule admin test

# Display the results of the HTTP operation.

[AC] display nqa result admin test

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

Destination IP address: 10.2.2.2

Send operation times: 1 Receive response times: 1

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

Square-Sum of round trip time: 4096

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

Extended results:

Packet loss in test: 0%

Failures due to timeout: 0

Failures due to disconnect: 0

Failures due to no connection: 0

Failures due to sequence error: 0

Failures due to internal error: 0

Failures due to other errors:

Packet(s) arrived late: 0

# Display the history records of the HTTP operation.

[AC] display nqa history admin test

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

Index Response Status Time

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

The output shows that AC takes 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 AC and 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 Device:

# Enable the NQA server and configure a listening service to listen on the IP address 10.2.2.2 and UDP port 9000.

<Device> system-view

[Device] nqa server enable

[Device] nqa server udp-echo 10.2.2.2 9000

4. Configure AC:

# Create a UDP jitter operation.

<AC> system-view

[AC] nqa entry admin test

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

# Configure 10.2.2.2 as the destination IP address and port 9000 as the destination port.

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

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

# Configure the operation to repeat at an interval of 1000 milliseconds.

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

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

# Start the UDP jitter operation.

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

# Stop the UDP jitter operation after a period of time.

[AC] undo nqa schedule admin test

# Display the results of the UDP jitter operation.

[AC] display nqa result admin test

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

Destination IP address: 10.2.2.2

Send operation times: 10 Receive response times: 10

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

Square-Sum of round trip time: 3235

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

Extended results:

Packet loss in test: 0%

Failures due to timeout: 0

Failures due to disconnect: 0

Failures due to no connection: 0

Failures due to sequence error: 0

Failures due to internal error: 0

Failures due to other errors: 0

Packet(s) arrived late: 0

UDP-jitter results:

RTT number: 10

Min positive SD: 4 Min positive DS: 1

Max positive SD: 21 Max positive DS: 28

Positive SD number: 5 Positive DS number: 4

Positive SD sum: 52 Positive DS sum: 38

Positive SD average: 10 Positive DS average: 10

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

Min negative SD: 1 Min negative DS: 6

Max negative SD: 13 Max negative DS: 22

Negative SD number: 4 Negative DS number: 5

Negative SD sum: 38 Negative DS sum: 52

Negative SD average: 10 Negative DS average: 10

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

One way results:

Max SD delay: 15 Max DS delay: 16

Min SD delay: 7 Min DS delay: 7

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

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

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

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

Lost packet(s) for unknown reason: 0

# Display the statistics of the UDP jitter operation.

[AC] display nqa statistics admin test

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

NO. : 1

Destination IP address: 10.2.2.2

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

Life time: 47 seconds

Send operation times: 410 Receive response times: 410

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

Square-Sum of round trip time: 206176

Extended results:

Packet loss in test: 0%

Failures due to timeout: 0

Failures due to disconnect: 0

Failures due to no connection: 0

Failures due to sequence error: 0

Failures due to internal error: 0

Failures due to other errors: 0

Packet(s) arrived late: 0

UDP-jitter results:

RTT number: 410

Min positive SD: 3 Min positive DS: 1

Max positive SD: 30 Max positive DS: 79

Positive SD number: 186 Positive DS number: 158

Positive SD sum: 2602 Positive DS sum: 1928

Positive SD average: 13 Positive DS average: 12

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

Min negative SD: 1 Min negative DS: 1

Max negative SD: 30 Max negative DS: 78

Negative SD number: 181 Negative DS number: 209

Negative SD sum: 181 Negative DS sum: 209

Negative SD average: 13 Negative DS average: 14

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

One way results:

Max SD delay: 46 Max DS delay: 46

Min SD delay: 7 Min DS delay: 7

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

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

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

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

Lost packet(s) for unknown reason: 0

SNMP operation configuration example

Network requirements

As shown in Figure 8, configure an SNMP operation to test the time it takes for the NQA client to get a value 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 SNMP agent (Device):

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

<Device> system-view

[Device] snmp-agent sys-info version all

[Device] snmp-agent community read public

[Device] snmp-agent community write private

4. Configure AC:

# Create an SNMP operation, and configure 10.2.2.2 as the destination IP address.

<AC> system-view

[AC] nqa entry admin test

[AC-nqa-admin-test] type snmp

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

# Enable the saving of history records.

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

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

# Start the SNMP operation.

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

# Stop the SNMP operation after a period of time.

[AC] undo nqa schedule admin test

# Display the results of the SNMP operation.

[AC] display nqa result admin test

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

Destination IP address: 10.2.2.2

Send operation times: 1 Receive response times: 1

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

Square-Sum of round trip time: 2500

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

Extended results:

Packet loss in test: 0%

Failures due to timeout: 0

Failures due to disconnect: 0

Failures due to no connection: 0

Failures due to sequence error: 0

Failures due to internal error: 0

Failures due to other errors: 0

Packet(s) arrived late: 0

# Display the history records of the SNMP operation.

[AC] display nqa history admin test

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

Index Response Status Time

1 2 Succeeded 2011-11-17 14:37:12.7

The output shows that AC takes 2 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 it takes for the NQA client to establish a TCP connection to the NQA server on Device B.

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 Device:

# Enable the NQA server, and configure a listening service to listen on the IP address 10.2.2.2 and TCP port 9000.

<Device> system-view

[Device] nqa server enable

[Device] nqa server tcp-connect 10.2.2.2 9000

4. Configure AC:

# Create a TCP operation.

<AC> system-view

[AC] nqa entry admin test

[AC-nqa-admin-test] type tcp

# Configure 10.2.2.2 as the destination IP address and port 9000 as the destination port.

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

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

# Enable the saving of history records.

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

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

# Start the TCP operation.

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

# Stop the TCP operation after a period of time.

[AC] undo nqa schedule admin test

# Display the results of the TCP operation.

[AC] display nqa result admin test

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

Destination IP address: 10.2.2.2

Send operation times: 1 Receive response times: 1

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

Square-Sum of round trip time: 169

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

Extended results:

Packet loss in test: 0%

Failures due to timeout: 0

Failures due to disconnect: 0

Failures due to no connection: 0

Failures due to sequence error: 0

Failures due to internal error: 0

Failures due to other errors: 0

Packet(s) arrived late: 0

# Display the history records of the TCP operation.

[AC] display nqa history admin test

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

Index Response Status Time

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

The output shows that AC takes 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 AC and 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 Device:

# Enable the NQA server, and configure a listening service to listen on the IP address 10.2.2.2 and UDP port 8000.

<Device> system-view

[Device] nqa server enable

[Device] nqa server udp-echo 10.2.2.2 8000

4. Configure AC:

# Create a UDP echo operation.

<AC> system-view

[AC] nqa entry admin test

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

# Configure 10.2.2.2 as the destination IP address and port 8000 as the destination port.

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

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

# Enable the saving of history records.

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

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

# Start the UDP echo operation.

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

# Stop the UDP echo operation after a period of time.

[AC] undo nqa schedule admin test

# Display the results of the UDP echo operation.

[AC] display nqa result admin test

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

Destination IP address: 10.2.2.2

Send operation times: 1 Receive response times: 1

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

Square-Sum of round trip time: 625

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

Extended results:

Packet loss in test: 0%

Failures due to timeout: 0

Failures due to disconnect: 0

Failures due to no connection: 0

Failures due to sequence error: 0

Failures due to internal error: 0

Failures due to other errors: 0

Packet(s) arrived late: 0

# Display the history records of the UDP echo operation.

[AC] display nqa history admin test

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

Index Response Status Time

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

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

NQA collaboration configuration example

Network requirements

As shown in Figure 11, configure a static route to AC 2 with Switch as the next hop on AC 1. Associate the static route, a track entry, and an NQA 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 AC 1, configure a unicast static route, and associate the static route with a track entry:

# Configure a static route, and associate the static route with track entry 1.

<AC1> system-view

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

3. On AC 1, create an NQA operation:

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

[AC1] nqa entry admin test

# Configure the NQA operation type as ICMP echo.

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

# Configure 10.2.1.1 as their destination IP address.

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

# Configure the operation to repeat at an interval of 100 milliseconds.

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

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

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

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

# Start the ICMP echo operation.

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

4. On AC 1, create the track entry:

# Create track entry 1, and associate it with reaction entry 1 of the ICMP echo operation (admin-test).

[AC 1] track 1 nqa entry admin test reaction 1

Verifying the configuration

# On AC 1, display information about all track entries.

[AC1] display track all

Track ID: 1

Status: Positive

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

Reference object:

NQA entry: admin test

Reaction: 1

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

[AC1] display ip routing-table

Routing Tables: Public

Destinations : 5 Routes : 5

Destination/Mask Proto Pre Cost NextHop Interface

10.1.1.0/24 Static 60 0 10.2.1.1 Vlan3

10.2.1.0/24 Direct 0 0 10.2.1.2 Vlan3

10.2.1.2/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

The 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.

<Switch> system-view

[Switch] interface vlan-interface 3

[Switch-Vlan-interface3] undo ip address

# On AC 1, display information about all track entries.

[AC1] display track all

Track ID: 1

Status: Negative

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

Reference object:

NQA entry: admin test

Reaction: 1

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

[AC1] display ip routing-table

Routing Tables: Public

Destinations : 4 Routes : 4

Destination/Mask Proto Pre Cost NextHop Interface

10.2.1.0/24 Direct 0 0 10.2.1.2 Vlan3

10.2.1.2/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

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

09-Network Management Configuration Guide

Configuring a TCP operation

Configuring a UDP echo operation

Introduction

Configuration prerequisites

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

Network requirements

Configuration procedure

Verifying the configuration

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