Log in to Anunna: Difference between revisions
| (18 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
== Log on using ssh == | == Log on using ssh == | ||
One can log | One can log in to [[Anunna | Anunna]] using the '''S'''ecure '''Sh'''ell Protocol (SSH) (default port tcp 22). The address of the login server is: | ||
login.anunna.wur.nl | |||
To log on one has to use an ssh ([http://en.wikipedia.org/wiki/Secure_Shell secure shell]) client. Such client systems are always available from Linux or MacOS systems. For | You will be automatically redirected to the currently valid login server. To log on one has to use an ssh ([http://en.wikipedia.org/wiki/Secure_Shell secure shell]) client. Such client systems are always available from Linux or MacOS systems. For Windows an ssh-client may need to be installed. The most popular ssh-client for Windows is [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]. | ||
Note that current access may be restricted to certain IP-ranges. Furthermore, ssh-protocols may be prohibited on systems where port 22 is unavailable due to firewall. | Note that current access may be restricted to certain IP-ranges. Furthermore, ssh-protocols may be prohibited on systems where port 22 is unavailable due to firewall. | ||
| Line 9: | Line 9: | ||
The ssh-connection can also be configured to work [[ssh_without_password | without password]], which means that no password needs to be provided at each log-in or secure copy attempt. | The ssh-connection can also be configured to work [[ssh_without_password | without password]], which means that no password needs to be provided at each log-in or secure copy attempt. | ||
'''IMPORTANT: the | '''IMPORTANT: the Login server can only act as access point and is not to be used for any serious CPU or RAM intensive work.''' | ||
'''Anything requiring even moderate resources should be [[ | '''Anything requiring even moderate resources should be [[Using_Slurm |scheduled using SLURM!]]''' | ||
=== CLI from a Linux/MacOSX terminal === | === CLI from a Linux/MacOSX terminal === | ||
A Command Line Interface ([http://en.wikipedia.org/wiki/Command-line_interface CLI]) ssh client is available from any Linux or MacOSX terminal. Secure shell (ssh) protocols require port 22 to be open. Should a connection be refused, the firewall settings of the system should be checked. Alternatively, local ICT regulations may prohibit the use of port 22. Wageningen UR FB-ICT for instance does not allow traffic through port 22 over WiFi to certain systems. | A Command Line Interface ([http://en.wikipedia.org/wiki/Command-line_interface CLI]) ssh client is available from any Linux or MacOSX terminal. Secure shell (ssh) protocols require port 22 to be open. Should a connection be refused, the firewall settings of the system should be checked. Alternatively, local ICT regulations may prohibit the use of port 22. Wageningen UR FB-ICT for instance does not allow traffic through port 22 over WiFi to certain systems. | ||
< | <pre> | ||
ssh [user name]@ | ssh [user name]@login.anunna.wur.nl | ||
</ | </pre> | ||
---- | |||
=== MobaXTerm on Windows === | |||
The program uses a full Cygwin stack, so commands from Mac and Linux can be used. Though MobaXTerm provides the Mobakeygen extension, which has an intuitive interface and is very convenient. | |||
==== Connecting to the HPC with MobaXTerm ==== | |||
Go to '''Session''' => '''SSH''' and under remote host type fill in: | |||
<nowiki>login.anunna.wur.nl</nowiki> | |||
Check the box specify username and type in your username (not your email). | |||
Click on OK. Accept the prompt and type in your WUR password and press enter. | |||
'''NOTE:''' No characters will appear on the screen while you are typing your password | |||
==== Generating an SSH key pair ==== | |||
# From the main menu choose '''Tools''' > MobaKeygen SSH Key Generator | |||
# Click on '''Generate''' and move your mouse to generate entropy | |||
# Type in a passphrase for the key | |||
# Save keys with a meaningful name | |||
=== PuTTY on Windows === | === PuTTY on Windows === | ||
| Line 45: | Line 71: | ||
* Session | * Session | ||
** Host Name [ | ** Host Name [login.anunna.wur.nl] | ||
** Saved Session name [your name for this connection] | ** Saved Session name [your name for this connection] | ||
* Terminal | * Terminal | ||
| Line 102: | Line 128: | ||
== Log on to worker nodes == | == Log on to worker nodes == | ||
In a complete emergency, it is then possible to log on to any of the worker nodes via the login node. Logging on to the worker nodes does not require password authentication, you should therefore not be prompted to provide a password. This is not normally allowed - be aware that running tasks outside of SLURM is prohibited, but so far there has not been any serious abuse of this. This is provided to allow you to get a little more insight in what your job is doing. | |||
< | <pre> | ||
ssh [user name]@[node name] | ssh [user name]@[node name] | ||
</ | </pre> | ||
For instance: | For instance: | ||
< | <pre> | ||
ssh dummy001@node049 | ssh dummy001@node049 | ||
</ | </pre> | ||
Again, it is not permitted to run jobs outside the scheduling software (slurm). So logging on to a worker node is for analyses of running jobs only. | |||
== See also == | == See also == | ||
* [[ | * [[Using _Slurm | Submit jobs with Slurm]] | ||
* [[ssh_without_password | ssh without password]] | * [[ssh_without_password | ssh without password]] | ||
* [[File_transfer | File transfer options]] | |||
== External links == | == External links == | ||
* [http://en.wikipedia.org/wiki/Secure_Shell secure shell on Wikipedia] | * [http://en.wikipedia.org/wiki/Secure_Shell secure shell on Wikipedia] | ||
* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY homepage] | * [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY homepage] | ||
Latest revision as of 15:31, 10 June 2024
Log on using ssh
One can log in to Anunna using the Secure Shell Protocol (SSH) (default port tcp 22). The address of the login server is:
login.anunna.wur.nl
You will be automatically redirected to the currently valid login server. To log on one has to use an ssh (secure shell) client. Such client systems are always available from Linux or MacOS systems. For Windows an ssh-client may need to be installed. The most popular ssh-client for Windows is PuTTY.
Note that current access may be restricted to certain IP-ranges. Furthermore, ssh-protocols may be prohibited on systems where port 22 is unavailable due to firewall.
The ssh-connection can also be configured to work without password, which means that no password needs to be provided at each log-in or secure copy attempt.
IMPORTANT: the Login server can only act as access point and is not to be used for any serious CPU or RAM intensive work. Anything requiring even moderate resources should be scheduled using SLURM!
CLI from a Linux/MacOSX terminal
A Command Line Interface (CLI) ssh client is available from any Linux or MacOSX terminal. Secure shell (ssh) protocols require port 22 to be open. Should a connection be refused, the firewall settings of the system should be checked. Alternatively, local ICT regulations may prohibit the use of port 22. Wageningen UR FB-ICT for instance does not allow traffic through port 22 over WiFi to certain systems.
ssh [user name]@login.anunna.wur.nl
MobaXTerm on Windows
The program uses a full Cygwin stack, so commands from Mac and Linux can be used. Though MobaXTerm provides the Mobakeygen extension, which has an intuitive interface and is very convenient.
Connecting to the HPC with MobaXTerm
Go to Session => SSH and under remote host type fill in:
login.anunna.wur.nl
Check the box specify username and type in your username (not your email).
Click on OK. Accept the prompt and type in your WUR password and press enter.
NOTE: No characters will appear on the screen while you are typing your password
Generating an SSH key pair
- From the main menu choose Tools > MobaKeygen SSH Key Generator
- Click on Generate and move your mouse to generate entropy
- Type in a passphrase for the key
- Save keys with a meaningful name
PuTTY on Windows
Putty is a free, powerful, and widely used SSH client that runs on Windows. It is extremely useful for those people who have a computer running Windows on their desk but must remotely connect to a computer running UNIX/Linux. Putty is one of a set of utilities that all work together to provide convenient connectivity between Windows and UNIX/Linux environments. Some of these utilities include:
- Putty -- the SSH client
- Pageant -- the authentication agent used with Putty
- Puttygen -- the RSA key generation utility
- Pscp -- the SCP secure file copy utility
Depending on your tasks, the above utilities are probably your minimum set of tools to make convenient connections and file transfers between a computer running Windows and a computer running UNIX/Linux.
Putty Configuration
Putty is able to store the configuration or connection profiles for a number of remote UNIX/Linix clients. Each of profile can be created and later edited by Right-clicking on a putty window header and choosing "New Session...". The minimum set of items that need to be configured for a given connection are:
- Session
- Host Name [login.anunna.wur.nl]
- Saved Session name [your name for this connection]
- Terminal
- Keyboard
- Backspace key -> Control-H
- Keyboard
- Connection
- Data
- Auto-login username [your remote username]
- SSH
- Auth
- Private key file for authentication [pathname to your .ppk file]
- Auth
- Data
Obviously, there are many other useful things that can be configured and customized in Putty but the above list should be considered a minimum. Please note that after making any change to a putty session you must explicitly save your changes.
Creating an SSH Key Pair
Puttygen is the utility used for creating both a .ppk file (private key) and the public authorized key information. Briefly, here are the steps needed to create a key pair:
- Run (double-click) the Puttygen application
- Click on "Generate"
- Replace the comment with something meaningful -- maybe your name
- Type in your passphrase (password) twice
- Save the .ppk file in a secure location on your Windows computer
- Use your mouse to copy the public key string then paste it into the ~/.ssh/authorized_keys file on the remote computer
Note: The full pathname of this .ppk file is used in the last step of Putty configuration as described above.
Using Pageant as an Interface for Putty
Pageant is a Putty helper program that is used for two main purposes:
- Pageant is used to hold the passphrase to your key pair
- Pageant is used as a convenience application to run a Putty session from any of your saved profiles
There is no configuration needed in Pageant. You simply need to run this program at login. Any easy way to do this is to create a shortcut in your startup folder that points to the Pageant executable. Once this has been done, every time you log in you will see a little icon of a computer with a hat in your taskbar. The first step in using this is to right-click on it and select "Add Key". Navigate to your .ppk file and select "Open". It will prompt you for your passphrase. At this point your passphrase has been conveniently stored for you so that when you use Putty to connect to your various remote computers, you won't have to type in your passphrase over and over again. The next step is to right-click on the Pageant icon again and select one of your saved sessions. If you have done everything correctly you will be logged right in so that you no longer have to type your passphrase.
Log on to worker nodes
In a complete emergency, it is then possible to log on to any of the worker nodes via the login node. Logging on to the worker nodes does not require password authentication, you should therefore not be prompted to provide a password. This is not normally allowed - be aware that running tasks outside of SLURM is prohibited, but so far there has not been any serious abuse of this. This is provided to allow you to get a little more insight in what your job is doing.
ssh [user name]@[node name]
For instance:
ssh dummy001@node049
Again, it is not permitted to run jobs outside the scheduling software (slurm). So logging on to a worker node is for analyses of running jobs only.