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
NOTE: This also applies if HOSTNAME_ADDRESS_FAMILY is set to ANY. See
“Allowing Root Access to an Unconfigured Node” in Chapter 5 of Managing
Serviceguard for more information.
• If you use a Quorum Server, you must make sure that the Quorum Server hostname
(and the alternate Quorum Server address specified by QS_ADDR, if any) resolve
to IPv6 addresses.
IMPORTANT: You must use Quorum Server version A.04.00 or later. See the latest
Quorum Server release notes for more information; you can find them at
docs.hp.com under High Availability —> Quorum Server.
The Quorum Server itself can be an IPv6–only system; in that case it can serve
IPv6–only and mixed-mode clusters, but not IPv4–only clusters.
• If you use a Quorum Server, and the Quorum Server is on a different subnet from
cluster, you must use an IPv6-capable router.
• 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 in IPv6-only mode.
NOTE: This also applies if HOSTNAME_ADDRESS_FAMILY is set to ANY. See
“About Cross-Subnet Configurations” (page 37) for information about this type
of configuration.
• CFS, CVM, VxVM, and VxFS are not supported in IPv6–only mode.
NOTE: CFS and CVM should not be installed on any system in an IPv6–only
cluster, even if they are not configured.
This also means that the Serviceguard component of bundles that include
Serviceguard cannot be configured in IPv6 mode.
• HPVM is not supported in IPv6-only mode. You cannot configure a virtual machine
either as a node or a package in an IPv6-only cluster.
• Serviceguard Manager does not yet support IPv6-only mode; see “Current
Limitations of Serviceguard Manager” (page 33).
What’s in this Release 25