HP XP P9500 Storage - Manual (Page 164)

-find to make horcm.conf, because only permitted volumes are shown with host side
view. Following is an example for HP-UX systems:
# ioscan -fun | grep rdsk | raidscan -find
DEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV PRODUCT_ID
/dev/rdsk/c0t3d0 0 F CL1-D 3 0 35013 17 OPEN-3
/dev/rdsk/c0t3d1 0 F CL1-D 3 1 35013 18 OPEN-3
permission command
RAID Manager recognizes permitted volumes at the result of the permission command. The
permission
command is the -find inst option of raidscan. This option issues an inquiry
to a specified device file to get Ser# and LDEV# from the RAID storage system, and checks an
identification for volumes of horcm.conf to all of own host volumes, then stores the result within
HORCM of the instance. This permission command is started by /etc/horcmgr automatically.
The following example shows the relation between the device file and horcm.conf for a manual
operation on an HP-UX system. All volumes of ioscan are permitted.
# ioscan -fun | grep rdsk | raidscan -find inst
DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV
/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 - 35013 17
/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 0 35013 17
New options for security
raidscan –find inst
This option registers the device file name to all mirror descriptors of the LDEV map table for RAID
Manager and permitsthe matching volumes on horcm.conf in protection mode. It is started from
/etc/horcmgr automatically. You will not normally need to use this option. This option issues an
Inquiry to a device file from the result of STDIN. Then RAID Manager gets Ser# and LDEV# from
the RAID storage system. Subsequently, RAID Manager compares the Inquiry result to the contents
of horcm.conf, and the result is stored within HORCM for the instance. At the same time RAID
Manager shows the result of this option about the relation. This option will also be terminated to
avoid wasteful scanning after registration based on horcm.conf, because HORCM does not
need the registration any more.
# ioscan -fun | grep rdsk | raidscan -find inst
DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV
/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 - 35013 17
/dev/rdsk/c0t3d0 oradb oradev1 CL1-D 3 0 0 35013 17
NOTE: When multiple device files share the same LDEV, the first device file is registered to the
LDEV map table.
raidscan –find verify [MU#]
This option shows the relation between group on horcm.conf and Device_File registered to the
LDEV map tables from DEVICE_FILE of STDIN.
# ioscan -fun | grep rdsk | raidscan -find verify -fd
DEVICE_FILE Group PairVol Device_File M SERIAL LDEV
/dev/rdsk/c0t3d0 oradb oradev1 c0t3d0 0 35013 17
/dev/rdsk/c0t3d1 oradb oradev2 Unknowm 0 35013 18
/dev/rdsk/c0t3d2 - - - 0 35013 19
NOTE: It shows shared LDEV among multiple device files, if there is a difference between
DEVICE_FILE and Device_File. You can also use this option to the command device that specified
non-protection mode. It is used for the purpose to see the relation between DEVICE_FILE and the
group of horcm.conf.
164 Data protection operations with RAID Manager