Configuration Requirements (Sun Cluster Data Service for Samba Guide for Solaris OS)

Sun Cluster Data Service for Samba Guide for Solaris OS

Configuration Requirements

The configuration requirements in this section apply only to Sun Cluster HA for Samba.

Caution –

If your data service configuration does not conform to these requirements, the data service configuration might not be supported.

Determine which Solaris Zone Samba will run use

Solaris zones provides a means of creating virtualized operating system environments within an instance of the Solaris 10 OS. Solaris zones allow one or more applications to run in isolation from other activity on your system. For complete information about installing and configuring a Solaris Container, see System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

You must determine which Solaris Zone Samba will run in. Samba can run within a global zone, non-global zone or in a failover zone configuration. Table 2 provides some reasons to help you decide.

Note –

Samba cam be deployed within a whole root zone or a sparse root zone of a non-global zone or failover zone.

Table 2 Choosing the appropriate Solaris Zone for Samba


Zone type	Reasons for choosing the appropriate Solaris Zone for Samba
Global Zone	Only one instance of Samba will be installed. Non-global zones are not required.
Non-global Zone	Several Samba instances need to be consolidated and isolated from each other. Different versions of Samba will be installed. Failover testing of Samba between non-global zones on the same node is required.
Failover Zone	You require Samba to run in the same zone regardless of which node the failover zone is running on.

Note –

If your requirement is simply to make Samba highly available you should consider choosing a global or non-global zone deployment over a failover zone deployment. Deploying Samba within a failover zone will incur additional failover time to boot/halt the failover zone.

Dependencies Between Sun Cluster HA for Samba Components

If your Samba resource requires winbind, you must configure a start dependency on the winbind resource.

You will be required to set this dependency after you have created the Samba and winbind resources and will be prompted to do so later on within Registering and Configuring Sun Cluster HA for Samba.

Table 3 list the various dependencies.

Table 3 Samba components and their dependencies


Component	Description
Samba resource (`smbd` and `nmbd`)	The `winbind` resource (If the Samba resource requires winbind services) The `smbd` Logical Host resource The `smbd` HA Storage resource
winbind resource (`winbindd`)	The `winbindd` Logical Host resource The `winbindd` HA Storage resource

Note –

Dependencies against the relevant component's Logical Host or HA Storage resource will be set for you when the Samba and winbind resources are registered.

Required parameters for the Samba `smb.conf` file

The Samba smb.conf file located within each configuration directory must contain the following parameters. Refer to the smb.conf(5) man page for complete configuration information on the parameters that follow.

Samba parameters required in smb.conf for Samba 2.2.x and 3.0.x.
- bind interfaces only must be set to True.
- interface must be defined to the Logical Hostname.
- lock dir must include the samba-configuration-directory in it's path.
- netbios name must be set to the NetBIOS name by which the Samba server is known.
- pid directory must include the samba-configuration-directory in it's path.
- security specifies the security mode under which the Samba instance will run.
- smb passwd file must include the samba-configuration-directory in it's path.
Winbind parameters required in smb.conf for Samba 2.2.x.
- workgroup must be set to the same value as the Samba smb.conf entry.
- bind interfaces only must be set to True.
- interface must be defined to the Logical Hostname.
- lock dir must include the samba-configuration-directory in it's path.
- netbios name must be set to the NetBIOS name by which the winbind server is known.
- password server must be set to the same value as the Samba smb.conf entry.
- pid directory must include the samba-configuration-directory in it's path.
- template homedir must be set to the same value as the Samba smb.conf entry.
- template shell must be set to the same value as the Samba smb.conf entry.
- winbind enum users must be set to the same value as the Samba smb.conf entry.
- winbind gid must be set to the same value as the Samba smb.conf entry.
- winbind uid must be set to the same value as the Samba smb.conf entry.
- winbind use default domain must be set to the same value as the Samba smb.conf entry.
Winbind parameters required in smb.conf for Samba 3.0.x.
- workgroup must be set to the same value as the Samba smb.conf entry.
- bind interfaces only must be set to True.
- interface must be defined to the Logical Hostname.
- lock dir must include the samba-configuration-directory in it's path.
- netbios name must be set to the NetBIOS name by which the winbind server is known.
- password server must be set to the same value as the Samba smb.conf entry.
- pid directory must include the samba-configuration-directory in it's path.
- template homedir must be set to the same value as the Samba smb.conf entry.
- template shell must be set to the same value as the Samba smb.conf entry.
- idmap gid must be set to the same value as the Samba smb.conf entry.
- winbind enum users must be set to the same value as the Samba smb.conf entry.
- idmap uid must be set to the same value as the Samba smb.conf entry.
- winbind use default domain must be set to TRUE.