Changes between Version 18 and Version 19 of PlasticSlices/OFStatus

Timestamp:

05/10/11 16:26:26 (13 years ago)

Author:

Josh Smift

Comment:

--

PlasticSlices/OFStatus

@@ -15 +15 @@
 || NLR          || 2011-04-25     || CT || AM || CA || LR || RS || SL || FV || NT || XT || Fully armed and operational. ||
 ||              ||                ||    ||    ||    ||    ||    ||    ||    ||    ||    ||  ||
-|| Rutgers      || 2011-05-02     ||    ||    ||    ||    ||    ||    ||    ||    ||    || listresources says "500 Internal Server Error". ||
+|| Rutgers      || 2011-05-02     || CT || AM || CA || LR ||    ||    ||    ||    ||    || Need info about which ports have the plnodes and cross-connects. ||
 || Washington   || 2011-05-02     || CT || AM || CA || LR || RS || SL || FV || NT || XT || Fully armed and operational. ||
 || Wisconsin    || 2011-05-02     || CT || AM || CA || LR || RS || SL || FV || NT || XT || Fully armed and operational. ||
@@ -36 +36 @@
 Assuming the MyPLC plnodes are all up and running, here are the commands that Josh has been using to test inter-campus connections. ('shmux' is a utility for running a command on multiple remote hosts, and aggregating the output)
 
-Set $net and $slicename to control which slice and network you want to test:
+For any of these tests, set $net and $slicename to control which slice and subnet you want to test:
 
 {{{
-net=101
-username=pgenigpolabbbncom_plastic$net
+subnet=101
+username=pgenigpolabbbncom_plastic$subnet
 }}}
 
-Test everything:
+These tests rely on ping having a non-zero exit status when it gets a 100% failure rate. It's not clear from the man page what the exit status is when ''some'' packets are received.
+
+These tests will produce some failures for slices that don't include every campus, of course. plastic-101 and plastic-102 include every campus; the former uses VLAN 3715 and the latter VLAN 3716, so they're likely candidates for basic connectivity testing.
+
+== Test anything ==
+
+This tests only that each of the BBN MyPLC plnode can reach the others on a subnet, which is a useful way to tell if anything at all is working on that subnet.
 
 {{{
-for i in {51..55} {72..73} {80..81} {90..93} {95..96} {104..105} ; do ipaddr=10.42.$net.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" $username@plnode{1..5}-myplc.gpolab.bbn.com ; done
-for i in {51..55} {72..73} {80..81} {90..93} {95..96} {104..105} ; do ipaddr=10.42.$net.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" $username@planetlab{4,5}.clemson.edu ; done
-for i in {51..55} {72..73} {80..81} {90..93} {95..96} {104..105} ; do ipaddr=10.42.$net.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" $username@pl{4,5}.myplc.grnoc.iu.edu ; done
-for i in {51..55} {72..73} {80..81} {90..93} {95..96} {104..105} ; do ipaddr=10.42.$net.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" $username@of-planet{1..4}.stanford.edu ; done
-for i in {51..55} {72..73} {80..81} {90..93} {95..96} {104..105} ; do ipaddr=10.42.$net.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" $username@wings-openflow-{2,3}.wail.wisc.edu ; done
-for i in {51..55} {72..73} {80..81} {90..93} {95..96} {104..105} ; do ipaddr=10.42.$net.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" $username@pl0{1,2}.cs.washington.edu ; done
+for i in {51..55} ; do ipaddr=10.42.$subnet.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" $username@plnode{1..5}-myplc.gpolab.bbn.com ; done
 }}}
 
-This relies on ping having a non-zero exit status when it gets a 100% failure rate. It's not clear from the man page what the exit status is when ''some'' packets are received.
+== Test everything ==
+
+Each of these lines tries to ping every known IP address on the subnet, from each of the MyPLC plnodes at one of the sites.
+
+{{{
+for i in {51..55} {72..73} {80..81} {90..93} {95..96} {104..105} ; do ipaddr=10.42.$subnet.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" $username@plnode{1..5}-myplc.gpolab.bbn.com ; done
+for i in {51..55} {72..73} {80..81} {90..93} {95..96} {104..105} ; do ipaddr=10.42.$subnet.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" $username@planetlab{4,5}.clemson.edu ; done
+for i in {51..55} {72..73} {80..81} {90..93} {95..96} {104..105} ; do ipaddr=10.42.$subnet.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" $username@pl{4,5}.myplc.grnoc.iu.edu ; done
+for i in {51..55} {72..73} {80..81} {90..93} {95..96} {104..105} ; do ipaddr=10.42.$subnet.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" $username@of-planet{1..4}.stanford.edu ; done
+for i in {51..55} {72..73} {80..81} {90..93} {95..96} {104..105} ; do ipaddr=10.42.$subnet.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" $username@wings-openflow-{2,3}.wail.wisc.edu ; done
+for i in {51..55} {72..73} {80..81} {90..93} {95..96} {104..105} ; do ipaddr=10.42.$subnet.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" $username@pl0{1,2}.cs.washington.edu ; done
+}}}
+
+== Results ==
 
 Failures look like this:
@@ -68 +82 @@
 }}}
 
-This indicates that the Clemson hosts couldn't ping 10.42.101.95. (In this case, they didn't yet have the static ARP entries for the Wisconsin hosts.)
+This indicates that the Clemson hosts couldn't ping 10.42.101.95. (At the time we generated this error, this was because they didn't yet have the static ARP entries for the Wisconsin hosts.)