Versions Compared

Old Version 45

changes.mady.by.user Xavier Abellan

Saved on

compared with

New Version 46

changes.mady.by.user Xavier Abellan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Multiexcerpt
MultiExcerptNamessh_standard_connection

Once you have configured the appropriate settings, any SSH-based tools such as ssh, scp or rsync should work out of the box without any additional options.

To test the connection you may ssh into hpc-login if you have access to ECMWF's HPCF:

No Format
ssh hpc-login

Or alternatively, if you only have access to ECMWF ECS service:

No Format
ssh ecs-login

Visit our HPCF User Guide for further information.

Tip
titletsh login every 12 hours

Remember you may need to redo the authentication step for any new ssh connections after 12 hours with:

No Format
tsh login

...

Optional: Automating the authentication step

Multiexcerpt
alternative-tsh-connection
MultiExcerptNameauto_tsh_login

You may instruct ssh to trigger a tsh login whenever required when establishing a new connection by adding the following line at the top of your ~/.ssh/config

Tabs Container
directionhorizontal

You may use the tsh client to connect without any modifications to your ~/.ssh/config with:

Tabs Page
titleLatest - jump-17.ecmwf.int
No Format
tsh ssh hpc-login

or

No Format
tsh ssh ecs-login

The target platforms you can connect to can be listed with

No Format
tsh ls

scp file transfers through the tsh client are also possible. For example, to transfer a file from your computer to your HOME in hpc-login:

No Format
tsh scp myfile hpc-login:
Note
titleCompatibility with other tools

If you choose this method and do not configure your ~/.ssh/config, you will not be able to use other tools that rely on a standard SSH connection, such as ssh itself, scp, rsync or VSCode.

Tabs Page
titleLegacy - jump.ecmwf.int

Unfortunately jump.ecmwf.int does not support this method. Choose the latest production service to enjoy this feature.

Optional: Automating the authentication step

Multiexcerpt
MultiExcerptNameauto_tsh_login

You may instruct ssh to trigger a tsh login whenever required when establishing a new connection by adding the following line at the top of your ~/.ssh/config

Tabs Container
directionhorizontal
Tabs Page
titleLatest - jump-17.ecmwf.int
No Format
Match host jump-17.ecmwf.int exec "tsh status --proxy %h >/dev/null 2>&1 || tsh --proxy %h login"
Tabs Page
titleLegacy - jump.ecmwf.int
No Format
Match host jump.ecmwf.int exec "tsh status --proxy %h >/dev/null 2>&1 || tsh --proxy %h login"
No Format
Match host jump-17.ecmwf.int exec "tsh status --proxy %h >/dev/null 2>&1 || tsh --proxy %h login"
Tabs Page
titleLegacy - jump.ecmwf.int
No Format
Match host jump.ecmwf.int exec "tsh status --proxy %h >/dev/null 2>&1 || tsh --proxy %h login"
Multiexcerpt
MultiExcerptNamevscode_local_server

Optional: VSCode settings

Tabs Container
directionhorizontal
Tabs Page
titleLatest - jump-17.ecmwf.int

For those using VSCode, you may meet to set the  Remote.SSH: Use Local Server setting to false in the extension setting. You can search for  @ext:ms-vscode-remote.remote-ssh to find the plugin-specific settings.

Tabs Page
titleLegacy - jump.ecmwf.int

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:

No Format
Host ecs-login hpc-login

Alternative connection method with tsh

Multiexcerpt
MultiExcerptNamealternative-tsh-connection
Tabs Container
directionhorizontal
Tabs Page
titleLatest - jump-17.ecmwf.int

You may use the tsh client to connect without any modifications to your ~/.ssh/config with:

No Format
tsh ssh hpc-login

or

No Format
tsh ssh ecs-login

The target platforms you can connect to can be listed with

No Format
tsh ls

scp file transfers through the tsh client are also possible. For example, to transfer a file from your computer to your HOME in hpc-login:

No Format
tsh scp myfile hpc-login:
Note
titleCompatibility with other tools

If you choose this method and do not configure your ~/.ssh/config, you will not be able to use other tools that rely on a standard SSH connection, such as ssh itself, scp, rsync or VSCode.


Tabs Page
Multiexcerpt
MultiExcerptNamevscode_local_server

Optional: VSCode settings

Tabs Container
directionhorizontal
Tabs Page
titleLatest - jump-17.ecmwf.int

For those using VSCode, you may meet to set the  Remote.SSH: Use Local Server setting to false in the extension setting. You can search for  @ext:ms-vscode-remote.remote-ssh to find the plugin-specific settings.

Host ecs-login hpc-login

Unfortunately jump.ecmwf.int does not support this method. Choose the latest production service to enjoy this feature.

Tabs Page
titleLegacy - jump.ecmwf.int

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:

No Format

Troubleshooting

Multiexcerpt
MultiExcerptNamereport_problem

If you cannot login to teleport or connect via SSH and you are not able to understand why, please raise an issue to our ECMWF Support portal and sending us the output of the commands:

Tabs Container
directionhorizontal
Tabs Page
titleLatest - jump-17.ecmwf.int
No Format
tsh version
tsh login --proxy=jump-17.ecmwf.int
ssh -V
ssh -v ecs-login
Tabs Page
titleLegacy - jump.ecmwf.int
No Format
tsh version
tsh login --proxy=jump.ecmwf.int
ssh -V
ssh -v ecs-login

You should also include information about your computer (Operating system) to help us narrow down the problem.