Deprecated Pre-Experiment Instructions

Preconfiguring with emulatorDaemon

Once your experiment is swapped in, you must perform a preconfiguration step using the emulatorDaemon command. This must be done in the working directory where you intend to run subsequent commands.: 
	-bash-3.2$ emulatorDaemon <user name> <group> <experiment name>
The parameters are as follows:
<user name>
Your CMULab user name
<group>
emulator
<experiment name>
The experiment name you used in the CMULab experiment creation process
This process creates a file <experiment name>.<group>.emulab in the current directory containing configuration information from the emulab software for the wireless emulator software. It is important that you run emuRun and startDaemon from the same directory.

Starting Node Daemons

These instructions are suspect. Sorry.

The main executable, emuRun relies on Java RMI to control and communicate with the nodes in your experiment. By default, emuRun starts these RMI servers automatically, but there are situations in which you will need to start them yourself. As a new user, you should assume that you need to start these processes yourself. For every node in your experiment (e.g. nodew1 and nodew2), do the following: 

-bash-3.2$ startDaemon <node_name>
You should expect output like the following. Note in particular that you may need to accept nodew1's ssh host key. 
start Node Daemon for [nodew1]; (1 nodes)
startDaemon for nodew1
The authenticity of host '10.96.65.104 (10.96.65.104)' can't be established.
RSA key fingerprint is 8e:51:04:cc:8c:f5:a4:0a:5f:da:0c:65:1e:b9:bf:c5.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.96.65.104' (RSA) to the list of known hosts.
ath0      Link encap:Ethernet  HWaddr 00:02:6F:21:EC:C5  
          inet addr:10.1.1.2  Bcast:10.1.1.255  Mask:255.255.255.0
          inet6 addr: fe80::202:6fff:fe21:ecc5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:468 (468.0 b)

rmiregistry: no process killed
ath0      Link encap:Ethernet  HWaddr 00:02:6F:21:EC:C5  
          inet addr:10.1.1.2  Bcast:10.1.1.255  Mask:255.255.255.0
          inet6 addr: fe80::202:6fff:fe21:ecc5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:468 (468.0 b)

java: no process killed
startDaemon is done
-bash-3.2$ ath0      Link encap:Ethernet  HWaddr 00:02:6F:21:EC:C5  
          inet addr:10.1.1.2  Bcast:10.1.1.255  Mask:255.255.255.0
          inet6 addr: fe80::202:6fff:fe21:ecc5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:468 (468.0 b)

ath0      Link encap:Ethernet  HWaddr 00:02:6F:21:EC:C5  
          inet addr:10.1.1.2  Bcast:10.1.1.255  Mask:255.255.255.0
          inet6 addr: fe80::202:6fff:fe21:ecc5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:468 (468.0 b)

Setting Emulator Hostname to 10.96.65.104

There are several possible failure modes here. If you don't see results like the above, check the following:

  1. Is your experiment (currently / still) swapped in?
  2. Was there a problem with ssh host keys?