This is an old revision of the document!
Table of Contents
Connecting to the CHPC
The CHPC hosts two systems of supercomputers:
- IBM
- e1350 cluster
- Blue Gene/P
- SUN
- Nehalem cluster
- Harpertown cluster
- M9000 SMP
- Nvidia visualization node
Each system has a single login node which is connected to the Internet and allows connections to the individual supercomputers of each system.
Logging In
Connections to the login nodes of the CHPC machines is via the ssh protocol. To connect use
ssh username@login-node.chpc.ac.za
where login-node is replaced by the hostname for the login node of the system you wish to connect to, and username is replaced by the user name assigned to your account at the CHPC.
Hostnames
The hostnames and IP addresses for all CHPC login nodes are listed below.
| System | Host Name | IP Number | |
|---|---|---|---|
| SUN | Primary address | sun.chpc.ac.za | 41.193.29.30 |
| IBM Blue Gene | Primary address | bgp.chpc.ac.za | 41.193.82.60 |
| GPU | Primary address | gpu.chpc.ac.za | ?????????? |
Note that if you are connecting from UCT or the CSIR please use the dedicated address for those subnets, otherwise use the primary address.
Connecting from the CSIR
| System | Host Name | IP Number | |
|---|---|---|---|
| SUN | …connecting from CSIR only | chpcsun.csir.co.za | 146.64.21.24 |
| IBM Blue Gene | …connecting from CSIR only | ????????? | ???????? |
| GPU | …connecting from CSIR only | ????????? | ?????????? |
Connecting from UCT
| System | Host Name | IP Number | |
|---|---|---|---|
| SUN | …IP address for UCT only | 196.13.250.16 | |
| IBM Blue Gene | …IP address for UCT only | ?????????? | |
| GPU | …IP address for UCT only | ????????? |
Transferring Files
Use scp or sftp to transfer files to or from your home directory on the CHPC systems. For example
scp src.tar.gz username@sun.chpc.ac.za:scratch/
to copy the file src.tar.gz to your work directory on the SUN cluster.
MS Windows
Should you be using a MS Windows computer to connect to the CHPC we suggest you download and install the open source PuTTY and WinSCP clients:
| Windows Application | Provides | Home page | |
|---|---|---|---|
| PuTTY | ssh | http://www.chiark.greenend.org.uk/~sgtatham/putty/ | download |
| WinSCP | scp/sftp | http://winscp.net/ | download |
ssh keys
The best way to connect via ssh is to create ssh keys which authenticate you instead of your password.
First create your private and public keys on your main work computer (which we assume is a desktop or laptop computer running Linux)
ssh-keygen -t dsa
This creates two new files in your .ssh directory
| id_dsa | your private key |
| id_dsa.pub | the corresponding public key |
It is the latter file that you need to add to the .ssh/authorized_keys file in your home directories on the CHPC login nodes (SUN or IBM).
From a recent Linux distribution you can simply do this :-
ssh-copy-id username@login-node.chpc.ac.za
From older Unix setups you might have to do this :-
cat ~/.ssh/id_dsa.pub > ssh username@login-node.chpc.ac.za "cat >> .ssh/authorized_keys; chmod 0700 .ssh; chmod 0600 .ssh/authorized_keys"
And the next time you ssh or scp to the CHPC login node you won't have to use your password!
(Notice that you need to change the permissions of the .ssh directory and the authorized_keys file on the login nodes to make them private and readable by you only before ssh will use the new public key.)
