HP Serviceguard Version A.11.19 Release Notes, March 2009

• A new cluster parameter, NETWORK_AUTO_FAILBACK, tells Serviceguard how
to handle the recovery of the primary LAN interface after it has failed over to the
standby interface because of a link level failure. See the description of this parameter
under “Cluster Configuration Parameters” in Chapter 4 of Managing Serviceguard.
• A new parameter, CONFIGURED_IO_TIMEOUT_EXTENSION, must be set for
extended-distance clusters using iFCP interconnects between sites. See the manual
Understanding and Designing Serviceguard Disaster Tolerant Architectures on
docs.hp.com —> High Availability —> Serviceguard for more
information.
The following features were first introduced in a patch to A.11.18:
• Serviceguard provides a means of automatically migrating existing (legacy)
packages to modular packages. See “Migrating Legacy to Modular Packages”
(page 31).
• Further package capabilities, additional to those introduced in Serviceguard A.11.19,
are described under “Other Package Changes First Introduced in Serviceguard
A.11.18 Patches” (page 32).
• Serviceguard supports cross-subnet configurations.
You can 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 33).
— Additional changes (including the addition of the parameters SITE_NAME and
SITE to the cluster configuration file) support site-aware disaster-tolerant
clusters, which require additional software (see “For More Information”
(page 35)).
• You can configure an alternate subnet for communication between the cluster
nodes and a Quorum Server. See “Alternate Quorum Server Subnet” (page 37).
• Serviceguard support Veritas 5.0 from Symantec; see “Support for Veritas 5.0 on
HP-UX 11i v2 and 11i v3” (page 39).
• There is a new volume monitor for VxVM and CVM. See “About the VxVM Volume
Monitor” (page 35).
What’s in this Release 21