HP Serviceguard Version A.11.19 Release Notes, July 2009
Table Of Contents
- HP Serviceguard Version A.11.19 Release Notes
- Table of Contents
- Printing History
- 1 Serviceguard Version A.11.19 Release Notes
- Announcements
- Platform Dependencies
- July 2009 Patches
- Serviceguard Bundled Components - New Product Structure
- Serviceguard Optional Products Not Bundled
- New Cluster Manager
- Serviceguard A.11.19 Is the Required Basis for Future Rolling Upgrades
- Quorum Server Upgrade Required if You Are Using an Alternate Address
- Serviceguard Manager Available from the System Management Homepage (SMH)
- Support for Mixed-OS Clusters (HP–UX 11i v2 and 11i v3)
- Version 5.0 of Veritas CVM and CFS from Symantec Required
- Version 3.5, 4.0, or 4.1 of HPVM Required
- ipnodes Entries Needed in /etc/nsswitch.conf
- Legacy Packages
- .rhosts Deprecated
- cmviewconf Deprecated
- Serviceguard Extension for Faster Failover Obsolete
- RS232 Heartbeat Obsolete
- Token Ring and FDDI Obsolete
- Parallel SCSI Dual Cluster Lock Obsolete
- Parallel SCSI Not Supported for Lock LUN
- Cluster Name Restrictions
- Optimizing Performance when Activating LVM Volume Groups
- High Availability Consulting Services
- Announcements for HP-UX 11i v2
- Announcements for HP-UX 11i v3
- What’s in this Release
- New Features for July 2009 Patches
- Features Introduced in A.11.19
- Serviceguard on HP-UX 11i v3
- What’s Not in this Release
- About the New Features
- Features Introduced Before A.11.19
- Features First Introduced in Serviceguard A.11.18 Patches
- Features First Introduced Before Serviceguard A.11.18
- Documents for This Version
- Further Information
- Compatibility Information and Installation Requirements
- Installing Serviceguard on HP-UX
- Uninstalling Serviceguard
- Patches for this Version
- Fixed in This Version
- Known Problems
- About Serviceguard Releases
- Release Notes Revisions
- Native Languages
- Announcements
Package Weight Feature, which you can find at the address given under “Documents for
This Version ” (page 47).
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.
In addition, with the patches listed under “July 2009 Patches” (page 11), you can
configure an IPv6–only cluster; and the Quorum Server, if used, can also be an IPv6–only
system. The following are the possibilities for resolving the nodes' hostnames (and
Quorum Server hostnames, if any) to network address families:
• IPv4-only
• IPv6-only (requires July 2009 patch)
• Mixed
The default is IPv4. You can change it either by editing the cluster configuration file
and setting the appropriate value for the HOSTNAME_ADDRESS_FAMILY parameter,
or by using the new -a option of cmquerycl (1m). For more information, see “About
Hostname Address Families: IPv4-Only, IPv6-Only, and Mixed Mode” in Chapter 4 of
the latest version of Managing Serviceguard, at the address given under “Documents
for This Version ” (page 47).
Some restrictions apply, as follows.
Rules and Restrictions for IPv6-Only Mode
• You cannot use DNS or NIS for name-resolution in an IPv6–only cluster.
• You cannot use WBEMProvider or the SNMP Subagent in an IPv6–only cluster.
• You cannot configure an IPv6–only Continentalcluster.
• All addresses used by the cluster must be in each node's /etc/hosts file.
In addition, the file must contain the following entry:
::1 localhost ipv6-localhost ipv6-loopback
• All addresses must be IPv6, apart from the node's IPv4 loopback address, which
cannot be removed from /etc/hosts.
• The node's public LAN address (by which it is known to the outside world) must
be the last address listed in /etc/hosts.
Otherwise there is a possibility of the address being used even when it is not
configured into the cluster.
• You must use $SGCONF/cmclnodelist, not ~/.rhosts or /etc/hosts.equiv,
to provide root access to an unconfigured node.
24 Serviceguard Version A.11.19 Release Notes