HP Serviceguard Contributed Toolkit Suite Version A.04.02.02 on Linux User Guide (December, 2012)

NOTE: When a Samba toolkit package is extended to one or more additional nodes, the same
SMB or CIFS file system and configuration file structure must be used on all nodes, regardless of
whether this is a local or a shared configuration. For a Samba local or shared configuration:
• Each node must have the same version of the Samba application.
• Each node must have the same configuration directory where identical copies of the
configuration files for each instance are placed in the local or shared hard disk.
• Each node must have the same SMB or CIFS file system directories to access the same shared
storage.
Local Configuration
In a typical local configuration, all SMB or CIFS file systems are shared between the nodes. Identical
copies of the Samba server configuration files reside in exactly the same locations of a local storage
on each node. You must ensure to maintain identical copies of the Samba components on the
different nodes.
Shared configuration
In shared configuration, the SMB and CIFS file systems and configuration files are placed on the
shared storage. The same SMB or CIFS file systems and configuration files are shared between
the cluster nodes, so you need not maintain identical copies of configuration files on each node.
In a cluster environment, each Samba server instance must have unique IP addresses. One or more
relocatable IP addresses are created for each Samba server when the package is created. When
the Samba server package is switched over from one node to another, this instance is stopped, IP
addresses are removed from the primary node, IP addresses are reallocated to a standby node,
and the instance is started on that node. Clients are then automatically connected or manually
reconnected through these IP addresses to the identical SMB or CIFS file systems on the standby
node.
Multiple Samba instances configuration
In this configuration, more than one instance of Samba can run on a node at the same time. For
example, if two nodes are running an instance of Samba and one node fails, the Samba instance
on the failed node can fail over to the other node and it can continue to run its own instance as
well.
By bringing the Samba instances in service on one or more nodes, you can distribute the workload
as desired. In addition, by adjusting the failover policy for each instances, the user can configure
the Samba instance to fail over to a particular node, or to fail over to different nodes to distribute
the workload when a failure occurs.
Using Samba toolkit
After installing the Samba toolkit, you can use this toolkit to:
• Configure packages in an SG/LX environment
• Manage packages
Configuring Samba toolkit packages
You can configure Samba toolkit packages using either legacy or modular style of packaging.
Configuring Samba legacy packages
To configure legacy Samba toolkit packages:
Using Samba toolkit 39