•
The
pairdisplay
command shows all volumes, so that you can confirm
non-permitted volumes. Non-permitted volumes are shown without
LDEV# information. As shown below, the LDEV# information is " **** " (-
CLI is "-").
#
pairdisplay -g oradb
Group PairVol(L/R) (Port#,TID,LU-M),Seq#, LDEV#.P/S,Status,
Seq#,P-LDEV# M
oradb oradev1(L) (CL1-D , 3, 0-0) 35013
****
..- -,- -
oradb oradev1(R) (CL1-D , 3, 1-0) 35013
****
..- -,- -
•
The
raidscan
command shows all volumes same as current specification,
because it does not need HORCM_DEV and HORCM_INST on
horcm.conf
.
If you want to know permitted volumes at
raidscan
, use
raidscan -
find
. The -find option shows device file name and storage system
information by using internal Inquiry result. You can use
raidscan -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
CCI 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 CCI and permits the matching volumes on
horcm.conf
in
protection mode. It is started from /etc/horcmgr automatically. You will not
7-10
Data protection operations with CCI
Command Control Interface User and Reference Guide
Summary of Contents for HUS VM
Page 10: ...x Command Control Interface User and Reference Guide ...
Page 18: ...xviii Preface Command Control Interface User and Reference Guide ...
Page 78: ...2 50 CCI software environment Command Control Interface User and Reference Guide ...
Page 154: ...4 8 Starting up CCI Command Control Interface User and Reference Guide ...
Page 191: ...Provisioning operations with CCI 5 37 Command Control Interface User and Reference Guide ...
Page 280: ...6 56 Data replication operations with CCI Command Control Interface User and Reference Guide ...
Page 286: ...6 62 Data replication operations with CCI Command Control Interface User and Reference Guide ...
Page 302: ...7 16 Data protection operations with CCI Command Control Interface User and Reference Guide ...
Page 324: ...8 22 Examples of using CCI commands Command Control Interface User and Reference Guide ...
Page 524: ...9 200 Troubleshooting Command Control Interface User and Reference Guide ...
Page 529: ...Command Control Interface User and Reference Guide ...