...
If you are on campus or connected to the University of Iowa VPN then you can access the HPC systems as follows:
No Format | ||
---|---|---|
| ||
Neon: ssh neon.hpc.uiowa.edu Argon: ssh argon.hpc.uiowa.edu |
Since the standard port for ssh is often used to attempt to break in to into systems, an alternate port is used if you are off-campus and not connected to the VPN.
No Format | ||
---|---|---|
| ||
Neon: ssh -p 40 neon.hpc.uiowa.edu Argon: ssh -p 40 argon.hpc.uiowa.edu |
If you are connecting from a computer where you are not logged in with your HawkID then you will have to specify the HawkID as the ssh client will try to login with the user name on the machine you are on. To do that, prepend your HawkID to the system name.
No Format | ||
---|---|---|
| ||
Neon: ssh -p 40 HawkID@neon.hpc.uiowa.edu Argon: ssh -p 40 HawkID@argon.hpc.uiowa.edu |
If on a Windows machine enter the appropriate values in the configuration fields of the client application. When you receive a password prompt enter your HawkID password. If all went well you should then be logged on to the selected HPC system.
The HPC systems have multiple login nodes so the above will connect you to one of the login nodes in a round-robin fashion. Generally speaking you do not have to worry about which login node you are on but be aware that different ssh sessions of yours could be running on different login nodes. The login nodes have both internal and external names with the internal name being the one visible in your shell. The mapping between internal and external names is pretty straight forward.
internal name | external name |
---|---|
neon-login-0-1.local | neon-login-1.hpc.uiowa.edu |
neon-login-0-2.local | neon-login-2.hpc.uiowa.edu |
This is a little more straightforward with Argon as the only difference is the domain name.
internal name | external name |
---|---|
argon-login-1.local | argon-login-1.hpc.uiowa.edu (currently unavailable) |
argon-login-2.local | argon-login-2.hpc.uiowa.edu |
The above may be useful if you need to reconnect back to the same login node for some reason.