Serviceguard Extension for RAC Version A.11.19 Release Notes, March 2009

GMS authorization
SGeRAC provides a GMS authorization feature. This feature prevents unauthorized users to
access cluster information and register/de-register group memberships. A new parameter
GMS_USER[] in the /etc/opt/nmapi/nmutils.conf is used to set this feature. By default
this feature is disabled.
Support for 8192 Oracle Server Processes for Oracle 9iR2, 10gR2 and 11gR1 RAC
The maximum number of Oracle server processes cmgmsd can handle is 8192. When there are
more than 8192 server processes connected to cmgmsd, it will start to reject new requests. Oracle
foreground server processes are needed to handle the requests of the Database (DB) client
connected to the DB instance.
NOTE: Starting with Oracle 10g and later, Oracle Clusterware processes register with cmgmsd
while Oracle server processes register with Oracle Clusterware. The maximum number of Oracle
server processes supported is determined by Oracle Clusterware. The maximum number of
processes registered by Oracle Clusterware should not exceed the maximum supported by
cmgmsd.
Serviceguard Extension for RAC does not support Mixed Clusters
For SGeRAC, the nodes in the cluster must be on the same architecture. SGeRAC does not support
clusters containing mixed architectural nodes, which consist of HP 9000 and HP Integrity servers,
or different operating system releases.
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.
Agile addressing is the default on new 11i v3 installations, but the I/O subsystem still recognizes
pre-11i v3 device files, which as of 11i v3 are 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, but 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
Mass Storage Stack under Network and Systems Management -> Storage Area Management at
docs.hp.com).
Migration involves modifying system and application configuration files and scripts to use
persistent device files and in some cases new commands and options; the process is described
in the white papers Migrating from HP-UX 11i v2 to HP-UX 11i v3 and LVM Migration from Legacy
to Agile Naming Model HP-UX 11i v3 at http://docs.hp.com.
If you cold-install HP-UX 11i v3, sets of both legacy and persistent device files are automatically
created. In this case, by default the installation process will configure system devices such as the
boot, root, swap, and dump devices to use persistent device files. This means that system
What’s in this Version 11