HPC/Network Access/PuTTY Configuration: Difference between revisions

From CNM Wiki
Jump to navigation Jump to search
m (rewrote intro)
mNo edit summary
 
(27 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Introduction ==
The Carbon cluster is reachable from networks outside of Argonne through SSH tunneling or VPN,
The Carbon cluster is reachable from networks outside Argonne only through SSH tunneling or VPN.
either of which has advantages and disadvantages. This page explains how to set up and use SSH tunneling.
Either way has advantages and disadvantages. This page explains how to connect through an ssh tunnel.


Tunneling is a two-step process:
Should your connection attempt fail, first review your [[../#Requirements|'''access requirements''']] and take steps as indicated.
# Establish the tunnel.
# Connect through the tunnel.
[[media:HPC_Using_Carbon_-_II_Remote_Access.pdf|Overview slides (pdf)]] and [[HPC/Network_Access/SSH_Tunnel_Setup_on_Linux_and_MacOS| specifics for Carbon]] are detailed elsewhere.  Here is a brief summary of the settings to be used for PuTTY.


<!--
[[media:HPC_Using_Carbon_-_II_Remote_Access.pdf|Overview slides (pdf)]] and [[HPC/Network_Access/SSH_Tunnel_Setup_on_Linux_and_MacOS| specifics for Carbon]] are detailed elsewhere.  The PuTTY setup for both steps is explained below.
Note that the ''PuTTY Configuration'' panel is somewhat idiosyncratic to operate, notably regarding the concept of ''Sessions''.  Numerous [http://images.google.com/images?um=1&hl=en&rls=en-us&q=PuTTY+ssh&btnG=Search+Images screenshots on Google] provide general guidance.
Note that the ''PuTTY Configuration'' panel is somewhat idiosyncratic to operate, notably regarding the concept of ''Sessions''.  Numerous [http://images.google.com/images?um=1&hl=en&rls=en-us&q=PuTTY+ssh&btnG=Search+Images screenshots on Google] provide general guidance.
-->


== Establish the tunnel ==
== Configuring ==
[[Image:putty-tunnel-carbon.png]]
The following steps need to be performed once for each workstation you wish to use to access Carbon.
* [[HPC/Network Access/PuTTY Configuration/The SSH Gateway | The SSH Gateway]]
* [[HPC/Network Access/PuTTY Configuration/The Carbon login nodes | The Carbon login nodes]]
* [[HPC/Network Access/PuTTY Configuration/Accessing Carbon licenses remotely | Accessing Carbon licenses remotely]] (advanced)


[[Image:putty-session-mega.png]]
== Connecting ==
To connect to Carbon for interactive work, or to access its networked licenses, perform a preparatory step, needed only once for a given Windows login session.
* [[HPC/Network Access/PuTTY Configuration/Connecting to the SSH Gateway | Connecting to the SSH Gateway]]
From then on, and while the preparatory window remains active, connect as often as desired.
* [[HPC/Network Access/PuTTY Configuration/Connecting to a Carbon login node | Connecting to a Carbon login node]]


Note: To reach the "Session" panel, you have to scroll the tree on the left all the way up and click on the topmost entry.
== File Transfers using PSFTP ==
# [[#Configuring | Configure your PuTTY installation]] as shown above.
# [[#Connecting | Connect to the SSH Gateway]], as shown in the preceeding section.
# Open the <code>psftp</code> application.
#: Use <code>clogin</code> (your configured PuTTY saved session name) as host to connect to.


== Connect through the tunnel ==
To learn more, see the [https://the.earth.li/~sgtatham/putty/0.71/htmldoc/Chapter5.html#pscp PSFTP documentation].
[[Image:putty-session-carbon.png]]


{{Template:Standard Footer}}
== Support ==
If you have difficulties connecting:
# Stop all open PuTTY sessions.
# Review the PuTTY configuration for ''both''  the SSH Gateway profile and the Carbon Login profile, as shown in section [[#Configuring]] above.
#* Make sure that ''tunneled port numbers match'' between the two profiles.
# Carefully follow the steps at [[#Connecting]] . Remember:
#* You need ''one preparatory'' connection to the SSH gateway running, then you can open ''one or more'' terminal or file transfer connections.
#* For the connection framework described here, open ''all'' SSH connections from ''your'' own machine, ''never'' from Mega.
 
If you still have difficulties, [[HPC/Support#Compose a support request for CNM HPC | '''submit a support request''']] with ''Remote Acces'' chosen from the drop-down menu ''Type of Request or Issue''.
 
[[Category:HPC|Network]]

Latest revision as of 16:48, March 10, 2021

The Carbon cluster is reachable from networks outside of Argonne through SSH tunneling or VPN, either of which has advantages and disadvantages. This page explains how to set up and use SSH tunneling.

Should your connection attempt fail, first review your access requirements and take steps as indicated.


Configuring

The following steps need to be performed once for each workstation you wish to use to access Carbon.

Connecting

To connect to Carbon for interactive work, or to access its networked licenses, perform a preparatory step, needed only once for a given Windows login session.

From then on, and while the preparatory window remains active, connect as often as desired.

File Transfers using PSFTP

  1. Configure your PuTTY installation as shown above.
  2. Connect to the SSH Gateway, as shown in the preceeding section.
  3. Open the psftp application.
    Use clogin (your configured PuTTY saved session name) as host to connect to.

To learn more, see the PSFTP documentation.

Support

If you have difficulties connecting:

  1. Stop all open PuTTY sessions.
  2. Review the PuTTY configuration for both the SSH Gateway profile and the Carbon Login profile, as shown in section #Configuring above.
    • Make sure that tunneled port numbers match between the two profiles.
  3. Carefully follow the steps at #Connecting . Remember:
    • You need one preparatory connection to the SSH gateway running, then you can open one or more terminal or file transfer connections.
    • For the connection framework described here, open all SSH connections from your own machine, never from Mega.

If you still have difficulties, submit a support request with Remote Acces chosen from the drop-down menu Type of Request or Issue.