No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

S12700 V200R013C00 Command Reference

This document describes all the configuration commands of the device, including the command function, syntax, parameters, views, default level, usage guidelines, examples, and related commands.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
NQA Configuration Commands

NQA Configuration Commands

Command Support

The RTP Test and RTP Snoop test instances can be configured only on the switches equipped with MPUA or MPUD main control units.

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.

Format

adv-factor factor-value

undo adv-factor

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.

Views

NQA view

Default Level

2: Configuration level

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

Example

# Set the advantage factor for a simulated voice test calculation to 20.

<HUAWEI> system-view
[HUAWEI] nqa test-instance admin jitter
[HUAWEI-nqa-admin-jitter] test-type jitter
[HUAWEI-nqa-admin-jitter] jitter-codec g711a
[HUAWEI-nqa-admin-jitter] adv-factor 20

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.

Format

agetime hh:mm:ss

undo agetime

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.

Views

NQA view

Default Level

2: Configuration level

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.

Example

# Set the aging time of NQA test instance user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type icmp
[HUAWEI-nqa-user-test] agetime 1:0:0
Related Topics

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 alarm. 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 and ICMP 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 and ICMP 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 and ICMP 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 and ICMP 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 and ICMP 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.
NOTE:

The switch does not support this parameter currently.

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

Views

NQA view

Default Level

2: Configuration level

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 the monitored item exceeds the threshold, an alarm is generated.

Prerequisites

  • The type of a test instance has been specified using the test-type command. The type of test instances that are not supported is as follows:
    • RTP test
    • RTP snoop
  • 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).
  • NQA alarms can be sent to the NMS only after the snmp-agent target-host trap address udp-domain ip-address command is used to configure the NMS to which the alarms sends.

Configuration Impact

After the undo alarm command is run, all alarms will be deleted if no alarm entry number is specified. If an alarm entry number is specified, the corresponding alarm will be deleted.

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
Related Topics

clear-records

Function

The clear-records command clears statistics on NQA test instances.

Format

clear-records

Parameters

None

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After each test instance is complete, test results and historical information will be recorded in result and historical tables respectively. You can run the following commands to view the corresponding data and assess the network quality.

After several test instances are performed to detect network quality, there may be too many records in the statistics table. In this case, you can run the clear-records command to clear historical records and result records of an NQA test instance.

Configuration Impact

Statistics cannot be restored after being cleared using the clear-records command.

Precautions

Clearing statistics on the ongoing test is forbidden.

Before running the command, ensure that the test type specified by the test-type command exists.

Example

# Clear all statistics on NQA test instance user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] clear-records

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.

Format

community read cipher community-name

undo community

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.
NOTE:
When quotation marks are used around the string, spaces are allowed in the string.

Views

NQA view

Default Level

2: Configuration level

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.

Example

# Set the community name for SNMP test.

<HUAWEI> system-view 
[HUAWEI] nqa test-instance user test1
[HUAWEI-nqa-user-test1] test-type snmp
[HUAWEI-nqa-user-test1] community read cipher Huawei-123

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.

Format

datafill fillstring

undo datafill

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

Views

NQA view

Default Level

2: Configuration level

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
  • UDP Jitter
  • ICMP
  • Trace
  • Path Jitter
  • LSP Ping
  • LSP Jitter
  • PWE3 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.

Example

# Set the pad characters of the test named user test to abcd.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type icmp
[HUAWEI-nqa-user-test] datafill abcd

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.

Format

datasize size

undo datasize

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:
Only for MAC ping test instance,the value ranges from 95 to 9000, in bytes.

Views

NQA view

Default Level

2: Configuration level

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 LSP Ping, LSP Jitter, PWE3 Ping, ICMP, MAC Ping, Path Jitter, Trace, UDP, and UDP Jitter test instances.

Precautions

You cannot change the size of the running test packets.

Example

# Set the size of the packets to 100 bytes in the test instance named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type icmp
[HUAWEI-nqa-user-test] datasize 100

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.

Format

description string

undo description

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.

Views

NQA view

Default Level

2: Configuration level

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.

Example

# Set the description of the test named user test to fortest.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] description fortest
Related Topics

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 ] | ipv6 ipv6-address }

destination-address mac mac-address

destination-address remote-mep mep-id rmep-id

destination-address url urlstring

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. -
mac mac-address Specifies a unicast MAC address. The value is a 12-digit hexadecimal number, in the format of H-H-H. Each H is 4 digits.
remote-mep mep-id rmep-id Specifies the ID of a remote MEP. The value is an integer that ranges from 1 to 8191.
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.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

NQA detects service features by creating test instances. In NQA, two test ends are called an NQA client and an NQA server. An NQA test is initiated by the NQA client. For a test instance, the server is specified using the destination IP address configured with the destination-address command.

For example, to detect whether the peer device is reachable, run the nqa command to create an NQA test instance, set the test type to ICMP, and then run the destination-address command to configure the IP address of the peer device as the destination IP address. After that, you can start the test instance. Based on the response packet, you can know whether the peer device is reachable.

Precautions

  • The Label Switched Path (LSP) parameters can be configured only for the LSP test instances.
  • The mac and remote-mep mep-id parameters can be configured only for MAC ping test instances.
  • Only the destination addresses of HTTP, trace, and DNS test instances can be URL addresses. For the HTTP test instances, only absolute URL addresses are supported.
  • The destination addresses of DNS test instances cannot be IPv4 addresses, and the destination URL addresses must contain dots (.); otherwise, the test will fail.
  • IPv6 destination IP addresses can be configured only for ICMP, trace, and jitter test instances.
  • You cannot change the destination address of a running test instance.

Example

# Configure the destination address for test instance user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type icmp
[HUAWEI-nqa-user-test] destination-address ipv4 10.1.1.1
Related Topics

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.

The default port numbers for test instances of different types are as follows:
  • TCP and UDP: 7
  • HTTP: 80
  • FTP: 21
  • Trace: 33434
  • Jitter: No default value is available, and the destination port number must be configured.
NOTE:

A port number larger than 10000 is recommended for a jitter test instance. A small port number may be conflict with the default port number of a protocol, causing a test failure.

Format

destination-port port-number

undo destination-port

Parameters

Parameter Description Value
port-number Specifies the destination port number.
The value range varies with test instances:
  • In RTP Test and RTP Snoop test instances, the value ranges from 1025 to 65535.
  • In other test instances, the value ranges from 1 to 65535.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

NQA detects service features by creating test instances. In NQA, two test ends are called an NQA client and an NQA server. An NQA test is initiated by the NQA client. After test instances are configured with commands on the client, NQA places different types of test instances into various test queues. After the test starts, a response packet is returned. Carriers can then know the operating status about protocols by analyzing the received response packet.

For a test instance, the port for accessing the server is specified using the destination port number configured with the destination-port command on the client.

For example, to detect whether the TCP service runs normally on the peer device using a TCP test instance, perform the following configurations:

  • On the server: Configure the TCP server used for NQA tests, including the supported client IP address and the TCP port number opened to the client.

  • On the client:
    • Create an NQA test instance and set its type to TCP.
    • Configure the IP address of the server as the destination IP address and configure the opened TCP port number on the server as the destination port number.
    • Start the test instance.

Precautions

In the case of a TCP test instance and a UDP test instance, the configured destination port number must be the same as the opened port number on the server.

This command applies to only the FTP, HTTP, RTP Test, RTP Snoop, TCP, Trace, UDP, and UDP Jitter test instances.

You cannot change the destination port number of the test that is being performed.

Example

# Set the destination port number to 2020 for the test instance named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] destination-port 2020
Related Topics

display nqa application

Function

The display nqa application command displays the type of the NQA test instance that corresponds to the service.

Format

display nqa application

Parameters

None

Views

All views

Default Level

1: Monitoring level

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

streaming media            ---                        jitter
                                                      icmpjitter
                                                      mtrace

network performance        ---                        jitter
                                                      icmpjitter
                                                      lspjitter
                                                      macping

trouble-shooting           application                http
                                                      ftp
                                                      dns
                                                      snmp
                                                      rtpsnoop
                                                      rtptest

                           network                    udp
                                                      tcp
                                                      icmp
                                                      trace
                                                      mtrace

                           link                       pwe3ping
                                                      pwe3trace
                                                      macping

                           mpls                       lspping
                                                      lsptrace
Table 16-61  Description of the display nqa application command output

Item

Description

Application

Service type.

Subclasss

Service sub-type.

NQA type

Type of the corresponding NQA test instance.

Related Topics

display nqa alarm

Function

The display nqa alarm command displays alarms of an NQA test instance.

Format

display nqa alarm [ test-instance admin-name test-name ]

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.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

You can run the display nqa alarm command to display current alarms of a specified test instance or all test instances.

NOTE:
To display alarms of a single test instance, ensure that the specified test instance exists.

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
Table 16-62  Description of the display nqa alarm test-instance admin jitter command output

Item

Description

NQA Alarm Information

Alarm configuration of an NQA test instance.

Admin-Name

Administrator of an NQA test instance.

You can run the nqa command to configure this parameter.

Operation-Tag

Name of an NQA test instance.

You can run the nqa command to configure this parameter.

Alarm-Entry

Index of an alarm.

You can run the alarm command to configure this parameter.

AlarmType

Type of the alarm:
  • Rising: An alarm is generated when the monitored item reaches the upper threshold.
  • Falling: An alarm is generated when the monitored item reaches the lower threshold.

You can run the alarm command to configure this parameter.

Event-Entry

ID of the event associated with an alarm.

You can run the alarm command to configure this parameter.

Related Topics

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.

Format

display nqa-alarm

Parameters

None

Views

NQA view

Default Level

1: Monitoring level

Usage Guidelines

After you run the display nqa-alarm command, the maximum number of NQA alarms that the NQA test instance allows and the number of NQA alarms that the NQA test instance already configured are displayed.

Example

# Display the number of NQA alarms of the NQA test instance.

<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                           
------------------------------------------------------    
Table 16-63  Description of the display nqa-alarm command output

Item

Description

NQA alarm information

Statistics about alarms of an NQA test instances.

NQA Alarm Max

Maximum number of NQA alarms that the NQA test instance allows.

NQA Alarm Number

Number of NQA alarms that the NQA test instance already configured.

Related Topics

display nqa event

Function

The display nqa event command displays the event associated with the alarm.

Format

display nqa event [ event-entry ]

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.

Views

All views

Default Level

1: Monitoring level

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
Table 16-64  Description of the display nqa event command output

Item

Description

NQA Event Information

Configuration of the event associated with the NQA alarm.

Event-Entry

Number of the event.

You can run the nqa event command to configure these parameters.

Event-type

Event processing mode:
  • log: records a log.
  • trap: sends a trap to the NMS.
  • log-trap: records a log and sends a trap to the NMS.
  • linkage: triggers a linkage test instance.
  • none: does not process the event.

You can run the nqa event command to configure these parameters.

Description

Description of the event.

You can run the nqa event command to configure these parameters.

Admin-Name

Administrator of the linkage NQA test instance.

This parameter is displayed only when the event processing mode is set to linkage using the nqa event command.

Operation-Tag

Name of the linkage NQA test instance.

This parameter is displayed only when the event processing mode is set to linkage using the nqa event command.

Related Topics

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.

Format

display nqa-event

Parameters

None

Views

All views

Default Level

1: Monitoring level

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.

Example

# Display information about NQA events.

<HUAWEI> display nqa-event
NQA event information:
------------------------------------------------------
NQA Event Max: 100                  NQA Event Number: 0
------------------------------------------------------        
Table 16-65  Description of the display nqa-event command output

Item

Description

NQA Event Max

Maximum number of NQA events that the system allows.

NQA Event Number

Number of configured NQA events.

Related Topics

display nqa history

Function

The display nqa history command displays the history records about an NQA test.

Format

display nqa history [ test-instance admin-name test-name ] [ from start-date start-time to end-date end-time ]

Parameters

Parameter Description Value
test-instance Indicates NQA test instances. -
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.

start-date Specifies the start date, in the format of YYYY/MM/DD. YYYY specifies a year that ranges from 2000 to 2099; MM specifies a month that ranges from 1 to 12; DD specifies a day that ranges from 1 to 31.
start-time Specifies the start time, in the format of HH:MM:SS. HH specifies an hour that ranges from 0 to 23; MM specifies a minute that ranges from 0 to 59; SS specifies a second that ranges from 0 to 59.
end-date Specifies the end date, in the format of YYYY/MM/DD. YYYY specifies a year that ranges from 2000 to 2099; MM specifies a month that ranges from 1 to 12; DD specifies a day that ranges from 1 to 31.
end-time Specifies the end time, in the format of HH:MM:SS. HH specifies an hour that ranges from 0 to 23; MM specifies a minute that ranges from 0 to 59; SS specifies a second that ranges from 0 to 59.

Views

All views

Default Level

1: Monitoring level

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.

NOTE:

No history record about the failed UDP Jitter and ICMP Jitter test instances exist.

You cannot run the display nqa history command to check historical records about the RTP Test and RTP Snoop test instances.

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  success       10.2.1.2       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
Table 16-66  Description of the display nqa history command output

Item

Description

NQA entry(admin, ftp) history

The history records about an NQA test instance:
  • admin: administrator of an NQA test instance.

  • ftp: name of an NQA test instance.

You can run the nqa command to configure this parameter.

Index

Index of a test record.

T/H/P

  • T: Times, which indicates the sequence of the test for a test instance.

  • H: Hop, which indicates the sequence of the hop.

  • P: Probe, which indicates the sequence of the probe.

Response

Period from the time when a probe packet is sent to the time when a response packet is received.

Status

Probe status:
  • success: indicates that the probe succeeds.

  • timeout: indicates that the probe times out and no response packet is received.

  • busy: indicates that the resources are insufficient and the probe packet fails to be sent. When Status is busy, the value of the Response field is 0 ms.

  • drop: indicates that the probe packet is discarded because of no link is available. When Status is busy, the value of the Response field is 0 ms.

Address

Destination IP address of an NQA test instance.

Time

Time when the response packet is received.

Related Topics

display nqa-parameter

Function

The display nqa-parameter command displays parameters for the current NQA test instance.

Format

display nqa-parameter

Parameters

None

Views

NQA view

Default Level

1: Monitoring level

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)
 probe-failtimes                    :---(default:1)
 test-failtimes                     :---(default:1)
 tos                                :---(default:0)
 fail-percent                       :---(default:100)
 interval                           :---(default:4000)
 vpn-instance                       :
 records history                    :---(default:50)
 records result                     :---(default:5)
 agetime                            :---(default:0:0:0)
 ip-forwarding                      :---(default:no)
 nexthop-address type               :
 nexthop-address                    :
Table 16-67  Description of the display nqa-parameter command output

Item

Description

*: the parameter must be configured before starting the test-instance.

Parameters marked with asterisks (*) must be configured before the test.

#: the parameter is undecided.

Parameters marked with number signs (#) have prerequisites in the configuration.

<blank>: the parameter is optional.

Parameters without any mark are optional parameters.

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.

probe-failtimes

Number of continuous probe failures in the NQA test instance, which is set using the probe-failtimes 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 historical 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.

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.
Related Topics

display nqa results

Function

The display nqa results command displays NQA test 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.
NOTE:

Only ICMP, UDP, ICMP Jitter, and UDP Jitter test instances support the query of details.

-

Views

All views

Default Level

1: Monitoring level

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 output of the display nqa results command contains the following two parts:
  • 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 displays the statistics on accumulative results. Currently, this command supports only the UDP Jitter, ICMP Jitter, and LSP Jitter test instances.

Precautions

The display nqa results command only displays the result of a test instance that has been completed.

When NQA test result table and historical table are displayed in a split screen, latest results are displayed to improve user experience.

By default, the unit of the delay statistics field in the result table is millisecond. The timestamp-unit command specifies the unit of delay statistics fields in result tables of the UDP Jitter and ICMP Jitter test instances.

When you run the display nqa results command to check the results of a single UDP Jitter or ICMP Jitter test instance:
  • 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.
When you run the display nqa results collection command to check the accumulative results of multiple UDP Jitter or ICMP Jitter test instances:
  • 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 %      

# Display detailed results of an NQA ICMP test.

<HUAWEI> display nqa results test-instance admin icmp verbose
  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 %      
   Detailed result information:
Table 16-68  Description of the display nqa results test-instance admin icmp and display nqa results test-instance admin icmp verbose command output

Item

Description

NQA entry(admin, icmp)

NQA test items:
  • admin: indicates the administrator or creator of the NQA test instance.

  • icmp: indicates the name of the NQA test instance.

You can run the nqa command to configure this parameter.

testflag

Test flag.
  • active: indicates that the test is running.Checking the result of a running test is invalid.

  • inactive: indicates that the test is complete.At this time, the actual test result is displayed.

testtype

Test type.

You can run the test-type command to configure this parameter.

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:
  • finished: indicates that the test is complete.

  • running: indicates that the test is running.

Send operation times

Number of sent packets.

Receive response times

Number of received response packets.

Completion

Completing status of the test:
  • success: indicates that the test is complete successfully.

  • no result: indicates that the test is running, so no test result is obtained or no test result is obtained after the test.

  • failed: indicates that the test fails.

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.

You can run the destination-address command to configure this parameter.

Min/Max/Average Completion Time

Minimum/Maximum/Average time taken to complete the test.

Sum/Square-Sum Completion Time

Sum/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.

Detailed result information

Displays detailed result information.

# Display the result of an NQA UDP 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-09-01 10:47:57+08:00                                                                                            
   End time: 2014-09-01 10:48:01+08:00  
Table 16-69  Description of the display nqa results test-instance admin jitter command output

Item

Description

NQA entry(admin, jitter)

NQA test items:
  • admin: indicates the name of the administrator for an NQA test instance.

  • jitter: indicates the name of the NQA test instance.

testflag

Test flag:
  • active: indicates that the test is running. Checking the test result during the operation is invalid.

  • inactive: indicates that the test is complete. At this time, the actual test result is displayed.

testtype

Test type.

SendProbe

Number of sent probes.

ResponseProbe

Number of received response probes.

Completion

Completing status of the test:
  • success: indicates that the test is complete successfully.

  • no result: indicates that the test is running, so no test result is obtained or no test result is obtained after the test.

  • failed: indicates that the test fails.

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 Number

Number of out-of-order fragmented 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.
Start time Time when the test began.
End time Time when the test ended.

# 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
Table 16-70  Description of the display nqa results collection command output

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.

Related Topics

display nqa support-server-type

Function

The display nqa support-server-type command displays the server types supported by NQA.

Format

display nqa support-server-type

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

To view the supported NQA server types, run the display nqa support-server-type command.

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                                                
                                                                                
---------------------------------------------------- 
Table 16-71  Description of the display nqa support-server-type command output

Item

Description

NQA support server type information

Information of server types supported by NQA.

Type

Server types:
  • tcp server
  • udp server
  • rtp server

Description

Description of the server types.

display nqa support-test-type

Function

The display nqa support-test-type command displays the test instance types supported by NQA.

Format

display nqa support-test-type

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

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.

Precautions

The test-type ? command running in the test instance view has the same function as the display nqa support-test-type command.

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
  pwe3ping        PWE3PING type NQA test
  pwe3trace       PWE3TRACE type NQA test
  mtrace          MTRACE type NQA test
  macping         MACPING type NQA test
  lspjitter       LSPJITTER type NQA test
  icmpjitter      ICMPJITTER type NQA test
  pathjitter      PATHJITTER type NQA test
  rtptest         RTPTEST type NQA test
  rtpsnoop        RTPSNOOP type NQA test 
 ----------------------------------------------------
Table 16-72  Description of the display nqa support-test-type command output

Item

Description

NQA support test type information

Information of test types supported by NQA.

Type

Test types.

Description

Description of the test types.

Related Topics

display nqa-agent

Function

The display nqa-agent command displays the status and configuration of the specified or all NQA test instances on an NQA client.

Format

display nqa-agent [ admin-name test-name ] [ verbose ]

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

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

After the test instances are configured on an NQA client, run the display nqa-agent command to view the status and configuration of the specified or all NQA test instances on an NQA client.

Example

# Display the status and configuration of all NQA test instances on an NQA client.

<HUAWEI> display nqa-agent
  NQA Tests Max:2000          NQA Tests  Number:   1
  NQA Flow  Max:1000          NQA Flow Remained:1000
nqa test-instance admin icmp
 test-type icmp
 destination-address ipv4 192.168.1.2
 nqa status : normal      
Table 16-73  Description of the display nqa-agent command output

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.

nqa test-instance admin icmp

test-type icmp

destination-address ipv4 192.168.1.2

nqa status : normal

The administrator of NQA test instance icmp is admin. Configurations of this test instance include the following:
  • test-type
  • destination-address
  • nqa status

You can run the nqa command to configure an NQA test instance. Configurations of different NQA test instances are not the same. For details, see Configuring an NQA Test Instance.

Related Topics

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.

Format

display nqa-ftp-record configuration

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

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.

The display nqa-ftp-record configuration command can display details about the NQA test result saved using FTP, including the FTP server address, FTP client address, and the user name as well as password for FTP server login.

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: DISABLE    TRAP: DISABLE                                                                                               
   IP-ADDRESS:                                                                                                                      
   SOURCE-ADDRESS:                                                                                                                  
   VPN-INSTANCE:                                                                                                                    
   USERNAME:                                                                                                                        
   PASSWORD:                                                                                                                        
   FILENAME:                                                                                                                        
   ITEM-NUM:100000                                                                                                                  
   TIME:60                                                                                                                          
   DATETIMETYPE:UTC                                                                                                                 
   LAST FINISHED FILENAME: 
Table 16-74  Description of the display nqa-ftp-record configuration command output

Item

Description

FUNCTION

Whether enable the NQA test results to be sent to the FTP server using FTP.
  • ENABLE: enabled.

  • DISABLE: disabled.

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.
  • ENABLE: enabled.

  • DISABLE: disabled.

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 to which the FTP server belongs.

To set this field, run the nqa-ftp-record vpn-instance command.

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:
  • UTC: worldwide standard time type.
  • LOCAL: local time type (recommended).

LAST FINISHED FILENAME

Name of a file created at the FTP server last time.

display nqa-server

Function

The display nqa-server command displays information about NQA servers.

Format

display nqa-server

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

The display nqa-server command can display information about NQA servers, including the maximum number of configurable NQA servers and the number and types of configured NQA servers.

Example

# Display the information about NQA servers.

<HUAWEI> display nqa-server 
 NQA Server Max: 5000             NQA Server Num: 1                             
 NQA Concurrent TCP Server: 0     NQA Concurrent UDP Server: 1                  
 NQA Concurrent RTP-UDP Server: 0 NQA Concurrent RTP-TCP Server: 0

nqa-server udpecho 10.1.1.1 6000    ACTIVE
Table 16-75  Description of the display nqa-server command output

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 Concurrent RTP-TCP Server

Number of the configured RTP-TCP servers.

nqa-server

Running servers.

ACTIVE

Status of the NQA server.

display snmp-agent trap feature-name nqa all

Function

The display snmp-agent trap feature-name nqa all command displays whether the switch is enabled to send traps of NQA feature to the NMS.

Format

display snmp-agent trap feature-name nqa all

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

After running the snmp-agent trap enable feature-name nqa command to enable the function of sending traps of the NQA feature to the NMS, you can run the display snmp-agent trap feature-name nqa all command to check whether this function is enabled.

Prerequisites

SNMP has been enabled. For details, see snmp-agent.

Example

# Display whether the switch is enabled to send traps of NQA feature to the NMS.

<HUAWEI> display snmp-agent trap feature-name nqa all
------------------------------------------------------------------------------  
Feature name: NQA                                                               
Trap number : 27                                                                
------------------------------------------------------------------------------  
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                      
nqaReflectorStateChangeNotification                                             
                                on                      on                      
nqaResultsTestResultChange      on                      on                      
Table 16-76  Description of the display snmp-agent trap feature-name nqa all command output

Item

Description

Feature name

Name of the feature that generates traps.

Trap number

Number of traps generated by NQA feature.

Trap name

Name of the trap.

Default switch status

Default status of a trap:
  • on: The switch is enabled to send this trap to the NMS.
  • off: The switch is disabled to send this trap to the NMS.

Current switch status

Current status of a trap:
  • on: The switch is enabled to send this trap to the NMS.
  • off: The switch is disabled to send this trap to the NMS.

This status can be configured using the snmp-agent trap enable feature-name nqa command.

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.

Format

dns-server ipv4 ip-address

undo dns-server

Parameters

Parameter Description Value
ipv4 ip-address Specifies an IPv4 address for the DNS server. The value is in dotted decimal notation.

Views

NQA view

Default Level

2: Configuration level

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.

Example

# Set the IP address of the DNS server to 10.1.1.1 in the test named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type dns
[HUAWEI-nqa-user-test] dns-server ipv4 10.1.1.1

duration

Function

The duration command sets the duration during which an RTP test instance is performed.

The undo duration command restores the default duration for performing an RTP test instance.

By default:
  • The duration of an RTP test is 60s.
  • The duration of an RTP snoop test is 30s.

Format

duration duration

undo duration

Parameters

Parameter Description Value
duration Specifies the duration for performing an RTP test instance. The value is an integer that ranges from 1 to 1800, in seconds.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

In a telepresence video conference, the audio or video quality may degrade due to poor network conditions. To resolve this problem, perform RTP and RTP snoop tests to test the delay, jitter, and packet loss ratio of the telepresence network, locate the points of failures, and take corrective measures.

The duration duration command configures the duration of an NQA test. After the duration expires, the NAQ test instance automatically stops running.

Prerequisites

The test-type { rtptest | rtpsnoop } command must have been run to configure an RTP test instance or an RTP snoop test instance.

Example

# Configure the duration of an RTP test to be 50s.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type rtptest
[HUAWEI-nqa-user-test] duration 50
Related Topics

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.

Format

fail-percent percent

undo fail-percent

Parameters

Parameter Description Value
percent Specifies the percentage of failed probes. The value is an integer that ranges from 1 to 100.

Views

NQA view

Default Level

2: Configuration level

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.

For example, the number of sent packets set in the probe-count command is 10, but seven of them are lost during the probe test, the following situations occur:
  • 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 type of test instances that are not supported is as follows:
  • FTP
  • Trace
  • LSP Trace
  • PWE3 Trace
  • Mtrace
  • DNS
  • Path Jitter
  • RTP Test
  • RTP Snoop

Precautions

The failure percentage of a running test instance cannot be changed.

Example

# Set the percentage of the failed probes to 10% in the test named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type icmp
[HUAWEI-nqa-user-test] fail-percent 10
Related Topics

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

Format

frequency interval

undo frequency

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.

Views

NQA view

Default Level

2: Configuration level

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 once at each configured interval. Configuring the interval of periodic NQA test avoids time-consuming manual operations.

Prerequisites

The type of a test instance has been specified using the test-type command. The following types of test instances are not supported:
  • RTP test
  • RTP snoop

Configuration Impact

If the master/slave switchover is performed on the NQA client before the test instance (group) is complete, the following situations may occur:
  • If the interval for automatically performing the test is not set, the test stops after the master/slave switchover.
  • If the interval for automatically performing the test instance is set, the test is performed from the next period after the master/slave switchover.

Precautions

  • The frequency of a running test instance cannot be changed.
  • In a trace, LSP trace, or PWE3 trace test, the configured frequency must be greater than or equal to 60s.
  • The configured frequency can not be smaller than the timeout value, otherwise, the test instance will start failed. If the configured frequency is smaller than or equal to (probe-count - 1) x interval + timeout + 1, the test result may be no result. For the test instance supporting the jitter-packetnum parameter, the number of sent packets is probe-count x jitter-packetnum packets.
  • In an FTP test instance, the configured frequency must be 2s greater than the timeout value; otherwise, the FTP test instance may fail.

Example

# Set the interval at which test instance user test is automatically performed to 20 seconds.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type icmp
[HUAWEI-nqa-user-test] frequency 20

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.

Format

ftp-filename file-name

undo ftp-filename

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.

Views

NQA view

Default Level

3: Management level

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.

NOTE:

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.

Example

# Set the FTP path and file name of test instance user test to D:\abc and abc.txt respectively.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type ftp
[HUAWEI-nqa-user-test] ftp-filename D:\abc\abc.txt

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.

Format

ftp-filesize size

undo ftp-filesize

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.

Views

NQA view

Default Level

2: Configuration level

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.

Example

# Set the size of the file to 1024 bytes in the FTP upload test named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type ftp
[HUAWEI-nqa-user-test] ftp-filesize 1024

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.

Format

ftp-operation { get | put }

undo ftp-operation put

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

Views

NQA view

Default Level

2: Configuration level

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.

Example

# Perform a test named user test to obtain the FTP download speed.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type ftp
[HUAWEI-nqa-user-test] ftp-operation get

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.

Format

ftp-password { password | cipher cipher-password }

undo ftp-password

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.

  • If the password is plaintext, the length ranges from 1 to 32.
  • If the password is ciphertext, the length ranges from 32 to 68.
  • If the password length is 32 and the configured ciphertext password can be decrypted successfully, the configured ciphertext password takes effect. If the configured ciphertext password cannot be decrypted, the plaintext password is used after passing the validity check.
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 68 case-sensitive characters without spaces.

  • If the password is plaintext, the length ranges from 1 to 32.
  • If the password is ciphertext, the length ranges from 32 to 68.
  • If the password length is 32 and the configured ciphertext password can be decrypted successfully, the configured ciphertext password takes effect. If the configured ciphertext password cannot be decrypted, the plaintext password is used after passing the validity check.
NOTE:
When quotation marks are used around the string, spaces are allowed in the string.

Views

NQA view

Default Level

2: Configuration level

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.

Example

# Set the password for logging in to the FTP server to Huawei-123.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type ftp
[HUAWEI-nqa-user-test] ftp-password Huawei-123

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.

Format

ftp-username name

undo ftp-username

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.

Views

NQA view

Default Level

2: Configuration level

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.

Example

# Set the user name for logging in to the FTP server to user1.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type ftp
[HUAWEI-nqa-user-test] ftp-username user1

http-operation

Function

The http-operation command sets the operation mode for an NQA HTTP test instance.

By default, the operation mode of the HTTP test instance is GET.

Format

http-operation get

Parameters

Parameter Description Value
get Obtains data from the HTTP server. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

This command applies only to the HTTP test.

You cannot change the operation mode of a running HTTP test instance.

Example

# Set the operation mode of HTTP test instance user test to get.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type http
[HUAWEI-nqa-user-test] http-operation get
Related Topics

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.

Format

http-url deststring [ verstring ]

undo http-url

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. The total length of verstring should be equal to or shorter than 7 characters. It can be set to v1.0 or 1.1. The default HTTP version is v1.0.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

HTTP1.0 and HTTP1.1 are supported in this test instance.

Precautions

The http-url command applies only to HTTP test instances. You cannot change the URL of a running HTTP test instance.

When running the http-url command, you need to specify a domain name or a server's IP address; otherwise, the test instance fails.

Example

# Set the URL of HTTP test instance user test to http://www.example.com.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type http
[HUAWEI-nqa-user-test] http-url http://www.example.com

icmp-jitter-mode

Function

The icmp-jitter-mode command specifies the mode of an ICMP jitter test.

The undo icmp-jitter-mode command restores the default mode of an ICMP jitter test.

By default, the ICMP jitter test is in icmp-timestamp mode.

Format

icmp-jitter-mode { icmp-echo | icmp-timestamp }

undo icmp-jitter-mode

Parameters

Parameter Description Value
icmp-echo Configures the ICMP jitter test to use ICMP Echo messages. -
icmp-timestamp Configures the ICMP jitter test to use ICMP Timestamp messages. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

The icmp-jitter-mode command can only be used to configure the mode for ICMP jitter or path jitter tests.

Example

# Configure the ICMP jitter test to use ICMP Echo messages.

<HUAWEI> system-view
[HUAWEI] nqa test-instance admin icmpjitter
[HUAWEI-nqa-admin-icmpjitter] test-type icmpjitter
[HUAWEI-nqa-admin-icmpjitter] icmp-jitter-mode icmp-echo
Related Topics

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.

By default, the intervals for sending test packets in various tests are as follows:

  • For UDP Jitter, Path Jitter, and ICMP Jitter test instance, the interval is 20 milliseconds.
  • The interval is 1 second for an LSP jitter test.

  • The interval is 4 seconds for other test instances.

Format

interval { milliseconds interval | seconds interval }

undo interval

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

Views

NQA view

Default Level

2: Configuration level

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 ICMP, ICMP Jitter, Path Jitter, SNMP, LSP Jitter, LSP Ping, PWE3 Ping, TCP, UDP, or UDP Jitter test instances.

Configuration Impact

  • Packets can be sent at interval of milliseconds only in UDP Jitter, Path Jitter, or ICMP 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 UDP Jitter, Path Jitter, or ICMP 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.

Example

# Set the interval for sending test packets to 1000 milliseconds.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] interval milliseconds 1000

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.

Format

ip-forwarding

undo ip-forwarding

Parameters

None

Views

NQA view

Default Level

2: Configuration level

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.

NOTE:

Only ICMP test instances support this configuration.

If you configure both the ip-forwarding and sendpacket passroute commands, the sendpacket passroute command takes effect. Therefore, the device sends packets without searching the routing table.

Example

# Configure packets to be forwarded using IP.
<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type icmp
[HUAWEI-nqa-user-test] ip-forwarding
Related Topics

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.

Format

jitter-codec { g711a | g711u | g729a }

undo jitter-codec

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

Views

NQA view

Default Level

2: Configuration level

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 size of a jitter test packet varies with the code type.
  • If the code type is g711a, the packet size configured using the datasize size command is 172 bytes.
  • If the code type is g711u, the packet size configured using the datasize size command is 172 bytes.
  • If the code type is g729a, the packet size configured using the datasize size command is 32 bytes.

The differences between g711a, g711u, and g729a of a jitter test instance are as follows:

Table 16-77  Differences between the code types
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.

Example

# Set the code type of a simulated voice test case to g711a.

<HUAWEI> system-view
[HUAWEI] nqa test-instance admin jitter
[HUAWEI-nqa-admin-jitter] test-type jitter
[HUAWEI-nqa-admin-jitter] jitter-codec g711a

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.

Format

jitter-packetnum number

undo jitter-packetnum

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.

Views

NQA view

Default Level

2: Configuration level

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 UDP Jitter, LSP jitter, Path Jitter, and ICMP Jitter test instances.

Configuration Impact

  • In UDP Jitter, LSP jitter, Path Jitter, and ICMP 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.

Example

# Perform 3 probes in the test named user test and send 1000 packets in each probe.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] probe-count 3
[HUAWEI-nqa-user-test] jitter-packetnum 1000

local-pw-id

Function

Using the local-pw-id command, you can set the ID of the local end of a PW or a VC.

Using the undo local-pw-id command, you can delete the configured ID of the local end of a PW or a VC.

By default, local-pw-id is not configured.

Format

local-pw-id local-pw-id

undo local-pw-id

Parameters

Parameter Description Value
local-pw-id Specifies the ID of the local end of a PW or a VC.

The value is a decimal integer.

  • When the test instance is of PWE3Ping, the value of local-pw-id is an integer that ranges from 1 to 4294967295, and only the VC type of LDP is supported.
  • When the test instance is of PWE3Trace: when the VC type is LDP, the value of local-pw-id is an integer that ranges from 1 to 4294967295; when the VC type is BGP, the value of local-pw-id is an integer that ranges from 0 to 65534.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

PWE3 ping and PWE3 trace test instances can be used in the following scenarios:

Connectivity and faulty node detections for a single-hop PW. After the local-pw-id command is run in the NQA view to configure the local PW ID or VC ID, you can specify a PW for the detection.

Connectivity and faulty node detections for a multi-hop PW. After the local-pw-id command is run in the NQA view to configure the local PW ID or VC ID, you need to specify the destination address.
  • If the label-type parameter is set to control-word, run the remote-pw-id remote-pw-id command to configure the remote PW ID.
  • If the label-type parameter is set to label-alert or normal, run the destination-address ipv4 ipv4-address [ lsp-masklen masklen | lsp-masklen masklen lsp-loopback loopback-address | lsp-loopback loopback-address lsp-masklen masklen ] command to configure the destination address for PWE3 ping and PWE3 trace test instances.

Prerequisites

Before running the local-pw-id command, you must set the NQA test type to PWE3 Trace or PWE3 Ping in the NQA view.

Precautions

The local-pw-id value must be the same as the VC ID value in the display mpls l2vc command output; otherwise, the test may fail.

Example

# Set the ID of the local end of a PW to 100 in the NQA view.

<HUAWEI> system-view
[HUAWEI] nqa test-instance admin pwe3
[HUAWEI-nqa-admin-pwe3] test-type pwe3trace
[HUAWEI-nqa-admin-pwe3] local-pw-id 100
Related Topics

local-pw-type

Function

Using the local-pw-type command, you can configure the PW type of the local end.

Using the undo local-pw-type command, you can cancel setting the PW type of the local end.

By default, the PW type of the local end is Ethernet.

Format

local-pw-type local-pw-type

undo local-pw-type

Parameters

Parameter Description Value
local-pw-type Specifies the PW type of the local end. Currently, encapsulation types ethernet, ip-interworking and vlanare supported. By the default, the value is ethernet.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The local-pw-type command is used to configure a PW encapsulation type for the local PE. The PW encapsulation type configured for the local PE must be the same as the PW encapsulation type for the remote PE.

Prerequisites

Before configuring the local-pw-type command, configure the test type of NQA test instances as PWE3 trace or PWE3 ping in the NQA view.

Precautions

The local-pw-type value must be the same as the VC type value in the display mpls l2vc command output; otherwise, the test may fail.

Example

# In the NQA view, configure the local pw-type as VLAN.

<HUAWEI> system-view
[HUAWEI] nqa test-instance admin pwe3
[HUAWEI-nqa-admin-pwe3] test-type pwe3trace
[HUAWEI-nqa-admin-pwe3] local-pw-type vlan
Related Topics

label-type

Function

Using the label-type command, you can configure the label type.

Using the undo label-type command, you can cancel the operation of configuring the label type.

By default, the label type is control-word.

Format

label-type { control-word | { label-alert | normal } [ no-control-word ] }

undo label-type

Parameters

Parameter Description Value
control-word Indicates that the control word option is encapsulated in MPLS Echo Request packets. -
label-alert Indicates that the router alert option is encapsulated in MPLS Echo Request packets. -
normal Indicates that neither control words nor router alert options are encapsulated in MPLS Echo Request packets. -
no-control-word Indicates that the control word option is not encapsulated in MPLS Echo Request packets. This parameter can be used in NQA PWE3 ping and NQA PWE3 trace tests. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The usage scenarios of the label types are as follows:

  • control-word:

    • If the encapsulation type is set to control-word, at a switch node on a multi-hop PW, the MPLS Echo Request packets are not delivered to the CPU for processing until the TTL of the label times out. In this case, the source obtains little PW information. This type, however, ensures system performance and the source cannot learn information on the downstream interfaces of the switch node. You should use this type when there are a great number of packets.

    • Only control-word is supported when the vc-type is BGP and lsp-version is draft6.
  • label-alert:

    • If the encapsulation type is set to label-alert, at a switch node on a multi-hop PW, the MPLS Echo Request packets are delivered to the CPU for processing. In this case, the source can obtain more PW information. The system performance is greatly affected when there are a great number of packets. You can use this type to obtain details about the switch node when test instances are few.

    • Only control-word or label-alert is supported when the vc-type is BGP and lsp-version is rfc4379.
  • In the case that a device communicates with Huawei devices running earlier versions and the label alert or normal mode is adopted, the no-control-word option must be carried in the test packets.

  • normal is unsupported when the lsp-version is draft6.

Prerequisites

Before running the label-type command, you must set the test type to PWE3 Trace or PWE3 Ping in the NQA view; otherwise, label-type cannot be specified.

Precautions

The label-type value must be the same as the local VCCV value in the display mpls l2vc command output; otherwise, the test may fail.

Example

# Configure the encapsulation type of test packets as label-alert in the NQA view.

<HUAWEI> system-view
[HUAWEI] nqa test-instance admin pwe3
[HUAWEI-nqa-admin-pwe3] test-type pwe3trace
[HUAWEI-nqa-admin-pwe3] label-type label-alert
Related Topics

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.

Format

lsp-exp exp

undo lsp-exp

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.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The MPLS experimental bits (EXP) field is a 3-bit field in the MPLS header used to mark the precedence of MPLS packets.

Test packets are added to different queues according to their LSP EXP values, so that
  • 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.

Example

# Set the LSP EXP value to 5.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type lspping
[HUAWEI-nqa-user-test] lsp-exp 5
Related Topics

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.

Format

lsp-nexthop nexthop-ip-address

undo lsp-nexthop

Parameters

Parameter Description Value
nexthop-ip-address Specifies the next hop address. It is in dotted decimal notation.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Two conditions must be meet before you use the command: You can use the lsp-nexthop command to configure the IP address of the next hop. Test instance type supported as following:
  • LSP Ping
  • LSP Trace
  • LSP Jitter

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 
Related Topics

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 }

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. Meanwhile, the NQA test instance fails because the client does not receive response packets.

udp Indicates that IPv4/IPv6 UDP packets are used to respond to the LSP test. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Using the lsp-replymode command, you can set the reply mode for the LSP test. The supported test instance are:
  • LSP Ping
  • LSP Trace
  • LSP Jitter
  • PWE3 Ping
  • PWE3 Trace

Precautions

lsp-replymode no-reply indicates the unidirectional test. If the client displays timeout, it indicates that the test succeeds; or the client displays that the LSP is non-existent.

You cannot change the reply mode of the currently performed LSP test.

Example

# Set the reply mode of the test named user test to sending UDP packets.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type lspping
[HUAWEI-nqa-user-test] lsp-replymode udp
Related Topics

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.

Format

lsp-tetunnel tunnel interface-number [ hot-standby | primary ]

undo lsp-tetunnel

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

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Hot standby: An ordinary backup CR-LSP is set up immediately after a primary CR-LSP is set up. The ordinary backup CR-LSP takes over traffic if the primary CR-LSP fails. After the primary CR-LSP recovers, traffic switches back.

CR-LSP backup can be configured to allow traffic to switch from a primary CR-LSP to a backup CR-LSP, providing end-to-end protection.

An NQA LSP test instance can check the reachability of the following LSPs and collect SLA statistics:
  • MPLS TE tunnel: Run the lsp-tetunnel interface-type interface-number command to configure an interface number for an MPLS TE tunnel.
  • Hot-standby MPLS CR-LSP: Run the lsp-tetunnel interface-type interface-number hot-standby command to configure an interface number for a hot-standby MPLS CR-LSP.
  • Primary MPLS TE tunnel: Run the lsp-tetunnel interface-type interface-number primary command to configure an interface number for a primary MPLS TE tunnel.

Prerequisites

Before using the lsp-tetunnel command to configure the TE tunnel in an NQA LSP test instance, perform the following operations:

  • Run the interface tunnel interface-number command to create a tunnel interface.
  • Run the lsp-type te command to set the NQA LSP test type to TE.

Precautions

LSP Jitter test instances cannot test the hot-standby tunnel of a TE tunnel.

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 1
[HUAWEI-Tunnel1] 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 1

# Configure the CR-LSP hot-standby tunnel of the test named user test.

<HUAWEI> system-view
[HUAWEI] interface tunnel 1
[HUAWEI-Tunnel1] 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 1 hot-standby
Related Topics

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.

Format

lsp-type { ipv4 | te | ipv4-vpn }

undo lsp-type

Parameters

Parameter Description Value
ipv4 Sets the test type to IPv4 LSP ping/trace/jitter. -
te Sets the type to LSP ping/trace/jitter of the TE tunnel. -
ipv4-vpn

Sets the LSP test type to IPv4 L3VPN.

-

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

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, LSP trace, or LSP jitter.
  • If the LSP test type is set to TE, the NQA test instance type must be set to LSP ping, LSP trace, or LSP jitter.
  • 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.

After the lsp-type command is configured, the destination-address, lsp-tetunnel, and lsp-version commands cannot be configured.

Example

# Set the type of the test named user test to Ipv4 LSP ping.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type lspping
[HUAWEI-nqa-user-test] lsp-type ipv4
Related Topics

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.

Format

lsp-version { rfc4379 | draft6 }

undo lsp-version

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

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

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, lsptrace, lspjitter, pwe3ping, or pwe3trace in the test-type command.

NOTE:
The protocol adopted by a running LSP test instance cannot be changed.

Example

# Configure the LSP test instance to use the protocol defined in RFC 4379.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type lspping
[HUAWEI-nqa-user-test] lsp-version rfc4379
Related Topics

md

Function

Using the md command, you can specified the Maintenance Domain (MD) and Maintenance Association (MA) of the NQA test packet to be sent. This command takes effect only in the MAC Ping test instance.

Using the undo md command, you can remove the specified MD from the NQA test packet to be sent.

By default, no MD is specified.

Format

md md-name ma ma-name

undo md

Parameters

Parameter Description Value
md-name Specifies an MD. The value is a string of 1 to 43 case-sensitive characters without spaces.
ma-name Specifies an MA. The value is a string of 1 to 43 case-sensitive characters without spaces.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

You can use this command to specify the MD and MA of an MAC Ping test instance. This command has the same effect as the operation of checking the connectivity fault in the MA view. Before running this command, you need to create an MD and MA, and set the test type to macping.

You cannot modify the MD and MA when the test instance is running. The total length of ma-name and md-name combination cannot be greater than 44 characters.

Example

# Set the test type of an NQA test instance to MAC Ping and specify the MD name to "mdcustome" and the MA name to "macustomer".

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type macping
[HUAWEI-nqa-user-test] md mdcustomer ma macustomer
Related Topics

mep

Function

Using the mep command, you can configure the MEP ID for an NQA test instance.

Using the undo mep command, you can delete the MEP ID configured for an NQA test instance.

By default ,the MEP ID for an NQA test instance is 0.

Format

mep mep-id mep-id

undo mep

Parameters

Parameter Description Value
mep-id Specifies the MEP ID of an NQA test instance. The value is an integer ranging from 1 to 8191.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Before starting an NQA test instance, you need to run the mep-id mep-id command to configure the EOAM module. Otherwise, the normal operation of the NQA test instance will be affected.

This command is available for NQA MAC ping test instances.

Example

# Set the MEP ID of an NQA MAC ping test instance to 1.

<HUAWEI> system-view
[HUAWEI] nqa test-instance test macping
[HUAWEI-nqa-test-macping] test-type macping
[HUAWEI-nqa-test-macping] mep mep-id 1
Related Topics

mtrace-source-address

Function

Using the mtrace-source-address command, you can set the IP address of a multicast source in an NQA Mtrace test.

Using the undo mtrace-source-address command, you can restore the default setting.

By default, the IP address of a multicast source is not specified in an NQA Mtrace test.

Format

mtrace-source-address ipv4 ip-address

undo mtrace-source-address

Parameters

Parameter Description Value
ipv4 ip-address Indicates the unicast Ipv4 address of a multicast source. It is in dotted decimal notation. The address cannot be configured as the loopback address 127.0.0.1.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

In NQA Mtrace tests, you must specify the IP address of a multicast source.

You can run this command only in NQA Mtrace tests. You cannot modify the IP address of a multicast source when an NQA Mtrace test is being performed.

Example

# Configure the IP address of a multicast source in an NQA Mtrace test named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type mtrace
[HUAWEI-nqa-user-test] mtrace-source-address ipv4 192.168.0.1

# Remove the IP address of a multicast source configured in an NQA Mtrace test named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type mtrace 
[HUAWEI-nqa-user-test] undo mtrace-source-address 

mtrace-last-hop-address

Function

Using the mtrace-last-hop-address command, you can configure the IP address of the last hop in an NQA Mtrace test.

Using the undo mtrace-last-hop-address command, you can restore the default setting.

By default, the IP address of the last hop is not specified in an NQA Mtrace test.

Format

mtrace-last-hop-address ipv4 ip-address

undo mtrace-last-hop-address

Parameters

Parameter Description Value
ipv4 ip-address Specifies the unicast IPv4 address of the last hop. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

If the sending mode of IGMP Tracert Query packets is set to last-hop, this parameter must be configured.

Example

# Configure the IP address of the last hop in an NQA Mtrace test named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type mtrace
[HUAWEI-nqa-user-test]mtrace-last-hop-address ipv4 192.168.0.1

# Remove the IP address of the last hop configured in an NQA Mtrace test named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type mtrace
[HUAWEI-nqa-user-test] undo mtrace-last-hop-address

mtrace-group-address

Function

Using the mtrace-group-address ipv4 command, you can set the IP address of a traced multicast group in an NQA Mtrace test.

Using the undo mtrace-group-address command, you can restore the default setting.

By default, the IP address of a traced multicast group is not set in an NQA Mtrace test.

Format

mtrace-group-address ipv4 ip-address

undo mtrace-group-address

Parameters

Parameter Description Value
ipv4 ip-address Indicates the unicast Ipv4 address of a traced multicast group. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Run this command according to the type of the path to be traced:

If the type of the path to be traced is an RPF path, you need not specify the group address to be traced.

If the type of the path to be traced is a (S, G) entry, you must specify the group address to be traced.

Example

# Configure the IP address of a traced multicast group in an NQA Mtrace test named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type mtrace
[HUAWEI-nqa-user-test] mtrace-group-address ipv4 225.1.1.1

# Remove the IP address of a traced multicast group configured in an NQA Mtrace test named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type mtrace 
[HUAWEI-nqa-user-test] undo mtrace-group-address 

mtrace-response-address

Function

Using the mtrace-response-address command, you can configure the destination IP address of an IGMP Tracert Response packet.

Using the undo mtrace-response-address command, you can restore the default setting.

By default, the destination multicast IP address is 224.0.1.32, and the TTL is 64.

Format

mtrace-response-address ipv4 ip-address [ ttl value ]

undo mtrace-response-address

Parameters

Parameter Description Value
ipv4 ip-address Indicates the destination IP address of a Response packet. The value is in dotted decimal notation.The destination address can be either a unicast IPv4 address or a multicast IPv4 address.
ttl value Indicates the TTL of a Response packet. The TTL value is an integer that ranges from 1 to 255.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

The following IP addresses can be destination IP addresses of IGMP Tracert Response packets:

  • IP address (a IPv4 unicast address) of the local querier

  • IP address of the traced multicast group, which is applicable only when the querier resides in a multicast distribution tree

Example

# Set the response address of the NQA Mtrace test named user test to a local interface address 10.1.1.1.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type mtrace
[HUAWEI-nqa-user-test] mtrace-response-address ipv4 10.1.1.1

# Set the response address of the NQA Mtrace test named user test to a traced group address 225.1.1.1 and the TTL of the Response packet to 10.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type mtrace
[HUAWEI-nqa-user-test] mtrace-response-address ipv4 225.1.1.1 ttl 10

# Set the response address of the NQA Mtrace test named user test to the default address 224.0.1.32 and the TTL of the Response packet to 10.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type mtrace
[HUAWEI-nqa-user-test] mtrace-response-address ipv4 224.0.1.32 ttl 10

# Restore the default response address 224.0.1.32 of the NQA Mtrace test named user test and the TTL of the Response packet to 64.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] undo mtrace-response-address 

mtrace-query-type

Function

The mtrace-query-type command configures the query type of an NQA Mtrace test, that is, the mode in which IGMP Tracert Query packets are sent.

The undo mtrace-query-type command restores the default setting.

By default, the query type is multicast-tree.

Format

mtrace-query-type { all-router | last-hop | destination | multicast-tree }

undo mtrace-query-type

Parameters

Parameter Description Value
all-router Indicates that a querier is directly connected to a destination host. -
last-hop Indicates that the address of the last hop is known and the last hop is reachable through unicast routes. -
destination Indicates that the network segment where the destination host resides is reachable through unicast routes. -
multicast-tree Indicates that a querier is on the multicast path from the multicast source to the destination host. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

The applicable environment of each query type is as follows:

  • all-router

    The querier is directly connected to a destination host.

  • last-hop

    If last-hop is specified, you must first run the mtrace-last-hop-address command to configure the IP address of the last hop.

    The querier encapsulates an IGMP Tracert Query packet in a multicast packet, with the destination address being 224.0.0.2. It sends the multicast packet across the local network segment and the last hop identifies and receives the multicast packet.

  • destination

    The querier encapsulates an IGMP Tracert Query packet in a common unicast packet and determines whether the last hop is directly connected with the receiver.

  • multicast-tree

    The querier encapsulates an IGMP Tracert Query packet in a (S, G) data packet and sends the packet to the last hop along the multicast distribution tree.

Example

# Set the query type for the NQA Mtrace test named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type mtrace
[HUAWEI-nqa-user-test] mtrace-query-type last-hop

# Restore the query type for the NQA Mtrace test named user test to multicast-tree.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] undo mtrace-query-type

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.

Format

nexthop ipv4 ip-address

undo nexthop

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.

Views

NQA view

Default Level

2: Configuration level

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

After you configure a next hop address for an NQA ICMP test instance, the test instance packets will be sent based on the address.

You can also run the source-interface command to specify an outbound interface through which the NQA ICMP test instance packets are sent to the specified next hop address. To guarantee that the test packets are sent, the following two conditions must be met:

  • The specified next hop address matches the outbound interface.
  • The specified outbound interface cannot be the member interface of a logical interface.

Example

# Configure a next hop address for NQA ICMP test packets.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type icmp
[HUAWEI-nqa-user-test] nexthop ipv4 10.1.1.1

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

Views

System view

Default Level

2: Configuration level

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 except the running test instance will be deleted.

Precautions

A running test instance cannot be deleted.

Example

# Create a test named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test]
Related Topics

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.

The value must be the name of an existing NQA test instance administrator.

test-name Specifies the name of the linkage test instance.

The value must be the name of an existing NQA test instance administrator.

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.

Views

System view

Default Level

2: Configuration level

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.

When an event occurs, you can process the event associated with the NQA alarm in the following ways:
  • 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.

Follow-up Procedure

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.

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

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.

Example

# Associate event table 1 with linkage test instance icmp.
<HUAWEI> system-view
[HUAWEI] nqa event 1 linkage admin icmp

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.

Format

nqa-ftp-record enable

undo nqa-ftp-record enable

Parameters

None

Views

System view

Default Level

2: Configuration level

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.

Example

# Enable the device to send test results to the FTP server using FTP.

<HUAWEI> system-view
[HUAWEI] nqa-ftp-record enable

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.

Format

nqa-ftp-record filename filename

undo nqa-ftp-record filename

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.

Views

System view

Default Level

2: Configuration level

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.

NOTE:

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.

Example

# Save test results to the file named a.

<HUAWEI> system-view
[HUAWEI] nqa-ftp-record filename a

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.

Format

nqa-ftp-record ip-address ip-address

undo nqa-ftp-record ip-address

Parameters

Parameter Description Value
ip-address Specifies an IP address for the FTP server. The IP address is in dotted decimal notation.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

During the FTP transmission, ensure the connectivity of the FTP connection. If the FTP connection fails and the buffer of the test result is full, the test result that is saved for the longest time in the buffer is deleted.

Example

# Configure NQA test results to be sent to 10.1.1.8 using FTP.

<HUAWEI> system-view
[HUAWEI] nqa-ftp-record ip-address 10.1.1.8

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.

Format

nqa-ftp-record item-num item-number

undo nqa-ftp-record item-num

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.

Views

System view

Default Level

2: Configuration level

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 an interval at which a test result is stored expires, a new file is also created on the FTP server by the sequence number to store the NQA test results. If both the nqa-ftp-record time and nqa-ftp-record item-num commands are configured, the following situations occur:
  • 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 saved 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 saved reaches the configured interval, a new file is created and the subsequent test results are saved to the new file.

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.

If the nqa-ftp-record enable command has been executed, the nqa-ftp-record item-num command cannot be used.

Example

# Set the number of NQA test results that can be saved to a file on the FTP server to 10010.

<HUAWEI> system-view
[HUAWEI] nqa-ftp-record item-num 10010

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.

Format

nqa-ftp-record password { password | cipher cipher-password }

undo nqa-ftp-record password

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.

  • If the password is in plain text, the length of the password ranges from 1 to 32.
  • If the password is in cipher text, the length of the password ranges from 32 to 68.
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.

  • If the password is in plain text, the length of the password ranges from 1 to 32.
  • If the password is in cipher text, the length of the password ranges from 32 to 68.
  • If the password length is 32 and the configured ciphertext password can be decrypted successfully, the configured ciphertext password takes effect. If the configured ciphertext password cannot be decrypted, the plaintext password is used after passing the validity check.
NOTE:
When quotation marks are used around the string, spaces are allowed in the string.

Views

System view

Default Level

2: Configuration level

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.

Example

# Set the password for logging in to the FTP server to Huawei-123.

<HUAWEI> system-view
[HUAWEI] nqa-ftp-record password Huawei-123

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.

Format

nqa-ftp-record time time

undo nqa-ftp-record time

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.

Views

System view

Default Level

2: Configuration level

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.

In addition, if the number of test results stored in a file on the FTP server reaches the configured number, a new file is also created on the FTP server by the sequence number to store the NQA test results. If both the nqa-ftp-record time and nqa-ftp-record item-num commands are configured, the following situations occur:
  • 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.

If the nqa-ftp-record enable command has been executed, the nqa-ftp-record time command cannot be used.

Example

# Set the interval at which NQA test results are saved to 10 minutes.

<HUAWEI> system-view
[HUAWEI] nqa-ftp-record time 10

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.

Format

nqa-ftp-record trap-enable

undo nqa-ftp-record trap-enable

Parameters

None

Views

System view

Default Level

2: Configuration level

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.

Prerequisites

Before using nqa-ftp-record trap-enable command, run the snmp-agent target-host trap command to configure a host to which the switch sends traps.

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.

Example

# Configure traps to be sent to the NMS using FTP after the NQA test result is saved.

<HUAWEI> system-view
[HUAWEI] nqa-ftp-record trap-enable
Related Topics

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 command cancels the configuration of the FTP client address.

By default, the address of the FTP client from which NQA test results are uploaded to the FTP server is not configured.

Format

nqa-ftp-record source-address ip-address

undo nqa-ftp-record source-address

Parameters

Parameter Description Value
ip-address Specifies an FTP client address. The value is in dotted decimal notation.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

To specify the address of the FTP client from which NQA test results are uploaded to the FTP server in a scenario that has client address restrictions, run the nqa-ftp-record source-address command.

Example

# Configure 10.2.2.8 as the address of the FTP client from which NQA test results are uploaded to the FTP server.

<HUAWEI> system-view
[HUAWEI] nqa-ftp-record source-address 10.2.2.8

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.

Format

nqa-ftp-record username username

undo nqa-ftp-record username

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.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

The user name configured for logging in to the FTP server where NQA test results are saved must be an existing user name on the FTP server.

Example

# Set the user name for logging in to the FTP server to ftp.

<HUAWEI> system-view
[HUAWEI] nqa-ftp-record username ftp

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.

Format

nqa-ftp-record vpn-instance vpn-instance

undo nqa-ftp-record vpn-instance

Parameters

Parameter Description Value
vpn-instance Specifies the name of the VPN instance to which the FTP server belongs. The value must be an existing VPN instance name.

Views

System view

Default Level

2: Configuration level

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.

Example

# Configure VPN instance v1 to send NQA test results.

<HUAWEI> system-view
[HUAWEI] nqa-ftp-record vpn-instance v1

nqa-jitter tag-version

Function

The nqa-jitter tag-version command sets the packet version for a UDP Jitter test instance.

The undo nqa-jitter tag-version command restores the default packet version for a UDP Jitter test instance.

By default, the packet version of a UDP Jitter test instance is 1.

Format

nqa-jitter tag-version version-number

undo nqa-jitter tag-version

Parameters

Parameter Description Value
version-number Specifies the packet version for a UDP Jitter test instance. The value can be 1 or 2.

Views

System view

Default Level

2: Configuration level

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 UDP Jitter test instance has been configured, running the nqa-jitter tag-version command will override the previous configuration.

Precautions

No matter the version number of the UDP Jitter test packet is 1 or 2, you need to run the nqa-server udpecho command to configure the NQA server. Otherwise, the UDP Jitter test instance will fail due to timeout.

Example

# Set the packet version of a UDP Jitter test instance to 2.

<HUAWEI> system-view
[HUAWEI] nqa-jitter tag-version 2

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.
NOTE:
This parameter is invalid when a loopback address is specified as the RTP server address.
The value must be an existing VPN instance name.
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. -

Views

System view

Default Level

2: Configuration level

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.

Example

# Configure an RTP UDP server for an NQA test instance.

<HUAWEI> system-view
[HUAWEI] nqa-server rtp-udp 10.10.10.2 2500

nqa-server rtp-tcp

Function

The nqa-server rtp-tcp command configures the RTP TCP server for an NQA test instance.

The undo nqa-server rtp-tcp command deletes the RTP TCP server for an NQA test instance.

By default, no TCP server is configured for an NQA test instance.

Format

nqa-server rtp-tcp [ vpn-instance vpn-instance-name ] ip-address port-number

undo nqa-server rtp-tcp { [ vpn-instance vpn-instance-name ] ip-address port-number | all }

Parameters

Parameter Description Value
vpn-instance vpn-instance-name Indicates the name of the VPN instance to which the RTP TCP server belongs.
NOTE:
This parameter is invalid when a loopback address is specified as the RTP server address.
The value must be an existing VPN instance name.
ip-address Specifies the IP address listened by the RTP TCP server. The value is in dotted decimal notation.
port-number Specifies the source port number configured on the TCP server. The value is an integer ranging from 1025 to 65535.
all Specifies all RTP TCP servers for an NQA test instance. -

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

In a telepresence video conference, the audio or video quality may degrade due to poor network conditions. To resolve this problem, run the nqa-server rtp-tcp command to configure a TCP server on the intermediate and destination nodes to test the delay of the telepresence network, locate the points of failures, and take corrective measures.

Example

# Configure an RTP TCP server for an NQA test instance.

<HUAWEI> system-view
[HUAWEI] nqa-server rtp-tcp 10.10.10.2 2000

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 must be an existing VPN instance name.
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.

Views

System view

Default Level

2: Configuration level

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.

Perform the following steps on the client to configure TCP server parameters:
  • 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.

Example

# Create a TCP server for an NQA test instance with the IP address as 10.10.10.1 and the port number as 5000.

<HUAWEI> system-view
[HUAWEI] nqa-server tcpconnect 10.10.10.1 5000

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 ] { ip-address | ipv6 ipv6-address } port-number

undo nqa-server udpecho { [ vpn-instance vpn-instance-name ] { 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. -

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

This command is used on a UDP server.

UDP packets are transmitted in a UDP 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 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 client and the server are connected through a VPN, you need to specify the VPN instance name.

No matter the version number of the UDP Jitter test packet is 1 or 2, you need to configure the NQA server. Otherwise, the UDP Jitter test instance will fail due to timeout.

Example

# Create an NQA UDP monitoring server with the IP address 10.10.10.2 and the port number 6000.

<HUAWEI> system-view
[HUAWEI] nqa-server udpecho 10.10.10.2 6000

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.

The default time type based on which NQA test results are uploaded to the server is Coordinated Universal Time (UTC).

Format

nqa upload statistics datetime-type { utc | local }

undo nqa upload statistics datetime-type

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.

-

Views

System view

Default Level

2: Configuration level

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.

NOTE:
  • 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.

Example

# Change the time type based on which NQA test results are uploaded to the server to local time.

<HUAWEI> system-view
[HUAWEI] nqa upload statistics datetime-type local

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.

Format

probe-count number

undo probe-count

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.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

An NQA test consists of multiple probes. By default, if one or more probes are successful in an NQA test, the test is considered successful. If all probes fail, the test is considered a failure. The number of probes in an NQA test is based on the network quality.
  • 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.
You can also detect the network quality based on statistics obtained from multiple probes. For example,
  • 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. The type of test instances that are not supported is as follows:
  • Mtrace
  • RTP Test
  • RTP Snoop
  • FTP
  • DNS

Configuration Impact

  • In UDP Jitter test instances, ICMP Jitter test instances, Path Jitter test instances, LSP 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 of a running test instance cannot be changed.

Example

# Set the number of probes to 6 in NQA test instance user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] probe-count 6

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.

Format

probe-failtimes times

undo probe-failtimes

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.

Views

NQA view

Default Level

2: Configuration level

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. The type of test instances that are not supported is as follows:
  • Mtrace
  • RTP test
  • RTP snoop
  • path jitter

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, you are advised to set probe-failtimes to 1; otherwise, traps cannot be sent.

If the test instance supports probe-count, you are advised to set probe-failtimes to be smaller or equivalent to probe-count; otherwise, traps cannot be sent.

Example

# Set the number of continuous probe failures to 10 in the test named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type tcp
[HUAWEI-nqa-user-test] probe-failtimes 10
Related Topics

protocol-type

Function

The protocol-type command sets the protocol type for an NQA test.

The undo protocol-type command deletes the protocol type of an NQA test.

By default, protocol type is UDP.

Format

protocol-type { udp | tcp }

undo protocol-type

Parameters

Parameter Description Value
udp Indicates the UDP protocol. -
tcp Indicates the TCP protocol. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The Telepresence conference system requires high network quality. Low network quality affects user experience. Detecting the Telepresence network before holding a Telepresence conference helps locate the faulty node.

Before starting an RTPsnoop test instance, run the protocol-type command to set the protocol type for the NQA test instance.

Prerequisites

Run the test-type { rtptest | rtpsnoop } command to configure an RTP test instance or RTP snoop test instance.

Example

# Set the protocol type of an NQA RTPsnoop test instance to UDP.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type rtpsnoop
[HUAWEI-nqa-user-test] protocol-type udp
Related Topics

rate

Function

The rate command configures the RTP test flows.

The undo rate command restores the default settings of RTP test flows.

By default:
  • The rate of the RTP test flow is 640 bit/s.
  • The size of the RTP test packet is 80 bytes.
  • The interval at which RTP test packets are sent is 1 ms.

Format

rate { rate | packet-size packet-size interval interval-value }

undo rate

Parameters

Parameter Description Value
rate Specifies the rate at which RTP test flows are sent. The value is an integer that ranges from 640 to 10000000, in bit/s. The default value is 640.
packet-size packet-size Specifies the size of the RTP test packet. The value is an integer that ranges from 80 to 1250, in bytes. The default value is 80.
interval interval-value Specifies the interval at which RTP test packets are sent. The value is an integer that ranges from 1 to 1000, in milliseconds. The default value is 1 ms.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Incomplete pictures or voice delay may occur during a Telepresence conference because of the unstable network. An RTP test instance can be configured to detect the delay, packet loss ratio, and jitter, which helps locate the faulty node. This facilitates network maintenance and improves Telepresence conference experience.

After an RTP test instance is configured at the source end, you can run the rate command to set the rate at which RTP test flows are sent, the size of RTP test packets, and the interval at which RTP test packets are sent.

Only two parameters among rate, packet-size, and interval-value need to be set. The third parameter is calculated using any one of the following formulas:

  • R = P x 8 x 1000/I
  • P = R x I/(8 x 1000)
  • I = P x 8 x 1000/R

In the preceding formulas, R indicates rate, in bit/s; P indicates packet size, in bytes; I indicates interval, in milliseconds.

If the calculated rate, packet size, or interval is greater than the upper threshold or smaller than the lower threshold, the upper threshold or lower threshold is used.

Prerequisites

An RTP test instance has been configured using the test-type rtptest command.

Example

# Set the size of the RTP test packet to 1000 bytes and the interval at which RTP test packets are sent to 20 ms.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type rtptest
[HUAWEI-nqa-user-test] rate packet-size 1000 interval 20
Related Topics

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.

Format

records { history number | result number }

undo records { history | result }

Parameters

Parameter Description Value
history number Specifies the maximum number of history records.

The value is an integer that ranges from 0 to 1000. 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.

Views

NQA view

Default Level

2: Configuration level

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. The type of test instances that are not supported is as follows:
  • RTP Test
  • RTP Snoop

This configuration of a running test instance cannot be changed.

Example

# Set the maximum number of history records to 30 for test instance user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] records history 30

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.

Format

remote-pw-id remote-pw-id

undo remote-pw-id

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.

  • In the case of a PWE3 ping test instance, the value of remote-pw-id is an integer that ranges from 1 to 4294967295, and only the VC type of LDP is supported. The default value is 0, indicating that the ID of the remote end of a PW is not configured.
  • In the case of a PWE3 trace: if the VC type is LDP, the value of remote-pw-id is an integer that ranges from 1 to 4294967295. The default value is 0; if the VC type is BGP, the value of remote-pw-id is an integer that ranges from 0 to 65534.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Before running the remote-pw-id command, you must set the test type to PWE3 Trace or PWE3 Ping in the NQA view.

Precautions

You cannot configure the remote-pw-id command after setting lsp-version to rfc4379.

The remote-pw-id value must be the same as the VC ID value in the display mpls l2vc remote-info verbose command output; otherwise, the test may fail.

Example

# In the NQA view, configure the ID of the remote end of a PW to 100, the administrator to admin, and the test type to PWE3 trace.

<HUAWEI> system-view
[HUAWEI] nqa test-instance admin pwe3
[HUAWEI-nqa-admin-pwe3] test-type pwe3trace
[HUAWEI-nqa-admin-pwe3] remote-pw-id 100
Related Topics

restart (NQA view)

Function

The restart command restarts the current running test instance.

Format

restart

Parameters

None

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Function of the restart command is the same as that of the start now command.

Example

# Restart the test instance named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] destination-port 8000
[HUAWEI-nqa-user-test] destination-address ipv4 10.1.1.1
[HUAWEI-nqa-user-test] restart
Related Topics

sampling-frequency

Function

The sampling-frequency command sets the sampling frequency for NQA RTPsnoop test instances.

The undo sampling-frequency command restores the default sampling frequency for NQA RTPsnoop test instances.

By default, the sampling frequency for NQA RTPsnoop test instances is 1 Hz.

Format

sampling-frequency sample-value

undo sampling-frequency

Parameters

Parameter Description Value
sample-value Specifies the sampling frequency for NQA RTPsnoop test instances. The value is an integer that ranges from 1 to 1000, in Hz. The default value is 1.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Incomplete or unclear pictures may occur during a Telepresence conference because of the unstable network. An RTPsnoop test instance can be configured to detect the packet loss ratio and jitter, which helps locate the faulty node. This facilitates network maintenance and improves Telepresence conference experience.

After configuring RTPsnoop test instances on the transit and destination nodes, you can run the sampling-frequency command to set the sampling frequency for the RTPsnoop test instances.

Prerequisites

An RTPsnoop test instance has been configured using the test-type rtpsnoop command.

Precautions

During an NQA RTP snoop test, the sender of RTP flows collects test results using millisecond as the time unit. To ensure correct test results, set the sampling frequency to 1 kHz or retain the default value on the snooper. During a Telepresence conference, set the sampling frequency on the snooper according to the traffic volume on the sender.

Example

# Set the sampling frequency to 100 Hz for NQA RTPsnoop test instances.

<HUAWEI> system-view
[HUAWEI] nqa test-instance admin rtpsnoop
[HUAWEI-nqa-admin-rtpsnoop] test-type rtpsnoop
[HUAWEI-nqa-admin-rtpsnoop] sampling-frequency 100
Related Topics

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.

Format

sendpacket passroute

undo sendpacket passroute

Parameters

None

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The type of a test instance has been specified using the test-type command. The type of test instances that are supported is as follows:
  • ICMP
  • TCP
  • UDP
  • HTTP
  • UDP Jitter
  • FTP
  • SNMP
  • Trace

Precautions

You cannot change this configuration of a running test instance.

If you configure both the sendpacket passroute and source-interface commands, the source-interface command takes effect. In this scenario, packets are sent from the interface specified using the source-interface command.

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.

Example

# Enable test packets to be sent without searching the routing table.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] sendpacket passroute
Related Topics

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:
  • The one-way delay (OWD) exceeds the threshold.
  • The RTD exceeds the threshold.
  • NQA probes fail.
  • An NQA test succeeds.
  • NQA tests fail.
-
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 UDP Jitter test instances and ICMP 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 UDP Jitter test instances and ICMP 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 the UDP Jitter and ICMP 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.

NOTE:

The parameter is configured only for UDP Jitter test instance and ICMP Jitter test instance.

-
jitter-ds

Indicates that a trap is sent when the jitter from the destination to the source exceeds the threshold.

NOTE:

The parameter is configured only for UDP Jitter test instance and ICMP Jitter test instance.

-
testresult-change

Indicates that a trap is sent when the probe result changes.

NOTE:

This function supports only ICMP test instances.

-

Views

NQA view

Default Level

2: Configuration level

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 device sends traps to the NMS in any of the following situations:
  • 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.

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 type of test instances that are not supported is as follows:
  • Mtrace
  • RTP Test
  • RTP Snoop
  • Path Jitter

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 command; otherwise, traps cannot be sent to the NMS.

Precautions

You cannot change this configuration of a running test instance.

Example

# Configure the test instance user test to send a trap when the test fails.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] send-trap testfailure

sender-address

Function

The sender-address command configures the source IP address in the multi-hop PW scenario.

The undo sender-address command restores the default setting.

By default, no source IP address is configured.

Format

sender-address ipv4 ip-address

undo sender-address

Parameters

Parameter Description Value
ipv4 ip-address Specifies a source IPv4 address. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When PWE3 ping is performed in the multi-hop PW scenario, and the lsp-version is rfc4379, the sender-address command specifies a source IP address. The value is a routable address on the same public network with the address of the destination PE. Usually, the source IP address is the address of the adjacent SPE or UPE.

Precautions

After the sender-address command is run, the LSP version cannot be set to draft6.

Example

# Set the source IP address of the PWE3 ping test instance in the multi-hop PW scenario to 10.1.1.1.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type pwe3ping
[HUAWEI-nqa-user-test] lsp-version rfc4379
[HUAWEI-nqa-user-test] sender-address ipv4 10.1.1.1

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.

Format

set-df

undo set-df

Parameters

None

Views

NQA view

Default Level

2: Configuration level

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.

Example

# Set the test packet sent without being fragmented.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type trace
[HUAWEI-nqa-user-test] set-df
Related Topics

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 { nqafaillingalarmnotification | nqaftpsaverecordnotification | nqaftpstatsprobefailed | nqaftpstatstestcompleted | nqaftpstatstestfailed | nqaftpstatsthresholdnotification | nqahttpstatsprobefailed | nqahttpstatstestcompleted | nqahttpstatstestfailed | nqahttpstatsthresholdnotification | nqajitterstatsowdthresholdnotificationds | nqajitterstatsowdthresholdnotificationsd | nqajitterstatsrtdthresholdnotification | nqajitterstatstestcompleted | nqajitterstatstestfailed | nqaresultsprobefailed | nqaresultstestcompleted | nqaresultstestfailed | nqaresultstestresultchange | nqaresultsthresholdnotification | nqarisingalarmnotification | pingprobefailed | pingtestcompleted | pingtestfailed | traceroutetestcompleted | traceroutetestfailed | nqareflectorstatechangenotification } ]

undo snmp-agent trap enable feature-name nqa [ trap-name { nqafaillingalarmnotification | nqaftpsaverecordnotification | nqaftpstatsprobefailed | nqaftpstatstestcompleted | nqaftpstatstestfailed | nqaftpstatsthresholdnotification | nqahttpstatsprobefailed | nqahttpstatstestcompleted | nqahttpstatstestfailed | nqahttpstatsthresholdnotification | nqajitterstatsowdthresholdnotificationds | nqajitterstatsowdthresholdnotificationsd | nqajitterstatsrtdthresholdnotification | nqajitterstatstestcompleted | nqajitterstatstestfailed | nqaresultsprobefailed | nqaresultstestcompleted | nqaresultstestfailed | nqaresultstestresultchange | nqaresultsthresholdnotification | nqarisingalarmnotification | pingprobefailed | pingtestcompleted | pingtestfailed | traceroutetestcompleted | traceroutetestfailed | nqareflectorstatechangenotification } ]

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. -
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. -
nqajitterstatsowdthresholdnotificationsd Sends a trap when the jitter time from the source to the destination expires in a jitter test instance. -
nqajitterstatsowdthresholdnotificationds 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.

-

Views

System view

Default Level

2: Configuration level

Usage Guidelines

To enable the trap function for one or more specific events, specify trap-name.

Example

# Enable the trap function for the NQA nqaftpstatsprobefailed module.

<HUAWEI> system-view
[HUAWEI] snmp-agent trap enable feature-name nqa trap-name nqaftpstatsprobefailed

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.

Format

source-address { ipv4 ipv4-address | ipv6 ipv6-address }

undo source-address

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

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the test packets are transmitted to the destination address, the source address of the NQA test instance The source-address command is used to configure the source IP address for the NQA test. 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 PWE3 trace, PWE3 ping, or MAC ping.

Precautions

The configuration of the source IP address of the running test instance cannot be changed.

Example

# Set the source IP address to 10.1.1.1 for test instance user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] source-address ipv4 10.1.1.1

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.

Format

source-interface interface-type interface-number

undo source-interface

Parameters

Parameter Description Value
interface-type interface-number Specifies the type and number of the source interface for an NQA test instance. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After test packets reach the destination address, the destination end sends response packets to the client end. After the source-interface command is used to configure the source interface for an NQA test instance, there are the following scenarios:
  • 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 ICMP, ICMP Jitter, UDP Jitter, and MAC Ping test instances.

Precautions

The configuration of the source interface of a running test instance cannot be changed.

The source interface of an NQA test instance must be an interface with an IP address configured; otherwise, the command cannot take effect.

The source interface cannot be a link aggregation interface or a member interface in load balancing scenario; otherwise, the command cannot take effect.

Example

# Set the source interface of test instance user test to vlanif 100.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type icmp
[HUAWEI-nqa-user-test] source-interface vlanif 100

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.

Format

source-port port-number

undo source-port

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.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If a source port number is specified in an NQA test instance, NQA test packets can be regulated more accurately, which prevents the probe packets from being filtered by rules such ACL. The source-port command can be used to configure the source port for this NQA test instance:
  • 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 can be configured for FTP, HTTP, SNMP, UDP Jitter, TCP, and UDP test instances.

Precautions

The port specified in the source-port command must be available; otherwise, the probe fails.

You cannot change this configuration of a running test instance.

Example

# Set the source port number of test instance user test to 3000.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type tcp
[HUAWEI-nqa-user-test] source-port 3000

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.
  • seconds second: specifies a delay in performing a test instance. The value is an integer ranging from 1 to 86399, in seconds.

  • hh:mm:ss: specifies a delay in performing a test instance. If hh:mm:ss is specified, the system automatically sets the moment in seconds. For example, 1:0:0 indicates that a test instance starts in one hour (3600 seconds).

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.
  • seconds second: specifies a delay in stopping a test instance. The value is an integer ranging from 6 to 86399 in seconds.

  • hh:mm:ss: specifies a delay in stopping a test instance. For example, 1:0:0 stands for a 3600-second delay from the current system time till the time that the test instance stops.

NOTE:

The delay in stopping a test instance must be set to at least 6s later than the delay in performing the test instance.

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.
  • seconds second: sets the life time of a test instance in seconds. The value is an integer ranging from 6 to 86399 in seconds.

  • hh:mm:ss: sets the lifetime of a test instance. For example, 1:0:0 indicates that the lifetime of a test instance is 3600s starting from the moment a test instance starts.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After configuring test instances and relevant attributes, you need to manually set the start and end modes for the test instances. The types of start and end modes are as follows:
  • 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
You can set the start and end modes as required.

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. Although this command has been run and configurations have been saved, this start now command will not be restored and needs to be run again after the device is restarted.

When starting a test instance at a specified time, the time must be later than the current time on the device.

If no end time is configured, the test cannot stop automatically. You need to stop it manually using the stop command.

Example

# Perform the test 10 hours later.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] destination-address ipv4 10.1.1.1
[HUAWEI-nqa-user-test] destination-port 4000
[HUAWEI-nqa-user-test] start delay 10:00:00

stop

Function

The stop command stops an NQA test instance.

Format

stop

Parameters

None

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

You can run this command to stop only the running NQA test instances, that is, test instances in active state.

Example

# Stop the test instance named user test.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] stop
Related Topics

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.

Format

test-failtimes times

undo test-failtimes

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.

Views

NQA view

Default Level

2: Configuration level

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. The type of test instances that are not supported is as follows:
  • Mtrace
  • RTP Test
  • RTP Snoop
  • Path Jitter

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.

Example

# Set the number of consecutive test failures to 10.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] test-failtimes 10

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 { dns | ftp | http | icmp | icmpjitter | jitter | lspjitter | lspping | lsptrace | macping | pathjitter | mtrace | pwe3ping | pwe3trace | snmp | tcp | trace | udp | rtpsnoop | rtptest }

undo test-type

Parameters

Parameter Description Value
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. -
jitter Specifies a UDP jitter test, which can detect the jitter during UDP packet transmission. -
lspjitter Specifies an LSP jitter test. -
lspping Specifies an LSP ping test. -
lsptrace Specifies an LSP trace route test. -
macping Specifies a MAC ping test. -
pathjitter Specifies a path jitter test, which can detect the hop-by-hop jitter during the ICMP packet transmission. -
mtrace Specifies a multicast trace test. -
pwe3ping Specifies a PWE3 ping test. -
pwe3trace Specifies a PWE3 trace test. -
snmp Specifies an SNMP test. -
tcp Specifies a TCP test. -
trace Specifies a trace test. -
udp Specifies a UDP test. -
rtpsnoop Specifies an RTP snoop test. -
rtptest Specifies an RTP test. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

  • After an NQA test instance is created, a test type needs to be specified for it as other parameters are configured based on the test instance type. To configure the test type for an NQA test instance, run the test-type command.
  • You cannot change the type of a running test instance.
  • An ICMP test is usually conducted to check the connectivity. However, it cannot accurately test the link delay. Therefore, to test link delay or other link performance, you are advised to conduct an ICMP jitter or UDP jitter test.

Example

# Configure the test type of an NQA test instance as TCP.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type tcp
Related Topics

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.

Format

timestamp-unit { millisecond | microsecond }

undo timestamp-unit microsecond

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

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

This command applies to the ICMP Jitter and UDP Jitter tests.

Example

# Set the unit of timestamp for an NQA test instance to microsecond.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] timestamp-unit microsecond
Related Topics

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.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

The OWD threshold is applied only to jitter test instances and ICMP jitter test instances.

The RTD threshold is not supported by Mtrace, Path Jitter, RTP Test, and RTP Snoop test.

Example

# Set the RTD threshold to 2 ms.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] threshold rtd 2
Related Topics

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 FTP test instances is 15 seconds and that for other test instances is 3 seconds.

Format

timeout time

undo timeout

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.

Views

NQA view

Default Level

2: Configuration level

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 test fails. The timeout period is set based on the actual networking.

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. The type of test instances that are not supported is as follows:
  • RTP test
  • RTP snoop

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

Precautions

You cannot change this configuration of a running test instance.

In an ICMP test instance, if the following conditions are met, the Completion field in the test results will be displayed as no result:
  • The system CPU usage exceeds 90% and the configured timeout period is less than 6s.
  • frequency configured ≤ (probe-count - 1) × interval + 6.

Example

# Set the timeout period of the test instance named user test to 20 seconds.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type jitter
[HUAWEI-nqa-user-test] timeout 20

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.

Format

tos value

undo tos

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.

Views

NQA view

Default Level

2: Configuration level

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

The type of a test instance has been specified using the test-type command. The following types of test instances are supported:
  • FTP
  • HTTP
  • ICMP
  • ICMP Jitter
  • UDP Jitter
  • SNMP
  • TCP
  • UDP

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.

Example

# Set the ToS value for the test instance named user test to 10.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type icmp
[HUAWEI-nqa-user-test] tos 10
Related Topics

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.

Format

tracert-hopfailtimes times

undo tracert-hopfailtimes

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.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

The tracert-hopfailtimes command only takes effect for trace, LSP trace, and PWE3 trace test instances.

You cannot change this configuration of a running test instance.

Example

# Set the number of consecutive failed hops indicating a failed trace test instance to 6.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type trace
[HUAWEI-nqa-user-test] tracert-hopfailtimes 6
Related Topics

tracert-livetime

Function

The tracert-livetime command sets the time to live (TTL) value for trace, Mtrace, PWE3 trace, and LSP trace test instances in an NQA test.

The undo tracert-livetime command restores the default TTL value for trace, Mtrace, PWE3 trace, and LSP trace test instances in an NQA test.

By default, the initial TTL value is 1 and the maximum TTL value is 30.

Format

tracert-livetime first-ttl first-ttl max-ttl max-ttl

undo tracert-livetime

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.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

The tracert-livetime command takes effect only for trace, multicast trace, PWE3 trace, and LSP trace test instances.

NOTE:

In a multicast trace test instance, the value of first-ttl must be 1.

You cannot change this configuration of a running test instance.

Example

# Set the initial TTL value of the test instance named user test to 5 and the maximum TTL value to 20.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type trace
[HUAWEI-nqa-user-test] tracert-livetime first-ttl 5 max-ttl 20
Related Topics

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.

Format

ttl number

undo ttl

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.

Views

NQA view

Default Level

2: Configuration level

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

The type of a test instance has been specified using the test-type command. The type of test instances that are not supported is as follows:
  • DNS
  • Trace
  • LSP Trace
  • PWE3 Trace
  • MAC Ping
  • Path Jitter
  • RTP Test
  • RTP Snoop

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.

In a PWE3 Ping test instance, the TTL propagation mode is set to the pipe mode using the ttl-copymode command and the LSP version is set to RFC4379 using the lsp-version command. The default TTL value is obtained based on the actual networking. When you run the display nqa-parameter command, the TTL value is always 0.

Example

# Set the TTL value for the test packets of a test instance named user test to 10.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type icmp
[HUAWEI-nqa-user-test] ttl 10
Related Topics

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.

Format

ttl-copymode { pipe | uniform }

undo ttl-copymode

Parameters

Parameter Description Value
pipe Sets the TTL propagation mode to pipe. -
uniform Sets the TTL propagation mode to uniform. -

Views

NQA view

Default Level

2: Configuration level

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 PWE3 networks and BGP/MPLS IP VPN networks.

The TTL propagated in pipe and uniform modes is processed in different manners:
  • 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.
NOTE:

The ttl-copymode command makes sense only in the PWE3 Ping,PWE3 Trace, and Trace test instances. In the case of an trace test instance, you need to first run the vpn-instance vpn-instance-name command to bind the NQA trace test instance with a VPN instance.

Example

# Configure the TTL propagation mode of packets in the NQA trace test instance as pipe.

<HUAWEI> system-view
[HUAWEI] nqa test-instance admin trace
[HUAWEI-nqa-admin-trace] test-type trace
[HUAWEI-nqa-admin-trace] vpn-instance voice
[HUAWEI-nqa-admin-trace] ttl-copymode pipe
Related Topics

undo no-control-word

Function

Using the undo no-control-word command, you can enable the control-word option.

By default, the control-word is used in packet encapsulation.

Format

undo no-control-word

Parameters

None

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

The control-word option carries control-word information in each encapsulated packet. The information is used for packet sequence verification, packet fragmentation, and packet reassembling on the forwarding plane.

By default, the control-word is used in packet encapsulation. If a non-huawei device does not support control-word information in the packet structure, the label-type { { label-alert | normal } no-control-word } command can be used on the Huawei device to remove the control-word option from each packet sent to the non-huawei device to facilitate their interworking.

If a non-huawei device supports control-word information in the packet structure, the undo no-control-word command can be used on the Huawei device to restore the Huawei packet structure.

NOTE:

Only PWE3 Ping and PWE3 Trace test instances support the undo no-control-word command.

Example

# Enable the control-word option.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type pwe3ping
[HUAWEI-nqa-user-test] label-type label-alert no-control-word
[HUAWEI-nqa-user-test] undo no-control-word
Related Topics

vc-type

Function

Using the vc-type command, you can configure the type of the protocol used for setting up an L2VPN VC in the NQA view.

Using the undo vc-type command, you can delete the protocol type configured in the NQA view.

By default, the type of the protocol used for setting up an L2VPN VC is LDP.

Format

vc-type { ldp | bgp }

undo vc-type

Parameters

Parameter Description Value
ldp Propagates inner labels by using LDP as the signaling protocol. -
bgp Propagates inner labels by using BGP as the signaling protocol. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The vc-type command is used to configure the signaling protocol for an NQA test instance to be identical with that for the PW on the network to be tested.

Prerequisites

For the vc-type ldp command, ensure that the test instance is of the following type:
  • PWE3 Ping
  • PWE3 Trace
For the vc-type bgp command, ensure that the test instance is of the following type:
  • PWE3 Trace

Precautions

The signaling type of a running test instance cannot be changed.

Example

# In the NQA view, configure BGP to be the type of the protocol used for setting up an L2VPN VC.

<HUAWEI> system-view
[HUAWEI] nqa test-instance admin pwe3
[HUAWEI-nqa-admin-pwe3] test-type pwe3trace
[HUAWEI-nqa-admin-pwe3] vc-type bgp
Related Topics

vpn-instance (NQA view)

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.

Format

vpn-instance vpn-instance-name

undo vpn-instance

Parameters

Parameter Description Value
vpn-instance-name Specifies the VPN instance that an NQA test instance belongs to. The value must be an existing VPN instance name.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

The vpn-instance command applies to FTP, HTTP, ICMP, ICMP Jitter, Path Jitter, SNMP, TCP, trace, UDP, MTrace, and UDP Jitter test instances.

In a PWE3 Trace test instance, if the protocol type of the L2VPN VC is set to BGP by the vc-type command, you can run the vpn-instance command to specify a VPN instance name for the PWE3 Trace test instance.

You cannot change this configuration of a running test instance.

Example

# Set the VPN instance for an NQA test instance named user test to vrf1.

<HUAWEI> system-view
[HUAWEI] nqa test-instance user test
[HUAWEI-nqa-user-test] test-type icmp
[HUAWEI-nqa-user-test] vpn-instance vrf1
Related Topics
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065659

Views: 113886

Downloads: 83

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next