HP Serviceguard for Linux Version A.11.18 Release Notes, 2nd Edition, March 2009

See the subsections that follow for details; see also the “Announcements” (page 11).
For information about documentation, see “What Documents are Available for This
Version ” (page 48).
• There is a new, modular method of configuring packages; see “About Modular
Packages” (page 18).
— In addition, in the patches listed under “New Features for March 2008 Patches”
(page 14), Serviceguard provides a means of automatically migrating existing
(legacy) packages to modular packages. See “Migrating Legacy to Modular
Packages” (page 28).
• A new Serviceguard Manager graphical user interface (GUI) is being supplied as
a plug-in to the System Management Homepage (SMH). See “About the
Serviceguard Manager SMH Plug-In” (page 38).
The A.05.01 standalone version of Serviceguard Manager (also known as the
station-management version) is obsolete, though it is still needed if you want to
manage multiple clusters from a single point; see “Launching Serviceguard
Manager: Three Scenarios” (page 40).
• You can now configure a package to be dependent on another package. See “About
Package Dependencies” (page 28).
• You can now create multi-node packages. See “About Multi-Node Packages”
(page 29).
• Other new package capabilities are provided in the patches listed in the section
headed “New Features for March 2008 Patches” (page 14); see “Other Package
Changes” (page 29).
• Serviceguard for Linux, with the patches listed in the section headed “New Features
for March 2008 Patches” (page 14), now supports HP Integrity Virtual Machines
(HPVM) and VMware ESX Server.
See “Support for HPVM and VMware ESX Server” (page 34).
• There are new networking capabilities:
— Serviceguard now supports cross-subnet configurations.
The patches listed under “March 2008 Patches (A.11.18.03)” (page 11) allow
you to configure multiple subnets, joined by a router, both for the cluster
heartbeat and for data, with some nodes using one subnet and some another.
See “About Cross-Subnet Configurations” (page 30).
— You can now make significant changes to the cluster’s networking configuring
while the cluster is running; see “New Online Networking-Configuration
Capabilities” (page 32).
— You can now use cmmodnet to enable or disable a LAN_name currently
configured in a cluster. (Note that if you use cmmodnet to disable a LAN_name
on a node that subsequently leaves the cluster, the LAN_name will be re-enabled
if the node then rejoins the cluster.) Extreme caution should be exercised when
16 Serviceguard for Linux Version A.11.18 Release Notes