User Manual

TRex 41 / 113
distribution : "random"
clients_start : 26.0.0.1"
clients_end : 26.0.1.255"
tcp_aging : 0
udp_aging : 0
- name : "c"
pools_list :
- name:"a"
probability: 0.8
- name:"b"
probability: 0.2
4.12 Measuring Jitter/Latency
To measure jitter/latency using independent flows (SCTP or ICMP), use -l [Hz] where Hz defines the number of packets to
send from each port per second. This option measures latency and jitter. We can define the type of traffic used for the latency
measurement using the --l-pkt-mode option.
Option
ID
Type
0 default, SCTP packets
1 ICMP echo request packets from both sides
2 Send ICMP requests from one side, and matching ICMP responses from other side.
This is particulary usefull if your DUT drops traffic from outside, and you need to open pin hole to get the
outside traffic in (for example when testing a firewall)
3 Send ICMP request packets with a constant 0 sequence number from both sides.
The shell output is similar to the following:
Cpu Utilization : 0.1 %
if| tx_ok , rx_ok , rx ,error, average , max , Jitter
v
1
,max
| , , check, , latency(usec),latency (usec) ,(usec) , window
--------------------------------------------------------------------------------------
0 | 1002, 1002, 2501, 0, 61 , 70, 3 | 60 60
1 | 1002, 1002, 2012, 0, 56 , 63, 2 | 50 51
2 | 1002, 1002, 2322, 0, 66 , 74, 5 | 68 59
3 | 1002, 1002, 1727, 0, 58 , 68, 2 | 52 49
Rx Check stats enabled
---------------------------------------------------------------------------------------
rx check: avg/max/jitter latency, 94 , 744, 49
v
2
| 252 287 3
active flows: 10, fif: 308, drop: 0, errors: 0
---------------------------------------------------------------------------------------
v
1
,
v
2
Jitter information