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

NODE_FAIL_FAST_ENABLED parameter is set to NO for the Oracle Clusterware package, and is

set to YES for the package monitoring CSS-HB subnet (Oracle Cluster Interconnect Subnet Package

as shown in the package configuration parameters examples below).

NOTE: Do not configure CLUSTER_INTERCONNECT_SUBNET in the RAC Instance package

due to the RAC-IC network being the same as CSS-HB network.

The following is an example of the relevant package configuration parameters:

Oracle Clusterware Package:

PACKAGE_NAME CRS_PACKAGE

PACKAGE_TYPE MULTI_NODE

LOCAL_LAN_FAILOVER_ALLOWED YES

NODE_FAIL_FAST_ENABLED NO

DEPENDENCY_NAME CI-PACKAGE

DEPENDENCY_CONDITION CI-PACKAGE=UP

DEPENDENCY_LOCATION SAME_NODE

Oracle Cluster Interconnect Subnet Package: Package to monitor the CSS-HB subnet

PACKAGE_NAME CI-PACKAGE

PACKAGE_TYPE MULTI_NODE

LOCAL_LAN_FAILOVER_ALLOWED YES

NODE_FAIL_FAST_ENABLED YES

CLUSTER_INTERCONNECT_SUBNET 192.168.1.0

NOTE: For information on guidelines to change certain Oracle Clusterware and Serviceguard

cluster configuration parameters, see “Guidelines for Changing Cluster Parameters” (page 40)

Alternate Configuration - Multiple RAC Databases

When there are multiple independent RAC databases on the same cluster and if there is insufficient

bandwidth over a single network, a separate network can be used for different database

interconnect traffic. This will avoid RAC-IC traffic of one database from interfering with that of

another.

Figure 2-3 RAC/RAC-IC Traffic Separation – Multiple Database Configuration

As shown in Figure 2-3, each primary and standby pair protects against a single failure. If the

subnet with SG-HB (lan1/lan2) fails, Serviceguard will resolve the subnet failure with a

Serviceguard cluster reconfiguration. If the 192.168.2.0 subnet (lan3 and lan4) fails, Oracle instance

membership recovery (IMR) will resolve the interconnect failure subnet, unless Serviceguard

subnet monitoring is used. Oracle will wait for IMR time interval prior to resolving the subnet

Cluster Communication Network Monitoring 39