HP Serviceguard Version A.11.19 Release Notes, March 2009

the same time, but, if the large node fails, you want only the critical packages to run

on the smaller system. Package weights allow you to configure Serviceguard to enforce

this behavior.

For more information, see “About Package Weights” in Chapter 4 of the latest version

of Managing Serviceguard, and the white paper Using Serviceguard’s Node 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, and those connected to a Quorum Server. Some restrictions apply; for details

see the latest version of Managing Serviceguard, especially the parameter descriptions

for STATIONARY_IP, HEARTBEAT_IP, QS_HOST, and QS_ADDR under “Cluster

Configuration Parameters”, and the section “Configuring Name Resolution” in Chapter

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:

• 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 “About the IP Monitor” in Chapter 3 of Managing

Serviceguard

24 Serviceguard Version A.11.19 Release Notes