| | 1 | = Hints for using the Cray-XC30 at HLRN = |
| | 2 | |
| | 3 | * running remote jobs |
| | 4 | |
| | 5 | == running remote jobs == |
| | 6 | |
| | 7 | Starting from r1255, PALM allows full remote access of the Berlin complex of HLRNIII. Since the batch compute nodes do not allow to use ssh/scp (which is required by '''mrun''' for carrying out several crucial tasks, e.g. for automatic submission of restart runs), the ssh/scp commands are executed on one of the login nodes (blogin1) as a workaround. Therefore, blogin1 must be a known host for ssh/scp. This requires the user to carry out the following three steps just once: |
| | 8 | |
| | 9 | 1. Login on blogin and create a pair of private/public ssh-keys (replace <hlrn-username> by your HLRN-username): |
| | 10 | {{{ |
| | 11 | ssh <hlrn-username>@blogin1.hlrn.de |
| | 12 | ssh-keygen -t dsa |
| | 13 | }}} |
| | 14 | Enter <return> for any query, until the shell-prompt appears again. |
| | 15 | |
| | 16 | 2. On blogin, define the public key as one of the authorized keys to access the system: |
| | 17 | {{{ |
| | 18 | cat id_dsa.pub >> authorized_keys |
| | 19 | }}} |
| | 20 | 3. Still logged in on blogin, login on blogin1: |
| | 21 | {{{ |
| | 22 | ssh <hlrn-username>@blogin1 |
| | 23 | }}} |
| | 24 | After the third step, the message |
| | 25 | {{{ |
| | 26 | Warning: Permanently added 'blogin1,130.73.233.1' (RSA) to the list of known hosts. |
| | 27 | }}} |
| | 28 | should appear on the terminal. |
