Configuring an LSP Ping 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 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 lspping

      The test instance type is set to LSP 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. 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 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 { tunnelName | ifType ifNum } [ hot-standby | primary ] command.

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

   • To configure an SR-MPLS TE tunnel, run the lsp-tetunnel { tunnelName | ifType ifNum } [ hot-standby | primary ] command.

   • To configure the destination address for an SR-MPLS BE tunnel, run the destination-address ipv4 destAddress lsp-masklen maskLen command.

   • To configure the name, binding segment ID, endpoint IP address, and color ID of an SR-MPLS TE policy, run the policy { policy-name policyname | binding-sid bsid | endpoint-ip endpointip color colorid } command.

6. (Optional) Run lsp-nexthop nexthop-ip-address

   An IP address is configured for the next hop when load balancing is enabled.

   When load balancing is enabled on an ingress node, run the lsp-nexthop nexthop-ip-address command to configure an IP address for the next hop.

7. Set parameters for the test instance to simulate packets.
   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 source-address ipv4 ip-address

      The source IP address of NQA test packets is set.

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

      If the percentage of failed probes is greater than or equal to the failure percentage, the test is regarded as a failure.

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

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

11. Run commit

    The configuration is committed.