Managing Serviceguard Nineteenth Edition, Reprinted June 2011

Table 4 Error Conditions and Package Movement for Failover Packages (continued)
ResultsPackage Error Condition
Package
Allowed to Run
on Alternate
Node
Package Allowed to
Run on Primary
Node after Error
Halt script
runs after
Error or Exit
HP-UX Status
on Primary
after Error
Service
Failfast
Enabled
Node Failfast
Enabled
Error or Exit Code
YesN/A (system reset)Nosystem resetEither SettingYESLoss of Network
YesYesYesRunningEither SettingNOLoss of Network
YesN/A (system reset)Nosystem resetEither SettingYESLoss of Monitored
Resource
YesYes, if the resource
is not a deferred
YesRunningEither SettingNOLoss of Monitored
Resource
resource. No, if the
resource is
deferred.
Yes if
dependency met
Yes when
dependency is
again met
YesRunningEither SettingEither Settingdependency
package failed
How the Network Manager Works
The purpose of the network manager is to detect and recover from network card failures so that
network services remain highly available to clients. In practice, this means assigning IP addresses
for each package to the primary LAN interface card on the node where the package is running
and monitoring the health of all interfaces, switching them when necessary.
NOTE: Serviceguard monitors the health of the network interfaces (NICs) and can monitor the
IP level (layer 3) network.
Stationary and Relocatable IP Addresses
Each node (host system) should have at least one IP address for each active network interface. This
address, known as a stationary IP address, is configured in the node's
/etc/rc.config.d/netconf file or in the node’s /etc/rc.config.d/netconf-ipv6 file.
A stationary IP address is not transferable to another node, but may be transferable to a standby
LAN interface card. The stationary IP address is not associated with packages. Stationary IP
addresses are used to transmit heartbeat messages (described earlier in the section “How the
Cluster Manager Works”) and other data.
IMPORTANT: Every subnet configured as a monitored_subnet in a package configuration
file must be configured into the cluster via NETWORK_INTERFACE and either STATIONARY_IP
or HEARTBEAT_IP in the cluster configuration file. See “Cluster Configuration Parameters ”
(page 105) and “Package Parameter Explanations” (page 222) for more information.
In addition to the stationary IP address, you normally assign one or more unique IP addresses to
each failover package. The package IP address is assigned to the primary LAN interface card by
the cmmodnet command in the package control script when the package starts up.
The IP addresses associated with a package are called relocatable IP addresses (also known as
package IP addresses or floating IP addresses) because the addresses can actually move from
one cluster node to another on the same subnet. You can use up to 200 relocatable IP addresses
in a cluster. These addresses can be IPv4, IPv6, or a combination of both address families.
Because system multi-node and multi-node packages do not fail over, they do not have relocatable
IP address.
64 Understanding Serviceguard Software Components