Managing Serviceguard Nineteenth Edition, Reprinted June 2011

Distributing the Configuration And Control Script with Serviceguard Manager
When you have finished creating a legacy package in Serviceguard Manager, click Apply
Configuration. If the package control script has no errors, it is converted to a binary file and
distributed to the cluster nodes.
Copying Package Control Scripts with HP-UX commands
IMPORTANT: In a cross-subnet configuration, you cannot use the same package control script
on all nodes if the package uses relocatable IP addresses. See “Configuring Cross-Subnet Failover”
(page 295).
Use HP-UX commands to copy legacy package control scripts from the node where you created
the files, to the same pathname on all nodes which can possibly run the package. Use your favorite
method of file transfer (e. g., rcp or ftp). For example, from ftsys9, you can run the rcp
command to copy the package control script to ftsys10 (all on one line):
rcp /etc/cmcluster/pkg1/control.sh
ftsys10:/etc/cmcluster/pkg1/control.sh
Distributing the Binary Cluster Configuration File with HP-UX Commands
Use the following steps from the node on which you created the cluster and package configuration
files:
• Verify that the configuration file is correct. Use the following command (all on one line):
cmcheckconf -C /etc/cmcluster/cmcl.conf -P
/etc/cmcluster/pkg1/pkg1.conf
• Activate the cluster lock volume group so that the lock disk can be initialized:
vgchange -a y /dev/vg01
• Generate the binary configuration file and distribute it across the nodes (all on one line):
cmapplyconf -v -C /etc/cmcluster/cmcl.conf -P
/etc/cmcluster/pkg1/pkg1.conf
• If you are using a lock disk, deactivate the cluster lock volume group:
vgchange -a n /dev/vg01
The cmapplyconf command creates a binary version of the cluster configuration file and distributes
it to all nodes in the cluster. This action ensures that the contents of the file are consistent across
all nodes.
NOTE: You must use cmcheckconf and cmapplyconf again any time you make changes to
the cluster and package configuration files.
Configuring Cross-Subnet Failover
To configure a legacy package to fail over across subnets (see “Cross-Subnet Configurations”
(page 29)), you need to do some additional configuration.
NOTE: You cannot use Serviceguard Manager to configure cross-subnet packages.
Suppose that you want to configure a package, pkg1, so that it can fail over among all the nodes
in a cluster comprising NodeA, NodeB, NodeC, and NodeD.
NodeA and NodeB use subnet 15.244.65.0, which is not used by NodeC and NodeD; and
NodeC and NodeD use subnet 15.244.56.0, which is not used by NodeA and NodeB. (See
“Obtaining Cross-Subnet Information” (page 181) for sample cmquerycl output).
Configuring a Legacy Package 295