Managing HP Serviceguard for Linux, Tenth Edition, September 2012

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
Linux Status
on Primary
after Error
Service
Failfast
Enabled
Node
Failfast
Enabled
Error or Exit
Code
Yes, unless the
timeout
N/A (system
reset)
N/Asystem resetEither
Setting
YESHalt Script
Timeout
happened
after the
cmhaltpkg
command was
executed.
NoYesN/ARunningEither
Setting
NOHalt Script
Timeout
YesN/A (system
reset)
Nosystem resetYESEither
Setting
Service Failure
YesNoYesRunningNOEither
Setting
Service Failure
YesN/A (system
reset)
Nosystem resetEither
Setting
YESLoss of
Network
YesYesYesRunningEither
Setting
NOLoss of
Network
Yes if
dependency
met
Yes when
dependency is
again met
YesRunningEither
Setting
Either
Setting
package
depended on
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 LAN interfaces 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 and Monitored Subnets
Each node (host system) should have an IP address for each active network interface.
This address, known as a stationary IP address, is configured in the file
/etc/sysconfig/network-scripts/ifcfg-<interface> on Red Hat or
68 Understanding Serviceguard Software Components