Configuring a PWE3 Trace Test

Procedure

1. Run system-view
2. Create an NQA test instance and set the test instance type to PWE3 trace.
   1. Run nqa test-instance admin-name test-name
   2. Run the test-type pwe3trace command to set the test instance type to PWE3 trace.
   3. (Optional) Run description description
3. (Optional) Run fragment enable

   MPLS packet fragmentation is enabled for the NQA test instance.

4. Set parameters for the Layer 2 virtual private network (L2VPN) to be monitored.
   1. Run local-pw-type pwTypeValue

      An encapsulation type is set for the PW on the local PE.

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

      An encapsulation type is set for packets.

   3. Run lsp-version { rfc4379 | ptn-mode }

      A protocol is configured for the LSP test instance.

   4. Run local-pw-id pwIdValue

      A PW ID is set on the local PE.

5. (Optional) Run peer-address peeraddress

   The peer IP address is configured.

6. (Optional) Configure remote provider edge (PE) information for a multi-segment PW to be monitored.

   An MS-PW can be monitored only after you specify control-word or normal.

   1. Run destination-address ipv4 destAddress

      An IP address is configured for the remote PE.

   2. Run remote-pw-id pwIdValue

      A PW ID is set for the remote PE.

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

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

7. (Optional) Set parameters for the test instance and simulate packets.
   1. Run lsp-exp exp
   2. Run lsp-replymode { level-control-channel | no-reply | udp } command to configure the LSP packet return mode for the NQA test instance.
   3. Run the probe-count number command to configure the number of probes in an NQA test instance.
   4. Run tracert-livetime first-ttl first-ttl max-ttl max-ttl

      The TTL of an NQA traceroute test instance is set.

8. (Optional) Configure test failure conditions.
   1. Run the timeout time command to configure the timeout period of response packets.
9. (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.
10. (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.

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

12. Run commit