Managing HP Serviceguard A.11.20.20 for Linux, May 2013

7.7.4.3 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.
7.7.5 Configuring Cross-Subnet Failover
To configure a legacy package to fail over across subnets (see “Cross-Subnet Configurations”
(page 27)), you need to do some additional configuration.
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 156) for sample cmquerycl output).
7.7.5.1 Configuring node_name
First you need to make sure that pkg1 will fail over to a node on another subnet only if it has to.
For example, if it is running on NodeA and needs to fail over, you want it to try NodeB, on the
same subnet, before incurring the cross-subnet overhead of failing over to NodeC or NodeD.
NOTE: If you are using a Metrocluster, you can configure site aware cluster using the SITE and
SITE_NAME parameters. For more information about SITE and SITE_NAME parameters, see
“Cluster Configuration Parameters ” (page 91).
Assuming nodeA is pkg1’s primary node (where it normally starts), create node_name entries in
the package configuration file as follows:
node_name nodeA
node_name nodeB
node_name nodeC
node_name nodeD
7.7.5.2 Configuring monitored_subnet_access
In order to monitor subnet 15.244.65.0 or 15.244.56.0, you would configure
monitored_subnet and monitored_subnet_access in pkg1’s package configuration file
as follows:
monitored_subnet 15.244.65.0
monitored_subnet_access PARTIAL
monitored_subnet 15.244.56.0
monitored_subnet_access PARTIAL
7.7 Configuring a Legacy Package 239