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
Recommendation for IPv6-Only Mode
If you decide to migrate the cluster to IPv6-only mode, you should plan to do so while
the cluster is down.
Rules and Restrictions for Mixed Mode
• 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” in Chapter 5 of Managing Serviceguard.
• 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” in Chapter 5 of Managing
Serviceguard 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 “About
Cross-Subnet Configurations” (page 37) for more information.
• CFS, CVM, VxVM, and VxFS are not supported.
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.
Restrictions if You Have Not Applied the July 2009 Patch
A.11.19 without the patch supports only IPv4–only and mixed-mode clusters; you
cannot configure an IPv6–only cluster.
In addition, 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
26 Serviceguard Version A.11.19 Release Notes