NEMO/Login

From bwHPC Wiki
Jump to navigation Jump to search
Attention.svg

Access to NEMO is limited to IP addresses from the BelWü network. All home institutions of our current users are connected to BelWü, so if you are on your campus network (e.g. in your office or on the campus WiFi) you should be able to connect to NEMO without restrictions. If you are outside one of the BelWü networks (e.g. at home), a VPN connection to the home institution or a connection to an SSH jump host at the home institution must be established first.

The login nodes of the bwHPC clusters are the access point to the compute system, your $HOME directory and your workspaces. All users must log in through these nodes to submit jobs to the cluster.

Prerequisites for successful login:

You need to have

Attention.svg

The NEMO registration continues to use the old registration page https://bwservices.uni-freiburg.de, while the second factor (2FA) must be configured on the new registration page https://login.bwidm.de. https://login.bwidm.de is not used for anything else so far!


Login to bwForCluster NEMO

Login to bwForCluster NEMO 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 general information on SSH clients, visit the SSH clients Guide.

Username

If you want to use the NEMO cluster you need to add a prefix to your local username. For prefixes please refer to the Username Wiki.

Example:

  • If your local username for the University is vwxyz1234 and you are a user from the University of Freiburg this would combine to: fr_vwxyz1234.


Hostnames

The system has two login nodes. You have to select the login node yourself.

Hostname Node type
login.nemo.uni-freiburg.de NEMO first login node alias
login1.nemo.uni-freiburg.de NEMO first login node
login2.nemo.uni-freiburg.de NEMO second login node


Login with SSH command (Linux, Mac, Windows)

Most Unix and Unix-like operating systems such as Linux, Mac OS, and *BSD, as well as newer versions of MS Windows 10 and 11, have a built-in SSH client provided by the OpenSSH project. If you want to use the full set of Linux commands on Windows, you can also install the Windows Subsystem for Linux (WSL) on newer Windows 10 and 11 versions very easily. Then start a terminal, e.g. "xterm", "konsole" or "gnome-terminal" under Linux, the "Terminal" app under Mac OS or under Windows the "Terminal" app (command: 'cmd') or "PowerShell".

For login use one of the following ssh commands:

ssh <username>@login.nemo.uni-freiburg.de
ssh -l <username> login.nemo.uni-freiburg.de

To run graphical applications, you can use the -X or -Y flag to ssh:

ssh -Y -l <username> login.nemo.uni-freiburg.de

For better graphical performance, we recommend using the VNC module on the cluster: 'module load vis/turbovnc'.

Login with graphical SSH client (Windows)

For Windows we suggest using MobaXterm for login and file transfer.

Start MobaXterm, fill in the following fields:

Remote name              : login.nemo.uni-freiburg.de    # or login1.nemo.uni-freiburg.de, login2.nemo.uni-freiburg.de
Specify user name        : <username>
Port                     : 22

After that click on 'ok'. Then a terminal will be opened and there you can enter your credentials.

Login Example

To log in to NEMO, you must provide your service password. Proceed as follows:

  1. Use SSH for a login node.
  2. When you log in for the first time, you must confirm the SSH fingerprint of the login node.
  3. The system will ask you for your service password Password:. Please enter it and confirm it with Enter/Return. 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 fr_vwxyz1234@login.nemo.uni-freiburg.de

The authenticity of host 'login.nemo.uni-freiburg.de (132.230.222.12)' can't be established.
ED25519 key fingerprint is SHA256:JDP0H4SjxdnkfYOVpP09xRHAlvB3GCGhAJVMZAmQX5M.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'login.nemo.uni-freiburg.de' (ED25519) to the list of known hosts.

fr_vwxyz1234@login.nemo.uni-freiburg.de's password: 

Last login: Thu Sep  8 16:01:18 2022 from host1.nemo.uni-freiburg.de

                     Research Cluster Baden Wuerttemberg
                                 bwForCluster

           ooooo      ooo oooooooooooo ooo        ooooo   .oooooo.
           `888b.     `8' `888'     `8 `88.       .888'  d8P'  `Y8b
            8 `88b.    8   888          888b     d'888  888      888
            8   `88b.  8   888oooo8     8 Y88. .P  888  888      888
            8     `88b.8   888    "     8  `888'   888  888      888
            8       `888   888       o  8    Y     888  `88b    d88'
           o8o        `8  o888ooooood8 o8o        o888o  `Y8bood8P'

            Neuroscience   Elementary   Microsystems   Materials
                               Particle     Engineering     Science
                                   Physics

--------------------------------------------------------------------------------
 Node            : login1.nemo.uni-freiburg.de 
 OS              : CentOS 7.9 (Rev. 23), 3.10.0-1160.76.1
--------------------------------------------------------------------------------
 NEMO Info       : http://www.nemo.uni-freiburg.de
 NEMO Status     : http://www.nemo.uni-freiburg.de/nemo/stat/
 NEMO Support    : http://www.nemo.uni-freiburg.de/support/
 NEMO News       : http://www.nemo.uni-freiburg.de/news/
 Central Wiki    : http://wiki.bwhpc.de

--------------------------------------------------------------------------------
 Status          : NEMO: normal operation
--------------------------------------------------------------------------------
 Published       : 2022-09-03 by HPC Team Freiburg

 Security update September applied (CentOS 7.9, Rev. 23).
 See update log for timestamps
 /opt/bwhpc/os-revisions/security_update_2022-09.

 See http://www.nemo.uni-freiburg.de for more information on NEMO.
--------------------------------------------------------------------------------

fr_vwxyz1234@login1 ~]$ 


SSH Keys on NEMO

Interactive SSH keys can be used with a second factor. You must copy your public SSH keys into:

~/.ssh/authorized_keys

Workflow and Command SSH Keys

This example uses 'rrsync' (see rrsync wiki).

If you want to use workflows and commands without a second factor, you can use SSH command keys. The command needs to look like this:

command="/usr/local/bin/rrsync -ro /home/aa/aa_bb/aa_abc1/",from="10.10.10.0/24"

Please send the following information to the NEMO support:

command="/usr/local/bin/rrsync -ro /home/aa/aa_bb/aa_abc1/",from="10.10.10.0/24" ssh-rsa ... username

This command then will be allowed on workflow.nemo.uni-freiburg.de, example:

rsync -av workflow.nemo.uni-freiburg.de:remotedir/ localdir/

For Moab job workflows, we provide the Python script /usr/local/bin/moab.py, which enables the following commands:

  • canceljob
  • checkjob
  • mdiag
  • mjobctl
  • msub
  • showq

If you need to change the directory, e.g. when using msub, add --chdir DIR to the end of your parameters.

Example:

$ ssh -q workflow.nemo.uni-freiburg.de 'msub test.sh --chdir test'
17667929

$ ssh -q workflow.nemo.uni-freiburg.de 'showq -u $USER -i'
eligible jobs----------------------
JOBID                 PRIORITY  XFACTOR  Q  USERNAME    ACCNT  PROCS     WCLIMIT     CLASS      SYSTEMQUEUETIME
17667929                     0      1.0  -  fr_usr12 bw16a001     20    00:05:00         -   Tue Nov 21 18:10:41
1 eligible job
Total job:  1

$ ssh -q workflow.nemo.uni-freiburg.de 'canceljob 17667929'
job '17667929' cancelled

Allowed Activities on Login Nodes

Attention.svg

To guarantee usability for all the users of clusters you must not run your compute jobs on the login nodes. Compute jobs must be submitted to the queuing system. Any compute job running on the login nodes will be terminated without any notice. Any long-running compilation or any long-running pre- or post-processing of batch jobs must also be submitted to the queuing system.

The login nodes of the bwHPC clusters are the access point to the compute system, your $HOME 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. Your activities may also be:

  • short compilation of your program code and
  • short pre- and post-processing of your batch jobs.

We advise users to use interactive jobs for compute and memory intensive tasks like compiling.

Related Information