faq.html 75.1 KB
Newer Older
Leigh B. Stoller's avatar
Leigh B. Stoller committed
1 2
<!--
   EMULAB-COPYRIGHT
3
   Copyright (c) 2000-2004 University of Utah and the Flux Group.
Leigh B. Stoller's avatar
Leigh B. Stoller committed
4 5
   All rights reserved.
  -->
6
<center>
7
<h2>Frequently Asked Questions</h2>
8 9 10
</center>

<h2>Contents</h2>
11
<ul>
12 13
<li> <a href="#GS">Getting Started</a>
     <ul>
14
     <li> <a href="#GS-Eligible">Who is Eligible to use Emulab.Net?</a>
15 16
     <li> <a href="#GS-1">How do I start a project?</a>
     <li> <a href="#GS-2">How do I join a project?</a>
17 18 19 20
     <li> <a href="#GS-2b">I'm a project leader, and someone applied
	                   to join my project, but they're not on the 
	                   list to be approved.</a>
     <li> <a href="#GS-2c">Will Emulab send me email messages?</a>
21
     <li> <a href="#GS-3">I have an Emulab account. Now what?</a>
22
     <li> <a href="#GS-PATH">Do I need to change my PATH variable?</a>
23 24
     <li> <a href="#GS-4">Can I be in more than one project?</a>
     <li> <a href="#GS-5">Can I change my Emulab password?</a>
25
     <li> <a href="#GS-6">I'm a project leader. Can I designate TAs?</a>
26 27
     <li> <a href="#GS-7a">How do I report a specific problem?</a>
     <li> <a href="#GS-7">Where do I get more help?</a>
28 29 30 31 32
     </ul>

<li> <a href="#UTT">Using the Testbed</a>
     <ul>
     <li> <a href="#UTT-1">Is there a tutorial?</a>
33 34
     <li> <a href="#UTT-NETBUILD">Do you have a <b>GUI</b> to help me
                                   create experiments?</a>
35
     <li> <a href="#UTT-TOPO">Are there any constraints on my topology?</a>
36
     <li> <a href="#UTT-NODES">How many nodes can I ask for?</a>
37
     <li> <a href="#UTT-HOWLONG">How long can I keep using my nodes?</a>
38 39
     <li> <a href="#UTT-QUEUE">I only need a couple of nodes but none are
     				free, should I just keep trying?</a>
40
     <li> <a href="#UTT-TOOFEW">What if I need more nodes than are free?</a>
41
     <li> <a href="#UTT-2">Do I get root access on my nodes?</a>
42
     <li> <a href="#UTT-3">Do my nodes have consoles I can look at?</a>
Chad Barb's avatar
Chad Barb committed
43 44
     <li> <a href="#UTT-TUNNEL">How do I connect directly to node consoles, 
                                without going through <b>users</b>?</a>
45
     <li> <a href="#UTT-4">Can I reboot (power cycle) my nodes?</a>
46
     <li> <a href="#UTT-SCROGGED">I've clobbered my disk! Now what?</a>
47 48
     <li> <a href="#UTT-5">Where do I store files needed by my experiment?</a>
     <li> <a href="#UTT-6">Are my files on <b>users.emulab.net</b>
49
                           backed up (filesaved)?</a>
50
     <li> <a href="#UTT-7">Are the nodes in my experiment backed up
51
                           (filesaved)?</a> 
52
     <li> <a href="#UTT-Swapping">What is Swapping?</a> 
53
     <li> <a href="#UTT-Restart">What is Experiment Restart?</a> 
Robert Ricci's avatar
Robert Ricci committed
54 55
     <li> <a href="#UTT-8">How can I get switch statistics (such as packet
                           counts) for my experiment?</a> 
56 57
     <li> <a href="#UTT-Naming">What names should I use to refer to the
			   nodes in my experiment?</a>
Chad Barb's avatar
 
Chad Barb committed
58 59
     <li> <a href="#UTT-Modify">Can I modify my experiment 
                           after creating it?</a> 
60 61
     <li> <a href="#UTT-SWPaths">Are there FreeBSD and/or Linux sources and 
                           packages available locally?</a>
62 63 64 65 66
     </ul>

<li> <a href="#HDS">Hardware setup</a>
     <ul>
     <li> <a href="#HDS-1">How many nodes are there?</a>
67 68
     <li> <a href="#HDS-2">How many nodes are currently available?</a>
     <li> <a href="#HDS-3">How many ethernet cards are on each node?</a>
69
     <li> <a href="#HDS-8">How do I ask for specific hardware?</a>
70 71
     <li> <a href="#HDS-4">How many nodes are currently available (free)?</a>
     <li> <a href="#HDS-5">Can I do traffic shaping on my links?</a>
Jay Lepreau's avatar
Jay Lepreau committed
72
     <li> <a href="#HDS-6">Can I modify the traffic shaping
73
                           parameters on my links?</a>
Jay Lepreau's avatar
Jay Lepreau committed
74
     <li> <a href="#HDS-7">Are there other traffic shaping parameters
75
                           besides latency, bandwidth, and PLR?</a>
76 77 78 79 80
     </ul>

<li> <a href="#SWS">Software setup</a>
     <ul>
     <li> <a href="#SWS-1">What OS do the nodes run?</a>
81
     <li> <a href="#SWS-2">How do I select which OS to run on each node?</a>
Leigh B. Stoller's avatar
Leigh B. Stoller committed
82 83
     <li> <a href="#SWS-3">Can I load my own software (RPMs/Tarballs)
			     on my nodes?</a> 
84
     <li> <a href="#SWS-4">Can I schedule programs to run
85 86 87 88
                           automatically when a node boots?</a>
     <li> <a href="#SWS-5">How can I turn on routing or set up routes
			   automatically in my nodes?</a>
     <li> <a href="#SWS-6">How does my software determine when other
89
                           nodes in my experiment are ready?</a>
90
     <li> <a href="#SWS-7">Can I run my own Operating System?</a>
91 92
     <li> <a href="#MovingImage">Can I share a disk image between two
                           projects?</a>
93
     <li> <a href="#SWS-8">What if I need more disk space on my nodes?</a>
94 95
     <li> <a href="#SWS-9">Are there testbed-specific daemons that could
                           interfere with my experiment?</a>
Mac Newbold's avatar
Mac Newbold committed
96
     <li> <a href="#SWS-10">Does Emulab support IP Multicast?</a>
97
     </ul>
98 99 100 101 102

<li> <a href="#SEC">Security Issues</a>
     <ul>
     <li> <a href="#SEC-1">Is Emulab Firewalled?</a>
     </ul>
103 104 105

<li> <a href="#TR">Troubleshooting</a>
     <ul>
106
     <li> <a href="#TR-0">My experiment setup failed, what did I do wrong?</a>
107
     <li> <a href="#TR-1">My experiment is set up, but I cannot
108 109 110 111 112 113 114 115
     			  send packets between some of the nodes. Why?</a>
     <li> <a href="#TR-2">I asked for traffic shaping, but everything
			  seems to be going at full LAN speeds. 
			  What's wrong?</a>
     <li> <a href="#TR-3">I set a non-zero packet-loss (or delay) but 'ping'
                          shows no packet-loss (or delay). Why?</a>
     <li> <a href="#TR-4">I set a non-zero packet-loss (or delay) but 'ping'
                          shows a different packet-loss (or delay). Why?</a>
116 117
     <li> <a href="#TR-5">I decreased the bandwidth on a link and now the
                          ping time between the nodes has increased. Why?</a>
118 119 120
     <li> <a href="#TR-6">I wrote a small TCP application to test the
     bandwidth of a link/LAN. I do not observe the bandwidth that I
     asked for. Why?</a>
121 122 123
     <li> <a href="#TR-6b">I wrote a small UDP application to test the
     bandwidth of a link/LAN. I do not observe the bandwidth that I
     asked for. Why?</a>
124 125
     <li> <a href="#TR-7">I am running a routing daemon in my topology
     but the daemon claims that all my nodes are directly connected! Why?</a>
126
     </ul>
127 128 129
</ul>

<hr>
130

131
<a NAME="GS"></a>
Chad Barb's avatar
 
Chad Barb committed
132
<font size='+1'><b>Getting Started</b></font>
133
<ul>
134
<li><a NAME="GS-Eligible"></a>
Chad Barb's avatar
 
Chad Barb committed
135
    <font size='+1'><b>Who is Eligible to use Emulab.Net?</b></font>
136
    <p>
137 138 139 140 141 142 143 144
    In principle, almost any research or educational use
    by those that have a need for it is appropriate and encouraged.
    This includes use by universities, industrial research labs, and both
    US and non-US institutions.   With some provisos, use for development
    and evaluation is also acceptable, even by companies.
    See our <a href ="docwrapper.php3?docname=policies.html">posted policies</a>
    for more detail.  If you are unsure about your eligibility to use
    Netbed/Emulab, please just send us an email inquiry.
145 146
    </p>

147
<li><a NAME="GS-1"></a>
Chad Barb's avatar
 
Chad Barb committed
148
    <font size='+1'><b>How do I start a project?</b></font>
149 150
    <p>
    If you are new to the Testbed, simply click on the "Start Project"
151
    link on the Emulab <a href="http://www.emulab.net">Home
152 153 154 155
    Page</a>. You will need to fill in the forms with your personal
    information and information about the project. Then click on the
    "Submit" button. Within a few days you will be contacted via email
    with an approval message. More information about starting projects
156 157
    can be found in <a href="docwrapper.php3?docname=auth.html">
    Authorization Page</a>.
158
    </p>
159 160 161 162 163 164 165
    <p>
    If you already have an Emulab account, and wish to start a second
    project, first log into the Web Interface. Then select the "Start
    Project" link; all of the personal information will already be
    filled in. You will need to complete just the project information
    section. 
    </p>
166

167
<li><a NAME="GS-2"></a>
Chad Barb's avatar
 
Chad Barb committed
168
    <font size='+1'><b>How do I join a project?</b></font>
169 170
    <p>
    If you are new to the Testbed, simply click on the "Join Project"
171
    link on the Emulab <a href="http://www.emulab.net">Home
172 173 174
    Page</a>. You will need to fill in the form with your personal
    information, and provide the name of the project you are trying to
    join (typically, the <i>Project Leader</i> will have told you the
175
    name of the project). Then click on the "Submit" button, and wait
176 177 178
    for an email with your new user key. When that email arrives, use
    the link in it (or the key itself), and use it with your password 
    to log into the web site and verify your account. Then just wait
179 180 181
    for the project leader to approve you.  When approved you will
    receive an email message saying so, and you can then log into the
    Testbed.
182 183
    </p>

184
<li><a NAME="GS-2b"></a>
Chad Barb's avatar
 
Chad Barb committed
185 186 187
    <font size='+1'><b>I'm a project leader, 
    and someone applied to join my project,
    but they're not on the list to be approved.</b></font>    
188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206
    <p>
      Joining a project has 3 stages. The first two are done by
      the person trying to join, and they both must be completed
      before you can approve their application. The first two are
      outlined <a href="#GS-2">in the previous question</a>, where the
      user fills out the "Join Project" form, and performs account
      verification. After these two steps are both complete, the
      project leader and any group leaders in the group 
      (<a href="#GS-6">More info here</a>) will get an email saying
      the account is ready to be approved, and it will appear on the
      list of new users waiting to be approved.
    <p>
      If someone says they've applied, but you haven't received an
      email from Emulab about it, and they don't show up on your
      list, the most likely cause is that they haven't finished the
      verification step.
    </p>

<li><a NAME="GS-2c"></a>
Chad Barb's avatar
 
Chad Barb committed
207
    <font size='+1'><b>Will Emulab send me email messages?</b></font>
208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236
    <p>
      Yes! Emulab uses email notifications to you in several different
      ways. Often it will send you a copy of information regarding
      experiments you set up, applications to projects, and other
      things you do at Emulab. Sometimes (like with account
      verification) the email is a critical part of being able to use
      Emulab.
    <p>
      For those reasons it is <b>critical</b> that any spam filtering
      software you have accept email from Emulab itself (anything
      coming from the emulab.net domain) and from Emulab staff (from
      the cs.utah.edu or flux.utah.edu domains). In many cases, it may
      also say that is from a specific machine in those domains. Our
      messages usually do not get flagged as spam by most filters, but
      in certain cases it can be a problem. It is also important that
      it not require manual intervention or confirmation to get emails
      through to you, so programs like SpamKiller can cause problems.
    <p>
      It is also important to read your email often while you are
      using Emulab, especially while you have machines reserved in 
      an experiment. A few emails may be the only notification you'll
      get before we swap out an experiment that appears to be idle,
      and if you don't respond, you may lose important work. Email is
      also our method for informing you about problems we may be
      experiencing, downtimes, or other important announcements. Your
      experience with Emulab (and ours with you) will be much more
      pleasant if everyone is responsive to email.
    </p>

237
<li><a NAME="GS-3"></a>
Chad Barb's avatar
 
Chad Barb committed
238
    <font size='+1'><b>I have an Emulab account. Now what?</b></font>
239 240 241 242 243 244
    <p>
    Once you have been approved to start (or join) your first project,
    you will be able to log into Emulab's user machine,
    <b>users.emulab.net</b>. We require that all Emulab users use ssh. For
    example, if your Emulab account name is "joe", then you would do:
    <pre>
245
	ssh users.emulab.net -l joe		</pre>
246 247
    </p>
    <p>
248 249
    Your password is the same as the password you supplied to the
    Start (or Join) Project web page.
250 251

<li><a NAME="GS-PATH"></a>
Chad Barb's avatar
 
Chad Barb committed
252 253
    <font size='+1'><b>Do I need any 
    special directories in my PATH variable?</b></font>
254 255 256 257
    <p>
    There are several useful (although not required) programs installed on
    <tt>users.emulab.net</tt> in <tt>/usr/testbed/bin</tt>. You should edit
    your dot files to include that directory in your search path. 
258 259 260
    </p>

<li><a NAME="GS-4"></a>
Chad Barb's avatar
 
Chad Barb committed
261
    <font size='+1'><b>Can I be in more than one project?</b></font>
262 263
    <p>
    Yes. You may join (and/or start) as many projects as you like,
264 265
    subject to Emulab <a href="docwrapper.php3?docname=policies.html">
    administrative policies</a>.
266 267 268
    </p>

<li><a NAME="GS-5"></a>
Chad Barb's avatar
 
Chad Barb committed
269
    <font size='+1'><b>Can I change my Emulab password?</b></font>
270 271 272
    <p>
    Yes. You can change your Emulab Web password and your Emulab login
    password (the password you use to log into <b>users.emulab.net</b>, as
273
    well as nodes in your experiments). To change your password,
274
    simply click on the "Update User Information" in the menu to your
275 276 277 278
    left, and then enter your new password in the location provided.
    Your new password will be installed on <b>users.emulab.net</b>
    immediately. Your experimental nodes will get the new password
    when they reboot.
279 280 281
    </p>

<li><a NAME="GS-6"></a>
Chad Barb's avatar
 
Chad Barb committed
282
    <font size='+1'><b>I'm a project leader. Can I designate TAs?</b></font>
283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310
    <p>
    Yes. To designate a TA, you must first create a project
    <em>group</em>. A project group is a lot like a unix group, and
    in fact unix groups is the mechanism used to protect members of
    one group from members of another group. When you create a group,
    you designate a <em>group leader</em> who is responsible for
    approving users who apply to join the group. Group leaders may
    also terminate experiments that have been created by members of
    the group. As Project Leader, you may also shift members of your
    project in and out of your project's groups as you like, and you
    are automatically a member of all groups within your project. As a
    convenience, all new projects are created with one new group,
    termed the <em>default group</em>. As its name implies, whenever
    the group is left unspecified in a form, it defaults to the
    project group (this allows you to create a project without any sub
    groups at all; new members join the default group, new experiments
    are created in the default group, etc.).
    </p>

    <p>
    Project groups are created via the Project Information link at
    your left. Simply go to the project page in which you want to
    create a group, and look for the "Create New Group" link. More
    information on project groups is available via the <a
    href="doc.php3">Emulab Documentation</a> page in the
    <a href="docwrapper.php3?docname=groups.html">Groups Tutorial</a>.
    </p>

311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342
<li><a NAME="GS-7a"></a>
    <font size='+1'><b>How do I report a specific problem?</b></font>
    <p>
    Don't hesitate to send us <a href="emailus.php3">email</a>!
    <p>
    Ok, hesitate just a little and read the rest of this entry first.
    Before sending email, be sure to check out the
    <a href="#TR">Troubleshooting</a>
    entry which describes several common problems and possible causes.
    If you do send email, there are several pieces of information you
    should include to make our job easier.
    <ul>
    <li> The affected <b>project and experiment name</b> is pretty obvious,
    but some people forget.
    <li> The particular <b>nodes, OSes, and programs</b>
    involved will help us zero in on the problem more quickly.
    <li> The <b>time</b> at which the problem occurred.
    We need this to correlate with our various log files.
    <li> Any <b>relevant observations and actions</b> you have attempted.
    Did the problem only happen once?  Is it reproducible?  Did restarting
    a program or rebooting a node help?
    </ul>
    After sending email,
    <em>please do not swap or terminate the experiment</em>, if possible.
    It can be a lot harder to track down a problem after the experiment
    is gone.  Sometime you may need to terminate it, for example it is
    in the middle of the night our time and you really need the nodes
    that are tied up in the experiment.  But at least give us 15 minutes
    to respond to your message before acting, and then let us know that
    you did swap/terminate it.
    </p>

343
<li><a NAME="GS-7"></a>
344
    <font size='+1'><b>Where do I get more help?</b></font>
345 346
    <p>
    If you cannot find an answer to your question in the
347
    <a href="doc.php3">Emulab Documentation</a>, then you can
348
    send us an <a href="emailus.php3">email message</a>. We will try
349 350
    to answer your question as quickly as we can.
    </p>
351
</ul>
352

Leigh B. Stoller's avatar
Leigh B. Stoller committed
353
<hr>
354 355

<a NAME="UTT"></a>
Chad Barb's avatar
 
Chad Barb committed
356
<font size='+1'><b>Using the Testbed</b></font>
357 358
<ul>
<li><a NAME="UTT-1"></a>
Chad Barb's avatar
 
Chad Barb committed
359
    <font size='+1'><b>Is there a tutorial?</b></font>
360
    <p>
361
    Yes, we have an extensive <a href="tutorial/tutorial.php3">tutorial</a>
362 363 364
    on using the Testbed.
    </p>

Chad Barb's avatar
Chad Barb committed
365
<li><a NAME="UTT-NETBUILD"></a>
Chad Barb's avatar
 
Chad Barb committed
366 367
    <font size='+1'><b>Do you have a GUI to 
    help me create experiments?</b></font>
368 369 370 371 372 373 374 375 376 377 378 379 380 381
    <p>
    Yes, we provide a GUI that gives you an easy to use drawing
    palette on which you can place nodes, lans, and links. Testbed
    specific attributes such as operating system, hardware type, and
    link/lan characteristics, may be attached to each object. With a
    single click, you can instantiate your new topology on the Testbed
    as an experiment in one of your projects. Alternatively, you can
    save the auto-generated NS file on your machine, edit as required,
    and then submit it later when creating an experiment.
    </p>
    
    <p>
    To access the GUI, please log in and go to the Begin Experiment page.
    <em>Note: you need a Java compliant browser.</em>
Chad Barb's avatar
Chad Barb committed
382 383
    </p>

384
<li><a NAME="UTT-TOPO"></a>
Chad Barb's avatar
 
Chad Barb committed
385
    <font size='+1'><b>Are there any constraints on my topology?</b></font>
386 387 388 389 390 391 392 393 394 395 396
    <p>
    Yes, but only those imposed by the physical hardware that is
    currently available in our testbed. The constraints that people
    most commonly run into are the maximum speed of our links
    (100Mbps) and the maximum number of network interface cards (NICs)
    in our machines. You can't get any links faster than 100Mbps,
    since we don't yet have gigabit links for experimenters to
    use. Our nodes each have 4 experimental network interfaces, so
    each node can be a member of up to 4 links or LANs. A good
    strategy for making your topology fit within those limits is to
    replace multiple links to a node with a LAN or with a router
397 398 399 400 401 402 403 404 405 406 407 408
    node. 
    </p>
    <p>
    Another approach is to use
    <a href=doc/docwrapper.php3?docname=linkdelays.html#EMULINKS>
    <em>emulated</em> network links.</a> Emulated links are multiplexed
    over the actual physical links, up to the physical bandwidth that
    the physical link can support. In other words, five 20Mb links can
    be multiplexed over a 100Mb physical link. More information on
    emulated links can be found <a
    href=doc/docwrapper.php3?docname=linkdelays.html>here.</a> Ask
    Testbed Operations if you need further assistance.
409 410
    </p>

411
<li><a NAME="UTT-NODES"></a>
Chad Barb's avatar
 
Chad Barb committed
412
    <font size='+1'><b>How many nodes can I ask for?</b></font>
413 414 415 416 417
    <p>
    You can ask for as many nodes as are currently available! You can
    click on the "Node Reservation Status" link at your left to see
    how many nodes are currently free. If you ask for more than are
    currently available, your experiment will be rejected (you
Jay Lepreau's avatar
Jay Lepreau committed
418
    will receive email notification shortly after you submit your NS
419 420 421 422 423 424 425 426 427
    file to the web interface).
    </p>

    <p>
    <em>We urge all new Emulab users to begin with a small 3-4 node
    experiment so that you will become familiar with NS syntax and the
    practical aspects of Emulab operation.</em>
    </p>

428
<li><a NAME="UTT-HOWLONG"></a>
Chad Barb's avatar
 
Chad Barb committed
429
    <font size='+1'><b>How long can I keep using my nodes?</b></font>
430 431 432 433 434 435 436 437 438 439 440 441 442 443
    <p>
    You can keep them as long as you need them, subject to our <a
    href="docwrapper.php3?docname=swapping.html">Node Usage
    Policies</a>.  In general, you should do your work, and then
    terminate your experiment as soon as you're done with it. If
    you're not done with it, but are through for a while, you should
    probably "swap out" your experiment (See the question <a
    href="#UTT-Swapping">What is Swapping</a> in this FAQ). It is
    especially important to swap out your experiment if you're through
    with it for the weekend. Emulab usually gets heavy use on the
    weekends by users who need to make very large experiments, so it
    is important to leave as many nodes available as possible.
    </p>

444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471
<li><a NAME="UTT-QUEUE"></a>
    <font size='+1'><b>I only need a couple of nodes but none are free,
      			should I just keep trying?</b></font>
    <p>
    It is better for you and us if you don't just keep hitting the
    submit button every few minutes.  It wastes your time and floods
    us with email (we get every failure message you do!)
    Instead, you can now use the
    <a href="tutorial/tutorial.php3#BatchMode">Batch System</a>
    to queue an interactive job.  By submitting your experiment as
    a batch job, but without any
    <a href="tutorial/tutorial.php3#Startupcmd"><tt>tb-set-node-startcmd</tt></a>
    directives in your NS file, the job will be queued until nodes are
    available.  For most experiments, this means just using your regular
    NS file, and checking the Batch Mode Experiment box when you create
    the experiment.
    </p><p>
    When your queued job is swapped in, you will be sent email to
    inform you, and you can start working!
    <b>Please note</b> that the
    experiment will be idle when it is swapped in, and will be
    <a href="swapping.html#idleswap">idle swapped</a> if you do not
    get things running on the nodes in a short period of time.  If your
    experiment does get swapped out before you can get to it, you can
    always visit the experiment's information page and try again by
    using the Queue Batch Experiment menu item.
    </p>

472
<li><a NAME="UTT-TOOFEW"></a>
Chad Barb's avatar
 
Chad Barb committed
473
    <font size='+1'><b>What if I need more nodes than are free?</b></font>
474 475 476
    <p>
    For example, say you need 50 nodes but there are only 40 free. In
    general, getting this many nodes is going to require intervention
Jay Lepreau's avatar
spello  
Jay Lepreau committed
477
    from Testbed Operations, if only so we can ask other experimenters
478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493
    to free up nodes, if possible. Please send us email if you are not
    able to able to get the number of nodes you need for your experiment.
    </p>

    <p>
    Another alternative is to use the
    <a href="tutorial/tutorial.php3#BatchMode">Batch System.</a> 
    If your experiment is amenable to being batched (does not require
    human intervention to start and stop), then you can submit a batch
    request, which will be serviced when enough nodes become
    available.  Typically, you would start out with a few nodes,
    getting used to the batch system and creating whatever scripts are
    needed to make the experiment batchable. Then scale up to larger
    numbers of nodes. Thats the easiest way of getting a lot of nodes!
    </p>    
    
494
<li><a NAME="UTT-2"></a>
Chad Barb's avatar
 
Chad Barb committed
495
    <font size='+1'><b>Do I get root access on my nodes?</b></font>
496 497 498 499 500 501
    <p>
    Yes. Project leaders get root access to all of the nodes in all of
    the experiments that are running in their project. Project members
    get root if their project leader grants them root access, when the
    leader approves the group <a href="#GS-1">membership request</a>.
    Root privileges are granted via the <code>sudo</code> command. The
502
    <a href="tutorial/tutorial.php3#RootAccess">tutorial</a> describes
503 504
    this in more detail.
    </p>
505 506

<li><a NAME="UTT-3"></a>
Chad Barb's avatar
 
Chad Barb committed
507
    <font size='+1'><b>Do my nodes have consoles I can look at?</b></font>
508
    <p>
509 510 511 512
    Yes. Each of the PCs has its own serial console line with which you can
    interact, either directly from your desktop (see next FAQ entry),
    or by hopping through the "users" machine,
    using our <tt>console</tt> program. To connect over serial line to
Mike Hibler's avatar
Mike Hibler committed
513
    "pc1" in your experiment, ssh into <b>users.emulab.net</b>, and
514 515 516 517 518 519
    then type <tt>console pc1</tt> at the Unix prompt. You may then
    interact with the serial console (hit "enter" to elicit output from
    the target machine).
    </p><p>
    In any case, all console output from each node is saved
    so that you may look at it it later. For each node,
520 521
    the console log is stored as <tt>/var/log/tiplogs/pcXXX.run</tt>.
    This <em>run</em> file is created when nodes are first allocated
522 523
    to an experiment, and the Unix permissions of the run files permit
    only members of the project to view them. When the nodes are
524 525
    deallocated, the run files are cleared, so if you want to save
    them, you must do so before terminating the experiment. 
526 527
    </p>

Chad Barb's avatar
Chad Barb committed
528
<li><a NAME="UTT-TUNNEL"></a>
Chad Barb's avatar
 
Chad Barb committed
529 530
    <font size='+1'><b>How do I connect directly to node consoles, 
        without going through <b>users</b>?</b></font>
Chad Barb's avatar
Chad Barb committed
531 532 533
    <p>
    Clicking "Connect to Serial Line"
    in the Node Options page will send your browser a "text/x-testbed-acl"
Chad Barb's avatar
 
Chad Barb committed
534 535 536 537 538 539 540
    ".tbacl" file. 
    In windows, if you have installed <code>tiptunnel</code>, available
    below, you can save this file in a folder and double-click it
    to launch a tunneled connection to your node.
    In FreeBSD or Linux, you can save the file and pass it as an argument
    to <code>tiptunnel</code>, or associate it with
    <code>tiptunnel</code> in your web browser.
541 542
    Upon connection you typically first have to hit "enter" to
    elicit output from the target machine.
Chad Barb's avatar
 
Chad Barb committed
543 544 545

<!--
    If you have downloaded <code>tiptunnel</code> and set it as the 
Chad Barb's avatar
Chad Barb committed
546 547 548 549 550
    handler for that MIME type, <code>tiptunnel</code> will launch a new 
    telnet running in a new xterm (this may take a few seconds.) 
    That telnet will be connected to a local port, 
    which is tunneled through SSL to your node's console. 
    Closing the xterm, exiting telnet, or killing <code>tiptunnel</code>
Chad Barb's avatar
 
Chad Barb committed
551 552
    itself will end the connection. -->
    
Chad Barb's avatar
Chad Barb committed
553
    </p>
Chad Barb's avatar
 
Chad Barb committed
554 555 556
    <ul>
    <li>
    You can download the <code>tiptunnel</code>
557
    <a href="downloads/tiptunnel-win32.exe">installer for Windows here</a>.
Chad Barb's avatar
 
Chad Barb committed
558 559
    </li>
    <li>
Chad Barb's avatar
 
Chad Barb committed
560 561
    You can download the <code>tiptunnel</code> statically-linked x86
    <a href="downloads/tiptunnel-freebsd.tar.gz">binary for FreeBSD here</a>.
Chad Barb's avatar
 
Chad Barb committed
562 563
    </li>
    <li>
Chad Barb's avatar
 
Chad Barb committed
564 565
    You can download the <code>tiptunnel</code> statically-linked x86
    <a href="downloads/tiptunnel-linux.tar.gz">binary for Linux here</a>.
Chad Barb's avatar
 
Chad Barb committed
566 567 568 569 570
    </li>   
    <li>
    A source distribution will be available soon.
    </li>
    </ul>
571

Chad Barb's avatar
 
Chad Barb committed
572
    <font size='+1'><b>Instructions for Windows:</b></font>
Chad Barb's avatar
 
Chad Barb committed
573 574 575 576 577 578 579 580 581 582
    <ul>
      <li>Run the installer executable, and successfully complete the installation.</li>
      <li>In the Web Interface Node view, 
          click on the "Connect to serial line" link.</li>
      <li><b>Save</b> the resulting .tbacl file in an appropriate place.
          (for instance a folder off the desktop.)</li>
      <li>For the lifetime of your experiment, you can simply double-click
          these .tbacl files to connect.</li>
    </ul> 

Chad Barb's avatar
 
Chad Barb committed
583
    <font size='+1'><b>Instructions for Linux/FreeBSD:</b></font>
584
    <ul>
Chad Barb's avatar
 
Chad Barb committed
585 586
    <li>Use <code>gunzip</code>, 
    then <code>tar xvf</code> on the downloaded file.</li>
587
    <li>Move the resulting <code>tiptunnel</code> binary into 
Chad Barb's avatar
 
Chad Barb committed
588
    a directory of your choice (<code>/usr/local/bin</code>, 
589 590 591
    or <code>~/bin</code> are two good places.)</li>
    <li>Set up your browser to handle MIME type "text/x-testbed-acl"
    as outlined below.</li>
Chad Barb's avatar
 
Chad Barb committed
592 593 594 595 596 597
    <li>In the Web Interface Node view, 
        click on the "Connect to serial line" link.</li>
    <li>If your browser is properly configured to use <code>tiptunnel</code>,
        a new xterm window with a telnet session open to your node
        should emerge.</li>
    <li>(Alternately, you can tell your browser to save "text/x-testbed-acl"
Chad Barb's avatar
 
Chad Barb committed
598 599 600 601
        files in a directory and you can run them with 
	<code>tiptunnel</code> directly;
        this may be more convenient than using the 
	web interface every time you wish
Chad Barb's avatar
 
Chad Barb committed
602
        to connect to a node in your experiment.
Chad Barb's avatar
 
Chad Barb committed
603 604
        Note that these files are valid for the 
	lifetime of your experiment.)</li>
605
    </ul>
606

Chad Barb's avatar
 
Chad Barb committed
607
    <font size='+1'><b>Linux/FreeBSD and Netscape 4.7:</b></font>
608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628
    <ul>
    <li>Choose <code>preferences</code> from the <code>edit</code> menu.</li>
    <li>Select <code>Navigator</code>, then <code>Applications</code> under
        it.</li>
    <li>Click the <code>New...</code> button.</li>
    <li>In the <code>MIMEType</code> box, type <code>text/x-testbed-acl</code>
    </li>
    <li>In the <code>Suffixes</code> box, type <code>tbacl</code></li>
    <li>Choose <code>Application</code> in the <code>Handled by</code>
        box</li>
    <li>Next to <code>Application</code>, either type the path to the
        <code>tiptunnel</code> binary, or use <code>Choose...</code> to find
        it.</li>
    <li>Now, <b>be sure to</b> put a space, then <code>%s</code> after the
        path to the application in the box. This tells netscape to actually
        pass the aclfile into tiptunnel (Mozilla does not require this;
        see below.)</li>
    <li>Click <code>OK</code>, then <code>OK</code> again.</li>
    <li>Clicking a "connect to serial line" link should now
        bring up a connection in an xterm window.</li>
    </ul> 
629

Chad Barb's avatar
 
Chad Barb committed
630
    <font size='+1'><b>Linux/FreeBSD and Mozilla:</b></font>
631 632 633 634 635
    <ul>
    <li>Choose <code>preferences</code> from the <code>edit</code> menu.</li>
    <li>Select <code>Navigator</code>, then <code>Helper Applications</code> 
        under it.</li>
    <li>Click the <code>New Type...</code> button.</li>
Chad Barb's avatar
 
Chad Barb committed
636 637
    <li>In the <code>MIMEType</code> box, 
    type <code>text/x-testbed-acl</code></li>
638 639 640
    <li>In the <code>File extension</code> box, type <code>tbacl</code></li>
    <li>For <code>Application to use</code>, either type the path to the
        <code>tiptunnel</code> binary, or use <code>Choose...</code> to find
641
	it.</li>
642 643 644 645 646
    <li>In Mozilla do <b>not</b> add a <code>%s</code>.</li>
    <li>Click <code>OK</code>, then <code>OK</code> again.</li>
    <li>Clicking a "connect to serial line" link should now
        bring up a connection in an xterm window.</li>
    </ul> 
647
    </p>
648

649
<li><a NAME="UTT-4"></a>
Chad Barb's avatar
 
Chad Barb committed
650
    <font size='+1'><b>Can I reboot (power cycle) my nodes?</b></font>
651 652
    <p>
    Yes. Each of the PCs is independently power controlled. If your
653
    node hangs, or is otherwise unresponsive, you can use the
654 655 656 657
    <tt>node_reboot</tt> command, as discussed in the
    <a href="tutorial/tutorial.php3#Wedged">Emulab Tutorial.</a>
    </p>

658
<li><a NAME="UTT-SCROGGED"></a>
659
    <font size='+1'><b>I've clobbered my disk! Now what?</b></font>
660 661 662 663 664 665 666 667 668 669
    <p>
    If you manage to corrupt a disk (or slice), no worries. You can easily
    repair the damage yourself by reloading a fresh copy of the default
    disk image. You will of course lose anything you have stored on that
    disk; it is a good idea to store only data that can be easily recreated, 
    or else store it in your project directory in <tt>/proj</tt>. Disk
    reloading is covered in more detail in the
    <a href="tutorial/tutorial.php3#Scrogged">Emulab Tutorial</a>.
    </p>

670
<li><a NAME="UTT-5"></a>
Chad Barb's avatar
 
Chad Barb committed
671 672
    <font size='+1'><b>Where do I 
    store files needed by my experiment?</b></font>
673 674 675 676
    <p>
    Each project has its own directory, rooted at <tt>/proj</tt>,
    which is available via NFS to all of the nodes in experiments
    running in that project. For example, when the "RON" project was
677
    created, a directory called <tt>/proj/RON</tt> was also created. This
678 679 680 681 682 683 684
    directory is owned by the project creator, and is in the unix
    group "RON." Its permission (mode) is 770; read/write/execute
    permitted by the project creator and by all of the members of the
    project RON, but protected against all access by people outside
    the RON project.
    </p>
    <p>
685 686 687 688 689
    Sub-groups within a project likewise have a directory in the
    <tt>/groups</tt> tree. A group named "group1" in the RON project
    would thus have a group directory in <tt>/groups/RON/group1</tt>.
    </p>
    <p>
690
    Project members are encouraged to store any files needed by their
691
    experiments in the corresponding /proj or /groups directory.
692 693
    </p>

694
<li><a NAME="UTT-6"></a>
Chad Barb's avatar
 
Chad Barb committed
695 696
    <font size='+1'><b>Are my files on 
    <b>users.emulab.net</b> backed up (filesaved)?</b></font>
697
    <p>
698 699 700
    Yes. All of the files in your home directory on /users, all of
    the files in your project directory in /proj, and all of the files
    in your groups directory in /groups are filesaved. While
701 702 703 704 705
    we can restore lost files in an emergency, we encourage you to
    back up critical data on your own to avoid (possibly long) delays
    in conducting your experiments.
    </p>
    
706
<li><a NAME="UTT-7"></a>
Chad Barb's avatar
 
Chad Barb committed
707 708
    <font size='+1'><b>Are the nodes 
    in my experiment backed up (filesaved)?</b></font>
709 710 711 712 713 714 715 716 717 718 719 720 721
    <p>
    No! The nodes in your experiment are not filesaved. Any changes
    you make to the local filesystems will be lost if the event of a
    disk failure. We plan to provide a mechanism for experimenters to
    create snapshots of their node state, but that is not done yet. In
    the meantime, any files that must not be lost should be stored in
    the project directory (/proj/<project_name>), which is available
    via NFS to all of the nodes in your experiment. You may also store
    files in your home directory (/users/<login>), also available via
    NFS to all of your nodes, but that is not the preferred location
    since quotas on /users are relatively small.
    </p>
    
722
<li><a NAME="UTT-Swapping"></a>
Chad Barb's avatar
 
Chad Barb committed
723
    <font size='+1'><b>What is Swapping?</b></font>
724
    <p>
725 726
    Swapping is when you (or we, or the Emulab system) temporarily swaps
    out your experiment,
727 728 729 730 731
    releasing all of the nodes in the experiment. Your experiment is
    still resident in the Emulab database, and you can see its status
    in the web interface, but no nodes are allocated. Once an
    experiment is swapped out, you can swap it back in via the web
    interface by going to the Experiment Information page for your
732
    experiment, and clicking on the swapin option. 
733
    You can also <a href="UTT-Modify">modify it</a>.
734 735
    </p>

736
    <p>
737
    The <tt>idle-swap</tt> checkbox in the Begin Experiment web page
738 739
    is used to determine what experiments can be <em>automatically</em>
    swapped by the testbed scheduling system. Note that all experiments are
740
    capable of being swapped; even if you do not check the idle-swap box,
741 742 743 744 745 746 747 748 749 750 751 752
    you are free to swap your own experiments as you like. The only
    difference is that the testbed scheduling system will not consider your
    experiment when looking for experiments to swap out. You will sometimes
    notice that the Experiment Information page does not contain the swap
    link. That is because experiments cannot be swapped when they are in
    transition. For example, when the experiment is being swapped in (say,
    after first being created) the link will disappear until the experiment
    is fully swapped in, and it is capable of being swapped out. You will
    need to occasionally reload the page so that the updated state is
    recognized and the swap link appears. 
    </p>
    
753 754 755
    <p>
    Be aware that we do not currently save any files that you may have
    placed on your nodes. When your experiment is swapped back in, you
756
    will likely get different nodes, with fresh copies of the disk
757 758 759
    images. For that reason, you should not swap your experiment out
    unless you make arrangements to save and restore any state you need.
    </p>
Robert Ricci's avatar
Robert Ricci committed
760

761
    <p>
762 763 764
    <em>Please be sure to read our 
    <a href="docwrapper.php3?docname=swapping.html"> Node Usage Policies</a></em>,
    which contain detailed information on swapping.
765
    </p>
Robert Ricci's avatar
Robert Ricci committed
766

767
<li><a NAME="UTT-Restart"></a>
Chad Barb's avatar
 
Chad Barb committed
768
    <font size='+1'><b>What is Experiment Restart?</b></font>
769 770 771 772 773
    <p>
    Experiment restart (or perhaps more aptly, replay) allows you to
    rerun your experiment from scratch, but without the added expense
    of a swapin and swapout. In other words, the nodes that are
    currently allocated to your experiment are all rebooted, and the
774 775
    experiment startup state is cleared. 
    The event scheduler for the experiment is restarted, and your event
776 777 778 779 780 781
    sequence is replayed again. Note that your rpms and tarfiles are
    <b>not</b> installed again. Replay is obviously faster than
    swapout/swapin, and has the added benefit that you will not run
    the risk of not being able to swapin for lack of available nodes.
    </p>

782
<li><a NAME="UTT-8"></a>
Chad Barb's avatar
 
Chad Barb committed
783 784
    <font size='+1'><b>How can I 
    get switch statistics (such as packet counts) for my experiment?</b></font>
Robert Ricci's avatar
Robert Ricci committed
785 786 787
    <p>
    We have a command called <code>portstats</code> that allows you access
    to some of the port counters on our switches. To use it, you'll need
788 789
    to ssh to <b>users.emulab.net</b>. '<code>portstats &lt;proj&gt; 
    &lt;exp&gt;</code>' will get you stats for all experimental interfaces in
Robert Ricci's avatar
Robert Ricci committed
790 791 792 793 794 795 796 797
    your experiment. Run '<code>portstats -h</code>' to get a list of other
    options, such as different sets of stats.
    </p>

    <p>
    Note that the numbers returned by <code>portstats</code> do not get
    reset between experiments.
    </p>
798 799

<li><a NAME="UTT-Naming"></a>
Chad Barb's avatar
 
Chad Barb committed
800 801
    <font size='+1'><b>What names should I use to refer to the nodes in my
    experiment?</b></font>
802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846

    <p>We set up names for your nodes in DNS, for use from outside,
    and <code>/etc/hosts</code> files for use on the nodes in the experiment.
    Since our nodes have multiple interfaces (the control network, and,
    depending on the experiment, possibly several experimental interfaces,)
    determining which name refers to which interface can be somewhat
    confusing. The rules below should help you figure this out.
    </p>

    <ul>
	<li><b>From the outside world</b> - 
	We set up names in the form
	<code><i>node</i>.<i>expt</i>.<i>proj</i>.emulab.net</code> in DNS,
	so that they visible anywhere on the Internet. This name always refers
	to the node's control network interface, which is the only one
	reachable from the outside world.
	</li>

	<li><b>On the nodes themselves</b> -
	There are three basic ways to refer to the interfaces of a node. The
	first is stored in DNS, and the second two are stored on the node in
	the <code>/etc/hosts</code> file.
	<ol>
	    <li><i>Fully-qualified hostnames</i> - These names the same ones
	    visible from the outside world, and referred to by attaching the
	    full domain name: ie.
	    <code><i>node</i>.<i>expt</i>.<i>proj</i>.emulab.net</code>. (note
	    that, since we put <code>.emulab.net</code> in nodes' domain
	    search paths, you can use
	    <code><i>node</i>.<i>expt</i>.<i>proj</i></code> as a shorthand.)
	    This name always refers to the control network
	    </li>

	    <li><i><code>node-link</code> form</i> - You can refer to an
	    individual experimental interface by suffixing it with the name of
	    the link or LAN (as defined in your NS file) that it is a member
	    of. For example, <code>nodeA-link0</code> or
	    <code>server-serverLAN</code>. This is the preferred way to refer
	    to experimental interfaces, since it uniquely and unambiguously
	    identifies an interface.
	    </li>

	    <li><i>Short form</i> - If a node is directly connected to the
	    node you're on, you can refer to that node simply with its name
	    (eg. <code>nodeA</code>.) Note that this differs from the fully-
Robert Ricci's avatar
Robert Ricci committed
847 848 849
	    qualified name in that no domain is given. We also create short
	    names for nodes you are not directly connected to.
	    However, if two nodes are
850 851 852 853 854 855 856 857
	    connected with more than one interface, or there is more than
	    one route between them, there is no guarantee that the short name
	    has been associated with the one is on the 'best' (ie. shortest or
	    highest bandwidth) path - so, if there is ambiguity, we strongly
	    suggest that you use the <code><i>node-link</i></code> form.
	    </li>
	</li>
    </ul>
Chad Barb's avatar
 
Chad Barb committed
858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890
<br>
<li><a NAME="UTT-Modify"></a>
    <font size='+1'><b>Can I modify my experiment after creating it?
    </b></font>

    <p>Yes. On the experiment view page, choose "Modify this Experiment".
       This will allow you to modify an experiment, either swapped-out or in,
       by editing its NS file.</p>
    <p>If the experiment is swapped-out, 
       Experiment Modify will simply replace its topology with the
       newly specified one;
       this new topology will be mapped when the experiment is swapped in.</p>
    <p>If the experiment is already swapped-in, Modify will change the topology
       and map in the portions which have been changed. This allows dynamic
       addition, subtraction, and replacement of an experiment's nodes and links.
       However, when modifying swapped-in experiments, there are a couple
       things to keep in mind:
       <ul>
         <li>Any node with the same name in the old and new topology will remain
	 on the same physical machine, unaffected-- its disk will not be reloaded.
	 If you want to, for example, change the hardware on a machine, you will
	 have to call the machine something different in the new topology.
	 </li>
	 <br>
	 <li>
	 It is highly recommended that you leave the
	 "Reboot nodes in experiment" box checked in the Experiment Modify form.
	 This is especially important if changing your experiment topology 
         (adding or removing nodes, links, and LANs).
	 If adding/removing a delay to/from an existing link, or replacing 
	 a lost node <i>without modifying the experiment topology</i>,
	 this won't be necessary.
	 </li>
891 892 893 894 895 896 897 898 899 900
	 <li>
	 The event system is not automatically restarted for your
	 experiment, so you will not be able to modify the traffic
	 shaping for new links. In addition, if you add program
	 agents or traffic generators, these will not activate unless
	 you restart the event system by hand. Unfortunately, all
	 events will be replayed, so be careful: On
	 <tt>users.emulab.net</tt>, you may do the following:
	     <blockquote>
	     	<code>
901
	        eventsys_control [-f] replay proj expt
902 903 904
		</code>
	     </blockquote>
	 </li>
Chad Barb's avatar
 
Chad Barb committed
905 906
       </ul>
    </p>
907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957

<li><a NAME="UTT-SWPaths"></a>
    <font size='+1'><b> 
    Are there Linux and/or FreeBSD sources and packages available locally?
    </b></font>
    <p>
    Yes.  We provide sources and packages for a few versions of
    FreeBSD and RedHat Linux.  The place to look for available
    software is under <b>/share</b> on either <b>users.emulab.net</b>
    or your experimental nodes.  This path is readonly (and NFS
    mounted on the nodes), so you'll need to make a copy of the
    contents found there if you need to do more than reference them
    for information or installation.
    </p>

    <ul>
        <li><b>FreeBSD Paths:</b>
        The FreeBSD kernel, and userland sources are available under
        <b>/share/freebsd</b>.  Look there to see if the version you are
        seeking is available.  You can also find Emulab additions and
        modifications to FreeBSD here.  Emulab kernel configurations are
        called TESTBED and located in <b>sys/i386/conf</b> relative to the
        FreeBSD source trees.  The README file in this directory has more
        information on the contents.
        </li>

        <br>
        <li><b>Linux Paths:</b>
        Linux kernel sources and RPMs for various versions of Redhat can
        be found under <b>/share/redhat</b>.  Look there to see if the
        version you are seeking is available.  You can also find Emulab
        additions and modifications to Linux here.  Emulab kernel
        configurations are called <b>config-emulab</b> and exist in the
        root of the kernel source trees.  The README file in this
        directory has more information on the contents.
        </li>
        
        <br>
        <li><b>Other Software:</b>
        We provide a few other generally useful software packages and
        sources under <b>/share</b> as well.  Have a look around.
        </li>

        <br>
        <li><b>Something Missing?</b> 
        If you think something should be added to <b>/share</b>, feel
        free to send your suggestion(s) to us via 
        <a href="emailus.php3">email</a>.  Note that we may retire some
        offerings if we determine them to be of little value.
        </li>
    </ul>
958 959 960 961 962 963
</ul>

<hr>


<a NAME="HDS"></a>
Chad Barb's avatar
 
Chad Barb committed
964
<font size='+1'><b>Hardware Setup</b></font>
965 966
<ul>
<li><a NAME="HDS-1"></a>
Chad Barb's avatar
 
Chad Barb committed
967
    <font size='+1'><b>What kind of computers are used for my nodes?
968 969 970
<li><a NAME="HDS-2"></a>
    How many nodes are there?
<li><a NAME="HDS-3"></a>
Chad Barb's avatar
 
Chad Barb committed
971
    How many ethernet cards are on each node?</b></font>
972
    <p>
973 974 975
    Please see the <a href="docwrapper.php3?docname=hardware.html">
    Hardware Overview</a> page for a description and count of the
    computers that comprise the Testbed.
976
    </p>
977 978 979 980 981 982 983 984 985 986 987 988 989
<li><a NAME="HDS-8"></a>
    <font size='+1'><b>How do I ask for specific hardware?</b></font>
    <p>
    See the previous FAQ entry for a description of what hardware is available.
    If you would like to ask for a specific type of hardware, such as a
    <code>pc850</code>, see the
    <a href="tutorial/docwrapper.php3?docname=nscommands.html#HARD"><code>tb-set-hardware</code></a>
    command in our <a href="tutorial/docwrapper.php3?docname=nscommands.html">NS
    extensions document</a>. You can also define classes of nodes which should
    be given the same hardware using
    <a href="tutorial/docwrapper.php3?docname=nscommands.html#VTYPE">virtual
    type commands</a>.
    </p>
990 991
    
<li><a NAME="HDS-4"></a>
Chad Barb's avatar
 
Chad Barb committed
992
    <font size='+1'><b>How many nodes are currently available (free)?</b></font>
993 994 995 996 997 998 999 1000
    <p>
    If you click on the "Node Reservation Status" link in the menu to
    your left, you will see a summary of the number of nodes (by type)
    that are currently available, followed by a listing of the
    reservation status of each individual node.
    </p>
    
<li><a NAME="HDS-5"></a>
Chad Barb's avatar
 
Chad Barb committed
1001
    <font size='+1'><b>Can I do traffic shaping on my links?</b></font>
1002 1003 1004 1005 1006 1007 1008 1009 1010
    <p>
    Yes! You can specify the delay, bandwidth, and packet loss rate
    between any two nodes in your topology. Bandwidth and delay are
    specified in the NS <tt>duplex-link</tt> statement, while packet
    loss rate is specified with the Emulab <tt>tb-set-link-loss</tt>
    extension to NS. You may also specify delay, bandwidth, and packet
    loss rate between nodes in a regular LAN.
    </p>
    <p>
1011
    Please see the
1012
    <a href="tutorial/docwrapper.php3?docname=nscommands.html">Extensions</a>
1013
    page for a summary of all Emulab NS extensions, and the
1014
    <a href = "tutorial/tutorial.php3">Emulab Tutorial</a> for an
1015 1016
    example. 
    </p>
1017 1018

<li><a NAME="HDS-6"></a>
Chad Barb's avatar
 
Chad Barb committed
1019 1020
    <font size='+1'><b>Can I modify the 
    traffic shaping parameters on my links?</b></font>
1021 1022 1023 1024 1025 1026
    <p>
    Yes! If your NS file specified traffic shaping on a link, then you
    can subsequently modify those parameters after the experiment has
    been swapped in. Note that you cannot <em>convert</em> a non shaped
    link into a shaped link; you can only modify the traffic shaping
    parameters of a link that is already being shaped.  To modify the
1027 1028 1029 1030 1031 1032
    parameters, go to the Experiment Information page of your
    experiment, and click on the "Control Traffic Shaping" menu
    option. Follow the instructions at the top of the page.
    </p>
    <p>
    An alternative method is to log into <b>users.emulab.net</b> and use the
1033 1034 1035
    <tt>delay_config</tt> program. This program requires that you know
    the symbolic names of the individual links. This information is
    available via the web interface on the Experiment Information
1036 1037
    page. The command line syntax for <tt>delay_config</tt> will be
    displayed when the <tt>-h</tt> option is given.
1038
    </p>
1039 1040

<li><a NAME="HDS-7"></a>
Chad Barb's avatar
 
Chad Barb committed
1041 1042 1043
    <font size='+1'><b>Are there other 
    traffic shaping parameters besides latency,
    bandwidth, and packet loss rate?</b></font>
1044
    <p>
1045 1046 1047 1048 1049 1050 1051
    Yes! Please see the
    <a href="tutorial/docwrapper.php3?docname=advanced.html">
    advanced tutorial</a>. Note though, that these other parameters
    can be specified for duplex links only (not lans), and that they
    are not configurable with <tt>delay_config</tt>, but with a
    different testbed utility call <tt>tevc</tt> (also described in
    the advanced tutorial).
1052
    </p>    
1053

1054 1055 1056 1057 1058
</ul>

<hr>

<a NAME="SWS"></a>
Chad Barb's avatar
 
Chad Barb committed
1059
<font size='+1'><b>Software Setup</b></font>
1060 1061
<ul>
<li><a NAME="SWS-1"></a>
Chad Barb's avatar
 
Chad Barb committed
1062
    <font size='+1'><b>What OS do the nodes run?</b></font>
1063
    <p>
1064 1065 1066
    Please see the <a href="docwrapper.php3?docname=software.html">
    Software Overview</a> page for a description of the Operating
    Systems that can be run on each of the Testbed nodes.
1067 1068 1069
    </p>

<li><a NAME="SWS-2"></a>
Chad Barb's avatar
 
Chad Barb committed
1070
    <font size='+1'><b>How do I select which OS to run on each node?</b></font>
1071 1072 1073 1074 1075 1076 1077 1078
    <p>
    When a choice of OS is available, you may specify which one you
    prefer for each node in the NS file using the Emulab
    <tt>tb-set-node-os</tt> extension to NS. When your experiment is
    configured, the appropriate disk image will be loaded on your
    nodes, and the selected operating system will boot up on each.
    </p>
    <p>
1079
    Please see the
1080
    <a href="tutorial/docwrapper.php3?docname=nscommands.html">Extensions</a>
1081
    page for a summary of all Emulab NS extensions, and the
1082
    <a href = "tutorial/tutorial.php3">Emulab Tutorial</a> for an
1083 1084 1085 1086
    example. 
    </p>    
    
<li><a NAME="SWS-3"></a>
Leigh B. Stoller's avatar
Leigh B. Stoller committed
1087 1088
    <font size='+1'><b>Can I load my own software (RPMs/Tarballs) on
                       my nodes?</b></font>
1089
    <p>
Timothy Stack's avatar
 
Timothy Stack committed
1090
    Yes! If you have an RPM or Tarball (or more than one) that is appropriate for
1091 1092
    loading on the OS you have selected, you can arrange to have them
    loaded automatically when your experiment is configured. The
Timothy Stack's avatar
 
Timothy Stack committed
1093
    Emulab NS extension, <a href="tutorial/docwrapper.php3?docname=nscommands.html#tb-set-node-rpms"><tt>tb-set-node-rpms</tt></a>, is used in the NS
Leigh B. Stoller's avatar
Leigh B. Stoller committed
1094
    file to specify a list of RPMS to install.
Timothy Stack's avatar
 
Timothy Stack committed
1095 1096 1097 1098 1099 1100 1101 1102
    The <a
    href="tutorial/docwrapper.php3?docname=nscommands.html#tb-set-node-tarfiles"><tt>tb-set-node-tarfiles</tt></a>
    command is used to specify a list of Tar
    files to install, as well as the directories in which the tars
    should be unpacked. You may specify a
    different list for each node in the experiment. The RPMs/Tarballs
    will be installed when the nodes first boot after the experiment is
    swapped in or if the nodes detect a changed RPM/Tarball during a reboot.
1103 1104
    </p>
    <p>
1105
    Please see the
1106
    <a href="tutorial/docwrapper.php3?docname=nscommands.html">Extensions</a>
1107
    page for a summary of all Emulab NS extensions, and the
Leigh B. Stoller's avatar
Leigh B. Stoller committed
1108
    <a href = "tutorial/tutorial.php3#RPMS">Emulab Tutorial</a> for an
1109 1110
    example. 
    </p>    
1111
    
1112
<li><a NAME="SWS-4"></a>
Chad Barb's avatar
 
Chad Barb committed
1113 1114
    <font size='+1'><b>Can I schedule 
    programs to run automatically when a node boots?</b></font>
1115 1116 1117 1118 1119 1120 1121
    <p>
    Yes! You can arrange to run a single program or script when your
    node boots. The script is run as the UID of the experiment
    creator, and is run after all other node configuration (including
    RPM installation) has completed. The exit status of the script (or
    program) is reported back and is made available for you to view in
    Experiment Information link in the menu at your left. The Emulab
1122
    NS extension <tt>tb-set-node-startcmd</tt> is used in the NS file
1123 1124 1125 1126
    to specify the path of the script (or program) to run. You may
    specify a different program for each node in the experiment.
    </p>
    <p>
1127
    Please see the
1128
    <a href="tutorial/docwrapper.php3?docname=nscommands.html">Extensions</a>
1129
    page for a summary of all Emulab NS extensions, and the
1130
    <a href = "tutorial/tutorial.php3">Emulab Tutorial</a> for an
1131 1132
    example.
    </p>    
1133

1134
<li><a NAME="SWS-5"></a>
Chad Barb's avatar
 
Chad Barb committed
1135 1136
    <font size='+1'><b>How can I turn on routing or set up routes automatically 
    in my nodes?</b></font>
1137
    <p>
1138
    By default, we do not setup any static routes or run any routing daemon
1139
    on nodes in an experiment.  However, we do provide several options for
Jay Lepreau's avatar
spello  
Jay Lepreau committed
1140
    experimenters, which are described in the
1141 1142 1143
    <a href="tutorial/tutorial.php3#Routing">"Setting up IP routing
    between nodes"</a> section of the
    <a href="tutorial/tutorial.php3">Emulab Tutorial.</a>
1144 1145 1146
    </p>
    
<li><a NAME="SWS-6"></a>
Chad Barb's avatar
 
Chad Barb committed
1147 1148
    <font size='+1'><b>How does my software determine when other nodes in my
    experiment are ready?</b></font>
1149
    <p>
1150 1151 1152 1153 1154
    If your application requires synchronization amongst your nodes,
    you may use the Emulab provided synchronization server, which
    provides a very simple form of barrier synchronization. Use of the
    synchronization server is described in more detail in the <a href =
    "tutorial/tutorial.php3#SyncServer">Emulab Tutorial</a>.
1155 1156
    </p>
    
1157
<li><a NAME="SWS-7"></a>
Chad Barb's avatar
 
Chad Barb committed
1158
    <font size='+1'><b>Can I run my own Operating System?</b></font>
1159
    <p>
1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193
    Yes! You can run your own OS (or a customized version of an Emulab
    supported OS) on any of the PCs. You can also run <a href =
    "http://www.cs.utah.edu/flux/oskit/">OSKit</a> kernels on the
    PCs. Each of the PCs is partitioned with two DOS partitions large
    enough to hold the typical OS installation. The 1st and 2nd
    partitions are each 3GB. The 3rd partition is 500MB, and is
    labeled as Linux Swap. The 4th partition is the remainder of the
    disk, and varies in size depending on the pc type. We recommend
    that you use the 1st or 2nd partition; using the 4th partition
    will restrict the number of machines that you can run your OS on
    since it varies in size. Note that you must leave the MBR (Master
    Boot Record) in sector 0 alone, and that your custom partition
    must contain a proper DOS boot record in the first sector.
    </p>

    <p>
    Please note that while users are free to customize their disks and
    install their own operating systems, Emulab staff will not be able
    to offer more than encouragement and advice! We cannot install the
    OS for you, and we cannot load CDROMS, floppy disks, or tape drives!
    We <em>do</em> provide an easy way for you to boot FreeBSD from a
    memory based filesystem (MFS) so that you can more easily work
    with the disk (in case it is not possible to install your OS on a
    live disk). Beyond that, you are pretty much on your own!
    </p>

    <p>
    Many users had great success with customizing an Emulab supported
    OS (FreeBSD or Linux), and then creating a disk image that is
    autoloaded when the experiment is swapped in. We strongly
    encourage people to use this approach whenever possible! There is
    more information available in the <a
    href="tutorial/tutorial.php3#CustomOS">Custom OS</a> section of
    the <a href = "tutorial/tutorial.php3">Emulab Tutorial.</a>