Changes between Version 89 and Version 90 of Documentation/FAQ


Ignore:
Timestamp:
Jan 11, 2013, 10:58:25 PM (12 years ago)
Author:
ssugrim
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Documentation/FAQ

    v89 v90  
    149149----------------------------------------
    150150
    151 Yes. Each of the radio nodes has its own serial console with which you can interact through the chasis manager (CM).  From the experiment console machine, telnet 10.1.X.Y 3025 in the case of the grid, and telnet 10.1.10N.XXXXYYYY 3025 in the case of the sandbox where N is the sandbox number.
    152 
    153 For e.g.
    154 
    155 Sandbox 1 (node1-1) - telnet 10.1.101.17 3025, (node1-2) - telnet 10.1.101.18 3025
    156 
    157 Sandbox 2 (node1-1) - telnet 10.1.102.17 3025, (node1-2) - telnet 10.1.102.18 3025
    158 
    159 Sandbox 5 (node1-1) - telnet 10.1.105.17 3025, (node1-2) - telnet 10.1.105.18 3025
     151Yes. Each of the radio nodes has its own serial console with which you can interact through the chasis manager (CM).  The interaction method is different for the the different versions of CM. For newer versions of CM (3 and older) you can telnet directly to the CM and you will be connected to the serial console. For the older versions your telnet session must connect to port 3025. The CM's are named consX-Y.domain, where X,Y are the "coordinates" of the node you are trying to reach, and domain is the resource you reserved (ie. grid, sandbox1, etc..)
     152
     153Examples:.
     154
     155Sandbox 1 (node1-1) - telnet cons1-1.sb1.orbit-lab.org 3025 - Serial console of node1-1
     156
     157Sandbox 5 (node1-1) - telnet cons1-1.sb5.orbit-lab.org - Serial console of node1-1
     158
     159grid  (node1-1) - telnet cons1-1.grid.orbit-lab.org - Serial console of node1-1
    160160
    161161The nodes must be turned on in order to be able to telnet.
    … …  
    166166Yes. Each of the radio nodes is independently power controlled by the chassis manager. If your node hangs, or is otherwise unresponsive, you can reboot it.  The preferable way to do perform such operations is given here `Tutorial/HowToSwitch`:trac:.
    167167
    168 An obsolete way is to, from the console machine, execute wget -0 - http://repository:5012/cmc/ and use the XML interface to modify the state of your node.
    169 for example, power on node 4,4 with command: wget -O - -q 'http://cmc:5012/cmc/on?x=4&y=4' or  wget -O - "http://cmc:5012/cmc/nodeSetOn?nodes=[4,4..6]"
    170 
    171 
    172168Is the ORBIT testbed firewalled?
    173169--------------------------------
    174170
    175 Yes.  The nodes do not have direct access to the Internet.  However, the machine used for initial login, "gateway.orbit-lab.org", does.  Recently, we also opened up the consoles for direct access from outside. e.g in order to access console for sandbox2, use '''ssh user@console.sb2.orbit-lab.org'''. Since your home directory on gateway is also accessible via the testbed consoles, it is possible to upload and download from the Internet on "gateway.orbit-lab.org" and copy files to your nodes from the testbed console.
     171Yes.  The nodes do not have direct access to the Internet.  However, the machine used for initial login, "gateway.orbit-lab.org", does.  The consoles are also open for direct access from outside. e.g in order to access console for sandbox2, use '''ssh user@console.sb2.orbit-lab.org'''. Since your home directory on gateway is also accessible via the testbed consoles, it is possible to upload and download from the Internet on "gateway.orbit-lab.org" and copy files to your nodes from the testbed console.
    176172
    177173
    … …  
    188184---------------------------------------
    189185
    190 There are two mini-PCI 802.11 a/b/g interfaces cards on each node. In addition to that, there will be USB-based Bluetooth and Zygbee interfaces.
     186There are two mini-PCI 802.11 a/b/g interfaces cards on each node. In addition to that there are many USB-based Bluetooth, Zygbee and other interfaces. See the Status page for a complete list.
    191187
    192188
    … …  
    198194For the main grid, check `IntelNodes`:trac:.
    199195
    200 Which is ath0?
    201 --------------
    202 Looking at the back of the node, the interface opposite the power supply is ath0.
    203 
    204196Software Questions
    205197===================
    … …  
    207199What OS do the nodes run?
    208200-------------------------           
    209 The default Operating Systems that run on each of the radio nodes is Debian GNU/Linux with the 2.6 kernel. But every experimenter can load any OS they want.
     201The default Operating Systems that run on each of the radio nodes is Ubuntu 12.04 (from the baseline image). But every experimenter can load any OS they want.
    210202
    211203
    … …  
    235227-------------------------------------------------------
    236228
    237 Yes. We provide packages mainly for GNU/Debian Linux, but sources are also available that should compile on most distributions.
     229Yes. We provide packages mainly for GNU/Ubuntu Linux, but sources are also available that should compile on most distributions.
    238230
    239231
    … …  
    242234
    243235If you've modified the baseline, or even installed your own OS on a node, you can take a snapshot of the node's disk.  The resulting image can be used on other nodes during your experiment and reused during other slots.  To save a node's disk as an image issue the following command on the experiment console (**NOT THE NODE'S SERIAL CONSOLE**):
    244  * saveNode x,y
    245 
    246 where x and y are the node's coordinates.  The image will be named in the form node-X-Y-<TIMESTAMP>.ndz and will be displayed in a status message during runtime.  Please keep track of the image name as you will need to supply it during imaging.
    247 
    248 ORBIT keeps your images on the machine named repository2 in the /export/orbit/image/tmp directory. They are considered temporary images unless you claim them by moving them to image repository with:
    249 
    250  * mv node-X-Y-<TIMESTAMP>.ndz ../your-active-image-name.ndz
     236{{{
     237   user@console.domain: omf save -n nodeX-Y.domain
     238}}}
     239
     240where X and Y are the node's coordinates.  The image will be named in the form username-node-fqdn-date.ndz and will be displayed in a status message during the save process.  Please keep track of the image name as you will need to supply it during imaging.
     241
     242ORBIT keeps your images on the machine named repository1 in the /export/omf/omf-images directory. They are considered temporary images unless you claim them by moving them to image repository with:
     243{{{
     244mv username-node-fqdn-date.ndz ../your-active-image-name.ndz
     245}}}
    251246
    252247Please bear in mind that the ORBIT software components (i.e. nodehandler/nodeagent, libmac, otr/otg, oml, and wireless drivers) are under constant development.  The baseline image is continually updated with the latest stable releases of these components.  If you are going to use your own derivative of the baseline and you use these components, may need to update these packages manually.  Please watch the orbit-user mail list for development related news.
    … …  
    257252
    258253You can image the nodes you need with your image using the following command from the "console" machine
    259  * imageNodes [x1,y1],[x2,y2] tmp/name_of_your_image.ndz
     254{{{
     255   user@console.domain: omf load -t topology -i imagename.ndz
     256}}}
     257
     258Loading images is covered the the tutorial on node images located ...
    260259
    261260How many images can I have? Do they get purged?