Version 1 (modified by 13 years ago) (diff) | ,
---|
Continuation Round 2
In this round, I ran plastic-104 for about three days, to try to exercise a monitoring bug.
The raw logs are at http://www.gpolab.bbn.com/plastic-slices/continuation/round-2/.
plastic-104
SteadyPerf UDP, using port=5104, time=518400, rate=3, and this table of client/server pairs:
client | server | server address |
ganel.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 | sardis.gpolab.bbn.com | server=10.42.104.53 |
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 $(awk 'NR%2==1' ~/plastic-slices/logins/logins-plastic-$subnet.txt | sed -r -e 's/.+@//') ; 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).
ganel.gpolab.bbn.com:
------------------------------------------------------------ Client connecting to 10.42.104.95, UDP port 5104 Sending 1470 byte datagrams UDP buffer size: 110 KByte (default) ------------------------------------------------------------ [ 3] local 10.42.104.51 port 56273 connected with 10.42.104.95 port 5104 [ 3] 0.0-243894.3 sec 85.2 GBytes 3.00 Mbits/sec [ 3] Sent 62217930 datagrams [ 3] Server Report: [ 3] 0.0-243892.1 sec 85.2 GBytes 3.00 Mbits/sec 0.010 ms 647/62217930 (0.001%) [ 3] 0.0-243892.1 sec 360 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: 110 KByte (default) ------------------------------------------------------------ [ 3] local 10.42.104.96 port 39179 connected with 10.42.104.112 port 5104 [ ID] Interval Transfer Bandwidth [ 3] 0.0-243902.8 sec 85.2 GBytes 3.00 Mbits/sec [ 3] Sent 62220093 datagrams [ 3] Server Report: [ 3] 0.0-243900.0 sec 85.2 GBytes 3.00 Mbits/sec 0.021 ms 952/62220093 (0.0015%) [ 3] 0.0-243900.0 sec 119 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: 110 KByte (default) ------------------------------------------------------------ [ 3] local 10.42.104.111 port 44818 connected with 10.42.104.72 port 5104 [ 3] 0.0-243912.5 sec 85.2 GBytes 3.00 Mbits/sec [ 3] Sent 62222584 datagrams [ 3] Server Report: [ 3] 0.0-243909.0 sec 85.2 GBytes 3.00 Mbits/sec 0.005 ms 1228/62222584 (0.002%) [ 3] 0.0-243909.0 sec 5091 datagrams received out-of-order
pl5.myplc.grnoc.iu.edu:
------------------------------------------------------------ Client connecting to 10.42.104.53, UDP port 5104 Sending 1470 byte datagrams UDP buffer size: 110 KByte (default) ------------------------------------------------------------ [ 3] local 10.42.104.73 port 34865 connected with 10.42.104.53 port 5104 [ 3] 0.0-243919.2 sec 85.2 GBytes 3.00 Mbits/sec [ 3] Sent 62224276 datagrams [ 3] Server Report: [ 3] 0.0-243916.3 sec 85.2 GBytes 3.00 Mbits/sec 0.005 ms 1186/62224276 (0.0019%) [ 3] 0.0-243916.3 sec 193 datagrams received out-of-order
Analysis
All data seems to have been sent successfully (up to four nines, anyway).