Configuring a PWE3 Ping Test

A PWE3 ping test helps detect the pseudo wire (PW) connectivity, packet loss rate, and delay on a virtual private wire service (VPWS) network.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Create an NQA test instance and configure the test instance type as PWE3 ping.
    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 pwe3ping

      The test instance type is configured as PWE3 ping.

    3. 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 L2VPN network to be tested.
    1. Run local-pw-type pwTypeValue

      An encapsulation type is configured for the local PW.

    2. Run label-type { control-word | { { label-alert | normal } [ no-control-word ] } }

      A packet encapsulation type is configured.

    3. Run local-pw-id pwIdValue

      The local PW ID is configured.

  5. (Optional) Run peer-address peeraddress

    The peer IP address is configured.

  6. (Optional) Configure information about the remote PE when a multi-segment PW is to be tested.

    A multi-segment PW can be tested only when the label-type is control-word or normal.

    1. Run destination-address ipv4 destAddress

      The IP address for the remote PE is configured.

    2. Run remote-pw-id pwIdValue

      The remote PW ID is configured.

    3. (Optional) Run sender-address ipv4 ip-address

      The source IP address of the public network session between the device and the remote PE is configured. This IP address is the IP address of the adjacent SPE or UPE.

      The sender-address command is configured only when the device interworks with devices from other vendors.

    4. (Optional) Run ttl-copymode { pipe | uniform }

      A time to live (TTL) copy mode is set.

  7. Set optional parameters for the test instance and simulate packets transmitted on an actual network.
    1. Run lsp-exp exp

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

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

      The reply mode in the NQA LSP test instance is configured.

    3. Run datafill fill-string

      Padding characters in NQA test packets are configured.

    4. Run datasize datasizeValue

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

    5. Run probe-count number

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

    6. Run interval seconds interval

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

    7. Run ttl ttlValue

      The TTL value in NQA test packets is set.

  8. (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.

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

  10. (Optional) Enable the system to send traps to the NMS.

    1. Run the probe-failtimes failTimes command to enable the system to send traps to the NMS when the number of consecutive probe failures reaches the specified threshold.

    2. Run the test-failtimes failTimes command to enable the system to send traps to the NMS when the number of consecutive test failures reaches the specified threshold.

    3. Run the threshold rtd thresholdRtd command to configure an RTD threshold.
    4. Run the send-trap { all | [ rtd | testfailure | probefailure | testcomplete ]* } command to configure the condition for triggering a trap.

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

      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 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 startat [ 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 startdailyhh:mm:sstohh:mm:ss [ beginyyyy/mm/dd ] [ endyyyy/mm/dd ] command.

  12. Run commit

    The configuration is committed.

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