Hitachi TAGMASTORE MK-90RD011-25 - Manual (Page 321)

Hitachi Command Control Interface (CCI) User and Reference Guide 303
„
Windows systems. $HORCMPERM is “\WINNT\horcmperm.conf” or
“\WINNT\horcmperm*.conf”(* is the instance number) as default.
type $HORCMPERM | x:\HORCM\etc\raidscan.exe -find inst
# The following are an example to permit the DB Volumes.
# Note: a numerical value is interpreted as Harddisk#.
# DB0 For MU# 0
Hd0-10
harddisk12 harddisk13 harddisk17
# DB1 For MU# 1
hd20-23
Verifying a group for DB1. The following is an example to verify whether DB volume
group is mapped to group (MU#1 for ShadowImage) on the horcm.conf correctly.
D:\HORCM\etc> set HORCC_MRCF=1
D:\HORCM\etc> echo hd20-23 | raidscan -find verify 1 -fd
DEVICE_FILE Group PairVol Device_File M SERIAL LDEV
Harddisk20 oradb1 oradev1 Harddisk20 1 35013 17
Harddisk21 oradb1 oradev2 Harddisk21 1 35013 18
Harddisk22 oradb oradev3 Harddisk22 1 35013 19
Harddisk23 - - - 1 35013 20
(1) If no $HORCMPERM file exists, then the following is executed to permit all volumes on
the host:
For HP-UX:
ioscan -fun | grep -e rdisk -e rdsk | /HORCM/usr/bin/raidscan -find inst
For Linux:
ls /dev/sd* | /HORCM/usr/bin/raidscan -find inst
For zLinux:
ls /dev/sd* /dev/dasd*| /HORCM/usr/bin/raidscan -find inst
For Solaris:
ls /dev/rdsk/* | /HORCM/usr/bin/raidscan -find inst
For AIX:
lsdev -C -c disk | grep hdisk | /HORCM/usr/bin/raidscan -find inst
For Tru64 UNIX:
ls /dev/rdisk/dsk* | /HORCM/usr/bin/raidscan -find inst
For Digital UNIX:
ls /dev/rrz* | /HORCM/usr/bin/raidscan -find inst
For DYNIX/ptx:
/etc/dumpconf -d | grep sd | /HORCM/usr/bin/raidscan -find inst
For IRIX64:
ls /dev/rdsk/*vol /dev/rdsk/*/*vol/* | /HORCM/usr/bin/raidscan -find inst
For OpenVMS:
/HORCM/usr/bin/raidscan -pi ‘$1$DGA0-10000 DKA0-10000 DGA0-10000’ -find inst
For Windows:
x:\HORCM\etc\raidscan.exe -pi $PhysicalDrive -find inst
Note: This registration process has risk because it is executed automatically by
/etc/horcmgr without judgment for protection mode in order to validate -fd option. This
registration brings a degradation in horcmstart.sh, but HORCM daemon has been running as
usual, and it will depend on how many devices a host has. In non-protection mode, if a user
wants to start faster at HORCM start-up, then it is required to put $HORCMPERM file of “SIZE
0 byte” as dummy file or to set HORCMPERM=MGRNOINST. At this time, -fd option will show
Device_File name as Unknown, and after a user will be able to use raidscan -find inst in
order to validate the -fd option.
Mapping to another group on horcm.conf !!
Unknown on horcm.conf !!