Configuring a VPLS PW Ping Test

A virtual private local area network service (VPLS) pseudo wire (PW) ping test instance monitors the PW connectivity, packet loss ratios, and delay time on a VPLS network.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Create an NQA test instance and set the test instance type to VPLS PW ping.
    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 vplspwping

      The test instance type is set to VPLS PW ping.

    3. (Optional) Run description description

      A description is configured for the NQA test instance.

  3. (Optional) Run fragment enable

    MPLS packet fragmentation is enabled for the NQA test instance.

  4. Set parameters for the VPLS network to be monitored.
    1. Run vsi vsi-name

      The name of a virtual switching instance (VSI) to be monitored is specified.

    2. Run destination-address ipv4 ip-address

      An IP address of the remote PE is specified.

    3. (Optional) Run local-pw-id pwIdValue

      A PW ID is set on the local PE.

      If the VSI configured using the vsi vsi-name command has a specified negotiation-vc-id, the local-pw-id local-pw-id command must be run.

  5. (Optional) Set optional parameters for the test instance to simulate packet transmission.
    1. Run lsp-exp exp

      An LSP EXP value is set for the NQA test instance.

    2. Run lsp-replymode { level-control-channel | no-reply | udp }

      The mode in which LSPs are returned is set for the NQA test instance.

    3. Run datafill fill-string

      Padding characters are configured for NQA test packets.

    4. Run datasize datasizeValue

      The size of the data field in the NQA test packet is set.

    5. Run probe-count number

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

    6. Run interval seconds interval

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

    7. Run ttl ttlValue

      The TTL value of NQA test packets is set.

  6. (Optional) Configure test failure conditions.
    1. Run timeout time

      The timeout period of response packets is set.

    2. Run fail-percent percent

      The failure percentage is set for the NQA test instance.

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

      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 thresholdRtd

      The RTD threshold is set.

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

      The condition for triggering a trap is configured.

  9. Schedule the NQA test instance.
    1. (Optional) Run frequency frequencyValue

      The test period is set for the NQA test instance.

    2. Run start

      The NQA test is started.

      You can start an NQA test instance immediately, at a specified time, after a delay, or periodically.

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

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