Using Serviceguard Extension for RAC, 5th Edition, June 2007

Introduction to Serviceguard Extension for RAC
Overview of SGeRAC Cluster Interconnect Subnet Monitoring
Chapter 1 27
the subnet on any other node does not affect the running instance.
No attempt will be made automatically to start the package instance
on the restored node. An attempt to start the instance of the package
on the restored node will be made, if the user explicitly tries to start
the package instance.
• If a multi-node package with CLUSTER_INTERCONNECT_SUBNET is
running on more than one node of the cluster, upon a failure of the
subnet on all nodes where the package is running, all but one
package instance will be halted one by one. Additionally if
NODE_FAIL_FAST_ENABLED is set to “YES” for such a package, all but
one node will be brought down one by one, that is one node will be
brought down, cluster reformation will happen, another node will be
brought down, cluster reformation will happen and so on till one
node remains in the cluster.
NOTE The CLUSTER_INTERCONNECT_SUBNET parameter is available only for
use with multi-node packages.
For more information on the Cluster Interconnect Subnet Monitoring
feature, refer to chapter 2, section “Cluster Communication Network
Monitoring” on page 62. This section describes various network
configurations for cluster communications in an SGeRAC/10g RAC
cluster, and how the package configuration parameter
CLUSTER_INTERCONNECT_SUBNET can be used to recover from Oracle
Cluster Communications network failures.