wiki:GeniNetworkStitchingConfirmationTestStatus/Kansas

Version 10 (modified by lnevers@bbn.com, 4 years ago) (diff)

--

University of Kansas Stitching Confirmation Tests

This pages capture the detailed test logs for each test defined in the New Site Stitching Confirmation Tests page. For the sites status see the New Site Stitching Confirmation Tests Status page.

IG-ST-1 New Site to GPO IG topology

The KANSAS site advertises the following stitching details:

<stitching xmlns="http://hpn.east.isi.edu/rspec/ext/stitch/0.1/" lastUpdateTime="2014-11-18T18:30:48Z" >
<aggregate id="urn:publicid:IDN+instageni.ku.gpeni.net+authority+cm" url="https://www.instageni.ku.gpeni.net:12369/protoge
ni/xmlrpc/am">
<aggregatetype>protogeni</aggregatetype>
<stitchingmode>chainANDTree</stitchingmode>
<scheduledservices>false</scheduledservices>
<negotiatedservices>false</negotiatedservices>
<lifetime id="life">
    <start type="time">2014-11-18T18:30:48Z</start>
    <end type="time">2014-11-18T18:30:48Z</end>
</lifetime>
<node id="urn:publicid:IDN+instageni.ku.gpeni.net+node+procurve2">
  <port id="urn:publicid:IDN+instageni.ku.gpeni.net+stitchport+procurve2:1.24.al2s">
    <capacity>1000000</capacity>
    <maximumReservableCapacity>1000000</maximumReservableCapacity>
    <minimumReservableCapacity>1000</minimumReservableCapacity>
    <granularity>1</granularity>
    <link id="urn:publicid:IDN+instageni.ku.gpeni.net+interface+procurve2:1.24.al2s">
      <remoteLinkId>urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:kansas-ig</remoteLi
nkId>
      <trafficEngineeringMetric>10</trafficEngineeringMetric>
      <capacity>1000000</capacity>
      <maximumReservableCapacity>1000000</maximumReservableCapacity>
      <minimumReservableCapacity>1000</minimumReservableCapacity>
      <granularity>1</granularity>
      <switchingCapabilityDescriptor>
        <switchingcapType>l2sc</switchingcapType>
        <encodingType>ethernet</encodingType>
        <switchingCapabilitySpecificInfo>
         <switchingCapabilitySpecificInfo_L2sc>
          <interfaceMTU>1500</interfaceMTU>
          <vlanRangeAvailability>1170-1189</vlanRangeAvailability>
          <vlanTranslation>false</vlanTranslation>
         </switchingCapabilitySpecificInfo_L2sc>
        </switchingCapabilitySpecificInfo>
      </switchingCapabilityDescriptor>
    </link>
  </port>
</node>
</aggregate>
</stitching>

Experimenter may not need any of this data, but it is helpful to reference when trying to determine how many VLANs are delegated for stitching at the site or how much bandwidth can be requested.

Create a slice and then create the stitched slivers with the RSpec IG-ST-1-al2s.rspec:

$ stitcher.py createsliver IG-ST-1a IG-ST-1-al2s.rspec -o
14:15:31 INFO    : Configured logging from file /home/lnevers/gcf-2.7/src/gcf/stitcher_logging.conf
14:15:32 INFO    : Reading slice IG-ST-1a credential...
14:15:32 INFO    : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-1a expires on 2014-11-25 19:13:52 UTC
14:15:32 INFO    : Using SCS at http://nutshell.maxgigapop.net:8081/geni/xmlrpc
14:15:32 INFO    : Calling SCS...
14:15:33 INFO    : Multi-AM reservation will include resources from these aggregates:
14:15:33 INFO    : 	<Aggregate gpo-ig>
14:15:33 INFO    : 	<Aggregate kansas-ig>
14:15:33 INFO    : 	<Aggregate oess>
14:15:33 INFO    : 	<Aggregate ion>
14:15:33 INFO    : Stitcher doing createsliver at <Aggregate gpo-ig>...
14:15:55 INFO    : ... Allocation at <Aggregate gpo-ig> complete.
14:15:55 INFO    : Stitcher doing createsliver at <Aggregate kansas-ig>...
14:16:11 INFO    : ... Allocation at <Aggregate kansas-ig> complete.
14:16:11 INFO    : Stitcher doing createsliver at <Aggregate oess>...
14:16:15 INFO    : ... Allocation at <Aggregate oess> complete.
14:16:15 INFO    : Stitcher doing createsliver at <Aggregate ion>...
14:17:02 INFO    : DCN AM <Aggregate ion>: must wait for status ready....
14:17:02 INFO    : Pausing 30 seconds to let circuit become ready...
14:17:40 INFO    : DCN circuit 139211 is ready at <Aggregate ion>
14:17:47 INFO    : ... Allocation at <Aggregate ion> complete.
14:17:47 INFO    : All aggregates are complete.
14:17:47 INFO    : Your resources expire at 2014-11-24T19:05:33 (UTC). 
14:17:47 INFO    : Saved combined reservation RSpec at 4 AMs to file '/home/lnevers/gcf-test/stitch-test/Kansas/IG-ST-1a-manifest-rspec-multiam-combined.xml'
Success: Reserved resources in slice IG-ST-1a at 4 Aggregates (including 2 intermediate aggregate(s) not in the original request), creating 1 stitched link(s).

Determined login information at each KANSAS and GPO aggregate:

$ readyToLogin.py IG-ST-1a -a kansas-ig
  ....
ig-chic's geni_status is: ready 
User lnevers logs in to ig-chic using:
	ssh -p 30010  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.instageni.ku.gpeni.net

$ readyToLogin.py IG-ST-1a -a gpo-ig
  ....
ig-gpo's geni_status is: changing 
User lnevers logs in to ig-gpo using:
	ssh -p 34362  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc5.instageni.gpolab.bbn.com

Measurements

Iperf InstaGENI GPO VM to InstaGENI KANSAS VM (TCP) - TCP window size: 23.5 KByte (default)

Collected: 2014-11-18

One Client_

[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-60.1 sec   141 MBytes  19.7 Mbits/sec

Five Clients

[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-60.0 sec  36.5 MBytes  5.10 Mbits/sec
[  5]  0.0-60.1 sec  28.6 MBytes  4.00 Mbits/sec
[  7]  0.0-60.2 sec  23.1 MBytes  3.22 Mbits/sec
[  6]  0.0-60.3 sec  26.0 MBytes  3.62 Mbits/sec
[  3]  0.0-60.4 sec  29.8 MBytes  4.13 Mbits/sec
[SUM]  0.0-60.4 sec   144 MBytes  20.0 Mbits/sec

Ten Clients

[ ID] Interval       Transfer     Bandwidth
[  8]  0.0-60.1 sec  18.2 MBytes  2.55 Mbits/sec
[  5]  0.0-60.1 sec  15.1 MBytes  2.11 Mbits/sec
[  3]  0.0-60.2 sec  21.1 MBytes  2.95 Mbits/sec
[ 12]  0.0-60.4 sec  8.12 MBytes  1.13 Mbits/sec
[ 10]  0.0-60.5 sec  12.8 MBytes  1.77 Mbits/sec
[  9]  0.0-61.1 sec  12.1 MBytes  1.67 Mbits/sec
[ 11]  0.0-61.5 sec  12.2 MBytes  1.67 Mbits/sec
[  4]  0.0-61.6 sec  16.8 MBytes  2.28 Mbits/sec
[  7]  0.0-61.6 sec  19.6 MBytes  2.67 Mbits/sec
[  6]  0.0-61.7 sec  10.4 MBytes  1.41 Mbits/sec
[SUM]  0.0-61.7 sec   146 MBytes  19.9 Mbits/sec

Iperf InstaGENI GPO VM to InstaGENI KANSAS VM (UDP) - UDP buffer size: 224 KByte (default)

[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-60.0 sec   719 MBytes   101 Mbits/sec
[  3] Sent 512813 datagrams
[  3] Server Report:
[  3]  0.0-60.0 sec   139 MBytes  19.5 Mbits/sec   0.108 ms 413476/512808 (81%)
[  3]  0.0-60.0 sec  1 datagrams received out-of-order

Ping from InstaGENI GPO VM to the InstaGENI KANSAS VM

60 packets transmitted, 60 received, 0% packet loss, time 59087ms
rtt min/avg/max/mdev = 43.975/44.447/49.426/0.679 ms

Iperf InstaGENI KANSAS VM to GPO InstaGENI VM (TCP) - TCP window size: 23.5 KByte (default)

Collected: 2014-11-18

One Client_

[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-60.2 sec   142 MBytes  19.8 Mbits/sec

Five Clients

[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-60.1 sec  25.1 MBytes  3.51 Mbits/sec
[  7]  0.0-60.2 sec  41.8 MBytes  5.82 Mbits/sec
[  5]  0.0-60.2 sec  24.8 MBytes  3.45 Mbits/sec
[  3]  0.0-60.6 sec  28.2 MBytes  3.91 Mbits/sec
[  6]  0.0-61.5 sec  24.2 MBytes  3.31 Mbits/sec
[SUM]  0.0-61.5 sec   144 MBytes  19.7 Mbits/sec

Ten Clients

[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-60.3 sec  11.9 MBytes  1.65 Mbits/sec
[ 10]  0.0-60.3 sec  14.1 MBytes  1.97 Mbits/sec
[  9]  0.0-60.3 sec  14.5 MBytes  2.02 Mbits/sec
[  4]  0.0-60.5 sec  18.1 MBytes  2.51 Mbits/sec
[  7]  0.0-60.7 sec  17.1 MBytes  2.37 Mbits/sec
[ 12]  0.0-60.7 sec  12.2 MBytes  1.69 Mbits/sec
[  5]  0.0-61.0 sec  16.9 MBytes  2.32 Mbits/sec
[  8]  0.0-61.1 sec  11.8 MBytes  1.61 Mbits/sec
[ 11]  0.0-61.4 sec  17.8 MBytes  2.43 Mbits/sec
[  6]  0.0-61.7 sec  12.1 MBytes  1.65 Mbits/sec
[SUM]  0.0-61.7 sec   146 MBytes  19.9 Mbits/sec

Iperf InstaGENI KANSAS VM to GPO InstaGENI VM (UDP) - UDP buffer size: 224 KByte (default)

[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-60.0 sec   719 MBytes   101 Mbits/sec
[  3] Sent 512806 datagrams
[  3] Server Report:
[  3]  0.0-60.2 sec   139 MBytes  19.4 Mbits/sec  13.769 ms 413480/512803 (81%)
[  3]  0.0-60.2 sec  1 datagrams received out-of-order

Ping from InstaGENI KANSAS VM to GPO InstaGENI VM

60 packets transmitted, 60 received, 0% packet loss, time 59031ms
rtt min/avg/max/mdev = 44.061/44.395/45.072/0.330 ms

IG-ST-2 New Site to GPO IG Loop topology

Create a slice and then create the stitched slivers with the RSpec IG-ST-2.rspec:

$ stitcher.py createsliver IG-ST-2a IG-ST-2.rspec -o
14:45:41 INFO    : Configured logging from file /home/lnevers/gcf-2.7/src/gcf/stitcher_logging.conf
14:45:41 INFO    : Reading slice IG-ST-2a credential...
14:45:42 INFO    : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-2a expires on 2014-11-25 19:45:40 UTC
14:45:42 INFO    : Using SCS at http://nutshell.maxgigapop.net:8081/geni/xmlrpc
14:45:42 INFO    : Calling SCS...
14:45:44 INFO    : Multi-AM reservation will include resources from these aggregates:
14:45:44 INFO    : 	<Aggregate gpo-ig>
14:45:44 INFO    : 	<Aggregate kansas-ig>
14:45:44 INFO    : 	<Aggregate oess>
14:45:44 INFO    : 	<Aggregate ion>
14:45:44 INFO    : Stitcher doing createsliver at <Aggregate gpo-ig>...
14:46:07 INFO    : ... Allocation at <Aggregate gpo-ig> complete.
14:46:07 INFO    : Stitcher doing createsliver at <Aggregate kansas-ig>...
14:46:23 INFO    : ... Allocation at <Aggregate kansas-ig> complete.
14:46:24 INFO    : Stitcher doing createsliver at <Aggregate oess>...
14:46:29 INFO    : ... Allocation at <Aggregate oess> complete.
14:46:29 INFO    : Stitcher doing createsliver at <Aggregate ion>...
14:47:21 INFO    : DCN AM <Aggregate ion>: must wait for status ready....
14:47:21 INFO    : Pausing 30 seconds to let circuit become ready...
14:48:00 INFO    : Pausing 30 seconds to let circuit become ready...
14:48:41 INFO    : DCN circuit 139251 is ready at <Aggregate ion>
14:48:49 INFO    : ... Allocation at <Aggregate ion> complete.
14:48:49 INFO    : All aggregates are complete.
14:48:49 INFO    : Your resources expire at 2014-11-24T19:35:44 (UTC). 
14:48:49 INFO    : Saved combined reservation RSpec at 4 AMs to file '/home/lnevers/gcf-test/stitch-test/Kansas/IG-ST-2a-manifest-rspec-multiam-combined.xml'
Success: Reserved resources in slice IG-ST-2a at 4 Aggregates (including 2 intermediate aggregate(s) not in the original request), creating 2 stitched link(s).

Determined login information at each KANSAS and GPO aggregate:

$ readyToLogin.py IG-ST-2a -a kansas-ig
  ....

ig-kans's geni_status is: ready 
User lnevers logs in to ig-kans using:
	ssh -p 30010  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc2.instageni.ku.gpeni.net

$ readyToLogin.py IG-ST-2a -a gpo-ig
  ....
ig-gpo's geni_status is: ready 
User lnevers logs in to ig-gpo using:
	ssh -p 35642  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.instageni.gpolab.bbn.com

Login to GPO host and ping the remote on each of the two interfaces. Below is the ping output for the GPO site:

$ remote-execute.py IG-ST-2a -a gpo-ig -m "ping 10.10.4.2 -c 60 -q ;ping 192.168.4.2 -c 60 -q"
1. Find login Info for hosts in slice IG-ST-2a
2. Send command 'ping 10.10.4.2 -c 60 -q ;ping 192.168.4.2 -c 60 -q' to ig-gpo

PING 10.10.4.2 (10.10.4.2) 56(84) bytes of data.

--- 10.10.4.2 ping statistics ---
60 packets transmitted, 60 received, 0% packet loss, time 59100ms
rtt min/avg/max/mdev = 43.644/43.709/44.034/0.224 ms
PING 192.168.4.2 (192.168.4.2) 56(84) bytes of data.

--- 192.168.4.2 ping statistics ---
60 packets transmitted, 60 received, 0% packet loss, time 59104ms
rtt min/avg/max/mdev = 43.645/43.709/43.829/0.199 ms
... Done with command 'ping 10.10.4.2 -c 60 -q ;ping 192.168.4.2 -c 60 -q' at ig-gpo

IG-ST-3 IG-ST-3 New Site 3 node linear topology

Create a slice and then create the stitched slivers with the RSpec IG-ST-3.rspec:

$ stitcher.py createsliver IG-ST-3 IG-ST-3.rspec -o
15:20:31 INFO    : Configured logging from file /home/lnevers/gcf-2.7/src/gcf/stitcher_logging.conf
15:20:31 INFO    : Reading slice IG-ST-3 credential...
15:20:32 INFO    : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-3 expires on 2014-11-25 20:06:43 UTC
15:20:32 INFO    : Using SCS at http://nutshell.maxgigapop.net:8081/geni/xmlrpc
15:20:32 INFO    : Calling SCS...
15:20:36 INFO    : Multi-AM reservation will include resources from these aggregates:
15:20:36 INFO    : 	<Aggregate ukypks2-ig>
15:20:36 INFO    : 	<Aggregate gpo-ig>
15:20:36 INFO    : 	<Aggregate kansas-ig>
15:20:36 INFO    : 	<Aggregate oess>
15:20:36 INFO    : 	<Aggregate ion>
15:20:36 INFO    : Stitcher doing createsliver at <Aggregate ukypks2-ig>...
15:20:57 INFO    : ... Allocation at <Aggregate ukypks2-ig> complete.
15:20:57 INFO    : Stitcher doing createsliver at <Aggregate gpo-ig>...
15:21:20 INFO    : ... Allocation at <Aggregate gpo-ig> complete.
15:21:20 INFO    : Stitcher doing createsliver at <Aggregate kansas-ig>...
15:21:37 INFO    : ... Allocation at <Aggregate kansas-ig> complete.
15:21:37 INFO    : Stitcher doing createsliver at <Aggregate oess>...
15:21:42 INFO    : ... Allocation at <Aggregate oess> complete.
15:21:42 INFO    : Stitcher doing createsliver at <Aggregate ion>...
15:22:28 INFO    : DCN AM <Aggregate ion>: must wait for status ready....
15:22:28 INFO    : Pausing 30 seconds to let circuit become ready...
15:23:05 INFO    : Pausing 30 seconds to let circuit become ready...
15:23:43 INFO    : DCN circuit 139321 is ready at <Aggregate ion>
15:23:43 INFO    : DCN circuit 139311 is ready at <Aggregate ion>
15:23:50 INFO    : ... Allocation at <Aggregate ion> complete.
15:23:50 INFO    : All aggregates are complete.
15:23:50 INFO    : Your resources expire at 2014-11-24T20:10:36 (UTC). 
15:23:50 INFO    : Saved combined reservation RSpec at 5 AMs to file '/home/lnevers/gcf-test/stitch-test/Kansas/IG-ST-3-manifest-rspec-multiam-combined.xml'
Success: Reserved resources in slice IG-ST-3 at 5 Aggregates (including 2 intermediate aggregate(s) not in the original request), creating 2 stitched link(s).

Determined login information the KANSAS host:

$ readyToLogin.py IG-ST-3 -a kansas-ig
  ....
ig-kans's geni_status is: ready 
User lnevers logs in to ig-kans using:
	ssh -p 30010  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc2.instageni.ku.gpeni.net

Login to the KANSAS host and ping each remote:

#ping GPO IG 
[lnevers@ig-kans ~]$ ping 192.168.2.1 -c 60 -q
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.

--- 192.168.2.1 ping statistics ---
60 packets transmitted, 60 received, 0% packet loss, time 59094ms
rtt min/avg/max/mdev = 43.647/43.702/43.818/0.119 ms

# UKYPKS2 IG
[lnevers@ig-kans ~]$ ping 192.168.4.1 -c 60 -q
PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data.

--- 192.168.4.1 ping statistics ---
60 packets transmitted, 60 received, 0% packet loss, time 59109ms
rtt min/avg/max/mdev = 42.696/42.756/42.828/0.229 ms

IG-ST-4 New Site to GPO EG interoperability

Create a slice and then create the stitched slivers with the RSpec IG-ST-4.rspec, which specifies a 100 Mbps link capacity. This was done to get around the mismatch in link capacity units that exists between IG and EG.

$ stitcher.py createsliver IG-ST-4 IG-ST-4.rspec -o 15:45:28 INFO    : Configured logging from file /home/lnevers/gcf-2.7/src/gcf/stitcher_logging.conf
15:45:28 INFO    : Reading slice IG-ST-4 credential...
15:45:29 INFO    : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+IG-ST-4 expires on 2014-11-25 20:45:27 UTC
15:45:29 INFO    : Using SCS at http://nutshell.maxgigapop.net:8081/geni/xmlrpc
15:45:29 INFO    : Calling SCS...
15:45:30 INFO    : Multi-AM reservation will include resources from these aggregates:
15:45:30 INFO    : 	<Aggregate kansas-ig>
15:45:30 INFO    : 	<Aggregate oess>
15:45:30 INFO    : 	<Aggregate gpo-eg>
15:45:30 INFO    : 	<Aggregate ion>
15:45:30 INFO    : Stitcher doing createsliver at <Aggregate kansas-ig>...
15:45:46 INFO    : ... Allocation at <Aggregate kansas-ig> complete.
15:45:46 INFO    : Stitcher doing createsliver at <Aggregate gpo-eg>...
15:46:04 INFO    : ... Allocation at <Aggregate gpo-eg> complete.
15:46:04 INFO    : Stitcher doing createsliver at <Aggregate oess>...
15:46:08 INFO    : ... Allocation at <Aggregate oess> complete.
15:46:08 INFO    : Stitcher doing createsliver at <Aggregate ion>...
15:46:53 INFO    : DCN AM <Aggregate ion>: must wait for status ready....
15:46:53 INFO    : Pausing 30 seconds to let circuit become ready...
15:47:32 INFO    : DCN circuit 139351 is ready at <Aggregate ion>
15:47:39 INFO    : ... Allocation at <Aggregate ion> complete.
15:47:39 INFO    : All aggregates are complete.
15:47:39 INFO    : Your resources expire at 2014-11-24T20:35:30 (UTC). 
15:47:39 INFO    : Saved combined reservation RSpec at 4 AMs to file '/home/lnevers/gcf-test/stitch-test/Kansas/IG-ST-4-manifest-rspec-multiam-combined.xml'
Success: Reserved resources in slice IG-ST-4 at 4 Aggregates (including 2 intermediate aggregate(s) not in the original request), creating 1 stitched link(s).

Determined login information at each KANSAS and GPO aggregate:

$ readyToLogin.py IG-ST-4 -a kansas-ig
  ....
ig-kans's geni_status is: ready 
User lnevers logs in to ig-kans using:
	ssh -p 30010  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc5.instageni.ku.gpeni.net

$ readyToLogin.py IG-ST-4 -a gpo-eg
  ....
eg-gpo's geni_status is: ready 
User lnevers logs in to eg-gpo using:
	ssh -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@192.1.242.62

Measurements

Iperf ExoGENI GPO VM to InstaGENI KANSAS VM (TCP) - TCP window size: 23.5 KByte (default)

Collected: 2014-08-XX

One Client_

Five Clients

Ten Clients

Iperf ExoGENI GPO VM to InstaGENI KANSAS VM (UDP) - UDP buffer size: 224 KByte (default)

Ping from ExoGENI GPO VM to the InstaGENI KANSAS VM

Iperf InstaGENI KANSAS VM to ExoGENI GPO VM (TCP) - TCP window size: 23.5 KByte (default)

Collected: 2014-08-XX

One Client_

Five Clients

Ten Clients

Iperf InstaGENI KANSAS VM to ExoGENI GPO VM (UDP) - UDP buffer size: 224 KByte (default)

Ping from InstaGENI KANSAS VM to ExoGENI GPO VM

IG-ST-5 Site Information

Various pages include stitching information for a site. Each of the following were verified for this site:

  1. Verified that stitching VLANs and Device URN information exists in the KANSAS Aggregate page.

  1. Verified that Delegated GENI Stitching VLANs for site are documented at the Delegated GENI Stitching VLANs.
  1. Stitching Computation Service logs were reviewed while testing stitching to this site, no issues found.
  1. Added site to the list of GENI Network Stitching Sites.

IG-ST-6 New Site OpenFlow topology

Create a slice and then create the stitched slivers using OpenFlow with the RSPec IG-ST-6.rspec:

omni.py createslice IG-ST-6
stitcher.py createsliver IG-ST-6 IG-ST-6.rspec -o

Determined login information at each KANSAS and GPO aggregate:

$ readyToLogin.py IG-ST-6 -a kansas-ig
  ....

$ readyToLogin.py IG-ST-6 -a gpo-ig
  ....

Measurements

Iperf InstaGENI GPO VM to InstaGENI KANSAS VM (TCP) - TCP window size: 23.5 KByte (default)

Collected: 2014-xx-xx

One Client_

Five Clients

Ten Clients

Iperf InstaGENI GPO VM to InstaGENI KANSAS VM (UDP) - UDP buffer size: 224 KByte (default)

Ping from InstaGENI GPO VM to InstaGENI KANSAS VM

Iperf InstaGENI KANSAS VM to InstaGENI GPO VM (TCP) - TCP window size: 23.5 KByte (default)

Collected: 2014-xx-xx

One Client_

Five Clients

Ten Clients

Iperf InstaGENI KANSAS VM to InstaGENI GPO VM (UDP) - UDP buffer size: 224 KByte (default)

Ping from InstaGENI KANSAS VM to InstaGENI GPO VM


Email help@geni.net for GENI support or email me with feedback on this page!