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

Check/Verify the physical LUN number that is associated with hdisk22 by issuing the lsdev
-dev hdisk22 -attr | grep lun_id command.
$ lsdev -dev hdisk22 -attr | grep lun_id
lun_id 0x1f4000000000000 Logical unit number ID False
Or issue lspath -dev hdisk22 to display the path status and the physical LUN number
associated with hdisk22.
$ 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
The Physical LUN number associated with hdisk22 is "1f4"
$ mkvdev -vdev hdisk22 -vadapter vhost0 -dev newvdev
newvdev Available
Verify any needed information regarding the newly created virtual device by issuing lsmap -all
and locating the hdisk22 backing device.
$ lsmap -all
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0 U8203.E4A.10DB5C1-V5-C11 0x00000007
VTD newvdev
Status Available
LUN 0x9600000000000000
Backing device hdisk22
Physloc U789C.001.DQD2174-P1-C1-T1-W22410002AC000044-L1F4000000000000
Once the LUNs have been virtualized and exported to the appropriate VHOST device definitions
using the mkvdev command, the devices will not be visible on the AIX guest clients LPAR until the
cfgmgr command is executed.
CAUTION: If dual IBM Virtual I/O Servers are configured and using the same physical devices
from the HP 3PAR StoreServ Storage, it is important to verify that the same physical LUN numbers
are represented when creating virtual SCSI devices on each of the IBM Virtual I/O Servers. Failure
to perform this step when using dual IBM Virtual I/O Servers will result in data corruption.
Example of cautionary scenario:
Assuming that dual IBM Virtual I/O Servers are configured named VIOS1 and VIOS2.
• From the IBM Virtual I/O Server named VIOS1, hdisk22 may be backed by physical device
LUN 1f4.
• However, from the IBM Virtual I/O Server named VIOS2, hdisk22 may be backed by
physical device LUN 1f0.
32 Allocating Storage for Access by the AIX or IBM Virtual I/O Server Host