Managing HP Serviceguard for Linux Ninth Edition, April 2009

Distributing the Configuration And Control Script with Serviceguard Manager
When you have finished creating a package in Serviceguard Manager, click Apply
Configuration. If the package configuration has no errors, it is converted to a binary
file and distributed to the cluster nodes.
Copying Package Control Scripts with Linux 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 259).
Use Linux commands to copy 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., scp or ftp). For example, from ftsys9,
you can issue the scp command to copy the package control script to ftsys10:
scp $SGCONF/pkg1/control.sh ftsys10:$SGCONF/pkg1/control.sh
Distributing the Binary Cluster Configuration File with Linux 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:
cmcheckconf -C $SGCONF/cmcl.conf -P $SGCONF/pkg1/pkg1.conf
• Generate the binary configuration file and distribute it across the nodes.
cmapplyconf -v -C $SGCONF/cmcl.conf -P $SGCONF/pkg1/pkg1.conf
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 32)), 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.
Configuring a Legacy Package 259