Managing HP Serviceguard for Linux, Tenth Edition, September 2012

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.
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
Configuring a Package: Next Steps
When you are ready to start configuring a package, proceed to Chapter 6: “Configuring
Packages and Their Services ” (page 199); start with “Choosing Package Modules”
(page 200). (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.)
Planning for Changes in Cluster Size
If you intend to add additional nodes to the cluster online (while it is running) ensure that
they are connected to the same heartbeat subnets and to the same lock disks as the other
cluster nodes.
In selecting a cluster lock configuration, be careful to anticipate any potential need for
additional cluster nodes. Remember that while a two-node cluster must use a cluster lock,
a cluster of more than four nodes must not use a lock LUN, but can use a quorum server.
So if you will eventually need five nodes, you should build an initial configuration that
uses a quorum server.
If you intend to remove a node from the cluster configuration while the cluster is running,
ensure that the resulting cluster configuration will still conform to the rules for cluster locks
described above. See “Cluster Lock Planning” (page 96) for more information.
154 Planning and Documenting an HA Cluster