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

Command Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R002C50

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

NOTE:

Only the CE8860EI, CE8850EI, CE7855EI, CE7850EI, CE6870EI, CE6860EI, CE6856HI, CE6855HI, CE6851HI, CE6850HI, and CE6850U-HI support LSP Ping and LSP Trace test instances.

The CE6810LI does not support IPv4 or IPv6 Layer 3 forwarding. After the IPv4 or IPv6 function is enabled on an interface of the CE6810LI, the configured IPv4 or IPv6 address can only be used to manage the switch.

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 UDP jitter test is used.
  • The code type for the simulated voice test of a jitter test instance has been set using the jitter-codec command. The code types of g711a, g711u, and g729a are applied to the VoIP applications of conversion between simulated voice signals and digital signals.
  • The nqa-server udpecho command has been run on the remote device to respond to the jitter test.

Configuration Impact

If the advantage factor has been configured, running the adv-factor command will override the previous configuration.

If the code type is changed after the jitter-codec command is run, the configured advantage factor does not take effect and you need to configure a new advantage factor.

Precautions

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

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

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

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:

  • ICMP
  • ICMP jitter (The datafill command supports ICMP jitter only after icmp-echo is specified in the icmp-jitter-mode command.)
  • Jitter
  • LSP Ping
  • Trace

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

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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.

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.

Prerequisites

The test type has been specified using the test-type command.

The datasize command is applicable to the following types of test instances:

  • ICMP
  • ICMP jitter (The datasize command supports ICMP jitter only after icmp-echo is specified in the icmp-jitter-mode command.)
  • Jitter
  • LSP Ping
  • Trace

Precautions

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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, no destination address is configured for an NQA test instance.

Format

destination-address { ipv4 ipv4-address [ lsp-masklen masklen | lsp-loopback loopback-address ] * | ipv6 ipv6-address }

undo destination-address

Parameters

Parameter Description Value
ipv4 ipv4-address Specifies an IPv4 destination address. The IPv4 address is in dotted decimal notation.
lsp-masklen masklen Specifies the mask length of an LSP's IPv4 address prefix. The value is an integer that ranges from 0 to 32.
lsp-loopback loopback-address Specifies a 127/8 IP address in the MPLS echo request packet header. -
ipv6 ipv6-address Specifies an IPv6 destination address.
NOTE:

Only ICMP and Trace test support IPv6 destination 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

NQA tests service performance using created 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 test instances are configured on the NQA client, NQA schedules these test instances into test instance queues according to their operation modes. After the test instances are started, data information about the protocol-related running status can be collected according to the return packet.

Precautions

The Label Switched Path (LSP) parameters can be configured only for the LSP test instances.

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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:
  • Jitter: No default value is available, and the destination port number must be configured.
  • TCP: 7
  • Trace: 33434

Format

destination-port port-number

undo destination-port

Parameters

Parameter Description Value
port-number Specifies the destination port number.

The value is 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

NQA tests service performance using created 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 test instances are configured on the NQA client, NQA schedules these test instances into test instance queues according to their operation modes. After the test instances are started, data information about the protocol-related running status can be collected according to the return packet.

Precautions

The destination-port command is applicable to the following types of test instances:
  • Jitter
  • TCP
  • Trace
If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

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.

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.

Configuration Impact

No history record about the failed jitter test instances exists.

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
T/H/P = Test ID/Hop ID/Probe ID   
NQA entry(admin,tcp) history: 
--------------------------------------------------------------------------------
Index T/H/P       Response (ms) Status       Address         Time                    
                                                                                
--------------------------------------------------------------------------------
 1    1/1/1          290       success      10.1.1.5        2013-09-10 21:40:33.737 
                                                                                
 2    1/1/2          484       success      10.1.1.5        2013-09-10 21:40:37.937 
                                                                                
 3    1/1/3          479       success      10.1.1.5        2013-09-10 21:40:41.943 
                                                                                
--------------------------------------------------------------------------------
Table 18-49  Description of the display nqa history command output

Item

Description

NQA entry(admin, tcp)

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

Index

Index of a test record.

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 (ms)

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

Status

Status of the NQA probe packet.
  • timeout: indicates that the probe times out and no response packet is received.
  • success: indicates that the probe succeeds.
  • busy: indicates that the resources are insufficient and the probe packet fails to be sent. The probe fails.
  • drop: indicates that the test instance configuration is incorrect and the probe packet fails to be sent. The probe fails.

Address

Destination address.

Time

Time when the response packet is received.

Related Topics

display nqa history this

Function

The display nqa history this command displays the history records about an NQA test instance in the specified NQA view.

Format

display nqa history this

Parameters

None

Views

NQA view

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.

To view history records of the specified NQA test instance, run the display nqa history this command in this NQA view. You can check information about the execution of each probe packet, including status of each probe packet and RTT, to learn about the network performance.

Prerequisites

An NQA test instance has been configured.

Configuration Impact

No history record about the failed jitter test instances exists.

Precautions

The display nqa history this command must be run in the view of an NQA test instance and displays the history records of this NQA test instance. The display nqa history command displays the history records of all NQA test instances.

Example

# Display the history record of the NQA test instance.

<HUAWEI> system-view 
[~HUAWEI] nqa test-instance admin tcp
[~HUAWEI-nqa-admin-tcp] display nqa history this
T/H/P = Test ID/Hop ID/Probe ID                                                 
NQA entry(admin,tcp) history:                                                   
--------------------------------------------------------------------------------
Index T/H/P       Response (ms) Status       Address         Time                    
                                                                                
--------------------------------------------------------------------------------
 1    1/1/1          290       success      10.1.1.5        2013-09-10 21:40:33.737 
                                                                                
 2    1/1/2          484       success      10.1.1.5        2013-09-10 21:40:37.937 
                                                                                
 3    1/1/3          479       success      10.1.1.5        2013-09-10 21:40:41.943 
                                                                                
 4    2/1/1          279       success      10.1.1.5        2013-09-11 09:26:36.358 
                                                                                
 5    2/1/2          272       success      10.1.1.5        2013-09-11 09:26:40.346 
                                                                                
--------------------------------------------------------------------------------
Table 18-50  Description of the display nqa history this command output

Item

Description

NQA entry(admin, tcp)

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

Index

Index of a test record.

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 (ms)

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

Status

Status of the NQA probe packet.
  • timeout: indicates that the probe times out and no response packet is received.
  • success: indicates that the probe succeeds.
  • busy: indicates that the resources are insufficient and the probe packet fails to be sent. The probe fails.
  • drop: indicates that the test instance configuration is incorrect and the probe packet fails to be sent. The probe fails.

Address

Destination address.

Time

Time when the response packet is received.

Related Topics

display nqa results

Function

The display nqa results command displays NQA test results.

Format

display nqa results [ collection ] [ test-instance admin-name test-name ]

Parameters

Parameter Description Value
collection Indicates the total NQA test results. This parameter is only valid for ICMP Jitter and Jitter 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.

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.

The display nqa results command displays the results of a test instance that has been complete.

Precautions

If no optional parameter is specified, all NQA test results are displayed.

Example

# Display the results of an NQA ICMP test.

<HUAWEI> display nqa results test-instance admin icmp
NQA entry(admin, icmp): test flag is inactive, test type is ICMP                
  1 . Test 1 result   The test is finished                                      
   Send operation times: 3                Receive response times: 3             
   Completion: success                    RTD over thresholds 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/7/3                                       
   Sum/Square-Sum  completion time: 11/57                                       
   Last response packet receiving time: 2012-07-27 02:42:20.3+08:00             
   Lost packet ratio: 0 %     
Table 18-51  Description of the display nqa results test-instance admin icmp 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.

test flag

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.

test type

Test type.

1 . Test 1 result

Sequence number of test results. Test results are numbered based on the time when the tests are complete.

The test is finished

Test status:
  • 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 result is obtained.

  • failed: indicates that the test fails.

RTD over thresholds number

Number of times that the round-trip delay (RTD) threshold is exceeded.

Attempts number

Test times.

Drop operation number

Number of system resource allocation failures.

Disconnect operation number

Number of forcible disconnections.

Operation timeout number

Number of timeout operations during the test.

System busy operation number

Number of conflict operations.

Connection fail number

Number of times that the local end fails to establish connections with the peer.

Operation sequence errors number

Number of received disordered packets.

RTT Status errors number

Number of RTT status errors.

Destination IP address

Destination IP address of the test.

Min/Max/Average completion time

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

Sum/Square-Sum completion time

Sum and square sum of the time taken to complete the test.

Last response packet receiving time

Time at which the last probe is complete.

Lost packet ratio

Packet loss ratio.

# Display the result of an NQA jitter test.

<HUAWEI> display nqa results test-instance admin jitter
                                                                                
NQA entry(admin, jitter): test flag is inactive, test type is JITTER
  1 . Test 1 result   The test is finished
   SendProbe: 60                           ResponseProbe: 60                      
   Completion: success                     RTD over thresholds number: 0           
   OWD over thresholds SD number: 0        OWD over thresholds DS number: 0        
   Min/Max/Avg/Sum RTT: 1/132/8/491        RTT square sum: 41843                  
   Num of RTT: 60                          Drop operation number: 0               
   Operation sequence errors number: 0     RTT Status errors number: 0             
   System busy operation number: 0         Operation timeout number: 0            
   Min positive SD: 0                      Min positive DS: 8                     
   Max positive SD: 0                      Max positive DS: 24                    
   Positive SD number: 0                   Positive DS number: 54                 
   Positive SD sum: 0                      Positive DS sum: 1153                  
   Positive SD square sum: 0               Positive DS square sum: 24847          
   Min negative SD: 20                     Min negative DS: 2                     
   Max negative SD: 23                     Max negative DS: 3                     
   Negative SD number: 59                  Negative DS number: 5                  
   Negative SD sum: 1273                   Negative DS sum: 12                    
   Negative SD square sum: 27491           Negative DS square sum: 30             
   Min delay SD: 1                         Min delay DS: 0                        
   Avg delay SD: 7                         Avg delay DS: 0                        
   Max delay SD: 132                       Max delay DS: 0                        
   Delay SD square sum: 41825              Delay DS square sum: 0                 
   Packet loss SD: 0                       Packet loss DS: 0                      
   Packet loss unknown: 0                  Average of jitter: 20                  
   Average of jitter SD: 21                Average of jitter DS: 19               
   Jitter out value: 15.9377600            Jitter in value: 14.1930380            
   Number of OWD: 60                       Packet loss ratio: 0 %                 
   OWD SD sum: 473                         OWD DS sum: 0                          
   ICPIF value: 0                          MOS-CQ value: 0                        
   TimeStamp unit: ms                     
Table 18-52  Description of the display nqa results command output
Item Description
NQA entry NQA test items:
  • admin: indicates the name of the administrator of the NQA test.
  • jitter: indicates the name of the NQA test instance.
test flag 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.
test type 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 result is obtained.
  • failed: indicates that the test fails.
RTD over thresholds number Number of times that the RTD threshold is exceeded.
OWD over thresholds SD number Number of times that the OWD threshold (from the source to the destination) is exceeded.
OWD over thresholds 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.
Num of RTT 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 Status 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.
Number of OWD Number of OWD packets.
OWD SD sum Sum of OWD from the source to the destination.
OWD DS sum Sum of OWD from the destination to the source.
Packet loss ratio Packet loss ratio.
MOS-CQ value Average estimate of VoIP performance.
ICPIF value Advantage factor.
TimeStamp unit Time unit.
Related Topics

display nqa results this

Function

The display nqa results this command displays NQA test results in a specified NQA view.

Format

display nqa results [ collection ] this

Parameters

Parameter Description Value
collection Indicates the total NQA test results. This parameter is only valid for ICMP Jitter and Jitter tests. -

Views

NQA view

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. NQA allows carriers to collect the operation indexes of networks in real time.

To view the results of a specified NQA test, you can run the display nqa results this command in this NQA view, which helps you know the completing status of the NQA test.

The display nqa results collection this command displays the total test results.

Prerequisites

An NQA test instance has been configured.

Precautions

The display nqa results this command must be run in an NQA view and displays the results of this NQA test. The display nqa results command displays results of all NQA tests.

Example

# Display the results of ICMP test instances.

<HUAWEI> system-view 
[~HUAWEI] nqa test-instance admin icmp
[~HUAWEI-nqa-admin-icmp] display nqa results this
  NQA entry(admin, icmp): test flag is inactive, test type is ICMP                  
  1 . Test 1 result   The test is finished                                      
   Send operation times: 3              Receive response times: 3               
   Completion:success                   RTD over thresholds 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 response packet receiving time: 2012-07-02 17:09:18.1                                  
   Lost packet ratio: 0 %      
Table 18-53  Description of the display nqa results this command output

Item

Description

NQA entry(admin, icmp)

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

test flag

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.

test type

Test type.

1 . Test 1 result

Serial number of the 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 result is obtained.
  • failed: indicates that the test fails.

RTD over thresholds number

Number of times that the RTD threshold is exceeded.

Attempts number

Test times.

Drop operation number

Number of system resource allocation failures.

Disconnect operation number

Number of forcible disconnections.

Operation timeout number

Number of timeout operations during the test.

System busy operation number

Number of conflict operations.

Connection fail number

Number of times that the local end fails to establish connections with the peer.

Operation sequence errors number

Number of received disordered packets.

RTT Status errors number

Number of RTT status errors.

Destination IP address

Destination IP address of the test.

Min/Max/Average completion time

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

Sum/Square-Sum completion Time

Sum and square sum of the time taken to complete the test.

Last response packet receiving time:

Time at which the last probe is complete.

Lost packet ratio

Packet loss ratio.

# Display the total test results of the jitter test instances.
<HUAWEI> system-view 
[~HUAWEI] nqa test-instance admin jitter 
[~HUAWEI-nqa-admin-jitter] display nqa results collection this

NQA entry(admin, jitter): test type is JITTER                                   
    1 . Test 1 collect result                                                   
   SendProbe: 60                          ResponseProbe: 60                     
   Completion: 2                          RTD over thresholds number: 0         
   OWD over thresholds SD number: 0       OWD over thresholds DS number: 0      
   Min/Max/Avg/Sum RTT: 2/145/13/785      RTT square sum: 64179                 
   Num of RTT: 60                         Drop operation number: 0              
   Operation sequence errors number: 0    RTT Status errors number: 0            
   System busy operation number: 0        Operation timeout number: 0           
   Min positive SD: 1                     Min positive DS: 1                    
   Max positive SD: 6                     Max positive DS: 6                    
   Positive SD number: 15                 Positive DS number: 11                
   Positive SD sum: 23                    Positive DS sum: 21                   
   Positive SD square sum: 61             Positive DS square sum: 61            
   Min negative SD: 1                     Min negative DS: 1                    
   Max negative SD: 6                     Max negative DS: 20                   
   Negative SD number: 14                 Negative DS number: 18                
   Negative SD sum: 23                    Negative DS sum: 163                  
   Negative SD square sum: 63             Negative DS square sum: 2819          
   Min delay SD: 0                        Min delay DS: 0                       
   Avg delay SD: 6                        Avg delay DS: 5                       
   Max delay SD: 72                       Max delay DS: 72                      
   Delay SD square sum: 15787             Delay DS square sum: 15560            
   Packet loss SD: 0                      Packet loss DS: 0                     
   Packet loss unknown: 0                 Average of jitter: 3                  
   Average of jitter SD: 1                Average of jitter DS: 6               
   Jitter out value: 0.5683860            Jitter in value: 2.7267760            
   Number of OWD: 60                      Packet loss ratio: 0 %                
   OWD SD sum: 375                        OWD DS sum: 350                       
   ICPIF value: 0                         MOS-CQ value: 0                       
   TimeStamp unit: ms                                                
Table 18-54  Description of the display nqa results collection this command output
Item Description
NQA entry (admin, jitter) NQA test items:
  • admin: indicates the name of the administrator of the NQA test.
  • jitter: indicates the name of the NQA test instance.

test flag

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.

test type Test type.
SendProbe Number of sent probes.
ResponseProbe Number of received response probes.
Completion Number of the test.
RTD over thresholds number Number of times that the RTD threshold is exceeded.
OWD over thresholds SD number Number of times that the OWD threshold (from the source to the destination) is exceeded.
OWD over thresholds 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.
Num of RTT 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 Status 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.
Number of OWD Number of OWD packets.
OWD SD sum Sum of OWD from the source to the destination.
OWD DS sum Sum of OWD from the destination to the source.
Packet loss ratio Packet loss ratio.
MOS-CQ value Average estimate of VoIP performance.
ICPIF value Advantage factor.
TimeStamp unit Time unit.
Related Topics

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

Both the server and the client need to be configured before starting a TCP or jitter test instance. Otherwise, the test instances cannot be started.
  • In the case of a TCP test instance, the nqa server tcpconnect command needs to be run to enable a TCP server.
  • In the case of a jitter test instance, the nqa server udpecho command needs to be run to enable a UDP server.

You can run the display nqa-server command to view the information about NQA servers. Each time a server is enabled, the number of the corresponding servers increases by one.

Example

# Display the information about NQA servers.

<HUAWEI> display nqa server 
NQA Server Max: 100              NQA Server Num: 2 
NQA Concurrent TCP Server: 1     NQA Concurrent UDP Server: 1 
-----------------------------------------------------------------
Type           VPN         Address        Port       Status        
-----------------------------------------------------------------
tcpconnect     ---         10.1.1.1        22        ACTIVE         
udpecho        vpn1        10.1.1.1        22        NOTINSERVICE      
Table 18-55  Description of the display nqa server command output

Item

Description

NQA Server Max

Maximum NQA servers allowed to be configured

NQA Server Num

Number of the current NQA servers

NQA Concurrent TCP Server

Number of the configured TCP servers

NQA Concurrent UDP Server

Number of the configured UDP servers

Type Type of NQA server
VPN

Name of a VPN instance to which the NQA server belongs

Address

IP address of the NQA server for monitoring services

Port

Port number of the NQA server for monitoring services

Status
Status of an NQA server:
  • ACTIVE: the NQA server is enabled.
  • NOTINSERVICE: the NQA server is disabled.

display snmp-agent trap feature-name nqa all

Function

The display snmp-agent trap feature-name nqa all command displays the status of all traps of the NQA module.

Format

display snmp-agent trap feature-name nqa all

Parameters

None

Views

All views

Default Level

3: Management level

Usage Guidelines

None

Example

# Display the status of all traps of the NQA module.

<HUAWEI> display snmp-agent trap feature-name nqa all
------------------------------------------------------------------------------  
Feature name: NQA
Trap number : 13
------------------------------------------------------------------------------
Trap name                      Default switch status   Current switch status
nqaJitterStatsOWDThresholdNotificationDS
                               on                      on
nqaJitterStatsOWDThresholdNotificationSD
                               on                      on
nqaJitterStatsRTDThresholdNotification
                               on                      on
nqaJitterStatsTestFailed       on                      on
nqaResultsProbeFailed          on                      on
nqaResultsTestCompleted        on                      on
nqaResultsTestFailed           on                      on
nqaResultsThresholdNotification
                               on                      on
pingProbeFailed                on                      on
pingTestCompleted              on                      on
pingTestFailed                 on                      on
traceRouteTestCompleted        on                      on
traceRouteTestFailed           on                      on
Table 18-56  Description of the display snmp-agent trap feature-name nqa all command output

Item

Description

Feature name

Name of the module that a trap belongs to.

Trap number

Number of traps.

Trap name

Name of a trap.

Default switch status

Default status of the trap function:
  • on: indicates that the trap function is enabled.
  • off: indicates that the trap function is disabled.

Current switch status

Status of the trap function:
  • on: indicates that the trap function is enabled.
  • off: indicates that the trap function is disabled.

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 following types of test instances are supported:
  • ICMP
  • ICMP Jitter
  • Jitter
  • LSP Ping
  • TCP

Precautions

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

fragment enable

Function

The fragment enable command enables MPLS packet fragmentation for an NQA test instance.

The undo fragment enable command restores the default configuration.

By default, MPLS packet fragmentation is disabled for NQA test instances.

Format

fragment enable

undo fragment enable

Parameters

None

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

In the LSP Ping or LSP Trace test, if the MPLS packet length is greater than the MTU of the MPLS tunnel, MPLS packets fail to pass through the tunnel. To allow the packets to pass through the tunnel, run the fragment enable command. This command enables MPLS packet fragmentation for NQA test.

Prerequisites

The type of a test instance has been set to LSP Ping or LSP Trace using the test-type { lspping | lsptrace } command.

Example

# Enable MPLS packet fragmentation for an NQA test instance.

<HUAWEI> system-view
[~HUAWEI] nqa test-instance user test
[*HUAWEI-nqa-user-test] test-type lspping
[*HUAWEI-nqa-user-test] fragment enable

frequency

Function

The frequency command sets the interval at which an NQA test instance is automatically performed.

The undo frequency command deletes the configured interval at which an NQA test instance is automatically performed.

By default, the interval at which an NQA test instance is automatically performed is not configured. That is, the test is performed for one time.

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 one time at each configured interval.

Configuring the interval of a periodic NQA test avoids time-consuming manual operations.

Prerequisites

The type of a test instance has been specified using the test-type command.

Precautions

The frequency value must comply with the following rule: If the frequency value does not meet the requirement of the frequency formula, the test result may be "no result".

Test Instance Type Formula Argument
  • ICMP test instance
  • LSP Ping test instance
  • TCP test instance

frequency > interval x ( probeCount - 1 ) + timeout

  • frequency: the interval at which the NQA test instance is automatically executed.
  • interval: the interval at which the probe packets are sent in the NQA test instance.
  • probeCount: the number of probes to be sent each time for the NQA test instance.
  • timeout: the timeout period of a probe for the NQA test instance.
  • ICMP Jitter test instance
  • UDP Jitter test instance
frequency > interval x ( probeCount x jitter-packetnum - 1 ) + timeout
  • frequency: the interval at which the NQA test instance is automatically executed.
  • interval: the interval at which the probe packets are sent in the NQA test instance.
  • probeCount: the number of probes to be sent each time for the NQA test instance.
  • jitter-packetnum: the number of packets sent in each probe of the NQA test instance.
  • timeout: the timeout period of a probe for the NQA test instance.
  • LSP Trace test instance
  • Trace test instance
The value of frequency is equal to or larger than 60. frequency: the interval at which the NQA test instance is automatically executed.
If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

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

Usage Scenario

You can run the icmp-jitter-mode command to specify the mode for an ICMP jitter test.

Precautions

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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.

  • The interval is 20 milliseconds for a jitter test instance or ICMP jitter test instance.

  • 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 10 to 60000.
seconds interval Sets the interval at which packets are sent, in seconds. The value is an integer that ranges from 1 to 60, in seconds.

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

Configuration Impact

  • If the configured interval is a multiple of 1000 milliseconds, the system will automatically convert milliseconds into seconds.
  • Packets can be sent at interval of milliseconds only in jitter 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 jitter test instance.
  • If the interval for sending packets has been configured, running the interval command will override the previous configuration.

Precautions

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

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 18-57  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

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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 jitter test instances and icmp jitter test instances.

Configuration Impact

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

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

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.

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

You can use the lsp-nexthop command to configure the IP address of the next hop. Currently, only LSP ping test instance is supported.

Precautions

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

Example

# Specify the next hop address for the LSP Ping test instance whose LSP type is IPv4.

<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-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 { level-control-channel | no-reply | udp }

undo lsp-replymode

Parameters

Parameter Description Value
level-control-channel Indicates that reply packets are sent through an application-level control channel. -
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 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

Precautions

lsp-replymode no-reply indicates the unidirectional test. If the client displays timeout, it indicates that the test succeeds.

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

undo lsp-type

Parameters

Parameter Description Value
ipv4 Sets the test type to Ipv4 LSP ping/trace. -

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.

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

Prerequisites

  • If the LSP test type is set to IPv4, the NQA test instance type must be set to LSP ping or LSP trace.

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

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.

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 determine 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 jitter tag-version

Function

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

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

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

Format

nqa jitter tag-version version-number

undo nqa jitter tag-version

Parameters

Parameter Description Value
version-number Specifies the packet version for a 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 jitter test instance has been configured, running the nqa jitter tag-version command will override the previous configuration.

Example

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

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

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 [ 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. The value is a string of 1 to 31 case-sensitive characters except spaces. When double quotation marks are used to include the string, spaces are allowed in the string. The value _public_ is reserved and cannot be used as the VPN instance name.
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.

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 port-number

undo nqa server udpecho [ 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 server belongs. The name of the VPN instance must already exist.
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.

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 jitter test. The test is used to obtain the packet delay, jitter, and packet loss ratio by comparing timestamps in the request and response packets. A UDP server needs to be configured for an NQA test to respond to probe packets.

If the client and the server are connected through a VPN, you need to specify the VPN instance name.

Precautions

A UDP server is configured only in a jitter test instance.

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

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.

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.

Configuration Impact

  • In jitter test instances, ICMP 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

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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.

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

The probe-failtimes command does not apply to ICMP Jitter, Jitter, LSP Ping, LSP Trace and Trace test instances.

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

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

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.

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

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

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

The test type has been specified using the test-type command.

The sendpacket passroute command is invalid for ICMP Jitter, LSP Ping, and LSP Trace test instances.

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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 } * }

undo send-trap { all | { owd-ds | owd-sd | probefailure | rtd | testcomplete | testfailure } * }

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 jitter test instances.
-
owd-sd Indicates that a trap is sent when the OWD from the source to the destination exceeds the threshold.
NOTE:
This parameter applies only to jitter test instances.
-
probefailure Indicates that a trap is sent when the number of probe failures reaches the threshold.
NOTE:
This parameter does not apply to Jitter and Trace 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.
NOTE:

This parameter does not apply to the jitter test instances.

-
testfailure Indicates that a trap is sent when the number of test failures reaches the threshold. -

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.

Precautions

The sendpacket passroute command is invalid for ICMP Jitter, LSP Ping, and LSP Trace test instances.

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

If the trap function is enabled for multiple test instances, a large number of traps (logs) may be generated, which increases the CPU usage and affects other services.

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

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

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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 { nqajitterstatsowdthresholdnotificationds | nqajitterstatsowdthresholdnotificationsd | nqajitterstatsrtdthresholdnotification | nqajitterstatstestfailed | nqaresultsprobefailed | nqaresultstestcompleted | nqaresultstestfailed | nqaresultsthresholdnotification | pingprobefailed | pingtestcompleted | pingtestfailed | traceroutetestcompleted | traceroutetestfailed } ]

undo snmp-agent trap enable feature-name nqa [ trap-name { nqajitterstatsowdthresholdnotificationds | nqajitterstatsowdthresholdnotificationsd | nqajitterstatsrtdthresholdnotification | nqajitterstatstestfailed | nqaresultsprobefailed | nqaresultstestcompleted | nqaresultstestfailed | nqaresultsthresholdnotification | pingprobefailed | pingtestcompleted | pingtestfailed | traceroutetestcompleted | traceroutetestfailed } ]

Parameters

Parameter Description Value
trap-name Indicates the name of a trap. -
nqajitterstatsowdthresholdnotificationds Indicates that a trap generated if the time of transmitting the packet from the destination address to the source address exceeds the threshold. -
nqajitterstatsowdthresholdnotificationsd Indicates that a trap generated if the time of transmitting the packet from the source address to the destination address exceeds the threshold. -
nqajitterstatsrtdthresholdnotification Indicates that a trap generated if a jitter test time exceeds the threshold. -
nqajitterstatstestfailed Indicates that a trap generated if a jitter test fails. -
nqaresultsprobefailed Indicates that a trap generated if the total number of continuous probe failures on the NQA module exceeds the threshold. -
nqaresultstestcompleted Indicates that a trap generated when a common test instance is complete. -
nqaresultstestfailed Indicates that a trap generated if a common test instance fails. -
nqaresultsthresholdnotification Indicates that a trap generated if the test duration exceeds the threshold. -
pingprobefailed Indicates that a trap generated if the number of continuous probe failures of an ICMP test exceeds the threshold. -
pingtestcompleted Indicates that a trap generated after the ICMP test is complete. -
pingtestfailed Indicates that a trap generated if an ICMP test fails. -
traceroutetestcompleted Indicates that a trap generated after the route to the peer end is obtained in the trace test instance.
NOTE:

The CE8860EI, CE8850EI, CE7855EI, CE7850EI, CE6880EI, CE6870EI, CE6860EI, CE6856HI, CE6855HI, CE6851HI, CE6850HI, and CE6850U-HI do not support this Parameter.

-
traceroutetestfailed Indicates that a trap generated if the route to the peer end cannot be obtained in the trace test instance.
NOTE:

The CE8860EI, CE8850EI, CE7855EI, CE7850EI, CE6880EI, CE6870EI, CE6860EI, CE6856HI, CE6855HI, CE6851HI, CE6850HI, and CE6850U-HI do not support this Parameter.

-

Views

System view

Default Level

3: Management 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 nqajitterstatsowdthresholdnotificationds module.

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

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, and trace test 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 is used as the destination address. 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.

Precautions

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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, Jitter test instances.

Precautions

Use an interface with an IP address as the source interface of the NQA test instance; otherwise, the command does not take effect.

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

The test instance type has been specified using the test-type command. The source port number can be configured only for TCP and, jitter test instances.

Precautions

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

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

start daily hh:mm:ss to hh:mm:ss [ begin { yyyy-mm-dd | yyyy/mm/dd } ] [ end { yyyy-mm-dd | yyyy/mm/dd } ]

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.

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.

start daily hh:mm:ss to hh:mm:ss [ begin { yyyy-mm-dd | yyyy/mm/dd } ] [ end { yyyy-mm-dd | yyyy/mm/dd } ] Performs a test instance every day. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

You can run the start command to set the start mode and end mode for an NQA test instance.

There are following usage scenarios:
  • To perform a test instance within a specified time, run the start at yyyy/mm/dd hh:mm:ss end at yyyy/mm/dd hh:mm:ss command.
  • To start a test instance at a specified time and stop the test instance after the specified seconds, run the start at yyyy/mm/dd hh:mm:ss end lifetime seconds second command.
  • To start a test instance after the specified seconds and stop the test instance at a specified time, run the start delay seconds second end at yyyy/mm/dd hh:mm:ss command.
  • To perform a test instance immediately and stop the test instance after the specified seconds, run the start now end lifetime seconds second command.
  • To perform a test instance within a specified time every day, run the start daily hh:mm:ss to hh:mm:ss command.

You can properly start a test instance based on service requirements.

Precautions

If the number of the running test instances reaches the maximum value defined by the system, the start command is invalid.

For the same test instance, the start now command can be used again only when the previous configuration is complete.

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

The test result may be inaccurate if the configuration does not meet the requirement of the frequency formula in Table 18-58. When an NQA test instance starts, the switch automatically checks the test frequency for the instance. If the frequency does not meet the formula requirement, the system prompts you that the frequency needs to be set properly. To ensure accurate test result, modify the frequency setting.

Table 18-58  Frequency check
Test Instance Type Formula Argument
  • ICMP test instance
  • LSP Ping test instance
  • TCP test instance

frequency > interval x ( probeCount - 1 ) + timeout

  • frequency: the interval at which the NQA test instance is automatically executed.
  • interval: the interval at which the probe packets are sent in the NQA test instance.
  • probeCount: the number of probes to be sent each time for the NQA test instance.
  • timeout: the timeout period of a probe for the NQA test instance.
  • ICMP Jitter test instance
  • UDP Jitter test instance
frequency > interval x ( probeCount x jitter-packetnum - 1 ) + timeout
  • frequency: the interval at which the NQA test instance is automatically executed.
  • interval: the interval at which the probe packets are sent in the NQA test instance.
  • probeCount: the number of probes to be sent each time for the NQA test instance.
  • jitter-packetnum: the number of packets sent in each probe of the NQA test instance.
  • timeout: the timeout period of a probe for the NQA test instance.
  • LSP Trace test instance
  • Trace test instance
The value of frequency is equal to or larger than 60. frequency: the interval at which the NQA test instance is automatically executed.

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

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.

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

The test-failtimes command is invalid for ICMP Jitter, LSP Ping, and LSP Trace test instances.

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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 { icmp | icmpjitter | jitter | tcp | lspping | lsptrace | trace }

undo test-type

Parameters

Parameter Description Value
icmp Specifies an ICMP test. -
icmpjitter Specifies an ICMP jitter test, which can detect the jitter on the network by using ICMP packets. -
jitter Specifies a jitter test, which can detect the jitter during UDP packet transmission. -
lspping Specifies an LSP ping test. -
lsptrace Specifies an LSP trace route test. -
tcp Specifies a TCP test. -
trace Specifies a trace test. -

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

The type of a running test instance cannot be changed. If you change the type of a running NQA test instance, the test instance will fail.

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

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 is millisecond.
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 is millisecond.
rtd rtd-value Sets the RTD threshold. The value is an integer that ranges from 1 to 60000. The unit is millisecond.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.
NOTE:

This command is invalid for ICMP jitter, LSP ping, and LSP trace tests.

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 for 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. If the value is too small, the NQA test instance fails.

On an unstable network with a low transmission rate, you need to prolong the timeout period for sending probe packets to ensure that response packets can be received.

Prerequisites

The type of a test instance has been specified using the test-type command.

Precautions

  • You are advised to set the timeout period based on the round-trip time (RTT) value. Ensure that the timeout period set by the timeout command is longer than the RTT value.
  • In all test instances except jitter and ICMP jitter test instances, the timeout period set by the timeout command must be smaller than the interval of automatic tests set by the interval command. Otherwise, the tests fail due to timeout of test packets.

Precautions

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

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 indicate 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 and LSP trace test instances.

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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, and LSP Trace test instances in an NQA test.

The undo tracert-livetime command restores the default TTL value for 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 and LSP trace test instances.

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

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:
  • ICMP
  • ICMP Jitter
  • Jitter
  • TCP

Configuration Impact

If you run the tos command multiple times, only the latest configuration takes effect.

Precautions

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

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 following types of test instances are supported:
  • ICMP
  • ICMP Jitter
  • Jitter
  • TCP
  • LSP Ping

Configuration Impact

If you run the ttl command multiple times, only the latest configuration takes effect.

Precautions

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

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

vpn-instance

Function

The vpn-instance command configures the VPN instance that an NQA test instance belongs to.

The undo vpn-instance command deletes the configured VPN instance.

By default, no VPN instance is configured.

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 is a string of 1 to 31 case-sensitive characters except spaces. When double quotation marks are used to include the string, spaces are allowed in the string. The value _public_ is reserved and cannot be used as the VPN instance name.

Views

NQA view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The vpn-instance command sets the name of a VPN instance that the NQA test instance belongs to.

The VPN instance that the NQA test instance belongs to must be specified if the NQA test is performed on a VPN.

Configuration Impact

The VPN instance must be created and valid; otherwise, the probe fails.

After the VPN is deleted, the NQA test instance that uses the VPN is deleted.

Precautions

The vpn-instance command applies to ICMP, ICMP Jitter, Jitter, TCP, and Trace test instances.

If you attempt to change the advantage factor of a running test instance, the system asks you whether to stop the test instance. Select Y or N as required.
  • If you select Y, the test instance stops and the advantage factor is changed. To make the value take effect, run the commit command. To restart the test instance, run the start command.
  • If you select N, the advantage factor fails to be changed and the test instance keeps running.

Example

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

<HUAWEI> system-view
[~HUAWEI] ip vpn-instance vrf1
[*HUAWEI-vpn-instance-vrf1] ipv4-family
[*HUAWEI-vpn-instance-vrf1-af-ipv4] route-distinguisher 100:1
[*HUAWEI-vpn-instance-vrf1-af-ipv4] quit
[*HUAWEI-vpn-instance-vrf1] quit
[*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-03-21

Document ID: EDOC1000166501

Views: 52059

Downloads: 339

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