Machine overview

There is a description of Mine's new HPC platform BlueM at: http://hpc.mines.edu/bluem/description.html Please review this page.

Access

Sshing (loging in) to directly form your workstation to aun or mc2 is not supported. There is a frontend machine bluem.mines.edu that is to be used as gain access to aun and mc2.

To get to aun or mc2 you first login to bluem and then ssh to your target machine. Bluem has access to the file system on mc2/aun, facilitating easy transfers of data.

Passwords on bluem, aun, mc2, are the same as your campus email password (as is Mio if you have an account there). However, you should rarely (if ever) need passwords for aun and mc2 after the first time you login. See below.

First time access to bluem, aun, and mc2

The first time you login to bluem the system may need to set up ssh keys to provide passwordless access to AuN, Mc2. Some accounts are "prestaged" and you may not be asked to set up ssh keys.

Step 1: getting on to bluem.

Login to bluem using ssh. You may receive a message similar to the one below about your ssh keys being setup.

[joeminer@mio ~]$ ssh bluem
joeminer@bluem's password: 
Last login: Thu Sep  5 11:17:42 2013 from osage.mines.edu

It doesn't appear that you have set up your ssh key.
This process will make the files:
     /u/pa/ru/joeminer/.ssh/id_dsa.pub
     /u/pa/ru/joeminer/.ssh/id_dsa
     /u/pa/ru/joeminer/.ssh/authorized_keys

Generating public/private dsa key pair.
Your identification has been saved in /u/pa/ru/joeminer/.ssh/id_dsa.
Your public key has been saved in /u/pa/ru/joeminer/.ssh/id_dsa.pub.
The key fingerprint is:
d7:67:9f:34:5b:e3:2d:7b:88:00:02:a6:94:34:da:fb joeminer@bluem
The key's randomart image is:
+--[ DSA 1024]----+
| .o.             |
| oo.o            |
|...o .           |
|  ..  . .  .     |
|  .    .S.. . o+.|
|   .     ..  oo.B|
|    E      . ..=o|
|            . .o.|
|              .. |
+-----------------+
 
[joeminer@bluem ~]$ 

Step 2: Getting on to AuN and Mc2.

Next login to AuN from bluem and then login to Mc2. You will most likely be asked for a password and you may see again see a message about setting up your ssh keys. You can login to Mc2 from either bluem or from AuN.

Step 3: Enabling easy access to AuN and Mc2 from bluem

After you have logged into Aun and Mc2 logout so that you are back on bluem.

Run the command /opt/utility/appendkeys from bluem. For example:

[joeminer@bluem ~]$ /opt/utility/appendkeys
copying bluem keys to AuN
copying bluem keys to Mc2
[joeminer@bluem ~]$ 

At this point you should be able to ssh to each of the machines from bluem without entering a password. For example:

[joeminer@bluem ~]$ ssh aun
Last login: Wed Sep  4 12:47:58 2013 from bluem.mines.edu
[joeminer@aun002 ~]$ exit
logout
Connection to aun closed.

[joeminer@bluem ~]$ ssh mc2
Last login: Wed Sep  4 12:17:06 2013 from bluem.mines.edu
 ###################################################################
 ##                                                               ##
 ##                    ** BlueGene/Q **                           ##
 ##                                                               ##
 ##  This internal system must only be used for conducting        ##
 ##  company business or for purposes authorized by managment     ##
 ##  Use is subject to audit at any time by management.           ##
 ##                                                               ##
 ##                                                               ##
[joeminer@mc2 ~]$ exit
logout

Setting up tunnels and ssh keys for easy access

It is highly recommended that you set up tunnels and ssh keys to allow for easier access to Bluem, Mc2, and AuN. After this is done you will be able to ssh directly to Mc2 and AuN from both on and off campus. See http://hpc.mines.edu/access. This page also has links to materials from a recent HPC workshop, including an introduction to Linux, MPI, OpenMP, and BlueM.

File system

The subdirectories in remote on bluem are links to the directories on AuN and Mc2. You can copy files to AuN and Mc2 by doing a copy to these subdirectories.

Scratch is shared across the platforms. This is where runs should be done, not in your home directory. The bins directory is distinct on the two machines. Files created in bins on mc2 are not in bins on aun. The bins directory is where you should store applications that you build.

The mc2 directory on aun is a link to your home directory on mc2 and the aun directory on mc2 is the reverse.