HPC/Network Access/PuTTY Configuration/Accessing Carbon licenses remotely - Revision history

Stern at 20:59, January 28, 2013

2013-01-28T20:59:18Z

← Older revision		Revision as of 20:59, January 28, 2013
Line 71:		Line 71:
	=== For connections using Mega ===		=== For connections using Mega ===
	# Scroll to the top of the tree and click Session.		# Scroll to the top of the tree and click Session.
	# Verify that "Clogin~~" or "Clogin direct~~" shows in the Saved Sessions field~~, depending on whether you use Mega or VPN~~. ~~If none of these apply~~, retrace your steps from section [[#Begin adding forwarded ports]].		# Verify that "Clogin" shows in the Saved Sessions field. Otherwise, retrace your steps from section [[#Begin adding forwarded ports]].
	# Push Save.		# Push Save.
	# To use the forwarded ports, [[../Connecting to a Carbon login node \| open a new "Clogin" session]]. You do not need to terminate an existing connection to the ''mega'' SSH gateway.		# To use the forwarded ports, [[../Connecting to a Carbon login node \| open a new "Clogin" session]]. You do not need to terminate an existing connection to the ''mega'' SSH gateway.

Stern at 20:58, January 28, 2013

2013-01-28T20:58:51Z

← Older revision		Revision as of 20:58, January 28, 2013
Line 69:		Line 69:

	== Finish adding forwarded ports ==		== Finish adding forwarded ports ==
			=== For connections using Mega ===
	# Scroll to the top of the tree and click Session.		# Scroll to the top of the tree and click Session.
	# Verify that "Clogin" or "Clogin direct" shows in the Saved Sessions field, depending on whether you use Mega or VPN. If none of these apply, retrace your steps from section [[#Begin adding forwarded ports]].		# Verify that "Clogin" or "Clogin direct" shows in the Saved Sessions field, depending on whether you use Mega or VPN. If none of these apply, retrace your steps from section [[#Begin adding forwarded ports]].
	# Push Save.		# Push Save.
	# To use the forwarded ports, [[../Connecting to a Carbon login node \| open a new "Clogin" session]]. You do not need to terminate an existing connection to the ''mega'' SSH gateway.		# To use the forwarded ports, [[../Connecting to a Carbon login node \| open a new "Clogin" session]]. You do not need to terminate an existing connection to the ''mega'' SSH gateway.

			=== For connections using VPN ===
			# Scroll to the top of the tree and click Session.
			# Verify that "Clogin direct" shows in the Saved Sessions field.
			# Push Save.
			# To use the forwarded ports, push Open.

Stern: /* Finish adding forwarded ports */

2013-01-28T20:57:06Z

Finish adding forwarded ports

← Older revision		Revision as of 20:57, January 28, 2013
Line 70:		Line 70:
	== Finish adding forwarded ports ==		== Finish adding forwarded ports ==
	# Scroll to the top of the tree and click Session.		# Scroll to the top of the tree and click Session.
	# Verify that "Clogin" shows in the Saved Sessions field. If ~~it does not~~, ~~go back to~~ section [[#Begin adding forwarded ports]].		# Verify that "Clogin" or "Clogin direct" shows in the Saved Sessions field, depending on whether you use Mega or VPN. If none of these apply, retrace your steps from section [[#Begin adding forwarded ports]].
	# Push Save.		# Push Save.
	# To use the forwarded ports, [[../Connecting to a Carbon login node \| open a new "Clogin" session]]. You do not need to terminate an existing connection to the ''mega'' SSH gateway.		# To use the forwarded ports, [[../Connecting to a Carbon login node \| open a new "Clogin" session]]. You do not need to terminate an existing connection to the ''mega'' SSH gateway.

Stern: /* For connections using VPN */

2013-01-28T20:54:50Z

For connections using VPN

← Older revision		Revision as of 20:54, January 28, 2013
Line 41:		Line 41:
	#: [[Image:HPC 2012-08 PuTTY config 13 loaded clogin.png]]		#: [[Image:HPC 2012-08 PuTTY config 13 loaded clogin.png]]
	# Alter the Host Name and Port fields to say "clogin.cnm.anl.gov" and 22.		# Alter the Host Name and Port fields to say "clogin.cnm.anl.gov" and 22.
	# Enter "Clogin direct" in the Saved ~~sessions~~ field.		# Enter "Clogin direct" in the Saved Sessions field.
	# Push Save.		# Push Save.
	Proceed at step 4 in the previous section.		Proceed at step 4 in the previous section.

Stern: /* For connections using VPN */

2013-01-28T20:54:14Z

For connections using VPN

← Older revision		Revision as of 20:54, January 28, 2013
Line 41:		Line 41:
	#: [[Image:HPC 2012-08 PuTTY config 13 loaded clogin.png]]		#: [[Image:HPC 2012-08 PuTTY config 13 loaded clogin.png]]
	# Alter the Host Name and Port fields to say "clogin.cnm.anl.gov" and 22.		# Alter the Host Name and Port fields to say "clogin.cnm.anl.gov" and 22.
			# Enter "Clogin direct" in the Saved sessions field.
			# Push Save.
	Proceed at step 4 in the previous section.		Proceed at step 4 in the previous section.

Stern: /* For connections using VPN */

2013-01-28T20:52:48Z

For connections using VPN

← Older revision		Revision as of 20:52, January 28, 2013
Line 41:		Line 41:
	#: [[Image:HPC 2012-08 PuTTY config 13 loaded clogin.png]]		#: [[Image:HPC 2012-08 PuTTY config 13 loaded clogin.png]]
	# Alter the Host Name and Port fields to say "clogin.cnm.anl.gov" and 22.		# Alter the Host Name and Port fields to say "clogin.cnm.anl.gov" and 22.
	Proceed at step 5 in the previous section.		Proceed at step 4 in the previous section.

	== Example: Add forwarded ports for VNL ==		== Example: Add forwarded ports for VNL ==

Stern: /* Overview */

2013-01-28T20:51:51Z

Overview

← Older revision		Revision as of 20:51, January 28, 2013
Line 10:		Line 10:

	The configuration settings to forward one or more ports will be stored in a PuTTY session that is normally used to connect to a Carbon login node.		The configuration settings to forward one or more ports will be stored in a PuTTY session that is normally used to connect to a Carbon login node.
	There are two routes to reach a login node:		There are two alternative routes to reach a login node:
	# Use Mega intermediate host - applicable for most users.		* Use Mega intermediate host - applicable for most users.
	# Use VPN to connect directly to a login node – available to Argonne employees only.		* Use VPN to connect directly to a login node – available to Argonne employees only.
	The port configurations are largely the same, except for the PuTTY session they will be applied to.		The port configurations are largely the same, except for the PuTTY session they will be applied to.

Stern at 20:47, January 28, 2013

2013-01-28T20:47:07Z

← Older revision		Revision as of 20:47, January 28, 2013
Line 8:		Line 8:
	The concept you will use is called port forwarding, also known as tunneling.		The concept you will use is called port forwarding, also known as tunneling.
	It makes a [http://en.wikipedia.org/wiki/Port_(computer_networking) ''port''] on your machine act like a port on one of Carbon's hosts.		It makes a [http://en.wikipedia.org/wiki/Port_(computer_networking) ''port''] on your machine act like a port on one of Carbon's hosts.

			The configuration settings to forward one or more ports will be stored in a PuTTY session that is normally used to connect to a Carbon login node.
			There are two routes to reach a login node:
			# Use Mega intermediate host - applicable for most users.
			# Use VPN to connect directly to a login node – available to Argonne employees only.
			The port configurations are largely the same, except for the PuTTY session they will be applied to.

	The table on the right lists port numbers for your system and the matching host:port destinations on Carbon.		The table on the right lists port numbers for your system and the matching host:port destinations on Carbon.
Line 32:		Line 38:
	=== For connections using VPN ===		=== For connections using VPN ===
	# In the main PuTTY Configuration window, click Session at the top of the tree on the left.		# In the main PuTTY Configuration window, click Session at the top of the tree on the left.
	# Select the '''Clogin''' session and push Load.		# Select the '''Clogin''' session and push Load. We will clone this session to connect directly.
	#: [[Image:HPC 2012-08 PuTTY config 13 loaded clogin.png]]		#: [[Image:HPC 2012-08 PuTTY config 13 loaded clogin.png]]
			# Alter the Host Name and Port fields to say "clogin.cnm.anl.gov" and 22.
			Proceed at step 5 in the previous section.

	== Example: Add forwarded ports for VNL ==		== Example: Add forwarded ports for VNL ==

Stern: /* Begin adding forwarded ports */

2013-01-28T20:36:18Z

Begin adding forwarded ports

← Older revision		Revision as of 20:36, January 28, 2013
Line 18:		Line 18:

	== Begin adding forwarded ports ==		== Begin adding forwarded ports ==
			=== For connections using Mega ===
	# In the main PuTTY Configuration window, click Session at the top of the tree on the left.		# In the main PuTTY Configuration window, click Session at the top of the tree on the left.
	# Select the '''Clogin''' session and push Load.		# Select the '''Clogin''' session and push Load.
Line 28:		Line 29:
	#* No forwarded ports should remain at this point.		#* No forwarded ports should remain at this point.
	#: [[Image:HPC 2012-08 PuTTY config 5 tunnels remove.png]][[Image:HPC 2012-08 PuTTY config 6 tunnels clean.png]]		#: [[Image:HPC 2012-08 PuTTY config 5 tunnels remove.png]][[Image:HPC 2012-08 PuTTY config 6 tunnels clean.png]]

			=== For connections using VPN ===
			# In the main PuTTY Configuration window, click Session at the top of the tree on the left.
			# Select the '''Clogin''' session and push Load.
			#: [[Image:HPC 2012-08 PuTTY config 13 loaded clogin.png]]

	== Example: Add forwarded ports for VNL ==		== Example: Add forwarded ports for VNL ==

Stern at 17:09, December 6, 2012

2012-12-06T17:09:14Z

← Older revision		Revision as of 17:09, December 6, 2012
Line 1:		Line 1:
			{{Template:Table of license ports}}
	== Overview ==		== Overview ==
	~~{{Template:Table of license ports}}~~
	Carbon hosts floating network licenses for several applications.		Carbon hosts floating network licenses for several applications.
	The applications are intended to be run on the compute nodes for compute jobs, or interactively on login nodes for purposes of pre-run preparations or post-run analysis and visualization.		The applications are intended to be run on the compute nodes for compute jobs, or interactively on login nodes for purposes of pre-run preparations or post-run analysis and visualization.