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

16
Figure 7 shows the supported HA configuration for the additional Serviceguard heartbeat network.
Figure 7: Private network configuration Option 1a
Advantages of configuration Option 1a:
• Increased resiliency in high-traffic environments, especially for high-write workloads on the common
dedicated network
• Faster cluster reformation, due to second Serviceguard heartbeat
Configuration Option 2
When one common network is used for all private traffic, heavy RAC interconnect traffic may interfere
with cluster heartbeat traffic and may cause heartbeat packets to be dropped. This can lead to a
node being evicted from the cluster. Therefore, for this configuration, the RAC interconnect network
can be configured on its own dedicated network separate from the cluster heartbeat network.
In this configuration, to ensure a fast RAC group membership recovery in case a node loses all RAC
interconnect networks, configure the RAC subnet to be monitored by Serviceguard. Otherwise, it will
take up to 17 minutes for RAC to recognize the failure and do a recovery.
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
APA Active/Standby
Configuration
NS: Network Switch
APA: Auto- Port Aggregation
IP 3
IP 4
APA
trunking and SG Local
LAN failover Configuration
NS NS