Serviceguard NFS Toolkit A.11.11.06, A.11.23.05 and A.11.31.07 Administrator's Guide (September 2010)

Configuring a Serviceguard NFS Modular Package
To configure a Serviceguard NFS modular package, complete the following tasks, included in
this section:
• “Editing the Package Configuration File (nfs.conf)”
• “Configuring Server-to-Server Cross-Mounts (Optional)”
• “Creating the Cluster Configuration File and Bringing Up the Cluster”
Editing the Package Configuration File (nfs.conf)
The nfs.conf file lists all the Serviceguard and HA-NFS related parameters. In the Serviceguard
NFS legacy framework, the NFS parameters are configured in the toolkit scripts. In the
Serviceguard NFS modular framework, the modular scripts that are delivered to the standard
location do not carry any parameters and hence neither modified nor copied. All the parameters
have been moved from the toolkit scripts to the package configuration file.
Starting from Serviceguard NFS Toolkit A.11.31.07, a new parameter called SUPPORTED_NETIDS
is introduced in the Serviceguard NFS modular framework.
1. Set the package_name variable.
package_name pkg1
You can use the default package name if you will run only one Serviceguard NFS modular
package on your Serviceguard cluster. Each package must have a unique name.
2. Set the package_type to the default value failover
package_type failover
3. Create a node_name variable for each node that will run the package. The first node_name
should specify the primary node. All the node_name variables following the primary node
should specify the adoptive nodes, in the order in which they will be tried.
node_name thyme
node_name basil
node_name sage
4. Specify the IP address for the package and the address of the subnet to which the IP
address belongs:
ip_subnet 16.92.84.0
ip_address 16.92.85.67
The IP address you specify is the relocatable IP address for the package. NFS clients that
mount the file systems in the package will use this IP address to identify the server. You
must configure a name for this address in the DNS or NIS database, or in the /etc/hosts
file.
5. By default the service_name is enabled and is set to nfs.monitor. Change nfs.monitor
to unique name for each package.
service_name nfs1.monitor
service_cmd "$SGCONF/scripts/nfs/nfs_upcc.mon"
service_restart none
service_fail_fast_enabled no
service_halt_timeout 0
Multiple instances of the monitor script for different packages, can run on the same node
without any problem. If a package fails over, only the instance associated with that package
is killed.
6. Create a separate vg for each LVM volume group that is used by the package:
vg vg01
vg vg02
7. Create a separate vxvm_dg for each VxVM disk group that is used by the package:
52 Installing and Configuring Serviceguard NFS Modular Package