Configuring an LSP Trace Test

Procedure

1. Run system-view

   The system view is displayed.

2. Create an NQA test instance and set the test instance type to LSP trace.
   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 lsptrace

      The test instance type is set to LSP trace.

   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. Run lsp-type { ipv4 | te | bgp | srte | srbe | srte-policy }

   The LSP type is specified for the NQA test instance.

   If the LSP type of the NQA test instance is srbe, run the following commands as required:

   • To configure an IP address for a remote FEC, run the remote-fec ldp remoteIpAddr remoteMaskLen command.
   • To configure Echo Request packets to be transmitted through the bypass LSP, run the path-type bypass command.
   • To specify a Flex-Algo ID for an SR-MPLS BE tunnel used as a Flex-Algo tunnel, run the flex-algo flex-algo-id command.

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:

     destination-address ipv4 destAddress [ { lsp-masklen maskLen } | { lsp-loopback loopbackAddress } ] ^*

   • To configure the tunnel interface for a checked TE tunnel, run:

     lsp-tetunnel { tunnelName | ifType ifNum } [ hot-standby | primary ]

   • To configure the destination address for a BGP tunnel, run:

     destination-address ipv4 destAddress [ { lsp-masklen maskLen } | { lsp-loopback loopbackAddress } ] ^*

   • To configure the tunnel interface for an SR-MPLS TE tunnel, run:

     lsp-tetunnel { tunnelName | ifType ifNum } [ hot-standby | primary ]

   • To configure the destination address for an SR-MPLS BE tunnel, run:

     destination-address ipv4 destAddress lsp-masklen maskLen

   • To configure the name, binding segment ID, endpoint IP address, and color ID of an SR-MPLS TE policy, run:

     policy { policy-name policyname | binding-sid bsid | endpoint-ip endpointip color colorid }

6. (Optional) Set optional parameters for the NQA 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 LSP packet return mode is configured for the NQA test instance.

   3. Run probe-count number

      The number of probes in an NQA test instance is configured.

   4. Run source-address ipv4 srcAddress

      The source IP address of NQA test packets is set.

   5. Run tracert-livetime first-ttl first-ttl max-ttl max-ttl

      The TTL of test packets is set.

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

      The timeout period of response packets is set.

   2. Run tracert-hopfailtimes hopfailtimesValue

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

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 are set for the NQA test instance.

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

      The test period is set for the NQA test instance.

   2. Run start

      The NQA test instance 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.