HP Serviceguard Version A.11.17 Release Notes, March 2006 (revised)

Serviceguard Version A.11.17 Release Notes
What’s in this Version
Chapter 1 11
1. If a failover application package uses CFS, you put an entry in its
configuration file to create a dependency on the CFS mount point
package, SG-CFS-MP-ID#, so the failover package will not start on a
node until the mount point is ready.
2. The mount point package has a dependency on the disk group
package, SG-CFS-DG-ID#, so it will not try to establish a mount point
on a node until the disk group is ready.
3. The disk group package has a dependency on the Cluster File System
package, SG-CFS-pkg, so it will not try to set up the disk groups on a
node until the required daemons for CFS are started.
If failover packages have dependencies, you configure those
dependencies with a new parameter set that can be added to the package
ASCII template:
• DEPENDENCY_NAME: a unique identifier
• DEPENDENCY_CONDITION: at this release, only one condition is
supported;
pkg_name =UP
• DEPENDENCY_LOCATION: at this release, only one location is
supported: SAME_NODE
You do not use an ASCII configuration file to create the system
multi-node CFS package (SG-CFS-pkg) or its multi-node packages
(SG-CFS-DG-ID# and SG-CFS-MP-ID#). You create them with the
cfscluster, cfsdgadm, and cfsmntadm commands. Once a disk group or
mount point is configured under a package, it is critical that cfs*
commands are used to maintain them. For example, use the cfsmount
command to mount a filesystem, not the mount command.
Several new Serviceguard commands have been added for the CFS
packages:
• cfscluster: options allow you to:
— Configure or unconfigure SG-CFS-pkg, the system multi-node
package used for clusters that use the VERITAS CVM 4.1 and
CFS.
— Start or stop the system multi-node package for the CFS.
— Get the status of the SG-CFS-pkg package.
• cfsdgadm: options allow you to: