Logging in to the system

From HPC users
Revision as of 13:16, 4 December 2013 by Melchert (talk | contribs)
Jump to navigationJump to search

From within the University (intranet)

Within the internal net of the University, access to the systems is granted via ssh. Use your favorite ssh client like OpenSSH, PuTTY, etc. For example, on a UNIX/Linux system, users of FLOW may type on the command line (replace "abcd1234" by your own account):

ssh abcd1234@flow.hpc.uni-oldenburg.de

Similarly, users of HERO login by typing:

ssh abcd1234@hero.hpc.uni-oldenburg.de

Use "ssh -X" for X11 forwarding (i.e., if you need to export the graphical display to your local system).

For security reasons, access to the HPC systems is denied from certain subnets. In particular, you cannot login from the WLAN of the University (uniolwlan) or from "public" PCs (located, e.g., in Libraries, PC rooms, or at other places).

From outside the University (internet)

First, you have to establish a VPN tunnel to the University intranet. After that, you can login to HERO or FLOW via ssh as described above. The data of the tunnel are:

Gateway       : vpn2.uni-oldenburg.de
Group name    : hpc-vpn
Group password: hqc-vqn

Cf. the instructions of the IT Services on how to configure the Cisco VPN client. For the HPC systems, a separate VPN tunnel has been installed, which is only accessible for users of FLOW and HERO. Therefore, you have to configure a new VPN connection and enter the data provided above. For security reasons, you cannot login to FLOW or HERO if you are connected to the intranet via the "generic" VPN tunnel of the University.

Difficulties to resolve hostname upon login to hero.hpc.uni-oldenburg

Sometimes, even though the VPN tunnel is correctly set up, the login procedure to HERO might fail due to problems resolving the hostname. Then you might try to access the cluster via the IP address of one of the distinguished login nodes. Just establish the VPN tunnel and try to access the HERO component of the HPC system via

 ssh abcd1234@10.140.1.61 

this should resolve the name issues and direct you to the login node hero01 (similarly, the IP address 10.104.1.62 will sent you to the login node hero02).