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

8
The network traffic between cluster nodes can be categorized as follows:
• SG-HB–SG-HB and communications traffic—supported over single or multiple subnets
• CSS-HB–CSS-HB traffic and communications traffic for OC—use a single logical connection over a
single subnet network
• RAC-DB-IC–RAC instance peer-to-peer traffic and communications for Global Cache Service (GCS)
and Global Enqueue Service (GES), formerly Cache Fusion (CF) and Distributed Lock Manager
(DLM)—network HA is provided by the HP-UX 11i platform (SG or APA bonding)
• GAB/LLT—applicable only when using CFS/CVM, Veritas cluster heartbeat, and communications
traffic; communicates over link-level protocol (DLPI [Data Link Provider Interface]) and is supported
over SG-HB subnets, including primary and standby links
Note that each category maintains its own timeout, after which members will be evicted.
The interconnect network requires HA configurations. When a single network failure occurs—for
example a LAN card or switch failure—all cluster nodes continue to operate. Without HA, a single
network failure results in a network partition, and evicted nodes are halted.
Using SG primary and standby links is the preferred HA model to provide HA for a cluster
communications interconnect network. SG primary and standby links provide redundancy, while SG
monitors the network and performs local failover if the primary network becomes unavailable.
General principles
HP recommends having all interconnect traffic for cluster communications on a single heartbeat
network with a standby interface. This configuration allows SG to monitor the network, detect
interconnect failures, and resolve failures by reconfiguring the cluster.
In the following cases, it is not possible to place all interconnect traffic on the same network:
• If RAC GCS (cache fusion) traffic is very high, a separate network for RAC-DB-IC is needed.
Otherwise, one RAC-DB-IC may interfere with another RAC-DB-IC in the same cluster. RAC-DB-IC
may also interfere with heartbeat traffic.
• If RAC-DB-IC is configured on InfiniBand, it should be on a separate network. InfiniBand networks
are not supported by CFS/CVM.
• Certain configurations for fast reconfiguration require at least one SG-HB network; CSS-HB and
RAC-DB-IC do not support multiple networks for HA purposes.
In these cases, unless special logic is developed, you may experience a longer time to recover from
network failures that are not protected by primary and standby links.
Note: Starting with SG A.11.19, faster failover capability is integrated with the base SG product.
Cluster interconnect configurations for CFS and CVM
Configurations with CFS and CVM include GAB/LLT traffic.