IPv6 addresses. Serviceguard will first try to resolve a node's hostname to an IPv4 address, then, if that fails, will try IPv6.

Rules and Restrictions for Mixed Mode

IMPORTANT: See the latest version of the Serviceguard release notes for the most current information on these and other restrictions.

The hostname resolution file on each node (for example, /etc/hosts) must contain entries for all the IPv4 and IPv6 addresses used throughout the cluster, including all STATIONARY_IP and HEARTBEAT_IP addresses as well any private addresses. There must be at least one IPv4 address in this file (in the case of /etc/hosts, the IPv4 loopback address cannot be removed).

In addition, the file must contain the following entry:

::1 localhost ipv6-localhost ipv6-loopback

For more information and recommendations about hostname resolution, see “Configuring Name Resolution” (page 168).

You must use $SGCONF/cmclnodelist, not ~/.rhosts or /etc/hosts.equiv, to provide root access to an unconfigured node.

See “Allowing Root Access to an Unconfigured Node” (page 166) for more information.

Hostname aliases are not supported for IPv6 addresses, because of operating system limitations.

NOTE: This applies to all IPv6 addresses, whether HOSTNAME_ADDRESS_FAMILY is set to

IPV6 or ANY.

Cross-subnet configurations are not supported.

This also applies if HOSTNAME_ADDRESS_FAMILY is set to IPV6. See “Cross-Subnet Configurations” (page 30) for more information.

VxVM, VxFS, and CVM/CFS are supported on HP Serviceguard A.11.20 April 2011 patches with Veritas Storage Foundation™ 5.1 SP1 and later.

NOTE: This also applies if HOSTNAME_ADDRESS_FAMILY is set to IPV6.

HPVM is not supported.

You cannot have a virtual machine that is either a node or a package if

HOSTNAME_ADDRESS_FAMILY is set to ANY or IPV6.

Cluster Configuration Parameters

You need to define a set of cluster parameters. These are stored in the binary cluster configuration file, which is distributed to each node in the cluster. You configure these parameters by editing the cluster configuration template file created by means of the cmquerycl (1m) command, as described under “Configuring the Cluster ” (page 186).

NOTE: See “Reconfiguring a Cluster” (page 291) for a summary of changes you can make while the cluster is running.

The following parameters must be configured:

CLUSTER_NAME

The name of the cluster as it will appear in the output of

 

cmviewcl and other commands, and as it appears in the

 

cluster configuration file.

Cluster Configuration Planning 109

Page 109
Image 109
HP Serviceguard manual Cluster Configuration Parameters, Rules and Restrictions for Mixed Mode, Cluster configuration file