Registration/Login/Hostname: Difference between revisions

From bwHPC Wiki
Jump to navigation Jump to search
(Created page with "= Login Hostnames of the bwHPC Clusters = From outside the clusters users can only use the login nodes to submit jobs. Please go to the section of the cluster you want to lo...")
 
m (M Janczyk moved page Login/Hostname to Registration/Login/Hostname)
 
(3 intermediate revisions by 2 users not shown)
Line 5: Line 5:
Please go to the section of the cluster you want to login:
Please go to the section of the cluster you want to login:


* '''[[Login/Hostname#bwUniCluster 2.0 Hostnames|bwUniCluster 2.0 Hostnames]]'''
* '''[[Login/Hostname#bwUniCluster_2.0_Hostnames|bwUniCluster 2.0 Hostnames]]'''
* '''[[Login/Hostname#BINAC Hostnames|BINAC Hostnames]]'''
* '''[[Login/Hostname#BINAC Hostnames|BINAC Hostnames]]'''
* '''[[Login/Hostname#MLS&WISO Hostnames|MLS&WISO Hostnames]]'''
* '''[[Login/Hostname#JUSTUS2 Hostnames|JUSTUS2 Hostnames]]'''
* '''[[Login/Hostname#JUSTUS2 Hostnames|JUSTUS2 Hostnames]]'''
* '''[[Login/Hostname#Helix Hostnames|Helix Hostnames]]'''
* '''[[Login/Hostname#NEMO Hostnames|NEMO Hostnames]]'''
* '''[[Login/Hostname#NEMO Hostnames|NEMO Hostnames]]'''


Line 14: Line 14:
== bwUniCluster 2.0 Hostnames ==
== bwUniCluster 2.0 Hostnames ==


The system has four login nodes.
The system has four 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 to bwUniCluster 2.0, these sessions will be established to different login nodes, so processes started in one session might not be visible in other sessions.
The selection of the login node is done automatically.

If you are logging in multiple times, different sessions might run on different login nodes.
The older Broadwell extension partition of the former bwUniCluster 1 is connected to bwUniCluster 2.0.


Login to bwUniClister 2.0:
Login to bwUniClister 2.0:
Line 29: Line 29:
|}
|}


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


Line 34: Line 35:
! Hostname !! Node type
! Hostname !! Node type
|-
|-
| '''uc2-login1.scc.kit.edu''' || bwUniCluster 2.0, first login node
| '''uc2-login1.scc.kit.edu''' || bwUniCluster 2.0 first login node
|-
| '''uc2-login2.scc.kit.edu''' || bwUniCluster 2.0 second login node
|-
| '''uc2-login3.scc.kit.edu''' || bwUniCluster 2.0 third login node
|-
| '''uc2-login4.scc.kit.edu''' || bwUniCluster 2.0 fourth login node
|-
|}


== BINAC Hostnames ==

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


Login to BINAC:

{| class="wikitable"
! Hostname !! Node type
|-
| '''login01.binac.uni-tuebingen.de''' || BINAC first login node
|-
| '''login02.binac.uni-tuebingen.de''' || BINAC second login node
|-
| '''login03.binac.uni-tuebingen.de''' || BINAC third login node
|-
|}


== JUSTUS2 Hostnames ==

The system has four 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 JUSTUS2:

{| class="wikitable"
! Hostname !! Node type
|-
| '''justus2.uni-ulm.de''' || login to one of the four login nodes
|-
|}

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

{| class="wikitable"
! Hostname !! Node type
|-
| '''justus2-login01.rz.uni-ulm.de''' || JUSTUS2 first login node
|-
| '''justus2-login02.rz.uni-ulm.de''' || JUSTUS2 second login node
|-
| '''justus2-login03.rz.uni-ulm.de''' || JUSTUS2 third login node
|-
| '''justus2-login04.rz.uni-ulm.de''' || JUSTUS2 fourth login node
|-
|}


== Helix Hostnames ==

The system has four 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 Helix:

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

In general, you should use automatic selection to allow us to balance the load over the four login nodes.

== NEMO Hostnames ==

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

Login to NEMO:

{| class="wikitable"
! Hostname !! Node type
|-
|-
| '''uc2-login2.scc.kit.edu''' || bwUniCluster 2.0, second login node
| '''login.nemo.uni-freiburg.de''' || NEMO first login node alias
|-
|-
| '''uc2-login3.scc.kit.edu''' || bwUniCluster 2.0, third login node
| '''login1.nemo.uni-freiburg.de''' || NEMO first login node
|-
|-
| '''uc2-login4.scc.kit.edu''' || bwUniCluster 2.0, fourth login node
| '''login2.nemo.uni-freiburg.de''' || NEMO second login node
|-
|-
|}
|}

Latest revision as of 16:45, 8 September 2022

Login Hostnames of the bwHPC Clusters

From outside the clusters users can only use the login nodes to submit jobs.

Please go to the section of the cluster you want to login:


bwUniCluster 2.0 Hostnames

The system has four 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 bwUniClister 2.0:

Hostname Node type
bwunicluster.scc.kit.edu login to one of the four login nodes
uc2.scc.kit.edu login to one of the four login nodes

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

Hostname Node type
uc2-login1.scc.kit.edu bwUniCluster 2.0 first login node
uc2-login2.scc.kit.edu bwUniCluster 2.0 second login node
uc2-login3.scc.kit.edu bwUniCluster 2.0 third login node
uc2-login4.scc.kit.edu bwUniCluster 2.0 fourth login node


BINAC Hostnames

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


Login to BINAC:

Hostname Node type
login01.binac.uni-tuebingen.de BINAC first login node
login02.binac.uni-tuebingen.de BINAC second login node
login03.binac.uni-tuebingen.de BINAC third login node


JUSTUS2 Hostnames

The system has four 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 JUSTUS2:

Hostname Node type
justus2.uni-ulm.de login to one of the four login nodes

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

Hostname Node type
justus2-login01.rz.uni-ulm.de JUSTUS2 first login node
justus2-login02.rz.uni-ulm.de JUSTUS2 second login node
justus2-login03.rz.uni-ulm.de JUSTUS2 third login node
justus2-login04.rz.uni-ulm.de JUSTUS2 fourth login node


Helix Hostnames

The system has four 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 Helix:

Hostname Node type
helix.bwservices.uni-heidelberg.de login to one of two login nodes

In general, you should use automatic selection to allow us to balance the load over the four login nodes.

NEMO Hostnames

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

Login to NEMO:

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