Serviceguard Extension for RAC Version A.11.20 Release Notes - (August 2011)

After you deploy Oracle RAC, using the -d option with cmhaltcl (or cmhaltnode) command
on a node in an SGeRAC cluster where CRS are running will return an error message and the
cmhaltcl (or cmhaltnode) command is aborted.
NOTE: In a mixed Serviceguard A.11.20 patch environment, where Serviceguard A.11.20 Patch
PHSS_42137 is installed on some nodes and the other nodes of the cluster are on patch levels
earlier to Serviceguard A.11.20 Patch PHSS_42137, then commands like cmhaltcl -d and
cmhaltnode -d will return an error message, if executed from the nodes which are on patch
levels lower than Serviceguard A.11.20 Patch PHSS_42137. cmhaltcl -d or cmhaltnode
-d command aborts though CRS is not running on any of the nodes.
For example: Consider a two node cluster with Serviceguard A.11.20 Patch PHSS_42137 in one
node and Serviceguard A.11.19 Patch PHSS_42216 in the other node. In this scenario, if you
run cmhaltcl -d and cmhaltnode -d command from the node with Serviceguard A.11.19
Patch PHSS_42216, then an error message is generated and cmhaltcl -d and cmhaltnode
-d is aborted.
NOTE: Live Application Detach is not supported for clusters using the Veritas Cluster Volume
Manager (CVM) or Cluster File System (CFS).
Live Application Detach feature is not supported in an SGeRAC with Metrocluster Site Aware
Disaster Tolerant Architecture (SADTA) environment.
Mixed Hardware Architecture Cluster not Supported
All nodes in an SGeRAC cluster must be of the same hardware architecture. For example, a single
cluster cannot include both HP 9000 and HP Integrity nodes.
NOTE: Rolling upgrades are not intended as a means of using mixed releases of HP-UX,
Serviceguard, or SGeRAC within the same cluster. HP recommends to upgrade all the cluster nodes
to the new release level at the earliest.
Announcements for HP-UX 11i v3
• SGeRAC A.11.20 on HP-UX 11i v3 supports LVM version 1.0, 2.0, or later.
• SGeRAC A.11.20 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 Agile Addressing and Cluster-wide Device Special Files (cDSFs)
HP-UX releases up to and including 11i v3 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
agile addressing on HP-UX 11i v3, each device has a unique identifier as seen from a given host.
This identifier is reflected in the name of the Device Special File (DSF).
Agile Addressing
Agile addressing is the default on new 11i v3 installations, but the I/O subsystem still recognizes
pre-11i v3 device files, referred to as legacy device files. Device files using the new nomenclature
are called persistent device files. When you upgrade to HP-UX 11i v3, a set of new, persistent
device files is created. The existing legacy device files are left intact and by default will continue
to be used by HP-UX and Serviceguard.
This means that you are not required to migrate to agile addressing when you upgrade to 11i v3,
though you should seriously consider its advantages (see the white paper The Next Generation
8 Serviceguard Extension for RAC Version A.11.20 Release Notes