Registration/Login/Hostname: Difference between revisions
H Winkhardt (talk | contribs) (Added BINAC2) |
H Winkhardt (talk | contribs) m (Fixed no of Helix Login nodes) |
||
| Line 104: | Line 104: | ||
== Helix Hostnames == |
== Helix Hostnames == |
||
The system has |
The system has two login nodes. |
||
The selection of the login node is done automatically. |
The selection of the login node is done automatically. |
||
If you are logging in multiple times, different sessions might run on different login nodes. |
If you are logging in multiple times, different sessions might run on different login nodes. |
||
Latest revision as of 14:59, 1 September 2025
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 3.0 Hostnames
- BINAC Hostnames
- BINAC2 Hostnames
- JUSTUS2 Hostnames
- Helix Hostnames
- NEMO2 Hostnames
bwUniCluster 3.0 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 |
|---|---|
| uc3.scc.kit.edu | login to one of the two login nodes |
| bwunicluster.scc.kit.edu | login to one of the two 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 |
|---|---|
| uc3-login1.scc.kit.edu | bwUniCluster 3.0 first login node |
| uc3-login2.scc.kit.edu | bwUniCluster 3.0 second 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 |
BINAC2 Hostnames
BinAC 2 has one login node serving as a load balancer. We use DNS round-robin scheduling to load-balance the incoming connections between the actual three login nodes. If you are logging in multiple times, different sessions might run on different login nodes and hence programs started in one session might not be visible in another sessions.
| Hostname | Destination |
|---|---|
| login.binac2.uni-tuebingen.de | one of the three login nodes |
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 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 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 login nodes.
NEMO2 Hostnames
The system has two login nodes. You have to select the login node yourself.
Login to NEMO2:
| Hostname | Node type |
|---|---|
| login.nemo.uni-freiburg.de | NEMO2 first or second login node |
| login1.nemo.uni-freiburg.de | NEMO2 first login node |
| login2.nemo.uni-freiburg.de | NEMO2 second login node |