Helix/Login
 |
Access to bwForCluster Helix is only possible from IP addresses within the BelWü network which connects universities and other scientific institutions in Baden-Württemberg. If your computer is in your University network (e.g. at your office), you should be able to connect to bwForCluster Helix without restrictions. If you are outside the BelWü network (e.g. at home), a VPN (virtual private network) connection to your University network must be established first. Please consult the VPN documentation of your University. |
Prerequisites for successful login:
You need to have
- completed the 3-step bwForCluster registration procedure.
- set a service password for bwForCluster Helix.
- registered a token for the two factor authentication (2FA).
Login
Login to bwForCluster Helix is only possible with a Secure Shell (SSH) client for which you must know your username on the cluster and a hostname of the login nodes. For a more detailed information on SSH clients, visit the SSH clients Wiki page.
Username
Your username on bwForCluster Helix consists of a prefix and your local username. For prefixes please refer to the Username Wiki page.
Example: If your local username at your University is ab123 and you are a user from Heidelberg University, your username on the cluster is: hd_ab123.
Hostnames
bwForCluster Helix has two login nodes. We use so-called DNS round-robin scheduling to load-balance the incoming connections between the nodes. If you open multiple SSH sessions, these sessions may run on different login nodes, so processes started in one session might not be visible in other sessions.
| Hostname | Node type |
|---|---|
| helix.bwservices.uni-heidelberg.de | login to one of the two login nodes |
Login with SSH command (Linux, Mac, Windows)
Most Unix and Unix-like operating systems like Linux or MacOS come with a built-in SSH client provided by the OpenSSH project. More recent versions of Windows 10 and Windows 11 using the Windows Subsystem for Linux (WSL) also come with a built-in OpenSSH client.
For login use one of the following commands:
ssh <username>@helix.bwservices.uni-heidelberg.de ssh -l <username> helix.bwservices.uni-heidelberg.de
To run graphical applications, you need to enable X11 forwarding with the -X flag:
ssh -X -l <username> helix.bwservices.uni-heidelberg.de
Login with graphical SSH client (Windows)
For Windows we suggest using MobaXterm for login and file transfer.
Start MobaXterm and fill in the following fields:
Remote name : helix.bwservices.uni-heidelberg.de Specify user name : <username> Port : 22
After that click on 'ok'. Then a terminal will open where you can enter your credentials.
Login Example
To login to bwForCluster Helix, proceed as follows:
- Login with SSH command or MoabXterm as shown above.
- The system will ask for a one-time password
Your OTP:. Please enter your OTP and confirm it with Enter/Return. The OTP is not displayed when typing. If you do not have a second factor yet, please create one (see Registration/2FA). - The system will ask you for your service password
Password:. Please enter it and confirm it with Enter/Return. The password is not displayed when typing. If you do not have a service password yet or have forgotten it, please create one (see Registration/Password). - You will be greeted by the cluster, followed by a shell.
$ ssh -l hd_ab123 helix.bwservices.uni-heidelberg.de Your OTP: Password:
Allowed Activities on Login Nodes
|
|
To guarantee usability for all users you must not run your compute jobs on the login nodes. Compute jobs must be submitted as batch jobs. Any compute job running on the login nodes will be terminated without notice. Any long-running compilation or any long-running pre- or post-processing of batch jobs must also be submitted to batch system. |
The login nodes are the access points to the compute system, your $HOME directory and your workspaces.
These nodes are shared with all users. Therefore, your activities on the login nodes are limited to primarily set up your batch jobs.
Your activities may also be:
- short compilation of your program code
- short pre- and post-processing of your batch jobs.
We advise users to use interactive jobs for compute and memory intensive tasks like compiling.
Password Reset
See Password Guide.
De-registration
SSH Keys
In contrast to many other HPC systems it is no longer possible to self-manage your SSH Keys by adding them to the ~/.ssh/authorized_keys file. Existing files will no longer be evaluated. SSH Keys have to be managed via bwServices instead. Please refer to the user guide for this functionality: