User Manual

TRex 70 / 113
-d <num>
Duration of the test in seconds.
-e
Same as -p, but change the src/dst IP according to the port. Using this, you will get all the packets of the same flow from
the same port, and with the same src/dst IP.
It will not work good with NBAR as it expects all clients ip to be sent from same direction.
-f <yaml file>
Specify traffic YAML configuration file to use. Mandatory option for stateful mode.
--hops <num>
Provide number of hops in the setup (default is one hop). Relevant only if the Rx check is enabled. Look here for details.
--iom <mode>
I/O mode. Possible values: 0 (silent), 1 (normal), 2 (short).
--ipv6
Convert templates to IPv6 mode.
-k <num>
Run “warm up” traffic for num seconds before starting the test. This is needed if TRex is connected to switch running
spanning tree. You want the switch to see traffic from all relevant source MAC addresses before starting to send real data.
Traffic sent is the same used for the latency test (-l option)
Current limitation (holds for TRex version 1.82): does not work properly on VM.
-l <rate>
In parallel to the test, run latency check, sending packets at rate/sec from each interface.
--learn-mode <mode>
Learn the dynamic NAT translation. Look here for details.
--learn-verify
Used for testing the NAT learning mechanism. Do the learning as if DUT is doing NAT, but verify that packets are not
actually changed.
--limit-ports <port num>
Limit the number of ports used. Overrides the “port_limit” from config file.
--lm <hex bit mask>
Mask specifying which ports will send traffic. For example, 0x1 - Only port 0 will send. 0x4 - only port 2 will send. This
can be used to verify port connectivity. You can send packets from one port, and look at counters on the DUT.
--lo
Latency only - Send only latency packets. Do not send packets from the templates/pcap files.
-m <num>
Rate multiplier. TRex will multiply the CPS rate of each template by num.
--nc
If set, will terminate exacly at the end of the specified duration. This provides faster, more accurate TRex termination.
By default (without this option), TRex waits for all flows to terminate gracefully. In case of a very long flow, termination
might prolong.
--no-flow-control-change
Since version 2.21.
Prevents TRex from changing flow control. By default (without this option), TRex disables flow control at startup for all
cards, except for the Intel XL710 40G card.
--no-hw-flow-stat
Relevant only for Intel x710 stateless mode. Do not use HW counters for flow stats.
Enabling this will support lower traffic rate, but will also report RX byte count statistics.