Changes between Version 11 and Version 12 of GENIFlowSpaceFirewallTests

Timestamp:

05/07/14 09:18:56 (10 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIFlowSpaceFirewallTests

@@ -86 +86 @@
 [[Image(fsfw-test-topology-step4.jpg)]]
 
-== 2.1 Test Methodology ==
+== 2.1 Test Characteristics ==
 
-Test Characteristics:
- - All test hosts are dedicate hosts (bare metal/raw-pc) unless otherwise stated
- - All results are captured for default bandwidth allocation (100Mb/s shaped), unless otherwise stated. 
- - All results collected between January 2014
+Each experiment will be run without and experimenter defined !OpenFlow Controller. Once shown to work, the experiment will add a user defined OpenFlow! Learning Switch controller.  
 
-Iperf TCP measurements captured in this page have the following assumptions:
- - All results are for a 60 second test run.
- - For !OpenFlow scenarios, traffic is exchanged before each of the measurements below to establish data flows:
+__Test Characteristics:__
+ - Both raw-pc and Xen VM will be used as IG end-points.  
+ - All requests will run with the default bandwidth allocation (100Mb/s), unless otherwise stated. 
+
+__Experimenter Generated traffic:__
+
+Iperf will be used to generate TCP and UDP traffic for 60 seconds test runs. For iperf TCP traffics, results will be collected for 1, 5 and 10 clients.  Commands used:
     - iperf '1 client' scenario command: 'iperf -c dest_host -t 60'
     - iperf '5 clients' scenario command: 'iperf -c dest_host -t 60 -P 5'
     - iperf '10 clients' scenario command: 'iperf -c dest_host -t 60 -P 10'
 
-Iperf UDP measurements captured in this page have the following assumptions:
- - Each test run is 60 seconds and traffic is exchanged before each of the measurements to establish a data flow.
- - UDP measurements between racks requested a bandwidth of 100 Mbits/sec, if results showed that 100Mb/s was possible, then increased to 1Gb/s.
+Iperf UDP measurements will request 100 Mbits/sec, based on results will increased or decrease bandwidth requests.
 
+Ping statistics will run got 60 seconds to capture network delay.
+