Difference between revisions of "NEMO/Login"

From bwHPC Wiki
Jump to: navigation, search
m
m (Login from Windows)
Line 64: Line 64:
 
<pre>
 
<pre>
 
Remote name : login.nemo.uni-freiburg.de # or login1.nemo.uni-freiburg.de, login2.nemo.uni-freiburg.de
 
Remote name : login.nemo.uni-freiburg.de # or login1.nemo.uni-freiburg.de, login2.nemo.uni-freiburg.de
Specify user name : <UserID>
+
Specify user name : <username>
 
Port : 22
 
Port : 22
 
</pre>
 
</pre>

Revision as of 17:53, 8 September 2022

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.

After completing the web registration, the NEMO cluster is ready for your SSH based login.


1 NEMO Username

If you want to use the NEMO cluster you need to add a prefix to your local username. The prefixes are described in the username Wiki page.

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


2 NEMO 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


3 SSH clients

For a more detailed information on SSH clients, visit the SSH clients Wiki page.

3.1 Login form Linux or Mac

Most Unix and Unix-like operating systems like Linux, Mac OS and *BSD come with a built-in SSH client provided by the OpenSSH project.

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 performance, we recommend using VNC.

3.2 Login from Windows

For windows we suggest using MobaXterm for login and file transfer. More recent versions of Windows 10 and Windows 11 using the 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:

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.

3.3 Login Example

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

  1. Use SSH for a login node.
  2. The system will ask you for your service password password:. Please enter it and confirm it with Enter/Return.
  3. You will be greeted by the cluster, followed by a shell.
~ $ ssh fr_vwxyz1234@login.nemo.uni-freiburg.de
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 ~]$ 

4 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.

5 Password Reset

See Password Guide.

6 De-registration

See De-registration Guide.

7 Further reading