HP XP RAID Manager Software - Manual (Page 171)

raidscan –f[d]
This option shows the Device_File that was registered on the group of HORCM, based on the LDEV
(as defined in the local instance configuration definition file).
# raidscan -p cl1-d -fd
Port# ,TargetID#,Lun#..Num(LDEV#....)...P/S, Status,Fence,LDEV#, Device_File
CL1-D , 3, 0...1(17)............SMPL - - -, c0t3d0
CL1-D , 3, 1...1(18)............SMPL - - -, c0t3d1
pairdisplay –f[d]
This option shows the relation between the Device_File and the paired volumes (protected volumes
and permitted volumes), based on the group, even though this option does not have any relation
with protection mode.
# pairdisplay -g oradb -fd
Group PairVol(L/R) Device_File M ,Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M
oradb oradev1(L) c0t3d0 0 35013 17..P-VOL COPY, 35013 18 -
oradb oradev1(R) c0t3d1 0 35013 18..S-VOL COPY, 35013 17 -
If either the local or the remote host (instance) has not been shown the Device_File, then pair
operations are rejected (except the local option such as “-l”) in protection mode because of Unknown
volume, as shown in the following example.
# pairdisplay -g oradb -fd
Group PairVol(L/R) Device_File M ,Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M
oradb oradev1(L) c0t3d0 0 35013 17..P-VOL COPY, 35013 18 -
oradb oradev1(R) Unknown 0 35013 ****..- -, - - -
Permitting protected volumes
Protection mode needs the recognition step to check accessible volumes and the horcm.conf at
the startup of HORCM on protection mode. The protected volumes must be registered to enable
the Data Protection Facility at each startup of HORCM, so that this registration process is executed
automatically by /etc/horcmgr.
With a $HORCMPERM file
The following is executed for registration of permitted volume file ($HORCMPERM file), if
$HORCMPERM file exists and there are permitted volumes. To permit only the volumes specified,
then the volume list must be defined in the $HORCMPERM file.
Naming of $HORCMPERM file on UNIX systems
$HORCMPERM is /etc/horcmperm.conf or /etc/horcmperm*.conf (* = instance number) by
default. For example, on HP-UX systems:
cat $HORCMPERM | /HORCM/usr/bin/raidscan -find inst
# The following are an example to permit the LVM Volume groups.
# For MU# 0
vg00 /dev/rdsk/c0t3d0 /dev/rdsk/c0t3d1
vg00 /dev/rdsk/c0t3d2 /dev/rdsk/c0t3d3
# For MU# 1
vg01 /dev/rdsk/c0t3d0 /dev/rdsk/c0t3d1
vg01 /dev/rdsk/c0t3d2 /dev/rdsk/c0t3d3
Verifying a group for vg01. The following are examples how to verify whether a LVM volume
group is mapped to group (MU#1 for Business Copy) in the horcm.conf file correctly.
# export HORCC_MRCF=1
# cat /etc/horcmperm.conf | grep vg01 | raidscan -find verify 1 -fd
OR
# vgdisplay -v /dev/vg01|grep dsk|sed ‘s/\/*\/dsk\//\/rdsk\//g’|raidscan -find verify 1 -fd
DEVICE_FILE Group PairVol Device_File M SERIAL LDEV
/dev/rdsk/c0t3d0 oradb1 oradev1 c0t3d0 1 35013 17
Data Protection facility 171