BigClusterDHCPInstructions < Main

Tags: view all tags
---+ Booting DHCP for the Big Cluster
To be the DHCP server, you must be on an x86 computer.

DHCP server, follow this sequence:
   * Boot up to the BCCD splash screen
   * Hit F3, then type <tt><i>framebuffer_mode_number</i>  startdhcp</tt> (<i>framebuffer_mode_number</i> just refers to what screen resolution to use; 4 is 1024x768.)
   * Enter the password we decide on the day of the event.
   * Follow directions for trivial-net-setup.   Hit Enter to select the highlighted answer and the arrow keys to change the selection.
      * Say NO when it asks if it should autoconfigure with DHCP and YES/OK for everything else.
      * When it asks for IP addresses, [[http://bccd.cs.uni.edu/cgi-bin/twiki/view/Main/DhcpSetup][configure as in the examples]].  You can just type in the addresses they use in the dialogs, which are
         * IP address 192.168.1.1
         * netmastk 255.255.255.0
         * router address 192.168.1.254
         * DNS server 192.168.1.1 


   * When you get to the option of logging in:
      * Login as root, using the password listed at the login prompt
      * Change the password.  If you are helping the owner, let the owner set the password.
      * Copy the example code from wherever to <tt>~bccd/src</tt>
      * <tt>chmod -R bccd ~/src</tt>
      * <tt>df</tt> to get a list of the mounted partitions
      * <tt>umount <i>partition</i></tt> for all of your local drive partitions, (e.g. <tt>umount /mnt/rw/discs/disc0/part3/home/fred</tt>)  Macs don't seem to mount all your local drives.
      * <tt>exit</tt>
   * Sign in as bccd, with the password given earlier.
   * Answer yes when it asks if you want to run a heartbeat.


---+++ [[http://bccd.cs.uni.edu/cgi-bin/twiki/view/Main/RunningLamMpi][Switch to LAM]] 
Switch to LAM:
   * edit <tt>~/.bashrc</tt> 
      * edit the PATH line so that the line reads <tt>export PATH=/lam-mpi/bin:$PATH</tt>
      * write file and quit
   * <tt>source ~/.bashrc</tt> (or log out and log back in)
   * For each node, rebuild the library cache: 
      * <tt>su - root</tt> (using the root password given)
      * <tt>ldconfig -v | less</tt>
      * <tt>exit</tt> (back to bccd)
   * <tt>bccd-allowall</tt> (Answer yes.)
   * <tt>bccd-snarfhosts</tt>
   * <tt>recon -v ~/machines</tt>  (It might take a few tries for this to work, not sure why.)
   * <tt>lamboot -v ~/machines</tt> 

You have the option of
   * <tt>startx</tt>



---+++ [[http://bccd.cs.uni.edu/cgi-bin/twiki/view/Main/CompilingAndRunning][Compile the target code]]
Everybody needs to compile the target code. 
   * <tt>bccd-syncdir ~bccd/src ~/machines</tt> 
   * <tt>cp -r <i>dirname</i>/cs521.<i>arch</i> ~bccd/cs521</tt> (where <i>dirname</i> is the tmp dir name and <i>arch</i> is either <tt>x86</tt> or <tt>ppc</tt>, e.g. <tt>cp -r /tmp/6g2w98s/cs521.x86 ~bccd/cs521</tt>)
   * <tt>cd ~bccd/cs521</tt>
   * <tt>make</tt>
   * <b>run the program</b>


As more machines come online, you might need to refresh your system state:
   * <tt>bccd-allowall</tt>
   * <tt>bccd-snarfhosts</tt>
   * <tt>recon -v ~/machines</tt> 

There is some order dependency that Ducky hasn't quite figured out yet; keep doing those and eventually it will all get settled out.
Raw edit | More topic actions
Topic revision: r1 - 2006-04-07 - TWikiGuest