wiki:PlasticSlices/BaselineEvaluation/Baseline6Details

Here are the details of Baseline 6, divided by slice.

The raw logs of each experiment are at http://www.gpolab.bbn.com/plastic-slices/baseline-logs/baseline-6/.

A variety of outages ocurred during this baseline. Here's a timeline of when we observed problems:

  • 2011-06-09 @ 18:10: All experiments started.
  • 2011-06-10 @ 17:15: We observed problems with all connections involving TCP and Stanford. We believe that non-GENI load on the Stanford FlowVisor was the underlying cause.
  • 2011-06-10 @ 17:30: A critical VM server at BBN needed to be rebooted, which included the server where the controllers for the slices were running. In the course of that, the Stanford and Internet2 FlowVisors went down. We haven't yet tried to reproduce this; we don't know of any reason why shutting down an experimenter's controller (even in a sudden emergency fashion) should affect upstream FlowVisors.
  • 2011-06-10 @ 21:00: The FlowVisors at Indiana and NLR also crashed, when the VM server that hosts them crashed. This again seems oddly coincidental, but there's no obvious causal chain. While investigating, we also discovered that a GENI test slice at BBN unrelated to Plastic Slices baseline testing had partially cross-connected VLAN 3715 and 3716, which created a loop when the misconfigured Indiana switches failed open rather than closed. All of these problems were corrected during the next few hours.
  • 2011-06-11 @ 00:00: The NLR and Internet2 FlowVisors came back online, and we were able to revive all of the experiments, except for a few involving Indiana.
  • 2011-06-12 @ 01:45: The Stanford FlowVisor was down.
  • 2011-06-12 @ 13:30: One of the Rutgers MyPLC nodes (orbitplc2) rebooted, and the node lost its static ARP table, stopping all of the experiments that used that node.
  • 2011-06-13 @ 12:30: Stanford upgraded their FlowVisor to a specific Git commit that addressed load-related bugs that were affecting them in earlier baseline testing. Indiana's switch/FlowVisor configuration problems were corrected. The orbitpclc2 still had no static ARP table.
  • 2011-06-13 @ 15:15: orbitplc2's static ARP table was fixed; everything was running smoothly again at this point.
  • 2011-06-14 @ 11:30: We changed the controller configuration to not include a FlowVisor between the switches and the controllers; shortly thereafter, Stanford's FlowVisor crashed, and all traffic (including e.g. between hosts at BBN) stopped flowing reliably. As before, we don't see any reason why one of these events should have caused the others, but the timing is very suspicious. Once Stanford restarted their FlowVisor, traffic within BBN (and elsewhere) returned to normal, and we were able to revive all of the experiments.
  • 2011-06-14 @ 17:20: An unexpected routing configuration change in Internet2 cut off the I2 OpenFlow switches from the I2 FlowVisor, which was running in Indiana University testlab IP space; we worked with I2 engineers to change the I2 switches to point to a new OpenFlow software stack in I2 production IP space (which we had planned to do at some point anyway, but this proved an opportune time). All traffic involving Internet2 was down at this point.
  • 2011-06-15 @ 14:10: The Internet2 address-related configuration change was complete, I2 traffic resumed flowing, and things continued to run smoothly for the brief remainder of the baseline, once we revived the experiments.
  • 2011-06-15 @ 19:30: All experiments shut down. We discovered shortly thereafter that we'd lost some log data from some experiments (detailed below), we believe due to a bug in 'screen', which we were using for logging. In particular, it appears that the buffered log data in memory wasn't written to disk when the screen process terminated, possibly due to the huge size of the logs.

That isn't a comprehensive record of when things actually went down and came back, but a general summary based on ticket notes. We plan to add a more detailed record based on log and monitoring analysis that is still in progress. We believe that these recorded outages explain most (if not all) of the anomalies in the results below.

plastic-101

SteadyPing, using interval=.006, and this table of client/server pairs:

client server server address
ganel.gpolab.bbn.com planetlab5.clemson.edu server=10.42.101.105
planetlab4.clemson.edu plnode2.cip.gatech.edu server=10.42.101.101
plnode1.cip.gatech.edu pl5.myplc.grnoc.iu.edu server=10.42.101.73
pl4.myplc.grnoc.iu.edu orbitplc2.orbit-lab.org server=10.42.101.112
orbitplc1.orbit-lab.org of-planet2.stanford.edu server=10.42.101.91
of-planet1.stanford.edu pl02.cs.washington.edu server=10.42.101.81
pl01.cs.washington.edu wings-openflow-3.wail.wisc.edu server=10.42.101.96
wings-openflow-2.wail.wisc.edu gardil.gpolab.bbn.com server=10.42.101.52

Commands run on each client

server=<ipaddr>
sudo ping -i .006 -s $((1500-8-20)) $server

Results

Generated from the logs with

subnet=101
for host in ganel.gpolab.bbn.com planetlab4.clemson.edu plnode1.cip.gatech.edu pl4.myplc.grnoc.iu.edu orbitplc1.orbit-lab.org of-planet1.stanford.edu pl01.cs.washington.edu wings-openflow-2.wail.wisc.edu ; do echo -e "$host:\n\n{{{" ; grep -A 2 statistics pgenigpolabbbncom_plastic$subnet\@$host.log ; echo -e "}}}\n" ; done

Some of the logfiles were evidently closed before the final statistics lines were written to them; those are indicated with "no output" below.

ganel.gpolab.bbn.com:

(no output)

planetlab4.clemson.edu:

(no output)

plnode1.cip.gatech.edu:

--- 10.42.101.73 ping statistics ---
53282242 packets transmitted, 52127122 received, 2% packet loss, time 522332014ms
rtt min/avg/max/mdev = 3.644/38.358/21405.426/32.473 ms, pipe 2143

pl4.myplc.grnoc.iu.edu:

--- 10.42.101.112 ping statistics ---
8891070 packets transmitted, 8574581 received, 3% packet loss, time 85173917ms
rtt min/avg/max/mdev = 54.920/56.100/25457.266/55.903 ms, pipe 2496
--
--- 10.42.101.112 ping statistics ---
5580 packets transmitted, 0 received, 100% packet loss, time 58475ms

--
--- 10.42.101.112 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms

--
--- 10.42.101.112 ping statistics ---
21 packets transmitted, 0 received, 100% packet loss, time 20002ms

--
--- 10.42.101.112 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

orbitplc1.orbit-lab.org:

--- 10.42.101.91 ping statistics ---
7994218 packets transmitted, 7443481 received, 6% packet loss, time 85244581ms
rtt min/avg/max/mdev = 84.523/85.961/53433.602/145.971 ms, pipe 4961

of-planet1.stanford.edu:

--- 10.42.101.81 ping statistics ---
7818571 packets transmitted, 7219892 received, 7% packet loss, time 85244792ms
rtt min/avg/max/mdev = 152.665/156.260/48351.800/245.054 ms, pipe 4447
--
--- 10.42.101.81 ping statistics ---
530 packets transmitted, 0 received, 100% packet loss, time 529557ms

pl01.cs.washington.edu:

(no output)

wings-openflow-2.wail.wisc.edu:

(no output)

Analysis

We lost the final stats for BBN - Clemson, Clemson - GT, Washinton - Wisconsin, and Wisconsin - BBN, and haven't gone back and tried to reconstruct them from the full logs.

plastic-102

SteadyPing, using interval=.006, and this table of client/server pairs:

client server server address
sardis.gpolab.bbn.com planetlab4.clemson.edu server=10.42.102.104
planetlab5.clemson.edu plnode1.cip.gatech.edu server=10.42.102.100
plnode2.cip.gatech.edu pl4.myplc.grnoc.iu.edu server=10.42.102.72
pl5.myplc.grnoc.iu.edu orbitplc1.orbit-lab.org server=10.42.102.111
orbitplc2.orbit-lab.org of-planet2.stanford.edu server=10.42.102.91
of-planet1.stanford.edu pl01.cs.washington.edu server=10.42.102.80
pl02.cs.washington.edu wings-openflow-2.wail.wisc.edu server=10.42.102.95
wings-openflow-3.wail.wisc.edu bain.gpolab.bbn.com server=10.42.102.54

Commands run on each client

server=<ipaddr>
sudo ping -i .006 -s $((1500-8-20)) $server

Results

Generated from the logs with

subnet=102
for host in sardis.gpolab.bbn.com planetlab5.clemson.edu plnode2.cip.gatech.edu pl5.myplc.grnoc.iu.edu orbitplc2.orbit-lab.org of-planet1.stanford.edu pl02.cs.washington.edu wings-openflow-3.wail.wisc.edu ; do echo -e "$host:\n\n{{{" ; grep -A 2 statistics pgenigpolabbbncom_plastic$subnet\@$host.log ; echo -e "}}}\n" ; done

Some of the logfiles were evidently closed before the final statistics lines were written to them; those are indicated with "no output" below.

sardis.gpolab.bbn.com:

(no output)

planetlab5.clemson.edu:

(no output)

plnode2.cip.gatech.edu:

--- 10.42.102.72 ping statistics ---
51229840 packets transmitted, 50126126 received, 2% packet loss, time 522292382ms
rtt min/avg/max/mdev = 42.395/143.607/88081.748/120.862 ms, pipe 8782

pl5.myplc.grnoc.iu.edu:

(no output)

orbitplc2.orbit-lab.org:

--- 10.42.102.91 ping statistics ---
3948355 packets transmitted, 0 received, +39620 errors, 100% packet loss, time 39896994ms
, pipe 4
--
--- 10.42.102.91 ping statistics ---
17842510 packets transmitted, 11365499 received, 36% packet loss, time 190691167ms
rtt min/avg/max/mdev = 84.524/85.382/37902.284/103.288 ms, pipe 3546

of-planet1.stanford.edu:

(no output)

pl02.cs.washington.edu:

(no output)

wings-openflow-3.wail.wisc.edu:

(no output)

Analysis

We lost the final stats for BBN - Clemson, Clemson - GT, and Indiana - Rutgers, Stanford - Washinton, Washington - Wisconsin, and Wisconsin - BBN, and haven't gone back and tried to reconstruct them from the full logs.

plastic-103

SteadyPerf TCP, using port=5103, time=518400, and this table of client/server pairs:

client server server address
of-planet1.stanford.edu navis.gpolab.bbn.com server=10.42.103.55
ganel.gpolab.bbn.com orbitplc1.orbit-lab.org server=10.42.103.111
pl02.cs.washington.edu bain.gpolab.bbn.com server=10.42.103.54
of-planet2.stanford.edu pl01.cs.washington.edu server=10.42.103.80
orbitplc2.orbit-lab.org of-planet3.stanford.edu server=10.42.103.92

One-time prep commands run on each client and server

sudo yum -y install iperf

Commands run on each server

server=<ipaddr>
nice -n 19 iperf -B $server -p 5103 -s -i 1

Commands run on each client

server=<ipaddr>
nice -n 19 iperf -c $server -p 5103 -t 518400

Results

Generated with

subnet=103
for host in of-planet1.stanford.edu ganel.gpolab.bbn.com pl02.cs.washington.edu of-planet2.stanford.edu orbitplc2.orbit-lab.org ; do echo -e "$host:\n\n{{{" ; grep -a -A 5 -B 1 "Client connecting" pgenigpolabbbncom_plastic$subnet\@$host.log ; echo -e "}}}\n" ; done

and then edited slightly to remove artifacts (like control characters, my prompt, etc).

of-planet1.stanford.edu:

------------------------------------------------------------
Client connecting to 10.42.103.55, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.90 port 41017 connected with 10.42.103.55 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-77492.8 sec  2633761741802670592 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.55, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.90 port 50080 connected with 10.42.103.55 port 5103
--
------------------------------------------------------------
Client connecting to 10.42.103.55, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.90 port 44654 connected with 10.42.103.55 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-6546.3 sec  1251150593240805888 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.55, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.90 port 56772 connected with 10.42.103.55 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-146944.4 sec  17233099848203849728 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.55, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.90 port 49335 connected with 10.42.103.55 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-82828.0 sec  4656702276830516224 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.55, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.90 port 39376 connected with 10.42.103.55 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-83244.3 sec  1549347708564942592 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.55, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.90 port 54347 connected with 10.42.103.55 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-91646.9 sec  550160791501918400 bits  0.00 (null)s/sec

ganel.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.103.111, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.51 port 41323 connected with 10.42.103.111 port 5103
write2 failed: Connection timed out
[  3]  0.0-84225.3 sec  13.4 GBytes  1.37 Mbits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.111, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 0.0.0.0 port 48834 connected with 10.42.103.111 port 5103
[  3]  0.0- 0.0 sec  0.00 Bytes  0.00 bits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.111, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.51 port 52780 connected with 10.42.103.111 port 5103
write2 failed: Connection timed out
[  3]  0.0-315048.4 sec  60.7 GBytes  1.65 Mbits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.111, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.51 port 43337 connected with 10.42.103.111 port 5103
write2 failed: Connection timed out
[  3]  0.0-36210.9 sec  5.97 GBytes  1.42 Mbits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.111, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.51 port 55138 connected with 10.42.103.111 port 5103
[  3]  0.0-14007.5 sec  2.19 GBytes  1.34 Mbits/sec

pl02.cs.washington.edu:

------------------------------------------------------------
Client connecting to 10.42.103.54, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.81 port 58396 connected with 10.42.103.54 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-84436.4 sec  49441449278490344 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.54, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.81 port 49936 connected with 10.42.103.54 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-12236.0 sec  2756308215358402560 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.54, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.81 port 53314 connected with 10.42.103.54 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-308675.6 sec  1712307745075661568 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.54, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.81 port 39888 connected with 10.42.103.54 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-91657.8 sec  4815184397506928640 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.54, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.81 port 41855 connected with 10.42.103.54 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-13984.6 sec  2.99 GBytes  1.83 Mbits/sec

of-planet2.stanford.edu:

------------------------------------------------------------
Client connecting to 10.42.103.80, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.91 port 60787 connected with 10.42.103.80 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-77763.2 sec  495418958515828160 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.80, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.91 port 44438 connected with 10.42.103.80 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-6614.1 sec  972954321614253696 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.80, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.91 port 50063 connected with 10.42.103.80 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-12299.5 sec  2812586413178213376 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.80, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.91 port 53156 connected with 10.42.103.80 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-134761.8 sec  17259808372104812544 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.80, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.91 port 51293 connected with 10.42.103.80 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-82718.3 sec  5692278029069475840 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.80, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.91 port 40214 connected with 10.42.103.80 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-91166.3 sec  1929400793955880192 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.80, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.91 port 34456 connected with 10.42.103.80 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-91729.8 sec  475403836956524288 bits  0.00 (null)s/sec

orbitplc2.orbit-lab.org:

------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 34318 connected with 10.42.103.92 port 5103
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 34318 connected with 10.42.103.92 port 5103
write2 failed: Connection timed out
[  3]  0.0-1586.3 sec  14.1 KBytes  73.0 bits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 52113 connected with 10.42.103.92 port 5103
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 52113 connected with 10.42.103.92 port 5103
write2 failed: Connection timed out
[  3]  0.0-1732.9 sec  14.1 KBytes  66.8 bits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 60151 connected with 10.42.103.92 port 5103
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 60151 connected with 10.42.103.92 port 5103
write2 failed: Connection timed out
[  3]  0.0-1588.5 sec  14.1 KBytes  72.9 bits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 55086 connected with 10.42.103.92 port 5103
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 55086 connected with 10.42.103.92 port 5103
write2 failed: Connection timed out
[  3]  0.0-1439.3 sec  15.6 KBytes  88.5 bits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 49791 connected with 10.42.103.92 port 5103
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 49791 connected with 10.42.103.92 port 5103
write2 failed: Connection timed out
[  3]  0.0-1733.6 sec  14.1 KBytes  66.8 bits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 0.0.0.0 port 44111 connected with 10.42.103.92 port 5103
[  3]  0.0- 0.0 sec  0.00 Bytes  0.00 bits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 0.0.0.0 port 44112 connected with 10.42.103.92 port 5103
[  3]  0.0- 0.0 sec  0.00 Bytes  0.00 bits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 0.0.0.0 port 51331 connected with 10.42.103.92 port 5103
[  3]  0.0- 0.0 sec  0.00 Bytes  0.00 bits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 54047 connected with 10.42.103.92 port 5103
write2 failed: Connection timed out
[  3]  0.0-1470.6 sec  15.6 KBytes  86.6 bits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 55795 connected with 10.42.103.92 port 5103
write2 failed: Connection timed out
[  3]  0.0-1586.0 sec  14.1 KBytes  73.0 bits/sec
--
------------------------------------------------------------
Client connecting to 10.42.103.92, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 59620 connected with 10.42.103.92 port 5103
write2 failed: Connection timed out
[  3]  0.0-1472.7 sec  15.6 KBytes  86.5 bits/sec

Analysis

(forthcoming)

plastic-104

SteadyPerf UDP, using port=5104, time=518400, rate=3, and this table of client/server pairs:

client server server address
navis.gpolab.bbn.com wings-openflow-2.wail.wisc.edu server=10.42.104.95
wings-openflow-3.wail.wisc.edu orbitplc2.orbit-lab.org server=10.42.104.112
orbitplc1.orbit-lab.org pl4.myplc.grnoc.iu.edu server=10.42.104.72
pl5.myplc.grnoc.iu.edu gardil.gpolab.bbn.com server=10.42.104.52

One-time prep commands run on each client and server

sudo yum -y install iperf

Commands run on each server

server=<ipaddr>
nice -n 19 iperf -u -B $server -p 5104 -s -i 1

Commands run on each client

server=<ipaddr>
nice -n 19 iperf -u -c $server -p 5104 -t 518400 -b 3M

Results

Generated with

subnet=104
for host in navis.gpolab.bbn.com wings-openflow-3.wail.wisc.edu orbitplc1.orbit-lab.org pl5.myplc.grnoc.iu.edu ; do echo -e "$host:\n\n{{{" ; grep -A 10 -B 1 "Client connecting" pgenigpolabbbncom_plastic$subnet\@$host.log ; echo -e "}}}\n" ; done

and then edited slightly to remove artifacts (like control characters, my prompt, etc).

navis.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.104.95, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:   108 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.55 port 46184 connected with 10.42.104.95 port 5104
[  3]  0.0-84338.4 sec  29.5 GBytes  3.00 Mbits/sec
[  3] Sent 21514845 datagrams
[  3] WARNING: did not receive ack of last datagram after 10 tries.
--
------------------------------------------------------------
Client connecting to 10.42.104.95, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:   108 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.55 port 38293 connected with 10.42.104.95 port 5104
[  3]  0.0- 3.9 sec  1.39 MBytes  3.00 Mbits/sec
[  3] Sent 988 datagrams
[  3] WARNING: did not receive ack of last datagram after 10 tries.
--
------------------------------------------------------------
Client connecting to 10.42.104.95, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:   108 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.55 port 38294 connected with 10.42.104.95 port 5104
[  3]  0.0-435503.9 sec    152 GBytes  3.00 Mbits/sec
[  3] Sent 111097722 datagrams
[  3] Server Report:
[  3]  0.0-427519.8 sec    118 GBytes  2.37 Mbits/sec  0.011 ms 25088001/111097722 (23%)
[  3]  0.0-427519.8 sec  54540 datagrams received out-of-order

wings-openflow-3.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.104.112, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.96 port 42476 connected with 10.42.104.112 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-518400.0 sec   181 GBytes  3.00 Mbits/sec
[  3] Sent 132244879 datagrams
[  3] Server Report:
[  3]  0.0-236119.1 sec  68.6 GBytes  2.50 Mbits/sec   0.089 ms 82123350/132244878 (62%)
[  3]  0.0-236119.1 sec  1577 datagrams received out-of-order

orbitplc1.orbit-lab.org:

------------------------------------------------------------
Client connecting to 10.42.104.72, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:   108 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.111 port 43809 connected with 10.42.104.72 port 5104
[  3]  0.0-86506.5 sec  30.2 GBytes  3.00 Mbits/sec
[  3] Sent 22067973 datagrams
[  3] WARNING: did not receive ack of last datagram after 10 tries.
--
------------------------------------------------------------
Client connecting to 10.42.104.72, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:   108 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.111 port 44217 connected with 10.42.104.72 port 5104
[  3]  0.0-435540.7 sec    152 GBytes  3.00 Mbits/sec
[  3] Sent 111107296 datagrams
[  3] Server Report:
[  3]  0.0-522051.0 sec    133 GBytes  2.19 Mbits/sec  0.016 ms 14056806/111107296 (13%)
[  3]  0.0-522051.0 sec  42345 datagrams received out-of-order

pl5.myplc.grnoc.iu.edu:

------------------------------------------------------------
Client connecting to 10.42.104.52, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:   108 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.73 port 35196 connected with 10.42.104.52 port 5104
[  3]  0.0-86500.6 sec  30.2 GBytes  3.00 Mbits/sec
[  3] Sent 22066473 datagrams
[  3] WARNING: did not receive ack of last datagram after 10 tries.
--
------------------------------------------------------------
Client connecting to 10.42.104.52, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:   108 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.73 port 35246 connected with 10.42.104.52 port 5104
[  3]  0.0- 4.3 sec  1.54 MBytes  3.00 Mbits/sec
[  3] Sent 1098 datagrams
[  3] WARNING: did not receive ack of last datagram after 10 tries.
--
------------------------------------------------------------
Client connecting to 10.42.104.52, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:   108 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.73 port 35246 connected with 10.42.104.52 port 5104
[  3]  0.0-435576.5 sec    152 GBytes  3.00 Mbits/sec
[  3] Sent 111116447 datagrams
[  3] Server Report:
[  3]  0.0-428686.3 sec    107 GBytes  2.15 Mbits/sec  0.004 ms 32854950/111116447 (30%)
[  3]  0.0-428686.3 sec  157390 datagrams received out-of-order

Analysis

(forthcoming)

plastic-105

SteadyPerf TCP, using port=5105, time=518400, and this table of client/server pairs:

client server server address
wings-openflow-2.wail.wisc.edu planetlab5.clemson.edu server=10.42.105.105
planetlab4.clemson.edu sardis.gpolab.bbn.com server=10.42.105.53
bain.gpolab.bbn.com plnode2.cip.gatech.edu server=10.42.105.101
plnode1.cip.gatech.edu wings-openflow-3.wail.wisc.edu server=10.42.105.96

One-time prep commands run on each client and server

sudo yum -y install iperf

Commands run on each server

server=<ipaddr>
nice -n 19 iperf -B $server -p 5105 -s -i 1

Commands run on each client

server=<ipaddr>
nice -n 19 iperf -c $server -p 5105 -t 518400

Results

Generated with

subnet=105
for host in wings-openflow-2.wail.wisc.edu planetlab4.clemson.edu bain.gpolab.bbn.com plnode1.cip.gatech.edu ; do echo -e "$host:\n\n{{{" ; grep -A 5 -B 1 "Client connecting" pgenigpolabbbncom_plastic$subnet\@$host.log ; echo -e "}}}\n" ; done

and then edited slightly to remove artifacts (like control characters, my prompt, etc).

wings-openflow-2.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.105.105, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.95 port 51077 connected with 10.42.105.105 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-86549.5 sec  290866635652324736 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.105.105, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.95 port 53078 connected with 10.42.105.105 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-186984.1 sec  3291735686781913088 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.105.105, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.95 port 49469 connected with 10.42.105.105 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-134293.4 sec  2071412879920256000 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.105.105, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.95 port 42096 connected with 10.42.105.105 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-105203.9 sec  81.5 GBytes  6.65 Mbits/sec

planetlab4.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.105.53, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.104 port 42928 connected with 10.42.105.53 port 5105
[ ID] Interval       Transfer     Bandwidth
--
------------------------------------------------------------
Client connecting to 10.42.105.53, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.104 port 47779 connected with 10.42.105.53 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-321410.1 sec  1889236641053468160 bits  0.00 (null)s/sec
--
------------------------------------------------------------
Client connecting to 10.42.105.53, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.104 port 52520 connected with 10.42.105.53 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-105268.3 sec  14595003305585724 bits  0.00 (null)s/sec

bain.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.105.101, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.54 port 50361 connected with 10.42.105.101 port 5105
write2 failed: Connection timed out
[  3]  0.0-83935.7 sec  25.5 GBytes  2.61 Mbits/sec
--
------------------------------------------------------------
Client connecting to 10.42.105.101, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.54 port 47983 connected with 10.42.105.101 port 5105
write2 failed: Connection timed out
[  3]  0.0-1631.4 sec    180 MBytes    924 Kbits/sec
--
------------------------------------------------------------
Client connecting to 10.42.105.101, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.54 port 60727 connected with 10.42.105.101 port 5105
write2 failed: Connection timed out
[  3]  0.0-301261.8 sec  94.3 GBytes  2.69 Mbits/sec
--
------------------------------------------------------------
Client connecting to 10.42.105.101, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.54 port 49619 connected with 10.42.105.101 port 5105
[  3]  0.0-105247.5 sec  32.9 GBytes  2.68 Mbits/sec

plnode1.cip.gatech.edu:

------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 42217 connected with 10.42.105.96 port 5105
write2 failed: Connection timed out
[  3]  0.0-83572.2 sec    122 GBytes  12.6 Mbits/sec
--
------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 34656 connected with 10.42.105.96 port 5105
write2 failed: Connection timed out
[  3]  0.0-89907.5 sec    122 GBytes  11.7 Mbits/sec
--
------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 57573 connected with 10.42.105.96 port 5105
write2 failed: Connection timed out
[  3]  0.0-12842.3 sec  10.8 GBytes  7.20 Mbits/sec
--
------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 35385 connected with 10.42.105.96 port 5105
--
------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 35390 connected with 10.42.105.96 port 5105
--
------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 35392 connected with 10.42.105.96 port 5105
write2 failed: Connection timed out
[  3]  0.0-8663.5 sec  6.01 GBytes  5.96 Mbits/sec
--
------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 53036 connected with 10.42.105.96 port 5105
write2 failed: Connection timed out
[  3]  0.0-84985.4 sec    125 GBytes  12.6 Mbits/sec
--
------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 48438 connected with 10.42.105.96 port 5105
[  3]  0.0-105332.2 sec    127 GBytes  10.3 Mbits/sec

Analysis

(forthcoming)

plastic-106

SteadyPerf UDP, using port=5106, time=518400, rate=3, and this table of client/server pairs:

client server server address
planetlab5.clemson.edu wings-openflow-2.wail.wisc.edu server=10.42.106.95
wings-openflow-3.wail.wisc.edu plnode1.cip.gatech.edu server=10.42.106.100
plnode2.cip.gatech.edu ganel.gpolab.bbn.com server=10.42.106.51
gardil.gpolab.bbn.com planetlab4.clemson.edu server=10.42.106.104

One-time prep commands run on each client and server

sudo yum -y install iperf

Commands run on each server

server=<ipaddr>
nice -n 19 iperf -u -B $server -p 5106 -s -i 1

Commands run on each client

server=<ipaddr>
nice -n 19 iperf -u -c $server -p 5106 -t 518400 -b 3M

Results

Generated with

subnet=106
for host in planetlab5.clemson.edu wings-openflow-3.wail.wisc.edu plnode2.cip.gatech.edu gardil.gpolab.bbn.com ; do echo -e "$host:\n\n{{{" ; grep -A 10 -B 1 "Client connecting" pgenigpolabbbncom_plastic$subnet\@$host.log ; echo -e "}}}\n" ; done

and then edited slightly to remove artifacts (like control characters, my prompt, etc).

planetlab5.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.106.95, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.105 port 48749 connected with 10.42.106.95 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-518400.0 sec   181 GBytes  3.00 Mbits/sec
[  3] Sent 132244861 datagrams
[  3] Server Report:
[  3]  0.0-518398.8 sec   157 GBytes  2.60 Mbits/sec   0.082 ms 17699410/132244860 (13%)
[  3]  0.0-518398.8 sec  79245 datagrams received out-of-order

wings-openflow-3.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.106.100, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.96 port 45800 connected with 10.42.106.100 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-518400.0 sec   181 GBytes  3.00 Mbits/sec
[  3] Sent 132244852 datagrams
[  3] Server Report:
[  3]  0.0-518398.5 sec   178 GBytes  2.95 Mbits/sec   1.308 ms 2170052/132244852 (1.6%)
[  3]  0.0-518398.5 sec  22633 datagrams received out-of-order

plnode2.cip.gatech.edu:

------------------------------------------------------------
Client connecting to 10.42.106.51, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:   122 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.101 port 37693 connected with 10.42.106.51 port 5106
[  3]  0.0-518400.0 sec    181 GBytes  3.00 Mbits/sec
[  3] Sent 132201326 datagrams
[  3] WARNING: did not receive ack of last datagram after 10 tries.

gardil.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.106.104, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:   108 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.52 port 44818 connected with 10.42.106.104 port 5106
[  3]  0.0-518400.0 sec    181 GBytes  3.00 Mbits/sec
[  3] Sent 132244653 datagrams
[  3] Server Report:
[  3]  0.0-518398.1 sec    178 GBytes  2.96 Mbits/sec  0.028 ms 1889396/132244653 (1.4%)
[  3]  0.0-518398.1 sec  3328 datagrams received out-of-order

Analysis

(forthcoming)

plastic-107

SteadyWeb, using port=4107, file=substrate.doc, md5sum=d4fcf71833327fbfef98be09deef8bfb, and this table of client/server pairs:

client server server address
planetlab5.clemson.edu pl4.myplc.grnoc.iu.edu server=10.42.107.72
pl5.myplc.grnoc.iu.edu plnode2.cip.gatech.edu server=10.42.107.101
plnode1.cip.gatech.edu pl02.cs.washington.edu server=10.42.107.81
pl01.cs.washington.edu planetlab4.clemson.edu server=10.42.107.104

One-time prep commands run on each server

sudo yum -y install pyOpenSSL patch
cd
rm -rf ~/gigaweb
mkdir -p ~/gigaweb/docroot

cd ~/gigaweb
wget http://code.activestate.com/recipes/442473-simple-http-server-supporting-ssl-secure-communica/download/1/ -O httpsd.py
wget http://groups.geni.net/geni/attachment/wiki/PlasticSlices/Experiments/httpsd.py.patch?format=raw -O httpsd.py.patch
patch httpsd.py httpsd.py.patch
rm httpsd.py.patch

cd ~/gigaweb/docroot
wget http://groups.geni.net/geni/attachment/wiki/DeliverablePage/Spiral1%20substrate%20catalog.doc?format=raw -O substrate.doc

cd ~/gigaweb
openssl genrsa -passout pass:localhost -des3 -rand /dev/urandom -out localhost.localdomain.key 1024
openssl req -subj /CN=localhost.localdomain -passin pass:localhost -new -key localhost.localdomain.key -out localhost.localdomain.csr
openssl x509 -passin pass:localhost -req -days 3650 -in localhost.localdomain.csr -signkey localhost.localdomain.key -out localhost.localdomain.crt
openssl rsa -passin pass:localhost -in localhost.localdomain.key -out decrypted.localhost.localdomain.key
mv -f decrypted.localhost.localdomain.key localhost.localdomain.key
cat localhost.localdomain.key localhost.localdomain.crt > localhost.localdomain.pem
rm localhost.localdomain.key localhost.localdomain.crt localhost.localdomain.csr

Commands run on each server

server=<ipaddr>
cd ~/gigaweb/docroot
python ../httpsd.py $server 4107

Commands run on each client

server=<ipaddr>
cd
rm -rf ~/gigaweb
mkdir ~/gigaweb
cd ~/gigaweb
while true ; do wget --no-check-certificate https://$server:4107/substrate.doc -O substrate.doc ; echo -n "md5sum: " ; md5sum substrate.doc ; rm substrate.doc ; done

Results

Since we transfered the file to each client hundreds (if not thousands) of times, we didn't save all the copies, but we did generate an MD5 checksum after each download, and log that, so we ran some grep commands on the logs to count the number of total checksums printed in each log, and the number where the checksum had the expected value.

Generated with

subnet=107
for host in planetlab5.clemson.edu pl5.myplc.grnoc.iu.edu plnode1.cip.gatech.edu pl01.cs.washington.edu ; do echo -e -n "$host:\n\n{{{\ntotal md5sum lines: " ; grep "md5sum:" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e -n "matching md5sum lines: " ; grep "md5sum: d4fcf71833327fbfef98be09deef8bfb" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e "}}}\n" ; done

planetlab5.clemson.edu:

total md5sum lines: 10590
matching md5sum lines: 10580

pl5.myplc.grnoc.iu.edu:

total md5sum lines: 30957
matching md5sum lines: 30891

plnode1.cip.gatech.edu:

total md5sum lines: 21248
matching md5sum lines: 21241

pl01.cs.washington.edu:

total md5sum lines: 27404
matching md5sum lines: 27396

Analysis

(forthcoming)

plastic-108

SteadyWeb, using port=4108, file=substrate.doc, md5sum=d4fcf71833327fbfef98be09deef8bfb, and this table of client/server pairs:

client server server address
wings-openflow-3.wail.wisc.edu of-planet2.stanford.edu server=10.42.108.91
of-planet1.stanford.edu orbitplc1.orbit-lab.org server=10.42.108.111
orbitplc2.orbit-lab.org pl5.myplc.grnoc.iu.edu server=10.42.108.73
pl4.myplc.grnoc.iu.edu wings-openflow-2.wail.wisc.edu server=10.42.108.95

One-time prep commands run on each server

sudo yum -y install pyOpenSSL patch
cd
rm -rf ~/gigaweb
mkdir -p ~/gigaweb/docroot

cd ~/gigaweb
wget http://code.activestate.com/recipes/442473-simple-http-server-supporting-ssl-secure-communica/download/1/ -O httpsd.py
wget http://groups.geni.net/geni/attachment/wiki/PlasticSlices/Experiments/httpsd.py.patch?format=raw -O httpsd.py.patch
patch httpsd.py httpsd.py.patch
rm httpsd.py.patch

cd ~/gigaweb/docroot
wget http://groups.geni.net/geni/attachment/wiki/DeliverablePage/Spiral1%20substrate%20catalog.doc?format=raw -O substrate.doc

cd ~/gigaweb
openssl genrsa -passout pass:localhost -des3 -rand /dev/urandom -out localhost.localdomain.key 1024
openssl req -subj /CN=localhost.localdomain -passin pass:localhost -new -key localhost.localdomain.key -out localhost.localdomain.csr
openssl x509 -passin pass:localhost -req -days 3650 -in localhost.localdomain.csr -signkey localhost.localdomain.key -out localhost.localdomain.crt
openssl rsa -passin pass:localhost -in localhost.localdomain.key -out decrypted.localhost.localdomain.key
mv -f decrypted.localhost.localdomain.key localhost.localdomain.key
cat localhost.localdomain.key localhost.localdomain.crt > localhost.localdomain.pem
rm localhost.localdomain.key localhost.localdomain.crt localhost.localdomain.csr

Commands run on each server

server=<ipaddr>
cd ~/gigaweb/docroot
python ../httpsd.py $server 4108

Commands run on each client

server=<ipaddr>
cd
rm -rf ~/gigaweb
mkdir ~/gigaweb
cd ~/gigaweb
while true ; do wget --no-check-certificate https://$server:4108/substrate.doc -O substrate.doc ; echo -n "md5sum: " ; md5sum substrate.doc ; rm substrate.doc ; done

Results

Since we transfered the file to each client hundreds (if not thousands) of times, we didn't save all the copies, but we did generate an MD5 checksum after each download, and log that, so we ran some grep commands on the logs to count the number of total checksums printed in each log, and the number where the checksum had the expected value.

Generated with

subnet=108
for host in wings-openflow-3.wail.wisc.edu of-planet1.stanford.edu orbitplc2.orbit-lab.org pl4.myplc.grnoc.iu.edu ; do echo -e -n "$host:\n\n{{{\ntotal md5sum lines: " ; grep "md5sum:" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e -n "matching md5sum lines: " ; grep "md5sum: d4fcf71833327fbfef98be09deef8bfb" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e "}}}\n" ; done

wings-openflow-3.wail.wisc.edu:

total md5sum lines: 13302
matching md5sum lines: 13274

of-planet1.stanford.edu:

total md5sum lines: 8226
matching md5sum lines: 8198

orbitplc2.orbit-lab.org:

total md5sum lines: 1984
matching md5sum lines: 1943

pl4.myplc.grnoc.iu.edu:

total md5sum lines: 64189
matching md5sum lines: 64178

Analysis

(forthcoming)

plastic-109

SteadyNetcat, using port=6109, file=substrate.doc, md5sum=d4fcf71833327fbfef98be09deef8bfb, and this table of client/server pairs:

client server server address
navis.gpolab.bbn.com pl5.myplc.grnoc.iu.edu server=10.42.109.73
pl4.myplc.grnoc.iu.edu pl02.cs.washington.edu server=10.42.109.81
pl01.cs.washington.edu planetlab5.clemson.edu server=10.42.109.105
planetlab4.clemson.edu of-planet1.stanford.edu server=10.42.109.90
of-planet2.stanford.edu wings-openflow-3.wail.wisc.edu server=10.42.109.96
wings-openflow-2.wail.wisc.edu ganel.gpolab.bbn.com server=10.42.109.51

One-time prep commands run on each server

sudo yum -y install nc
mkdir -p ~/giganetcat
cd ~/giganetcat
wget http://groups.geni.net/geni/attachment/wiki/DeliverablePage/Spiral1%20substrate%20catalog.doc?format=raw -O substrate.doc

One-time prep commands run on each client

sudo yum -y install nc

Commands run on each server

server=<ipaddr>
cd ~/giganetcat
while true ; do nc -l $server 6109 < substrate.doc ; done

Commands run on each client

server=<ipaddr>
cd
rm -rf ~/giganetcat
mkdir ~/giganetcat
cd ~/giganetcat
while true ; do nc $server 6109 > substrate.doc ; echo -n "$(date "+%F %T")  " ; md5sum substrate.doc ; rm substrate.doc ; done

Results

Since we transfered the file to each client hundreds (if not thousands) of times, we didn't save all the copies, but we did generate an MD5 checksum after each download, and log that, so we ran some grep commands on the logs to count the number of total checksums printed in each log, and the number where the checksum had the expected value.

Generated with

subnet=109
for host in navis.gpolab.bbn.com pl4.myplc.grnoc.iu.edu pl01.cs.washington.edu planetlab4.clemson.edu of-planet2.stanford.edu wings-openflow-2.wail.wisc.edu ; do echo -e -n "$host:\n\n{{{\ntotal md5sum lines: " ; grep "substrate.doc" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e -n "matching md5sum lines: " ; grep "d4fcf71833327fbfef98be09deef8bfb  substrate.doc" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e "}}}\n" ; done

navis.gpolab.bbn.com:

total md5sum lines: 8935
matching md5sum lines: 8872

pl4.myplc.grnoc.iu.edu:

total md5sum lines: 9797
matching md5sum lines: 9717

pl01.cs.washington.edu:

total md5sum lines: 12061
matching md5sum lines: 12016

planetlab4.clemson.edu:

total md5sum lines: 20239
matching md5sum lines: 20151

of-planet2.stanford.edu:

total md5sum lines: 6208
matching md5sum lines: 5999

wings-openflow-2.wail.wisc.edu:

total md5sum lines: 28398
matching md5sum lines: 28341

Analysis

(forthcoming)

plastic-110

SteadyNetcat, using port=6110, file=substrate.doc, md5sum=d4fcf71833327fbfef98be09deef8bfb, and this table of client/server pairs:

client server server address
gardil.gpolab.bbn.com pl01.cs.washington.edu server=10.42.110.80
pl02.cs.washington.edu of-planet1.stanford.edu server=10.42.110.90
of-planet2.stanford.edu orbitplc2.orbit-lab.org server=10.42.110.112
orbitplc1.orbit-lab.org pl4.myplc.grnoc.iu.edu server=10.42.110.72
pl5.myplc.grnoc.iu.edu plnode1.cip.gatech.edu server=10.42.110.100
plnode2.cip.gatech.edu sardis.gpolab.bbn.com server=10.42.110.53

One-time prep commands run on each server

sudo yum -y install nc
mkdir -p ~/giganetcat
cd ~/giganetcat
wget http://groups.geni.net/geni/attachment/wiki/DeliverablePage/Spiral1%20substrate%20catalog.doc?format=raw -O substrate.doc

One-time prep commands run on each client

sudo yum -y install nc

Commands run on each server

server=<ipaddr>
cd ~/giganetcat
while true ; do nc -l $server 6110 < substrate.doc ; done

Commands run on each client

server=<ipaddr>
cd
rm -rf ~/giganetcat
mkdir ~/giganetcat
cd ~/giganetcat
while true ; do nc $server 6110 > substrate.doc ; echo -n "$(date "+%F %T")  " ; md5sum substrate.doc ; rm substrate.doc ; done

Results

Since we transfered the file to each client hundreds (if not thousands) of times, we didn't save all the copies, but we did generate an MD5 checksum after each download, and log that, so we ran some grep commands on the logs to count the number of total checksums printed in each log, and the number where the checksum had the expected value.

Generated with

subnet=110
for host in gardil.gpolab.bbn.com pl02.cs.washington.edu of-planet2.stanford.edu orbitplc1.orbit-lab.org pl5.myplc.grnoc.iu.edu plnode2.cip.gatech.edu ; do echo -e -n "$host:\n\n{{{\ntotal md5sum lines: " ; grep "substrate.doc" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e -n "matching md5sum lines: " ; grep "d4fcf71833327fbfef98be09deef8bfb  substrate.doc" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e "}}}\n" ; done

gardil.gpolab.bbn.com:

total md5sum lines: 12149
matching md5sum lines: 12071

pl02.cs.washington.edu:

total md5sum lines: 22735
matching md5sum lines: 22509

of-planet2.stanford.edu:

total md5sum lines: 5737
matching md5sum lines: 5236

orbitplc1.orbit-lab.org:

total md5sum lines: 2722
matching md5sum lines: 2617

pl5.myplc.grnoc.iu.edu:

total md5sum lines: 6128
matching md5sum lines: 5232

plnode2.cip.gatech.edu:

total md5sum lines: 8854
matching md5sum lines: 8796

Analysis

(forthcoming)

Last modified 9 years ago Last modified on 07/11/11 17:32:26