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

17
Figure 8 shows the supported HA configurations for the two private networks.
Either APA Active/Standby or Serviceguard local LAN failover can be configured to provide
network HA.
In addition, if the RAC interconnect traffic requires higher bandwidth, APA trunking can be configured
to combine the bandwidth of multiple NICs in primary/standby configuration along with Serviceguard
local LAN failover for HA.
Figure 8: Private network configuration Option 2
If the RAC interconnect needs to be configured on its own dedicated network:
• Configure a common dedicated HA network for Serviceguard heartbeat, CFS interconnect (if CFS is
used), and CSS heartbeat.
• Configure the RAC interconnect on its own dedicated HA network, and configure Serviceguard to
monitor the RAC interconnect network for faster RAC group membership recovery.
• Use Serviceguard local LAN failover for network HA.
• Configure the Serviceguard heartbeat on the same network as the CSS heartbeat. CSS only
supports one active network and Serviceguard heartbeat will fail and cause the node to be evicted
if the network used by CSS fails. If you do not do this it will take a timeout of 600 seconds before
node failure and recovery will occur.
2 HA choices for common dedicated network for:
• Serviceguard heartbeat
• Oracle Clusterware CSS heartbeat
3 HA choices for dedicated network for:
• RAC GCS/GES (Cache fusion/DLM)
NS
NS
IP 3
IP 4
IP 1
IP 2
NS NS
NS
NS
IP 3
IP 4
IP 1 IP 2
NS NS
OR
SG Local LAN Failover
Configuration
NS: Network Switch
APA: Auto- Port Aggregation
IP 3 IP 4
APA
Trunking and SG Local
LAN failover Configuration
NS NS
APA Active/Standby
Configuration