Difference between revisions of "Samba Installation"
Paul.nunez (talk | contribs) |
Paul.nunez (talk | contribs) |
||
| (7 intermediate revisions by the same user not shown) | |||
| 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 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 | |
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: | |
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 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 30: | Line 29: | ||
MIN_CHANNELCNT = 2560 | MIN_CHANNELCNT = 2560 | ||
| − | + | 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 | |
| + | |||
| + | == Cluster Considerations == | ||
| + | |||
| + | 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'''. 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, separate locations (one location per System disk). Each separate installation directory represents a separate Samba cluster. | ||
| + | |||
| + | 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 both Alpha and Integrity cluster members to be members of the same Samba cluster, install Samba on each platform to the same destination. | ||
| + | |||
| + | 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 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. | ||
| − | = | + | == 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 == |
| − | = Resolving Common Issues = | + | == Resolving Common Issues == |
[[Category:Samba|Installation]] | [[Category:Samba|Installation]] | ||
Latest revision as of 01:45, 22 May 2020
Contents
Pre-installation Tasks
The following tasks must be accomplished prior to installing 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
Samba is supported on:
VSI OpenVMS i64 v8.4-1H1 and newer VSI OpenVMS Alpha v8.4-2L1 and newer
The system must be running one of the following TCP/IP stacks:
TCP/IP Services for OpenVMS VSI TCP/IP Multinet TCPware
The SYSGEN parameter PROCSECTCNT must be a minimum of 512
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:
MIN_PROCSECTCNT = 512 MIN_CHANNELCNT = 2560
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 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
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. 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, separate locations (one location per System disk). Each separate installation directory represents a separate Samba cluster.
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 both Alpha and Integrity cluster members to be members of the same Samba cluster, install Samba on each platform to the same destination.
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 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.
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
