User Manual

TRex 63 / 113
v
6
time in sec to linger the deallocation of TCP flows (in particular return the src_port to the pool). Good for cases when there
is a very high socket utilization (>50%) and there is a need to verify that socket source port are not wrapped and reuse.
Default value is zero. Better to keep it like that from performance point of view. High value could create performance
penalty
v
7
same as #11 for UDP flows
6.1.2 Timer Wheel section configuration
(from v2.13) see Timer Wheel section [timer_w]
6.1.3 Per template section
- name: cap2/dns.pcap
v
1
cps : 10.0
v
2
ipg : 10000
v
3
rtt : 10000
v
4
w : 1
v
5
server_addr : "48.0.0.7"
v
6
one_app_server : true
v
7
v
1
The name of the template pcap file. Can be relative path from the t-rex-64 image directory, or an absolute path. The pcap
file should include only one flow. (Exception: in case of plug-ins).
v
2
Connection per second. This is the value that will be used if specifying -m 1 from command line (giving -m x will multiply
this
v
3
If the global section of the YAML file includes cap_ipg :false, this line sets the inter-packet gap in microseconds.
v
4
Should be set to the same value as ipg (microseconds).
v
5
Default value: w=1. This indicates to the IP generator how to generate the flows. If w=2, two flows from the same
template will be generated in a burst (more for HTTP that has burst of flows).
v
6
If one_app_server is set to true, then all templates will use the same server.
v
7
If the same server address is required, set this value to true.
6.2 YAML Configuration File (parameter of --cfg option)
The configuration file, in YAML format, configures TRex behavior, including:
• IP address or MAC address for each port (source and destination).
• Masked interfaces, to ensure that TRex does not try to use the management ports as traffic ports.
• Changing the zmq/telnet TCP port.
You specify which config file to use by adding --cfg <file name> to the command line arguments.
If no --cfg given, the default /etc/trex_cfg.yaml is used.
Configuration file examples can be found in the $TREX_ROOT/scripts/cfg folder.