Changes between Version 2 and Version 3 of PlasticSlices/Continuation/Round9


Ignore:
Timestamp:
05/25/12 13:27:45 (7 years ago)
Author:
Josh Smift
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PlasticSlices/Continuation/Round9

    v2 v3  
    44
    55In this round, the plan was to run all ten slices on all seven sites, for a week.
     6
     7Wisconsin suffered a major outage in the middle of the week, affecting all of the slices that they're a part of.
    68
    79The raw logs are at http://www.gpolab.bbn.com/plastic-slices/continuation/round-9/.
     
    3638}}}
    3739
     40ganel.gpolab.bbn.com:
     41
     42{{{
     43--- 10.42.101.105 ping statistics ---
     4460616348 packets transmitted, 60101723 received, +4555 errors, 0% packet loss, time 603873971ms
     45rtt min/avg/max/mdev = 137.979/138.803/29421.397/74.601 ms, pipe 3868
     46}}}
     47
     48planetlab4.clemson.edu:
     49
     50{{{
     51--- 10.42.101.101 ping statistics ---
     5260428426 packets transmitted, 54618968 received, +4576 errors, 9% packet loss, time 604322150ms
     53rtt min/avg/max/mdev = 5.320/56.341/24832.987/38.795 ms, pipe 2486
     54}}}
     55
     56plnode1.cip.gatech.edu:
     57
     58{{{
     59--- 10.42.101.73 ping statistics ---
     6063749841 packets transmitted, 63177150 received, +4782 errors, 0% packet loss, time 603992529ms
     61rtt min/avg/max/mdev = 37.118/38.150/42375.436/75.287 ms, pipe 4211
     62}}}
     63
     64pl4.myplc.grnoc.iu.edu:
     65
     66{{{
     67--- 10.42.101.91 ping statistics ---
     6860563865 packets transmitted, 59943291 received, +5993 errors, 1% packet loss, time 603979365ms
     69rtt min/avg/max/mdev = 102.673/102.975/14960.036/33.122 ms, pipe 1414
     70}}}
     71
     72of-planet1.stanford.edu:
     73
     74{{{
     75--- 10.42.101.81 ping statistics ---
     7659627849 packets transmitted, 58755149 received, +6237 errors, 1% packet loss, time 603972071ms
     77rtt min/avg/max/mdev = 153.075/154.404/13256.334/43.909 ms, pipe 1356
     78}}}
     79
     80pl01.cs.washington.edu:
     81
     82{{{
     83--- 10.42.101.96 ping statistics ---
     8457466511 packets transmitted, 32971249 received, +257541 errors, 42% packet loss, time 603931891ms
     85rtt min/avg/max/mdev = 59.706/61.876/10494.960/37.911 ms, pipe 1009
     86}}}
     87
     88wings-openflow-2.wail.wisc.edu:
     89
     90{{{
     91}}}
     92
    3893== Comments ==
    3994
    40 ''(forthcoming)''
     95We didn't get any log data from wings-openflow-2.wail.wisc.edu, and high packet loss from pl01.cs.washington.edu to 1042.101.96 (on wings-openflow-3.wail.wisc.edu), due to the outage at Wisconsin.
     96
     97The 9% packet loss from planetlab4.clemson.edu to 10.42.101.101 (on plnode2.cip.gatech.edu) is unexpectedly high; we haven't investigated the cause.
    4198
    4299= plastic-102 =
     
    69126}}}
    70127
     128navis.gpolab.bbn.com:
     129
     130{{{
     131--- 10.42.102.104 ping statistics ---
     13260388197 packets transmitted, 59890888 received, +4716 errors, 0% packet loss, time 603564330ms
     133rtt min/avg/max/mdev = 165.433/165.715/19394.280/32.904 ms, pipe 1793
     134}}}
     135
     136planetlab5.clemson.edu:
     137
     138{{{
     139--- 10.42.102.100 ping statistics ---
     14099111985 packets transmitted, 98010857 received, +4419 errors, 1% packet loss, time 603621429ms
     141rtt min/avg/max/mdev = 4.902/6.045/4318.493/7.668 ms, pipe 687
     142}}}
     143
     144plnode2.cip.gatech.edu:
     145
     146{{{
     147--- 10.42.102.72 ping statistics ---
     14836404450 packets transmitted, 35859984 received, +4773 errors, 1% packet loss, time 603602380ms
     149rtt min/avg/max/mdev = 143.039/175.294/17996.136/56.039 ms, pipe 1080
     150}}}
     151
     152pl5.myplc.grnoc.iu.edu:
     153
     154{{{
     155--- 10.42.102.91 ping statistics ---
     15662114299 packets transmitted, 61520938 received, +5814 errors, 0% packet loss, time 603590568ms
     157rtt min/avg/max/mdev = 77.454/77.687/16509.553/22.526 ms, pipe 1475
     158}}}
     159
     160of-planet1.stanford.edu:
     161
     162{{{
     163--- 10.42.102.80 ping statistics ---
     16457598200 packets transmitted, 56930142 received, +5607 errors, 1% packet loss, time 603580960ms
     165rtt min/avg/max/mdev = 20.442/21.395/13855.638/14.768 ms, pipe 1274
     166}}}
     167
     168pl02.cs.washington.edu:
     169
     170{{{
     171--- 10.42.102.95 ping statistics ---
     17256998165 packets transmitted, 31861651 received, +257001 errors, 44% packet loss, time 603573426ms
     173rtt min/avg/max/mdev = 59.711/61.799/17626.355/39.431 ms, pipe 1535
     174}}}
     175
     176wings-openflow-3.wail.wisc.edu:
     177
     178{{{
     179}}}
     180
    71181== Comments ==
    72182
    73 ''(forthcoming)''
     183We didn't get any log data from wings-openflow-3.wail.wisc.edu, and high packet loss from pl02.cs.washington.edu to 1042.101.95 (on wings-openflow-2.wail.wisc.edu), due to the outage at Wisconsin.
     184
     185The absence of packet loss between Clemson and GT here, compared to plastic-101, is somewhat unexpected; we haven't investigated it.
    74186
    75187= plastic-103 =
     
    113225and then edited slightly to remove artifacts (like control characters, my prompt, etc).
    114226
     227sardis.gpolab.bbn.com:
     228
     229{{{
     230------------------------------------------------------------
     231Client connecting to 10.42.103.90, TCP port 5103
     232TCP window size: 16.0 KByte (default)
     233------------------------------------------------------------
     234[  3] local 10.42.103.53 port 60939 connected with 10.42.103.90 port 5103
     235write2 failed: No route to host
     236[  3]  0.0-359374.0 sec    104 GBytes  2.48 Mbits/sec
     237--
     238------------------------------------------------------------
     239Client connecting to 10.42.103.90, TCP port 5103
     240TCP window size: 16.0 KByte (default)
     241------------------------------------------------------------
     242[  3] local 10.42.103.53 port 48795 connected with 10.42.103.90 port 5103
     243write2 failed: No route to host
     244[  3]  0.0-62326.2 sec  17.6 GBytes  2.43 Mbits/sec
     245}}}
     246
     247of-planet2.stanford.edu:
     248
     249{{{
     250------------------------------------------------------------
     251Client connecting to 10.42.103.80, TCP port 5103
     252TCP window size: 16.0 KByte (default)
     253------------------------------------------------------------
     254[  3] local 10.42.103.91 port 36826 connected with 10.42.103.80 port 5103
     255[ ID] Interval       Transfer     Bandwidth
     256[  3]  0.0-423883.1 sec  17561894255500267520 bits  0.00 (null)s/sec
     257--
     258------------------------------------------------------------
     259Client connecting to 10.42.103.80, TCP port 5103
     260TCP window size: 16.0 KByte (default)
     261------------------------------------------------------------
     262[  3] local 10.42.103.91 port 34411 connected with 10.42.103.80 port 5103
     263[ ID] Interval       Transfer     Bandwidth
     264[  3]  0.0-179565.0 sec  13485676214369468416 bits  0.00 (null)s/sec
     265}}}
     266
     267pl02.cs.washington.edu:
     268
     269{{{
     270------------------------------------------------------------
     271Client connecting to 10.42.103.51, TCP port 5103
     272TCP window size: 16.0 KByte (default)
     273------------------------------------------------------------
     274[  3] local 10.42.103.81 port 46683 connected with 10.42.103.51 port 5103
     275write2 failed: No route to host
     276[  3]  0.0-486223.7 sec    127 GBytes  2.23 Mbits/sec
     277}}}
     278
    115279== Comments ==
    116280
    117 ''(forthcoming)''
     281We've seen the "0.00 (null)s/sec" business from iperf TCP summaries before; traffic is clearly flowing, so we're not sure what causes that.
     282
     283None of these ran to completion, due to temporary network failures (the "no route to host" errors). It'd be nice to have a more resilient TCP traffic generator.
    118284
    119285= plastic-104 =
     
    156322and then edited slightly to remove artifacts (like control characters, my prompt, etc).
    157323
     324ganel.gpolab.bbn.com:
     325
     326{{{
     327------------------------------------------------------------
     328Client connecting to 10.42.104.95, UDP port 5104
     329Sending 1470 byte datagrams
     330UDP buffer size:   110 KByte (default)
     331------------------------------------------------------------
     332[  3] local 10.42.104.51 port 41464 connected with 10.42.104.95 port 5104
     333[  3]  0.0-518400.0 sec    664 GBytes  11.0 Mbits/sec
     334[  3] Sent 484931597 datagrams
     335[  3] WARNING: did not receive ack of last datagram after 10 tries.
     336}}}
     337
     338pl5.myplc.grnoc.iu.edu:
     339
     340{{{
     341------------------------------------------------------------
     342Client connecting to 10.42.104.53, UDP port 5104
     343Sending 1470 byte datagrams
     344UDP buffer size:   110 KByte (default)
     345------------------------------------------------------------
     346[  3] local 10.42.104.73 port 54328 connected with 10.42.104.53 port 5104
     347[  3]  0.0-518400.0 sec    664 GBytes  11.0 Mbits/sec
     348[  3] Sent 484932280 datagrams
     349[  3] Server Report:
     350[  3]  0.0-518390.2 sec    657 GBytes  10.9 Mbits/sec  0.017 ms 5368914/484932279 (1.1%)
     351[  3]  0.0-518390.2 sec  16126 datagrams received out-of-order
     352}}}
     353
    158354== Comments ==
    159355
    160 ''(forthcoming)''
     356We didn't get back a server report from ganel.gpolab.bbn.com, due to the outage at Wisconsin. (It was connecting to 10.42.104.95.)
     357
     358We haven't analyzed whether the packet loss from Indiana to BBN was consistent throughout the run, or due to a single outage, or what.
    161359
    162360= plastic-105 =
     
    201399and then edited slightly to remove artifacts (like control characters, my prompt, etc).
    202400
     401wings-openflow-2.wail.wisc.edu:
     402
     403{{{
     404------------------------------------------------------------
     405Client connecting to 10.42.105.105, UDP port 5105
     406Sending 1470 byte datagrams
     407UDP buffer size:  110 KByte (default)
     408------------------------------------------------------------
     409[  3] local 10.42.105.95 port 60158 connected with 10.42.105.105 port 5105
     410}}}
     411
     412planetlab4.clemson.edu:
     413
     414{{{
     415------------------------------------------------------------
     416Client connecting to 10.42.105.55, UDP port 5105
     417Sending 1470 byte datagrams
     418UDP buffer size:  110 KByte (default)
     419------------------------------------------------------------
     420[  3] local 10.42.105.104 port 41408 connected with 10.42.105.55 port 5105
     421[ ID] Interval       Transfer     Bandwidth
     422[  3]  0.0-518400.0 sec   362 GBytes  6.00 Mbits/sec
     423[  3] Sent 264489797 datagrams
     424[  3] Server Report:
     425[  3]  0.0-518394.5 sec   358 GBytes  5.94 Mbits/sec   0.010 ms 2818608/264489796 (1.1%)
     426[  3]  0.0-518394.5 sec  8277 datagrams received out-of-order
     427}}}
     428
     429bain.gpolab.bbn.com:
     430
     431{{{
     432------------------------------------------------------------
     433Client connecting to 10.42.105.101, UDP port 5105
     434Sending 1470 byte datagrams
     435UDP buffer size:   110 KByte (default)
     436------------------------------------------------------------
     437[  3] local 10.42.105.54 port 37129 connected with 10.42.105.101 port 5105
     438[  3]  0.0-518400.0 sec    362 GBytes  6.00 Mbits/sec
     439[  3] Sent 264487534 datagrams
     440[  3] Server Report:
     441[  3]  0.0-518396.4 sec    357 GBytes  5.92 Mbits/sec  3.197 ms 3455085/264487534 (1.3%)
     442[  3]  0.0-518396.4 sec  7492 datagrams received out-of-order
     443}}}
     444
     445plnode1.cip.gatech.edu:
     446
     447{{{
     448------------------------------------------------------------
     449Client connecting to 10.42.105.96, UDP port 5105
     450Sending 1470 byte datagrams
     451UDP buffer size:   122 KByte (default)
     452------------------------------------------------------------
     453[  3] local 10.42.105.100 port 47829 connected with 10.42.105.96 port 5105
     454[  3]  0.0-518400.0 sec    362 GBytes  6.00 Mbits/sec
     455[  3] Sent 264473352 datagrams
     456[  3] WARNING: did not receive ack of last datagram after 10 tries.
     457}}}
     458
    203459== Comments ==
    204460
    205 ''(forthcoming)''
     461We didn't get any log data from wings-openflow-2.wail.wisc.edu, due to the outage at Wisconsin.
     462
     463We didn't get back a server report from plnode1.cip.gatech.edu, due to the outage at Wisconsin. (It was connecting to 10.42.104.96.)
     464
     465We haven't analyzed whether the packet loss in the others was consistent throughout the run, or due to a single outage, or what.
    206466
    207467= plastic-106 =
     
    246506and then edited slightly to remove artifacts (like control characters, my prompt, etc).
    247507
     508planetlab5.clemson.edu:
     509
     510{{{
     511------------------------------------------------------------
     512Client connecting to 10.42.106.95, TCP port 5106
     513TCP window size: 16.0 KByte (default)
     514------------------------------------------------------------
     515[  3] local 10.42.106.105 port 55591 connected with 10.42.106.95 port 5106
     516[ ID] Interval       Transfer     Bandwidth
     517[  3]  0.0-518400.0 sec  14017702187097243648 bits  0.00 (null)s/sec
     518}}}
     519
     520wings-openflow-3.wail.wisc.edu:
     521
     522{{{
     523------------------------------------------------------------
     524Client connecting to 10.42.106.100, TCP port 5106
     525TCP window size: 16.0 KByte (default)
     526------------------------------------------------------------
     527[  3] local 10.42.106.96 port 32950 connected with 10.42.106.100 port 5106
     528}}}
     529
     530plnode2.cip.gatech.edu:
     531
     532{{{
     533------------------------------------------------------------
     534Client connecting to 10.42.106.54, TCP port 5106
     535TCP window size: 16.0 KByte (default)
     536------------------------------------------------------------
     537[  3] local 10.42.106.101 port 46041 connected with 10.42.106.54 port 5106
     538write2 failed: No route to host
     539[  3]  0.0-486087.3 sec  16.7 GBytes    296 Kbits/sec
     540}}}
     541
     542navis.gpolab.bbn.com:
     543
     544{{{
     545------------------------------------------------------------
     546Client connecting to 10.42.106.104, TCP port 5106
     547TCP window size: 16.0 KByte (default)
     548------------------------------------------------------------
     549[  3] local 10.42.106.55 port 60960 connected with 10.42.106.104 port 5106
     550write2 failed: No route to host
     551[  3]  0.0-486070.0 sec    171 GBytes  3.02 Mbits/sec
     552}}}
     553
    248554== Comments ==
    249555
    250 ''(forthcoming)''
     556We've seen the "0.00 (null)s/sec" business from iperf TCP summaries before; traffic is clearly flowing, so we're not sure what causes that.
     557
     558We didn't get any log data from wings-openflow-3.wail.wisc.edu, due to the outage at Wisconsin.
     559
     560Neither of the others ran to completion, due to temporary network failures (the "no route to host" errors). It'd be nice to have a more resilient TCP traffic generator.
    251561
    252562= plastic-107 =
     
    291601and then edited slightly to remove artifacts (like control characters, my prompt, etc).
    292602
     603planetlab5.clemson.edu:
     604
     605{{{
     606------------------------------------------------------------
     607Client connecting to 10.42.107.72, TCP port 5107
     608TCP window size: 16.0 KByte (default)
     609------------------------------------------------------------
     610[  3] local 10.42.107.105 port 50196 connected with 10.42.107.72 port 5107
     611[ ID] Interval       Transfer     Bandwidth
     612[  3]  0.0-518400.0 sec  9618427753724442624 bits  0.00 (null)s/sec
     613}}}
     614
     615pl5.myplc.grnoc.iu.edu:
     616
     617{{{
     618------------------------------------------------------------
     619Client connecting to 10.42.107.101, TCP port 5107
     620TCP window size: 16.0 KByte (default)
     621------------------------------------------------------------
     622[  3] local 10.42.107.73 port 38928 connected with 10.42.107.101 port 5107
     623write2 failed: No route to host
     624[  3]  0.0-486026.4 sec    143 GBytes  2.53 Mbits/sec
     625}}}
     626
     627plnode1.cip.gatech.edu:
     628
     629{{{
     630------------------------------------------------------------
     631Client connecting to 10.42.107.81, TCP port 5107
     632TCP window size: 16.0 KByte (default)
     633------------------------------------------------------------
     634[  3] local 10.42.107.100 port 55218 connected with 10.42.107.81 port 5107
     635write2 failed: No route to host
     636[  3]  0.0-486028.4 sec    255 GBytes  4.51 Mbits/sec
     637}}}
     638
     639pl01.cs.washington.edu:
     640
     641{{{
     642------------------------------------------------------------
     643Client connecting to 10.42.107.104, TCP port 5107
     644TCP window size: 16.0 KByte (default)
     645------------------------------------------------------------
     646[  3] local 10.42.107.80 port 57380 connected with 10.42.107.104 port 5107
     647write2 failed: No route to host
     648[  3]  0.0-486023.2 sec    279 GBytes  4.92 Mbits/sec
     649}}}
     650
    293651== Comments ==
    294652
    295 ''(forthcoming)''
     653We've seen the "0.00 (null)s/sec" business from iperf TCP summaries before; traffic is clearly flowing, so we're not sure what causes that.
     654
     655None of the others ran to completion, due to temporary network failures (the "no route to host" errors). It'd be nice to have a more resilient TCP traffic generator.
    296656
    297657= plastic-108 =
     
    335695and then edited slightly to remove artifacts (like control characters, my prompt, etc).
    336696
     697wings-openflow-3.wail.wisc.edu:
     698
     699{{{
     700------------------------------------------------------------
     701Client connecting to 10.42.108.91, UDP port 5108
     702Sending 1470 byte datagrams
     703UDP buffer size:  110 KByte (default)
     704------------------------------------------------------------
     705[  3] local 10.42.108.96 port 46435 connected with 10.42.108.91 port 5108
     706}}}
     707
     708of-planet1.stanford.edu:
     709
     710{{{
     711------------------------------------------------------------
     712Client connecting to 10.42.108.73, UDP port 5108
     713Sending 1470 byte datagrams
     714UDP buffer size:  110 KByte (default)
     715------------------------------------------------------------
     716[  3] local 10.42.108.90 port 60229 connected with 10.42.108.73 port 5108
     717[ ID] Interval       Transfer     Bandwidth
     718[  3]  0.0-518400.0 sec   483 GBytes  8.00 Mbits/sec
     719[  3] Sent 352626691 datagrams
     720[  3] Server Report:
     721[  3]  0.0-518393.7 sec   476 GBytes  7.88 Mbits/sec   0.027 ms 5105757/352626690 (1.4%)
     722[  3]  0.0-518393.7 sec  16667 datagrams received out-of-order
     723}}}
     724
     725pl4.myplc.grnoc.iu.edu:
     726
     727{{{
     728------------------------------------------------------------
     729Client connecting to 10.42.108.95, UDP port 5108
     730Sending 1470 byte datagrams
     731UDP buffer size:   110 KByte (default)
     732------------------------------------------------------------
     733[  3] local 10.42.108.72 port 46159 connected with 10.42.108.95 port 5108
     734[  3]  0.0-518400.0 sec    483 GBytes  8.00 Mbits/sec
     735[  3] Sent 352649481 datagrams
     736[  3] WARNING: did not receive ack of last datagram after 10 tries.
     737}}}
     738
    337739== Comments ==
    338740
    339 ''(forthcoming)''
     741We didn't get any log data from wings-openflow-3.wail.wisc.edu, due to the outage at Wisconsin.
     742
     743We didn't get back a server report from pl4.myplc.grnoc.iu.edu, due to the outage at Wisconsin. (It was connecting to 10.42.108.95.)
     744
     745We haven't analyzed whether the packet loss in the other was consistent throughout the run, or due to a single outage, or what.
    340746
    341747= plastic-109 =
     
    382788and then edited slightly to remove artifacts (like control characters, my prompt, etc).
    383789
     790gardil.gpolab.bbn.com:
     791
     792{{{
     793------------------------------------------------------------
     794Client connecting to 10.42.109.73, UDP port 5109
     795Sending 1470 byte datagrams
     796UDP buffer size:   110 KByte (default)
     797------------------------------------------------------------
     798[  3] local 10.42.109.52 port 34116 connected with 10.42.109.73 port 5109
     799[  3]  0.0-518400.0 sec    241 GBytes  4.00 Mbits/sec
     800[  3] Sent 176326532 datagrams
     801[  3] Server Report:
     802[  3]  0.0-518397.1 sec    239 GBytes  3.96 Mbits/sec  0.005 ms 1921335/176326532 (1.1%)
     803[  3]  0.0-518397.1 sec  8568 datagrams received out-of-order
     804}}}
     805
     806pl4.myplc.grnoc.iu.edu:
     807
     808{{{
     809------------------------------------------------------------
     810Client connecting to 10.42.109.81, UDP port 5109
     811Sending 1470 byte datagrams
     812UDP buffer size:   110 KByte (default)
     813------------------------------------------------------------
     814[  3] local 10.42.109.72 port 42414 connected with 10.42.109.81 port 5109
     815[  3]  0.0-518400.0 sec    241 GBytes  4.00 Mbits/sec
     816[  3] Sent 176326102 datagrams
     817[  3] Server Report:
     818[  3]  0.0-518397.2 sec    239 GBytes  3.96 Mbits/sec  0.891 ms 1925666/176326102 (1.1%)
     819[  3]  0.0-518397.2 sec  79755 datagrams received out-of-order
     820}}}
     821
     822pl01.cs.washington.edu:
     823
     824{{{
     825------------------------------------------------------------
     826Client connecting to 10.42.109.105, UDP port 5109
     827Sending 1470 byte datagrams
     828UDP buffer size:   110 KByte (default)
     829------------------------------------------------------------
     830[  3] local 10.42.109.80 port 57597 connected with 10.42.109.105 port 5109
     831[  3]  0.0-518400.0 sec    241 GBytes  4.00 Mbits/sec
     832[  3] Sent 176247368 datagrams
     833[  3] Server Report:
     834[  3]  0.0-518395.7 sec    238 GBytes  3.95 Mbits/sec  0.100 ms 2084033/176247368 (1.2%)
     835[  3]  0.0-518395.7 sec  24113 datagrams received out-of-order
     836}}}
     837
     838planetlab4.clemson.edu:
     839
     840{{{
     841------------------------------------------------------------
     842Client connecting to 10.42.109.90, UDP port 5109
     843Sending 1470 byte datagrams
     844UDP buffer size:  110 KByte (default)
     845------------------------------------------------------------
     846[  3] local 10.42.109.104 port 38981 connected with 10.42.109.90 port 5109
     847[ ID] Interval       Transfer     Bandwidth
     848[  3]  0.0-518400.0 sec   241 GBytes  4.00 Mbits/sec
     849[  3] Sent 176326532 datagrams
     850[  3] Server Report:
     851[  3]  0.0-518397.4 sec   238 GBytes  3.94 Mbits/sec   0.019 ms 2472993/176326531 (1.4%)
     852[  3]  0.0-518397.4 sec  10171 datagrams received out-of-order
     853}}}
     854
     855of-planet2.stanford.edu:
     856
     857{{{
     858------------------------------------------------------------
     859Client connecting to 10.42.109.96, UDP port 5109
     860Sending 1470 byte datagrams
     861UDP buffer size:  110 KByte (default)
     862------------------------------------------------------------
     863[  3] local 10.42.109.91 port 43669 connected with 10.42.109.96 port 5109
     864[ ID] Interval       Transfer     Bandwidth
     865[  3]  0.0-518400.0 sec   241 GBytes  4.00 Mbits/sec
     866[  3] Sent 176324610 datagrams
     867[  3] WARNING: did not receive ack of last datagram after 10 tries.
     868}}}
     869
     870wings-openflow-2.wail.wisc.edu:
     871
     872{{{
     873------------------------------------------------------------
     874Client connecting to 10.42.109.51, UDP port 5109
     875Sending 1470 byte datagrams
     876UDP buffer size:  110 KByte (default)
     877------------------------------------------------------------
     878[  3] local 10.42.109.95 port 59778 connected with 10.42.109.51 port 5109
     879}}}
     880
    384881== Comments ==
    385882
    386 ''(forthcoming)''
     883We didn't get back a server report from of-planet2.stanford.edu, due to the outage at Wisconsin. (It was connecting to 10.42.109.96.)
     884
     885We didn't get any log data from wings-openflow-2.wail.wisc.edu, due to the outage at Wisconsin.
     886
     887We haven't analyzed whether the packet loss in the others was consistent throughout the run, or due to a single outage, or what.
    387888
    388889= plastic-110 =
     
    428929and then edited slightly to remove artifacts (like control characters, my prompt, etc).
    429930
     931bain.gpolab.bbn.com:
     932
     933{{{
     934------------------------------------------------------------
     935Client connecting to 10.42.110.80, TCP port 5110
     936TCP window size: 16.0 KByte (default)
     937------------------------------------------------------------
     938[  3] local 10.42.110.54 port 59225 connected with 10.42.110.80 port 5110
     939write2 failed: No route to host
     940[  3]  0.0-485821.8 sec    346 GBytes  6.12 Mbits/sec
     941}}}
     942
     943pl02.cs.washington.edu:
     944
     945{{{
     946------------------------------------------------------------
     947Client connecting to 10.42.110.90, TCP port 5110
     948TCP window size: 16.0 KByte (default)
     949------------------------------------------------------------
     950[  3] local 10.42.110.81 port 46991 connected with 10.42.110.90 port 5110
     951write2 failed: No route to host
     952[  3]  0.0-359034.3 sec    937 GBytes  22.4 Mbits/sec
     953--
     954------------------------------------------------------------
     955Client connecting to 10.42.110.90, TCP port 5110
     956TCP window size: 16.0 KByte (default)
     957------------------------------------------------------------
     958[  3] local 10.42.110.81 port 55111 connected with 10.42.110.90 port 5110
     959write2 failed: No route to host
     960[  3]  0.0-63692.8 sec    170 GBytes  22.9 Mbits/sec
     961}}}
     962
     963of-planet2.stanford.edu:
     964
     965{{{
     966------------------------------------------------------------
     967Client connecting to 10.42.110.72, TCP port 5110
     968TCP window size: 16.0 KByte (default)
     969------------------------------------------------------------
     970[  3] local 10.42.110.91 port 59670 connected with 10.42.110.72 port 5110
     971[ ID] Interval       Transfer     Bandwidth
     972[  3]  0.0-422191.7 sec  17205709671801458688 bits  0.00 (null)s/sec
     973--
     974------------------------------------------------------------
     975Client connecting to 10.42.110.72, TCP port 5110
     976TCP window size: 16.0 KByte (default)
     977------------------------------------------------------------
     978[  3] local 10.42.110.91 port 57556 connected with 10.42.110.72 port 5110
     979[ ID] Interval       Transfer     Bandwidth
     980[  3]  0.0-179228.7 sec  13026921957609984000 bits  0.00 (null)s/sec
     981}}}
     982
     983pl5.myplc.grnoc.iu.edu:
     984
     985{{{
     986------------------------------------------------------------
     987Client connecting to 10.42.110.100, TCP port 5110
     988TCP window size: 16.0 KByte (default)
     989------------------------------------------------------------
     990[  3] local 10.42.110.73 port 34143 connected with 10.42.110.100 port 5110
     991write2 failed: No route to host
     992[  3]  0.0-134175.6 sec  45.2 GBytes  2.89 Mbits/sec
     993--
     994------------------------------------------------------------
     995Client connecting to 10.42.110.100, TCP port 5110
     996TCP window size: 16.0 KByte (default)
     997------------------------------------------------------------
     998[  3] local 10.42.110.73 port 55400 connected with 10.42.110.100 port 5110
     999write2 failed: No route to host
     1000[  3]  0.0-240750.2 sec  83.3 GBytes  2.97 Mbits/sec
     1001}}}
     1002
     1003plnode2.cip.gatech.edu:
     1004
     1005{{{
     1006------------------------------------------------------------
     1007Client connecting to 10.42.110.55, TCP port 5110
     1008TCP window size: 16.0 KByte (default)
     1009------------------------------------------------------------
     1010[  3] local 10.42.110.101 port 52109 connected with 10.42.110.55 port 5110
     1011write2 failed: No route to host
     1012[  3]  0.0-134135.9 sec  8.72 GBytes    559 Kbits/sec
     1013--
     1014------------------------------------------------------------
     1015Client connecting to 10.42.110.55, TCP port 5110
     1016TCP window size: 16.0 KByte (default)
     1017------------------------------------------------------------
     1018[  3] local 10.42.110.101 port 35891 connected with 10.42.110.55 port 5110
     1019write2 failed: No route to host
     1020[  3]  0.0-240675.2 sec  14.1 GBytes    503 Kbits/sec
     1021}}}
     1022
    4301023== Comments ==
    4311024
    432 ''(forthcoming)''
     1025We've seen the "0.00 (null)s/sec" business from iperf TCP summaries before; traffic is clearly flowing, so we're not sure what causes that.
     1026
     1027None of the others ran to completion, due to temporary network failures (the "no route to host" errors). It'd be nice to have a more resilient TCP traffic generator.