1. Installing and Configuring HA for Samba
Overview of Installing and Configuring HA for Samba
Planning the HA for Samba Installation and Configuration
Restriction for the supported configurations of Samba
Restriction for the Location of Samba files
Restriction for the Samba smb.conf files
Restriction for multiple Samba instances that require winbind
Determine which Solaris Zone Samba will run use
Dependencies Between HA for Samba Components
Required parameters for the Samba smb.conf file
Installing and Configuring Samba
How to Install and Configure Samba
How to Check Samba is installed with Solaris 9 or 10
How to Install and Configure Samba downloaded from http://www.samba.org
How to Prepare Samba for HA for Samba
Verifying the Installation and Configuration of Samba
How to Verify the Installation and Configuration of Samba
Installing the HA for Samba Packages
How to Install the HA for Samba Packages
Registering and Configuring HA for Samba
How to Register and Configure HA for Samba
How to Register and Configure HA for Samba in a failover resource group
How to Register and Configure HA for Samba in an HA Container
Verifying the HA for Samba Installation and Configuration
How to Verify the HA for Samba Installation and Configuration
How to Migrate Existing Resources to a New Version of HA for Samba
Understanding the HA for Samba Fault Monitor
Probing Algorithm and Functionality
How to turn on debug for HA for Samba
A. Deployment Example: Installing Samba packaged with Solaris 10
B. Deployment Example: Installing Samba from http://www.samba.org
This section describes the HA for Samba fault monitor's probing algorithm or functionality, states the conditions, messages, and recovery actions associated with unsuccessful probing.
For conceptual information on fault monitors, see the Oracle Solaris Cluster Concepts Guide.
The HA for Samba fault monitor uses the same resource properties as resource type SUNW.gds. Refer to the SUNW.gds(5) man page for a complete list of resource properties used.
The HA for Samba fault monitor is controlled by the extension properties that control the probing frequency. The default values of these properties determine the preset behavior of the fault monitor. The preset behavior should be suitable for most Oracle Solaris Cluster installations. Therefore, you should tune the HA for Samba fault monitor only if you need to modify this preset behavior.
Setting the interval between fault monitor probes (Thorough_probe_interval)
Setting the time-out for fault monitor probes (Probe_timeout)
Setting the number of times the fault monitor attempts to restart the resource (Retry_count)
The HA for Samba fault monitor checks the smbd, nmbd, and winbindd components within an infinite loop. During each cycle the fault monitor will check the relevant component and report either a failure or success.
If the fault monitor is successful it returns to its infinite loop and continues the next cycle of probing and sleeping.
If the fault monitor reports a failure a request is made to the cluster to restart the resource. If the fault monitor reports another failure another request is made to the cluster to restart the resource. This behavior will continue whenever the fault monitor reports a failure.
If successive restarts exceed the Retry_count within the Thorough_probe_interval a request to failover the resource group onto a different node or zone is made.
Note - The winbindd daemon resolves user and group information as a service to the Name Service Switch. When running winbindd the Name Service Cache daemon must be turned off. To disable this refer to Step 4 in How to Prepare Samba for HA for Samba.
The winbind fault monitor periodically checks that the fault monitor user can be retrieved by using getent passwd samba-fault-monitor-user.
The Samba probe checks the nmbd daemon using the nmblookup program for each interface specified within the smb.conf file.
The Samba probe checks the smbd daemon using the smbclient program together with the samba-fault-monitor-user to access the scmondir share.
If smbclient cannot connect, there could be network/server issues causing smbclient to fail. These errors maybe transient and correctable within a few seconds. Therefore before a failure is called by the probe, smbclient is retried within 85% of the available Probe_timeout less 15 seconds, which is approximately the time-out for the first smbclient failure.
However, doing this is only realistic if Probe_timeout=30 seconds or more. If Probe_timeout is below 30 seconds then smbclient is tried only once.