...
You can connect for the first time via SSH from another ECMWF platform.
No Format |
---|
$> ssh aa-login # or for users with no formal access to HPC service: $> ssh ecs-login |
See also HPC2020: Persistent interactive job with ecinteractive if you wish to customise the resource limits of your interactive session.
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
Host aa-login aa-login.ecmwf.int ecs-login ecs-login.ecmwf.int User yourusername ForwardX11 yes ForwardX11Timeout 0 ServerAliveInterval 60 TCPKeepAlive yes # Temporary extra jump through ecgate until direct access is sorted ProxyJump shell.ecmwf.int,ecgate |
...
Check if you have an existing ssh key pair on other ECMWF platforms:
No Format $> ls ~/.ssh/id_* ~/.ssh/id_rsa ~/.ssh/id_rsa.pub
If you don't, you may generate them like so:
No Format $> ssh-keygen # press 'enter' 3 more times
Make sure it is added into the different platforms to be used
Note If the key was already present in the
~/.ssh/authorized_keys
file, it will be duplicated.No Format $> ssh-copy-id -i ~/.ssh/id_rsa.pub ecgate $> ssh-copy-id -i ~/.ssh/id_rsa.pub cca $> ssh-copy-id -i ~/.ssh/id_rsa.pub aa-login # or for users with no formal access to HPC service: $> ssh-copy-id -i ~/.ssh/id_rsa.pub ecs-login
Copy also your private key onto those platforms so you can make the connections in both directions:
No Format $> rsync -av ~/.ssh/id_rsa cca:.ssh/ $> rsync -av ~/.ssh/id_rsa aa-login:.ssh/ # or for users with no formal access to HPC service: $> rsync -av ~/.ssh/id_rsa ecs-login:.ssh/