Serviceguard Extension for RAC Version A.11.20 Release Notes, April 2013

the same cluster. HP recommends to upgrade all the cluster nodes to the new release level at the
earliest.
Support for the Oracle Grid Infrastructure 11.2.0.2 HAIP with SGeRAC A.11.20
Starting with SGeRAC A.11.19, Oracle Grid Infrastructure 11.2.0.2 HAIP feature can be configured
and used in an SGeRAC cluster.
The following network configuration requirements must be met to use the Oracle Grid Infrastructure
11.2.0.2 HAIP feature in an SGeRAC cluster:
1. Any networks in the SGeRAC A.11.20 cluster configured for heartbeat must also be configured
as Oracle cluster interconnect network in the Oracle Grid Infrastructure 11.2.0.2. Similarly
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. When configuring standby interface for the network used for Serviceguard heartbeat and
Oracle cluster interconnect, register the standby interface in the Oracle Clusterware Registry
(OCR) using the oifcfg command.
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.
3. Configure one network with standby interfaces for both Oracle cluster interconnect and
Serviceguard heartbeat and register the standby network by Oracle oifcfg command.
Support for Logical Volume Manager Version 2.0 and later
Logical Volume Manager (LVM) 2.0 volume groups that remove some of the limitations imposed
by LVM 1.0 volume groups can be used on systems running HP-UX 11i v3 0803 Fusion or later
with LVM version B.11.31.0809 and Serviceguard and SGeRAC A.11.20.
NOTE: You are not required to move to LVM 2.0 volume groups. If you do use LVM 2.0 volume
groups, you can manage them with the same commands as before. You may need to make minor
changes to any scripts you use that parse the output of lvdisplay, vgdisplay, pvdisplay
or vgscan, as the output of these commands has changed slightly. In addition, new options are
available for some commands.
For more information, see the white paper LVM Version 2.0 Volume Groups in HP-UX 11i v3 at
www.hp.com/go/hpux-core-docs —> HP-UX 11i v3 —> white papers. For information
about all other aspects of LVM on HP-UX 11i v3, see the HP-UX System Administrator's Guide:
Logical Volume Management HP-UX 11i Version 3 at www.hp.com/go/hpux-core-docs —>
HP-UX 11i v3 —> User guide.
What’s in this Version 13