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

NE40E V800R010C00 Configuration Guide - System Monitor 01

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 NQA to Monitor an IP Network

Configuring NQA to Monitor an IP Network

When NQA is used to monitor an IP network, the following test instances can be configured. Before configuring NQA to monitor an IP network, familiarize yourself with the usage scenario of each test instance and complete the pre-configuration tasks.

Usage Scenario

Table 4-1  NQA test instances used to monitor IP networks
Test Type Usage Scenario
ICMP test An Internet Control Message Protocol (ICMP) test monitors the end-to-end connectivity, packet loss ratio, and delay time on an IP network.
TCP test A TCP test monitors the connectivity, packet loss ratio, and delay time of a TCP connection on an IP network.
UDP test A UDP test measures the round-trip delay time of UDP packets exchanged between Huawei devices.
SNMP test An SNMP test measures the communication speed between a host and an SNMP agent using UDP packets.
Trace test A trace test monitors the connectivity, packet loss ratio, and delay time hop by hop on an IP network and the packet forwarding path.
UDP jitter test A UDP jitter test measures the end-to-end jitter time for various services or simulates a voice test. Although the Internet Control Message Protocol (ICMP) reply function may be disabled on devices on the public network to defend against network attacks, the UDP jitter test can still be conducted.
ICMP Jitter test An Internet Control Message Protocol (ICMP) Jitter test measures the end-to-end jitter time for various services.
Path Jitter test An NQA path jitter test instance, however, can identify the router whose jitter value is great.
Path MTU test A path MTU test can obtain the maximum MTU value that does not require packet fragmentation during the packet transmission on the link.

Pre-configuration Tasks

Before configuring NQA to monitor an IP network, configure static routes or an Interior Gateway Protocol (IGP) to implement network connectivity.

Configuration Procedures

Perform one or more of the following configurations as required.

Configuring an ICMP Test

An Internet Control Message Protocol (ICMP) test monitors the end-to-end connectivity, packet loss ratio, and delay time on an IP network.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Create an NQA test instance and set the test instance type to ICMP.
    1. Run:

      nqa test-instance admin-name test-name

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

    2. Run:

      test-type icmp

      The test type is set to ICMP.

    3. (Optional) Run:

      description description

      A description is configured for the NQA test instance.

  3. (Optional)Run:

    destination-address ip-address

    The destination address (that is, the NQA server address) of the client is specified.

  4. Set parameters for the test instance to simulate a specific type of packet.
    1. Run:

      agetime time

      The aging time of an NQA test is configured.

    2. Run:

      datafill fillstring

      Padding characters in NQA test packets are configured.

    3. Run:

      datasize size

      The size of the data field in an NQA test packet.

    4. Run:

      probe-count number

      The number of probes in a test is set for the NQA test instance.

    5. Run:

      interval seconds interval

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

    6. Run:

      sendpacket passroute

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

    7. Run:

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

      The source IP address of NQA test packets is set.

    8. Run:

      source-interface interface-type interface-number

      The source interface for NQA test packets is set.

    9. Run:

      tos value

      The ToS value in NQA test packets is set.

    10. Run:

      ttl number

      The TTL value in NQA test packets is set.

    11. Run:

      nexthop ipv4 ip-address

      The next-hop address is configured for the test instance.

      NOTE:

      This command applies to an NQA track IPv4 static route scenario.

  5. Run:

    path-type bypass

    The Echo Request packets to be sent through an IP FRR bypass LSP is configured.

  6. (Optional) Configure test failure conditions.
    1. Run:

      timeout time

      The response timeout period is set.

      If no response packets are received before the set period expires, the probe is regarded as a failure.

    2. Run:

      fail-percent percent

      The failure percentage is set for the NQA test instance.

      If the percentage of failed probes is equal to or greater than the failure percentage, the test is regarded as a failure.

  7. (Optional) Configure the NQA statistics function.

    Run:

    records { history number | result number }

    The maximum number of history records and the maximum number of result records that can be saved for the NQA test instance are set.

  8. (Optional) Enable the device to send traps to the NMS.
    1. Run:

      test-failtimes times

      The NQA test instance is configured to send a trap message to the NMS when the number of continuous test failures reaches the specified value.

    2. Run:

      threshold rtd rtd-value

      The RTD threshold is set.

    3. Run:

      send-trap { all | [ rtd | testfailure | testcomplete ]* }

      The condition for triggering a trap is configured.

  9. (Optional) Run:

    vpn-instance vpn-instance-name

    The VPN instance name is configured for the NQA test instance.

  10. Schedule the test instance.
    1. (Optional) Run:

      frequency interval

      The test period is set for the NQA test instance.

      NOTE:
      If the following conditions are met, the Completion field in the test results will be displayed as no result:
      • frequency configured ≤ (probe-count - 1) x interval + timeout.

    2. Run:

      start

      An NQA test is started.

      The start command has multiple formats. Choose one of the following as needed.

      • To start an NQA test immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance at a specified time, run the 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 } } ] command.

      • To start an NQA test instance after a specified delay, run the 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 } } ] command.

      • To start an NQA test instance at a specified time every day, run the start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

  11. Run:

    commit

    The configuration is committed.

Configuring a TCP Test

A TCP test monitors the connectivity, packet loss ratio, and delay time of a TCP connection on an IP network.

Procedure

  • Configure the NQA server for the TCP test.

    1. Run:

      system-view

      The system view is displayed.

    2. Run:

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

      The IP address and number of the port used to monitor TCP services are specified on the NQA server.

    3. Run:

      commit

      The configuration is committed.

  • Configure the NQA client for the TCP test.
    1. Run:

      system-view

      The system view is displayed.

    2. Create an NQA test instance and set the test instance type to TCP.

      1. Run:

        nqa test-instance admin-name test-name

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

      2. Run:

        test-type tcp

        The test instance type is set to TCP.

      3. (Optional) Run:

        description description

        The description of the test instance is configured.

    3. Specify the destination address and destination port number for the test instance.

      NOTE:

      The destination address and destination port number specified in this step must be the same as ip-address and port-number specified for the NQA server.

      1. Run:

        destination-address ipv4 ip-address

        The client's destination address that is the NQA server address is specified.

      2. Run:

        destination-port port-number

        The destination port number is specified for the NQA test instance.

    4. (Optional) Set parameters for the test instance to simulate packets.

      1. Run:

        probe-count number

        The number of probes is set for an NQA test instance.

      2. Run:

        interval { milliseconds interval | seconds interval }

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

      3. Run:

        sendpacket passroute

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

      4. Run:

        source-address ipv4 ip-address

        The source IP address of NQA test packets is set.

      5. Run:

        source-port port-number

        The source port number is set for the NQA test instance.

      6. Run:

        tos value

        The ToS value in NQA test packets is set.

      7. Run:

        ttl number

        The TTL value in NQA test packets is set.

    5. (Optional) Configure test failure conditions.

      • Run:

        timeout time

        The response timeout period is set.

        If no response packets are received before the configured period elapses, the probe is considered as a failure.

      • Run:

        fail-percent percent

        The failure percentage is set for the NQA test instance.

        If the percentage of failed probes is greater than or equal to the configured failure percentage, the test is considered as a failure.

    6. (Optional) Configure the NQA statistics function.

      Run:

      records { history number | result number }

      The maximum number of historical records and the maximum number of result records that can be saved for the NQA test instance are set.

    7. (Optional) Enable the device to send traps to the NMS.

      1. Run:

        probe-failtimes

        The device enabled to send traps to the NMS after the number of consecutive probe failures reaches the specified threshold. By default, a trap is sent for each probe failure.

      2. Run:

        test-failtimes times

        The device is enabled to send traps to the NMS after the number of consecutive failures of the test instance reaches the specified threshold.

      3. Run:
        threshold rtd rtd-value

        The RTD threshold is set.

      4. Run:
        send-trap { all | [ rtd | testfailure | probefailure | testcomplete ]* }

        The condition for triggering a trap is configured.

    8. (Optional) Run:

      vpn-instance vpn-instance-name

      The VPN instance name is configured for the NQA test instance.

    9. Schedule the test instance.

      1. (Optional) Run:

        frequency interval

        The test period is set for the NQA test instance.

      2. Run:

        start

        An NQA test is started.

        The start command has multiple formats. Choose one of the following formats as needed.

        • To start an NQA test instance immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

        • To start an NQA test instance at a specified time, run the 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 } } ] command.

        • To start an NQA test instance after a specified delay, run the 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 } } ] command.

        • To start an NQA test instance at a specified time every day, run the start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

    10. Run:

      commit

      The configuration is committed.

Configuring a UDP Test

A UDP test measures the round-trip delay time of UDP packets exchanged between Huawei devices.

Procedure

  • Configure an NQA 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 IP address and port number of the NQA server for monitoring UDP services are specified.

    3. Run:
      commit

      The configuration is committed.

  • Configure an NQA client.
    1. Run:

      system-view

      The system view is displayed.

    2. Create an NQA test instance, set the test instance type to UDP, and add description information for the test instance.

      1. Run:
        nqa test-instance admin-name test-name

        The NQA test instance is created, and the view of the test instance is displayed.

      2. Run:
        test-type udp

        The test instance type is set to UDP.

      3. (Optional) Run:
        description description

        The description for of test instance is added.

    3. Specify the destination IP address and destination port number for the test instance.

      1. Run:
        destination-address ipv4 ip-address

        The destination IP address for the test instance (the IP address of the NQA server) is specified.

      2. (Optional) Run:

        destination-port port-number

        The destination port number for the test instance is specified.

    4. (Optional) Set parameters for the test instance and simulate packets.

      1. Run:

        agetime fillstring

        The aging time is set for the NQA test instance.

      2. Run:

        datafill fillstring

        The padding string in probe packets is set.

      3. Run:

        datasize size

        The size of the data field in an NQA test packet.

      4. Run:

        probe-count number

        The number of probes to be sent each time is set.

      5. Run:

        interval seconds interval

        The interval at which probe packets are sent is set.

      6. Run:

        sendpacket passroute

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

      7. Run:

        source-address ipv4 ip-address

        The source IP address of probe packets is set.

      8. Run:

        source-port port-number

        The source port number of probe packets is set.

      9. Run:

        tos value

        The ToS value in probe packets is set.

      10. Run:

        ttl number

        The TTL value in probe packets is set.

    5. (Optional) Configure probe failure conditions.

      • Run:

        timeout time

        Timeout period for response packets is set.

        If no response is received when the timeout period elapses, the probe fails.

      • Run:

        fail-percent percent

        The probe failure percentage is set for the test instance.

        If the percentage of failed probes is greater than or equal to the configured failure percentage, the test is considered as a failure.

    6. (Optional) Configure NQA statistics. Run:

      records { history number | result number }

      The maximum numbers of historical records and result records are set for the test instance.

    7. (Optional) Enable the device to send traps to the NMS.

      1. Run:

        probe-failtimes

        The device is enabled to send traps to the NMS after the number of consecutive probe failures reaches the specified threshold.

      2. Run:

        test-failtimes times

        The device is enabled to send traps to the NMS after the number of consecutive failures of the test instance reaches the specified threshold.

      3. Run:
        threshold rtd rtd-value

        The RTD threshold is set.

      4. Run:
        send-trap { all | [ rtd | testfailure | probefailure | testcomplete ]* }

        The condition for triggering a trap is configured.

    8. (Optional) Run:

      vpn-instance vpn-instance-name

      The VPN instance name is configured for the test instance.

    9. Schedule the test instance.

      1. (Optional) Run:

        frequency interval

        The test period is set for the NQA test instance.

      2. Run:

        start

        An NQA test is started.

        The start command has multiple formats. Select one of the following formats:

        • To start an NQA test instance immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

        • To start an NQA test instance at a specified time, run the 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 } } ] command.

        • To start an NQA test instance after a specified delay, run the 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 } } ] command.

        • To start an NQA test instance at a specified time every day, run the start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

    10. Run:

      commit

      The configuration is committed.

Configuring an SNMP Test

An SNMP test measures the communication speed between a host and an SNMP agent using UDP packets.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Create an NQA test instance and set the test instance type to SNMP.

    NOTE:

    Before configuring an NQA SNMP test instance, configure SNMP. The NQA SNMP test instance supports SNMPv1, SNMPv2c, and SNMPv3.

    1. Run:

      nqa test-instance admin-name test-name

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

    2. Run:

      test-type snmp

      The test instance type is set to SNMP.

    3. (Optional) Run:

      description description

      A description is configured for the NQA test instance.

  3. Run:

    destination-address ipv4 ip-address

    The destination address (that is, the NQA server address) of the client is specified.

  4. (Optional) Run:

    community read cipher community-name

    A community name is specified.

    If a target SNMP agent runs SNMPv1 or SNMPv2c, the read community name specified in the community read cipher command must be the same as the read community name configured on the SNMP agent. Otherwise, the SNMP test will fail.

  5. (Optional) Set parameters for the test instance and simulate packets.
    1. Run:

      probe-count number

      The number of probes in a test is set for the NQA test instance.

    2. Run:

      interval seconds interval

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

    3. Run:

      sendpacket passroute

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

    4. Run:

      source-address ipv4 ip-address

      The source IP address of NQA test packets is set.

    5. Run:

      source-port port-number

      The source port number is set for the NQA test instance.

      By default, the source port number is 0, and the system automatically allocates the port number.

    6. Run:

      tos value

      The ToS value in NQA test packets is set.

    7. Run:

      ttl number

      The TTL value in NQA test packets is set.

  6. (Optional) Configure probe failure conditions.
    1. Run:

      timeout time

      The response timeout period is set.

      If no response packets are received before the set period expires, the probe is regarded as a failure.

    2. Run:

      fail-percent percent

      The failure percentage is set for the NQA test instance.

      If the percentage of failed probes is equal to or greater than the failure percentage, the test is regarded as a failure.

  7. (Optional) Configure the NQA statistics function.

    Run:

    records { history number | result number }

    The maximum number of history records and the maximum number of result records that can be saved for the NQA test instance are set.

  8. (Optional) Enable the device to send traps to the NMS.
    1. Run:

      probe-failtimes

      The device is enabled to send traps to the NMS after the number of consecutive probe failures reaches the specified threshold.

    2. Run:

      test-failtimes times

      The NQA test instance is configured to send a trap message to the NMS when the number of continuous test failures reaches the specified value.

    3. Run:

      threshold rtd rtd-value

      The RTD threshold is set.

    4. Run:

      send-trap{ all | [ rtd | testfailure | probefailure | testcomplete ]* }

      The condition for triggering a trap is configured.

  9. (Optional) Run:

    vpn-instance vpn-instance-name

    The VPN instance name is configured for the NQA test instance.

  10. Schedule the test instance.
    1. (Optional) Run:

      frequency interval

      The test period is set for the NQA test instance.

    2. Run:

      start

      An NQA test is started.

      The start command has multiple formats. Choose one of the following as needed.

      • To start an NQA test immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance at a specified time, run the 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 } } ] command.

      • To start an NQA test instance after a specified delay, run the 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 } } ] command.

      • To start an NQA test instance at a specified time every day, run the start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

  11. Run:

    commit

    The configuration is committed.

Configuring a Trace Test

A trace test monitors the connectivity, packet loss ratio, and delay time hop by hop on an IP network and the packet forwarding path.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Create an NQA test instance and set the test instance type to trace.
    1. Run:

      nqa test-instance admin-name test-name

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

    2. Run:

      test-type trace

      The test instance type is set to trace.

    3. (Optional) Run:

      description description

      A description is configured for the NQA test instance.

  3. Specify the destination address and destination port number for the test instance.

    1. Run:

      destination-address ipv4 ip-address

      The destination address (that is, the NQA server address) of the client is specified.

    2. (Optional) Run:

      destination-port port-number

      The destination port number is specified for the NQA test instance.

  4. (Optional) Set parameters for the test instance to simulate packets.
    1. Run:

      agetime time

      The aging time of an NQA test is configured.

    2. Run:

      datafill fillstring

      Padding characters in NQA test packets are configured.

    3. Run:

      datasize size

      The size of the data field in an NQA test packet.

    4. Run:

      probe-count number

      The number of probes in a test is set for the NQA test instance.

    5. Run:

      sendpacket passroute

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

    6. Run:

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

      The source IP address of NQA test packets is set.

    7. Run:

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

      The TTL of test packets is set.

  5. (Optional) Run the set-df command to prevent packet fragmentation.

    Use a trace test instance to obtain the path MTU as follows:

    Run the set-df command to disable packet fragmentation. Then, run the datasize command to set the size of the packet data area. After that, start the test instance. If the test is successful, the size of the sent packet's data area is smaller than the path MTU. Then, keep increasing the packet data area size using the datasize command until the test fails. If the test fails, the size of the sent packet's data area is greater than the path MTU.

  6. (Optional) Configure test failure conditions.
    1. Run:

      timeout time

      The response timeout period is set.

      If no response packets are received before the set period expires, the probe is regarded as a failure.

    2. Run:

      tracert-hopfailtimes times

      The maximum number of hop failures in a probe is set.

  7. (Optional) Configure the NQA statistics function.

    Run:

    records { history number | result number }

    The maximum number of history records and the maximum number of result records that can be saved for the NQA test instance are set.

  8. (Optional) Enable the device to send traps to the NMS.
    1. Run:

      test-failtimes times

      The NQA test instance is configured to send a trap message to the NMS when the number of continuous test failures reaches the specified value.

    2. Run:

      threshold rtd rtd-value

      The RTD threshold is set.

    3. Run:

      send-trap { all | [ rtd | testfailure | testcomplete ]* }

      The condition for triggering a trap is configured.

  9. (Optional) Run:

    vpn-instance vpn-instance-name

    The VPN instance name is configured for the NQA test instance.

  10. Schedule the test instance.
    1. (Optional) Run:

      frequency interval

      The test period is set for the NQA test instance.

    2. Run:

      start

      An NQA test is started.

      The start command has multiple formats. Choose one of the following as needed.

      • To start an NQA test immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance at a specified time, run the 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 } } ] command.

      • To start an NQA test instance after a specified delay, run the 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 } } ] command.

      • To start an NQA test instance at a specified time every day, run the start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

  11. Run:

    commit

    The configuration is committed.

Configuring a UDP Jitter Test

A UDP jitter test measures the end-to-end jitter time for various services or simulates a voice test. Although the Internet Control Message Protocol (ICMP) reply function may be disabled on devices on the public network to defend against network attacks, the UDP jitter test can still be conducted.

Procedure

  • Configure the NQA server for the UDP jitter test.

    1. Run:

      system-view

      The system view is displayed.

    2. Run:

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

      The IP address and number of the port used to monitor UDP services are specified on the NQA server.

    3. Run:

      commit

      The configuration is committed.

  • Configure the NQA client for the UDP jitter test.
    1. Run:

      system-view

      The system view is displayed.

    2. (Optional) Run:

      nqa-jitter tag-version version-number

      The packet version is configured for a UDP jitter test instance.

      Packet statistics collected in version 2 is more accurate than those in version 1. Packet version 2 is recommended.

    3. Create an NQA test instance and set the test instance type to UDP jitter.

      1. Run:

        nqa test-instance admin-name test-name

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

      2. Run:
        test-type jitter

        The test instance type is set to UDP jitter.

      3. (Optional) Run:

        description description

        A description is configured for the test instance.

    4. The destination address and destination port number are set for the test instance.

      1. Run:

        destination-address ipv4 ip-address

        The client's destination address that is the NQA server address is specified.

      2. Run:

        destination-port port-number

        The destination port number is specified for the UDP jitter test.

    5. (Optional) Run:

      hardware-based enable

      The hardware forwarding engine on an interface board is enabled to send packets and add timestamps to the packets.

    6. (Optional) Run:

      timestamp-unit { millisecond | microsecond }

      A timestamp unit is configured for the NQA test instance.

      The timestamp units need to be configured only after the hardware-based enable command is run.

    7. (Optional) Configure the code type and advantage factor for simulated voice test calculation.

      1. Run:

        jitter-codec { g711a | g711u | g729a }

        The code type is set for the simulated voice test.

        If the code type is not set, a UDP jitter test instance is used to measure the jitter time of common services by default, not voice services.

      2. Run:

        adv-factor factor-value

        The advantage factor for simulated voice test calculation is set.

    8. (Optional) Set parameters for the test instance to simulate packets.

      1. Run:

        datasize size

        The size of the data field in an NQA test packet.

        By default, if the value of jitter-codec is g711a or g711u, the default size of the data field in an NQA test packet is 172 bytes. If the value of jitter-codec is g729a, the default size of the data field in an NQA test packet is 32 bytes.

      2. Run:

        jitter-packetnum number

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

      3. Run:

        probe-count number

        The number of probes is set for an NQA test instance.

      4. Run:

        interval { milliseconds interval | seconds interval }

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

      5. Run:

        sendpacket passroute

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

      6. Run:

        source-address ipv4 ip-address

        The source IP address of NQA test packets is set.

      7. Run:

        source-port port-number

        The source port number is set for the NQA test instance.

      8. Run:

        tos value

        The ToS value in NQA test packets is set.

      9. Run:

        ttl number

        The TTL value in NQA test packets is set.

    9. (Optional) Configure test failure conditions.

      • Run:

        timeout time

        The response timeout period is set.

        If no response packets are received after the configured period elapses, the probe fails.

      • Run:

        fail-percent percent

        The failure percentage is set for the NQA test instance.

        If the percentage of failed probes is greater than or equal to the configured failure percentage, the test is considered as a failure.

    10. (Optional) Configure the NQA statistics function.

      Run:

      records { history number | result number }

      The maximum number of historical records and the maximum number of result records that can be saved for the NQA test instance are set.

    11. (Optional) Enable the device to send traps to the NMS.

      1. Run:

        test-failtimes times

        The NQA test instance is configured to send a trap message to the NMS when the number of continuous probe failures reaches the specified value.

      2. Run:

        threshold { owd-ds owd-ds-value | owd-sd owd-sd-value | rtd rtd-value }

        The thresholds for the round-trip delay (RTD) and one-way delay (OWD) are set.

      3. Run:

        send-trap { all | [ owd-ds | owd-sd | rtd | testfailure ]* }

        The condition for triggering a trap is configured.

    12. (Optional) Run:

      vpn-instance vpn-instance-name

      The VPN instance name is configured for the NQA test instance.

    13. Schedule the test instance.

      1. (Optional) Run:

        frequency interval

        The test period is set for the NQA test instance.

      2. Run:

        start

        An NQA test is started.

        The start command has multiple formats. Choose one of the following formats as needed.

        • To start an NQA test instance immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

        • To start an NQA test instance at a specified time, run the 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 } } ] command.

        • To start an NQA test instance after a specified delay, run the 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 } } ] command.

        • To start an NQA test instance at a specified time every day, run the start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

    14. Run:

      commit

      The configuration is committed.

Configuring an ICMP Jitter Test

An Internet Control Message Protocol (ICMP) Jitter test measures the end-to-end jitter time for various services.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Create an NQA test instance and set the test instance type to ICMP Jitter.
    1. Run:

      nqa test-instance admin-name test-name

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

    2. Run:

      test-type icmpjitter

      The test instance type is set to ICMP Jitter.

    3. (Optional) Run:

      description description

      A description is configured for the NQA test instance.

  3. Run:

    destination-address ipv4 ip-address

    The destination address (that is, the NQA server address) of the client is specified.

  4. (Optional) Run:

    hardware-based enable

    The hardware forwarding engine on an interface board is enabled to send packets.

    NOTE:

    After you enable the interface board to send packets on a client, run the nqa-server icmp-server [ vpn-instance vpn-instance-name ] ip-address command on the NQA server to specify the IP address of the ICMP services monitored by the NQA server.

  5. (Optional) Run:

    timestamp-unit { millisecond | microsecond }

    A timestamp unit is configured for the NQA test instance.

    Perform this step only after the interface board is enabled to send packets.

  6. Set parameters for the test instance to simulate packets.
    1. Run:

      agetime time

      The aging time of an NQA test is configured.

    2. Run:

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

      The mode for an ICMP jitter test is set.

    3. Run:

      datafill fillstring

      Padding characters in NQA test packets are configured.

      Only supported when the icmp-jitter-mode is icmp-echo.

    4. Run:

      datasize size

      The size of the data field in an NQA test packet.

      Only supported when the icmp-jitter-mode is icmp-echo.

    5. Run:

      jitter-packetnum number

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

    6. Run:

      probe-count number

      The number of probes in a test is set for the NQA test instance.

    7. Run:

      interval { milliseconds interval | seconds interval }

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

    8. Run:

      source-address ipv4 ip-address

      The source IP address of NQA test packets is set.

    9. Run:

      ttl number

      The TTL value in NQA test packets is set.

    10. Run:

      tos value

      The ToS value in NQA test packets is set.

  7. (Optional) Configure test failure conditions.
    1. Run:

      timeout time

      The response timeout period is set.

      If no response packets are received before the set period expires, the probe is regarded as a failure.

    2. Run:

      fail-percent percent

      The failure percentage is set for the NQA test instance.

      If the percentage of failed probes is equal to or greater than the failure percentage, the test is regarded as a failure.

  8. (Optional) Configure the NQA statistics function.

    Run:

    records { history number | result number }

    The maximum number of history records and the maximum number of result records that can be saved for the NQA test instance are set.

  9. (Optional) Run:

    vpn-instance vpn-instance-name

    The VPN instance name is configured for the NQA test instance.

  10. Schedule the test instance.
    1. (Optional) Run:

      frequency interval

      The test period is set for the NQA test instance.

    2. Run:

      start

      An NQA test is started.

      The start command has multiple formats. Choose one of the following as needed.

      • To start an NQA test immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance at a specified time, run the 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 } } ] command.

      • To start an NQA test instance after a specified delay, run the 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 } } ] command.

      • To start an NQA test instance at a specified time every day, run the start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

  11. Run:

    commit

    The configuration is committed.

Configuring Parameters for the Path Jitter Test

An NQA path jitter test instance, however, can identify the router whose jitter value is great.

Context

Perform the following steps on the NQA client:

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 test instance view is displayed.

  3. Run:

    test-type pathjitter

    The type of the test instance is configured as path jitter.

  4. Run:

    destination-address ipv4 ip-address

    The destination IP address is configured.

  5. (Optional) Run the following commands to configure other parameters for the path jitter test:

    • Run:

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

      The mode of the path jitter test is configured.

    • Run:

      vpn-instance vpn-instance-name

      The VPN instance to be tested is configured.

    • Run:

      source-address ipv4 ip-address

      The source IP address is configured.

    • Run:

      probe-count number

      The number of test probes to be sent each time is set.

    • Run:

      jitter-packetnum number

      The number of test packets to be sent during each test is set.

      NOTE:

      The probe-count command is used to configure the number of times for the jitter test and the jitter-packetnum command is used to configure the number of test packets sent during each test. In actual configuration, the product of the number of times for the jitter test and the number of test packets must be less than 3000.

    • Run:

      interval seconds interval

      The interval for sending jitter test packets is set.

      The shorter the interval is, the sooner the test is complete. However, delays arise when the processor sends and receives test packets. Therefore, if the interval for sending test packets is set to a small value, a relatively greater error may occur in the statistics of the jitter test.

    • Run:

      fail-percent percent

      The percentage of the failed NQA tests is set.

  6. Run:

    start

    The NQA test is started.

    Select the start mode as required because the start command has several forms.

    • To perform the NQA test immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      The test instance is started immediately.

    • To perform the NQA test at the specified time, run the 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 } } ] command.

      The test instance is started at a specified time.

    • To perform the NQA test after a certain delay period, run the 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 } } ] command.

      The test instance is started after a certain delay.

Configuring Parameters for the Path MTU Test

A path MTU test can obtain the maximum MTU value that does not require packet fragmentation during the packet transmission on the link.

Context

Perform the following steps on the NQA client:

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 test instance view is displayed.

  3. Run:

    test-type pathmtu

    The type of the test instance is configured as path MTU.

  4. Run:

    destination-address ipv4 ip-address

    The destination IP address is configured.

  5. (Optional) Run the following commands to configure other parameters for the path MTU test.

    • Run:

      discovery-pmtu-max pmtu-max

      The maximum value of the path MTU test range is set.

    • Run:

      step step

      The value of the incremental step is set for the packet length in the path MTU test.

    • Run:

      vpn-instance vpn-instance-name

      The VPN instance to be tested is configured.

    • Run:

      source-address ipv4 ip-address

      The source IP address is configured.

    • Run:

      probe-count number

      The maximum number of probe packets that are allowed to time out consecutively is configured.

  6. Run:

    start

    The NQA test is started.

    Select the start mode as required because the start command has several forms.

    • To perform the NQA test immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      The test instance is started immediately.

    • To perform the NQA test at the specified time, run the 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 } } ] command.

      The test instance is started at a specified time.

    • To perform the NQA test after a certain delay period, run the 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 } } ] command.

      The test instance is started after a certain delay.

Checking the Configurations

After the test is complete, use the following commands to view test results.

Prerequisites

NOTE:
NQA test results are not displayed automatically on the terminal. To view test results, run the display nqa results command.

Procedure

  • Run the display nqa results [ collection ] [ test-instance admin-name test-name ] command to check NQA test results.
  • Run the display nqa results [collection] this command to check NQA test results in a specified NQA test instance view.
  • Run the display nqa history [ test-instance admin-name test-name ] command to check historical NQA test records.
  • Run the display nqa history [ this ] command to check historical statistics on NQA tests in a specified NQA test instance view.
  • Run the display nqa-server command to check the NQA server status.

Example

Run the display nqa results command to view NQA test results.

<HUAWEI> display nqa results test-instance admin icmp
 NQA entry(admin, icmp) :testFlag is inactive ,testtype is icmp
  1 . Test 1 result   The test is finished
   Send operation times: 3                     Receive response times: 3
   Completion:success                          RTD OverThresholds number: 0
   Attempts number:1                           Drop operation number:0   
   Disconnect operation number:0               Operation timeout number:0
   System busy operation number:0              Connection fail number:0   
   Operation sequence errors number:0          RTT Stats errors number:0
   Destination ip address:10.1.1.2
   Min/Max/Average Completion Time: 31/46/36   
   Sum/Square-Sum  Completion Time: 108/4038
   Last Good Probe Time: 2006-8-2 10:7:11.4    
   Lost packet ratio: 0 % 

Run the display nqa results [collection] this command to view NQA test results in a specified NQA test instance view.

<HUAWEI> system-view 
[*HUAWEI] nqa test-instance admin icmp
[*HUAWEI-nqa-admin-icmp] test-type icmp
[*HUAWEI-nqa-admin-icmp] display nqa results this
NQA entry(admin, icmp) :testFlag is inactive ,testtype is icmp
1 . Test 1 result The test is finished
    Send operation times: 3              Receive response times: 3 
    Completion:success                   RTD OverThresholds number: 0
    Attempts number:1                    Drop operation number:0
    Disconnect operation number:0        Operation timeout number:0
    System busy operation number:0       Connection fail number:0
    Operation sequence errors number:0   RTT Stats errors number:0
    Destination ip address:10.1.1.2
    Min/Max/Average Completion Time: 31/46/36
    Sum/Square-Sum Completion Time: 108/4038
    Last Good Probe Time: 2006-8-2 10:7:11.4
    Lost packet ratio: 0 % 

Run the display nqa history command to view historical NQA test records.

<HUAWEI> display nqa history test-instance admin icmp
NQA entry(admin,icmp) history:
--------------------------------------------------------------------------------
Index   T/H/P     Response Status       Address         Time
--------------------------------------------------------------------------------
 1      1/1/1        32ms  success      1.1.1.1         2015-11-27 10:12:38.511
 2      1/1/2        47ms  success      1.1.1.1         2015-11-27 10:12:42.520
 3      1/1/3        46ms  success      1.1.1.1         2015-11-27 10:12:46.531
--------------------------------------------------------------------------------

Run the display nqa history[ this ] command to view historical statistics on NQA tests in a specified NQA test instance view.

<HUAWEI> system-view 
[*HUAWEI] nqa test-instance admin icmp
[*HUAWEI-nqa-admin-icmp] test-type icmp
[*HUAWEI-nqa-admin-icmp] display nqa history this
NQA entry(admin,icmp) history:
--------------------------------------------------------------------------------
Index  T/H/P     Response Status       Address         Time
--------------------------------------------------------------------------------
 1     1/1/1         32ms success      1.1.1.1         2012-11-27 10:12:38.511
 2     1/1/2         47ms success      1.1.1.1         2012-11-27 10:12:42.520
 3     1/1/3         46ms success      1.1.1.1         2012-11-27 10:12:46.531
--------------------------------------------------------------------------------

Run the display nqa-server command to view the NQA server status.

<HUAWEI> display nqa-server 
 NQA Server Max: 5000                   NQA Server Num: 3                     
 NQA Concurrent TCP Server: 1           NQA Concurrent UDP Server: 2          
 NQA Concurrent ICMP Server: 0         
 nqa-server tcpconnect 100.1.1.2 6789 NOTINSERVICE
 nqa-server udpecho 200.1.1.2 6789 NOTINSERVICE
 nqa-server udpecho 172.16.1.1 6789 ACTIVE Hardware-based
Download
Updated: 2018-07-12

Document ID: EDOC1100028538

Views: 31652

Downloads: 235

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next