test_spec: Expand deployment scenario in RFC2889 Broadcast Rate test

In the RFC 2889 Broadcast rate testing, four test ports are required.
One of the ports is connected to the test device, so it can send
broadcast frames and listen for miss-routed frames.

JIRA: VSPERF-103

Change-Id: I5ee3d20c71d7debf6c7b09fc094f72b2d4c10684
Signed-off-by: Al Morton <acmorton@att.com>
Reviewed-by: Maryam Tahhan <maryam.tahhan@intel.com>
Reviewed-by: Billy O'Mahony<billy.o.mahony@intel.com>
Reviewed-by: Gene Snider <eugene.snider@huawei.com>

diff --git a/docs/to-be-reorganized/vswitchperf_ltd.rst b/docs/to-be-reorganized/vswitchperf_ltd.rst
index ccba213..ee89c98 100644 (file)
--- a/docs/to-be-reorganized/vswitchperf_ltd.rst
+++ b/docs/to-be-reorganized/vswitchperf_ltd.rst
@@ -1659,7 +1659,9 @@ Test ID: LTD.Throughput.RFC2889.BroadcastFrameForwarding
 
     **Deployment scenario**:
 
-    -  Physical → virtual switch 3x physical.
+    -  Physical → virtual switch 3x physical. In the Broadcast rate testing,
+    four test ports are required. One of the ports is connected to the test
+    device, so it can send broadcast frames and listen for miss-routed frames.
 
 2.3.2 Packet Latency tests
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~