HP Serviceguard A.11.20 Release Notes, September 2012

• Support for Shared LVM (SLVM) in an HPVM environment only — that is, when the cluster
includes virtual machines (either as nodes or within packages) that are managed by HPVM.
For more information, see HP-UX vPars and Integrity VM V6.1 Administrator Guide at http://
www.hp.com/go/hpux-hpvm-docs. For more information about using HPVM in a Serviceguard
cluster, see “Support for HP Integrity Virtual Machines (HPVM)” (page 33).
• Improved support for nested mount points.
Serviceguard now ensures that a package will never attempt to mount a nested directory
concurrently with the parent, no matter what
concurrent_mount_and_umount_operations is set to. (In earlier releases, this could
happen if concurrent_mount_and_umount_operations was set to a value greater
than 1.)
See also:
• “About LVM 2.x” (page 31)
• “Serviceguard on HP-UX 11i v3” (page 14)
Features First Introduced Before Serviceguard A.11.19
About olrad
You must remove a LAN or VLAN interface from the cluster configuration before removing it from
the system. You can do this without bringing down the cluster.
HP-UX 11i v3 provides a new option for the olrad command, olrad -C, to help you determine
whether or not an interface is part of the cluster configuration: run olrad -C with the affected
I/O slot ID as argument.
If the NIC is part of the cluster configuration, you’ll see a warning message telling you to remove
it from the configuration before you proceed. See the olrad(1M) manpage for more information
about olrad.
After removing the NIC from the cluster configuration, you can remove it from an HP-UX 11i v3
cluster node without shutting down the system by running olrad -d.
See “Removing a LAN or VLAN Interface from a Node” in Chapter 7 of Managing Serviceguard
for more information.
About vgchange -T
Serviceguard supports vgchange -T, which allows multi-threaded activation of volume groups
on HP-UX 11i v3 systems.
This means that when the volume group is activated, physical volumes (disks or LUNs) are attached
to the volume group in parallel, and mirror copies of logical volumes are synchronized in parallel,
rather than serially. That can improve a package’s startup performance if its volume groups contain
a large number of physical volumes.
To enable vgchange -T for all of a package’s volume groups, set enable_threaded_vgchange
to 1 in the package configuration file (the default is 0, meaning that multi-threaded activation is
disabled).
Note that, in the context of a Serviceguard package, this affects the way physical volumes are
activated within a volume group; another package parameter,
concurrent_vgchange_operations, controls how many volume groups the package can
activate simultaneously.
IMPORTANT: Make sure you read the configuration file comments for both
concurrent_vgchange_operations and enable_threaded_vgchange before configuring
these options, as well as the vgchange (1m) manpage.
30 Serviceguard Version A.11.20 Release Notes