Report: COnfigure reoirt 2001.14

[csit.git] / docs / report / introduction / methodology_trex_traffic_generator.rst

diff --git a/docs/report/introduction/methodology_trex_traffic_generator.rst b/docs/report/introduction/methodology_trex_traffic_generator.rst
index 4d4de96..d9e7df5 100644 (file)
--- a/docs/report/introduction/methodology_trex_traffic_generator.rst
+++ b/docs/report/introduction/methodology_trex_traffic_generator.rst
@@ -4,17 +4,15 @@ TRex Traffic Generator
 Usage
 ~~~~~
 
 Usage
 ~~~~~
 

-`TRex traffic generator <https://wiki.fd.io/view/TRex>`_ is used for all
+`TRex traffic generator <https://trex-tgn.cisco.com>`_ is used for all

 CSIT performance tests. TRex stateless mode is used to measure NDR and
 CSIT performance tests. TRex stateless mode is used to measure NDR and

-PDR throughputs using binary search (NDR and PDR discovery tests) and
-for quick checks of DUT performance against the reference NDRs (NDR
-check tests) for specific configuration.
+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:
+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
 
 - If the TRex is not already installed on TG, it is installed in the

-  suite setup phase - see `TRex intallation`_.
+  suite setup phase - see `TRex installation`_.

 - TRex configuration is set in its configuration file
   ::
 
 - TRex configuration is set in its configuration file
   ::
 


@@ -23,11 +21,11 @@ is:
 - TRex is started in the background mode
   ::
 
 - TRex is started in the background mode
   ::
 

-  $ sh -c 'cd <t-rex-install-dir>/scripts/ && sudo nohup ./t-rex-64 -i -c 7 --iom 0 > /tmp/trex.log 2>&1 &' > /dev/null
+  $ 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
 
 - 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_lib.api.STLClient`.
+  :command:`trex.stl.api.STLClient`.

 
 Measuring Packet Loss
 ~~~~~~~~~~~~~~~~~~~~~
 
 Measuring Packet Loss
 ~~~~~~~~~~~~~~~~~~~~~


@@ -50,4 +48,4 @@ 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
 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.
+min/avg/max latency values and encoded HDRHstogram data.