wiki:PlasticSlices/BaselineEvaluation/Baseline7Details

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

In this baseline, we intended to run multiple rounds of experiments simulating Emergency Stop requests at different campuses. We completed one round with the GMOC and agreed to postpone the rest. We left the "round" structure (on this page and in the log directory) in place for simplicity. We'll run additional rounds after GEC 11 in the continuation phase of this project.

We conducted two Emergency Stop tests: One in which the GMOC contacted the site admins about suspicious traffic from a slice (plastic-104 in this example) and asked them to cut it off; and one to simulate the situation in which the GMOC is unable to contact any site admins, and cuts off traffic in the core. We used BBN as the site for both tests, and uncovered a variety of procedural and documentation issues, which the GMOC and GPO are addressing.

The raw logs of each experiment are at http://www.gpolab.bbn.com/plastic-slices/baseline-logs/baseline-7/, with a subdirectory for the logs from each round.

The raw logs from this baseline are somewhat misleading, because we did not stop the experiments immediately after the Emergency Stop tests, so they show disruptions from the following day (e.g. from the NLR OpenFlow stack migration) that are entirely unrelated to the Emergency Stop tests themselves. We will separate the Emergency Stop period from the remainder of the experiment duration in our final log analysis.

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

Round 1

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 -A 2 statistics pgenigpolabbbncom_plastic$subnet\@$host.log ; echo -e "}}}\n" ; done

ganel.gpolab.bbn.com:

--- 10.42.101.105 ping statistics ---
10725017 packets transmitted, 5981642 received, 44% packet loss, time 107766151ms
rtt min/avg/max/mdev = 59.340/60.240/15342.663/73.027 ms, pipe 1562

planetlab4.clemson.edu:

--- 10.42.101.101 ping statistics ---
11693 packets transmitted, 0 received, +129 errors, 100% packet loss, time 131416ms
pipe 4
--
--- 10.42.101.101 ping statistics ---
13585766 packets transmitted, 9263789 received, 31% packet loss, time 107218483ms
rtt min/avg/max/mdev = 3.582/4.208/8717.049/22.313 ms, pipe 823

plnode1.cip.gatech.edu:

--- 10.42.101.73 ping statistics ---
10886851 packets transmitted, 6156327 received, 43% packet loss, time 107881509ms
rtt min/avg/max/mdev = 8.146/38.429/9021.162/17.822 ms, pipe 901

pl4.myplc.grnoc.iu.edu:

--- 10.42.101.112 ping statistics ---
10623170 packets transmitted, 5997749 received, 43% packet loss, time 107897957ms
rtt min/avg/max/mdev = 54.928/55.543/31019.006/34.814 ms, pipe 3091

orbitplc1.orbit-lab.org:

--- 10.42.101.91 ping statistics ---
10157911 packets transmitted, 7639252 received, 24% packet loss, time 122333217ms
rtt min/avg/max/mdev = 0.000/88.905/1539429.002/264.080 ms, pipe 2934

of-planet1.stanford.edu:

--- 10.42.101.81 ping statistics ---
9855957 packets transmitted, 6174833 received, 37% packet loss, time 107938274ms
rtt min/avg/max/mdev = 152.667/153.538/10275.952/30.624 ms, pipe 866

pl01.cs.washington.edu:

--- 10.42.101.96 ping statistics ---
9858796 packets transmitted, 6400905 received, 35% packet loss, time 107941283ms
rtt min/avg/max/mdev = 59.681/62.672/79689.934/213.076 ms, pipe 7187

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

--- 10.42.101.52 ping statistics ---
10639644 packets transmitted, 10339659 received, 2% packet loss, time 107964235ms
rtt min/avg/max/mdev = 29.546/29.931/15318.010/50.501 ms, pipe 1553

Analysis

The high packet loss was caused by the NLR OpenFlow software stack migration, not the Emergency Stop test itself.

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

Round 1

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 -A 2 statistics pgenigpolabbbncom_plastic$subnet\@$host.log ; echo -e "}}}\n" ; done

sardis.gpolab.bbn.com:

--- 10.42.102.104 ping statistics ---
11020228 packets transmitted, 7683177 received, 30% packet loss, time 106988674ms
rtt min/avg/max/mdev = 164.704/165.470/18298.280/30.614 ms, pipe 1810

planetlab5.clemson.edu:

--- 10.42.102.100 ping statistics ---
14641295 packets transmitted, 11707617 received, 20% packet loss, time 106999718ms
rtt min/avg/max/mdev = 3.577/4.472/26248.806/17.709 ms, pipe 2335

plnode2.cip.gatech.edu:

--- 10.42.102.72 ping statistics ---
10544938 packets transmitted, 7384548 received, 29% packet loss, time 107013563ms
rtt min/avg/max/mdev = 94.632/143.461/9093.793/22.880 ms, pipe 910

pl5.myplc.grnoc.iu.edu:

--- 10.42.102.111 ping statistics ---
10567157 packets transmitted, 7474264 received, 29% packet loss, time 107022108ms
rtt min/avg/max/mdev = 160.283/161.065/6173.288/12.767 ms, pipe 609

orbitplc2.orbit-lab.org:

--- 10.42.102.91 ping statistics ---
10082481 packets transmitted, 8351445 received, 17% packet loss, time 121433398ms
rtt min/avg/max/mdev = 84.530/86.516/1523265.330/120.902 ms, pipe 2748

of-planet1.stanford.edu:

--- 10.42.102.80 ping statistics ---
10099080 packets transmitted, 9410392 received, 6% packet loss, time 107055300ms
rtt min/avg/max/mdev = 20.049/21.365/29806.125/78.747 ms, pipe 2673
--
--- 10.42.102.80 ping statistics ---
10099080 packets transmitted, 9410392 received, 6% packet loss, time 107055300ms
rtt min/avg/max/mdev = 20.049/21.365/29806.125/78.747 ms, pipe 2673

pl02.cs.washington.edu:

--- 10.42.102.95 ping statistics ---
9896287 packets transmitted, 8200931 received, 17% packet loss, time 107074911ms
rtt min/avg/max/mdev = 59.678/61.534/7679.401/34.021 ms, pipe 691

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

--- 10.42.102.54 ping statistics ---
10287701 packets transmitted, 8559175 received, 16% packet loss, time 107078926ms
rtt min/avg/max/mdev = 29.538/30.273/47162.963/115.420 ms, pipe 4427

Analysis

The high packet loss was caused by the NLR OpenFlow software stack migration, not the Emergency Stop test itsef.

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

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

Round 1

Results

Generated with

subnet=103
for host in of-planet1.stanford.edu ganel.gpolab.bbn.com pl02.cs.washington.edu of-planet2.stanford.edu ; 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 45761 connected with 10.42.103.55 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-107206.8 sec  14702427515809245184 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 55400 connected with 10.42.103.111 port 5103
[  3]  0.0-107217.5 sec  24.4 GBytes  1.95 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 34918 connected with 10.42.103.54 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-107214.6 sec  15680587508745166848 bits  0.00 (null)s/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 33617 connected with 10.42.103.80 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-107225.7 sec  15786353488367775744 bits  0.00 (null)s/sec

Analysis

The results are reported strangely: "14702427515809245184 bits 0.00 (null)s/sec"? The server-side logs make it clear that data was being transfered, though -- with some gaps, but by and large, as expected.

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

Round 1

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 -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 43228 connected with 10.42.104.95 port 5104
[  3]  0.0-287.2 sec    103 MBytes  3.00 Mbits/sec
[  3] Sent 73268 datagrams
[  3] Server Report:
[  3]  0.0-152.2 sec  54.2 MBytes  2.99 Mbits/sec  0.008 ms 34575/73268 (47%)
[  3]  0.0-152.2 sec  7 datagrams received out-of-order
--
------------------------------------------------------------
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 43269 connected with 10.42.104.95 port 5104
write2 failed: Invalid argument
[  3]  0.0-5079.2 sec  1.77 GBytes  3.00 Mbits/sec
[  3] Sent 1295721 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 45310 connected with 10.42.104.95 port 5104
[  3]  0.0-93017.9 sec  32.5 GBytes  3.00 Mbits/sec
[  3] Sent 23728956 datagrams
[  3] Server Report:
[  3]  0.0-106824.3 sec  26.7 GBytes  2.15 Mbits/sec  0.007 ms 4192865/23728956 (18%)
[  3]  0.0-106824.3 sec  4382 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 58444 connected with 10.42.104.112 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-107115.2 sec  37.4 GBytes  3.00 Mbits/sec
[  3] Sent 27325281 datagrams
[  3] Server Report:
[  3]  0.0-121404.9 sec  31.9 GBytes  2.26 Mbits/sec   0.006 ms 4031254/27325280 (15%)
[  3]  0.0-121404.9 sec  789 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 36508 connected with 10.42.104.72 port 5104
write2 failed: Connection refused
[  3]  0.0-113.6 sec  40.6 MBytes  3.00 Mbits/sec
[  3] Sent 28985 datagrams
read failed: Connection refused
[  3] WARNING: did not receive ack of last datagram after 5 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 36510 connected with 10.42.104.72 port 5104
write2 failed: Connection refused
[  3]  0.0- 2.2 sec    820 KBytes  3.00 Mbits/sec
[  3] Sent 571 datagrams
read failed: Connection refused
[  3] WARNING: did not receive ack of last datagram after 1 tries.

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 42146 connected with 10.42.104.52 port 5104
write2 failed: Operation not permitted
[  3]  0.0-212.6 sec  76.0 MBytes  3.00 Mbits/sec
[  3] Sent 54235 datagrams
[  3] WARNING: did not receive ack of last datagram after 10 tries.

Analysis

The results are generally consistent with what we'd expect.

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

Round 1

Results

Generated with

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

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

(The pgenigpolabbbncom_plastic105@plnode1.cip.gatech.edu.log file was somewhat garbled, and thus processed separately, to skip the garbled end of the file.)

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 46117 connected with 10.42.105.105 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-106638.2 sec  15963149704666316800 bits  0.00 (null)s/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 43412 connected with 10.42.105.53 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-106656.6 sec  14853835148726927360 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 34435 connected with 10.42.105.101 port 5105
write2 failed: Connection timed out
[  3]  0.0-47341.7 sec  13.5 GBytes  2.45 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 59068 connected with 10.42.105.96 port 5105
nice -n 19 iperf -c $server -p 5105 -t 518400
------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 59068 connected with 10.42.105.96 port 5105
write2 failed: Connection timed out
[  3]  0.0-47318.0 sec  68.3 GBytes  12.4 Mbits/sec

Analysis

As in plastic-103, the results are reported strangely, but the server-side logs make it clear that data was being transfered.

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

Round 1

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 -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 60803 connected with 10.42.106.95 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-106707.7 sec  37.3 GBytes  3.00 Mbits/sec
[  3] Sent 27221363 datagrams
[  3] Server Report:
[  3]  0.0-106706.5 sec  29.6 GBytes  2.38 Mbits/sec   0.022 ms 5588962/27221362 (21%)
[  3]  0.0-106706.5 sec  14694 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 41297 connected with 10.42.106.100 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-106722.9 sec  37.3 GBytes  3.00 Mbits/sec
[  3] Sent 27225207 datagrams
[  3] Server Report:
[  3]  0.0-106721.6 sec  31.2 GBytes  2.51 Mbits/sec   0.020 ms 4416833/27225206 (16%)
[  3]  0.0-106721.6 sec  231902 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 49973 connected with 10.42.106.51 port 5106
[  3]  0.0-106733.6 sec  37.3 GBytes  3.00 Mbits/sec
[  3] Sent 27212296 datagrams
[  3] Server Report:
[  3]  0.0-106732.6 sec  35.7 GBytes  2.87 Mbits/sec  0.142 ms 1150469/27212296 (4.2%)
[  3]  0.0-106732.6 sec  2814 datagrams received out-of-order

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 53445 connected with 10.42.106.104 port 5106
[  3]  0.0-106739.0 sec  37.3 GBytes  3.00 Mbits/sec
[  3] Sent 27229300 datagrams
[  3] Server Report:
[  3]  0.0-106735.7 sec  30.4 GBytes  2.45 Mbits/sec  0.028 ms 5037614/27229300 (19%)
[  3]  0.0-106735.7 sec  1692 datagrams received out-of-order

Analysis

The results are generally consistent with what we'd expect.

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

Round 1

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 -a "md5sum:" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e -n "matching md5sum lines: " ; grep -a "md5sum: d4fcf71833327fbfef98be09deef8bfb" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e "}}}\n" ; done

planetlab5.clemson.edu:

total md5sum lines: 1062
matching md5sum lines: 1061

pl5.myplc.grnoc.iu.edu:

total md5sum lines: 5035
matching md5sum lines: 5034

plnode1.cip.gatech.edu:

total md5sum lines: 2056
matching md5sum lines: 2055

pl01.cs.washington.edu:

total md5sum lines: 2648
matching md5sum lines: 2647

Analysis

The results are generally consistent with what we'd expect.

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

Round 1

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 -a "md5sum:" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e -n "matching md5sum lines: " ; grep -a "md5sum: d4fcf71833327fbfef98be09deef8bfb" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e "}}}\n" ; done

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

total md5sum lines: 3112
matching md5sum lines: 3111

of-planet1.stanford.edu:

total md5sum lines: 2549
matching md5sum lines: 2544

orbitplc2.orbit-lab.org:

total md5sum lines: 531
matching md5sum lines: 530

pl4.myplc.grnoc.iu.edu:

total md5sum lines: 11425
matching md5sum lines: 11424

Analysis

The results are generally consistent with what we'd expect.

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

Round 1

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 -a "substrate.doc" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e -n "matching md5sum lines: " ; grep -a "d4fcf71833327fbfef98be09deef8bfb  substrate.doc" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e "}}}\n" ; done

navis.gpolab.bbn.com:

total md5sum lines: 225
matching md5sum lines: 224

pl4.myplc.grnoc.iu.edu:

total md5sum lines: 1977
matching md5sum lines: 1968

pl01.cs.washington.edu:

total md5sum lines: 1142
matching md5sum lines: 1140

planetlab4.clemson.edu:

total md5sum lines: 6368
matching md5sum lines: 6251

of-planet2.stanford.edu:

total md5sum lines: 728
matching md5sum lines: 727

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

total md5sum lines: 3485
matching md5sum lines: 3461

Analysis

The results are generally consistent with what we'd expect.

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

Round 1

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 -a "substrate.doc" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e -n "matching md5sum lines: " ; grep -a "d4fcf71833327fbfef98be09deef8bfb  substrate.doc" pgenigpolabbbncom_plastic$subnet\@$host.log | wc -l ; echo -e "}}}\n" ; done

gardil.gpolab.bbn.com:

total md5sum lines: 4498
matching md5sum lines: 4443

pl02.cs.washington.edu:

total md5sum lines: 2412
matching md5sum lines: 2410

of-planet2.stanford.edu:

total md5sum lines: 2591
matching md5sum lines: 2493

orbitplc1.orbit-lab.org:

total md5sum lines: 453
matching md5sum lines: 450

pl5.myplc.grnoc.iu.edu:

total md5sum lines: 501
matching md5sum lines: 499

plnode2.cip.gatech.edu:

total md5sum lines: 2141
matching md5sum lines: 2040

Analysis

The results are generally consistent with what we'd expect.

Last modified 9 years ago Last modified on 07/11/11 21:23:32