Serviceguard Extension for RAC Version A.11.19 Release Notes, October 2009 (T1907-90051)

NOTE: All nodes in a given cluster must be running the same version of HP-UX. See
“Mixed Clusters not Supported” (page 9).
SGeRAC can be installed on top of the HP-UX 11i v2 and 11i v3 Mission Critical
Operating Environment (MCOE), and the 11i v3 High Availability Operating
Environment (HAOE) or Data Center Operating Environment (DCOE). It is not
necessary to uninstall Serviceguard filesets before installing SGeRAC.
NOTE: If the version of Serviceguard in the MCOE, HAOE, or DCOE is not A.11.19,
you must first upgrade to Serviceguard version A.11.19. For Serviceguard upgrade
requirements, see the latest version of the Serviceguard Version A.11.19 Release Notes; for
procedures, see the latest version of Managing Serviceguard.
For information about capabilities available only on HP-UX 11i v3, see “Announcements
for HP-UX 11i v3” .
Serviceguard Features Not Yet Supported
Serviceguard cross-subnet configurations are currently not supported with SGeRAC.
Mixed Clusters not Supported
All nodes in a SGeRAC cluster must be of the same hardware type and running the
same version of the same operating system. For example, a single cluster cannot include
both HP 9000 and HP Integrity nodes, or run both HP-UX 11i v2 and 11i v3.
Announcements for HP-UX 11i v3
• SGeRAC A.11.19 on HP-UX 11i v3 supports LVM version 2.0 or later.
• SGeRAC A.11.19 on HP-UX 11i v3 supports Dynamic Root Disk (DRD). See
“Upgrade Using DRD” (page 16).
In addition, HP-UX 11i v3 itself introduces important improvements, particularly in
regard to the I/O subsystem, as described below.
About Device Special Files (DSFs)
HP-UX releases up to and including 11i v2 use a naming convention for device files
that encodes their hardware path. For example, a device file named /dev/dsk/
c3t15d0 would indicate SCSI controller instance 3, SCSI target 15, and SCSI LUN 0.
HP-UX 11i v3 introduces a new nomenclature for device files, known as agile addressing
(sometimes also called persistent LUN binding). Under the agile addressing convention,
the hardware path name is no longer encoded in a storage device’s name; instead, each
device file name reflects a unique instance number, for example /dev/[r]disk/
disk3, that does not need to change when the hardware path does.
Announcements 9