Commit 3d23514a authored by Lukáš Krupčík's avatar Lukáš Krupčík
Browse files

add .md files

parent a621a1ab
Pipeline #1074 failed with stage
in 10 seconds
This diff is collapsed.
Welcome to Anselm supercomputer cluster. The Anselm cluster consists of
209 compute nodes, totaling 3344 compute cores with 15TB RAM and giving
over 94 Tflop/s theoretical peak performance. Each node is a <span
class="WYSIWYG_LINK">powerful</span> x86-64 computer, equipped with 16
cores, at least 64GB RAM, and 500GB harddrive. Nodes are interconnected
by fully non-blocking fat-tree Infiniband network and equipped with
Intel Sandy Bridge processors. A few nodes are also equipped with NVIDIA
Kepler GPU or Intel Xeon Phi MIC accelerators. Read more in [Hardware
The cluster runs bullx Linux [<span
which is compatible with the <span class="WYSIWYG_LINK">RedHat</span>
[<span class="WYSIWYG_LINK">Linux
We have installed a wide range of
packages targeted at different scientific domains. These packages are
accessible via the [modules
User data shared file-system (HOME, 320TB) and job data shared
file-system (SCRATCH, 146TB) are available to users.
The PBS Professional workload manager provides [computing resources
allocations and job
Read more on how to [apply for
[obtain login
and [access the
Shell access and data transfer
Interactive Login
The Anselm cluster is accessed by SSH protocol via login nodes login1
and login2 at address The login nodes may be addressed
specifically, by prepending the login node name to the address.
Login address Port Protocol Login node
----------------------- ------ ---------- ---------------------------------------------- 22 ssh round-robin DNS record for login1 and login2 22 ssh login1 22 ssh login2
The authentication is by the [private
Please verify SSH fingerprints during the first logon. They are
identical on all login nodes:<span class="monospace">
29:b3:f4:64:b0:73:f5:6f:a7:85:0f:e0:0d:be:76:bf (DSA)
d4:6f:5c:18:f4:3f:70:ef:bc:fc:cc:2b:fd:13:36:b7 (RSA)</span>
Private keys authentication:
On **Linux** or **Mac**, use
local $ ssh -i /path/to/id_rsa
If you see warning message "UNPROTECTED PRIVATE KEY FILE!", use this
command to set lower permissions to private key file.
local $ chmod 600 /path/to/id_rsa
On **Windows**, use [PuTTY ssh
After logging in, you will see the command prompt:
/ | |
/ _ __ ___ ___| |_ __ ___
/ / | '_ / __|/ _ | '_ ` _
/ ____ | | | __ __/ | | | | | |
/_/ __| |_|___/___|_|_| |_| |_|
Last loginTue Jul 9 15:57:38 2013 from
[username@login2.anselm ~]$
The environment is **not** shared between login nodes, except for
Data Transfer
Data in and out of the system may be transferred by the
[scp]( and sftp
protocols. <span class="discreet">(Not available yet.) In case large
volumes of data are transferred, use dedicated data mover node for increased performance.</span>
Address Port Protocol
-------------------------------------------------- ---------------------------------- ----------------------------------------- 22 scp, sftp 22 scp, sftp 22 scp, sftp
<span class="discreet"></span> <span class="discreet">22</span> <span class="discreet">scp, sftp</span>
 The authentication is by the [private
Data transfer rates up to **160MB/s** can be achieved with scp or sftp.
1TB may be transferred in 1:50h.
To achieve 160MB/s transfer rates, the end user must be connected by 10G
line all the way to IT4Innovations and use computer with fast processor
for the transfer. Using Gigabit ethernet connection, up to 110MB/s may
be expected.  Fast cipher (aes128-ctr) should be used.
If you experience degraded data transfer performance, consult your local
network provider.
On linux or Mac, use scp or sftp client to transfer the data to Anselm:
local $ scp -i /path/to/id_rsa my-local-file
local $ scp -i /path/to/id_rsa -r my-local-dir
> or
local $ sftp -o IdentityFile=/path/to/id_rsa
Very convenient way to transfer files in and out of the Anselm computer
is via the fuse filesystem
local $ sshfs -o IdentityFile=/path/to/id_rsa mountpoint
Using sshfs, the users Anselm home directory will be mounted on your
local computer, just like an external disk.
Learn more on ssh, scp and sshfs by reading the manpages
$ man ssh
$ man scp
$ man sshfs
On Windows, use [WinSCP
client]( to transfer
the data. The [win-sshfs
client]( provides a
way to mount the Anselm filesystems directly as an external disc.
More information about the shared file systems is available
Outgoing connections
Connection restrictions
Outgoing connections, from Anselm Cluster login nodes to the outside
world, are restricted to following ports:
Port Protocol
------ ----------
22 ssh
80 http
443 https
9418 git
Please use **ssh port forwarding** and proxy servers to connect from
Anselm to all other remote ports.
Outgoing connections, from Anselm Cluster compute nodes are restricted
to the internal network. Direct connections form compute nodes to
outside world are cut.
Port forwarding
### []()Port forwarding from login nodes
Port forwarding allows an application running on Anselm to connect to
arbitrary remote host and port.
It works by tunneling the connection from Anselm back to users
workstation and forwarding from the workstation to the remote host.
Pick some unused port on Anselm login node  (for example 6000) and
establish the port forwarding:
local $ ssh -R
In this example, we establish port forwarding between port 6000 on
Anselm and  port 1234 on the By accessing
localhost:6000 on Anselm, an application will see response of The traffic will run via users local workstation.
Port forwarding may be done **using PuTTY** as well. On the PuTTY
Configuration screen, load your Anselm configuration first. Then go to
Connection-&gt;SSH-&gt;Tunnels to set up the port forwarding. Click
Remote radio button. Insert 6000 to Source port textbox. Insert Click Add button, then Open.
Port forwarding may be established directly to the remote host. However,
this requires that user has ssh access to
$ ssh -L 6000:localhost:1234
NotePort number 6000 is chosen as an example only. Pick any free port.
### []()Port forwarding from compute nodes
Remote port forwarding from compute nodes allows applications running on
the compute nodes to access hosts outside Anselm Cluster.
First, establish the remote port forwarding form the login node, as
[described above](#port-forwarding-from-login-nodes).
Second, invoke port forwarding from the compute node to the login node.
Insert following line into your jobscript or interactive shell
$ ssh  -TN -f -L 6000:localhost:6000 login1
In this example, we assume that port forwarding from login1:6000 to has been established beforehand. By accessing
localhost:6000, an application running on a compute node will see
response of
### Using proxy servers
Port forwarding is static, each single port is mapped to a particular
port on remote host. Connection to other remote host, requires new
Applications with inbuilt proxy support, experience unlimited access to
remote hosts, via single proxy server.
To establish local proxy server on your workstation, install and run
SOCKS proxy server software. On Linux, sshd demon provides the
functionality. To establish SOCKS proxy server listening on port 1080
local $ ssh -D 1080 localhost
On Windows, install and run the free, open source [Sock
Puppet]( server.
Once the proxy server is running, establish ssh port forwarding from
Anselm to the proxy server, port 1080, exactly as [described
local $ ssh -R 6000:localhost:1080
Now, configure the applications proxy settings to **localhost:6000**.
Use port forwarding  to access the [proxy server from compute
nodes](#port-forwarding-from-compute-nodes) as well .
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment