Samba Installation - Revision history

Paul.nunez at 01:45, 22 May 2020

2020-05-22T01:45:52Z

← Older revision		Revision as of 01:45, 22 May 2020
Line 6:		Line 6:
	In a cluster, these tasks must be completed on each cluster member that will run Samba.		In a cluster, these tasks must be completed on each cluster member that will run Samba.

	#Verify the system is running a supported VSI OpenVMS version		Verify the system is running a supported VSI OpenVMS version

	Samba is supported on:		Samba is supported on:
Line 13:		Line 13:
	VSI OpenVMS Alpha v8.4-2L1 and newer		VSI OpenVMS Alpha v8.4-2L1 and newer

	#The system must be running one of the following TCP/IP stacks:		The system must be running one of the following TCP/IP stacks:

	TCP/IP Services for OpenVMS		TCP/IP Services for OpenVMS
Line 20:		Line 20:
	TCPware		TCPware

	#The SYSGEN parameter PROCSECTCNT must be a minimum of 512		The SYSGEN parameter PROCSECTCNT must be a minimum of 512

	#The SYSGEN parameter CHANNELCNT must be a minimum of 2560		The SYSGEN parameter CHANNELCNT must be a minimum of 2560

	If necessary, add the following lines to SYS$SYSTEM:MODPARAMS.DAT, AUTOGEN, and reboot the system:		If necessary, add the following lines to SYS$SYSTEM:MODPARAMS.DAT, AUTOGEN, and reboot the system:
Line 29:		Line 29:
	MIN_CHANNELCNT = 2560		MIN_CHANNELCNT = 2560

	#The software must be installed and used on an ODS-5 file system.		The software must be installed and used on an ODS-5 file system.

	The software cannot be installed on an ODS-2 file system and ODS-2 file systems cannot be used for file shares. If migrating from CIFS for OpenVMS, if CIFS is installed on an ODS-2 volume, convert the volume to ODS-5 before installing Samba. Alternately, move CIFS for OpenVMS to an ODS-5 volume as documented in the CIFS for OpenVMS Administrator Guide.		The software cannot be installed on an ODS-2 file system and ODS-2 file systems cannot be used for file shares. If migrating from CIFS for OpenVMS, if CIFS is installed on an ODS-2 volume, convert the volume to ODS-5 before installing Samba. Alternately, move CIFS for OpenVMS to an ODS-5 volume as documented in the CIFS for OpenVMS Administrator Guide.

	#The OpenVMS internationalization data kit (VMSI18N) must be installed in order for Samba to be able to correctly support international characters in file names		The OpenVMS internationalization data kit (VMSI18N) must be installed in order for Samba to be able to correctly support international characters in file names

	== Cluster Considerations ==		== Cluster Considerations ==

Paul.nunez at 01:44, 22 May 2020

2020-05-22T01:44:59Z

← Older revision		Revision as of 01:44, 22 May 2020
Line 6:		Line 6:
	In a cluster, these tasks must be completed on each cluster member that will run Samba.		In a cluster, these tasks must be completed on each cluster member that will run Samba.

	* Verify the system is running a supported VSI OpenVMS version		#Verify the system is running a supported VSI OpenVMS version

	Samba is supported on:		Samba is supported on:
Line 13:		Line 13:
	VSI OpenVMS Alpha v8.4-2L1 and newer		VSI OpenVMS Alpha v8.4-2L1 and newer

	* The system must be running one of the following TCP/IP stacks:		#The system must be running one of the following TCP/IP stacks:

	TCP/IP Services for OpenVMS		TCP/IP Services for OpenVMS
Line 20:		Line 20:
	TCPware		TCPware

	* The SYSGEN parameter PROCSECTCNT must be a minimum of 512		#The SYSGEN parameter PROCSECTCNT must be a minimum of 512

	* The SYSGEN parameter CHANNELCNT must be a minimum of 2560		#The SYSGEN parameter CHANNELCNT must be a minimum of 2560

	If necessary, add the following lines to SYS$SYSTEM:MODPARAMS.DAT, AUTOGEN, and reboot the system:		If necessary, add the following lines to SYS$SYSTEM:MODPARAMS.DAT, AUTOGEN, and reboot the system:
Line 29:		Line 29:
	MIN_CHANNELCNT = 2560		MIN_CHANNELCNT = 2560

	* The software must be installed and used on an ODS-5 file system.		#The software must be installed and used on an ODS-5 file system.

	The software cannot be installed on an ODS-2 file system and ODS-2 file systems cannot be used for file shares. If migrating from CIFS for OpenVMS, if CIFS is installed on an ODS-2 volume, convert the volume to ODS-5 before installing Samba. Alternately, move CIFS for OpenVMS to an ODS-5 volume as documented in the CIFS for OpenVMS Administrator Guide.		The software cannot be installed on an ODS-2 file system and ODS-2 file systems cannot be used for file shares. If migrating from CIFS for OpenVMS, if CIFS is installed on an ODS-2 volume, convert the volume to ODS-5 before installing Samba. Alternately, move CIFS for OpenVMS to an ODS-5 volume as documented in the CIFS for OpenVMS Administrator Guide.

	* The OpenVMS internationalization data kit (VMSI18N) must be installed in order for Samba to be able to correctly support international characters in file names		#The OpenVMS internationalization data kit (VMSI18N) must be installed in order for Samba to be able to correctly support international characters in file names

	== Cluster Considerations ==		== Cluster Considerations ==

Paul.nunez at 01:43, 22 May 2020

2020-05-22T01:43:33Z

← Older revision		Revision as of 01:43, 22 May 2020
Line 19:		Line 19:
	Multinet		Multinet
	TCPware		TCPware


	* The SYSGEN parameter PROCSECTCNT must be a minimum of 512		* The SYSGEN parameter PROCSECTCNT must be a minimum of 512

Paul.nunez at 01:18, 22 May 2020

2020-05-22T01:18:37Z

← Older revision		Revision as of 01:18, 22 May 2020
Line 1:		Line 1:

	= Pre-installation Tasks =		== Pre-installation Tasks ==

	The following tasks must be accomplished prior to installing Samba.		The following tasks must be accomplished prior to installing Samba.
Line 36:		Line 36:
	* The OpenVMS internationalization data kit (VMSI18N) must be installed in order for Samba to be able to correctly support international characters in file names		* The OpenVMS internationalization data kit (VMSI18N) must be installed in order for Samba to be able to correctly support international characters in file names

	= Cluster Considerations =		== Cluster Considerations ==

	Samba can run on multiple cluster members simultaneously.		Samba can run on multiple cluster members simultaneously.
Line 56:		Line 56:
	Running instances of CIFS for OpenVMS and Samba for OpenVMS in the same OpenVMS cluster is possible, but is not supported nor recommended.		Running instances of CIFS for OpenVMS and Samba for OpenVMS in the same OpenVMS cluster is possible, but is not supported nor recommended.

	= Installation (and Upgrade) =		== Installation (and Upgrade) ==

	For a new installation, the default installation directory is SYS$COMMON:[SAMBA]. Use the /DESTINATION qualifier of the PRODUCT INSTALL command to specify a different location.		For a new installation, the default installation directory is SYS$COMMON:[SAMBA]. Use the /DESTINATION qualifier of the PRODUCT INSTALL command to specify a different location.
Line 68:		Line 68:
	* Pre-installation checks performed during installation		* Pre-installation checks performed during installation

	= Post-installation Tasks =		== Post-installation Tasks ==

	= Resolving Common Issues =		== Resolving Common Issues ==

	[[Category:Samba\|Installation]]		[[Category:Samba\|Installation]]

Paul.nunez: /* Installation (and Upgrade) */

2020-05-22T01:12:30Z

Installation (and Upgrade)

← Older revision		Revision as of 01:12, 22 May 2020
Line 57:		Line 57:

	= Installation (and Upgrade) =		= Installation (and Upgrade) =

			For a new installation, the default installation directory is SYS$COMMON:[SAMBA]. Use the /DESTINATION qualifier of the PRODUCT INSTALL command to specify a different location.

			Note: The installation procedure creates a subdirectory named SAMBA beneath the destination path specified. Thus, to install Samba to device:[SAMBA], specify /DESTINATION=device:[000000].

			If Samba for OpenVMS is installed on a system on which $ PRODUCT SHOW PRODUCT SAMBA indicates Samba for OpenVMS is already installed (this includes Samba for OpenVMS v1.2 ECO1, which is more commonly known as CIFS for OpenVMS), Samba is installed to the same location as the existing product (if /DESTINATION is specified, it is ignored by PCSI), replacing the existing product files. However, '''existing Samba/CIFS configuration and data files are retained during installation'''.

			Existing CIFS for OpenVMS configurations will be migrated to Samba for OpenVMS when the Samba configuration procedure is first executed after installation.

			* Pre-installation checks performed during installation

	= Post-installation Tasks =		= Post-installation Tasks =

Paul.nunez: /* Cluster Considerations */

2020-05-22T00:49:02Z

Cluster Considerations

← Older revision		Revision as of 00:49, 22 May 2020
Line 40:		Line 40:
	Samba can run on multiple cluster members simultaneously.		Samba can run on multiple cluster members simultaneously.

	When cluster members share the same Samba installation directory (defined by the SAMBA$ROOT logical name), they are considered to be in the same '''Samba cluster'''. ~~Members~~ of a Samba cluster share the same Samba configuration and data files and coordinate access to system resources by Samba clients.		When cluster members share the same Samba installation directory (defined by the SAMBA$ROOT logical name), they are considered to be in the same '''Samba cluster'''. Said another way, a Samba cluster is a collection of one or more OpenVMS cluster members which share the same SAMBA$ROOT: directory tree. A Samba cluster represents a single instance of Samba. All members of a Samba cluster share the same Samba configuration and data files and coordinate access to system resources by Samba clients.

	In clusters with multiple system disks, Samba may be installed in multiple locations (one location per System disk). Each separate installation directory represents a separate ~~'''~~Samba ~~instance'''~~.		In clusters with multiple system disks, Samba may be installed in multiple, separate locations (one location per System disk). Each separate installation directory represents a separate Samba cluster.

	CAUTION: While multiple ~~instances of~~ Samba may run simultaneously ~~in a cluster~~, ~~multiple instances~~ running simultaneously should not allow access to the same files as no lock coordination occurs between Samba instances. Administrators who ignore this recommendation risk file and/or data corruption.		CAUTION: While multiple Samba clusters may run simultaneously, when running simultaneously they should not allow access to the same files as no lock coordination occurs between Samba instances. Administrators who ignore this recommendation risk file and/or data corruption.

	To allow multiple cluster members to share the same installation directory tree, install Samba on a device which is mountable on all applicable cluster members.		To allow multiple cluster members to share the same installation directory tree, install Samba on a device which is mountable on all applicable cluster members.

	To allow both Alpha and Integrity cluster members to ~~share~~ the same Samba ~~installation directory~~, install Samba on each platform to the same destination.		To allow both Alpha and Integrity cluster members to be members of the same Samba cluster, install Samba on each platform to the same destination.

	A cluster member may be a member of only one Samba cluster at any time.		An OpenVMS cluster member may be a member of only one Samba cluster at any time.

	Each Samba cluster requires a unique Samba cluster alias name (set during configuration) which is shared by all members of that Samba cluster. The Samba cluster alias name may be specified by clients when establishing sessions to ~~the~~ Samba cluster (in addition to the hostname or IP address of each cluster member).		Each Samba cluster requires a unique Samba cluster alias name (set during configuration) which is shared by all members of that Samba cluster. The Samba cluster alias name may be specified by clients when establishing sessions to a Samba cluster (in addition to the hostname or IP address of each Samba cluster member).

			Running instances of CIFS for OpenVMS and Samba for OpenVMS in the same OpenVMS cluster is possible, but is not supported nor recommended.
	Running instances of CIFS for OpenVMS and Samba for OpenVMS in the same OpenVMS cluster is ~~allowed Samba cluster~~ is not supported~~. Existing CIFS for OpenVMS configurations will be migrated to Samba for OpenVMS~~.

	= Installation (and Upgrade) =		= Installation (and Upgrade) =

Paul.nunez: /* Cluster Considerations */

2020-05-22T00:13:48Z

Cluster Considerations

← Older revision		Revision as of 00:13, 22 May 2020
Line 42:		Line 42:
	When cluster members share the same Samba installation directory (defined by the SAMBA$ROOT logical name), they are considered to be in the same '''Samba cluster'''. Members of a Samba cluster share the same Samba configuration and data files and coordinate access to system resources by Samba clients.		When cluster members share the same Samba installation directory (defined by the SAMBA$ROOT logical name), they are considered to be in the same '''Samba cluster'''. Members of a Samba cluster share the same Samba configuration and data files and coordinate access to system resources by Samba clients.

	In clusters with multiple system disks, Samba may be installed in multiple locations (one location per System disk). Each separate installation directory represents a separate instance ~~of Samba~~.		In clusters with multiple system disks, Samba may be installed in multiple locations (one location per System disk). Each separate installation directory represents a separate '''Samba instance'''.

	CAUTION: While multiple instances of Samba may run simultaneously in a cluster, multiple instances running simultaneously should not allow access to the same files as no lock coordination occurs between Samba instances. Administrators who ignore this recommendation risk file and/or data corruption.		CAUTION: While multiple instances of Samba may run simultaneously in a cluster, multiple instances running simultaneously should not allow access to the same files as no lock coordination occurs between Samba instances. Administrators who ignore this recommendation risk file and/or data corruption.

Paul.nunez: /* Cluster Considerations */

2020-05-22T00:03:37Z

Cluster Considerations

← Older revision		Revision as of 00:03, 22 May 2020
Line 38:		Line 38:
	= Cluster Considerations =		= Cluster Considerations =

	Samba can run on multiple cluster members simultaneously~~, either in coordination with other cluster members or independent of other cluster members~~. When ~~multiple~~ cluster members share the same Samba installation directory (defined by the SAMBA$ROOT logical name), they are considered to be in the same Samba cluster. To allow multiple cluster members to share the same ~~SAMBA$ROOT:~~ directory tree, install Samba on a device which ~~may be mounted~~ on all applicable cluster members.		Samba can run on multiple cluster members simultaneously.

			When cluster members share the same Samba installation directory (defined by the SAMBA$ROOT logical name), they are considered to be in the same '''Samba cluster'''. Members of a Samba cluster share the same Samba configuration and data files and coordinate access to system resources by Samba clients.

			In clusters with multiple system disks, Samba may be installed in multiple locations (one location per System disk). Each separate installation directory represents a separate instance of Samba.

			CAUTION: While multiple instances of Samba may run simultaneously in a cluster, multiple instances running simultaneously should not allow access to the same files as no lock coordination occurs between Samba instances. Administrators who ignore this recommendation risk file and/or data corruption.

			To allow multiple cluster members to share the same installation directory tree, install Samba on a device which is mountable on all applicable cluster members.

			To allow both Alpha and Integrity cluster members to share the same Samba installation directory, install Samba on each platform to the same destination.

	A cluster member may be a member of only one Samba cluster at any time.		A cluster member may be a member of only one Samba cluster at any time.

	Each Samba cluster requires a unique Samba cluster alias name (set during configuration) which is shared by ~~the~~ members of that Samba cluster. The Samba cluster alias name may be specified by clients when establishing sessions to the Samba cluster, in addition to the hostname or IP address of each cluster member.		Each Samba cluster requires a unique Samba cluster alias name (set during configuration) which is shared by all members of that Samba cluster. The Samba cluster alias name may be specified by clients when establishing sessions to the Samba cluster (in addition to the hostname or IP address of each cluster member).


	~~CAUTION: While multiple~~ instances of Samba ~~may run simultaneously~~ in ~~a cluster, multiple instances should not allow access to~~ the same ~~files as no lock coordination occurs between~~ Samba cluster ~~instances~~. ~~Administrators who ignore this recommendation risk file corruption~~.		Running instances of CIFS for OpenVMS and Samba for OpenVMS in the same OpenVMS cluster is allowed Samba cluster is not supported. Existing CIFS for OpenVMS configurations will be migrated to Samba for OpenVMS.

	= Installation (and Upgrade) =		= Installation (and Upgrade) =

Paul.nunez at 21:12, 21 May 2020

2020-05-21T21:12:19Z

← Older revision		Revision as of 21:12, 21 May 2020
Line 52:		Line 52:
	= Resolving Common Issues =		= Resolving Common Issues =

	[[Category:Samba]\|Installation]		[[Category:Samba\|Installation]]

Paul.nunez at 21:09, 21 May 2020

2020-05-21T21:09:03Z

← Older revision		Revision as of 21:09, 21 May 2020
Line 52:		Line 52:
	= Resolving Common Issues =		= Resolving Common Issues =

	[[Category:Samba]]		[[Category:Samba]\|Installation]