Using Serviceguard Extension for RAC Version A.11.20 - (August 2011)

Figure 10 1-1 mapping between SLVM logical and physical volumes for ASM configuration

If the LVM patch PHKL_36745 (or equivalent) is installed in the cluster, a timeout equal to (2* PV

timeout) will suffice to try all paths.

The SLVM volume groups are marked as shared volume groups and exported across the SGeRAC

cluster using standard SGeRAC procedures. As noted above, multiple physical paths to each

physical volume should be configured using the LVM PV Links feature or a separate multipathing

product such as HP StorageWorks Secure Path.

Please note that, for the case in which the SLVM PVs being used by ASM are disk array LUs, the

requirements in this section do not place any constraints on the configuration of the LUs. The LUs

may be configured with striping, mirroring and other characteristics at the array level, following

guidelines provided by Oracle and the array provider for use by ASM.

Sample Command Sequence for Configuring SLVM Volume Groups

This section includes an example of a command sequence that can be used to prepare SLVM

Logical Volumes for use by ASM to meet the requirements specified above.

The scenario for our example is that we are preparing a new volume group named vgora_asm

with two PVs, each with two physical paths. The physical paths for the first PV are /dev/dsk/

c9t0d1 and /dev/dsk/c10t0d1 and those for the second PV are /dev/dsk/c9t0d2 and

/dev/dsk/c10t0d2.

1. Create the volume group with the two PVs, incorporating the two physical paths for each

(choosing hh to be the next hexadecimal number that is available on the system, after the

volume groups that are already configured) :

# pvcreate -f /dev/dsk/c9t0d1

# pvcreate -f /dev/dsk/c9t0d2

# mkdir /dev/vgora_asm

# mknod /dev/vgora_asm/group c 64 0xhh0000

# vgcreate /dev/vgora_asm /dev/dsk/c9t0d1

# vgextend /dev/vgora_asm /dev/dsk/c9t0d2

SG/SGeRAC Support for ASM on HP-UX 11i v2 71