Architecture considerations and best practices for architecting an Oracle RAC solution with Serviceguard and SGeRAC

14
Private network configuration
There are a number of choices available when configuring the private network for the combined
Oracle RAC and SGeRAC stack. This section discusses several different options and the supported HA
configuration for each option.
Configuration Option 1—recommended configuration
In this configuration, Serviceguard heartbeat, CFS interconnect (if CFS is used), Oracle Clusterware CSS
heartbeat, and RAC interconnect are configured on the same network. Since Serviceguard’s heartbeat is
sent over this network, Serviceguard will monitor this network. If a node’s connection to this network is
down, Serviceguard will evict the impacted node from the cluster after the MEMBER_TIMEOUT value
expires (or NODE_TIMEOUT for Serviceguard/SGeRAC A.11.18 or earlier).
This is the recommended configuration because it provides the fastest cluster and RAC recovery if all
private networks for a node fail.
Figure 6 shows the supported HA configurations for common private networks for Serviceguard cluster
heartbeat, Oracle Clusterware CSS heartbeat, and RAC interconnect. In this configuration either APA
Active/Standby or Serviceguard Local LAN failover is supported.
15
Figure 6: Private network configuration option 1
15
APA is supported for networks which are used for CFS interconnect beginning with HP Serviceguard Storage Management Suite A.03.00
Recommended Configuration
2 HA choices for common dedicated network for:
• Serviceguard heartbeat
• Oracle Clusterware CSS
• RAC GCS/GES (Cache fusion/DLM)
SG Local LAN Failover Configuration
IP 1
IP 2
NS
NS
APA Active/Standby
IP 1 IP 2
NS
NS
NS: Network Switch
APA: Auto - Port