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: In all three cases, the discussion refers to mixing HP-UX versions 11i v2 and
11i v3. Unless explicitly stated otherwise, “version” in this subsection means HP-UX
version, not Serviceguard version.
• Homogeneous cluster refers to a cluster that is not being upgraded, and which
has no need to include nodes running different major versions of HP-UX. See “HP
Recommendation for Homogeneous Clusters” (page 51).
• Cluster in transition refers to a cluster whose HP-UX version is being upgraded
as part of a normal rolling upgrade that occurs over a relatively short period. See
“Rules and Restrictions for Clusters in Transition” (page 51).
• Heterogeneous cluster refers to a cluster that contains a mix of nodes running
HP-UX 11i v2 and 11i v3. See “Rules and Restrictions for Heterogeneous Clusters”
(page 52).
Such a cluster is either being upgraded from HP-UX 11i v2 to 11i v3 over an
extended period, or for some other reason needs to accommodate nodes running
both versions of HP-UX (for example you might have purchased a new server,
running HP-UX 11i v3, and want to add it to an existing cluster whose nodes are
running 11i v2).
HP Recommendation for Homogeneous Clusters
All nodes should be running the same major HP-UX version. Major version means a
release such as 11i v2 or 11i v3. It is acceptable to have a mix of different HP-UX Fusion
releases for the same major revision (for example, 11i v2 September 2004 and 11i v2
September 2006), although it is generally best to have all nodes running the same Fusion
release at the same patch level.
Rules and Restrictions for Clusters in Transition
You can upgrade a cluster from HP-UX 11i v2 to 11i v3 as part of a rolling upgrade. A
rolling upgrade includes upgrading to a new version of Serviceguard. Rules, guidelines,
and restrictions for rolling upgrades are in Appendix D of Managing Serviceguard, which
you can find at the address given under “Documents for This Version ” (page 47). See
also “Upgrading from an Earlier Serviceguard Release” (page 59).
It is also possible to upgrade the HP-UX version without upgrading Serviceguard, and
so avoid the rolling upgrade restrictions. In this case you must make sure that:
Compatibility Information and Installation Requirements 51