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

Capacity and Package Weight Feature, which you can find on docs.hp.com under High
Availability —> Serviceguard —> White Papers.
New Support for IPv6
Serviceguard A.11.19 allows you to choose either the IPv4 or the IPv6 address family
for any subnet configured into the cluster, including subnets that carry the cluster
heartbeat. For SLES 10 only, you can also configure IPv6 connections to the Quorum
Server.
Some additional restrictions apply; for details see the latest version of Managing
Serviceguard for Linux, especially the parameter descriptions for
HOSTNAME_ADDRESS_FAMILY, STATIONARY_IP, HEARTBEAT_IP, QS_HOST,
and QS_ADDR under “Cluster Configuration Parameters” in chapter 4, and the section
“Configuring Name Resolution” in Chapter 5.
Use the new HOSTNAME_ADDRESS_FAMILY cluster parameter to tell Serviceguard
whether to attempt to resolve hostnames to addresses to IPv4 addresses only (IPv4)
or to both IPv4 and IPv6 (ANY).
IMPORTANT:
• You cannot configure an IPv6 connection to the Quorum Server (QS_HOST or
QS_ADDR) on Red Hat 5.
• Quorum Server version A.04.00 is required for IPv6 Quorum Server addresses.
• You cannot use cmquerycl -q to configure IPv6 addresses (or hostnames that
resolve only to IPv6 addresses) for QS_HOST and QS_ADDR. You must generate
a cluster template file and then edit it to set the appropriate (IPv6) values for
QS_HOST and QS_ADDR, and set HOSTNAME_ADDRESS_FAMILY to ANY, and
then use cmapplyconf to apply the configuration. See the latest version of the
HP Serviceguard Quorum Server Version A.04.00 Release Notes on docs.hp.com —>
High Availability —> Quorum Server for more information.
About the IP Monitor
In addition to monitoring network interfaces at the link level, Serviceguard A.11.19
can also monitor the IP level, checking Layer 3 health and connectivity for both IPv4
and IPv6 subnets. This is done by the IP Monitor, which is configurable: you can enable
IP monitoring for any subnet configured into the cluster, but you do not have to monitor
any. You can configure IP monitoring for a subnet, or turn off monitoring, while the
cluster is running.
For more information, see the section “Monitoring LAN Interfaces and Detecting Failure:
IP Level ” in Chapter 3 of Managing Serviceguard for Linux.
16 Serviceguard for Linux Version A.11.19 Release Notes