feature functions properly in A.11.18, install the following patch on all servers that will be configured as nodes in the cluster.
PHSS_39484 | 1.0 | Serviceguard A.11.18.00 |
6.Configuring Serviceguard NFS Legacy Package over CFS Packages
This section describes how to configure and start Serviceguard NFS legacy packages in a Serviceguard over CFS environment. It is assumed that you have already setup your Serviceguard cluster, and have performed the steps listed in the “Before Creating a Serviceguard NFS Legacy Package” section of the Serviceguard NFS Toolkit A.11.11.06, A.11.23.05 and A.11.31.08 Administrator’s Guide to configure the /etc/rc.config.d/nfsconf file, start the NFS server, configure the disk hardware, and setup volume groups, logical volumes, and file systems. It is assumed that you have setup CFS as documented in the Veritas Storage Foundation Cluster File System Installation and Administration Guide, and that you have already started the Serviceguard CFS
In the following example, the CFS file systems are /cfs1 and /cfs2, and they correspond to Serviceguard CFS
# cmviewcl
CLUSTER STATUS
cluster1 up
NODE STATUS | STATE |
|
|
|
thyme up | running |
|
|
|
NODE STATUS | STATE |
|
|
|
basil up | running |
|
|
|
MULTI_NODE_PACKAGES |
|
|
| |
PACKAGE | STATUS | STATE | AUTO_RUN | SYSTEM |
up | running | enabled | yes | |
| up | running | enabled | no |
| up | running | enabled | no |
| up | running | enabled | no |
Create a directory on each server in the cluster to hold all the configuration files (if this directory already exists you should save the contents before continuing):
# mkdir /etc/cmcluster/nfs
The rest of the configuration is dependent upon whether or not the cluster requires file locking (as described in the Issues and Limitations with the current CFS implementation section). If file locking is not required, follow the instructions in section “Serviceguard NFS Legacy Package over CFS Packages without File Locking”. If file
8