Sample Configuration with HP Serviceguard Extension for RAG and Oracle Real Application Clusters 11g release 2 using Cluster File System

Figure 1. Preferred: single subnet with Ethernet primary and standby, including GAB/LLT

Figure 1 shows a common configuration where SG-HB, CSS-HB, RAC-DB-IC, and GAB/LLT share the

same network for cluster communications. This configuration is recommended and suitable for most

installations where the RAC traffic does not saturate the network and negatively impact other

components (SG-HB, CSS-HB, and GAB/LLT traffic). There is one network with sufficient bandwidth. A

failure of the primary network is protected by SG local LAN failover for SB-HB, CSS-HB, and RAC-DB-

IC. GAB/LLT uses both the primary (LAN1) and the standby (LAN2) for communications, so GAB/LLT

can tolerate a failure of either the primary or standby links. Node failure is detected by SG when it

misses heartbeats.

Configurations with heavy RAC-DB-IC traffic may place a limit on how aggressive an SG

MEMBER_TIMEOUT setting can be used, because the SG-HB may not be processed in time. A longer

MEMBER_TIMEOUT may be needed to avoid false cluster reconfigurations.

Figure 2. Dual SG-HBs with a CSS-HB and RAC-DB-IC on a single subnet including GAB/LLT