HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook – Rev 13.00 Page 8 (of 108)
Chapter 15 Serviceguard
October 29, 2013
Packages
A cluster can operate up to 300 packages. A package identifies unique system resources,
business applications that need those resources and application monitor services, and the manner
in which they are activated or started when the package is started. The package also defines the
manner in which to halt those applications and deactivate system resources. Since a package
may operate on a different node, packages requiring SAN storage require that adoptive nodes are
zoned to the shared storage.
Package styles
There are two styles of packages – legacy and modular. A package is defined by a modular*
configuration file or legacy configuration file and a control script. Modular and legacy packages
can co-exist on a cluster. *modular package capability was introduced in A.11.18.
The legacy-style package configuration file contains some parameters that reference the package
name, package control script path and other features. The legacy control script contains
additional parameters defining volume groups or disk groups, logical volumes and their mount
directories and options, and relocatable IPs. The control script usually also identifies external
application start/stop scripts and application monitor scripts. One drawback of a 2-file concept
was that the admin often forgot to copy updates to package scripts to adoptive nodes.
The modular-style package configuration file includes all customizable parameters found in both
legacy configuration and control files. This enables the control script functionality to be generic
across nodes in the cluster. Many enablement toolkits include modular package integration.
Both legacy and modular package configuration file parameters must be loaded in the cluster
binary file using cmapplyconf. cmapplyconf cannot be used with legacy package control scripts.
Failover packages are created/managed/deleted using the commands cmapplyconf, cmgetpkgenv,
cmhaltpkg, cmmakepkg, cmmigratepkg, cmmodpkg and cmrunpkg and cmdeleteconf.
Package classes
There are also 3 classes of packages - failover, system multi-node (SMN), and multi-node
(MN). Only failover packages can be modular packages until A.11.20 Patch B is installed. Then
the admin can also create modular MN packages. A failover package can run on only one
system at a time. This means that package-related system resources can only be activated on one
node at any given time. Failover packages may TOC a node when configuration criteria are met.
SMN and MN packages are non-failover packages and were introduced with a patch for A.11.17.
The only supported SMN package is named SG-CFS-pkg. If the CFS bundle has been installed
and the admin configures SG-CFS-pkg, it starts VERITAS Cluster Volume Manager (cvmd) and
it must run on all active nodes in order to enable CFS MN packages. Failure of the SG-CFS-pkg
on a node causes that node to TOC. MN packages can run on multiple active nodes
simultaneously and are typically dedicated to supporting Cluster File System which is available
in specific Storage Management Suite (SMS) products. SMS-based packages use only VxVM
disk groups and volumes. As of A.11.18, customers could create non-CFS-based multi-node
packages. As of this writing, SMS and MN packages based on CFS are built and destroyed