HP 3PAR AIX and IBM Virtual I/O Server Implementation Guide

From VIOS1:
$ lspath -dev hdisk22
status name parent connection
Enabled hdisk22 fscsi0 22410002ac000044,1f4000000000000
Enabled hdisk22 fscsi0 22510002ac000044,1f4000000000000
Enabled hdisk22 fscsi0 23220002ac000044,1f4000000000000
Enabled hdisk22 fscsi0 23410002ac000044,1f4000000000000
Enabled hdisk22 fscsi0 23510002ac000044,1f4000000000000
Enabled hdisk22 fscsi1 22410002ac000044,1f4000000000000
Enabled hdisk22 fscsi1 22510002ac000044,1f4000000000000
Enabled hdisk22 fscsi1 23220002ac000044,1f4000000000000
Enabled hdisk22 fscsi1 23410002ac000044,1f4000000000000
Enabled hdisk22 fscsi1 23510002ac000044,1f4000000000000
where 1f4000000000000 indicates the physical LUN number.
From VIOS2:
$ lspath -dev hdisk22
status name parent connection
Enabled hdisk22 fscsi0 22410002ac000044,1f0000000000000
Enabled hdisk22 fscsi0 22510002ac000044,1f0000000000000
Enabled hdisk22 fscsi0 23220002ac000044,1f0000000000000
Enabled hdisk22 fscsi0 23410002ac000044,1f0000000000000
Enabled hdisk22 fscsi0 23510002ac000044,1f0000000000000
Enabled hdisk22 fscsi1 22410002ac000044,1f0000000000000
Enabled hdisk22 fscsi1 22510002ac000044,1f0000000000000
Enabled hdisk22 fscsi1 23220002ac000044,1f0000000000000
Enabled hdisk22 fscsi1 23410002ac000044,1f0000000000000
Enabled hdisk22 fscsi1 23510002ac000044,1f0000000000000
where 1f0000000000000 indicates the physical LUN number.
However, hdisk23 on VIOS2 has the correct physical LUN number of 1f4000000000000.
$ lspath -dev hdisk22
status name parent connection
Enabled hdisk23 fscsi0 22410002ac000044,1f4000000000000
Enabled hdisk23 fscsi0 22510002ac000044,1f4000000000000
Enabled hdisk23 fscsi0 23220002ac000044,1f4000000000000
Enabled hdisk23 fscsi0 23410002ac000044,1f4000000000000
Enabled hdisk23 fscsi0 23510002ac000044,1f4000000000000
Enabled hdisk23 fscsi1 22410002ac000044,1f4000000000000
Enabled hdisk23 fscsi1 22510002ac000044,1f4000000000000
Enabled hdisk23 fscsi1 23220002ac000044,1f4000000000000
Enabled hdisk23 fscsi1 23410002ac000044,1f4000000000000
Enabled hdisk23 fscsi1 23510002ac000044,1f4000000000000
Therefore, when the virtual SCSI devices are created on each of the IBM Virtual I/O Servers, it is
necessary to use different hdisk definitions when using the mkvdev command to create the virtual
SCSI device;
On VIOS1, the command is:
$ mkvdev -vdev hdisk22 -vadapter vhost0 -dev newvdev
newvdev Available
Creating Virtual SCSI Devices for Connected LPARs 33