From ce2525c2a621af3d20fc58f03a8f88d29e0e3617 Mon Sep 17 00:00:00 2001 From: ahothan Date: Tue, 7 Apr 2020 08:26:12 -0700 Subject: NFVBENCH-161 NFVbench --force-cleanup deletes more ports than needed Change-Id: Id2c015248df6ef161b57192e1691a70af9bc2c9b Signed-off-by: ahothan --- docs/testing/user/userguide/hw_requirements.rst | 3 ++- docs/testing/user/userguide/readme.rst | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) (limited to 'docs/testing/user/userguide') diff --git a/docs/testing/user/userguide/hw_requirements.rst b/docs/testing/user/userguide/hw_requirements.rst index 124e8a0..44ab549 100644 --- a/docs/testing/user/userguide/hw_requirements.rst +++ b/docs/testing/user/userguide/hw_requirements.rst @@ -14,7 +14,8 @@ To run NFVbench you need the following hardware: - a DPDK compatible NIC with at least 2 ports (preferably 10Gbps or higher) - 2 ethernet cables between the NIC and the OpenStack pod under test (usually through a top of rack switch) -The DPDK-compliant NIC must be one supported by the TRex traffic generator (such as Intel X710, refer to the `Trex Installation Guide `_ for a complete list of supported NIC) +The DPDK-compliant NIC must be one supported by the TRex traffic generator (such as Intel X710, +refer to the Trex Installation Guide for a complete list of supported NIC) To run the TRex traffic generator (that is bundled with NFVbench) you will need to wire 2 physical interfaces of the NIC to the TOR switch(es): - if you have only 1 TOR, wire both interfaces to that same TOR diff --git a/docs/testing/user/userguide/readme.rst b/docs/testing/user/userguide/readme.rst index 1789d4a..50175c3 100644 --- a/docs/testing/user/userguide/readme.rst +++ b/docs/testing/user/userguide/readme.rst @@ -92,7 +92,7 @@ Traffic Generation NFVbench currently integrates with the open source TRex traffic generator: -- `TRex `_ (pre-built into the NFVbench container) +- `TRex `_ (pre-built into the NFVbench container) Supported Packet Paths -- cgit 1.2.3-korg