The NQA LSP Jitter test is performed to check the reachability of static LSP, LDP LSP, and TE tunnels. After receiving a packet from the source, the destination calculates the maximum, minimum, and average jitter time of the packet transmitted from the source to the destination. This clearly reflects the status of the MPLS network.
Before configuring the LSP Jitter test, configure an LSP tunnel or an MPLS TE tunnel.
LSP Jitter tests do not support load balancing.
Perform the following steps on the NQA client.
The system view is displayed.
An NQA test instance is created and the test instance view is displayed.
The test type is set to LSP Jitter.
Configure the LSP jitter test for the LSP tunnel.
Run lsp-type ipv4
The tunnel type is set to be the LSP tunnel.
Run destination-address ipv4 ipv4-address [ lsp-masklen masklen | lsp-masklen masklen lsp-loopback loopback-address | lsp-loopback loopback-address lsp-masklen masklen ]
The destination IP address of the LSP Jitter test is configured.
Configure the LSP jitter test for the MPLS TE tunnel.
Run lsp-type te
The tunnel type is set to be the MPLS TE tunnel.
Run lsp-tetunnel tunnel interface-number
The TE tunnel interface to be tested is configured.
To configure the next-hop IP address in the scenario where load balancing is enabled on the initiator of the LSP jitter test, run the lsp-nexthop nexthop-ip-address command.
The next-hop IP address can be configured only when lsp-type is IPv4 and lsp-version is RFC 4379.
To configure the response mode of the Echo packet, run the lsp-replymode { no-reply | udp } command.
In a uni-directional LSP Trace test, if the lsp-replymode no-reply command is configured, the test result shows that the test fails regardless of whether the test is successful or fails. If the test is successful, the test result also displays the number of the timeout packets. If the test fails, the test result displays the number of the discarded packets.
To configure the LSP EXP value, run the lsp-exp exp command.
Run description string
A description is configured for the test instance.
Run frequency interval
The test period is set for the NQA test instance.
Run timeout time
The timeout period of a probe is set for the NQA test instance.
Run source-address ipv4 ipv4-address
The source IP address is configured.
Run ttl number
The TTL value in the NQA test packet is set.
Run datafill fillstring
The padding field is configured for the NQA test instance.
Run datasize size
The packet size is set for the NQA test instance.
Run probe-count number
The number of probes in each test is set.
By default, the number of probes is 3.
Run jitter-packetnum number
The number of test packets sent in each probe is set.
By default, 20 packets are sent each time in each test.
The LSP Jitter test is used to collect and analyze the delay variation during the LSP Jitter test packet transmission. To improve the accuracy of the test result, the system sends multiple test packets each time. The more test packets are sent, the more accurate the statistics are, and the longer the test lasts.
The probe-count command sets the number of LSP Jitter probes and the jitter-packetnum command sets the number of test packets sent during each probe. The product of probe count multiplied by the number of test packets must be less than or equal to 3000.
Run probe-failtimes times
The number of permitted maximum probe failures, (the threshold to trigger the trap message) is set for the NQA test instance.
Run test-failtimes times
The trap threshold for continuous probe failures is set for the NQA test instance.
Run fail-percent percent
The failure percentage is set for the NQA test instance.
By default, the failure percentage is 100%, that is, the test is regarded failed only when all the probes fail.
Run interval seconds interval
The interval at which test packets are sent is set.
Run records history number
The maximum number of historical records is set for the NQA test instance.
Run records result number
The maximum number of result records is set for the NQA test instance.
Run agetime hh:mm:ss
The aging time is set for the NQA test instance.