Page tree
Skip to end of metadata
Go to start of metadata

Prerequisites to connect to SCITAS clusters:

Our clusters

The clusters are accessible via SSH at the following addresses:

Step-by-step guide

  1. Log to a cluster using your GASPAR username and password as follows:

    ssh -X <myusername>@<mypreferedcluster>

    SSH clients

    SSH clients are available by default on MacOS X and Linux. For windows, we recommend Git BashPuTTY or  MobaXterm.

  2. Once logged in, you have access to your home directory at /home/<username>.  

    Your home directory is the same on all SCITAS clusters, and is limited by a quota of 100GB per user. Home files are backed up every night. This means that important files like source code, consolidated simulation results, etc should go here. 

  3. On each cluster, you have also access to a private scratch directory at /scratch/<username>.

    Scratch file systems are local to each cluster and are fast. This is typically where raw results, checkpoints, large temporary datasets will go. Scratch files are not backed up and files older than two weeks are subject to automatic deletion by a daily cleanup procedure.

Please note that from outside the EPFL network you will need to connect to the VPN



A SSH server is identified by a key which is used to derive the security of the connection. A fingerprint of the key is kept on the SSH client at the first login and compared at every consequent logins. If the key changes after some time, the SSH client refuses to connect and you see this error. It's required from you that you check that the server you're connecting to is legit and you're not being hacked. Usually it means contacting the server administrator to ask for the new key fingerprint. You can then proceed by removing the old offending key from your ~/.ssh/know_hosts file and connect again. You'll be asked to accept the new key fingerprint.

Check the current fingerprint, against the list you can find bellow:

ssh-keygen -F -l

If the fingerprint doesn't match, remove the offending key (in this example for

ssh-keygen -R

Here's the list of fingerprints for our cluster frontends:

RSA      SHA256:/jlWbXG/gt8H/BmJzEA1V7bsiw7S5/osbasbNICsIuw  MD5:27:05:8d:d3:9e:dd:fc:66:40:8b:0d:fc:18:e7:9d:9b
ECDSA    SHA256:aczEF2Rvlvhbc0pCxTnNxRwbiiAy/uPPixTp3QYf19E  MD5:e7:63:59:d6:35:0a:bb:c1:63:37:dd:92:76:3f:7a:3b
ED25519  SHA256:QB7ocpnEQrS8nbU3VtjGOtIP3PAs6MSVaED0imOJhJk  MD5:6a:9f:6e:9d:46:c8:da:2d:18:29:b6:80:18:ed:a8:69
DSA      SHA256:HvbcrjP3X29Bn0g1OgXB+vHLEjWuSWvoaf/vLdZoe/Q  MD5:7a:a0:c8:f2:e9:2d:7f:e7:66:69:4a:d3:b8:dd:22:bd
ECDSA    SHA256:mLntSNT2Rz69Nba7jOyWt6r+kwF4zpmZZlyrRGfRgXw  MD5:5a:c4:54:4d:c5:44:9c:f5:10:1d:e8:17:09:ab:27:4e
ED25519  SHA256:JPhzMzsmR4Zkb2tBaWsIGA0kLV5VLzpSeT6VLRd9HWI  MD5:1d:19:a2:fc:23:63:1a:55:17:55:c2:66:f6:df:c7:7d
RSA      SHA256:mqLUyQMqKNzC8b+HgBPvf3QRnojeZWFJNWHCt7dE1FM  MD5:2f:d3:37:32:88:4f:e6:70:29:15:d8:48:10:b4:d5:1f
DSA       SHA256:jjg2UsZi+5vn4JVSHhHO+8nCbJe+PYeus5oXDy5HrIg  MD5:59:d4:c1:a0:97:bc:90:ae:69:46:af:03:41:3c:3b:5b
ECDSA     SHA256:/4HY5EVScDLu/Btzr0Rr7b+G9vcZtqp2a3P6NoH5Ey4  MD5:95:76:2b:0d:10:ad:2d:be:ca:cd:8e:37:3b:f5:56:3f
ED25519   SHA256:fUxBEzD/f9VKiEzApNQQ6bs2p/9d1vUcYeplHrzNVfc  MD5:f0:03:14:d8:6c:a0:66:61:b9:65:18:04:b2:5a:27:ef
RSA       SHA256:NbpSOygH72m2b4xb4bptwv0of8RXhHiYMJeuUsG4hcA  MD5:b8:02:e0:27:8b:75:ce:9a:3f:5a:78:18:de:7e:3a:15
DSA      SHA256:jjg2UsZi+5vn4JVSHhHO+8nCbJe+PYeus5oXDy5HrIg  MD5:59:d4:c1:a0:97:bc:90:ae:69:46:af:03:41:3c:3b:5b
ECDSA    SHA256:kYv/aUHBYR1v7NUGDqieMEET9EcB3Uk4CDVSaTuoJ5c  MD5:b6:53:ec:b0:a8:aa:a9:8c:76:e5:f0:ac:d5:8d:88:11
ED25519  SHA256:R/BxGi0pIlW9s7o2xNOcxcHuo4fneu+hWAghR1nimDo  MD5:04:f6:b9:f1:77:b2:a6:c3:28:7c:ac:b0:30:93:59:4c
RSA      SHA256:NbpSOygH72m2b4xb4bptwv0of8RXhHiYMJeuUsG4hcA  MD5:b8:02:e0:27:8b:75:ce:9a:3f:5a:78:18:de:7e:3a:15