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

Example:
# lsattr -El hdisk1 | grep -i LUN
lun_id 0x0 Logical unit number ID False
# lsattr -El hdisk2 | grep -i LUN
lun_id 0x1000000000000 Logical unit number ID False
To display the LUN number in HEX for each exported HP 3PAR StoreServ Storage LUN for
the IBM Virtual I/O Server, issue the following command through the IBM Virtual I/O CLI
command line:
$ lsdev -dev hdisk1 -attr | grep -i lun
Example:
$ lsdev -dev hdisk1 -attr | grep -i lun
lun_id 0xa000000000000
• To display the exported raw LUN capacity in megabytes for AIX, issue the bootinfo -s
hdisk1 command on the AIX CLI. For example:
# bootinfo -s hdisk1
5120
To display the exported raw LUN capacity in megabytes, issue bootinfo -s hdisk1 from
the oem_setup_env environment. For example:
# bootinfo -s hdisk1
71680
Creating Virtual SCSI Devices for Connected LPARs
This section describes the steps to create a virtual SCSI device to be used by a connected LPAR.
In this example, assuming that virtual SCSI devices have been defined in the managed profiles for
the IBM Virtual I/O Server and that the LPAR is receiving its virtualized SCSI devices from the virtual
I/O Server, a virtual device will be created by physical backing device hdisk22 that will be
mapped to virtual adapter vhost0.
WARNING! In an environment where two IBM Virtual I/O Servers are used to access the same
storage, it is imperative to insure that the LUN numbers are identical on each IBM Virtual I/O
Server when virtualizing those devices to an attached client. Failure to do so will result in data
corruption.
Verify that hdisk22 is connected to the IBM Virtual I/O Server by issuing the lsdev -type
disk | grep hdisk22 command.
$ lsdev -type disk | grep hdisk22
hdisk22 Available 3PAR InServ Virtual Volume
Creating Virtual SCSI Devices for Connected LPARs 31