Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
linux_ssh_access [2021/02/03 01:42] pgh5a |
linux_ssh_access [2021/04/13 19:34] pgh5a |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| All Linux servers run "secure shell" - 'ssh'. Anyone with a CS account may log into these servers. | All Linux servers run "secure shell" - 'ssh'. Anyone with a CS account may log into these servers. | ||
| - | On Grounds, you can simply 'ssh' to CS servers typically by using a Terminal application like HyperTerm (Windows) or Terminal (Mac). | + | On Grounds, you can simply 'ssh' to CS servers. |
| - | Off Grounds, you are not able to 'ssh' directly into CS servers. However connections to ''%%portal.cs.virginia.edu%%'' are allowed from off Grounds. | + | Off Grounds, you are not able to 'ssh' directly into most CS servers except ''%%portal.cs.virginia.edu%%''. |
| You must use your CS domain userid (identical to your UVA userid) and password to 'ssh' to portal. For example: | You must use your CS domain userid (identical to your UVA userid) and password to 'ssh' to portal. For example: | ||
| Line 11: | Line 11: | ||
| ''%%ssh -l abc1de portal.cs.virginia.edu%%''. Alternatively, ''%%ssh abc1de@portal.cs.virginia.edu%%'' | ''%%ssh -l abc1de portal.cs.virginia.edu%%''. Alternatively, ''%%ssh abc1de@portal.cs.virginia.edu%%'' | ||
| - | Note that if you are opening a terminal application on your Mac or PC, your username on the Mac or PC may be different from your CS/UVA userid. So be sure to include your userid on the 'ssh' command line. | + | Most users on a Mac or Windows PC will use a Terminal application like SecureCRT, Cmder, KiTTY, or Putty (Windows), Terminal or iTerm2 (Mac) to 'ssh' to our linux servers. |
| + | |||
| + | Note that your username on the Mac or PC may be different from your CS/UVA userid. So be sure to include your userid on the 'ssh' command line. | ||
| If you'd like to use a graphical windowing interface to department servers, see: [[nx_lab|NX Linux Remote Desktop Cluster]] | If you'd like to use a graphical windowing interface to department servers, see: [[nx_lab|NX Linux Remote Desktop Cluster]] | ||
| Line 34: | Line 36: | ||
| abc1de@portal04 ~ $ hostname | abc1de@portal04 ~ $ hostname | ||
| portal04 <-- We are logged into portal cluster | portal04 <-- We are logged into portal cluster | ||
| - | abc1de@portal04 ~ $ ssh gpusrv01 <-- We can now access gpusrv01 | + | abc1de@portal04 ~ $ ssh gpusrv01 <-- We can now 'ssh' to gpusrv01 |
| abc1de@gpusrv01's password: | abc1de@gpusrv01's password: | ||
| .... | .... | ||
| Line 42: | Line 44: | ||
| === Jumphost Option === | === Jumphost Option === | ||
| - | The ssh client has an option ''%%-J%%'' to specify a host to use as a "jumphost" that lets you access other servers directly, in one step. This combines two steps (for example, ssh into portal.cs.virginia.edu and then ssh to gpusrv01) into one single command. From the //man// page: | + | The ssh client has an option ''%%-J%%'' to specify a host to use as a "jumphost" that lets you access other servers directly with one command. This combines two steps (for example, ssh into portal.cs.virginia.edu and then ssh to gpusrv01) into one single command. |
| - | + | ||
| - | <code> | + | |
| - | -J destination | + | |
| - | Connect to the target host by first making a ssh connection to | + | |
| - | the jump host described by destination and then establishing a | + | |
| - | TCP forwarding to the ultimate destination from there. Multiple | + | |
| - | jump hops may be specified separated by comma characters. This | + | |
| - | is a shortcut to specify a ProxyJump configuration directive. | + | |
| - | Note that configuration directives supplied on the command-line | + | |
| - | generally apply to the destination host and not any specified | + | |
| - | jump hosts. Use ~/.ssh/config to specify configuration for jump | + | |
| - | hosts. | + | |
| - | </code> | + | |
| Here is how we use this option to "jump" from portal.cs to another CS server. Let's repeat the example of logging in to ''%%gpusrv01%%'' | Here is how we use this option to "jump" from portal.cs to another CS server. Let's repeat the example of logging in to ''%%gpusrv01%%'' | ||
| <code> | <code> | ||
| - | [abc1de@outside-uva ~]$ ssh -l abc1de gpusrv01 -J portal.cs.virginia.edu | + | [abc1de@outside-uva ~]$ ssh abc1de@gpusrv01 -J abc1de@portal.cs.virginia.edu |
| - | abc1de@portal04.cs.virginia.edu's password: <-- first asked to authenticate to portal | + | abc1de@portal04.cs.virginia.edu's password: <-- first asked to authenticate to portal |
| - | abc1de@gpusrv01's password: <-- immediately able to log into gpusrv01 | + | abc1de@gpusrv01's password: <-- immediately able to log into gpusrv01 |
| .... | .... | ||
| abc1de@gpusrv01 ~ $ | abc1de@gpusrv01 ~ $ | ||
| Line 105: | Line 94: | ||
| === Servers === | === Servers === | ||
| - | For a listing of generally available servers in CS, see the article [[compute_resources|General Purpose Nodes]] | + | For a listing of generally available servers in CS, see the article [[compute_resources|Computing Resources]] |
| === Login Restrictions (Info for Faculty) === | === Login Restrictions (Info for Faculty) === | ||