AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010 Command Reference
NQA Configuration Commands
adv-factor
Function
The adv-factor command configures an advantage factor for simulated voice calculation in an NQA jitter test.
The undo adv-factor command restores the default setting.
By default, the advantage factor for simulated voice test calculation is 0.
Parameters
| Parameter | Description | Value |
|---|---|---|
| factor-value | Specifies the advantage factor for simulated voice test calculation. | The value is an integer that ranges from 0 to 20. The default value is 0. |
Usage Guidelines
Usage Scenario
On a network bearing VoIP services, a jitter test is used to test VoIP service quality. The adv-factor command is used to configure the advantage factor for voice test calculation to simulate packet jitter generated by actual voice packets.
When calculating the quality parameter R value of the voice transmission network, a test engineer needs to specify an advantage factor according to the transmission distance and media. The value shows the expected compensation for voice quality degradation during network transmission. The user-defined value is determined by the type of the network to be tested. The higher the expected level of service quality degradation, the greater the value. The factor-value parameter shows tolerance over a certain level of voice quality degradation during network transmission.
For example:
- Set the advantage factor to 0 in testing a common wire communication system.
- Set the advantage factor to 20 in testing a multi-hop FR network connected to the satellite.
Prerequisites
The adv-factor command can be used only after the following conditions are met:
- The UDP jitter test is used.
- The code type for the simulated voice test of a jitter test instance has been set using the jitter-codec command. The code types of g711a, g711u, and g729a are applied to the VoIP applications of conversion between simulated voice signals and digital signals.
- The nqa-server udpecho command has been run on the remote device to respond to the jitter test.
Configuration Impact
If the advantage factor has been configured, running the adv-factor command will override the previous configuration.
If the code type is changed after the jitter-codec command is run, the configured advantage factor does not take effect and you need to configure a new advantage factor.
Precautions
The advantage factor of a running test instance cannot be changed.
agetime
Function
The agetime command sets the aging time of an NQA test instance.
The undo agetime command restores the default aging time of an NQA test instance.
The default aging time of an NQA test instance is 0, indicating that the test instance is not aged.
Parameters
| Parameter | Description | Value |
|---|---|---|
| hh:mm:ss | Specifies the aging time. | hh ranges from 0 to 23; mm ranges from 0 to 59; ss ranges from 0 to 59. |
Usage Guidelines
Usage Scenario
To prevent endless running of a test instance, you need to age the test instance periodically. The agetime command can be used to configure the aging time to change the survival time of a test instance in the system.
- The aging time is started when the NQA test instance is in the inactive state. When the aging time expires, the system deletes the NQA test instance automatically.
- The aging time is reset when the NQA test instance is in the active state.
Prerequisites
The type of a test instance has been specified using the test-type command.
Precautions
The aging time of a running test instance cannot be changed.
alarm
Function
The alarm command sets an alarm threshold for the monitored item of an NQA test result.
The undo alarm command deletes an alarm threshold for the monitored item of an NQA test result.
By default, no alarm threshold is configured for the monitored item of an NQA test result.
Format
alarm entry-number { jitter-average | jitter-ds-average | jitter-sd-average | lost-packet-ratio | packet-loss-ds | packet-loss-sd | rtt-average } { absolute | delta } { falling-threshold threshold-value1 event-entry1 | rising-threshold threshold-value2 event-entry2 } * [ description description ]
undo alarm [ entry-number ]
Parameters
| Parameter | Description | Value |
|---|---|---|
| entry-number | Specifies the index of an entry. | The value is an integer that ranges from 1 to 65535. |
| jitter-average | Indicates the average jitter value. This value is available only for jitter test instances. | - |
| jitter-ds-average | Indicates the average jitter value of packets from the destination to the source. This value is available only for jitter test instances. | - |
| jitter-sd-average | Indicates the average jitter value of packets from the source to the destination. This value is available only for jitter test instances. | - |
| lost-packet-ratio | Indicates the packet loss ratio. This value is available for all test instances. | - |
| packet-loss-ds | Indicates the number of lost packets sent from the destination to the source. This value is available only for jitter test instances. | - |
| packet-loss-sd | Indicates the number of lost packets sent from the source to the destination. This value is available only for jitter test instances. | - |
| rtt-average | Indicates the average round trip time (RTT). This value is available for all test instances. | - |
| absolute | Indicates an absolute sampled value, which refers to the sampled value obtained this time. | - |
| delta | Indicates a relative sampled value, which refers to a changed value comparing with the last sampled value | - |
| falling-threshold threshold-value1 | Specifies the lower threshold. | The value is an integer that ranges from 0 to 2147483647. |
| event-entry1 | Specifies the index of the entry corresponding to the lower threshold in the event table. | The value is an integer that ranges from 1 to 65535. |
| rising-threshold threshold-value2 | Specifies the upper threshold. | The value is an integer that ranges from 0 to 2147483647. |
| event-entry2 | Specifies the index of the entry corresponding to the upper threshold in the event table. | The value is an integer that ranges from 1 to 65535. |
| description | Indicates the description of this alarm. | The value is a string of 1 to 127 case-sensitive characters with spaces supported. |
Usage Guidelines
Usage Scenario
If the monitored item of an NQA test result exceeds the threshold, the system sends an alarm to the NMS.
According to the NQA alarm mechanism, an alarm is generated when the monitored item exceeds the threshold only after an alarm threshold and an alarm event are both configured. The system will generate an alarm if the monitored item exceeds the upper or lower threshold configured in the event table. If an incorrect alarm variable is specified, for example, an inexistent OID is specified, no alarm will be generated.
You can run the alarm command to add or delete an alarm entry in the NQA alarm table. If an alarm variable is specified, an alarm is generated when the system becomes abnormal. If the monitored item exceeds the threshold, an alarm is generated.
Prerequisites
An event has been associated with the NQA alarm using the nqa event command. An alarm table is determined by an event table. The entry number in an event table and the event number specified by an alarm must be consistent. Otherwise, if you run the alarm command, the system will display a message indicating that the alarm event does not exist.
The trap function has been enabled for the NQA module using the snmp-agent trap enable feature-name nqa command and the route between the device and NMS is reachable. In this way, NQA alarms can be sent to the network management system (NMS).
Configuration Impact
Ensure that the alarm entry to be entered is unique. If an alarm entry number exists and you enter the same entry number, the new entry number will override the configuration to which the original alarm corresponds.
Example
# Configure alarms to be sent when the packet loss ratio exceeds the threshold.
<Huawei> system-view
[Huawei] nqa event 10 trap
[Huawei] nqa event 100 trap
[Huawei] nqa test-instance admin jitter
[Huawei-nqa-admin-jitter] test-type jitter
[Huawei-nqa-admin-jitter] alarm 10 lost-packet-ratio absolute falling-threshold 10 10 rising-threshold 100 100
clear-records
Usage Guidelines
Clearing statistics on the ongoing test is forbidden.
Before running the command, ensure that the test type specified by the test-type command exists.
community read cipher
Function
The community read cipher command configures the community name for SNMP test.
The undo community command deletes the community name of SNMP test.
By default, the community name for SNMP test is public.
Parameters
| Parameter | Description | Value |
|---|---|---|
| community-name | Specifies the community name for SNMP test. | The value is a string of case-sensitive characters without command line characters such as spaces and question marks. The length ranges from 1 to 32 for plain text and ranges from 32 to 68 for cipher text. |
Usage Guidelines
Usage Scenario
A community, uniquely identified by a community name, defines administrative relationships between NMSs and SNMP agents. The community name acts like a password to regulate access to an SNMP agent. An NMS can access an SNMP agent only if the community name carried in the SNMP request sent by the NMS is the same as the community name configured on the SNMP agent.
When the SNMP versions on agents are SNMPv1 or SNMPv2c, the community name must be configured using the community read cipher command, and the community name must be a read-only community name on SNMP agents. When the SNMP versions on agents are SNMPv3, the community name does not need to be configured because SNMPv3 does not support community names.
Prerequisites
The NQA test instance has been configured using the nqa command, and the test instance type has been set to SNMP using the test-type command.
datafill
Function
The datafill command configures pad characters in an NQA test instance.
The undo datafill command deletes the pad characters in an NQA test instance.
By default, there are no padding characters in an NQA test instance.
Parameters
| Parameter | Description | Value |
|---|---|---|
| fillstring | Specifies the pad characters for NQA test packets. | The value is a string of 1 to 230 case-sensitive characters with spaces supported. The question mark (?) is not supported. The default value is 0 (an empty pad character). |
Usage Guidelines
Usage Scenario
In an NQA test, you need to simulate actual datagrams to obtain more accurate statistics. The datasize command can be used to set the size of the Data field. To differentiate packets sent from different test instances, add the specified characters to identify the test packets.
Prerequisites
The type of a test instance has been specified using the test-type command. The type can be one of the following:
- UDP
- Jitter
- ICMP
- Trace
- LSP Ping
Configuration Impact
After the datafill command is run, the following situations may occur:
If the length of the data packet sent from the test instance is shorter than the configured pad character, only the forepart of the pad character can be used.
If the length of the data packet sent from the test instance is larger than the configured pad character, the pad character is repeated in sequence until the data packet is successfully padded.
For example, the pad character is set to abcd. If the length of the test packet is 3, only abc is used to pad the test packet. If the length of the test packet is 6, abcdab is used to pad the test packet.
Precautions
The pad character of a running test instance cannot be changed.
datasize
Function
The datasize command sets the size of the NQA test packet.
The undo datasize command restores the size of the NQA test packet.
The default size is 0, which indicates that the test packet does not carry data information.
Parameters
| Parameter | Description | Value |
|---|---|---|
| size | Specifies the size of the NQA test packet. |
The value is an integer that ranges from 0 to 8100, in bytes. If the configured size of a packet is smaller than the default size of a packet, the configured size is invalid and the packet is forwarded based on its default size. NOTE:
When you run the hardware-based enable command for a Jitter test instance, the value ranges from
0 to 1472, in bytes. |
Usage Guidelines
Usage Scenario
You can run the datasize command to set the size of the data field of a test packet. This ensures that the size of the test packet is closer to the size of the actual data packet and the obtained statistics are more accurate.
For example, if a UDP jitter test instance is used to detect voice over IP (VoIP) services, you can run the datasize command to set the size of the NQA test packet to the same size as the actual voice packet. This enables a simulation of the actual traffic that occurs in a period of time.
To simulate a voice data flow with the transmission rate of 64 kbit/s, you can set the size of the voice packet to 172 bytes (160-byte payload + 12-byte RTP header + 28-byte IP header and UDP header) and set the interval for sending the voice packet to 20 ms. In this manner, 3000 packets can be sent in one minute.
Prerequisites
The test type has been specified using the test-type command.
The datasize command is applicable only to the ICMP, UDP, trace, LSP ping, and jitter test instances.
Precautions
You cannot change the size of the running test packets.
description (NQA view)
Function
The description command configures description of an NQA test instance.
The undo description command deletes the description of an NQA test instance.
By default, no description is configured for an NQA test instance.
Parameters
| Parameter | Description | Value |
|---|---|---|
| string | Specifies the description of an NQA test instance. | The value is a string of 1 to 230 case-sensitive characters with spaces. |
Usage Guidelines
Usage Scenario
The description command can be used to briefly describe the test instance to help maintenance. Generally, the test item or the test objective of a test instance is described.
Prerequisites
The type of a test instance has been specified using the test-type command.
Configuration Impact
If the description of a test instance has been configured, running the description command will override the previous configuration.
Precautions
The description of a running test instance cannot be changed.
destination-address
Function
The destination-address command specifies the destination address of an NQA test instance.
The undo destination-address command deletes the destination address of an NQA test instance.
By default, destination address is not configured for an NQA test instance.
Format
destination-address { ipv4 ipv4-address [ lsp-masklen masklen [ lsp-loopback loopback-address ] [ vpn-frr-path ] | lsp-loopback loopback-address [ lsp-masklen masklen ] [ vpn-frr-path ] | vpn-frr-path ] | ipv6 ipv6-address | url urlstring }
destination-address mac mac-address
undo destination-address
Parameters
| Parameter | Description | Value |
|---|---|---|
| ipv4 ipv4-address | Specifies an IPv4 destination address. | The IPv4 address is in dotted decimal notation. |
| lsp-masklen masklen | Specifies the mask length of an LSP's IPv4 address prefix. | The value is an integer that ranges from 0 to 32. |
| lsp-loopback loopback-address | Specifies a 127/8 IP address in the MPLS echo request packet header. | - |
| vpn-frr-path | Indicates that the connectivity of the backup VPN FRR LSP will be checked. | - |
| ipv6 ipv6-address | Specifies an IPv6 destination address. | The value is a 32-digit hexadecimal number, in the format X:X:X:X:X:X:X:X. |
| url urlstring | Specifies a destination URL address. | The value is a string of 1 to 230 case-insensitive characters without spaces. When quotation marks are used around the string, spaces are allowed in the string. |
| mac mac-address | Indicates the unicast MAC address. | A MAC address in the format of H-H-H. Each H stands for one to four hexadecimal characters. |
Usage Guidelines
Usage Scenario
You can run the destination-address command to specify the destination address of an NQA test instance.
Precautions
- The Label Switched Path (LSP) parameters can be configured only for the LSP test instances.
- You cannot configure destination IP address for DHCP test instances.
- You can specify the destination address as a URL address only for the HTTP, trace, and DNS test instances.
- The destination addresses of DNS test instances must be URL addresses but cannot be IPv4 addresses, and the destination URL addresses must contain dots (.); otherwise, the test may fail.
- You cannot change the destination address of a running test instance.
destination-port
Function
The destination-port command configures the destination port number for an NQA test.
The undo destination-port command restores the default setting.
By default, no destination port number is specified for an NQA test.
display ip nqa-compatible responder statistics
Function
The display ip nqa-compatible responder statistics command displays statistics on the NQA handshake packets sent from the third-party device or NMS software.
Usage Guidelines
Usage Scenario
When a device works with a third-party device or NMS software to perform UDP-Echo or UDP-Jitter packets, this command displays statistics about NQA handshake packets sent from the third-party device or NMS software.
Prerequisites
The device is configured to respond to the UDP tests initiated by the third-party device or NMS software.
Example
# Display statistics on NQA handshake packets sent from the third-party device or NMS software.
<Huawei> display ip nqa-compatible responder statistics
IP NQA-COMPATIBLEs Responder is: Enabled
Number of control message received:4
Recent success sources:
Number of successes:2
SIP DIP Sport Dport Tos Time
-------------------------------------------------------------------------------
10.10.10.26 10.10.10.14 30000 40000 36 [21:13:02.028 UTC 20 06 2013]
10.10.10.26 10.10.10.14 30000 40000 36 [21:13:12.008 UTC 20 06 2013]
Recent fail sources:
Fail reason: IP,PortNum or Tos matching failure.
Number of failures:2
SIP DIP Sport Dport Tos Time
-------------------------------------------------------------------------------
10.10.10.28 10.10.10.14 30001 40001 38 [21:13:06.358 UTC 20 06 2013]
10.10.10.28 10.10.10.14 30001 40001 38 [21:13:11.368 UTC 20 06 2013]
Item |
Description |
|---|---|
IP NQA-COMPATIBLEs Responder is |
Whether the device is enabled to respond to UDP-Echo or UDP-Jitter packets sent by the third-party device or NMS software. |
Number of control message received |
Number of received handshake packets. |
Recent success sources |
The third-party packets that are successfully received. |
Number of successes |
Number of packets that are successfully received. |
SIP |
Source IP address of packets. |
DIP |
Destination IP address of packets. |
Sport |
Source port of packets. |
Dport |
Destination port of packets. |
Tos |
Packet priority. |
| Time |
Packet receiving time. |
Recent fail sources |
The third-party packets that are failed to be received. |
Fail reason |
Reason of packet receiving failure. |
Number of failures |
Number of packets that are failed to be received. |
display nqa application
Function
The display nqa application command displays the type of the NQA test instance that corresponds to the service.
Usage Guidelines
You need to choose a proper NQA test instance type based on the service to be tested. You can run the display nqa application command to view the type of the NQA test instance that corresponds to the service.
Example
# Display the type of the NQA test instance corresponding to the service.
<Huawei> display nqa application
Application: The area that you test.
Subclasss : The subclass of application.
NQA type : The type of NQA test-instance.
Application Subclass NQA type
______________________________________________________________________________
internet --- http
ftp
dns
dhcp
streaming media --- jitter
network performance --- jitter
trouble-shooting application http
ftp
dns
dhcp
snmp
network udp
tcp
icmp
trace
link
mpls lspping
lsptrace
display nqa alarm
Parameters
| Parameter | Description | Value |
|---|---|---|
| test-instance admin-name | Specifies the administrator of an NQA test instance. | The value is a string of 1 to 32 characters. |
| test-name | Specifies the name of an NQA test instance. | The value is a string of 1 to 32 characters. |
Usage Guidelines
You can run the display nqa alarm command to display current alarms of a specified test instance or all test instances.
Example
# Display alarms of a single NQA test instance.
<Huawei> display nqa alarm test-instance admin jitter
NQA Alarm Information: ------------------------------------------------------------------- Admin-Name Operation-Tag Alarm-Entry AlarmType Event-Entry ------------------------------------------------------------------- admin jitter 10 Rising 10 admin jitter 10 Falling 10
display nqa-alarm
Function
The display nqa-alarm command displays the maximum number of NQA alarms that the system allows and the number of current NQA alarms.
Usage Guidelines
After you run the display nqa-alarm command, the maximum number of NQA alarms that the system allows and the number of current NQA alarms are displayed.
Example
# Display the number of NQA alarms.
<Huawei> system-view
[Huawei] nqa test-instance user test
[Huawei-nqa-user-test] display nqa-alarm
NQA alarm information: ------------------------------------------------------ NQA Alarm Max: 5 NQA Alarm Number: 0 ------------------------------------------------------
display nqa event
Parameters
| Parameter | Description | Value |
|---|---|---|
| event-entry | Specifies the index of the entry that is associated with the alarm in the event table. If this parameter is not specified, all events associated with alarms are displayed. | The value is an integer that ranges from 1 to 65535. |
Usage Guidelines
You can run the display nqa event command to view the event associated with the NQA alarm.
Example
# Display event 10.
<Huawei> display nqa event 10
NQA Event Information: ----------------------------------------------------------------------------- Event-Entry Event-type Description Admin-Name Operation-Tag ----------------------------------------------------------------------------- 10 linkage None admin icmp
display nqa-event
Function
The display nqa-event command displays the maximum number of NQA events that the system allows and the number of configured NQA events.
Usage Guidelines
The display nqa-event command displays the maximum number of NQA events that the system allows and the number of NQA events that have been configured.
display nqa-group
Parameters
| Parameter | Description | Value |
|---|---|---|
| group-name | Specifies the name of an NQA group. | The value is a string of 1 to 32 case-sensitive characters without spaces or question marks. If the character string is quoted by double quotation marks, the character string can contain spaces and question marks. |
Usage Guidelines
To view NQA group status, run the display nqa-group command. By viewing NQA group status, you can know whether the probe of an NQA group is successful and the probe result of each NQA test instance, facilitating fault location.
If the group-name parameter is not specified, status of all NQA groups is displayed.
Example
# View NQA group status.
<Huawei> display nqa-group
NQA-group information:
--------------------------------------------------------------------------------
NQA-group group1
Admin-name Test-name State
NQA admin1 test1 NA
NQA admin2 test2 NA
NQA admin3 test3 NA
NQA-group group2
Admin-name Test-name State
NQA admin4 test4 NA
NQA admin5 test5 NA
--------------------------------------------------------------------------------
Item |
Description |
|---|---|
NQA-group |
Name of an NQA group. |
Admin-name |
Administrator of an NQA test instance. |
Test-name |
Name of an NQA test instance. |
State |
NQA group status:
|
NQA |
NQA test instance information, including the administrator, name, and status of an NQA test instance. |
display nqa history
Format
display nqa history [ test-instance admin-name test-name ] [ from start-date start-time to end-date end-time ]
Parameters
Usage Guidelines
Usage Scenario
NQA provides NQA test instances to test network operation conditions, to export statistics, and to effectively cut costs. NQA measures the performance of different protocols running on the network.
The display nqa history command helps you understand the network status by displaying the operation statistics about each test packet, including the status and round-trip delay.
No history record about the failed jitter test instances exist.
To filter out information about failed tests in a historical table related to ICMP test instances, run the records history-filter failures command before viewing historical statistics.
Precautions
If no optional parameter is specified, all history records of an NQA test instance are displayed.
When NQA test result table and historical table are displayed in a split screen, latest results are displayed to improve user experience.
Example
# Display the history records about an NQA test.
<Huawei> display nqa history
NQA entry(admin, ftp) history:
Index T/H/P Response Status Address Time
1 1/1/1 1157ms success 10.2.1.2 2012-07-15 10:16:38.188
2 2/1/1 3000ms timeout UnKnow 2012-07-15 10:18:2.922
NQA entry(admin, http) history:
Index T/H/P Response Status Address Time
1 1/1/1 0ms busy UnKnow 2012-07-15 11:16:39.915
2 1/1/2 0ms busy UnKnow 2012-07-15 11:16:39.978
3 1/1/3 0ms busy UnKnow 2012-07-15 11:16:39.40
Item |
Description |
|---|---|
NQA entry(admin, ftp) |
NQA test items:
|
Index |
Index of a test record. |
T/H/P |
|
Response |
Period from the time when a probe packet is sent to the time when a response packet is received. |
Status |
Probe status:
|
Address |
Destination IP address of an NQA test instance. |
Time |
Time when the response packet is received. |
display nqa-parameter
Usage Guidelines
You can run the display nqa-parameter command to view parameters available for the current NQA test instance.
Differences between the display nqa-parameter and display this commands are as follows:
- The display this command is used to display commands that have been configured for the test instance. It shows the configuration records.
- The display nqa-parameter command is used to display parameters available for the current NQA test instance and prompt which parameter is mandatory for the start of the test instance. Before running the display nqa-parameter command, ensure that the type of the test instance is configured.
Example
# Display parameters available for the NQA test instance in the NQA view.
<Huawei> system-view
[Huawei] nqa test-instance admin icmp
[Huawei-nqa-admin-icmp] test-type icmp
[Huawei-nqa-admin-icmp] description huawei nqa
[Huawei-nqa-admin-icmp] destination-address ipv4 10.1.1.1
[Huawei-nqa-admin-icmp] timeout 5
[Huawei-nqa-admin-icmp] display nqa-parameter
*: the parameter must be configured before starting the test-instance.
#: the parameter is undecided.
<blank>: the parameter is optional.
*test-type :icmp
description :huawei nqa
frequency :
timeout :5(default:3)
threshold rtd :
*destination-address type :ipv4
*destination-address :10.1.1.1
source-address type :
source-address :
ttl :---(default:30)
datasize :
datafill :
source-interface :
sendpacket passroute :---(default:no)
probe-count :---(default:3)
send-trap :---(default:none)
test-failtimes :---(default:1)
tos :---(default:0)
fail-percent :---(default:100)
interval :---(default:4000)
vpn-instance :
records history :---(default:50)
records result :---(default:5)
records history-filter :---(default:all)
agetime :---(default:0:0:0)
ip-forwarding :---(default:no)
nexthop-address type :
nexthop-address :
Item |
Description |
|---|---|
test-type |
Type of the NQA test instance, which is set using the test-type command. |
description |
Description of the NQA test instance, which is configured using the description command. |
frequency |
Interval at which the NQA test instance is automatically performed, which is set using the frequency command. |
timeout |
timeout period for a probe of an NQA test instance, which is set using the timeout command. |
threshold rtd |
RTD of the NQA test instance, which is set using the threshold command. |
destination-address type |
Destination IP address type of the NQA test instance, which is set using the destination-address command. |
destination-address |
Destination IP address of the NQA test instance, which is set using the destination-address command. |
source-address type |
Source IP address type of the NQA test instance, which is set using the source-address command. |
source-address |
Source IP address of the NQA test instance, which is set using the source-address command. |
ttl |
TTL of the NQA test packet, which is set using the ttl command. |
datasize |
Size of the NQA test packet, which is set using the datasize command. |
datafill |
Pad characters in the NQA test packet, which is set using the datafill command. |
source-interface |
Source interface of the NQA test instance, which is set using the source-interface command. |
sendpacket passroute |
Whether the test instance is configured to send packets without searching the routing table, which is set using the sendpacket passroute command. |
probe-count |
Number of probes for the NQA test instance, which is set using the probe-count command. |
send-trap |
Conditions for sending traps for the NQA test instance, which are configured using the send-trap command. |
test-failtimes |
Number of continuous test failures in the NQA test instance, which is set using the test-failtimes command. |
tos |
Type of service (TOS) of the test package in the NQA test instance, which is set using the tos command. |
fail-percent |
Percentage of failed NQA test instances, which is set using the fail-percent command. |
interval |
Interval for sending NQA test packets, which is set using the interval command. |
vpn-instance |
VPN instance name of the NQA test instance, which is set using the vpn-instance command. |
records history |
Maximum number of history records allowed for the NQA test instance, which is set using the records command. |
records result |
Maximum number of test result records allowed for the NQA test instance, which is set using the records command. |
records history-filter |
Filtering records from a historical table for an NQA test instance, referring to the records history-filter command. |
agetime |
Aging time of the NQA test instance, which is set using the agetime command. |
ip-forwarding |
Forwarding IP packets forcibly, which is set using the ip-forwarding command. |
nexthop-address type |
The type of the next hop address, which is set using the nexthop command. |
nexthop-address |
The next hop address, which is set using the nexthop command. |
display nqa results
Format
display nqa results [ collection | success | failed ] [ test-instance admin-name test-name ] [ verbose ]
Parameters
| Parameter | Description | Value |
|---|---|---|
| collection | Indicates the total NQA test results. | - |
| success | Indicates the results of successful tests. | - |
| failed | Indicates the results of failed tests. | - |
| test-instance | Indicates an NQA test instance. | - |
| admin-name | Specifies the name of the administrator for an NQA test instance. | The value must be the name of an existing NQA test instance administrator. |
| test-name | Specifies the name of an NQA test instance. | The value must be the name of an existing NQA test instance. |
| verbose | Displays detailed information. | - |
Usage Guidelines
Usage Scenario
NQA test results cannot be displayed automatically on the terminal. To view NQA test results, run the display nqa results command.
If no test instance is specified, the test result of the test instance is displayed in the corresponding test instance view, and the test result of all test instances is displayed in the system view or other views irrelevant to test instances. If a test instance is specified, the test result of only this test instance is displayed.
The display nqa results command displays the results of a test instance that has been complete.
Universal test results: This part does not vary according to the test instance type.
Detailed statistics of each test: Statistics items in this part vary according to the test instance type.
The display nqa results collection command is used to display the statistics on accumulative results. At present, only the jitter test supports the query of accumulated results.
Precautions
If no optional parameter is specified, all NQA test results are displayed.
- If the value of SendProbe is 0, no test packet has been sent, and Packet Loss Ratio is displayed as 100% (default value).
- If the value of SendProbe is not 0 and the value of Packet Loss Ratio is 100%, all test packets have been lost.
- If the value of SendProbe is 0, no test packet has been sent in these tests, and Packet Loss Ratio is displayed as 0% (default value).
- If the value of SendProbe is not 0 but the value of Packet Loss Ratio is 0%, no test packet has been lost.
Formula used to calculate the accumulative packet loss ratio: Accumulative packet loss ratio = (Accumulative number of sent packets – Accumulative number of received packets)/Accumulative number of sent packets x 100%. If the value of SendProbe in the results of a single test is 0, it is not considered during the calculation of the accumulative packet loss ratio.
Example
# Display the results of an NQA ICMP test.
<Huawei> display nqa results test-instance admin icmp
NQA entry(admin, icmp) :testflag is inactive ,testtype is icmp 1 . Test 1 result The test is finished Send operation times: 3 Receive response times: 3 Completion:success RTD OverThresholds number: 0 Attempts number:1 Drop operation number:0 Disconnect operation number:0 Operation timeout number:0 System busy operation number:0 Connection fail number:0 Operation sequence errors number:0 RTT Status errors number:0 Destination ip address:10.138.77.21 Min/Max/Average Completion Time: 2/2/2 Sum/Square-Sum Completion Time: 6/12 Last Good Probe Time: 2012-07-02 17:09:18.1 Lost packet ratio: 0 %
Item |
Description |
|---|---|
NQA entry(admin, icmp) |
NQA test items:
|
testflag |
Test flag.
|
testtype |
Test type. |
1 . Test 1 result |
Sequence number of test results. Test results are numbered based on the time when the tests are complete. |
The test is finished |
Test status:
|
Send operation times |
Number of sent packets. |
Receive response times |
Number of received response packets. |
Completion |
Completing status of the test:
|
RTD OverThresholds number |
Number of times that the round-trip delay (RTD) threshold is exceeded. |
Attempts number |
Test times. |
Drop operation number |
Number of system resource allocation failures. |
Disconnect operation number |
Number of forcible disconnections. |
Operation timeout number |
Number of timeout operations during the test. |
System busy operation number |
Number of conflict operations. |
Connection fail number |
Number of times that the local end fails to establish connections with the peer. |
Operation sequence errors number |
Number of received disordered packets. |
RTT Status errors number |
Number of RTT status errors. |
Destination ip address |
Destination IP address of the test. |
Min/Max/Average Completion Time |
Minimum/Maximum/Average time taken to complete the test. |
Sum/Square-Sum Completion Time |
Sum and square sum of the time taken to complete the test. |
Last Good Probe Time |
Time at which the last probe is complete. |
Lost packet ratio |
Packet loss ratio. |
# Display the result of an NQA jitter test.
<Huawei> display nqa results test-instance admin jitter
NQA entry(admin, jitter) :testflag is inactive ,testtype is jitter 1 . Test 1 result The test is finished SendProbe:60 ResponseProbe:0 Completion:failed RTD OverThresholds number:0 OWD OverThresholds SD number:0 OWD OverThresholds DS number:0 Min/Max/Avg/Sum RTT:0/0/0/0 RTT Square Sum:0 NumOfRTT:0 Drop operation number:0 Operation sequence errors number:0 RTT Stats errors number:0 System busy operation number:0 Operation timeout number:60 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 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 Square Sum:0 Negative DS Square Sum:0 Min Delay SD:0 Min Delay DS:0 Avg Delay SD:0 Avg Delay DS:0 Max Delay SD:0 Max Delay DS:0 Delay SD Square Sum:0 Delay DS Square Sum:0 Packet Loss SD:0 Packet Loss DS:0 Packet Loss Unknown:0 Average of Jitter:0 Average of Jitter SD:0 Average of Jitter DS:0 Jitter out value:0.0000000 Jitter in value:0.0000000 NumberOfOWD:0 Packet Loss Ratio: 100% OWD SD Sum:0 OWD DS Sum:0 ICPIF value: 0 MOS-CQ value: 0 TimeStamp unit: ms Packet Rewrite Number: 0 Packet Rewrite Ratio: 0% Packet Disorder Number: 0 Packet Disorder Ratio: 0% Fragment-disorder Number: 0 Fragment-disorder Ratio: 0% Jitter OverThresholds SD number:0 Jitter OverThresholds DS number:0 OverallOverThresholds number:0 Start time: 2014-06-25 18:47:05+08:00 End time: 2014-06-25 18:47:05+08:00
Item |
Description |
|---|---|
NQA entry(admin, jitter) |
NQA test items:
|
testflag |
Test flag:
|
testtype |
Test type. |
SendProbe |
Number of sent probes. |
ResponseProbe |
Number of received response probes. |
Completion |
Completing status of the test:
|
RTD OverThresholds number |
Number of times that the RTD threshold is exceeded. |
OWD OverThresholds SD number |
Number of times that the one-way delay (OWD) threshold (from the source to the destination) is exceeded. |
OWD OverThresholds DS number |
Number of times that the OWD threshold (from the destination to the source) is exceeded. |
Min/Max/Avg/Sum RTT |
Minimum/Maximum/Average/Sum of the RTT. |
RTT Square Sum |
RTT square sum of the probes. |
NumOfRTT |
Number of RTTs. |
Drop operation number |
Number of system resource allocation failures. |
Operation sequence errors number |
Serial number of the error packets received by the client. |
RTT Stats errors number |
Number of RTT status errors. |
System busy operation number |
Number of conflict operations. |
Operation timeout number |
Number of timeout operations during the test. |
Min Positive SD |
Minimum positive jitter from the source to the destination. |
Min Positive DS |
Minimum positive jitter from the destination to the source. |
Max Positive SD |
Maximum positive jitter from the source to the destination. |
Max Positive DS |
Maximum positive jitter from the destination to the source. |
Positive SD Number |
Number of the positive jitter from the source to the destination. |
Positive DS Number |
Number of the positive jitter from the destination to the source. |
Positive SD Sum |
Sum of the positive jitter from the source to the destination. |
Positive DS Sum |
Sum of the positive jitter from the destination to the source. |
Positive SD Square Sum |
Square sum of the positive jitter from the source to the destination. |
Positive DS Square Sum |
Square sum of the positive jitter from the destination to the source. |
Min Negative SD |
Minimum negative jitter from the source to the destination. |
Min Negative DS |
Minimum negative jitter from the destination to the source. |
Max Negative SD |
Maximum negative jitter from the source to the destination. |
Max Negative DS |
Maximum negative jitter from the destination to the source. |
Negative SD Number |
Number of the negative jitter from the source to the destination. |
Negative DS Number |
Number of the negative jitter from the destination to the source. |
Negative SD Sum |
Sum of the negative jitter from the source to the destination. |
Negative DS Sum |
Sum of the negative jitter from the destination to the source. |
Negative SD Square Sum |
Square sum of the negative jitter from the source to the destination. |
Negative DS Square Sum |
Square sum of the negative jitter from the destination to the source. |
| Min Delay SD | Minimum delay from the source to the destination. |
| Min Delay DS | Minimum delay from the destination to the source. |
| Avg Delay SD | Average delay from the source to the destination. |
| Avg Delay DS | Average delay from the destination to the source. |
Max Delay SD |
Maximum delay from the source to the destination. |
Max Delay DS |
Maximum delay from the destination to the source. |
| Delay SD Square Sum | Square sum of the delay jitter from the source to the destination. |
| Delay DS Square Sum | Square sum of the delay jitter from the destination to the source. |
Packet Loss SD |
Maximum number of lost packets from the source to the destination. |
Packet Loss DS |
Maximum number of lost packets from the destination to the source. |
Packet Loss Unknown |
Number of packets lost at an unknown direction. |
Average of Jitter |
Average jitter. |
Average of Jitter SD |
Average jitter from the source to the destination. |
Average of Jitter DS |
Average jitter from the destination to the source. |
Jitter out value |
Jitter in sending packets. |
Jitter in value |
Jitter in receiving packets. |
NumberOfOWD |
Number of OWD packets. |
Packet Loss Ratio |
Packet loss ratio. |
OWD SD Sum |
Sum of OWD from the source to the destination. |
OWD DS Sum |
Sum of OWD from the destination to the source. |
MOS-CQ value |
Average estimate of VoIP performance. |
ICPIF value |
Advantage factor. |
TimeStamp unit |
Unit of the timestamp. |
Packet Rewrite Number |
Number of rewritten packets. |
Packet Rewrite Ratio |
Percentage of rewritten packets to total packets. |
Packet Disorder Number |
Number of out-of-order packets. |
Packet Disorder Ratio |
Percentage of out-of-order packets to total packets. |
Fragment-disorder Ratio |
Percentage of out-of-order fragmented packets to total packets. |
| Jitter OverThresholds SD number | Number of times that a test instance is successfully performed with the jitter exceeding the specified threshold from the source to the destination. |
| Jitter OverThresholds DS number | Number of times that a test instance is successfully performed with the jitter exceeding the specified threshold from the destination to the source. |
| OverallOverThresholds number | Number of times that a test instance is successfully performed with any of the delays from the source to the destination or from the destination to the source, the bi-directional delay, the jitters from the source to the destination or from the destination to the source exceeding the set threshold. |
# Display the statistics on the total NQA test results after the packet rewrite check function is configured.
<Huawei> display nqa results collection
NQA entry(admin, jitter) :testtype is jitter 1 . Test 1 collect result SendProbe:60 ResponseProbe:47 Completion:1 RTD OverThresholds number:0 OWD OverThresholds SD number:0 OWD OverThresholds DS number:0 Min/Max/Avg/Sum RTT:30/1130/296/13910 RTT Square Sum:10840100 NumOfRTT:47 Drop operation number:0 Operation sequence errors number:0 RTT Stats errors number:0 System busy operation number:0 Operation timeout number:13 Min Positive SD:10 Min Positive DS:10 Max Positive SD:260 Max Positive DS:160 Positive SD Number:9 Positive DS Number:4 Positive SD Sum:690 Positive DS Sum:230 Positive SD Square Sum:122900 Positive DS Square Sum:27700 Min Negative SD:20 Min Negative DS:30 Max Negative SD:60 Max Negative DS:290 Negative SD Number:31 Negative DS Number:5 Negative SD Sum:1010 Negative DS Sum:530 Negative SD Square Sum:34300 Negative DS Square Sum:105100 Min Delay SD:15 Min Delay DS:14 Avg Delay SD:147 Avg Delay DS:146 Max Delay SD:565 Max Delay DS:564 Delay SD Square Sum:2710025 Delay DS Square Sum:2696162 Packet Loss SD:0 Packet Loss DS:0 Packet Loss Unknown:0 Average of Jitter:50 Average of Jitter SD:42 Average of Jitter DS:84 Jitter out value:0.0000000 Jitter in value:0.0000000 NumberOfOWD:47 Packet Loss Ratio: 21% OWD SD Sum:6955 OWD DS Sum:6908 ICPIF value: 0 MOS-CQ value: 0 TimeStamp unit: ms Packet Rewrite Number: 0 Packet Rewrite Ratio: 0% Packet Disorder Number: 0 Packet Disorder Ratio: 0% Fragment-disorder Number: 0 Fragment-disorder Ratio: 0% Jitter OverThresholds SD number:0 Jitter OverThresholds DS number:0 OverallOverThresholds number:0
Item |
Description |
|---|---|
SendProbe |
Number of sent probes. |
ResponseProbe |
Number of received response probes. |
Completion |
Number of times that the test is performed. |
RTD OverThresholds number |
Number of times that the RTD threshold is exceeded. |
OWD OverThresholds SD number |
Number of times that the OWD threshold (from the source to the destination) is exceeded. |
OWD OverThresholds DS number |
Number of times that the OWD threshold (from the destination to the source) is exceeded. |
Min/Max/Avg/Sum RTT |
Minimum/Maximum/Average/Sum of the RTT. |
RTT Square Sum |
RTT square sum of the probes. |
NumOfRTT |
Number of RTTs. |
Drop operation number |
Number of system resource allocation failures. |
Operation sequence errors number |
Serial number of the error packets received by the client. |
RTT Stats errors number |
Number of RTT status errors. |
System busy operation number |
Number of conflict operations. |
Operation timeout number |
Number of timeout operations during the test. |
Min Positive SD |
Minimum positive jitter from the source to the destination. |
Min Positive DS |
Minimum positive jitter from the destination to the source. |
Max Positive SD |
Maximum positive jitter from the source to the destination. |
Max Positive DS |
Maximum positive jitter from the destination to the source. |
Positive SD Number |
Number of the positive jitter from the source to the destination. |
Positive DS Number |
Number of the positive jitter from the destination to the source. |
Positive SD Sum |
Sum of the positive jitter from the source to the destination. |
Positive DS Sum |
Sum of the positive jitter from the destination to the source. |
Positive SD Square Sum |
Square sum of the positive jitter from the source to the destination. |
Positive DS Square Sum |
Square sum of the positive jitter from the destination to the source. |
Min Negative SD |
Minimum negative jitter from the source to the destination. |
Min Negative DS |
Minimum negative jitter from the destination to the source. |
Max Negative SD |
Maximum negative jitter from the source to the destination. |
Max Negative DS |
Maximum negative jitter from the destination to the source. |
Negative SD Number |
Number of the negative jitter from the source to the destination. |
Negative DS Number |
Number of the negative jitter from the destination to the source. |
Negative SD Sum |
Sum of the negative jitter from the source to the destination. |
Negative DS Sum |
Sum of the negative jitter from the destination to the source. |
Negative SD Square Sum |
Square sum of the negative jitter from the source to the destination. |
Negative DS Square Sum |
Square sum of the negative jitter from the destination to the source. |
| Min Delay SD | Minimum delay from the source to the destination. |
| Min Delay DS | Minimum delay from the destination to the source. |
| Avg Delay SD | Average delay from the source to the destination. |
| Avg Delay DS | Average delay from the destination to the source. |
Max Delay SD |
Maximum delay from the source to the destination. |
Max Delay DS |
Maximum delay from the destination to the source. |
| Delay SD Square Sum | Square sum of the delay jitter from the source to the destination. |
| Delay DS Square Sum | Square sum of the delay jitter from the destination to the source. |
Packet Loss SD |
Maximum number of lost packets from the source to the destination. |
Packet Loss DS |
Maximum number of lost packets from the destination to the source. |
Packet Loss Unknown |
Number of packets lost at an unknown direction. |
Average of Jitter |
Average jitter. |
Average of Jitter SD |
Average jitter from the source to the destination. |
Average of Jitter DS |
Average jitter from the destination to the source. |
Jitter out value |
Jitter in sending packets. |
Jitter in value |
Jitter in receiving packets. |
NumberOfOWD |
Number of OWD packets. |
Packet Loss Ratio |
Packet loss ratio. |
OWD SD Sum |
Sum of OWD from the source to the destination. |
OWD DS Sum |
Sum of OWD from the destination to the source. |
MOS-CQ value |
Average estimate of VoIP performance. |
ICPIF value |
Advantage factor. |
TimeStamp unit |
Unit of the timestamp. |
display nqa support-server-type
Example
# Display the server types supported by NQA.
<Huawei> display nqa support-server-type
NQA support server type information:
----------------------------------------------------
Type Description
tcp server NQA TCP server
udp server NQA UDP server
rtp server NQA RTP server
----------------------------------------------------
display nqa support-test-type
Function
The display nqa support-test-type command displays the test instance types supported by NQA.
Usage Guidelines
You can run the display nqa support-test-type command to view all test instances supported by the device.
- If the display nqa support-test-type command is run on the NQA server, the test instances supported by the server are displayed.
- If the display nqa support-test-type command is run on the NQA client, the test instances supported by the client are displayed.
Example
# Display the test instance types supported by NQA.
<Huawei> display nqa support-test-type
NQA support test type information:
----------------------------------------------------
Type Description
tcp TCP type NQA test
udp UDP type NQA test
http HTTP type NQA test
ftp FTP type NQA test
jitter JITTER type NQA test
icmp ICMP type NQA test
snmp SNMP type NQA test
trace TRACE type NQA test
lspping LSPPING type NQA test
lsptrace LSPTRACE type NQA test
dns DNS type NQA test
dhcp DHCP type NQA test
----------------------------------------------------
display nqa-agent
Parameters
| Parameter | Description | Value |
|---|---|---|
| admin-name | Specifies the administrator of an NQA test instance. | The value is a string of 1 to 32 characters. |
| test-name | Specifies the name of an NQA test instance. | The value is a string of 1 to 32 characters. |
| verbose | Indicates detailed information about the client status of an NQA test. | - |
Example
# Display the client status of an NQA test.
<Huawei> display nqa-agent
NQA Tests Max:256 NQA Tests Number: 1
NQA Flow Max:256 NQA Flow Remained:256
nqa test-instance admin icmp
test-type icmp
destination-address ipv4 192.168.1.2
Item |
Description |
|---|---|
NQA Tests Max |
Maximum number of supported NQA test instances. |
NQA Tests Number |
Number of current NQA test instances. |
NQA Flow Max |
Maximum number of concurrent NQA test instances. |
NQA Flow Remained |
Maximum number of concurrent and performable NQA test instances. |
test-type |
Test type. |
destination-address |
destination address of a test. |
display nqa-ftp-record configuration
Function
The display nqa-ftp-record configuration command displays the configuration of NQA test result sent to the FTP server using FTP.
Usage Guidelines
To check the configuration of NQA test result upload to the FTP server through FTP, run the display nqa-ftp-record configuration command.
Example
# Display the configuration of NQA test result sending to the FTP server using FTP.
<Huawei> display nqa-ftp-record configuration ---------------NQA FTP SAVE RECORD CONFIGURATION--------------- FUNCTION: ENABLE TRAP: ENABLE IP-ADDRESS:10.1.2.8 SOURCE-ADDRESS:10.1.2.1 VPN-INSTANCE: USERNAME:ftp PASSWORD: FILENAME:icmp ITEM-NUM:100000 TIME:60 DATETIMETYPE:UTC LAST FINISHED FILENAME:icmp20131214-163628.txt
Item |
Description |
|---|---|
FUNCTION |
Whether enable the NQA test results to be sent to the FTP
server using FTP.
To set this field, run the nqa-ftp-record enable command. |
TRAP |
Whether send a trap when the NQA test result is saved to
the FTP server using FTP.
To set this field, run the nqa-ftp-record trap-enable command. |
IP-ADDRESS |
FTP server address. To set this field, run the nqa-ftp-record ip-address command. |
SOURCE-ADDRESS |
FTP client address. To set this field, run the nqa-ftp-record source-address command. |
VPN-INSTANCE |
VPN instance name. |
USERNAME |
User name for logging in to the FTP server. To set this field, run the nqa-ftp-record username command. |
PASSWORD |
Password for logging in to the FTP server. To set this field, run the nqa-ftp-record password command. |
FILENAME |
Name of a file created at the FTP server. To set this field, run the nqa-ftp-record filename command. |
ITEM-NUM |
Number of NQA test results that are saved to a file using FTP. To set this field, run the nqa-ftp-record item-num command. |
TIME |
Duration of saving NQA test results to a file using FTP. To set this field, run the nqa-ftp-record time command. |
DATETIMETYPE |
Type of time based on which test results are saved to a
file on the FTP server:
To set this field, run the nqa upload statistics datetime-type command. |
LAST FINISHED FILENAME |
Name of a file created at the FTP server last time. |
display nqa-server
Usage Guidelines
- In the case of a TCP test instance, the nqa-server tcpconnect command needs to be run to enable a TCP server.
- In the case of a jitter or a UDP test instance, the nqa-server udpecho command needs to be run to enable a UDP server.
Example
# Display the information about NQA servers.
<Huawei> display nqa-server
NQA Server Max: 128 NQA Server Num: 1
NQA Concurrent TCP Server: 0 NQA Concurrent UDP Server: 1
NQA Concurrent RTP-UDP Server: 0
nqa-server udpecho 10.1.1.1 6000 ACTIVE Hardware-based
Item |
Description |
|---|---|
NQA Server Max |
Maximum number of NQA servers that can be configured. |
NQA Server Num |
Number of current NQA servers. |
NQA Concurrent TCP Server |
Number of the configured TCP servers. |
NQA Concurrent UDP Server |
Number of the configured UDP servers. |
NQA Concurrent RTP-UDP Server |
Number of the configured RTP-UDP servers. |
nqa-server |
Running servers. |
ACTIVE |
Status of the NQA server. |
display nqa-server session
Function
The display nqa-server session command displays the NQA client information on the NQA server.
Usage Guidelines
Usage Scenario
After the nqa-server session-record enable command is executed on the NQA server to enable NQA client information display, run the display nqa-server session command to view information about all NQA clients connected to the NQA server. The NQA client information includes the IP address of NQA server, IP address of NQA client, source port of NQA client, and VPN.
Precautions
This command is valid for only hardware-based UDP jitter test.
Example
# Display NQA client information on the NQA server.
<Huawei> display nqa-server session Total NQA Jitter items = 2 -------------------------------------------------------------- Server-IP Client-IP Client-Port VPN-INSTANCE -------------------------------------------------------------- 192.168.0.1 192.168.0.255 63081 192.168.0.1 192.168.0.255 53779 --------------------------------------------------------------
Item |
Description |
|---|---|
Total NQA Jitter items |
Number of UDP jitter test instances. |
Server-IP |
IP address of the NQA server. |
Client-IP |
IP address of the NQA client. |
Client-Port |
Source port of the NQA client. |
VPN-INSTANCE |
VPN instance that the server belongs to. |
display snmp-agent trap feature-name nqa all
Function
The display snmp-agent trap feature-name nqa all command displays the status of all traps of the NQA module.
Example
# Display the status of all traps of the NQA module.
<Huawei> display snmp-agent trap feature-name nqa all
------------------------------------------------------------------------------
Feature name: NQA
Trap number : 29
------------------------------------------------------------------------------
Trap name Default switch status Current switch status
nqaResultsProbeFailed on on
nqaHTTPStatsProbeFailed on on
pingProbeFailed on on
nqaFTPStatsProbeFailed on on
pingTestFailed on on
pingTestCompleted on on
traceRouteTestFailed on on
traceRouteTestCompleted on on
nqaResultsTestFailed on on
nqaResultsTestCompleted on on
nqaResultsThresholdNotification
on on
nqaHTTPStatsTestFailed on on
nqaHTTPStatsTestCompleted on on
nqaHTTPStatsThresholdNotification
on on
nqaFTPStatsTestFailed on on
nqaFTPStatsTestCompleted on on
nqaFTPStatsThresholdNotification
on on
nqaJitterStatsTestFailed on on
nqaJitterStatsTestCompleted on on
nqaJitterStatsRTDThresholdNotification
on on
nqaJitterStatsOWDThresholdNotificationSD
on on
nqaJitterStatsOWDThresholdNotificationDS
on on
nqaRisingAlarmNotification on on
nqaFaillingAlarmNotification on on
nqaFtpSaveRecordNotification on on
nqaJitterStatsJitterThresholdNotificationSD
on on
nqaJitterStatsJitterThresholdNotificationDS
on on
nqaReflectorStateChangeNotification
on on
nqaResultsTestResultChange on on
Item |
Description |
|---|---|
Feature name |
Name of the module that a trap belongs to. |
Trap number |
Number of traps. |
Trap name |
Name of a trap. |
Default switch status |
Default status of the trap function:
|
Current switch status |
Status of the trap function:
|
dns-server
Function
The dns-server command configures the IP address of the domain name service (DNS) server in the NQA test.
The undo dns-server command deletes the configured IP address of the DNS server.
By default, the IP address of the DNS server is not configured.
Parameters
| Parameter | Description | Value |
|---|---|---|
| ipv4 ip-address | Specifies an IPv4 address for the DNS server. | The value is in dotted decimal notation. |
Usage Guidelines
Usage Scenario
Before using a DNS test instance to detect the rate of resolving a given DNS name to an IP address, configure a DNS server first.
Prerequisites
The type of a test instance has been specified using the test-type command. The test instance can only be a DNS or HTTP test instance.
Precautions
The DNS server configuration of a running test instance cannot be changed.
fail-percent
Function
The fail-percent command sets the failure percentage for the NQA test instance.
The undo fail-percent command deletes the configured failure percentage for the NQA test instance.
By default, the failure percentage is 100%. That is, the test is regarded as a failure only when all the probes fail.
Parameters
| Parameter | Description | Value |
|---|---|---|
| percent | Specifies the percentage of failed probes. | The value is an integer that ranges from 1 to 100. |
Usage Guidelines
Usage Scenario
In an NQA test instance, multiple probes are sent to test probe packets. Statistics obtained from multiple probe tests show the network quality.
In actual scenarios, however, a probe test may fail because of interference in the network. In addition, a failure in a probe test does not mean that the NQA test fails. The fail-percent command can be used to set failure percentage to check whether an NQA test fails or not. If the number of failure probe packets to the total number of probe packets reaches a specified percentage, the NQA test is considered as a failure.
- If the failure percentage is set to 80, the probe test is considered a success.
- If the failure percentage is set to 60, the probe test is considered a failure.
Prerequisites
The type of a test instance has been specified using the test-type command. The failure percentage cannot be set for an FTP, a trace, a LSP Trace, and a DNS test instance.
Precautions
The failure percentage of a running test instance cannot be changed.
forwarding-simulation inbound-interface
Function
The forwarding-simulation inbound-interface command configures a simulated inbound interface.
The undo forwarding-simulation inbound-interface command deletes a simulated inbound interface.
By default, no simulated inbound interfaces are configured.
Format
forwarding-simulation inbound-interface interface-type interface-number
undo forwarding-simulation inbound-interface
Parameters
| Parameter | Description | Value |
|---|---|---|
| interface-type interface-number | Specifies the type and number of a simulated inbound interface. | – |
Usage Guidelines
Usage Scenario
By default, NQA test packets are regarded as host packets. The host packets are processed differently with the forwarded packets in that the former is preferably forwarded.
The forwarding-simulation inbound-interface command configures a simulated interface through which the NQA test packets, same as the forwarded packets, are forwarded to the product forwarding channel.
In a generalflow test instance, to allow the initiator and reflector to support the lossless mode, run the forwarding-simulation inbound-interface interface-type interface-number command. This allows the initiator and reflector interfaces to transmit both RFC 2544 and non-RFC 2544 traffic.Prerequisites
Before configuring a DHCP test instance, configure a DHCP server or DHCP Relay, and ensure reachable routes between the DHCP client and the DHCP server or the DHCP Relay.
Precautions
The type of the test instance must be DHCP test instances.
In the DHCP test instance case, source-interface interface-type interface-number command and forwarding-simulation inbound-interface interface-type interface-number command are mutually exclusive. In addition, the DHCP client and NQA DHCP test instance cannot be configured on the same device. Otherwise, the NQA DHCP test instance may fail.
frequency
Function
The frequency command sets the interval at which an NQA test instance is automatically performed.
The undo frequency command deletes the configured interval at which an NQA test instance is automatically performed.
By default, the interval at which an NQA test instance is automatically performed is not configured. That is, the test is performed for one time.
Parameters
| Parameter | Description | Value |
|---|---|---|
| interval | Specifies the interval at which an NQA test instance is automatically performed. | The value is an integer that ranges from 1 to 604800, in seconds. |
Usage Guidelines
Usage Scenario
You can run the start command to set the start time and end time of an NQA test. If you need to perform period test from the start time to the end time in a test instance, run the frequency command to set the interval at which an NQA test instance is automatically performed. After that, the NQA test is automatically performed one time at each configured interval.
Configuring the interval of periodic NQA test avoid time-consuming manual operations.
Prerequisites
The type of a test instance has been specified using the test-type command.
Precautions
In the DHCP, DNS, FTP, HTTP, or Trace test instance, the frequency value must be larger than the product of timeout and probe-count.
In the ICMP, SNMP, TCP, or UDP test instance, the frequency value must be larger than the product of intervaland probe-count.
In the Jitter test instance:
frequency > probe-count × jitter-packetnum × interval + timeout
In the hardware-based Jitter test instance:
frequency > probe-count × jitter-packetnum × interval + 6200 + (5 × timeout/3)
The unit of 6200 is ms.
may be returned if the following condition is true: Interval at which the NQA test is automatically performed ≤ (Number of sent packets -1) x Interval + Timeout period + 1. For a test instance with jitter-packetnum configured, the number of sent packets is Probe-count x jitter-packetnum.
For trace and LSP trace test instances, the interval must be larger than or equal to 60 seconds.
If no end time is configured, the test cannot stop automatically. You need to stop it manually. The frequency of a running test instance cannot be changed.
ftp-filename
Function
The ftp-filename command configures the file name and file path for an NQA FTP test instance.
The undo ftp-filename command deletes the file name and file path for an NQA FTP test instance.
By default, no file name and file path are configured.
Parameters
| Parameter | Description | Value |
|---|---|---|
| file-name | Specifies the name and path of the operation file in an FTP test instance. | The value is a string of 1 to 230 characters. |
Usage Guidelines
The ftp-filename command is valid only for FTP test instances.
You cannot change the file path and file name of a running test instance.
If no file path is specified, the system searches for the file in the current path.
The file name cannot end with any forward slashes (/) or backward slashes (\).
The file name includes but is not limited to the extension name, such as .txt.
Various FTP servers may support files with the file name in different length ranges. Before you configure this command, ensure that the target FTP server supports the length of the specified file name. Otherwise, NQA test results may fail to be transmitted using FTP.
ftp-filesize
Function
The ftp-filesize command sets the size of the file used in an NQA FTP test instance.
The undo ftp-filesize command restores the default size of the file used in an NQA FTP test instance.
By default, the size of the file used in the FTP test is 1000 Kbytes.
Parameters
| Parameter | Description | Value |
|---|---|---|
| size | Specifies the size of the file used in the FTP test. | The value is an integer that ranges from 1 to 10000, in Kbytes. |
Usage Guidelines
You cannot change the configured size of the file when the test is running.
If specifying the size of the upload file is adopted, the FTP client automatically generates the file name nqa-ftp-test.txt. If the test is performed several times, the newly uploaded file replaces the previous one.
The type of the test instance has been set to ftp using the test-type command.
ftp-operation
Function
The ftp-operation command sets the operation mode for an NQA FTP test instance.
The undo ftp-operation command restores the default operation mode of an NQA FTP test instance.
By default, the operation mode of an FTP test instance is get.
Parameters
| Parameter | Description | Value |
|---|---|---|
| get | Indicates that the client downloads a file from the server and the download speed is recorded. | - |
| put | Indicates that the client uploads a local file or a created file to the server and the upload speed is recorded. | - |
Usage Guidelines
Usage Scenario
In the FTP download test, the local device functions as an FTP client to download/upload the specified file from/to the FTP server. Statistics about each FTP phase are displayed, including the time to set up an FTP control connection and the time to transmit data.
The ftp-operation command can be used to specify the FTP operation mode as put or get. A connection with the FTP server is set up using the IP address, the user name, and the password of the FTP server, and the time to set up FTP connection is recorded.
Prerequisites
The type of the test instance has been set to ftp using the test-type command.
Precautions
The operation mode of a running test instance cannot be changed.
ftp-password
Function
The ftp-password command sets a password for logging in to the FTP server in an NQA FTP test instance.
The undo ftp-password command deletes the configured password for logging in to the FTP server.
By default, no password is set for FTP test instances.
Parameters
| Parameter | Description | Value |
|---|---|---|
| password | Specifies the password for logging in to the FTP server in an FTP test instance. | The value is a string of 1 to 32 or 32 to 68 case-sensitive characters without spaces.
NOTE:
When quotation marks are used around the string, spaces are allowed in the string. |
| cipher cipher-password | Specifies the password for logging in to the FTP server in an FTP test instance. | The value is a string of 1 to 32 or 32 to 68case-sensitive characters without spaces.
NOTE:
When quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
In the FTP test, the local device functions as an FTP client to download/upload the specified file from/to the FTP server. Statistics about each FTP phase are displayed, including the time to set up an FTP control connection and the time to transmit data.
To ensure test security and prevent unauthorized users from accessing the network, you need to enable identity authentication. The ftp-password command can be used to set the specified user and password. Only the user who enters the authorized user name and password is authorized to access the network.
Prerequisites
The type of the test instance has been set to ftp using the test-type command.
Precautions
The password of a running test instance cannot be changed.
ftp-username
Function
The ftp-username command sets the user name for logging in to the FTP server in an FTP test instance.
The undo ftp-username command deletes the configured user name for logging in to the FTP server.
By default, no user name is set for FTP test instances.
Parameters
| Parameter | Description | Value |
|---|---|---|
| name | Specifies the user name for logging in to the FTP server. | The value is a string of 1 to 255 case-sensitive characters without
spaces. NOTE:
When quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
In the FTP test, the local device functions as an FTP client to download/upload the specified file from/to the FTP server. Statistics about each FTP phase are displayed, including the time to set up an FTP control connection and the time to transmit data.
To ensure test security and prevent unauthorized users from accessing the network, you need to enable identity authentication. The ftp-username command can be used to set the specified user in an FTP test. Only the user who enters the authorized user name and password is authorized to access the network.
Prerequisites
The type of the test instance has been set to ftp using the test-type command.
Precautions
The user name of a running test instance cannot be changed.
hardware-based enable
Function
The hardware-based enable command enables the hardware forwarding engine on the LPU to send packets and add timestamps to the packets during the jitter test.
The undo hardware-based command disables the hardware forwarding engine on the LPU from sending packets and adding timestamps to the packets during the jitter test.
By default, the hardware forwarding engine on the LPU is not enabled to send packets and add timestamps to the packets.
Usage Guidelines
The hardware-based enable command can only be used in the jitter test to enable the hardware forwarding engine on the LPU to send packets and add timestamps to the packets.
After the hardware-based enable command is configured, the sendpacket passroute can be configured, but does not take effect.
http-operation
http-url
Function
The http-url command configures the uniform resource locator (URL) and version information for an HTTP test instance.
The undo http-url command deletes the configured URL and version information.
By default, no URL or version information is configured for an HTTP test instance.
Parameters
| Parameter | Description | Value |
|---|---|---|
| deststring | Specifies the name of the web page used for an HTTP test. | The value is a string of 1 to 230 case-insensitive characters without spaces. NOTE:
When quotation marks are used around the string, spaces are allowed in the string. |
| verstring | Specifies the HTTP version. | It can be set to v1.0 or 1.1. The default HTTP version is v1.0. |
icmp-jitter-mode
Function
The icmp-jitter-mode command sets the type of ICMP jitter test instance.
The undo icmp-jitter-mode command restores the default type of ICMP jitter test instance.
By default, the ICMP jitter test type is icmp-timestamp.
Parameters
| Parameter | Description | Value |
|---|---|---|
| icmp-echo | Configures the ICMP jitter test instance to use ICMP echo packets. | - |
| icmp-timestamp | Configures the ICMP jitter test instance to use ICMP timestamp packets. | - |
Usage Guidelines
If the remote device does not support icmp-timestamp or requires ICMP echo packets, configure icmp-echo.
interval (NQA view)
Function
The interval command sets the interval at which NQA test packets are sent.
The undo interval command restores the default setting.
The interval is 20 milliseconds for a jitter test instance.
The interval is 4 seconds for other test instances.
Parameters
| Parameter | Description | Value |
|---|---|---|
| milliseconds interval | Sets the interval at which packets are sent, in milliseconds. NOTE:
If the configured interval is a multiple of 1000 milliseconds,
the system will automatically convert milliseconds into seconds. |
The value is an integer that ranges from 10 to 60000. |
| seconds interval | Sets the interval at which packets are sent, in seconds. | The value is an integer that ranges from 1 to 60, in seconds. |
Usage Guidelines
Usage Scenario
In an NQA test instance, multiple probes are sent. Statistics obtained from multiple probe tests show the network quality. Probe packets (or probes) are sent at a specified interval.
- If the network quality is poor, the interval at which packets are sent must be increased. Otherwise, the network performance may deteriorate.
- If the network quality is good, the interval at which are sent can be decreased to shorten the waiting time.
Prerequisites
The type of a test instance has been specified using the test-type command. The interval command is valid only for the jitter, ICMP, SNMP, LSP Ping, TCP, and UDP test instances.
Configuration Impact
- If the configured interval is a multiple of 1000 milliseconds, the system will automatically convert milliseconds into seconds.
- Packets can be sent at interval of milliseconds only in jitter test instances. The interval at which packets are sent must be greater than the timeout period set using the timeout command in all test instances except the jitter test instance.
- If the interval for sending packets has been configured, running the interval command will override the previous configuration.
Precautions
- The interval for sending packets of a running test instance cannot be changed.
- The interval for sending UDP jitter test packets must be less than 1 second.
ip nqa-compatible responder enable
Function
The ip nqa-compatible responder enable command enables the device to respond to UDP-Echo or UDP-Jitter packets sent by a third-party device or NMS software.
The undo ip nqa-compatible responder enable command disables the device from responding to UDP-Echo or UDP-Jitter packets sent by a third-party device or NMS software.
By default, the device is disabled from responding to UDP-Echo or UDP-Jitter packets sent by a third-party device or NMS software.
Format
ip nqa-compatible responder [ vpn-instance vpn-instance-name ] enable
undo ip nqa-compatible responder [ vpn-instance vpn-instance-name ] enable
Parameters
| Parameter | Description | Value |
|---|---|---|
| vpn-instance vpn-instance-name | Specifies the VPN instance of the third-party device or NMS software. | The VPN instance has been created on the device. |
ip nqa-compatible auto
Function
The ip nqa-compatible auto command configures the device to respond to UDP-Echo or UDP-Jitter packets sent from a third-party device or NMS software.
The undo ip nqa-compatible auto command configures the device not to respond to UDP-Echo or UDP-Jitter packets sent from a third-party device or NMS software.
By default, the device does not respond to UDP-Echo or UDP-Jitter packets sent from a third-party device or NMS software.
Usage Guidelines
Usage Scenario
When the device works with a third-party device or software to perform UDP-Echo or UDP-Jitter tests, this command allows the device to respond to UDP-Echo or UDP-Jitter packets sent from the third-party device or NMS software.
Prerequisites
The ip nqa-compatible responder enable command has been executed in the device view to enable the capability to respond to the UDP-Echo or UDP-Jitter packets sent from the a third-party device or NMS software.
Precautions
If the ip nqa-compatible udp command has been configured, the ip nqa-compatible auto command does not take effect. Run the undo ip nqa-compatible udp first.
ip nqa-compatible udp
Function
The ip nqa-compatible udp command configures the IP address, port number, and service type of the response to the UDP-Echo or UDP-Jitter packets sent by a third-party device or NMS software.
The undo ip nqa-compatible udp command deletes the IP address, port number, and service type of the response to the UDP-Echo or UDP-Jitter packets sent by a third-party device or NMS software.
By default, the IP address, port number, and service type of the response to the UDP-Echo or UDP-Jitter packets sent by a third-party device or NMS software are not configured.
Format
ip nqa-compatible { device | network-management } udp ip-address [ vpn-instance vpn-instance-name ] port-number [ tos-value ]
undo ip nqa-compatible { device | network-management } udp ip-address [ vpn-instance vpn-instance-name ] port-number [ tos-value ]
Parameters
| Parameter | Description | Value |
|---|---|---|
| device | Specifies a third-party device. | - |
| network-management | Specifies a third-party NMS software. | - |
| ip-address | Specifies the IP address of the third-party device or NMS software. | The value is in dotted decimal notation. |
| vpn-instance vpn-instance-name | Specifies the VPN instance of the third-party device or NMS software. | The VPN instance has been created on the device. |
| port-number | Specifies the port number of the third-party device or NMS software. | The value is an integer that ranges from 0 to 65535. |
| tos-value | Specifies the service type of the third-party device or NMS software. | The value is an integer that ranges from 0 to 255. |
Usage Guidelines
Usage Scenario
When the device connects to the third-party device or NMS software and needs to respond to the UDP-Echo or UDP-Jitter packets sent by the third-party device or NMS software, run this command to specify the IP address, port number, and service type of the response. This command helps improving the accuracy and security of NQA tests.
Prerequisites
The ip nqa-compatible responder [ vpn-instance vpn-instance-name ] enable command has been executed in the system view to enable the device to respond to the UDP-Echo or UDP-Jitter packets sent by the third-party device or NMS software.
Precaution
If the configured port number is 7, 13, or 19, run the undo anti-attack udp-flood enable command to disable UDP Flood attack defense before running the ip nqa-compatible udp command. Otherwise, the device discards UDP-Echo or UDP-Jitter packets. If the configured port number is occupied by another process, the ip nqa-compatible udp command fails to take effect.
If the ip nqa-compatible auto command has been configured, the ip nqa-compatible udp command does not take effect. Run the undo ip nqa-compatible auto first.
ip-forwarding
Function
The ip-forwarding command configures packets to be forcibly forwarded using IP on the first node.
The undo ip-forwarding command disables packets from being forcibly forwarded using IP on the first node.
Usage Guidelines
When a fault occurs on the network, you can first run the ping command to check network connectivity. On an MPLS network, if a fault occurs but the control layer fails to detect the fault, the ping operation fails. To fast identify whether the fault occurs on the MPLS network or on the IP network, you can configure IP packets to be forcibly forwarded using IP on the first node. This can help you fast locate the fault.
Currently, only NQA ICMP test instances support this configuration.
jitter-codec
Function
The jitter-codec command configures a code type for an NQA jitter simulated voice test.
The undo jitter-codec command deletes the configured code type of an NQA jitter simulated voice test.
By default, an NQA jitter test is not a simulated voice test.
Parameters
| Parameter | Description | Value |
|---|---|---|
| g711a | Sets the code type of a simulated voice test to g711alaw. The transmission rate of g711alaw is 64 kbit/s. | - |
| g711u | Sets the code type of a simulated voice test to g711ulaw. The transmission rate of g711ulaw is 64 kbit/s. | - |
| g729a | Sets the code type of a simulated voice test to g729a. The transmission rate of g729a is 8 kbit/s. | - |
Usage Guidelines
Usage Scenario
The jitter-codec command can be used to configure the code types of conversion between simulated voice signals and digital signals to detect VoIP services in jitter test instances. You can specify different code types for VoIP services in actual situations.
The differences between g711a, g711u, and g729a of a jitter test instance are as follows:
| Code Type | Length of Data Area | Number of the Sent Packets | Interval at Which Packets Are Sent |
|---|---|---|---|
| g711a | 172 bytes | 1000 | 20 ms |
| g711u | 172 bytes | 1000 | 20 ms |
| g729a | 32 bytes | 1000 | 20 ms |
After configuring the code type, run the adv-factor command to configure an advantage factor to simulate the jitter of actual voice packets.
After configuring the jitter-codec and adv-factor commands in a jitter test instance, you can adjust test packets to simulate the sending of VoIP traffic. This simulation helps to detect VoIP network and analyze service traffic.
Prerequisites
- The actual code types of the VoIP services to be tested have been set to the same.
- The test instance type has been set to jitter using the test-type jitter command.
- The remote device has been enabled to respond to the jitter test using the nqa-server udpecho command.
Configuration Impact
- If a code type has been configured, running the jitter-codec command will override the previous configuration.
- If a code type is changed, the configured advantage factor does not take effect and you need to configure a new advantage factor.
Precautions
The code type of a running test instance cannot be changed.
jitter-packetnum
Function
The jitter-packetnum command sets the number of packets sent in each probe test instance.
The undo jitter-packetnum command restores the default number of packets sent in each probe test instance.
By default, 20 test packets are sent in each probe.
Parameters
| Parameter | Description | Value |
|---|---|---|
| number | Specifies the number of test packets sent in each probe in the jitter test (probe-count). | The value is an integer that ranges from 1 to 3000. The default value is 20. |
Usage Guidelines
Usage Scenario
In an NQA test instance, the jitter-packetnum command can be used to set the number of consecutive packets to simulate the actual traffic of a data in a specified period of time. This helps simulate services more accurately.
For example, the jitter-packetnum command can be used to set the number of consecutive packets to 3000 and an interval of 20 ms to send packets. In this way, G.711 traffic can be simulated within one minute to detect VoIP services in UDP jitter test instances.
Prerequisites
The type of a test instance has been specified using the test-type command. The number of sent packets can be configured only for jitter test instances.
Configuration Impact
In jitter test instances, the number of sent packets = jitter-packetnum x probe-count, but the product cannot exceed 3000.
If the number of probe packets has been set, running the jitter-packetnum command will override the previous configuration.
Precautions
The number of probe packets of a running test instance cannot be changed.
lsp-exp
Function
The lsp-exp command configures the LSP EXP value of MPLS Echo Request packets in an NQA test instance.
Using the undo lsp-exp command, you can restore the default setting.
By default, LSP EXP is 0.
Parameters
| Parameter | Description | Value |
|---|---|---|
| exp | Specifies the LSP EXP value of an NQA test instance. |
The value is an integer that ranges from 0 to 7. The default value is 0. |
Usage Guidelines
Usage Scenario
The AR100&AR120&AR150&160&200 does not support the lsp-exp command.
The MPLS experimental bits (EXP) field is a 3-bit field in the MPLS header used to mark the precedence of MPLS packets.
- Congestion on the link can be avoided.
- Specified queue can be detected.
Precautions
This command applies to only the LSP test.
You cannot change the configured LSP EXP value when the test is performed.
lsp-path full-display
Function
Using the lsp-path full-display command, you can view all devices, including Ps, along an LSP in the NQA test result.
Using the undo lsp-path full-display command, you can view all devices, except for Ps, along an LSP in the NQA test result.
By default, you can view only PEs, not Ps, along an LSP in the NQA test result.
Usage Guidelines
The lsp-path full-display command can be used to display all devices, including Ps, along an LSP in the NQA test result. At present, this command is available only for VPLS PW trace test instances.
After the lsp-path full-display command is run, you can view all devices, including Ps, along an LSP in the result of a VPLS PW trace test instance. Otherwise, you can view only PEs along an LSP.
lsp-nexthop
Function
The lsp-nexthop command is used to configure the IP address of the next hop in the case that load balancing is enabled.
Using the undo lsp-nexthop command, you can cancel the current setting.
By default, the next-hop IP address of any link that participates in load balancing.
Parameters
| Parameter | Description | Value |
|---|---|---|
| nexthop-ip-address | Specifies the next hop address. | It is in dotted decimal notation. |
Usage Guidelines
Usage Scenario
The AR100&AR120&AR150&160&200 does not support the lsp-nexthop command.
- lsp-type is IPv4
- lsp-version is RFC4379
- LSP Ping
- LSP Trace
Precautions
A running test instance cannot be configured with the next hop address.
Example
# Specify the next hop address for the LSP Ping test instance whose LSP type is IPv4 and lsp-version is rfc4379.
<Huawei> system-view [Huawei] nqa test-instance user test [Huawei-nqa-user-test] test-type lspping [Huawei-nqa-user-test] lsp-type ipv4 [Huawei-nqa-user-test] lsp-version rfc4379 [Huawei-nqa-user-test] lsp-nexthop 10.1.2.20
lsp-replymode
Function
Using the lsp-replymode command, you can set the reply mode for the LSP test.
Using the undo lsp-replymode command, you can restore the default setting.
By default, UDP packets are used.
Format
lsp-replymode { no-reply | udp | udp-via-vpls | udp-router-alert | level-control-channel }
undo lsp-replymode
Parameters
| Parameter | Description | Value |
|---|---|---|
| no-reply | Indicates that the LSP test is not responded. | If the no-reply parameter is specified in the command, the destination does not respond to NQA probe packets. This configuration is used to collect the statistics on or process received probe packets on the destination host, and no response packets need to be sent. The NQA test instance fails because the client does not receive response packets. |
| udp | Indicates that IPv4 UDP packets are used to respond to the LSP test. | - |
| udp-via-vpls | Indicates that VPLS UDP packets are used to respond to the LSP test. | - |
| udp-router-alert | Indicates that VPLS UDP packets are used to respond to the LSP test. | - |
| level-control-channel | Indicates that the reply packets are sent through the application-level control channel. | - |
Usage Guidelines
Usage Scenario
The AR100&AR120&AR150&160&200 does not support the lsp-replymode command.
- LSP Ping
- LSP Trace
Precautions
lsp-replymode no-reply indicates the unidirectional test. If the client displays timeout, it indicates that the test succeeds.
You cannot change the reply mode of the currently performed LSP test.
lsp-tetunnel
Function
The lsp-tetunnel command configures the TE tunnel used in an NQA LSP test.
The undo lsp-tetunnel command deletes the configured TE tunnel.
By default, no TE tunnel is configured for an LSP test instance.
Parameters
| Parameter | Description | Value |
|---|---|---|
| tunnel interface-number | Specifies the tunnel interface number. | - |
| hot-standby | Indicates the hot-standby tunnel of the TE tunnel. | - |
| primary | Indicates the primary tunnel of the TE tunnel. | - |
Usage Guidelines
Prerequisites
The AR100&AR120&AR150&160&200 does not support the lsp-tetunnel command.
Before using the lsp-tetunnel command to configure the TE tunnel in an NQA LSP test instance, run the lsp-type te command to specify the NQA LSP test type to TE.
You cannot change the TE tunnel when the LSP test is performed.
Example
# Configure the TE tunnel of the test named user test.
<Huawei> system-view
[Huawei] interface tunnel 0/0/1
[Huawei-Tunnel0/0/1] quit
[Huawei] nqa test-instance user test
[Huawei-nqa-user-test] test-type lspping
[Huawei-nqa-user-test] lsp-type te
[Huawei-nqa-user-test] lsp-tetunnel tunnel 0/0/1
<Huawei> system-view [Huawei] interface tunnel 0/0/1 [Huawei-Tunnel0/0/1] quit [Huawei] nqa test-instance user test [Huawei-nqa-user-test] test-type lspping [Huawei-nqa-user-test] lsp-type te [Huawei-nqa-user-test] lsp-tetunnel tunnel 0/0/1 hot-standby
lsp-type
Function
Using the lsp-type command, you can configure the LSP test type.
Using the undo lsp-type command, you can cancel configuring the LSP test type.
By the default, the value of lsp-type is ipv4.
Parameters
| Parameter | Description | Value |
|---|---|---|
| ipv4 | Sets the test type to Ipv4 LSP ping/trace. | - |
| te | Sets the type to LSP ping/trace of the TE tunnel. | - |
| ipv4-vpn | Sets the LSP test type to IPv4 L3VPN. |
- |
Usage Guidelines
Usage Scenario
The AR100&AR120&AR150&160&200 does not support the lsp-type command.
The lsp-type command can be used to configure the LSP test type of an NQA test instance to detect an LDP or a TE tunnel.
- If ipv4 is configured, the NQA test instance is used to detect the connectivity of a specified LDP LSP. The destination address of the test instance is configured using the destination-address command.
- If te is configured, the NQA test instance is used to detect the connectivity of a specified TE tunnel. The destination address of the test instance is configured using the lsp-tetunnel command.
- If the ipv4-vpn parameter is set, the NQA test case is used to test LSPs on a BGP-based
L3VPN network.
- To test a primary LSP on a BGP-based L3VPN network, specify the destination address using the destination-address lsp-masklen masklen command.
- To test a primary LSP on a BGP-based L3VPN network, specify the destination address using the destination-address lsp-masklen masklen vpn-frr-path command.
Prerequisites
- If the LSP test type is set to IPv4, the NQA test instance type must be set to LSP ping or LSP trace.
- If the LSP test type is set to TE, the NQA test instance type must be set to LSP ping or LSP trace.
- If the LSP test type is set to IPv4 L3VPN, the NQA test instance type must be set to LSP ping.
Precautions
The type of an LSP test that is running cannot be changed.
lsp-version
Function
Using the lsp-version command, you can configure the protocol that is used by the LSP test instance.
Using the undo lsp-version command, you can restore the default setting.
By default, draft6 is adopted.
Parameters
| Parameter | Description | Value |
|---|---|---|
| rfc4379 | Indicates that the protocol defined in RFC 4379 is adopted. | - |
| draft6 | Indicates that Draft-ietf-mpls-lsp-ping-06 is adopted. | - |
| ptn-mode | Indicates that trace VC packets are replied in a multi-segment PW scenario. |
- |
Usage Guidelines
Usage Scenario
The AR100&AR120&AR150&AR160&200 does not support the lsp-version command.
The lsp-version command can be used to specify the protocol that is used by the LSP test instance.
Prerequisites
If draft6 or rfc4379 is specified in the lsp-version command, specify lspping or lsptrace in the test-type command.
nexthop
Function
The nexthop configures a next hop address for NQA test packets.
The undo nexthop deletes the configured next hop address for the NQA test packets.
By default, the next hop address for the NQA test packets is obtained by searching the routing table.
Parameters
| Parameter | Description | Value |
|---|---|---|
| ipv4 ip-address | Specifies a next hop address for NQA test packets. |
The value is in dotted decimal notation. NOTE:
The specified next hop must be the physical interface directly connected to the device that sends the NQA test packets. |
Usage Guidelines
Usage Scenario
In the scenario that an NQA test instance is associated with static routes, if a link becomes faulty, the NQA test instance detects this fault and then the static routes associated with the NQA test instance become Down. After the link recovers, the NQA test instance attempts to send ICMP test packets over the static routes. Because these static routes are still Down, the NQA test instance still fails to detect link connectivity. Traffic fails to be forwarded.
The nexthop command configures a next hop address for the NQA test packets, which ensures that the packets are forwarded when the link recovers from the fault, and the static routes associated with the NQA test instance are Up.
Prerequisites
Only the NQA ICMP test instance allows you to specify a next hop address for NQA test packets.
Precautions
If the next hop address is allocated dynamically using DHCP, the source-interface command must be run to specify the outbound interface.
In this case, the test must meet the following conditions. Otherwise, the test fails.
- The specified next hop address matches the outbound interface.
- The specified outbound interface cannot be the member interface of a logical interface.
nqa
Function
The nqa command creates an NQA test instance and enters the NQA view.
The undo nqa command deletes an NQA test instance.
Format
nqa test-instance admin-name test-name
undo nqa { test-instance admin-name test-name | all-test-instance }
Parameters
| Parameter | Description | Value |
|---|---|---|
| admin-name | Specifies the administrator of an NQA test instance. | The value is a string of 1 to 32 case-sensitive characters, excluding question marks (?), en dashes (-), a single or consecutive quotation marks ("). |
| test-name | Specifies the name of an NQA test instance. | The value is a string of 1 to 32 case-sensitive characters, excluding question marks (?), en dashes (-), a single or consecutive quotation marks ("). |
| all-test-instance | Specifies all NQA test instances. | - |
Usage Guidelines
Usage Scenario
The NQA is an integrated network test function. NQA test instances can accurately detect network running status, collect test statistics, and reduce costs.
NQA measures the performance of different protocols running on the network. NQA allows enterprise users to collect network operation indexes in real time, such as total delay of the HTTP, TCP connection delay, DNS resolution delay, file transmission delay, FTP connection delay, and DNS resolution error ratio.
To check these performance indexes, you can create NQA test instances. The two ends of an NQA test are called the NQA client and NQA server. The NQA client is responsible for initiating an NQA test. After receiving packets, the NQA server sends response messages to the NQA client. You can learn about the running status of a corresponding network according to the returned packets.
Configuration Impact
After the undo nqa all-test-instance command is run, all NQA test instances including the running test instance will be deleted. In this scenario, you cannot perform any operation on each test instance.
Precautions
The undo nqa test-instance admin-name test-name command cannot delete a running NQA test instance.
The undo nqa all-test-instance command deletes all NQA test instances (including the running test instances).
nqa (NQA group view)
Function
The nqa command adds the specified NQA test instance to an NQA group.
The undo nqa command deletes the specified NQA test instance from an NQA group.
Parameters
| Parameter | Description | Value |
|---|---|---|
| admin-name | Specifies the administrator of an NQA test instance. | The value is a string of 1 to 32 case-sensitive characters, excluding question marks (?), en dashes (-), a single or consecutive quotation marks ("). |
| test-name | Specifies the name of an NQA test instance. | The value is a string of 1 to 32 case-sensitive characters, excluding question marks (?), en dashes (-), a single or consecutive quotation marks ("). |
Usage Guidelines
Usage Scenario
To add the specified NQA test instance to an NQA group, run the nqa (NQA group view) command. When an NQA group contains multiple NQA test instances, you can monitor multiple links at the same time by managing this NQA group.
The detection of an NQA group succeeds when at least one NQA test instance in the group succeeds. If no NQA test instance in an NQA group succeeds, the detection of this NQA group fails.
Precautions
If you delete an NQA test instance that belongs to an NQA group, this test instance is also deleted from this group.
nqa event
Function
The nqa event command associates an event with the NQA alarm.
The undo nqa event command deletes the configured event.
By default, no event is associated with the NQA alarm.
Format
nqa event event-entry { log | trap | log-trap | linkage admin-name test-name | none } [ description ]
undo nqa event [ event-entry ]
Parameters
| Parameter | Description | Value |
|---|---|---|
| event-entry | Specifies the index of the entry in the event table. | The value is an integer that ranges from 1 to 65535. |
| log | Records a log for the event. | - |
| trap | Sends a trap to the NMS. | - |
| log-trap | Records a log and sends a trap to the NMS for the event. | - |
| linkage | Triggers a linkage test instance for the event. | - |
| admin-name | Specifies the administrator of the linkage test instance. | It is a string of 1 to 32 characters, spaces not supported. When quotation marks are used around the string, spaces are allowed in the string. |
| test-name | Specifies the name of the linkage test instance. | It is a string of 1 to 32 characters, spaces not supported. When quotation marks are used around the string, spaces are allowed in the string. |
| none | Marks as no event for the event. | - |
| description | Indicates the description of the event. | The value is a string of 1 to 127 characters with spaces supported. |
Usage Guidelines
Usage Scenario
If the monitored item of an NQA test result exceeds the threshold, the system sends an alarm. The nqa event command can be used to associate an event with the alarm.
- Record a log.
- Send a trap to the NMS.
- Record a log and send a trap to the NMS.
- Trigger a linkage test instance.
- Mark as no event.
Prerequisites
A test instance has been configured before associating it with an event. Creating other types of events requires no prerequisites.
Configuration Impact
After the undo nqa event command is run, all alarm events will be deleted if no event entry number is specified. If an event entry number is specified, the corresponding alarm event will be deleted.
Precautions
After running the nqa event command, run the alarm command to configure the alarm threshold for the monitored item of an NQA test result. In this case, an alarm is generated when the system becomes abnormal.
During configuration, check whether the event entry exists. If an event entry number to be entered exists, and the original event is not associated with an alarm, the original event which the event entry number corresponds to is overwritten after the event number is entered.
The event being associated with an alarm cannot be deleted.
nqa-ftp-record enable
Function
The nqa-ftp-record enable command enables the device to send the NQA test result to the FTP server using FTP.
The undo nqa-ftp-record enable command disables the device from sending the NQA test result to the FTP server using FTP.
By default, the test result is not sent to the FTP server using FTP.
Usage Guidelines
Usage Scenario
The latest test result overrides the previous ones, because only a few NQA test results can be saved on the device. By default, the system stores the latest five test results. If you do not query the test results in a timely manner, some of them will be lost.
To solve this problem, you can save NQA test results to the FTP server using FTP. The NQA client sends test results to the specified FTP server using FTP. The FTP server then saves the test results to a text file.
Prerequisites
Parameters for the FTP connection have been set using the nqa-ftp-record ip-address, nqa-ftp-record username, nqa-ftp-record password, and nqa-ftp-record filename commands.
Precautions
During the FTP transmission, ensure the connectivity of the FTP connection.
It is recommended that you use the FTP protocol in the secure network environment.
nqa-ftp-record filename
Function
The nqa-ftp-record filename command configures a file name for NQA test results when the test results are saved to the FTP server.
The undo nqa-ftp-record filename command deletes the file name configured for NQA test results.
Parameters
| Parameter | Description | Value |
|---|---|---|
| filename | Specifies the file name. | The value is a string of 1 to 200 characters. The file name cannot end with any forward slashes (/) or backward slashes (\). NOTE:
When quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
The file to be saved is named in the format of file name-year-month-day-hour-minute-second.txt. If the number of sent results reaches the configured maximum value or the storage time of results expires, the system creates a file to save these results.
Various FTP servers may support files with the file name in different length ranges. Before you configure this command, ensure that the target FTP server supports the length of the specified file name. Otherwise, NQA test results may fail to be transmitted using FTP.
nqa-ftp-record ip-address
Function
The nqa-ftp-record ip-address command configures an IP address for the FTP server where NQA test results are saved.
The undo nqa-ftp-record ip-address command deletes the IP address of the FTP server where NQA test results are saved.
By default, no IP address is configured for the FTP server.
Parameters
| Parameter | Description | Value |
|---|---|---|
| ip-address | Specifies an IP address for the FTP server. | The IP address is in dotted decimal notation. |
nqa-ftp-record item-num
Function
The nqa-ftp-record item-num command sets the number of test results that can be saved to a file on the FTP server.
The undo nqa-ftp-record item-num command restores the default number of test results that can be saved to a file on the FTP server.
By default, 100000 test results can be saved to a file on the FTP server.
Parameters
| Parameter | Description | Value |
|---|---|---|
| item-number | Specifies the number of test results that can be saved to a file on the FTP server. | The value is an integer that ranges from 10000 to 2147483647. |
Usage Guidelines
Usage Scenario
When NQA test results are sent to the specified FTP server using FTP and the FTP server stores NQA test results to a text file, you need to set the maximum number of NQA test results that can be saved in each text file. If the number of test results exceeds the configured number, a new text file is created on the FTP server by the sequence number to store the subsequent NQA test results.
In addition, if the interval at which a test result is saved expires, a new file is also created on the FTP server by the sequence number to store NQA test results. If both the nqa-ftp-record time and nqa-ftp-record item-num commands are executed, a new file is created and the subsequent test results are saved to the new file when either of the interval at which a test result is saved or the number of test results reaches the configured value.
Configuration Impact
The system can send two test results to the FTP server each time. If the FTP server cannot resume the process of file writing after the process is interrupted, a new file is created on the FTP server to store NQA test results.
Before test results are sent to the FTP server using FTP, ensure that the FTP connection works properly.
nqa-ftp-record password
Function
The nqa-ftp-record password command configures a password for logging in to the FTP server where NQA test results are saved.
The undo nqa-ftp-record password command deletes the password for logging in to the FTP server where NQA test results are saved.
Parameters
| Parameter | Description | Value |
|---|---|---|
| password | Specifies a password for logging in to the FTP server where NQA test results are saved. | The value is a string of 1 to 32 or 32 to 68 case-sensitive characters without spaces.
NOTE:
When quotation marks are used around the string, spaces are allowed in the string. |
| cipher cipher-password | Specifies a password for logging in to the FTP server where NQA test results are saved. | The value is a string of 1 to 32 or 32 to 68 case-sensitive characters without spaces.
NOTE:
When quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
The command can be used when the system sends NQA test results to the specified FTP server using FTP. To ensure test security and prevent unauthorized users from accessing the network, you need to enable identity authentication. The nqa-ftp-record password command can be used to set the specified user and password. Only the user who enters the authorized user name and password is authorized to access the network.
Configuration Impact
Ensure that the nqa-ftp-record password command has been run before running the nqa-ftp-record enable command. Otherwise, FTP record (FTPR) cannot be enabled.
Precautions
The configured password and the user name configured by the nqa-ftp-record username command must be consistent.
Before test results are sent to the FTP server using FTP, ensure that the FTP connection works properly.
nqa-ftp-record time
Function
The nqa-ftp-record time command sets the interval at which test results are saved to a file on the FTP server.
The undo nqa-ftp-record time command restores the default interval at which test results are saved to a file on the FTP server.
By default, the interval at which NQA test results are saved to a file on the FTP server is 60 minutes.
Parameters
| Parameter | Description | Value |
|---|---|---|
| time | Specifies the interval at which test results are stored to a text file using FTP. | The value is an integer that ranges from 1 to 43200, in minutes. The default value is 60. |
Usage Guidelines
Usage Scenario
When NQA test results are sent to a specified FTP server using FTP and the FTP server stores NQA test results to a text file, you need to set the interval at which test results are stored to a text file. A text file can store the test results in a specified period of time. If the interval exceeds the configured time, a new text file is created on the FTP server by the sequence number to store the subsequent NQA test results.
- If the number of test results stored in a file on the FTP server reaches the configured number, a new file is created and the subsequent test results is stored to the new file.
- If the number of test results stored in a file on the FTP server does not reach the configured number, but the interval at which a test result is stored reaches the configured interval, a new file is created and the subsequent test results are stored to the new file.
Precautions
Before test results are sent to the FTP server using FTP, ensure that the FTP connection works properly.
nqa-ftp-record trap-enable
Function
The nqa-ftp-record trap-enable command generates traps after NQA test results are saved using FTP.
The undo nqa-ftp-record trap-enable command disables the generation of traps after NQA test results are saved using FTP.
By default, no trap is generated when the NQA test result is saved using FTP.
Usage Guidelines
Usage Scenario
The command can be used when the system sends NQA test results to the specified FTP server using FTP. After the NQA test results are saved using FTP, the system sends a trap to the NMS.
Configuration Impact
If the test result is saved successfully at the first time, no trap is generated. If the test result is saved successfully at the second time, a trap is generated.
A trap is generated only after each text file is saved successfully. That is, when the number of saved test results reaches the configured number, or the interval at which a test result is saved reaches the configured time, the current text file can be saved successfully and a trap is generated.
Precautions
Before test results are sent to the FTP server using FTP, ensure that the FTP connection works properly.
nqa-ftp-record source-address
Function
The nqa-ftp-record source-address command configures the address of the FTP client from which NQA test results are uploaded to the FTP server.
The nqa-ftp-record source-address restores the default FTP client address from which NQA test results are uploaded to the FTP server.
By default, the address of the FTP client from which NQA test results are uploaded to the FTP server is not configured.
Parameters
| Parameter | Description | Value |
|---|---|---|
| ip-address | Specifies an FTP client address. | The value is in dotted decimal notation. |
nqa-ftp-record username
Function
The nqa-ftp-record username command configures a user name for logging in to the FTP server where NQA test results are saved.
The undo nqa-ftp-record username command deletes the user name for logging in to the FTP server where NQA test results are saved.
By default, no user name is configured.
Parameters
| Parameter | Description | Value |
|---|---|---|
| username | Specifies a user name for logging in to the FTP server where NQA test results are saved. | The value is a string of 1 to 255 characters. |
nqa-ftp-record vpn-instance
Function
The nqa-ftp-record vpn-instance command configures a VPN instance for the FTP server where NQA test results are saved.
The undo nqa-ftp-record vpn-instance command deletes the VPN instance configured for the FTP server where NQA test results are saved.
By default, the name of a VPN instance is not configured on the system.
Parameters
| Parameter | Description | Value |
|---|---|---|
| vpn-instance | Specifies the name of the VPN instance to which the FTP server belongs. | The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
The command can be used when the system sends NQA test results to the specified FTP server using FTP. When the NQA client is connected to the FTP server through a VPN, the nqa-ftp-record vpn-instance command can be used to specify the name of the VPN instance.
Precautions
Before test results are sent to the FTP server using FTP, ensure that the FTP connection works properly.
nqa-group
Function
The nqa-group command creates an NQA group and displays the NQA group view, or displays an existing NQA group view.
The undo nqa-group command deletes an NQA group.
Parameters
| Parameter | Description | Value |
|---|---|---|
| group-name | Specifies the name of an NQA group. | It is a string of 1 to 32 case-sensitive characters without any space. |
Usage Guidelines
Usage Scenario
After an NQA group is created using the nqa-group command, you can add NQA test instances to the NQA group using the nqa (NQA group view) command, and then manage the NQA group to monitor multiple links at the same time.
nqa-jitter tag-version
Function
The nqa-jitter tag-version command sets the packet version for a jitter test instance.
The undo nqa-jitter tag-version command restores the default packet version for a jitter test instance.
By default, the packet version of a jitter test instance is 1.
Parameters
| Parameter | Description | Value |
|---|---|---|
| version-number | Specifies the packet version for a jitter test instance. | The value can be 1 or 2. |
Usage Guidelines
Usage Scenario
Version 1 does not support unidirectional packet loss statistics.
Version 2 produces more accurate packet statistics, which helps network administrators to locate network faults and detect malicious attacks towards the network. After version 2 and collecting the packet loss across a unidirectional link are enabled, you can view the packet loss across the link from the source end to the destination end, from the destination end to the source end, or in an unknown direction in the test results.
Therefore, configuring version 2 is recommended.
Configuration Impact
If the packet version of a jitter test instance has been configured, running the nqa-jitter tag-version command will override the previous configuration.
Precautions
- If the packet version for the jitter test is 1, configuring the UDP server is optional.
- If the packet version of the jitter test is 2, configuring UDP server is mandatory. You need to run the nqa-server udpecho command to configure the UDP server. If the command is not configured, the UDP jitter test instance on the ingress will fail due to timeout.
nqa-server rtp-udp
Function
The nqa-server rtp-udp command configures an RTP server for an NQA test.
The undo nqa-server rtp-udp command deletes the RTP server for an NQA test.
By default, no RTP server is configured.
Format
nqa-server rtp-udp [ vpn-instance vpn-instance-name ] ip-address port-number
undo nqa-server rtp-udp { [ vpn-instance vpn-instance-name ] ip-address port-number | all }
Parameters
| Parameter | Description | Value |
|---|---|---|
| vpn-instance vpn-instance-name | Specifies the name of the VPN instance to which the RTP server belongs. | The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
| ip-address | Specifies the IP address of the RTP server for monitoring RTP services. | The value is in dotted decimal notation. |
| port-number | Specifies the port number of the RTP server for monitoring RTP services. | The value is an integer that can be any value in the range of 1025 to 65535. |
| all | Specifies RTP servers for all NQA tests. | - |
Usage Guidelines
Incomplete or unclear pictures may occur during a Telepresence conference because of the unstable network. You can deploy an RTP test instance at the source node, and run the nqa-server rtp-udp command at the transit mode and destination node to deploy RTP servers to perform a jitter test. This method helps you easily locate faults, facilitates network maintenance, and improves Telepresence conference experience.
nqa-server session-record enable
Function
The nqa-server session-record enable command enables NQA client information display on the NQA server.
The undo nqa-server session-record enable command disables NQA client information display on the NQA server.
By default, NQA client information display is disabled on the NQA server.
Usage Guidelines
Usage Scenario
After the nqa-server session-record enable command is executed on the NQA server to enable NQA client information display, run the display nqa-server session command to view information about all NQA clients connected to the NQA server. The NQA client information includes the IP address of NQA server, IP address of NQA client, source port of NQA client, and VPN.
Precautions
This command is valid for only hardware-based UDP jitter test.
nqa-server tcpconnect
Function
The nqa-server tcpconnect command configures the IP address and port number for the TCP server in an NQA TCP test instance.
The undo nqa-server tcpconnect command deletes the IP address and port number configured for the TCP server in an NQA TCP test instance.
By default, no IP address or port number is configured for the TCP server in an NQA TCP test instance.
Format
nqa-server tcpconnect [ vpn-instance vpn-instance-name ] ip-address port-number
undo nqa-server tcpconnect { all | [ vpn-instance vpn-instance-name ] ip-address port-number }
Parameters
| Parameter | Description | Value |
|---|---|---|
| vpn-instance vpn-instance-name | Specifies the name of the VPN instance to which the TCP server
belongs. NOTE:
This
parameter is invalid when a loopback address is specified as the TCP
server address. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
| all | Indicates all TCP listening addresses and port numbers. | - |
| ip-address | Specifies the IP address of the TCP server for monitoring TCP services. | The value is in dotted decimal notation. |
| port-number | Specifies the port number of the TCP server for monitoring TCP services. | The value is an integer that ranges from 1 to 65535. The configured port cannot be a well-known port or used by other modules. |
Usage Guidelines
Usage Scenario
The NQA TCP test is used to detect the rate at which a TCP connection is set up between an NQA client and a TCP server through the three-way handshake. In a TCP test instance, a TCP server needs to be configured on the server end to respond to probe packets.
- Run the destination-address command to configure the destination address of an NQA test instance or the IP address of the TCP server.
- Run the destination-port command to configure the destination port number of an NQA test instance, or the port number of the TCP server.
If the client and the server are connected through a VPN, you need to specify the VPN instance name.
Configuration Impact
Running the undo nqa-server tcpconnect all command will delete the IP address and port number of the TCP server.
Precautions
A TCP server is configured only in a TCP test instance.
nqa-server udpecho
Function
The nqa-server udpecho command configures the IP address and port number for the UDP server in an NQA test.
The undo nqa-server udpecho command deletes the IP address and port number configured for the UDP server in an NQA test.
By default, no IP address or port number is configured for the UDP server in an NQA test.
Format
nqa-server udpecho [ vpn-instance vpn-instance-name ] { auto-address | ip-address | ipv6 ipv6-address } port-number
undo nqa-server udpecho { [ vpn-instance vpn-instance-name ] { auto-address | ip-address | ipv6 ipv6-address } port-number | all }
Parameters
| Parameter | Description | Value |
|---|---|---|
| vpn-instance vpn-instance-name | Specifies the name of the VPN instance to which the
server belongs. NOTE:
This parameter is invalid when a loopback address is specified as
the UDP server address. |
The value is a string of 1 to 31 characters. |
| all | Specifies a server for all NQA test instances. | - |
| ip-address | Specifies the IP address of the server for monitoring UDP services. | The value is in dotted decimal notation. |
| port-number | Specifies the port number of the server for monitoring UDP services. | The value is an integer that ranges from 1 to 65535. The configured port cannot be a well-known port or used by other modules. |
| ipv6 ipv6-address | Specifies the IPv6 address of the server for monitoring UDP services. | - |
| auto-address | Configures the UDP service on the NQA server to automatically monitor all IPv4 addresses. | - |
Usage Guidelines
Usage Scenario
This command is used on a UDP server.
UDP packets are transmitted in a jitter test. The test is used to obtain the packet delay, jitter, and packet loss ratio by comparing timestamps in the request and response packets. A UDP server needs to be configured for an NQA test to respond to probe packets.
If the client and the server are connected through a VPN, you need to specify the VPN instance name.
If the local IPv4 address cannot be predicted because of dynamic address allocation by DHCP, specify the auto-address keyword to configure the UDP service on the NQA server to automatically monitor all IPv4 addresses.
Configuration Impact
Running the undo nqa-server udpecho all command will delete the IP address and port number of the UDP server for all NQA UDP test instances.
Precautions
- If the version number of the jitter test packets is 1, the command is optional.
- If the version number of the jitter test packets is 2, the command is mandatory. If the command is not configured, the jitter test instance on the ingress will fail due to timeout.
nqa upload statistics datetime-type
Function
The nqa upload statistics datetime-type command configures the time type based on which NQA test results are uploaded to the server.
The undo nqa upload statistics datetime-type command restores the default time type based on which NQA test results are uploaded to the server.
The default time type based on which NQA test results are uploaded to the server is Coordinated Universal Time (UTC).
Parameters
| Parameter | Description | Value |
|---|---|---|
| utc | Indicates that NQA test results are uploaded to the server based on UTC. |
- |
| local | Indicates that NQA test results are uploaded to the server based on local time. |
- |
Usage Guidelines
UTC is the default time type based on which NQA test results are uploaded to the server. This time type causes difficulties in time understanding. To change the time type to local time, run the nqa upload statistics datetime-type local command.
UTC: Coordinated Universal Time, which is the standard time used globally.
Local time: If the local time is faster than UTC, for example, Beijing Time is 8 hours faster than UTC, the time zone of China is UTC+8. If the local time is slower than UTC, for example, Hawaii Time is 10 hours slower than UTC, the time zone of Hawaii is UTC-10.
probe-count
Function
The probe-count command sets the number of probes for an NQA test instance.
The undo probe-count command restores the default number of probes for an NQA test instance.
By default, the number of probes for an NQA test instance is 3.
Parameters
| Parameter | Description | Value |
|---|---|---|
| number | Specifies the number of probes in an NQA test instance. | The value is an integer that ranges from 1 to 15. The
default value is 3. NOTE:
The number of probes in a trace test instance cannot be
more than 10. |
Usage Guidelines
Usage Scenario
- If the network to be tested is a reliable network, the number of probes can be set relatively small because the probe can be successful after a small number of probe packets are sent.
- If the network to be tested is an unreliable network, the number of probes can be set relatively large because the probe can be successful only after a large number of probe packets are sent.
- If the probe test is successful after a small number of probes packets are sent, the network quality is good.
- If the probe test is successful after a large number of probes packets are sent, the network quality is poor.
Prerequisites
The type of a test instance has been specified using the test-type command.
Configuration Impact
In jitter test instances, the number of sent packets = probe-count x jitter-packetnum, but the product cannot exceed 3000.
If the number of probes has been configured, running the probe-count command will override the previous configuration.
Precautions
The number of probes cannot be set for an FTP or a DNS test.
The number of probes of a running test instance cannot be changed.
probe-failtimes
Function
The probe-failtimes command sets the threshold for the number of traps to be sent when the NQA test fails. That is, test packet fragmentation is not allowed.
The undo probe-failtimes command restores the default threshold for the number of traps to be sent when the NQA test fails.
By default, one trap is sent for each probe failure.
Parameters
| Parameter | Description | Value |
|---|---|---|
| times | Specifies the threshold for the number of traps to be sent when the NQA test fails, that is, the number of continuous probe failures. | The value is an integer that ranges from 1 to 15. The default value is 1. |
Usage Guidelines
Usage Scenario
The NQA probe test is used to check whether response packets are received in a probe. If the number of continuous probe failures reaches the specified value, the system sends a trap to the specified NMS.
Prerequisites
The type of a test instance has been specified using the test-type command.
Follow-up Procedure
Run the send-trap probefailure command to enable the system to send a trap to the NMS after a probe fails. Otherwise, the trap cannot be sent to the NMS after a probe fails.
Precautions
- This configuration of a running test instance cannot be changed.
- If the test instance does not support probe-count number, you are advised to set probe-failtimes to 1; otherwise, traps cannot be sent.
- If the test instance supports probe-count number, you are advised to set probe-failtimes to be smaller or equivalent to probe-count; otherwise, traps cannot be sent.
packet-rewrite-check
Function
The packet-rewrite-check command configures the NQA packet rewrite check function by padding NQA packets.
The undo packet-rewrite-check command cancels NQA packet padding.
By default, NQA packet padding is not configured.
Parameters
| Parameter | Description | Value |
|---|---|---|
| alternant-binary | Pads bits 0101 and 1010 alternatively into test packets. | - |
| same-binary | Pads bits 0000 and 1111 alternatively into test packets. | - |
Usage Guidelines
Usage Scenario
Packet rewrite frequently occurs on the live network. The NQA packet rewrite check function can locate the device where the packet rewrite occurs by dividing the network into different parts and checking these parts one by one. The NQA packet rewrite check function uses test packets padded with specified bits for rewrite checking. Bit transition may occur on any bit of the packet, for example, it may occur on one bit in bits 1010, 0000, or 1111. To locate where the bit transition or whether packet rewrite occurs, configuring both alternant-binary and same-binary is recommended. In this manner, the length and contents of the bits can be changed as required. For example, bits 1010 can be padded into the first test packet and 0101 into the second one. After receiving the response packet, the device checks contents of the packet and determines whether the packet is rewritten.
Configuration Impact
Packet contents will be changed because bit characters are padded into the packet.
Precautions
If the packet-rewrite-check command has been configured, the datafill command cannot be used. In addition, you cannot configure the hardware-based enable command, because the LPU does not support the NQA packet rewrite check function.
records
Function
The records command sets the maximum number of history records and the maximum number of test results for NQA test instances.
The undo records command restores the default maximum number of history records and the default maximum number of test results for NQA test instances.
By default, the number of history records is 50, and the number of test results is 5.
Parameters
| Parameter | Description | Value |
|---|---|---|
| history number | Specifies the maximum number of history records. | The value is an integer that ranges from 0 to 50. The default value is 50. |
| result number | Specifies the maximum number of test results. | The value is an integer that ranges from 1 to 10. The default value is 5. |
Usage Guidelines
Usage Scenario
You can run the records command to set the maximum number of history records and the maximum number of test results for NQA test instances.
By default, a test instance supports 50 history records. You need to limit the number of history records on the device. In addition, you need to set the number of allowed remaining history records that can be added. The configured maximum number of history records cannot exceed the sum of the total default number of history records and the remaining number of history records.
Precautions
The type of a test instance has been specified using the test-type command.
This configuration of a running test instance cannot be changed.
records history-filter
Function
The records history-filter command enables a device to filter out records in a historical NQA test instance table.
The undo records history-filter command disables a device from filtering records in historical NQA test instance tables.
By default, a device does not filter records in historical NQA test instance tables.
Parameters
| Parameter | Description | Value |
|---|---|---|
| all | Indicates all records. | - |
| failures | Indicates records about failed test instances. | - |
Usage Guidelines
Before running the records history-filter command, you must run the test-type command to specify the test instance type.
To filter records about failed NQA test instances, configure the failures parameter in the records history-filter command.
remote-pw-id
Function
Using the remote-pw-id command, you can configure the ID of the remote end of a PW or a VC.
Using the undo remote-pw-id command, you can remove the configured ID of the remote end of a PW or a VC.
When the VC type is LDP, remote-pw-id defaults to be 0.
Parameters
| Parameter | Description | Value |
|---|---|---|
| remote-pw-id | Specifies the ID of the remote end of a PW or a VC. | The value is a decimal integer.
|
remote-address (NQA view)
Function
Using the remote-address command, you can configure the remote address.
Using the undo remote-address command, you can delete a remote address.
By default, no remote address is configured.
Parameters
| Parameter | Description | Value |
|---|---|---|
| ipv4 remote-ip-address | Specifies the remotely assigned IP address. | It is in dotted decimal notation. |
reset ip nqa-compatible responder statistics
Function
The reset ip nqa-compatible responder statistics command deletes statistics on the NQA handshake packets sent from the third-party device or NMS software.
Usage Guidelines
Usage Scenario
Before checking the latest status of communication between the device and third-party device or NMS software, use this command to delete old statistics first.
Precautions
Once statistics on the NQA handshake packets sent from the third-party device or NMS software are deleted, they cannot be restored. Confirm the action before you perform it.
sendpacket passroute
Function
The sendpacket passroute command enables test packets to be sent without searching the routing table.
The undo sendpacket passroute command restores the default setting.
By default, the test packet is sent according to the routing table.
Usage Guidelines
- ICMP
- TCP
- UDP
- HTTP
- Jitter
- FTP
- SNMP
- Trace
You cannot change this configuration of a running test instance.
After the sendpacket passroute command is executed, the device sends test packets without searching the routing table. However, the configurations of ttl and ip-forwarding become invalid.
send-trap
Function
The send-trap command configures conditions for sending traps.
The undo send-trap command deletes the previous configuration.
By default, the device is disabled from sending traps.
Format
send-trap { all | { owd-ds | owd-sd | probefailure | rtd | testcomplete | testfailure | jitter-sd | jitter-ds | testresult-change } * }
undo send-trap { all | { owd-ds | owd-sd | probefailure | rtd | testcomplete | testfailure | jitter-sd | jitter-ds | testresult-change } * }
Parameters
| Parameter | Description | Value |
|---|---|---|
| all | Indicates that a trap is sent in any of the following
situations:
|
- |
| owd-ds | Indicates that a trap is sent when the OWD from the
destination to the source exceeds the threshold. NOTE:
This parameter applies only to jitter test instances. |
- |
| owd-sd | Indicates that a trap is sent when the OWD from the
source to the destination exceeds the threshold. NOTE:
This parameter applies only to jitter test instances. |
- |
| probefailure | Indicates that a trap is sent when the number of probe
failures reaches the threshold. NOTE:
This parameter does not apply to Jitter test instances. |
- |
| rtd | Indicates that a trap is sent when the RTD exceeds the threshold. | - |
| testcomplete | Indicates that a trap is sent when a test succeeds. | - |
| testfailure | Indicates that a trap is sent when the number of test failures reaches the threshold. | - |
| jitter-sd | Indicates that a trap is sent when the jitter from the source to the destination exceeds the threshold. | - |
| jitter-ds | Indicates that a trap is sent when the jitter from the destination to the source exceeds the threshold. | - |
| testresult-change | Indicates that a trap is sent when the probe result
changes. NOTE:
This function supports only ICMP test instances. |
- |
Usage Guidelines
Usage Scenario
Traps are generated no matter whether the NQA test succeeds or fails. You can determine whether traps are sent to the NMS by enabling or disabling the trap function.
The OWD exceeds the threshold.
If the OWD from the source to the destination or from the destination to the source exceeds the threshold, the device sends a trap to the NMS using the configured NMS address.
The RTD exceeds the threshold.
If the RTD exceeds the threshold, the device sends a trap to the NMS using the configured address.
NQA probes fail.
When no response packet is received after a specified number of continuous test packets are sent, the device sends a trap to the NMS using the configured address.
An NQA test succeeds.
When the device receives a response packet from a destination address, the device sends a trap to the NMS using the configured address.
NQA tests fail.
When the number of continuous test failures reaches the maximum number, the device sends a trap to the NMS using the configured address.
- NQA probe result changes.
When the NQA probe result changes, the device sends a trap to the NMS using the configured address.
You can run the send-trap command to configure conditions for sending traps. When a condition is met, the device sends a trap to the NMS.
Prerequisites
The type of a test instance has been specified using the test-type command.
The route between the device and NMS is reachable, and related configurations are complete. The trap function has been enabled for the NQA module using the snmp-agent trap enable feature-name nqa command, and the host where traps are sent is configured using the snmp-agent target-host trap-hostname command; otherwise, traps cannot be sent to the NMS.
Precautions
You cannot change this configuration of a running test instance.
set-df
Function
The set-df command configures the DF (Don't Fragment) field of the test packet. This field prevents packets from being fragmented.
The undo set-df command restores the default setting.
By default, packet fragmentation is allowed.
Usage Guidelines
Usage Scenario
If two hosts need to communicate with each other over multiple networks, the smallest MTU value of the networks is the path MTU value. Packets can be transmitted normally over multiple networks only after the path MTU value is obtained.
If the DF bit of a packet is not configured, and the length of the packet is longer than the MTU value, the packet will be fragmented into several fragments that are shorter than the path MTU value. As a result, the path MTU cannot be detected by sending packets with increasing lengths. To detect the path MTU value, run the set-df command to prohibit packet fragmentation. Then, increase the length of packets sent along the path to find the path MTU value.
Prerequisites
The type of a test instance has been set to Trace using the test-type trace command.
Precautions
The configuration of the DF bit for packets in a running test instance cannot be changed.
snmp-agent trap enable feature-name nqa
Function
The snmp-agent trap enable feature-name nqa command enables the trap function for the NQA module.
The undo snmp-agent trap enable feature-name nqa command disables the trap function for the NQA module.
By default, the trap function is enabled for the NQA module.
Format
snmp-agent trap enable feature-name nqa [ trap-name { nqaresultsprobefailed | nqahttpstatsprobefailed | pingprobefailed | nqaftpstatsprobefailed | pingtestfailed | pingtestcompleted | traceroutetestfailed | traceroutetestcompleted | nqaresultstestfailed | nqaresultstestcompleted | nqaresultsthresholdnotification | nqahttpstatstestfailed | nqahttpstatstestcompleted | nqahttpstatsthresholdnotification | nqaftpstatstestfailed | nqaftpstatstestcompleted | nqaftpstatsthresholdnotification | nqajitterstatstestfailed | nqajitterstatstestcompleted | nqajitterstatsrtdthresholdnotification | nqajitterstatsowdthresholdnotificationsd | nqajitterstatsowdthresholdnotificationds | nqarisingalarmnotification | nqafaillingalarmnotification | nqaftpsaverecordnotification | nqajitterstatsjitterthresholdnotificationsd | nqajitterstatsjitterthresholdnotificationds | nqareflectorstatechangenotification | nqaResultsTestResultChange } ]
undo snmp-agent trap enable feature-name nqa [ trap-name { nqaresultsprobefailed | nqahttpstatsprobefailed | pingprobefailed | nqaftpstatsprobefailed | pingtestfailed | pingtestcompleted | traceroutetestfailed | traceroutetestcompleted | nqaresultstestfailed | nqaresultstestcompleted | nqaresultsthresholdnotification | nqahttpstatstestfailed | nqahttpstatstestcompleted | nqahttpstatsthresholdnotification | nqaftpstatstestfailed | nqaftpstatstestcompleted | nqaftpstatsthresholdnotification | nqajitterstatstestfailed | nqajitterstatstestcompleted | nqajitterstatsrtdthresholdnotification | nqajitterstatsowdthresholdnotificationsd | nqajitterstatsowdthresholdnotificationds | nqarisingalarmnotification | nqafaillingalarmnotification | nqaftpsaverecordnotification | nqajitterstatsjitterthresholdnotificationsd | nqajitterstatsjitterthresholdnotificationds | nqareflectorstatechangenotification | nqaResultsTestResultChange } ]
Parameters
| Parameter | Description | Value |
|---|---|---|
| trap-name | Enables the trap function for the specified event for the NQA module. | - |
| nqaresultsprobefailed | Sends a trap when the number of continuous probe failures exceeds the threshold. | - |
| nqahttpstatsprobefailed | Sends a trap when the number of continuous probe failures exceeds the threshold in an HTTP test instance. | - |
| pingprobefailed | Sends a trap when the number of continuous ping failures exceeds the threshold. | - |
| nqaftpstatsprobefailed | Sends a trap when a test result fails to be saved to the FTP server. | - |
| pingtestfailed | Sends a trap when a ping test fails. | - |
| pingtestcompleted | Sends a trap when a ping test is complete. | - |
| traceroutetestfailed | Sends a trap when no destination path is obtained in a traceroute test. | - |
| traceroutetestcompleted | Sends a trap when a destination path is obtained in a traceroute test. | - |
| nqaresultstestfailed | Sends a trap when a common test fails. | - |
| nqaresultstestcompleted | Sends a trap when a common test is complete. | - |
| nqaresultsthresholdnotification | Sends a trap when the completing time of a test instance expires. | - |
| nqahttpstatstestfailed | Sends a trap when an HTTP test fails. | - |
| nqahttpstatstestcompleted | Sends a trap when an HTTP test is complete. | - |
| nqahttpstatsthresholdnotification | Sends a trap when the completing time of an HTTP test instance expires. | - |
| nqaftpstatstestfailed | Sends a trap when an FTP test fails. | - |
| nqaftpstatstestcompleted | Sends a trap when an FTP test is complete. | - |
| nqaftpstatsthresholdnotification | Sends a trap when the completing time of an FTP test instance expires. | - |
| nqajitterstatstestfailed | Sends a trap when a jitter test fails. | - |
| nqajitterstatstestcompleted | Sends a trap when a jitter test is complete. | - |
| nqajitterstatsrtdthresholdnotification | Sends a trap when the completing time of a jitter test instance expires. | - |
| nqajitterstatsowdthresholdnotificationsd | Sends a trap when the time from the source to the destination expires in a jitter test instance. | - |
| nqajitterstatsowdthresholdnotificationds | Sends a trap when the time from the destination to the source expires in a jitter test instance. | - |
| nqarisingalarmnotification | Sends a traps when the value of the monitored node exceeds the threshold. | - |
| nqafaillingalarmnotification | Sends a traps when the value of the monitored node is smaller than the threshold. | - |
| nqaftpsaverecordnotification | Sends a trap when a test result is saved to the FTP server. | - |
| nqajitterstatsjitterthresholdnotificationsd | Sends a trap when the jitter time from the source to the destination expires in a jitter test instance. | - |
| nqajitterstatsjitterthresholdnotificationds | Sends a trap when the jitter time from the destination to the source expires in a jitter test instance. | - |
| nqareflectorstatechangenotification | Trap generated when the reflector status in the general flow test instance changes. | - |
| nqaResultsTestResultChange | Trap generated when the probe result of an ICMP test instance changes. |
- |
source-address
Function
The source-address command sets the source IP address for a test instance.
The undo source-address command restores the default setting.
By default, the IP address of the interface where packets are sent functions as the source IP address of a test instance.
Parameters
| Parameter | Description | Value |
|---|---|---|
| ipv4 ipv4-address | Specifies the IPv4 source address for the NQA test instance. | The value is in dotted decimal notation. |
| ipv6 ipv6-address | Specifies the IPv6 source address for the NQA test instance. NOTE:
Only DNS, ICMP, trace, and jitter tests support IPv6 source addresses. |
The value consists of 128 octets, which are classified into 8 groups. Each group contains 4 hexadecimal numbers in the format X:X:X:X:X:X:X:X. |
Usage Guidelines
Usage Scenario
The source-address command is used to configure the source IP address for the NQA test. After the test packets reach the destination, a packet is returned, with the configured source IP address as the destination address. If no source IP address is configured, the system specifies the IP address that sends test packets as the source IP address.
Prerequisites
The type of a test instance has been specified using the test-type command. However, the test type cannot be DHCP.
Precautions
The configuration of the source IP address of the running test instance cannot be changed.
source-interface
Function
The source-interface command configures the source interface for an NQA test instance.
The undo source-interface command cancels the configuration.
By default, no source interface is configured for an NQA test instance.
Parameters
| Parameter | Description | Value |
|---|---|---|
| interface-type interface-number | Specifies the type and number of the source interface for an NQA test instance. | - |
Usage Guidelines
Usage Scenario
- If the source-address command is run to specify the source IP address, the test packets are sent from the specified source interface, but the response packets are received from the configured source IP address.
- If no source IP address is specified for an NQA test instance, the IP address of the source interface will be used as the source IP address of the NQA test instance. In this scenario, the initiated and responded packets are both transmitted over the outbound interface specified by the source-interface command.
Prerequisites
The type of a test instance has been specified using the test-type command. The source interface can be configured only for DHCP, ICMP, and Jitter test instances.
Precautions
The configuration of the source interface of a running test instance cannot be changed.
Use an interface with an IP address as the source interface of the NQA test instance; otherwise, the command does not take effect.
In the load balancing scenario, trunks and their member interfaces do not support tests.
source-port
Function
The source-port command configures the source port for an NQA test instance.
The undo source-port command restores the default setting.
No default source port number is specified, port numbers are randomly allocated by the system.
Parameters
| Parameter | Description | Value |
|---|---|---|
| port-number | Specifies the source port number for an NQA test instance. | The value is an integer that ranges from 1 to 65535. The configured port cannot be a well-known port or used by other modules. |
Usage Guidelines
Usage Scenario
- If no source port number is specified for an NQA test instance, a port number is selected at random to receive or send NQA test packets.
- If source port number is specified for an NQA test instance, the specified port number is used to receive and send NQA test packets.
Prerequisites
The test instance type has been specified using the test-type command. The source port number can be configured only for TCP, FTP, HTTP, UDP, jitter (including jitter test instances based on the mechanism that the LPU sends packets), and SNMP test instances.
Precautions
The port specified in the source-port command must be available; otherwise, the probe fails.
Port numbers 61442 to 65535 are reserved. Do not use the port numbers; otherwise, the probe fails.
You cannot change this configuration of a running test instance.
start
Function
The start command sets the start mode and end mode for an NQA test instance.
The undo start command stops a running NQA test instance or restores the configuration of start mode and end mode of an unperformed NQA test instance.
By default, the test instance stops automatically after test packets are sent.
Format
start at [ yyyy/mm/dd ] hh:mm:ss [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ]
start delay { seconds second | hh:mm:ss } [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ]
start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ]
undo start
Parameters
| Parameter | Description | Value |
|---|---|---|
| start at [ yyyy/mm/dd ] hh:mm:ss | Performs a test instance at a specified time. NOTE:
The configured time must be later than the time on the device. |
- |
| start delay { seconds second | hh:mm:ss } | Specifies a delay in performing a test instance. |
|
| start now | Performs a test instance immediately. | - |
| end at [ yyyy/mm/dd ] hh:mm:ss | Stops a test instance at a specified time. | - |
| end delay { seconds second | hh:mm:ss } | Specifies a delay in stopping a test instance. This delay is set based on the current system time. For example: If start at 9:00:00 end delay seconds 60 is run at 8:59:40, then, a test instance starts at 9:00:00 and ends at 9:00:40. |
|
| end lifetime { seconds second | hh:mm:ss } | Specifies the lifetime of an NQA test instance (starting from the moment that the NQA test instance starts). For example: If start delay seconds 60 end lifetime seconds 120 is run at 9:00:00, then, a test instance lasts for 120s as it starts at 09:01:00 and ends at 09:03:00. |
|
Usage Guidelines
Usage Scenario
- Start modes:
- Starting a test instance at a specified time
- Starting a test instance immediately
- Starting a test instance after a certain delay
- End modes:
- Ending a test instance at a specified time
- Ending a test instance immediately
- Ending a test instance after a certain delay
- Ending a test instance after all test packets are sent
Precautions
If the number of the running test instances reaches the maximum value defined by the system, the start command is invalid.
For the same test instance, the start now command can be used again only when the previous configuration is complete.
When starting a test instance at a specified time, the time must be later than the current time on the device.
stop
test-failtimes
Function
The test-failtimes command sets the number of consecutive test failures in an NQA test.
The undo test-failtimes command restores the default setting.
By default, a trap message is sent for each test failure.
Parameters
| Parameter | Description | Value |
|---|---|---|
| times | Specifies the number of consecutive test failures in an NQA test. | The value is an integer that ranges from 1 to 15. The default value is 1. |
Usage Guidelines
Usage Scenario
An NQA test consists of multiple probe tests. By default, if one or more probe tests are successful in an NQA test, the test is considered successful. If all probe tests fail, the test is considered failed. If the number of consecutive test failures reaches the specified value, the system will send a trap to the specified NMS.
Prerequisites
The type of a test instance has been specified using the test-type command.
Follow-up Procedure
Run the send-trap testfailure command to send a trap to the NMS after an NQA test fails. Otherwise, the trap cannot be sent to the NMS after an NQA test fails.
Precautions
This configuration of a running test instance cannot be changed.
test-type
Function
The test-type command configures the test type for an NQA test instance.
The undo test-type command cancels the test type configured for an NQA test instance.
By default, no test type is configured.
Format
test-type { dhcp | dns | ftp | http | icmp | icmpjitter | jitter | lspping | lsptrace | snmp | tcp | trace | udp | vplsping | vplstrace | vplspwping | vplspwtrace }
undo test-type
Parameters
| Parameter | Description | Value |
|---|---|---|
| dhcp | Specifies a DHCP test. | - |
| dns | Specifies a DNS test. | - |
| ftp | Specifies an FTP service test. | - |
| http | Specifies an HTTP service test. | - |
| icmp | Specifies an ICMP test. | - |
| icmpjitter | Specifies an ICMP jitter test, which can detect the jitter on the network by using ICMP packets. | - |
| jitter | Specifies a jitter test, which can detect the jitter during UDP packet transmission. | - |
| lspping | Specifies an LSP ping test. | - |
| lsptrace | Specifies an LSP trace route test. | - |
| snmp | Specifies an SNMP test. | - |
| tcp | Specifies a TCP test. | - |
| trace | Specifies a trace test. | - |
| udp | Specifies a UDP test. | - |
| vplsping | Specifies a VPLS MAC ping test. | - |
| vplstrace | Specifies a VPLS MAC trace test. | - |
| vplspwping | Specifies a VPLS PW ping test. | - |
| vplspwtrace | Specifies a VPLS PW trace test. | - |
timestamp-unit
Function
The timestamp-unit command sets the unit of timestamp for an NQA test instance.
The undo timestamp-unit command restores the default setting.
By default, the unit of timestamp for an NQA test instance is millisecond.
Parameters
| Parameter | Description | Value |
|---|---|---|
| millisecond | Sets the unit of timestamp for an NQA test instance to millisecond. | - |
| microsecond | Sets the unit of timestamp for an NQA test instance to microsecond. | - |
Usage Guidelines
Usage Scenario
The timestamp-unit millisecond command sets the unit of timestamp for an NQA test instance to millisecond.
The timestamp-unit microsecond command sets the unit of timestamp for an NQA test instance to microsecond.
Prerequisites
Hardware forwarding has been enabled using the hardware-based enable command.
Precautions
The timestamp-unit command takes effect for only jitter test instances.
threshold
Function
The threshold command sets the OWD and RTD threshold.
The undo threshold command deletes the OWD threshold and the RTD threshold.
By default, no threshold is set.
Format
threshold { owd-ds owd-ds-value | owd-sd owd-sd-value | rtd rtd-value }
undo threshold { owd-ds | owd-sd | rtd }
Parameters
| Parameter | Description | Value |
|---|---|---|
| owd-ds owd-ds-value | Sets the OWD threshold of packets sent from the destination to the source. | The value is an integer that ranges from 1 to 60000. The unit of this value is the same as that of the timestamp set using the timestamp-unit command. |
| owd-sd owd-sd-value | Sets the OWD threshold of packets sent from the source to the destination. | The value is an integer that ranges from 1 to 60000. The unit of this value is the same as that of the timestamp set using the timestamp-unit command. |
| rtd rtd-value | Sets the RTD threshold. | The value is an integer that ranges from 1 to 60000. The unit of this value is the same as that of the timestamp set using the timestamp-unit command. |
timeout
Function
The timeout command sets the timeout period for a probe of an NQA test instance.
The undo timeout command restores the default timeout period for a probe of an NQA test instance.
By default, the timeout period for DHCP and FTP test instances is 15 seconds and that for other test instances is 3 seconds.
Parameters
| Parameter | Description | Value |
|---|---|---|
| time | Specifies the timeout period for a probe. | The value is an integer that ranges from 1 to 60, in seconds. |
Usage Guidelines
Usage Scenario
The timeout period refers to the waiting time after a probe is sent. If no response packet is received when the timeout period expires, the probe fails. The timeout period is set based on the actual networking. If the value is too small, the NQA test instance fails.
On an unstable network with a low transmission rate, you need to prolong the timeout period for sending probe packets to ensure that response packets can be received.
Prerequisites
The type of a test instance has been specified using the test-type command.
Precautions
- You are advised to set the timeout period based on the round-trip time (RTT) value. Ensure that the timeout period set by the timeout command is longer than the RTT value.
- In all test instances except jitter test instance, the timeout period set by the timeout command must be smaller than or equal to the interval of automatic tests set by the interval command. Otherwise, the tests fail due to timeout of test packets.
- In a DHCP test, packets are sent at random within 10 seconds. If the timeout period is shorter than 10 seconds, some or all packets may time out. Therefore, in a DHCP test, the timeout period must be longer than 10 seconds. The default timeout period is 15 seconds.
Precautions
You cannot change this configuration of a running test instance.
- The system CPU usage exceeds 90% and the configured timeout period is less than 6s.
- frequency configured ≤ (probe-count - 1) × interval + 6.
tos
Function
The tos command sets the ToS value for an NQA test packet.
The undo tos command restores the default ToS value of an NQA test packet.
By default, the ToS value is 0.
Parameters
| Parameter | Description | Value |
|---|---|---|
| value | Specifies the ToS value of a packet. | The value is an integer that ranges from 0 to 255. The default value is 0. |
Usage Guidelines
Usage Scenario
The ToS field contains a precedence sub-field and a ToS sub-field. The precedence sub-field indicates the priority of a packet and the ToS sub-field is seldom used. All the bits in the ToS sub-field must be set to 0. You can set the priority of probe packets by setting the ToS value. When a large number of packets are received, packets of high priorities are processed preferentially.
Prerequisites
- DNS
- DHCP
- Trace
- LSP Ping
- LSP Trace
Configuration Impact
If you run the tos command multiple times, only the latest configuration takes effect.
Precautions
The ToS value of a running test instance cannot be changed.
tracert-hopfailtimes
Function
The tracert-hopfailtimes command sets the number of consecutive failed hops indicating a failed trace test instance.
The undo tracert-hopfailtimes command restores the default number of consecutive failed hops indicating a failed trace test instance.
By default, five consecutive failed hops indicates a failed trace test instance.
Parameters
| Parameter | Description | Value |
|---|---|---|
| times | Specifies the number of consecutive failed hops indicating a failed trace test instance. | The value is an integer that ranges from 1 to 255. |
tracert-livetime
Function
The tracert-livetime command sets the time to live (TTL) value for trace test instances in an NQA test.
The undo tracert-livetime command restores the default TTL value for trace test instances in an NQA test.
By default, the initial TTL value is 1 and the maximum TTL value is 30.
Parameters
| Parameter | Description | Value |
|---|---|---|
| first-ttl first-ttl | Specifies the initial TTL value of a packet. | The value is an integer that ranges from 1 to 255. The default value is 1. |
| max-ttl max-ttl | Specifies the maximum TTL value of a packet. | The value is an integer that ranges from 1 to 255. The value of max-ttl must be greater than the value of first-ttl. By default, the maximum TTL value is 30. |
ttl
Function
The ttl command sets the TTL value for the test packets of an NQA test instance.
The undo ttl command restores the default setting.
The default TTL value is 30.
Parameters
| Parameter | Description | Value |
|---|---|---|
| number | Specifies the TTL value. | The value is an integer that ranges from 1 to 255. The default TTL value is 30. |
Usage Guidelines
Usage Scenario
To prevent test packets from being transmitted endlessly, the test instance must be performed within certain hops.
When a test packet is created, you can run the ttl command to set the TTL value. When the test packet is transmitted along Layer 3 routing devices, each Layer 3 routing device decrements the TTL value by one when the packet arrives. When the TTL value is 0, the Layer 3 routing device discards the test packet and sends an error message to the sending end. This prevents test packets from being transmitted endlessly.
Prerequisites
- DNS
- DHCP
- Trace
- LSP Trace
Configuration Impact
If you run the ttl command multiple times, only the latest configuration takes effect.
Precautions
The type of a running test instance cannot be changed.
ttl-copymode
Function
Using the ttl-copymode command, you can specify the TTL propagation mode (pipe or uniform) for a multi-hop PW detection.
Using the undo ttl-copymode command, you can cancel the TTL propagation mode configured in the NQA view.
By default, the TTL propagation mode varies with products.
Parameters
| Parameter | Description | Value |
|---|---|---|
| pipe | Sets the TTL propagation mode to pipe. | - |
| uniform | Sets the TTL propagation mode to uniform. | - |
Usage Guidelines
During the detection of a multi-hop PW, if the default TTL propagation mode on different devices is different, you need to specify the TTL propagation mode on the first hop of the PW. This command is used to detect BGP/MPLS IP VPN networks.
- When receiving a packet carrying the TTL propagated in pipe mode, the system strips the outer tag of the packet, decreases the TTL in the inner tag by 1, and then sets the TTL in the outer tag to 255.
- When receiving a packet carrying the TTL propagated in uniform mode, the system maps the TTL in the outer tag to the inner tag, decreases the TTL in the inner tag by 1, and then sets the TTL in the outer tag to the value of the TTL in the inner tag.
vlan (NQA view)
Function
Using the vlan command, you can configure a VLAN ID for the NQA test instance.
Using the undo vlan command, you can delete a specified VLAN.
By default, no VLAN ID is configured.
Parameters
| Parameter | Description | Value |
|---|---|---|
| vlan vlan-id | Indicates a VLAN. vlan-id specifies the VLAN ID. | vlan-id is an integer that ranges from 1 to 4094. |
vpn-instance
Function
The vpn-instance command configures the VPN instance that an NQA test instance belongs to.
The undo vpn-instance command deletes the configured VPN instance.
By default, no VPN instance is configured.
Parameters
| Parameter | Description | Value |
|---|---|---|
| vpn-instance-name | Specifies the VPN instance that an NQA test instance belongs to. | The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
- adv-factor
- agetime
- alarm
- clear-records
- community read cipher
- datafill
- datasize
- description (NQA view)
- destination-address
- destination-port
- display ip nqa-compatible responder statistics
- display nqa application
- display nqa alarm
- display nqa-alarm
- display nqa event
- display nqa-event
- display nqa-group
- display nqa history
- display nqa-parameter
- display nqa results
- display nqa support-server-type
- display nqa support-test-type
- display nqa-agent
- display nqa-ftp-record configuration
- display nqa-server
- display nqa-server session
- display snmp-agent trap feature-name nqa all
- dns-server
- fail-percent
- forwarding-simulation inbound-interface
- frequency
- ftp-filename
- ftp-filesize
- ftp-operation
- ftp-password
- ftp-username
- hardware-based enable
- http-operation
- http-url
- icmp-jitter-mode
- interval (NQA view)
- ip nqa-compatible responder enable
- ip nqa-compatible auto
- ip nqa-compatible udp
- ip-forwarding
- jitter-codec
- jitter-packetnum
- lsp-exp
- lsp-path full-display
- lsp-nexthop
- lsp-replymode
- lsp-tetunnel
- lsp-type
- lsp-version
- nexthop
- nqa
- nqa (NQA group view)
- nqa event
- nqa-ftp-record enable
- nqa-ftp-record filename
- nqa-ftp-record ip-address
- nqa-ftp-record item-num
- nqa-ftp-record password
- nqa-ftp-record time
- nqa-ftp-record trap-enable
- nqa-ftp-record source-address
- nqa-ftp-record username
- nqa-ftp-record vpn-instance
- nqa-group
- nqa-jitter tag-version
- nqa-server rtp-udp
- nqa-server session-record enable
- nqa-server tcpconnect
- nqa-server udpecho
- nqa upload statistics datetime-type
- probe-count
- probe-failtimes
- packet-rewrite-check
- records
- records history-filter
- remote-pw-id
- remote-address (NQA view)
- reset ip nqa-compatible responder statistics
- restart (NQA view)
- sendpacket passroute
- send-trap
- set-df
- snmp-agent trap enable feature-name nqa
- source-address
- source-interface
- source-port
- start
- stop
- test-failtimes
- test-type
- timestamp-unit
- threshold
- timeout
- tos
- tracert-hopfailtimes
- tracert-livetime
- ttl
- ttl-copymode
- vlan (NQA view)
- vpn-instance