Essentially only accounts of the Johannes Gutenberg University can get access.
Since the Mogon clusters are Linux-based systems, remote access is granted via SSH.
The Mogon login nodes are directly only accessible from inside the university network. To access Mogon from the outside (e.g. from home), please refer to these instructions:
(Outside) access using Linux / (Outside) access using Windows. The latter link also contains information for internal access with Windows.
Login to the login-nodes is mediated by a jump node: Acces is done with direct login (ssh) to “
mogon”. This name implements a 'Round-Robin-DNS' login to both login nodes of MOGON I, mil01.zdv.uni-mainz.de and mil02.zdv.uni-mainz.de. If for some reason you want to login to a specific login node, you can use this names directly. (or if for some other Reason one of the nodes is broken, and the dns allways gives you the wrong, broken one to connect to)
All users from the ETAP group must use one of the four ETAP login machines (
mogonetap.zdv.uni-mainz.de), that are for ETAP members only. A login on Mogon I login-nodes is not allowed for ETAP members.
The login nodes of Mogon II are
miil03.zdv.uni-mainz.de. Projects on Mogon I do not have access to Mogon II automatically. You have to apply for Mogon I and Mogon II separately. Only password-less login is available. You need to have your ssh-key1) on Mogon I to be able to log in to Mogon II.
The accelerators (GPUs) of Mogon II reside within Mogon I infrastructure that is to say you have to login to Mogon I but use your Mogon II account (-A m2_*) to have access to those accelerators.
You need to have your ssh-key on Mogon I to be able to log in to Mogon II. (RSA authentication)!
Your home directory is on the same file system on both clusters. In order to access MogonI I, you need to copy your ssh-key once to your home directory on Mogon I (