Changes between Version 7 and Version 8 of PlasticSlices/OFStatus
- Timestamp:
- 04/29/11 12:43:00 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PlasticSlices/OFStatus
v7 v8 1 [[PageOutline]] 2 1 3 The [wiki:PlasticSlices/ProjectPlan Plastic Slices project plan] calls for each [wiki:PlasticSlices/ProjectPlan#a4.2.1.Campuses campus] to "Configure a local !OpenFlow network consistent with the recommended [wiki:OpenFlow/CampusTopology campus topology], connected to the [wiki:NetworkCore GENI network core]." and "Provide a GENI AM API compliant Expedient aggregate managing the !OpenFlow network connecting the MyPLC hosts to the GENI network core.", and for [wiki:PlasticSlices/ProjectPlan#a4.2.2.Internet2andNLR Internet2 and NLR] to "Provide an Expedient aggregate managing the !OpenFlow resources in the Internet2 portion of the GENI network core." 4 5 = Status = 2 6 3 7 This table is tracking the status of those items, divided by deadline. … … 13 17 || Rutgers || 2011-05-02 || || || || || || || || || || listresources says "500 Internal Server Error"; they're working on topology. || 14 18 || Washington || 2011-05-02 || CT || AM || CA || LR || || || || || || Vjeko is making intercampus VLANs non-OF controlled. || 15 || Wisconsin || 2011-05-02 || CT || AM || CA || LR || RS || SL || FV || || || Testing internally now. ||19 || Wisconsin || 2011-05-02 || CT || AM || CA || LR || RS || SL || FV || NT || XT || Fully armed and operational. || 16 20 || || || || || || || || || || || || || 17 21 || GT || 2011-05-09 || || || || || || || || || || Haven't tried yet. || … … 27 31 * NT: internally tested within a site 28 32 * XT: externally tested with other sites 33 34 = Testing = 35 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) 37 38 {{{ 39 for i in {51..55} {95..96} {104..105} ; do ipaddr=10.42.101.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" pgenigpolabbbncom_jbstest@{ganel,gardil,sardis,navis,bain} ; done 40 for i in {51..55} {95..96} {104..105} ; do ipaddr=10.42.101.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" pgenigpolabbbncom_jbstest@planetlab{4,5}.clemson.edu ; done 41 for i in {51..55} {95..96} {104..105} ; do ipaddr=10.42.101.$i ; echo -e "\n--> $ipaddr" ; shmux -c "ping -c 3 $ipaddr > /dev/null" pgenigpolabbbncom_jbstest@wings-openflow-{2,3}.wail.wisc.edu ; done 42 }}} 43 44 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. 45 46 Failures look like this: 47 48 {{{ 49 --> 10.42.101.95 50 shmux! Child for pgenigpolabbbncom_jbstest@planetlab4.clemson.edu exited with status 1 51 shmux! Child for pgenigpolabbbncom_jbstest@planetlab5.clemson.edu exited with status 1 52 53 2 targets processed in 4 seconds. 54 Summary: 2 errors 55 Error : pgenigpolabbbncom_jbstest@planetlab4.clemson.edu pgenigpolabbbncom_jbstest@planetlab5.clemson.edu 56 }}} 57 58 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.)