BinAC/Login: Difference between revisions

From bwHPC Wiki
Jump to navigation Jump to search
No edit summary
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
= Login =

After registration (registration procedure at [[bwForCluster User Access]], the bwForCluster BinAC can be accessed via a Secure Shell like <tt>ssh</tt> on Linux and Mac or <tt>PuTTY</tt> on Windows systems.

{|style="background:#deffee; width:100%;"
{|style="background:#deffee; width:100%;"
|style="padding:5px; background:#cef2e0; text-align:left"|
|style="padding:5px; background:#cef2e0; text-align:left"|
[[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"|
Access to bwForCluster BinAC is only possible from IP addresses within the [https://www.belwue.de BelWü] network which connects universities and other scientific institutions in Baden-Württemberg.
Login is only possible through university networks! If you're at home or abroad, you will need to use your university's VPN.
If your computer is in your University network (e.g. at your office), you should be able to connect to bwForCluster BinAC 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 [[registration/bwForCluster|bwForCluster registration]] procedure.
* [[Registration/Password|set a service password]] for bwForCluster BinAC.
* Setup the [[BinAC/Login#TOTP_Second_Factor|two factor authentication (2FA)]].


= Login to bwForCluster BinAC =


== TOTP Second Factor ==
== TOTP Second Factor ==
Line 22: Line 30:
Your authenticator app now displays a 6-digit number which changes every 30 seconds, representing the second factor required for the login to BinAC.
Your authenticator app now displays a 6-digit number which changes every 30 seconds, representing the second factor required for the login to BinAC.


If you have a new smartphone and cannot migrate your OTP data from the old to the new device, you will have to [[BinAC/Support|open a ticket]]. We will then reset your OTP and you can create a new QR code.
== Login ==
You may use the nodes login01.binac.uni-tuebingen.de and login02.binac.uni-tuebingen.de to access the BinAC e.g.


Login to bwForCluster BinAC 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.
<pre>
For more gneral information on SSH clients, visit the [[Registration/Login/Client|SSH clients Guide]].
ssh <UserID>@login01.binac.uni-tuebingen.de # or
ssh <UserID>@login02.binac.uni-tuebingen.de # or
ssh <UserID>@login03.binac.uni-tuebingen.de
</pre>


== Username ==
You will be asked for the 6-digit second factor and afterwards for your password.
If you mistype the password after entering the correct 6-digit second factor you have to wait for 30 seconds till a new second factor is generated, as it is truly a time-based one-time password and cannot be used again.


Your username on bwForCluster BinAC consists of a prefix and your local username.
== SSH Keys (optional) ==
For prefixes please refer to the [[Registration/Login/Username|Username Guide]].
You may use SSH keys to access the login nodes. It is mandatory to secure your private key with a password. Place your public key into ~/.ssh/authorized_keys and take care about line breaks.
If you are using services which require automated password less login, contact us hpcmaster@uni-tuebingen.de. We are working on appropriate solutions and will adopt them individually.


Example: If your local username at your University is <code>ab123</code> and you are a user from Tübingen University, your username on the cluster is: <code>tu_ab123</code>.
== About UserID / Username ==


== Hostnames ==
<UserID> of the ssh command is a placeholder for your username at your home organization and a prefix denoting your organization. Prefixes and resulting user names are as follows:


bwForCluster BinAC has three login nodes.
{| style="border:3px solid darkgray; margin: 5em auto 5em auto;" width="60%"

|-
{| class="wikitable"
!scope="row" {{Darkgray}} | Site
! Hostname !! Destination
!scope="row" {{Darkgray}}| Prefix
!scope="row" {{Darkgray}}| Username
|-
| Freiburg
| fr
| fr_username
|-
|-
| login01.binac.uni-tuebingen.de || login node 01
|Heidelberg
|hd
|hd_username
|-
|-
| login02.binac.uni-tuebingen.de || login node 02
|Hohenheim
|ho
|ho_username
|-
|-
| login03.binac.uni-tuebingen.de || login node 03
|Karlsruhe
|ka
|ka_username
|-
|-
|Konstanz
|kn
|kn_username
|-
|Mannheim
|ma
|ma_username
|-
|Stuttgart
|st
|st_username
|-
|Tübingen
|tu
|tu_username
|-
|Ulm
|ul
|ul_username
|}
|}


== Login with SSH command (Linux, Mac, Windows) ==
== Allowed activities on login nodes ==


Most Unix and Unix-like operating systems like Linux or MacOS come with a built-in SSH client provided by the OpenSSH project.
The login nodes are the access point to the compute system and its $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:
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.
* compilation of your program code and
* short pre- and postprocessing of your batch jobs.


For login use one of the following ssh commands:
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 any notice.


ssh <username>@login01.binac.uni-tuebingen.de


To run graphical applications on the cluster, you need to enable X11 forwarding with the <code>-X</code> flag:
= Password Reset =

ssh -X <username>@login01.binac.uni-tuebingen.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:
<pre>
Remote name : login01.binac.uni-tuebingen.de
Specify user name : <username>
Port : 22
</pre>

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

== Login Example ==

To login to bwForCluster BinAC, proceed as follows:
# Login with SSH command or MoabXterm as shown above.
# The system will ask for a one-time password <code>One-time password (OATH) for <username></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 [BinAC/Login#TOTP_Second_Factor]]).
# 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]]).
# You will be greeted by the cluster, followed by a shell.
<pre>
$ ssh tu_ab123@login01.binac.uni-tuebingen.de
One-time password (OATH) for tu_ab123:
Password:

Last login: ...

bwFOR Cluster BinAC, Bioinformatics and Astrophysics

------------------------------------------------------------------------------

please submit jobs solely with the 'qsub' command. Available queues are
tiny - 20min - fast queue for testing (four GPU cores available)
short - 48hrs - serial/parallel jobs
long - 7days - serial/parallel jobs
gpu - 30days - GPU-only jobs
smp - 7days - large SMP jobs ( memory > 128GB/node )

The COMPUTE and GPU nodes provide 28 cores and 128GB of RAM each. In
addition, every GPU node is equipped with 2 Nvidia K80 accelerator cards,
totalling in 4 GPUs per node. The SMP machines provide 40 cores per node
and 1 TB of RAM.

A local SCRATCH directory (/scratch) is available on each node. A fast,
parallel WORK file system is mounted on /beegfs/work. Please also use the
workspace tools.

Register to our BinAC mailing list via
https://listserv.uni-tuebingen.de/mailman/listinfo/binac_announce

------------------------------------------------------------------------------
Please do not keep data on WORK for a prolonged time. If rarely needed and
while working on a project, please compress files to an archive.
------------------------------------------------------------------------------


[tu_ab123@login01 ~]$

</pre>

= Allowed Activities on Login Nodes =

{|style="background:#deffee; width:100%;"
|style="padding:5px; background:#cef2e0; text-align:left"|
[[Image:Attention.svg|center|25px]]
|style="padding:5px; background:#cef2e0; text-align:left"|
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 <code>$HOME</code> directory and your workspaces.
If you forgot your password for the bwForCluster BinAC you can set a new one on the [https://bwservices.uni-tuebingen.de BinAC service page]. Just use the link in the "bwForCluster BinAC" service box.
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.
= Further reading =


= Related Information =
* Scientific software is made accessible using the [[Environment Modules]] system


* If you want to reset your service password, consult the [[Registration/Password|Password Guide]].
* Compute jobs must be submitted as [[Batch Jobs]]
* If you want to register a new token for the two factor authentication (2FA), consult [[BinAC/Login#TOTP_Second_Factor|this section]].
* If you want to de-register, consult the [[Registration/Deregistration|De-registration Guide]].
* Configuring your shell: [[.bashrc Do's and Don'ts]]
<!--* If you need an SSH key for your workflow, read [[Registration/SSH|Registering SSH Keys with your Cluster]].-->

Latest revision as of 11:55, 5 November 2024

Attention.svg

Access to bwForCluster BinAC 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 BinAC 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 BinAC

TOTP Second Factor

Install a TOTP (time-based one-time password) app to your mobile device such as Google, Microsoft, andOTP, Aegis, FreeOTP, or Yubico Authenticator. These apps work very similar and allow you to scan a QR code containing a secret key used for the TOTP password generation.

Connect to the QR code server and enter your password. 

ssh <UserID>@c2fa.binac.uni-tuebingen.de

The QR code displayed on screen must be scanned with your authenticator app. Note, the QR code is only displayed once. If you need a new QR code , please contact us (hpcmaster@uni-tuebingen.de) to reset the procedure. Your authenticator app now displays a 6-digit number which changes every 30 seconds, representing the second factor required for the login to BinAC.

If you have a new smartphone and cannot migrate your OTP data from the old to the new device, you will have to open a ticket. We will then reset your OTP and you can create a new QR code.

Login to bwForCluster BinAC 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 BinAC 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 Tübingen University, your username on the cluster is: tu_ab123.

Hostnames

bwForCluster BinAC has three login nodes.

Hostname Destination
login01.binac.uni-tuebingen.de login node 01
login02.binac.uni-tuebingen.de login node 02
login03.binac.uni-tuebingen.de login node 03

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>@login01.binac.uni-tuebingen.de

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

ssh -X <username>@login01.binac.uni-tuebingen.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              : login01.binac.uni-tuebingen.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 BinAC, proceed as follows:

  1. Login with SSH command or MoabXterm as shown above.
  2. The system will ask for a one-time password One-time password (OATH) for <username>. 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 [BinAC/Login#TOTP_Second_Factor]]).
  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 tu_ab123@login01.binac.uni-tuebingen.de
One-time password (OATH) for tu_ab123:
Password: 

Last login: ...

          bwFOR Cluster BinAC, Bioinformatics and Astrophysics 

------------------------------------------------------------------------------

please submit jobs solely with the 'qsub' command. Available queues are
 
    tiny  - 20min     - fast queue for testing (four GPU cores available) 
    short - 48hrs     - serial/parallel jobs
    long  - 7days     - serial/parallel jobs
    gpu   - 30days    - GPU-only jobs  
    smp   - 7days     - large SMP jobs ( memory > 128GB/node ) 

The COMPUTE and GPU nodes provide 28 cores and 128GB of RAM each. In 
addition, every GPU node is equipped with 2 Nvidia K80 accelerator cards, 
totalling in 4 GPUs per node. The SMP machines provide 40 cores per node 
and 1 TB of RAM.

A local SCRATCH directory (/scratch) is available on each node. A fast, 
parallel WORK file system is mounted on /beegfs/work. Please also use the 
workspace tools.

Register to our BinAC mailing list via 
https://listserv.uni-tuebingen.de/mailman/listinfo/binac_announce

------------------------------------------------------------------------------
   Please do not keep data on WORK for a prolonged time. If rarely needed and
   while working on a project, please compress files to an archive. 
------------------------------------------------------------------------------


[tu_ab123@login01 ~]$

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

Retrieved from "https://wiki.bwhpc.de/wiki/index.php?title=BinAC/Login&oldid=13151"