Managing Serviceguard Sixteenth Edition, March 2009

NOTE: last_halt_failed appears only in the line output of cmviewcl, not the
default tabular format; you must use the -v and -f line options to see it.
The value of last_halt_failed is no if the halt script ran successfully, or was not
run since the node joined the cluster, or was not run since the package was configured
to run on the node; otherwise it is yes.
About Cross-Subnet Failover
It is possible to configure a cluster that spans subnets joined by a router, with some
nodes using one subnet and some another. This is known as a cross-subnet
configuration; see “Cross-Subnet Configurations” (page 41). In this context, you can
configure packages to fail over from a node on one subnet to a node on another.
The implications for configuring a package for cross-subnet failover are as follows:
• For modular packages, you must configure two new parameters in the package
configuration file to allow packages to fail over across subnets:
— ip_subnet_node (page 273) - to indicate which nodes a subnet is configured on
— monitored_subnet_access (page 271) - to indicate whether a monitored subnet is
configured on all nodes (FULL) or only some (PARTIAL). (Leaving
monitored_subnet_access unconfigured for a monitored subnet is equivalent to
FULL.)
(For legacy packages, see “Configuring Cross-Subnet Failover” (page 347).)
• You should not use the wildcard (*) for node_name (page 263) in the package
configuration file, as this could allow the package to fail over across subnets when
a node on the same subnet is eligible. Failing over across subnets can take longer
than failing over on the same subnet. Instead, list the nodes in order of preference.
• Each subnet interface (NIC) used by the package must have a standby interface
on the local bridged net.
The standby interface can be shared between subnets.
188 Planning and Documenting an HA Cluster