Using Serviceguard Extension for RAC, 8th Edition, March 2009

NOTE: CVM 4.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 3.x or 4.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 18)).
Do not enter the names of LVM volume groups or VxVM disk 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 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.
NOTE: A package with the CLUSTER_INTERCONNECT_SUBNET parameter is available for both
Modular and Legacy packages. A package with this parameter can be configured only when all
nodes of the cluster are running SGeRAC version A.11.18 or higher. For more information, see
the latest edition of the Managing Serviceguard Sixteenth Edition user’s guide at
http://docs.hp.com. -> High Availability.
Figure 2-1 Single Network for Cluster Communications
Cluster Communication Network Monitoring 37