Configuration Restrictions

This section provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for Samba only.

For restrictions that apply to all data services, see the Sun Cluster Release Notes.

Your data service configuration might not be supported if you do not observe these restrictions.

• The Sun Cluster HA for Samba data service deployment – The Sun Cluster HA for Samba data service consists of two components, Samba and Winbind. These components have the following deployment restrictions.

  • Samba component — The Samba component, that is. SMB/CIFS and NetBIOS Name Server, cannot operate as a scalable service. Therefore, you can configure the Sun Cluster HA for Samba data service for the Samba component only be run as a failover service.

  • Winbind component — The Winbind component can operate as either a failover or scalable service. Therefore, you can configure the Sun Cluster HA for Samba data service for the Winbind component to run as a failover or scalable service.

• Windows 200x with ADS (Active Directory Support) — Only Samba version 3.0.x can be used. Samba version 2.2.x does not have ADS capabilities.

• Winbind deployment – The following restrictions apply when deploying winbind.

  • Samba Version — If the winbind feature is used, then you must install Samba v2.2.4 or later.

  • Solaris Version — Solaris 9 with patch 113476–05 or later.

  • Multiple instances — Only one instance of winbind can be deployed, whether that instance is a failover or scalable service.

• Supported configurations – Currently, only the following configurations are supported with the Sun Cluster HA for Samba data service.

  • Samba in a Primary Domain Controller (PDC) configuration.

  • Samba in a Backup Domain Controller (BDC) configuration to a Samba PDC.

  • Samba as an NT 4 Domain member without winbind.

  • Samba as an NT 4 Domain Member with winbind (Refer to the restriction above with Solaris 9.)

  • Samba as an Windows 200x with ADS (Active Directory Support) member without winbind.

  • Samba as an Windows 200x with ADS (Active Directory Support) member with winbind (Refer to the restriction above with Solaris 9.)

  • Samba in a Standalone configuration

• Installing Samba onto Cluster File Systems — The following restrictions apply for all Samba delivery methods.

  • Samba component — Each Samba instance must have a unique configuration directory that reflects the Samba NetBIOS instance name. You can mount this configuration directory as either a Failover File System or Global File System.

  • Winbind component — The winbind component only as a single instance. However, Winbind still requires a configuration directory. This configuration directory is the same directory as for the Samba component in failover service and in a separated directory for a scalable service.

  ---

  Note –

  It is best practice to mount Global File Systems with the /global prefix and to mount Failover File Systems with the /local prefix.

  ---

  shows Samba installed from http://www.samba.org onto a Global File System with two Samba instances (SAMBA1 and SAMBA2) and Winbind within that Global File System. The final output shows a subset of the /etc/vfstab entries for Samba deployed using Solaris Volume Manager.

Example 1 Samba instances and Winbind with Global File Systems

# ls -l /usr/local
total 4
drwxrwxrwx   2 root     other        512 Oct  1 16:44 bin
lrwxrwxrwx   1 root     other         13 Oct 11 11:20 samba -> /global/samba
#
# ls -l /global/samba
total 18
drwxr-xr-x   2 root     other        512 Oct 11 15:00 bin
drwxr-xr-x   3 root     other        512 Oct 14 13:49 lib
drwxr-xr-x   6 root     other        512 Oct 11 15:00 man
drwxr-xr-x   2 root     other        512 Oct 14 10:05 private
drwxr-xr-x   7 root     other        512 Oct 14 13:39 SAMBA1
drwxr-xr-x   7 root     other        512 Oct 14 13:40 SAMBA2
drwxr-xr-x   6 root     other        512 Oct 11 15:01 swat
drwxr-xr-x   3 root     other        512 Oct 14 10:45 var
drwxr-xr-x   2 root     other        512 Jan 17 09:28 winbind
#
# more /etc/vfstab (Subset of the output)
/dev/md/dg_d6/dsk/d63   /dev/md/dg_d6/rdsk/d63  /global/samba
           ufs     4       yes     logging,global
#

In Example 1–1 the configuration directory for the Samba NetBIOS instance SAMBA1 is /global/samba/SAMBA1, whereas the configuration directory for the Samba NetBIOS instance SAMBA2 is /global/samba/SAMBA2. The Winbind configuration directory is /global/samba/winbind.

Example 1–2 shows Samba installed from Solaris 9 on Local File Systems and two Samba instances (SMB1 and SMB2) on Failover File Systems. The final output shows a subset of the /etc/vfstab entries for Samba deployed using Solaris Volume Manager.

Example 2 Samba instances with Failover File Systems

# ls -l /local/samba
total 4
drwxr-xr-x   2 root     other        512 Dec 19 15:51 SMB1
drwxr-xr-x   2 root     other        512 Dec 19 15:51 SMB2
#
# more /etc/vfstab (Subset of the output)
/dev/md/dg_d7/dsk/d70   /dev/md/dg_d7/rdsk/d70  /local/samba/SMB1
       ufs     3       no      logging
/dev/md/dg_d8/dsk/d80   /dev/md/dg_d8/rdsk/d80  /local/samba/SMB2
       ufs     3       no      logging
#

In example 1–2 the configuration directory for the Samba NetBIOS instance SMB1 is /local/samba/SMB1, whereas the configuration directory for the Samba NetBIOS instance SMB2 is /local/samba/SMB2.