Changes between Version 15 and Version 16 of GEC20Agenda/LabWiki/ModuleE/Execute


Ignore:
Timestamp:
08/04/14 11:27:51 (5 years ago)
Author:
dbhat@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC20Agenda/LabWiki/ModuleE/Execute

    v15 v16  
    1717==== 3.1.2a. Start Trema controllers on the two switch nodes in the topology shown in [http://groups.geni.net/geni/wiki/GEC20Agenda/LabWiki/ModuleC/DesignSetup ModuleC] ====
    1818
    19 Show in [http://groups.geni.net/geni/wiki/GEC20Agenda/LabWiki/ModuleC/DesignSetup ModuleC]
     19Shown in [http://groups.geni.net/geni/wiki/GEC20Agenda/LabWiki/ModuleC/DesignSetup ModuleC]. If you have run Module C before this, your controllers are already running and there is no need to do this step.
    2020
    2121==== 3.1.2b. Start an Iperf server on nodef ====
    2222
    2323{{{
     24#!ruby
    2425defApplication('iperfserv') do |app|
    2526  app.description = "manually run Iperf server"
     
    3738
    3839{{{
     40#!ruby
    3941defApplication('iperfclient') do |app|
    4042  app.description = "manually run Iperf client"
     
    5355OEDL script
    5456{{{
    55 
     57#!ruby
    5658defProperty('source1', "switch1-egtest7", "ID of a resource")
    5759defProperty('theSender1', "nodeb-egtest7", "ID of a resource")
     
    168170That will automatically fill out the experiment relevant information in this window and allow you to start the actual experiment by clicking on the "Start Experiment" button.
    169171
    170 [[Image(LW_wiki_flowstats1.png, 90%)]]
     172[[Image(LW_wiki_flowstats1.png, 60%)]]
    171173
    172174Explanation of the fields in the Execute window:
     
    185187The figure below gives an example for the Execute window during experiment execution.
    186188
    187 [[Image(LW_wiki_flowstats2.png, 90%)]]
     189[[Image(LW_wiki_flowstats2.png, 60%)]]
    188190
    189191Now the window lists experiment properties, one or several live graphs (if they have been specified in the OEDL script), and logging information. The latter would be a good starting point for trouble shooting, should your experiment not run as expected.