Configuring an LSP Jitter Test

A label switched path (LSP) jitter test monitors the end-to-end jitter time on an MPLS network.

Procedure

  1. Run system-view
  2. Create an NQA test instance and set the test instance type to LSP jitter.
    1. Run nqa test-instance admin-name test-name

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

    2. Run test-type lspjitter

      The test instance type is set to LSP jitter.

    3. (Optional) Run description description

      A description is configured for the test instance.

  3. (Optional) Run fragment enable

    MPLS packet fragmentation is enabled for the NQA test instance.

  4. Run lsp-type { ipv4 | te }

    The LSP type is specified for the NQA test instance.

  5. Configure the destination address or tunnel interface based on the type of the checked LSP.

    • To configure the destination address for a checked LDP LSP, run the destination-address ipv4 destAddress [ { lsp-masklen maskLen } | { lsp-loopback loopbackAddress } ] * command.

    • To configure the tunnel interface for a checked TE tunnel, run the lsp-tetunnel tunnel ifNum command.

    • To configure the destination address for a BGP tunnel, run the destination-address ipv4 destAddress [ { lsp-masklen maskLen } | { lsp-loopback loopbackAddress } ] * command.

  6. (Optional) Set parameters for the test instance to simulate packets.
    1. Run lsp-exp exp
    2. Run lsp-replymode { level-control-channel | no-reply | udp }
    3. Run the datafill fill-string command to configure padding characters in NQA test packets.
    4. Run the datasize datasizeValue command to set the size of the data field in an NQA test packet.
    5. Run jitter-packetnum packetNum
    6. Run the probe-count number command to configure the number of probes in an NQA test instance.
    7. Run interval seconds interval

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

    8. Run source-addressipv4srcAddress

      The source IP address of NQA test packets is specified.

    9. Run the ttl ttlValue command to configure the TTL value of NQA test packets.
  7. (Optional) Configure test failure conditions.
    1. Run the timeout time command to configure the timeout period of response packets.
    2. Run the fail-percent percent command to configure the failure percentage for the NQA test instance.
  8. (Optional) Configure the NQA statistics function. Run the records { history number | result number } command to configure the maximum number of history records and the maximum number of result records for the NQA test instance.
  9. Schedule the test instance.
    1. (Optional) Run frequency frequencyValue
    2. Run the start command to start an NQA test.

      An NQA test instance can be started immediately, at a specified time, or after a specified delay.

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

      • 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 at a specified time.

      • 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 after a specified delay.

      • Run the start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command to start the test instance at the specified time every day.

  10. Run commit

    The configuration is committed.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >