15-496 Spring 2008

Setting Up Your Emulator Accounts

This page describes what you need to setup your emulator accounts for your experiments. You should only need to do everything on this page once.

Before You Begin

You should have:

• An email from the administrators containing:
  • A login name on emucontrol-1 identical to your andrew ID,
  • an ssh password for emucontrol-1,
  • and a GUI password

You can change your emucontrol-1 password after logging in, with the passwd command.

Remember to read-protect your home directory on emucontrol-1 to prevent your solutions from being accessed by other students. From emucontrol-1, type:

chmod 700 ~

You can change your GUI password by logging in to this page with it and selecting "Manage Account".

Applying for an account on CMULab

1. Go to https://boss.cmcl.cs.cmu.edu/
2. Click on "Request Account"
3. Select "Join an Existing Project"
4. Fill in the form
   • Username: Use your Andrew ID
   • Project Name: emulator
   • Group Name: emulator
5. Submit and check your email
6. On the received email, click on the link to confirm your email verification
7. Wait for an administration member to confirm your registration
8. Login at https://boss.cmcl.cs.cmu.edu/

Setting up SSH access for ops.cs.cmu.edu

One paragraph intro to SSH: You generate two keys (one public, one private). Place the public key on the server. During authentication, the server will verify that you possess the private counterpart of the public key that it has in its database.

If that description didn't make sense, try the short SSH tutorial here (optional, for interested readers only): http://kimmo.suominen.com/docs/ssh/

Instructions for setting up SSH from emucontrol-1.ece.cmu.edu to ops.cs.cmu.edu

1. Typical emucontrol-1 accounts already have a ~/.ssh directory containing two files: id_rsa (containing your private key) and id_rsa.pub (containing your public key).
• If these files do not exist, generate them with: ssh-keygen -t rsa (use the "no passphrase" option).
2. Now, copy the file id_rsa.pub to your local machine.
• You can use scp to copy the file, or WinSCP for windows machines. Authenticate at emucontrol-1 using your password.
3. From "My Emulab" (homepage after login at https://boss.cmcl.cs.cmu.edu/)
4. Select Profile
5. On the left sidebar "Options", select "edit SSH keys"
6. Upload the file id_rsa.pub. Supply your Emulab password where prompted.

Instructions for setting up SSH from your local computer to ops.cs.cmu.edu (optional)

1. If it's a linux or unix machine, just follow the steps above identically.
2. For Windows machines, generate your keypair with PuttyGen, get it here: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
3. Save both your private and public keys somewhere secure
• i.e. in a directory that only you can read
4. Upload your public key as above (steps 3-6)
5. On your SSH or SCP application, select your saved private key file as your method of authentication.

Setting up SSL Access

These steps are necessary for the emulator software to interface with the emulab software.

1. login to emucontrol-1.ece.cmu.edu
2. Check that the folder ~/.ssl exists (use ls -A or just cd .ssl).
   1. If the folder doesn't exist, make it (mkdir ~/.ssl)
3. Copy over the file emulab.pem existing on ops.cmcl.cs.cmu.edu:
   • scp ops.cmcl.cs.cmu.edu:~/.ssl/emulab.pem ~/.ssl/emulab.pem

Set Up Necessary Files on ops.cs.cmu.edu

1. Grab either emustartpack.rar or emustartpack.taz from http://www.cs.cmu.edu/~haowen/15496/
• Take your pick, they're the same
• Open the rar with WinRAR, or the taz with the command: tar xvzf emustartpack.taz
2. Copy (scp) the file.cshrc to ops.cs.cmu.edu:~ rename it to .cshrc
• This file is pushed out to the nodes so when you login to an experiment node, the correct environment variables are set up.
3. Copy (scp) the whole emuNode directory to ops.cs.cmu.edu:~
   • All the files in your ops.cs.cmu.edu:~/emuNode directory are pushed onto your wireless nodes when your experiment loads
   • ops.cs.cmu.edu:~/emuNode is where you would put your extra diagnostic applications and custom protocols if you want to run them on the nodes
   • Remember to chmod +x * in that directory so you can actually execute these programs.
4. Remaining files in the package are useful examples.

Frequently Encountered Problems

1. The shell files may be translated into windows text format if you modify them in a windows machine. If you see errors like ": command not found" it means you've got this problem. To remedy this, you can just copy over the shell files from my directory on the machines.
   1. On ops.cmcl.cmu.edu, do cp ~/../haowen/.cshrc ~
   2. On emucontrol-1.ece.cmu.edu, do cp ~/../haowenchan/.bashrc ~

Now your're done! Try running this tutorial here.