HP Serviceguard manual How the Network Manager Works, Stationary and Relocatable IP Addresses

Table 4 Error Conditions and Package Movement for Failover Packages (continued)

Package Error Condition			Results
Error or Exit Code	Node Failfast	Service	HP-UX Status	Halt script	Package Allowed to	Package
	Enabled	Failfast	on Primary	runs after	Run on Primary	Allowed to Run
		Enabled	after Error	Error or Exit	Node after Error	on Alternate
						Node
Loss of Network	YES	Either Setting	system reset	No	N/A (system reset)	Yes
Loss of Network	NO	Either Setting	Running	Yes	Yes	Yes
Loss of Generic	YES	Either Setting	system reset	No	N/A (system reset)	Yes
Resource
Loss of Generic	NO	Either Setting	Running	Yes	Yes, if the resource	Yes
Resource					is not a
					during_package_start
					resource. No, if the
					resource is
					during_package_start.
Loss of Monitored	YES	Either Setting	system reset	No	N/A (system reset)	Yes
Resource
Loss of Monitored	NO	Either Setting	Running	Yes	Yes, if the resource	Yes
Resource					is not a deferred
					resource. No, if the
					resource is
					deferred.
dependency	Either Setting	Either Setting	Running	Yes	Yes when	Yes if
package failed					dependency is	dependency met
					again met

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-ipv6file. 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 109) and “Package Parameter Explanations” (page 233) 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.

How the Network Manager Works 67