Samba Installation

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. 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.

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).

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.