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

Serviceguard Configuration for Oracle 10g RAC
Cluster Communication Network Monitoring
Chapter 268
for IMR time interval prior to resolving the subnet failure. In SGeRAC
configurations, default value of IMR time interval may be as high as
seventeen minutes.
CLUSTER_INTERCONNECT_SUBNET can be configured for RAC instance
MNP to monitor the RAC-IC subnet that is different from CSS-HB
subnet. The parameter file (SPFILE or PFILE) for RAC instances must
have cluster_interconnects parameter defined, to hold IP address in
the appropriate subnet if the RAC Instances use a RAC-IC network
different from CSS-HB network. No special subnet monitoring is needed
for CSS-HB Subnet because Serviceguard monitors the subnet
(heartbeat) and will handle failures of the subnet.
The database instances that use 192.168.2.0 must have
cluster_interconnects defined in their SPFILE or PFILE as follows:
orcl1.cluster_interconnects=’192.168.2.1’
orcl2.cluster_interconnects=’192.168.2.2’
NOTE Do not configure CLUSTER_INTERCONNECT_SUBNET in the RAC instance
package if the RAC-IC network is the same as CSS-HB network.
The following is an example of the relevant package configuration
parameters:
Oracle RAC Instance Package
PACKAGE_NAME RAC_PACKAGE
PACKAGE_TYPE MULTI_NODE
LOCAL_LAN_FAILOVER_ALLOWED YES
NODE_FAIL_FAST_ENABLED NO
CLUSTER_INTERCONNECT_SUBNET 192.168.2.0
NOTE For information on guidelines to change certain Oracle Clusterware and
Serviceguard cluster configuration parameters, see “Guidelines for
Changing Cluster Parameters” on page 72