blob: d9e7df57d3b881883954acfd68a0dd096cd889ca (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
TRex Traffic Generator
----------------------
Usage
~~~~~
`TRex traffic generator <https://trex-tgn.cisco.com>`_ is used for all
CSIT performance tests. TRex stateless mode is used to measure NDR and
PDR throughputs using MLRsearch and to measure maximum transer rate
in MRR tests.
TRex is installed and run on the TG compute node. The typical procedure is:
- If the TRex is not already installed on TG, it is installed in the
suite setup phase - see `TRex installation`_.
- TRex configuration is set in its configuration file
::
/etc/trex_cfg.yaml
- TRex is started in the background mode
::
$ sh -c 'cd <t-rex-install-dir>/scripts/ && sudo nohup ./t-rex-64 -i --prefix $(hostname) --hdrh --no-scapy-server > /tmp/trex.log 2>&1 &' > /dev/null
- There are traffic streams dynamically prepared for each test, based on traffic
profiles. The traffic is sent and the statistics obtained using
:command:`trex.stl.api.STLClient`.
Measuring Packet Loss
~~~~~~~~~~~~~~~~~~~~~
Following sequence is followed to measure packet loss:
- Create an instance of STLClient.
- Connect to the client.
- Add all streams.
- Clear statistics.
- Send the traffic for defined time.
- Get the statistics.
If there is a warm-up phase required, the traffic is sent also before
test and the statistics are ignored.
Measuring Latency
~~~~~~~~~~~~~~~~~
If measurement of latency is requested, two more packet streams are
created (one for each direction) with TRex flow_stats parameter set to
STLFlowLatencyStats. In that case, returned statistics will also include
min/avg/max latency values and encoded HDRHstogram data.
|
