HP Serviceguard Toolkit for NFS on Linux User Guide (May 2013)

NOTE: If you modify the unsupported attribute values, then appropriate error message is
displayed when you run the execution of cmcheckconf -P command.
• Use cmapplyconf command to add the new changes in the package configuration to the
Serviceguard cluster environment.
For example: #cmapplyconf –P <<Latest_Toolkit_Conf_File>>.
NOTE: Information related to package reconfiguration will be logged in the package log.
Deleting the package
To delete the package from the cluster, run the following command:
# cmdeleteconf -p <package_name>
This command prompts for a confirmation, before removing the package configuration from the
cluster binary file, unless you use the -f option.
Configuring alert notification for NFS toolkit package
You can configure the NFS toolkit package to send alert notification during package failure by
configuring the email_id attribute in the package configuration file. This alert notification feature
is not supported for legacy style of packaging.
Toolkit sends an alert email with failure messages in the following scenarios when:
• NFS daemon is not running on the node.
Message: <process_name> process is not running. NFS toolkit package <package_name>
failed on node <node_name>.
• RPC daemons fails to ping after specified number of retries.
Message: Unable to ping <process_name> process. NFS toolkit package <package_name>
failed on node <node_name>.
• rmtab synchronization process is not running.
Message: rmtab synchronization process is not running. NFS toolkit package
<package_name> failed on node <node_name>
• rpc.idmapd process is not running.
Message: rpc.idmapd process is not running. NFS toolkit package <package_name>
failed on node <node_name>.
• File lock migration script has gone down.
Message: File Lock Migration script has gone down. NFS toolkit package <package_name>
failed on node <node_name>.
Mounting NFS shares at client node
Using the package name in the mount command, you must NFS-mount a file system on the client
system. The package name is associated with the relocatable IP address of the package. On the
client systems, you must use a hard mount. For auto-mounter, the timeout must be greater than the
total end-to-end recovery time for the Serviceguard NFS package, which includes failover time,
running fsck, mounting file systems, and exporting file systems on the new node. The default
value of the timeout is five minutes. If you set the timeout to zero, it does not allow you to unmount.
Managing the NFS toolkit package 21