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 imperative that PIs take the initiative to assign these administrative responsibilities to competent individuals within the team, including themselves if necessary.
Contact us today to designate the appropriate individual for the role, ensuring seamless operation and organization within your project or group.
Please request your PI or the designated Group/Project Administrators to provide us with the following through the ticket system at m3c-support@zdv.uni-tuebingen.de:
Once we have this information, we will create an account for you. You will be informed by email, and then you will be able to SSH into the login nodes using a command such as ssh your_username@l1.m3c.uni-tuebingen.de.
Here are the fingerprints of our login nodes SSH host keys. Please ensure you are connecting to the right 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) :
To better comprehend how to execute your computations in M3C, please refer to the Slurm and storage sections.
Be aware that 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 node, not the 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.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 ofdate ; 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 could be timesaving to permanently set parameters for your SSH connection and define aliases. This can be done by inserting the following into ~/.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 yesReplace your_username and /path/to/our/private.key with the appropriate values for yourself.
Afterwards you should be able to login by using the aliases m3l1 and m3l2, e.g. ssh m3l1 will be sufficient to login to our first login server.
If ~/.ssh/config does not exist yet, simply create it.ForwardAgent yes enables SSH agent forwarding, allowing you to log in to allocated compute nodes for your jobs from the login nodes.
It can be used to configure all ssh connections and allows to specify a lot of other parameters. See man ssh_config or search for more information online.
On Windows the config file location is $HOME\.ssh\config. If the .ssh folder doesnt exist yet simply create it.