Filter
Top Products
Hitachi Command Control Interface (CCI) User and Reference Guide 125
CCI on AIX VIO should be used with the following restrictions:
1. Command device. CCI uses SCSI Path-through driver for the purpose of access of the
command device. Therefore the command device must be mapped as RAW device of
Physical Mapping Mode. At least one command device must be assigned for each VIO
Client. The CCI instance numbers among different VIO Clients must be different, even if
the command will be assigned for each VIO Client, because the command device cannot
distinguish between VIO Clients due to use of the same WWN via vscsi.
2. Lun sharing between VIO Server and VIO Clients. It is not possible to share a command
device between VIO Server and VIO Clients, and a normal Lun also cannot be shared
between VIO Server and VIO Clients.
3. Volume discovery via vscsi on VIO Client. The inqraid command discovers the volume
information by using SCSI inquiry, but VIO Client cannot report the real SCSI inquiry
(Page0 and Page83) as shown below.
Example for inqraid command:
lsdev -Cc disk | /HORCM/usr/bin/inqraid
hdisk0 -> NOT supported INQ. [AIX ] [VDASD ]
hdisk1 -> NOT supported INQ. [AIX ] [VDASD ]
hdisk2 -> NOT supported INQ. [AIX ] [VDASD ]
:
:
hdisk19 -> NOT supported INQ. [AIX ] [VDASD ]
The following commands option discovers the volumes by issuing SCSI inquiry. These
commands option cannot be used, because there is no Port/LDEV for RAID information.
raidscan –pd <device>, raidar –pd <device>, raidvchkscan –pd <device>
raidscan –find [conf] , mkconf.sh, inqraid
pairxxx –d[g] <device>, raidvchkdsp –d[g] <device>, raidvchkset –d[g] <device>
\\.\CMD-Serial#-LDEV#-Port#:/dev/rhdisk on horcm.conf
So the user needs to know the volume mapping information (/dev/rhdisk??) on VIO Client
by referring to the physical volume mapping through the VIO Server.
4. About running on VIO Server. The volume mapping( /dev/rhdisk??) on VIO Server is a
physical connection without converting SCSI Inquiry, so CCI will perform like running on
AIX 5.3. However, IBM does not allow running applications in the VIO server. Since
commands or scripts would have to be run outside the restricted shell, it may be
necessary to get IBM's approval to run in the VIO server. So the user would have to
change their scripts to run in a VIO server to issue the oem_setup_env command to
access the non-restricted shell.