Managing HP Serviceguard A.12.00.00 for Linux, June 2014
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 167) for sample cmquerycl output).
4.9.12.2.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.
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
4.9.12.2.2 Configuring monitored_subnet_access
In order to monitor subnet 15.244.65.0 or 15.244.56.0, depending on where pkg1 is running,
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
NOTE: Configuring monitored_subnet_access as FULL (or not configuring
monitored_subnet_access) for either of these subnets will cause the package configuration
to fail, because neither subnet is available on all the nodes.
4.9.12.2.3 Configuring ip_subnet_node
Now you need to specify which subnet is configured on which nodes. In our example, you would
do this by means of entries such as the following in the package configuration file:
ip_subnet 15.244.65.0
ip_subnet_node nodeA
ip_subnet_node nodeB
ip_address 15.244.65.82
ip_address 15.244.65.83
ip_subnet 15.244.56.0
ip_subnet_node nodeC
ip_subnet_node nodeD
ip_address 15.244.56.100
ip_address 15.244.56.101
4.9.13 Configuring a Package: Next Steps
When you are ready to start configuring a package, proceed to Chapter 6: “Configuring Packages
and Their Services ” (page 179); start with “Choosing Package Modules” (page 179). (If you find it
helpful, you can assemble your package configuration data ahead of time on a separate worksheet
for each package; blank worksheets are in Appendix C).
140 Planning and Documenting an HA Cluster