HP CIFS Server 3.0f Administrator's Guide verison A.02.03

Installing Highly Available HP CIFS Server
HA HP CIFS Servers must be installed and configured on all cluster nodes in the configuration. All cluster
nodes may (but are not required to) act as "primary" nodes and, at the same time, as "alternate" nodes for
others. If there is no failover, each cluster node runs one of the packages. If a failover occurs, a cluster node
will pick up the failed package in addition to its original package.
Before creating a Highly Available HP CIFS Server package, you must set up your MC/ServiceGuard cluster
according to the instructions in the Managing MC/ServiceGuard manual.
To do so, perform the following:
1. Following the instructions, configure the disk hardware for high availability.
2. Use SAM or LVM commands, or VxVM commands to set up the volume groups, logical volumes, and
file systems needed for the data that must be available to the primary and alternate cluster nodes when
failover occurs.
HA HP CIFS Server Installation
1. Install HP CIFS Server using SD on all cluster nodes. If HP CIFS Server is already installed and configured
on either node, simply stop it with the /opt/samba/bin/stopsmb command and skip to step 4.
2. On the first node:
Run the script /opt/samba/bin/samba_setup to configure the Samba server. Enter the server name
and domain/workgroup name for the HA HP CIFS Server.
3. On the secondary nodes:
Run the script /opt/samba/bin/samba_setup to configure the second node. You will need to specify
the same domain/workgroup name specified on the first node. Do not use the same server name.
4. For any UNIX users used to authenticate CIFS clients, check that they have the same name, user ID
number, primary group and password on both of the nodes.
This is required for any users used to authenticate to either Samba server in the Active-Active
configuration. This means that any user name used on both Samba servers must have the same user
ID, primary group ID, and password on both cluster nodes. If this isn't the case, you cannot use Samba
as an Active-Active server for this MC/ServiceGuard cluster.
5. Check that the RUN_SAMBA and RUN_WINBIND parameters in the /etc/rc.config.d/samba file is
set to 0 on both nodes.
Configure a Highly Available HP CIFS Server
Introduction
Before configuring the MC/Serviceguard packages, it is important to understand how HP CIFS Server is
able to support active-active configurations.
The HP CIFS Server permits multiple instances of its NetBIOS and SMB master demons.
Each CIFS Server has its own smb.conf file to define its behavior. The NetBIOS name and IP address that
the client connects to is used to decide which smb.conf file is used for the connection. This multiple CIFS
master demon configuration allows HP CIFS to run multiple MC/ServiceGuard packages simultaneously.
When a failover occurs, MC/ServiceGuard transfers the IP address from the failing cluster node to another
node. When MC/ServiceGuard moves the package from the failing cluster node to the other node, it activates
the appropriate CIFS Server on a remaining node. With the IP address switched, all the traffic that was
going to the failed node now goes to the other active node. The key is to have a CIFS Server configured to
look and act just like the CIFS Server that was running on the original node.
Load balancing between systems while all systems are up can be achieved by having the CIFS shares
accessible only through certain CIFS Server names (NetBIOS names). Keep this in mind when you associate
the CIFS shares and directories with logical volumes during server configuration.
Note that each cluster node needs to know all the UNIX users that connect to the samba servers (packages).
This means that the /etc/passwd file may need to be updated. For NIS installations, you can generate
new maps using theypmake or similar tool if there are new passwd or group files. For LDAP installations,
you may grenerate LDAP data for new accounts using the migration tools provided by the LDAP-UX Integration
154 Configuring HA HP CIFS