- Table of Contents
-
- 14-Network Management and Monitoring Command Reference
- 00-Preface
- 01-System maintenance and debugging commands
- 02-NQA commands
- 03-iNQA commands
- 04-iFIT commands
- 05-SRPM commands
- 06-NTP commands
- 07-PTP commands
- 08-Network synchronization commands
- 09-SNMP commands
- 10-RMON commands
- 11-NETCONF commands
- 12-CWMP commands
- 13-EAA commands
- 14-Process monitoring and maintenance commands
- 15-Sampler commands
- 16-Mirroring commands
- 17-NetStream commands
- 18-IPv6 NetStream commands
- 19-TCP connection trace commands
- 20-Performance management commands
- 21-Flow log commands
- 22-Information center commands
- 23-Packet capture commands
- 24-Flow monitor commands
- Related Documents
-
Title | Size | Download |
---|---|---|
02-NQA commands | 769.16 KB |
Contents
adjust-udp-checksum global enable (TWAMP Light client view)
display nqa twamp-light client
display nqa twamp-light client statistics
display nqa twamp-light client test-session reaction counters
one-way delay-measure global enable
operation (FTP operation view)
operation (HTTP/HTTPS operation view)
reaction checked-element { jitter-ds | jitter-sd }
reaction checked-element { owd-ds | owd-sd }
reaction checked-element icpif
reaction checked-element packet-loss
reaction checked-element probe-duration
reaction checked-element probe-fail (for trap)
reaction checked-element probe-fail (for trigger)
reaction checked-element two-way-delay
reaction checked-element two-way-jitter
reaction checked-element two-way-loss
reset nqa twamp-light statistics
source interface (ICMP echo/UDP tracert operation view)
start (TWAMP Light sender view)
stop (TWAMP Light sender view)
test-session (TWAMP Light client view)
adjust-udp-checksum global enable (TWAMP Light responder view)
display nqa twamp-light responder
test-session (TWAMP Light responder view)
display nqa twamp server global-information
display nqa twamp server session
NQA commands
NQA client commands
adjust-udp-checksum enable
Use adjust-udp-checksum enable to enable checksum field adjustment for test packets.
Use undo adjust-udp-checksum enable to disable checksum field adjustment for test packets.
Syntax
adjust-udp-checksum enable
undo adjust-udp-checksum enable
Default
Checksum field adjustment for test packets is disabled.
Views
TWAMP Light client-session view
Predefined user roles
network-admin
Usage guidelines
By default, the checksum value in TWAMP Light test packets is 0. With this command configured, Twamp Light will fill the calculated checksum value in the checksum field of test packets. Support for the checksum value varies by TWAMP Light reflectors. Enable checksum field adjustment for test sessions as required by the TWAMP Light reflector connected to the device.
Enable checksum field adjustment for test packets in either of following ways:
· Enable the feature globally. The feature will take effect on all sessions to be created in TWAMP Light client view, and will not affect existing sessions.
· Enable the feature in test session view. The feature will take effect only on the session to start.
This feature applies only to IPv6 packets.
Examples
# Enable checksum field adjustment for test packets.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] adjust-udp-checksum enable
Related commands
adjust-udp-checksum global enable
adjust-udp-checksum global enable (TWAMP Light client view)
Use adjust-udp-checksum global enable to enable checksum field adjustment globally for test packets.
Use undo adjust-udp-checksum global enable to disable checksum field adjustment globally for test packets.
Syntax
adjust-udp-checksum global enable
undo adjust-udp-checksum global enable
Default
Checksum field adjustment for test packets is disabled globally.
Views
TWAMP Light client view
Predefined user roles
network-admin
Usage guidelines
By default, the checksum value in TWAMP Light test packets is 0. With this command configured, Twamp Light will fill the calculated checksum value in the checksum field of test packets. Support for the checksum value varies by TWAMP Light reflectors. Enable checksum field adjustment for test sessions as required by the TWAMP Light reflector connected to the device.
Enable checksum field adjustment for test packets in either of following ways:
· Enable the feature globally. The feature will take effect on all sessions to be created in TWAMP Light client view, and will not affect existing sessions.
· Enable the feature in test session view. The feature will take effect only on the session to start.
This feature applies only to IPv6 packets.
Examples
# Enable checksum field adjustment globally for test packets.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] adjust-udp-checksum global enable
Related commands
adjust-udp-checksum enable
advantage-factor
Use advantage-factor to set the advantage factor to be used for calculating Mean Opinion Scores (MOS) and Calculated Planning Impairment Factor (ICPIF) values.
Use undo advantage-factor to restore the default.
Syntax
advantage-factor factor
undo advantage-factor
Default
The advantage factor is 0.
Views
Voice operation view
Predefined user roles
network-admin
Parameters
factor: Specifies the advantage factor in the range of 0 to 20.
Usage guidelines
The evaluation of voice quality depends on users' tolerance for voice quality. For users with higher tolerance for voice quality, use the advantage-factor command to set an advantage factor. When the system calculates the ICPIF value, it subtracts the advantage factor to modify ICPIF and MOS values for voice quality evaluation.
Examples
# Set the advantage factor to 10 for the voice operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type voice
[Sysname-nqa-admin-test-voice] advantage-factor 10
allowed-frame-loss
Use allowed-frame-loss to set the frame loss ratio (FLR) threshold.
Use undo allowed-frame-loss to restore the default.
Syntax
allowed-frame-loss count
undo allowed-frame-loss
Default
The FLR threshold is not set.
Views
Y.1564 operation view
Predefined user roles
network-admin
Parameters
count: Specifies the maximum number of frames lost over 100000 sent frames. The value range is 0 to 100000.
Usage guidelines
If the FLR during a test in the Y.1564 operation exceeds the FLR threshold, the test fails and the Y.1564 operation is terminated.
Examples
# Set the FLR threshold to 1/1000 for the Y.1564 operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type y1564
[Sysname-nqa-admin-test-y1564] allowed-frame-loss 100
allowed-jitter
Use allowed-frame-loss to set the frame delay variation (FDV) threshold.
Use undo allowed-jitter to restore the default.
Syntax
allowed-jitter jitter
undo allowed-jitter
Default
The FDV threshold is not set.
Views
Y.1564 operation view
Predefined user roles
network-admin
Parameters
jitter: Specifies the FDV threshold in microseconds. The value range is 1 to 10000000.
Usage guidelines
If the FDV calculated during a test in the Y.1564 operation exceeds the FDV threshold, the test fails and the Y.1564 operation is terminated.
Examples
# Set the FDV threshold to 10000 microseconds for the Y.1564 operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type y1564
[Sysname-nqa-admin-test-y1564] allowed-jitter 10000
allowed-loss-ratio
Use allowed-loss-ratio to set the maximum allowed frame loss ratio.
Use undo allowed-loss-ratio to restore the default.
Syntax
allowed-loss-ratio ratio
undo allowed-loss-ratio
Default
The maximum allowed frame loss ratio is 1/10000.
Views
Throughput operation view
Predefined user roles
network-admin
Parameters
ratio: Specifies the maximum allowed frame loss ratio, 1/10000 or 1/1000000000.
Usage guidelines
# Set the maximum allowed frame loss ratio to 1/1000000000 for the throughput operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type throughput
[Sysname-nqa-admin-test-throughput] allowed-loss-ratio 1/1000000000
allowed-transfer-delay
Use allowed-transfer-delay to set the frame transfer delay (FTD) threshold.
Use undo allowed-transfer-delay to restore the default.
Syntax
allowed-transfer-delay delay
undo allowed-transfer-delay
Default
The FTD threshold is not set.
Views
Y.1564 operation view
Predefined user roles
network-admin
Parameters
delay: Specifies the FTD threshold in microseconds. The value range is 1 to 10000000.
Usage guidelines
If the FTD calculated during a test in the Y.1564 operation exceeds the FTD threshold, the test fails and the Y.1564 operation is terminated.
Examples
# Set the FTD threshold to 10000 microseconds for the Y.1564 operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type y1564
[Sysname-nqa-admin-test-y1564] allowed-transfer-delay 10000
bandwidth
Use bandwidth to specify the committed information rate (CIR) and peak information rate (PIR).
Use undo bandwidth to restore the default.
Syntax
bandwidth cir cir-value [ pir pir-value ]
undo bandwidth
Default
The CIR and PIR are not specified.
Views
Y.1564 operation view
Predefined user roles
network-admin
Parameters
cir-value: Specifies the CIR in kbps. The value range for this argument is 8 to 32000000.
pir-value: Specifies the PIR in kbps. The value range for this argument is 8 to 32000000. If you do not specify the PIR, no PIR test will be performed.
Usage guidelines
Use this command to specify the CIR and PIR to be tested in a Y.1564 operation.
For the CIR test to run correctly, the specified CIR must meet the following requirement:
(CIR*1000) / (frame-size + 20) / step count > 1.
The frame-size is the test frame size configured by using the frame-size command, and step count is the step count configured by using the cir-test enable step-count count command.
Examples
# Set the CIR to 2000 kbps and PIR to 3000 kbps for the Y.1564 operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type y1564
[Sysname-nqa-admin-test-y1564] bandwidth cir 2000 pir 3000
bind nqa-entry
Use bind nqa-entry to bind an operation to an operation group.
Use undo bind nqa-entry to remove an operation from an operation group.
Syntax
bind nqa-entry admin-name operation-tag
undo bind nqa-entry admin-name operation-tag
Default
An operation group does not contain any operations.
Views
Y.1564 operation group view
RFC2544 operation group view
Predefined user roles
network-admin
Parameters
admin-name operation-tag: Specifies a Y.1564 operation by its administrator name and operation tag. The admin-name argument represents the name of the administrator who creates the operation. The operation-tag argument represents the operation tag. Each of the arguments is a case-insensitive string of 1 to 32 characters that cannot contain hyphens (-).
Usage guidelines
You cannot bind an operation to or remove an operation from an active operation group.
Examples
# Bind the Y.1564 operation with administrator name admin and operation tag test to Y.1564 operation group test.
<Sysname> system-view
[Sysname] nqa y1564 group test
[Sysname-nqa-y1564group-test] bind nqa-entry admin test
Related commands
nqa y1564 group
nqa rfc2544 group
cir-test enable
Use cir-test enable to enable the CIR test.
Use undo cir-test enable to disable the CIR test.
Syntax
cir-test enable [ step-count count ] [ step-duration duration ]
undo cir-test enable
Default
The CIR test is enabled.
Views
Y.1564 operation view
Predefined user roles
network-admin
Parameters
step-count count: Specify the number of steps in the CIR test. The value range is 1 to 1000, and the default is 1.
step-duration duration: Specify the duration of each step in seconds. The value range is 1 to 60, and the default is 3.
Usage guidelines
The CIR test uses a step load test method to gradually reach the CIR configured by using the bandwidth command. Test frames are transmitted at an initial rate of CIR/N, where N is the step count configured by using the step-count count option. The frame transmission rate is increased by CIR/N per step until the CIR is reached.
For a CIR test with a step count of 1, test frames are transmitted at once to the configured CIR.
For the CIR test to run correctly, the specified CIR must meet the following requirement:
(CIR*1000) / (frame-size + 20) / step count > 1.
The frame-size is the test frame size configured by using the frame-size command.
Examples
# Enable the CIR test in the Y.1564 operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type y1564
[Sysname-nqa-admin-test-y1564] cir-test enable
Related commands
bandwidth
codec-type
Use codec-type to configure the codec type for the voice operation.
Use undo codec-type to restore the default.
Syntax
codec-type { g711a | g711u | g729a }
undo codec-type
Default
The codec type for the voice operation is G.711 A-law.
Views
Voice operation view
Predefined user roles
network-admin
Parameters
g711a: Specifies the G.711 A-law codec type.
g711u: Specifies the G.711 µ-law codec type
g729a: Specifies the G.729 A-law codec type.
Examples
# Set the codec type to g729a for the voice operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type voice
[Sysname-nqa-admin-test-voice] codec-type g729a
color-aware-mode enable
Use color-aware-mode enable to enable the color-aware mode.
Use undo color-aware-mode enable to disable the color-aware mode.
Syntax
color-aware-mode enable [ { 8021p | dscp } green value1 [ to value2 ] yellow value1 [ to value2 ] ]
undo color-aware-mode enable
Default
The color-aware mode is disabled.
Views
Y.1564 operation view
Predefined user roles
network-admin
Parameters
8021p: Colors the probe frames according to the 802.1p priority value. You must specify the 802.1p priority in a Layer 2 network.
dscp: Colors the probe frames according to the DSCP precedence value. You must specify the DSCP precedence in a Layer 3 network.
green: Specifies the green color.
yellow: Specifies the yellow color.
value1 to value2: Specifies the priority value range. The value range is 0 to 7 for 802.1p priority, and 0 to 63 for the DSCP precedence. The value2 value must be higher than the value1 value. For forwarding based on MPLS labels, the device automatically converts the 802.1p priority or DSCP precedence into an EXP value. Make sure the EXP values converted from the 802.1p priority and DSCP precedence are different.
Usage guidelines
To test the traffic service quality in a congested Layer 2 network, you can use this command to specify colors for probe frames of different priorities.
This command only takes effect for the PIR test and traffic policing test.
· If color-aware mode is disabled, the device sends probe frames at a fixed rate.
· If color-aware mode is enabled, the device sends probe packets at different rates according to the frame priorities.
For more information about the mapping between 802.1p or DSCP priorities and colors, see configuring priority mapping in ACL and QoS Configuration Guide.
Examples
# Enable the color-aware mode.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type y1564
[Sysname-nqa-admin-test-y1564] color-aware-mode enable 8021p green 1 to 4 yellow 5
Related commands
priority 8021p
community read
Use community read to specify the community name for the SNMP operation.
Use undo community read to restore the default.
Syntax
community read { cipher | simple } community-name
undo community read
Default
The SNMP operation uses community name public.
Views
SNMP operation view
SNMP template view
Predefined user roles
network-admin
Parameters
cipher: Specifies a community name in encrypted form.
simple: Specifies a community name in plaintext form. For security purposes, the community name specified in plaintext form will be stored in encrypted form.
community-name: Specifies the community name. Its plaintext form is a case-sensitive string of 1 to 32 characters. Its encrypted form is a case-sensitive string of 33 to 73 characters.
Usage guidelines
You must specify the community name for the SNMP operation when both of the following conditions exist:
· The SNMP operation uses the SNMPv1 or SNMPv2c agent.
· The SNMPv1 or SNMPv2c agent is configured with a read-only or read-write community name.
The specified community name must be the same as the community name configured on the SNMP agent.
The community name configuration is not required if the SNMP operation uses the SNMPv3 agent.
For more information about SNMP, see "Configuring SNMP."
Examples
# Specify readaccess as the community name for the SNMP operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type snmp
[Sysname-nqa-admin-test-snmp] community read simple readaccess
data-fill
Use data-fill to configure the payload fill string for probe packets.
Use undo data-fill to restore the default.
Syntax
data-fill string
undo data-fill
Default
The default payload fill string is the hexadecimal string 00010203040506070809.
Views
ICMP/UDP echo operation view
Path jitter/UDP jitter/voice/ICMP jitter operation view
ICMP/TCP/UDP template view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
string: Specifies a case-sensitive string of 1 to 200 characters.
Usage guidelines
If the payload length is smaller than the string length, only the first part of the string is filled. For example, if you configure the string as abcd and set the payload size to 3 bytes, abc is filled.
If the payload length is greater than the string length, the system fills the payload with the string cyclically until the payload is full. For example, if you configure the string as abcd and set the payload size to 6 bytes, abcdab is filled.
How the string is filled depends on the operation type.
· For the ICMP echo operation, the string fills the whole payload of an ICMP echo request.
· For the UDP echo operation, the first five bytes in the payload of a UDP packet are for special purpose. The string fills the remaining part of payload.
· For the UDP jitter operation, the first 68 bytes in the payload of a UDP packet are for special purpose. The string fills the remaining part of the payload.
· For the voice operation, the first 16 bytes in the payload of a UDP packet are for special purpose. The string fills the remaining part of the payload.
· For the path jitter operation, the first four bytes in the payload of an ICMP echo request are for special purpose. The string fills the remaining part of payload.
· For the ICMP jitter operation, the first 20 bytes in the payload of an ICMP packet are for special purpose. The string fills the remaining part of payload. Additionally, an ICMP jitter operation in timestamp packet mode does not support this command.
If you execute this command and the hex-data-fill command multiple times, the most recent configuration takes effect.
Examples
# Specify abcd as the payload fill string for ICMP echo requests.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] data-fill abcd
# In TCP template view, specify abcd as the payload fill string for probe packets.
<Sysname> system-view
[Sysname] nqa template tcp tcptplt
[Sysname-nqatplt-tcp-tcptplt] data-fill abcd
Related commands
hex-data-fill
data-size
Use data-size to set the payload size for each probe packet.
Use undo data-size to restore the default.
Syntax
data-size size
undo data-size
Default
The default payload size of a probe packet for different operations is described in Table 1.
Table 1 Default payload size of a probe packet
Operation type |
Codec type |
Default size (bytes) |
ICMP echo |
N/A |
100 |
ICMP-jitter |
N/A |
20 |
UDP echo |
N/A |
100 |
UDP jitter |
N/A |
100 |
UDP tracert |
N/A |
100 |
Path jitter |
N/A |
100 |
Voice |
G.711 A-law |
172 |
Voice |
G.711 µ-law |
172 |
Voice |
G.729 A-law |
32 |
TWAMP Light |
N/A |
142 |
Views
ICMP/UDP echo operation view
UDP tracert operation view
Path jitter/UDP jitter/voice/ICMP jitter operation view
ICMP/UDP template view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
size: Specifies the payload size in bytes. The value ranges vary by operation type and destination address type.
· For NQA operations that use IPv4 destination addresses, the value ranges are as follows:
¡ 20 to 65507 for ICMP echo, ICMP jitter, UDP echo, and UDP tracert operations.
¡ 68 to 65507 for UDP jitter and path jitter operations.
¡ 16 to 65507 for voice operations.
· For NQA operations that use IPv6 destination addresses, the value ranges are as follows:
¡ 20 to 65503 for UDP echo operations.
¡ 68 to 65503 for UDP jitter operations.
¡ 20 to 65487 for ICMP echo, ICMP jitter, and UDP tracert operations.
¡ 68 to 65487 for path jitter operations.
¡ 16 to 65487 for voice operations.
· 44 to 1518 for TWAMP Light tests.
Usage guidelines
In TWAMP Light tests and UDP jitter operations, the payload size cannot be larger than the MTU size of any interface on the test link.
Examples
# Set the payload size to 80 bytes for each ICMP echo request.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] data-size 80
# In ICMP template view, set the payload size to 80 bytes for each probe packet.
<Sysname> system-view
[Sysname] nqa template icmp icmptplt
[Sysname-nqatplt-icmp-icmptplt] data-size 80
description
Use description to configure a description for an NQA operation, such as the operation type or purpose.
Use undo description to restore the default.
Syntax
description text
undo description
Default
No description is configured for an NQA operation.
Views
Any NQA operation view
Any NQA template view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
text: Specifies a description, a case-sensitive string of 1 to 200 characters.
Examples
# Configure the description as icmp-probe for the ICMP echo operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] description icmp-probe
# In ICMP template view, configure the description as icmp-probe for the NQA operation.
<Sysname> system-view
[Sysname] nqa template icmp icmptplt
[Sysname-nqatplt-icmp-icmptplt] description icmp-probe
destination host
Use destination host to configure the destination host name for the operation.
Use undo destination host to restore the default.
Syntax
destination host host-name
undo destination host
Default
No destination host name is configured for the operation.
Views
UDP tracert operation view
Predefined user roles
network-admin
Parameters
host-name: Specifies the destination host name, a case-sensitive string of 1 to 254 characters. The host name can contain letters, digits, hyphens (-), underscores (_), and dots (.), but consecutive dots (.) are not allowed. If the host name is a series of dot-separated labels, each label can contain a maximum of 63 characters.
Usage guidelines
To configure the destination IP address for probe packets, use the destination ip or destination ipv6 command.
Examples
# Specify www.test.com as the destination host name for the UDP tracert operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-tracert
[Sysname-nqa-admin-test-udp-tracert] destination host www.test.com
destination ip
Use destination ip to configure the destination IPv4 address for the operation.
Use undo destination ip to restore the default.
Syntax
Y.1564 operations:
destination ip ipv4-address1 [ to ipv4-address2 ]
undo destination ip
Other operations:
destination ip ipv4-address
undo destination ip
Default
No destination IPv4 address is configured for an operation.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/SNMP operation view
UDP tracert operation view
ICMP jitter/path jitter/UDP jitter/voice operation view
Frame loss/latency/throughput/Y.1564 operation view
ARP/DNS/ICMP/IMAP/POP3/RADIUS/SMTP/SNMP/SSL/TCP/TCP half open/UDP template view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
ipv4-address: Specifies the destination IPv4 address.
ipv4-address1 to ipv4-address2: Specifies a destination IPv4 address range. The ipv4-address2 must be higher than the ipv4-address1. Between the two destination IPv4 addresses, only one octet difference is allowed and the value difference cannot exceed 127.
Usage guidelines
For path quality analysis operations and Y.1564 operations to start successfully, configure the source and destination IP addresses as follows:
· In a Layer 2 Ethernet, Layer 3 Ethernet, L2VPN, or L3VPN network, configure both source and destination IP addresses.
· In other networks, configure both of them or none of them. If they are configured, make sure the source and destination IP addresses are of the same IP version.
Examples
# Specify 10.1.1.2 as the destination IPv4 address for the ICMP echo operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] destination ip 10.1.1.2
# In ICMP template view, specify 10.1.1.2 as the destination IPv4 address for the ICMP echo operation.
<Sysname> system-view
[Sysname] nqa template icmp icmptplt
[Sysname-nqatplt-icmp-icmptplt] destination ip 10.1.1.2
# In TWAMP Light client-session view, specify 10.1.1.2 as the destination IPv4 address for the TWAMP Light test.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] destination ip 10.1.1.2
destination ipv6
Use destination ipv6 to configure the destination IPv6 address for the operation.
Use undo destination ipv6 to restore the default.
Syntax
Y.1564 operations:
destination ipv6 ipv6-address1 [ to ipv6-address2 ]
undo destination ipv6
Other operations:
destination ipv6 ipv6-address
undo destination ipv6
Default
No destination IPv6 address is configured for an operation.
Views
ICMP echo/TCP/UDP echo operation view
UDP jitter operation view
ICMP jitter/DLSw/DNS/SNMP/UDP tracert/path jitter/voice operation view
Frame loss/latency/throughput/Y.1564 operation view
DNS/ICMP/IMAP/POP3/RADIUS/SMTP/SNMP/SSL/TCP/TCP half open/UDP template view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies the destination IPv6 address. IPv6 link-local addresses are not supported.
ipv6-address1 to ipv6-address2: Specifies a destination IPv6 address range. The ipv6-address2 must be higher than the ipv6-address1. Between the two destination IPv6 addresses, only one octet difference is allowed and the value difference cannot exceed 127.
Usage guidelines
An MPLS simulation-enabled UDP jitter operation cannot use an IPv6 address as the destination address.
For path quality analysis operations and Y.1564 operations to start successfully, configure the source and destination IP addresses as follows:
· In a Layer 2 Ethernet, Layer 3 Ethernet, L2VPN, or L3VPN network, configure both source and destination IP addresses.
· In other networks, configure both of them or none of them. If they are configured, make sure the source and destination IP addresses are of the same IP version.
Examples
# In ICMP template view, specify 1::2 as the destination IPv6 address for the ICMP echo operation.
<Sysname> system-view
[Sysname] nqa template icmp icmptplt
[Sysname-nqatplt-icmp-icmptplt] destination ipv6 1::2
# In TWAMP Light client-session view, specify 1::2 as the destination IPv6 address for the TWAMP Light test.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] destination ipv6 1::2
destination mac
Use destination mac to specify the destination MAC address for the operation.
Use undo destination mac to restore the default.
Syntax
Frame loss/latency/throughput/TWAMP Light operations:
destination mac mac-address
undo destination mac
Y.1564 operations:
destination mac mac-address1 [ to mac-address2 ]
undo destination mac
Default
For the frame loss, latency, throughput, or Y.1564 operation, the destination MAC address is 0023-8900-0001.
For the TWAMP Light test, no destination MAC address is specified.
Views
Frame loss/latency/throughput/Y.1564 operation view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
mac-address: Specifies the destination MAC address in the format H-H-H. For example, to use 000f-00e2-0001 as the destination MAC address, set this argument to f-e2-1.
mac-address1 to mac-address2: Specifies a destination MAC address range. The mac-address2 must be higher than the mac-address1. Between the two destination MAC addresses, only one octet difference is allowed and the value difference cannot exceed 127.
Examples
# Specify 0001-0001-0002 as the destination MAC address for the throughput operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type throughput
[Sysname-nqa-admin-test-throughput] destination mac 1-1-2
# In TWAMP Light client-session view, specify 0001-0001-0002 as the destination MAC address for the TWAMP Light test.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] destination mac 1-1-2
destination port
Use destination port to configure the destination port number for the operation.
Use undo destination port to restore the default.
Syntax
Y.1564 operations:
destination port port-number1 [ to port-number2 ]
undo destination port
Other operations:
destination port port-number
undo destination port
Default
The destination port numbers for the following operations are as follows:
· 33434 for the UDP tracert operation.
· 161 for the SNMP operation.
· 7 for the frame loss, latency, and throughput operations.
The destination port numbers for the operations that use the following NQA templates are:
· 53 for the DNS template.
· 143 for the IMAP template.
· 110 for the POP3 template.
· 1812 for the RADIUS template.
· 25 for the SMTP template.
· 161 for the SNMP template.
No destination port number is configured for other types of operations.
Views
TCP/UDP echo/SNMP operation view
UDP tracert operation view
UDP jitter/voice operation view
Frame loss/latency/throughput/Y.1564 operation view
DNS/IMAP/POP3/RADIUS/SMTP/SNMP/SSL/TCP/UDP template view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
port-number: Specifies the destination port number, in the range of 1 to 65535.
port-number1 to port-number2: Specifies the destination port number range. The port-number2 must be greater than the port-number1. Between the two destination port numbers, only one octet difference is allowed and the value difference cannot exceed 127.
Examples
# Set the destination port number to 9000 for the UDP echo operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-echo
[Sysname-nqa-admin-test-udp-echo] destination port 9000
# In TCP template view, set the destination port number to 9000 for the NQA operation.
<Sysname> system-view
[Sysname] nqa template tcp tcptplt
[Sysname-nqatplt-tcp-tcptplt] destination port 9000
# In TWAMP Light client-session view, set the destination port number to 9000 for the TWAMP Light test.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] destination port 9000
display nqa history
Use display nqa history to display the history records of NQA operations.
Syntax
display nqa history [ admin-name operation-tag ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
admin-name operation-tag: Specifies an NQA operation by its administrator name and operation tag. The admin-name argument represents the name of the administrator who creates the NQA operation. The operation-tag argument represents the operation tag. Each of the arguments is a case-insensitive string of 1 to 32 characters that cannot contain hyphens (-). If you do not specify an NQA operation, the command displays the history records of all NQA operations.
Usage guidelines
The display nqa history command does not display the results or statistics of the following operations:
· Frame loss.
· ICMP jitter.
· Latency.
· Path jitter.
· Throughput.
· UDP jitter.
· Voice.
To view the results or statistics of the ICMP jitter, path jitter, UDP jitter, and voice operations, use the display nqa result or display nqa statistics command.
To view the results of the frame loss, latency, and throughput operations, use the display nqa result command.
Examples
# Display the history records of the UDP tracert operation with administrator name administrator and operation tag tracert.
<Sysname> display nqa history administrator tracert
NQA entry (admin administrator, tag tracert) history records:
Index TTL Response Hop IP Status Time
1 2 328 4.1.1.1 Succeeded 2013-09-09 14:46:06.2
1 2 328 4.1.1.1 Succeeded 2013-09-09 14:46:05.2
1 2 328 4.1.1.1 Succeeded 2013-09-09 14:46:04.2
1 1 328 3.1.1.2 Succeeded 2013-09-09 14:46:03.2
1 1 328 3.1.1.1 Succeeded 2013-09-09 14:46:02.2
1 1 328 3.1.1.1 Succeeded 2013-09-09 14:46:01.2
# Display the history records of the NQA operation with administrator name administrator and operation tag test.
<Sysname> display nqa history administrator test
NQA entry (admin administrator, tag test) history records:
Index Response Status Time
10 329 Succeeded 2011-04-29 20:54:26.5
9 344 Succeeded 2011-04-29 20:54:26.2
8 328 Succeeded 2011-04-29 20:54:25.8
7 328 Succeeded 2011-04-29 20:54:25.5
6 328 Succeeded 2011-04-29 20:54:25.1
5 328 Succeeded 2011-04-29 20:54:24.8
4 328 Succeeded 2011-04-29 20:54:24.5
3 328 Succeeded 2011-04-29 20:54:24.1
2 328 Succeeded 2011-04-29 20:54:23.8
1 328 Succeeded 2011-04-29 20:54:23.4
Table 2 Command output
Field |
Description |
Index |
History record ID. The history records in one UDP tracert operation have the same ID. |
TTL |
If the routing table bypass feature is not enabled in the operation, this field displays the TTL value in the probe packet. If the routing table bypass feature is enabled, the value of this field varies by the init-ttl command. However, the actual TTL value in the probe packet is fixed at 1. |
Response |
Round-trip time if the operation succeeds, timeout time upon timeout, or 0 if the operation cannot be completed, in milliseconds. |
Hop IP |
IP address of the node that sent the reply packet. |
Status |
Status of the operation result: · Succeeded. · Unknown error. (This state triggers the Track state switchover in NQA-Track collaboration.) · Internal error. (This state does not trigger the Track state switchover in NQA-Track collaboration.) · Timeout. (This state triggers the Track state switchover in NQA-Track collaboration.) |
Time |
Time when the operation was completed. |
display nqa reaction counters
Use display nqa reaction counters to display the current monitoring results of reaction entries.
Syntax
display nqa reaction counters [ admin-name operation-tag [ item-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
admin-name operation-tag: Specifies an NQA operation by its administrator name and operation tag. The admin-name argument represents the name of the administrator who creates the NQA operation. The operation-tag argument represents the operation tag. Each of the arguments is a case-insensitive string of 1 to 32 characters that cannot contain hyphens (-). If you do not specify an NQA operation, the command displays the current monitoring results of reaction entries for all NQA operations.
item-number: Specifies a reaction entry by its ID in the range of 1 to 10. If you do not specify a reaction entry, the command displays the results of all reaction entries.
Usage guidelines
The result fields display hyphens (-) in one of the following conditions:
· The threshold type is the average value.
· The monitored performance metric is ICPIF or MOS of the voice operation.
The monitoring results of an operation are accumulated, and are not cleared after the operation completes.
Examples
# Display the monitoring results of all reaction entries of the ICMP echo operation with administrator name admin and operation tag test.
<Sysname> display nqa reaction counters admin test
NQA entry (admin admin, tag test) reaction counters:
Index Checked Element Threshold Type Checked Num Over-threshold Num
1 probe-duration accumulate 12 4
2 probe-duration average - -
3 probe-duration consecutive 160 56
4 probe-fail accumulate 12 0
5 probe-fail consecutive 162 2
Table 3 Command output
Field |
Description |
Index |
ID of a reaction entry. |
Checked Element |
Monitored performance metric. The available performance metrics vary by NQA operation type. For more information, see Table 4 and Table 5. |
Threshold Type |
Threshold type. |
Checked Num |
Number of targets that have been monitored for data collection. |
Over-threshold Num |
Number of threshold violations. |
Monitored performance metric |
Threshold type |
Collect data in |
Checked Num |
Over-threshold Num |
probe-duration |
accumulate |
Probes after the operation starts. |
Number of completed probes. |
Number of probes with duration exceeding the threshold. |
average |
N/A |
N/A |
N/A |
|
consecutive |
Probes after the operation starts. |
Number of completed probes. |
Number of probes with duration exceeding the threshold. |
|
probe-fail |
accumulate |
Probes after the operation starts. |
Number of completed probes. |
Number of probe failures. |
consecutive |
Probes after the operation starts. |
Number of completed probes. |
Number of probe failures. |
Table 5 Monitored performance metrics for ICMP jitter/UDP jitter/voice operations
Monitored performance metric |
Threshold type |
Collect data in |
Checked Num |
Over-threshold Num |
RTT |
accumulate |
Packets sent after the operation starts. |
Number of sent packets. |
Number of packets with round-trip time exceeding threshold. |
average |
N/A |
N/A |
N/A |
|
jitter-DS/jitter-SD |
accumulate |
Packets sent after the operation starts. |
Number of sent packets. |
Number of packets with the one-way jitter exceeding the threshold. |
average |
N/A |
N/A |
N/A |
|
OWD-DS/OWD-SD |
N/A |
Packets sent after the operation starts. |
Number of sent packets. |
Number of packets with the one-way delay exceeding the threshold. |
packet-loss |
accumulate |
Packets sent after the operation starts. |
Number of sent packets. |
Total packet loss. |
ICPIF/MOS (available only for the voice operation) |
N/A |
N/A |
N/A |
N/A |
display nqa result
Use display nqa result to display the most recent result of an NQA operation.
Syntax
display nqa result [ admin-name operation-tag ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
admin-name operation-tag: Specifies an NQA operation by its administrator name and operation tag. The admin-name argument represents the name of the administrator who creates the NQA operation. The operation-tag argument represents the operation tag. Each of the arguments is a case-insensitive string of 1 to 32 characters that cannot contain hyphens (-). If you do not specify an NQA operation, the command displays the most recent results of all NQA operations.
Examples
# Display the most recent result of the TCP operation with administrator name admin and operation tag test.
<Sysname> 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: 35/35/35
Square-Sum of round trip time: 1225
Last succeeded probe time: 2011-05-29 10:50:33.2
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 most recent result of the ICMP jitter operation with administrator name admin and operation tag test.
<Sysname> display nqa result admin test
NQA entry (admin admin, tag test) test results:
Send operation times: 10 Receive response times: 10
Min/Max/Average round trip time: 1/2/1
Square-Sum of round trip time: 13
Last packet received time: 2015-03-09 17:40:29.8
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: 0 Min positive DS: 0
Max positive SD: 0 Max positive DS: 0
Positive SD number: 0 Positive DS number: 0
Positive SD sum: 0 Positive DS sum: 0
Positive SD average: 0 Positive DS average: 0
Positive SD square-sum: 0 Positive DS square-sum: 0
Min negative SD: 1 Min negative DS: 2
Max negative SD: 1 Max negative DS: 2
Negative SD number: 1 Negative DS number: 1
Negative SD sum: 1 Negative DS sum: 2
Negative SD average: 1 Negative DS average: 2
Negative SD square-sum: 1 Negative DS square-sum: 4
SD average: 1 DS average: 2
One way results:
Max SD delay: 1 Max DS delay: 2
Min SD delay: 1 Min DS delay: 2
Number of SD delay: 1 Number of DS delay: 1
Sum of SD delay: 1 Sum of DS delay: 2
Square-Sum of SD delay: 1 Square-Sum of DS delay: 4
Lost packets for unknown reason: 0
# Display the most recent result of the UDP jitter operation with administrator name admin and operation tag test.
<Sysname> display nqa result admin test
NQA entry (admin admin, tag test) test results:
Send operation times: 10 Receive response times: 10
Min/Max/Average round trip time: 15/46/26
Square-Sum of round trip time: 8103
Last packet received time: 2011-05-29 10:56:38.7
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: 8 Min positive DS: 8
Max positive SD: 18 Max positive DS: 8
Positive SD number: 5 Positive DS number: 2
Positive SD sum: 75 Positive DS sum: 32
Positive SD average: 15 Positive DS average: 16
Positive SD square-sum: 1189 Positive DS square-sum: 640
Min negative SD: 8 Min negative DS: 1
Max negative SD: 24 Max negative DS: 30
Negative SD number: 4 Negative DS number: 7
Negative SD sum: 56 Negative DS sum: 99
Negative SD average: 14 Negative DS average: 14
Negative SD square-sum: 946 Negative DS square-sum: 1495
SD average: 14 DS average: 14
One way results:
Max SD delay: 22 Max DS delay: 23
Min SD delay: 7 Min DS delay: 7
Number of SD delay: 10 Number of DS delay: 10
Sum of SD delay: 125 Sum of DS delay: 132
Square-Sum of SD delay: 1805 Square-Sum of DS delay: 1988
SD lost packets: 0 DS lost packets: 0
Lost packets for unknown reason: 0
# Display the most recent result of the voice operation with administrator name admin and operation tag test.
<Sysname> display nqa result admin test
NQA entry (admin admin, tag test) test results:
Send operation times: 1000 Receive response times: 0
Min/Max/Average round trip time: 0/0/0
Square-Sum of round trip time: 0
Last packet received time: 0-00-00 00:00:00.0
Extended results:
Packet loss ratio: 100%
Failures due to timeout: 1000
Failures due to internal error: 0
Failures due to other errors: 0
Packets out of sequence: 0
Packets arrived late: 0
Voice results:
RTT number: 0
Min positive SD: 0 Min positive DS: 0
Max positive SD: 0 Max positive DS: 0
Positive SD number: 0 Positive DS number: 0
Positive SD sum: 0 Positive DS sum: 0
Positive SD average: 0 Positive DS average: 0
Positive SD square-sum: 0 Positive DS square-sum: 0
Min negative SD: 0 Min negative DS: 0
Max negative SD: 0 Max negative DS: 0
Negative SD number: 0 Negative DS number: 0
Negative SD sum: 0 Negative DS sum: 0
Negative SD average: 0 Negative DS average: 0
Negative SD square-sum: 0 Negative DS square-sum: 0
SD average: 0 DS average: 0
One way results:
Max SD delay: 0 Max DS delay: 0
Min SD delay: 0 Min DS delay: 0
Number of SD delay: 0 Number of DS delay: 0
Sum of SD delay: 0 Sum of DS delay: 0
Square-Sum of SD delay: 0 Square-Sum of DS delay: 0
SD lost packets: 0 DS lost packets: 0
Lost packets for unknown reason: 1000
Voice scores:
MOS value: 0.99 ICPIF value: 87
# Display the most recent result of the path jitter operation with administrator name admin and operation tag test.
<Sysname> display nqa result admin test
NQA entry (admin admin, tag test) test results:
Hop IP 192.168.40.210
Basic Results:
Send operation times: 10
Receive response times: 10
Min/Max/Average round trip time: 1/1/1
Square-Sum of round trip time: 10
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
Path-Jitter Results:
Jitter number: 9
Min/Max/Average jitter: 0/0/0
Positive jitter number: 0
Min/Max/Average positive jitter: 0/0/0
Sum/Square-Sum positive jitter: 0/0
Negative jitter number: 0
Min/Max/Average negative jitter: 0/0/0
Sum/Square-Sum negative jitter: 0/0
Hop IP 192.168.50.209
Basic Results:
Send operation times: 10
Receive response times: 10
Min/Max/Average round trip time: 1/1/1
Square-Sum of round trip time: 10
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
Path-Jitter Results:
Jitter number: 9
Min/Max/Average jitter: 0/0/0
Positive jitter number: 0
Min/Max/Average positive jitter: 0/0/0
Sum/Square-Sum positive jitter: 0/0
Negative jitter number: 0
Min/Max/Average negative jitter: 0/0/0
Sum/Square-Sum negative jitter: 0/0
# Display the most recent result of the UDP tracert operation with administrator name admin and operation tag test.
<Sysname> display nqa result admin test
NQA entry (admin admin, tag test) test results:
Send operation times: 6 Receive response times: 6
Min/Max/Average round trip time: 35/35/35
Square-Sum of round trip time: 1225
Last succeeded probe time: 2013-09-09 14:23:24.5
Extended results:
Packet loss ratio: 0%
Failures due to timeout: 0
Failures due to internal error: 0
Failures due to other errors: 0
UDP-tracert results:
TTL Hop IP Time
1 3.1.1.1 2013-09-09 14:23:24.5
2 4.1.1.1 2013-09-09 14:23:24.5
# Display the most recent result of the Y.1564 operation with administrator name admin and operation tag test.
<Sysname> display nqa result admin test
NQA entry (admin admin, tag test) test results:
Status : Succeeded
Last test : Service performance test
Estimated total time : 6
Actual test time used : 6
Detailed test results:
CIR test (with the step of 1):
Start time : 2016-11-15 21:00:02.1
End time : 2016-11-15 21:00:14.3
Status : Succeeded
Min/Max/Average IR(kbps) : 996/1003/1000
Min/Max/Average FTD(us) : 67/78/69
Min/Max/Average FDV(us) : 0/10/1
FL count/FLR : 0/0.000%
Packets out of order : 0
Severely Err Secs/AVAIL : 0/100.000%
PIR test (color green):
Start time : 2016-11-15 21:00:22.3
End time : 2016-11-15 21:00:34.5
Status : Succeeded
Min/Max/Average IR(kbps) : 997/1005/1000
Min/Max/Average FTD(us) : 68/69/68
Min/Max/Average FDV (us) : 35/39/37
FL count/FLR : 2/0.002%
Packets out of order : 0
Severely Err Secs/AVAIL : 0/100.000%
PIR test (color yellow):
Start time : 2016-11-15 21:00:22.5
End time : 2016-11-15 21:00:34.7
Status : --
Min/Max/Average IR(kbps) : 496/503/499
Min/Max/Average FTD(us) : 67/69/68
Min/Max/Average FDV (us) : 40/45/42
FL count/FLR : 2/0.002%
Packets out of order : 0
Severely Err Secs/AVAIL : 0/100.000%
PIR test (total):
Start time : 2016-11-15 21:00:22.5
End time : 2016-11-15 21:00:34.7
Status : --
Min/Max/Average IR(kbps) : 1493/1508/1499
Min/Max/Average FTD(us) : 68/69/68
Min/Max/Average FDV (us) : 35/45/40
FL count/FLR : 2/0.002%
Packets out of order : 0
Severely Err Secs/AVAIL : 0/--
Traffic policing test (color green)
Start time : 2016-11-15 21:00:42.7
End time : 2016-11-15 21:00:54.9
Status : Succeeded
Min/Max/Average IR(kbps) : 997/1005/1000
Min/Max/Average FTD(us) : 67/69/68
Min/Max/Average FDV (us) : 94/98/96
FL count/FLR : 4/0.004%
Packets out of order : 0
Severely Err Secs/AVAIL : 0/100.000%
Traffic policing test (color yellow):
Start time : 2016-11-15 21:00:42.1
End time : 2016-11-15 21:00:54.3
Status : --
Min/Max/Average IR(kbps) : 622/627/624
Min/Max/Average FTD(us) : 68/69/68
Min/Max/Average FDV (us) : 58/62/60
FL count/FLR : 10/0.01%
Packets out of order : 0
Severely Err Secs/AVAIL : 0/100.000%
Traffic policing test (total):
Start time : 2016-11-15 21:00:42.5
End time : 2016-11-15 21:00:54.7
Status : --
Min/Max/Average IR(kbps) : 1619/1632/1624
Min/Max/Average FTD(us) : 67/69/68
Min/Max/Average FDV (us) : 58/62/60
FL count/FLR : 10/0.01%
Packets out of order : 0
Severely Err Secs/AVAIL : 0/--
Service performance test:
Start time : 2016-11-15 21:16:06.7
End time : 2016-11-15 21:17:07.9
Status : Succeeded
Min/Max/Average IR(kbps) : 996/1003/999
Min/Max/Average FTD(us) : 67/69/68
Min/Max/Average FDV (us) : 47/51/49
FL count/FLR : 2/0.002%
Packets out of order : 0
Severely Err Secs/AVAIL : 0/100.000%
# Display the most recent result of the throughput operation with administrator name admin and operation tag test.
<Sysname> display nqa result admin test
NQA entry (admin admin, tag test) test results:
Basic results :
Initial speed(Kbps) : 100000
Speed granularity(Kbps): 1000
Probe duration(s) : 60
Probe interval(s) : 4
Allowed-loss-ratio : 1/10000
Throughput results:
Frame size(Byte): 64
Current speed(Kbps): -
Frame-loss(Loss/Tx): -
Status : Failed
Time : 2022-01-01 07:20:40.8
Frame size(Byte): 512
Current speed(Kbps): 4000
Frame-loss(Loss/Tx): 0/10000
Status : Succeeded
Time : 2022-01-01 07:21:40.8
Frame size(Byte): 1024
Current speed(Kbps): 8000
Frame-loss(Loss/Tx): 0/10000
Status : Succeeded
Time : 2022-01-01 07:22:52.8
Frame size(Byte): 1280
Current speed(Kbps): 10000
Frame-loss(Loss/Tx): 0/10000
Status : Succeeded
Time : 2022-01-01 07:23:45.8
Frame size(Byte): 1518
Current speed(Kbps): 10000
Frame-loss(Loss/Tx): 0/10000
Status : Succeeded
Time : 2022-01-01 07:24:45.8
Table 6 Command output
Field |
Description |
NQA entry (admin admin, tag test) test results |
NQA operation results. |
Data collecting in progress |
The operation is in progress. |
Send operation times |
Number of operations. |
Receive response times |
Number of response packets received. |
Min/Max/Average round trip time |
Minimum/maximum/average round-trip time in milliseconds. |
Square-Sum of round trip time |
Square sum of round-trip time. |
Last succeeded probe time |
Time when the most recent successful probe was completed. If no probes are successful in an operation, the field displays 0. This field is not available for UDP jitter, path jitter, and voice operations. |
Last packet received time |
Time when the most recent response packet was received. If no response packets in a probe were received, the field displays 0. This field is available only for UDP jitter and voice operations. |
Extended results |
Results of extended items. |
Packet loss ratio |
Average packet loss ratio. |
Failures due to timeout |
Number of timeout occurrences in an operation. |
Failures due to disconnect |
Number of disconnections by the peer. |
Failures due to no connection |
Number of failures to connect with the peer. |
Failures due to internal error |
Number of failures due to internal errors. |
Failures due to other errors |
Failures due to other errors. |
Packets out of sequence |
Number of failures due to out-of-sequence packets. |
ICMP-jitter results |
ICMP jitter operation results. This field is available only for the ICMP jitter operation. |
Packets arrived late |
Number of response packets received after a probe times out. |
UDP-jitter results |
UDP jitter operation results. This field is available only for the UDP jitter operation. |
Voice results |
Voice operation results. This field is available only for the voice operation. |
RTT number |
Number of response packets received. |
Min positive SD |
Minimum positive jitter from source to destination, in milliseconds. |
Min positive DS |
Minimum positive jitter from destination to source, in milliseconds. |
Max positive SD |
Maximum positive jitter from source to destination, in milliseconds. |
Max positive DS |
Maximum positive jitter from destination to source, in milliseconds. |
Positive SD number |
Number of positive jitters from source to destination. |
Positive DS number |
Number of positive jitters from destination to source. |
Positive SD sum |
Sum of positive jitters from source to destination, in milliseconds. |
Positive DS sum |
Sum of positive jitters from destination to source, in milliseconds. |
Positive SD average |
Average positive jitters from source to destination, in milliseconds. |
Positive DS average |
Average positive jitters from destination to source, in milliseconds. |
Positive SD square-sum |
Square sum of positive jitters from source to destination. |
Positive DS square-sum |
Square sum of positive jitters from destination to source. |
Min negative SD |
Minimum absolute value among negative jitters from source to destination, in milliseconds. |
Min negative DS |
Minimum absolute value among negative jitters from destination to source, in milliseconds. |
Max negative SD |
Maximum absolute value among negative jitters from source to destination, in milliseconds. |
Max negative DS |
Maximum absolute value among negative jitters from destination to source, in milliseconds. |
Negative SD number |
Number of negative jitters from source to destination. |
Negative DS number |
Number of negative jitters from destination to source. |
SD average |
Average jitter from source to destination, in milliseconds. |
DS average |
Average jitter from destination to source, in milliseconds. |
Negative SD sum |
Sum of absolute values of negative jitters from source to destination, in milliseconds. |
Negative DS sum |
Sum of absolute values of negative jitters from destination to source, in milliseconds. |
Negative SD average |
Average absolute value of negative jitters from source to destination, in milliseconds. |
Negative DS average |
Average absolute value of negative jitters from destination to source, in milliseconds. |
Negative SD square-sum |
Square sum of negative jitters from source to destination. |
Negative DS square-sum |
Square sum of negative jitters from destination to source. |
One way results |
Unidirectional delay in milliseconds. This field is available only for the ICMP jitter, UDP jitter, and voice operations. |
Max SD delay |
Maximum delay from source to destination, in milliseconds. |
Max DS delay |
Maximum delay from destination to source, in milliseconds. |
Min SD delay |
Minimum delay from source to destination, in milliseconds. |
Min DS delay |
Minimum delay from destination to source, in milliseconds. |
Number of SD delay |
Number of delays from source to destination. |
Number of DS delay |
Number of delays from destination to source. |
Sum of SD delay |
Sum of delays from source to destination, in milliseconds. |
Sum of DS delay |
Sum of delays from destination to source, in milliseconds. |
Square-Sum of SD delay |
Square sum of delays from source to destination. |
Square-Sum of DS delay |
Square sum of delays from destination to source. |
SD lost packets |
Number of lost packets from the source to the destination. |
DS lost packets |
Number of lost packets from the destination to the source. |
Lost packets for unknown reason |
Number of lost packets for unknown reasons. |
Voice scores |
Voice parameters. This field is available only for the voice operation. |
MOS value |
MOS value calculated for the voice operation. |
ICPIF value |
ICPIF value calculated for the voice operation. |
Hop IP |
IP address of the hop. This field is available only for the path jitter operation. |
Path-jitter results |
Path jitter operation results. This field is available only for the path jitter operation. |
Jitter number |
Number of jitters. This field is available only for the path jitter operation. |
Min/Max/Average jitter |
Minimum/maximum/average jitter in milliseconds. This field is available only for the path jitter operation. |
Positive jitter number |
Number of positive jitter. This field is available only for the path jitter operation. |
Min/Max/Average positive jitter |
Minimum/maximum/average positive jitter in milliseconds. This field is available only for the path jitter operation. |
Sum/Square-Sum positive jitter |
Sum/square sum of the positive jitter. This field is available only for the path jitter operation. |
Negative jitter number |
Number of negative jitter. This field is available only for the path jitter operation. |
Min/Max/Average negative jitter |
Minimum/maximum/average negative jitter in milliseconds. This field is available only for the path jitter operation. |
Sum/Square-Sum negative jitter |
Sum/square sum of the negative jitter. This field is available only for the path jitter operation. |
TTL |
If the routing table bypass feature is not enabled in the operation, this field displays the TTL value in the probe packet. If the routing table bypass feature is enabled, the value of this field varies by the init-ttl command. However, the actual TTL value in the probe packet is fixed at 1. |
Hop IP |
IP address of the node that sent the reply packet. |
Time |
Time when the NQA client received the reply packet. |
Status |
Status of the Y.1564 operation or a test in the Y.1564 operation: · Succeeded. · Failed. · In progress. · Aborted—The test was manually aborted. · Timeout. · Unknown error. This field displays two hyphens (--) for a test whose status is meaningless. |
Last test |
Most recent completed test. · CIR test. · PIR test. · Traffic policing test. · Service performance test. |
Estimated total time |
Total amount of time that the Y.1564 operation was estimated to take, in seconds. |
Actual test time used |
Actual amount of time to complete the Y.1564 operation, in seconds. The timer used to measure the test start time and end time is accurate to 1 second. Therefore, a difference of up to 1 second might exist between the value in this field and the time duration between the start and end of the test. |
CIR test (with the step of 1) |
Information about the CIR test with a step count of 1. |
Start time |
Start time of the test. |
End time |
End time of the test. |
Min/Max/Average IR(kbps) |
Minimum, maximum, and average information rates in kbps. |
Min/Max/Average FTD(us) |
Minimum, maximum, and average frame transfer delays in microseconds. |
Min/Max/Average FDV(us) |
Minimum, maximum, and average frame delay variations in microseconds. |
FL count/FLR |
Number of lost frames and the frame loss ratio. |
Packets out of order |
Number of out-of-order packets. |
Severely Err Secs/AVAIL |
Total number of severely errored seconds (SESs) and the network availability ratio (AVAIL). A severely errored second occurs when the ratio of lost frames during a one-second interval exceeds 50%. AVAIL is calculated as follows: AVAIL = Total seconds in available periods / total seconds taken by the test. · The network is in an unavailable period after 10 consecutive SESs. The unavailable period ends when 10 consecutive non-SESs are recorded. · The network is in an available period after 10 consecutive non-SESs. The available period ends when 10 consecutive SESs are recorded. By default, the test enters the available period when it starts. |
PIR test (color green) |
Statistics about the green frames in the PIR test. |
PIR test (color yellow) |
Statistics about the yellow frames in the PIR test. |
PIR test (total) |
Summary statistics about the PIR test. |
PIR test (color-blind) |
Statistics about the PIR test in non-color-aware mode. |
Traffic policing test (color green) |
Statistics about the green frames in the traffic policing test. |
Traffic policing test (color yellow) |
Statistics about the yellow frames in the traffic policing test. |
Traffic policing test (total) |
Summary statistics about the traffic policing test. |
Traffic policing test (color-blind) |
Statistics about the traffic policing test in non-color-aware mode. |
Service performance test |
Statistics about the service performance test. |
Basic results |
Results of basic items. |
Throughput results |
Throughput operation results. |
Frame-loss results |
Frame loss operation results. |
Latency results |
Latency operation results. |
Initial speed(Kbps) |
Initial rate for sending probe packets, in kbps. |
Speed granularity(Kbps) |
Granularity of rate adjustment, in kbps. |
Probe duration(s) |
Duration of a probe, in seconds. |
Probe interval(s) |
Intervals at which probes are performed, in seconds. |
Allowed-loss-ratio |
Maximum packet loss rate supported. |
Frame size(Byte) |
Frame size in bytes. |
Current speed(Kbps) |
Current rate in kbps. |
Frame-loss(Loss/Tx) |
Frame loss rate. |
Min-latency(us) |
Minimum latency in microseconds. |
Max-latency(us) |
Maximum latency in microseconds. |
Avg-latency(us) |
Average latency in microseconds. |
Min-jitter(ns) |
Minimum jitter in nanoseconds. |
Max-jitter(ns) |
Maximum jitter in nanoseconds. |
Avg-jitter(ns) |
Average jitter in nanoseconds. |
Sent packets |
Number of packets sent. |
Received packets |
Number of packets received. |
Status |
Probe result: · Succeeded. · Failed. |
Time |
Time when the probe was completed. |
display nqa rfc2544 group
Use display nqa rfc2544 group to display information about path quality analysis operation groups.
Syntax
display nqa rfc2544 group [ brief | name group-name | result [ group-name ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
brief: Displays brief information about path quality analysis operation groups.
name group-name: Specifies a path quality analysis operation group by its name, a case-insensitive string of 1 to 32 characters. If you do not specify this option, the command displays detailed information about all path quality analysis operation groups.
result: Displays probe results of path quality analysis operation groups.
Usage guidelines
If you do not specify any parameters, this command displays detailed information about all path quality analysis operation groups.
Examples
# Display brief information about path quality analysis operation groups.
<Sysname> display nqa rfc2544 group brief
Group name Status
test1 Active
test2 Idle
# Display detailed information about path quality analysis operation group test.
<Sysname> display nqa rfc2544 group name test
Group name: test
Status: Idle
Bound NQA entry information:
Admin-name Operation-tag
admin 1
admin 2
# Display probe results of path quality analysis operation group test.
<Sysname> display nqa rfc2544 group result test
NQA entry (admin admin, tag 1) test results:
Basic results :
Initial speed(Kbps) : 100000
Probe duration(s) : 60
Probe interval(s) : 4
Frame-loss results:
Frame size(Byte): 64
Current speed(Kbps): 100000
Frame-loss : 0.0672002%
Status : Succeeded
Time : 2021-04-17 15:39:33.3
Frame size(Byte): 96
Current speed(Kbps): 100000
Frame-loss : 0.0928005%
Status : Succeeded
Time : 2021-04-17 15:39:35.3
NQA entry (admin admin, tag 2) test results:
Basic results :
Initial speed(Kbps): 100000
Probe duration(s) : 60
Probe interval(s) : 4
Latency results:
Frame size : 64
Min-latency(us) : 146
Max-latency(us) : 150
Avg-latency(us) : 148
Min-jitter(ns) : 0
Max-jitter(ns) : 0
Avg-jitter(ns) : 0
Sent packets : 10000
Received packets : 9998
Status : Succeeded
Time : 2021-04-17 15:39:37.3
Frame size : 128
Min-latency(us) : 82
Max-latency(us) : 86
Avg-latency(us) : 84
Min-jitter(ns) : 0
Max-jitter(ns) : 0
Avg-jitter(ns) : 0
Sent packets : 10000
Received packets : 9998
Status : Succeeded
Time : 2021-04-17 15:39:39.3
NQA entry (admin admin, tag 3) test results:
Basic results :
Initial speed(Kbps) : 100000
Speed granularity(Kbps): 1000
Probe duration(s) : 60
Probe interval(s) : 4
Allowed-loss-ratio : 1/10000
Throughput results:
Frame size(Byte): 64
Current speed(Kbps): -
Frame-loss(Loss/Tx): -
Status : Failed
Time : 2021-04-17 15:41:12.4
Table 7 Command output
Field |
Description |
Group name |
Name of the path quality analysis operation group |
Status |
Status of the operation: · Idle. · Active. |
Bound NQA entry information |
Information about the NQA operation bound to the path quality analysis operation group. |
Admin-name |
Administrator name of the NQA operation. |
Operation-tag |
Operation tag. |
Status |
Operation status: · Succeeded. · Failed. · In progress. · Aborted—the operation is stopped manually by the user. · Timeout. · Unknown error. · --—The operation status is invalid. |
display nqa statistics
Use display nqa statistics to display NQA operation statistics.
Syntax
display nqa statistics [ admin-name operation-tag ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
admin-name operation-tag: Specifies an NQA operation by its administrator name and operation tag. The admin-name argument represents the name of the administrator who creates the NQA operation. The operation-tag argument represents the operation tag. Each of the arguments is a case-insensitive string of 1 to 32 characters that cannot contain hyphens (-). If you do not specify an NQA operation, the command displays statistics for all NQA operations.
Usage guidelines
The statistics are generated after the NQA operation completes. If you execute the display nqa statistics command before the operation completes, the statistics are displayed as all 0s.
If a reaction entry is configured, the command displays the monitoring results of the reaction entry in the period specified by the statistics internal command. The result fields display hyphens (-) in one of the following conditions:
· The threshold type is average value.
· The monitored performance metric is ICPIF or MOS for the voice operation.
The command is not available for the frame loss, latency, throughput, or UDP tracert operation.
Examples
# Display the statistics for the TCP operation with administrator name admin and operation tag test.
<Sysname> display nqa statistics admin test
NQA entry (admin admin, tag test) test statistics:
NO. : 1
Start time: 2007-01-01 09:30:20.0
Life time: 2 seconds
Send operation times: 1 Receive response times: 1
Min/Max/Average round trip time: 13/13/13
Square-Sum of round trip time: 169
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 statistics for the ICMP jitter operation with administrator name admin and operation tag test.
<Sysname> display nqa statistics admin test
NQA entry (admin admin, tag test) test statistics:
NO. : 1
Start time: 2015-03-09 17:42:10.7
Life time: 156 seconds
Send operation times: 1560 Receive response times: 1560
Min/Max/Average round trip time: 1/2/1
Square-Sum of round trip time: 1563
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: 1560
Min positive SD: 1 Min positive DS: 1
Max positive SD: 1 Max positive DS: 2
Positive SD number: 18 Positive DS number: 46
Positive SD sum: 18 Positive DS sum: 49
Positive SD average: 1 Positive DS average: 1
Positive SD square-sum: 18 Positive DS square-sum: 55
Min negative SD: 1 Min negative DS: 1
Max negative SD: 1 Max negative DS: 2
Negative SD number: 24 Negative DS number: 57
Negative SD sum: 24 Negative DS sum: 58
Negative SD average: 1 Negative DS average: 1
Negative SD square-sum: 24 Negative DS square-sum: 60
SD average: 1 DS average: 1
One way results:
Max SD delay: 1 Max DS delay: 2
Min SD delay: 1 Min DS delay: 1
Number of SD delay: 4 Number of DS delay: 4
Sum of SD delay: 4 Sum of DS delay: 5
Square-Sum of SD delay: 4 Square-Sum of DS delay: 7
Lost packets for unknown reason: 0
Reaction statistics:
Index Checked Element Threshold Type Checked Num Over-threshold Num
1 jitter-DS accumulate 1500 10
2 jitter-SD average - -
3 OWD-DS - 1560 2
4 OWD-SD - 1560 0
5 packet-loss accumulate 0 0
6 RTT accumulate 1560 0
# Display the statistics for the UDP jitter operation with administrator name admin and operation tag test.
<Sysname> display nqa statistics admin test
NQA entry (admin admin, tag test) test statistics:
NO. : 1
Start time: 2007-01-01 09:33:22.3
Life time: 23 seconds
Send operation times: 100 Receive response times: 100
Min/Max/Average round trip time: 1/11/5
Square-Sum of round trip time: 24360
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: 550
Min positive SD: 1 Min positive DS: 1
Max positive SD: 7 Max positive DS: 1
Positive SD number: 220 Positive DS number: 97
Positive SD sum: 283 Positive DS sum: 287
Positive SD average: 1 Positive DS average: 2
Positive SD square-sum: 709 Positive DS square-sum: 1937
Min negative SD: 2 Min negative DS: 1
Max negative SD: 10 Max negative DS: 1
Negative SD number: 81 Negative DS number: 94
Negative SD sum: 556 Negative DS sum: 191
Negative SD average: 6 Negative DS average: 2
Negative SD square-sum: 4292 Negative DS square-sum: 967
SD average: 2 DS average: 2
One way results:
Max SD delay: 5 Max DS delay: 5
Min SD delay: 1 Min DS delay: 1
Number of SD delay: 550 Number of DS delay: 550
Sum of SD delay: 1475 Sum of DS delay: 1201
Square-Sum of SD delay: 5407 Square-Sum of DS delay: 3959
SD lost packets: 0 DS lost packets: 0
Lost packets for unknown reason: 0
Reaction statistics:
Index Checked Element Threshold Type Checked Num Over-threshold Num
1 jitter-DS accumulate 90 25
2 jitter-SD average - -
3 OWD-DS - 100 24
4 OWD-SD - 100 13
5 packet-loss accumulate 0 0
6 RTT accumulate 100 52
# Display the statistics for the voice operation with administrator name admin and operation tag test.
<Sysname> display nqa statistics admin test
NQA entry (admin admin, tag test) test statistics:
NO. : 1
Start time: 2007-01-01 09:33:45.3
Life time: 120 seconds
Send operation times: 10 Receive response times: 10
Min/Max/Average round trip time: 1/12/7
Square-Sum of round trip time: 620
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
Voice results:
RTT number: 10
Min positive SD: 3 Min positive DS: 1
Max positive SD: 10 Max positive DS: 1
Positive SD number: 3 Positive DS number: 2
Positive SD sum: 18 Positive DS sum: 2
Positive SD average: 6 Positive DS average: 1
Positive SD square-sum: 134 Positive DS square-sum: 2
Min negative SD: 3 Min negative DS: 1
Max negative SD: 9 Max negative DS: 1
Negative SD number: 4 Negative DS number: 2
Negative SD sum: 25 Negative DS sum: 2
Negative SD average: 6 Negative DS average: 1
Negative SD square-sum: 187 Negative DS square-sum: 2
SD average: 6 DS average: 1
One way results:
Max SD delay: 0 Max DS delay: 0
Min SD delay: 0 Min DS delay: 0
Number of SD delay: 0 Number of DS delay: 0
Sum of SD delay: 0 Sum of DS delay: 0
Square-Sum of SD delay: 0 Square-Sum of DS delay: 0
SD lost packets: 0 DS lost packets: 0
Lost packets for unknown reason: 0
Voice scores:
Max MOS value: 4.40 Min MOS value: 4.40
Max ICPIF value: 0 Min ICPIF value: 0
Reaction statistics:
Index Checked Element Threshold Type Checked Num Over-threshold Num
1 ICPIF - - -
2 MOS - - -
# Display the statistics for the path jitter operation with administrator name admin and operation tag test.
<Sysname> display nqa statistics admin test
NQA entry (admin admin, tag test) test statistics:
NO. : 1
Path 1:
Hop IP 192.168.40.210
Basic Results:
Send operation times: 10
Receive response times: 10
Min/Max/Average round trip time: 1/1/1
Square-Sum of round trip time: 10
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
Path-Jitter Results:
Jitter number: 9
Min/Max/Average jitter: 0/0/0
Positive jitter number: 0
Min/Max/Average positive jitter: 0/0/0
Sum/Square-Sum positive jitter: 0/0
Negative jitter number: 0
Min/Max/Average negative jitter: 0/0/0
Sum/Square-Sum negative jitter: 0/0
Hop IP 192.168.50.209
Basic Results:
Send operation times: 10
Receive response times: 10
Min/Max/Average round trip time: 1/1/1
Square-Sum of round trip time: 10
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
Path-Jitter Results:
Jitter number: 9
Min/Max/Average jitter: 0/0/0
Positive jitter number: 0
Min/Max/Average positive jitter: 0/0/0
Sum/Square-Sum positive jitter: 0/0
Negative jitter number: 0
Min/Max/Average negative jitter: 0/0/0
Sum/Square-Sum negative jitter: 0/0
Table 8 Command output
Field |
Description |
No. |
Statistics group ID. |
Start time |
Time when the operation started. |
Life time |
Duration of the operation in seconds. |
Send operation times |
Number of probe packets sent. |
Receive response times |
Number of response packets received. |
Min/Max/Average round trip time |
Minimum/maximum/average round-trip time in milliseconds. |
Square-Sum of round trip time |
Square sum of round-trip time. |
Packet loss ratio |
Average packet loss ratio. |
Failures due to timeout |
Number of timeout occurrences in an operation. |
Failures due to disconnect |
Number of disconnections by the peer. |
Failures due to no connection |
Number of failures to connect with the peer. |
Failures due to internal error |
Number of failures due to internal errors. |
Failures due to other errors |
Failures due to other errors. |
Packets out of sequence |
Number of failures due to out-of-sequence packets. |
Packets arrived late |
Number of response packets received after a probe times out. |
ICMP-jitter results |
ICMP jitter operation results. This field is available only for the ICMP jitter operation. |
UDP-jitter results |
UDP jitter operation results. This field is available only for the UDP jitter operation. |
Voice results |
Voice operation results. This field is available only for the voice operation. |
RTT number |
Number of response packets received. |
Min positive SD |
Minimum positive jitter from source to destination, in milliseconds. |
Min positive DS |
Minimum positive jitter from destination to source, in milliseconds. |
Max positive SD |
Maximum positive jitter from source to destination, in milliseconds. |
Max positive DS |
Maximum positive jitter from destination to source, in milliseconds. |
Positive SD number |
Number of positive jitters from source to destination. |
Positive DS number |
Number of positive jitters from destination to source. |
Positive SD sum |
Sum of positive jitters from source to destination, in milliseconds. |
Positive DS sum |
Sum of positive jitters from destination to source, in milliseconds. |
Positive SD average |
Average positive jitters from source to destination, in milliseconds. |
Positive DS average |
Average positive jitters from destination to source, in milliseconds. |
Positive SD square-sum |
Square sum of positive jitters from source to destination. |
Positive DS square-sum |
Square sum of positive jitters from destination to source. |
Min negative SD |
Minimum absolute value among negative jitters from source to destination, in milliseconds. |
Min negative DS |
Minimum absolute value among negative jitters from destination to source, in milliseconds. |
Max negative SD |
Maximum absolute value among negative jitters from source to destination, in milliseconds. |
Max negative DS |
Maximum absolute value among negative jitters from destination to source, in milliseconds. |
Negative SD number |
Number of negative jitters from source to destination. |
Negative DS number |
Number of negative jitters from destination to source. |
Negative SD sum |
Sum of absolute values of negative jitters from source to destination, in milliseconds. |
Negative DS sum |
Sum of absolute values of negative jitters from destination to source, in milliseconds. |
Negative SD average |
Average absolute value of negative jitters from source to destination, in milliseconds. |
Negative DS average |
Average absolute value of negative jitters from destination to source, in milliseconds. |
Negative SD square-sum |
Square sum of negative jitters from source to destination. |
Negative DS square-sum |
Square sum of negative jitters from destination to source. |
SD average |
Average jitter from source to destination, in milliseconds. |
DS average |
Average jitter from destination to source, in milliseconds. |
One way results |
Unidirectional delay in milliseconds. This field is available only for the ICMP jitter, UDP jitter, and voice operations. |
Max SD delay |
Maximum delay from source to destination, in milliseconds. |
Max DS delay |
Maximum delay from destination to source, in milliseconds. |
Min SD delay |
Minimum delay from source to destination, in milliseconds. |
Min DS delay |
Minimum delay from destination to source, in milliseconds. |
Number of SD delay |
Number of delays from source to destination. |
Number of DS delay |
Number of delays from destination to source. |
Sum of SD delay |
Sum of delays from source to destination, in milliseconds. |
Sum of DS delay |
Sum of delays from destination to source, in milliseconds. |
Square-Sum of SD delay |
Square sum of delays from source to destination. |
Square-Sum of DS delay |
Square sum of delays from destination to source. |
SD lost packets |
Number of lost packets from the source to the destination. |
DS lost packets |
Number of lost packets from the destination to the source. |
Lost packets for unknown reason |
Number of lost packets for unknown reasons. |
Voice scores |
Voice parameters. This field is available only for the voice operation. |
Max MOS value |
Maximum MOS value. |
Min MOS value |
Minimum MOS value. |
Max ICPIF value |
Maximum ICPIF value. |
Min ICPIF value |
Minimum ICPIF value. |
Reaction statistics |
Statistics about the reaction entry in the counting interval. |
Index |
ID of a reaction entry. |
Checked Element |
Monitored element. |
Threshold Type |
Threshold type. |
Checked Num |
Number of targets that have been monitored for data collection. |
Over-threshold Num |
Number of threshold violations. |
Path |
Serial number for the path in the path jitter operation. This field is available only for the path jitter operation. |
Hop IP |
IP address of the hop. This field is available only for the path jitter operation. |
Path-jitter results |
Path jitter operation results. This field is available only for the path jitter operation. |
Jitter number |
Number of jitters. This field is available only for the path jitter operation. |
Min/Max/Average jitter |
Minimum/maximum/average positive jitter in milliseconds. This field is available only for the path jitter operation. |
Positive jitter number |
Number of positive jitters. This field is available only for the path jitter operation. |
Min/Max/Average positive jitter |
Minimum/maximum/average positive jitter in milliseconds. This field is available only for the path jitter operation. |
Sum/Square-Sum positive jitter |
Sum/square sum of positive jitters. This field is available only for the path jitter operation. |
Negative jitter number |
Number of negative jitters. This field is available only for the path jitter operation. |
Min/Max/Average negative jitter |
Minimum/maximum/average negative jitter in milliseconds. This field is available only for the path jitter operation. |
Sum/Square-Sum negative jitter |
Sum/square sum of negative jitters. This field is available only for the path jitter operation. |
Table 9 Monitored performance metrics for DHCP/DLSw/DNS/FTP/HTTP/ICMP echo/SNMP/TCP/UDP echo operations
Monitored performance metric |
Threshold type |
Collect data in |
Checked Num |
Over-threshold Num |
probe-duration |
accumulate |
Probes in the counting interval. |
Number of completed probes. |
Number of probes of which the duration exceeds the threshold. |
average |
N/A |
N/A |
N/A |
|
consecutive |
Probes in the counting interval. |
Number of completed probes. |
Number of probes of which the duration exceeds the threshold. |
|
probe-fail |
accumulate |
Probes in the counting interval. |
Number of completed probes. |
Number of probe failures. |
consecutive |
Probes in the counting interval. |
Number of completed probes. |
Number of probe failures. |
Table 10 Monitored performance metrics for ICMP jitter/UDP jitter/voice operations
Monitored performance metric |
Threshold type |
Collect data in |
Checked Num |
Over-threshold Num |
RTT |
accumulate |
Packets sent in the counting interval. |
Number of sent packets. |
Number of packets of which the round-trip time exceeds the threshold. |
average |
N/A |
N/A |
N/A |
|
jitter-DS/jitter-SD |
accumulate |
Packets sent in the counting interval. |
Number of sent packets. |
Number of packets of which the one-way jitter exceeds the threshold. |
average |
N/A |
N/A |
N/A |
|
OWD-DS/OWD-SD |
N/A |
Packets sent in the counting interval. |
Number of sent packets. |
Number of packets of which the one-way delay exceeds the threshold. |
packet-loss |
accumulate |
Packets sent in the counting interval. |
Number of sent packets. |
Number of packet loss. |
ICPIF/MOS (available only for the voice operation) |
N/A |
N/A |
N/A |
N/A |
Related commands
statistics interval
display nqa twamp-light client
Use display nqa twamp-light client to display test session information on the TWAMP Light client.
Syntax
display nqa twamp-light client [ link-bundle ] [ test-session session-id | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
link-bundle: Displays information about sessions on the link bundle interfaces. Without this keyword configured, this command displays information about all sessions.
test-session session-id: Displays detailed information about a test session by its ID. The value range for the session-id argument is 1 to 512.
verbose: Displays detailed information about all TWAMP Light test sessions.
Usage guidelines
If you do not specify any keywords, this command displays brief information about all test sessions.
Examples
# Display brief information about all test sessions.
<Sysname> display nqa twamp-light client
Brief information about all test sessions:
Total sessions: 2
Active sessions: 1
------------------------------------------------------------------------------------
ID Status Source IP/Port Destination IP/Port
1 Active 10.1.1.1/10000 10.2.2.2/20000
2 Inactive 4.4.4.1/7777 4.4.4.2/8888
# Display brief information about sessions on the link bundle interfaces.
<Sysname> display nqa twamp-light client link-bundle
Brief information about all test sessions:
Total sessions: 2
Active sessions: 2
------------------------------------------------------------------------------------
ID Status Source IP/Port Destination IP/Port Link bundle interface
1 Active 1.1.1.1/2001 2.2.2.2/2010 Route-Aggregation1
2 Active 2001::1/2001 2001::2/2010 Route-Aggregation1
# Display detailed information about all test sessions.
<Sysname> display nqa twamp-light client verbose
Session ID : 1
Status : Active
Session type : Permanent
Source interface : -
Service instance : -
Source IP : 10.1.1.1
Source IPv6 : -
Destination IP : 10.2.2.2
Destination IPv6 : -
Source port : 10000
Destination port : 20000
Source MAC : -
Destination MAC : -
VLAN ID : -
Service VLAN ID : -
Customer VLAN ID : -
ToS : 0
Padding length : 142
Timestamp format : PTP
VPN instance : -
Priority 802.1p : 0
Adjust-udp-checksum : Disabled
One-way delay-measure state : Disabled
Last start time : Never
Last stop time : Never
Packet sending interval(ms) : 100
Timeout(sec) : 5
Duration(sec) : -
Packets sent : -
Statistics interval(ms) : 10000
Monitor time(ms) : 20000
Delay monitor time(ms) : 20000
Jitter monitor time(ms) : 20000
Loss monitor time(ms) : 20000
Link bundle interface : Route-Aggregation1
Member interface : Ten-GigabitEthernet3/0/1
Status : Active
Last start time : 2021-11-29 23:05:33.7
Last stop time : Never
Adjust-udp-checksum : Disabled
One-way delay-measure state : Disabled
Session ID : 2
Status : Inactive
Session type : -
Source interface : Ten-GigabitEthernet3/0/2
Service instance : -
Source IP : 4.4.4.1
Source IPv6 : -
Destination IP : 4.4.4.2
Destination IPv6 : -
Source port : 7777
Destination port : 8888
Source MAC : 0001-0001-0001
Destination MAC : 0001-0001-0002
VLAN ID : -
Service VLAN ID : -
Customer VLAN ID : -
ToS : 0
Padding length : 142
Timestamp format : PTP
VPN instance : -
Priority 802.1p : 0
Adjust-udp-checksum : Disabled
One-way delay-measure state : Disabled
Last start time : Never
Last stop time : Never
Packet sending interval(ms) : -
Timeout(sec) : -
Duration(sec) : -
Packets sent : -
Statistics interval(ms) : -
Monitor time(ms) : -
Delay monitor time(ms) : -
Jitter monitor time(ms) : -
Loss monitor time(ms) : -
Link bundle interface : -
Table 11 Command output
Field |
Description |
Total sessions |
Total number of test sessions. |
Active sessions |
Number of active sessions. |
Session ID |
Session ID. |
Status |
Test status: · Active—The TWAMP Light test is active. · Inactive—The TWAMP Light test is not active. |
Session type |
Test session type: · On-demand. · Permanent. |
Source interface |
Source AC interface of the test session. |
Service instance |
Ethernet service instance bound to source interface. The Ethernet service instance on the client must be consistent with that on the server. |
Source IP |
Source IPv4 address of the test session. |
Source IPv6 |
Source IPv6 address of the test session. |
Destination IP |
Destination IPv4 address of the test session. |
Destination IPv6 |
Destination IPv6 address of the test session. |
Source port |
Source port number of the test session. |
Destination port |
Destination port number of the test session. |
Source MAC address |
Source MAC address of the test session. |
Destination MAC address |
Destination MAC address of the test session. |
VLAN ID |
VLAN ID of the test session. |
Service VLAN ID |
Outer VLAN ID of the test session. |
Customer VLAN ID |
Inner VLAN ID of the test session. |
ToS |
Type of Service of the test session. |
Padding length |
Padding length of the test session. |
Timestamp format |
Timestamp format: NTP or PTP. |
VPN instance |
MPLS L3VPN instance name. |
Priority 802.1p |
802.1p priority. |
Adjust-udp-checksum |
Checksum field adjustment status: · Enabled—Uses the actual value. · Disabled—Uses value 0. Without link bundle configured, this field indicates whether the session can adjust the checksum field. With link bundle configured, this field displays Enabled when at least one member session can adjust the checksum field. |
One-way delay-measure state |
State of the one-way latency measurement feature for the session: · Enabled · Disabled Without link bundle configured, this field indicates whether the session can measure one-way latency. With link bundle configured, this field displays Enabled when at least one member session can measure one-way latency. |
Last start time |
Start time of the most recent TWAMP Light test, in the format of YYYY-MM-DD HH:MM:SS:MS. Without link bundle configured, if the test does not start, this field displays Never. With link bundle configured, this field always displays Never. |
Last stop time |
Stop time of the most recent TWAMP Light test, in the format of YYYY-MM-DD HH:MM:SS:MS. Without link bundle configured, if the test does not start, this field displays Never. With link bundle configured, this field always displays Never. |
Packet sending interval(ms) |
Packet sending interval of the TWAMP Light test, in milliseconds. |
Timeout(sec) |
Timeout time of the reflected packet within a TWAMP Light test, in seconds. |
Duration(sec) |
Duration of the TWAMP Light test, in seconds. This field is available only for the on-demand test that is configured with the duration. |
Packets sent |
Number of sent packets in the TWAMP Light test. This field is available only for the on-demand test that is configured with the number of packets sent in the test. |
Statistics interval(ms) |
Statistics collection interval of the TWAMP Light test, in milliseconds. |
Monitor time(ms) |
Packet monitoring time of the TWAMP Light test, in milliseconds. The value of this field is specified by the start command in TWAMP Light sender view. |
Delay monitor time(ms) |
Monitoring time for two-way delay of the TWAMP Light test, in milliseconds. This field displays a hyphen (-) when the test is not started. |
Jitter monitor time(ms) |
Monitoring time for two-way jitter of the TWAMP Light test, in milliseconds. This field displays a hyphen (-) when the test is not started. |
Loss monitor time(ms) |
Monitoring time for two-way packet loss of the TWAMP Light test, in milliseconds. This field displays a hyphen (-) when the test is not started. |
Link bundle interface |
Name of the link bundle interface. In this software version, the link bundle interface can only be a Layer 3 aggregate interface. This field displays a hyphen (-) when the interface is not a link bundle interface. |
Member interface : Status : Last start time : Last stop time : Adjust-udp-checksum : One-waydelay-measure state : |
Information about the TWAMP Light test for the member interface: · Name of the member interface. · Session status: ¡ Active—The TWAMP Light test is active. ¡ Inactive—The TWAMP Light test is not active. · Start time of the most recent TWAMP Light test, in the format of YYYY-MM-DD HH:MM:SS:MS. If the test does not start, this field displays Never. · End time of the most recent TWAMP Light test, in the format of YYYY-MM-DD HH:MM:SS:MS. If the test does not complete, this field displays Never. · Checksum field adjustment status for the member interface: ¡ Enabled—Uses the actual checksum value. ¡ Disabled—Uses value 0. · State of the one-way latency measurement feature for the member interface: ¡ Enabled ¡ Disabled |
Related commands
test-session
display nqa twamp-light client statistics
Use display nqa twamp-light client statistics to display test session statistics on the TWAMP Light client, including two-way delay, two-way jitter, and two-way packet loss.
Syntax
display nqa twamp-light client statistics { one-way-delay | two-way-delay | two-way-loss } test-session session-id [ link-bundle-member interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
one-way-delay: Displays statistics about one-way delay and one-way jitter
two-way-delay: Displays statistics about two-way delay and two-way jitter.
two-way-loss: Displays statistics about two-way packet loss.
session-id: Specifies a session ID. The value must be an integer. The value range for this argument is 1 to 512.
link-bundle-member interface-type interface-number: Displays statistics for a specific member interface of the link bundle interface. The interface-type interface-number argument specifies an interface by its type and number. If you do not specify the interface-type interface-number argument, this command displays statistics about all member interfaces of the link bundle interface.
Examples
# Display statistics about one-way latency and jitter for the specified TWAMP Light test session.
<Sysname> display nqa twamp-light client statistics one-way-delay test-session 1
Latest one-way-delay statistics(us):
Index SD-delay(Avg)DS-delay(Avg) SD-jitter(Avg) DS-jitter(Avg)
1 1869927531 0 1307 138
2 1869921226 0 1691 186
3 1869924535 0 1040 168
--------------------------------------------------------------------------------
Average SD delay : 1869924431 Average DS delay : 0
Maximum SD delay : 1869927531 Maximum DS delay : 0
Minimum SD delay : 1869921226 Minimum DS delay : 0
Average SD jitter: 1346 Average DS jitter: 164
Maximum SD jitter: 40805 Maximum DS jitter: 13141
Minimum SD jitter: 1 Minimum DS jitter: 1
Table 12 Command output
Field |
Description |
Link bundle member |
Statistics for the member interfaces of the link bundle interface. |
Latest one-way delay statistics(μs) |
Most recent statistics of one-way delay in microseconds. |
Index |
Serial number of the statistics data. |
SD-delay(avg) |
Average delay from source to destination. |
DS-delay(avg) |
Average delay from destination to source. |
SD-jitter(avg) |
Average jitter from source to destination. |
DS-jitter(avg) |
Average jitter from destination to source. |
Average SD delay |
Average delay from source to destination. |
Average DS delay |
Average delay from destination to source. |
Maximum SD delay |
Maximum delay from source to destination. |
Maximum DS delay |
Maximum delay from destination to source. |
Minimum SD delay |
Minimum delay from source to destination. |
Minimum DS delay |
Minimum delay from destination to source.. |
Average SD jitter |
Average jitter from source to destination. |
Average DS jitter |
Average jitter from destination to source. |
Maximum SD jitter |
Maximum jitter from source to destination. |
Maximum DS jitter |
Maximum jitter from destination to source. |
Minimum SD jitter |
Minimum jitter from source to destination. |
Minimum DS jitter |
Minimum jitter from destination to source. |
# Display statistics about two-way delay and two-way jitter for the specified TWAMP Light test session.
<Sysname> display nqa twamp-light client statistics two-way-delay test-session 1
Latest two-way-delay statistics(us):
Index Delay(Avg) Jitter(Avg) SD-jitter(Avg) DS-jitter(Avg)
1 734 240 81 159
2 658 24 12 12
3 580 91 31 60
4 667 40 42 2
5 8346 15226 15293 67
6 627 18 17 35
7 659 10 4 14
8 662 67 46 21
--------------------------------------------------------------------------------
Average delay : 1617 Average jitter : 1965
Maximum delay : 15959 Maximum jitter : 15226
Minimum delay : 534 Minimum jitter : 10
Average SD jitter: 1941 Average DS jitter: 46
Maximum SD jitter: 15293 Maximum DS jitter: 159
Minimum SD jitter: 4 Minimum DS jitter: 2
# Display statistics about two-way delay and two-way jitter for the specified TWAMP Light test session. (Suppose the test is performed only for a Layer 3 aggregate interface with two member interfaces. This command displays statistics for the two member interfaces separately.)
<Sysname> display nqa twamp-light client statistics two-way-delay test-session 2
Link bundle member: Ten-GigabitEthernet3/0/1
Latest two-way-delay statistics(us):
Index Delay(Avg) Jitter(Avg) SD-jitter(Avg) DS-jitter(Avg)
1 0 0 0 0
2 0 0 0 0
3 4 4 4 4
4 1 1 1 1
Link bundle member: Ten-GigabitEthernet3/0/2
Latest two-way-delay statistics(us):
Index Delay(Avg) Jitter(Avg) SD-jitter(Avg) DS-jitter(Avg)
1 0 0 0 0
2 0 0 0 0
3 4 4 4 4
4 1 1 1 1
--------------------------------------------------------------------------------
Average delay : 1 Average jitter : 1
Maximum delay : 7 Maximum jitter : 7
Minimum Delay : 0 Minimum jitter : 0
Average SD jitter : 1 Average DS jitter : 1
Maximum SD jitter : 7 Maximum DS jitter : 7
Minimum SD jitter : 0 Minimum DS jitter : 0
Table 13 Command output
Field |
Description |
Link bundle member |
Statistics for the member interfaces of the link bundle interface. |
Latest two-way delay statistics(μs) |
Most recent statistics of two-way delay in microseconds. |
Index |
Serial number of the statistics data. |
Delay(avg) |
Average delay. |
Jitter(avg) |
Average jitter. |
SD jitter(avg) |
Average jitter from source to destination. |
DS jitter(avg) |
Average jitter from destination to source. |
Average delay |
Average delay. |
Average jitter |
Average jitter. |
Maximum delay |
Maximum delay. |
Maximum jitter |
Maximum jitter. |
Minimum delay |
Minimum delay. |
Minimum jitter |
Minimum jitter. |
Average SD jitter |
Average jitter from source to destination. |
Average DS jitter |
Average jitter from destination to source. |
Maximum SD jitter |
Maximum jitter from source to destination. |
Maximum DS jitter |
Maximum jitter from destination to source. |
Minimum SD jitter |
Minimum jitter from source to destination. |
Minimum DS jitter |
Minimum jitter from destination to source. |
# Display the two-way packet loss statistics for the specified TWAMP Light test session.
<Sysname> display nqa twamp-light client statistics two-way-loss test-session 1
Latest two-way loss statistics:
Index Loss count Loss ratio Error count Error ratio
11006 5 50.0000% 0 0.0000%
11007 3 30.0000% 0 0.0000%
11008 4 40.0000% 0 0.0000%
11009 8 80.0000% 0 0.0000%
11010 10 100.0000% 0 0.0000%
11011 1 10.0000% 0 0.0000%
11012 10 100.0000% 0 0.0000%
11013 2 20.0000% 0 0.0000%
11014 10 100.0000% 0 0.0000%
11015 9 90.0000% 0 0.0000%
11016 6 60.0000% 0 0.0000%
11017 2 20.0000% 0 0.0000%
11018 8 80.0000% 0 0.0000%
11019 2 20.0000% 0 0.0000%
11020 8 80.0000% 0 0.0000%
11021 2 20.0000% 0 0.0000%
11022 2 20.0000% 0 0.0000%
11023 7 70.0000% 0 0.0000%
11024 4 40.0000% 0 0.0000%
11025 4 40.0000% 0 0.0000%
11026 7 70.0000% 0 0.0000%
11027 7 70.0000% 0 0.0000%
11028 8 80.0000% 0 0.0000%
11029 1 10.0000% 0 0.0000%
11030 2 20.0000% 0 0.0000%
11031 8 80.0000% 0 0.0000%
11032 7 70.0000% 0 0.0000%
11033 7 70.0000% 0 0.0000%
11034 8 80.0000% 0 0.0000%
11035 4 40.0000% 0 0.0000%
--------------------------------------------------------------------------------
Average loss count : 5 Average loss ratio : 55.3333%
Maximum loss count : 10 Maximum loss ratio : 100.0000%
Minimum loss count : 1 Minimum loss ratio : 10.0000%
Average error count: 0 Average error ratio: 0.0000%
Maximum error count: 0 Maximum error ratio: 0.0000%
Minimum error count: 0 Minimum error ratio: 0.0000%
# Display the two-way packet loss statistics for TWAMP Light test session 2. (Link bundle interface.)
<Sysname> display nqa twamp-light client statistics two-way-loss test-session 2
Link bundle member: Ten-GigabitEthernet3/0/1
Latest two-way loss statistics:
Index Loss count Loss ratio Error count Error ratio
87 100 100.0000% 0 0.0000%
88 100 100.0000% 0 0.0000%
89 100 100.0000% 0 0.0000%
90 100 100.0000% 0 0.0000%
91 100 100.0000% 0 0.0000%
92 100 100.0000% 0 0.0000%
93 100 100.0000% 0 0.0000%
94 100 100.0000% 0 0.0000%
95 100 100.0000% 0 0.0000%
96 100 100.0000% 0 0.0000%
97 100 100.0000% 0 0.0000%
98 100 100.0000% 0 0.0000%
99 100 100.0000% 0 0.0000%
100 100 100.0000% 0 0.0000%
101 100 100.0000% 0 0.0000%
102 100 100.0000% 0 0.0000%
103 100 100.0000% 0 0.0000%
104 100 100.0000% 0 0.0000%
105 100 100.0000% 0 0.0000%
106 100 100.0000% 0 0.0000%
107 100 100.0000% 0 0.0000%
108 100 100.0000% 0 0.0000%
109 100 100.0000% 0 0.0000%
110 100 100.0000% 0 0.0000%
111 100 100.0000% 0 0.0000%
112 100 100.0000% 0 0.0000%
113 100 100.0000% 0 0.0000%
114 100 100.0000% 0 0.0000%
115 100 100.0000% 0 0.0000%
116 100 100.0000% 0 0.0000%
--------------------------------------------------------------------------------
Average loss count : 100 Average loss ratio : 100.0000%
Maximum loss count : 100 Maximum loss ratio : 100.0000%
Minimum loss count : 100 Minimum loss ratio : 100.0000%
Average error count : 0 Average error ratio : 0.0000%
Maximum error count : 0 Maximum error ratio : 0.0000%
Minimum error count : 0 Minimum error ratio : 0.0000%
Table 14 Command output
Field |
Description |
Link bundle member |
Statistics for the member interfaces of the link bundle interface. |
Latest two-way loss statistics |
Most recent statistics of two-way packet loss. |
Loss count |
Number of lost packets. |
Loss ratio |
Packet loss rate. |
Error count |
Number of error packets. |
Error ratio |
Packet error rate. |
Average loss count |
Average number of lost packets. |
Average loss ratio |
Average packet loss rate. |
Maximum loss count |
Maximum number of lost packets. |
Maximum loss ratio |
Maximum packet loss rate. |
Minimum loss count |
Minimum number of lost packets. |
Minimum loss ratio |
Minimum packet loss rate. |
Average error count |
Average number of error packets. |
Average error ratio |
Average packet error rate. |
Maximum error count |
Maximum number of error packets. |
Maximum error ratio |
Maximum packet error rate. |
Minimum error count |
Minimum number of error packets. |
Minimum error ratio |
Minimum packet error rate. |
Index |
ID of a reaction entry. |
Related commands
reset nqa twamp-light statistics
test-session (TWAMP Light client view)
display nqa twamp-light client test-session reaction counters
Use display nqa twamp-light client test-session reaction counters to display the current monitoring results of reaction entries for the TWAMP Light test sessions.
Syntax
display nqa twamp-light client test-session reaction counters [ session-id [ item-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
session-id: Specifies a session by its ID. The value range for this argument is 1 to 512. If you do not specify this option, the command displays all statistics information about the specified session.
item-number: Specifies a reaction entry ID in the range of 1 to 10. If you do not specify a reaction entry, the command displays the current monitoring results of all reaction entries.
Usage guidelines
If you do not specify any parameters, this command displays the monitoring results of reaction entries for all TWAMP Light test sessions.
Examples
# Display the current monitoring results of the reaction entries for TWAMP Light test session 1.
<Sysname> display nqa twamp-light client test-session reaction counters 1
Reaction counters for session 1:
Link bundle member interface Ten-GigabitEthernet3/0/1:
Index: 1
Checked element: two-way-delay
Lower-threshold: 5
Upper-threshold: 50
Action type: trap-only
Check-objects: 0
Threshold violations: 0
Reaction counters for session 2:
Index: 1
Checked element: two-way-delay
Lower-threshold: 5
Upper-threshold: 50
Action type: trap-only
Check-objects: 1
Threshold violations: 0
Table 15 Command output
Field |
Description |
Reaction counters for session |
Monitoring results of the reaction entries for the TWAMP Light test session. |
Link bundle member interface |
Information about the member interfaces of the link bundle interface. |
Index |
ID of a reaction entry. |
Checked element |
Monitored performance metric. |
Lower threshold |
Lower limit of the threshold. |
Upper threshold |
Upper limit of the threshold. |
Action type |
Action for the threshold violation event. |
Checked objects |
Number of packets that have been monitored. |
Threshold violations |
Number of threshold violations. |
Related commands
reaction checked-element two-way-delay
reaction checked-element two-way-loss
reaction checked-element two-way-jitter
display nqa y1564 group
Use display nqa y1564 group to display information about Y.1564 operation groups.
Syntax
display nqa y1564 group [ brief | name group-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
brief: Displays brief information about all NQA Y.1564 operation groups.
name group-name: Displays detailed information about a Y.1564 operation group. The group-name argument specifies the group name, a case-insensitive string of 1 to 32 characters.
Usage guidelines
If you do not specify any parameters, this command displays detailed information about all Y.1564 operation groups.
Examples
# Display brief information about all Y.1564 operation groups.
<Sysname> display nqa y1564 group brief
Group name Status
test1 Active
test2 Idle
# Display detailed information about the Y.1564 operation group test.
<Sysname> display nqa y1564 group name test
Group name: test
Status: Idle
Bound NQA entry information:
Admin-name Operation-tag
y1564 1
y1564 2
Table 16 Command output
Field |
Description |
Group name |
Name of the Y.1564 operation group. |
Status |
Status of the Y.1564 operation group: · Idle. · Active. |
Admin-name |
Admin name of a Y.1564 operation bound to the Y.1564 operation group. |
Operation-tag |
Operation tag of the Y.1564 operation. |
Related commands
nqa y1564 group
exchange-port enable
Use exchange-port enable to enable port exchange between the source port and the destination port.
Use undo exchange-port enable to restore the default.
Syntax
exchange-port enable
undo exchange-port enable
Default
Exchange between the source port and the destination port is disabled.
Views
Frame loss/latency/throughput/Y.1564 operation view
Predefined user roles
network-admin
Usage guidelines
By default, the NQA server reflects the probe packets back to the client without changing the source or destination port in the frame loss, latency, throughput, and Y.1564 operations. The client can parse the probe packets directly because the ports are not changed.
If port exchange is enabled on the NQA server, enable port exchange on the client so that the client can correctly parse the port information in the reflected packets. To enable port exchange on the server, specify the exchange-port keyword in the nqa reflector command.
Examples
# Enable port exchange between the source and destination ports.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type throughput
[Sysname-nqa-admin-test-throughput] exchange-port enable
expect data
Use expect data to configure the expected data.
Use undo expect data to restore the default.
Syntax
expect data expression [ offset number ]
undo expect data
Default
No expected data is configured.
Views
HTTP/HTTPS/TCP/UDP template view
Predefined user roles
network-admin
Parameters
expression: Specifies the expected data, a case-sensitive string of 1 to 200 characters.
offset number: Specifies the offset in bytes after which the first match operation starts. The value range for the number argument is 0 to 1000, and the default value is 0. If you do not specify an offset, the match operation starts from the beginning byte of the payload.
Usage guidelines
Upon receiving a response packet, the NQA client examines the target payload for the expected data.
· If a match is found, the NQA client verifies the NQA destination device as legal.
· If no match is found, the NQA client looks up the entire payload for a match. If no match is found again, the NQA destination device is verified as illegal. The NQA client does not perform the second round if no offset is specified. It verifies the NQA destination as illegal directly if no match is found for the first round.
Expected data check takes place in the following conditions:
· For features that use the HTTP or HTTPS template, the NQA client checks for the expected data if the response contains the Content-Length header.
· For features that use the TCP or UDP template, the NQA client checks for the expected data if the data-fill command is configured.
The first five bytes of the UDP packet payload identify the probe packet type. The start byte of the offset is the sixth byte of the UDP payload.
Examples
# In HTTP template view, set the expected data to welcome!.
<Sysname> system-view
[Sysname] nqa template http httptplt
[Sysname-nqatplt-http-httptplt] expect data welcome!
expect ip
Use expect ip to specify the expected IPv4 address.
Use undo expect ip to restore the default.
Syntax
expect ip ip-address
undo expect ip
Default
No expected IPv4 address is specified.
Views
DNS template view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the expected IPv4 address for a DNS echo request.
Usage guidelines
During a DNS operation, the NQA client compares the expected IPv4 address with the IPv4 address resolved by the DNS server. If they are the same, it considers the DNS server legal.
Examples
# In DNS template view, specify 1.1.1.1 as the expected IPv4 address.
<Sysname> system-view
[Sysname] nqa template dns dnstplt
[Sysname-nqatplt-dns-dnstplt] expect ip 1.1.1.1
expect ipv6
Use expect ipv6 to specify the expected IPv6 address.
Use undo expect ipv6 to restore the default.
Syntax
expect ipv6 ipv6-address
undo expect ipv6
Default
No expected IPv6 address is specified.
Views
DNS template view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the expected IPv6 address for a DNS echo request.
Usage guidelines
During a DNS operation, the NQA client compares the expected IPv6 address with the IPv6 address resolved by the DNS server. If they are the same, it considers the DNS server legal.
Examples
# In DNS template view, specify 1::1 as the expected IPv6 address.
<Sysname> system-view
[Sysname] nqa template dns dnstplt
[Sysname-nqatplt-dns-dnstplt] expect ipv6 1::1
expect status
Use expect status to configure the expected status code.
Use undo expect status to restore the default.
Syntax
expect status status-list
undo expect status [ status-list ]
Default
No expected status code is configured.
Views
HTTP template view
HTTPS template view
Predefined user roles
network-admin
Parameters
status-list: Specifies a space-separated list of up to 10 status code items. Each item specifies a status code or a range of status codes in the form of status-num1 to status-num2. The value ranges for both the status-num1 and status-num2 arguments are 0 to 999. The value for the status-num2 argument must be equal to or greater than the value for the status-num1 argument.
Usage guidelines
The status code of the HTTP or HTTPS packet is a three-digit field in decimal notation, and the code includes the server status information. The first digit defines the class of response.
Examples
# In HTTP template view, set the expected status codes to 200, 300, and 400 to 500.
<Sysname> system-view
[Sysname] nqa template http httptplt
[Sysname-nqatplt-http-httptplt] expect status 200 300 400 to 500
filename
Use filename to specify a file to be transferred between the FTP server and the FTP client.
Use undo filename to restore the default.
Syntax
filename filename
undo filename
Default
No file is specified.
Views
FTP operation view
FTP template view
Predefined user roles
network-admin
Parameters
filename: Specifies the name of a file, a case-insensitive string of 1 to 200 characters that cannot contain slashes (/).
Examples
# Specify config.txt as the file to be transferred between the FTP server and the FTP client for the FTP operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type ftp
[Sysname-nqa-admin-test-ftp] filename config.txt
# In FTP template view, specify config.txt as the file to be transferred between the FTP server and the FTP client.
<Sysname> system-view
[Sysname] nqa template ftp ftptplt
[Sysname-nqatplt-ftp-ftptplt] filename config.txt
frame-size
Use frame-size to specify a list of probe packet sizes.
Use undo frame-size to restore the default.
Syntax
frame-size size&<1-7>
undo frame-size [ size&<1-7> ]
Default
The probe packet size is 512 bytes for the Y.1564 operation. For the frame loss, latency, or throughput operation, the probe packet size is 1518 bytes.
Views
Frame loss/latency/throughput/Y.1564 operation view
Predefined user roles
network-admin
Parameters
size&<1-7>: Specifies a space-separated list of up to 7 packet size items. Each item specifies a packet size. The size value range is 64 to 9600 bytes.
Usage guidelines
The frame loss, latency, or throughput operation uses the list of packet sizes to send probe packets. The packet in each probe are of the same size.
If the service packet size is larger than the smallest packet size in the specified list, the probe packets might not be sent. In this case, you can use this command to adjust the probe packet size.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Specify a probe packet size list of 64, 512, 1024, and 1280 bytes for the throughput operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type throughput
[Sysname-nqa-admin-test-throughput] frame-size 64 512 1024 1280
# Set the probe packet size to 1024 bytes for the Y.1564 operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type y1564
[Sysname-nqa-admin-test-y1564] frame-size 1024
frequency
Use frequency to specify the interval at which the NQA operation repeats.
Use undo frequency to restore the default.
Syntax
frequency interval
undo frequency
Default
In NQA operation view, the interval between two consecutive voice or path jitter operations is 60000 milliseconds. The interval between two consecutive operations of other types is 0 milliseconds.
In NQA template view, the interval between two consecutive operations is 5000 milliseconds.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
UDP tracert operation view
ICMP jitter/path jitter/UDP jitter/voice operation view
Any NQA template view
Predefined user roles
network-admin
Parameters
interval: Specifies the interval between two consecutive operations, in the range of 0 to 604800000 milliseconds. An interval of 0 milliseconds configures NQA to perform the operation only once, and not to generate any statistics.
Usage guidelines
After an NQA operation starts, it repeats at the specified interval. However, when the interval is reached, but the current operation is not completed or not timed out, the next operation does not start.
Examples
# Configure the ICMP echo operation to repeat every 1000 milliseconds.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] frequency 1000
# In DNS template view, configure the DNS operation to repeat every 1000 milliseconds.
<Sysname> system-view
[Sysname] nqa template dns dnstplt
[Sysname-nqatplt-dns-dnstplt] frequency 1000
Related commands
probe timeout
hex-data-fill
Use hex-data-fill to configure a hexadecimal string to fill the probe packet payload.
Use undo hex-data-fill to restore the default.
Syntax
hex-data-fill hex
undo hex-data-fill
Default
The hexadecimal payload fill string is 00010203040506070809.
Views
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
hex: Specifies a hexadecimal string, which is case-insensitive and can contain any even number of characters in the range of 2 to 200.
Usage guidelines
The hexadecimal string will be truncated at the end or cyclically repeated to fit the payload size of the probe packet.
For example, if you configure the hexadecimal payload fill string as aa:
· Probe packet with a payload size of 1 byte will be filled with aa.
· Probe packet with a payload size of 6 bytes will be filled with aaaaaaaaaaaa.
If you execute this command and the hex-data-fill command multiple times, the most recent configuration takes effect.
Examples
# In TWAMP Light client-session view, specify aa as the hexadecimal payload fill string.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] hex-data-fill aa
Related commands
data-fill
high-performance-mode
Use high-performance-mode enable to enable the high performance mode in the UDP jitter operation.
Use undo high-performance-mode enable to disable the high performance mode in the UDP jitter operation.
Syntax
high-performance-mode enable
undo high-performance-mode enable
Default
The high performance mode is disabled in a UDP jitter operation.
Views
UDP jitter operation view
Predefined user roles
network-admin
Usage guidelines
The high performance mode improves the efficiency and accuracy of the UDP jitter operation.
After you enable the high performance mode in the UDP jitter operation, the following commands configured in the UDP jitter operation view become invalid:
· route-option bypass-route.
· reaction checked-element { jitter-ds | jitter-sd } threshold-type accumulate.
· reaction checked-element rtt threshold-type accumulate.
Examples
# Enable the high performance mode in the UDP jitter operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-jitter
[Sysname-nqa-admin-test-udp-jitter] high-performance-mode enable
history-record enable
Use history-record enable to enable the saving of history records for the NQA operation.
Use undo history-record enable to disable the saving of history records.
Syntax
history-record enable
undo history-record enable
Default
The saving of history records is enabled only for the UDP tracert operation.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
UDP tracert operation view
Predefined user roles
network-admin
Usage guidelines
To display the history records of the NQA operation, use the display nqa history command.
The undo form of the command also removes existing history records of an NQA operation.
Examples
# Enable the saving of history records for the NQA operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] history-record enable
Related commands
display nqa history
history-record keep-time
Use history-record keep-time to set the lifetime of history records for an NQA operation.
Use undo history-record keep-time to restore the default.
Syntax
history-record keep-time keep-time
undo history-record keep-time
Default
The history records of an NQA operation are kept for 120 minutes.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
UDP tracert operation view
Predefined user roles
network-admin
Parameters
keep-time: Specifies how long the history records can be saved. The value range is 1 to 1440 minutes.
Usage guidelines
When an NQA operation completes, the timer starts. All records are removed when the lifetime is reached.
Examples
# Set the lifetime of the history records to 100 minutes for the ICMP echo operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] history-record keep-time 100
history-record number
Use history-record number to set the maximum number of history records that can be saved for an NQA operation.
Use undo history-record number to restore the default.
Syntax
history-record number number
undo history-record number
Default
A maximum of 50 history records can be saved for an NQA operation.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
UDP tracert operation view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of history records that can be saved for an NQA operation. The value range is 0 to 50.
Usage guidelines
If the number of history records for an NQA operation exceeds the maximum number, earliest history records are removed.
Examples
# Set the maximum number of history records to 10 for the ICMP echo operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] history-record number 10
icmp-jitter-mode
Use icmp-jitter-mode to set the packet mode for an ICMP jitter operation.
Use undo icmp-jitter-mode to restore the default.
Syntax
icmp-jitter-mode { icmp-echo | icmp-timestamp }
undo icmp-jitter-mode
Default
An ICMP jitter operation is in timestamp packet mode.
Views
ICMP jitter operation view
Predefined user roles
network-admin
Parameters
icmp-echo: Specifies the echo packet mode.
icmp-timestamp: Specifies the timestamp packet mode.
Restrictions and guidelines
This command applies only to operations that are not started. You can execute this command for multiple times. The most recent configuration takes effect.
Only IPv4 ICMP jitter operations support this command.
Examples
# Specify the echo packet mode for the ICMP jitter operation.
<Sysname> system-view
[Sysname] nqa entry admin test1
[Sysname-nqa-admin-test1] type icmp-jitter
[Sysname-nqa-admin-test1-icmp-jitter] icmp-jitter-mode icmp-echo
init-ttl
Use init-ttl to set the initial TTL value for UDP packets in the UDP tracert operation.
Use undo init-ttl to restore the default.
Syntax
init-ttl value
undo init-ttl
Default
The initial TTL value for UDP packets in the UDP tracert operation is 1.
Views
UDP tracert operation view
Predefined user roles
network-admin
Parameters
value: Specifies the TTL value in the range of 1 to 255.
Examples
# Set the initial TTL value to 5 for UDP packets in the UDP tracert operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-tracert
[Sysname-nqa-admin-test-udp-tracert] init-ttl 5
key
Use key to set the shared key for secure RADIUS authentication.
Use undo key to restore the default.
Syntax
key { cipher | simple } string
undo key
Default
No shared key is configured for secure RADIUS authentication.
Views
RADIUS template view
Predefined user roles
network-admin
Parameters
cipher: Specifies a key in encrypted form.
simple: Specifies a key in plaintext form. For security purposes, the key specified in plaintext form will be stored in encrypted form.
string: Specifies the shared key string. Its plaintext form is a case-sensitive string of 1 to 64 characters. Its encrypted form is a case-sensitive string of 1 to 117 characters.
Usage guidelines
Make sure the NQA client and the RADIUS server have the same shared key.
Examples
# In RADIUS template view, set the shared key to abc in plain text for secure RADIUS authentication.
<Sysname> system-view
[Sysname] nqa template radius radiustplt
[Sysname-nqatplt-radius-radiustplt] key simple abc
link-bundle-interface
Use link-bundle-interface to enable the TWAMP Light test for all member interfaces of the link bundle interface.
Use undo link-bundle-interface to restore the default.
Syntax
link-bundle-interface interface-type interface-number
undo link-bundle-interface
Default
The TWAMP Light test for all member interfaces of the link bundle interface is disabled.
Views
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number. In this software version, you can specify only a Layer 3 aggregate interface for the argument.
Usage guidelines
For successful probes, make sure the specified interface is up.
By default, if the output interface for TWAMP Light probe packets is a Layer 3 aggregate interface or Layer 3 aggregate subinterface, the device automatically selects a member interface. The test is performed on the link associated with the member interface, but the test result will be used for measuring the quality of the entire aggregate link. After you configure this feature, the device performs the test on all member interfaces of the aggregate interface to measure the quality of links associated to all member interfaces.
For a successful and accurate test, enable or disable the TWAMP Light test for all member interfaces of the aggregate interface on both the TWAMP Light client and server.
Examples
# Enable the TWAMP Light test on all member interfaces of aggregate interface Route-Aggregation 1.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] link-bundle-interface route-aggregation 1
lsr-path
Use lsr-path to specify a loose source routing (LSR) path.
Use undo lsr-path to restore the default.
Syntax
lsr-path ip-address&<1-8>
undo lsr-path
Default
No LSR path is configured.
Views
Path jitter operation view
Predefined user roles
network-admin
Parameters
ip-address&<1-8>: Specifies a space-separated list of up to eight IP addresses. Each IP address represents a hop on the path.
Usage guidelines
The path jitter operation first uses tracert to detect each hop to the destination. It then sends ICMP echo requests to measure the delay and jitters from the source to each node. If multiple routes exist between the source and destination, the operation uses the path specified by using lsr-path command.
Examples
# Specify 10.1.1.20 and 10.1.2.10 as the hops on the LSR path for the path jitter operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type path-jitter
[Sysname-nqa-admin-test- path-jitter] lsr-path 10.1.1.20 10.1.2.10
mailbox
Use mailbox to specify the mailbox name to be used in the IMAP operation.
Use undo mailbox to restore the default.
Syntax
mailbox mailbox-name
undo mailbox
Default
The IMAP operation uses the mailbox name INBOX.
Views
IMAP template view
Predefined user roles
network-admin
Parameters
mailbox-name: Specifies the mailbox name, a case-sensitive string of 1 to 64 characters.
Examples
# Set the mailbox name to fortest1 for the IMAP template.
<Sysname> system-view
[Sysname] nqa template imap imaptplt
[Sysname-nqatplt-imap-imaptplt] mailbox fortest1
max-failure
Use max-failure to set the maximum number of consecutive probe failures in a UDP tracert operation.
Use undo max-failure to restore the default.
Syntax
max-failure times
undo max-failure
Default
A UDP tracert operation stops and fails when it detects five consecutive probe failures.
Views
UDP tracert operation view
Predefined user roles
network-admin
Parameters
times: Specifies the maximum number in the range of 0 to 255. When this argument is set to 0 or 255, the UDP tracert operation does not stop when consecutive probe failures occur.
Usage guidelines
When a UDP tracert operation detects the maximum number of consecutive probe failures, the operation fails and stops probing the path.
Examples
# Set the maximum number of consecutive probe failures to 20 in a UDP tracert operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-tracert
[Sysname-nqa-admin-test-udp-tracert] max-failure 20
mode
Use mode to set the data transmission mode for the FTP operation.
Use undo mode to restore the default.
Syntax
mode { active | passive }
undo mode
Default
The FTP operation uses the data transmission mode active.
Views
FTP operation view
FTP template view
Predefined user roles
network-admin
Parameters
active: Sets the data transmission mode to active. The FTP server initiates a connection request.
passive: Sets the data transmission mode to passive. The FTP client initiates a connection request.
Examples
# Set the data transmission mode to passive for the FTP operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type ftp
[Sysname-nqa-admin-test-ftp] mode passive
# In FTP template view, set the data transmission mode to passive for the FTP operation.
<Sysname> system-view
[Sysname] nqa template ftp ftptplt
[Sysname-nqatplt-ftp-ftptplt] mode passive
mpls-simulation enable
Use mpls-simulation enable to enable MPLS simulation in the UDP jitter operation.
Use undo mpls-simulation enable to restore the default.
Syntax
mpls-simulation enable [ exp exp-value ]
undo mpls-simulation enable
Default
MPLS simulation is disabled in the UDP jitter operation.
Views
UDP jitter operation view
Predefined user roles
network-admin
Parameters
exp exp-value: Specifies the EXP value for the MPLS packets. The value range is 0 to 7, and the default is 0.
Usage guidelines
This command is configurable only after the high-performance-mode enable command is configured in the UDP jitter operation.
With MPLS simulation enabled, the UDP jitter operation will send MPLS packets as probe packets to test the forwarding performance of MPLS traffic from the NQA client to the designated NQA server.
The UDP jitter operation can test the forwarding performance of MPLS traffic only over the link between two directly connected device interfaces.
For the MPLS simulation-enabled UDP jitter operation to work correctly, the following requirements must be met:
· The NQA client must be directly connected to the NQA server.
· MPLS must be enabled (by using the mpls enable command) on the interconnection interfaces between the NQA client and NQA server.
For more information about the mpls enable command, see basic MPLS commands in MPLS Command Reference.
· The destination address of the operation must be an IPv4 address.
Examples
# Enable MPLS simulation in the UDP jitter operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-jitter
[Sysname-nqa-admin-test-udp-jitter] mpls-simulation enable exp 5
next-hop ip
Use next-hop ip to specify the next hop IPv4 address for probe packets.
Use undo next-hop ip to restore the default.
Syntax
next-hop ip ip-address
undo next-hop ip
Default
No next hop IPv4 address is specified for probe packets.
Views
ICMP echo operation view
ICMP/TCP half open template view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the IPv4 address of the next hop.
Usage guidelines
If the next hop IPv4 address is not configured, the device searches the routing table to determine the next hop IPv4 address for the probe packets.
Examples
# Specify 10.1.1.1 as the next hop IPv4 address for the ICMP echo operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] next-hop ip 10.1.1.1
next-hop ipv6
Use next-hop ipv6 to specify the next hop IPv6 address for probe packets.
Use undo next-hop ipv6 to restore the default.
Syntax
next-hop ipv6 ipv6-address
undo next-hop ipv6
Default
No next hop IPv6 address is specified for probe packets.
Views
ICMP echo operation view
ICMP/TCP half open template view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies the IPv6 address of the next hop. IPv6 link-local addresses are not supported.
Usage guidelines
If the next hop IPv6 address is not configured, the device searches the routing table to determine the next hop IPv6 address for the probe packets.
Examples
# Specify 10::1 as the next hop IPv6 address for the ICMP echo operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] next-hop ipv6 10::1
no-fragment enable
Use no-fragment enable to enable the no-fragmentation feature.
Use undo no-fragment enable to disable the no-fragmentation feature.
Syntax
no-fragment enable
undo no-fragment enable
Default
The no-fragmentation feature is disabled.
Views
UDP tracert operation view
Predefined user roles
network-admin
Usage guidelines
The no-fragmentation feature sets the DF field to 1. Packets with the DF field set cannot be fragmented during the forwarding process.
You can use this command to test the path MTU of a link.
Examples
# Enable the no-fragmentation feature for the UDP tracert operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-tracert
[Sysname-nqa-admin-test-udp-tracert] no-fragment enable
nqa
Use nqa to create an NQA operation and enter its view, or enter the view of an existing NQA operation.
Use undo nqa to remove the operation.
Syntax
nqa entry admin-name operation-tag
undo nqa { all | entry admin-name operation-tag }
Default
No NQA operations exist.
Views
System view
Predefined user roles
network-admin
Parameters
admin-name operation-tag: Specifies an NQA operation by its administrator name and operation tag. The admin-name argument represents the name of the administrator who creates the NQA operation. The operation-tag argument represents the operation tag. Each of the arguments is a case-insensitive string of 1 to 32 characters that cannot contain hyphens (-).
all: Removes all NQA operations, templates, and operation groups.
Usage guidelines
After you create an NQA operation, use the type command to specify the operation type for it. Only one operation type can be specified for one operation. After that, you can use the nqa entry command to directly enter the NQA operation type view.
To remove an operation group that contains operations, remove all the operations from the group first. This restriction does not apply to the undo nqa all command.
Examples
# Create an NQA operation with administrator name admin and operation tag test, and enter NQA operation view.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test]
nqa agent enable
Use nqa agent enable to enable the NQA client.
Use undo nqa agent enable to disable the NQA client and stop all operations being performed.
Syntax
nqa agent enable
undo nqa agent enable
Default
The NQA client is enabled.
Views
System view
Predefined user roles
network-admin
Examples
# Enable the NQA client.
<Sysname> system-view
[Sysname] nqa agent enable
Related commands
nqa server enable
nqa report-ftp
Use nqa report-ftp to configure the FTP server to which the NQA client uploads the operation results.
Use undo nqa report-ftp to restore the default.
Syntax
nqa report-ftp url url [ username username ] [ password { cipher | simple } string ]
undo nqa report-ftp
Default
No FTP server is configured for the NQA client to upload operation results.
Views
System view
Predefined user roles
network-admin
Parameters
url: Specifies the URL of the FTP server, a case-sensitive string of 1 to 255 characters. The following table describes the valid URL formats.
URL format |
Parameter description |
ftp://host |
The host parameter represents the host name of the FTP server. The host name is a dot-separated case-sensitive string including letters, digits, hyphens (-), and underscores (_). Host names are composed of series of labels, aabbcc.com for example. Each label consists of 1 to 63 characters. Consecutive dots (.) are not allowed. The port parameter specifies the port number in the range of 0 to 65535. |
ftp://host:port |
username username: Specifies the FTP login username, a case-sensitive string of 1 to 32 characters. Do not specify this option if no username is required for FTP login.
password: Specifies the FTP login password. Do not specify this keyword if no password is required for FTP login.
cipher: Specifies a password in encrypted form.
simple: Specifies a password in plaintext form. For security purposes, the password specified in plaintext form will be stored in encrypted form.
string: Specifies the FTP login password. Its plaintext form is a case-sensitive string of 1 to 32 characters. Its encrypted form is a case-sensitive string of 1 to 73 characters.
Usage guidelines
Both path quality analysis operations and Y.1564 operations support uploading the operation results to the FTP server.
Examples
# Configure the NQA client to upload the operation results to the FTP server at ftp://19.23.1.25, and set the login username and password to test and 123456, respectively.
<Sysname> system-view
[Sysname] nqa report-ftp url ftp://19.23.1.25 username test password simple 123456
nqa rfc2544 group
Use nqa rfc2544 group to create a path quality analysis operation group and enter its view, or enter the view of an existing path quality analysis operation group.
Use undo nqa rfc2544 group to delete a path quality analysis operation group.
Syntax
nqa rfc2544 group group-name
undo nqa rfc2544 group group-name
Default
No path quality analysis operation groups exist.
Views
System view
Predefined user roles
network-admin
Parameters
group-name: Specifies a path quality analysis operation group by its name, a case-insensitive string of 1 to 32 characters.
Usage guidelines
A path quality analysis operation group is a set of path quality analysis operations. In path quality analysis operation group view, you can start or stop all the path quality analysis operations in the path quality analysis operation group.
To remove a path quality analysis operation group that contains path quality analysis operations, remove all the path quality analysis operations from the group first.
Examples
# Create a path quality analysis operation group named test, and enter its view.
<Sysname> system-view
[Sysname] nqa rfc2544 group test
[Sysname-nqa-rfc2544group-test]
nqa schedule
Use nqa schedule to configure scheduling parameters for an NQA operation.
Use undo nqa schedule to stop the operation.
Syntax
nqa schedule admin-name operation-tag start-time { hh:mm:ss [ yyyy/mm/dd | mm/dd/yyyy ] | now } lifetime { lifetime | forever } [ recurring ]
undo nqa schedule admin-name operation-tag
Default
No schedule is configured for an NQA operation.
Views
System view
Predefined user roles
network-admin
Parameters
admin-name operation-tag: Specifies an NQA operation by its administrator name and operation tag. The admin-name argument represents the name of the administrator who creates the NQA operation. The operation-tag argument represents the operation tag. Each of the arguments is a case-insensitive string of 1 to 32 characters that cannot contain hyphens (-).
start-time: Specifies the start time and date of the NQA operation.
hh:mm:ss: Specifies the start time of an NQA operation.
yyyy/mm/dd: Specifies the start date of an NQA operation. The default value is the current system time, and the value for the yyyy argument is in the range of 2000 to 2035.
mm/dd/yyyy: Specifies the start date of an NQA operation. The default value is the current system time, and the value for the yyyy argument is in the range of 2000 to 2035.
now: Starts the operation immediately.
lifetime: Specifies the duration of an operation.
lifetime: Specifies the duration of an operation in seconds. The value range is 1 to 2147483647.
forever: Performs the operation until you stop it by using the undo nqa schedule command.
recurring: Runs the operation automatically at the start time and for the specified duration. If you do not specify this keyword, the NQA operation is performed only once at the specified date and time.
Usage guidelines
You cannot enter the view of a scheduled NQA operation. If you want to enter such a view, use the undo nqa schedule command to stop the NQA operation first. This restriction does not apply to path quality analysis operations.
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 time 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.
Specify a lifetime long enough for an operation to complete.
The path quality analysis operations and Y.1564 operations cannot be scheduled.
Examples
# Schedule the operation with administrator name admin and operation tag test to start on 08:08:08 2008/08/08 and last 1000 seconds.
<Sysname> system-view
[Sysname] nqa schedule admin test start-time 08:08:08 2008/08/08 lifetime 1000 recurring
Related commands
destination ip
display clock (Fundamentals Command Reference)
nqa entry
type
nqa template
Use nqa template to create an NQA template and enter its view, or enter the view of an existing NQA template.
Use undo nqa template to remove an NQA template.
Syntax
nqa template { arp | dns | ftp | http | https | icmp | imap | pop3 | radius | smtp | snmp | ssl | tcp | tcphalfopen | udp } name
undo nqa template { arp | dns | ftp | http | https | icmp | imap | pop3 | radius | smtp | snmp | ssl | tcp | tcphalfopen | udp } name
Default
No NQA templates exist.
Views
System view
Predefined user roles
network-admin
Parameters
arp: Specifies the ARP template.
dns: Specifies the DNS template.
ftp: Specifies the FTP template.
http: Specifies the HTTP template.
https: Specifies the HTTPS template.
icmp: Specifies the ICMP template.
imap: Specifies the IMAP template.
pop3: Specifies the POP3 template.
radius: Specifies the RADIUS template.
smtp: Specifies the SMTP template.
snmp: Specifies the SNMP template.
ssl: Specifies the SSL template.
tcp: Specifies the TCP template.
tcphalfopen: Specifies the TCP half open template.
udp: Specifies the UDP template.
name: Specifies the name of the NQA template, a case-insensitive string of 1 to 32 characters.
Examples
# Create an ICMP template named icmptplt, and enter its view.
<Sysname> system-view
[Sysname] nqa template icmp icmptplt
[Sysname-nqatplt-icmp-icmptplt]
nqa twamp-light client
Use nqa twamp-light client to enable the TWAMP Light client and enter its view, or enter the view of the enabled TWAMP Light client.
Use undo nqa twamp-light client to disable the TWAMP Light client.
Syntax
nqa twamp-light client
undo nqa twamp-light client
Default
The TWAMP Light client is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
The Two-Way Active Measurement Protocol (TWAMP) measures network performance in the complex networks. To create test sessions, you must first use the nqa twamp-light client command to enter TWAMP Light client view.
The undo nqa twamp-light client command disables the TWAMP Light client and deletes the test sessions on the TWAMP Light client.
Examples
# Enable the TWAMP Light client and enter its view.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client]
nqa twamp-light sender
Use nqa twamp-light sender to enable the TWAMP Light sender and enter its view, or enter the view of the enabled TWAMP Light sender.
Use undo nqa twamp-light sender to disable the TWAMP Light sender.
Syntax
nqa twamp-light sender
undo nqa twamp-light sender
Default
The TWAMP Light sender is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
In the TWAMP Light sender view, you can start or stop a TWAMP Light test.
Examples
# Enable the TWAMP Light sender and enter its view.
<Sysname> system-view
[Sysname] nqa twamp-light sender
[Sysname-nqa-twamp-light-sender]
nqa y1564 group
Use nqa y1564 group to create a Y.1564 operation group and enter its view, or enter the view of an existing Y.1564 operation group.
Use undo nqa y1564 group to delete a Y.1564 operation group and all configuration in its view.
Syntax
nqa y1564 group group-name
undo nqa y1564 group group-name
Default
No Y.1564 operation groups exist.
Views
System view
Predefined user roles
network-admin
Parameters
group-name: Specifies the group name, a case-insensitive string of 1 to 32 characters.
Usage guidelines
A Y.1564 operation group is a set of Y.1564 operations. By executing the start or stop command in Y.1564 operation group view, you can start or stop all the Y.1564 operations in the Y.1564 operation group.
To remove a Y.1564 operation group that contains Y.1564 operations, remove all the Y.1564 operations from the group first.
Examples
# Create a Y.1564 operation group named test and enter its view.
<Sysname> system-view
[Sysname] nqa y1564 group test
[Sysname-nqa-y1564group-test]
Related commands
bind nqa-entry
start
stop
one-way delay-measure enable
Use one-way delay-measure enable to enable one-way delay measurement for a TWAMP Light session.
Use undo one-way delay-measure enable to disable one-way delay measurement for a TWAMP Light session.
Syntax
one-way delay-measure enable
undo one-way delay-measure enable
Default
One-way delay measurement is disabled for a TWAMP Light session.
Views
TWAMP Light client-session view
Predefined user roles
network-admin
Usage guidelines
By default, TWAMP Light measures two-way path delay, jitter, and packet loss rate. After you enable one-way delay measurement for a TWAMP Light session and start the session, TWAMP Light also measures delay on the following directions separately:
· From the TWAMP Light client to TWAMP Light server.
· From the TWAMP Light server to TWAMP Light client.
You can use one-way delay-measure global enable or one-way delay-measure enable to enable one-way delay measurement for the TWAMP Light session. The one-way delay-measure global enable command applies to all new test sessions on the TWAMP Light client. The one-way delay-measure enable command applies to only the specified test session.
Examples
# Enable one-way delay measurement for the TWAMP Light session.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] one-way delay-measure enable
Related commands
one-way delay-measure global enable
one-way delay-measure global enable
Use one-way delay-measure global enable to enable one-way delay measurement for the TWAMP Light client.
Use undo one-way delay-measure global enable to enable one-way delay measurement for the TWAMP Light client.
Syntax
one-way delay-measure global enable
undo one-way delay-measure global enable
Default
One-way delay measurement is disabled for the TWAMP Light client.
Views
TWAMP Light client view
Predefined user roles
network-admin
Usage guidelines
By default, TWAMP Light measures two-way path delay, jitter, and packet loss rate. After you enable one-way delay measurement for a TWAMP Light session and start the session, TWAMP Light also measures delay on the following directions separately:
· From the TWAMP Light client to TWAMP Light server.
· From the TWAMP Light server to TWAMP Light client.
You can use one-way delay-measure global enable or one-way delay-measure enable to enable one-way delay measurement for the TWAMP Light session. The one-way delay-measure global enable command applies to all new test sessions on the TWAMP Light client. The one-way delay-measure enable command applies to only the specified test session.
Examples
# Enable one-way delay measurement for the TWAMP Light client.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] one-way delay-measure global enable
Related commands
one-way delay-measure enable
operation (FTP operation view)
Use operation to specify the operation type for the FTP operation.
Use undo operation to restore the default.
Syntax
operation { get | put }
undo operation
Default
The FTP operation type is get.
Views
FTP operation view
FTP template view
Predefined user roles
network-admin
Parameters
get: Gets a file from the FTP server.
put: Transfers a file to the FTP server.
Usage 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 for occupying much network bandwidth.
Examples
# Set the operation type to put for the FTP operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type ftp
[Sysname-nqa-admin-test-ftp] operation put
# In FTP template view, set the operation type to put for the FTP operation.
<Sysname> system-view
[Sysname] nqa template ftp ftptplt
[Sysname-nqatplt-ftp-ftptplt] operation put
Related commands
password
username
operation (HTTP/HTTPS operation view)
Use operation to specify the operation type for the HTTP or HTTPS operation.
Use undo operation to restore the default.
Syntax
operation { get | post | raw }
undo operation
Default
The HTTP or HTTPS operation type is get.
Views
HTTP operation view
HTTP/HTTPS template view
Predefined user roles
network-admin
Parameters
get: Gets data from the HTTP or HTTPS server.
post: Transfers data to the HTTP or HTTPS server.
raw: Sends the RAW request to the HTTP or HTTPS server.
Usage guidelines
The HTTP and HTTPS operations use HTTP and HTTPS requests as probe packets.
For the get or post operation, the content in the request is obtained from the URL specified by the url command.
For the raw operation, the content in the request is configured in raw request view. You can use the raw-request command to enter the raw request view.
Examples
# Set the operation type to raw for the HTTP operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type http
[Sysname-nqa-admin-test-http] operation raw
# In HTTP template view, set the operation type to raw for the HTTP operation.
[Sysname] nqa template http httptplt
[Sysname-nqatplt-http-httptplt] operation raw
password
raw-request
username
out interface
Use out interface to specify the output interface for probe packets.
Use undo out interface to restore the default.
Syntax
out interface interface-type interface-number
undo out interface
Default
The output interface for probe packets is not specified. The NQA client determines the output interface based on the routing table lookup.
Views
ICMP echo operation view
DHCP operation view
UDP tracert operation view
UDP jitter operation view
Frame loss/latency/throughput/Y.1564 operation view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
Usage guidelines
For successful operation, the specified output interface must be up.
If both the next-hop and out interface commands are configured for the ICMP echo operation, the out interface command does not take effect.
Examples
# Specify Ten-GigabitEthernet 3/0/1 as the output interface for probe packets in the UDP tracert operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-tracert
[Sysname-nqa-admin-test-udp-tracert] out interface ten-gigabitethernet 3/0/1
password
Use password to specify a password.
Use undo password to restore the default.
Syntax
password { cipher | simple } string
undo password
Default
No password is specified.
Views
FTP/HTTP operation view
FTP/HTTP/HTTPS/IMAP/POP3/RADIUS template view
Predefined user roles
network-admin
Parameters
cipher: Specifies a password in encrypted form.
simple: Specifies a password in plaintext form. For security purposes, the password specified in plaintext form will be stored in encrypted form.
string: Specifies the password. This argument is case sensitive and its value varies as follows:
· For FTP, HTTP, and HTTPS operations, the plaintext form of the password is a string of 1 to 32 characters. The encrypted form of the password is a string of 1 to 73 characters.
· For RADIUS templates, the plaintext form of the password is a string of 1 to 64 characters. The encrypted form of the password is a string of 1 to 117 characters.
· For IMAP and POP3 templates, the plaintext form of the password is a string of 1 to 40 characters. The encrypted form of the password is a string of 1 to 85 characters.
Examples
# Set the FTP login password to ftpuser.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type ftp
[Sysname-nqa-admin-test-ftp] password simple ftpuser
# Set the FTP login password to ftpuser in FTP template view.
<Sysname> system-view
[Sysname] nqa template ftp ftptplt
[Sysname-nqatplt-ftp-ftptplt] password simple ftpuser
Related commands
operation
username
performance-test enable
Use performance-test enable to enable the service performance test in a Y.1564 operation.
Use undo performance-test enable to disable the service performance test in a Y.1564 operation.
Syntax
performance-test enable [ duration duration ]
undo performance-test enable
Default
The service performance test is enabled in a Y.1564 operation.
Views
Y.1564 operation view
Predefined user roles
network-admin
Parameters
duration duration: Specifies the duration of the service performance test in minutes. The value range is 1 to 1440, and the default is 15.
Usage guidelines
By default, the service performance test is enabled and will run at the configured CIR for 15 minutes in a Y.1564 operation. You can use this command to change the test duration or disable the test in a Y.1564 operation.
Examples
# Enable the service performance test in a Y.1564 operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type y1564
[Sysname-nqa-admin-test-y1564] performance-test enable
Related commands
Bandwidth
pir-test enable
Use pir-test enable to enable the PIR test in a Y.1564 operation.
Use undo pir-test enable to disable the PIR test in a Y.1564 operation.
Syntax
pir-test enable [ duration duration ]
undo pir-test enable
Default
The PIR test is enabled in a Y.1564 operation.
Views
Y.1564 operation view
Predefined user roles
network-admin
Parameters
duration duration: Specifies the duration of the PIR test in seconds. The value range is 1 to 60, and the default is 3.
Usage guidelines
The PIR test can operate in color-aware mode or non-color-aware mode.
· In color-aware mode, the PIR test transmits green frames at a rate equal to the CIR and yellow frames at a rate equal to the PIR.
· In non-color-aware mode, the PIR test transmits frames at a rate equal to CIR + PIR.
You can enable or disable the color-aware mode in a Y.1564 operation.
Examples
# Enable the PIR test in a Y.1564 operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type y1564
[Sysname-nqa-admin-test-y1564] pir-test enable
Related commands
bandwidth
color-aware-mode enable
priority 8021p
Use priority 8021p to set the 802.1p priority for the probe packets.
Use undo priority 8021p to restore the default.
Syntax
priority 8021p value
undo priority 8021p
Default
The 802.1p priority of the probe packets is 0.
Views
Frame loss/latency/throughput/Y.1564 operation view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
value: Specifies the 802.1p priority value in the range of 0 to 7.
Usage guidelines
To test the service quality for specific packet priorities in a congested Layer 2 network, you can use this command to specify the priorities.
For more information about 802.1p priority, see QoS in ACL and QoS Configuration Guide.
Examples
# Set the 802.1p priority to 1 for probe packets in the latency operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type latency
[Sysname-nqa-admin-test-latency] priority 8021p 1
probe count
Use probe count to specify the probe times.
Use undo probe count to restore the default.
Syntax
probe count times
undo probe count
Default
In an UDP tracert operation, the NQA client performs three probes to each hop along the path.
In other types of operations, the NQA client performs one probe to the destination per operation.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
UDP tracert operation view
ICMP jitter/UDP jitter operation view
Predefined user roles
network-admin
Parameters
times: Specifies the probe times.
· For the UDP tracert operation, this argument specifies the times of probes to each hop along the path. The value range for this argument is 1 to 10.
· For other types of operations, this argument specifies the times of probes to the destination per operation. The value range for this argument is 1 to 15.
Usage guidelines
The following describes how NQA performs different types of operations:
· A TCP or DLSw 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.
· A DHCP operation gets an IP address through DHCP.
· A DNS operation translates a domain name to an IP address.
· An ICMP echo 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.
· A UDP tracert operation determines the routing path from the source to the destination. The number of probe packets sent to each hop is set by using the probe count command.
If an operation is to perform multiple probes, the NQA client starts a new probe in one of the following conditions:
· The NQA client receives responses to packets sent in the last probe.
· The probe timeout time expires.
This command is not available for the voice or path jitter operations. Each of these operations performs only one probe.
Examples
# Configure the ICMP echo operation to perform 10 probes.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] probe count 10
probe duration
Use probe duration to specify the probe duration.
Use undo probe duration to restore the default.
Syntax
probe duration time
undo probe duration
Default
The probe duration is 60 seconds.
Views
Frame loss/latency/throughput operation view
Predefined user roles
network-admin
Parameters
time: Specifies the probe duration in seconds. The value range is 10 to 172800.
Examples
# Set the probe duration to 90 seconds for the throughput operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type throughput
[Sysname-nqa-admin-test-throughput] probe duration 90
probe interval
Use probe interval to specify the interval between consecutive probes.
Use undo probe interval to restore the default.
Syntax
probe interval interval
undo probe interval
Default
The probe interval is 4 seconds.
Views
Frame loss/latency/throughput operation view
Predefined user roles
network-admin
Parameters
time: Specifies the probe interval in seconds. The value range is 1 to 60.
Usage guidelines
After a frame loss, latency, or throughput operation probe is complete, the NQA client waits the specified probe interval before starting another probe.
Examples
# Set the probe interval to 30 seconds for the throughput operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type throughput
[Sysname-nqa-admin-test-throughput] probe interval 30
probe packet-interval
Use probe packet-interval to configure the packet sending interval in the probe.
Use undo probe packet-interval to restore the default.
Syntax
probe packet-interval interval
undo probe packet-interval
Default
The packet sending interval is 20 milliseconds.
Views
ICMP jitter/path jitter/UDP jitter/voice operation view
Predefined user roles
network-admin
Parameters
interval: Specifies the sending interval in the range of 10 to 60000 milliseconds.
Examples
# Configure the UDP jitter operation to send packets every 100 milliseconds.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-jitter
[Sysname-nqa-admin-test-udp-jitter] probe packet-interval 100
probe packet-number
Use probe packet-number to set the number of packets to be sent per probe.
Use undo probe packet-number to restore the default.
Syntax
probe packet-number number
undo probe packet-number
Default
An ICMP jitter, UDP jitter, or path jitter probe sends 10 packets and a voice probe sends 1000 packets.
Views
ICMP jitter/path jitter/UDP jitter/voice operation view
Predefined user roles
network-admin
Parameters
number: Specifies the number of packets to be sent per probe. Available value ranges include:
· 10 to 1000 for the ICMP jitter, UDP jitter, and path jitter operations.
· 10 to 60000 for the voice operation.
Examples
# Configure the UDP jitter probe to send 100 packets.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-jitter
[Sysname-nqa-admin-test-udp-jitter] probe packet-number 100
probe packet-timeout
Use probe packet-timeout to set the amount of time the NQA client waits for a response from the destination device.
Use undo probe packet-timeout to restore the default.
Syntax
probe packet-timeout timeout
undo probe packet-timeout
Default
The response timeout time in the ICMP jitter, UDP jitter, or path jitter operation is 3000 milliseconds.
The response timeout time in the voice operation is 5000 milliseconds.
Views
ICMP jitter/path jitter/UDP jitter/voice operation view
Predefined user roles
network-admin
Parameters
timeout: Specifies the timeout time in milliseconds. The value range is 10 to 3600000.
Examples
# Set the response timeout time to 100 milliseconds in the UDP jitter operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-jitter
[Sysname-nqa-admin-test-udp-jitter] probe packet-timeout 100
probe timeout
Use probe timeout to set the probe timeout time.
Use undo probe timeout to restore the default.
Syntax
probe timeout timeout
undo probe timeout
Default
The timeout time of a probe is 3000 milliseconds.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
UDP tracert operation view
Frame loss/latency/throughput/Y.1564 operation view
Any NQA template view
Predefined user roles
network-admin
Parameters
timeout: Specifies the probe timeout time in milliseconds. The value range for this argument varies as follows:
· For FTP and HTTP operations, the value range is 10 to 86400000.
· For DHCP, DNS, DLSw, ICMP echo, SNMP, TCP, UDP echo, and UDP tracert operations, the value range is 10 to 3600000.
· For frame loss, latency, throughput, and Y.1564 operations, the value range is 10 to 60000.
· For FTP, HTTP, and HTTPS templates, the value range is 10 to 86400000.
· For other types of NQA templates, the value range is 10 to 3600000.
Usage guidelines
If a probe does not complete within the period, the probe is timed out.
Examples
# Set the probe timeout time to 10000 milliseconds for the DHCP operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type dhcp
[Sysname-nqa-admin-test-dhcp] probe timeout 10000
# In HTTP template view, set the probe timeout time to 10000 milliseconds for the HTTP operation.
<Sysname> system-view
[Sysname] nqa template http httptplt
[Sysname-nqatplt-http-httptplt] probe timeout 10000
raw-request
Use raw-request to enter raw request view and specify the content of an HTTP or HTTPS request.
Use undo raw-request to restore the default.
Syntax
raw-request
undo raw-request
Default
The contents of an HTTP or HTTPS raw request are not specified.
Views
HTTP operation view
HTTP/HTTPS template view
Predefined user roles
network-admin
Usage guidelines
This command places you in raw request view and deletes the previously configured request content. To ensure successful operations, make sure the request content is in the correct format.
If the HTTP or HTTPS operation type is set to raw, you must enter raw request view and configure the request content to be sent to the HTTP or HTTPS server. To ensure successful operations, make sure the request content does not contain command aliases configured by using the alias command. For more information about the alias command, see CLI commands in Fundamentals Command Reference.
Examples
# Enter raw request view and specify the content of a GET request for the HTTP operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type http
[Sysname-nqa-admin-test-http] raw-request
[Sysname-nqa-admin-test-http-raw-request] GET /sdn/ui/app/index HTTP/1.0\r\nHost: 172.0.0.2\r\n\r\n
# In HTTP template view, enter raw request view and specify the content of a POST request for the HTTP operation.
<Sysname> system-view
[Sysname] nqa template http httptplt
[Sysname-nqatplt-http-httptplt] raw-request
[Sysname-nqatplt-http-httptplt-raw-request] POST /sdn/ui/app/index HTTP/1.0\r\nHost:
172.0.0.2\r\nAuthorization: Basic cm9vdDoxMjM0NTY=\r\n\r\n
reaction checked-element { jitter-ds | jitter-sd }
Use reaction checked-element { jitter-ds | jitter-sd } to configure a reaction entry for monitoring the one-way jitter in the NQA operation.
Use undo reaction to delete a reaction entry.
Syntax
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 } ]
undo reaction item-number
Default
No reaction entries for monitoring one-way jitter exist.
Views
ICMP jitter/UDP jitter/voice operation view
Predefined user roles
network-admin
Parameters
item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.
jitter-ds: Specifies the destination-to-source jitter of each probe packet as the monitored element (or performance metric).
jitter-sd: Specifies source-to-destination jitter of each probe packet as the monitored element.
threshold-type: Specifies a threshold type.
accumulate accumulate-occurrences: Checks the total number of threshold violations in the operation. The value range is 1 to 14999 for the ICMP jitter and UDP jitter operations, and 1 to 59999 for the voice operation.
average: Checks the average one-way jitter.
threshold-value: Specifies threshold range in milliseconds.
upper-threshold: Specifies the upper limit in the range of 0 to 3600000.
lower-threshold: Specifies the lower limit in the range of 0 to 3600000. It must not be greater than the upper limit.
action-type: Specifies the action to be triggered. The default action is none.
none: Specifies the action of displaying results on the terminal display.
trap-only: Specifies the action of displaying results on the terminal display and meanwhile sending SNMP trap messages to the NMS.
Usage guidelines
You cannot edit a reaction entry after it is created. To change the attributes in a reaction entry, use the undo reaction command to delete the entry, and then configure a new one.
Only successful probe packets are monitored. Statistics about failed probe packets are not collected.
Examples
# Create reaction entry 1 for monitoring the average destination-to-source jitter of UDP jitter packets, and set the upper limit to 50 milliseconds and the lower limit to 5 milliseconds. Before the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the average destination-to-source jitter is checked against the threshold range. If it exceeds the upper limit, the state of the reaction entry is set to over-threshold. If it is below the lower limit, the state is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-jitter
[Sysname-nqa-admin-test-udp-jitter] reaction 1 checked-element jitter-ds threshold-type average threshold-value 50 5 action-type trap-only
# Create reaction entry 2 for monitoring the destination-to-source jitter of UDP jitter probe packets, and set the upper limit to 50 milliseconds, and the lower limit to 5 milliseconds. Before the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the destination-to-source jitter is checked against the threshold range. If the total number of threshold violations reaches or exceeds 100, the state of the entry is set to over-threshold. Otherwise, the state of the entry is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-jitter
[Sysname-nqa-admin-test-udp-jitter] reaction 2 checked-element jitter-ds threshold-type accumulate 100 threshold-value 50 5 action-type trap-only
reaction checked-element { owd-ds | owd-sd }
Use reaction checked-element { owd-ds | owd-sd } to configure a reaction entry for monitoring the one-way delay.
Use undo reaction to delete a reaction entry.
Syntax
reaction item-number checked-element { owd-ds | owd-sd } threshold-value upper-threshold lower-threshold
undo reaction item-number
Default
No reaction entries for monitoring the one-way delay exist.
Views
ICMP jitter/UDP jitter/voice operation view
Predefined user roles
network-admin
Parameters
item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.
owd-ds: Specifies the destination-to-source delay of each probe packet as the monitored element.
owd-sd: Specifies the source-to-destination delay of each probe packet as the monitored element.
threshold-value: Specifies threshold range in milliseconds.
upper-threshold: Specifies the upper limit in the range of 0 to 3600000.
lower-threshold: Specifies the lower limit in the range of 0 to 3600000. It must not be greater than the upper limit.
Usage guidelines
You cannot edit a reaction entry after it is created. To change the attributes in a reaction entry, use the undo reaction command to delete the entry, and then configure a new one.
Only successful probe packets are monitored. Statistics about failed probe packets are not collected.
No actions can be configured for a reaction entry of monitoring one-way delays. To display the monitoring results and statistics, use the display nqa reaction counters and display nqa statistics commands.
Examples
# Create reaction entry 1 for monitoring the destination-to-source delay of every UDP jitter packet, and set the upper limit to 50 milliseconds and lower limit to 5 milliseconds. Before the NQA operation starts, the initial state of the reaction entry is invalid. The destination-to-source delay is calculated after the response to the probe packet arrives. If the delay exceeds the upper limit, the state of the reaction entry is set to over-threshold. If it is below the lower limit, the state is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-jitter
[Sysname-nqa-admin-test-udp-jitter] reaction 1 checked-element owd-ds threshold-value 50 5
reaction checked-element icpif
Use reaction checked-element icpif to configure a reaction entry for monitoring the ICPIF value in the voice operation.
Use undo reaction to delete a reaction entry.
Syntax
reaction item-number checked-element icpif threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]
undo reaction item-number
Default
No reaction entries for monitoring ICPIF values exist.
Views
Voice operation view
Predefined user roles
network-admin
Parameters
item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.
threshold-value: Specifies threshold range.
upper-threshold: Specifies the upper limit in the range of 1 to 100.
lower-threshold: Specifies the lower limit in the range of 1 to 100. It must not be greater than the upper limit.
action-type: Specifies what action to be triggered. The default action is none.
none: Specifies the action of displaying results on the terminal display.
trap-only: Specifies the action of displaying results on the terminal display and meanwhile sending SNMP trap messages to the NMS.
Usage guidelines
You cannot edit a reaction entry after it is created. To change the attributes in a reaction entry, use the undo reaction command to delete the entry, and then configure a new one.
Examples
# Create reaction entry 1 for monitoring the ICPIF value in the voice operation, and set the upper limit to 50 and lower limit to 5. Before the voice operation starts, the initial state of the reaction entry is invalid. After the operation, the ICPIF value is checked against the threshold range. If it exceeds the upper limit, the state of the reaction entry is set to over-threshold. If it is below the lower limit, the state is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type voice
[Sysname-nqa-admin-test-voice] reaction 1 checked-element icpif threshold-value 50 5 action-type trap-only
reaction checked-element mos
Use reaction checked-element mos to configure a reaction entry for monitoring the MOS value in the voice operation.
Use undo reaction to delete a reaction entry.
Syntax
reaction item-number checked-element mos threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]
undo reaction item-number
Default
No reaction entries for monitoring the MOS value exist.
Views
Voice operation view
Predefined user roles
network-admin
Parameters
item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.
threshold-value: Specifies threshold range.
upper-threshold: Specifies the upper limit in the range of 1 to 500.
lower-threshold: Specifies the lower limit in the range of 1 to 500. It must not be greater than the upper limit.
action-type: Specifies what action to be triggered. The default action is none.
none: Specifies the action of displaying results on the terminal display.
trap-only: Specifies the action of displaying results on the terminal display and meanwhile sending SNMP trap messages to the NMS.
Usage guidelines
You cannot edit a reaction entry after it is created. To change the attributes in a reaction entry, use the undo reaction command to delete the entry, and then configure a new one.
For the MOS threshold, the number is expressed in three digits representing ones, tenths, and hundredths. For example, to express a MOS threshold of 1, enter 100.
Examples
# Create reaction entry 1 for monitoring the MOS value of the voice operation, and set the upper limit to 2 and lower limit to 1. Before the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the MOS value is checked against the threshold range. If it exceeds the upper limit, the state of the reaction entry is set to over-threshold. If it is below the lower limit, the state is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type voice
[Sysname-nqa-admin-test-voice] reaction 1 checked-element mos threshold-value 200 100 action-type trap-only
reaction checked-element packet-loss
Use reaction checked-element packet-loss to configure a reaction entry for monitoring packet loss in an NQA operation.
Use undo reaction to delete a reaction entry.
Syntax
reaction item-number checked-element packet-loss threshold-type accumulate accumulate-occurrences [ action-type { none | trap-only } ]
undo reaction item-number
Default
No reaction entries for monitoring packet loss exist.
Views
ICMP jitter/UDP jitter/voice operation view
Predefined user roles
network-admin
Parameters
item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.
threshold-type: Specifies a threshold type.
accumulate accumulate-occurrences: Specifies the total number of lost packets in the operation. The value range is 1 to 15000 for the ICMP jitter and UDP jitter operations and 1 to 60000 for the voice operation.
action-type: Specifies what action to be triggered. The default action is none.
none: Specifies the action of displaying results on the terminal display.
trap-only: Specifies the action of displaying results on the terminal display and meanwhile sending SNMP trap messages to the NMS.
Usage guidelines
You cannot edit a reaction entry after it is created. To change the attributes in a reaction entry, use the undo reaction command to delete the entry, and then configure a new one.
Examples
# Create reaction entry 1 for monitoring packet loss in the UDP jitter operation. Before the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the total number of the lost packets is checked against the threshold. If the number reaches or exceeds 100, the state of the reaction entry is set to over-threshold. Otherwise, the state is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-jitter
[Sysname-nqa-admin-test-udp-jitter] reaction 1 checked-element packet-loss threshold-type accumulate 100 action-type trap-only
reaction checked-element probe-duration
Use reaction checked-element probe-duration to configure a reaction entry for monitoring the probe duration.
Use undo reaction to delete a reaction entry.
Syntax
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 } ]
undo reaction item-number
Default
No reaction entries for monitoring the probe duration exist.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
Predefined user roles
network-admin
Parameters
item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.
threshold-type: Specifies a threshold type.
accumulate accumulate-occurrences: Checks the total number of threshold violations. The value range is 1 to 15.
average: Checks the average probe duration.
consecutive consecutive-occurrences: Specifies the number of consecutive threshold violations after the NQA operation starts. The value range is 1 to 16.
threshold-value: Specifies threshold range in milliseconds.
upper-threshold: Specifies the upper limit in the range of 0 to 3600000.
lower-threshold: Specifies the lower limit in the range of 0 to 3600000. It must not be greater than the upper threshold.
action-type: Specifies what action to be triggered. The default action is none.
none: Specifies the action of displaying results on the terminal display.
trap-only: Specifies the action of displaying results on the terminal display and meanwhile sending SNMP trap messages to the NMS. This keyword is not available for the DNS operation.
Usage guidelines
You cannot edit a reaction entry after it is created. To change the attributes in a reaction entry, use the undo reaction command to delete the entry, and then configure a new one.
Only successful probe packets are monitored. Statistics about failed probe packets are not collected.
Examples
# Create reaction entry 1 for monitoring the average probe duration of ICMP echo operation, and set the upper limit to 50 milliseconds and lower limit to 5 milliseconds. Before the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the average probe duration is checked. If it exceeds the upper limit, the state is set to over-threshold. If it is below the lower limit, the state of the reaction entry is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-duration threshold-type average threshold-value 50 5 action-type trap-only
# Create reaction entry 2 for monitoring the probe duration of ICMP echo operation, and set the upper limit to 50 milliseconds and the lower limit to 5 milliseconds. Before the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the accumulated probe duration is checked against the threshold range. If the total number of threshold violations reaches or exceeds 10, the state of the entry is set to over-threshold. If it is below the lower threshold, the state of the entry is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] reaction 2 checked-element probe-duration threshold-type accumulate 10 threshold-value 50 5 action-type trap-only
# Create reaction entry 3 for monitoring the probe duration time of ICMP echo operation, and set the upper limit to 50 milliseconds and the lower limit to 5 milliseconds. Before the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the consecutive probe duration is checked against the threshold range. If the total number of consecutive threshold violations reaches or exceeds 10, the state of the entry is set to over-threshold. If it is below the lower threshold, the state of the entry is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] reaction 3 checked-element probe-duration threshold-type consecutive 10 threshold-value 50 5 action-type trap-only
reaction checked-element probe-fail (for trap)
Use reaction checked-element probe-fail to configure a reaction entry for monitoring the probe failures of the operation.
Use undo reaction to delete a reaction entry.
Syntax
reaction item-number checked-element probe-fail threshold-type { accumulate accumulate-occurrences | consecutive consecutive-occurrences } [ action-type { none | trap-only } ]
undo reaction item-number
Default
No reaction entries for monitoring probe failures exist.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
Predefined user roles
network-admin
Parameters
item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.
threshold-type: Specifies a threshold type.
accumulate accumulate-occurrences: Checks the total number of probe failures. The value range is 1 to 15.
consecutive consecutive-occurrences: Checks the maximum number of consecutive probe failures. The value range is 1 to 16.
action-type: Specifies what action to be triggered. The default action is none.
none: Specifies the action of displaying results on the terminal display.
trap-only: Specifies the action of displaying results on the terminal display and meanwhile sending SNMP trap messages to the NMS. This keyword is not available for the DNS operation.
Usage guidelines
You cannot edit a reaction entry after it is created. To change the attributes in a reaction entry, use the undo reaction command to delete the entry, and then configure a new one.
Examples
# Create reaction entry 1 for monitoring the probe failures in ICMP echo operation. Before the NQA operation starts, the initial state of the reaction entry is invalid. If the total number of probe failures reaches or exceeds 10, the state of the entry is set to over-threshold. If it is below the threshold, the state of the entry is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type accumulate 10 action-type trap-only
# Create reaction entry 2 for monitoring the probe failures in ICMP echo operation. Before the NQA operation starts, the initial state of the reaction entry is invalid. If the number of consecutive probe failures reaches or exceeds 10, the state of the entry is set to over-threshold. If it is below the threshold, the state of the entry is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] reaction 2 checked-element probe-fail threshold-type consecutive 10 action-type trap-only
reaction checked-element probe-fail (for trigger)
Use reaction checked-element probe-fail to configure a reaction entry for monitoring probe failures.
Use undo reaction to delete a reaction entry.
Syntax
reaction item-number checked-element probe-fail threshold-type consecutive consecutive-occurrences action-type trigger-only
undo reaction item-number
Default
No reaction entries for monitoring probe failures exist.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
Predefined user roles
network-admin
Parameters
item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.
threshold-type: Specifies a threshold type.
consecutive consecutive-occurrences: Checks the maximum number of consecutive probe failures, in the range of 1 to 16.
action-type: Specifies what action to be triggered.
trigger-only: Triggers other modules to react to certain conditions.
Usage guidelines
You cannot edit a reaction entry after it is created. To change the attributes in a reaction entry, use the undo reaction command to delete the entry, and then configure a new one.
Examples
# Create reaction entry 1. If the number of consecutive probe failures reaches 3, collaboration is triggered.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type tcp
[Sysname-nqa-admin-test-tcp] reaction 1 checked-element probe-fail threshold-type consecutive 3 action-type trigger-only
Related commands
track (High Availability Command Reference)
reaction checked-element rtt
Use reaction checked-element rtt to configure a reaction entry for monitoring packet round-trip time.
Use undo reaction to delete a reaction entry.
Syntax
reaction item-number checked-element rtt threshold-type { accumulate accumulate-occurrences | average } threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]
undo reaction item-number
Default
No reaction entries for monitoring packet round-trip time exist.
Views
ICMP jitter/UDP jitter/voice operation view
Predefined user roles
network-admin
Parameters
item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.
threshold-type: Specifies a threshold type.
accumulate accumulate-occurrences: Checks the total number of threshold violations. Available value ranges include:
· 1 to 15000 for the ICMP jitter and UDP jitter operations.
· 1 to 60000 for the voice operation.
average: Checks the packet average round-trip time.
threshold-value: Specifies threshold range in milliseconds.
upper-threshold: Specifies the upper limit in the range of 0 to 3600000.
lower-threshold: Specifies the lower limit in the range of 0 to 3600000. It must not be greater than the upper limit.
action-type: Specifies what action to be triggered. The default action is none.
none: Specifies the action of displaying results on the terminal display.
trap-only: Specifies the action of displaying results on the terminal display and meanwhile sending SNMP trap messages to the NMS.
Usage guidelines
You cannot edit a reaction entry after it is created. To change the attributes in a reaction entry, use the undo reaction command to delete the entry, and then configure a new one.
Only successful probe packets are monitored. Statistics about failed probe packets are not collected.
Examples
# Create reaction entry 1 for monitoring the average round-trip time of UDP jitter probe packets, and set the upper limit to 50 milliseconds and lower limit to 5 milliseconds. Before the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the average packet round-trip time is checked. If it exceeds the upper limit, the state is set to over-threshold. If it is below the lower limit, the state is set to below-threshold. Once the reaction entry state changes, a trap message is generated and sent to the NMS.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-jitter
[Sysname-nqa-admin-test-udp-jitter] reaction 1 checked-element rtt threshold-type average threshold-value 50 5 action-type trap-only
# Create reaction entry 2 for monitoring the round-trip time of UDP jitter probe packets, and set the upper limit to 50 milliseconds and lower limit to 5 milliseconds. Before the NQA operation starts, the initial state of the reaction entry is invalid. After the operation, the packet round-trip time is checked. If the total number of threshold violations reaches or exceeds 100, the state of the entry is set to over-threshold. Otherwise, the state of the entry is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the NMS.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-jitter
[Sysname-nqa-admin-test-udp-jitter] reaction 1 checked-element rtt threshold-type accumulate 100 threshold-value 50 5 action-type trap-only
reaction checked-element two-way-delay
Use reaction checked-element two-way-delay to configure a reaction entry for monitoring the two-way delay in the TWAMP Light tests.
Use undo reaction trap to delete a reaction entry.
Syntax
reaction item-number checked-element two-way-delay threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]
undo reaction item-number
Default
No reaction entries for monitoring two-way delay exist.
Views
Client-session view
Predefined user roles
network-admin
Parameters
item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.
threshold-value: Specifies threshold range in microseconds.
upper-threshold: Specifies the upper limit in the range of 2 to 1000000.
lower-threshold: Specifies the lower limit in the range of 1 to 999999. It must not be greater than the upper limit.
action-type: Specifies the action to be triggered. The default action is none.
none: Specifies the action of displaying results on the terminal display.
trap-only: Specifies the action of displaying results on the terminal display and sending SNMP trap messages to the NMS.
Usage guidelines
You cannot edit a reaction entry after it is created. To change the attributes in a reaction entry, use the undo reaction command to delete the entry, and then configure a new one.
Only successful probe packets are monitored. Statistics about failed probe packets are not collected.
In a TWAMP test, the device monitors the test result, and starts the monitoring time when either of the following conditions is met:
· The monitoring result goes beyond the threshold upper limit.
· The monitoring result drops below the threshold lower limit from a monitoring result higher than the lower limit.
If either condition is always true during the monitoring time, a threshold violation occurs. To set the monitoring time, use the monitor-time keyword in the start command.
Examples
# Create reaction entry 1 for monitoring the two-way delay of probe packets, and set the upper limit to 50 microseconds and the lower limit to 5 microseconds.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] reaction 1 checked-element two-way-delay threshold-value 50 5 action-type trap-only
Related commands
start (TWAMP Light sender view)
reaction checked-element two-way-jitter
Use reaction checked-element two-way-jitter to configure a reaction entry for monitoring the two-way jitter in the TWAMP Light tests.
Use undo reaction to delete a reaction entry.
Syntax
reaction item-number checked-element two-way-jitter threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]
undo reaction item-number
Default
No reaction entries for monitoring two-way jitter exist.
Views
Client-session view
Predefined user roles
network-admin
Parameters
item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.
threshold-value: Specifies threshold range in microseconds.
upper-threshold: Specifies the upper limit in the range of 2 to 1000000.
lower-threshold: Specifies the lower limit in the range of 1 to 999999. It must not be greater than the upper limit.
action-type: Specifies the action to be triggered. The default action is none.
none: Specifies the action of displaying results on the terminal display.
trap-only: Specifies the action of displaying results on the terminal display and sending SNMP trap messages to the NMS.
Usage guidelines
You cannot edit a reaction entry after it is created. To change the attributes in a reaction entry, use the undo reaction command to delete the entry, and then configure a new one.
Only successful probe packets are monitored. Statistics about failed probe packets are not collected.
In a TWAMP test, the device monitors the test result, and starts the monitoring time when either of the following conditions is met:
· The monitoring result goes beyond the threshold upper limit.
· The monitoring result drops below the threshold lower limit from a monitoring result higher than the lower limit.
If either condition is always true during the monitoring time, a threshold violation occurs. To set the monitoring time, use the monitor-time keyword in the start command.
Examples
# Create reaction entry 1 for monitoring the two-way jitter of probe packets, and set the upper limit to 20 microseconds and the lower limit to 3 microseconds.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] reaction 1 checked-element two-way-jitter threshold-value 20 3 action-type trap-only
Related commands
start (TWAMP Light sender view)
reaction checked-element two-way-loss
Use reaction checked-element two-way-loss to configure a reaction entry for monitoring the two-way packet loss in the TWAMP Light tests.
Use undo reaction to delete a reaction entry.
Syntax
reaction item-number checked-element two-way-loss threshold-value upper-threshold lower-threshold [ action-type { none | trap-only } ]
undo reaction item-number
Default
No reaction entries for monitoring two-way packet loss exist.
Views
Client-session view
Predefined user roles
network-admin
Parameters
item-number: Assigns an ID to the reaction entry, in the range of 1 to 10.
threshold-value: Specifies threshold range.
upper-threshold: Specifies the upper limit in the range of 2 to 1000000.
lower-threshold: Specifies the lower limit in the range of 1 to 999999. It must not be greater than the upper limit.
action-type: Specifies the action to be triggered. The default action is none.
none: Specifies the action of displaying results on the terminal display.
trap-only: Specifies the action of displaying results on the terminal display and sending SNMP trap messages to the NMS.
Usage guidelines
You cannot edit a reaction entry after it is created. To change the attributes in a reaction entry, use the undo reaction command to delete the entry, and then configure a new one.
In a TWAMP test, the device monitors the test result, and starts the monitoring time when either of the following conditions is met:
· The monitoring result goes beyond the threshold upper limit.
· The monitoring result drops below the threshold lower limit from a monitoring result higher than the lower limit.
If either condition is always true during the monitoring time, a threshold violation occurs. To set the monitoring time, use the monitor-time keyword in the start command.
Examples
# Create reaction entry 1 for monitoring the two-way packet loss of probe packets, and set the upper limit to 1000 and the lower limit to 500.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] reaction 1 checked-element two-way-loss threshold-value 1000 500 action-type trap-only
Related commands
start (TWAMP Light sender view)
reaction trap
Use reaction trap to configure the sending of traps to the NMS under specific conditions.
Use undo reaction trap to restore the default.
Syntax
reaction trap { path-change | probe-failure consecutive-probe-failures | test-complete | test-failure [ accumulate-probe-failures ] }
undo reaction trap { path-change | probe-failure | test-complete | test-failure }
Default
No traps are sent to the NMS.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
UDP tracert operation view
ICMP jitter/UDP jitter/voice operation view
Predefined user roles
network-admin
Parameters
path-change: Sends a trap when the UDP tracert operation detects a different path to the destination.
probe-failure consecutive-probe-failures: Sends a trap to the NMS if the number of consecutive probe failures in an operation is greater than or equal to consecutive-probe-failures. The value range for the consecutive-probe-failures argument is 1 to 15. The system counts the number of consecutive probe failures for each operation, so multiple traps might be sent.
test-complete: Sends a trap to indicate that the operation is completed.
test-failure: Sends a trap when an operation fails. For operations other than UDP tracert operation, the system counts the total number of probe failures in an operation. If the number reaches or exceeds the value for the accumulate-probe-failures argument, a trap is sent for the operation failure.
accumulate-probe-failures: Specifies the total number of probe failures in an operation. The value range is 1 to 15. This argument is not supported by the UDP tracert operation.
Usage guidelines
The ICMP jitter, UDP jitter, and voice operations support only the test-complete keyword.
The following parameters are not available for the UDP tracert operation:
· The probe-failure consecutive-probe-failures option.
· The accumulate-probe-failures argument.
Examples
# Configure the system to send a trap if five or more consecutive probe failures occur in an ICMP echo operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] reaction trap probe-failure 5
reaction trigger per-probe
Use reaction trigger per-probe to configure the probe result sending on a per-probe basis.
Use undo reaction trigger per-probe to restore the default.
Syntax
reaction trigger per-probe
undo reaction trigger per-probe
Default
The probe result is sent to the feature that uses the template after three consecutive failed or successful probes.
Views
ICMP/TCP half open template view
Predefined user roles
network-admin
Usage guidelines
The feature enables the NQA client to send the probe result to the feature that uses the NQA template every time a probe is completed.
If you execute this command and the reaction trigger probe-fail command multiple times, the most recent configuration takes effect.
If you execute this command and the reaction trigger probe-pass command multiple times, the most recent configuration takes effect.
Examples
# In ICMP template view, configure the probe result sending on a per-probe basis.
<Sysname> system-view
[Sysname] nqa template icmp icmptplt
[Sysname-nqatplt-icmp-icmptplt] reaction trigger per-probe
Related commands
reaction trigger probe-fail
reaction trigger probe-pass
reaction trigger probe-fail
Use reaction trigger probe-fail to set the number of consecutive probe failures to determine an operation failure.
Use undo reaction trigger probe-fail to restore the default.
Syntax
reaction trigger probe-fail count
undo reaction trigger probe-fail
Default
The NQA client notifies the feature of the operation failure when the number of consecutive probe failures reaches 3.
Views
Any NQA template view
Predefined user roles
network-admin
Parameters
count: Specifies the number of consecutive probe failures, in the range of 1 to 15.
Usage guidelines
If the number of consecutive probe failures is reached, the NQA client notifies the feature that uses the NQA template of the operation failure.
If you execute this command and the reaction trigger per-probe command multiple times, the most recent configuration takes effect.
Examples
# In HTTP template view, configure the NQA client to notify the feature of the operation failure when the number of consecutive probe failures reaches 5.
<Sysname> system-view
[Sysname] nqa template http httptplt
[Sysname-nqatplt-http-httptplt] reaction trigger probe-fail 5
Related commands
reaction trigger per-probe
reaction trigger probe-pass
reaction trigger probe-pass
Use reaction trigger probe-pass to set the number of consecutive successful probes to determine a successful operation event.
Use undo reaction trigger probe-pass to restore the default.
Syntax
reaction trigger probe-pass count
undo reaction trigger probe-pass
Default
The NQA client notifies the feature of the successful operation event if the number of consecutive successful probes reaches 3.
Views
Any NQA template view
Predefined user roles
network-admin
Parameters
count: Specifies the number of consecutive successful probes, in the range of 1 to 15.
Usage guidelines
If number of consecutive successful probes is reached, the NQA client notifies the feature that uses the template of the successful operation event.
If you execute this command and the reaction trigger per-probe command multiple times, the most configuration takes effect.
Examples
# In HTTP template view, configure the NQA client to notify the feature of the successful operation event if the number of consecutive successful probes reaches 5.
<Sysname> system-view
[Sysname] nqa template http httptplt
[Sysname-nqatplt-http-httptplt] reaction trigger probe-pass 5
Related commands
reaction trigger per-probe
reaction trigger probe-fail
reset nqa twamp-light statistics
Use reset nqa twamp-light statistics to clear the TWAMP Light test sessions.
Syntax
reset nqa twamp-light statistics { all | test-session session-id }
Views
User view
Predefined user roles
network-admin
Parameters
all: Clears statistics about all TWAMP Light test sessions.
test-session session-id: Specifies a session by its ID. The value range for the session-id argument is 1 to 512.
Usage guidelines
Use the command with caution. Once being cleared, the test session cannot be recovered.
Examples
# Clear statistics about all TWAMP Light test sessions.
<Sysname> reset nqa twamp-light statistics all
Related commands
display nqa twamp-light client statistic
resolve-target
Use resolve-target to specify the domain name to be resolved through DNS.
Use undo resolve-target to restore the default.
Syntax
resolve-target domain-name
undo resolve-target
Default
The domain name to be resolved through DNS is not specified.
Views
DNS operation view
DNS template view
Predefined user roles
network-admin
Parameters
domain-name: Specifies the domain name to be resolved. The domain name is a dot-separated case-sensitive string of 1 to 255 characters including letters, digits, hyphens (-), and underscores (_). For example, aabbcc.com. Each part consists of 1 to 63 characters, and consecutive dots (.) are not allowed.
Examples
# Specify domain1 as the domain name to be resolved.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type dns
[Sysname-nqa-admin-test-dns] resolve-target domain1
# In DNS template view, specify domain1 as the domain name to be resolved.
<Sysname> system-view
[Sysname] nqa template dns dnstplt
[Sysname-nqatplt-dns-dnstplt] resolve-target domain1
resolve-type
Use resolve-type to configure the domain name resolution type.
Use undo resolve-type to restore the default.
Syntax
resolve-type { A | AAAA }
undo resolve-type
Default
The domain name resolution type is type A.
Views
DNS operation view
DNS template view
Predefined user roles
network-admin
Parameters
A: Specifies the type A queries. A type A query resolves a domain name to a mapped IPv4 address.
AAAA: Specifies the type AAAA queries. A type AAAA query resolves a domain name to a mapped IPv6 address.
Examples
# In DNS operation view, set the domain name resolution type to A.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type dns
[Sysname-nqa-admin-test-dns] resolve-type A
# In DNS template view, set the domain name resolution type to A.
<Sysname> system-view
[Sysname] nqa template dns dnstplt
[Sysname-nqatplt-dns-dnstplt] resolve-type A
route-option bypass-route
Use route-option bypass-route to enable the routing table bypass feature to test the connectivity to the direct destination.
Use undo route-option bypass-route to disable the routing table bypass feature.
Syntax
route-option bypass-route
undo route-option bypass-route
Default
The routing table bypass feature is disabled.
Views
ICMP echo/TCP/UDP echo operation view
DLSw/DNS/FTP/HTTP/SNMP operation view
UDP tracert operation view
ICMP jitter/UDP jitter/voice operation view
Predefined user roles
network-admin
Usage guidelines
When the routing table bypass feature is enabled, the following events occur:
· The routing table is not searched. Packets are sent to the destination on a directly connected network.
· The TTL value in the probe packet is set to 1. The TTL set in the ttl command does not take effect.
This command does not take effect if the destination address of the NQA operation is an IPv6 address.
Examples
# Enable the routing table bypass feature.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] route-option bypass-route
source interface (frame loss/latency/throughput/Y.1564 operation view/TWAMP Light client-session view)
Use source interface to specify a source AC or source interface for probe packets.
Use undo source interface to restore the default.
Syntax
source interface interface-type interface-number [ service-instance instance-id ]
undo source interface
Default
No source AC or source interface is specified for probe packets.
Views
Frame loss/latency/throughput/Y.1564 operation view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
service-instance instance-id: Specifies an Ethernet service instance by its ID in the range of 1 to 4096. In Layer 2 networks, an Ethernet service instance and a source interface determine a source AC interface. For more information about the Ethernet service instance and AC interface, see VPLS in MPLS Configuration Guide.
Usage guidelines
On an L2VPN network, you can execute this command to bind an Ethernet service instance to the Layer 2 Ethernet interface to create a source AC interface for sending probe packets.
On a Layer 3 network, you can execute this command to use the Layer 3 Ethernet interface as the source interface for sending probe packets.
Follow these guidelines when you configure this command:
· The specified interface must be up.
· If the interface-type interface-number argument represents a Layer 2 interface, the service-instance instance-id option is required.
· If the interface-type interface-number argument represents a Layer 3 interface, the following rules apply:
¡ In an MPLS L3VPN network, do not specify the service-instance instance-id option.
¡ In an MPLS L2VPN network, the service-instance instance-id option is optional. This option takes effect if the Layer 3 interface switches to a Layer 2 interface. In this case, you do not have to stop the operation and reconfigure this command. The operation restarts automatically by using the new source AC after the MPLS L2VPN configuration is modified.
Examples
# Specify service instance 1 on Ten-GigabitEthernet 3/0/1 as the source AC interface for the throughput operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type throughput
[Sysname-nqa-admin-test-throughput] source interface ten-gigabitethernet 3/0/1 service-instance 1
# In the TWAMP Light client-session view, specify Ethernet service instance service-instance 1 on Ten-GigabitEthernet 3/0/1 as the source AC interface.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] source interface ten-gigabitethernet 3/0/1 service-instance 1
Related commands
source ip
source interface (ICMP echo/UDP tracert operation view)
Use source interface to specify the IP address of an interface as the source IP address of probe packets.
Use undo source interface to restore the default.
Syntax
source interface interface-type interface-number
undo source interface
Default
The probe packets take the primary IP address of the outgoing interface as their source IP address.
Views
ICMP echo operation view
UDP tracert operation view
ICMP template view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
Usage guidelines
The specified interface must be up. If the interface is down, no probe requests can be sent out.
If you execute this command and the source ip or source ipv6 command for an ICMP echo operation or ICMP template multiple times, the most recent configuration takes effect.
If you execute this command and the source ip command for a UDP tracert operation multiple times, the most recent configuration takes effect.
Examples
# Specify the IP address of interface Ten-GigabitEthernet 3/0/1 as the source IP address of ICMP echo request packets.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] source interface ten-gigabitethernet 3/0/1
# In ICMP template view, specify the IP address of the interface Ten-GigabitEthernet 3/0/1 as the source IP address of ICMP echo request packets.
<Sysname> system-view
[Sysname] nqa template icmp icmptplt
[Sysname-nqatplt-icmp-icmptplt] source interface ten-gigabitethernet 3/0/1
Related commands
source ip
source ipv6
source ip
Use source ip to configure the source IPv4 address for probe packets.
Use undo source ip to restore the default.
Syntax
Y.1564 operations:
source ip ipv4-address1 [ to ipv4-address2 ]
undo source ip
Other operations:
source ip ipv4-address
undo source ip
Default
The source IPv4 address for probe packets is not specified for the frame loss, latency, throughput, Y.1564, or TWAMP Light test. For other types of NQA operations, the probe packets take the primary IP address of their output interface as the source IPv4 address.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/FTP/HTTP/SNMP operation view
UDP tracert operation view
ICMP jitter/path jitter/UDP jitter/voice operation view
Frame loss/latency/throughput/Y.1564 operation view
Any NQA template view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
Ipv4-address: Specifies the source IPv4 address for probe packets.
ipv4-address1 to ipv4-address2: Specifies a source IPv4 address range. The ipv4-address2 must be higher than the ipv4-address1. Between the two source IPv4 addresses, only one octet difference is allowed and the value difference cannot exceed 127.
Usage guidelines
The specified source IP address must be the IPv4 address of a local interface, and the local interface must be up. Otherwise, no probe packets can be sent out. This restriction does not apply to the frame loss, latency, or throughput operation.
For an NQA template, if the source and destination addresses are of different IP versions, the source address does not take effect.
If you execute the source interface and source ip commands multiple times for an ICMP echo operation, UDP tracert operation, or ICMP template, the most recent configuration takes effect.
For path quality analysis operations and Y.1564 operations to start successfully, configure the source and destination IP addresses as follows:
· In a Layer 2 Ethernet, Layer 3 Ethernet, L2VPN, or L3VPN network, configure both source and destination IP addresses.
· In other networks, configure both of them or none of them. If they are configured, make sure the source and destination IP addresses are of the same IP version.
Examples
# Specify 10.1.1.1 as the source IPv4 address for ICMP echo requests.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] source ip 10.1.1.1
# In ICMP template view, specify 10.1.1.1 as the source IPv4 address for ICMP echo requests.
<Sysname> system-view
[Sysname] nqa template icmp icmptplt
[Sysname-nqatplt-icmp-icmptplt] source ip 10.1.1.1
# In TWAMP Light client-session view, specify 10.1.1.1 as the source IPv4 address for the TWAMP Light tests.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] source ip 10.1.1.1
Related commands
source interface
source ipv6
Use source ipv6 to configure the source IPv6 address for probe packets.
Use undo source ipv6 to restore the default.
Syntax
Y.1564 operations:
source ipv6 ipv6-address1 [ to ipv6-address2 ]
undo source ipv6
Other operations:
source ipv6 ipv6-address
undo source ipv6
Default
The source IPv6 address for probe packets is not specified for the frame loss, latency, throughput, Y.1564, or TWAMP Light test. For other types of NQA operations, the probe packets take the IPv6 address of their output interface as the source IPv6 address.
Views
ICMP echo/TCP/UDP echo operation view
UDP jitter operation view
ICMP jitter/DLSw/FTP/HTTP/SNMP/UDP tracert/path jitter/voice operation view
Frame loss/latency/throughput/Y.1564 operation view
DNS/FTP/HTTP/HTTPS/ICMP/IMAP/POP3/RADIUS/SMTP/SNMP/SSL/TCP/TCP half open/UDP template view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies the source IPv6 address for probe packets. IPv6 link-local addresses are not supported.
ipv6-address1 to ipv6-address2: Specifies a source IPv6 address range. The ipv6-address2 must be higher than ipv6-address1. Between the two source IPv6 addresses, only one octet difference is allowed and the value difference cannot exceed 127.
Usage guidelines
The specified source IPv6 address must be the IPv6 address of a local interface. The local interface must be up. Otherwise, no probe packets can be sent out.
For an NQA template, if the source and destination addresses are of different IP versions, the source address does not take effect.
If you execute the source interface and source ipv6 commands multiple times for an ICMP echo operation or ICMP template, the most recent configuration takes effect.
For path quality analysis operations and Y.1564 operations to start successfully, configure the source and destination IP addresses as follows:
· In a Layer 2 Ethernet, Layer 3 Ethernet, L2VPN, or L3VPN network, configure both source and destination IP addresses.
· In other networks, configure both of them or none of them. If they are configured, make sure the source and destination IP addresses are of the same IP version.
Examples
# In ICMP template view, specify 1::1 as the source IPv6 address for ICMP echo requests.
<Sysname> system-view
[Sysname] nqa template icmp icmptplt
[Sysname-nqatplt-icmp-icmptplt] source ipv6 1::1
# In TWAMP Light client-session view, specify 1::1 as the source IPv6 address for the TWAMP Light tests.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] source ipv6 1::1
Related commands
source interface
source mac
Use source mac to specify the source MAC address for probe packets.
Use undo source mac to restore the default.
Syntax
source mac mac-address [ to mac-address1 ]
undo source mac
Default
For the frame loss, latency, throughput, or Y.1564 operation, the probe packets take the MAC address of the egress interface as the source MAC address.
For the TWAMP Light test, no source MAC address is specified.
Views
Frame loss/latency/throughput/Y.1564 operation view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
mac-address: Specifies the source MAC address in the format of H-H-H. For example, to use 000f-00e2-0001 as the source MAC address, set this argument to f-e2-1.
to mac-address1: Specifies a source MAC address range. The mac-address1 must be higher than the mac-address. Between the two source MAC addresses, only one octet difference is allowed and the value difference cannot exceed 127. Only the Y.1564 operations support this option.
Examples
# Set the source MAC address of probe packets to 0001-0001-0001 in a Y.1564 operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type y1564
[Sysname-nqa-admin-test-y1564] source mac 1-1-1
# In TWAMP Light client-session view, specify 0001-0001-0001 as the source MAC address for the TWAMP Light test.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] source mac 1-1-1
source port
Use source port to configure the source port number for probe packets.
Use undo source port to restore the default.
Syntax
Y.1564 operations:
source port port-number1 [ to port-number2 ]
Other operations:
source port port-number
undo source port
Default
The source port number is 49184 for the frame loss, latency, throughput, or Y.1564 operation. For TWAMP Light tests, the source port number is not specified. For other types of NQA operations, the system automatically selects an unused port number as the source port number.
Views
UDP echo operation view
SNMP operation view
UDP tracert operation view
UDP jitter/voice operation view
Frame loss/latency/throughput/Y.1564 operation view
DNS template view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
port-number: Specifies the source port number in the range of 1 to 65535.
port-number1 to port-number2: Specifies a source port number range. The port-number2 must be greater than port-number1. Between the two source port numbers, only one octet difference is allowed and the value difference cannot exceed 127.
Usage guidelines
For TWAMP Light operations, you must configure this command. For other operation types, as a best practice, use the default setting.
For the operation to succeed, make sure the specified port number is not used by any services on the device.
· To obtain the IPv4 addresses and the port numbers in use on this device, see the Local Addr:port field in the output from the display tcp and display udp commands.
· To obtain the IPv6 addresses and the port numbers in use on this device, see the LAddr->port field in the output from the display ipv6 tcp and display ipv6 udp commands.
Examples
# Set the source port number to 8000 for probe packets in the UDP echo operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type udp-echo
[Sysname-nqa-admin-test-udp-echo] source port 8000
# In DNS template view, set the source port number to 8000 for probe packets in the DNS operation.
<Sysname> system-view
[Sysname] nqa template dns dnstplt
[Sysname-nqatplt-dns-dnstplt] source port 8000
# In TWAMP Light client-session view, set the source port number to 8000 for the TWAMP Light test.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] source port 8000
Related commands
display ipv6 tcp (Layer 3—IP Services Command Reference)
display ipv6 udp (Layer 3—IP Services Command Reference)
display tcp (Layer 3—IP Services Command Reference)
display udp (Layer 3—IP Services Command Reference)
speed granularity
Use speed granularity to set the granularity for adjusting the packet sending speed.
Use undo speed granularity to restore the default.
Syntax
speed granularity value
undo speed granularity
Default
The granularity for adjusting the packet sending speed is 1000 kbps.
Views
Throughput operation view
Predefined user roles
network-admin
Parameters
value: Specifies the granularity in kbps. The value range is 1 to 10000.
Usage guidelines
After a probe completes, the NQA client adjusts the packet sending speed by using the speed adjusting granularity for the next probe.
Examples
# Set the speed granularity to 2000 kbps for the throughput operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type throughput
[Sysname-nqa-admin-test-throughput] speed granularity 2000
speed init
Use speed init to set the initial packet sending speed.
Use undo speed init to restore the default.
Syntax
speed init init-speed
undo speed init
Default
The initial frame sending speed is 100000 kbps.
Views
Frame loss/latency/throughput operation view
Predefined user roles
network-admin
Parameters
init-speed: Specifies the initial packet sending speed in kbps. The value range is 1000 to 10000000.
Examples
# Set the initial packet sending speed to 10000 kbps for the throughput operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type throughput
[Sysname-nqa-admin-test-throughput] speed init 10000
ssl-client-policy
Use ssl-client-policy to specify an SSL client policy for an HTTPS or SSL template.
Use undo ssl-client-policy to restore the default.
Syntax
ssl-client-policy policy-name
undo ssl-client-policy
Default
No SSL client policy is specified for an HTTPS or SSL template.
Views
HTTPS/SSL template view
Predefined user roles
network-admin
Parameters
policy-name: Specifies an SSL client policy by its name, a case-insensitive string of 1 to 31 characters.
Usage guidelines
In the HTTPS or SSL operation, the NQA client uses the specified SSL client policy to establish an SSL connection to the server.
Examples
# Specify SSL client policy policy for SSL template ssltplt.
<Sysname> system-view
[Sysname] nqa template ssl ssltplt
[Sysname-nqatplt-ssl-ssltplt] ssl-client-policy policy
start (frame loss/latency/throughput/Y.1564 operation view/Y.1564 operation group view/RFC2544 operation group view)
Use start to start the frame loss, throughput, latency, or Y.1564 operation.
Syntax
start
Default
The frame loss, throughput, latency, or Y.1564 operation is not started.
Views
Frame loss/latency/throughput/Y.1564 operation view
Y.1564 operation group view
RFC2544 operation group view
Predefined user roles
network-admin
Usage guidelines
The frame loss, latency, throughput, or Y.1564 operation requires all bandwidth of the link over which the operation is performed. Before such an operation starts, suspend all the services that are transmitting data over the link.
The frame loss, latency, throughput, or Y.1564 operation cannot run simultaneously with other NQA operations over the same link.
While a frame loss, latency, throughput, or Y.1564 operation is running on the NQA client, you cannot start another operation of the same type.
To start multiple Y.1564 operations simultaneously, add the Y.1564 operations to a Y.1564 operation group, stop all other operations, and then start the Y.1564 operation group.
For path quality analysis operations and Y.1564 operations to start successfully, configure the source and destination IP addresses as follows:
· In a Layer 2 Ethernet, Layer 3 Ethernet, L2VPN, or L3VPN network, configure both source and destination IP addresses.
· In other networks, configure both of them or none of them. If they are configured, make sure the source and destination IP addresses are of the same IP version.
Examples
# Start the throughput operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type throughput
[Sysname-nqa-admin-test-throughput] start
Related commands
nqa y1564 group
stop (frame loss/latency/throughput/Y.1564 operation view/Y.1564 operation group view/RFC2544 operation group view)
start (TWAMP Light sender view)
Use start to start the TWAMP Light test.
Syntax
start test-session session-id { permanent | duration duration | packet-count count } [ tx-interval { 10 | 100 | 1000 | 10000 | 30000 } ] [ time-out timeout ] [ [ statistics-interval statistics-interval ] monitor-time time ]
Default
The TWAMP Light test is not started.
Views
TWAMP Light sender view
Predefined user roles
network-admin
Parameters
test-session session-id: Specifies a TWAMP Light test session by its ID. The value range for the session-id argument is 1 to 512.
permanent: Runs a TWAMP Light test permanently.
duration duration: Specifies the duration for a TWAMP Light test in seconds.The value range for the duration argument is 60 to 300.
packet-count count: Specifies the number of packets to be sent, in the range of 100 to 30000.
tx-interval { 10 | 100 | 1000 | 10000 | 30000 }: Specifies a list of up to four packet sending intervals. Valid intervals are 10, 100, 1000, 10000, and 30000 milliseconds. The default packet sending interval is 100 milliseconds.
time-out timeout: Specifies the timeout time of the reflected packet within a TWAMP Light test, in seconds. The value range for this argument is 1 to 10.The default timeout time is 5 seconds.
statistics-interval interval: Specifies a statistics collection interval for the TWAMP Light test in milliseconds. The value must be an integer multiple of 10 milliseconds. The value range for this argument is 1000 to 20000.The default statistics collection interval varies by packet sending interval. For more information, see Table 17.
monitor-time time: Specifies the packet monitoring time for the TWAMP Light test in milliseconds. The packet monitoring time must be an integer multiple of the statistics collection interval. The value range for this argument is 1000 to 86400000.
Usage guidelines
The TWAMP Light test includes on-demand test and permanent test.
· The on-demand test is manually scheduled. It allows a single performance measurement.
· A permanent test, once being started, does not stop unless you execute the stop command in the TWAMP Light sender view to stop it manually.
In a TWAMP test, the device monitors the test result, and starts the monitoring time when either of the following conditions is met:
· The monitoring result goes beyond the threshold upper limit.
· The monitoring result drops below the threshold lower limit from a monitoring result higher than the lower limit.
If either condition is always true during the monitoring time, a threshold violation occurs.
The monitoring time varies by the monitor-time time option in this command:
· If you specify this option, the monitoring time for packet loss, delay, and jitter uses the specified value.
· If you do not specify this option, the default monitoring time for packet loss, delay, and jitter is used. The default monitoring time varies by the packet sending interval. For more information, see Table 17.
To set the upper and lower limits, use the reaction entry threshold monitoring commands for the TWAMP Light test.
In the TWAMP Light test, a test session is identified by the combination of source IP address, source port number, destination IP address, and destination port number. To ensure the test result, do not specify the same combination for multiple test sessions.
With the data-fill command configured, the packet sending interval cannot be 10 or 100 milliseconds.
With the timestamp-format ntp command configured, the packet sending interval cannot be 10 or 100 milliseconds.
To prevent empty reported test statistics, set the test interval no less than the packet sending interval.
Table 17 Default values for the statistics collection interval and monitoring time
Packet sending interval |
Default test interval (seconds) |
Default monitoring time for two-way packet loss (seconds) |
Default monitoring time for two-way delay and jitter (seconds) |
10 milliseconds |
2 |
60 |
2 |
100 milliseconds |
20 |
60 |
20 |
1 seconds |
200 |
200 |
200 |
10 seconds |
400 |
400 |
400 |
30 seconds |
600 |
600 |
600 |
Examples
# Start the TWAMP Light test and allow the device to send 3000 packets.
<Sysname> system-view
[Sysname] nqa twamp-light sender
[Sysname-nqa-twamp-light-sender] start test-session 1 packet-count 3000
Related commands
data-fill
stop (TWAMP Light sender view)
reaction checked-element two-way-delay
reaction checked-element two-way-loss
reaction checked-element two-way-jitter
statistics hold-time
Use statistics hold-time to set the hold time of statistics groups for an NQA operation.
Use undo statistics hold-time to restore the default.
Syntax
statistics hold-time hold-time
undo statistics hold-time
Default
The hold time of statistics groups for an NQA operation is 120 minutes.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
ICMP jitter/path jitter/UDP jitter/voice operation view
Predefined user roles
network-admin
Parameters
hold-time: Specifies the hold time in minutes, in the range of 1 to 1440.
Usage guidelines
A statistics group is deleted when its hold time expires.
Examples
# Set the hold time to 3 minutes for statistics groups of the ICMP echo operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] statistics hold-time 3
statistics interval
Use statistics interval to set the statistics collection interval for an NQA operation.
Use undo statistics interval to restore the default.
Syntax
statistics interval interval
undo statistics interval
Default
The statistics collection interval is 60 minutes.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
ICMP jitter/path jitter/UDP jitter/voice operation view
Predefined user roles
network-admin
Parameters
interval: Specifies the interval in minutes, in the range of 1 to 35791394.
Usage guidelines
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.
Examples
# Configure NQA to collect the ICMP echo operation statistics every 2 minutes.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] statistics interval 2
statistics max-group
Use statistics max-group to set the maximum number of statistics groups that can be saved.
Use undo statistics max-group to restore the default.
Syntax
statistics max-group number
undo statistics max-group
Default
A maximum of two statistics groups can be saved.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
ICMP jitter/path jitter/UDP jitter/voice operation view
Predefined user roles
network-admin
Parameters
number: Specifies the maximum number of statistics groups, in the range of 0 to 100. To disable statistics collection, set the value to 0.
Usage guidelines
When the maximum number of statistics groups is reached, the system will delete the oldest statistics group to save a new one.
Examples
# Configure NQA to save a maximum of five statistics groups for the ICMP echo operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] statistics max-group 5
stop (frame loss/latency/throughput/Y.1564 operation view/Y.1564 operation group view/RFC2544 operation group view)
Use stop to stop the frame loss, throughput, latency, or Y.1564 operation.
Syntax
stop
Views
Frame loss/latency/throughput/Y.1564 operation view
Y.1564 operation group view
RFC2544 operation group view
Predefined user roles
network-admin
Usage guidelines
Use this command in operation view to stop unexecuted probes (not available for executed probes) in the operation. You can use this command in operation group view to stop all probes in the operation group.
Examples
# Stop the throughput operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type throughput
[Sysname-nqa-admin-test-throughput] stop
Related commands
nqa y1564 group
start (frame-loss/latency/throughput/Y.1564 operation view/Y.1564 operation group view/RFC2544 operation group view)
stop (TWAMP Light sender view)
Use stop to stop the TWAMP Light test.
Syntax
stop { all | test-session session-id }
Views
TWAMP Light sender view
Predefined user roles
network-admin
Parameters
all: Stops the all TWAMP Light test sessions.
test-session session-id: Specifies the ID of a TWAMP Light test session. The value range for this argument is 1 to 512.
Examples
# Stop the TWAMP Light test of the session 1.
<Sysname> system-view
[Sysname] nqa twamp-light sender
[Sysname-nqa-twamp-light-sender] stop test-session 1
Related commands
start (TWAMP Light sender view)
target-only
Use target-only to perform the path jitter operation only on the destination address.
Use undo target-only to restore the default.
Syntax
target-only
undo target-only
Default
NQA performs the path jitter operation to the destination hop by hop.
Views
Path jitter operation view
Predefined user roles
network-admin
Examples
# Perform the path jitter operation only on the destination address.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type path-jitter
[Sysname-nqa-admin-test-path-jitter] target-only
test-session (TWAMP Light client view)
Use test-session to create a test session on TWAMP Light client and enter the client-session view, or enter the client-session view of an existing test session on the TWAMP Light client.
Use undo test-session to delete a test session on the TWAMP Light client.
Syntax
test-session session-id
undo test-session session-id
Default
No test sessions exist on the TWAMP Light client.
Views
TWAMP Light client view
Predefined user roles
network-admin
Parameters
session-id: Specifies a test session by its ID. The value range for this argument is 1 to 512.
Usage guidelines
To start a TWAMP Light test, perform the following tasks in sequence:
1. Create a test session on the TWAMP Light client and complete the settings.
2. Use the nqa twamp-light sender command to enter the TWAMP Light sender view, and start the test session.
Examples
# Specify a test session test-session 1 on the TWAMP Light client and enter the client-session view.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1]
test-session bind interface
Use test-session bind interface to bind an interface as the output interface for a TWAMP Light test session.
Use undo test-session bind interface to unbind an interface from a TWAMP Light test session.
Syntax
test-session session-id bind interface interface-type interface-number
undo test-session session-id bind interface [ interface-type interface-number ]
Default
No interface is specified as the output interface for a TWAMP Light test session.
Views
TWAMP Light client view
Predefined user roles
network-admin
Parameters
session-id: Specifies a test session by its ID. The value range for this argument is 1 to 512.
interface-type interface-number: Specifies an interface by its type and number. If you do not specify this argument, the TWAMP Light test uses all interfaces as the output interfaces for test sessions.
Usage guidelines
With this command configured, the device sends TWAMP Light test packets out of the specified interface. Therefore, configure the interface as the output interface of the route to the TWAMP Light server.
This command also enables the collaboration between the TWAMP Light module and other service modules. After obtaining the valid statistics, the TWAMP Light module will send the delay information (including remote IP address, maximum delay, minimum delay, and average delay) to other service modules, such as the ISIS module, to complete related functions.
The TWAMP Light module sends the data to other service module when the following conditions are met:
· A continuous TWAMP Light test is configured.
· Valid delay data has been collected.
A TWAMP Light test session can be bound with only one interface. If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Bind Ten-GigabitEthernet 3/0/1 as the output interface for TWAMP Light test session 1.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1 bind interface ten-gigabitethernet 3/0/1
timestamp-format
Use timestamp-format to specify the timestamp format for probe packets in the TWAMP Light test.
Use undo timestamp-format to restore the default.
Syntax
timestamp-format { ntp | ptp }
undo timestamp-format
Default
The timestamp format for probe packets in the TWAMP Light test is PTP.
Views
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
ntp: Specifies the NTP format.
ptp: Specifies the PTP format.
Usage guidelines
This command allows you to specify a timestamp format for the probe packet in the TWAMP Light test. The time accuracy in the PTP format is higher than that in the NTP format.
If the time is not synchronized through NTP or PTP, or the TWAMP Light test sender and responder use different timestamp formats, the TWAMP Light test can still be performed, but the test result accuracy might be affected.
Examples
# Specify the timestamp format as NTP for the TWAMP Light test.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] timestamp-format ntp
tos
Use tos to set the ToS value in the IP header for probe packets.
Use undo tos to restore the default.
Syntax
tos value
undo tos
Default
The ToS value in the IP header of probe packets is 0.
Views
Any operation view
DNS/FTP/HTTP/HTTPS/ICMP/IMAP/POP3/RADIUS/SMTP/SNMP/SSL/TCP/TCP half open/UDP template view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
value: Specifies the ToS value in the range of 0 to 255.
Examples
# In ICMP echo operation view, set the ToS value to 1 in the IP header for probe packets.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] tos 1
# In ICMP template view, set the ToS value to 1 in the IP header for probe packets.
<Sysname> system-view
[Sysname] nqa template icmp icmptplt
[Sysname-nqatplt-icmp-icmptplt] tos 1
traffic-policing-test enable
Use traffic-policing-test enable to enable the traffic policing test in a Y.1564 operation.
Use undo traffic-policing-test enable to disable the traffic policing test in a Y.1564 operation.
Syntax
traffic-policing-test enable [ duration duration ]
undo traffic-policing-test enable
Default
The traffic policing test is disabled in a Y.1564 operation.
Views
Y.1564 operation view
Predefined user roles
network-admin
Parameters
duration duration: Specifies the test duration in seconds. The value range is 1 to 60, and the default is 3.
Usage guidelines
The traffic policing test can operate in color-aware mode or non-color aware mode.
· In color-aware mode, the test transmits green frames at the CIR and yellow frames at 125% * PIR or 25% * CIR + PIR, if PIR < 20% * CIR.
· In non-color-aware mode, the test transmits frames at a rate equal to CIR + 125% * PIR or 125%*CIR + PIR, if PIR < 20% * CIR.
You can enable or disable the color-aware mode in a Y.1564 operation.
Examples
# Enable the traffic policing test in a Y.1564 operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type y1564
[Sysname-nqa-admin-test-y1564] traffic-policing-test enable
Related commands
bandwidth
color-aware-mode enable
ttl
Use ttl to set the maximum number of hops that the probe packets can traverse.
Use undo ttl to restore the default.
Syntax
ttl value
undo ttl
Default
The maximum number of hops is 30 for probe packets of the UDP tracert operation, and is 20 for probe packets of other types of operations.
Views
ICMP echo/TCP/UDP echo operation view
DLSw/DNS/FTP/HTTP/SNMP operation view
UDP tracert operation view
ICMP jitter/UDP jitter/voice operation view
DNS/FTP/HTTP/HTTPS/ICMP/IMAP/POP3/RADIUS/SMTP/SNMP/SSL/TCP/TCP half open/UDP template view
Predefined user roles
network-admin
Parameters
value: Specifies the maximum number of hops that the probe packets can traverse, in the range of 1 to 255.
Usage guidelines
The route-option bypass-route command sets the TTL to 1 for probe packets. If you configure both the route-option bypass-route and ttl commands for an operation, the ttl command does not take effect.
For a successful UDP tracert operation, make sure the maximum number of hops is not smaller than the value set in the init-ttl command.
Examples
# Set the maximum number of hops to 16 for probe packets in the ICMP echo operation.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] ttl 16
# In ICMP template view, set the maximum number of hops to 16 for probe packets.
<Sysname> system-view
[Sysname] nqa template icmp icmptplt
[Sysname-nqatplt-icmp-icmptplt] ttl 16
type
Use type to specify an NQA operation type and enter its view.
Syntax
type { dhcp | dlsw | dns | frame-loss | ftp | http | icmp-echo | icmp-jitter | latency | path-jitter | snmp | tcp | throughput | udp-echo | udp-jitter | udp-tracert | voice | y1564 }
Default
No operation type is specified.
Views
NQA operation view
Predefined user roles
network-admin
Parameters
dhcp: Specifies the DHCP operation type.
dlsw: Specifies the DLSw operation type.
dns: Specifies the DNS operation type.
frame-loss: Specifies the frame loss operation type.
ftp: Specifies the FTP operation type.
http: Specifies the HTTP operation type.
icmp-echo: Specifies the ICMP echo operation type.
icmp-jitter: Specifies the ICMP jitter operation type.
latency: Specifies the latency operation type.
path-jitter: Specifies the path jitter operation type.
snmp: Specifies the SNMP operation type.
tcp: Specifies the TCP operation type.
throughput: Specifies the throughput operation type.
udp-echo: Specifies the UDP echo operation type.
udp-jitter: Specifies the UDP jitter operation type.
udp-tracert: Specifies the UDP tracert operation type.
voice: Specifies the voice operation type.
y1564: Specifies the Y.1564 operation type.
Usage guidelines
You can specify only one type for an NQA operation. After that, you can configure the operation type-related settings for the NQA operation. To change the type of the NQA operation, remove the NQA operation in system view, and then re-create the NQA operation.
Examples
# Specify FTP as the NQA operation type and enter FTP operation view.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type ftp
[Sysname-nqa-admin-test-ftp]
url
Use url to specify the URL of the destination.
Use undo url to restore the default.
Syntax
url url
undo url
Default
The destination URL is not specified.
Views
FTP/HTTP operation view
FTP/HTTP/HTTPS template view
Predefined user roles
network-admin
Parameters
url: Specifies the URL of the destination server, a case-sensitive string of 1 to 255 characters. The following table describes the URL format and parameters for different operations.
Operation |
URL format |
Parameter description |
HTTP operation |
http://host/resource http://host:port/resource |
The host parameter represents the host name of the destination server. The host name is a dot-separated case-sensitive string including letters, digits, hyphens (-), and underscores (_). Host names are composed of series of labels, aabbcc.com for example. Each label consists of 1 to 63 characters. Consecutive dots (.) and question marks are not allowed. For description about the filename parameter, see Fundamentals Configuration Guide. |
HTTPS operation |
https://host/resource https://host:port/resource |
|
FTP operation |
ftp://host/filename ftp://host:port/filename |
Examples
# Configure the URL that the HTTP operation visits as http://www.company.com/index.html.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type http
[Sysname-nqa-admin-test-http] url http://www.company.com/index.html
# In HTTP template view, configure the URL that the HTTP operation visits as http://www.company.com/index.html.
<Sysname> system-view
[Sysname] nqa template http httptplt
[Sysname-nqatplt-http-httptplt] url http://www.company.com/index.html
username
Use username to specify a username.
Use undo username to restore the default.
Syntax
username username
undo username
Default
No username is configured.
Views
FTP/HTTP operation view
FTP/HTTP/HTTPS/IMAP/POP3/RADIUS template view
Predefined user roles
network-admin
Parameters
username: Specifies the username. The username is case sensitive and its string length varies as follows:
· The FTP, HTTP, or HTTPS username is a string of 1 to 32 characters.
· The POP3 or IMAP username is a string of 1 to 40 characters in the format username@domain.com.
· The RADIUS authentication username is a string of 1 to 253 characters.
Examples
# Set the FTP login username to administrator in FTP operation view.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type ftp
[Sysname-nqa-admin-test-ftp] username administrator
# Set the FTP login username to administrator in FTP template view.
<Sysname> system-view
[Sysname] nqa template ftp ftptplt
[Sysname-nqatplt-ftp-ftptplt] username administrator
Related commands
operation
password
version
Use version to specify the version used in the HTTP or HTTPS operation.
Use undo version to restore the default.
Syntax
version { v1.0 | v1.1 }
undo version
Default
Version 1.0 is used in the HTTP operation or HTTPS operation.
Views
HTTP operation view
HTTP/HTTPS template view
Predefined user roles
network-admin
Parameters
v1.0: Uses version 1.0.
v1.1: Uses version 1.1.
Examples
# Configure the HTTP operation to use the HTTP version 1.1.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type http
[Sysname-nqa-admin-test-http] version v1.1
vlan
Use vlan to specify a VLAN for probe packets.
Use undo vlan to restore the default.
Syntax
Frame loss/latency/throughput/TWAMP Light operations:
vlan { vlan-id | s-vid vlan-id c-vid vlan-id }
undo vlan
Y.1564 operations:
vlan { vlan-id1 [ to vlan-id2 ] | s-vid vlan-id1 [ to vlan-id2 ] c-vid vlan-id1 [ to vlan-id2 ] }
undo vlan
Default
No VLAN is specified for probe packets.
Views
Frame loss/latency/throughput/Y.1564 operation view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
vlan-id: Specifies a VLAN for the probe packet by its ID in the range of 1 to 4094.
vlan-id1 to vlan-id2: Specifies a VLAN for the probe packet by its ID in the range of 1 to 4094. The vlan-id2 must be greater than the vlan-id1. The value difference between two VLAN IDs cannot exceed 127.
s-vid: Specifies an inner VLAN ID.
c-vid: Specifies an outer VLAN ID.
Usage guidelines
After you specify a VLAN, the operation sends probe packets in the specified VLAN.
You can use this command to specify an inner VLAN ID or outer VLAN ID as needed.
Examples
# Configure the throughput operation to send probe packets in VLAN 3.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type throughput
[Sysname-nqa-admin-test-throughput] vlan 3
# Configure the TWAMP Light test to send probe packets in VLAN 3.
<Sysname> system-view
[Sysname] nqa twamp-light client
[Sysname-nqa-twamp-light-client] test-session 1
[Sysname-nqa-twamp-light-client-session1] vlan 3
vpn-instance
Use vpn-instance to apply the operation to a VPN instance.
Use undo vpn-instance to restore the default.
Syntax
vpn-instance vpn-instance-name
undo vpn-instance
Default
The operation is performed on the public network.
Views
ICMP echo/TCP/UDP echo operation view
DHCP/DLSw/DNS/FTP/HTTP/SNMP operation view
UDP tracert operation view
ICMP jitter/path jitter/UDP jitter/voice operation view
Frame loss/latency/throughput/Y.1564 operation view
Any NQA template view
TWAMP Light client-session view
Predefined user roles
network-admin
Parameters
vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
After you specify a VPN instance, the NQA operation is performed in the specified VPN instance.
Examples
# Apply the ICMP echo operation to vpn1.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] vpn-instance vpn1
# In FTP template view, apply the FTP operation to vpn1.
<Sysname> system-view
[Sysname] nqa template ftp ftptplt
[Sysname-nqatplt-ftp-ftptplt] vpn-instance vpn1
NQA server commands
IMPORTANT: Configure the NQA server only for UDP jitter, TCP, UDP echo, and voice operations. |
adjust-udp-checksum global enable (TWAMP Light responder view)
Use adjust-udp-checksum global enable to enable checksum field adjustment globally for test packets.
Use undo adjust-udp-checksum global enable to disable checksum field adjustment globally for test packets.
Syntax
adjust-udp-checksum global enable
undo adjust-udp-checksum global enable
Default
Checksum field adjustment for test packets is disabled globally.
Views
TWAMP Light responder view
Predefined user roles
network-admin
Usage guidelines
By default, the checksum value in TWAMP Light test packets is 0. With this command configured, Twamp Light will fill the calculated checksum value in the checksum field of test packets. Support for the checksum value varies by TWAMP Light reflectors. Enable checksum field adjustment for test sessions as required by the TWAMP Light reflector connected to the device.
Enable checksum field adjustment for test packets in either of following ways:
· Enable the feature globally. The feature will take effect on all sessions to be created in TWAMP Light responder view, and will not affect existing sessions.
· Use the test-session (TWAMP Light responder view) command to enable the feature. The feature will take effect only on the session to start.
This feature applies only to IPv6 packets.
Examples
# Enable checksum field adjustment globally for test packets.
<Sysname> system-view
[Sysname] nqa twamp-light responder
[Sysname-nqa-twamp-light-responder] adjust-udp-checksum global enable
Related commands
test-session (TWAMP Light responder view)
display nqa reflector
Use display nqa reflector to display a reflector of a path quality analysis operation or Y.1564 operation.
Syntax
display nqa reflector [ reflector-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
reflector-id: Specifies the ID of a reflector. The value range for this argument is 1 to 544.If you do not specify this option, the command displays information about all reflectors.
Examples
# Display information about the specified reflector.
<Sysname> display nqa reflector 1
NQA server status:Enabled
Reflector ID : 1
Status : Active
Interface : XGE3/0/1
Service instance : -
Destination IP : 1.1.1.2
Destination IPv6 : -
Source IP : 1.1.1.1
Source IPv6 : -
Destination port : 2010
Source port : 2001
Destination MAC : -
Source MAC : -
VLAN ID : -
Service VLAN ID : -
Customer VLAN ID : -
VPN instance : -
Switch src/dst ports : Enabled
Table 18 Command output
Field |
Description |
NQA server status |
NQA server status: Disabled or Enabled. |
Reflector ID |
Reflector ID. |
Status |
Reflector status: · Active—The reflector is running. · Inactive—The reflector is not running. |
Interface |
Interface that reflects the test packets. |
Service instance |
Ethernet service instance bound to the interface. The Ethernet service instance on the reflector must be consistent with that on the client. |
Destination IP |
Destination IPv4 address in the reflected packets. |
Destination IPv6 |
Destination IPv6 address or IPv6 address range in the reflected packets. |
Source IP |
Source IPv4 address or IPv4 address range in the reflected packets. |
Source IPv6 |
Source IPv6 address or IPv6 address range in the reflected packets |
Destination port |
Destination UDP port number or port number range in the reflected packets. |
Source port |
Source UDP port number or port number range in the reflected packets. |
Destination MAC |
Destination MAC address or MAC address range in the reflected packets. |
Source MAC |
Source MAC address or MAC address range in the reflected packets. |
VLAN ID |
VLAN ID or VLAN ID range in the reflected packets. |
Service VLAN ID |
Outer VLAN ID or VLAN ID range in the reflected packets. |
Customer VLAN ID |
Inner VLAN ID or VLAN ID range in the reflected packets. |
VPN instance |
VPN instance name. |
Switch src/dst ports |
Port exchange status: · Enabled. · Disabled. |
display nqa server
Use display nqa server status to display NQA server status.
Syntax
display nqa server
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display NQA server status.
<Sysname> display nqa server
NQA server status: Enabled
TCP connect:
IP address:2.2.2.2
Port:2000
ToS:200
VPN instance:-
UDP echo:
IP address:3.3.3.3
Port:3000
ToS:255
VPN instance:-
High performance mode: Enabled
Table 19 Command output
Field |
Description |
NQA server status |
NQA server status: · Disabled. · Enabled. |
TCP connect |
Information about the TCP listening service on the NQA server. |
UDP echo |
Information about the UDP listening service on the NQA server. |
IP address |
IP address specified for the TCP/UDP listening service on the NQA server. |
Port |
Port number specified for the TCP/UDP listening service on the NQA server. |
ToS |
ToS value in the reply packets sent by the NQA server. The ToS value can be specified when you configure a TCP or UDP listening service on the NQA server. If no ToS value is specified, the following rules apply: · This field displays a hyphen (-). · The ToS value in the reply packets of a TCP listening service is 0. · The ToS value in the reply packets of a UDP listening service is obtained from the request packets sent by the client. |
VPN instance |
Name of the VPN instance to which the IP address that the NQA server listens on belongs. This field displays a hyphen (-) if the NQA server listens on a public IP address. |
High performance mode |
Whether or not the high performance mode is enabled on the NQA server. |
display nqa twamp-light responder
Use display nqa twamp-light responder to display test sessions on the TWAMP Light responder.
Syntax
display nqa twamp-light responder [ test-session session-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
test-session session-id: Specifies a test session by its ID. The value range for this argument is 1 to 512. If you do not specify this option, the command displays all test sessions on the TWAMP Light responder.
Examples
# Display all test sessions on the TWAMP Light responder.
<Sysname> display nqa twamp-light responder
NQA server status:Enabled
TWAMP-light:
Session ID : 1
Status : Active
Interface : -
Service instance : -
Destination IP : 1.1.1.1
Destination IPv6 : -
Source IP : 2.2.2.2
Source IPv6 : -
Destination port : 2001
Source port : 2010
VPN instance : -
Destination MAC : 0001-0001-0002
Source MAC : 0001-0001-0001
VLAN ID : -
Service VLAN ID : -
Customer VLAN ID : -
Timestamp format : PTP
Description : -
Adjust-udp-checksum : Enabled
Extended-packet : Enabled
Link bundle interface : -
Session ID : 2
Status : Active
Interface : -
Service instance : -
Destination IP : 1.1.1.1
Destination IPv6 : -
Source IP : 3.3.3.3
Source IPv6 : -
Destination port : 2001
Source port : 2020
VPN instance : -
Destination MAC : 0001-0001-0002
Source MAC : 0001-0001-0001
VLAN ID : -
Service VLAN ID : -
Customer VLAN ID : -
Timestamp format : NTP
Description : -
Adjust-udp-checksum : Disabled
Extended-packet : Disabled
Link bundle interface : Route-Aggregation 1
Member interface : Ten-GigabitEthernet3/0/1
Status : Active
Member interface : Ten-GigabitEthernet3/0/2
Status : Active
Table 20 Command output
Field |
Description |
NQA server status |
NQA server status: · Disabled · Enabled |
TWAMP-light |
Information about the TWAMP Light feature on the NQA server. |
Session ID |
Test session ID. |
Status |
TWAMP Light responder status: · Active—The TWAMP Light responder is active. · Inactive—The TWAMP Light responder is not active. |
Interface |
Interface that reflects the test packets. |
Service instance |
Ethernet service instance bound to the interface. The Ethernet service instance on the responder must be consistent with that on the client. |
Destination IP |
Destination IP address in the reflected packet. |
Destination IPv6 |
Destination IPv6 address in the reflected packet. |
Source IP |
Source IP address in the reflected packet. |
Source IPv6 |
Source IPv6 address in the reflected packet. |
Destination port |
Destination port number in the reflected packet. |
Source port |
Source port number in the reflected packet. |
VPN instance |
MPLS L3VPN instance name. |
Destination MAC |
Destination MAC address in the reflected packet. |
Source MAC |
Source MAC address in the reflected packet. |
VLAN ID |
VLAN ID in the reflected packet. |
Service VLAN ID |
Outer VLAN ID or VLAN ID range in the reflected packet. |
Customer VLAN ID |
Inner VLAN ID or VLAN ID range in the reflected packet. |
Timestamp format |
Timestamp format: · AUTO—The TWAMP Light responder selects a timestamp format automatically if you do not set a timestamp format by using the test-session command. · NTP. · PTP. |
Description |
Description about the test session. |
Adjust-udp-checksum |
Whether or not to adjust the checksum value in test packets. · Enabled—Adjust the checksum value in test packets. · Disabled—Do not adjust the checksum value in test packets. The checksum value is 0. |
Adjust-udp-checksum |
Whether or not to extend the header of reflected packets. · Enabled—The device extends the TWAMP packet header in the reflected packets to the standard header length if the data size of received test packets is less than 41 bytes. · Disabled—The device directly constructs reflected packets based on the received test packets with a data size of less than 41 bytes, without extending the TWAMP packet header. The test result might be inaccurate because the header of reflected packets lacks necessary parameters. |
Extended-packet |
Whether or not to extend the header of reflected packets. · Enabled—The device extends the TWAMP packet header in the reflected packets to the standard header length if the data size of received test packets is less than 41 bytes. · Disabled—The device directly constructs reflected packets based on the received test packets with a data size of less than 41 bytes, without extending the TWAMP packet header. The test result might be inaccurate because the header of reflected packets lacks necessary parameters. |
Link bundle interface |
Name of the link bundle interface. In this software version, the link bundle interface can only be a Layer 3 aggregate interface or subinterface. This field displays a hyphen (-) when the interface is not a link bundle interface. |
Member interface : Status : |
· Name of the member interface. · Session status: ¡ Active—The TWAMP Light test is active. ¡ Inactive—The TWAMP Light test is not active. |
Related commands
nqa reflector
test-session (TWAMP Light responder view)
nqa reflector
Use nqa reflector to configure a reflector for the path quality analysis operation or Y.1564 operation.
Use undo nqa reflector to delete the reflector for the path quality analysis operation or Y.1564 operation.
Syntax
nqa reflector reflector-id interface interface-type interface-number [ service-instance instance-id ] [ { ip | ipv6 } { destination address1 [ to address2 ] | source address1 [ to address2 ] } * | destination-port port-number1 [ to port-number2 ] | source-port port-number1 [ to port-number2 ] | destination-mac mac-address1 [ to mac-address2 ] | source-mac mac-address1 [ to mac-address2 ] | vlan { vlan-id1 [ to vlan-id2 ] | s-vid vlan-id1 [ to vlan-id2 ] c-vid vlan-id1 [ to vlan-id2 ] } | exchange-port | vpn-instance vpn-instance-name ] *
undo nqa reflector { all | reflector-id [ { ip | ipv6 } { destination | source } | destination-port | source-port | destination-mac | source-mac | vlan | exchange-port | vpn-instance ] * }
Default
No reflector is configured for the path quality analysis operation or Y.1564 operation.
Views
System view
Predefined user roles
network-admin
Parameters
reflector-id: Specifies the ID of a reflector .The reflector ID must be unique and is locally significance. The value range for this argument is 1 to 544.
interface: Specifies an interface that reflects the packets.
interface-type interface-number: Specifies an interface by its type and number.
service-instance instance-id: Specifies an Ethernet service instance by its ID, in the range of 1 to 4096. For more information about the Ethernet service instance, see MPLS L2VPN in MPLS Configuration Guide.
ip: Specifies an IPv4 address.
ipv6: Specifies an IPv6 address.
destination: Specifies a destination address of the packets to be reflected.
source: Specifies a source address of the packets to be reflected.
address1 to address2: Specifies an IP address range. The address2 must be higher than the address1. Between the two IP addresses, only one octet difference is allowed and the value difference cannot exceed 127.
destination-port: Specifies a destination UDP port number of the packets to be reflected. The default destination port number is 7.
source-port: Specifies a source UDP port number of the packets to be reflected. The default source port number is 49185.
port-number1 to port-number2: Specifies a port range, in the range of 1 to 65535. The port-number2 must be greater than the port-number1. Between the two port numbers, only one octet difference is allowed and the value difference cannot exceed 127.
destination-mac: Specifies a destination MAC address for the packet to be reflected. If you do not specify this keyword, the command uses the MAC address of the interface specified by the interface-type interface-number option. Broadcast, multicast, and all-zero MAC addresses are not supported.
source-mac: Specifies a source MAC address for the packets to be reflected. Broadcast, multicast, and all-zero MAC addresses are not supported.
mac-address1 to mac-address2: Specifies a MAC address range. The mac-address2 must be higher than the mac-address1. Between the two MAC addresses, only one octet difference is allowed and the value difference cannot exceed 127.
vlan: Specifies a VLAN, inner VLAN ID, or outer VLAN ID for the packets to be reflected.
vlan-id1 to vlan-id2: Specifies a VLAN ID range, in the range of 1 to 4094. The vlan-id2 must be higher than the vlan-id1. Between the two VLAN IDs, only one octet difference is allowed and the value difference cannot exceed 127.
s-vid: Specifies an inner VLAN ID.
c-vid: Specifies an outer VLAN ID.
exchange-port: Exchanges the port number between source and destination ports. If you specify this keyword, execute the exchange-port enable command on the client.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the operation is performed on the public network.
all: Disables all reflectors for the path quality analysis operation or Y.1564 operation.
Usage guidelines
This command is required on the NQA server for the path quality analysis operation and Y.1564 operation. It enables the server to reflect matching probe packets directly to the NQA client.
You can specify only one value range for one of the following options when configuring this command:
· Source IP address.
· Destination IP address.
· Source MAC address.
· Destination MAC address.
· Source port.
· Destination port.
· Service VLAN ID.
· Customer VLAN ID.
In the path quality analysis operations, you cannot specify value ranges for the above options.
You can specify the same interface or Ethernet service instance for different reflectors.
If you want to edit or delete the interface or Ethernet service instance in an existing reflector, you must delete the reflector and reconfigure it.
Except for the interface and Ethernet service instance, you can directly edit or delete other parameters.
If you do not specify any optional parameters in the undo command, the reflector will be deleted.
To ensure correct operations, do not configure both the nqa reflector command and the l2vpn reflector command. For more information about the l2vpn reflector command, see MPLS L2VPN in MPLS Command Reference.
Examples
# Configure a reflector on the NQA server for path quality analysis operations and Y.1564 operations.
<Sysname> system-view
[Sysname] nqa reflector 1 interface ten-gigabitethernet 3/0/1 ip destination 2.2.2.2 source 1.1.1.1
nqa server enable
Use nqa server enable to enable the NQA server.
Use undo nqa server enable to disable the NQA server.
Syntax
nqa server enable
undo nqa server enable
Default
The NQA server is disabled.
Views
System view
Predefined user roles
network-admin
Examples
# Enable the NQA server.
<Sysname> system-view
[Sysname] nqa server enable
nqa server icmp-server
Use nqa server icmp-server to configure an ICMP reflector on the NQA server.
Use undo nqa server icmp-server to restore the default.
Syntax
nqa server icmp-server { ipv4-address | ipv6 ipv6-address } [ vpn-instance vpn-instance-name ] [ tos tos ]
undo nqa server icmp-server { ipv4-address | ipv6 ipv6-address } [ vpn-instance vpn-instance-name ]
Default
No ICMP reflector is configured for the NQA server.
Views
System view
Predefined user roles
network-admin
Parameters
ipv4-address: Specifies the IPv4 address to be reflected by the ICMP reflector.
ipv6-address: Specifies the IPv6 address to be reflected by the ICMP reflector.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the ICMP reflector reflects a public IP address.
tos tos: Specifies the ToS value in the IP header for reply packets. The value range is 0 to 255. If you do not specify this option, the ToS value is 0.
Usage guidelines
Before you perform an ICMP jitter operation in echo packet mode, configue this command to enhance accuracy. This command does not apply to other type of operations.
The IP address or VPN instance specified in this command must be the same as the destination IP address or VPN instance specified for the NQA client. Additionally, the IP address specified in this command must be that of an interface on the device.
To specify mutiple IP addresses or VPN instances, execute this command multiple times. This command no longer takes effect if the number of reflected entries for the ICMP reflector reaches the upper limit.
Examples
# Configure an ICMP reflector that reflects IP address 10.1.1.2.
<Sysname> system-view
[Sysname] nqa server icmp-server 10.1.1.2
Related commands
destination ip
vpn-instance
nqa server tcp-connect
Use nqa server tcp-connect to configure a TCP listening service to enable the NQA server to listen to a TCP port on an IP address.
Use undo nqa server tcp-connect to remove a TCP listening service.
Syntax
nqa server tcp-connect { ipv4-address | ipv6 ipv6-address } port-number [ vpn-instance vpn-instance-name ] [ tos tos ]
undo nqa server tcp-connect { ipv4-address | ipv6 ipv6-address } port-number [ vpn-instance vpn-instance-name ]
Default
No TCP listening services exist.
Views
System view
Predefined user roles
network-admin
Parameters
ipv4-address: Specifies the IPv4 address for the TCP listening service.
ipv6 ipv6-address: Specifies the IPv6 address for the TCP listening service.
port-number: Specifies the port number for the TCP listening service, in the range of 1 to 65535.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the NQA server listens on a public IP address.
tos tos: Specifies the ToS value in the IP header for reply packets. The value range is 0 to 255. If you do not specify this option, the ToS value is 0.
Usage guidelines
Use this command on the NQA server only for the TCP and DLSw operations. For the DLSw operation, the port number for the TCP listening service on the NQA server must be 2065. Otherwise, the DLSw operation fails.
When you configure the IP address and port number for a TCP listening service on the NQA server, follow these restrictions and guidelines:
· The IP address, port number, and VPN instance must be unique on the NQA server and match the configuration on the NQA client.
· The IP address must be the address of an interface on the NQA server.
· To ensure successful NQA operations and avoid affecting existing services, do not configure the TCP listening service on well-known ports.
Examples
# Configure a TCP listening service to enable the NQA server to listen to TCP port 9000 on IP address 169.254.10.2.
<Sysname> system-view
[Sysname] nqa server tcp-connect 169.254.10.2 9000
Related commands
destination ip
destination port
vpn-instance
nqa server udp-echo
Use nqa server udp-echo to configure a UDP listening service to enable the NQA server to listen to a UDP port on an IP address.
Use undo nqa server udp-echo to remove the UDP listening service created.
Syntax
nqa server udp-echo { ipv4-address | ipv6 ipv6-address } port-number [ vpn-instance vpn-instance-name ] [ high-performance-mode ] [ tos tos ]
undo nqa server udp-echo { ipv4-address | ipv6 ipv6-address } port-number [ vpn-instance vpn-instance-name ]
Default
No UDP listening services exist.
Views
System view
Predefined user roles
network-admin
Parameters
ipv4-address: Specifies the IPv4 address for the UDP listening service.
ipv6 ipv6-address: Specifies the IPv6 address for the UDP listening service.
port-number: Specifies the port number for the UDP listening service, in the range of 1 to 65535.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the NQA server listens on a public IP address.
high-performance-mode: Enables the high performance mode for the UDP jitter operation on the NQA server. By default, the high performance mode is disabled.
tos tos: Specifies the ToS value in the IP header for reply packets. The value range for this argument is 0 to 255. If you do not specify this option, the ToS value is obtained from the request packets sent by the client.
Usage guidelines
Use this command on the NQA server only for the UDP jitter, UDP echo, and voice operations.
When you configure the IP address and port number for a UDP listening service on the NQA server, follow these restrictions and guidelines:
· The IP address, port number, and VPN instance must be unique on the NQA server and match the configuration on the NQA client.
· The IP address must be the address of an interface on the NQA server.
· To ensure successful NQA operations and avoid affecting existing services, do not configure the UDP listening service on well-known ports.
Examples
# Configure a UDP listening service to enable the NQA server to listen to UDP port 9000 on IP address 169.254.10.2.
<Sysname> system-view
[Sysname] nqa server udp-echo 169.254.10.2 9000
Related commands
destination ip
destination ipv6
destination port
vpn-instance
nqa twamp-light responder
Use nqa twamp-light responder to enable the TWAMP Light responder and enter its view, or enter the view of the enabled TWAMP Light responder.
Use undo nqa twamp-light responder to disable the TWAMP Light responder.
Syntax
nqa twamp-light responder
undo nqa twamp-light responder
Default
The TWAMP Light responder is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
In TWAMP Light responder view, you can create a test session to interact with the test session on the TWAMP Light client.
The undo nqa twamp-light responder command disables the responder and deletes all test sessions on the responder.
Examples
# Enable the TWAMP Light responder and enter its view.
<Sysname> system-view
[Sysname] nqa twamp-light responder
[Sysname-nqa-twamp-light-responder]
test-session (TWAMP Light responder view)
Use test-session to create a test session on the TWAMP Light responder.
Use undo test-session to delete a test session on the TWAMP Light responder.
Syntax
test-session session-id [ interface interface-type interface-number [ service-instance instance-id ] ] [ link-bundle-interface interface-type interface-number ] { destination-mac mac-address source-mac mac-address | { ip | ipv6 } destination address source address destination-port port-number source-port port-number [ vpn-instance vpn-instance-name ] } * [ adjust-udp-checksum | description text | extended-packet | timestamp-format { ntp | ptp } | vlan { vlan-id | s-vid vlan-id c-vid vlan-id } ] *
undo test-session session-id
Default
No test sessions exist on the TWAMP Light responder.
Views
TWAMP Light responder view
Predefined user roles
network-admin
Parameters
session-id: Specifies a test session by its ID. The value range for this argument is 1 to 512.
interface interface-type interface-number: Specifies a reflecting interface by its type and number.
service-instance instance-id: Specifies an Ethernet service instance by its ID, in the range of 1 to 4096.
link-bundle-interface interface-type interface-number: Specifies an aggregate interface by its type and number. The member interfaces of the aggregate interface will be used as output interfaces for the reflected packets.
destination-mac: Specifies a destination MAC address for the packets to be reflected.
source-mac: Specifies a source MAC address for the packets to be reflected.
mac-address: Specifies a MAC address in the format H-H-H. For example, to use 000f-00e2-0001 as the destination MAC address, set this argument to f-e2-1.
ip: Specifies an IPv4 address.
ipv6: Specifies an IPv6 address.
destination: Specifies a destination address for the packets to be reflected.
source: Specifies a source address for the packets to be reflected.
destination-port port-number: Specifies a destination UDP port number for the packets to be reflected, in the range of 1 to 65535.
source-port port-number: Specifies a source UDP port number for the packets to be reflected, in the range of 1 to 65535.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the operation is performed on the public network.
adjust-udp-checksum: Adjusts the checksum value in TWAMP Light test packets.
description text: Specifies a description for the test session, a case-sensitive string of 1 to 200 characters.
extended-packet: Extends the TWAMP Light packet header in the reflected packets to the standard header length if the data size of received test packets is less than 41 bytes. If this keyword is not specified, the device directly constructs reflected packets based on the received test packets, without extending the TWAMP Light packet header. The test result might be inaccurate because the header of reflected packets lacks necessary parameters.
timestamp-format: Specifies the timestamp format for the TWAMP Light responder. If you do not specify a timestamp format, the default value AUTO is used and the TWAMP Light responder selects a timestamp format automatically.
· ntp: Specifies the NTP format.
· ptp: Specifies the PTP format.
vlan: Specifies a VLAN, service VLAN ID, or customer VLAN ID for the packets to be reflected.
· vlan-id: Specifies a VLAN ID, in the range of 1 to 4094.
· s-vid: Specifies a service VLAN ID.
· c-vid: Specifies a customer VLAN ID.
Usage guidelines
The test session on the TWAMP Light responder interacts with the test session on the TWAMP Light client.
The following settings specified in this command must be consistent with those on the TWAMP Light client:
· Source IP address.
· Destination IP address.
· Source UDP port number.
· Destination UDP port number.
· VPN instance name.
If the specified test session ID does not exist, this command creates a new test session. If you specify an existing session ID, you are modifying the test session.
You can specify the same interface or Ethernet service instance for different test sessions.
If you want to edit or delete the interface or Ethernet service instance in an existing reflector, you must delete the reflector and reconfigure it.
Except for the interface and Ethernet service instance, you can edit or delete other parameters.
If you do not specify any optional parameters in the undo command, you are deleting the test session. If all configurations about the session are deleted, the test session will be deleted.
By default, the checksum value in TWAMP Light test packets is 0. With adjust-udp-checksum specified in this command, Twamp Light will fill the calculated checksum value in the checksum field of test packets. Support for the checksum value varies by TWAMP Light reflectors. Enable checksum field adjustment for test sessions as required by the TWAMP Light reflector connected to the device. If the TWAMP Light client is an H3C device, this keyword is not required.
Enable checksum field adjustment for test packets in either of following ways:
· Enable the feature globally. The feature will take effect on all sessions to be created in TWAMP Light responder view, and will not affect existing sessions.
· Use this command to enable the feature. The feature will take effect only on the session to start.
This feature applies only to IPv6 packets.
Examples
# Create a test session test-session 1 on the TWAMP Light responder. Specify source IPv4 address 1.1.1.1, destination IPv4 address 2.2.2.2, source port 3000, destination port 3001, and VPN instance vpn1 for the test session.
<Sysname> system-view
[Sysname] nqa twamp-light responder
[Sysname-nqa-twamp-light-responder] test-session 1 ip destination 2.2.2.2 source 1.1.1.1 destination-port 3001 source-port 3000 vpn-instance vpn1
Related commands
adjust-udp-checksum enable (TWAMP Light responder view)
TWAMP server commands
client acl
Use client acl to specify an ACL to control client access.
Use undo client acl to restore the default.
Syntax
client acl { acl-number | name acl-name }
undo client acl
Default
No ACL is specified to control TWAMP client access.
Views
IPv4 TWAMP server view
IPv6 TWAMP server view
Predefined user roles
network-admin
Parameters
acl-number: Specifies an ACL by its number. The following are available value ranges:
· 2000 to 2999 for basic ACLs.
· 3000 to 3999 for advanced ACLs.
name acl-name: Specifies an ACL by its name. The acl-name argument is a case-insensitive string of 1 to 63 characters. It must start with an English letter and it cannot be all to avoid confusion. This command supports only basic and advanced ACLs.
Usage guidelines
With this command configured, only the clients matching the ACL permit rule can connect to the TWAMP server.
If the specified ACL does not exist, or no rule is contained in the specified ACL, the client access will not be controlled by ACLs.
IPv4 ACLs take effect only in IPv4 TWAMP server view and IPv6 ACLs in IPv6 TWAMP server view. If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Specify ACL 3000 to control TWAMP client access.
<Sysname> system-view
[Sysname] nqa twamp server
[Sysname-twamp-server] client acl 3000
control-session timeout
Use control-session timeout to specify a timeout timer for TWAMP server control sessions.
Use undo control-session timeout to restore the default.
Syntax
control-session timeout timeout
undo control-session timeout
Default
The timeout timer for TWAMP server control sessions is 900 seconds.
Views
IPv4 TWAMP server view
IPv6 TWAMP server view
Predefined user roles
network-admin
Parameters
timeout: Specifies a timeout timer for TWAMP server control sessions, in the range of 1 to 6000 seconds.
Usage guidelines
A TWAMP test involves a TWAMP control session and TWAMP test session. One TWAMP test corresponds to one TWAMP test session and multiple TWAMP test sessions can share one TWAMP control session. Based on the TCP protocol, a TWAMP control session is used to negotiate the parameters of TWAMP test sessions.
If a TWAMP control session is inactive for a specified period of time, it will be deleted to release system resources.
Examples
# Specify 600 seconds as the timeout timer for TWAMP server control sessions.
<Sysname> system-view
[Sysname] nqa twamp server
[Sysname-twamp-server] control-session timeout 600
display nqa twamp server global-information
Use display nqa twamp server global-information to display global information about the TWAMP server.
Syntax
display nqa twamp [ ipv6 ] server global-information
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv6: Displays global information about the IPv6 TWAMP server. If you do not specify this keyword, this command displays global information about the IPv4 TWAMP server.
Examples
# Display global information about the TWAMP server.
<Sysname> display nqa twamp server global-information
Start time : 2020-10-27 17:43:24.111
Server address : 0.0.0.0
Server port : 862
Server timeout time : 900
Reflector timeout time : --
Reflector status : Enabled
Control sessions : 10
Test sessions : 10
Completed test sessions : 10
Aborted test sessions : 0
Sent probe packets : 100
Received probe packets : 100
Table 21 Command output
Field |
Description |
Start time |
Time when the TWAMP test starts. |
Server address |
IP address listened by the TWAMP service. |
Server port |
Port listened by the TWAMP server. |
Server timeout time |
Aging time of control sessions. |
Reflector timeout time |
Aging time of test sessions. |
Reflector status |
Status of TWAMP test sessions: · Enabled. · Disabled. |
Control sessions |
Number of control sessions. |
Test sessions |
Number of test sessions. |
Completed test sessions |
Number of completed test sessions. |
Aborted test sessions |
Number of aborted test sessions. |
Sent probe packets |
Number of sent test packets. |
Received probe packets |
Number of received test packets. |
display nqa twamp server session
Use display nqa twamp server session to display session information about the TWAMP server.
Syntax
display nqa twamp [ ipv6 ] server session [ source source-ip [ vpn-instance vpn-instance-name ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv6: Displays session information about the IPv6 TWAMP server. If you do not specify this keyword, this command displays session information about the IPv4 TWAMP server.
source source-ip: Specifies the source IP address.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the TWAMP test is performed on the public network.
Examples
# Display session information about the TWAMP server.
<Sysname> display nqa twamp server session
Controle session 1:
Client address : 192.168.29.2
Client port : 51637
Server address : 192.168.29.1
Server port : 5001
VPN instance : --
Mode : No Authentication
Created at : 2012-08-05 16:47:55
Connection state : Active
Test session 1:
Sender address : 192.168.29.2
Sender port : 11001
Reflector address : 192.168.29.1
Reflector port : 12001
DSCP : 0
Padding length : 128
Created at : 2012-08-05 16:47:55
Session ID : 192.168.29.1:3596890923-1139789831:dca28147
Sent probe packets : 100
Received probe packets : 100
Session state : Active
Test session 2:
Sender address : 192.168.29.2
Sender port : 11001
Reflector address : 192.168.29.1
Reflector port : 12001
DSCP : 0
Padding length : 128
Created at : 2012-08-05 16:47:55
Session ID : 192.168.29.1:3596890923-1139789831:dca28147
Sent probe packets : 100
Received probe packets: 100
Session state : Active
Controle session 2:
Client address : 192.168.29.2
Client port : 51637
Server address : 192.168.29.1
Server port : 5001
VPN instance : --
Mode : No Authentication
Created time : 2012-08-05 16:47:55
Connection state : Active
Test session 1:
Sender address : 192.168.29.2
Sender port : 11001
Reflector address : 192.168.29.1
Reflector port : 12001
DSCP : 0
Padding length : 128
Created at : 2012-08-05 16:47:55
Session ID : 192.168.29.1:3596890923-1139789831:dca28147
Sent probe packets : 100
Received probe packets: 100
Session state : Active
Table 22 Command output
Field |
Description |
Controle session |
Control session information. |
Client address |
Client IP address. |
Client port |
Client port number. |
Server address |
Server IP address. |
Server port |
Server port number. |
VPN instance |
VPN instance where the server belongs. |
Mode |
Probe mode: · No Authentication—The test uses the non-authentication mode. · Invalid Mode—The control session uses the initial mode. |
Created time |
Time when the control session is created. |
Connection state |
Connection state: · Initial—The control session is in the initialization state. · Connecting—The control session is in connection state and the parameters are being negotiated. · Establish—The control session is established but the test session is not established. · Inactive—Both the control session and test session are established, but the test session is in inactive state. · Active—Both the control session and test session are established, and the test session is in active state. |
Test session |
Test session information. |
Sender address |
Sender IP address. |
Sender port |
Sender port number. |
Reflector address |
Reflector IP address. |
Reflector port |
Reflector port number. |
DSCP |
DSCP value of the test packets. |
Padding length |
Padding length of the test packets. |
Created at |
Time when the test session is created. |
Session ID |
Test session ID that is generated by the device automatically. |
Sent probe packets |
Number of test packets sent by the device. |
Received probe packets |
Number of test packets received by the device. |
Session state |
Test session state: · Active. · Inactive. |
nqa twamp reflector
Use nqa twamp reflector to enable the TWAMP reflector and enter its view.
Use undo nqa twamp reflector to disable the TWAMP reflector.
Syntax
nqa twamp reflector
undo nqa twamp reflector
Default
The TWAMP reflector is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
A TWAMP test uses the client-server mode. Meanwhile, the server can function as the reflector and the client as the sender.
A TWAMP test works as follow:
· The server and the client establish a TWAMP control session to negotiate and manage the TWAMP test session.
· The reflector and the sender establish a TWAMP test session to exchange test packets.
With this command configured, the device functions as the reflector to respond the test packets sent by the sender.
Examples
# Enable the TWAMP reflector.
<Sysname> system-view
[Sysname] nqa twamp reflector
[Sysname-nqa-twamp-reflector]
nqa twamp server
Use nqa twamp server to enable the TWAMP server and enter its view.
Use undo nqa twamp server to disable the TWAMP server.
Syntax
nqa twamp [ ipv6 ] server
undo nqa twamp [ ipv6 ] server
Default
Both the TWAMP server and IPv6 TWAMP server are disabled.
Views
System view
Predefined user roles
network-admin
Parameters
ipv6: Enables the IPv6 TWAMP server and enters its view. If you do not specify this keyword, this command enables the IPv4 TWAMP server and enters its view.
Usage guidelines
A TWAMP test uses the client-server mode. Meanwhile, the server must support the reflector feature and the client supports the sender feature.
A TWAMP test works as follow:
· The server and the client establish a TWAMP control session to negotiate and manage the TWAMP test session.
· The reflector and the sender establish a TWAMP test session to exchange test packets.
With this command configured, the device functions as the TWAMP server to respond the test requests sent by the TWAMP client.
If you execute the undo nqa twamp [ ipv6 ] server command, all the TWAMP server settings are deleted.
Examples
# Enable the IPv4 TWAMP Server.
<Sysname> system-view
[Sysname] nqa twamp server
[Sysname-nqa-twamp-server]
# Enable the IPv6 TWAMP Server.
<Sysname> system-view
[Sysname] nqa twamp ipv6 server
[Sysname-nqa-twamp-ipv6-server]
tcp port
Use tcp port to specify a TCP port listened by the TWAMP server.
Use undo tcp port to restore the default.
Syntax
tcp port port-number [ all | vpn-instance vpn-instance-name ]
undo tcp port
Default
The TCP port listened by the TWAMP server is 862.
Views
IPv4 TWAMP server view
IPv6 TWAMP server view
Predefined user roles
network-admin
Parameters
port-number: Specifies the TCP port number in the range of 1 to 65535.
all: Specifies the public network and all VPN instances.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the TWAMP test is performed on the public network.
Usage guidelines
Execute this command to modify the TCP port listened by the TWAMP server when either of the following conditions are met:
· The default TCP port is used by other services.
· The destination port number of the test packets sent by the TWAMP client is not 862.
The TCP port listened by the TWAMP server must be consistent with the destination port of the test packets sent by the TWAMP client.
Examples
# Specify 65530 as the TCP port listened by the TWAMP server.
<Sysname> system-view
[Sysname]nqa twamp server
[Sysname-nqa-twamp-server]tcp port 65530
test-session timeout
Use test-session timeout to specify a timeout timer for TWAMP reflector test sessions.
Use undo test-session timeout to restore the default.
Syntax
test-session timeout timeout
undo test-session timeout
Default
The timeout timer for TWAMP reflector test sessions is 900 seconds.
Views
TWAMP reflector view
Predefined user roles
network-admin
Parameters
timeout: Specifies a timeout timer for TWAMP reflector test sessions, in the range of 1 to 604800 seconds.
Usage guidelines
A TWAMP test involves a TWAMP control session and TWAMP test session. One TWAMP test corresponds to one TWAMP test session and multiple TWAMP test sessions can share one TWAMP control session. A TWAMP test session is established based on the UDP protocol.
If a TWAMP test session is inactive for a specified period of time, it will be deleted to release system resources.
Examples
# Specify 600 seconds as the timeout timer for TWAMP reflector test sessions.
<Sysname> system-view
[Sysname] nqa twamp reflector
[Sysname-nqa-twamp-reflctor] test-session timeout 600