Using SAMBA Toolkit in a ServiceGuard for Linux (SG/LX) Cluster Version A.01.00, June 2003

Using SAMBA Toolkit in a ServiceGuard for Linux (SG/LX) Cluster Version A.01.00
Setting Up SAMBA Server Application for a SG/LX Cluster
Chapter 112
the SG/LX cluster configuration, including cluster name, node names,
heartbeat IP addresses, etc. Refer to the Getting Started with
ServiceGuard for Linux manual for more detail.
NOTE you must edit the cluster configuration file to update the cluster name
and the “MAX_CONFIGURED_PACKAGES” to be supported in this
cluster. You must then use command “cmapplyconf -C <cluster_file>” to
distribute the cluster configuration file.
NOTE The following procedures presume the environment is RedHat. If the
environment is SLES 8/UL, PLEASE REPLACE ALL OCCURRANCES
OF “/usr/local” WITH “/opt”.
Before working on the package configuration, you must create a
directory (e.g. /usr/local/cmcluster/smb_pkg1) for this package to
run. This directory should belong to a single SAMBA package and not
share with other packages. Then, you need to copy all SAMBA toolkit
scripts from directory /usr/local/cmcluster/sambatoolkit to the package
directory.
Example:
$ mkdir /usr/local/cmcluster/http_pkg1
$ cd /usr/local/cmcluster/http_pkg1
$ cp /usr/local/cmcluster/SAMBAtoolkit/*
To create both the package configuration (smb_pkg.conf) and package
control (smb_pkg.cntl) files, you must be in the package directory (e.g.
/usr/local/cmcluster/smb_pkg1).
1. Create a SG/LX package configuration file with the command
cmmakepkg -p. The package configuration file must be edited as
indicated by the comments in that file. The package name must be
unique within the cluster.
Example:PACKAGE_NAMEsmb_pkg1
NODE_NAMEnode1
NODE_NAMEnode2