Managing Serviceguard A.11.20, March 2013

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.
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 232); start with “Choosing Package Modules” (page 232). (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 E.)
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.
For cross-subnet considerations, see “Cross-Subnet Configurations” (page 29).
In selecting a cluster lock configuration, be careful to anticipate any potential need for additional
cluster nodes. Remember that a cluster of more than four nodes must not use a lock disk, but a
two-node cluster must use a cluster lock. Thus, 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 103) for more information.
If you are planning to add a node online, and a package will run on the new node, ensure that
any existing cluster bound volume groups for the package have been imported to the new node.
Also, ensure that the MAX_CONFIGURED_PACKAGES parameter (see “Cluster Configuration
Parameters ” is set high enough to accommodate the total number of packages you will be using.
162 Planning and Documenting an HA Cluster