Managing Serviceguard 12th Edition, March 2006

Configuring Packages and Their Services
Creating the Package Configuration
Chapter 6 271
Package in Stages” on page 274, because many steps do not have to
be done in sequence. The control script can be created automatically
if you want.
4. Verifying the Package Configuration: Click the Check button. If you
don’t see the log window, open one from the View menu.
5. Distributing the Configuration: Click Apply. The binary
configuration file will be created, then it and the generated control
script will be distributed to the package’s nodes.
If you want, you can configure your control script yourself. This may be
necessary if you do not use a standard control script. However, once you
edit a control script yourself, Serviceguard Manager will never be able to
see or modify it again. If you choose to edit the control script, you must
also distribute it yourself.
Using Serviceguard Commands to Configure a
Package
There are three types of packages:
• SYSTEM_MULTI_NODE packages: These special-purpose packages run
simultaneously on every node in the cluster. The CFS system
multi-node package is configured using the cfscluster command,
not by editing configuration files.
• MULTI_NODE packages: These special-purpose packages run
simultaneously on more than one node in the cluster. The CFS
multi-node packages are configured using the cfsdgadm and
cfsmntadm commands, not by editing configuration files.
• FAILOVER packages: These packages run on one node at a time. If
there is a failure, Serviceguard (or a user) can halt them, and then
start them up on another node from their configuration list. They are
configured by entering specifications into their configuration files.
Configuring System Multi-node Packages
There are two system multi-node packages that regulate VERITAS CVM
Cluster Volume Manager. These packages ship with the Serviceguard
product. There are two versions of the package files: VxVM-CVM-pkg for
CVM Version 3.5, and SG-CFS-pkg for CVM Version 4.1.
The SG-CFS-pkg for CVM Version 4.1 has the following responsibilities: