HP Serviceguard Extension for RAC (SGeRAC) manual Single Network for Cluster Communications

any network configured for Oracle cluster interconnect must also be configured as SGeRAC A.11.20 heartbeat network.

NOTE: Do not configure Serviceguard heartbeat and Oracle cluster interconnect in mutually exclusive networks.

2.Serviceguard standby interfaces must not be configured for the networks used for Serviceguard heartbeat and Oracle cluster interconnect.

For Oracle Grid Infrastructure 11.2.0.2 HAIP feature to work properly in an SGeRAC cluster and to have a resilient network configured for Serviceguard heartbeat and Oracle cluster interconnect, use one of the following network configurations:

1.Configure one or more networks, each using one HP Auto Port Aggregation (APA) interface for Oracle cluster interconnect and Serviceguard heartbeat. The APA interfaces must contain two or more physical network interfaces in hot standby mode or in LAN monitor mode.

NOTE: APA interfaces on all the cluster nodes in the same network must use the same APA mode (LAN monitor or hot standby). Since these monitoring and failover functions work differently and do not communicate with each other, unexpected failover can occur.

2.Configure two or more networks on different interfaces without any standby interface for both Oracle cluster interconnect and Serviceguard heartbeat.

Single Network for Cluster Communications

The single network configuration is the most common configuration for network installations. In this configuration, there is sufficient bandwidth for all cluster communications traffic to go through one network. If there are multiple databases, all database traffic goes through the same network.

As shown in Figure 2-1, both CSS-HB and SG-HB are on the same network. The primary and standby interface pair protects against a single network interface failure. Serviceguard monitors the network and will perform a local LAN failover (transparent to CSS and RAC) if the primary interface fails.

NOTE: A package with the CLUSTER_INTERCONNECT_SUBNET parameter is available for both Modular and Legacy packages. A package with this parameter can be configured only when all nodes of the cluster are running SGeRAC version A.11.18 or higher. For more information, see the latest edition of the Managing Serviceguard Eighteenth Edition user guide at www.hp.com/go/hpux-serviceguard-docs—> HP Serviceguard.

Figure 7 Single Network for Cluster Communications

36 Serviceguard Configuration for Oracle 10g, 11gR1, or 11gR2 RAC