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

Configuration Guide - Network Management and Monitoring

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of Network Management and Monitoring, including SNMP, RMON, NETCONF, OpenFlow, LLDP, NQA, Mirroring, Packet Capture, Packet Trace, Path and Connectivity Detection Configuration, NetStream, sFlow, and iPCA.
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).
Starting an NQA Test Instance

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.

The test result may be inaccurate if the configuration does not meet the requirement of the frequency formula in Table 8-2. 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 8-2 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.

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 | yyyy/mm/dd } ] [ end { yyyy-mm-dd | 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.

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

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075365

Views: 33677

Downloads: 121

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