NFVBENCH-140 Retrieve High Dynamic Range latency histograms with TRex v2.59

[nfvbench.git] / docs / testing / user / userguide / hw_requirements.rst

diff --git a/docs/testing/user/userguide/hw_requirements.rst b/docs/testing/user/userguide/hw_requirements.rst
index acb4c0a..124e8a0 100644 (file)
--- a/docs/testing/user/userguide/hw_requirements.rst
+++ b/docs/testing/user/userguide/hw_requirements.rst
@@ -20,19 +20,17 @@ To run the TRex traffic generator (that is bundled with NFVbench) you will need
     - if you have only 1 TOR, wire both interfaces to that same TOR
     - 1 interface to each TOR if you have 2 TORs and want to use bonded links to your compute nodes
 
-.. image:: images/nfvbench-trex-setup.svg
+.. image:: images/nfvbench-trex-setup.png
 
 
 Switch Configuration
 --------------------
-For VLAN encapsulation, the 2 corresponding ports on the switch(es) facing the Trex ports on the Linux server should be configured in trunk mode (NFVbench will instruct TRex to insert the appropriate vlan tag).
-
-For VxLAN encapsulation, the switch(es) must support the VTEP feature (VxLAN Tunnel End Point) with the ability to attach an interface to a VTEP (this is an advanced feature that requires an NFVbench plugin for the switch).
+The 2 corresponding ports on the switch(es) facing the Trex ports on the Linux server should be configured in trunk mode (NFVbench will instruct TRex to insert the appropriate vlan tag).
 
 Using a TOR switch is more representative of a real deployment and allows to measure packet flows on any compute node in the rack without rewiring and includes the overhead of the TOR switch.
 
 Although not the primary targeted use case, NFVbench could also support the direct wiring of the traffic generator to
-a compute node without a switch (although that will limit some of the features that invove multiple compute nodes in the packet path).
+a compute node without a switch.
 
 Software Requirements
 ---------------------
@@ -69,11 +67,4 @@ Finally, the correct iommu options and huge pages to be configured on the Linux
 - enable intel_iommu and iommu pass through: "intel_iommu=on iommu=pt"
 - for Trex, pre-allocate 1024 huge pages of 2MB each (for a total of 2GB): "hugepagesz=2M hugepages=1024"
 
-More detailed instructions can be found in the DPDK documentation (https://media.readthedocs.org/pdf/dpdk/latest/dpdk.pdf).
-
-
-NFVbench loopback VM image Upload
----------------------------------
-
-The NFVbench loopback VM image should be uploaded to OpenStack prior to running NFVbench.
-The NFVbench VM qcow2 image can be rebuilt from script or can be copied from the OPNFV artifact repository [URL TBP].
+More detailed instructions can be found in the DPDK documentation (https://buildmedia.readthedocs.org/media/pdf/dpdk/latest/dpdk.pdf).