Every group or project requires designated administrators, whether they're principal investigators (PIs) or chosen members. These administrators play a crucial role in managing encryption, onboarding, offboarding, and more.
It is recommended that PIs delegate and share these administrative responsibilities with other members of their team.
Please contact us to designate the appropriate people for the role.
Ask your PI or the designated Group/Project administrators to request an account via the ticket system at m3c-support@zdv.uni-tuebingen.de including the following information:
Once we have this information, we will create your account and notify you by email.
Afterwards you will be able to SSH into the login nodes using a command such as
ssh <your_username>@l1.m3c.uni-tuebingen.de
Information on how to execute computations on the M3 Cluster can be found in the Slurm and Storage sections.
Below are the SSH host key fingerprints of our login nodes. Please ensure you are connecting to the correct host:
l1.m3c.uni-tuebingen.de (193.196.25.97, 2001:7c0:800:1:be24:11ff:fec3:1e15) :
l2.m3c.uni-tuebingen.de (193.196.25.98, 2001:7c0:800:1:be24:11ff:feea:b380) :
Be aware that our login nodes are resource-constrained and are limited to 40G RAM and 4 CPU cores per user. You should run your calculations on the compute nodes and not on a login node.
ssh-keygen -t ed25519 -C "your_email@example.com". This command generates an SSH key with your email as the comment./home/your_username/.ssh/ folder by default and start with "id_".ssh-keygen does not support ed25519 key pairs, simply use ssh-keygen -t rsa -b 3072 -C "your_email@example.com" instead..pub extension) to yourself. Only the public part of your key, identified by the .pub extension, needs to be shared.~/.ssh/authorized_keys.~/.ssh/ , the ssh command will not find it automatically. Instead you need to specify it as an argument (e.g. ssh -i /path/to/your/private.key your_username@l1.m3c.uni-tuebingen.de - replace /path/to/your/private.key with the appropriate path on your PC) or define it permanently in the ~/.ssh/config as described below.chmod 600 /path/to/your/privat.key. If your file permissions are to open the ssh client refuses to use the key.Most Windows versions (10+11) also contain ssh-keygen . If yours does not have it, you can easily find tutorials on how to generate ssh keys by searching the web.
The process may vary slightly depending on the specific tools (e.g. PuTTYgen) or software you're using.
Should you have trouble logging in please report the complete output of
date ; ssh -v your_username@l1.m3c.uni-tuebingen.de
to m3c-support@uni-tuebingen.de.
Once you have access, you can manage your keys by inspecting the ~/.ssh/authorized_keys file.
It saves time to define aliases and permanently set parameters for your SSH connection. This can be done by inserting the following snippet into the config file ~/.ssh/config (on Windows the location is $HOME\.ssh\config) on your PC:
Host m3l1
Hostname l1.m3c.uni-tuebingen.de
Host m3l2
Hostname l2.m3c.uni-tuebingen.de
Host m3l*
User your_username
IdentityFile /path/to/your/private.key
ForwardAgent yes
If the config file does not exist yet, simply create it. Replace your_username and /path/to/our/private.key with the appropriate values for yourself. The option ForwardAgent yes enables SSH agent forwarding, allowing you to log in to compute nodes allocated by your jobs.
After modifying the config file you should be able to log in by using the aliases m3l1 and m3l2,
e.g. ssh m3l1 will be sufficient to access the first login server.
The config file can be used to configure multiple SSH connections and allows to specify a lot of other parameters. See man ssh_config or search for more information online.