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

13
Public network configuration
Oracle only supports one active public network for client connections. Use APA or Serviceguard Local
LAN failover to configure network high availability for the public network. This is shown in Figure 5.
Figure 5: Configuring the public network for HA option
SG Local LAN Failover Configuration
Stationary IP 1
Stationary IP 2
VIP 1
VIP 2
Clients
NS
NS
APA Active/Standby Configuration
Stationary IP 1 Stationary IP 2
VIP 1
VIP 2
Clients
NS NS
Client access
Network
VIP: Oracle Virtual IP
NS: Network Switch
APA: Auto-Port Aggregation
The preferred method is Serviceguard local LAN failover. Serviceguard local LAN failover works very
fast for failover of an IP address to an available standby (executing a failover in 8-10 seconds with
the default 2-second polling interval). The default interval for CRS VIP polling (inter-node IP failover)
is 60 seconds.
Beginning with Serviceguard A.11.19 for HP-UX 11i v3, Serviceguard provides IP-level monitoring for
both IPv4 and IPv6 subnets, through the use of its IP Monitor feature. The IP Monitor provides the
capability to monitor network status beyond the first level of switches, and detect errors that prevent
packets from being received but do not affect the link-level health of an interface.
The best practice for RAC public network HA is to use Serviceguard local LAN failover and do the
following:
• Configure VIP with a redundant network managed by Serviceguard
13
• Configure the VIP polling interval to a value smaller than 60 seconds
14
13
See Oracle Support (
for faster VIP remote failover
http://support.oracle.com login required) Bulletin ID: 296874.1 for instruction on how to configure Oracle VIP with
redundant network managed by Serviceguard
14
See Oracle Support (http://support.oracle.com login required) Bulletin ID: 294336.1 for instruction on how to modify the VIP monitoring
interval.