Managing Serviceguard 11th Edition, Version A.11.16, Second Printing June 2004

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4160
RESOURCE_START AUTOMATIC
RESOURCE_UP_VALUE = UP
In the package control script, specify only the deferred resources, using
the DEFERRED_RESOURCE_NAME parameter:
DEFERRED_RESOURCE_NAME[0]="/net/interfaces/lan/status/lan0"
DEFERRED_RESOURCE_NAME[1]="/net/interfaces/lan/status/lan1"
Planning for Expansion
You can add packages to a running cluster. This process is described in
the chapter “Cluster and Package Administration.” When adding
packages, be sure not to exceed the value of MAX_CONFIGURED_PACKAGES
as defined in the cluster configuration file.
When planning on increasing the number of packages, remember that
the use of packages requires 6MB plus about 100KB of lockable memory
on each cluster node.
Choosing Switching and Failover Behavior
Switching IP addresses from a failed LAN card to a standby LAN card on
the same physical subnet may take place if Automatic Switching is set to
Enabled in Serviceguard Manager (LOCAL_LAN_FAILOVER_ALLOWED set
to YES in the ASCII package configuration file). Automatic Switching
Enabled is the default.
To determine failover behavior, you can define a package failover policy
that governs which nodes will automatically start up a package that is
not running. In addition, you can define a failback policy that determines
whether a package will be automatically returned to its primary node
when that is possible.
Table 3-3 in the previous chapter describes different types of failover
behavior and the settings in Serviceguard Manager or in the ASCII
package configuration file that determine each behavior.
Package Configuration File Parameters
Prior to generation of the package configuration file, assemble the
following package configuration data. The parameter names given below
are the names that appear in Serviceguard Manager. The names coded in