ECMWF logo Support Portal
changes.mady.by.user Xavier Abellan
Saved on Dec 16, 2022
...
Host jump.ecmwf.int a?-* a??-* hpc-* hpc2020-* ecs-* User ecmwfusername IdentityFile ~/.tsh/keys/jump.ecmwf.int/user.address@somewhere.com CertificateFile ~/.tsh/keys/jump.ecmwf.int/user.address@somewhere.com-ssh/jump.ecmwf.int-cert.pub HostKeyAlgorithms +ssh-rsa*,rsa-sha2-512 PubkeyAcceptedKeyTypes +ssh-rsa* ServerAliveInterval 60 TCPKeepAlive yes Host a?-* a??-* hpc-* hpc2020-* ecs-* ProxyJump jump.ecmwf.int
You can find the right values for those two parameters in the output of the tsh command:
% tsh login
> Profile URL: https://jump.ecmwf.int:443
Logged in as: user.address@somewhere.com
Cluster: jump.ecmwf.int
Roles:
Logins: ecmwfusername
Kubernetes: disabled
Valid until: 2022-12-13 20:54:18 +0000 GMT [valid for 3h56m0s]
Extensions: permit-X11-forwarding, permit-agent-forwarding, permit-port-forwarding, permit-pty
If you are using Visual Studio Code with the Remote SSH extension, it will not recognise hosts with wildcards as defined in the previous SSH config file.
You may add append an explicit entry for the desired hosts in your ssh config file:
Host ecs-login hpc-login