normally need to use this option. This option issues an Inquiry to a device file
from the result of STDIN. Then CCI gets Ser# and LDEV# from the RAID
storage system. Subsequently, CCI compares the Inquiry result to the
contents of horcm.conf, and the result is stored within HORCM for the
instance. At the same time CCI 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 Unknown 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.
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
Data protection operations with CCI
7-11
Command Control Interface User and Reference Guide
To Next Page
Loading...
