Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Cluster and Package Maintenance
Configuring a Legacy Package
Chapter 7286
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” on page 30), 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” on
page 175 for sample cmquerycl output).
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.
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