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

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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).
Configuring the NQA

Configuring the NQA

Configuring an NQA Test Instance

You can configure an NQA test instance to perform an NQA test of a specified type.

Pre-configuration Tasks

Before configuring the NQA test instance, complete the following tasks:

  • Starting the device
  • Configuring routing to ensure reachable routes between devices involved in the test
NOTE:

The pre-configuration tasks differ from different test instances. For details, see the configuration of each test instance.

Configuration Process

The following test instances are independent from each other. You can configure one or more test instances as required.

Configuring an ICMP Test Instance

Context

Before configuring an ICMP test instance, configure reachable routes between the NQA client and the tested device.

An ICMP test has the same function as the ping command but displays more detailed information.

NOTE:

Perform the following steps on the NQA client.

The timeout, probe-count, frequency, and interval commands constrain each other; therefore, properly set the values when running the four commands. Improper command settings may lead to test failure.

  • On a network with poor quality and low transmission rate, increase the timeout value to ensure that the response to NQA detection packets can be received.
  • On a network with low reliability, increase the probe-count value because multiple detection packets may need to be sent to ensure successful detection.
  • The interval value must be larger than the timeout value.
  • The frequency value must be larger than the product of interval and probe-count.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    nqa test-instance admin-name test-name

    An NQA test instance is created, and the NQA view is displayed.

  3. Run:

    test-type icmp

    The test type is set to ICMP.

  4. Run:

    destination-address { ipv4 ipv4-address | ipv6 ipv6-address }

    The destination address is configured.

  5. (Optional) Run the following commands as required to configure parameters for the ICMP test.

    • Run:

      description string

      A description is configured for the test instance.

    • Run:

      frequency interval

      The test period is set for the NQA test instance.

    • Run:

      timeout time

      The timeout period of a probe is set for the NQA test instance.

      By default, the timeout period of a ICMP probe is 3 seconds.

    • Run:

      source-interface interface-type interface-number

      The source interface that sends test packets is configured.

    • Run:

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

      The source IP address is configured.

      ip-address and ipv6-address are similar to -a in the ping command.

    • Run:

      ttl number

      The TTL value is set.

      number is similar to -h in the ping command.

    • Run:

      datasize size

      The size of Echo Request packets excluding the IP header is configured.

      size is similar to -s in the ping command.

    • Run:

      datafill fillstring

      The padding field is configured.

      fillstring is similar to -p in the ping command.

    • Run:

      sendpacket passroute

      The NQA test instance is configured to send packets without searching the routing table.

    • Run:

      probe-count number

      The number of probes in a test is set.

    • Run:

      tos value

      The type of service (ToS) field value in an IP header is configured.

      value is similar to -tos in the ping command.

    • Run:

      fail-percent percent

      The failure percentage is set for the NQA test instance.

    • Run:

      interval seconds interval

      The interval at which test packets are sent is configured.

      interval is similar to -m in the ping command.

    • Run:

      vpn-instance vpn-instance-name

      The VPN instance name is configured.

    • Run:

      records history number

      The maximum number of historical records is set for the NQA test instance.

    • Run:

      records result number

      The maximum number of result records is set for the NQA test instance.

    • Run:

      agetime hh:mm:ss

      The aging time is set for the NQA test instance.

  6. Run:

    commit

    The configuration is committed.

Configuring an ICMP Jitter Test Instance

Context

Before configuring an ICMP jitter test, ensure that the NQA client and the tested device have reachable routes to each other.

When configuring an ICMP jitter test instance, you can set the number of packets to be sent consecutively in a single test. This configuration can simulate traffic of various types in a specified period. For example, you can simulate voice service traffic through this configuration.

NOTE:

Perform the following steps on the NQA client. The NQA client also functions as the ICMP jitter client.

The timeout, probe-count, frequency, jitter-packetnum, and interval commands constrain each other; therefore, properly set the values when running the five commands. Improper command settings may lead to test failure.

  • On a network with poor quality and low transmission rate, increase the timeout value to ensure that the response to NQA detection packets can be received.

  • On a network with low reliability, increase the probe-count value because multiple detection packets may need to be sent to ensure successful detection.

  • The frequency value must comply with the following rules:

    frequency > probe-count × jitter-packetnum × interval + timeout

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    nqa test-instance admin-name test-name

    An NQA test instance is created, and the NQA view is displayed.

  3. Run:

    test-type icmpjitter

    The test type is set to ICMP Jitter.

  4. Run:

    destination-address ipv4 ipv4-address

    The destination address is configured.

  5. Configure global parameters for the test instance to simulate network packets.

    • Run:

      
      

      A description is configured for the test instance.

    • Run:

      
      

      The test period is set for the NQA test instance.

    • Run:

      
      

      The timeout period of a probe is set for the NQA test instance.

    • Run:

      
      

      The failure percentage is set for the NQA test instance.

      By default, the failure percentage is 100%, that is, the test is regarded failed only when all the probes fail.

    • Run:

      
      

      An NQA ICMP jitter test instance is created.

    • Run:

      
      

      The padding field is configured.

    • Run:

      
      

      The size of Echo Request packets without the IP header is configured.

    • Run:

      
      

      The number of packets sent each time in a probe is set.

    • Run:

      
      

      The number of probes in a test is set.

    • Run:

      
      

      The interval at which NQA test packets are sent is set.

      A shorter interval enables a test to be complete sooner. Delays occur during the sending and receiving of test packets on the processor. Therefore, if the interval for sending test packets is short, the ICMP Jitter test results are inaccurate.

    • Run:

      
      

      The source IP address is set.

    • Run:

      
      

      The TTL value in the NQA test packet is set.

    • Run:

      
      

      Type of Service (ToS) is set for the test packet.

    • Run:

      
      

      The VPN instance name is configured.

    • Run:

      
      

      The maximum number of historical records is set for the NQA test instance.

    • Run:

      
      

      The maximum number of result records is set for the NQA test instance.

    • Run:

      
      

      The aging time is set for the NQA test instance.

  6. Run:

    commit

    The configuration is committed.

Configuring a TCP Test Instance

Context

Before configuring a TCP test instance, configure a TCP server and ensure reachable routes between the TCP client and the TCP server.

An NQA TCP test measures the speed at which a TCP connection can be set up between an NQA client and a TCP server through the three-way handshake.

NOTE:

The NQA client also functions as the TCP client.

The timeout, probe-count, frequency, and interval commands constrain each other; therefore, properly set the values when running the four commands. Improper command settings may lead to test failure.

  • On a network with poor quality and low transmission rate, increase the timeout value to ensure that the response to NQA detection packets can be received.

  • On a network with low reliability, increase the probe-count value because multiple detection packets may need to be sent to ensure successful detection.

  • The interval value must be larger than the timeout value.

  • The frequency value must be larger than the product of interval and probe-count.

Procedure

  • Configure the TCP server.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

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

      The monitoring IP address and port number of the TCP server are configured.

  • Configure the NQA client.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      nqa test-instance admin-name test-name

      An NQA test instance is created, and the NQA view is displayed.

    3. Run:

      test-type tcp

      The test type is set to TCP.

    4. Run:

      destination-address ipv4 ipv4-address

      The destination IP address is configured.

    5. (Optional) Run the following commands as required to configure parameters for the TCP test.

      • Run:

        description string

        A description is configured for the test instance.

      • Run:

        frequency interval

        The test period is set for the NQA test instance.

      • Run:

        timeout time

        The timeout period of a probe is set for the NQA test instance.

      • Run:

        destination-port port-number

        The destination port number is configured.

      • Run:

        source-address ipv4 ipv4-address

        The source IP address is configured.

      • Run:

        source-port port-number

        The source port number is configured.

      • Run:

        ttl number

        The TTL value in the NQA test packet is set.

      • Run:

        sendpacket passroute

        The NQA test instance is configured to send packets without searching the routing table.

      • Run:

        probe-count number

        The number of probes in a test is set.

      • Run:

        tos value

        Type of Service (TOS) is set for the test packet.

      • Run:

        fail-percent percent

        The failure percentage is set for the NQA test instance.

      • Run:

        interval seconds interval

        The interval at which test packets are sent is configured.

      • Run:

        vpn-instance vpn-instance-name

        The VPN instance name is configured.

      • Run:

        records history number

        The maximum number of historical records is set for the NQA test instance.

      • Run:

        records result number

        The maximum number of result records is set for the NQA test instance.

      • Run:

        agetime hh:mm:ss

        The aging time is set for the NQA test instance.

    6. Run:

      commit

      The configuration is committed.

Configuring a UDP Jitter Test Instance

Context

When configuring a UDP Jitter test instance, configure reachable routes between the UDP Jitter client and the UDP Jitter server.

You can set the number of packets to be sent consecutively in each test instance. This configuration is used to simulate certain traffic. For example, G.711 traffic can be simulated within 1 minute by sending 3000 UDP packets at an interval of 20 milliseconds.

NOTE:

Configuring NTP on the client and the server can effectively improve the accuracy of the test.

The NQA client also functions as the UDP Jitter client. The jitter obtained in this test is the UDP Jitter. Perform the following steps on the NQA client.

The timeout, probe-count, frequency, jitter-packetnum, and interval commands constrain each other; therefore, properly set the values when running the five commands. Improper command settings may lead to test failure.

  • On a network with poor quality and low transmission rate, increase the timeout value to ensure that the response to NQA detection packets can be received.

  • On a network with low reliability, increase the probe-count value because multiple detection packets may need to be sent to ensure successful detection.

  • The frequency value must comply with the following rules:

    frequency > probe-count × jitter-packetnum × interval + timeout

Procedure

  • Configure the UDP Jitter server.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

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

      The monitoring IP address and port number of the UDP server are configured.

  • Configure the NQA client.
    1. Run:

      system-view

      The system view is displayed.

    2. (Optional) Run:

      nqa jitter tag-version version-number

      The version number is configured for Jitter packets.

      By default, the version number of Jitter test packets is 1.

      After setting the version number of the Jitter test packets to 2 and enabling the NQA client to collect statistics about packet loss in one direction, you can view the number of lost packets on the link from the source to the destination, from the destination to the source, or from unknown directions. Based on these statistics, you can easily locate network faults and detect malicious attacks.

    3. Run:

      nqa test-instance admin-name test-name

      An NQA test instance is created, and the NQA view is displayed.

    4. Run:

      test-type jitter

      The test type is set to Jitter.

    5. Run:

      destination-address ipv4 ipv4-address

      The destination address is configured.

    6. Run:

      destination-port port-number

      The destination port number is configured.

    7. (Optional) Run the following commands as required to configure parameters for the Jitter test:

      • Run:

        description string

        A description is configured for the test instance.

      • Run:

        frequency interval

        The test period is set for the NQA test instance.

      • Run:

        timeout time

        The timeout period of a probe is set for the NQA test instance.

      • Run:

        source-address ipv4 ipv4-address

        The source IP address is configured.

      • Run:

        source-port port-number

        The source port number is configured.

      • Run:

        ttl number

        The TTL value in the NQA test packet is set.

      • Run:

        datasize size

        The packet size is set for the NQA test instance.

      • Run:

        datafill fillstring

        The padding field is configured for the NQA test instance.

      • Run:

        source-interface interface-type interface-number

        The source interface that sends test packets is configured.

      • Run:

        sendpacket passroute

        The NQA test instance is configured to send packets without searching the routing table.

        By default, the NQA test packets are sent with searching the routing table.

      • Run:

        probe-count number

        The number of probes in each test is set.

        By default, the number of probes is 3.

      • Run:

        tos value

        Type of Service (TOS) is set for the test packet.

      • Run:

        fail-percent percent

        The failure percentage is set for the NQA test instance.

        By default, the failure percentage is 100%, that is, the test is regarded failed only when all the probes fail.

      • Run:

        interval { milliseconds interval | seconds interval }

        The interval at which test packets are sent is set.

        A shorter interval enables a test to be complete sooner. Delays occur during the sending and receiving of test packets on the processor. Therefore, if the interval for sending test packets is short, the Jitter test results are inaccurate.

      • Run:

        jitter-packetnum number

        The number of test packets sent in each probe is set.

        By default, 20 packets are sent each time in each test.

        The Jitter test is used to collect and analyze the delay variation during the UDP packet transmission. To improve the accuracy of the test result, the system sends multiple test packets each time. The more test packets are sent, the more accurate the statistics are, and the longer the test lasts.

        NOTE:

        The probe-count command sets the number of Jitter probes and the jitter-packetnum command sets the number of test packets sent during each probe. The product of probe count multiplied by the number of test packets must be smaller than or equal to 3000.

      • Run:

        jitter-codec { g711a | g711u | g729a }

        The code type is configured for jitter tests of analog voice services.

        This command is applied only to jitter tests of analog voice services.

      • Run:

        adv-factor factor-value

        The advantage factor is configured for analog voice test calculation.

        This command is applied only to jitter tests of analog voice services.

      • Run:

        vpn-instance vpn-instance-name

        The VPN instance name is configured.

      • Run:

        records history number

        The maximum number of historical records is set for the NQA test instance.

      • Run:

        records result number

        The maximum number of result records is set for the NQA test instance.

      • Run:

        agetime hh:mm:ss

        The aging time is set for the NQA test instance.

    8. Run:

      commit

      The configuration is committed.

Checking the Configuration

Prerequisites

After completing NQA configuration, run the following commands to check the NQA configuration.

Procedure

  • Run the display nqa server command on the NQA server to check information about the server.

Configuring the NQA Transmission Delay Threshold and Alarm Threshold

The statistics about the test packets that exceed the threshold are displayed in the NQA test result. This provides a basis for the network administrators to analyze the operating status of the specified service. The alarm information is sent to the NMS to report the change to the device.

Pre-configuration Tasks

Before configuring the NQA transmission threshold and alarm function, complete the following tasks:

  • Enabling the device
  • Creating the NQA test instance and configuring related parameters
Configuration Process

The configured NQA transmission threshold and Alarm Threshold help you obtain the statistics about the test packet that exceed the thresholds in the test result. This improves the NQA function and provides an optional configuration for NQA test.

The alarm information can be sent to the NMS only when the routes between the device and NMS are reachable and the related configurations are completed.

NOTE:

Perform the following configurations on the NQA client.

Configuring the Two-Way Transmission Delay Threshold

Context

If the two-way transmission delay threshold is configured for an NQA test instance, the statistics about the test packets that exceed the threshold are displayed in the test result. This provides a basis for the network administrators to analyze the operating status of the specified service.

NOTE:

The one-way transmission delay threshold can be configured only when the test-type is set to icmp, jitter, and tcp.

This two-way transmission delay refers to the round-trip transmission delay.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    nqa test-instance admin-name test-name

    The NQA view is displayed.

  3. Run:

    threshold rtd rtd-value

    The two-way transmission delay threshold is configured.

    By default, no two-way transmission delay threshold is configured.

  4. Run:

    commit

    The configuration is committed.

Configuring the One-Way Transmission Delay Threshold

Context

In Jitter tests , after the one-way transmission delay threshold is configured, the test results show statistics about the test packets of which the transmission exceeds the threshold. Network administrators can analyze the operating status of the network according to the test results.

NOTE:

The one-way transmission delay threshold can be configured only when the test-type is set to jitter.

You can perform either of 3 and 4 or both of them in any sequence.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    nqa test-instance admin-name test-name

    The NQA view is displayed.

  3. Run:

    threshold owd-sd owd-sd-value

    The one-way transmission delay threshold (from the source to the destination) is configured.

    By default, no one-way transmission delay threshold is configured.

  4. Run:

    threshold owd-ds owd-ds-value

    The one-way transmission delay threshold (from the destination to the source) is configured.

    By default, no one-way transmission threshold is configured.

  5. Run:

    commit

    The configuration is committed.

Configuring the Trap Function

A device generates traps no matter whether the NQA test succeeds or fails. You can enable or disable the trap function to determine whether the device sends traps to the NMS.

Context

NQA supports three types of traps as defined in DISMAN-PING-MIB. NQA also supports the sending of traps to the NMS when the one-way or two-way transmission delay exceeds the threshold.

  • For some test instances, if the two-way transmission delay exceeds the threshold and the trap function is enabled, traps are sent to the NMS with the specified IP address.
  • During a jitter test, if the one-way delay from the source to the destination or from the destination to the source exceeds the threshold and the trap function is enabled, the NQA client sends a trap message to the specified NMS IP address.

Traps carry the following information: destination IP addresses, operating status, destination IP address of the test packet, minimum RTT, maximum RTT, total RTT, number of sent probe packets, number of received packets, RTT square sum, and time of the latest successful probe.

Pre-configuration Tasks

Before configuring the trap function of the NQA test, complete the following tasks:

  • Configuring reachable routes between the NQA client and the NMS
  • Creating the NQA test instance and configuring related parameters
Configuration Process

The following configuration is a supplement to NQA tests. All configurations are optional.

The configurations take effect after the NQA alarm function is enabled.

NOTE:

Perform the following configurations on the NQA client.

Enabling the NQA Alarm Function

Context

After the NQA alarm function is enabled, the device sends alarms to the NMS.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

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

    The alarm function is enabled for the NQA module.

    By default, the alarm function is enabled for the NQA module.

  3. Run:

    commit

    The configuration is committed.

Configuring the NQA Client to Send Traps When a Test Fails

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    nqa test-instance admin-name test-name

    The NQA view is displayed.

  3. Run:

    send-trap testfailure

    The NQA client is configured to send traps when the test fails.

    By default, the NQA client sends no trap when an NQA test fails.

  4. Run:

    test-failtimes times

    The threshold on the traps sent after the NQA test fails is configured, The threshold specifies maximum number of continuous test failures for the NQA test instance.

    By default, a trap is sent for each test failure.

  5. Run:

    commit

    The configuration is committed.

Configuring the NQA Client to Send Traps When a Probe Fails

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    nqa test-instance admin-name test-name

    The NQA view is displayed.

  3. Run:

    send-trap probefailure

    The NQA client is configured to send traps when a probe fails.

    By default, the NQA client sends no trap when a probe fails.

    NOTE:

    This command cannot be configured when the test-type is set to jitter.

  4. Run:

    probe-failtimes times

    The threshold on the traps sent after the probe fails is configured, The threshold specifies maximum number of continuous probe failures for the NQA test instance.

    By default, a trap is sent for each probe failure.

    NOTE:

    This command cannot be configured when the test-type is set to jitter.

  5. Run:

    commit

    The configuration is committed.

Configuring the NQA Client to Send Traps After a Probe Succeeds

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    nqa test-instance admin-name test-name

    The NQA view is displayed.

  3. Run:

    send-trap testcomplete

    The NQA client is configured to send traps when a probe succeeds.

    By default, the NQA client sends no trap when a probe succeeds.

    NOTE:

    This command cannot be configured when the test-type is set to jitter.

  4. Run:

    commit

    The configuration is committed.

Configuring the NQA Client to Send Traps When the Transmission Delay Exceeds the Threshold

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    nqa test-instance admin-name test-name

    The NQA view is displayed.

  3. Run:

    send-trap { owd-ds | owd-sd | rtd }*

    The NQA client is configured to send traps when the transmission delay exceeds the threshold.

    By default, the NQA client sends no trap when the transmission delay exceeds the threshold.

    NOTE:

    Parameters owd-ds and owd-sd can be configured only for jitter test instances.

  4. Run:

    commit

    The configuration is committed.

Checking the Configuration

Context

After configuring the trap function, check the alarm information.

Procedure

  • Run the display snmp-agent trap feature-name nqa all command to check status of all traps on the NQA module.

Scheduling an NQA Test Instance

After completing the configuration of an NQA test instance, you can schedule the NQA test instance as required, for example, starting the NQA test instance.

Pre-configuration Tasks

Before scheduling an NQA test instance, complete the following tasks:

  • Configuring the server
  • Configuring an NQA test instance on the client
  • Configuring reachable routes between the server and the client
NOTE:

Perform the following configurations on the NQA client.

Starting an NQA Test Instance

Context

After completing the configuration of an NQA test instance, start the NQA test instance in following modes:
  • Start the NQA test instance immediately.
  • Start the NQA test instance at a specified time.
  • Start the NQA test instance after a delay.

If the test fails, restart the NQA test instance in the next time period.

NOTE:
  • If the number of 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 test is complete.
  • The specified time to start a test instance must be later than the current time of the device.

Procedure

  • Start an NQA test instance.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      nqa test-instance admin-name test-name

      The NQA view is displayed.

    3. Run:

      start

      The NQA test instance is started.

      • Run:

        start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ]

        The NQA test instance is started immediately.

      • Run:

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

        The NQA test instance is started in a specified time.

      • Run:

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

        The NQA test instance is started after a specified delay.

      • Run:

        start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ]

        The NQA test instance is started at a fixed time every day.

    4. Run:

      commit

      The configuration is committed.

  • Restart an NQA test instance.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      nqa test-instance admin-name test-name

      The NQA view is displayed.

    3. Run:

      restart

      Then NQA test instance is restarted.

      NOTE:
      • The restart command stops the running test instance and restart it.
      • The restart command functions the same as the start now command.

    4. Run:

      commit

      The configuration is committed.

(Optional) Stopping an NQA Test Instance

Context

A running NQA test instance can stop in the following modes:
  • The test stops automatically after all test packets are sent.
  • Stop the NQA test instance at a specified time.
  • Stop the NQA test instance after a delay.
  • Start a test instance and stop it at specified time every day.
Stop a running NQA test instance using either of the following commands:
  • Run the undo start command to stop the running NQA test instance.
  • Run the stop command to stop the running NQA test instance.

Procedure

  • Run the undo start command.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      nqa test-instance admin-name test-name

      The NQA view is displayed.

    3. Run:

      undo start

      The running NQA test instance is stopped.

    4. Run:

      commit

      The configuration is committed.

  • Run the stop command.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      nqa test-instance admin-name test-name

      The NQA view is displayed.

    3. Run:

      stop

      The running NQA test instance is stopped.

    4. Run:

      commit

      The configuration is committed.

Checking Test Results

Prerequisites

An NQA test instance has been configured and the NQA test has been completed.

NOTE:
  • The display nqa results command displays the test results of only the test instances that have been completed.
  • The display nqa results collection command displays accumulative results of all test instances. Only the jitter tests support the query of accumulative results.
  • The display nqa results collection this command displays accumulative results of all test instances. Only the jitter tests support the query of accumulative results.
  • Failed Jitter tests are not recorded in the historical records.

Procedure

  • Run the display nqa results [ collection ] [ test-instance admin-name test-name ] command to check NQA test results.
  • Run the display nqa history [ test-instance admin-name test-name ] command to check the historical records of NQA test instances.
  • Run the display nqa results [ collection ] this command to check results of an NQA test in the specified test instance view.
  • Run the display nqa history this command to check historical records of NQA tests in the specified test instance view.
Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 58691

Downloads: 3621

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