BwUniCluster3.0/Login

Access to bwUniCluster 3.0 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 bwUniCluster 3.0 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

1. Completed the 3-step registration procedure.
2. Set a service password for bwUniCluster 3.0.
3. Set up a second factor for the time-based one-time password (TOTP).

Login to the bwUniCluster

Login to the bwUniCluster 3.0 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 bwUniCluster 3.0 you need to add a prefix to your local username.

For prefixes please refer to the prefix table.

Examples:

• If your local username for the University is ab123 and you are a user from the University of Freiburg this would combine to: fr_ab123.
• If your KIT username is ab1234 and you are a user from KIT this would combine to: ka_ab1234.

Hostnames

The system has two login nodes. The selection of the login node is done automatically. If you are logging in multiple times, different sessions might run on different login nodes.

Login to bwUniCluster 3.0:

Hostname	Node type
bwunicluster.scc.kit.edu	login to one of the three login nodes
uc3.scc.kit.edu	login to one of the three login nodes

In general, you should use automatic selection to allow us to balance the load over the three login nodes. If you need to connect to specific login nodes, you can use the following hostnames:

Hostname	Node type
uc3-login1.scc.kit.edu	bwUniCluster 3.0 first login node
uc3-login2.scc.kit.edu	bwUniCluster 3.0 second login node

Host Keys

When you log in, you may receive the message The authenticity of host '<host address>' can't be established. along with the host key fingerprint. This is intended so you can verify the authenticity of the host you are connecting to. Before you continue you should verify, if this fingerprint matches one of the following:

Algorithm	Fingerprint (SHA256)
RSA	SHA256:RaE0/tqQMMBmJuDCIo3WZ38YJsz0godVyt6aUOk/E0M
ECDSA	SHA256:LjBYL/x86ZAlL0JdlXrCmPYXvS3DaSiMuvycojBMdwQ
ED25519	SHA256:5mZYEpKigwK5ibBMHRrh3WIkOtCqomJW6H7OMbPk3ec

Login with SSH command (Linux, Mac, Windows)

Linux, Mac OS, other Unix-like operating systems and Microsoft Windows come with a built-in SSH client, most likely provided by the OpenSSH project.

For login use one of the following ssh commands:

ssh <username> uc3.scc.kit.edu
ssh <username>@bwunicluster.scc.kit.edu

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              : uc3.scc.kit.edu    # or bwunicluster.scc.kit.edu
Specify user name        : <username>
Port                     : 22

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

Note: When using File transfer with MobaXterm version 23.6 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 with Jupyterhub

Login takes place at:

• bwUniCluster 3.0: uc3-jupyter.scc.kit.edu
• SDIL: sdil-jupyter.scc.kit.edu

More Information can be found here.

Login Example

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

1. Use SSH for a login node.
2. The system will ask for a one-time password Your OTP:. Please enter your OTP and confirm it with Enter/Return. 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. 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.

[user@client ~]$ ssh ka_ab1234@uc3.scc.kit.edu
(ka_ab1234@uc3.scc.kit.edu) Your OTP: cccccctlljdbrjdleujigivvfnkjbucudugjjlutfbrk
(ka_ab1234@uc3.scc.kit.edu) Password: 
********************************************************************************
*                                                                              *
*                   Karlsruher Institut für Technologie (KIT)                  *
*                                                                              *
*                       Scientific Computing Center (SCC)                      *
*                                                                              *
*                            _    _    _____   ____                            *
*                           | |  | |  / ____| |___ \                           *
*                           | |  | | | |        __) |                          *
*                           | |  | | | |       |__ <                           *
*                           | |__| | | |____   ___) |                          *
*                            \____/   \_____| |____/                           *
*                                                                              *
*                                                                              *
*                  (KITE 2.0, RHEL 9.4, Lustre 2.14.0_ddn154)                  *
*                                                                              *
*                                                                              *
********************************************************************************
Last login: Wed Feb 26 11:08:20 2025 from 2a00:1398:4:181c:2be1:437b:1c36:1337

[ka_ab1234@uc3n990 ~]$

Troubleshooting

See bwUniCluster FAQ.

Allowed Activities on Login Nodes

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

• If you want to reset your service password, consult the Password Guide.
• If you want to register a new token for the two factor authentication (2FA), consult the 2FA Guide.
• If you want to de-register, consult the De-registration Guide.
• If you need an SSH key for your workflow, read Registering SSH Keys with your Cluster.
• Configuring your shell: .bashrc Do's and Don'ts