...
use password-based or ssh-key-based authentication as a user from Paderborn University.
We recommend ssh-key-based authentication with password-protected ssh-keys.
As an external user, you can only use ssh-key-based authentication due to security considerations.
If you have not yet deposited a key, please send us the public key of your SSH keyring to pc2-support@uni-paderborn.de. We can then install it for you.
Instruction on how to create an ssh-key can be found
...
here: Managing SSH Keys.
System-Specific Access
Both, Noctua 1 and Noctua 2 provide a jump host which provides load balancing across the front end nodes of each cluster.
...
We recommend the following combined command for an interactive session (replace USERNAME with your lowercase username):
Code Block |
---|
ssh -t feUSERNAME@fe.noctua1.pc2.uni-paderborn.de ssh noctuanoctua1 |
Alternatively, you can put
Code Block |
---|
Host noctuanoctua1 HostName fe.noctua1.pc2.uni-paderborn.de User [USERNAME] RequestTTY force IdentityFile [PATH TO PRIVATE KEY] IdentitiesOnly yes RemoteCommand ssh noctuanoctua1 |
in your ~/.ssh/config and replace [USERNAME] with your username on Noctua and [PATH TO PRIVATE KEY] with the path to your private key of your ssh-key. Then you can use the short command ssh noctuanoctua1 to connect to Noctua. You will be asked for the password of your ssh-key when logging in instead of your user password.
If you want to connect to the last connected frontend, then use this command:
Code Block |
---|
ssh -t feUSERNAME@fe.noctua1.pc2.uni-paderborn.de ssh noctuanoctua1-last |
If you need to a run graphical application, the -X option should be used, which enables X11 forwarding with X11 SECURITY extension. The complete command is
Code Block |
---|
ssh -X -t feUSERNAME@fe.noctua1.pc2.uni-paderborn.de ssh -X noctuanoctua1 |
Noctua 2
The configuration for Noctua 2 ist quite similar to Noctua 1, except for the hostnames. The Jump-Host for Noctua 2 is fe.noctua2.pc2.uni-paderborn.de. Port 22 (SSH).
...
We recommend the following combined command for an interactive session (replace USERNAME with your lowercase username):
Code Block |
---|
ssh -t feUSERNAME@fe.noctua2.pc2.uni-paderborn.de ssh noctua2 |
Alternatively, you can put
Code Block |
---|
Host noctua2 HostName fe.noctua2.pc2.uni-paderborn.de User [USERNAME] RequestTTY force IdentityFile [PATH TO PRIVATE KEY] IdentitiesOnly yes RemoteCommand ssh noctua2 |
...
If you want to connect to the last connected frontend, then use this command:
Code Block |
---|
ssh -t feUSERNAME@fe.noctua2.pc2.uni-paderborn.de ssh noctua2-last |
If you need to a run graphical application, the -X option should be used, which enables X11 forwarding with X11 SECURITY extension. The complete command is
Code Block |
---|
ssh -X -t feUSERNAME@fe.noctua2.pc2.uni-paderborn.de ssh -X noctua2 |
...