213 | | Checking of monitoring status is replaced by iperf tests. Add capture here. |
| 213 | Iperf tests were run for a few scenarios and are captured in this step. The Iperf server is run on the InstaGENI VM for each scenario. |
| 214 | |
| 215 | __Two InstaGENI VMs on the Shared VLAN 1750__ |
| 216 | |
| 217 | In a scenario where two VMs where reserved on the shared VLAN 1750, Iperf was run to capture the following statistics: |
| 218 | |
| 219 | [ ID] Interval Transfer Bandwidth |
| 220 | [ 3] 0.0-10.0 sec 1.10 GBytes 941 Mbits/sec |
| 221 | |
| 222 | __ One InstaGENI VMs and One Emulab VM node both on share VLAN 1750__ |
| 223 | |
| 224 | In a scenario where one VMs was reserved on the shared VLAN 1750 and one VM node reserved on VLAN 1750 at the Emulab aggregate. Iperf was run to capture the following statistics: |
| 225 | |
| 226 | [ ID] Interval Transfer Bandwidth |
| 227 | [ 3] 0.0-10.0 sec 1.10 GBytes 941 Mbits/sec |
| 228 | |
| 229 | __ One InstaGENI VMs and One Rutgers WAPG node both on share VLAN 1750__ |
| 230 | |
| 231 | In a scenario where one VMs was reserved on the shared VLAN 1750 and one WAPG node at Rutgers reserved on VLAN 1750. Iperf was run to capture the following statistics: |
| 232 | |
| 233 | [ ID] Interval Transfer Bandwidth |
| 234 | |