HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)

Attribute Definition File (ADF) is installed in /etc/cmcluster/modules/ecmt/samba .
Table 32 Attribute Definition File (ADF)
DescriptionFile Name
For every parameter in the legacy toolkit user configuration file, there is an
attribute in the ADF. It also has an additional attribute TKIT_DIR which is
samba.1
analogous to the package directory in the legacy method of packaging. The
ADF is used to generate a modular package ASCII template file.
For the alert mail notification feature, an additional parameter called ALERT_MAIL_ID is
introduced in the ADF. ALERT_MAIL_ID sends an email message to the specified email address
when packages fail. This email is generated only when packages fail, and not when a package
is halted by the operator. To send this email message to multiple recipients, a group email ID must
be created and specified for this parameter. When an email ID is not specified for this parameter,
the script does not send out this email.
The following files are located in /etc/cmcluster/scripts/ecmt/samba after installation:
Table 33 Scripts name
DescriptionFile Name
This script is called by the Master Control Script and acts as an interface between the Master
Control Script and the Toolkit interface script (toolkit.sh). The script calls the Toolkit Configuration
File Generator Script (described below).
tkit_module.sh
This script is called by the Module Script when the package configuration is applied using
cmapplyconf to generate the toolkit user configuration file in the package directory (TKIT_DIR
).
tkit_gen.sh
Install the HP CIFS Server application on all nodes that run the HP CIFS Server packages in the
Serviceguard cluster. A typical clustered configuration configures one node as a primary node
and the other nodes as standby nodes. The HP CIFS Server runs on the primary node serving HP
CIFS Server requests from the clients. In the event of a failure on the primary node, the package
fails over to the standby node. Therefore, all necessary configuration information on all nodes must
be identical and the resources must be available to all supporting nodes. The file systems with
client access must be stored on shared disks and these disks must be accessible by the same path
names on each node.
HP CIFS Server Package Configuration Overview
Configuration rules include the following:
• Each node has the same version of the HP CIFS Server application. The HP CIFS Server file
system and configuration files must be available on all nodes configured to run the package.
• A file system containing HP CIFS Server data must reside on shared storage. Configuration
files and executables may either reside on shared or local storage. However, for easy
maintenance, you can place configuration files on shared storage.
• Each node has the same configuration directory, where identical copies of the configuration
files for each instance are placed on a local or shared hard disk.
• Each node has the same HP CIFS Server file system directories to access the shared storage.
The following information discusses configuration options of either using a combination of shared
and local storage, or using shared storage only. The choice of local or shared storage is left to
the user's discretion. However, shared storage is recommended, as it is easier to maintain.
Local Configuration
In a local configuration, identical copies of the HP CIFS Server configuration files reside in exactly
the same locations on the local file system on each node. All HP CIFS Server file systems are shared
between the nodes. The toolkit administrator must maintain identical copies of the HP CIFS Server
124 Using SAMBA Toolkit in a Serviceguard Cluster