Consolidating HP Serviceguard for Linux and Oracle RAC 10g Clusters, June 2005

Figure 1 is an example of the network configuration for a two node consolidated cluster. It
has two bonded network pairs. One dedicated to the HP Serviceguard for Linux and Oracle
heartbeats. The other for communication external to the cluster and also for HP
Serviceguard for Linux heartbeats. This is the minimum supported. Dual port NICs can be
used, but for availability, bonded pairs should NOT use the connections from a single dual
port NIC. More NICs can be added at the users’ option. If possible, these should be made
highly available via bonding, and also, if possible, should be configured as a Serviceguard
for Linux heartbeat.
The focus of the recommendations has been to eliminate the possibility of the both clusters
going down through the use of multiple heartbeat paths.
If the Quorum Service is used as a
Serviceguard arbitration mechanism to provide protection against loss of all heartbeats, then
it is required to keep the Oracle and HP Serviceguard for Linux installation with default
cluster timing settings (“pure installation”). This is necessary because there are certain timing
parameters within the two clusters that cause Serviceguard to be the cluster that determines
cluster membership first if all heartbeats are lost. Changing these settings can possibly cause
that not to be the case, defeating the purpose of the Quorum Service. When the Quorum
Service is not used the redundant heartbeat paths are protecting the cluster. In this case
there is no restriction against changing the cluster timing settings.
5