Using Serviceguard Extension for RAC, 10th Edition, April 2011

• cDSFs are not supported by CVM, CFS, or any other application that assumes DSFs reside
only in /dev/disk and /dev/rdisk.
• cDSFs do not support disk partitions.
Such partitions can be addressed by a device file using the agile addressing scheme, but not
by a cDSF.
For more information about Cluster-wide Device Special Files (cDSFs), see the Managing
Serviceguard, Eighteenth Edition manual at www.hp.com/go/hpux-serviceguard-docs —>
HP Serviceguard .
Configuration File Parameters
You need to code specific entries for all the storage groups that you want to use in an Oracle RAC
configuration. If you are using LVM, the OPS_VOLUME_GROUP parameter is included in the cluster
ASCII file. If you are using Veritas CVM, the STORAGE_GROUP parameter is included in the package
ASCII file. Details are as follows:
OPS_VOLUME_GROUP The name of an LVM volume group whose disks are attached to at least
two nodes in the cluster. The disks will be accessed by more than one
node at a time using SLVM with concurrency control provided by Oracle
RAC. Such disks are considered cluster aware.
Volume groups listed under this parameter are marked for activation in
shared mode. The entry can contain up to 40 characters.
STORAGE_GROUP This parameter is used for CVM disk groups. Enter the names of all the
CVM disk groups the package will use.
In the ASCII package configuration file, this parameter is called
STORAGE_GROUP.
Unlike LVM volume groups, CVM disk groups are not entered in the cluster configuration file, they
are entered in the package configuration file.
NOTE: CVM 5.x or later with CFS does not use the STORAGE_GROUP parameter because the
disk group activation is performed by the multi-node package. CVM 5.x and later without CFS
uses the STORAGE_GROUP parameter in the ASCII package configuration file in order to activate
the disk group (on HP-UX releases that support Veritas CFS and CVM). See “About Veritas CFS
and CVM from Symantec” (page 16).
Do not enter the names of LVM volume groups in the package ASCII configuration file.
Cluster Communication Network Monitoring
This section describes the various network configurations for cluster communications in a
SGeRAC/10g/11gR1/11gR2 RAC cluster, and how the package configuration parameter
CLUSTER_INTERCONNECT_SUBNET can be used to recover from Oracle cluster communications
network failures in certain configurations.
Single Network for Cluster Communications
The single network configuration is the most common configuration for network installations. In this
configuration, there is sufficient bandwidth for all cluster communications traffic to go through one
network. If there are multiple databases, all database traffic goes through the same network.
As shown in Figure 2-1, both CSS-HB and SG-HB are on the same network. The primary and
standby interface pair protects against a single network interface failure. Serviceguard monitors
the network and will perform a local LAN failover (transparent to CSS and RAC) if the primary
interface fails.
36 Serviceguard Configuration for Oracle 10g, 11gR1, or 11gR2 RAC