From 8e49abe59fa559e319ce5a956c74881a6e0184a7 Mon Sep 17 00:00:00 2001 From: Al Morton Date: Fri, 2 Oct 2015 02:18:09 +0100 Subject: 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 Reviewed-by: Maryam Tahhan Reviewed-by: Billy O'Mahony Reviewed-by: Gene Snider --- docs/to-be-reorganized/vswitchperf_ltd.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/to-be-reorganized/vswitchperf_ltd.rst b/docs/to-be-reorganized/vswitchperf_ltd.rst index ccba2131..ee89c98b 100644 --- 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- cgit 1.2.3-korg