Helix/Login: Difference between revisions

From bwHPC Wiki
Jump to navigation Jump to search
 
(51 intermediate revisions by 2 users not shown)
Line 15: Line 15:
* registered a token for the [[Registration/2FA|two factor authentication (2FA)]].
* registered a token for the [[Registration/2FA|two factor authentication (2FA)]].



Access 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.
= Login to bwForCluster Helix =

Login to bwForCluster Helix is only possible with a Secure Shell (SSH) client for which you must know your username on the cluster and the hostname of the login nodes.
For more gneral information on SSH clients, visit the [[Registration/Login/Client|SSH clients Guide]].


== Username ==
== Username ==


Your username on bwForCluster Helix consists of a prefix and your local username.
Your username on bwForCluster Helix consists of a prefix and your local username.
For prefixes please refer to the [[Registration/Login/Username|'''Username Wiki''']].
For prefixes please refer to the [[Registration/Login/Username|Username Guide]].


Example: If your local username at your University is <code>ab123</code> and you are a user from Heidelberg University, your username on the cluster is: <code>hd_ab123</code>.
Example: If your local username at your University is <code>ab123</code> and you are a user from Heidelberg University, your username on the cluster is: <code>hd_ab123</code>.
Line 26: Line 30:
== Hostnames ==
== Hostnames ==


The system has two login nodes and 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 be established to different login nodes, so processes started in one session might not be visible in other sessions.
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.


{| class="wikitable"
{| class="wikitable"
! Hostname !! Node type
! Hostname !! Destination
|-
|-
| '''helix.bwservices.uni-heidelberg.de''' || login to one of the two login nodes
| '''helix.bwservices.uni-heidelberg.de''' || one of the two login nodes
|}
|}


== Login with SSH command (Linux, Mac, Windows) ==
== SSH Clients ==


Most Unix and Unix-like operating systems like Linux or MacOS come with a built-in SSH client provided by the OpenSSH project.
For a more detailed information on SSH clients, visit the [[Registration/Login/Client|SSH clients Wiki page]].
More recent versions of Windows 10 and Windows 11 using the [https://docs.microsoft.com/en-us/windows/wsl/install Windows Subsystem for Linux] (WSL) also come with a built-in OpenSSH client.


For login use one of the following ssh commands:
== Login from Linux or Mac ==

Most Unix and Unix-like operating systems like Linux or MacOS come with a built-in SSH client provided by the OpenSSH project.


ssh <username>@helix.bwservices.uni-heidelberg.de
ssh <username>@helix.bwservices.uni-heidelberg.de
ssh -l <username> helix.bwservices.uni-heidelberg.de
ssh -l <username> helix.bwservices.uni-heidelberg.de


To run graphical applications, you can use the <code>-X</code> or <code>-Y</code> flag to <code>ssh</code>:
To run graphical applications on the cluster, you need to enable X11 forwarding with the <code>-X</code> flag:


ssh -Y -l <username> helix.bwservices.uni-heidelberg.de
ssh -X -l <username> helix.bwservices.uni-heidelberg.de


== Login from Windows ==
== Login with graphical SSH client (Windows) ==


For Windows we suggest using MobaXterm for login and file transfer.
For Windows we suggest using MobaXterm for login and file transfer.
More recent versions of Windows 10 and Windows 11 using the [https://docs.microsoft.com/en-us/windows/wsl/install Windows Subsystem for Linux] (WSL) also come with a built-in OpenSSH client.
After installing a linux system with WSL use the instructions for linux.
Start ''MobaXterm'', fill in the following fields:
Start MobaXterm and fill in the following fields:
<pre>
<pre>
Remote name : helix.bwservices.uni-heidelberg.de
Remote name : helix.bwservices.uni-heidelberg.de
Line 63: Line 64:


After that click on 'ok'. Then a terminal will open where you can enter your credentials.
After that click on 'ok'. Then a terminal will open where you can enter your credentials.

'''Note''': When using File transfer with MobaXterm version >=23.3, the following configuration change has to be made: In the settings in the tab "SSH", change the option "SSH engine" from "<new>" to "<legacy>". Then restart MobaXterm.


== Login Example ==
== Login Example ==


To log into bwForCluster Helix, you must provide your [[Registration/Password|service password]].
To login to bwForCluster Helix, proceed as follows:
# Login with SSH command or MoabXterm as shown above.
Proceed as follows:
# Use an SSH client as shown above.
# The system will ask for a one-time password <code>Your OTP:</code>. 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 for a one-time password <code>Your OTP:</code>. 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 <code>Password:</code>. 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]]).
# The system will ask you for your service password <code>Password:</code>. 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]]).
Line 76: Line 78:
Your OTP:
Your OTP:
Password:
Password:

********************************************************************************
* *
* Baden-Wuerttemberg HPC Cluster for *
* Structural and Systems Biology, Medical Science, *
* Soft Matter, Computational Humanities, and *
* Mathematics and Computer Science *
* *
* bwForCluster *
* _ _ _ _ *
* | | | | | | (_) *
* | |__| | ___ | | _ __ __ *
* | __ | / _ \ | | | | \ \/ / *
* | | | | | __/ | | | | > < *
* |_| |_| \___| |_| |_| /_/\_\ *
* *
* *
* (xCAT 2.16.4 / RHEL 8.8 / GPFS 5.1.8) *
* *
* *
* bwHPC Wiki : https://wiki.bwhpc.de/e/Helix *
* Ticket System : https://www.bwhpc.de/supportportal *
* Job Monitoring : https://helix-monitoring.bwservices.uni-heidelberg.de *
* E-learning : https://training.bwhpc.de/ *
* -> 'Introduction to bwForCluster Helix' *
* *
********************************************************************************

Last login: ...
[hd_ab123@login ~]$
</pre>
</pre>


== Allowed Activities on Login Nodes ==
= Allowed Activities on Login Nodes =


{|style="background:#deffee; width:100%;"
{|style="background:#deffee; width:100%;"
Line 84: Line 116:
[[Image:Attention.svg|center|25px]]
[[Image:Attention.svg|center|25px]]
|style="padding:5px; background:#cef2e0; text-align:left"|
|style="padding:5px; background:#cef2e0; text-align:left"|
To guarantee usability for all the users of clusters you must not run your compute jobs on the login nodes.
To guarantee usability for all users you must not run your compute jobs on the login nodes.
Compute jobs must be submitted to the queuing system.
Compute jobs must be submitted as batch jobs.
Any compute job running on the login nodes will be terminated without any notice.
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 the queuing system.
Long-running compilation or long-running pre- or post-processing tasks must also be submitted as batch jobs.
|}
|}


The login nodes of the bwHPC clusters are the access point to the compute system, your <code>$HOME</code> directory and your workspaces.
The login nodes are the access points to the compute system, your <code>$HOME</code> directory and your workspaces.
These nodes are shared with all the users therefore, your activities on the login nodes are limited to primarily set up your batch jobs.
These nodes are shared with all users. Hence, your activities on the login nodes are primarily limited to setting up your batch jobs.
Your activities may also be:
Your activities may also be:
* '''short''' compilation of your program code and
* quick compilation of program code or
* '''short''' pre- and post-processing of your batch jobs.
* quick pre- and post-processing of results from batch jobs.

We advise users to use [[Helix/Slurm#Interactive_Jobs|interactive jobs]] for compute and memory intensive tasks like compiling.

= Password Reset =

See [[Registration/Password|Password Guide]].

= De-registration =

See [[Registration/Deregistration|De-registration Guide]].

= 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:

* [[Registration/SSH|Registering SSH Keys with your Cluster]]

== Login to bwForCluster Helix ==

After registration bwForCluster Helix can be accessed via Secure Shell (SSH). Only SSH is allowed for login.

From Linux machines, you can log in using the following command:

<code> ssh <UserID>@helix.bwservices.uni-heidelberg.de</code>

To run graphical applications, you need to enable X11 forwarding with the -X option:

<code> ssh -X <UserID>@helix.bwservices.uni-heidelberg.de</code>

For SSH client programs with graphical user interfaces, fill in UserID and login server name accordingly. For Windows you can use [https://www.putty.org/ PuTTY] or [https://mobaxterm.mobatek.net/ MobaXterm]. The later comes with an integrated X11 server which is necessary for the work with graphical applications.

The bwForCluster Helix has serveral login nodes. The selection of the login node is done automatically. If you log in multiple times, different sessions might run on different login nodes. In general, you should use the generic hostname given above to allow us to balance the load over the login nodes.


We advise to use [[Helix/Slurm#Interactive_Jobs|interactive batch jobs]] for compute and memory intensive compilation and pre- and post-processing tasks.
== Allowed activities on login nodes ==


= Related Information =
The login nodes are the access point to the compute system and to your $HOME directory. The login nodes are shared with all the users of the cluster. Therefore, your activities on the login nodes are limited to primarily set up your batch jobs. Your activities may also be:
* compilation of your program code and
* short pre- and postprocessing of your batch jobs.


* If you want to reset your service password, consult the [[Registration/Password|Password Guide]].
To guarantee usability for all the users of the bwForCluster 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.
* If you want to register a new token for the two factor authentication (2FA), consult the [[Registration/2FA|2FA Guide]].
* If you want to de-register, consult the [[Registration/Deregistration|De-registration Guide]].
* If you need an SSH key for your workflow, read [[Registration/SSH|Registering SSH Keys with your Cluster]].
* Configuring your shell: [[.bashrc Do's and Don'ts]]

Latest revision as of 11:55, 5 November 2024

Attention.svg

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


Login to bwForCluster Helix

Login to bwForCluster Helix is only possible with a Secure Shell (SSH) client for which you must know your username on the cluster and the hostname of the login nodes. For more gneral information on SSH clients, visit the SSH clients Guide.

Username

Your username on bwForCluster Helix consists of a prefix and your local username. For prefixes please refer to the Username Guide.

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 Destination
helix.bwservices.uni-heidelberg.de 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 ssh commands:

ssh <username>@helix.bwservices.uni-heidelberg.de
ssh -l <username> helix.bwservices.uni-heidelberg.de

To run graphical applications on the cluster, 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.

Note: When using File transfer with MobaXterm version >=23.3, the following configuration change has to be made: In the settings in the tab "SSH", change the option "SSH engine" from "<new>" to "<legacy>". Then restart MobaXterm.

Login Example

To login to bwForCluster Helix, proceed as follows:

  1. Login with SSH command or MoabXterm as shown above.
  2. 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).
  3. 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).
  4. You will be greeted by the cluster, followed by a shell.
$ ssh -l hd_ab123 helix.bwservices.uni-heidelberg.de
Your OTP:
Password: 

********************************************************************************
*                                                                              *
*                     Baden-Wuerttemberg HPC Cluster for                       *
*              Structural and Systems Biology, Medical Science,                *
*                 Soft Matter, Computational Humanities, and                   *
*                      Mathematics and Computer Science                        *
*                                                                              *
*                                bwForCluster                                  *
*                        _    _          _   _                                 *
*                       | |  | |        | | (_)                                *
*                       | |__| |   ___  | |  _  __  __                         *
*                       |  __  |  / _ \ | | | | \ \/ /                         *
*                       | |  | | |  __/ | | | |  >  <                          *
*                       |_|  |_|  \___| |_| |_| /_/\_\                         *
*                                                                              *
*                                                                              *
*                   (xCAT 2.16.4 / RHEL 8.8 / GPFS 5.1.8)                      *
*                                                                              *
*                                                                              *
*        bwHPC Wiki : https://wiki.bwhpc.de/e/Helix                            *
*     Ticket System : https://www.bwhpc.de/supportportal                       *
*    Job Monitoring : https://helix-monitoring.bwservices.uni-heidelberg.de    *
*        E-learning : https://training.bwhpc.de/                               *
*                     -> 'Introduction to bwForCluster Helix'                  *
*                                                                              *
********************************************************************************

Last login: ...
[hd_ab123@login ~]$ 

Allowed Activities on Login Nodes

Attention.svg

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. Long-running compilation or long-running pre- or post-processing tasks must also be submitted as batch jobs.

The login nodes are the access points to the compute system, your $HOME directory and your workspaces. These nodes are shared with all users. Hence, your activities on the login nodes are primarily limited to setting up your batch jobs. Your activities may also be:

  • quick compilation of program code or
  • quick pre- and post-processing of results from batch jobs.

We advise to use interactive batch jobs for compute and memory intensive compilation and pre- and post-processing tasks.

Related Information