User Manual

TRex 17 / 113
v
9
Number of TRex active "flows". Could be different than the number of router flows, due to aging issues. Usualy the TRex
number of active flows is much lower than that of the router because the router ages flows slower.
v
10
Total number of TRex flows opened since startup (including active ones, and ones already closed).
v
11
Drop rate.
v
12
Rx and latency thread CPU utilization.
v
13
Tx_ok on port 0 should equal Rx_ok on port 1, and vice versa.
3.5.2 Additional information about statistics in output
socket
Same as the active flows.
Socket/Clients
Average of active flows per client, calculated as active_flows/#clients.
Socket-util
Estimate of number of L4 ports (sockets) used per client IP. This is approximately (100*active_flows/#clients)/64K, calcu-
lated as (average active flows per client*100/64K). Utilization of more than 50% means that TRex is generating too many
flows per single client, and that more clients must be added in the generator configuration.
Max window
Maximum latency within a time window of 500 msec. There are few values shown per port. The earliest value is on the
left, and latest value (last 500msec) on the right. This can help in identifying spikes of high latency clearing after some
time. Maximum latency is the total maximum over the entire test duration. To best understand this, run TRex with the
latency option (-l) and watch the results with this section in mind.
Platform_factor
In some cases, users duplicate traffic using a splitter/switch. In this scenario, it is useful for all numbers displayed by TRex
to be multiplied by this factor, so that TRex counters will match the DUT counters.
Warning
If you do not see Rx packets, review the MAC address configuration.