HP Serviceguard for Linux Version A.11.19 Release Notes, April 2009

monitored for this package are configured for PARTIAL access, each node on the
node_name list must have at least one of these subnets configured.
— As in other configurations, a package will not start on a node unless the subnets
configured on that node, and specified in the package configuration file as
monitored subnets, are up.
• You cannot use Serviceguard Manager to configure a cross-subnet cluster or
package.
For More Information
For more information on the details of configuring the cluster and packages in a
cross-subnet context, see the following sections in Managing Serviceguard for Linux, at
http://docs.hp.com -> High Availability -> Serviceguard: “Obtaining
Cross-Subnet Information” in Chapter 5, “About Cross-Subnet Failover” in Chapter 4,
and (for legacy packages only) “Configuring Cross-Subnet Failover” in Chapter 7.
IMPORTANT: Although cross-subnet topology can be implemented on a single site,
it is most commonly used by extended-distance clusters.
Design and configuration of such clusters are covered in the disaster-tolerant
documentation delivered with Serviceguard. For more information, see Understanding
and Designing Serviceguard Disaster Tolerant Architectures at http://www.docs.hp.com
-> High Availability.
Migrating Legacy to Modular Packages
A new Serviceguard command, cmmigratepkg, first introduced in a patch to A.11.18,
automates the process of migrating legacy packages to modular packages as far as
possible. Many, but not all, packages can be migrated in this way; for details, see the
white paper Migrating Packages from Legacy to Modular Style at http://docs.hp.com
->High Availability ->Serviceguard ->White papers.
NOTE: The cmmigratepkg command requires Perl version 5.8.5 or higher on the
system on which you run the command. It should already be on the system as part of
the Linux distribution.
Other Package Changes
The patches listed under “New Features First Introduced in Serviceguard for Linux
A.11.18 Patches” (page 22) provide the following new capabilities:
• Serviceguard now supplies information explaining why a package has shut down.
Serviceguard will set the new environment variable SG_HALT_REASON to one
of the following values when the package halts:
24 Serviceguard for Linux Version A.11.19 Release Notes