Changes between Version 7 and Version 8 of Old/OTG/FAQ


Ignore:
Timestamp:
Nov 2, 2005, 10:57:28 PM (19 years ago)
Author:
zhibinwu
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Old/OTG/FAQ

    v7 v8  
    2020apt-get install otg
    2121}}}
     22
    2223three binary files "otg" "otr", "otf" will be copied to /usr/local/bin directory.
    2324
     
    3738doxygen otgdoc.cfg
    3839}}}
    39 Note: If Doxygen generates contradictory descriptions against Fucntion Specification, Function Sepcifiactions take precedence.
     40Note: If Doxygen generates contradictory descriptions against Function Specification, Function Specifications take precedence.
    4041 
    4142=== What is OTF? ===
     
    4748=== Why I have to write nodeHandler scripts to use OTG? ===
    4849
    49 Basically, NodeHandler is a comprehensive tool to control the whole experiment in Orbit Testbed, including the functuons to power on/off nodes, setup/break wired/wireless links. As OTG software can be used to test a link only after the link is eatablished, it is not a bad idea to use "nodehandler"  to give command-line and run-time options for OTG/OTR program too. Therefore, the nodehandler script will include all necessary information to start, stop and control OTG programs. Users will no longer need to input command line arguments manually.  What's more, with this, users do not need to SSH to everynode and run the OTG program one by one manually if an experiment involves a large number of nodes.
     50Basically, NodeHandler is a comprehensive tool to control the whole experiment in Orbit Testbed, including the functions to power on/off nodes, setup/break wired/wireless links. As OTG software can be used to test a link only after the link is eatablished, it is not a bad idea to use "nodehandler"  to give command-line and run-time options for OTG/OTR program too. Therefore, the nodehandler script will include all necessary information to start, stop and control OTG programs. Users will no longer need to input command line arguments manually.  What's more, with this, users do not need to SSH to every node and run the OTG program one by one manually if an experiment involves a large number of nodes.
    5051
    5152=== When using nodehandler, where can I find the outputs of OTG/OTR during the experiment? ===
     
    8182
    8283you can check if the otg.rb already list "port" as a property or not? If yes, then go to sender.rb to see if
    83 the "port" property is binded to the sender object or not?
     84the "port" property is bind to the sender object or not?
    8485if both are done, you can configure this property as same as other property in your experiment script.
    8586
    8687== Trouble shouting ==
    8788=== why the OML database for my experiment has empty tables (0 records)? ===
    88 The OTG/OTR is only used to test link performance. The user has to ensure the link availabilty before running OTG/OTR programs. One plausible reason for empty table is the link does not exists at all (wrong channel setting, cell id mismatch...). This is surprisingly frequent in wireless tests. Check your experiment scripts carefully.
     89The OTG/OTR is only used to test link performance. The user has to ensure the link availability before running OTG/OTR programs. One plausible reason for empty table is the link does not exists at all (wrong channel setting, cell id mismatch...). This is surprisingly frequent in wireless tests. Check your experiment scripts carefully.
    8990
    9091=== Why I get "bind error" when starting otg/otr? ===
    9192Be sure a port in one machine can only used by one program. If you run multiple OTG programs in one machine, use different "--port" settings.
    9293
     94=== Why during the experiment, OTG offerload suddenly drops to zero, till the end of experiment? ===
    9395
    94 === Why I get an "rx_timestamp" earler than "tx_timestamp" ? ===
    95 Timestamp shows the time offset since the program is started.
    96 If you start OTR later than OTG, it is possible to see a smaller rx_timestamp than tx_timestamp.
    97 
    98 
    99 
    100 
    101 
     96The problem is that the sender failed to continue sending any packets out due to a driver issue. It often happened when sender tries to push offered load which is higher than the actual wireless link capacity. This problem is usually seen in Atheros card.