From 78f547514e54a9332b919734aed7c8ca1390cb48 Mon Sep 17 00:00:00 2001 From: Pierrick Louin Date: Sun, 8 Nov 2020 22:31:41 +0100 Subject: NFVBENCH-187: Augment --l2-loopback command line option capabilities [vlan(s)|no-tag|true|false] - Update documentation Clarify some fuzzy coding in options processing [nfvbench.py] Change-Id: Ie6eec7722bfa557924f435f268b852c300e160df Signed-off-by: Pierrick Louin --- docs/testing/user/userguide/readme.rst | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) (limited to 'docs/testing/user/userguide/readme.rst') diff --git a/docs/testing/user/userguide/readme.rst b/docs/testing/user/userguide/readme.rst index 50175c3..f6cc153 100644 --- a/docs/testing/user/userguide/readme.rst +++ b/docs/testing/user/userguide/readme.rst @@ -78,15 +78,22 @@ NFVbench supports settings that involve externally staged packet paths with or w Direct L2 Loopback (Switch or wire loopback) -------------------------------------------- -NFVbench supports benchmarking of pure L2 loopbacks (see "--l2-loopback vlan" option) +NFVbench supports benchmarking of pure L2 loopbacks - Switch level loopback - Port to port wire loopback -In this mode, NFVbench will take a vlan ID and send packets from each port to the other port -(dest MAC set to the other port MAC) using the same VLAN ID on both ports. +In this mode, NFVbench will send packets from each port to the other port +(the destination MAC address is set to the other port MAC address). This can be useful for example to verify that the connectivity to the switch is working properly. +Such a test can be quickly run using the CLI ``--l2-loopback`` :ref:`option `. + +For a typical test, packets will be VLAN tagged with the same ID on both ports. +However, multiple L2 vlan tagged service chains are also allowed, +which permits testing various configurations and the behavior of the bench itself. + + Traffic Generation ------------------ -- cgit 1.2.3-korg