HP CIFS Server 3.0k Administrator's Guide version A.02.04

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 product. These tools are found in
/opt/ldapux/migrate and documented in the LDAP-UX Client Services Administrator's Guide
available at http://docs.hp.com/hpux/internet.
Instructions
The following instructions are for one of the MC/ServiceGuard package. You will have to go
through these steps for each CIFS server package (one for each node). You will then need to copy
all the files to all nodes in your cluster.
When complete, each HP-UX system will have a package using the unique name for each node
in the cluster, though only the package corresponding to itself will be active until a failover
occurs.
For example, if you have a three node cluster, you will have three packages on each of the three
HPUX systems.
There will be three cluster directories:
1. /etc/cmcluster/samba/pkg1
2. /etc/cmcluster/samba/pkg2
3. /etc/cmcluster/samba/pkg3
There will be three configuration files:
1. /etc/opt/samba/smb.conf.pkg1
2. /etc/opt/samba/smb.conf.pkg2
3. /etc/opt/samba/smb.conf.pkg3
There will be three directories:
1. /var/opt/samba/pkg1
2. /var/opt/samba/pkg2
3. /var/opt/samba/pkg3
...where the locks and log files will reside.
With most configurations, it will be easier to set up and maintain the dynamic security and data
files on shared disks. Therefore, you may want to create the /var/opt/samba/<package name> paths
used in the example on shared disks.
Complete the following for each CIFS package of your MC/ServiceGuard cluster:
1. Create the following directories:
/var/opt/samba/<package name>
/var/opt/samba/<package name>/locks
/var/opt/samba/<package name>/logs
/var/opt/samba/<package name >/private
where <package name> is the name for cluster package for your CIFS server. For example:
$mkdir /var/opt/samba/pkg1
Overview of HA HP CIFS Server 171