Managing Serviceguard Eighteenth Edition, September 2010
3. Create the partition; for example (using partition.txt as input):
/usr/sbin/idisk -w -p -f partition.txt /dev/rdsk/c1t4d0
Or, on an HP-UX 11i v3 system using agile addressing (see “About Device File
Names (Device Special Files)” (page 106):
/usr/sbin/idisk -w -p -f partition.txt /dev/rdisk/disk12
NOTE: Device files for partitions cannot be cluster-wide DSFs (cDSFs). For more
information about cDSFs, see “About Cluster-wide Device Special Files (cDSFs)”
(page 135).
This will create three device files, for example
/dev/dsk/c1t4d0s1, /dev/dsk/c1t4d0s2, and /dev/dsk/c1t4d0s3
or:
/dev/disk/disk12_p1, /dev/disk/disk12_p2, and /dev/disk/disk12_p3
NOTE: The first partition, identified by the device file /dev/dsk/c1t4d0s1 or
/dev/disk/disk12_p1 in this example, is reserved by EFI and cannot be used
for any other purpose.
4. Create the device files on the other cluster nodes.
Use the command insf -e on each node. This will create device files
corresponding to the three partitions, though the names themselves may differ
from node to node depending on each node’s I/O configuration.
5. Define the lock LUN; see “Defining the Lock LUN”.
Defining the Lock LUN
Use cmquerycl -L to create a cluster configuration file that defines the lock LUN.
• If the pathname for the lock LUN is the same on all nodes, use a command such
as:
cmquerycl -C $SGCONF/config.ascii -L /dev/dsk/c0t1d1 -n
<node1> -n <node2>
• If the pathname for the lock LUN is different on some nodes, you must specify the
path on each node; for example (all on one line):
cmquerycl -C $SGCONF/config.ascii -n <node1> -L
/dev/dsk/c0t1d1 -n <node2> -L /dev/dsk/c0t1d2
228 Building an HA Cluster Configuration