HP Serviceguard Version A.11.18 Release Notes, September 2008

ip_subnet_node
In a cross-subnet configuration, specifies which nodes an ip_subnet is configured on.
If no ip_subnet_nodes are listed under an ip_subnet, it is assumed to be configured on
all nodes in this package’s node_name list.
See also “monitored_subnet_access” and “About Cross-Subnet Configurations” (page 40).
New for modular packages. For legacy packages, see “Configuring Cross-Subnet
Failover” in Chapter 7 of Managing Serviceguard.
cluster_interconnect_subnet
Specifies an IPv4 address. Can be configured only for a multi-node package in a
Serviceguard Extension for Real Application Cluster (SGeRAC) installation. Can be
used in both modular and legacy packages.
(See the latest version of Using Serviceguard Extension for RAC at
http://www.docs.hp.com -> High Availability - > Serviceguard
Extension for Real Application Cluster (Serviceguard OPS Edition)
for more information.)
enable_threaded_vgchange
Indicates whether multi-threaded activation of volume groups (vgchange -T)is
enabled. New for modular packages. Available on HP-UX 11i v3 only.
Legal values are zero (disabled) or 1 (enabled). The default is zero.
Set enable_threaded_vgchange to 1 to enable vgchange -T for all of a package’s volume
groups. This means that when each 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.
Note that, in the context of a Serviceguard package, this affects the way physical volumes
are activated within a volume group; 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.
vxvm_dg_retry
Specifies whether to retry the import of a VxVM disk group, using vxdisk scandisks
to check for any missing disks that might have caused the import to fail.
Legal values are yes and no. yes means vxdisk scandisks will be run in the event
of an import failure. The default is no.
What’s in this Release 33